SESSION DESCRIPTION INFORMATION FOR OVER-THE-AIR BROADCAST MEDIA DATA

• US 20160205158A1
• Filed: 01/06/2016
• Published: 07/14/2016
• Est. Priority Date: 01/08/2015
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Lo, Charles Nung, Stockhammer, Thomas, Luby, Michael George, Pazos, Carlos Marcelo Dias, Wang, Jun
• Granted Patent: US 10,129,308 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 1/0045 Arrangements at the receiver end
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 65/00 Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04N 21/2362 Generation or processing of Service Information [SI]
• CPC Class Codes: H04N 21/2381 Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network transmission of MPEG streams over ATM H04L12/5601
• CPC Class Codes: 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
• CPC Class Codes: H04N 21/4433 Implementing client middleware, e.g. Multimedia Home Platform [MHP]
• CPC Class Codes: H04W 4/06 Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

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.

Claims

1. A method of receiving media data, the method comprising, by an over-the-air (OTA) broadcast middleware unit:

receiving 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

extracting at least some of the media data from the OTA broadcast based on the aggregated session description data.

2. The method of claim 1, wherein receiving the aggregated session data comprises receiving the aggregated session description data out of band relative to the media data of the OTA broadcast.

3. The method of claim 1, wherein the aggregated session description data includes extended file delivery table (EFDT) data that includes data of a file delivery table (FDT) as defined in File Delivery over Unidirectional Transport (FLUTE) for each of the plurality of sessions.

4. The method of claim 3, wherein the extended file delivery table (EFDT) includes additional file description parameters not defined in a nominal file delivery table (FDT) as associated with File Delivery over Unidirectional Transport (FLUTE).

5. The method of claim 1, wherein the media data comprises a sequence of media segments formatted according to Dynamic Adaptive Streaming over HTTP (DASH).

6. The method of claim 1, wherein the aggregated session description data comprises a layered coding transport (LCT) Session Instance Description (LSID) fragment.

7. The method of claim 1, wherein receiving the aggregated session description data comprises receiving metadata out of band relative to the plurality of sessions carrying the media data described by the metadata.

8. The method of claim 1,

wherein receiving comprises receiving Fast Information Channel (FIC) data, and

wherein extracting comprises:

determining layered coding transport (LCT) data corresponding to the FIC data, wherein the LCT data is included in the OTA broadcast;

determining service layer signaling (SLS) fragments associated with the LCT data;

determining user service description (USD) data of the SLS fragments;

determining a media presentation description (MPD) corresponding to the USD;

determining representation identification information for requested representations from the MPD;

determining a layered coding transport (LCT) Session Instance Description (LSID) fragment corresponding to the USD;

determining session descriptions for the requested representations from the LSID fragment using the representation identification information; and

extracting media data for the requested representations from the OTA broadcast using the determined session descriptions.

9. The method of claim 1, further comprising:

caching the extracted media data;

receiving requests for the media data in accordance with dynamic adaptive streaming over HTTP (DASH) from a DASH client; and

in response to the requests, sending the requested media data to the DASH client.

10. The method of claim 9, wherein the OTA broadcast middleware unit and the DASH client are included within a common client device.

11. The method of claim 1,

wherein receiving comprises retrieving information from a Lower Layer Signaling (LLS) stream;

and

wherein extracting comprises;

tuning to a service layer signaling (SLS) stream using information from the LLS stream;

retrieving a user service bundle description (USBD) fragment, a layered coding transport (LCT) Session Instance Description (LSID) fragment, a Media Presentation Description (MPD) fragment, and a Schedule fragment from the SLS stream;

selecting service components using the USBD fragment, the LSID fragment, the MPD fragment, and the Schedule fragment;

tuning to the service component streams over respective Real-Time Object Delivery over Unidirectional Transport (ROUTE)/LCT sessions; and

extracting media data from the respective service component streams.

12. The method of claim 1, wherein receiving the aggregated session description data includes:

receiving an identifier element that references a corresponding user service description (USD) element;

receiving one or more broadcast stream identifier elements that identify broadcast streams corresponding to the plurality of sessions;

receiving one or more sender IP address elements that specify IP addresses for senders of the broadcast streams;

receiving one or more destination IP address elements that specify IP addresses for destinations of the broadcast streams;

receiving one or more port elements that specify destination ports for the broadcast streams;

receiving one or more physical layer pipe (PLP) ID elements that specify identifiers for the PLP within the broadcast streams;

receiving one or more transport session identifier (TSI) elements that specify TSIs of associated source or repair flows for the broadcast streams;

receiving one or more bandwidth elements that specify maximum bit-rates for the plurality of sessions;

receiving one or more start time elements that specify start times for the plurality of sessions; and

receiving one or more end time elements that specify end times for the plurality of sessions.

13. The method of claim 12, wherein receiving the aggregated session description data further includes receiving one or more source flow elements, wherein receiving the source flow elements includes:

receiving one or more real time elements each having a binary value for the plurality of sessions; and

when the real time element for one of the plurality of sessions has a value of true, receiving a minimum buffer size element that describes a buffer size for a transport buffer of a receiver of the one of the plurality of sessions.

14. The method of claim 12, wherein receiving the aggregated session description data further includes receiving an extended file delivery table (EFDT) element for one of the plurality of sessions, wherein receiving the EFDT element comprises:

receiving an identifier element specifying an identifier for the EFDT;

receiving a version element specifying a version of the EFDT;

receiving a maxExpiresDelta element specifying a maximum expiry time for an object in the one of the plurality of sessions;

receiving a maxTransportSize element specifying a maximum transport size of any object described by the EFDT; and

receiving a file template element specifying a file uniform resource locator (URL) or a file template for a file of the one of the plurality of sessions.

15. The method of claim 12, wherein receiving the aggregated session description data further includes receiving a payload element, wherein receiving the payload element includes:

receiving a codepoint element specifying a CodePoint value used for the payload element;

receiving a delivery format identifier element specifying a payload format for the payload element;

receiving a fragmentation element having a value indicating arbitrary, application specific (sample based), or application specific (collection of boxes);

receiving a delivery order element having a value indicating arbitrary, in-order delivery, or in-order delivery of media samples and prior to movie fragment box; and

receiving a source forward error correction (FEC) payload identifier element having a value that indicates one of;

a source FEC payload identifier is absent and an entire delivery object is contained in a corresponding packet;

the source FEC payload identifier is a thirty-two bit value and expresses a start offset for the delivery object;

or

that a FEC parameters element defines a format for the source FEC payload identifier.

16. The method of claim 15, further comprising receiving the FEC parameters element that defines parameters of a FEC scheme associated with one of the plurality of sessions.

17. The method of claim 12, wherein receiving the aggregated session description data further includes receiving a repair flow element, wherein receiving the repair flow element comprises:

receiving one or more forward error correction (FEC) parameters, including receiving one or more of;

a maximum delay element specifying a maximum delivery delay between any source packet in a source flow and a corresponding repair flow;

an overhead element specifying overhead as a percentage value;

or

a minimum buffer element specifying a required buffer size;

receiving one or more FEC object transmission information (FECOTI) elements; and

receiving a protected object element that specifies a source flow protected by a repair flow corresponding to the repair flow element.

18. The method of claim 17, wherein receiving the protected object element comprises:

receiving a session description element specifying session description information for the source flow;

receiving a transport session identifier (TSI) element specifying a TSI for the source flow;

receiving a source transmission object identifier (TOI) element specifying a TOI of a delivery object corresponding to a TOI included in the repair flow; and

receiving a FEC transport object size element specifying a default size of each FEC transport object in units of symbols.

19. A device for receiving media data, the device comprising:

an interface configured to receive over-the-air (OTA) broadcast data; and

a processor comprising an OTA broadcast middleware unit configured to;

receive, via the interface, 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.

20. The device of claim 19, wherein the OTA broadcast middleware unit is configured to receive the aggregated session description data out of band relative to the media data of the OTA broadcast.

21. The device of claim 19, wherein the aggregated session description data includes extended file delivery table (EFDT) data that includes data of a file delivery table (FDT) as defined in File Delivery over Unidirectional Transport (FLUTE) for each of the plurality of sessions.

22. The device of claim 19,

wherein the OTA broadcast middleware unit is configured to receive Fast Information Channel (FIC) data of the OTA broadcast, and

wherein to extract the at least some of the media data, the OTA broadcast middleware unit is configured to:

determine layered coding transport (LCT) data corresponding to the FIC data, wherein the LCT data is included in the OTA broadcast;

determine service layer signaling (SLS) fragments associated with the LCT data;

determine user service description (USD) data of the SLS fragments;

determine a media presentation description (MPD) corresponding to the USD;

determine representation identification information for requested representations from the MPD;

determine a layered coding transport (LCT) Session Instance Description (LSID) fragment corresponding to the USD;

determine session descriptions for the requested representations from the LSID fragment using the representation identification information; and

extract media data for the requested representations from the OTA broadcast using the determined session descriptions.

23. The device of claim 19, further comprising a memory configured to cache data;

wherein the OTA broadcast middleware unit is configured to;

cache the extracted media data in the memory;

receive requests for the media data in accordance with dynamic adaptive streaming over HTTP (DASH) from a DASH client; and

in response to the requests, send the requested media data to the DASH client.

24. The device of claim 23, further comprising the DASH client.

25. The device of claim 19,

wherein the OTA middleware unit is configured to retrieve information from a Lower Layer Signaling (LLS) stream of the OTA broadcast;

and

wherein to extract the at least some of the media data, the OTA broadcast middleware unit is configured to;

tune to a service layer signaling (SLS) stream using information from the LLS stream;

retrieve a user service bundle description (USBD) fragment, a layered coding transport (LCT) Session Instance Description (LSID) fragment, a Media Presentation Description (MPD) fragment, and a Schedule fragment from the SLS stream;

select service components using the USBD fragment, the LSID fragment, the MPD fragment, and the Schedule fragment;

tune to the service component streams over respective Real-Time Object Delivery over Unidirectional Transport (ROUTE)/LCT sessions; and

extract media data from the respective service component streams.

26. The device of claim 19, wherein to receive the aggregated session description data and the media content of the broadcast service described by the aggregated session description data, the OTA broadcast middleware unit is configured to:

receive an identifier element that references a corresponding user service description (USD) session identifier element;

receive one or more broadcast stream identifier elements that identify broadcast streams corresponding to the plurality of sessions;

receive one or more sender IP address elements that specify IP addresses for senders of the broadcast streams;

receive one or more destination IP address elements that specify IP addresses for destinations of the broadcast streams;

receive one or more port elements that specify destination ports for the broadcast streams;

receive one or more physical layer pipe (PLP) ID elements that specify identifiers for the PLP within the broadcast streams;

receive one or more transport session identifier (TSI) elements that specify TSIs of associated source or repair flows for the broadcast streams;

receive one or more bandwidth elements that specify maximum bit-rates for the plurality of sessions;

receive one or more start time elements that specify start times for the plurality of sessions; and

receive one or more end time elements that specify end times for the plurality of sessions.

27. A device for receiving media data, the device comprising:

means for receiving 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 over-the-air (OTA) broadcast, and

means for extracting at least some of the media data from the OTA broadcast based on the aggregated session description data.

28. The device of claim 27, wherein the means for receiving the aggregated session data comprises means for receiving the aggregated session description data out of band relative to the media data of the OTA broadcast.

29. The device of claim 27, wherein the aggregated session description data includes extended file delivery table (EFDT) data that includes data of a file delivery table (FDT) as defined in File Delivery over Unidirectional Transport (FLUTE) for each of the plurality of sessions.

30. The device of claim 27,

wherein the means for receiving comprises means for receiving Fast Information Channel (FIC) data, and

wherein the means for extracting comprises:

means for determining layered coding transport (LCT) data corresponding to the FIC data, wherein the LCT data is included in the OTA broadcast;

means for determining service layer signaling (SLS) fragments associated with the LCT data;

means for determining user service description (USD) data of the SLS fragments;

means for determining a media presentation description (MPD) corresponding to the USD;

means for determining representation identification information for requested representations from the MPD;

means for determining a layered coding transport (LCT) Session Instance Description (LSID) fragment corresponding to the USD;

means for determining session descriptions for the requested representations from the LSID fragment using the representation identification information; and

means for extracting media data for the requested representations from the OTA broadcast using the determined session descriptions.

31. The device of claim 27, further comprising:

means for caching the extracted media data;

means for receiving requests for the media data in accordance with dynamic adaptive streaming over HTTP (DASH) from a DASH client; and

means for sending, in response to the requests, the requested media data to the DASH client.

32. The device of claim 31, further comprising the DASH client.

33. The device of claim 27,

wherein the means for receiving comprises means for retrieving information from a Lower Layer Signaling (LLS) stream;

and

wherein the means for extracting comprises;

means for tuning to a service layer signaling (SLS) stream using information from the LLS stream;

means for retrieving a user service bundle description (USBD) fragment, a layered coding transport (LCT) Session Instance Description (LSID) fragment, a Media Presentation Description (MPD) fragment, and a Schedule fragment from the SLS stream;

means for selecting service components using the USBD fragment, the LSID fragment, the MPD fragment, and the Schedule fragment;

means for tuning to the service component streams over respective Real-Time Object Delivery over Unidirectional Transport (ROUTE)/LCT sessions; and

means for extracting media data from the respective service component streams.

34. The device of claim 27, wherein the means for receiving the aggregated session description data includes:

means for receiving an identifier element that references a corresponding user service description (USD) session identifier element;

means for receiving one or more broadcast stream identifier elements that identify broadcast streams corresponding to the plurality of sessions;

means for receiving one or more sender IP address elements that specify IP addresses for senders of the broadcast streams;

means for receiving one or more destination IP address elements that specify IP addresses for destinations of the broadcast streams;

means for receiving one or more port elements that specify destination ports for the broadcast streams;

means for receiving one or more physical layer pipe (PLP) ID elements that specify identifiers for the PLP within the broadcast streams;

means for receiving one or more transport session identifier (TSI) elements that specify TSIs of associated source or repair flows for the broadcast streams;

means for receiving one or more bandwidth elements that specify maximum bit-rates for the plurality of sessions;

means for receiving one or more start time elements that specify start times for the plurality of sessions; and

means for receiving one or more end time elements that specify end times for the plurality of sessions.

35. A non-transitory computer-readable storage medium having stored thereon instructions that, when executed, cause a processor of a device for receiving media data 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 over-the-air (OTA) broadcast, and

extract at least some of the media data from the OTA broadcast based on the aggregated session description data.

36. The non-transitory computer-readable storage medium of claim 35, wherein the instructions that cause the processor to receive the aggregated session data comprise instructions that cause the processor to receive the aggregated session description data out of band relative to the media data of the OTA broadcast.

37. The non-transitory computer-readable storage medium of claim 35, wherein the aggregated session description data includes extended file delivery table (EFDT) data that includes data of a file delivery table (FDT) as defined in File Delivery over Unidirectional Transport (FLUTE) for each of the plurality of sessions.

38. The non-transitory computer-readable storage medium of claim 35,

wherein the instructions that cause the processor to receive comprise instructions that cause the processor to receive Fast Information Channel (FIC) data, and

wherein the instructions that cause the processor to extract comprise instructions that cause the processor to:

determine layered coding transport (LCT) data corresponding to the FIC data, wherein the LCT data is included in the OTA broadcast;

determine service layer signaling (SLS) fragments associated with the LCT data;

determine user service description (USD) data of the SLS fragments;

determine a media presentation description (MPD) corresponding to the USD;

determine representation identification information for requested representations from the MPD;

determine a layered coding transport (LCT) Session Instance Description (LSID) fragment corresponding to the USD;

determine session descriptions for the requested representations from the LSID fragment using the representation identification information; and

extract media data for the requested representations from the OTA broadcast using the determined session descriptions.

39. The non-transitory computer-readable storage medium of claim 35, further comprising instructions that cause the processor to:

cache the extracted media data;

receive requests for the media data in accordance with dynamic adaptive streaming over HTTP (DASH) from a DASH client; and

in response to the requests, send the requested media data to the DASH client.

40. The non-transitory computer-readable storage medium of claim 39, wherein the DASH client is included within the device for receiving media data.

41. The non-transitory computer-readable storage medium of claim 35,

wherein the instructions that cause the processor to receive comprise instructions that cause the processor to retrieve information from a Lower Layer Signaling (LLS) stream;

and

wherein the instructions that cause the processor to extract comprise instructions that cause the processor to;

tune to a service layer signaling (SLS) stream using information from the LLS stream;

retrieve a user service bundle description (USBD) fragment, a layered coding transport (LCT) Session Instance Description (LSID) fragment, a Media Presentation Description (MPD) fragment, and a Schedule fragment from the SLS stream;

select service components using the USBD fragment, the LSID fragment, the MPD fragment, and the Schedule fragment;

tune to the service component streams over respective Real-Time Object Delivery over Unidirectional Transport (ROUTE)/LCT sessions; and

extract media data from the respective service component streams.

42. The non-transitory computer-readable storage medium of claim 35, wherein the instructions that cause the processor to receive the aggregated session description data include instructions that cause the processor to:

receive an identifier element that references a corresponding user service description (USD) session identifier element;

receive one or more broadcast stream identifier elements that identify broadcast streams corresponding to the plurality of sessions;

receive one or more sender IP address elements that specify IP addresses for senders of the broadcast streams;

receive one or more destination IP address elements that specify IP addresses for destinations of the broadcast streams;

receive one or more port elements that specify destination ports for the broadcast streams;

receive one or more physical layer pipe (PLP) ID elements that specify identifiers for the PLP within the broadcast streams;

receive one or more transport session identifier (TSI) elements that specify TSIs of associated source or repair flows for the broadcast streams;

receive one or more bandwidth elements that specify maximum bit-rates for the plurality of sessions;

receive one or more start time elements that specify start times for the plurality of sessions; and

receive one or more end time elements that specify end times for the plurality of sessions.