Scalable content delivery network request handling mechanism to support a request processing layer
US-2017078453-A1 · Mar 16, 2017 · US
US10257318B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10257318-B2 |
| Application number | US-201715473279-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 29, 2017 |
| Priority date | Dec 21, 2012 |
| Publication date | Apr 9, 2019 |
| Grant date | Apr 9, 2019 |
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.
Described herein are improved systems, methods, and devices for delivering and managing metadata in a distributed computing platform such as a content delivery network (CDN) so as to configure content servers to handle client requests. The teachings hereof provide, among other things, scalable and configurable solutions for delivering and managing metadata, preferably by leveraging dynamically obtained control information. For example, in one embodiment, a given content server may store metadata, e.g., in a configuration file, that references dynamic, late-bound control information for use in satisfying dependencies. This dynamic control information can be requested by the CDN content server, typically from a remote host, when needed to parse and execute the metadata.
Opening claim text (preview).
The invention claimed is: 1. An apparatus comprising: a content delivery network (CDN) server operated by a CDN service provider, the CDN server having circuitry forming one or more processors coupled to memory storing non-transitory computer-program instructions to be executed by the one or more processors to cause the CDN server to: receive a first request from a client device over a network interface, the first request being a request for particular content; associate the first request with a particular configuration selected from a plurality of configurations stored at the CDN server, based at least in part on a hostname in the first request, the particular configuration being associated with a cloud service provider distinct from the CDN service provider, the cloud service provider being at least one of: an infrastructure as a service (IaaS) provider, a platform as a service (PaaS) provider, a software as a service (SaaS) provider; identify, within the particular configuration, a reference to dynamic control information; at the time of the first request, and in response to receipt of the first request and the identification of the reference to the dynamic control information, extract an identifier from the first request, the identifier corresponding to a customer of the cloud service provider, and send a second request that includes the identifier to a remote host to retrieve the dynamic control information; receive the dynamic control information from the remote host in response to the second request, wherein the dynamic control information comprises code with one or more logical conditions for the CDN server to evaluate; in response to receipt of the dynamic control information, evaluate the code, said evaluation resulting in at least one of: (i) a value for a variable declared in the particular configuration and (ii) a determination whether to perform an action declared in the particular configuration; apply the particular configuration to determine how to handle the first request, said application including using at least one of (iii) the value for the variable and (iv) the determination whether to perform the action; and, handling the first request in accord with the application of the particular configuration. 2. The apparatus of claim 1 , wherein the code defines one or more categories of client-server traffic to which the dynamic control information applies. 3. The apparatus of claim 1 , wherein the dynamic control information is a content policy. 4. The apparatus of claim 1 , wherein the dynamic control information is defined by the cloud service provider. 5. The apparatus of claim 1 , wherein the first request comprises an HTTP request and the CDN server comprises an HTTP proxy server. 6. The apparatus of claim 1 , wherein the identifier extracted from the first request comprises at least one of: at least part of a URI, and at least part of a hostname. 7. The apparatus of claim 1 , wherein said evaluation of the code results in (i) a value for a variable declared in the particular configuration, and wherein the application of the particular configuration to determine how to handle the first request includes using (iii) the value for the variable. 8. The apparatus of claim 1 , wherein said evaluation of the code results in (ii) a determination whether to perform an action declared in the particular configuration, and wherein the application of the particular configuration to determine how to handle the first request includes using (iv) the determination whether to perform the action. 9. The apparatus of claim 1 , wherein said evaluation of the code results in (ii) a determination whether to perform an action declared in the particular configuration, and the determination is a true or false response from the code. 10. A method performed by a content delivery network (CDN) server operated by a CDN service provider, the method comprising: receiving a first request from a client device over a network interface, the first request being a request for particular content; associating the first request with a particular configuration selected from a plurality of configurations stored at the CDN server, based at least in part on a hostname in the first request, the particular configuration being associated with a cloud service provider distinct from the CDN service provider, the cloud service provider being at least one of: an infrastructure as a service (IaaS) provider, a platform as a service (PaaS) provider, a software as a service (SaaS) provider; identifying, within the configuration, a reference to dynamic control information; at the time of the first request, and in response to receipt of the first request and the identification of the reference to the dynamic control information, extracting an identifier from the first request, the identifier corresponding to a customer of the cloud service provider, and sending a second request that includes the identifier to a remote host to retrieve the dynamic control information; receiving the dynamic control information from the remote host, in response to the second request, wherein the dynamic control information comprises code with one or more conditions for the CDN server to evaluate; in response to receipt of the dynamic control information, evaluating the code in the dynamic control information, said evaluation resulting in at least one of: (i) a value for a variable declared in the particular configuration and (ii) a determination whether to perform an action declared in the particular configuration; applying the particular configuration to determine how to handle the first request, said application including using at least one of (iii) the value for the variable and (iv) the determination whether to perform the action; and, handling the first request in accord with the application of the particular configuration. 11. A system comprising: a content delivery network (CDN) server operated by a CDN service provider, the CDN server having circuitry forming one or more processors coupled to memory storing non-transitory computer-program instructions to be executed by the one or more processors to cause the CDN server to: receive a first request from a client device over a network interface, the first request being a request for particular content; associate the first request with a particular configuration selected from a plurality of configurations stored at the CDN server, based at least in part on a hostname in the first request, the particular configuration being associated with a cloud service provider distinct from the CDN service provider, the cloud service provider being at least one of: an infrastructure as a service (IaaS) provider, a platform as a service (PaaS) provider, a software as a service (SaaS) provider; identify, within the configuration, a reference to dynamic control information; at the time of the first request, and in response to receipt of the first request and the identification of the reference to the dynamic control information, extract an identifier from the first request, the identifier corresponding to a customer of the cloud service provider, and send a second request that includes the identifier to a remote host to retrieve the dynamic control information; receive the dynamic control information from the remote host, in response to the second request, wherein the dynamic control information comprises code with one or more conditions for the CDN server to evaluate; in response to receipt of the dynamic control information, evaluate the code in the dynamic control information, said evaluation resulting in at least one of: (i) a value for a variable declared in the particular configuration and (ii) a
wherein the managed service relates to media content delivery, e.g. audio, video or TV · CPC title
Configuration setting · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Service on demand, e.g. definition and deployment of services in real time · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.