US 9456053

US Patent 9456053: Content Delivery Network

Title: Content delivery network

Assignee: Sandpiper Cdn LLC (Current Assignee); Level 3 Communications LLC (Original Assignee)

Inventors: Christopher Newton, Laurence R. Lipstone, William Crowder, Jeffrey G. Koller, David Fullagar, Maksim Yevmenkin

Filing Date: 2012-12-14

Issue Date: 2016-09-27

Abstract:
A content delivery network (CDN) that treats all data that is to be moved between CDN components (e.g., control core data, log data, etc.) as web objects or resources. The CDN can thus use its own mechanisms to deal with CDN control and/or management-related information (e.g., control core data). Thus, any CDN component can obtain CDN data using the CDN. In effect, the control core can act as an origin tier for such objects, and each CDN object has a URL (or whatever address is used by the CDN), and each CDN object can be requested, filled, invalidated, refreshed, etc. In some embodiments, the CDN includes cache servers that are configured to process executable resources, and CDN users (e.g., content providers, the CDN itself) are able to provide extensions to resources via these executable resources.

Plain-Language Overview of Independent Claims:

US Patent 9456053 has 12 independent claims.

Independent Claim 1 (Method for Content Delivery):
This claim describes a method for operating a content delivery network (CDN) where various components of the CDN (like cache servers and a control core) exchange data by treating that data as standard web objects, each with a unique identifier (like a URL). The control core acts as the authoritative source for these CDN-related web objects. When a CDN component needs such an object, it requests it from the control core using its identifier, similar to how clients request content from origin servers. The CDN then delivers this requested CDN-related web object to the requesting component.

Independent Claim 2 (Content Delivery Network System):
This claim defines a content delivery network (CDN) system. It includes multiple cache servers and at least one control core. The control core is configured to store and serve data related to the CDN's configuration and operation, treating this data as web objects with unique identifiers. The cache servers are designed to obtain these CDN-related web objects from the control core by making requests using their identifiers.

Independent Claim 3 (Method for Content Delivery with Executable Resources):
Similar to Claim 1, this method involves a CDN where data exchange between components is done using web objects. A key addition here is that the CDN components can process "executable resources," which are scripts or code that can be executed by an interpreter within the CDN to generate a response. This allows for dynamic and extended functionality within the CDN.

Independent Claim 4 (Content Delivery Network System with Executable Resources):
This claim builds on Claim 2 by specifying a CDN system that includes executable resources. The control core stores CDN-related data as web objects, some of which are executable resources. The cache servers are capable of requesting and executing these executable resources to generate responses or perform other functions.

Independent Claim 5 (Method for Adding a Cache Server):
This claim outlines a method for integrating a new cache server into a CDN. The new cache server registers with the control core and then requests configuration data from the control core, which includes information about the CDN's operations and potentially customer-specific settings. The control core provides this data to the new cache server, enabling it to begin functioning within the CDN.

Independent Claim 6 (Content Delivery Network for Adding a Cache Server):
This claim describes a CDN system structured to facilitate the addition of new cache servers. It includes a control core that stores CDN configuration data and is equipped to register new cache servers and provide them with the necessary configuration data. This allows new cache servers to integrate and become operational within the network.

Independent Claim 7 (Method for Processing Requests with Customer Scripts):
This method focuses on a cache server in a CDN receiving a request for a resource. The cache server determines if a customer configuration script (CCS) is associated with the request's customer. If so, it obtains and uses this CCS to guide the processing of the request and the serving of the resource, allowing for customized handling based on customer-defined rules.

Independent Claim 8 (Cache Server with Customer Script Processing):
This claim details a cache server designed for a CDN. The server includes a mechanism to identify customers associated with incoming requests and a database to store customer configuration scripts (CCSs). The server retrieves and utilizes the relevant CCS to process requests and serve content according to customer-specific policies.

Independent Claim 9 (Method for Dynamic Configuration of Handlers):
This claim describes a method executed by a cache server in a CDN. Upon receiving a request, the cache server determines if a customer configuration script (CCS) is associated with the request. If a CCS exists, it is executed to dynamically configure a sequence of handlers that will then process the request and ultimately deliver the resource.

Independent Claim 10 (Cache Server with Dynamic Handler Configuration):
This claim specifies a cache server in a CDN that can dynamically configure its request processing. It includes a mechanism to identify customers and their associated customer configuration scripts (CCSs). The server is configured to execute a CCS to set up a specific sequence of handlers to process a request.

Independent Claim 11 (Method for Request-Response Processing in a CDN Component):
This method covers a CDN component receiving a resource request. The component determines if it has a valid Global Configuration Object (GCO), which contains information necessary to serve the resource. If not, it retrieves the GCO (e.g., from the control core). It then obtains a Customer Configuration Script (CCS) if one is associated with the request, and uses the GCO and CCS to process the request and deliver the resource.

Independent Claim 12 (CDN Component for Request-Response Processing):
This claim describes a CDN component (e.g., a cache server) equipped for request-response processing. It includes modules for obtaining and validating a Global Configuration Object (GCO) and for retrieving Customer Configuration Scripts (CCSs). The component uses both the GCO and CCSs to process incoming resource requests.

CAFC 2026 Dockets Search:

As of April 26, 2026, a search for "9456053" in the CAFC 2026 dockets did not return any directly identifiable litigation cases. Information regarding court dockets generally requires specific case numbers or party names for precise searches, and broad searches for patent numbers within dockets are not always comprehensive in public search interfaces.

Note: The legal status on Google Patents (https://patents.google.com/patent/[US9456053](/patent/US9456053)/en) indicates the patent is "Active, expires 2034-03-14" and mentions "Family has litigation," specifically:

• "PTAB case IPR2026-00190 filed (Pending)"
• "US case filed in Texas Eastern District Court"
• "First worldwide family litigation filed"

While the CAFC 2026 dockets search did not yield direct results for the patent number, the Google Patents information confirms ongoing litigation related to this patent family, including a PTAB case IPR2026-00190, which is currently pending. The Texas Eastern District Court case is identified by case number 2:25-cv-00664.