Level 3 Communications, LLC

Sandpiper Cdn, LLC

William Crowder

Christopher Newton

Laurence R Lipstone

Andrew D Swart

Lewis Robert Varney

David Fullagar

Jeffrey G Koller

William R Power

Maksim Yevmenkin

Daniel L Jensen

Pawel Jakobowski

Kevin Christopher Johns

Fiona Wong

Vikas Dogra

Fiona Wang

Daniel Lee Jensen

Jeffrey Koller

A content delivery network (CDN) includes a plurality of CDN components including at least one CDN rendezvous mechanism and at least one control core. The CDN components are controlled by control core data from the at least one control core. Some CDN components obtain CDN resources including control core data from at least some other CDN components. The CDN components use the CDN rendezvous mechanism to select one or more CDN components from which to obtain CDN resources.

Control in a content delivery network

A method for registering a handler in a configured sequence of handlers includes: receiving, by a processor and memory implementing a sequencer infrastructure, a configuration script defining a sequence including one or more handler identifiers and corresponding one or more handler arguments; invoking a handler initialization entry point for a handler corresponding to a handler identifier, the invoking the handler initialization entry point including: selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of: a configured instance of the handler; a configured alternate handler different from the handler; an alternate sequence of handlers; an expression; and a no-op handler; and initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments; and adding the configured handler to a configured sequence of handlers.

Systems and methods for configuration of sequence handlers

Examples described herein relate to apparatuses and methods for managing caching for a content delivery system, which may include receiving a content request indicating that the caching agent is requesting content data for a client, filling the content data in a first cache storage of the business logic agent, providing the cached content data to the caching agent, and while a second cache storage of the caching agent is being filled with the content data, maintaining the cached content data in response to receiving additional content requests from the caching agent. The additional content requests may indicate that the caching agent is requesting the same content data for additional clients.

Cache management in content delivery systems

Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Uniformity of instructions for content requests and responses in a content delivery network

A method on a device in a content delivery (CD) network (CDN) that distributes content on behalf of one or more subscribers. In response to receiving configuration information from a subscriber, the configuration information relating to at least one property of the subscriber, generating subscriber-specific platform configuration information for the at least one property. Storing the subscriber-specific platform configuration information in platform configuration storage. Invalidating prior platform configuration information associated with the particular subscriber. Responsive to a request from a CDN component for platform configuration information associated with the particular subscriber: obtaining the subscriber-specific platform configuration information from the platform configuration storage; and providing the subscriber-specific platform configuration information to the CDN component.

Subscriber configuration ingestion in a content delivery network

A computer-implemented method, operable with a content delivery network (CDN) uses late binding of caching policies; by a caching node in the CDN, in response to a request for content, determining if the content is cached locally. When it is determined that said content is cached locally, then: determining a current cache policy associated with the content; and then determining, based on said current cache policy associated with the content, whether it is acceptable to serve the content that is cached locally; based on said determining, when it is not acceptable to serve the content that is cached locally, obtaining a new version of the content and then serving the new version of the content, otherwise when it is acceptable to serve the content that is cached locally, serving the content that is cached locally.

Caching in a content delivery framework

A computer-implemented method, in a content delivery (CD) network that delivers content on behalf of multiple content providers. The method includes, at a server in the CDN, wherein the server is currently processing at least one other request in at least one other session: receiving a connection request from a client, the connection request being associated with a corresponding content request; determining whether handling the content request will cause the server to become overloaded; and, based on the determining in (B) and on information about the content request, conditionally (i) accepting the content request, and (ii) terminating or throttling at least one session on the server.

Predictive load mitigation and control in a content delivery network (CDN)

Examples described herein relate to systems and methods for containing a faulty stimulus. A computer-implemented method may include listing in a suspect list every received stimulus including the faulty stimulus, and implicitly testing the stimuli by respectively acting upon those stimuli by a software application. Responsive to successfully acting upon each of the stimuli besides the faulty stimulus, each non-faulty stimulus is deleted from the suspect list and, responsive to such deletion, made available to a downstream node. Responsive to acting upon the faulty stimulus, the software application crashes which leaves the faulty stimulus listed in the suspect list. The software application then restarts and deems the faulty stimulus as being faulty based upon the faulty stimulus still being listed in the suspect list after the restart.

Containing a faulty stimulus in a content delivery network

Examples described herein relate to systems and methods for storing content items. The methods may be implemented by a computer comprising a processor, primary storage device, secondary storage, device and network interface. The primary storage device may receive, via the network interface, a plurality of content items responsive to respective requests from clients. The plurality of content items may be distributed, via the network interface, from the primary storage device to clients responsive to the respective requests from the clients. The processor may generate a dynamic priority list for the content items based on the respective requests from the clients over time, and may write, based on the dynamic priority list, only a subset of the content items to the secondary storage device.

Growing community of inventors

Camarillo, CA, United States of America

William Crowder