REQUEST ROUTING IN A NETWORKED ENVIRONMENT

• US 20160028644A1
• Filed: 09/30/2015
• Published: 01/28/2016
• 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.
• Granted Patent: US 9,794,216 B2
• Time in Patent Office: 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 one or more content providers with the service provider, the registration associated with hosting at least of portion of request routing functionality associated with one or more resources provided by the content provider;

obtaining identification of routing information to be utilized by the service provider in processing and resolving DNS queries;

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

providing the client computing device with at least one of an identifier associated with a storage component for the requested resource based on supplemental routing information not included in the resource request and an alternative resource identifier associated with the service provider and the supplemental routing information.

2. The method as recited in claim 1, wherein the one or more resources are associated with one or more embedded resources.

3. The method as recited in claim 1, wherein the one or more resources are associated with a domain associated with the content provider.

4. The method as recited in claim 1, wherein the storage component corresponds to at least one of the content provider, the service provider and a network storage provider.

5. The method as recited in claim 1, wherein the routing information comprises at least one of service level plan information and geographic selection information.

6. The method as recited in claim 1, wherein the routing information comprises cost information associated with one or more storage components.

7. 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 domains associated with the content provider with the service provider.

8. The method as recited in claim 1, wherein the supplemental routing information is not included in the first resource identifier.

9. A system for request routing comprising:

an interface component for obtaining;

registration information at a service provider for registering one or more content providers with the service provider, the registration associated with hosting at least a portion of request routing functionality associated with one or more resources provided by the content provider, and

identification of routing information to be utilized by the service provider in processing and resolving DNS queries;

a first network point of presence associated with a service provider, wherein the first network point of presence includes a DNS server component 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 is operable 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 associated with 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 component 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 is operable 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.

10. The system as recited in claim 9, wherein the original resource identifier includes at least a portion of the request routing criteria.

11. The system as recited in claim 9, wherein the DNS server in the first network point of presence is further operable to obtain at least a portion of the cost information.

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

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

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

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

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

17. The system as recited in claim 9, 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. 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 one or more content providers with the service provider, the registration associated with hosting at least of portion of request routing functionality associated with one or more resources provided by the content provider;

obtain identification of routing information to be utilized by the service provider in processing and resolving DNS queries;

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

provide the client computing device with at least one of an identifier associated with a storage component for the requested resource based on supplemental routing information not included in the resource request and an alternative resource identifier associated with the service provider and the supplemental routing information.

19. The non-transitory, computer-readable storage medium as recited in claim 18, wherein the one or more resources are associated with one or more embedded resources.

20. The non-transitory, computer-readable storage medium as recited in claim 18, wherein the one or more resources are associated with a domain associated with the content provider.