Apparatus and method for managing internet resource requests

• US 7,343,399 B2
• Filed: 06/25/2001
• Issued: 03/11/2008
• Est. Priority Date: 06/25/2001
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Hayball, Clive, Davies, Philip, Cable, Julian, Biddiscombe, Martin, Bradley, Gordon, Bragg, Nigel
• Primary Examiner(s): Donaghue, Larry D.
• Assistant Examiner(s): BILGRAMI, ASGHAR H
• Application Number:
  US09/888,730
• Publication Number:
  US 20030009591A1
• Time in Patent Office: 2,451 Days
• Field of Search: 709/245, 709/238, 709/239, 709/104, 709/105, 709/203, 709/223, 709/228, 709/219, 712/27, 718/105
• US Class Current: 709/219
• 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/101 based on network conditions
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1038 Load balancing arrangements to avoid a single path through a load balancer
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

DNS in its native form cannot identify a good or best server. Traditional Service Providers deploy a centralised approach to global traffic management based on enhancements to DNS, but do have the capability to augment this with edge-based server selection because they do not own/operate an edge network. Their resolution of DNS requests is typically restricted to identifying candidate servers within an edge domain rather than selecting the “best” server. The invention proposes a method of handling Internet resource requests whereby a local lookup server receiving a request searches for a best server able to satisfy the resource request. The local lookup server finds the best server by searching a database for a resource record associated with the best server, and then uses the resource record to retrieve an identifier of a series of executable instructions that are executed to locate the best server. The resource requests and responses may hold additional information relating to operational characteristics which may used to determine the best server. The invention proposes a DNS record type comprising a user-defined field for conveying this additional information in the resource request and in the response. The invention also proposes architecture for handling the resource request comprising a network server that provides the requested resource using the best server, as well as a communications network comprising this architecture.

Claims

1. A method of handling a resource request made by a client in a client network, the network including a Generic Local Lookup Service (GLLS) located at a network edge and a Generic Domain Lookup System (GDLS) located at a location remote from the network edge, the method comprising the steps of:

receiving a resource request at the GLLS from the said client, the resource request identifying the requested resource;

forwarding the resource request from the GLLS to the GDLS;

searching a database in the GDLS for a resource record associated with the requested resource;

the GDLS analyzing a set of resource providers and determining the resource providers compatible with the resource request;

transmitting a response containing a list of resource providers from the GDLS to the GLLS, the list including server selection criteria associated with the resource providers;

the GLLS selecting the best resource provider in the list according to the server selection criteria and additional client information relating to a client performance characteristic, the additional client information including the client access speed; and

the GLLS returning data to the client which identifies the best resource provider for the requested resource.

2. A method according to claim 1, wherein the additional client information is added to the resource request by the said client.

3. A method according to claim 1 wherein the additional client information is added to the resource request after said resource request is received at the GLLS from the client.

4. A method according to claim 1, further comprising the steps of the GLLS:

converting the resource request into a form processable by the GDLS; and

transmitting the converted resource request to the GDLS.

5. A method according to claim 1, wherein the resource request is a DNS record and the information in the resource request is contained within an additional DNS text field forming part of the DNS record.

6. A method according to claim 1, wherein the response transmitted by the GOLS is a DNS record and the server selection criteria of the compatible resource providers are contained within an additional ONS text field forming part of the DNS record.

11. A method according to claim 2, wherein the server selection criteria includes information on one of the group comprising:

a response time of said resource provider, a load on said resource provider, a distance to the resource provider from the client, and a throughput of the resource provider.

12. A method according to claim 1, wherein the requested resource is available on the resource provider but is not available on the GLLS.

14. A method according to claim 1 wherein the list of resource providers transmitted by the GDLS is in order of their compatibility with the resource request, the most compatible resource provider placed first.

15. A method according to claim 1 wherein the OLLS includes a Content Distribution Point Manager (CDPM), the CDPM adapted to provide information about local resource providers within an ISP domain.

16. A method according to claim 1 wherein the GDLS includes a Content Distribution Point Manager (CDPM), the CDPM adapted to provide information about resource providers throughout the network.

17. A method according to claim 1, wherein the additional client information includes the client location in the network.

7. A scaleable architecture for handling a resource request from a client, the resource request comprising a first identity of a resource provider, the architecture comprising:

a GLLS at a network edge for identifying a preferred resource provider for the requested resource to the client in response to receiving the resource request from the client, said preferred resource provider being defined by the resource provider that Is most compatible with the resource request with respect to Content Selection Criteria contained in the resource request; and

a GDLS at a location remote from the client network for returning data identifying a set of resource providers and including server selection criteria associated with the resource providers in response to receipt of a converted resource request from the GLLS, the GLLS being operable to select et preferred resource provider based on the server selection criteria and additional client information relating to a client performance characteristic, the additional client information including the client access speed.

8. An architecture according to claim 7, wherein the resource request from the client further comprises the additional client information relating to a client performance characteristic.

9. An architecture according to claim 8, further comprising a content distribution point manager (CDPM) associated with the GDLS, the CDPM holding information on resource providers, said CDPM configured to provide information on all known resource providers able to supply the requested resource on receiving a query from the OLLS corresponding to the resource request received by the GLLS.

13. A communications network comprising the scaleable architecture as claimed in claim 7.

10. A computer readable storage medium storing instructions that, when executed on entities within a network, cause the entities to perform a method for handling a resource request, the method comprising the steps of;

receiving a resource request at a GLLS located at a network edge from a client In the client network, the resource request identifying the requested resource;

forwarding the resource request from the OILS to a GDLS at a location remote from the network edge;

searching a database in the GDLS for a resource record associated with the requested resource the resource record including a series of executable instructions;

the GDLS analyzing a set of resource providers and determining the resource providers compatible with the resource request;

transmitting a response containing a list of resource providers from the GDLS to the GLLS, the list including server selection criteria associated with the resource providers;

the GLLS selecting the best resource provider in the list according to the server selection criteria and additional client information relating to a client performance characteristic the additional client information including the client access speed; and

the GLLS returning data to the client which identifies the best resource provider for the requested resource.