The present invention relates to online collaboration systems and more particularly to an enhanced online collaboration system for use by viewers of video presentations.
Rapid growth in the availability of reasonably-priced but nevertheless powerful personal computer systems coupled with explosive growth of the Internet has created unprecedented opportunities for people to collaborate online with large numbers of other people on a local, national or even global scale. Online collaboration systems (e.g., chat rooms) have always been a popular way for computer users to exchange thoughts with one another on topics of common interest. In a typical online collaboration system, every user can independently create messages that are sent to a collaboration server. Unlike a conventional e-mail system where messages are stored until they are requested by the addressees, collaboration system messages are posted (i.e., made available to all other users of the system) as soon as they are received. Every user is free to comment on any previously posted messages. The intent of atypical collaboration system is to provide a text-based online equivalent of a room full of people, many of whom are trying to talk at the same time about generally the same topic.
Early collaboration systems rarely fulfilled that intent. Relatively low network data transmission rates, high data error rates and relatively slow personal computer systems combined to cause significant delays in distributing posted messages to users and more delays in receiving responses from those users. Since users could submit messages at any time without regard to what was currently being posted by the collaboration server, it was not uncommon for a discussion to completely change direction before a given user could respond to a previously posted comment. By the time the given user's message reached the collaboration server, other users would have taken the discussions in a different direction, reducing the relevancy of the given user's message.
Message delays limited the usefulness of online collaboration systems. While such systems were feasible where people wanted to collaborate on a topic that either didn't change or changed relatively slowly, such systems were too slow to be of real value if people wanted to collaborate about a “topic” happening in real time, such as a broadcast of a television show or other video event.
However, as both personal computer systems and networks have become faster, it has become more feasible for viewers to collaborate in real-time about events as those events happen; for example, about a football game that is underway or a current episode of a favorite television show during its original airing. And, as online collaboration systems have become better able to “keep up” with real-time events, such systems have became more popular with more viewers until there are now significant communities of people who tune in to watch the event while simultaneously, enthusiastically communicating with others online (both within their community and throughout their country or the world) about the event as it happens.
It is somewhat ironic that as technology enabling people to collaborate online in real-time about events becomes more widely available, people are finding it difficult to find the time to participate in such collaborations due to the demands of their personal and professional lives.
The problem is not that someone who misses a broadcast of an event when it first occurs will never be able to see the event. There are a variety of ways in which a viewer can see a recording of the event even after the event has been completed. Personal recording devices, such as digital video recorders (DVRs), are widely used to record events for later viewing. The popularity of such recording devices is increasing as the devices become cheaper and easier to use while providing better quality recordings. Features such as frame-by-frame or slow-motion playback have increased the popularity of such personal recording devices, particularly among sports fans.
There are other ways a person can see a broadcast of an event long after the original broadcast has ended. One such way takes advantage of the power of the Internet. Content providers, including the original broadcaster and authorized re-broadcasters, can stream recordings across the Internet either on a published schedule or on demand by an individual viewer, enabling the viewer to watch the recording at his or her convenience. Similarly, the original content provider or an authorized re-broadcaster may distribute an encore presentation (that is, a rerun) of the event through the original broadcast medium.
A user who wants to watch a post-original presentation of an event (whether in the form of a personal recording or an Internet download or a rerun) won't miss out on the event. What the user will miss out on is the opportunity to collaborate in real time with others who are also watching a post-original presentation of the same event at the same time.
The present invention assures that a viewer who has missed an original presentation of an event and wants to view the event as a post-original presentation will have an opportunity to collaborate online with others seeing the same presented material at the same time.
An online collaboration system makes available multiple online collaboration sessions for each video presentation. Each collaboration session is associated with a different time slot in the presentation. The system receives requests from one or more viewers who wish to collaborate with other viewers while watching the presentation. Each viewer is assigned to one of the available collaboration sessions, ideally a collaboration session associated with the time slot the viewer is currently watching. For example, if the viewer is currently watching content that occurs 19 minutes after the start of the presentation, the viewer is preferably assigned to a collaboration session associated with content occurring between 18 minutes and 20 minutes after the start of the presentation. The availability of multiple collaboration sessions associated with different time slots in the content decreases the chances the viewer will be thrown into a collaboration session with someone who has already seen more of the presentation and who may inadvertently or intentionally “spoil the ending” of the presentation for other viewers. As the presentation progresses, the viewer will progress through collaboration sessions associated with successively later time slots so the viewer will generally be collaborating with someone who has just as much of the presentation as the viewer, no matter when the presentation starts in “real world” time.
While the specification concludes with claims that particularly point out and distinctly claim the invention, details of embodiments of the invention may be more readily ascertained from the following detailed description when read in conjunction with the accompanying drawings wherein:
Referring to
Although not shown in
Referring now to
Referring to
Referring to
Referring to
While it is possible to limit the number of sessions to twelve (based on the initial assumptions of 5 minute time slots and a 60 minute presentation, it may be preferable to add a thirteenth time slot for a final session that would be open to any viewer who has finished watching the entire presentation. The final session would preferably remain open as long as at two or more viewers wanted to continue exchanging messages about the presentation. The final session could, at least in theory, remain open indefinitely as new viewers who have just finished viewing the entire presentation may continue to enter the session.
Also, depending on the type of presentation, the length of the time slots may be considerably shorter than five minutes, possibly on the order of two minutes, which should decrease the chances of a “spoiling” comment by a senior viewer in a session but would also obviously increases the number sessions required to cover the entire presentation.
A similar set of collaboration sessions must be set up for each video presentation the collaboration server is willing to support. If the collaboration server is willing to support collaborations about a reasonably large number of different video presentations, the number of collaboration sessions that will be simultaneously available will be substantial.
In one embodiment of the invention, multiple sets of collaboration sessions may be setup for viewers having different degrees of maturity. For example, at least four different sets of collaboration sessions may be set up for young viewers (age 12 and under), adolescent viewers (ages 13-18), adult viewers (ages 19-55) and senior viewers (ages 55+). While providing multiple sets of collaboration sessions obviously complicates the task of controlling the sessions, it increases the chance that viewers will be more likely to engage with someone who has a similar perspective on a presentation while decreasing the chance that a particular comment will be offensive or inappropriate to others participating in the same session. Maturity-related collaboration sessions would also make it more feasible for the collaboration service provider to provide moderators, working through a moderator console 50, for collaboration sessions open to younger viewers.
Based on the user's current viewpoint for a video presentation, information about the viewer maintained in a viewer profile database 48 and possible input from a moderator interacting with the collaboration server through the moderator console 50, a user's choice of collaboration sessions may be limited. Several different methods for assigning a user to a particular collaboration session are discussed in greater detail below.
Assuming for the moment that the viewer has joined a particular collaboration session associated with a particular time slot, the collaboration session controller 40 receives any comments the viewer makes and routes them to other viewers who are currently in the same session. The controller 40 can also cause those comments to be recorded in a viewer comments database 44. Stored comments are preferably “stamped” to identify the time slot to which the comments pertain to and any properties of the collaboration session (e.g., viewer age range) during which the comments were made.
The same video presentation may be seen a number of times by different sets of viewers. Comments made by some of those viewers might be of interest to future sets of viewers. A viewer comments database 44 is used to capture and store comments made by viewers during a particular presentation. The captured comments are then made available to future viewers of the presentation. Not every comment made by a viewer is necessarily worth keeping. Moderators, working through a moderator console 50, may filter incoming comments so that only worthwhile comments reach the database 44.
Stored comments are released to future sets of viewers after being filtered by a comment filter 46 to make sure the comments are not released to an inappropriate set of viewers; i.e., a set of viewers who have not yet seen the part of the presentation to which the comments apply or who are in a wrong age range.
In at least one embodiment of the invention, the comments database is also used to store a special type of comment that is exempt from the type of time filtering just described. This special type of comment can be referred to as a “trusted user” comment. A trusted user is basically any user that the collaboration service provider has concluded would not be likely to provide outcome-spoiling comments even if given the privilege of submitting comments for delivery to session members or individual participants who have not yet viewed the time slot to which the comment applies. A typical trusted user comment might be something like “Pay close attention to the last scene and let me know how you interpret it.”
Trusted users can be chosen in different ways. An individual user may submit a list of users trusted by the individual user. A session moderator may, based on an individual user's past actions in the sessions, decide that user is trustworthy enough to be classified as a trusted user. The designation of a particular user as a trusted user is maintained in the viewer profile stored in the database 48.
For a viewer to be assigned to an appropriate collaboration session, that viewer has to submit certain information to the collaboration server when asking to join one of the collaboration sessions.
Once a user has joined a collaboration session every comment submitted by that user is packaged with other information needed by the collaboration server.
To make it easy for users to understand what their options are once they've logged onto the collaboration server and have identified the video presentation in which they are interested, a graphical user interface may be installed in each user's personal computer system.
A unique view indicator 94 marks a viewer's current view point in the presentation. The position of indicator 94 in the drawing indicates who has watched roughly half of the presentation.
Additional indicators 96, 98 and 100 mark active collaboration sessions associated with particular time slots in the presentation. The absence of a session indicator in the time slot containing the view indicator 94 indicates that no one else is viewing the presentation at exactly the same place as the current viewer, at least no one that wants to collaborate online about it. In such a situation, the viewer may want to join one of the existing collaboration sessions 96, 98 and 100.
In a preferred embodiment, the viewer could be considered to have a right to join collaboration session 100 or any collaboration session to the right of the view indicator since the viewers in those sessions will have already seen everything the current viewer has seen. The viewer preferably would not have the right to join any collaboration sessions to the left of the view indicator 94 as the viewers in those sessions will not have seen as much of the presentation as the current viewer. An exception could be made if the viewer had already been identified as a trusted user. A transfer process for allowing a user to leave one collaboration session and join another is described later.
From a visual standpoint, both the user's view indicator and the collaboration session indicators will appear to march across the screen from left to right as the viewer sees more and more of the presentation and as viewers in a collaboration session associated with one time slot in the presentation “leave” that session and “enter” the session associated with the next time slot in the presentation. The users do not, of course, physically or electronically leave one collaboration session and join the next. What really happens is the session designation associated with the users changes front one time slot to the next.
Referring to
However, once a valid join request is received, the viewer is authenticated in a step 112. Assuming the viewer is found not to be authorized in step 114, the join request is rejected in a step 116 and the process ends. If the viewer is authenticated, the collaboration server checks (step 118) to determine whether there are any collaboration sessions associated with the video presentation identified by the user in the join request.
If no open collaboration sessions are found, the collaboration server can start a session (step 122) and associate the session with the time slot coincident with the viewer's view point (step 124).
If, however, there are already one or more open sessions, the viewer can be assigned to one of those open sessions in a step 120, possibly the session associated with the time slot closest to the user's current view point.
The assignment step 120 in the basic join process described above is somewhat rudimentary.
If step 118 indicates there are no open collaboration sessions having “senior” participants, the viewer is assigned in step 136 to one of the existing open sessions occupied by “junior” session participants, perhaps with an admonition not to reveal information the participants had not yet seen.
If sessions of junior viewers are found, a check is made (step 142) whether the joining user is already classified as a trusted user. If the joining user is a trusted user, the user is notified (step 144) of all open sessions for the specified video presentation and asked to make a selection of the session he would like to join. Once the joining user's selection is received (step 146), the joining user is assigned to the selected session in a step 148.
If step 140 fails to reveal that there are open collaboration sessions of junior users, the joining viewer is notified of open sessions occupied by senior viewers (step 150) and asked to select one of those sessions. The process ends once the viewer is assigned to one of the open sessions.
A user who is assigned to a particular collaboration session may become dissatisfied with his experiences in the assigned session.
If the user is found not to be a trusted user, a check is then made (step 168) whether the request is for a transfer to a senior session; that is, a session whose members have already seen as much or more of the presentation as the requesting user. If the request is for transfer to a senior session, the request is granted in step 170 and the transfer process ends. If, however, the request is for transfer to a junior session, the request is rejected in a step 172 before the transfer process ends.
The collaboration server may be implemented by programming a general purpose computer system to perform the specific functions described above.
A computer system includes an internal system bus 200, a system processor 210, internal memory components 202 and one or more “external” memory components, such as an optical drive 212 and a magnetic hard drive 214. The internal memory 202 includes specific types of memory such as read only memory (ROM) 204, basic input/out system (BIOS) memory 206 and random access memory (RAM) 208. The BIOS 206 stores configuration information for the computer system and basic routines used to control the transfer of information among the components of the computer system.
A drive, such as optical drive 212 or hard drive 214, includes a computer usable medium that provides non-volatile storage for applications and processes that execute in the computer system and for data used in and/or generated by those applications and processes. Depending on the technology employed, the drives may include removable media. The special purpose programming needed by a computer system to implement the described invention would typically be stored in one of these drives and transferred as needed into RAM 208.
The computer system also includes a significant number of input/output (I/O) ports 218 that provide interfaces between a variety of input/output devices and the remainder of the computer system. Common examples of input/output devices include keyboard 220, mouse 222, monitor 224 and printer 226.
It should not be inferred that only the devices shown in
Finally, the computer system will include one or more network adapters 216 that are needed to establish communications between the computer system and other computers. Many different types of network adapters exist today and there is no intent to limit the description to a particular type.
While specific embodiments of the Invention have been described, there is no intent to limit the scope of the invention to those specific embodiments. The scope of the invention includes not only the specific embodiments that also all variations and modifications that would occur to those of ordinary skill in the relevant art.
Number | Name | Date | Kind |
---|---|---|---|
5694163 | Harrison | Dec 1997 | A |
5774666 | Portuesi | Jun 1998 | A |
5828839 | Moncreiff | Oct 1998 | A |
6061716 | Moncreiff | May 2000 | A |
6076100 | Cottrille et al. | Jun 2000 | A |
6081830 | Schindler | Jun 2000 | A |
6411988 | Tafoya et al. | Jun 2002 | B1 |
6425012 | Trovato et al. | Jul 2002 | B1 |
6697824 | Bowman-Amuah | Feb 2004 | B1 |
6973665 | Dudkiewicz et al. | Dec 2005 | B2 |
7036083 | Zenith | Apr 2006 | B1 |
7089278 | Churchill et al. | Aug 2006 | B1 |
7124164 | Chemtob | Oct 2006 | B1 |
7143428 | Bruck et al. | Nov 2006 | B1 |
7231131 | Ostrover | Jun 2007 | B2 |
7290698 | Poslinski et al. | Nov 2007 | B2 |
7305436 | Willis | Dec 2007 | B2 |
7441199 | Zenith | Oct 2008 | B2 |
7478334 | Chen et al. | Jan 2009 | B2 |
7600189 | Fujisawa | Oct 2009 | B2 |
7624416 | Vandermolen et al. | Nov 2009 | B1 |
7669213 | Wick et al. | Feb 2010 | B1 |
7739584 | Vella et al. | Jun 2010 | B2 |
7917583 | Angiolillo et al. | Mar 2011 | B2 |
7945622 | Pegg | May 2011 | B1 |
8122474 | Tecot et al. | Feb 2012 | B2 |
8255950 | Wick et al. | Aug 2012 | B1 |
8430299 | Poslinski et al. | Apr 2013 | B2 |
8614718 | Rapo et al. | Dec 2013 | B2 |
8762844 | Kim et al. | Jun 2014 | B2 |
20020059584 | Ferman et al. | May 2002 | A1 |
20020198973 | Besaw | Dec 2002 | A1 |
20030026593 | Ostrover | Feb 2003 | A1 |
20030101450 | Davidsson et al. | May 2003 | A1 |
20030122922 | Saffer et al. | Jul 2003 | A1 |
20030208545 | Eaton et al. | Nov 2003 | A1 |
20040098754 | Vella et al. | May 2004 | A1 |
20040111467 | Willis | Jun 2004 | A1 |
20040125133 | Pea et al. | Jul 2004 | A1 |
20040205822 | Ullman et al. | Oct 2004 | A1 |
20040236865 | Ullman et al. | Nov 2004 | A1 |
20050034065 | Weight | Feb 2005 | A1 |
20050149987 | Boccon-Bigod et al. | Jul 2005 | A1 |
20050193335 | Dorai et al. | Sep 2005 | A1 |
20050198015 | Sezan et al. | Sep 2005 | A1 |
20050262542 | DeWeese et al. | Nov 2005 | A1 |
20060015923 | Chuah et al. | Jan 2006 | A1 |
20060045470 | Poslinski et al. | Mar 2006 | A1 |
20060094409 | Inselberg | May 2006 | A1 |
20060130109 | Zenith | Jun 2006 | A1 |
20060173974 | Tang | Aug 2006 | A1 |
20060248160 | Plummer | Nov 2006 | A1 |
20070083423 | Delbridge | Apr 2007 | A1 |
20070168463 | Rothschild | Jul 2007 | A1 |
20070198738 | Angiolillo et al. | Aug 2007 | A1 |
20070226766 | Poslinski et al. | Sep 2007 | A1 |
20080059580 | Kalinowski et al. | Mar 2008 | A1 |
20080301232 | Facemire et al. | Dec 2008 | A1 |
20080320085 | Bouilloux-Lafont et al. | Dec 2008 | A1 |
20080320523 | Morris et al. | Dec 2008 | A1 |
20090064245 | Facemire et al. | Mar 2009 | A1 |
20090129747 | Casagrande | May 2009 | A1 |
20090187856 | Rapo et al. | Jul 2009 | A1 |
20090310668 | Sackstein et al. | Dec 2009 | A1 |
20100242074 | Rouse et al. | Sep 2010 | A1 |
20110047487 | DeWeese et al. | Feb 2011 | A1 |
20110173672 | Angiolillo et al. | Jul 2011 | A1 |
20120324491 | Bathiche et al. | Dec 2012 | A1 |
20130004138 | Kilar et al. | Jan 2013 | A1 |
20130086159 | Gharachorloo et al. | Apr 2013 | A1 |
20130091239 | Hao et al. | Apr 2013 | A1 |
20130198642 | Carney et al. | Aug 2013 | A1 |
Number | Date | Country | |
---|---|---|---|
20080301232 A1 | Dec 2008 | US |