Patent Application
20140267559
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Meetings are a daily part of the work environment. Due to recent advances in real-time communications technology as well as trends toward distributed workforces, many meetings in today's work environment consist of in-room as well as remote attendees. As a result, meeting rooms utilize audio/video technology for enabling communication with remote attendees and for presenting meeting content to in-room attendees on shared displays. Current meeting room setups provide videoconferencing (“VTC”) units or other peripherals (e.g., computing devices) incorporating video conferencing software, to which users may connect to in order to start a meeting. Drawbacks associated with current meeting setups include the fact that they are often costly and further may be dependent on unknown and/or unreliable computing device hardware states, thereby causing delays in the start of scheduled meetings. It is with respect to these considerations and others that the various embodiments of the present invention have been made.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
Embodiments are provided for pairing and configuring a computing device for use in a meeting space. An appliance may communicate a broadcast to a computing device which announces the availability of a meeting space for a meeting. The computing device may establish a connection with the appliance. The computing device may then join the meeting in the meeting space.
These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are illustrative only and are not restrictive of the invention as claimed.
Embodiments are provided for pairing and configuring a computing device for use in a meeting space. An appliance may communicate a broadcast to a computing device which announces the availability of a meeting space for a meeting. The computing device may establish a connection with the appliance. The computing device may then join the meeting in the meeting space.
In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit or scope of the present invention. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
Referring now to the drawings, in which like numerals represent like elements through the several figures, various aspects of the present invention will be described.
In accordance with an embodiment, the meeting appliance 70 may be connected to a display 80 and may comprise an embedded device including interfaces 71, a camera 72, one or more communication devices 74 and a smart card 76. The interfaces 71 may include a wireless interface which enables the computing device 10 to discover and connect to the meeting appliance 70. The interfaces 71 may further include a network interface for connecting to an online communication session, such as a meeting. It should be understood that the network interface may be either wired or wireless. The camera 72 may comprise a webcam (which may include a microphone for capturing audio). In accordance with the present embodiment, the communication devices 74 may comprise devices for establishing wireless communications with computing devices in proximity to the meeting appliance 70 for authenticating a user during a pairing process. The communication devices 74 may include, without limitation, Near Field Communication (“NFC”) devices, BLUETOOTH wireless technology devices, Smart Card devices and WI-FI devices. It should be appreciated that the camera 72 may also be utilized for authentication via facial recognition.
The routine 200 begins at operation 205, where the application 30, executing on the computing device 10, may receive the broadcast 12 from the meeting appliance 70. In particular, the meeting appliance 70 may send out a wireless broadcast signal that it is available for connection to the computing device 10. In accordance with an embodiment, the broadcast 12 may be restricted to a physical meeting space (e.g., the meeting space 10) using wireless power management and directionality.
From operation 205, the routine 200 continues to operation 210, where the application, executing on the computing device 10, may establish the connection 16 with the meeting appliance 70. In particular, the computing device 10 may detect the broadcast 12 from the meeting appliance 70 and choose to connect to it using the pairing instructions 14. It should be understood that the connection to the meeting appliance 70 may be accomplished automatically (such as by checking the meeting data 40 to determine that the user 2 has a meeting scheduled around the time the broadcast is detected) or via a user prompt according to a predetermined policy or preference. In accordance with an embodiment, the paring instructions may comprise an exchange of Third Party Control Protocol (“TPCP”) and Session Initiated Protocol (“SIP”) data (i.e., TPCP/SIP data) between the computing device 10 and the meeting appliance 70. As should be understood by those skilled in the art, TPCP is a client-server protocol which is used to initiate, control and observe sessions between remote parties and which includes three types of primitives: Request, Notify and Responses. As should also be understood by those skilled in the art, SIP is a signaling protocol used for controlling communication sessions over Internet Protocol (“IP”). The protocol can be used for creating, modifying and terminating two-party (unicast) or multiparty (multicast) communication sessions. In accordance with one example, a TPCP paring data (including the user's SIP address) may be sent from the user 2's computing device 10 to the meeting appliance 70 when the user 2 is in proximity to the meeting appliance 70. For example, the application 30 may configure the computing device 10 so that it can detect that it is in proximity to the meeting appliance 70 which is in a meeting. The meeting appliance 70 may then return a TPCP signal requesting an authentication code from the computing device 10. The authorization code may be obtained by prompting the user to communicate the code (e.g., a numerical code) or automatically from the computing device 10 via any of a number of authentication methods including, without limitation, facial recognition, NFC authentication and Smart Card authentication. Upon the completion of the authentication process, the paring process is completed and a control channel may be established between the computing device 10 and the meeting appliance 70.
From operation 210, the routine 200 continues to operation 215, where the application 30, executing on the computing device 10, may join a meeting in the meeting space 20 via the meeting appliance 70. In accordance with an embodiment, the particular, the computing device 10 may join a meeting when it is remotely located with respect to the meeting appliance 70 in the meeting space 20. In accordance with another embodiment, the computing device 10 may join a meeting when it is in proximity to the meeting appliance 70 (i.e., the user 2 of the computing device 10 is physically in the meeting space 20 for the meeting). It should be understood that when the computing device 10 joins a meeting, the meeting appliance 70's webcam and microphone may be utilized to capture audio and video and the meeting room display (e.g., the display 70) may be utilized to show a meeting view (e.g., video of remote participants and any content uploaded to the meeting). Remote participants may also see the user 2 in a roster (i.e., a meeting roster). In accordance with an embodiment, once a meeting has been joined, the meeting roster of participants may be automatically updated on the computing device 10. The meeting roster may include the names of meeting attendees in the meeting space 20. Furthermore, remote attendees may know who is in the meeting room and who is talking via the aforementioned meeting roster. In accordance with an embodiment, presence information associated with meeting attendees may be automatically updated (e.g., a presence may be updated to “in a conference” as opposed to “in a meeting”) so that they are not disturbed during the meeting. In accordance with an embodiment, the audio portion of a meeting may not be joined in order to avoid feedback/echo.
From operation 215, the routine 200 continues to operation 220, where the meeting application 30, executing on the computing device 10, may provide the user interface 35 for conducting meeting functions during the meeting. In particular, the user interface 35 may be utilized to add participants, mute participants, select content to share, choose meeting views to show on a meeting room display and communicate content, commands and responses during the meeting. For example, meeting participants may use the user interface 35 on the computing device 10 to add content into a meeting (e.g., add photos of concepts, designs, whiteboard, share documents, slides, etc.), drive the meeting (e.g., navigate slides, invite new attendees, etc.) and communicate via a back-channel in the meeting (e.g., respond to a poll, send/receive instant messages, respond to questions and answers, troubleshoot issues on the side without disturbing the flow of the meeting, etc.). It should understood that in accordance with an embodiment, the user interface 35 may be configured to display video of additional attendees who are not being displayed on the meeting room display and asynchronously browse meeting content. It should be further understood that in accordance with an embodiments, the meeting room may also be configured (e.g., by using the user interface 35) from the computing device 10 according to user preferences. For example, the user interface 35, provided by the application 30, may allow the user 2 to manage the environment of the meeting space (e.g., displays, video, audio, lighting, etc.) from the computing device 10. From operation 220, the routine 200 then ends.
The computing device 300 may have additional features or functionality. For example, the computing device 300 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, solid state storage devices (“SSD”), flash memory or tape. Such additional storage is illustrated in
Generally, consistent with various embodiments, program modules may be provided which include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types. Moreover, various embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, automotive computing systems and the like. Various embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Furthermore, various embodiments may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. For example, various embodiments may be practiced via a system-on-a-chip (“SOC”) where each or many of the components illustrated in
Various embodiments, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
The term computer readable media as used herein may include computer storage media. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information (such as computer readable instructions, data structures, program modules, or other data) in hardware. The system memory 304, removable storage 309, and non-removable storage 310 are all computer storage media examples (i.e., memory storage.) Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by the computing device 300. Any such computer storage media may be part of the computing device 300.
The term computer readable media as used herein may also include communication media. Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.
Mobile computing device 450 incorporates output elements, such as display 425, which can display a graphical user interface (GUI). Other output elements include speaker 430 and LED 480. Additionally, mobile computing device 450 may incorporate a vibration module (not shown), which causes mobile computing device 450 to vibrate to notify the user of an event. In yet another embodiment, mobile computing device 450 may incorporate a headphone jack (not shown) for providing another means of providing output signals.
Although described herein in combination with mobile computing device 450, in alternative embodiments may be used in combination with any number of computer systems, such as in desktop environments, laptop or notebook computer systems, multiprocessor systems, micro-processor based or programmable consumer electronics, network PCs, mini computers, main frame computers and the like. Various embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network in a distributed computing environment; programs may be located in both local and remote memory storage devices. To summarize, any computer system having a plurality of environment sensors, a plurality of output elements to provide notifications to a user and a plurality of notification event types may incorporate the various embodiments described herein.
Applications 467 may be loaded into memory 462 and run on or in association with an operating system 464. The system 402 also includes non-volatile storage 468 within memory the 462. Non-volatile storage 468 may be used to store persistent information that should not be lost if system 402 is powered down. The applications 467 may use and store information in the non-volatile storage 468. The applications 467 may also include functionality for pairing and configuring the computing device 450 for use in a meeting space. A synchronization application (not shown) also resides on system 402 and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage 468 synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may also be loaded into the memory 462 and run on the mobile computing device 450.
The system 402 has a power supply 470, which may be implemented as one or more batteries. The power supply 470 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.
The system 402 may also include a radio 472 (i.e., radio interface layer) that performs the function of transmitting and receiving radio frequency communications. The radio 472 facilitates wireless connectivity between the system 402 and the “outside world,” via a communications carrier or service provider. Transmissions to and from the radio 472 are conducted under control of OS 464. In other words, communications received by the radio 472 may be disseminated to the applications 467 via OS 464, and vice versa.
The radio 472 allows the system 402 to communicate with other computing devices, such as over a network. The radio 472 is one example of communication media. The embodiment of the system 402 is shown with two types of notification output devices: the LED 480 that can be used to provide visual notifications and an audio interface 474 that can be used with speaker 430 to provide audio notifications. These devices may be directly coupled to the power supply 470 so that when activated, they remain on for a duration dictated by the notification mechanism even though processor 460 and other components might shut down for conserving battery power. The LED 480 may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface 474 is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to speaker 430, the audio interface 474 may also be coupled to a microphone (not shown) to receive audible (e.g., voice) input, such as to facilitate a telephone conversation. In accordance with embodiments, the microphone may also serve as an audio sensor to facilitate control of notifications. The system 402 may further include a video interface 476 that enables an operation of on-board camera 440 to record still images, video streams, and the like.
A mobile computing device implementing the system 402 may have additional features or functionality. For example, the device may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
Data/information generated or captured by the mobile computing device 450 and stored via the system 402 may be stored locally on the mobile computing device 450, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio 472 or via a wired connection between the mobile computing device 450 and a separate computing device associated with the mobile computing device 450, for example, a server computer in a distributed computing network such as the Internet. As should be appreciated such data/information may be accessed via the mobile computing device 450 via the radio 472 or via a distributed computing network. Similarly, such data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.
Various embodiments are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products. The functions/acts noted in the blocks may occur out of the order as shown in any flow diagram. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
While certain embodiments have been described, other embodiments may exist. Furthermore, although various embodiments have been described as being associated with data stored in memory and other storage mediums, data can also be stored on or read from other types of computer-readable media, such as secondary storage devices (i.e., hard disks, floppy disks, or a CD-ROM), a carrier wave from the Internet, or other forms of RAM or ROM. Further, the disclosed routine's operations may be modified in any manner, including by reordering operations and/or inserting or operations, without departing from the embodiments described herein.
It will be apparent to those skilled in the art that various modifications or variations may be made without departing from the scope or spirit of the embodiments described herein. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments described herein.
