Content delivery network (CDN) content server request handling mechanism with metadata framework support

• US 20070250560A1
• Filed: 06/27/2007
• Published: 10/25/2007
• Est. Priority Date: 04/14/2000
• Status: Abandoned Application

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Karger, David, Wein, Joel, Lisiecki, Philip, Kloninger, John, Nottingham, Mark
• Application Number:
  US11/768,935
• Publication Number:
  US 20070250560A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/61 for supporting one-way streaming services, e.g. Internet radio
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30

Abstract

To serve content through a content delivery network (CDN), the CDN must have some information about the identity, characteristics and state of its target objects. Such additional information is provided in the form of object metadata, which according to the invention can be located in the request string itself, in the response headers from the origin server, in a metadata configuration file distributed to CDN servers, or in a per-customer metadata configuration file. CDN content servers execute a request identification and parsing process to locate object metadata and to handle the request in accordance therewith. Where different types of metadata exist for a particular object, metadata in a configuration file is overridden by metadata in a response header or request string, with metadata in the request string taking precedence.

Claims

1. A method operative in a content delivery network (CDN) wherein participating content providers identify content to be served from a set of CDN content servers in response to requests, wherein the CDN uses metadata to determine how a CDN content server will handle a request for a given object, comprising:

establishing a framework for delivery of metadata to a given CDN content server either in-band or out-of-band;

at a given CDN content server, parsing a request for the given object and identifying a set of metadata; and

applying at least one precedence rule to the set of metadata to identify given metadata to be applied to the given content prior to serving a response to the request from the given CDN content server.

2. The method as described in claim 1 wherein the metadata is delivered to the given CDN content server in-band within a request string.

3. The method as described in claim 1 wherein the metadata is delivered to the given content server in-band within a HTTP response header.

4. The method as described in claim 1 wherein the metadata is delivered to the given content server out-of-band within a configuration file.

5. The method as described in claim 4 wherein the configuration file is generated by a CDN service provider and delivered to the CDN content servers over the CDN.

6. The method as described in claim 4 wherein the configuration file is generated by a participating content provider.

7. The method as described in claim 1 wherein the precedence rule overrides out-of-band metadata with in-band metadata to identify the given metadata.

8. A method operative in a content delivery network (CDN) wherein participating content providers identify content to be served from a set of CDN content servers in response to requests, wherein the CDN uses metadata to determine how a CDN content server will handle a request for a given object, comprising:

delivering metadata to a given CDN content server in a configuration file;

at the given CDN content server, parsing a request for the given object and identifying the configuration file; and

overriding the configuration file with any in-band metadata associated with the request.

9. The method as described in claim 8 wherein the in-band metadata is delivered to the given CDN content server in the request string.

10. The method as described in claim 8 wherein the in-band metadata is delivered to the given CDN content server in an HTTP response header from a participating content provider origin server.

11. The method as described in claim 8 wherein the configuration file is delivered to the CDN content server from a CDN service provider.

12. The method as described in claim 8 wherein the configuration file is generated by a participating content provider.

13. In a content delivery network (CDN) wherein participating content providers identify content to be served from a set of CDN content servers in response to requests and the CDN uses metadata to determine how a CDN content server will handle the request, the improvement comprising:

a framework for locating metadata for a given object in one or more of a set of data structures selected from the set of;

a request string, a response header, and a configuration file; and

a CDN surrogate origin server including code for parsing a request for an object, for identifying metadata associated with the object, and for applying the metadata to the object prior to serving the object in response to the request.

14. In the content delivery network as described in claim 13 wherein the CDN surrogate origin server code applies a given precedence rule to the metadata prior to applying the metadata to the object.

15. In the content delivery network as described in claim 14 wherein the given precedence rule overrides metadata in the configuration file with any metadata in a request string or a response header.

16. In the content delivery network as described in claim 14 wherein the given precedence rule overrides metadata in the configuration file first with metadata in the response header and second with metadata in the request string.