Distributed origin content delivery network

• US 8,533,280 B1
• Filed: 05/02/2008
• Issued: 09/10/2013
• Est. Priority Date: 05/02/2008
• Status: Active Grant

• Current Assignee: TATA Communications Limited (Tata Sons Pvt Ltd.)
• Original Assignee: Juniper Networks Incorporated, Bitgravity Incorporated (Tata Sons Pvt Ltd.)
• Inventors: Lyon, Barrett Gibson, Clarke, Donald Peregrine, Crump, Edward Deitz
• Primary Examiner(s): Ashraf, Waseem
• Application Number:
  US12/151,133
• Time in Patent Office: 1,957 Days
• Field of Search: 709/207, 709223-224
• US Class Current: 709/207
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

Updating a node of a content delivery network is disclosed. In some embodiments, an indication of an event associated with a piece of content, which event is associated with a change in a corpus of content associated with a content delivery network, is received at a node of the content delivery network; and in response to the received indication, an action is performed at the node, if applicable, such that at least a portion of the corpus of content associated with the content delivery network stored at the node is updated based on the event.

Claims

1. A method for updating a plurality of nodes of a content delivery network, comprising:

configuring a node of the plurality of nodes of the content delivery network that hosts a corpus of content to store the corpus of content;

receiving, at the node of the plurality of nodes, a notification of an event associated with a piece of content at the node of the plurality of nodes, wherein the event is associated with a change in the corpus of content;

transmitting, to at least one other node of the plurality of nodes, the notification of the event, wherein the at least one other node of the plurality of nodes is at least a predetermined number of hops away from the node of plurality of nodes;

adding, at the at least one other node of the plurality of nodes, the notification of the event to a queue that at least in part may control the order in which notifications are processed at the at least one other node of the plurality of nodes;

determining, at the at least one other node of the plurality of nodes, whether the notification is associated with a previously received notification of an in-progress event;

performing, based at least in part on the determination, an action at the at least one other node of the plurality of nodes in response to the notification, if applicable, such that the corpus of content stored at the at least one node of the plurality of nodes is updated based on the event;

cancelling the in-progress event at the at least one other node of the plurality of nodes which is associated with the previously received notification, when the notification contradicts the previously received notification; and

continuing the in-progress event at the at least one other node of the plurality of nodes which is associated with the previously received notification, and delaying the event associated with the notification, when the notification does not contradict the previously received notification.

2. The method as recited in claim 1, wherein the notification is received from a node of the plurality of nodes at which the event originally occurred.

3. The method as recited in claim 1, wherein the notification is received from a neighboring node of the at least one other node of the plurality of nodes.

4. The method as recited in claim 1, wherein the event associated with a piece of content comprises an add event associated with a file.

5. The method as recited in claim 4, wherein the action comprises requesting and receiving the file from a node of the plurality of nodes from which the notification is received.

6. The method as recited in claim 4, wherein the notification is received in response to the file being uploaded to the node of the plurality of nodes.

7. The method as recited in claim 1, wherein the event associated with a piece of content comprises a delete event associated with a file.

8. The method as recited in claim 7, wherein the action comprises deleting the file at the at least one other node of the plurality of nodes.

9. The method as recited in claim 1, wherein the event associated with a piece of content comprises a change event associated with a file.

10. The method as recited in claim 9, wherein the action comprises changing the file as specified by the change event at the at least one other node of the plurality of nodes.

11. The method as recited in claim 1, wherein the event associated with a piece of content comprises a rename event associated with a file.

12. The method as recited in claim 11, wherein the action comprises renaming the file at the at least one other node of the plurality of nodes.

13. The method as recited in claim 1, wherein a subset of nodes of the plurality of nodes comprising the content delivery network each comprises a cache node.

14. The method as recited in claim 1, wherein at least notifications of changes in the corpus of content are pushed to the plurality of nodes comprising the content delivery network.

15. The method as recited in claim 1, wherein the piece of content is a first piece of content and further comprising receiving a request for a second piece of content at the node of the plurality of nodes.

16. The method as recited in claim 15, further comprising providing the second piece of content to the requestor if the second piece of content is locally available at the node of the plurality of nodes.

17. The method as recited in claim 15, further comprising redirecting the requestor to a different node of the plurality of nodes if the second piece of content is not yet available at the node of the plurality of nodes.

18. The method as recited in claim 15, further comprising proxying the second piece of content from another node of the plurality of nodes if the second piece of content is not yet available at the node of the plurality of nodes.

19. The method as recited in claim 15, wherein the second piece of content comprises the first piece of content.

22. The method as recited in claim 1,

wherein the in-progress event is an add event or a change event.

23. The method as recited in claim 1, wherein each node of the plurality of nodes of the content delivery network stores the corpus of content.

20. A content delivery network, comprising:

a node and at least one other node;

the node of a content delivery network that hosts a corpus of content comprising;

a processor and a memory coupled to the processor configured to provide the processor with instructions to;

store the corpus of content,

receive a notification of an event associated with a piece of content, wherein the event is associated with a change in the corpus of content,

transmit, to the at least one other node of the content delivery network, the notification of the event, wherein the at least one other node is at least a predetermined number of hops away from the node;

the at least one other node comprising;

a processor and a memory coupled to the processor configured to provide the processor with instructions to;

add the notification of the event to a queue that at least in part may control the order in which notifications are processed at the at least one other node of the content delivery network,

determine whether the notification is associated with a previously received notification of an in-progress event,

perform based at least in part on the determination an action in response to the notification, if applicable, such that the corpus of content stored at the at least one other node is updated based on the event,

cancel the in-progress event at the at least one other node which is associated with the previously received notification, when the notification contradicts the previously received notification, and

continue the in-progress event at the at least one other node which is associated with the previously received notification, and delaying the event associated with the notification, when the notification does not contradict the previously received notification.

21. A computer program product for updating a plurality of nodes of a content delivery network, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

storing, at a node of the plurality of nodes, a corpus of content associated with the content delivery network;

receiving, at the node of the plurality of nodes, a notification of an event associated with a piece of content at the node of the plurality of nodes, wherein the event is associated with a change in the corpus of content;

transmitting, to at least one other node of the plurality of nodes, the notification of the event, wherein the at least one other node of the plurality of nodes is at least a predetermined number of hops away from the node of the plurality of nodes;

adding, at the at least one other node of the plurality of nodes, the notification of the event to a queue that at least in part may control the order in which notifications are processed at the at least one other node of the plurality of nodes;

determining, at the at least one other node of the plurality of nodes, whether the notification is associated with a previously received notification of an in-progress event; and

performing, based at least in part on the determination, an action at the at least one other node of the plurality of nodes in response to the notification, if applicable, such that the corpus of content stored at the at least one other node of the plurality of nodes is updated based on the event;

cancelling the in-progress event at the at least one other node of the plurality of nodes which is associated with the previously received notification, when the notification contradicts the previously received notification; and

continuing the in-progress event at the at least one other node of the plurality of nodes which is associated with the previously received notification, and delaying the event associated with the notification, when the notification does not contradict the previously received notification.