System for balancing loads among network servers

• US 20030069968A1
• Filed: 06/04/2002
• Published: 04/10/2003
• Est. Priority Date: 10/01/1998
• Status: Abandoned Application

• Current Assignee: Hanger Solutions, LLC (IP Investments Group LLC)
• Original Assignee: Hanger Solutions, LLC (IP Investments Group LLC)
• Inventors: Nerz, Robert F., OʼNeil, Kevin M., Aubin, Robert R.
• Application Number:
  US10/162,419
• Publication Number:
  US 20030069968A1
• Time in Patent Office: Days
• US Class Current: 709/225
• 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/1014 based on the content of a request
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism

Abstract

A system which distributes requests among a plurality of network servers receives a request from a remote source at a first one of the network servers, and determines whether to process the request in the first network server. The request is processed in the first network server in a case that it is determined that the request should be processed in the first network server. On the other hand, the request is routed to another network server in a case that it is determined that the request should not be processed in the first network server.

Claims

1. A method of distributing requests among a plurality of network servers, the method comprising the steps of:

receiving a request from a remote source at a first one of the network servers;

executing a determining step in the first server, the determining step for determining whether to process the request in the first network server;

processing the request in the first network server in a case that the determining step determines that the request should be processed in the first network server; and

routing the request to another network server in a case that the determining step determines that the request should not be processed in the first network server.

2. A method according to claim 1, wherein the determining step makes a determination as to whether the request should be processed in the first network server based on a load currently being processed in the first network server.

3. A method according to claim 2, wherein the determining step makes the determination based, in addition, on a load currently being processed in one or more of the other network servers.

4. A method according to claim 1, wherein the determining step comprises the steps of:

determining a load currently being processed by the first network server; and

receiving information in the first network server from each of the other network servers, the information from each of the other network servers comprising information concerning a load currently being processed in each network server;

wherein the determining step determines that the first network server should process the request in a case that (i) the load currently being processed in the first network server is below a first predetermined level, or (ii) the load currently being processed in the first network server is above the first predetermined level and is above loads currently being processed by either of the other network servers by less than a second predetermined level; and

wherein the determining step determines that the first network server should not process the request in a case that the load currently being processed in the first network server is above the first predetermined level and a load currently being processed in at least one of the other network servers is below the level of the first network server by at least the second predetermined level.

5. A method according to claim 1, wherein, in a case that the determining step determines that the request should not be processed in the first network server and the plurality of network servers includes at least two other network servers, the method further comprises a second determining step for determining which of the at least two other network servers that the request should be routed to in the routing step.

6. A method according to claim 5, wherein the second determining step determines which of the at least two other network servers that the request should be routed to based on loads currently being processed in the at least two other network servers.

7. A method according to claim 6, wherein the second determining step determines that the request should be routed to a network server which is currently processing a smallest load.

8. A method according to claim 1, wherein the plurality of network servers comprises one or more of the following types of servers:

World Wide Web servers, CORBA servers, ORB servers, FTP servers, and SMTP servers.

9. A method according to claim 1, wherein the routing step comprises sending a command to the remote source which instructs the remote source to send the request to the other one of the network servers.

10. A method according to claim 1, wherein the determining step determines whether to process the request in the first network server based on a content of the request.

11. A method according to claim 10, wherein the request comprises a uniform resource locator (“

URL”

) and a uniform resource indicator (“

URI”

); and

wherein the determining step determines whether to process the request in the first network server based on the URI in the request.

12. A method according to claim 11, wherein the determining step determines whether to process the request in the first network server based, in addition, on a load currently being processed in the first network server and loads currently being processed in one or more of the other network servers.

13. A method according to claim 1, further comprising, before the routing step, the step of determining which, if any, of the plurality of network servers are off-line;

wherein the routing step routes the request to a network server which is on-line and does not route the request to a network server which is off-line.

40. A method according to claim 1, wherein the determining step comprises determining whether the request is related to a stateful transaction based on a URI in the request,and

wherein (i) in a case that the request is related to a stateful transaction, determining that the request should be processed in the first network server, and (ii) in a case that the request is not related to a stateful transaction, determining if the request should be processed in the first network server.

41. A method according to claim 40, wherein, in a case that the request is related to a stateful transaction, determining that at least a second request having a URI substantially the same as the URI of the request should be processed in the first network server.

14. Computer-executable process steps stored on a computer-readable medium, the computer executable process steps comprising a server module which is installable in a plurality of network servers to distribute requests among the plurality of network servers, the computer-executable process steps comprising:

code to receive a request from a remote source at a first one of the network servers;

code, executable by the first server, to determine whether to process the request in that server;

code to process the request in the first network server in a case that the determining code determines that the request should be processed in the first network server; and

code to route the request to another network server in a case that the determining code determines that the request should not be processed in the first network server.

15. Computer-executable process steps according to claim 14, wherein the determining code comprises code to make a determination as to whether the request should be processed in the first network server based on a load currently being processed in the first network server.

16. Computer-executable process steps according to claim 15, wherein the determining code comprises code to make the determination based, in addition, on a load currently being processed in one or more of the other network servers.

17. Computer-executable process steps according to claim 14, wherein the determining code comprises:

code to determine a load currently being processed by the first network server; and

code to receive information in the first network server from each of the other network servers, the information from each of the other network servers comprising information concerning a load currently being processed in each network server,

wherein the determining code determines that the first network server should process the request in a case that (i) the load currently being processed in the first network server is below a first predetermined level, or (ii) the load currently being processed in the first network server is above the first predetermined level and is above loads currently being processed by either of the other network servers by less than a second predetermined level; and

wherein the determining code determines that the first network server should not process the request in a case that the load currently being processed in the first network server is above the first predetermined level and a load currently being processed in at least one of the other network servers is below the level of the first network server by at least the second predetermined level.

18. Computer-executable process steps according to claim 14, wherein the computer-executable process steps further comprise code to determine which of the other network servers that the request should be routed to by the routing code in a case that the determining code determines that the request should not be processed in the first network server.

19. Computer-executable process steps according to claim 18, wherein the code to determine which of the at least two other network servers that the request should be routed to makes a determination based on loads currently being processed in the at least two other network servers.

20. Computer-executable process steps according to claim 19, wherein the code to determine which of the at least two other network servers that the request should be routed to determines that the request should be routed to a network server which is currently processing a smallest load.

21. Computer-executable process steps according to claim 14, wherein the plurality of network servers comprises one or more of the following types of servers:

World Wide Web servers, CORBA servers, ORB servers, FTP servers, and SMTP servers.

22. Computer-executable process steps according to claim 14, wherein the routing code comprises code to send a command to the remote source which instructs the remote source to send the request to the other one of the network servers.

23. Computer-executable process steps according to claim 14, wherein the determining code determines whether to process the request in the first network server based on a content of the request.

24. Computer-executable process steps according to claim 23, wherein the request comprises a uniform resource locator (“

URL”

) and a uniform resource indicator (“

URI”

); and

wherein the determining code determines whether to process the request in the first network server based on the URI in the request.

25. Computer-executable process steps according to claim 24, wherein the determining code determines whether to process the request in the first network server based, in addition, on a load currently being processed in the first network server and loads currently being processed in one or more of the other network servers.

26. Computer-executable process steps according to claim 14, further comprising code to determine which, if any, of the plurality of network servers are off-line;

wherein the routing code routes the request to a network server which is on-line and does not route the request to a network server which is off-line.

42. Computer-executable process steps according to claim 14, wherein the determining code comprises code to determine whether the request is related to a stateful transaction based on a URI in the request;

and

wherein (i) in a case that the request is related to a stateful transaction, the determining code determines that the request should be processed in the first network server, and (ii) in a case that the request is not related to a stateful transaction, the determining code determines if the request should be processed in the first network server.

43. Computer-executable process steps according to claim 42, wherein, in a case that the request is related to a stateful transaction, the code to determine determines that at least a second request having a URI substantially the same as the URI of the request should be processed in the first network server.

27. A network server which is capable of processing requests and of distributing the requests among a plurality of other network servers, the network server comprising:

a memory which stores a module comprised of computer-executable process steps; and

a processor which executes the process steps stored in the memory so as (i) to receive a request from a remote source at the network server, (ii) to determine whether to process the request in the network server, (iii) to process the request in the network server in a case that the processor determines that the request should be processed in the network server, and (iv) to route the request to another one of the plurality of network servers in a case that the processor determines that the request should not be processed in the network server.

28. A network server according to claim 27, wherein the processor makes a determination as to whether the request should be processed in the network server based on a load currently being processed in the network server.

29. A network server according to claim 27, wherein the processor makes the determination based, in addition, on a load currently being processed in one or more of the other network servers.

30. A network server according to claim 27, wherein the processor determines whether to process the request in the network server by executing process steps so as (i) to determine a load currently being processed by the first network server, and (ii) to receive information in the first network server from each of the other network servers, the information from each of the other network servers comprising information concerning a load currently being processed in each network server;

wherein the processor determines that the first network server should process the request in a case that (i) the load currently being processed in the fist network server is below a first predetermined level, or (ii) the load currently being processed in the first network server is above the first predetermined level and is above loads currently being processed by either of the other network servers by less than a second predetermined level; and

wherein the processor determines that the first network server should not process the request in a case that the load currently being processed in the first network server is above the first predetermined level and a load currently being processed in at least one of the other network servers is below the level of the first network server by at least the second predetermined level.

31. A network server according to claim 27, wherein, in a case that the processor determines that the request should not be processed in the network server and the plurality of other network servers includes at least two other network servers, the processor executes process steps to determine to which of the at least two other network servers that the request should be routed.

32. A network server according to claim 31, wherein the processor determines which of the at least two other network servers that the request should be routed to based on loads currently being processed in the at least two other network servers.

33. A network server according to claim 32, wherein the processor determines that the request should be routed to a network server which is currently processing a smallest load.

34. A network server according to claim 27, wherein the plurality of other network servers comprises one or more of the following types of servers:

World Wide Web servers, CORBA servers, ORB servers, FTP servers, and SMTP servers.

35. A network server according to claim 27, wherein the processor routes the request to another one of the plurality of network servers by executing process steps to send a command to the remote source which instructs the remote source to send the request to the other one of the network servers.

36. A network server according to claim 27, wherein the processor determines whether to process the request in the network server based on a content of the request.

37. A network server according to claim 36, wherein the request comprises a uniform resource locator (“

URL”

) and a uniform resource indicator (“

URI”

); and

wherein the processor determines whether to process the request in the network server based on the URI in the request.

38. A network server according to claim 37, wherein the processor determines whether to process the request in the network server based, in addition, on a load currently being processed in the network server and a load currently being processed in one or more of the other network servers.

39. A network server according to claim 27, wherein the processor executes process steps to determine which, if any, of the plurality of network servers are off-line;

wherein the processor routes the request to a network server which is on-line and does not route the request to a network server which is off-line.

44. A network server according to claim 27, wherein the processor determines whether the request should be processed in the network server by determining whether the request is related to a stateful transaction based on a URI in the request;

and

wherein (i) in a case that the request is related to a stateful transaction, the processor determines that the request should be processed in the network server, and (ii) in a case that the request is not related to a stateful transaction, the processor determines if the request should be processed in the network server.

45. A network server according to claim 44, wherein, in a case that the request is related to a stateful transaction, the processor determines that at least a second request having a URI substantially the same as the URI of the request should be processed in the network server.