Media transfer protocol

• US 7,664,872 B2
• Filed: 12/30/2005
• Issued: 02/16/2010
• Est. Priority Date: 01/05/2005
• Status: Active Grant

• Current Assignee: Sonic IP Incorporated (Endeavor Group Holdings Inc.)
• Original Assignee: DIVX Incorporated (SoftBank Group Corp.)
• Inventors: Fudge, Brian, Fry, Kevin, Osborne, Roland, Srinivasan, Mayur, Robinson, Aaron, van Zoest, Alexander
• Primary Examiner(s): Patel; Ashok B.
• Assistant Examiner(s): Edwards; Linglan
• Application Number:
  US11/323,062
• Publication Number:
  US 20060174021A1
• Time in Patent Office: 1,509 Days
• Field of Search: 709/203, 709217-219, 709230-232, 710/61, 370/324
• US Class Current: 709/232
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A computer device selected as a media server is connected to a consumer electronic (CE) device over multiple media transfer channels. The multiple media transfer channels together with an improved media transfer protocol allow for efficient, real-time transfer of different types of digital media, in various combinations, for playing on the CE device. Each type of media is transferred over its own dedicated channel according to its individual data rate. The improved media transfer protocol allows the data to be transmitted in either an asynchronous mode or a synchronous stream or timestamp mode depending on whether synchronization is desired. A dedicated control channel allows for the transfer of control information from the CE device to the media server as well as for resynchronizing media position of the server upon a change in play mode of the corresponding media.

Claims

1. A server configured to transfer video, and audio, media data to a client over separate video, and audio media transfer channels and to communicate with the client via a separate control channel, where the client includes a media timer and is configured to transmit timestamps associated with media being played by the client to the server via the control channel, the server comprising:

a storage device containing video, and audio media data stored in at least one file;

a media server module configured to identify video, and audio media data from within the at least one file for transmission over the separate video, and audio media transfer channels;

a network transport module configured to create separate video, and audio media data packets and prepend header information to the media data packets, where the header information includes timing data generated for the specific media data packet by the network transport module,

wherein the network transport module is also configured to transmit the video, and audio media data packets via the separate video, and audio media transfer channels according to different data rates; and

wherein the timing data for each media data packet includes at least a synchronization mode field indicating a synchronization mode and a timestamp, where the server is configured to generate the timestamp based upon the synchronization mode.

2. The server of claim 1, wherein the media server module receives control information from the client over the control channel, processes the control information and identifies particular video, and audio media data stored in the at least one file in response and the network transport module transmits video, and audio, media data packets containing the particular video, and audio media data over the separate video and audio media transfer channels.

3. The server of claim 2, wherein, the overlay media data is subtitle data, and the synchronization mode field indicates that the overlay media data is synchronous timestamped data for rendering by a client when the media timer is greater than or equal to the timestamp.

4. The server of claim 2 wherein the control information further comprises control packets including a keypress type field and a button identifier field.

5. The server of claim 4 wherein the keypress type field indicates a button'"'"'s current state and the button identifier field indicates a particular button that is invoked on a user input device.

6. The server of claim 1, wherein the synchronization mode field of the video media data packets indicates that the video data is streaming data for rendering immediately by the client asynchronously from the audio media data.

7. The server of claim 6, wherein the video data is for a user interface video prompting user interactions with the client.

8. The server of claim 1, wherein:

the synchronization mode field of the video media data packets indicates that the video data is synchronous stream data for rendering by the client according to the timestamp; and

the timing data further including a duration value, where the server is configured to generate the duration value as indicative of the duration of time in which the transmitted data is valid.

9. The server of claim 1 wherein

the media server module is configured to receive a request to playback a particular media file, and the media server module is configured to identify the particular media file as a file having a neutral file type in which playback is unsupported by the server but is supported by the client;

and

a network transport module configured to receive from the client a particular range of data included in the particular media file, create a media transfer packet including the requested range of data, and transmit the media transfer packet over one of the plurality of a media transfer channel dedicated for transmitting media files having neutral file types.

10. The server of claim 1, wherein:

the server is further configured to transfer overlay media data to a client over a separate overlay media transfer channel;

the at least one file also includes overlay media data;

the media server module is also configured to identify overlay media data from within the at least one file for transmission over the separate overlay media transfer channel;

the network transport module is also configured to create separate overlay media data packets and prepend header information to the overlay media data packets, where the header information includes timing data generated for the specific overlay media data packet by the network transport module; and

the timing data for each media data packet includes at least a synchronization mode field indicating a synchronization mode and a timestamp, where the server is configured to generate the timestamp based upon the synchronization mode.