Request routing in a networked environment

• US 9,191,338 B2
• Filed: 08/25/2014
• Issued: 11/17/2015
• 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:
  US14/467,774
• Publication Number:
  US 20140365666A1
• Time in Patent Office: 449 Days
• US Class Current: 1/1
• 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 request routing functionality comprising:

obtaining registration information at a service provider for registering a content provider with the service provider, the registration information including a registration request by the content provider for the service provider to provide at least a portion of request routing functionality associated with one or more resources provided by the content provider, wherein the registration request for request routing functionality is different from 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 a first resource identifier and wherein the first DNS server corresponds to the service provider; and

providing the client computing device with at least one of an identifier corresponding to a storage component for the requested resource based on supplemental request routing information not included in the first resource identifier or an alternative resource identifier query to resolve to a domain corresponding to the service provider, wherein the alternative resource identifier includes the supplemental request routing information not included in the first resource identifier.

2. The method as recited in claim 1, wherein the registration information includes the supplemental request routing information.

3. The method as recited in claim 1 further comprising causing generation, by the service provider, of a user interface for registering the one or more resources associated with the content provider with the service provider.

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

5. The method as recited in claim 1, 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.

6. 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 a content provider with the service provider, the registration information including a registration request by the content provider for the service provider to provide at least a portion of request routing functionality associated with one or more resources provided by the content provider, wherein the registration request for request routing functionality is different from a registration request for hosting or providing 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;

provide the client computing device with at least one of an identifier corresponding to a storage component for the requested resource based on supplemental request routing information not included in the first resource identifier or an alternative resource identifier query to resolve to a domain corresponding to the service provider, wherein the alternative resource identifier includes the supplemental request routing information not included in the first resource identifier.

7. The system as recited in claim 6, wherein the one or more resources correspond to one or more embedded resources.

8. The system as recited in claim 6, wherein the one or more resources correspond to a domain associated with the content provider.

9. The system as recited in claim 6, wherein the storage component corresponds to at least one of the content provider, the service provider or a network storage provider.

10. The system as recited in claim 6, wherein the supplemental request routing information comprises service level plan information.

11. The system as recited in claim 6, wherein the supplemental request routing information comprises geographic selection information.

12. The system as recited in claim 6, wherein the supplemental request routing information comprises cost information associated with one or more storage components.

13. The system as recited in claim 6, wherein the DNS server in the first network point of presence is further operative to execute instructions stored in memory to cause generation, by the service provider, of a user interface for registering the one or more resources associated with the content provider with the service provider.

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

15. The system as recited in claim 6, 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.

16. A non-transitory, computer-readable storage medium having computer-executable modules for managing resources, the computer-executable modules comprising:

one or more modules configured to;

obtain registration information at a service provider for registering a content provider with the service provider, the registration information including a registration request by the content provider for the service provider to provide at least a portion of request routing functionality associated with one or more resources provided by the content provider, wherein the registration request for request routing functionality is different from a registration request for hosting or providing content on behalf of the content provider;

obtain a DNS query from a client computing device at a first DNS server, wherein the DNS query corresponds to a requested resource associated with a first resource identifier and wherein the first DNS server corresponds to the service provider; and

provide the client computing device with at least one of an identifier corresponding to a storage component for the requested resource based on supplemental request routing information not included in the first resource identifier or an alternative resource identifier query to resolve to a domain corresponding to the service provider, wherein the alternative resource identifier includes the supplemental request routing information not included in the first resource identifier.

17. The non-transitory, computer-readable storage medium of claim 16, wherein the registration information includes the supplemental request routing information.

18. The non-transitory, computer-readable storage medium of claim 16, wherein one or more modules are further configured to cause generation, by the service provider, of a user interface for registering the one or more resources associated with the content provider with the service provider.

19. The non-transitory, computer-readable storage medium of claim 16, wherein a second, different service provider provides the requested resource on behalf of the content provider.

20. The non-transitory, computer-readable storage medium of claim 16, 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.