Multicast heartbeat signaling

• US 20070041327A1
• Filed: 08/16/2005
• Published: 02/22/2007
• Est. Priority Date: 08/16/2005
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Andreasen, Flemming, Nieuwesteeg, Leo, Foster, William, McDaniel, David
• Application Number:
  US11/204,964
• Publication Number:
  US 20070041327A1
• Time in Patent Office: Days
• US Class Current: 370/242
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A mechanism that provides for communication of heartbeat signals from servers (call agents) to clients (gateways) in a packet telephony network environment. Clients listen for receipt of multicast heartbeats from any of the servers that may be part of a multicast group. A client assigned to a particular server for control messaging, upon failure to receive a response to a message sent to the assigned server and failure to receive a heartbeat from the assigned server, may select a second server from among the servers and re-send the message to the second server. Without receipt of heartbeat signals, the client defaults to a normal retry behavior for re-sending the message first to the assigned server a number of times before attempting to re-send the message to the second server. With receipt of the heartbeat from the second server, the client adopts an aggressive retry behavior by re-sending the message to the assigned server a lesser number of retries before attempting to re-send the message to the second server. The clients use the multicast heartbeats as a hint, allowing them to switch to the more aggressive retry behavior and consequently reduce the time to re-associate with a new server and re-establish a new security association (if IPsec is used), resulting in a drastic reduction in service delay due to server failures.

Claims

1. A method of communication by a client over a network having plural servers, one of the servers assigned to receive messages from the client, the method comprising:

listening for receipt of multicast heartbeats from any of the servers;

sending a message to the assigned server;

upon failure to receive a response to the message sent to the assigned server and failure to receive a heartbeat from the assigned server, selecting a second server from among the servers and re-sending the message to the second server.

2. The method of claim 1 wherein each multicast heartbeat includes a payload having a preference value, and selecting includes:

selecting the second server based on the preference value.

3. The method of claim 2 wherein the preference value indicates relative loading of the corresponding server, and the client selects the least loaded server.

4. The method of claim 1 further including:

if a multicast heartbeat is received from at least one other server, re-sending the message to the assigned server up to a first number of retries before re-sending the message to the second server, otherwise re-sending the message to the assigned server up to a second number of retries before re-sending the message to the second server where the first number is less than the second number.

5. The method of claim 1 wherein the assigned server is a primary server and the second server is a backup server that sends multicast heartbeats upon failover of the primary server.

6. The method of claim 5 wherein the backup server takes over the virtual IP address of the primary server upon failover of the primary server.

7. The method of claim 6 wherein each multicast heartbeat includes a payload that includes a server identifier, and the client distinguishes the primary server from the backup server based on the server identifier.

8. The method of claim 1 wherein the client is a gateway or media termination adapter and the servers are call agents in a VoIP network.

9. A method of communication by a client over a network having a primary server and a backup server, the method comprising:

establishing IPsec security association between the client and the primary server;

listening for receipt of multicast heartbeats, each having a source IP address and a payload that includes a server identifier;

sending a message to the IP address of the primary server;

upon receipt of one or more multicast heartbeats having the same source IP address as the IP address of the primary server and the server identifier of the backup server, and failure to receive a response to the message sent to the IP address of the primary server, re-establishing IPsec security association between the client and the backup server.

10. The method of claim 9 further including:

re-sending the message to the IP address of the primary server up to a first number of retries before re-establishing IPsec security association.

11. The method of claim 9 further including:

re-sending the message to the IP address of the primary server after re-establishing IPsec security association.

12. The method of claim 9 wherein the client is a gateway or media termination adapter and the servers are call agents in a VoIP network.

13. A method of reducing service delay for a client over a network having a primary server and a backup server, the method comprising:

monitoring the status of the primary server at the backup server;

upon failover of the primary server,

starting transmission of multicast heartbeats from the backup server to the client; and

processing messages received from the client at the backup server.

14. The method of claim 13 further including taking over the virtual IP address of the primary server at the backup server upon failover, each multicast heartbeat including a server identifier to distinguish between the primary server and the backup server.

15. The method of claim 14 wherein failover of the primary server includes loss of IPsec security association between the primary server and the client, the method further including upon failover of the primary server:

re-establishing IPsec security association between the backup server and the client.

16. A method of reducing service delay for a client over a network having plural servers, one of the servers assigned to receive messages from the client, the method comprising:

sending multicast heartbeats from each of the servers to the client, each heartbeat including a preference value; and

upon failover of the assigned server, processing at one of the servers messages directed from the client based on the preference values.

17. The method of claim 16 wherein the preference value indicates relative loading of the corresponding server.

18. A client for communicating over a network having plural servers including an assigned server, the client comprising:

a receiver that receives multicast heartbeats from any of the servers;

a transmitter that sends a message to the assigned server;

a heartbeat reception component that selects a second server from among the servers based on a preference value in a payload of the received heartbeat, the transmitter re-sending the message to the second server upon failure to receive a response to the message sent to the assigned server and failure to receive a heartbeat from the assigned server.

19. The client of claim 18 wherein the preference value indicates relative loading of the corresponding server, and the client selects the least loaded server.

20. The client of claim 18 wherein if a multicast heartbeat is received from at least one other server, the transmitter re-sends the message to the assigned server up to a first number of retries before re-sending the message to the second server, otherwise re-sending the message to the assigned server up to a second number of retries before re-sending the message to the second server where the first number is less than the second number.

21. The client of claim 18 wherein the assigned server is a primary server and the second server is a backup server that sends multicast heartbeats upon failover of the primary server and wherein each multicast heartbeat includes a payload that includes a server identifier, and the client distinguishes the primary server from the backup server based on the server identifier.

22. The client of claim 18 wherein the client is a gateway or media termination adapter and the servers are call agents in a VoIP network.

23. Apparatus for communicating over a network having plural servers including an assigned server, the apparatus comprising:

means for listening for receipt of multicast heartbeats from any of the servers;

means for sending a message to the assigned server;

means for selecting a second server from among the servers and means for re-sending the message to the second server upon failure to receive a response to the message sent to the assigned server and failure to receive a heartbeat from the assigned server.

24. Apparatus for communicating over a network having a primary server and a backup server, the apparatus comprising:

means for establishing IPsec security association with the primary server;

means for listening for receipt of multicast heartbeats, each having a source IP address and a payload that includes a server identifier;

means for sending a message to the IP address of the primary server;

means for re-establishing IPsec security association with the backup server upon receipt of one or more multicast heartbeats having the same source IP address as the IP address of the primary server and the server identifier of the backup server, and failure to receive a response to the message sent to the IP address of the primary server.

25. Apparatus for reducing service delay in a network having a primary server and a backup server, the apparatus comprising:

means for monitoring the status of the primary server at the backup server;

means for starting transmission of multicast heartbeats from the backup server to the client and means for processing messages received from the client at the backup server upon failover of the primary server.

26. Apparatus for reducing service delay for a client over a network having plural servers, one of the servers assigned to receive messages from the client, the apparatus comprising:

means for sending multicast heartbeats from each of the servers to the client, each heartbeat including a preference value; and

means for processing at one of the servers messages directed from the client based on the preference values upon failover of the assigned server.

27. A server for reducing service delay for clients over a network, the server comprising:

a packet network interface for receiving messages from the clients; and

a heartbeat transmission component for sending multicast heartbeats periodically to the clients.

28. The server of claim 27 wherein the heartbeat comprises a payload that includes a server identifier and a preference value that indicates relative loading of the server.

29. The server of claim 27 wherein the server is a call agent in a VoIP network.

30. A backup server for reducing service delay for clients over a network that includes a primary server, the backup server comprising:

a heartbeat transmission component that sends multicast heartbeats periodically to the clients upon a failover of the primary server; and

a packet network interface for receiving messages from the clients.

31. The backup server of claim 30 wherein the heartbeat comprises a payload that includes a server identifier and a preference value that indicates relative loading of the backup server.

32. The backup server of claim 30 wherein the backup server is a call agent in a VoIP network.