| Sonstiges: |
- Nachgewiesen in: USPTO Patent Applications
- Sprachen: English
- Document Number: 20160261665
- Publication Date: September 8, 2016
- Appl. No: 15/058963
- Application Filed: March 02, 2016
- Claim: 1. A method of receiving media data, the method comprising: determining a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation from a layered coding transport (LCT) Session Instance Description (LSID), wherein the LSID includes information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of the representations; and initiating consumption of one or more of the representations of the DASH media presentation using the LSID and without using a manifest file for the DASH media presentation, wherein the initiating consumption comprises: receiving packets of the LCT sessions including portions of data of the one or more of the representations; and providing data of the packets to a media decoder.
- Claim: 2. The method of claim 1, further comprising: determining at least one of coding characteristics or rendering characteristics of the representations of the DASH media presentation from one or more content descriptors of the LSID; and selecting the one or more of the representations based on the determined coding characteristics or rendering characteristics.
- Claim: 3. The method of claim 2, wherein the one or more coding characteristics or rendering characteristics include one or more of codec, accessibility information, quality, spatial resolution, viewpoint, rating, a profile attribute of an adaptation set, sample aspect ratio, frame rate, audio sampling rate, mime type, scan type, frame packing information, audio channel configuration, content preparation, essential property, supplemental property, or inband event stream.
- Claim: 4. The method of claim 1, wherein initiating consumption comprises receiving a first set of data of the one or more representations up to a first playback time without using the manifest file, the method further comprising: receiving the manifest file; and receiving a second set of data, different from the first set of data, of the DASH media presentation using the manifest file, the second set of data having playback times following the first playback time.
- Claim: 5. The method of claim 4, further comprising using the manifest file to combine broadcast and unicast delivery of data of the DASH media presentation.
- Claim: 6. The method of claim 1, wherein the manifest file comprises a lightweight manifest file that only includes data needed for broadcast tune-in or channel change.
- Claim: 7. The method of claim 6, wherein the DASH media presentation provides a first plurality of lightweight manifest files with a first set of random access points (RAPs) of the DASH media presentation, and a second plurality of full manifest files with a second plurality of RAPs, wherein the second plurality of RAPs is smaller than the first plurality of RAPs.
- Claim: 8. The method of claim 1, further comprising receiving data indicative of target transmission times in the packets of the LCT sessions.
- Claim: 9. The method of claim 8, wherein receiving the data indicative of the target transmission times comprises receiving the data indicative of the target transmission times in congestion control information fields of LCT headers of the packets or header extension fields of the LCT headers.
- Claim: 10. The method of claim 8, wherein the target transmission times are expressed as one of relative times to other packets of the LCT sessions or absolute wall clock times.
- Claim: 11. The method of claim 8, wherein the target transmission times are expressed relative to target transmission times of other packets of the LCT sessions, the method further comprising receiving data indicating release times signaled in at least some of the packets.
- Claim: 12. The method of claim 1, wherein at least one of the one or more representations includes an initialization segment and one or more media segments formatted according to a DASH segment format, and wherein packets comprising data for the initialization segment or the media segments further comprise LCT headers.
- Claim: 13. The method of claim 12, further comprising, for each of the packets, determining, from a codepoint field of the LCT header of the packet: a type for a segment to which the packet corresponds, whether the packet includes a ROUTE header, whether timeline discontinuities can be signaled for the packet, whether the packet corresponds to a redundant initialization segment, and whether the packet corresponds to an auxiliary initialization segment.
- Claim: 14. The method of claim 1, further comprising using transport session identifier (TSI) fields of LCT headers of the packets of the LCT sessions description to determine correspondences between the LCT sessions and the representations.
- Claim: 15. The method of claim 1, further comprising determining release times for data of packets of the LCT sessions from at least one of protocol-specific indication (PSI) bits of LCT headers of the packets or extension headers of the LCT headers of the packets.
- Claim: 16. The method of claim 1, further comprising determining target transmission times for packets of the LCT sessions from congestion control information of LCT headers of the packets.
- Claim: 17. The method of claim 1, further comprising determining sequence numbers for media segments of the DASH media presentation from transport object identifiers (TOIs) signaled in LCT headers of packets of the LCT sessions.
- Claim: 18. A device for receiving media data, the device comprising: one or more media decoders configured to decode media data; a network interface configured to receive a layered coding transport (LCT) Session Instance Description (LSID), wherein the LSID includes information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation and data of one or more of the LCT sessions; and a processor configured to initiate consumption of one or more of the representations of the DASH media presentation using the LSID and without using a manifest file for the DASH media presentation, wherein to initiate consumption, the processor is configured to: receive, via the network interface, packets of the LCT sessions including portions of data of the one or more of the representations; and provide data of the packets to the one or more media decoders.
- Claim: 19. The device of claim 18, wherein the processor is further configured to: determine at least one of coding characteristics or rendering characteristics of the representations of the DASH media presentation from one or more content descriptors of the LSID; and select the one or more of the representations based on the determined coding characteristics or rendering characteristics.
- Claim: 20. The device of claim 18, wherein the processor is further configured to determine target transmission times from the packets of the LCT sessions and to use the target transmission times to provide the data of the packets to the one or more media decoders.
- Claim: 21. The device of claim 18, wherein at least one of the one or more representations includes an initialization segment and one or more media segments formatted according to a DASH segment format, and wherein the packets comprising data for the initialization segment or the media segments further comprise LCT headers.
- Claim: 22. The device of claim 21, wherein the processor is further configured to, for each of the packets, determine, from a codepoint field of the LCT header of the packet: a type for a segment to which the packet corresponds, whether the packet includes a ROUTE header, whether timeline discontinuities can be signaled for the packet, whether the packet corresponds to a redundant initialization segment, and whether the packet corresponds to an auxiliary initialization segment.
- Claim: 23. The device of claim 18, wherein the processor is configured to determine correspondences between the LCT sessions and the representations from transport session identifier (TSI) fields of LCT headers of the packets of the LCT sessions.
- Claim: 24. The device of claim 18, wherein the processor is configured to determine release times for data of packets of the LCT sessions from at least one of protocol-specific indication (PSI) bits of LCT headers of the packets or extension headers of the LCT headers of the packets.
- Claim: 25. The device of claim 18, wherein the processor is configured to determine sequence numbers for media segments of the DASH media presentation from transport object identifiers (TOIs) signaled in LCT headers of packets of the LCT sessions.
- Claim: 26. The device of claim 18, wherein the device comprises at least one of: an integrated circuit; a microprocessor; or a wireless communication device.
- Claim: 27. A device for receiving media data, the device comprising: means for determining a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation from a layered coding transport (LCT) Session Instance Description (LSID), wherein the LSID includes information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of the representations; and means for initiating consumption of one or more of the representations of the DASH media presentation using the LSID and without using a manifest file for the DASH media presentation, wherein the means for initiating consumption comprises: means for receiving packets of the LCT sessions including portions of data of the one or more of the representations; and means for providing data of the packets to a media decoder.
- Claim: 28. A computer-readable storage medium having stored thereon instructions that, when executed, cause a processor of a device for receiving media data to: determine a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation from a layered coding transport (LCT) Session Instance Description (LSID), wherein the LSID includes information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of the representations; and initiate consumption of one or more of the representations of the DASH media presentation using the LSID and without using a manifest file for the DASH media presentation, wherein the instructions that cause the processor to initiate consumption comprise instructions that cause the processor to: receive packets of the LCT sessions including portions of data of the one or more of the representations; and provide data of the packets to a media decoder.
- Claim: 29. A method of sending media data, the method comprising: constructing a layered coding transport (LCT) Session Instance Description (LSID) including information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation, wherein the LSID indicates correspondences between the LCT sessions and the representations; outputting the LSID; and outputting data of the representations in the corresponding LCT sessions.
- Claim: 30. A device for sending media data, the device comprising: a network interface for outputting data of a plurality of layered coding transport (LCT) sessions; and a processor configured to: construct an LCT Session Instance Description (LSID) including information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation, wherein the LSID indicates correspondences between the LCT sessions and the representations; output the LSID via the network interface; and output data of the representations in the corresponding LCT sessions via the network interface.
- Claim: 31. A device for sending media data, the device comprising: means for constructing a layered coding transport (LCT) Session Instance Description (LSID) including information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation, wherein the LSID indicates correspondences between the LCT sessions and the representations; means for outputting the LSID; and means for outputting data of the representations in the corresponding LCT sessions.
- Claim: 32. A computer-readable storage medium having stored thereon instructions that, when executed, cause a processor of a device for sending media data to: construct a layered coding transport (LCT) Session Instance Description (LSID) including information representative of a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a Dynamic Adaptive Streaming over HTTP (DASH) media presentation, wherein the LSID indicates correspondences between the LCT sessions and the representations; output the LSID; and output data of the representations in the corresponding LCT sessions.
- Current International Class: 04; 04
|
