EFFICIENT LOAD BALANCING AND HEARTBEAT MECHANISM FOR TELECOMMUNICATION ENDPOINTS

• US 20080317060A1
• Filed: 08/29/2008
• Published: 12/25/2008
• Est. Priority Date: 06/28/2005
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Technology Corporation Miami Lakes FLA US
• Inventors: Balasaygun, Mehmet C., Marwah, Manish, Boyle, Frank John, Moon, Sung H., Schmidt, Nancy Kathryn, Krahn, Renee F., Hendrick, Scott E.
• Granted Patent: US 8,089,872 B2
• Time in Patent Office: Days
• US Class Current: 370/437
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention is directed to load balancing call signaling channels at the times that they are established, the use of variable frequency keep alive mechanisms depending on the state of the call signaling channel, and the establishment of a call signaling channel when resources are available or otherwise based on need.

Claims

1-15. -15. (canceled)

16. A method, comprising:

(a) a first computational component determining whether a first channel has been established between the first computational component and a second computational component;

(b) when the first computational component determines that the first channel has been established, sending to a second computational component a keep alive signal at a first frequency; and

(c) when the first computational component determines that the first channel has not been established, sending to the second computational component a keep alive signal at a second frequency, wherein the first frequency is lower than the second frequency.

17. The method of claim 16, wherein the first computational component is an endpoint, wherein the second computational is at least one of a gatekeeper and server, wherein the keep alive signals are sent on a second channel between the first and second computational components different from the first channel.

18. The method of claim 17, wherein the first computational component has determined that the first channel has not been established and further comprising:

(d) determining whether the endpoint is currently being serviced by a primary server or an alternate server;

(e) when the endpoint is current being serviced by a primary server, the endpoint starts a Primary Search Timer (PST); and

(f) when the endpoint is current being serviced by an alternate server, the endpoint starts a Primary Migration Timer (PMT).

19. The method of claim 18, wherein the endpoint is current being serviced by a primary server and further comprising:

(g) sending a first registration request to a first gatekeeper on an Alternate Gatekeeper List (AGL);

(h) when no response is received within a determined time, selecting a further gatekeeper from the AGL;

(i) sending a further registration request to the further gatekeeper; and

(j) repeating steps (h) and (i) until the PST expires and/or a response is received within the determined time; and

(k) when a response is not received within the determined time and the PST expires, sending a registration request to an alternate server.

20. The method of claim 19, wherein when a response is received within a determined time and before the PST expires, further comprising:

(l) determining whether the response has been received from the second computational component and/or a third computational component;

(m) when a response has been received from the second computational component and/or the third computational component, starting a short keep alive timer;

(n) determining whether the first channel has been established;

(o) when the first channel has been established, starting a recovery procedure; and

(p) when the first channel has not been established, sending a registration request to a currently registered address associated with at least one of the second and third computational components.

21. The method of claim 18, wherein the endpoint is current being serviced by a primary server and further comprising:

(g) sending a registration request to an alternate server;

(h) determining whether a response is received within a determined time;

(i) when no response is received within a determined time, repeating steps (g) and (h) until the PMT expires or a response is received; and

(k) when a response is not received within the determined time and the PMT expires, sending a registration request to a primary server.

22. The method of claim 21, further comprising:

(l) when a response is received within a determined time, cancelling the PMT and starting a short keep alive timer;

(m) determining whether the first channel has been established;

(n) when the first channel has been established, migrating to the alternate server; and

(o) when the first channel has not been established, sending a registration request to a currently registered address associated with at least one of the second and third computational components.

23. A computer readable medium comprising processor executable instructions to perform the steps of claim 16.

25. A telecommunications endpoint comprising the first computational component of claim 16.

24. (canceled)