Distributing load of requests from clients over multiple servers

• US 20070180113A1
• Filed: 01/31/2006
• Published: 08/02/2007
• Est. Priority Date: 01/31/2006
• Status: Abandoned Application

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Van Bemmel, Jeroen
• Application Number:
  US11/344,523
• Publication Number:
  US 20070180113A1
• Time in Patent Office: Days
• US Class Current: 709/226
• 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

Abstract

The present invention provides a method and an apparatus for balancing load of a plurality of requests from at least one of first and second clients between a first and a second server. The method comprises comparing the load of the plurality of requests to a threshold of processing requests at the first server to determine whether the first server can process the plurality of requests. The method further comprises selectively redirecting a set of requests from the plurality of requests to the second server based on a policy associated with the first server, if the first server can not process the plurality of requests based on the threshold.

Claims

1. A method of balancing load of a plurality of requests from at least one of first and second clients between a first and a second server, the method comprising:

comparing said load of said plurality of requests to a threshold of processing requests at said first server to determine whether said first server can process said plurality of requests; and

if said first server can not process said plurality of requests based on said threshold, selectively redirecting a set of requests from said plurality of requests to said second server based on a policy associated with said first server.

2. A method, as set forth in claim 1, wherein comparing said load of said plurality of requests to said threshold of processing requests further comprises:

receiving a first load of processing said plurality of requests from said at least one of first and second clients at said first server; and

determining whether said first load of processing said plurality of requests is higher than said threshold of processing requests.

3. A method, as set forth in claim 2, further comprising:

sharing a first indication of said first load of processing said plurality of requests with said second server; and

receiving a second indication of a second load of processing said plurality of requests from said second server.

4. A method, as set forth in claim 3, further comprising:

determining whether said second load of processing said plurality of requests is smaller than said first load of processing said plurality of requests based on said first and second indications; and

if said second load of processing said plurality of requests is smaller and said first load of processing said plurality of requests is higher than said threshold of processing requests, temporarily redirecting at least two of said plurality of requests to said second server.

5. A method, as set forth in claim 1, further comprising:

distributing a first set of requests from said load of said plurality of requests based on a database of subscriber information in a data communications network.

6. A method, as set forth in claim 1, further comprising:

determining whether an overload condition is reached at said first server based on said threshold of processing requests; and

in response to said overload condition, redirecting one or more requests of said plurality of requests to said second server.

7. A method, as set forth in claim 6, wherein redirecting one or more requests of said plurality of requests further comprises:

using a single redirect action from said first server to redirect more than one request of said plurality of requests.

8. A method, as set forth in claim 6, wherein redirecting one or more requests of said plurality of requests further comprises:

receiving said one or more requests at said first server; and

determining whether said one or more requests received in a desired timeframe are related based on a common criterion of at least one of sent by a particular user, a particular application and belongs to a particular application session.

9. A method, as set forth in claim 6, wherein redirecting one or more requests of said plurality of requests further comprises:

dimensioning a telephony system to enable processing of said load of said plurality of requests over said first and second servers.

10. A method, as set forth in claim 1, further comprising:

providing a transport protocol to enable temporary redirection of a first set of requests of said plurality of requests that match a given criterion of at least one of all requests being associated with a first user or all users request for operating in a single session.

11. A method, as set forth in claim 1, further comprising:

in response to said load of said plurality of requests at said first server exceeding said threshold of processing requests, sending a redirect with an address of said second server being a less-loaded server node.

12. A method, as set forth in claim 11, wherein sending a redirect further comprises:

sending an indication of a time period for which said first server to redirect said load of said plurality of requests to said second server for a user.

13. A method, as set forth in claim 1, further comprising:

using a first and a second communication port at each server of said first and second servers to redirect said load of said plurality of requests.

14. A method, as set forth in claim 13, wherein using a first and a second communication port at each server further comprises:

causing said first and second clients to use said first communication port as a public port for redirecting one or more requests of said plurality of requests from said first server.

15. A method, as set forth in claim 13, wherein using a first and a second communication port at each server further comprises:

causing said first and second clients to use said second communication port as a private port for said second server to receive one or more redirected requests of said plurality of requests from said first server.

16. A method, as set forth in claim 15, wherein causing said first and second clients to use said second communication port as a private port further comprises:

processing said one or more redirected requests received at said second communication port of said second server without redirecting to a third server.

17. A method, as set forth in claim 16, wherein processing said one or more redirected requests further comprises:

processing said one or more redirected requests received at said second communication port of said second server with a higher priority than said one or more requests of said plurality of requests received at said first communication port of said second server.

18. A method, as set forth in claim 1, wherein selectively redirecting said plurality of requests to said second server further comprises:

determining whether it is likely that more of the same kind of a particular type of request of said plurality of requests will arrive at said first server; and

if so, selectively redirecting said particular type of request to said second server.

19. A method, as set forth in claim 1, wherein determining whether it is likely that more of the same kind of a particular type of request further comprises:

determining whether said particular type of request is associated with at least one of a session in which a number of requests were recently received or said particular type of request is a first request in a set of requests associated with an application that issues a series of multiple requests.

20. A method, as set forth in claim 19, further comprising:

sending a redirect indication to at least one of said first and second clients;

causing said at least one of said first and second clients to cache said redirect indication for a predetermined period of time for routing said plurality of requests.