Managing request routing information utilizing performance information

• US 9,083,743 B1
• Filed: 06/20/2012
• Issued: 07/14/2015
• Est. Priority Date: 03/21/2012
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Patel, Imran S., MacCarthaigh, Colm, Liborski, Valeri, Acharya, Prashanth
• Primary Examiner(s): YI, DAVID
• Application Number:
  US13/528,674
• Time in Patent Office: 1,119 Days
• Field of Search: 709/203
• US Class Current: 1/1
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

Systems and methods for managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider are provided. 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. Based on the processing resource requests initiated by a client computing device, a CDN service provider can obtain performance information from client computing devices and correlate the performance information into a prioritized list for classes of client computing devices. The prioritized list can be utilized in resolving subsequent DNS queries.

Claims

1. A method for processing content comprising:

providing, by a service provider, at least one identifier for identifying an embedded resource provided by a content provider;

obtaining, by the service provider, a plurality of requests for content from one or more client computing devices responsive to the at least one identifier for the embedded resource provided by the content provider;

obtaining, by the service provider, performance information associated with the plurality of requests for content;

correlating, by the service provider, the performance information to generate prioritized lists for processing subsequent resource requests for classes of client computing devices, wherein the prioritized lists identify point of presence servers associated with classes of computing devices;

obtaining, by the service provider, a domain name service request from a client computing device;

determining, by the service provider, a class of computing devices for the client computing device based, at least in part, on an address of the client computing device;

if a prioritized list is associated with the determined class, resolving, by the service provider, the domain name service request based on the prioritized list for processing subsequent resource requests by identifying a point of presence server associated with the determined class of computing devices; and

if a prioritized list is not associated with the determined class of computing devices, resolving, by the service provider, the domain name service request by utilizing geographic location information associated with the resource request.

2. The method as recited in claim 1, wherein the performance information relates to latency information.

3. The method as recited in claim 1, wherein the at least one identifier corresponds to a uniform resource locator of the service provider.

4. The method as recited in claim 1 further comprising conducting, by the service provider, availability checking prior to resolving the domain name service request.

5. A non-transitory computer-readable storage medium having stored thereon instructions that, when executed, direct a computing system to perform a method for processing content comprising:

obtaining, by a service provider, latency information associated with processing of requests for a resource, wherein the resource is associated with at least one identifier;

generating prioritization information for subsequent processing of requests for the resource based at least in part on the latency information, the prioritization information comprises at least one prioritized list, wherein the at least one prioritized list is associated with at least one class of computing devices, wherein individual prioritized lists identify point of presence servers associated with a class of computing devices;

obtaining, by the service provider, a domain name service request from a client computing device associated with the resource and based on the at least one identifier, the client computing device associated with a class of computing devices;

determining, by the service provider, a class of computing devices for the client computing device based, at least in part, on an address of the client computing device;

determining whether prioritization information is associated with the determined class of computing devices for the computing device;

if a prioritized list is associated with the determined class of computing devices, resolving, by the service provider, the domain name service request based on the prioritized list by identifying a point of presence server associated with the determined class of computing devices; and

if a prioritized list is not associated with the determined class of computing devices, resolving, by the service provider, the domain name service request by utilizing geographic location information associated with the resource request.

6. The non-transitory computer-readable storage medium as recited in claim 5, wherein the at least one identifier corresponds to a uniform resource locator of the service provider.

7. The non-transitory computer-readable storage medium as recited in claim 5, wherein the at least one identifier corresponds to a uniform resource locator of a content provider.

8. The non-transitory computer-readable storage medium as recited in claim 5 further comprising conducting, by the service provider, availability checking prior to resolving the domain name service request.

9. The non-transitory computer-readable storage medium as recited in claim 5, wherein the class of computing device corresponds to an association of a domain name server resolver component.

10. The non-transitory computer-readable storage medium as recited in claim 5, wherein the class of computing device corresponds to an association of at least a portion of a network address.

11. The non-transitory computer-readable storage medium as recited in claim 5, wherein obtaining the latency information associated with a processing of the requested resource includes obtaining latency information from the client computing device executing code associated with the at least one identifier.

12. The non-transitory computer-readable storage medium as recited in claim 5, wherein obtaining the latency information associated with processing of a request for a resource includes obtaining latency information from a content provider executing code associated with the at least one identifier.

13. A computer-implemented system for processing content, the system comprising:

a data store configured to store information correlating performance information related to requests for content; and

a computing system in communication with the data store and comprising a processor, the processor configured to execute instructions that configure the processor to;

obtain monitored information associated with a processing of requested resources from a client computing device;

generate prioritization information for subsequent processing of requests for the resource based, at least in part, on the monitored information, the prioritization information comprises at least one prioritized list, wherein the at least one is associated with at least one class of computing devices, wherein individual prioritized lists identify point of presence servers associated with a class of computing devices;

obtain domain name a service request from a client computing device associated with the requested resources, the client computing device associated with a class of computing devices; and

determine, by the service provider, a class of computing devices for the client computing device based, at least in part, on an address of the client computing device;

determine whether prioritization information is associated with the determined class of computing devices for the computing device;

if a prioritized list is associated with the determined class of computing devices, resolve the domain name service request based on the prioritized list by identifying a point of presence server associated with the determined class of computing devices; and

if a prioritized list is not associated with the determined class of computing devices, resolving, by the service provider, the domain name service request by utilizing geographic location information associated with the resource request.

14. The system as recited in claim 13, wherein at least one identifier associated with the requested resources is a uniform resource locator.

15. The system as recited in claim 13, wherein the class of computing device corresponds to an association of a domain name server resolver component.

16. The system as recited in claim 13, wherein the class of computing device corresponds to an association of at least a portion of a network address.

17. The system as recited in claim 13, wherein the computing system is further operable to conduct availability checking prior to resolving the domain name service request.

18. The system as recited in claim 13, wherein the monitored information corresponds to latency information associated with processing the request associated with the requested resources.

19. The system as recited in claim 13, wherein the computing system is further operable to obtain a request for content from a requesting client computing device responsive to at least one identifier for causing client computing devices to generate a request for content to the service provider.

20. The system as recited in claim 19, wherein the computing system is further operable to transmit a confirmation responsive to the request associated with the at least one identifier.

21. The system as recited in claim 19, wherein the computing system is further operable to transmit an error responsive to the request associated with the at least one identifier.

22. The system as recited in claim 19 wherein the computing system is further operable to make no response based on the request associated with the at least one identifier.