Method for caching and delivery of compressed content in a content delivery network

• US 7,395,355 B2
• Filed: 07/11/2002
• Issued: 07/01/2008
• Est. Priority Date: 07/11/2002
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Afergan, Michael M., Schlossberg, Charisma, Hong, Duke P., Rao, Satish Balusu
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): KOROBOV, VITALI A
• Application Number:
  US10/194,043
• Publication Number:
  US 20040010621A1
• Time in Patent Office: 2,182 Days
• Field of Search: 709/247, 709/219, 709/232, 709/217, 709/203, 709/225, 709/231
• US Class Current: 709/247
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 45/20 Hop count for routing purposes, e.g. TTL
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

A content delivery network (CDN) edge server is provisioned to provide last mile acceleration of content to requesting end users. The CDN edge server fetches, compresses and caches content obtained from a content provider origin server, and serves that content in compressed form in response to receipt of an end user request for that content. It also provides “on-the-fly” compression of otherwise uncompressed content as such content is retrieved from cache and is delivered in response to receipt of an end user request for such content. A preferred compression routine is gzip, as most end user browsers support the capability to decompress files that are received in this format. The compression functionality preferably is enabled on the edge server using customer-specific metadata tags.

Claims

1. A server operative in a content delivery network that is managed by a service provider and shared by a set of participating content provider customers, wherein participating content provider customers identify content to be delivered over the content delivery network and such content has associated therewith at least one content handling requirement that is enforceable at the server, comprising:

an XML-based structured document associated with each participating content provider customer, the XML-based structured document comprising one of;

at least a first metadata tag, and a second metadata tag, wherein attributes of the first and second metadata tags are settable on a per participating content provider customer basis, and wherein each metadata tag has an associated match type condition;

a compression utility;

code responsive to receipt of a request for content associated with a given participating content provider customer for retrieving and parsing the XML-based structured document associated with that participating content provider customer;

code responsive to a match on the associated match type condition in the first metadata tag for applying the compression utility to a first content type prior to caching; and

code responsive to a match on the associated match type condition in the second metadata tag for applying the compression utility to a second content type prior to serving;

wherein the first content type and the second content type comprise content types associated with content that a given participating content provider customer has identified to be delivered over the content delivery network.

2. The server as described in claim 1 wherein the compression utility is gzip.

3. The server as described in claim 1 wherein the first content type is content that has a given time-to-live (TTL) associated therewith that is greater than zero.

4. The server as described in claim 1 wherein the first content type is content that is unassociated with an ESI request.

5. The server as described in claim 1 wherein the second content type is content that has a given time-to-live (TTL) associated therewith that is zero.

6. The server as described in claim 1 wherein the second content type is content that is associated with an ESI request.

7. The server as described in claim 1 wherein the code is executable in a processor.

8. In a content delivery network (CDN) edge server having a processor, a cache, an HTTP server-side request handling routine and an HTTP client-side request handling routine, wherein the edge server is managed by a service provider and shared by a set of participating content provider customers, wherein participating content provider customers identify content to be delivered over the content delivery network and such content has associated therewith at least one content handling requirement that is enforceable at the edge server, the improvement comprising:

an XML-based structured document associated with each participating content provider customer, the XML-based structured document comprising one of;

at least a first metadata tag, and a second metadata tag, wherein attributes of the first and second metadata tags are settable on a per participating content provider customer basis, and wherein each metadata tag has an associated match type condition;

code responsive to receipt of a request for content associated with a given participating content provider customer for retrieving and parsing the XML-based structured document associated with that participating content provider customer;

a first compression routine associated with the server-side request handling routine;

a second compression routine associated with the client-side request handling routine; and

a metadata routine (a) responsive to a match on the associated match type condition in the first metadata tag associated with a given first type of content for applying the first compression routine to the given first type of content, and (b) responsive to a match on the associated match type condition in the second metadata tag associated with a given second type of content for applying the second compression routine to the given second type of content;

wherein the given first content type and given second content type comprise content types associated with content that a given participating content provider customer has identified to be delivered over the content delivery network.

9. In the CDN edge server as described in claim 8 wherein the given first type of content is a piece of content that is stored in the cache following compression by the first compression routine.

10. In the CDN edge server as described in claim 9 wherein the HTTP client side request handling routine retrieves the piece of content from the cache and serves the piece of content in compressed form in response to an HTTP request.

11. In the CDN edge server as described in claim 8 wherein the client side HTTP request handling routine retrieves a piece of content from the cache and serves the piece of content in response to an HTTP request following application of the second compression routine.

12. In the CDN edge server as described in claim 8 wherein the first and second compression routines are gzip.