Request routing in a networked environment

• US 8,819,283 B2
• Filed: 09/28/2010
• Issued: 08/26/2014
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Cormie, John, MacCarthaigh, Colm, Redman, Benjamin W. S.
• Primary Examiner(s): Tran, Jimmy H
• Application Number:
  US12/892,877
• Publication Number:
  US 20120079115A1
• Time in Patent Office: 1,428 Days
• Field of Search: 709/226, 709/245, 709/217, 709/223, 709/238
• US Class Current: 709/245
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/3331 Query processing
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

A system, methods, and interfaces for managing request routing functionality associated with resource requests for one or more resources associated with a content provider. The request routing functionality can correspond to the processing of domain name service (“DNS”) requests for resources by computing devices and the resolution of the DNS requests by the identification of a network address of a computing device that will provide the requested resources. Unlike traditional CDN service provider implementation, the processing of resource requests by the service provider is separate from the delivery of the content by the content provider (or on behalf of the content provider).

Claims

1. A computer-implemented method for managing resource requests comprising:

obtaining a request routing inquiry from a content provider at a service provider, the request routing inquiry corresponds to an inquiry for request routing functionality by the service provider on behalf of the content provider;

causing generation, by the service provider, of a user interface for request routing functionality by the service provider on behalf of the content provider;

obtaining registration information at the service provider for registering one or more domains associated with the content provider with the service provider, the registration information including a registration request by the content provider for the service provider to provide request routing functionality on behalf of the content provider, wherein the registration request for request routing functionality is independent of a registration request for hosting or providing content on behalf of the content provider;

obtaining a DNS query from a client computing device at a first DNS server, wherein the DNS query corresponds to a requested resource associated with an original resource identifier provided by a content provider, wherein the original resource identifier corresponds to the one or more domains associated with the content provider and wherein the first DNS server corresponds to the service provider that is different from the content provider;

determining whether the first DNS server is authoritative to the DNS query as a function of additional information associated with the content provider, wherein at least a portion of the additional information is included in the DNS query;

obtaining an alternative resource identifier based on information associated with the client computing device and the content provider if the DNS server is determined not to be authoritative, wherein the alternative resource identifier includes request routing information not included in the original resource identifier and wherein the alternative resource identifier is selected at least in part on the additional information associated with the content provider;

transmitting the alternative resource identifier to the client computing device;

obtaining a subsequent DNS query from the client computing device at a subsequent DNS server, wherein the subsequent DNS query corresponds to the alternative resource identifier provided by the service provider and wherein the subsequent DNS server corresponds to the service provider that is different from the content provider;

determining whether the subsequent DNS server is authoritative to the subsequent DNS query; and

selecting a cache component for providing content associated with the original resource request if the subsequent DNS server is authoritative to the subsequent DNS query; and

transmitting information identifying the selected cache component if the subsequent DNS server is determined to be authoritative.

2. The method as recited in claim 1, wherein the original resource identifier corresponds to a uniform resource locator provided by the content provider.

3. The method as recited in claim 1, wherein the alternative resource identifier corresponds to a canonical name record identifier.

4. The method as recited in claim 1, wherein the one or more resources correspond to one or more embedded resources.

5. The method as recited in claim 1, wherein processing data corresponding to the registration of the one or more resources with the service provider comprises notifying the content provider of the registration of the one or more resources with the service provider.

6. The method as recited in claim 1 further comprising:

obtaining a second alternative resource identifier based on information associated with the client computing device and the content provider if the subsequent DNS server is determined not to be authoritative to the subsequent DNS query, wherein the second alternative resource identifier includes request routing information not included in the original resource identifier or the alternative resource identifier;

transmitting the alternative resource identifier to the client computing device;

obtaining a second subsequent DNS query from the client computing device at a third DNS server, wherein the second subsequent DNS query corresponds to the second alternative resource identifier provided by the service provider and wherein the third DNS server corresponds to the service provider that is different from the content provider;

determining whether the third DNS server is authoritative to the second subsequent DNS query; and

selecting a cache component for providing content associated with the original resource request if the third DNS server is authoritative to the second subsequent DNS query; and

transmitting information identifying the selected cache component if the third DNS server is determined to be authoritative to the second subsequent DNS query.

17. The method as recited in claim 1, wherein a second, different service provider provides the requested resource on behalf of the content provider.

19. The method as recited in claim 1, wherein the registration request is only for request routing functionality.

7. A system for request routing comprising:

a processor operative to execute instructions stored in memory to obtain registration information at a service provider for registering one or more content providers with the service provider, the registration information corresponding to hosting at least a portion of request routing functionality associated with one or more resources provided by the content provider independent of registration information to host or provide content on behalf of the content provider;

a first network point of presence associated with a service provider, wherein the first network point of presence includes a DNS server that receives a DNS query from a client computing device, wherein the DNS query corresponds to a requested resource associated with a first resource identifier, and wherein the DNS server in the first network point of presence includes a processor and is operative to execute instructions stored in memory to;

determine that the first resource identifier is associated with an alternative resource identifier as a function of request routing criteria associated with a content provider; and

transmit an alternative resource identifier to the client computing device, wherein the alternative resource identifier includes information for causing a DNS query to resolve to a domain corresponding to the service provider; and

a second network point of presence associated with a service provider, wherein the second network point of presence includes a DNS server that receives a subsequent DNS query from a client computing device, wherein the subsequent DNS query corresponds to a requested resource associated with the alternative resource identifier, and wherein the DNS server in the second network point of presence includes a processor and is operative to execute instructions stored in memory of the one or more computing devices to;

resolve the subsequent DNS query to identify a cache component for providing content associated with the original resource request; and

transmit information identifying the identified cache component to the client computing device.

8. The system as recited in claim 7, wherein the first resource identifier includes at least a portion of the request routing criteria.

9. The system as recited in claim 7, wherein the DNS server in the first network point of presence is further operative to obtain at least a portion of the request routing criteria.

10. The system as recited in claim 7, wherein the alternative resource identifier corresponds to a canonical name record identifier.

11. The system as recited in claim 7, wherein the request routing criteria includes regional service information and wherein the alternative resource identifier includes information identifying a regional service plan provided by the service provider.

12. The system as recited in claim 11, wherein the DNS server in the first network point of presence is operative to obtain information corresponding to a geographic location of the client computing device.

13. The system as recited in claim 7, wherein information identifying the identified cache component to the client computing device includes a network address of a cache component associated with the content provider.

14. The system as recited in claim 7, wherein information identifying the identified cache component to the client computing device includes a network address of a cache component associated with a third party service provider.

15. The system as recited in claim 7, wherein the request routing criteria includes cost information and wherein the alternative resource identifier includes information identifying a cost plan provided by the service provider.

16. The system as recited in claim 7, wherein the request routing criteria includes network performance information and wherein the alternative resource identifier includes information identifying a network performance plan provided by the service provider.

18. The system as recited in claim 7, wherein a second, different service provider provides the requested resource on behalf of the content provider.

20. The system as recited in claim 7, wherein the registration information includes information only for hosting at least a portion of request routing functionality associated with one or more resources provided by the content provider.