LOAD BALANCING AMONG VOIP SERVER GROUPS

• US 20110271005A1
• Filed: 04/30/2010
• Published: 11/03/2011
• Est. Priority Date: 04/30/2010
• Status: Abandoned Application

• Current Assignee: Sonus Networks Incorporated (Ribbon Communications, Inc.)
• Original Assignee: Sonus Networks Incorporated (Ribbon Communications, Inc.)
• Inventors: Hart, Justin, Asveren, Tolga, Bharrat, Shaun Jaikarran
• Application Number:
  US12/771,618
• Publication Number:
  US 20110271005A1
• Time in Patent Office: Days
• US Class Current: 709/232
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing

Abstract

Described are computer-based methods and apparatuses, including computer program products, for load balancing among VOIP servers. An identity table includes an identity entry for a plurality of servers, each identity entry comprising a FQDN and load balancing information. A persistence table stores persistence entries indicative of a persistent connection between a client and a server. Updated load balancing information determined by the first server is received. The identity table is updated based on the updated load balancing information. A service request is received from a client. If the client is not associated with a persistence entry, a second server is selected from the plurality of servers based on load balancing information for each identity entry in the identity table. A persistence entry is stored indicative of a persistent connection between the client and the selected second server, the persistence entry comprising a FQDN and an identifier for the client.

Claims

1. A computerized method for load balancing among servers in a network, the method comprising:

storing, by a Domain Name Server (DNS) server, an identity table in a database, wherein the identity table comprises an identity entry for each of a plurality of servers in communication with the DNS server, each identity entry comprising a fully qualified domain name (FQDN) and load balancing information for the associated server;

storing, by the DNS server, a persistence table in the database for storing one or more persistence entries, each persistence entry indicative of a persistent connection between a server, from the plurality of servers, and a client;

receiving, by the DNS server, updated load balancing information from a first server of the plurality of servers, wherein the updated load balancing information is determined by the first server;

updating, by the DNS server, the identity table based on the updated load balancing information, wherein the load balancing information for the identity entry associated with the first server is updated to include the updated load balancing information;

receiving, by the DNS server, a service request from a client;

determining, by the DNS server, whether the client is associated with a persistence entry in the persistence table; and

if the client is not associated with a persistence entry;

selecting, by the DNS server, a second server from the plurality of servers based on load balancing information for each identity entry in the identity table;

storing, by the DNS server, a persistence entry indicative of a persistent connection between the client and the selected second server, the persistence entry comprising a FQDN from the identity entry associated with the selected second server and an identifier for the client; and

transmitting, by the DNS server, the FQDN to the client.

2. The method of claim 1, further comprising, if the client is associated with a persistence entry, transmitting the FQDN from the persistence entry associated with the client to the client to continue the persistent connection between the client and a third server associated with the persistence entry.

3. The method of claim 1, wherein receiving updated load balancing information comprises:

transmitting a DNS Service (SRV) request to the first server, the request comprising a SRV target Uniform Resource Locator (URL) supported by the first server; and

receiving the updated load balancing information from the first server in response to the DNS SRV request.

4. The method of claim 3, wherein the updated load balancing information includes a time-to-live value for an identity entry associated with the first server, wherein the time-to-live value is based on a desired sampling period.

5. The method of claim 1, wherein the updated load balancing information comprises a class from a plurality of classes for the plurality of servers, wherein the class is determined by the first server based on a current congestion state of the first server.

6. The method of claim 5, wherein the plurality of classes comprises a first class indicative of one or more servers that can receive a normal rate of additional load, a second class indicative of one or more servers that can receive a reduced rate of additional load, a third class indicative of one or more servers that cannot receive any additional load, or any combination thereof.

7. The method of claim 6, wherein the updated load balancing information comprises a priority value determined by the first server based on the class, wherein each server associated with the class is associated with the priority value.

8. The method of claim 6, wherein the updated load balancing information comprises a weight value determined by the first server based on the class.

9. The method of claim 1, wherein the updated load balancing information comprises a class from a plurality of classes for the plurality of servers, wherein the class is determined by the first server based on a current resource availability of the first server.

10. The method of claim 1, further comprising:

determining a third server is unavailable;

identifying one or more persistence entries in the persistence table associated with the unavailable third server;

deleting each of the one or more persistence entries, associated with the unavailable third server, from the persistence table.

11. The method of claim 1, further comprising:

identifying an identity entry in the identity table associated with a third server, wherein a time-to-live value of the identity entry has expired;

removing the identity entry associated with the third server from the identity table;

determining whether there are one or more persistence entries in the persistence table associated with the third server; and

for each of the one or more determined persistence entries, deleting the persistence entry from the persistence table.

12. The method of claim 1, wherein storing the persistence entry comprises associating an expiration time with the persistence entry, the method further comprising:

determining the persistence entry expired based on the associated expiration time; and

deleting the persistence entry from the persistence table.

13. The method of claim 1, wherein, if the client is associated with a persistence entry:

transmitting the FQDN from the persistence entry associated with the client to the client; and

updating an expiration time associated with the persistence entry.

14. The method of claim 1, wherein:

each server in the plurality of servers comprises a group of servers, each server in the group of servers comprising a unique internet protocol (IP) address,

the method further comprising storing, in the identity table, a mapping for each SRV record to a FQDN, wherein the FQDN represents all servers in the group of servers.

15. The method of claim 1, wherein the stored persistence entry does not include an IP address of the selected second server.

16. An apparatus for load balancing among servers in a network, the apparatus comprising:

a database;

a DNS server in communication with the database, the DNS server being configured to;

store an identity table in a database, wherein the identity table comprises an identity entry for each of a plurality of servers in communication with the DNS server, each identity entry comprising a fully qualified domain name (FQDN) and load balancing information for the associated server;

store a persistence table in the database for storing one or more persistence entries, each persistence entry indicative of a persistent connection between a server, from the plurality of servers, and a client;

receive updated load balancing information from a first server of the plurality of servers, wherein the updated load balancing information is determined by the first server;

update the identity table based on the updated load balancing information, wherein the load balancing information for the identity entry associated with the first server is updated to include the updated load balancing information;

receive a service request from a client;

determine whether the client is associated with a persistence entry in the persistence table; and

if the client is not associated with a persistence entry;

select a second server from the plurality of servers based on load balancing information for each identity entry in the identity table;

store a persistence entry indicative of a persistent connection between the client and the selected second server, the persistence entry comprising a FQDN from the identity entry associated with the selected second server and an identifier for the client; and

transmit the FQDN to the client.

17. A computer program product, tangibly embodied in a machine-readable storage device, the computer program product including instructions being operable to cause a data processing apparatus to:

store an identity table in a database, wherein the identity table comprises an identity entry for each of a plurality of servers in communication with the DNS server, each identity entry comprising a fully qualified domain name (FQDN) and load balancing information for the associated server;

store a persistence table in the database for storing one or more persistence entries, each persistence entry indicative of a persistent connection between a server, from the plurality of servers, and a client;

receive updated load balancing information from a first server of the plurality of servers, wherein the updated load balancing information is determined by the first server;

update the identity table based on the updated load balancing information, wherein the load balancing information for the identity entry associated with the first server is updated to include the updated load balancing information;

receive a service request from a client;

determine whether the client is associated with a persistence entry in the persistence table; and

if the client is not associated with a persistence entry;

select a second server from the plurality of servers based on load balancing information for each identity entry in the identity table;

store a persistence entry indicative of a persistent connection between the client and the selected second server, the persistence entry comprising a FQDN from the identity entry associated with the selected second server and an identifier for the client; and

transmit the FQDN to the client.