Meeting room control via mobile device

Various aspects of the subject technology relate to systems, methods, and machine-readable media for meeting room control. The method includes receiving, through a mobile device of a user, a request to access a meeting, the meeting comprising one or more meetings. The method also includes receiving, from the mobile device of the user, a request to toggle a control mode for the meeting, the control mode comprising an interface for the meeting, the interface displayed through the mobile device. The method also includes receiving instructions regarding controlling functions of the meeting through the interface on the mobile device, the functions comprising at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting. The method also includes applying the instructions to the functions of the meeting.

TECHNICAL FIELD

The present disclosure generally relates to videoconferencing and teleconferencing, and more particularly to meeting room control via a mobile device.

BACKGROUND

Conventionally, videoconferencing and teleconferencing technology require use of a fixed/dedicated room controller that allows only a single user to control aspects of the meeting. The fixed/dedicated room controller typically is bulky and not meant for multiple users to access. This becomes problematic when multiple users desire control of the meeting, but are limited in their ability to access the fixed/dedicated room controller.

BRIEF SUMMARY

The subject disclosure provides for systems and methods for remote control of meeting room systems via a mobile device. In an aspect, multiple meeting participants may each receive access to meeting room controls through their mobile devices. For example, each mobile device may be configured with a meeting application through which the users may join a meeting. The meeting application may include a remote control mode of operation that may be toggled by the users to control aspects of the meeting.

According to one embodiment of the present disclosure, a computer-implemented method for meeting room control is provided. The method includes receiving, through a mobile device of a user, a request to access a meeting, the meeting comprising one or more meetings. The method also includes receiving, from the mobile device of the user, a request to toggle a control mode for the meeting, the control mode comprising an interface for the meeting, the interface displayed through the mobile device. The method also includes receiving instructions regarding controlling functions of the meeting through the interface on the mobile device, the functions comprising at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting. The method also includes applying the instructions to the functions of the meeting.

According to one embodiment of the present disclosure, a system is provided including a processor and a memory comprising instructions stored thereon, which when executed by the processor, causes the processor to perform a method for meeting room control. The method includes receiving, through a mobile device of a user, a request to access a meeting, the meeting comprising one or more meetings. The method also includes receiving, from the mobile device of the user, a request to toggle a control mode for the meeting, the control mode comprising an interface for the meeting, the interface displayed through the mobile device. The method also includes receiving instructions regarding controlling functions of the meeting through the interface on the mobile device, the functions comprising at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting. The method also includes applying the instructions to the functions of the meeting.

According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium is provided including instructions (e.g., stored sequences of instructions) that, when executed by a processor, cause the processor to perform operations for meeting room control. The operations include receiving, through a mobile device of a user, a request to access a meeting, the meeting comprising one or more meetings. The operations also include receiving, from the mobile device of the user, a request to toggle a control mode for the meeting, the control mode comprising an interface for the meeting, the interface displayed through the mobile device. The operations also include receiving instructions regarding controlling functions of the meeting through the interface on the mobile device, the functions comprising at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting. The operations also include applying the instructions to the functions of the meeting.

According to one embodiment of the present disclosure, a system is provided that includes means for storing instructions, and means for executing the stored instructions that, when executed by the means, cause the means to perform a method for meeting room control. The method includes receiving, through a mobile device of a user, a request to access a meeting, the meeting comprising one or more meetings. The method also includes receiving, from the mobile device of the user, a request to toggle a control mode for the meeting, the control mode comprising an interface for the meeting, the interface displayed through the mobile device. The method also includes receiving instructions regarding controlling functions of the meeting through the interface on the mobile device, the functions comprising at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting. The method also includes applying the instructions to the functions of the meeting.

DETAILED DESCRIPTION

Conventionally, videoconferencing and teleconferencing technology requires use of a fixed/dedicated room controller that allows only a single user to control aspects of the meeting. The fixed/dedicated room controller typically is bulky and not meant for multiple users to access. This becomes problematic when multiple users desire control of the meeting, but are limited in their ability to access the fixed/dedicated room controller. As a result, it becomes a complicated process to control simple aspects of the meeting (e.g., muting all participants, sharing a screen, etc.) by multiple users.

Aspects of the present disclosure address these issues by providing for meeting room control via a mobile device. In an aspect, multiple meeting participants may each receive access to meeting room controls through their mobile devices. For example, each mobile device may be configured with a meeting application through which the users may join a meeting. The meeting application may include a remote control mode of operation that may be toggled by the users to control aspects of the meeting. As a result, multiple hosts may control common meeting functions without having to change chairs, designate someone as a controller, or pass a device around a meeting room, etc. Additionally, the mobile device itself is portable and more convenient to use, instead of a fixed/dedicated room controller (e.g., a full-sized computer, hardphone, etc.).

The disclosed system addresses a problem in traditional videoconferencing and teleconferencing tied to computer technology, namely, the technical problem of controlling functions of a meeting. The disclosed system solves this technical problem by providing a solution also rooted in computer technology, namely, by providing for meeting control via a mobile device. The disclosed system also improves the functioning of the computer itself because it improves efficiency of meeting controls.

FIG. 1illustrates an example unified communication platform100, according to some embodiments. The unified communication platform100includes servers130, clients110, and one or more meeting room systems160connected over a network150. In some embodiments, the processor in server130is configured to host an application for operating a unified communication network between multiple client devices110. Further, in some embodiments, the processor in server130is configured to provide support for collaborative network event applications, and other networking applications such as meeting services and the like, to a participant in the unified communication network through client device110. The servers130can return images, documents, rich-text documents, and the like intended for shared use and modification by multiple participants in a meeting as disclosed herein. In some embodiments, servers130are configured to transmit voice over internet protocols (VoIP) data packets to and from one or more client devices110. For purposes of load balancing, multiple servers130can host memories including instructions to one or more processors and multiple servers130for hosting one or more tools as disclosed herein.

The client devices110can be, for example, desktop computers, mobile computers, tablet computers (e.g., including e-book readers), mobile devices (e.g., a smartphone or PDA), or any other devices having appropriate processor, memory, and communications capabilities for accessing a meeting through one of the servers130. The network150can include, for example, any one or more of a local area network (LAN), a wide area network (WAN), the Internet, and the like. Further, the network150can include, but is not limited to, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star-bus network, tree or hierarchical network, and the like. The meeting room system160may include, for example, one or more cameras, microphones, speakers, displays, and hardware and/or software configured for executing collaboration software (e.g., meeting software).

FIG. 2is a block diagram illustrating an example server and a client device in a unified communication platform200, according to certain aspects of the disclosure. The client device110and the server130are communicatively coupled over the network150via respective communication modules218-1and218-2(hereinafter, collectively referred to as “communication modules218”). The communication modules218are configured to interface with the network150to send and receive information, such as data, requests, responses, and commands to other devices on the network150. The communications modules218can be, for example, modems or Ethernet cards. In some embodiments, the communication modules218may be configured to receive and transmit voice and video data over a telephone network, a wireless cellular network, a data network (e.g., VoIP), or any combination of the above. In some embodiments, the communication modules218may be configured to transmit data between one or more participants in a meeting.

The client device110may be any one of a desktop computer, a laptop, or a mobile computing device. The client device110may include a processor212-1and a memory220-1. An input device214and an output device216enable the user to interact with the client device110. Examples of the input device214and the output device216may include a mouse, a keyboard, a display, a touch-interactive display, and the like.

A processor212-1is configured to execute instructions, such as instructions physically coded into the processor212-1, instructions received from software in memory220-1, or a combination of both. A user of the client device110may use an input device214to control meeting functions through a meeting engine240via a user interface of an application222.

Server130includes a memory220-2, a processor212-2, and a communications module218-2. The user interface is displayed for the user in an output device216of the client device110. The memory220-2includes a meeting engine240and a database252. In some embodiments, an application222in the client device110may communicate with meeting engine240using a connection tool242and a functions tool244. In some embodiments, establishing a communication channel between one or more client devices110may include determining that one or more of the client devices110is a subscriber of a client network of the server130. For example, in some embodiments, the client device110having an application222installed in the memory220-1is a subscriber of a client network of the server130. For example, in some embodiments, participants in a meeting may all be members of an enterprise or organization registered with the server130, or is a client of the services provided by the server130. In some embodiments, at least one of the client devices110participating in a communication channel hosted by the server130may not be a subscriber of a client network of the server130. For example, in some embodiments, at least one of the client devices110participating in a communication channel may be a subscriber of a public network, and available through a telephone number.

The user may access meeting engine240through the application222installed in the memory220-1of client device110. The user may also access the meeting engine240via a web browser installed in the client device110, or simply by dialing a telephone number (e.g., a telephone number in database252, or any other number registered within unified communication platform200). Execution of the application222may be controlled by the processor212-1. In some embodiments, the application222is downloaded and installed by the user into the client device110, from the server130.

FIG. 3illustrates an exemplary user interface300(e.g., an interface) for controlling a meeting through a mobile device320, according to certain aspects of the present disclosure. For example, the meeting may include one or more meetings that are being held in one or more meeting rooms, both virtual and non-virtual. According to aspects, meeting rooms may be outfitted with a meeting room system (e.g., video/audio capture devices, speakers, one or more monitors/video display devices, and hardware/software running a meeting/collaboration software client). It is further understood that a “meeting room” may include any suitable locale outfitted with a meeting room system to allow one or more participants to participate in an audio/video/collaboration session.

The user interface300may include a room controller function302that toggles a remote mode (e.g., a control mode) for the meeting through the mobile device320. As illustrated, the room controller function302has already been activated, and toggling the controller function302again would revert the interface300back to a normal mode. For example, the normal mode may include additional functionality for the meeting that is not included in the remote mode. That is because the remote mode includes a simplified interface for users to navigate that includes the most commonly used meeting functions.

According to aspects, the user interface300may include functionality for controlling various aspects of the meeting through the mobile device320of the user. For example, controls may be included for muting all participants304, promoting a speaker306, recording the meeting308, muting/unmuting310a user microphone on the mobile device320, sharing a screen312, transferring a meeting room314, audio connectivity316, and ending the meeting318. Additional controls may be included for kicking a remote participant, screen share controls, and controlling cameras of room systems (e.g., angle, pitch, and zoom), among others. It is understood that these described functions are exemplary only, and other functions, including any commonly used meeting functions, may be added and/or substituted for any of the displayed functions without departing from the scope of the disclosure.

According to aspects, muting all participants304mutes all participants of the meeting so that only a single speaker may be heard. Promoting a speaker306may allow a single speaker to be highlighted, zoomed-in on, projected onto a main screen, etc., so that the speaker may be appropriately heard.

In an implementation, promoting the speaker306may be only allowed by users with host privileges. For example, any host of the meeting may provide host privileges to other users. According to an aspect, a speaker may also be demoted through similar means. According to additional aspects, facial recognition of participants visible to a camera may be utilized to quickly identify a face of a speaker to focus the camera on that person for everyone to see. Furthermore, different angles of the speaker may be chosen to determine a best angle.

Recording the meeting308allows for recording of the meeting or parts of the meeting. Muting/unmuting310causes a user microphone on the mobile device320to be either muted or unmuted. Sharing a screen312allows the user to share their screen from their mobile device (e.g., display, cloud, application, etc.). Transferring a meeting room314allows the user to transfer the meeting to another room or another device. For example, nearby rooms may be automatically discovered through multiple channels including Bluetooth proximity or ultrasonic signaling from room speakers. In an implementation, a list of rooms may be obtained by integration with corporate directory/calendar systems. According to aspects, the meeting may be a virtual meeting with virtual participants.

Audio connectivity316allows audio from the meeting to be played over a wireless sound system (e.g., switching an audio source). Ending the meeting318allows the user to end/exit the meeting through their mobile device. For example, the user may be asked to confirm that they are ending/exiting the meeting before the end meeting318task is executed.

According to aspects, any user participating in the meeting may access the user interface300through their own mobile device. For example, the user interface300may be accessed through a meeting application330that may be installed on the user devices. The meeting application330may be configured to join the meeting through the mobile device. For example, the users may select a mode in which to join the meeting. According to aspects, users may join in a normal meeting mode, a silent mode (e.g., muting on join), or the remote mode. In an implementation, joining in the remote mode directly would allow users to access the interface300for the sole purpose of controlling the meeting through their mobile device.

According to aspects, any mobile device can manage the meeting virtual scene and/or stage. For example, a mobile remote (e.g., user interface300) may be utilized to focus the video in a room on a specific person, set several key participants as focused and/or larger videos, have a laser pointer, etc. As a result, the mobile remote may include controls that go beyond and offer features not as easy to use from a conventional primary room control device.

As described herein, the user interface300leverages existing functions and controls in a format designed for portable controlling of a meeting room, similar to “car mode” where most buttons are removed and key buttons are made larger for safety. As a result, any user mobile device may become a room controller. According to aspects, a user may remotely control one or more meetings, each meeting having one or more meeting rooms with meeting participants. In this way, a single meeting administrator may oversee and control multiple meetings simultaneously through the user interface300.

FIG. 4illustrates an exemplary system400for controlling a meeting through a mobile device, in accordance with one or more implementations. In some implementations, system400may include one or more computing platforms402. Computing platform(s)402may be configured to communicate with one or more remote platforms404according to a client/server architecture, a peer-to-peer architecture, and/or other architectures. Remote platform(s)404may be configured to communicate with other remote platforms via computing platform(s)402and/or according to a client/server architecture, a peer-to-peer architecture, and/or other architectures. Users may access system400via remote platform(s)404.

Computing platform(s)402may be configured by machine-readable instructions406. Machine-readable instructions406may include one or more instruction modules. The instruction modules may include computer program modules. The instruction modules may include one or more of meeting access module408, remote mode module410, remote control interface module412, meeting functions module414, and/or other instruction modules.

Meeting access module408may be configured to access a meeting through a mobile device of a user. By way of non-limiting example, the meeting may include one or more meetings having one or more meeting rooms and meeting participants. The meeting may be a virtual meeting with virtual participants.

Remote mode module410may be configured to toggle a control mode for the meeting through the mobile device. By way of non-limiting example, the control mode may include an interface for the meeting.

Remote control interface module412may be configured to cause display of the control interface for the meeting through the mobile device.

Meeting functions module414may be configured to control functions of the meeting through the interface. By way of non-limiting example, the functions may include at least one of muting all the meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting to another room.

A given remote platform404may include one or more processors configured to execute computer program modules. The computer program modules may be configured to enable an expert or user associated with the given remote platform404to interface with system400and/or external resources424, and/or provide other functionality attributed herein to remote platform(s)404. By way of non-limiting example, a given remote platform404and/or a given computing platform402may include one or more of a server, a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resources424may include sources of information outside of system400, external entities participating with system400, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources424may be provided by resources included in system400.

Computing platform(s)402may include electronic storage426, one or more processors428, and/or other components. Computing platform(s)402may include communication lines or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of computing platform(s)402inFIG. 4is not intended to be limiting. Computing platform(s)402may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to computing platform(s)402. For example, computing platform(s)402may be implemented by a cloud of computing platforms operating together as computing platform(s)402.

Electronic storage426may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage426may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with computing platform(s)402and/or removable storage that is removably connectable to computing platform(s)402via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage426may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage426may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage426may store software algorithms, information determined by processor(s)428, information received from computing platform(s)402, information received from remote platform(s)404, and/or other information that enables computing platform(s)402to function as described herein.

Processor(s)428may be configured to provide information processing capabilities in computing platform(s)402. As such, processor(s)428may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s)428is shown inFIG. 4as a single entity, this is for illustrative purposes only. In some implementations, processor(s)428may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s)428may represent processing functionality of a plurality of devices operating in coordination. Processor(s)428may be configured to execute modules408,410,412, and/or414, and/or other modules. Processor(s)428may be configured to execute modules408,410,412, and/or414, and/or other modules by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s)428. As used herein, the term “module” may refer to any component or set of components that perform the functionality attributed to the module. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although modules408,410,412, and/or414are illustrated inFIG. 4as being implemented within a single processing unit, in implementations in which processor(s)428includes multiple processing units, one or more of modules408,410,412, and/or414may be implemented remotely from the other modules. The description of the functionality provided by the different modules408,410,412, and/or414described below is for illustrative purposes, and is not intended to be limiting, as any of modules408,410,412, and/or414may provide more or less functionality than is described. For example, one or more of modules408,410,412, and/or414may be eliminated, and some or all of its functionality may be provided by other ones of modules408,410,412, and/or414. As another example, processor(s)428may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one of modules408,410,412, and/or414.

FIG. 5illustrates an example flow diagram (e.g., process500) for controlling a meeting through a mobile device, according to certain aspects of the disclosure. For explanatory purposes, the example process500is described herein with reference toFIGS. 1-4. Further for explanatory purposes, the steps of the example process500are described herein as occurring in serial, or linearly. However, multiple instances of the example process500may occur in parallel. For purposes of explanation of the subject technology, the process500will be discussed in reference toFIGS. 1-4.

At step502, a request to access a meeting is received through a mobile device of a user, the meeting comprising one or more meetings having one or more meeting rooms and meeting participants. At step504, a request to toggle a control mode for the meeting is received through the mobile device, the control mode comprising an interface for the meeting. For example, the interface is displayed through the mobile device. At step506, instructions are received regarding controlling functions of the meeting through the interface on the mobile device. The functions include at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting to another room. At step508, the instructions are applied to the functions of the meeting.

For example, as described above in relation toFIGS. 1-4, at step502, a request for accessing a meeting (e.g., via meeting engine240) is received through a mobile device (e.g., client110) of a user (e.g., through meeting access module408), the meeting comprising one or more meetings having one or more meeting rooms and meeting participants. At step504a request from a user to toggle a control mode (e.g., through remote mode module410) for the meeting is received through the mobile device (e.g., mobile device320), the control mode comprising an interface (e.g., user interface300) for the meeting. The interface may be displayed (e.g., through remote control interface module412) for the meeting through the mobile device. At step506, instructions regarding controlling functions of the meeting are received through the interface on the mobile device (e.g., through meeting functions module414), the functions comprising at least one of muting all meeting participants, promoting a speaker, recording the meeting, sharing the meeting, or transferring the meeting (e.g., meeting room) to another room. At step508, the instructions are applied (e.g., through meeting functions module414) to the functions of the meeting.

According to an aspect, the control mode includes a reduced set of user controls. According to an aspect, the interface comprises large-sized icons for ease of user access. According to an aspect, toggling the control mode automatically mutes the user on the mobile device of the user.

According to an aspect, the process500may further include receiving a selection for the meeting through the mobile device, and granting the mobile device access to the meeting in the control mode.

According to an aspect, the process500may further include confirming that the user has host privileges for the meeting.

According to an aspect, the mobile device accesses the meeting through a meeting application installed on the mobile device of the user. According to an aspect, the meeting comprises a virtual meeting. According to an aspect, a meeting room of the meeting comprises a virtual meeting room.

FIG. 6is a block diagram illustrating an exemplary computer system600with which aspects of the subject technology can be implemented. In certain aspects, the computer system600may be implemented using hardware or a combination of software and hardware, either in a dedicated server, integrated into another entity, or distributed across multiple entities.

Computer system600(e.g., server and/or client) includes a bus608or other communication mechanism for communicating information, and a processor602coupled with bus608for processing information. By way of example, the computer system600may be implemented with one or more processors602. Processor602may be a general-purpose microprocessor, a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other manipulations of information.

Computer system600can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them stored in an included memory604, such as a Random Access Memory (RAM), a flash memory, a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable PROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device, coupled to bus608for storing information and instructions to be executed by processor602. The processor602and the memory604can be supplemented by, or incorporated in, special purpose logic circuitry.

Computer system600further includes a data storage device606such as a magnetic disk or optical disk, coupled to bus608for storing information and instructions. Computer system600may be coupled via input/output module610to various devices. The input/output module610can be any input/output module. Exemplary input/output modules610include data ports such as USB ports. The input/output module610is configured to connect to a communications module612. Exemplary communications modules612include networking interface cards, such as Ethernet cards and modems. In certain aspects, the input/output module610is configured to connect to a plurality of devices, such as an input device614and/or an output device616. Exemplary input devices614include a keyboard and a pointing device, e.g., a mouse or a trackball, by which a user can provide input to the computer system600. Other kinds of input devices614can be used to provide for interaction with a user as well, such as a tactile input device, visual input device, audio input device, or brain-computer interface device. For example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback, and input from the user can be received in any form, including acoustic, speech, tactile, or brain wave input. Exemplary output devices616include display devices, such as an LCD (liquid crystal display) monitor, for displaying information to the user.

According to one aspect of the present disclosure, the above-described gaming systems can be implemented using a computer system600in response to processor602executing one or more sequences of one or more instructions contained in memory604. Such instructions may be read into memory604from another machine-readable medium, such as data storage device606. Execution of the sequences of instructions contained in the main memory604causes processor602to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in memory604. In alternative aspects, hard-wired circuitry may be used in place of or in combination with software instructions to implement various aspects of the present disclosure. Thus, aspects of the present disclosure are not limited to any specific combination of hardware circuitry and software.

As the user computing system600reads game data and provides a game, information may be read from the game data and stored in a memory device, such as the memory604. Additionally, data from the memory604servers accessed via a network, the bus608, or the data storage606may be read and loaded into the memory604. Although data is described as being found in the memory604, it will be understood that data does not have to be stored in the memory604and may be stored in other memory accessible to the processor602or distributed among several media, such as the data storage606.