Abstract:
Data objects can be delivered over a network using a file delivery system and universal object delivery and template-based file delivery. This might be done by forming source data into a sequence of data objects represented by symbols in packets, sending those to receivers on request, wherein a transmitter obtains a template file delivery table with delivery metadata for the data objects, and constructing a first transmission object identifier for a data object based on a transmission object identifier construction rule described in the template file delivery table. A receiver might receive packets, extract a second transmission object identifier, associate encoded symbols comprising the received data packet with the data object if the first transmission object identifier and the second transmission object identifier identify the same data object, and recover, at least approximately, the source data for the data object based on the encoded symbols associated with the data object.
Abstract:
Systems, methods, and devices of the various embodiments enable HTTP redirect messages to indicate content access policy information. In this manner, policy rules may be implemented based on the policy information in the HTTP redirect messages to control network congestion and/or quality of service (“QOS”).
Abstract:
Embodiment methods and systems enable completing online transactions when there is insufficiently reliable connectivity between the initiating computing device and the remote server to enable completing the transaction directly. Transactions in such situations are accomplished using a RESTful Delay Tolerant Network. A set of messages constituting the web transaction are bundled, together with instructions and other metadata, in a manner that enables intermediate nodes in the network to complete the transactions on behalf of the source computing device. The source computing device then delegates the web transaction to an intermediate node. If the intermediate node can complete the transaction with the destination device, it does so on behalf of the source computing device. If not, the intermediate node delegates the web transaction to another intermediate node, which may be repeated until an intermediate node is able to complete the transaction with the destination.
Abstract:
Data objects can be delivered over a network using a file delivery system and universal object delivery and template-based file delivery. This might be done by forming source data into a sequence of data objects represented by symbols in packets, sending those to receivers on request, wherein a transmitter obtains a template file delivery table with delivery metadata for the data objects, and constructing a first transmission object identifier for a data object based on a transmission object identifier construction rule described in the template file delivery table. A receiver might receive packets, extract a second transmission object identifier, associate encoded symbols comprising the received data packet with the data object if the first transmission object identifier and the second transmission object identifier identify the same data object, and recover, at least approximately, the source data for the data object based on the encoded symbols associated with the data object.
Abstract:
A client device presents streaming media and includes a stream manager, a request accelerator, and a source component coupled to the stream manager and the request accelerator for determining which requests to make. A rate selection process can make rate decisions so that the buffer is filled when it is low, avoiding erratically changing rates and can choose the correct steady rate quickly. Multimedia download strategies can be used for HTTP that allow for accurate rate estimations, achieving link capacity even if network delays and packet loss rates are high, achieving timely delivery of the stream, and achieving relatively steady download rates with little short term variability. A receiver might use multiple HTTP connections, decompose media requests into smaller chunk requests, synchronize the connections using TCP flow control mechanisms, and request data in bursts. In addition, the receiver might use an HTTP pipelining process to keep the connections busy.