Abstract:
In one example, a device for retrieving audio data includes one or more processors configured to receive availability data representative of a plurality of available adaptation sets, the available adaptation sets including a scene-based audio adaptation set and one or more object-based audio adaptation sets, receive selection data identifying which of the scene-based audio adaptation set and the one or more object-based audio adaptation sets are to be retrieved, and provide instruction data to a streaming client to cause the streaming client to retrieve data for each of the adaptation sets identified by the selection data, and a memory configured to store the retrieved data for the audio adaptation sets.
Abstract:
Various embodiments enable “bundled FEC protection,” in which a single repair flow may be used to provide recovery protection for a plurality of individual source RTP streams. The embodiment techniques may utilize novel FEC source payload and repair payload definitions that enable a single repair flow to be defined for multiple RTP flows. For example, as FEC FRAME Raptor code options do not currently address the case of bundled protection of multiple media types over multiple real-time transport protocol (RTP) synchronization sources (SSRC's), RTP stream header extensions may be utilized to allow a single FEC RTP stream to be configured to provide redundancy for a plurality of source RTP streams, regardless of their content type (e.g., audio or video). Based on such extensions, the embodiment techniques allow for protection of multiple source RTP streams that each has a unique sequence number space.
Abstract:
Systems, methods, and devices of the various embodiments enable objects associated with a service available in a MBMS network to be delivered through more than one delivery method or context. In various embodiments, an application service document may map objects of a service to their respective delivery methods or contexts. In an embodiment, an application service document may also identify service area restrictions applicable to an object. In an embodiment, an application service document may further identify group restrictions applicable to an object. In a further embodiment, the application service document may identify identical and alternative objects that are available.
Abstract:
Systems, methods, and devices of the various embodiments enable HTTP servers, such as HTTP servers providing segments to DASH clients according to the various embodiments, to pass incomplete versions of segments in response to segment requests from the DASH clients. The various embodiments may enable clients, such as DASH clients, to parse incomplete versions of segments.
Abstract:
Systems, methods, and devices of the various embodiments enable HTTP servers, such as HTTP servers providing segments to DASH clients according to the various embodiments, to pass incomplete versions of segments in response to segment requests from the DASH clients. The various embodiments may enable clients, such as DASH clients, to parse incomplete versions of segments.
Abstract:
Systems, methods, and devices of the various embodiments enable managing a start time of media content in a media receiver device. A processor of the receiver device may receive media content labeled with a transmission time from a sending device. The processor may determine a service construction delay of the media content of the media content. The processor may determine a time offset of the media content based on the service construction delay. The processor may deliver the media content to a streaming media client in the receiver device using the time offset.
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:
Embodiments enable HTTP servers to pass incomplete and/or corrupted files in response to file requests from clients. In the various embodiments, HTTP servers may be enabled to generate status codes identifying that an incomplete version of a file is being returned in response to a file request. In an embodiment, an HTTP server may be enabled to determine the ability of a client to handle incomplete versions of files.
Abstract:
Techniques are provided for receiving one or more representations of content wirelessly. The method may involve receiving a media presentation description (MPD) that includes parameters for reception of data segments for multiple representations of content via broadcast transmission and unicast transmission. The method may involve determining whether the broadcast transmission or the unicast transmission is appropriate for reception of the data segments, and selecting a given representation from among the multiple representations of the content based on a criteria of the mobile entity. The method may involve receiving the data segments for the given representation based at least in part on the parameters for the determined one of the broadcast transmission and the unicast transmission.
Abstract:
A client device (e.g., user equipment or “UE”) may be configured to engage in a media communication session, such as a WebRTC session, with another client device. The client devices may separate a quality of service (QoS) specification from a QoS flow definition, to allow for separate interactive connectivity establishment (ICE) negotiation. The QoS specification may cover all segments of a connection for the media communication session. For example, QoS may be requested for a case where a server (e.g., a Traversal Using Relay Network Address Translation (TURN) server) is hosted by a mobile network operator (MNO). The QoS specification and the QoS flow description may be linked.