IP Library Granted Patent US 6,910,148
Granted Patent B1
US 6,910,148 · App. 09/733,284 · Granted Jun 21, 2005

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 6,910,148
App. No.
09/733,284
Granted
Jun 21, 2005
Kind
B1
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 (47)

1. In a network device having a redundancy platform including an active controller system and a standby controller system, a method comprising:

receiving a routing protocol state change from a peer node by the active controller system;

sending the routing protocol state change to the standby controller system;

receiving a commitment to the routing protocol state change by the active controller system from the standby controller system;

committing to the routing protocol state change in the active controller system; and

sending the commitment to the peer node by the active controller system.

2. The method of claim 1 , further comprising:

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

3. The method of claim 1 , further comprising:

sending the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.

4. The method of claim 1 , wherein the routing protocol state change includes 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 method of claim 1 , further comprising:

receiving or generating a routing protocol message by the active controller system; and

selectively replicating the received or generated routing protocol message in the standby controller system.

6. The method of claim 5 , wherein the routing protocol message includes a BGP message, a RIP message, an OSPF message, or an IS-IS message.

7. The method of claim 1 , further comprising:

detecting a failure in the active controller system; and

maintaining the same routing protocol state changes in the active controller system prior to failure in the standby controller system.

8. The method of claim 1 , further comprising:

performing Internet Protocol (IP) layer 3 service or a Multiprotocol Label Switching (MPLS) service.

9. A network device comprising:

a standby controller; and

an active controller to receive a routing protocol state change from a peer node, to send the routing protocol state change to the standby controller, to receive a commitment to the routing protocol state change from the standby controller system, to commit to the routing protocol state after receiving the commitment from the standby controller, and to send the commitment to the peer node.

10. The network device of claim 9 , wherein the active controller is to send the routing protocol state change to a routing protocol after receiving the commitment from the standby controller.

11. The network device of claim 9 , wherein the active controller is to send the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.

12. The network device of claim 9 , wherein the routing protocol state change includes 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.

13. The network device of claim 9 , wherein the active controller system is to receive or generate a routing protocol message and to replicate selectively the received or generated routing protocol message to the standby controller system.

14. The network device of claim 13 , wherein the routing protocol message includes a BGP message, a RIP message, an OSPF message, or an IS-IS message.

15. The network device of claim 9 , wherein the active controller system is to detect a failure and the standby controller system is to maintain the same routing protocol state changes in the active controller system prior to the failure.

16. The network device of claim 9 , wherein the active controller system or standby controller system is to perform an Internet Protocol (IP) layer 3 service or a Multiprotocol Label Switching (MPLS) service.

17. The network device of claim 9 , wherein the network device includes a network router, switch, optical switch, bridge, hub, or gateway.

18. A machine-readable medium that provides instructions, which if executed by a processor, cause the processor to perform the operations comprising:

receiving a routing protocol state change from a peer node by an active controller system;

sending the routing protocol state change to a standby controller system;

receiving a commitment to the routing protocol state change by the active controller system from the standby controller system;

committing to the routing protocol state change in the active controller system; and

sending the commitment to the peer node by the active controller system.

19. The machine-readable medium of claim 18 , that further provides instructions, which if executed by the processor, cause the processor to perform the operations comprising:

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

20. The machine-readable medium of claim 18 , that further provides instructions, which if executed by the processor, cause the processor to perform the operations comprising:

sending the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.

21. A system having a redundancy platform including an active controller system and a standby controller system, the system comprising:

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

first sending means for sending the routing protocol state change to the standby controller system;

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

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

second sending means for sending the commitment to the peer node by the active controller system.

Assignments (10)
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: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
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 →
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: NOKIA USA INC.
Reel/Frame 043879/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 →
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/0330 →
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 →