Note: Descriptions are shown in the official language in which they were submitted.
CA 02793374 2012-10-26
= Moderation Control Method for Participants in a Heterogeneous Conference
Call
FIELD
[0001] Example embodiments relate to conference call systems and
methods, and in
particular to a method for controlling moderation when conferences are
combined to form a
heterogeneous conference call.
BACKGROUND
[0002] In general, there are three common conference hosting systems
for executing
conferencing calls: using a mobile device as the conference bridge (mobile
bridge), using an
intermediate conference server (for example a private branch exchange (PBX)),
and using a
conference bridge. The mobile bridge typically provides the fewest number of
participants and
number of moderator controls. The intermediate conference server generally can
host larger
conferences and provide an increased number of moderator controls.
Additionally, the conference
bridge generally can host an even larger number of participants and generally
provides the moderator
with the most controls.
[0003] Currently, the methods of generating conference calls are
generally limited to a single
conference hosting system. For example, a conference call is hosted either by
only the intermediate
conference server or only the conference bridge. The system independence can
lead to problems of
scalability when the participant level of the conference hosting system
reaches its maximum limit.
For example, a mobile bridge can only have a participant limit of three
devices. Thus, if there are
three conference call participants and if another participant will need to be
added to the conference
call, the conference call must be terminated. The conference call must then be
implemented using a
conference hosting system with additional resources, for example, the
intermediate conference server
or the conference bridge. Thus, necessitating that all of the conference call
participants be-
reconnected into the conference using the intermediate conference server.
[0004] Additionally, moderation controls are specific to the hosting
system and currently
there is no method of establishing, maintaining, or transferring moderation
control in heterogeneous
conferences (a teleconference that includes a plurality of different
conference hosting systems).
- 1 -
CA 02793374 2012-10-26
'
,
- BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Reference will now be made to the accompanying drawings showing
example
embodiments of the present application, and in which:
[0006] Figure 1 shows, in block diagram form, an example system
utilizing a conference call
scheduling system;
[0007] Figure 2 shows a block diagram illustrating a mobile
communication device in
accordance with an example embodiment;
[0008] Figure 3A shows an example conference call using a mobile
bridge;
[0009] Figure 3B shows an example heterogeneous conference call with a
mobile bridge and
an intermediate conference server;
[0010] Figure 3C shows an example heterogeneous conference call with a
mobile bridge, an
intermediate conference server, and a conference server;
[0011] Figure 3D shows the example heterogeneous conference call of
Figure 3C with a
moderator coupled via the intermediate conference server;
[0012] Figure 4 is a block diagram depicting example moderator control
system for
managing moderator controls in a heterogeneous conference;
[0013] Figure 5 illustrates an example moderator control graphical
user interface;
[0014] Figure 6A illustrates an example moderator control menu broken
down by participant
and participant C selected;
[0015] Figure 6B illustrates an example moderator control menu broken
down by participant
and participant B selected;
[0016] Figure 7 shows a flowchart representing an example method for
adding additional
conference hosting systems to create an expanded heterogeneous conference;
[0017] Figure 8A shows an example conference call using a mobile
bridge and a separate
conference call using an intermediate conference server;
[0018] Figure 8b shows an example conference call merged conference
call;
- 2 -
CA 02793374 2012-10-26
'
,
= [0019] Figure 9 shows a flowchart representing an example method
for merging one or more
conferences into a single heterogeneous conference; and
[0020] Figure 10 illustrates an example merge control menu.
DESCRIPTION OF EXAMPLE EMBODIMENTS
[0021] The example embodiments provided below describe a moderator
control system
and method where a moderator control window operating on a device (moderating
device) allows
a user (conference moderator) to merge a plurality of conference calls
(conferences), operating
using different types of conference hosting systems, into a single
heterogeneous conference. A
conference hosting system can be a mobile bridge, an intermediate conference
server (for
example a private branch exchange (PBX)), a conference bridge, or a media
server. A
heterogeneous conference is a conference call (audio, video, or a combination
thereof) that
includes a plurality of different conference hosting systems that are coupled
together through a
server. The moderator control system sends a merge control to the server,
wherein the server is
configured to establish conference connections with the conference hosting
systems of the
conferences being merged. The moderator control system determines the identity
of the
moderator of the heterogeneous conference; and automatically transfers one or
more moderator
controls to the moderator of the heterogeneous conference. Additionally, in
some embodiments,
there can be one or more sub-group moderators under the control of the
moderator.
[0022] The moderator controls associated with a participant of the
heterogeneous
conference depend on what conference hosting system the participant is
connected with.
Additionally, the controls available to the moderator can vary depending on
whether the
conference is an audio, video, or a combination thereof. Moreover, each
conference hosting
system can have set formats for controls in order for the controls to be
recognized by the
conference hosting system. When the moderator attempts to exercise a control
over a particular
participant of the heterogeneous conference, the control is sent to the server
that connects the
different conference hosting systems. In some embodiments, the control is
placed in the correct
format before sending to the server. In other embodiments, the server receives
the control and
properly formats it before sending it to the appropriate conference hosting
system.
- 3 -
CA 02793374 2012-10-26
,
- [0023] Additionally, when adding participants to the conference,
additional conference
hosting systems can be added to ensure that the participant limit of
heterogeneous conference is
not met. Some of the example embodiments below describe systems and methods
for adding
participants to a conference via additional conference hosting systems that
are added as needed.
[0024] Reference is now made to Figure 1, which shows, in block
diagram form, an example
system utilizing a moderator control system for managing moderator control in
heterogeneous
conferences, generally designated 100, for the control and management of
communications. System
100 includes an enterprise network 105, which in some embodiments includes a
local area network
(LAN). In some embodiments, enterprise network 105 can be an enterprise or
business system. In
some embodiments, enterprise network 105 includes more than one network and is
located in
multiple geographic areas.
[0025] Enterprise network 105 can be coupled often through a firewall
110, to a wide area
network (WAN) 115, such as the Internet. Enterprise network 105 can also be
coupled to a public
switched telephone network (PSTN) 128 via direct inward dialing (DID) trunks
or primary rate
interface (PRI) trunks.
[0026] Enterprise network 105 can also communicate with a public land
mobile network
(PLMN) 120, which is also referred to as a wireless wide area network (WWAN)
or, in some cases, a
cellular network. The connection with PLMN 120 is via a relay 125, as known in
the art.
[0027] In some embodiments, enterprise network 105 provides a wireless
local area network
(WLAN), not shown, featuring wireless access points, such as wireless access
point 125a. In some
embodiments, other WLANs can exist outside enterprise network 105. For
example, a WLAN
coupled to WAN 115 can be accessed via wireless access point 125b. WAN 115 is
coupled to one or
more mobile devices, for example mobile device 140. Additionally, WAN 115 can
be coupled to one
or more desktop or laptop computers 142 (one shown).
[0028] System 100 can include a number of enterprise-associated mobile
devices, for
example, mobile devices 130, 135, 136, and 140. Mobile devices 130, 135, 136,
and 140 can include
devices equipped for cellular communication through PLMN 120, mobile devices
equipped for Wi-
Fi communications over one of the WLANs via wireless access points 125a or
125b, or dual-mode
- 4 -
CA 02793374 2012-10-26
- devices capable of both cellular and WLAN communications. Wireless access
points 125a or 125b
can be configured to WLANs that operate in accordance with one of the IEEE
802.11 specifications.
[0029] Mobile devices 130, 135, 136, and 140 can be, for example,
cellular phones,
smartphones, tablets, netbooks, and a PDA (personal digital assistant) enabled
for wireless
communication. Moreover, mobile devices 130, 135, 136, and 140 can communicate
with other
components using voice communications or data communications (such as
accessing content from a
website). Mobile devices 130, 135, 136, and 140 include devices equipped for
cellular
communication through PLMN 120, devices equipped for Wi-Fi communications via
wireless access
points 125a or 125b, or dual-mode devices capable of both cellular and WLAN
communications.
Mobile devices 130, 135, 136, and 140 are described in detail below in Figure
2.
[0030] Mobile devices 130, 135, 136, and 140 also include one or more
radio transceivers
and associated processing hardware and software to enable wireless
communications with PLMN
120, and/or one of the WLANs via wireless access points 125a or 125b. In
various embodiments,
PLMN 120 and mobile devices 130, 135, 136, and 140 are configured to operate
in compliance with
any one or more of a number of wireless protocols, including GSM, GPRS, CDMA,
EDGE, UMTS,
EvD0, HSPA, 3GPP, or a variety of others. It will be appreciated that mobile
devices 130, 135, 136,
and 140 can roam within PLMN 120 and across PLMNs, in known manner, as their
user moves. In
some instances, dual-mode mobile devices 130, 135, 136, and 140 and/or
enterprise network 105 are
configured to facilitate roaming between PLMN 120 and a wireless access points
125a or 125b, and
are thus capable of seamlessly transferring sessions (such as voice calls)
from a connection with the
cellular interface of dual-mode device (i.e., 130, 135, 136, and 140) to a
WLAN interface of the dual-
mode device, and vice versa.
[0031] Each mobile device 130, 135, 136, and 140 has the ability to act
as a mobile bridge.
For example, mobile device 130 includes a mobile bridge system 133 that allows
mobile device 130
to act as the mobile bridge with mobile device 136. Mobile bridge system 133
can also be present in
one or more of mobile devices 135, 136, and 140. Generally, a conference call
hosted using a mobile
bridge will have a maximum of 3 participants. Moderator controls at the mobile-
bridge level include
adding additional participants, muting at least one participant, un-muting at
least one participant, and
- 5 -
CA 02793374 2012-10-26
= exiting the conference call. The particular moderator controls associated
with the mobile bridge can
vary depending on the type of mobile bridge used. Additionally, the controls
available to the
moderator can vary depending on whether the conference is an audio, video, or
a combination
thereof.
[0032] Enterprise network 105 typically includes a number of networked
servers, computers,
and other devices. For example, enterprise network 105 can connect one or more
desktop or laptop
computers 143 (one shown). The connection can be wired or wireless in some
embodiments.
Enterprise network 105 can also connect to one or more digital telephone
phones 160.
[0033] Relay 125 serves to route messages received over PLMN 120 from
mobile device 130
to corresponding enterprise network 105. Relay 125 also pushes messages from
enterprise network
105 to mobile device 130 via PLMN 120.
[0034] Enterprise network 105 also includes an enterprise server 150.
Together with relay
125, enterprise server 150 functions to redirect or relay incoming e-mail
messages addressed to a
user's e-mail address through enterprise network 105 to mobile device 130 and
to relay incoming e-
mail messages composed and sent via mobile device 130 out to the intended
recipients within WAN
115 or elsewhere. Enterprise server 150 and relay 125 together facilitate a
"push" e-mail service for
mobile device 130, enabling the user to send and receive e-mail messages using
mobile device 130
as though the user were coupled to an e-mail client within enterprise network
105 using the user's
enterprise-related e-mail address, for example on computer 143.
[0035] As is typical in many enterprises, enterprise network 105
includes a Private Branch
exchange (although in various embodiments the PBX can be a standard PBX or an
IP-PBX, for
simplicity the description below uses the term PBX to refer to both) 127
having a connection with
PSTN 128 for routing incoming and outgoing voice calls for the enterprise. PBX
127 is coupled to
PSTN 128 via DID trunks or PRI trunks, for example. PBX 127 can use ISDN
signaling protocols
for setting up and tearing down circuit-switched connections through PSTN 128
and related
signaling and communications. In some embodiments, PBX 127 can be coupled to
one or more
conventional analog telephones 129. PBX 127 is also coupled to enterprise
network 105 and, through
it, to telephone terminal devices, such as digital telephone sets 160,
softphones operating on
- 6 -
CA 02793374 2012-10-26
= computers 143, etc. Within the enterprise, each individual can have an
associated extension number,
sometimes referred to as a PNP (private numbering plan), or direct dial phone
number. Calls
= outgoing from PBX 127 to PSTN 128 or incoming from PSTN 128 to PBX 127
are typically circuit-
switched calls. Within the enterprise, for example, between PBX 127 and
terminal devices, voice
calls are often packet-switched calls, for example Voice-over-IP (VoIP) calls.
[0036] PBX 127 possesses an intermediate conferencing server
capability, and generally can
host a conference call with a predetermined maximum number of participants,
for example 3 to 7
participants. PBX127 is configured to allow the moderator to possess one or
more moderator
controls. For example, typical moderator controls at the intermediate
conference server level include
joining a conference call, muting a participant, un-muting a participant,
adding one or more
participants, and dropping one or more participants. The particular moderator
controls associated
with the intermediate conference server can vary depending on the type of
intermediate conference
server used. Additionally, the controls available to the moderator can vary
depending on whether the
conference is an audio, video, or a combination thereof.
[0037] System 100 includes one or more conference bridges 132.
Conference bridge 132 can
be part of enterprise network 105. Additionally, in some embodiments,
conference bridge 132 can be
accessed via WAN 115 or PTSN 128.
[0038] Conference bridge 132 generally is configured to host conference
calls with a
maximum number of participants numbering in the 100s or more (for example,
1000). Conference
bridge 132 is configured such that the moderator possesses a plurality of
moderator controls.
Conference bridge 132 moderator controls can include joining a conference
call, muting one or more
participants, speaking priority (i.e. when moderator speaks all participants
are muted), listener mode,
exiting the conference call, dropping one or more participants, recording the
transcript of the
conference call, creating side conferences, voting, raising hand, etc.
Conferences hosted using
conference bridge 132 typically have a larger maximum number of participants
and a larger number
of moderator controls. The particular moderator controls associated with the
conference bridge can
vary depending on the type of conference bridge used. Additionally, the
controls available to the
- 7 -
CA 02793374 2012-10-26
'
= moderator can vary depending on whether the conference is an audio,
video, or a combination
thereof.
[0039] Enterprise network 105 can further include a Service Management
Platform (SMP)
165 for performing some aspects of messaging or session control, like call
control and advanced call
processing features. Service Management Platform (SMP) can have one or more
processors and at
least one memory for storing program instructions. The processor(s) can be a
single or multiple
microprocessors, field programmable gate arrays (FPGAs), or digital signal
processors (DSPs)
capable of executing particular sets of instructions. Computer-readable
instructions can be stored on
a tangible non-transitory computer-readable medium, such as a flexible disk, a
hard disk, a CD-ROM
(compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital
versatile disk-
read only memory), a DVD RAM (digital versatile disk-random access memory), or
a semiconductor
memory. Alternatively, the methods can be implemented in hardware components
or combinations
of hardware and software such as, for example, ASICs, special purpose
computers, or general
purpose computers. SMP 165 is configured to connect different conference
systems to create a
heterogeneous conference, for example, a single teleconference, where
participants can be joined to
the conference via a mobile bridge and an intermediate conference server.
[0040] Moderator control system 400 can include one or more processors
(not shown), a
memory (not shown), and a data interface (not shown). The processor(s) can be
a single or multiple
microprocessors, field programmable gate arrays (FPGAs), or digital signal
processors (DSPs)
capable of executing particular sets of instructions. Computer-readable
instructions can be stored on
a tangible non-transitory computer-readable medium, such as a flexible disk, a
hard disk, a CD-ROM
(compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital
versatile disk-
read only memory), a DVD RAM (digital versatile disk-random access memory), or
a semiconductor
memory. Alternatively, the methods can be implemented in hardware components
or combinations
of hardware and software such as, for example, ASICs, special purpose
computers, or general
purpose computers. Moderator control system 400 can be implemented on a mobile
device, a single
computer, distributed across a plurality of computers, or some combination
thereof.
[0041] Reference is now made to Figure 2 which illustrates in detail
mobile device 130 in
- 8 -
CA 02793374 2012-10-26
= which example embodiments can be applied. Note that while Figure 2 is
described in reference to
mobile device 130, it also applies to mobile devices 135, 136, and 140. Mobile
device 130 is a two-
way communication device having data and voice communication capabilities, and
the capability to
communicate with other computer systems, for example, via the Internet.
Depending on the
functionality provided by mobile device 130, in various embodiments mobile
device 130 can be a
handheld device, a multiple-mode communication device configured for both data
and voice
communication, a smartphone, a mobile telephone, a tablet, or a PDA (personal
digital assistant)
enabled for wireless communication.
[0042] Mobile device 130 includes a rigid case (not shown) housing the
components of
mobile device 130. The internal components of mobile device 130 can, for
example, be constructed
on a printed circuit board (PCB). The description of mobile device 130 herein
mentions a number of
specific components and subsystems. Although these components and subsystems
can be realized as
discrete elements, the functions of the components and subsystems can also be
realized by
integrating, combining, or packaging one or more elements in any suitable
fashion.
[0043] Mobile device 130 includes a controller comprising at least one
processor 240 (such
as a microprocessor), which controls the overall operation of mobile device
130. Processor 240
interacts with device subsystems such as a communication systems 211 for
exchanging radio
frequency signals with the wireless network (for example WAN 115 and/or PLMN
120) to perform
communication functions. Processor 240 interacts with additional device
subsystems including a
display 204 such as a liquid crystal display (LCD) screen or any other
appropriate display, input
devices 206 such as a keyboard and control buttons, persistent memory 244,
random access memory
(RAM) 246, read only memory (ROM) 248, auxiliary input/output (I/0) subsystems
250, data port
252 such as a conventional serial data port or a Universal Serial Bus (USB)
data port, speaker 256,
microphone 258, short-range communication subsystem 262 (which can employ any
appropriate
wireless (for example, RF), optical, or other short range communications
technology), and other
device subsystems generally designated as 264. Some of the subsystems shown in
Figure 2 perform
communication-related functions, whereas other subsystems can provide
"resident" or on-device
functions.
- 9 -
CA 02793374 2012-10-26
- [0044] Display 204 can be realized as a touch-screen display in some
embodiments. The
touch-screen display can be constructed using a touch-sensitive input surface
coupled to an electronic
controller and which overlays the visible element of display 204. The touch-
sensitive overlay and the
electronic controller provide a touch-sensitive input device and processor 240
interacts with the
touch-sensitive overlay via the electronic controller.
[0045] Communication systems 211 includes one or more communication
systems for
communicating with wireless WAN 115 and wireless access points 125a and 125b
within the
wireless network. The particular design of communication systems 211 depends
on the wireless
network in which mobile device 130 is intended to operate. Mobile device 130
can send and receive
communication signals over the wireless network after the required network
registration or activation
procedures have been completed.
[0046] Processor 240 operates under stored program control and executes
software modules
221 stored in memory such as persistent memory 244 or ROM 248. Processor 240
can execute code
means or instructions. ROM 248 can contain data, program instructions or both.
Persistent memory
244 can contain data, program instructions, or both. In some embodiments,
persistent memory 244 is
rewritable under control of processor 240, and can be realized using any
appropriate persistent
memory technology, including EEPROM, EAROM, FLASH, and the like. As
illustrated in Figure 2,
software modules 221 can include operating system software 223. Additionally,
software modules
221 can include software applications 225.
[0047] In some embodiments, persistent memory 244 stores user-profile
information,
including, one or more conference dial-in telephone numbers. Persistent memory
244 can
additionally store identifiers related to particular conferences. Persistent
memory 244 can also store
information relating to various people, for example, name of a user, a user's
identifier (user name,
email address, or any other identifier), place of employment, work phone
number, home address, etc.
[0048] Software modules 221, for example, moderator control system 400,
or parts thereof
can be temporarily loaded into volatile memory such as RAM 246. RAM 246 is
used for storing
runtime data variables and other types of data or information. In some
embodiments, different
assignment of functions to the types of memory could also be used.
- 10 -
CA 02793374 2012-10-26
- [0049] Software applications 225 can further include a range of
applications, including, for
example, an application related to a moderator control system, e-mail
messaging application, address
book, calendar application, notepad application, Internet browser application,
voice communication
(i.e., telephony) application, mapping application, or a media player
application, or any combination
thereof. Each of software applications 225 can include layout information
defining the placement of
particular fields and graphic elements (for example, text fields, input
fields, icons, etc.) in the user
interface (i.e., display 204) according to the application.
[0050] In some embodiments, auxiliary input/output (I/0) subsystems 250
comprise an
external communication link or interface, for example, an Ethernet connection.
In some
embodiments, auxiliary I/0 subsystems 250 can further comprise one or more
input devices,
including a pointing or navigational tool such as a trackpad, touchpad,
joystick, clickable trackball or
scroll wheel or thumbwheel, or one or more output devices, including a
mechanical transducer such
as a vibrator for providing vibratory notifications in response to various
events on the mobile device
130 (for example, receipt of an electronic message or incoming phone call), or
for other purposes
such as haptic feedback (touch feedback).
[0051] In some embodiments, mobile device 130 also includes one or more
removable
memory modules 230 (typically comprising FLASH memory) and one or more memory
module
interfaces 232. Among possible functions of removable memory module 230 is to
store information
used to identify or authenticate a user or the user's account to the wireless
network (for example
WAN 115 and/or PLMN 120). For example, in conjunction with certain types of
wireless networks,
including GSM and successor networks, removable memory module 230 is referred
to as a
Subscriber Identity Module or SIM. Memory module 230 is inserted in or coupled
to memory
module interface 232 of mobile device 130 in order to operate in conjunction
with the wireless
network.
[0052] Mobile device 130 stores data 227 in persistent memory 244. In
various
embodiments, data 227 includes service data comprising information required by
mobile device 130
to establish and maintain communication with the wireless network (for example
WAN 115 and/or
PLMN 120). Data 227 can also include, for example, scheduling and connection
information for
- 11 -
CA 02793374 2012-10-26
= connecting to a scheduled call. Data 227 can include moderator control
system data used by mobile
device 130 for various tasks. For example, to add participants in a
heterogeneous conference call, to
provide moderator control over a heterogeneous conference call to mobile
device 130 when mobile
device 130 acts as a moderator device, to determine moderator identity when
one or more
conferences are merged with an existing conference to create a single
heterogeneous conference, and
to transfer moderator control from mobile device 130 to another heterogeneous
conference
participant, etc.
[0053] Mobile device 130 also includes a battery 238 which furnishes
energy for operating
mobile device 130. Battery 238 can be coupled to the electrical circuitry of
mobile device 130
through a battery interface 236, which can manage such functions as charging
battery 238 from an
external power source (not shown) and the distribution of energy to various
loads within or coupled
to mobile device 130. Short-range communication subsystem 262 is an additional
optional
component which provides for communication between mobile device 130 and
different systems or
devices, which need not necessarily be similar devices. For example, short-
range communication
subsystem 262 can include an infrared device and associated circuits and
components, or a wireless
bus protocol compliant communication mechanism such as a BLUETOOTH
communication module
to provide for communication with similarly-enabled systems and devices.
[0054] A predetermined set of applications that control basic device
operations, including
data and possibly voice communication applications can be installed on mobile
device 130 during or
after manufacture. Additional applications and/or upgrades to operating system
software 223 or
software applications 225 can also be loaded onto mobile device 130 through
the wireless network
(for example WAN 115 and/or PLMN 120), auxiliary I/0 subsystem 250, data port
252, short-range
communication subsystem 262, or other suitable subsystem 264. The downloaded
programs or code
modules can be permanently installed, for example, written into the program
memory (for example
persistent memory 244), or written into and executed from RAM 246 for
execution by processor 240
at runtime.
[0055] Mobile device 130 can provide three principal modes of
communication: a data
communication mode, a voice communication mode, and a video communication mode
In the data
- 12 -
CA 02793374 2012-10-26
= communication mode, a received data signal such as a text message, an e-
mail message, Web page
download, or an image file are processed by communication systems 211 and
input to processor 240
for further processing. For example, a downloaded Web page can be further
processed by a browser
application, or an e-mail message can be processed by an e-mail message
messaging application and
output to display 204. A user of mobile device 130 can also compose data
items, such as e-mail
messages, for example, using the input devices in conjunction with display
204. These composed
items can be transmitted through communication systems 211 over the wireless
network (for
example WAN 115 and/or PLMN 120). In the voice communication mode, mobile
device 130
provides telephony functions and operates as a typical cellular phone. In the
video communication
mode, mobile device 130 provides video telephony functions and operates as a
video teleconference
term. In the video communication mode, mobile device 130 utilizes one or more
cameras (not
shown) to capture video of video teleconference. Additionally, in some
embodiments, mobile device
130 utilizes the one or more cameras to capture video. The video can be stored
as one or more video
data files in persistent memory 244, RAM 248, memory module 230, or any other
data storage
medium.
[0056]
Figure 3A illustrates an example conference (audio or video) between
participant A
on a mobile device and participant B where mobile device is acting as a mobile
bridge 305. The
mobile device used by the moderator of the conference is referred to as the
moderator device. In
Figures 3A-3D the moderator devices are shown using "circles." In Figure 3A,
the moderator of the
conference is participant A. If a conference participant decides to add
participant C, the moderator
device (for example, mobile device 130) automatically communicates with a
server 300 (for
example, SMP 165) to join participant C using an additional conference hosting
system. In some
embodiments, any mobile device can add additional participants. In other
embodiments, only the
moderator device can add additional participants. Figure 3B illustrates a
heterogeneous conference
utilizing mobile bridge 305 to connect participant A and participant B and
server 300 (for example,
SMP 165), and a connection with participant C via an intermediate conference
server 310 (for
example PBX 127). Additional participants can then be added until the
conference hosting systems
have reached some maximum number of participants. This maximum value can be
determined
automatically by the moderator control system located on the mobile device of
participant A. Or in
- 13 -
CA 02793374 2012-10-26
- some embodiments, the maximum value is automatically determined by server
300 or by one of the
conferencing hosting systems included within the heterogeneous conferences, or
some combination
thereof Additionally, in some embodiments the moderator can set the maximum
participant value to
a value one or more below the actual maximum of the heterogeneous conference.
Once the
maximum participant value occurs server 300 is configured to automatically
conference in an
additional conference resource, for example, a conference bridge 320 (can
correspond to conference
bridge 132), thus creating an expanded heterogeneous conference. In some
embodiments, discussed
below in reference to Figure 4, the moderator control system 400 is configured
to automatically
conference in an additional conference resource without using server 300.
Figure 3C illustrates a
heterogeneous conference utilizing mobile bridge 305, server 300, intermediate
conference server
310, and conference bridge 320.
[0057] Additionally, server 300 is configured to communicate with the
moderating device of
the heterogeneous conference to ensure the moderating device retains moderator
control over other
participants in the heterogeneous conference. The amount of moderator control
depends on how the
participant is coupled to the heterogeneous conference. For example, in Figure
3C moderator A has
moderator control at the level of mobile bridge 305 in connection with
participant B, because
participant B is coupled to the conference via mobile bridge 305. In contrast,
moderator A has
moderator control at the level of intermediate conference server 310 in
connection with participants
C - K because participants C - K are coupled to the conference via
intermediate conference server
310. Likewise, moderator A has moderator controls at the level of conference
bridge 320 in
connection with participants L-X because participants L-X are coupled to the
conference via
conference bridge 320.
[0058] Additionally, the location of the moderator within the
heterogeneous conference
makes no difference in terms of the moderator control available to the
moderator over participants in
the heterogeneous conference. For example, Figure 3D illustrates that
participant C is the moderator
of the heterogeneous conference. The moderator control provided to moderator
C, however, is in
relation to the location of the participant being regulated. Thus, moderator C
has moderator control
over conference participants A-B, participants D-K, and participants L-X, at
the level of mobile
bridge 305, an intermediate conference server 310, and a conference bridge
320, respectively.
- 14 -
CA 02793374 2012-10-26
- [0059] Referring back to Figure 3C, server 300 is also configured to
assist in transferring
moderator control between devices joined in a heterogeneous conference. For
example, when
moderator A transfers moderator control to participant C. The moderating
device communicates with
server 300 and participant C's device (for example, mobile device 135) to pass
moderation control to
participant C. In some embodiments not shown, the moderator control system 400
is configured to
automatically pass moderation control to participant C without using server
300.
[0060] Referring back to Figure 1, collectively SMP 165, conference
bridge 132, and PBX
127 is referred to as the enterprise communications platform, generally
designated 180. It will be
appreciated that enterprise communications platform 180 and, in particular,
SMP 165, is
implemented on one or more servers having suitable communications interfaces
for connecting to
and communicating with PBX 127, conference bridge 132 and DID/PRI trunks.
Although SMP 165
can be implemented on a stand-alone server, it will be appreciated that it can
be implemented into an
existing control agent/server as a logical software component.
[0061] Mobile device 130 has a moderator control system 400 and is in
communication with
enterprise network 105. In some example embodiments, moderator control system
300 also operates
on mobile devices 135, 136, and 140, computers 142 and 143, digital phone 160,
or any variation
thereof. In some embodiments, moderator control system 400 is in communication
with and operates
as part of a conference call program installed on mobile devices 130, 135,
136, and 140, and other
servers on enterprise network 105, for example, SMP 165. Additionally, in some
embodiments,
moderator control system 400 is integral to the conference call program.
[0062] Figure 4 is a block diagram depicting example moderator control
system 400. As
illustrated, moderator control system 400 includes an interface module 410, a
control module 420, a
communication module 430, and a data storage module 440. It is appreciated
that one or more of
these modules can be deleted, modified, or combined together with other
modules.
[0063] Interface module 410 displays the moderator controls and enables
selection of
moderator controls. For example, interface module 410 enables the user to
select different moderator
controls. Interface module 410 can be coupled to control module 420,
communication module 430,
and data storage module 440. Figure 5 illustrates an example moderator
controls graphical user
- 15 -
CA 02793374 2015-11-23
interface (GUI) 500 generated by interface module 410, displaying global
controls 510.
Global controls 510 can include one or more controls, for example add
participant,
mute/unmute a participant, join/drop a participant, and merge. The above
listing of controls
is not exclusive, and can include other moderator controls not listed.
Additionally, the
controls available to the moderator can vary depending on whether the
conference is an
audio, video, or a combination thereof The add participant control allows the
moderator to
add an additional participant. The add participant control acquires a list of
potential
participants from a contact list associated with the moderator. The contact
list can be stored
in data storage module 440. Moderator controls GUI 500 displays the potential
list of
participants to the moderator. In a heterogeneous conference, after the
moderator designates
which participant is to be added, mobile device 130 communicates with a server
(for
example, SMP 165) to add the selected participant via one of the conference
hosting systems
included in the heterogeneous conference. The method of adding the additional
participant is
discussed below with reference to Figure 7.
[0064] Global controls 510 can include a number of controls. For example,
a mute
control that mutes the moderator with respect to the rest of the conference, a
speaker priority
control mute all the participants when the moderator speaks. The join control
allows the
moderator to join one or more other conferences as a participant of those
conferences.
Additionally, in some embodiments, there is an exit conference control (not
shown) that
allows the moderator to leave the heterogeneous conference. In some
embodiments, when the
exit control is executed, the moderator control system can prompt the
moderator to transfer
moderator control to another conference participant before leaving the
heterogeneous
conference.
[0065] Global controls 510 also can include merge control 530. Merge
control 530
allows the moderator to merge one or more conferences with the existing
conference. In some
embodiments, the moderator is acting as the moderator of at least one of the
conferences
being merged. The above listing of controls is not exclusive, and can include
other moderator
controls not listed. Merging one or more conferences is discussed in detail
below in reference
to Figures 8-10.
[0066] Additionally, Figure 5 illustrates a By Participant button 520.
Selecting By
Participant button 520 displays a listing of participants of the heterogeneous
conference and
the
-16-
CA 02793374 2012-10-26
associated moderator control over the participants in the listing. For
example, the moderator will
have the most control in relation to participants coupled to the heterogeneous
conference via a
conference bridge and the least controls in relation to participants coupled
to the heterogeneous
conference via a mobile bridge (for example mobile bridge 305).
[0067] Figure 6A illustrates an example menu display opened when By
Participant button
520 is selected. Participants 610 lists all the participants in the
heterogeneous conference call.
Controls 620 lists the available controls that the moderator has for each
participant. When the
moderator highlights a particular participant, for example, participant C, the
available controls are
displayed as active in controls 620. Participant C can be coupled to the
heterogeneous conference via
a conference bridge(for example conference bridge 132), accordingly all the
controls associated with
the conference bridge are listed in the control listing 620 as corresponding
to participant C. Likewise,
if participant C were coupled to the conference via an intermediate conference
server, then all the
controls associated with the intermediate conference server would be listed in
the control listing 620
as corresponding to participant C.
[0068] In some embodiments, controls 620 includes all the moderator
controls available
regardless of whether the controls are used for a particular participant. In
this embodiment, when a
participant is selected from participants 610, moderator controls that are not
available are displayed
as being inactive controls 630. For example, Figure 6B illustrates a menu
where participant B is
highlighted. Participant B is coupled to the heterogeneous conference using a
mobile bridge,
accordingly the moderator control over participant B is less than moderator
control over participant
C, which is coupled to the heterogeneous conference via the conference bridge.
In this example,
moderator control associated with a mobile bridge are limited to mute, drop,
and transfer moderator
control. In this example, inactive controls 630 in relation to participant B
include, side conference
and record. In some embodiments, as additional conference hosting systems with
new controls are
added to the heterogeneous conference, the new controls are added to controls
620. Likewise, if a
particular conference hosting system is removed from the heterogeneous
conference that has
moderator controls specific to the particular conference hosting system, those
controls are removed
from controls 620. Control module 420 is configured to track what level of
moderator control is
available over each heterogeneous conference participant. When a control is
asserted in relation to a
- 17 -
CA 02793374 2012-10-26
= participant coupled via a particular conference hosting system, control
module 420 communicates
with a server (for example, server 300) via communication module 430 to
execute the selected
control. For example, if the moderator exercises the mute control over the
participant, control
module 420 would transmit this control to the server, which would then re-
transmit the mute control
to the particular conference hosting system which then mutes the participant.
Because the conference
is heterogeneous, the format of the controls can be different depending on how
the participant is
coupled to the heterogeneous conference. For example, referring to Figure 3C,
a mute control to be
exercised over participant C is formatted such that it is recognized by
intermediate conference server
310. Whereas, the same mute control, sent to participant L coupled to the
heterogeneous conference
via conference bridge 320, can require a different format for conference
bridge 320 to recognize the
control. Server 300 receives controls from control module 420 and
automatically formats them to
conform with the protocols of the conference hosting systems coupled to the
heterogeneous
conference. Referring back to Figure 4, in some embodiments, moderator control
system 400 places
the controls in the appropriate format before sending them to the server,
which then relays the
controls to the appropriate conference hosting system. Additionally, in some
embodiments moderator
control system 400 directly sends the properly formatted controls to the
conference hosting systems
which make up the heterogeneous conference. Additionally, in some embodiments,
moderator
control system 400 is configured to send conference information to one or more
conference
participants. Conference information can include number of conference
participants, identity of
conference participants, and roles of conference participants (acting as a
moderator or a subgroup
moderator). Control module 420 can be coupled to interface module 410,
communication module
430, and data storage module 440.
[0069]
Communication module 430 is configured to transmit moderator controls, via
enterprise network 105, PLMN 120, WAN 115, or some combination thereof, to
server 300 (for
example, SMP 165). Additionally, in some embodiments communication module 430
directly sends
properly formatted controls to the conference hosting systems which make up
the heterogeneous
conference. In some embodiments, communication module 430 sends conference
information to one
or more conference participants. In some embodiments, communication module 430
can store a
- 18 -
CA 02793374 2012-10-26
= record of the communications sent and received in data storage module
440. Communication module
430 can be coupled to interface module 410, control module 420, and data
storage module 440.
[0070] Data storage module 440 can also include a database, one or more
computer files in a
directory structure, or any other appropriate data storage mechanism such as a
memory. Additionally,
in some embodiments, data storage module 440 stores user profile information,
including, one or
more conference dial in telephone numbers, identifiers associated with
particular conferences,
information relating to various people, for example, name, place of
employment, work phone
number, home address, etc., and conference information. Conference information
can include
number of conference participants, identity of conference participants, and
roles of conference
participants (acting as a moderator or a subgroup moderator). In some example
embodiments, data
storage module 440 is distributed across one or more network servers. Data
storage module 440 can
communicate with interface module 410, control module 420, and communication
module 430.
[0071] Each of modules 410, 420, 430, and 440 can be software programs
stored in a RAM,
a ROM, a PROM, a FPROM, or other dynamic storage devices, or persistent memory
for storing
information and instructions.
[0072] Figure 7 is a flowchart representing an example method for
adding participants to
create a heterogeneous conference. While the flowchart discloses the following
steps in a particular
order, it is appreciated that at least some of the steps can be moved,
modified, or deleted where
appropriate.
100731 In step 710, a moderator control system receives a control to
add an additional
participant. In step 720, moderator control system automatically determines
whether the participant
limit of the heterogeneous conference has been reached. If the hosting systems
that make up the
heterogeneous conference have not reached the participant limit, the new
participant is added (step
730). The moderator device then updates the moderator controls to include the
newly added
participant (step 740). If, however, the participant limit would be reached,
then the server adds the
participant using an additional conference hosting system and notifies the
moderator device that the
participant has been added (step 750). For example, the new participant can be
added using an
additional mobile bridge, intermediate conference server, conference bridge,
or media server. In
- 19 -
CA 02793374 2012-10-26
some embodiments, not shown, the moderator control system is configured to add
the participant
using the additional conference hosting system.
100741 The moderator device then updates the moderator controls to
include the newly added
participant (step 740). This process continues indefinitely until all
participants are added to the
heterogeneous conference. Additionally, in some embodiments the combination of
hosting systems
that make up the heterogeneous conference does not matter. For example, the
heterogeneous
conference can use a plurality of mobile bridges, intermediate conference
servers, and conference
bridges.
100751 Figure 8A shows an example homogeneous (single conference hosting
platform)
conference call 800 using a mobile bridge, and a separate homogeneous
conference call 810 using an
intermediate conference server 820. The moderator of conference call 800 is
moderator A, and
conference call 800 has a single participant B. Because conference call 800 is
using the mobile
bridge, only moderator controls associated with the mobile bridge are
available to moderator A.
Generally, moderator control in conferences held via a mobile bridge is
minimal, as are the number
of allowed participants. For example, mute, drop, and transfer, are controls
that could be available to
moderator A to exercise over participant B in conference call 800.
100761 The moderator of conference call 810 is moderator C, and
conference call 810 has a
plurality of participants in addition to moderator C. Because conference call
810 is using the
intermediate conference server 820, only moderator controls associated with
the intermediate
conference server 820 are available to moderator C. Generally, moderator
control in conferences held
via intermediate conference servers are more than numerous, as are the number
of allowed
participants, than moderator control associated with conferences held via
mobile bridges. For
example, mute, drop, transfer, and join, are controls that could be available
to moderator C to
exercise over participants in conference call 810.
[0077] Figure 9 is a flowchart representing an example method for
establishing moderator
control when merging one or more conferences to create a single heterogeneous
conference using a
moderator controls system. While the flowchart discloses the following steps
in a particular order, it
is appreciated that at least some of the steps can be moved, modified, or
deleted where appropriate.
- 20 -
CA 02793374 2012-10-26
[0078] In step 910, a moderating device acquires a merge input, in the
form of a merge
control. For example, referring to Figure 5, an example merge control 530 is
listed on the moderator
controls GUI 500. Merge control 530 is used to merge one or more conferences
with the conference
being moderated by the moderating device. The one or more conferences can be
hosted using the
same type or different types of hosting systems. For example, the moderator
can merge a conference
hosted on a conference bridge and a separate conference hosted on an
intermediate conference server
to an existing conference that the moderator is controlling. In some
embodiments, the moderator can
be a participant in the one or more conferences that are being merged, but not
have moderator
control. Figure 10 illustrates an example merge control menu 1010. If merge
control 530 is selected,
the merge controls menu 1010 opens from which the moderator can select which
conferences to be
merged with the existing conference. Merge control menu 1010 includes a
listing of conferences
1020 that the moderator can select for merging. Conferences listing 1020
displays potential
conferences to merge via a dial-in number or an associated identifier, for
example, US Group 1040.
If the moderator selects a particular conference from conferences listing
1020, it is displayed under
selected conferences 1030. For example, in Figure 10, US Group conference 1040
is selected and is
displayed in the selected field 1050. The moderator can then select the merge
button 1060 to execute
the merge of the conference US Group with the existing conference the
moderator is currently
moderating.
[0079] Referring back to Figure 9, in step 920, the moderator device
communicates with a
server to merge the one or more conferences, for example US Group 1040 with
the existing
conference. The server establishes the appropriate connections with conference
hosting systems of
the one or more conferences being merged. In some embodiments not shown, the
moderator device
can directly establish the appropriate connections with the conference hosting
systems.
[0080] Each of the one or more conferences prior to merging have their
own moderator (pre-
merge moderator). After merging the calls into a single heterogeneous
conference, however, only one
moderator exists. In step 930, the moderator control system determines the
moderator identity. In
some embodiments, the moderator control system is configured to automatically
make the pre-merge
moderator who is merging the conference calls the moderator. In other
embodiments, the moderator
control system prompts each of the pre-merge moderators to determine who shall
retain moderator
- 21 -
CA 02793374 2012-10-26
control. Additionally, in some embodiments moderator control system
automatically passes
moderator control to the pre-merge moderator with the largest number of
participants. In some
embodiments not shown, one or more of the pre-merge moderators who are not
identified as the
moderator of the merged heterogeneous conference can become a sub-group
moderator. The sub-
group moderator retains limited moderator control over the participants it
controlled in the pre-merge
conference. For example, in Figure 8A the pre-merge moderators are
participants A and C. If these
separate conferences were to merge (Figure 8B), the moderator control system
would determine a
moderator for the merged conference (moderator A) and, in this embodiment,
would also identify
participant C as a sub-group moderator. Sub-group moderator C retains limited
moderator control
over participants D to K who are coupled to the conference via intermediate
conference server 820.
The controls of the sub-group moderator can be greater than, the same as, or
less than the controls
available to the sub-group moderator pre-merge.
[0081] In step 940, moderator control over all the participants in the
merged heterogeneous
conference is transferred to the moderator. The level of moderator control a
moderator has over a
particular participant is dependent on how the participant is coupled to the
heterogeneous conference.
In particular, it depends on the controls associated with the conference
hosting system that the
participant is using to connect to the heterogeneous conference. For example,
referring to Figure 8A,
moderator A can merge conference call 800 with conference call 810 resulting
in a single
heterogeneous conference call 830 as shown in Figure 8B. Participant B is
coupled to the
heterogeneous conference 830 via the mobile bridge. Thus, moderator A
possesses only those
moderator controls associated with the mobile bridge with respect to
participant B. Accordingly, in
this example, moderator A is only able to exercise the mute, drop, and
transfer controls over
participant B.
[0082] In contrast, participants C-K are coupled to the heterogeneous
conference call 830 via
intermediate conference server 820. Thus, moderator A possesses only those
moderator controls
associated with intermediate conference server 820 with respect to
participants C-K. Accordingly, in
this example moderator A is only able to exercise the mute, drop, transfer,
side conference, and
record controls over participants C-K, for example, as shown in Figure 6A.
Moderator A would not
- 22 -
CA 02793374 2012-10-26
- be able to exercise the side conference or record controls over
participant B, for example as shown in
Figure 6B.
[0083] Similarly, if a participant is coupled to the heterogeneous
conference via server
conference bridge (not shown), the level of moderator control associated with
the participant are the
moderator controls of the conference bridge. In some embodiments not shown,
the moderator control
system also transfers sub-group moderator control to the one or more
identified sub-group
moderators.
[0084] Additionally, in some embodiments not shown, the moderator
control system also
transfers conference information to the identified moderator. Conference
information can include
number of conference participants, identity of conference participants, and
roles of conference
participants (acting as a moderator or a subgroup moderator).
[0085] Certain adaptations and modifications of the described
embodiments can be made.
Therefore, the above discussed embodiments are considered to be illustrative
and not restrictive.
[0086] Embodiments of the present application are not limited to any
particular operating
system, mobile device architecture, server architecture, or computer
programming language.
-23 -
