Method and apparatus for a fault resilient collaborative media serving array
First Claim
Patent Images
1. A method for recovering from fault in a content serving array comprising at least a first node, a second node, and a third node, the method comprising:
- partitioning content into an ordered list of parts comprising at least a first part and a second part;
allocating the first part to the first node;
allocating the second part to the second node;
sending the content successively and chronologically in-order as an ordered stream of parts corresponding to the ordered list by;
indicating to the first node that it should send the first part to a client device;
failing to receive by the second node an indication that the first node has sent the first part to the client device;
indicating to the third node that it should send the first part to the client device;
sending by the third node the first part to the client device; and
sending by the second node the second part to the client device.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments of the present invention provide methods, systems, and apparatuses for a fault resilient collaborative media serving array comprising a plurality of nodes. In one embodiment, the present invention provides a method for creating a fault resilient collaborative media serving array where the array nodes do not share memory, the serving of a content file is accomplished by the collaborative efforts of many nodes in the array, and where there is no fixed allocation of sessions to nodes.
85 Citations
17 Claims
-
1. A method for recovering from fault in a content serving array comprising at least a first node, a second node, and a third node, the method comprising:
-
partitioning content into an ordered list of parts comprising at least a first part and a second part; allocating the first part to the first node; allocating the second part to the second node; sending the content successively and chronologically in-order as an ordered stream of parts corresponding to the ordered list by; indicating to the first node that it should send the first part to a client device; failing to receive by the second node an indication that the first node has sent the first part to the client device; indicating to the third node that it should send the first part to the client device; sending by the third node the first part to the client device; and sending by the second node the second part to the client device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
Specification