The present invention relates generally to the fields of data networks and communication systems; more specifically, to systems and methods aimed at enabling and managing conference sessions among at least two endpoints in a communications system.
Push-to-talk (PTT) is a two-way communication service that works like a walkie-talkie. A normal cell phone call is full-duplex, meaning both parties can hear each other at the same time. PTT is half-duplex, meaning communication can only travel in one direction at any given moment. A token-based model of operation, in which a person must be first granted access to the floor by a floor control mechanism before he may speak to other session participants, typically governs most PTT sessions. For instance, a PTT-enabled handset typically requires that a caller press and hold a button while talking, and then release the button when they are done. Any listener may then press their button in a similar manner to request access to the floor in order to respond.
The present invention will be understood more fully from the detailed description that follows and from the accompanying drawings, which however, should not be taken to limit the invention to the specific embodiments shown, but are for explanation and understanding only.
A conferencing system and method for dynamically upgrading a PTT session to a full-duplex conference, as well as downgrading a full-duplex conference to a PTT conference, is described. In the following description specific details are set forth, such as device types, system configurations, protocols, methods, etc., in order to provide a thorough understanding of the present invention. However, persons having ordinary skill in the relevant arts will appreciate that these specific details may not be needed to practice the present invention.
According to one embodiment of the present invention, a conferencing system and method is provided in which all or some participants of a regular conference can either be downgraded to a PTT session, or upgraded from a PTT session to a full-duplex conferencing session. Downgrading/upgrading between half-duplex and full-duplex conferencing may be initiated by a processor running a program on the conferencing server, the conference moderator, or by a participant to the conference. A user interface may be utilized to initiate a downgrade/upgrade by a moderator or conference participant. For example, a graphical user interface (GUI), a touch user interface (TUI), or a voice user interface (VUI) may be used. For example, a VUI may utilize an interactive voice response (IVR) session initiated with the conference server win in the user presses a special key code, e.g., “#5”, or, for IP phones, a “upgrade/downgrade” softkey button. In another embodiment, the system may utilize known speech recognition and/or natural language recognition techniques to initiate the mode transition.
System initiated downgrades may be initiated via a policy configured via a web based interface (e.g., a GUI). Various criteria may be applied for downgrading a user from full-duplex to PTT. For example, the downgrade of a conference participant to PTT may occur automatically based on the occurrence of an event or condition affecting conferencing resources, e.g., active speaker statistics, weighted priorities assigned to participants in the conference, or another conference of a higher priority vying for conferencing resources. In another embodiment, the system may attempt to reserve conferencing resources to allow new users to join the conference. As soon as the conference resources fall below a pre-configured threshold, the system moves full-duplex participants to half-duplex modality in order to free up conferencing resources. Depending on the particular policy being implemented, such automatic downgrades may be temporary, e.g., 10 minutes, or until conferencing resource availability permits the downgraded participants to be upgraded to a full-duplex conference. That is, after a predetermined time duration has elapsed, or upon release of resources (e.g., conferencing ports) the system may automatically upgrade the participant from PTT to full-duplex.
In another embodiment, a moderator can use a web-based GUI running on a PC to downgrade/upgrade a participant or conference to PTT mode. For instance, the GUI may list the entire set of participants in the conference along with their current communication mode (full duplex, PTT). When the moderator selecting PTT mode for a given participant, the GUI outputs a signal via an external interface of the PC to a conferencing server that causes the server to immediately change the communication channel of that participant from full-duplex to PTT. Likewise, a moderator can upgrade a PTT user to a regular conference by selecting the full-duplex setting for that participant. Note that in this latter case, upgrading is dependent upon the conferencing system having enough resources available.
If there are insufficient resources available at the time that the change is requested by the moderator, the participant will remain in PTT mode, and a message such as, “Cannot upgrade—system has no resources” may appear on the interface. In this latter instance, the system may provide the moderator with the option of “camping-on” the system to request or reserve the needed resources once they become available. Once the resources are available, the participant is automatically upgraded from PTT to full-duplex mode, with the moderator's GUI being updated accordingly. In another embodiment the system may advise the moderator that in order to facilitate the transition of the conference from half-duplex to full-duplex a certain number of participants would need to be dropped out from the conference.
Participant initiated mode changes may be implemented in a similar manner to that of moderator-initiated upgrades/downgrades. For example, a GUI may list the current modality and permit the user/participant to switch modalities, i.e., from PTT to full-duplex, or vice versa. The GUI may be generated by software (i.e., code) running the user's PC. In other cases, the GUI may comprise a collaborative web-based application that is accessed by the browser software running on the user's PC. In other instances, GUI 13 may comprise a downloaded application, or other forms of computer-executable code that may be loaded or accessed by a participant's PC.
As in the case of a moderator-initiated upgrade, a participant may only be permitted to upgrade to PTT mode if there are adequate resources available. If not, the user may have the option to camp-on the system until the required resources are available for his use.
A participant who has been downgraded/upgraded may be informed via an audio prompt or a text message sent to their endpoint device. The audio prompt may comprise special tone (e.g., two short “beep” tones for upgrade, one long beep for downgrade) or a pre-recorded message indicating that he has been downgraded to PTT, or upgraded to Full Duplex mode, whichever the case might be. For downgraded users, the message may also include a brief reason why the person was moved to PTT (e.g., “You have been downgraded due to insufficient conferencing resources.”). Depending on the capabilities of the endpoint devices being used, other conference participants may also be notified of the change in status of those who have been upgraded/downgraded.
It is appreciated that the media path for the conference participants may include audio (voice) transmissions across a variety of different networks (e.g., Internet, intranet, PSTN, etc.), protocols (e.g., IP, Asynchronous Transfer Mode (ATM), Point-to-Point Protocol (PPP)), with connections that span across multiple services, systems, and devices (e.g., private branch exchange (PBX) systems, VoIP gateways, etc.). In a specific embodiment, the present invention may be implemented by software or hardware (firmware) installed in an IP communications system that includes components such as Cisco System's IP Communicator, Call Manager, MeetingPlace, Softphone (a PC that has phone capabilities installed), and other IP phone/communication products. Alternative embodiments of the present invention may be implemented in PBX, telephony, telephone, and other telecommunications systems.
Conferencing server 13 is responsible for providing the resources necessary to conduct the conference session. Typically, conferencing server 13 includes a digital signal processor (DSP) that mixes audio streams received from each of the conference participants—including the PTT speaker with the floor control token—with the mixed stream being output back to the conference participants and also the PTT users who are in listen-only mode (i.e., without the floor control token). Conference participants may be connected to conferencing server 13 via IP network 11 through a variety of communication devices. For example,
Also shown is a time-division multiplexing (TDM) phone 19 connected to IP network 11 via a VoIP gateway 18. A standard VoIP phone 14 is shown directly connected with IP network 11. Additionally, an IP wireless phone 17 is illustrated in
Practitioners in the arts will understand that PTT server 12 and conferencing server 13 shown in
As previously discussed, a single conference server can support many conferences. Therefore, a request to upgrade one or more participants may not always be granted, since granting the request depends on the current network resource allocation. In response to the upgrade request, the conferencing server may run an algorithm to determine whether the session can be upgraded to full duplex mode for each of the participants selected (block 29). In the event that the there are insufficient resources available (e.g., no ports on the conferencing server or insufficient mixer resources) the conferencing server may be “camped-on” until there are sufficient ports available to convert the PTT conversations to full-duplex conference (block 30). Basically, the upgrade request stays with the conferencing server in the form of a reservation to use server resources are once they become available. Alternatively, the system may notify the moderator that a number of users should be converted to half-duplex communication mode in order to accommodate the request.
In a specific embodiment, a subset of the participants may hold onto the conference server ports while the rest of the conference participants are shifted to PTT mode. This hybrid scenario may be useful to keep key meeting participants in a full-duplex mode while temporarily downgrading the other participants are to a PTT session.
Continuing with the example of
It should be understood that upgrading/downgrading participants can occur anytime during the conference session by either the moderator, the system (automatically, based on policy rules), or by the conference participants themselves, depending on the particular system configuration.
By way of example, where discussions in a meeting begin to spin out of control a moderator may regain control by temporarily downgrading particularly vociferous individuals to PTT mode. Note that when downgrading participants to PTT mode a choice may be presented to the moderator (e.g., via a GUI) whether to hold the ports, in order to switch back to full duplex mode in the near future, or release them entirely. In a different scenario, the moderator may change the mode of communication of current participants from full-duplex to half-duplex mode to free up resources that may enable other users to join the meeting.
In
In yet another embodiment, a subset of the participants in the full-duplex conference may enter into a breakout or sidebar session, with the conferencing server automatically switching the sidebar participants into a PTT session. In another implementation, the sidebar session is created as a PTT session between the sidebar participants only in the event that the conferencing server no longer has available ports or other necessary resources for you full-duplex sidebar session. When the sidebar participants end their breakout session, they may be automatically returned to full-duplex mode, assuming, of course, that the necessary conferencing resources (e.g., ports) are still available.
It is appreciated that a variety of token-based floor control algorithms or paradigms may be applied to the entire conference in order to improve the experience of the PTT speaker to the conference session. For example, whenever a PTT user wants to say something to all of the conference participants, he first gains access to the floor via the floor control algorithm running on the PTT server. At the point where an audio stream arrives at a slot or port of the mixer of the conferencing server, that event may trigger a transition in the conferencing server wherein a token-based scheme is imposed on the regular conference participants. In other words, only one person may be allowed to speak at a time. In this way, a PTT speaker does not miss out on any other discussions that might otherwise occur while he is speaking.
It should be understood that elements of the present invention may also be provided as a computer program product which may include a machine-readable medium having stored thereon instructions which may be used to program a computer (e.g., a processor or other electronic device) to perform a sequence of operations. Alternatively, the operations may be performed by a combination of hardware and software. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnet or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions. For example, elements of the present invention may be downloaded as a computer program product, wherein the program may be transferred from a remote computer or telephonic device to a requesting process by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., a modem or network connection).
Additionally, although the present invention has been described in conjunction with specific embodiments, numerous modifications and alterations are well within the scope of the present invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Number | Name | Date | Kind |
---|---|---|---|
5483587 | Hogan et al. | Jan 1996 | A |
5600366 | Schulman | Feb 1997 | A |
5673253 | Shaffer | Sep 1997 | A |
5729687 | Rothrock et al. | Mar 1998 | A |
5917830 | Chen et al. | Jun 1999 | A |
5963217 | Grayson et al. | Oct 1999 | A |
6044081 | Bell et al. | Mar 2000 | A |
6137834 | Wine et al. | Oct 2000 | A |
6141324 | Abbott et al. | Oct 2000 | A |
6236854 | Bradshaw | May 2001 | B1 |
6269107 | Jong | Jul 2001 | B1 |
6332153 | Cohen | Dec 2001 | B1 |
6501739 | Cohen | Dec 2002 | B1 |
6505169 | Bhagavath et al. | Jan 2003 | B1 |
6608820 | Bradshaw | Aug 2003 | B1 |
6671262 | Kung et al. | Dec 2003 | B1 |
6675216 | Quatrano et al. | Jan 2004 | B1 |
6718553 | Kenworthy | Apr 2004 | B2 |
6735572 | Landesmann | May 2004 | B2 |
6744785 | Robinett et al. | Jun 2004 | B2 |
6771644 | Brassil et al. | Aug 2004 | B1 |
6771657 | Elstermann | Aug 2004 | B1 |
6775247 | Shaffer et al. | Aug 2004 | B1 |
6816469 | Kung et al. | Nov 2004 | B1 |
6876734 | Summers et al. | Apr 2005 | B1 |
6865540 | Faber et al. | Aug 2005 | B1 |
6925068 | Stanwood et al. | Aug 2005 | B1 |
6931001 | Deng | Aug 2005 | B2 |
6931113 | Ortel | Aug 2005 | B2 |
6937569 | Sarkar et al. | Aug 2005 | B1 |
6947417 | Laursen et al. | Sep 2005 | B2 |
6956828 | Simard et al. | Oct 2005 | B2 |
6959075 | Cutaia et al. | Oct 2005 | B2 |
6976055 | Shaffer et al. | Dec 2005 | B1 |
6989856 | Firestone et al. | Jan 2006 | B2 |
7003086 | Shaffer et al. | Feb 2006 | B1 |
7007098 | Smyth et al. | Feb 2006 | B1 |
7084898 | Firestone et al. | Aug 2006 | B1 |
20010000540 | Cooper et al. | Apr 2001 | A1 |
20020052214 | Maggenti et al. | May 2002 | A1 |
20020087976 | Kaplan et al. | Jul 2002 | A1 |
20030016632 | Refai et al. | Jan 2003 | A1 |
20030076850 | Jason, Jr. | Apr 2003 | A1 |
20030198195 | Li | Oct 2003 | A1 |
20040057449 | Black | Mar 2004 | A1 |
20040165710 | DelHoyo et al. | Aug 2004 | A1 |
20040213152 | Matuoka et al. | Oct 2004 | A1 |
20050069102 | Chang | Mar 2005 | A1 |
20050078171 | Firestone et al. | Apr 2005 | A1 |
20050081244 | Barrett et al. | Apr 2005 | A1 |
20060020995 | Opie et al. | Jan 2006 | A1 |
20060189337 | Farrill et al. | Aug 2006 | A1 |
20070110029 | Gilmore et al. | May 2007 | A1 |
20070123284 | Schliwa-Bertling et al. | May 2007 | A1 |
20070133435 | Eneroth et al. | Jun 2007 | A1 |
Number | Date | Country |
---|---|---|
1 553 735 | Jul 2005 | EP |
Number | Date | Country | |
---|---|---|---|
20070239885 A1 | Oct 2007 | US |