1. Technical Field
The present invention relates in general to the field of computers, and in particular to the use of computers for teleconferencing. Still more particularly, the present invention relates to a method and system for coordinating the status of attendees of a teleconference meeting.
2. Description of the Related Art
While modern computers have a wide variety of uses, one that is becoming more popular and more sophisticated is the use of a computer for teleconferencing. Such teleconferencing utilizes one or more computers connected to a network, usually a Local Area Network (LAN), through which users can communicate. With the expanded use of Wide Area Networks (WANs), including the Internet, such teleconferences can also be held by users that are physically located in remote locations, including different countries.
A popular form of teleconferencing uses a “chat room.” Such chat rooms are typically browser based and comport with rules and conventions specified by the Internet Relay Chat (IRC), published by the Network Working Group, and identified as Request For Comments (RFC) 1459, May 1993, et seq.
A single teleconference is by definition limited to a single channel. Per RFC 1459, section 1.3, a channel is a named group of one or more clients which all receive messages addressed to that channel. Typically, a channel is under the control of an operator, who has control over who may be in the channel. A user may be part of several channels (and thus several teleconferences) at once, thus making coordination and control of who is and is not authorized to be in a channel problematic.
What is needed, therefore, is a method and system that permits a teleconference operator to easily see what users are allowed to participate in a teleconference, to easily insert and remove users from the teleconference, and to easily see the participation status of all users authorized to participate in the teleconference.
The present invention is thus directed to a method and system for coordinating a Voice Over Internet Protocol (VoIP) teleconference. A teleconference operator drags the names of invited attendees into a hot window, which connects the invited attendees to a channel for the teleconference. Each invited attendee's name has a status icon associated with it, indicating if the invited attendee is active in the teleconference. Each invited attendee has access to a Graphical User Interface (GUI) that permits the attendee to toggle back and forth between different teleconferences.
The above, as well as additional purposes, features, and advantages of the present invention will become apparent in the following detailed written description.
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further purposes and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, where:
a-f depict exemplary Graphical User Interfaces (GUIs) seen by the operator (manager) of the teleconference;
With reference now to the figures and, in particular to
Also connected to system bus 108 are a system memory 110 and an input/output (I/O) bus bridge 112. I/O bus bridge 112 couples an I/O bus 114 to system bus 108, relaying and/or transforming data transactions from one bus to the other. Peripheral devices such as nonvolatile storage 116, which may be a hard disk drive, and input device 118, which may include a conventional mouse, a trackball, or the like, is connected to I/O bus 114.
The exemplary embodiment shown in
A first computer system such as shown as data processing system 100 is used by an operator (manager) of a teleconference, and second computer system, also incorporating the exemplar features described for data processing system 100, is used by an attendee (client) of the teleconference.
With reference now to
Once the list of authorized clients has been displayed, then the name of each client to be invited to a teleconference is “drag and dropped” by the operator into an active window for a specific teleconference (block 206). By dropping the client's name into the active window, an invitation (preferably via a pop-up window or alternatively via an e-mail) is sent to the named client to join in the teleconference. Preferably, the invitation includes information such as a passcode to join the teleconference, the subject matter of the teleconference, the names of other attendees, and other like information. In a preferred embodiment of the invention, this invitation is given at the same time that the teleconference is to be held. That is, rather than asking the client to calendar the teleconference for a future “call in,” the invitation allows the client to immediately join the teleconference.
At block 208, the client either accepts or declines the invitation. The time to accept may be limited to any amount of time within the teleconference. That is, the time to accept may be limited to a fixed amount of time from when the invitation was received (e.g., five minutes), a fixed time of day (e.g., between 1:00 and 1:15 p.m. EST), or the time period during which the teleconference is actually in session.
As soon as the operator has invited the desired clients (query block 210), the teleconference begins (block 212). During the teleconference, the status of the attendees is monitored for changes (query block 214). That is, if an attendee drops out of the teleconference, or mutes out, or switches out to another teleconference, then the status icon next to that attendee is changed accordingly (block 216). As long as the teleconference is in session (query block 218), new attendees can be added by the operator, and the status icon for those attendees is continually updated until the teleconference ends (terminator block 220).
Referring now to
As shown in
Referring now to
With reference to
The status icon 304a associated with “Igor” is shown as “M” indicating that Igor has muted his microphone. The status icons 304a associated with “Francine” and “Harriet” are “P” for “private,” indicating that they are having a private teleconference with another attendee of the Teleconference-A. In this case, the private teleconference is obviously between Francine and Harriet.
Referring now to
With reference now to
When the local attendee wishes to quit a particular teleconference, then the appropriate “Quit” button 410 is clicked, thus removing the attendee from the channel on which the teleconference is active.
Note that GUI 400 preferably has other hot buttons as well. For example, by clicking the “Mute Microphone” button 412, then the local microphone is muted, and other teleconference attendees, including the teleconference operator, are unable to hear the local attendee. This will result in the status icon for the local attendee to show up as “M” to the rest of the teleconference attendees in both Teleconference-A and Teleconference-B. Similarly, the local attendee can mute is own speaker by clicking the “Mute Speaker” button 414, resulting in her status icon showing as a “B.”
If at any time the local attendee wishes to record (video, audio or text) a teleconference, she can click the “Record” button 416, and such recordation will immediately begin. Such recordation preferably occurs at the local computer used by the attendee, or may occur remotely on a server, the operator's computer, or any other similar device.
Likewise, the local attendee may be offered a copy of a file, such as offered by an attendee of the operator of Teleconference-A. By clicking the “Sales Report” button 418, a copy of the text file titled “Sales Report” will be sent to the local attendee.
While the status icons have been shown as letter inside boxes next to the name of an attendee/client, in a preferred embodiment the status icons are color coded. For example, a status icon for “attending” could be green, while the status icon for “muted” could be yellow, and the status icon for “busy” could be red.
The present invention preferably utilizes Voice Over Internet Protocol (VoIP), in compliance with the H.323 suite of standards promulgated by the International Telecommunications Union (ITU), which standards are incorporated by reference herein in their entirety. Note that the H.323 standard for VoIP defines and describes software components of VoIP as being only the top four layers (Application, Presentation, Session and Transport) of the Open Systems Interconnection (OSI) Standard promulgated by the International Organization of Standardization (IOS). The OSI Standard is incorporated by reference herein in its entirety.
With reference now to
It should be understood that at least some aspects of the present invention may alternatively be implemented in a program product. Programs defining functions of the present invention can be delivered to a data storage system or a computer system via a variety of media, which include, without limitation, non-writable storage media (e.g., CD-ROM), writable storage media (e.g., a floppy diskette, hard disk drive, read/write CD ROM, optical media), and communication media, such as computer and telephone networks including Ethernet. It should be understood, therefore in such media when carrying or encoding computer readable instructions that direct method functions of the present invention represent alternative embodiments of the present invention. Further, it is understood that the present invention may be implemented by a system having means in the form of hardware, software, or a combination of software and hardware, as described herein or their equivalent.
While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
4653090 | Hayden | Mar 1987 | A |
4796293 | Blinken et al. | Jan 1989 | A |
4920565 | Strawczynski et al. | Apr 1990 | A |
5426510 | Meredith | Jun 1995 | A |
5594859 | Palmer et al. | Jan 1997 | A |
5596635 | Rao | Jan 1997 | A |
5604738 | Shibata et al. | Feb 1997 | A |
5608653 | Palmer et al. | Mar 1997 | A |
5619555 | Fenton et al. | Apr 1997 | A |
5657246 | Hogan et al. | Aug 1997 | A |
5802294 | Ludwig et al. | Sep 1998 | A |
5925101 | Bayless et al. | Jul 1999 | A |
5938723 | Hales et al. | Aug 1999 | A |
6069943 | David et al. | May 2000 | A |
6125398 | Mirashrafi et al. | Sep 2000 | A |
6195683 | Palmer et al. | Feb 2001 | B1 |
6201859 | Memhard et al. | Mar 2001 | B1 |
6237025 | Ludwig et al. | May 2001 | B1 |
6266341 | Surprenant et al. | Jul 2001 | B1 |
6330321 | Detampel et al. | Dec 2001 | B2 |
6496201 | Baldwin et al. | Dec 2002 | B1 |
6574469 | Xiang et al. | Jun 2003 | B1 |
6615239 | Berstis | Sep 2003 | B1 |
6925065 | Roy | Aug 2005 | B1 |
7043528 | Schmitt et al. | May 2006 | B2 |
7152093 | Ludwig et al. | Dec 2006 | B2 |
7185054 | Ludwig et al. | Feb 2007 | B1 |
7206809 | Ludwig et al. | Apr 2007 | B2 |
7213051 | Zhu et al. | May 2007 | B2 |
7230639 | Ferren et al. | Jun 2007 | B2 |
7328264 | Babka | Feb 2008 | B2 |
7761505 | Krzyzanowski et al. | Jul 2010 | B2 |
20020054104 | Berczik et al. | May 2002 | A1 |
20030156603 | Rakib et al. | Aug 2003 | A1 |
20040039794 | Biby et al. | Feb 2004 | A1 |
20040098456 | Krzyzanowski et al. | May 2004 | A1 |
20040107255 | Ludwig et al. | Jun 2004 | A1 |
20040114746 | Caspi et al. | Jun 2004 | A1 |
20060010392 | Noel et al. | Jan 2006 | A1 |
20060098085 | Nichols et al. | May 2006 | A1 |
20060098798 | Krasnansky | May 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20060147009 A1 | Jul 2006 | US |