Systems and methods for processing requests for content of a content distribution network
US-2022158970-A1 · May 19, 2022 · US
US11606331B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-11606331-B1 |
| Application number | US-202217958354-A |
| Country | US |
| Kind code | B1 |
| Filing date | Oct 1, 2022 |
| Priority date | Dec 11, 2018 |
| Publication date | Mar 14, 2023 |
| Grant date | Mar 14, 2023 |
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.
Improved methods for retrieval of content from CDNs is provided that includes a rendezvous controller that receives information of an identification of content being requested and an estimated location of a content requesting device. Based on this information, the rendezvous system identifies a server within a CDN from which the requested content may be retrieved. The selected server may be based on a repeatable hash function such that the likelihood that the content being requested is cached at the selected server. Steering requests to a server of the CDN which may have the content cached may reduce the number of servers within the CDN with the same cached content, particularly for the highest requested content. The rendezvous system may then return a corresponding domain name associated with the selected server and that can be subsequently submitted to a DNS for resolution to the IP address of the identified server.
Opening claim text (preview).
I claim: 1. A method of processing content requests comprising: receiving, at a networking device, a request for content comprising each of a content identifier associated with a content file and a location identifier associated with a geographic location of a content-receiving device; generating, by the network device and based on the content identifier, a server identifier corresponding to a server in the geographic location; transmitting, to a requesting device, a domain name comprising a server identifier corresponding to the server, an indication of the geographic location of the content-receiving device, and a shared domain identifier, wherein a domain name system (DNS) utilizes the domain name to obtain an identification of the server from a database associated with the shared domain identifier; and executing a hashing function with the content identifier as an input variable, wherein the output of the hashing function corresponds to the server identifier of the server. 2. The method of claim 1 wherein the server is geographically proximate to the geographic location indicated by the location identifier. 3. The method of claim 1 wherein the server identifier and the indication of the geographic location are encoded prior to transmission of the domain name to the DNS. 4. The method of claim 1 wherein the database comprises a plurality of entries, each of the plurality of entries comprising a domain name associated with the shared domain identifier and a corresponding content server identifier. 5. The method of claim 1 wherein the identification of the server comprises an Internet Protocol (IP) address at which the server receives communications via a network. 6. The method of claim 1 wherein the request for content is received from a client computing device and transmitting the domain name comprises transmitting the domain name to the client computing device. 7. A networking device comprising: one or more processors; and a non-transitory storage device configured to store one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to: communicate with a requesting device to receive a request for content comprising each of a content identifier associated with a content file and a location identifier associated with a geographic location of a content-receiving device; generate, based on the content identifier, a server identifier corresponding to a server in the geographic location, wherein generating the server identifier comprises executing a hashing function with the content identifier as an input variable, wherein the output of the hashing function corresponds to the server identifier of the server; and transmit, to the requesting device, a domain name comprising a server identifier corresponding to the server, an indication of the geographic location of the content-receiving device, and a shared domain identifier, wherein a domain name system (DNS) utilizes the domain name to obtain an identification of the server from a database associated with the shared domain identifier. 8. The networking device of claim 7 wherein the requesting device is a content management system (CMS) and transmitting the domain name comprises transmitting the domain name to the CMS. 9. The networking device of claim 8 wherein the location identifier is inserted into the request for content by the CMS upon receiving a request from the content-receiving device. 10. The networking device of claim 7 wherein the requesting device is the content-receiving device. 11. The networking device of claim 7 wherein the output of the hashing function indicates a location on a hashing circle, wherein each location on the ring corresponds to a value in a hash key space defined by the range of outcomes of the hashing function and each value corresponds to one of the plurality of content servers. 12. The networking device of claim 7 wherein the one or more programs further cause the one or more processors to: transmit a retrieval instruction to the server to retrieve and store the requested content. 13. The networking device of claim 7 wherein the one or more programs further cause the one or more processors to: encode a portion of the domain name prior to transmission of the domain name to the DNS.
using cryptographic hash functions · CPC title
Storing data temporarily at an intermediate stage, e.g. caching · CPC title
Internet protocol [IP] addresses · CPC title
specially adapted for the location of the user terminal · CPC title
using domain name system [DNS] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.