METHOD AND SYSTEM FOR DISTRIBUTING LOAD BY REDIRECTING TRAFFIC

• US 20090282149A1
• Filed: 02/10/2009
• Published: 11/12/2009
• Est. Priority Date: 06/26/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Brown, Robert, Simons, David J., Apreutesei, Elena, Kumbalimutt, Vishwajith
• Granted Patent: US 8,713,092 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54

Abstract

Disclosed is a system for servers to redirect client requests to other servers in order to distribute client traffic among the servers. A client is assigned to a server although the client may be unaware of that assignment. When the client accesses a server, a server possibly identified to the client by a name service, the server checks the client'"'"'s assignment. If the client is not assigned to this server, then in some scenarios this server redirects the client to its assigned server. The client responds by sending its request to the assigned server. In other scenarios, the first server accessed by the client proxies the client'"'"'s traffic to the assigned server. A database is kept of client-to-server assignments. If the present load distribution is less than ideal (e.g., clients are assigned to an unavailable server), then the assignment database is updated to reflect how the load should be distributed.

Claims

1-38. -38. (canceled)

39. A method performed by servers that each provide a service for clients, the method for distributing a request for service received from a client to a server for servicing the request, the servers being in a network, some of the clients being internal to the network and some of the clients being external to the network, the method comprising:

providing a client-to-server assignment data structure specifying assignments of each client to one of the servers as a home server for the client;

receiving by a receiving server a request sent from a requesting client for a service; and

under control of the receiving server,

identifying a home server of the requesting client from the client-to-server data structure;

when the receiving server is the identified home server, providing by the receiving server the service requested by the requesting client;

when the receiving server is not the identified home server,

when the requesting client is internal to the network, sending a response to the requesting client indicating to redirect the received request to the identified home server so that the identified home server provides the service requested by the requesting client; and

when the requesting client is external to the network, proxying the received request from the receiving server to the identified home server so that the identified home server provides the service requested by the requesting client.

40. The method of claim 39 wherein the network includes an edge server through which requests from external clients pass before being provided to a receiving server.

41. The method of claim 40 wherein the edge server upon receiving a request for a service from an external client selects a server to receive the request to effect load balancing of receiving requests among the servers.

42. The method of claim 41 wherein the client-to-server data structure provides load balancing among assignments of clients to home servers.

43. The method of claim 40 wherein the request sent from a client includes a Via header, the edge server adds another Via header to a request sent from an external client, and the receiving server determines whether the requesting client is internal or external to the network based on number of Via headers of the received request.

44. The method of claim 39 wherein the network includes a firewall separating the servers and internal clients from the external clients.

45. A computer-readable storage medium containing instructions for controlling a server that provides a service for clients to distribute a request for service received from a client to another server that also provides the service for clients, the servers being in a network, some of the clients being internal to the network and some of the clients being external to the network, by a method comprising:

receiving by a receiving server a request sent from a requesting client for a service; and

under control of the receiving server,

identifying the home server of the requesting client;

when the receiving server is the identified home server, providing the service requested by the requesting client;

when the receiving server is not the identified home server,

when the requesting client is internal to the network, sending a response to the requesting client indicating to redirect the received request to the identified home server so that the identified home server provides the service requested by the requesting client; and

when the requesting client is external to the network, proxying the received request from the receiving server to the identified home server so that the identified home server provides the service requested by the requesting client.

46. The computer-readable storage medium of claim 45 wherein the network includes an edge server through which requests from external clients pass before being provided to a receiving server.

47. The computer-readable storage medium of claim 46 wherein the edge server upon receiving a request for a service from an external client selects a server to receive the request to effect load balancing of receiving requests among the servers.

48. The computer-readable storage medium of claim 47 wherein a client-to-server data structure specifies assignments of each client to one of the servers as a home server for the client to provide load balancing among assignments of clients to home servers.

49. The computer-readable storage medium of claim 46 wherein the request sent from a client includes a Via header, the edge server adds another Via header to a request sent from an external client, and the receiving server determines whether the requesting client is internal or external to the network based on number of Via headers of the received request.

50. The computer-readable storage medium of claim 45 wherein the network includes a firewall separating the servers and internal clients from the external clients.

51. A server that receives from a requesting client a request to provide a service and the receiving server either provides the service to the client or distributes the received request to another server that also provides the service for clients, the servers being in a network, some of the clients being internal to the network and some of the clients being external to the network, comprising:

a component that identifies a home server of the requesting client;

a component that, when the receiving server is the identified home server, provides the service requested by the requesting client;

a component that, when the receiving server is not the identified home server,

determines whether the requesting client is internal or external to the network;

when it is determined that the requesting client is internal to the network, sends a response to the requesting client indicating to redirect the received request to the identified home server; and

when it is determined that the requesting client is external to the network, proxies the received request from the receiving server to the identified home server.

52. The server of claim 51 wherein the network includes an edge server through which requests from external clients pass before being provided to a receiving server.

53. The server of claim 52 wherein the edge server selects a server to receive the each request it receives from an external client to effect load balancing of receiving requests among the servers.

54. The server of claim 53 wherein an internal client selects a server to receive the request to effect load balancing of receiving requests among the servers.

55. The server of claim 51 wherein a client-to-server data structure specifies assignments of each client to one of the servers as a home server for the client to provide load balancing among assignments of clients to home servers.

56. The server of claim 52 wherein the request sent from a client includes a Via header, the edge server adds another Via header to a request sent from an external client, and the receiving server determines whether the requesting client is internal or external to the network based on number of Via headers of the received request.

57. The server of claim 51 wherein the network includes a firewall separating the servers and internal clients from the external clients.