System and method using RSVP hello suppression for graceful restart capable neighbors

US9294343B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9294343-B2
Application numberUS-201213722152-A
CountryUS
Kind codeB2
Filing dateDec 20, 2012
Priority dateJul 27, 2012
Publication dateMar 22, 2016
Grant dateMar 22, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A system, method and apparatus adapting one or more routers or nodes in a network to operate in a first mode to exchange hello messages with neighboring nodes to indicate thereby active or live status, and to operate in a second mode to avoid the use of hello messages by opportunistically relying upon service or management protocols to convey active or live status.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for use at a network node, the method comprising: establishing a neighboring node relationship with a neighboring node using a Resource Reservation Protocol (RSVP) HELLO message exchange; in a first mode of operation with respect to the neighboring node, using RSVP HELLO messages to determine whether the neighboring node is in a failed state; in response to receiving an indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node and based on a determination that a Bi-directional Forwarding Detection (BFD) session is active for the neighboring node, entering a second mode of operation with respect to the neighboring node; in the second mode of operation with respect to the neighboring node, suppressing transmission of RSVP HELLO messages toward the neighboring node and using the BFD session to determine whether the neighboring node is in a failed state. 2. The method of claim 1 , further comprising: in response to the use of the Bi-directional Forwarding Detection (BFD) session, transmitting HELLO suppression active indicia toward one or more upstream neighboring nodes. 3. The method of claim 2 , further comprising: in response to receiving the indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node, transmitting HELLO suppression active indicia toward one or more upstream neighboring nodes. 4. The method of claim 1 , wherein the indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node comprises inclusion of a Hello_Suppress object within an RSVP HELLO message. 5. The method of claim 4 , wherein said Hello_Suppress object is set to a first state to indicate the first mode of operation and to a second state to indicate the second mode of operation. 6. The method of claim 5 , wherein said Hello_Suppress object includes data indicative of a revised time interval within which failure to receive an RSVP HELLO message is indicative of a failed neighboring node. 7. The method of claim 6 , wherein said data indicative of a revised time interval comprises an existing time interval multiplier. 8. The method of claim 6 , wherein said data indicative of a revised time interval comprises a specific time interval. 9. The method of claim 1 , further comprising: exiting the second mode of operation with respect to the neighboring node based on a determination that the BFD session is inactive for the neighboring node. 10. The method of claim 1 , further comprising: returning to the first mode of operation with respect to the neighboring node in response to receiving an indication from the neighboring node that RSVP HELLO message suppression is inactive at the neighboring node. 11. The method of claim 10 , wherein the indication from the neighboring node that RSVP HELLO message suppression is inactive at the neighboring node comprises exclusion of a Hello_Suppress object within an RSVP HELLO message. 12. The method of claim 1 , wherein the indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node comprises an RSVP HELLO message including a Hello_Suppress object having a REQUEST field set to a TRUE value and an ACK field set to a FALSE value, the method further comprising: based on a determination that RSVP HELLO message suppression is active at the network node, propagating, from the network node toward the neighboring node, a second RSVP HELLO message including a second Hello_Suppress object having a REQUEST field set to the TRUE value and an ACK field set to the TRUE value. 13. An apparatus, comprising: a processor and a memory communicatively connected to the processor, the processor configured to: establish a neighboring node relationship with a neighboring node using a Resource Reservation Protocol (RSVP) HELLO message exchange; in a first mode of operation with respect to the neighboring node, use RSVP HELLO messages to determine whether the neighboring node is in a failed state; in response to receiving an indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node and based on a determination that a Bi-directional Forwarding Detection (BFD) session is active for the neighboring node, enter a second mode of operation with respect to the neighboring node; in the second mode of operation with respect to the neighboring node, suppress transmission of RSVP HELLO messages toward the neighboring node and use the BFD session to determine whether the neighboring node is in a failed state. 14. The apparatus of claim 13 , wherein the indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node comprises an RSVP HELLO message including a Hello_Suppress object having a REQUEST field set to a TRUE value and an ACK field set to a FALSE value, wherein the processor is configured to: based on a determination that RSVP HELLO message suppression is active at the network node, propagate, from the network node toward the neighboring node, a second RSVP HELLO message including a second Hello_Suppress object having a REQUEST field set to the TRUE value and an ACK field set to the TRUE value. 15. A non-transitory computer readable storage medium storing instructions which, when executed by a computer, adapt the operation of the computer to provide a method, the method comprising: establishing a neighboring node relationship with a neighboring node using a Resource Reservation Protocol (RSVP) HELLO message exchange; in a first mode of operation with respect to the neighboring node, using RSVP HELLO messages to determine whether the neighboring node is in a failed state; in response to receiving an indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node and based on a determination that a Bi-directional Forwarding Detection (BFD) session is active for the neighboring node, entering a second mode of operation with respect to the neighboring node; in the second mode of operation with respect to the neighboring node, suppressing transmission of RSVP HELLO messages toward the neighboring node and using the BFD session to determine whether the neighboring node is in a failed state. 16. The non-transitory computer readable storage medium of claim 15 , wherein the indication from the neighboring node that RSVP HELLO message suppression is active at the neighboring node comprises an RSVP HELLO message including a Hello_Suppress object having a REQUEST field set to a TRUE value and an ACK field set to a FALSE value, the method further comprising: based on a determination that RSVP HELLO message suppression is active at the network node, propagating, from the network node toward the neighboring node, a second RSVP HELLO message including a second Hello_Suppress object having a REQUEST field set to the TRUE value and an ACK field set to the TRUE value. 17. A computer program product having stored thereon computer instructions which, when processed by a computer, adapt the operation of the computer to provide a method, the method comprising: establishing a neighboring node relationship with a neighboring node using a Resource Reservation Protocol (RSVP) HELLO message exchange; in a first mode of operation with respect to the neighboring node, using RSVP HELLO messages to determine whether the neighboring node is in a failed state; in response to receiving an indication from the neighboring node that RSVP HELLO message suppression is

Assignees

Inventors

Classifications

  • at intermediate nodes, e.g. resource reservation protocol [RSVP] · CPC title

  • using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title

  • Additional information in the notification, e.g. enhancement of specific meta-data · CPC title

  • by balancing the load, e.g. traffic engineering · CPC title

  • using route fault recovery · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9294343B2 cover?
A system, method and apparatus adapting one or more routers or nodes in a network to operate in a first mode to exchange hello messages with neighboring nodes to indicate thereby active or live status, and to operate in a second mode to avoid the use of hello messages by opportunistically relying upon service or management protocols to convey active or live status.
Who is the assignee on this patent?
Jain Pradeep G, Singh Kanwar D, Ramamurthy Santoshkumar, and 1 more
What technology area does this patent fall under?
Primary CPC classification H04L41/0686. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Mar 22 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).