Abstract: Data can be sent from a sender to a receiver with reliability of transmission encoding data blocks into packets each having a packet header and a packet payload, a block size, a global packet sequence number that uniquely identifies the packet relative to other packets of the data, a block identifier of the data block, and an encoding identifier. The sender determines from feedback from the receiver whether packets are lost and sends repair packets as needed.

Abstract: A block-request streaming system provides for improvements in the user experience and bandwidth efficiency of such systems, typically using an ingestion system that generates data in a form to be served by a conventional file server (HTTP, FTP, or the like), wherein the ingestion system intakes content and prepares it as files or data elements to be served by the file server. A client device can be adapted to take advantage of the ingestion process. The client device might be configured to optimize use of resources, given the information available to it from the ingestion system. This may include configurations to determine the sequence, timing and construction of block requests based on monitoring buffer size and rate of change of buffer size, use of variable sized requests, mapping of block requests to underlying transport connections, flexible pipelining of requests, and/or use of whole file requests based on statistical considerations.

Abstract: Data can be sent from a sender to a receiver with reliability of transmission encoding data blocks into packets each having a packet header and a packet payload, a block size, a global packet sequence number that uniquely identifies the packet relative to other packets of the data, a block identifier of the data block, and an encoding identifier. The sender determines from feedback from the receiver whether packets are lost and sends repair packets as needed.

Abstract: A block-request streaming system provides for low-latency streaming of a media presentation. A plurality of media segments are generated according to an encoding protocol. Each media segment includes a random access point. A plurality of media fragments are encoded according to the same protocol. The media segments are aggregated from a plurality of media fragments.

Abstract: Systems and methods providing for storing fragments for one or more source objects at storage nodes of multiple cluster instances comprising a cluster set are disclosed. Repair of the stored data is operated within cluster instances autonomously or semi-autonomously of other cluster instances of the cluster set according to embodiments. Embodiments may provide a storage process operable to generate fragments for a first source object to be stored in a storage system using a first encoding, wherein a different plurality of fragments of the generated fragments are stored at different cluster instances of a cluster set. A repair process may be enacted at each cluster instance of the cluster set, wherein a repair process enacted at a cluster instance is used to maintain the recoverability of the fragments of the first source object stored at that cluster instance using a second encoding.

Abstract: An over-the-air (OTA) broadcast middleware unit is configured to receive aggregated session description data for a plurality of sessions, wherein each of the sessions transports media data related to common media content, and wherein each of the sessions is transmitted as part of an OTA broadcast, and extract at least some of the media data from the OTA broadcast based on the aggregated session description data. The OTA broadcast middleware unit may further deliver the extracted media data to a streaming client, such as a Dynamic Adaptive Streaming over HTTP (DASH) client.

Abstract: Systems and methods which implement repair bandwidth control techniques, such as may provide a feedback control structure for regulating repair bandwidth in the storage system. Embodiments control a source object repair rate in a storage system by analyzing source objects represented in a repair queue to determine repair rate metrics for the source objects and determining a repair rate based on the repair rate metrics to provide a determined level of recovery of source data stored as by the source objects and to provide a determined level of repair efficiency in the storage system. For example, embodiments may determine a per storage object repair rate (e.g., a repair rate preference for each of a plurality of source objects) and select a particular repair rate (e.g., a maximum repair rate) for use by a repair policy. Thereafter, the repair policy of embodiments may implement repair of one or more source objects in accordance with the repair rate.

Abstract: Systems and methods utilizing available storage space within a storage system (e.g., as “supplemental” storage) and/or implement less physical storage space in the storage system (e.g., reduced storage overhead) through operation of fragment pre-storage techniques are disclosed. Such fragment pre-storage utilization of the aforementioned available storage space may provide operation emulating larger storage overhead than is actually provided in the storage system, facilitate improved repair rates, and/or facilitate reduced repair bandwidth in the storage system according to embodiments. A fragment pre-storage repair policy may implement source object repair whereby additional fragments for the source object are pre-generated and pre-stored in the storage system as transient fragments, whereby the transient fragments are moved to corresponding storage nodes when those storage nodes become physically present in the storage system.

Abstract: Systems and methods which implement one or more data organization techniques that facilitate efficient access to source data stored by a storage system are disclosed. Data organization techniques implemented according to embodiments are adapted to optimize (e.g., maximize) input/output efficiency and/or (e.g., minimize) storage overhead, while maintaining mean time to data loss, repair efficiency, and/or traffic efficiency. Data organization techniques as may be implemented by embodiments include blob based organization techniques, grouped symbols organization techniques, data ordering organization techniques, and combinations thereof.

Abstract: Systems and methods which implement forward checking of data integrity are disclosed. A storage system of embodiments may, for example, comprise data integrity forward checking logic which is operable to perform forward checking of data integrity in real-time or near real-time to check that a number of node failures can be tolerated without loss of data. Embodiments may be utilized to provide assurance that a number of fragments needed for source data recovery will be available for the source objects most susceptible to failure when a certain number of additional fragments are lost, such as due to storage node failures.

Abstract: Content (e.g., multimedia streams, audio-video streams, video files, text, etc.) may be delivered to receiver devices over a broadcast channel and/or via a broadcast network via components (e.g., servers, receiver device, software applications, modules, processes, etc.) configured to communicate the content in a manner that reduces the amount of information communicated over the broadcast network, reduces the amount network bandwidth consumed by the communication, meets precise timing requirements for the individual objects that are communicated, and enables each receiver device to receive, decode, and render the content without consuming an excess amount of that receiver device's battery or processing resources.

Abstract: Systems and methods which implement one or more data organization techniques that facilitate efficient access to source data stored by a storage system are disclosed. Data organization techniques implemented according to embodiments are adapted to optimize (e.g., maximize) input/output efficiency and/or (e.g., minimize) storage overhead, while maintaining mean time to data loss, repair efficiency, and/or traffic efficiency. Data organization techniques as may be implemented by embodiments include blob based organization techniques, grouped symbols organization techniques, data ordering organization techniques, and combinations thereof.

Abstract: Content (e.g., multimedia streams, audio-video streams, video files, text, etc.) may be delivered to receiver devices over a broadcast channel and/or via a broadcast network via components (e.g., servers, receiver device, software applications, modules, processes, etc.) configured to communicate the content in a manner that reduces the amount of information communicated over the broadcast network, reduces the amount network bandwidth consumed by the communication, meets precise timing requirements for the individual objects that are communicated, and enables each receiver device to receive, decode, and render the content without consuming an excess amount of that receiver device's battery or processing resources.

Abstract: Systems and methods providing for storing fragments for one or more source objects at storage nodes of multiple cluster instances comprising a cluster set are disclosed. Repair of the stored data is operated within cluster instances autonomously or semi-autonomously of other cluster instances of the cluster set according to embodiments. Embodiments may provide a storage process operable to generate fragments for a first source object to be stored in a storage system using a first encoding, wherein a different plurality of fragments of the generated fragments are stored at different cluster instances of a cluster set. A repair process may be enacted at each cluster instance of the cluster set, wherein a repair process enacted at a cluster instance is used to maintain the recoverability of the fragments of the first source object stored at that cluster instance using a second encoding.

Abstract: Transport accelerator (TA) systems and methods for accelerating delivery of content to a user agent (UA) of a client device are provided according to embodiments of the present disclosure. Embodiments comprise a TA architecture implementing a connection manager (CM) and a request manager (RM). A CM of embodiments requests chunks of content from a content server, receives data in response to requesting the chunks of content, wherein the received data is missing data from a requested chunk of content, and provides a receipt acknowledgement (ACK) for the missing data. The received data, which is missing data from a requested chunk of the chunks of content, may be passed through a communication protocol stack to an application for assembly into a one or more content objects.

Abstract: Systems and methods which are adapted to provide transport accelerator operation through the use of user agent (UA) signaling are disclosed. In operation according to embodiments, a transport accelerator (TA) analyzes content requests to determine if the content request includes an indication that transport acceleration functionality is to be provided. If such an indication is present, the TA further analyzes the content request to determine if transport acceleration functionality will be provided.

Abstract: Embodiments provide methodologies for reliably storing data within a storage system using liquid distributed storage control. Such liquid distributed storage control operates to compress repair bandwidth utilized within a storage system for data repair processing to the point of operating in a liquid regime. Liquid distributed storage control logic of embodiments may employ a lazy repair policy, repair bandwidth control, a large erasure code, and/or a repair queue. Embodiments of liquid distributed storage control logic may additionally or alternatively implement a data organization adapted to allow the repair policy to avoid handling large objects, instead streaming data into the storage nodes at a very fine granularity.

Abstract: Systems and methods utilizing available storage space within a storage system (e.g., as “supplemental” storage) and/or implement less physical storage space in the storage system (e.g., reduced storage overhead) through operation of fragment pre-storage techniques are disclosed. Such fragment pre-storage utilization of the aforementioned available storage space may provide operation emulating larger storage overhead than is actually provided in the storage system, facilitate improved repair rates, and/or facilitate reduced repair bandwidth in the storage system according to embodiments. A fragment pre-storage repair policy may implement source object repair whereby additional fragments for the source object are pre-generated and pre-stored in the storage system as transient fragments, whereby the transient fragments are moved to corresponding storage nodes when those storage nodes become physically present in the storage system.

Abstract: Embodiments providing co-derived data storage patterns for use in reliably storing data and/or facilitating access to data within a storage system using fragments of source objects are disclosed. A set of data storage patterns for use in storing the fragments distributed across a plurality of storage nodes may be generated whereby the set of data storage patterns are considered collectively to meet one or more system performance goals. Such co-derived data storage pattern sets may be utilized when storing fragments of a source object to storage nodes of a storage system. Co-derived pattern set management logic may generate co-derived data storage pattern sets, select/assign data storage patterns of a co-derived data storage pattern set for use with respect to source objects, modify data storage patterns of a co-derived data storage pattern set, and generate additional data storage patterns for a co-derived data storage pattern set in accordance with the concepts herein.

Abstract: Embodiments provide methodologies for reliably storing data within a storage system using liquid distributed storage control. Such liquid distributed storage control operates to compress repair bandwidth utilized within a storage system for data repair processing to the point of operating in a liquid regime. Liquid distributed storage control logic of embodiments may employ a lazy repair policy, repair bandwidth control, a large erasure code, and/or a repair queue. Embodiments of liquid distributed storage control logic may additionally or alternatively implement a data organization adapted to allow the repair policy to avoid handling large objects, instead streaming data into the storage nodes at a very fine granularity.