# US 10,454,985 B2 · File format based streaming with dash formats based on LCT > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,454,985 B2 - Document ID: US10454985B2 - Status: Granted - Kind: B2 - Application number: 15/058,963 - Filed: 2016-03-02 - Published: 2016-09-08 - Granted: 2019-10-22 - Earliest claimed: 2015-03-04 - Assignees: QUALCOMM Incorporated - Applicants: QUALCOMM Incorporated - Inventors: Thomas Stockhammer; Gordon Kent Walker; Ye-Kui Wang - Web page: https://patentgrep.com/patent/US10454985B2 ## CPC - H04L 65/764: {at the destination (reformatting of additional data in video clients H04N21/4355)} - H04L 65/61: for supporting one-way streaming services, e.g. Internet radio - H04L 65/612: for unicast - H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP] - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04N 21/23439: {for generating different versions} - H04N 21/26258: {for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list (retrieval of multimedia data based on playlists G06F16/40)} - H04N 21/6131: {involving transmission via a mobile phone network (wireless downlink channel access H04W74/006)} - H04N 21/8456: {by decomposing the content in the time domain, e.g. in time segments} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION ## Abstract In one example, a device includes 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), the LSID including information representing a plurality of LCT sessions, each of the LCT sessions including data of a respective one of a plurality of representations of a 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. ## Claims ### 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; initiating consumption of one or more of the representations of the DASH media presentation based on: 1) using the LSID and 2) without using a manifest file to generate a request for a portion of data of the one or more representations of the DASH media presentation, wherein the initiating consumption comprises: receiving a first set of data including packets of the LCT sessions including the portion of the data of the one or more of the representations up to a first playback time; and providing data of the packets to a media decoder; after receiving the first set of data, 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 2 (depends on 1) 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 (depends on 2) 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 (depends on 1) The method of claim 1, further comprising using the manifest file to combine broadcast and unicast delivery of data of the DASH media presentation. ### Claim 5 (depends on 1) The method of claim 1, 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 6 (depends on 1) The method of claim 1, further comprising receiving data indicative of target transmission times in the packets of the LCT sessions. ### Claim 7 (depends on 6) The method of claim 6, 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 8 (depends on 6) The method of claim 6, 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 9 (depends on 6) The method of claim 6, 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 10 (depends on 1) 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 11 (depends on 10) The method of claim 10, 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 12 (depends on 1) 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 13 (depends on 1) 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 14 (depends on 1) 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 15 (depends on 1) 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 16 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 based on: 1) use of the LSID and 2) without use of a manifest file to generate a request for a portion of data of the one or more representations of the DASH media presentation, wherein to initiate consumption, the processor is configured to: receive, via the network interface, a first set of data including packets of the LCT sessions including the portion of the data of the one or more of the representations up to a first playback time; and provide data of the packets to the one or more media decoders; after receiving the first set of data, receive the manifest file; and receive 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 17 (depends on 11) The device of claim 11, 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 18 (depends on 11) The device of claim 11, 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 19 (depends on 11) The device of claim 11, 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 20 (depends on 19) The device of claim 19, 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 21 (depends on 11) The device of claim 11, 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 22 (depends on 11) The device of claim 11, 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 23 (depends on 11) The device of claim 11, 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 24 (depends on 11) The device of claim 11, wherein the device comprises at least one of: an integrated circuit; a microprocessor; or a wireless communication device. ### Claim 25 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; means for initiating consumption of one or more of the representations of the DASH media presentation based on 1) use of the LSID and 2) without use of a manifest file to generate a request for a portion of data of the one or more representations of the DASH media presentation, wherein the means for initiating consumption comprises: means for receiving a first set of data including packets of the LCT sessions including the portion of the data of the one or more of the representations up to a first playback time; and means for providing data of the packets to a media decoder; means for receiving the manifest file after receiving the first set of data; and means for 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 26 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; initiate consumption of one or more of the representations of the DASH media presentation based on: 1 use of the LSID and 2) without use of a manifest file to generate a request for a portion of data of the one or more representations of the DASH media presentation, wherein the instructions that cause the processor to initiate consumption comprise instructions that cause the processor to: receive a first set of data including packets of the LCT sessions including the portion of the data of the one or more of the representations up to a first playback time; and provide data of the packets to a media decoder; after receiving the first set of data, receive the manifest file; and receive 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 27 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; outputting, without reception of a request for data of the representations that is based on a manifest file, a first set of data including the data of the representations in the corresponding LCT sessions up to a first playback time; after outputting the first set of data, outputting the manifest file; and outputting a second set of data, different from the first set of data, of the DASH media presentation in response to one or more requests based on the manifest file, the second set of data having playback times following the first playback time. ### Claim 28 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; output, without reception of a request for data of the representations that is based on a manifest file, a first set of data including the data of the representations in the corresponding LCT sessions via the network interface up to a first playback time; after outputting the first set of data, output the manifest file; and output a second set of data, different from the first set of data, of the DASH media presentation in response to one or more requests based on the manifest file, the second set of data having playback times following the first playback time. ### Claim 29 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; means for outputting, without reception of a request for data of the representations that is based on a manifest file, a first set of data including the data of the representations in the corresponding LCT sessions up to a first playback time; means for outputting the manifest file after outputting the first set of data; and means for outputting a second set of data, different from the first set of data, of the DASH media presentation in response to one or more requests based on the manifest file, the second set of data having playback times following the first playback time. ### Claim 30 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; output, without reception of a request for data of the representations that is based on a manifest file, the data of the representations in the corresponding LCT sessions; after outputting the first set of data, output the manifest file; and output a second set of data, different from the first set of data, of the DASH media presentation in response to one or more requests based on the manifest file, the second set of data having playback times following the first playback time.