Method and system for purging content from a content delivery network

• US 8,266,305 B2
• Filed: 09/18/2006
• Issued: 09/11/2012
• Est. Priority Date: 10/31/2000
• Status: Expired due to Term

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Sherman, Alexander, Lisiecki, Philip A., Wein, Joel M., Dailey, Don A., Dilley, John, Weihl, William E.
• Primary Examiner(s): Feild, Lynn
• Assistant Examiner(s): Pollack, Melvin H
• Application Number:
  US11/522,557
• Publication Number:
  US 20070174442A1
• Time in Patent Office: 2,185 Days
• Field of Search: 709/203, 709/218, 709/219, 709/227, 709/229, 709/248, 709/249, 718/101, 726/12, 726/14, 726/30
• US Class Current: 709/229
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 63/14 for detecting or protecting against malicious traffic
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A content file purge mechanism for a content delivery network (CDN) is described. A Web-enabled portal is used by CDN customers to enter purge requests securely. A purge request identifies one or more content files to be purged. The purge request is pushed over a secure link from the portal to a purge server, which validates purge requests from multiple CDN customers and batches the requests into an aggregate purge request. The aggregate purge request is pushed from the purge server to a set of staging servers. Periodically, CDN content servers poll the staging servers to determine whether an aggregate purge request exists. If so, the CDN content servers obtain the aggregate purge request and process the request to remove the identified content files from their local storage.

Claims

1. A system, comprising:

a content delivery network operated by a service provider on behalf of participating content providers, the content delivery network comprising content servers that are shared by the participating content providers to cache and serve content files, wherein content servers in the content delivery network also share content files with each other; and

a mechanism for selectively identifying and delivering given requests to a set, or a given subset, of content servers in the content delivery network, comprising;

a participating content provider interface through which given information to be provided to the content servers and entered by a first participating content provider and a second participating content provider is received, the first participating content provider being distinct from the second participating content provider, the given information comprising instructions for how content files associated with each respective participating content provider are to be handled on the content servers;

a control server for receiving first and second requests pushed from the interface, validating the first and second requests, and batching at least the first and second requests into an aggregate request, wherein the first request is associated with the first participating content provider and is derived from the given information received at the participating content provider interface as a result of being entered by the first participating content provider about how content files associated with the first participating content provider are to be handled on the content servers, and the second request is associated with the second participating content provider and is derived from the given information received at the participating content provider interface as a result of being entered by the second participating content provider about how content files associated with the second participating content provider are to be handled on the content servers;

a set of staging servers for receiving the aggregate request pushed from the control server, wherein each staging server of the set of staging servers is located remotely from the content servers; and

code executing on a given content server for periodically polling a given staging server over a network connection, for pulling the aggregate request, for taking a given action with respect to a content file associated with the first request in the aggregate request, and for taking a given action with respect to a content file associated with the second request in the aggregate request.

2. The system as described in claim 1 wherein each of the first and second requests is a purge request.

3. The system as described in claim 1 wherein the interface is a Web-based portal.

4. The system as described in claim 1 further including a secure link between the control server and each of the set of staging servers.

5. The system as described in claim 1 further including a secure link between each of the staging servers and each of the content servers.

6. The system as described in claim 1 wherein at least one of the first and second requests is associated with content file metadata.

7. A machine-implemented method of identifying and scheduling information for dissemination, comprising

securely pushing an aggregate request from a central server to each of a set of staging servers, each aggregate request including an identifier associated with a content file being served from content servers in a content delivery network, wherein the content delivery network is operated by a service provider on behalf of participating content providers who use the content servers to serve content files;

periodically, having each of a set, or a given subset, of content servers securely obtain, over a network connection, the aggregate request from a given staging server located remotely from the content servers, wherein the content servers obtain the aggregate request independently; and

at each content server that obtains the aggregate request, taking a given action with respect to the content file identified in the aggregate request.

8. The machine-implemented method as described in claim 7 wherein the given action is a purge of the content file identified in the aggregate request.

9. The machine-implemented method as described in claim 8 further including issuing a notification that the content file identified in the aggregate request has been purged from the content delivery network.

10. The machine-implemented method as described in claim 7 wherein the aggregate request includes metadata associated with the content file.