Real-time or near real-time streaming

• US 9,729,830 B2
• Filed: 04/01/2011
• Issued: 08/08/2017
• Est. Priority Date: 04/01/2010
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: May, Jr., William, Pantos, Roger
• Primary Examiner(s): MAI, KEVIN S
• Application Number:
  US13/078,741
• Publication Number:
  US 20110246621A1
• Time in Patent Office: 2,321 Days
• Field of Search: 709219
• CPC Class Codes: G06F 16/4387 by the use of playlists
• CPC Class Codes: H04L 65/612 for unicast
• 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/4586 Content update operation triggered locally, e.g. by comparing the version of software modules in a DVB carousel to the version stored locally deployment, distribution, installation, update of software G06F8/65; error detection or correction of the data by redundancy during software upgrading G06F11/1433; arrangements for updating broadcast information or broadcast-related information H04H60/25
• CPC Class Codes: H04N 21/6125 involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/654 Transmission by server directed to the client
• CPC Class Codes: H04N 21/6581 Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application
• CPC Class Codes: H04N 21/8543 using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML] information retrieval of semistructured data, the underlying structure being taken into account, e.g. mark-up language structure data G06F16/80
• CPC Class Codes: H04N 7/17318 Direct or substantially direct transmission and handling of requests

Abstract

A near real time content streaming system can use a playlist file, in one embodiment, that includes an indicator of the type of content represented by the playlist file. The type can be indicated by a parameter, such as Video on Demand (VOD) or live, or event, that specifies the type of playlist file, and a client device can process the playlist file based upon the type of playlist file indicated by the parameter. For example, the client device, after determining the type of playlist from a playlist file can make efficiency optimizations when processing the playlist file. For example, the client, knowing the playlist file is a VOD playlist, can save the previously used variant playlist when switching to a new variant playlist rather than discarding the previously used variant playlist.

Claims

1. A machine readable, tangible, non-transitory storage medium storing executable instructions that, when executed, cause a data processing system to perform a method comprising:

requesting, with a client device, a playlist file from a server device, wherein the client device is configured to play media content using the playlist file, the media content having a media content type comprising video on demand, event, or live, wherein a type parameter of “

live”

indicates that the media content has an indefinite start time, and wherein a type parameter of “

event”

indicates that the media content has a definite start time and an indefinite ending time;

receiving, at the client device in response to the request, the playlist file from the server device, the playlist file having Universal Resource Indicators (URIs) which indicate a plurality of media files and a plurality of tags having parameters related to playback of the plurality of media files;

parsing, by the client device, the playlist file and determining that one of the plurality of tags comprises an optional PLAYLIST-TYPE tag having a type parameter which indicates a type of the playlist file, wherein the type parameter comprises one of video on demand (VOD), live, or event;

parsing, by the client device, the playlist file to determine whether one of the plurality of tags comprises an ENDLIST tag, indicating that no more media files will be added to the playlist file;

in response to determining that the playlist file does not contain the ENDLIST tag;

in response to the PLAYLIST-TYPE tag having the type parameter “

VOD”

, playing media content using the playlist file comprises the client;

not requesting an updated playlist file from the server; and

generating an error indicating that the playlist file does not contain the ENDLIST tag;

in response to the PLAYLIST-TYPE tag having the type parameter “

live”

, playing media content using the playlist file comprises the client device requesting and loading an updated playlist file from the server device;

in response to the PLAYLIST-TYPE tag having the type parameter “

event”

, playing the media content using the playlist file comprises the client requesting an updated playlist file, and;

loading only a portion of the updated playlist file;

or

loading the entire updated playlist file and parsing only a portion of the updated playlist file;

requesting, by the client device from the server device, one or more of the media files in an order indicated by the playlist file; and

receiving, by the client device from the server device, the one or more requested media files through the network using the non-streaming transfer protocol.

2. The medium as in claim 1 further comprising, in response to the PLAYLIST-TYPE having the type parameter live, configuring the client device to process the updated playlist as a sliding window playlist, wherein a sliding window playlist comprises the playlist file with one or more URIs deleted from the playlist and one or more URIs appended to the playlist file, each URI referencing a media file.

3. The medium as in claim 2 wherein when the type parameter is VOD the playlist file does not change, and the client device is configured to save the playlist file for future use when switching to a variant playlist for content referred to by the playlist file.

4. The medium as in claim 1 wherein when the type parameter is event, the event has a specified and fixed beginning time for an event playlist file, and the updated playlist file comprises the playlist file with one or more URIs appended to the playlist file and no URIs removed from the playlist file, each URI referencing a media file.

5. The medium as in claim 2 wherein the method further comprises generating an audio or video or an audio/video output representing the stream of content by playing the media files with the client device in the order indicated by the playlist file and wherein the non-streaming transfer protocol comprises a hypertext transfer protocol (HTTP) compliant protocol.

6. The medium as in claim 1 wherein the method further comprises:

storing, in at least one log, statistics relating to data access of the media files or network errors which occur when receiving the media files;

receiving a request, through an API (Application Program Interface), to obtain the statistics.

15. The medium of claim 1, wherein a type parameter of “

live”

indicates that the media content has an indefinite start time, and wherein a type parameter of “

event”

indicates that the media content has a definite start time and an indefinite ending time.

16. The medium of claim 2, wherein generating an error comprises marking the playlist file as having an error.

17. The medium of claim 1, further comprising:

in response to determining that the PLAYLIST-TYPE tag is not present in the playlist file and that the ENDLIST tag is not present in the playlist file, requesting, by the client device, an updated playlist file.

7. A machine implemented method performed by a data processing system, the method comprising:

requesting, with a client device, a playlist file from a server device, wherein the client device is configured to play media content using the playlist file, the media content having a media content type comprising video on demand, event, or live, wherein a type parameter of “

live”

indicates that the media content has an indefinite start time, and wherein a type parameter of “

event”

indicates that the media content has a definite start time and an indefinite ending time;

receiving, at the client device in response to the request, the playlist file from the server device, the playlist file having Universal Resource Indicators (URIs) which indicate a plurality of media files and a plurality of tags having parameters related to playback of the plurality of media files;

parsing, by the client device, the playlist file and determining that one of the plurality of tags comprises an optional PLAYLIST-TYPE tag having a type parameter which indicates a type of the playlist file, wherein the type parameter comprises one of video on demand (VOD), live, or event;

parsing, by the client device, the playlist file to determine whether one of the plurality of tags comprises an ENDLIST tag, indicating that no more media files will be added to the playlist file;

in response to determining that the playlist file does not contain the ENDLIST tag;

in response to the PLAYLIST-TYPE tag having the type parameter VOD, playing media content using the playlist file comprises the client;

not requesting an updated playlist file from the server; and

generating an error indicating that the playlist file does not contain the ENDLIST tag;

in response to the PLAYLIST-TYPE tag having the parameter “

live”

, playing media content using the playlist file comprises the client device requesting and loading an updated playlist file from the server device;

in response to the PLAYLIST-TYPE tag having the type parameter “

event”

, playing the media content using the playlist file comprises the client device requesting an updated playlist file, and;

loading only a portion of the updated playlist file;

or

loading the entire playlist file and parsing only a portion of the updated playlist file;

requesting, by the client device from the server device, one or more of the media files in an order indicated by the playlist file; and

receiving, by the client device from the server device, the one or more requested media files through the network using the non-streaming transfer protocol.

8. The method as in claim 7 further comprising, in response to the PLAYLIST-TYPE having the type parameter configuring the client device to process the updated playlist as a sliding window playlist, wherein a sliding window playlist comprises the playlist file with one or more URIs deleted from the playlist file and one or more URIs appended to the playlist file, each URI referencing a media file.

9. The method as in claim 8 wherein when the type parameter is VOD the playlist does not change, and the client device is configured to save the playlist for future use when switching to a variant playlist for content referred to by the playlist.

10. The method as in claim 7 wherein when the type parameter is event, the event has a specified and fixed beginning time for an event playlist file, and the updated playlist file comprises the playlist file with one or more URIs appended to the playlist file, and no URIs removed from the playlist file, each URI referencing a media file.

11. The method as in claim 8 wherein the method further comprises generating an audio or video or an audio/video output representing the stream of content by playing the media files with the client device in the order indicated by the playlist file and wherein the non-streaming transfer protocol comprises a hypertext transfer protocol (HTTP) compliant protocol.

12. A data processing system comprising:

a processing device programmed with executable instructions that, when executed, perform a method comprising;

requesting, with a client device, a playlist file from a server device, wherein the client device is configured to play media content using the playlist file, the media content having a media content type comprising video on demand, event, or live, wherein a type parameter of “

live”

indicates that the media content has an indefinite start time, and wherein a type parameter of “

event”

indicates that the media content has a definite start time and an indefinite ending time;

receiving, at the client device in response to the request, the playlist file from the server device, the playlist file having Universal Resource Indicators (URIs) which indicate a plurality of media files and a plurality of tags having parameters related to playback of the plurality of media files;

parsing, by the client device, the playlist file and determining that one of the plurality of tags comprises an optional PLAYLIST-TYPE tag having a type parameter which indicates a type of the playlist file, wherein the type parameter comprises one of video on demand (VOD), live, or event;

parsing, by the client device, the playlist file to determine whether one of the plurality of tags comprises an ENDLIST tag, indicating that no more media files will be added to the playlist file;

in response to determining that the playlist file does not contain the ENDLIST tag;

in response to the PLAYLIST-TYPE tag having the type parameter VOD, playing media content using the playlist file comprises the client;

not requesting an updated playlist file from the server; and

generating an error indicating that the playlist file does not contain the ENDLIST tag;

in response to the PLAYLIST-TYPE tag having the type parameter “

live”

playing the media content using the playlist file comprises the client device requesting and loading an updated playlist file from the server device;

in response to the PLAYLIST-TYPE tag having the type parameter “

event”

, playing the media content using the playlist comprises the client device requesting an updated playlist file, and;

loading only a portion of the updated playlist file;

or

loading the entire playlist file and parsing only a portion of the updated playlist file;

requesting, by the client device from the server device, one or more of the media files in an order indicated by the playlist file; and

receiving, by the client device from the server device, the one or more requested media files through the network using the non-streaming transfer protocol.

13. The system as in claim 12 further comprising, in response to the PLAYLIST-TYPE tag having the type parameter live, configuring the client device to process the updated playlist as a sliding window playlist, wherein a sliding window playlist comprises the playlist file with one or more URIs deleted from the playlist file and one or more URIs appended to the playlist file, each URI referencing a media file.

14. The system as in claim 13 wherein when the type parameter is VOD the playlist does not change, and the client device is configured to save the playlist for future use when switching to a variant playlist for content referred to by the playlist, and wherein when the type parameter is event, the event has a specified and fixed beginning time for an event playlist, and the updated playlist file comprises the playlist file with one or more URIs appended to the playlist file, and no URI s removed from the playlist file, each URI referencing a media file.