Method and apparatus for client-side proxy selection

• US 20020069241A1
• Filed: 12/06/2000
• Published: 06/06/2002
• Est. Priority Date: 12/06/2000
• Status: Abandoned Application

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Yagati, Lakshman N., Narlikar, Girija
• Application Number:
  US09/731,348
• Publication Number:
  US 20020069241A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 61/59 using proxies for addressing
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• 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 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus are disclosed for selecting a proxy server that stores a web resource from an array of proxies in a network. A disclosed proxy selector reduces the latency and bandwidth utilization required to obtain Web resources. A given proxy server is selected based on a proxy selection table generally maintained by each client. The proxy selection table redirects requests to a given proxy server in an array of proxy servers, based on the address of the requested resource and the recent history of client request patterns. The proxy selection table can encode the assignment of heavy file types and heavy domains to individual proxy servers. When a client requests a web resource, the proxy selection table is accessed to redirect the request to the appropriate proxy server. If the resource type is a heavy type, the request is redirected to one or more proxy servers responsible for heavy file types. If the resource is provided by a heavy domain, the request is redirected to the proxy server responsible for that domain. If the resource type is not a heavy type or provided by a heavy domain, a hash function is applied to only the domain part of the URL to identify a proxy server from which to obtain the desired resource.

Claims

1. A method of selecting a proxy server storing a web resource from among a plurality of proxy servers, said method comprising the steps of:

receiving a request for said web resource;

determining if said web resource is a predefined file type; and

redirecting said web request to a proxy server associated with said file type.

2. The method according to claim 1, wherein said predefined file type has an average size that exceeds a predefined threshold.

3. The method according to claim 1, wherein said redirecting step further comprises the step of accessing a proxy selection table that associates said file type to a proxy server.

4. The method according to claim 1, wherein said redirecting step further comprises the step of redirecting said request to a given proxy server based on the recent history of client request patterns.

5. The method according to claim 1, further comprising the step of analyzing the recent history of client request patterns.

6. The method according to claim 1, further comprising the step of assigning P×

1/h of the available proxy servers to serve heavy file types, where P is the total number of proxy servers and the heavy file types account for a fraction 1/h of the total load.

7. A method of selecting a proxy server storing a web resource from among a plurality of proxy servers, said method comprising the steps of:

receiving a request for said web resource;

determining if said web resource is a served by a domain having a traffic volume that exceeds a predefined threshold; and

redirecting said web request to a proxy server associated with said domain.

8. The method according to claim 7, wherein said predefined threshold is based on a maximum normalized daily load.

9. The method according to claim 7, wherein said redirecting step further comprises the step of accessing a proxy selection table that associates said domain to a proxy server.

10. The method according to claim 7, wherein said redirecting step further comprises the step of redirecting said request to a given proxy server based on the recent history of client request patterns.

11. The method according to claim 7, further comprising the step of analyzing the recent history of client request patterns.

12. The method according to claim 7, further comprising the steps of sorting heavy domains in increasing order of their average file sizes, splitting said sorted list into P×

(1-h) partitions of equal load, and assigning one partition to each of the remaining proxy servers, where P is the total number of proxy servers and the heavy file types account for a fraction 1/h of the total load.

14. The system according to claim 13, wherein said predefined file type has an average size that exceeds a predefined threshold.

15. The system according to claim 13, wherein said memory further includes a proxy selection table that associates said file type to a proxy server.

16. The system according to claim 13, wherein said processor is further configured to redirect said request to a given proxy server based on the recent history of client request patterns.

18. The system according to claim 17, wherein said predefined threshold is based on a maximum normalized daily load.

19. The system according to claim 17, wherein said memory further includes a proxy selection table that associates said domain to a proxy server.

20. The system according to claim 17, wherein said processor is further configured to redirect said request to a given proxy server based on the recent history of client request patterns.

13. A system for selecting a proxy server storing a web resource from among a plurality of proxy servers, said system comprising:

a memory for storing computer readable code; and

a processor operatively coupled to said memory, said processor configured to;

receive a request for said web resource;

determine if said web resource is a predefined file type; and

redirect said web request to a proxy server associated with said file type.

17. A system for selecting a proxy server storing a web resource from among a plurality of proxy servers, said system comprising:

a memory for storing computer readable code; and

a processor operatively coupled to said memory, said processor configured to;

receive a request for said web resource;

determine if said web resource is a served by a domain having a traffic volume that exceeds a predefined threshold; and

redirect said web request to a proxy server associated with said domain.

21. An article of manufacture for selecting a proxy server storing a web resource from among a plurality of proxy servers, comprising:

a computer readable medium having computer readable code means embodied thereon, said computer readable program code means comprising;

a step to receive a request for said web resource;

a step to determine if said web resource is a predefined file type; and

a step to redirect said web request to a proxy server associated with said file type.

22. An article of manufacture for selecting a proxy server storing a web resource from among a plurality of proxy servers, comprising:

a computer readable medium having computer readable code means embodied thereon, said computer readable program code means comprising;

a step to receive a request for said web resource;

a step to determine if said web resource is a served by a domain having a traffic volume that exceeds a predefined threshold; and

a step to redirect said web request to a proxy server associated with said domain.