Request routing using a popularity identifier to identify a cache component

• US 10,264,062 B2
• Filed: 11/06/2015
• Issued: 04/16/2019
• Est. Priority Date: 03/27/2009
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Marshall, Bradley E., Sivasubramanian, Swaminathan
• Primary Examiner(s): Murray, Daniel C.
• Application Number:
  US14/935,228
• Publication Number:
  US 20160065665A1
• Time in Patent Office: 1,257 Days
• Field of Search: 709217
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04L 2101/668 Internet protocol [IP] address subnets
• CPC Class Codes: H04L 45/566 Routing instructions carried by the data packet, e.g. active networks
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1014 based on the content of a request
• 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/1036 Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• 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
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04N 21/278 : Content descriptor database or directory service for end-user access details of content or meta data based information retrieval of video data in video databases G06F16/739

Abstract

A system, method and computer-readable medium for request routing based on content popularity information are provided. A client computing device transmits a first DNS query to a content delivery network service provider. The content delivery network service provider transmits an alternative resource identifier in response to the client computing device DNS query. The alternative resource identifier is selected as a function of popularity information pertaining to the requested resource. The client computing device then transmits a second DNS query to the content delivery network service provider. The content delivery network service provider can then either resolve the second DNS query with an IP address of a cache component or transmit another alternative resource identifier that will resolve to the content delivery network service provider. The process can repeat until a DNS nameserver resolves a DNS query from the client computing device.

Claims

1. A computer-implemented method comprising:

receiving a domain name system (DNS) query from a client computing device by a computing device associated with a content delivery network (CDN) service provider, wherein the DNS query corresponds to a resource associated with a first resource identifier, wherein a popularity identifier is included in a DNS portion of the first resource identifier accessible to a DNS nameserver component;

parsing, by the DNS nameserver component, the first resource identifier so as to obtain the popularity identifier for use in further obtaining popularity information regarding the resource, wherein the popularity information is associated with the popularity identifier;

identifying a resource cache component of the CDN service provider based at least upon at least a portion of the popularity information; and

transmitting information identifying the resource cache component to the client computing device.

2. The method of claim 1, wherein identifying a resource cache component comprises identifying an Internet Protocol address.

3. The method of claim 1, wherein the popularity information is determined by the CDN service provider.

4. The method of claim 1, wherein the popularity information is retrieved by the CDN service provider.

5. The method of claim 1, wherein the popularity information is periodically updated by an original content provider.

6. The method of claim 1 further comprising obtaining additional popularity information regarding the requested resource based on the popularity identifier included in the first resource identifier.

7. The method of claim 1, wherein the popularity identifier included in the first resource identifier corresponds to a frequency at which the resource is requested from the CDN service provider.

8. The method of claim 1, wherein the popularity identifier included in the first resource identifier corresponds to a total number of requests for the resource received by the CDN service provider.

9. The method of claim 1, wherein the popularity identifier included in the first resource identifier corresponds to a popularity category associated with the resource.

10. The method of claim 1 further comprising obtaining additional routing information including at least one of service routing criteria, network performance routing criteria, financial cost routing criteria, or content provider specified routing criteria.

11. A system comprising:

a computing device having a processor and a memory to present a first network point of presence (POP) associated with a content delivery network (CDN) service provider,

wherein the first network POP includes a first domain name system (DNS) nameserver component that receives a DNS query from a client computing device,

wherein the DNS query corresponds to a resource associated with a first resource identifier,

wherein a popularity identifier is included in a DNS portion of the first resource identifier,

wherein the popularity identifier is associated with the resource, and

wherein the first network POP is operative to;

parse, by the first DNS nameserver component, the first resource identifier so as to obtain the popularity identifier for use in further obtaining popularity information regarding the resource, wherein the popularity information is associated with the popularity identifier;

identify a resource cache component of the CDN service provider based at least upon at least a portion of the popularity information; and

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

12. The system of claim 11, wherein identifying a resource cache component comprises identifying an Internet Protocol address.

13. The system of claim 11, wherein the first network POP is operative to obtain additional popularity information regarding the requested resource based on the popularity identifier included in the first resource identifier.

14. The system of claim 11, wherein the popularity information is determined by the CDN service provider.

15. The system of claim 11, wherein the popularity information is retrieved by the CDN service provider.

16. The system of claim 11, wherein the popularity information is periodically updated by an original content provider.

17. The system of claim 11, wherein the popularity identifier included in the first resource identifier corresponds to a frequency at which the resource is requested from the CDN service provider.

18. The system of claim 11, wherein the popularity identifier included in the first resource identifier corresponds to a total number of requests for the resource received by the CDN service provider.

19. The system of claim 11, wherein the popularity identifier included in the first resource identifier corresponds to a popularity category associated with the resource.

20. The system of claim 11 further comprising obtaining additional routing information including at least one of service routing criteria, network performance routing criteria, financial cost routing criteria, or content provider specified routing criteria.