Patent Grant
8417827
This invention is related to a communications system that provides synchronous media playback and messaging.
Telecommunications is expanding from just providing communications from one user to another user to providing multimedia communications among a group of users. Moreover, telecommunications is more than a mechanism for the traditional functionality of providing communications. Telecommunications is allowing people to socialize even though people may not be located in the immediate vicinity of each other. On the other hand, telecommunications is enabling people in the same immediate vicinity to converse even though people are not really acquainted with each other. As one example, while in the same recreational venue a wireless subscriber may use short message service (SMS) to talk with another wireless subscriber, whom the wireless subscriber would like to know. Communications is thus providing a non-traditional function of introducing people in order for people to meet with other people.
In line with the above discussion, friends want to socialize with each other whether or not in close proximity. However, people are “on the go,” traveling to other cities, states, or countries. People want to share the experience of enjoying a good song or video with friends even though they not are physically near each other. They want to talk about the feeling and ideas that the performance or recording has provoked. In order to provide an effective experience, both the medium being perceived and any associated communication should be synchronized among all the participants.
It would be advantageous to enable people to watch or listen to the same performance or recording, such as a song or video that is conveyed on a recording medium, at substantially the same time in distant locations and to engage in interaction with other users having access to the recording medium. Moreover, it is important that the intellectual property rights of the media owners are protected.
To overcome limitations in the prior art described above and to overcome other limitations that will be apparent upon reading and understanding the present specification, the present invention is directed to provide synchronous media playback and messaging between a host user and at least one guest user. The host user wishes to initiate a playback session in which the host user and the guest users view a presentation, corresponding to a media file that is locally stored on each of the user's terminals. In order to initiate the playback session, the host user invites the guest users. If a guest user wishes to participate in the playback session, the guest user accepts the invitation. When the host user determines that the session should begin, based upon the acceptances from the guest users, the host user initiates the playback of the media file that is locally stored at each terminal. The present invention also supports playback actions that may occur during the playback session. Action types include pause playback, rewind, fast forward, user-specified internal effect algorithm to modify audio or video, or comment text from a user. The host user can terminate the playback session, and any of the guest users can withdraw during the playback session.
The disclosure provides an exemplary embodiment in which wireless terminals communicate through a central server using Global System of Mobile Communications (GSM) short message service SMS messages. However, variations of the exemplary embodiment support other wireless standards as well as wireline services such as the Internet. Several variations for providing synchronicity (the playing of the media file at the terminals and the associated messaging) is also disclosed.
In the following description of the various embodiments, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration various embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present invention.
Terminal 101 initiates service (as initiated by the host user) by sending invite request 201 (as explained in
Terminal 101 can also communicate with media server 113 over link 123. Link 123 can also assume one of various communications channels, including a wireless communications channel, wireline channel, or cable modem channel. Terminal 101 can download a selected media file from media server 113 so that the media file can be played on a playback device that is logically associated with terminal 101. (As examples, the media file can be an audio media file, a visual media file, or an audiovisual media file.) In one variation of the embodiment, the accessing of a media file is in accordance with copyright protection provided to the owner of the associated medium as known in the art. Terminal 101 can use a usage right certificate in order to obtain permission to access the selected media file from media server 113. The media file may be created by a third party or may be created by the host user. System 100 can utilize Digital Rights Management (DRM) mechanisms to ensure that users are not able to distribute media files to which they do not have the distribution rights. In one variation, terminal 101 has a local media storage memory or removable media device (such as a CD or DVD player) and the server system 107 is accessed in order to fetch DRM certificates, which are used to decrypt the media stored in the memory or the removable media storage. Thus the distribution of the media files is replaced by the distribution of the decryption certificates. Alternatively, the media server 113 can simply check the eligibility or compliancy of the locally stored media file and deliver the permission for participating the playback session to central server 107.
In the exemplary embodiment, the host user wishes to initiate a playback session with guest user A (whose name is “Bob” and corresponds to terminal 103) and guest user B (whose name is “Jane” and corresponds to terminal 105). As previously referenced, terminal 101 correspondingly sends invite request 201 to messaging server 109. Invite request 201 comprises a media file identification and the identifications of guest user A and guest user B. The identity of a guest user may be the telephone number of the corresponding terminal or may be name of the guest user. Messaging server 109 sends a request to user data server 111 over link 133 to record the identities of guest users A and B. Moreover, if the name (e.g. “Bob”) of a guest user is the identity of the user, then user data server 111 translates the name into a telephone number of the corresponding terminal as stored in a data structure in user data server 111. Messaging server 109 uses the telephone number to distribute (forward) the invite request to guest user A and guest server B. Additionally, user data server 111 may translate the media file identification in order that the guest user can retrieve the selected media file from media server 113. User data server 111 performs the translation in concert with media server 113 through link 135.
Terminal 103 (guest user A) and terminal 105 (guest user B) receive the distributed invite requests from messaging server 109 over links 125 and 129, respectively. As with link 121, links 125 and 129 can correspond to one of a number of communication channel types. Also, terminal 103 and terminal 105 can download the selected media file as identified by the media file identification in invite request 201 through links 127 and 131, respectively.
While the disclosed exemplary embodiment has at least one server interceding in the synchronous media playback and messaging configuration, other embodiments may utilize direct communications between terminals 101, 103, and 105 obviating the need for any servers. For example, terminal 101 may directly communicate to terminal 103 and to terminal 105 through a wireless infrastructure comprising switching and radio equipment.
With a variation of the embodiment, terminal 101 (host user) queries terminals for the media files or certificates they have and create “ad-hoc” viewer groups based on matching file ownerships. A local (Bluetooth) or network (Internet) service may be used to poll any accessible terminals for the media files or DRM certificates. When terminals are found that have the same media files or certificates, an alert is sent to the users indicating that a playback session can be formed with the devices. The users then have the option to start or schedule a session. Access privilege systems for allowing such queries apply. Terminal 101 (host user) can distribute the scheduled playback session to unspecified users, as another form of invitation. Central server 107 can manage a database of open session invitations so that interested users can search for a playback session with specific interest in either the media file or the host user's identity and sign up for the playback session.
As was discussed in relation to
With another variation of the exemplary embodiment, links 121, 125, and 129 are Internet communication channels. In such a configuration, extensible Markup Language (XML) can be utilized rather than GSM SMS. An example of invite request 201 using XML is:
Central server 107 distributes invite request 203 to terminal 103 and invite request 205 to terminal 105. When each of the terminals receive the invite requests, an associated playback player compares its local storage of media files and/or rights certificates to the media file ID in order to determine whether the guest user must obtain this media file or access rights to it. If the guest user needs to obtain the media file, the guest user's terminal (103, 105) communicates with central server 107 and initiates suitable transactional procedures. If media server 113 were a separate physical entity, then the user's terminal needs to establish a transaction with the appropriate media server.
With reference to
The host user (“Pete”) is informed that both guest user A (“Bob”) and guest user B (“Jane”) have accepted participating in the playback session. In this example, the host user waits until central server 107 reports that all the guest users have accepted (by returning accept response messages). In general, the host user can initiate the playback session whenever a sufficient number of quest users have accepted. Consequently, host user (“Pete”) manipulates terminal 101 to send start playback request 219 to central server 107. As with invite request 201, the exemplary embodiment utilizes GSM SMS. In this example, the SMS message is:
Central server 107 distributes start playback request 219 by sending start playback request 221 to terminal 103 (guest user A) and start playback request 223 to terminal 105 (guest user B). The beginning of the playback session need not correspond to the beginning of the media file and thus can correspond to any time within the media file. When terminals 103 and 105 receive start playback request 221 and 223 respectively, the associated player device starts playing the media file at the predetermined time as indicated in invite request 203 and 205 (refer to the playback start time field in Table 1). In a variation of the exemplary embodiment, central server 107 distributes the start playback request to the terminals of all active users, including the host user, in order to achieve a degree of synchronism that compensates for varying time delays in system 100. In one variation the playback session can be started regardless of the replies from the guest users, thus allowing the host user to start playback at any time. The playback start time can be compared with the actual time that a guest user accepts the invitation and starts viewing the playback. This offset can be used to achieve a degree of synchronism that compensates for the various time delays in system 100, whether network or user action related.
During the playback session (as initiated by start playback requests 221 and 223), any of the active users (host user and guest users) can request a playback action. In order to do so, an active user sends an action request (e.g. action request 225) to central server 107. The action request message requests one of a number of action types during the playback session, including pause playback, rewind, fast-forward, user-specified internal effect algorithm to modify audio or video (e.g. altering the audio and video in order to accentuate a favorite actress), or textual comment from a user. The first three action types are patterned after actions that are typically associated with an audio cassette player or a VCR. The fourth action type is user-specified that can be customized for the specific application. As an example, the media player can be instructed to emphasize the dialog of a particular actress in a particular scene. As another example, if a user wishes to send a comment to the other users, an action request message with textual comment (e.g. “I really like this scene—Jane”) is sent to central server 107.
In order for message server 109 to distribute action request 227 to terminal 101 (host user) and action request 229 to terminal 103 (guest user A), guest user B (terminal 105) may require permission in a variation of the embodiment, allowing guest user B to request the given action. As an example, guest user B may be permitted to comment during the playback session but not rewind the video presentation. In the exemplary embodiment, permissions for active users are stored on central 107 (logically corresponding to user data server 111). In variations of the embodiment, the host user may be conversing with the guest users through a conferenced voice telephone call. In another variation of the invention, the permissions are stored in terminal 101, 103, or 105 and not in central server 107. Once the permission is checked with server 107, the locally stored permissions expedite the process of checking with central server 107 again.
In
The playback session is started in a substantially synchronous manner for all the active users (host user, guest user A, and guest user B). Synchronism can be achieved by a number of approaches. Central server 107 stores an internal time at the time of starting the playback session. The playback session commences when central server 107 receives start playback request 201 and consequently distributes start playback request 203 and 205 to guest user A and guest user B, respectively. At that time, central server 107 stores the internal time for starting the playback session. Other guest users (not depicted in
If a greater degree of synchronicity is desired (as may be the case if time delays in system 100 are a concern), a more complex method to ensure true synchronicity can be incorporated by system 100. For example, the internal times tracked by terminals 101, 103, and 105 and central server 107 can be synchronized to a common global clock, e.g. the Global Positioning System (GPS). Central Server 107 compares the internal clocks (as reported in messages such as accept responses 207 and 215) with the internal clock of central server 107. The time delays can be compensated by sending the corresponding time differences to terminals 101, 103, and 105 so that the corresponding playback device (which are considered as logically contained in the terminal) can coordinate media player operation in order to synchronize player actions.
In step 305, message server 109 receives accept response 207 and 215 from terminals 105 and 103, respectively. In step 307, message server 109 instructs user data server 111 to record terminals 105 and 103 as being active in the playback session. Message server 109 relays accept responses 209 and 217 to terminal 101 in step 309.
In the exemplary embodiment, the host user waits until all the guest users have accepted the invitation in step 311. However, with variations of the exemplary embodiment, the host user may wish to continue with the playback session when a subset of the invited guest users has accepted.
It is assumed that terminals 101, 103, and 105 can fully utilize the selected media file. However, this may not be the case. With a plurality of terminals participating in the playback session, the terminals may have different capabilities. For example, the playback session may be processing a movie having both audio and video components. One of terminals (e.g. terminal 105) may have only audio capability while terminals 103 and 103 have both audio and video capabilities. Moreover, the active users in the playback session may desire to modify the media file in order to accentuate the viewing experience.
According to one embodiment, the playback device associated with each of terminals 101, 103, and 105 is able to modify media characteristics, using a preset selection of effects and modifications (e.g. converting color imagery into black and white, inverting the colors, distorting the sound channels, changing the tempo and speed of the playback) stored at the terminal. In other words, a playback device utilizes a data file containing associated modifications in order to alter the processing of the media file during the playback session.
Modification file 703 can be formed by storing all the playback control messages created during the playback session. In one variation, the users access modification files associated with a particular media file and play back the media file using the modification file. Modification files can be stored in the remote (central) server or local memory of user's terminal.
Modification file 703 comprises a unique media file identifier and a list of modification functions that are linked to media file 701 with the following characteristics:
In addition, modification file 703 can comprise DRM-related data, which limits use of media file 703 by a guest user.
Using a suitable messaging standard (e.g. Multimedia Message System), modification file 703 can be more usable in the receiving terminal that is unable to display media file 701 or display modified media file 706 by appropriately altering modification file 703.
Messaging server 109 queries user data server 111 in order to determine if modification file 703 requires adaptation in accordance with the capabilities of terminal 807 by sending message 807 (comprising modification message 802 and the identification of terminal 807). User data server 111 stores characteristics of terminal 807 and correspondingly alters the modification file and returns adapted modification message 804 to messaging server 109.
Messaging server 109 converts a selected media file in order to be compatible with the capabilities of terminal 807. The converted terminal-suitable media file is delivered to terminal 807. The basic media type remains similar, e.g. full motion video, but the modification capabilities are dissimilar. Thus, one terminal may be capable of showing a video effect on the image, e.g. inverting the colors, while another terminal may not be capable of that particular effect. The modification file describing the “invert” effect is altered to another suitable effect for this particular terminal, e.g. blink the image on/off in a stroboscope fashion.
In a variation of the embodiment, messaging server 109 directs modification message 805 (comprising the altered modification file) to terminal 807. As an example, a terminal without video playback capabilities can process a media file by creating still image compilation of key images. As another example, the audio portion of the playback session may be converted to text captions for users who are hearing-impaired.
Services processor 909 supports the processing of the media playback services for the host user in accordance with the flow diagrams in
Media file 701 (as shown in
The host user inputs requests through keypad unit 921 that is connected to services processor 909 through link 920. The host user views display unit 915 that displays choices from which the host user inputs selects using a cursor control on keypad unit 921, In the exemplary embodiment, display unit 915 shows list 917 of media files and list 919 of guest users that are to be selected for the playback session. The host user inputs associated selections through the cursor control on keypad unit 921 through link 920, services processor 909, and link 916. The host user selects the media file with cursor 923 and selects at least one guest user with cursor 925. Lists 917 and 919 may be shown currently or sequentially on display unit 915.
Although
As can be appreciated by one skilled in the art, a computer system with an associated computer-readable medium containing instructions for controlling the computer system can be utilized to implement the exemplary embodiments that are disclosed herein. The computer system may include at least one computer such as a microprocessor and associated peripheral electronic circuitry.
It is to be understood that the above-described embodiment is merely an illustrative principle of the invention and that many variations may be devised by those skilled in the art without departing from the scope of the invention. It is, therefore, intended that such variations be included with the scope of the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5339413 | Koval et al. | Aug 1994 | A |
| 5600775 | King et al. | Feb 1997 | A |
| 5615401 | Harscoet et al. | Mar 1997 | A |
| 5734589 | Kostreski et al. | Mar 1998 | A |
| 5784527 | Ort | Jul 1998 | A |
| 5805821 | Saxena et al. | Sep 1998 | A |
| 5828866 | Hao et al. | Oct 1998 | A |
| 5854898 | Riddle | Dec 1998 | A |
| 5920338 | Katz | Jul 1999 | A |
| 5930473 | Teng et al. | Jul 1999 | A |
| 5953506 | Kalra et al. | Sep 1999 | A |
| 5999977 | Riddle | Dec 1999 | A |
| 6003084 | Green et al. | Dec 1999 | A |
| 6006253 | Kumar et al. | Dec 1999 | A |
| 6075560 | Katz | Jun 2000 | A |
| 6223211 | Hamilton et al. | Apr 2001 | B1 |
| 6314466 | Agarwal et al. | Nov 2001 | B1 |
| 6341316 | Kloba et al. | Jan 2002 | B1 |
| 6351467 | Dillon | Feb 2002 | B1 |
| 6353174 | Schmidt et al. | Mar 2002 | B1 |
| 6389471 | Agraharam et al. | May 2002 | B1 |
| 6424841 | Gustafsson | Jul 2002 | B1 |
| 6425131 | Crandall et al. | Jul 2002 | B2 |
| 6430576 | Gates et al. | Aug 2002 | B1 |
| 6453355 | Jones et al. | Sep 2002 | B1 |
| 6480961 | Rajasekharan et al. | Nov 2002 | B2 |
| 6526335 | Treyz et al. | Feb 2003 | B1 |
| 6594260 | Aviani et al. | Jul 2003 | B1 |
| 6604129 | Slutsman et al. | Aug 2003 | B2 |
| 6631410 | Kowalski et al. | Oct 2003 | B1 |
| 6671732 | Weiner | Dec 2003 | B1 |
| 6757517 | Chang | Jun 2004 | B2 |
| 6816895 | Andreakis et al. | Nov 2004 | B2 |
| 6891822 | Gubbi et al. | May 2005 | B1 |
| 6907570 | Amir et al. | Jun 2005 | B2 |
| 6976094 | Dalrymple et al. | Dec 2005 | B1 |
| 7076560 | Lango et al. | Jul 2006 | B1 |
| 7133923 | MeLampy et al. | Nov 2006 | B2 |
| 7136934 | Carter et al. | Nov 2006 | B2 |
| 7193987 | Vilander | Mar 2007 | B2 |
| 7200357 | Janik et al. | Apr 2007 | B2 |
| 7493644 | Tanskanen | Feb 2009 | B1 |
| 7890661 | Spurgat et al. | Feb 2011 | B2 |
| 20010003523 | Crandall et al. | Jun 2001 | A1 |
| 20010025316 | Oh | Sep 2001 | A1 |
| 20010037367 | Iyer | Nov 2001 | A1 |
| 20010049728 | Kang | Dec 2001 | A1 |
| 20020069419 | Raverdy et al. | Jun 2002 | A1 |
| 20020076025 | Liversidge et al. | Jun 2002 | A1 |
| 20020078454 | Auberger | Jun 2002 | A1 |
| 20020091848 | Agresta et al. | Jul 2002 | A1 |
| 20020095612 | Furhrer et al. | Jul 2002 | A1 |
| 20020107040 | Crandall et al. | Aug 2002 | A1 |
| 20020138569 | Slutsman et al. | Sep 2002 | A1 |
| 20020144276 | Radford et al. | Oct 2002 | A1 |
| 20020164973 | Janik et al. | Nov 2002 | A1 |
| 20020168938 | Chang | Nov 2002 | A1 |
| 20020174243 | Spurgat et al. | Nov 2002 | A1 |
| 20020194309 | Carter et al. | Dec 2002 | A1 |
| 20030014488 | Dalal et al. | Jan 2003 | A1 |
| 20030023741 | Tomassetti et al. | Jan 2003 | A1 |
| Number | Date | Country |
|---|---|---|
| 9946702 | Sep 1999 | WO |
| WO 9946702 | Sep 1999 | WO |
| 0056088 | Sep 2000 | WO |
| Entry |
|---|
| Microsoft, Computer Dictionary, Fifth Edition, by Michael Heim, p. 506. |
| RFC 2327: SDP, Handley, Apr. 1998. |
| RFC 2543: SIP, Handley, Mar. 1999. |
| International Search Report, International Application No. PCT/IB02/05215, Mar. 14, 2003. |
| European Search Report for EP 02788305.7. |
| European Search Report for EP 02788305.7, Feb. 5, 2007. |
| European Office Action for corresponding EP Application No. 02 788 305.7-1244, Jun. 10, 2011, pp. 1-6. |
| Number | Date | Country | |
|---|---|---|---|
| 20030126211 A1 | Jul 2003 | US |
