System and method for router keep-alive control

• US 20030084161A1
• Filed: 09/17/2001
• Published: 05/01/2003
• Est. Priority Date: 09/17/2001
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Foundry Networks LLC (Broadcom, Inc.)
• Inventors: Watson, Thomas Lee, Visser, Lance Arnold, Gillam, David A.
• Granted Patent: US 7,788,381 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168

Abstract

The real-time aspects of keep-alive generation are removed from the dynamic routing protocol (DRP) application and are embedded within a Unix-based operating system, which is programmed by DRP. A keep-alive control provides the ability to create a keep-alive message and a timeout interval on a TCP socket. Each socket can have an independent keep-alive message and timeout interval. A keep-alive message is sent whenever the TCP socket sends no normal user output for a duration exceeding the timeout interval. A timeout interval is normally specified in seconds and a keep-alive message is user definable and must not exceed a predetermined length in bytes. System calls are used to set the timeout interval and keep-alive message independently. Both a timeout and a keep-alive message must be set before the timeout becomes active.

Claims

1. A method of router keep-alive message control comprising:

modifying system software of a router;

programming a real-time kernel underlying a routing protocol process to perform embedded keep-alive message processing, such that said routing protocol programs said real-time kernel;

after said programming, relieving said routing protocol from additional responsibility for performing keep-alive message processing; and

periodically sending from said underlying real-time kernel keep-alive messages of user definable length, whenever no user output message has been sent for a predetermined duration.

2. The method of claim 1 wherein said modifying comprises establishing at least one programming interface socket.

3. The method of claim 2 wherein said programming comprises setting a timeout interval and a prototypical keep-alive message independently for said socket.

4. The method of claim 3 wherein said socket is a TCP socket.

5. The method of claim 4 wherein said setting comprises using system calls for adding fields to a TCP control block associated with said socket.

6. The method of claim 3 further comprising activating said timeout interval, provided that said programming interface socket, said timeout interval, and said prototypical keep-alive message are all established.

7. The method of claim 6 wherein said periodically sending comprises:

a. establishing a current time;

b. resetting a scheduled time equal to said current time plus said timeout interval;

c. if a user output message is sent before said scheduled time, then dropping said keep-alive message and returning to resetting operation b;

otherwise

d. when said current time equals said scheduled time, then rescheduling said keep-alive message replicating said prototypical keep-alive message, sending said keep-alive message, and returning to resetting operation b.

8. The method of claim 7 wherein said operation 7d further comprises inserting an incrementing sequence number into said keep-alive message.

9. The method of claim 7 wherein said routing protocol comprises a dynamic routing protocol (DRP).

10. The method of claim 9 wherein said real-time kernel is the kernel of a real-time operating system.

11. The method of claim 10 wherein said operating system is a Unix-based operating system.

12. The method of claim 11 wherein said operating system is a version of FreeBSD.

13. The method of claim 12 wherein said DRP utilizes the Border Gateway Protocol (BGP) layered on top of TCP.

14. The method of claim 12 wherein said FreeBSD operating system and said DRP routing protocol run on a master control processor (MCP) within said router.

15. The method of claim 7 wherein said keep-alive processing is performed on multiple processors distributed throughout a router.

16. The method of claim 15 wherein said routing protocol comprises an Open Shortest Path First (OSPF) protocol.

17. The method of claim 15 wherein said multiple distributed processors comprise packet forwarding engines.

18. The method of claim 7 wherein said programming further comprises inserting entries for each said timeout interval and prototypical keep-alive message in a queue of scheduled activities.

19. The method of claim 18 wherein said periodically sending further comprises timeout processing of said queue of scheduled activities by a conventional interrupt handler in response to interrupts generated by a hardware clock.

20. The method of claim 5 wherein said modifying comprises:

modifying a per-socket data structure to establish a timeout timer, timeout value, and keep-alive message;

modifying a TCP layer of system calls to initialize said per-socket data structure and start the timer;

creating a timeout routine to send said keep-alive message;

modifying a TCP socket output function to reset said keep-alive timer whenever said output function issues a user output message;

deallocating any keep-alive resources associated with a TCP socket when said TCP socket is destroyed; and

maintaining state associated with said socket output packets.

21. The method of claim 20 wherein said modifying further comprises adding two state variables counting respectively keep-alive messages that have been sent and keep-alive messages that have been dropped.

22. A system for router keep-alive message control comprising a plurality of network routers operable to exchange keep-alive messages, said plurality of routers including a router having modified router software comprising a real-time kernel programmed by a routing protocol process to perform embedded keep-alive message processing, said real-time kernel underlying said routing protocol process, such that after programming said real-time kernel, said routing protocol is relieved from additional responsibility for performing keep-alive message generation.

23. The system of claim 22 wherein said modified router software further comprises at least one programming interface socket.

24. The system of claim 23 wherein said modified router software further comprises a timeout interval and a prototypical keep-alive message set in said socket.

25. The system of claim 24 wherein said socket is a TCP socket.

26. The system of claim 25 wherein said modified router software further comprises an incrementing sequence number to be inserted into said keep-alive message.

27. The system of claim 22 wherein said routing protocol comprises a dynamic routing protocol (DRP).

28. The system of claim 27 wherein said real-time kernel is the kernel of a real-time operating system.

29. The system of claim 28 wherein said operating system is a Unix-based operating system.

30. The system of claim 29 wherein said operating system is a version of FreeBSD.

31. The system of claim 30 wherein said FreeBSD operating system and DRP software are configured to run on a master control processor (MCP) within said router.

32. The system of claim 22 configured such that said keep-alive processing is performed on multiple processors distributed throughout said router.

33. The system of claim 32 wherein said routing protocol comprises an Open Shortest Path First (OSPF) protocol.

34. The system of claim 32 wherein said multiple distributed processors comprise packet forwarding engines.

35. The system of claim 24 wherein said modified router software further comprises entries for each said timeout interval and prototypical keep-alive message within a queue of scheduled activities.

36. The system of claim 35 wherein said modified router software further comprises an interrupt handler configured to perform timeout processing of said queue of scheduled activities in response to interrupts generated by a hardware clock.

37. The system of claim 22 wherein said modified router software further comprises two state variables configured respectively to count keep-alive messages that have been sent and keep-alive messages that have been dropped.