Partial object distribution in content delivery network

• US 8,463,876 B2
• Filed: 08/01/2012
• Issued: 06/11/2013
• Est. Priority Date: 04/07/2010
• Status: Active Grant

• Current Assignee: Limelight, Inc.
• Original Assignee: Limelight, Inc.
• Inventors: Raciborski, Nathan F., Swanson, Wylie, Roersma, Jacob S., Black, Bryan D., Tobey, Albert P.
• Primary Examiner(s): Patel, Chirag R
• Application Number:
  US13/564,387
• Publication Number:
  US 20120297033A1
• Time in Patent Office: 314 Days
• Field of Search: 709217-219, 709231-233
• US Class Current: 709/219
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

Techniques for the distribution of content objects in a content delivery network (CDN) are disclosed. A CDN distribution server detects a content object'"'"'s availability and determines whether the content object is a candidate for distribution. The distribution server detects the availability of the content object in response to a provider making new or updated content available at a content site or a location within the CDN. The distribution server obtains identifying information for a candidate content object and determines a select portion of the content object to be distributed within the CDN. The select portion can be a predetermined number of bytes located at a predetermined position in the content object, the size and location of which may be determined according to content-specific mapping data. The distribution server pushes the select portion of the content object to one or more groups of CDN edge servers absent an end-user request.

Claims

1. A method of distributing partial content objects in a content delivery network (CDN), the method comprising:

receiving at a distribution server an indication that a content object is available at a first point of presence;

determining whether the content object is a candidate for distribution;

upon determining that the content object is a candidate for distribution;

determining a select portion of the content object to be distributed;

retrieving the select portion of the content object, the select portion including at least one of information indicative of a content type associated with the content object, or information used by an end user system to prepare to playback the content object;

selecting a plurality of edge servers to receive the select portion of the content object, the plurality of edge servers being selected based on a property of the content object, a usage property of the CDN and/or a property of a target customer;

not in response to an end user request for the content object, sending the select portion of the content object to the plurality of edge servers;

receiving a request from an end-user device for the content object;

assigning the request to one of the plurality of edge server; and

sending the select portion of the content object to the end-user device.

2. The method of claim 1, wherein the plurality of edge servers being selected based on a type of the content object, a category of the content object, a customer agreement, a target computing platform and/or demand levels.

3. The method of claim 1, wherein the select portion of the content object further comprises an identifier uniquely associated with the select portion.

4. The method of claim 1, further comprising:

receiving a second request from a second end-user device for the content object;

assigning the second request to another edge server, the plurality of edge servers not including the another edge server; and

receiving an event from the another edge server indicating that a partial content object associated with a content object requested by the second end-user device is not available at the another edge server; and

determining partial content objects stored at least one of the plurality of edge servers.

5. The method of claim 1, wherein obtaining information relating to the content object comprises obtaining metadata for the content object.

6. The method of claim 1, wherein the select portion of the content object comprises between one and ten data bytes of the content object.

7. The method of claim 1, further comprising:

detecting that an edge server lacks a portion of a second content object that is a candidate for positioning;

obtaining the portion of the second content object at the distribution server; and

sending the portion of the second content object from the distribution server to the edge server.

8. The method of claim 7, wherein detecting that the edge server lacks a portion of a second content object comprises:

requesting a sequence identifier from each edge server in the plurality of edge servers; and

comparing the sequence identifiers to an index of candidate content objects at the distribution server.

9. The method of claim 7, wherein detecting that the edge server lacks a portion of a second content object is responsive to receiving a cache-miss event message generated by the edge server.

10. A content distribution server, comprising:

a messaging subsystem configured to receive event messages and to communicate with a plurality of edge servers over a CDN;

one or more processors configured to distribute content objects, wherein distributing content objects comprises;

determining whether the content object is a candidate for positioning at edge servers of the CDN,

determining a select portion of the content object to be distributed;

obtaining the select portion of the content object, the select portion including at least one of information indicative of a content type associated with the content object, or information used by an end user system to prepare to playback the content object,

selecting a plurality of edge servers to receive the select portion of the content object, the plurality of edge servers being selected based on a property of the content object, a usage property of the CDN and/or a property of a target customer, and

not in response to an end user request for the content object, sending the select portion of the content object to the at least two edge servers.

11. The distribution server of claim 10, wherein the plurality of edge servers are selected based on a type of the content object, a category of the content object, a customer agreement, a target computing platform and/or demand levels.

12. The distribution server of claim 10, wherein distributing content objects further comprising:

assigning a request from an end-user device for the content object to an edge server; and

sending the select portion of the content object to the end-user device via one of the plurality of edge servers.

13. The distribution server of claim 12, wherein the edge server and the one of the plurality of edge servers are the same server.

14. The distribution server of claim 12, wherein the assigning is based at least partly on deriving a path from the user'"'"'s request.

15. The distribution server of claim 10, wherein the memory is configured to store content provider information, and wherein determining whether the content object is a candidate for positioning is based on the content provider information.

16. A content delivery system (CDS), comprising:

a distribution server, comprising;

a messaging interface configured to detect the availability of a content object independent of a request for delivery of the content object,

an object analyzer configured to;

determine whether the content object is a candidate for positioning,

determine a select portion of the content object, and

retrieve a portion of the content object in response to a determination that the content object is a candidate for positioning, the portion of the content object including at least one of information indicative of a content type associated with the content object, or information used by an end user system to prepare to playback of the content object, and

an edge-server group manager configured to determine a group of edge servers to receive the portion of the content object and, absent a request for the content object to send the portion of the content object to the group in a manner that is asynchronous to the operation of the messaging interface;

one or more request routers configured to route a request to a point of presence and to assign the request to one of a plurality of edge servers at the point of presence; and

a plurality of edge servers arranged into an edge-server group, each edge server in the group comprising;

a CDS interface configured to receive a message with the portion of the content object from the distribution server,

a byte store configured to store partial content objects at the edge server, said partial content objects comprising a number of bytes that varies according to a type of a corresponding full content object,

a request interface configured to receive a content request and to send a content object to an end user computer in response to said content object request, and

a storage controller configured to store the portion of the content object received from the distribution server in the byte store and to retrieve data from the byte store in response to receiving the content request after pre-population of the byte store.

17. The CDS of claim 16, wherein the group of edge servers is determined based on a type of the content object, a category of the content object, a customer agreement, a target computing platform and/or demand levels.

18. The CDS of claim 16, wherein the storage controller is configured to generate a CDS event if it is determined that the byte store does not contain a partial content object associated with the content request.

19. The CDS of claim 16, wherein the message that the CDS interface is configured to receive is a group message.

20. The CDS of claim 16, wherein the portion of the content object further comprises an identifier uniquely associated with the portion.