IP Library Granted Patent US 7,392,424
Granted Patent B2
US 7,392,424 · App. 11/124,134 · Granted Jun 24, 2008

Router and routing protocol redundancy

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,392,424
App. No.
11/124,134
Granted
Jun 24, 2008
Kind
B2
Abstract

A router and routing protocol redundancy are disclosed to reduce service outage or degradation for a network device and thus to increase service availability on a network due to software and hardware failures of the network device. A network device such as router includes a redundancy platform having an active controller system and a standby controller system. A routing protocol state change is received or generated by the active controller system. The received or generated routing protocol state change is replicated to the standby controller system. By replicating the routing protocol state change, the standby controller system can maintain the routing protocol sessions for the network device if a failure occurs in the active controller system. Furthermore, the routing protocol states are maintained in realtime to handle the dynamic changes created by routing protocols.

Claims (62)

1. An apparatus comprising:

a receiver configured to receive a routing protocol state change from a peer node;

a transmitter configured to send the routing protocol state change to a second controller,

wherein the receiver is further configured to receive a commitment to the routing protocol state change from the second controller; and

a committer configured to commit to the routing protocol state after receiving the commitment from the second controller,

wherein the transmitter is further configured to send the commitment to the peer node.

2. The apparatus of claim 1 , wherein the receiver is further configured to send the routing protocol state change to a routing protocol after receiving the commitment from the second controller.

3. The apparatus of claim 1 , wherein the transmitter is further configured to send the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.

4. The apparatus of claim 1 , wherein the routing protocol state change comprises a border gateway protocol (BGP) state change, a routing internet protocol (RIP) state change, an open shortest path first protocol (OSPF) state change, or an intermediate system-to-intermediate system protocol (IS-IS) state change.

5. The apparatus of claim 1 , further comprising:

a replicator configured to replicate selectively the received or generated routing protocol message to the second controller.

wherein the receiver is further configured to receive or generate a routing protocol message.

6. The apparatus of claim 1 , further comprising:

a detector configured to detect a failure, wherein the second controller is configured to maintain the same routing protocol state changes in the apparatus prior to the failure.

7. An apparatus comprising:

a generator configured to generate a routing protocol state change to a peer node,

a transmitter configured to send the routing protocol state change to a second controller;

a receiver configured to receive a commitment to the routing protocol state change from the second controller; and

a committer configured to commit to the routing protocol state change after receiving the commitment from the second controller,

wherein the transmitter further configured to send the commitment to the peer node.

8. The apparatus of claim 7 , wherein the transmitter is further configured to send the routing protocol state change to a routing protocol after receiving the commitment from the second controller.

9. The apparatus of claim 7 , wherein the routing protocol state change comprises a border gateway protocol (BGP) state change, a routing internet protocol (RIP) state change, an open shortest path first protocol (OSPF) state change, or an intermediate system-to-intermediate system protocol (IS-IS) state change.

10. The apparatus of claim 7 , further comprising:

a replicator configured to replicate selectively the received or generated routing protocol message to the second controller,

wherein the receiver is further configured to receive or generate a routing protocol message.

11. The apparatus of claim 7 , further comprising:

a detector configured to detect a failure,

wherein the second controller is configured to maintain the same routing protocol state changes in the first controller prior to the failure.

12. An apparatus comprising:

a receiver configured to receive a routing protocol state change from a second controller;

a transmitter configured to send a commitment to the routing protocol state change to the second controller; and

a committer configured to commit to the routing protocol state change after sending the commitment to the second controller,

wherein the transmitter further configured to send the commitment to a peer node.

13. A method comprising:

receiving a routing protocol state change from a peer node by a first controller;

sending the routing protocol state change to a second controller;

receiving a commitment to the routing protocol state change by the first controller from the second controller;

committing to the routing protocol state change in the first controller; and

sending the commitment to the peer node by the first controller.

14. The method of claim 13 , further comprising:

sending the routing protocol state change to a routing protocol after receiving the commitment from the second controller.

15. The method of claim 13 , further comprising: sending the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.

16. A method comprising:

generating a routing protocol state change to a peer node by a first controller;

sending the routing protocol state change to a second controller;

receiving a commitment to the routing protocol state change by the first controller from the second controller;

committing to the routing protocol state change in the first controller; and

sending the commitment to the peer node by the first controller.

17. The method of claim 16 , further comprising:

sending the routing protocol state change to a routing protocol after generating the commitment to the second controller.

18. An apparatus comprising:

receiving means for receiving a routing protocol state change from a peer node by a first controller;

sending means for sending the routing protocol state change to a second controller;

receiving means for receiving a commitment to the routing protocol state change by the from the second controller;

committing means for committing to the routing protocol state change in the first controller; and

sending means for sending the commitment to the peer node by the first controller.

19. An apparatus comprising:

generating means for generating a routing protocol state change to a peer node by a first controller;

sending means for sending the routing protocol state change to a second controller;

receiving means for receiving a commitment to the routing protocol state change by the first controller from the second controller;

committing means for committing to the routing protocol state change in the first controller; and

sending means for sending the commitment to the peer node by the first controller.

Assignments (12)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
MERGER Recorded Aug 3, 2017
From: NOKIA INTELLIGENT EDGE ROUTERS, INC.
To: NOKIA INC.
Reel/Frame 043192/0529 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2017
From: HO, CHI FAI; GUPTA, AMAR; GRANDHI, MADHU; BACHMUTSKY, ALEX
To: AMBER NETWORKS
Reel/Frame 043192/0393 →
MERGER Recorded Aug 3, 2017
From: AMBER NETWORKS
To: NOKIA INTELLIGENT EDGE ROUTERS INC.
Reel/Frame 043192/0478 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2015
From: NOKIA CORPORATION
To: NOKIA TECHNOLOGIES OY
Reel/Frame 035602/0284 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2014
From: NOKIA INC.
To: NOKIA CORPORATION
Reel/Frame 032180/0810 →