Request routing using network computing components
US-9021128-B2 · Apr 28, 2015 · US
US9712484B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9712484-B1 |
| Application number | US-89277710-A |
| Country | US |
| Kind code | B1 |
| Filing date | Sep 28, 2010 |
| Priority date | Sep 28, 2010 |
| Publication date | Jul 18, 2017 |
| Grant date | Jul 18, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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 of DNS queries initiated by a client computing device, a CDN service provider can correlate client computing device identifiers, such as an Internet Protocol (“IP”) address, with identifiers (e.g., IP addresses) associated with other components in a content delivery environment, such as DNS resolvers associated with the client computing device.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for processing content comprising: providing, by a service provider, at least one identifier for causing client computing devices to generate a request for content to the service provider, the at least one identifier to be included as an embedded resource provided by a content provider; obtaining, by the service provider, a request for content from a first client computing device responsive to the at least one identifier for causing client computing devices to generate a request for content to the service provider, the request for content from the first client computing device associated with a first network address; determining, by the service provider, the first network address associated with the first client computing device; generating, by a point of presence of the service provider, an alternative identifier responsive to the request for content from the first client computing device, the alternative identifier including identification of the point of presence, at least a portion of the first network address, and additional information not included in the request for content in a domain name service (DNS) portion of the alternative identifier, the additional information associated with routing or processing the request for content from the first client computing device; transmitting, by the service provider, at least one instruction causing the first client computing device to generate a subsequent request for content based on the alternative identifier; obtaining, by the service provider, a first DNS query for the alternative identifier from a DNS resolver component associated with the first client computing device, the first DNS query associated with a second network address corresponding to the DNS resolver component; obtaining, by the service provider, the at least a portion of the first network address and the additional information included in the first DNS query for the alternative identifier; correlating, by the service provider, the identification of the point of presence, the at least a portion of the first network address, and the additional information with the second network address corresponding to the DNS resolver component to form correlated information; obtaining, by the service provider, a second DNS query from a second client computing device; determining, by the service provider, a class associated with the second client computing device based at least in part on the correlated information; and resolving the second DNS query based on the determined class. 2. The method as recited in claim 1 further comprising transmitting, by the service provider, information responsive to the first DNS query for the alternative identifier. 3. The method as recited in claim 1 , wherein the at least one identifier for causing client computing devices to generate a request for content to the service provider corresponds to a uniform resource locator of the service provider. 4. The method as recited in claim 1 , wherein the alternative identifier corresponds to a uniform resource locator of the service provider. 5. The method as recited in claim 1 , wherein the alternative identifier includes a label representative of the at least a portion of the first network address. 6. The method as recited in claim 5 , wherein the label representative of the at least a portion of the first network address includes a label representative of timestamp information. 7. The method as recited in claim 1 , wherein the additional information included in the DNS portion of the alternative identifier comprises additional information identifying the first client computing device. 8. The method as recited in claim 1 , wherein generating the alternative identifier responsive to the request for content from the first client computing device, includes encrypting the at least a portion of the obtained first network address associated with the first client computing device. 9. A computer-implemented method for processing content comprising: obtaining, by a service provider, a request for content from a first client computing device responsive to at least one identifier for causing client computing devices to generate a request for content to the service provider, the request for content from the first client computing device associated with a network address; determining, by the service provider, the network address associated with the first client computing device; generating, by a point of presence of the service provider, an alternative identifier responsive to the request for content from the first client computing device, the alternative identifier including identification of the point of presence, information related to the network address associated with the first client computing device, and additional information not included in the request for content in a domain name service (DNS) portion of the alternative identifier, the additional information associated with routing or processing the request for content from the first client computing device; transmitting, by the service provider, at least one instruction causing the first client computing device to generate a subsequent request for content based on the alternative identifier; wherein the subsequent request is associated with a second network address corresponding to a DNS resolver component; obtaining, by the service provider, at least a portion of the network address associated with the first client computing device and the additional information included in the DNS query for the alternative identifier; correlating, by the service provider, the identification of the point of presence, the at least a portion of the network address associated with the first client computing device, and the additional information with the second network address to form correlated information; obtaining, by the service provider, a DNS query from a second client computing device; determining, by the service provider, a class associated with the second client computing device based at least in part on the correlated information; and resolving the second DNS query based on the determined class. 10. The method as recited in claim 9 , wherein the at least one identifier for causing client computing devices to generate a request for content to the service provider corresponds to a uniform resource locator of the service provider. 11. The method as recited in claim 9 , wherein the at least one identifier for causing client computing devices to generate a request for content to the service provider corresponds to a uniform resource locator of a content provider. 12. The method as recited in claim 9 , wherein the alternative identifier corresponds to a uniform resource locator of the service provider. 13. The method as recited in claim 9 , wherein the additional information in the DNS portion of the alternative identifier comprises additional information identifying the first client computing device. 14. The method as recited in claim 13 , wherein the additional information identifying the first client computing device comprises timestamp information. 15. A computer-implemented system for processing content, the system comprising: a data store for storing information correlating a plurality of identifiers associated with client computing device requests for content; and a computing system in communication with said data store that is operative to: provide at least one identifier for causing client computing devices to generate a request for content to the computing system, the at least one identifier to be included as an embedded resour
Electricity · mapped topic
containing special prefixes · CPC title
using domain name system [DNS] · CPC title
Storing data temporarily at an intermediate stage, e.g. caching · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.