US20120159347A1 - Meeting-specific state indicators - Google Patents
Meeting-specific state indicators Download PDFInfo
- Publication number
- US20120159347A1 US20120159347A1 US12/968,332 US96833210A US2012159347A1 US 20120159347 A1 US20120159347 A1 US 20120159347A1 US 96833210 A US96833210 A US 96833210A US 2012159347 A1 US2012159347 A1 US 2012159347A1
- Authority
- US
- United States
- Prior art keywords
- meeting
- user
- state
- computer
- specific state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/02—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
Definitions
- IM instant messaging
- a user's state might also be set automatically. For instance, an IM client might automatically update a user's state based on activity or inactivity detected at the user's computer, in another example, a user's calendar might be utilized to automatically set the user's state to “in a meeting” during the time a meeting is scheduled on the user's calendar.
- state indicators communicate only a very general notion of the current state of a user.
- conventional general-purpose state indicators typically include “online”, “busy”, “offline”, “in a meeting”, and other similarly general phrases.
- the conventional general-purpose state indicators “busy” and “in a meeting” are helpful to people outside of a meeting.
- these general-purpose state indicators provide little information for invitees to the same meeting.
- the “busy” and “in a meeting” general-purpose state indicators may be unhelpful and even misleading, especially if one of the invitees is not actually at the meeting.
- meeting-specific state indicators can be provided to users that have been invited to the same meeting.
- General-purpose state indicators can be provided to users not invited to the meeting. In this manner, more relevant state indicators may be provided to users attended the same meeting.
- a state client and a state service are configured to provide meeting-specific state indicators.
- a meeting-specific state indicator is a state indicator that identifies a user's state with respect to a particular meeting and that is shared only with other invitees to the same meeting.
- a state client is a component configured to display state indicators, such as an IM client or a personal information management (“PIM”) program.
- a state service is a component configured to maintain state data and to make the state data available to state clients. For instance, a stand-alone state service may be configured to provide meeting-specific state indicators.
- an IM server or a meeting service may implement the state service.
- a state client is provided that is configured to provide a user interface for allowing a user to specify a meeting-specific state.
- the state client might allow a user to specify that the user is late for a meeting, that the user cannot attend the meeting, or that the user has checked in for the meeting.
- the meeting-specific state indicator might also identify an action that the user is performing at the meeting, such as presenting in the meeting, that the user is a next presenter in the meeting, or that the user is sharing a computer desktop with other meeting attendees.
- the meeting-specific state indicator might also identify a request by the user, such as that the user has a question or would like a meeting presenter to speed up or slow down.
- a state service configured to store data identifying the current state of one or more users, including a meeting-specific state.
- the state service also receives and responds to requests for the state of a user relative to a meeting. For instance, a state client might make a request for the state of a user in a particular meeting. In response to such a request, the state service returns the state of the user in the meeting.
- a state client might make a request on behalf of one user for the state of another user.
- the state service determines whether a meeting is in progress, or about to be in progress, for which both users are invitees.
- the state service might communicate with a meeting service or another type of service to make this determination.
- the state service determines that both users are not invitees to the same meeting, the state service returns a general-purpose state indicator (e,g. “online”, “busy”, “offline”, “in a fleeting”) in response to the request. If the state service determines that the users are invitees to the same meeting, the state service returns a meeting-specific state indicator. For instance, as discussed above, the state service might return a meeting-specific state indicator such as “late for the meeting,” “cannot attend the meeting,” or “checked in.” The state client may then display the meeting-specific state indicator. In this manner, more relevant state indicators may be provided to users attended the same meeting.
- a general-purpose state indicator e,g. “online”, “busy”, “offline”, “in a fleeting”
- the state service returns a meeting-specific state indicator. For instance, as discussed above, the state service might return a meeting-specific state indicator such as “late for the meeting,” “cannot attend the meeting,” or “checked in.”
- the state client may then
- FIGS. 1A-1B are software and network architecture diagrams showing several illustrative operating environments for the embodiments disclosed herein;
- FIG. 2 is a block diagram illustrating aspects of one mechanism disclosed herein for providing meeting-specific state indicators
- FIG. 3 is a flow diagram showing aspects of the operation of a state client according to one embodiment presented herein for providing meeting-specific state indicators
- FIGS. 4A-4B are user interface diagrams showing aspects of several illustrative user interfaces generated by a state client according to one embodiment disclosed herein;
- FIG. 5 is a flow diagram showing aspects of the operation of a state service according to one embodiment presented herein for providing meeting-specific state indicators.
- FIG. 6 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing the various embodiments presented herein.
- a state client is configured to allow a meeting-specific state to be specified. For instance, a user might be permitted to specify that they are running late for a meeting, checked in to the meeting, or unable to attend the meeting. Alternately, the meeting-specific state may be generated automatically, such as for instance in response to a user entering a conference room or joining an audio or video stream of a meeting.
- a state service stores data identifying the user's meeting-specific state.
- the state service disclosed herein also responds to requests for the state of the user. When such a request is received, the state service provides the state for a user with regard to a particular meeting in response to the request. A state client may then display meeting-specific state indicators indicating the user's state with respect to the meeting. The state client might also display general-purpose state indicators.
- the state service determines whether the user is an invitee to the same meeting as a user requesting the state. If not, the state service returns a general-purpose state indicator for the user. If both users are invitees to the same meeting, the state service returns a meeting-specific state indicator, which may then be displayed by a state client. In this way, meeting-specific state indicators can be provided to invitees of the same meeting,
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- FIG. 1A is a software and network architecture diagram showing one illustrative operating environment 100 A for the embodiments disclosed herein.
- the illustrative operating environment 100 A shown in FIG. 1 includes a number of state clients 102 A- 102 C, which may be referred to herein individually as “a state client 102 ” or collectively as “the state clients 102 ”, and a state service 106 .
- the state clients 102 are connected to the state service 106 by way of a network 114 .
- Each of the state clients 102 is a component configured to display the state indicators 104 A- 104 C.
- the state clients 102 are IM client applications configured to display the state indicators 104 for one or more users.
- the state clients 102 may be PIM programs, such as the OUTLOOK PIM program from MICROSOFT CORPORATION of Redmond, Wash.
- the state clients 102 might also be programs for editing and/or presenting documents.
- the state clients 102 may be word processing applications, presentation applications, spreadsheet applications, and other types of applications. It should be appreciated that, in general, the state clients 102 may be any type of component configured to display the state indicators 104 .
- the state indicators 104 are visual indications that specify the state of a person.
- the state indicators 104 may be user interface (“UI”) elements that show the state of one or more people.
- UI user interface
- the state indicators 104 might also comprise other types of graphical, audible, and audio/visual indicators that indicate the state of a person.
- the state clients 102 are connected to the state service 106 by way of the network 114 .
- the state service 106 is a component configured to maintain state data 108 and to make the state data 108 available to the state clients 102 .
- the state data 10 $ is data that identifies the state of one or more people. For instance, according to various implementations, each of the state clients 102 A- 102 C may transmit data indicating the state of an associated user to the state service 106 . In turn, the state service 106 stores the received information as the state data 108 .
- the state service 106 responds to requests from the state clients 102 , for the state data 108 .
- each of the state clients 102 A- 102 C can provide state indicators 104 for an associated group of users.
- the state service 106 is illustrated in FIG. 1A as a stand-alone service, the state service 106 might also be implemented by an IM server, a PIM server program, such as the EXCHANGE PIM server program from MICROSOFT CORPORATION, or by another component.
- the state service 106 might also be implemented in conjunction with a meeting service.
- the state clients 102 disclosed herein are configured to provide a UI for allowing a user to specify a meeting-specific state.
- the state clients 102 might allow a user to specify a meeting-specific state indicator 104 , such as an indication that the user is late for a meeting, the user cannot attend the meeting, or that the user has checked in for the meeting.
- the meeting-specific state indicator 104 might also identify an action that the user is performing at the meeting, such as presenting in the meeting, that the user is a next presenter in the meeting, or that the user is sharing a computer desktop with other meeting attendees.
- Meeting-specific state indicators 104 might also identify a request by the user such as that the user has a question, would like a meeting presenter to speed up or slow down, or would like the presenter to speak more loudly.
- a meeting-specific state indicator might also be specified automatically, such as when a user enters a meeting room or joins an audio or video broadcast of the meeting.
- the state clients 102 A- 102 C illustrated in FIG. 1 may also allow an associated user to specify a general-purpose state indicator.
- general-purpose state indicators communicate a very general notion of the current state of a user.
- general-purpose state indicators typically include an indication that a user is online, busy, offline, or in a meeting.
- General-purpose state indicators do not provide any indication regarding a user's particular state within a meeting.
- the state service 106 receives and responds to requests from the state clients 102 for the state of users. For example, the state service 106 might response to a request from a state client 102 A for the status of a user with respect to a meeting. In response to receiving such a request, the state service 106 identifies the appropriate meeting in the state data 108 and returns the appropriate meeting-specific state in response to the request. For instance, as discussed above, the state service 106 might return a meeting-specific state indicator such as “late for the meeting,” “cannot attend the meeting,” or “checked in.” The state client 102 A might then display a state indicator 104 A indicating the meeting-specific state of the user.
- a meeting-specific state indicator such as “late for the meeting,” “cannot attend the meeting,” or “checked in.”
- the state service 106 might support many other state clients 102 .
- a single network 114 has been disclosed herein, it should be appreciated that many more networks might be utilized to connect the state clients 102 to the state service 106 .
- the network 114 described herein may be the Internet, or any suitable local or wide area network configured for connecting a state client 102 and a state service 106 .
- the operating environment 100 A shown in FIG. 1A is merely illustrative and that many other implementations might be utilized.
- the state data 108 is stored at the state clients 102 .
- the state clients 102 are configured to determine when two users are in the same meeting and to display the appropriate meeting-specific state indicator.
- FIG. 1B is a software and network architecture diagram showing another illustrative operating environment 100 B for the embodiments disclosed herein.
- the state service 106 operates in conjunction with a meeting service 110 .
- the state client 102 A might make a request on behalf of an associated user for the state of another user.
- the state service 106 disclosed herein determines whether a meeting is in progress, or about to be in progress, for which both users are invitees.
- the state service 106 communicates with a meeting service 110 to make this determination.
- the meeting service 110 might store meeting data 112 that defines the time and attendees at one or more meetings. Other mechanisms might also be utilized by the state service 106 to determine whether two users are invitees to the same meeting.
- the state service 106 determines that both risers are not invitees to the same meeting, the state service 106 returns a general-purpose state indicator in response to the request from the state client 102 . If the state service 106 determines that the users are invitees to the same meeting, the state service returns a meeting-specific state indicator. The state client 102 that requested the state may then display the meeting-specific state indicator. In this manner, more relevant state indicators 104 may be provided to users attending the same meeting. Users not attending the meeting will be presented with a general-purpose indicator, such as “in a meeting.” In alternate embodiments, users are presented with both a meeting-specific and a general-purpose state indicator. Additional details regarding the operation of the state clients 102 and the state service 106 will be described below.
- state service 106 and the meeting service 110 have been illustrated in FIG. 1B as separate components, the functionality provided by these components may be performed by more or fewer components than illustrated in FIG. 1B .
- the presence data 108 and the meeting data 112 may be combined into a single database.
- the operating environment 100 B shown in FIG. 1B is merely illustrative and that many other implementations might be utilized.
- FIG. 2 is a block diagram illustrating aspects of one mechanism disclosed herein for providing meeting-specific state indicators.
- FIG. 2 illustrates how the state clients 102 A- 102 D are configured to display meeting-specific state indicators 104 for invitees to the same meeting and to display general-purpose state indicators to users that are not meeting invitees.
- four users 202 A- 202 D are utilizing the state clients 102 A- 102 D, respectively.
- the users 202 B- 202 D are invitees to the same meeting.
- the user 202 A has specified a general-purpose state indicator indicating that they are online.
- the user 202 B has specified a general-purpose state indicator specifying that they are in a meeting and a meeting-specific state indicator indicating that they are checked in to the meeting.
- the user 202 C has specified a general-purpose state indicator indicating that they are in a meeting and a meeting-specific state indicator indicating that they are running late for the meeting.
- the user 202 D has specified a general-purpose state indicator indicating that they are in a meeting and a meeting-specific state indicator indicating that they cannot attend the meeting,
- the state client 102 A will only display general-purpose state indicators for the users 202 B- 202 D, in particular, in the example shown in FIG. 2 , the state client 102 A displays state indicators 104 D, 104 E, and 104 F indicating that the users 202 B- 202 D, respectively, are in a meeting.
- the state client 10213 utilized by the user 202 B displays a general-purpose state indicator 104 G for the user 202 A indicating that the user 202 A is online
- the state client 102 B displays meeting-specific state indicators 104 H and 104 I for the users 202 C and 202 D indicating that the users are running late and cannot attend the meeting, respectively,
- the state client 102 C displays a general-purpose indicator 104 J for the user 202 A indicating that the user is online.
- the state client 102 C displays the meeting-specific state indicators 104 K and 104 L for the users 202 B and 202 D, respectively.
- the meeting-specific state indicator 104 K indicates that the user 20213 has checked in to the meeting.
- the meeting-specific state indicator 1041 L indicates that the user 202 D cannot attend the meeting.
- the state client 102 D displays the general-purpose state indicator 104 M for the user 202 A indicating that the user 202 A is online.
- the state client 102 D also displays the meeting-specific state indicators 104 N and 104 O for the users 202 B and 202 C, respectively.
- the meeting-specific state indicator 104 N indicates that the user 202 B has checked in to the meeting and the meeting-specific state indicator 1040 indicates that the user 202 C is running late for the meeting.
- each of the users 202 A- 202 D may he set manually by a user, such as through a user interface provided by a state client 102 , or automatically on behalf of the user, such as by the meeting service 110 . It should be further appreciated that although four users 202 A- 202 D have been illustrated in FIG. 2 , the technologies and concepts disclosed herein may be utilized with many more or fewer users than illustrated in FIG. 2 and described herein.
- FIG. 3 is a flow diagram showing one illustrative routine 300 showing aspects of the operation of the state client 102 according to one embodiment disclosed herein.
- the logical operations described herein with respect to FIG. 3 and the other FIGURES are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as operations, structural devices, acts, or modules.
- the routine 300 begins at operation 302 , where the state client 102 determines whether a user has requested to update their state. If a user has not requested to update their state, the routine 300 proceeds to operation 302 where another such determination is made. If the state client 102 determines that a user has requested to update their state, the routine 300 proceeds from operation 302 to operation 304 As discussed above, state might also be updated automatically, such as by a shared computer in a meeting room, by the meeting service 110 , in response to a user joining an audio or video feed of a meeting, or in another manner.
- the state client 102 determines if a meeting is in progress for which the associated user is an invitee. For instance, the state client 102 might contact the meeting service 110 to determine whether a meeting is in progress or about to be in progress for which the associated user is an invitee. From operation 304 , the routine 300 proceeds to operation 306 .
- the routine 300 proceeds to operation 308 where the state client 102 provides a user interface for allowing the user to specify their meeting-specific state.
- One illustrative user interface for specifying a meeting-specific state will be described below with reference to FIG. 4B . From operation 308 , the routine 300 proceeds to operation 312 .
- the routine 300 proceeds from operation 306 to operation 310 .
- the state client 102 provides a user interface for allowing the associated user to specify a general-purpose state.
- Art illustrative user interface for specifying a general-purpose state will he described below with reference to FIG. 4A .
- the routine 300 proceeds to operation 312 , where the state client 102 receives the general-purpose or meeting-specific state from the user via the provided user interface. The routine 300 then proceeds to operation 314 where the state client 102 transmits the data identifying the specified state to the state service 106 . As discussed briefly above, the state service 106 may store the received data as the state data 108 . From operation 314 , the routine 300 proceeds to operation 302 where a user may update their state in the manner described above.
- the operation of the state client 102 described in FIG. 3 allows the state client 102 to provide a user interface for specifying a general-purpose state when the user is not in a meeting, and a user interface for specifying a meeting-specific state when the user is in a meeting. It should be appreciated that, in other implementations, the state client 102 might provide a single user interface for providing a general-purpose state and/or a meeting-specific state. A user's state may also be specified automatically, such as by the meeting service 110 .
- FIGS. 4A-4B are user interface diagrams showing aspects of several illustrative user interfaces generated by a state client 102 according to one embodiment disclosed herein.
- FIG. 4A shows a user interface control 402 A for specifying a general-purpose state indicator 104 P- 104 T.
- the state indicators 104 P- 104 T are displayed and may be selected by a user.
- the general-purpose state indicators 104 P- 104 T illustrated in FIG. 4A are merely illustrative and other general-purpose state indicators might be specified by the user interface control 402 A.
- the user interface control 402 A may be displayed by the state client 102 A when a user requests to modify their state that is not an invitee to an in-progress meeting,
- FIG. 4B shows a user interface control 402 B for specifying a meeting-specific state indicator, such as the state indicators 104 U- 104 W.
- the user interface control 402 B might be utilized to specify other meeting-specific state indicators.
- the user interface control 402 B might be utilized to specify a state indicator that identifies an action that a user is performing at a meeting, such as presenting in the meeting, that the user is a next presenter in the meeting, or that the user is currently sharing a computer desktop with other meeting attendees.
- the user interface control 402 B might also allow a user to specify a meeting-specific state indicator that identifies a request by the user, such as that the user has a question or would like a meeting presenter to speed up or slow down.
- a user that specifies the state indicator 104 V for indicating that they are running late to a meeting might also be presented with another user interface for providing additional details. For instance, a UI might be presented through which the user can specify a duration of time until they will arrive at the meeting or a free-form comment such as “start without me” or “wait until I get there,” A similar UI might also be provided for other states. For instance, if a user indicates that they cannot attend a meeting, a UI might be provided through which the user can specify a text string indicating why they cannot attend. This information is transmitted to the state service 106 in the manner described above and may be displayed along with the state indicators 104 .
- the user interfaces shown in FIGS. 4A-4B are merely illustrative and that other types of user interfaces might be utilized.
- the current state of a user may be specified in ways other than through the use of the user interface controls 402 A- 402 B.
- the state client 102 may specify the current state of the user based upon detected inactivity.
- the meeting service 110 or another component might also specify the current state of a user to the state service 106 ,
- FIG. 5 is a flow diagram showing aspects of the operation of a state service 106 according to one embodiment presented herein for providing meeting-specific state indicators.
- the routine 500 begins at operation 502 where the state service 106 receives a request from a state client 102 for the current state of a user. In response to receiving such a request, the routine 500 proceeds from operation 502 to operation 504 where the state service 106 determines whether the user for which the state was requested and the user requesting the state are invitees to the same meeting. As discussed above, the state service 106 might utilize a meeting service 110 to make such a determination.
- the routine 500 proceeds to operation 506 .
- the state service 106 returns the meeting-specific state of the user for which state was requested to the requesting state client 102 . If, at operation 504 , the state service 106 determines that a meeting is not in progress for which the requesting user and the user for which state was requested are invitees, the routine 500 proceeds to operation 508 .
- the state service 106 returns a general-purpose state indicator 104 for the user for which state was requested in response to the request from the state client 102 .
- routine 500 proceeds to operation 510 .
- the state service 106 determines whether state has been requested for more users. If so, the routine 500 proceeds to operation 502 where the request for a user's state is processed in the manner described above. If not, the routine 500 proceeds from operation 510 to operation 512 , where it ends.
- FIG. 6 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing the various embodiments presented herein.
- the computer architecture shown in FIG. 6 illustrates a conventional desktop, laptop computer, or server computer and may be utilized to execute the various software components described herein,
- the computer architecture shown in FIG. 6 includes a central processing unit 602 . (“CPU”), a system memory 608 , including a random access memory 614 (“RAM”) and a read-only memory (“ROM”) 616 , and a system bus 604 that couples the memory to the CPU 602 .
- a basic input/output system (“BIOS”) containing the basic routines that help to transfer information between elements within the computer 600 , such as during startup, is stored in the ROM 616 .
- the computer 600 further includes a mass storage device 610 for storing an operating system 618 , application programs, and other program modules, which will be described in greater detail below.
- the mass storage device 610 is connected to the CPU 602 through a mass storage controller (not shown) connected to the bus 604 .
- the mass storage device 610 and its associated computer-readable storage media provide non-volatile storage for the computer 600 .
- computer-readable media can be any available computer storage media that can be accessed by the computer 600 .
- computer-readable storage media may include volatile and non-volatile, 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
- computer-readable storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium which can he used to store the desired information and which can be accessed by the computer 600 .
- Computer-readable media also encompasses communication media.
- Communication media typically embodies 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.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
- Computer-readable storage media does not encompass communication media.
- the computer 600 may operate in a networked environment using logical connections to remote computers through a network such as the network 620 .
- the computer 600 may connect to the network 620 through a network interface unit 606 connected to the bus 604 . It should be appreciated that the network interface unit 606 may also be utilized to connect to other types of networks and remote computer systems.
- the computer 600 may also include an input/output controller 612 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIG. 6 ). Similarly, an input/output controller may provide output to a display screen, a printer, or other type of output device (also not shown in FIG. 6 ),
- a number of program modules and data files may be stored in the mass storage device 610 and RAM 614 of the computer 600 , including an operating system 618 suitable for controlling the operation of a networked desktop, laptop, or server computer.
- the mass storage device 610 and RAM 614 may also store one or more program modules.
- the mass storage device 610 and the RAM 614 may store the state client 102 , the state service 106 , the meeting service 110 , and/or the other software components described above.
- the mass storage device 610 and RAM 614 may also store other program modules and data.
- software applications or modules may, when loaded into the CPU 602 and executed transform the CPU 602 and the overall computer 600 from a general-purpose computing system into a special-purpose computing system customized to perform the functionality presented herein.
- the CPU 602 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the CPU 602 may operate as one or more finite-state machines, in response to executable instructions contained within the software or modules. These computer-executable instructions may transform the CPU 602 , by specifying how the CPU 602 transitions between states, thereby physically transforming the transistors or other discrete hardware elements constituting the CPU 602 .
- Encoding the software or modules onto a mass storage device may also transform the physical structure of the mass storage device or associated computer readable storage media.
- the specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the computer readable storage media, whether the computer readable storage media are characterized as primary or secondary storage, and the like.
- the computer readable storage media is implemented as semiconductor-based memory
- the software or modules may transform the physical state of the semiconductor memory, when the software is encoded therein.
- the software may transform the states of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory.
- the computer readable storage media may be implemented using magnetic or optical technology.
- the software or modules may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.
Abstract
Description
- Various types of computer programs allow a user to share data describing their current state with other users. For instance, a user of an instant messaging (“IM”) client application might manually specify their current state as “bus.” The specified state may then be communicated to other IM users.
- A user's state might also be set automatically. For instance, an IM client might automatically update a user's state based on activity or inactivity detected at the user's computer, in another example, a user's calendar might be utilized to automatically set the user's state to “in a meeting” during the time a meeting is scheduled on the user's calendar.
- Conventional indicators of a user's current state (“state indicators”) communicate only a very general notion of the current state of a user. For instance, conventional general-purpose state indicators typically include “online”, “busy”, “offline”, “in a meeting”, and other similarly general phrases.
- The conventional general-purpose state indicators “busy” and “in a meeting” are helpful to people outside of a meeting. However, these general-purpose state indicators provide little information for invitees to the same meeting. For invitees to the same meeting, the “busy” and “in a meeting” general-purpose state indicators may be unhelpful and even misleading, especially if one of the invitees is not actually at the meeting.
- It is with respect to these and other considerations that the disclosure made herein is presented.
- Technologies are described herein for providing meeting-specific state indicators. Through an implementation of the concepts and technologies presented herein, meeting-specific state indicators can be provided to users that have been invited to the same meeting. General-purpose state indicators can be provided to users not invited to the meeting. In this manner, more relevant state indicators may be provided to users attended the same meeting.
- According to one aspect presented herein, a state client and a state service are configured to provide meeting-specific state indicators. A meeting-specific state indicator is a state indicator that identifies a user's state with respect to a particular meeting and that is shared only with other invitees to the same meeting. A state client is a component configured to display state indicators, such as an IM client or a personal information management (“PIM”) program. A state service is a component configured to maintain state data and to make the state data available to state clients. For instance, a stand-alone state service may be configured to provide meeting-specific state indicators. In other embodiments, an IM server or a meeting service may implement the state service.
- According to another aspect, a state client is provided that is configured to provide a user interface for allowing a user to specify a meeting-specific state. For instance, the state client might allow a user to specify that the user is late for a meeting, that the user cannot attend the meeting, or that the user has checked in for the meeting. The meeting-specific state indicator might also identify an action that the user is performing at the meeting, such as presenting in the meeting, that the user is a next presenter in the meeting, or that the user is sharing a computer desktop with other meeting attendees. The meeting-specific state indicator might also identify a request by the user, such as that the user has a question or would like a meeting presenter to speed up or slow down. When a user specifies a general-purpose or meeting-specific state indicator, the specified state is transmitted to the state service.
- According to another aspect, a state service is provided that is configured to store data identifying the current state of one or more users, including a meeting-specific state. The state service also receives and responds to requests for the state of a user relative to a meeting. For instance, a state client might make a request for the state of a user in a particular meeting. In response to such a request, the state service returns the state of the user in the meeting.
- In another embodiment, a state client might make a request on behalf of one user for the state of another user. In response to such a request, the state service determines whether a meeting is in progress, or about to be in progress, for which both users are invitees. The state service might communicate with a meeting service or another type of service to make this determination.
- If the state service determines that both users are not invitees to the same meeting, the state service returns a general-purpose state indicator (e,g. “online”, “busy”, “offline”, “in a fleeting”) in response to the request. If the state service determines that the users are invitees to the same meeting, the state service returns a meeting-specific state indicator. For instance, as discussed above, the state service might return a meeting-specific state indicator such as “late for the meeting,” “cannot attend the meeting,” or “checked in.” The state client may then display the meeting-specific state indicator. In this manner, more relevant state indicators may be provided to users attended the same meeting.
- This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
-
FIGS. 1A-1B are software and network architecture diagrams showing several illustrative operating environments for the embodiments disclosed herein; -
FIG. 2 is a block diagram illustrating aspects of one mechanism disclosed herein for providing meeting-specific state indicators; -
FIG. 3 is a flow diagram showing aspects of the operation of a state client according to one embodiment presented herein for providing meeting-specific state indicators; -
FIGS. 4A-4B are user interface diagrams showing aspects of several illustrative user interfaces generated by a state client according to one embodiment disclosed herein; -
FIG. 5 is a flow diagram showing aspects of the operation of a state service according to one embodiment presented herein for providing meeting-specific state indicators; and -
FIG. 6 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing the various embodiments presented herein. - The following detailed description is directed to technologies for providing meeting-specific state indicators. As discussed briefly above, a state client is configured to allow a meeting-specific state to be specified. For instance, a user might be permitted to specify that they are running late for a meeting, checked in to the meeting, or unable to attend the meeting. Alternately, the meeting-specific state may be generated automatically, such as for instance in response to a user entering a conference room or joining an audio or video stream of a meeting. A state service stores data identifying the user's meeting-specific state.
- The state service disclosed herein also responds to requests for the state of the user. When such a request is received, the state service provides the state for a user with regard to a particular meeting in response to the request. A state client may then display meeting-specific state indicators indicating the user's state with respect to the meeting. The state client might also display general-purpose state indicators.
- In another embodiment, the state service determines whether the user is an invitee to the same meeting as a user requesting the state. If not, the state service returns a general-purpose state indicator for the user. If both users are invitees to the same meeting, the state service returns a meeting-specific state indicator, which may then be displayed by a state client. In this way, meeting-specific state indicators can be provided to invitees of the same meeting,
- While the subject matter described herein is presented in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- In the following detailed description, references are made to the accompanying drawings that form a part hereof, and which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of a computing system and methodology for providing meeting-specific state indicators will be described.
-
FIG. 1A is a software and network architecture diagram showing oneillustrative operating environment 100A for the embodiments disclosed herein. Theillustrative operating environment 100A shown inFIG. 1 includes a number ofstate clients 102A-102C, which may be referred to herein individually as “astate client 102” or collectively as “thestate clients 102”, and astate service 106. Thestate clients 102 are connected to thestate service 106 by way of anetwork 114. - Each of the
state clients 102 is a component configured to display thestate indicators 104A-104C. For instance, in one implementation, thestate clients 102 are IM client applications configured to display the state indicators 104 for one or more users. Alternatively, thestate clients 102 may be PIM programs, such as the OUTLOOK PIM program from MICROSOFT CORPORATION of Redmond, Wash. Alternatively, thestate clients 102 might also be programs for editing and/or presenting documents. For instance, thestate clients 102 may be word processing applications, presentation applications, spreadsheet applications, and other types of applications. It should be appreciated that, in general, thestate clients 102 may be any type of component configured to display the state indicators 104. - The state indicators 104 are visual indications that specify the state of a person. For instance, in one implementation where the
state client 102A is an IM program, the state indicators 104 may be user interface (“UI”) elements that show the state of one or more people. The state indicators 104 might also comprise other types of graphical, audible, and audio/visual indicators that indicate the state of a person. - As discussed briefly above, the
state clients 102 are connected to thestate service 106 by way of thenetwork 114. Thestate service 106 is a component configured to maintainstate data 108 and to make thestate data 108 available to thestate clients 102. The state data 10$ is data that identifies the state of one or more people. For instance, according to various implementations, each of thestate clients 102A-102C may transmit data indicating the state of an associated user to thestate service 106. In turn, thestate service 106 stores the received information as thestate data 108. - As will also be described in greater detail below, the
state service 106 responds to requests from thestate clients 102, for thestate data 108. In this manner, each of thestate clients 102A-102C can provide state indicators 104 for an associated group of users. Although thestate service 106 is illustrated inFIG. 1A as a stand-alone service, thestate service 106 might also be implemented by an IM server, a PIM server program, such as the EXCHANGE PIM server program from MICROSOFT CORPORATION, or by another component. As will be described in greater detail below with regard toFIG. 1B , thestate service 106 might also be implemented in conjunction with a meeting service. - As will be described in greater detail below, the
state clients 102 disclosed herein are configured to provide a UI for allowing a user to specify a meeting-specific state. For instance, thestate clients 102 might allow a user to specify a meeting-specific state indicator 104, such as an indication that the user is late for a meeting, the user cannot attend the meeting, or that the user has checked in for the meeting. The meeting-specific state indicator 104 might also identify an action that the user is performing at the meeting, such as presenting in the meeting, that the user is a next presenter in the meeting, or that the user is sharing a computer desktop with other meeting attendees. Meeting-specific state indicators 104 might also identify a request by the user such as that the user has a question, would like a meeting presenter to speed up or slow down, or would like the presenter to speak more loudly. A meeting-specific state indicator might also be specified automatically, such as when a user enters a meeting room or joins an audio or video broadcast of the meeting. - The
state clients 102A-102C illustrated inFIG. 1 may also allow an associated user to specify a general-purpose state indicator. As discussed above, general-purpose state indicators communicate a very general notion of the current state of a user. For instance, general-purpose state indicators typically include an indication that a user is online, busy, offline, or in a meeting. General-purpose state indicators do not provide any indication regarding a user's particular state within a meeting. When a user utilizes astate client 102 to specify a general-purpose or meeting-specific state indicator 104, the specified state is transmitted to thestate service 106 and stored as thestate data 108. - As also described briefly above, the
state service 106 receives and responds to requests from thestate clients 102 for the state of users. For example, thestate service 106 might response to a request from astate client 102A for the status of a user with respect to a meeting. In response to receiving such a request, thestate service 106 identifies the appropriate meeting in thestate data 108 and returns the appropriate meeting-specific state in response to the request. For instance, as discussed above, thestate service 106 might return a meeting-specific state indicator such as “late for the meeting,” “cannot attend the meeting,” or “checked in.” Thestate client 102A might then display astate indicator 104A indicating the meeting-specific state of the user. - It should be appreciated that while three
state clients 102A-102C have been illustrated inFIG. 1A , thestate service 106 might support manyother state clients 102. Additionally, although asingle network 114 has been disclosed herein, it should be appreciated that many more networks might be utilized to connect thestate clients 102 to thestate service 106. Moreover, thenetwork 114 described herein may be the Internet, or any suitable local or wide area network configured for connecting astate client 102 and astate service 106. In this regard, it should be generally appreciated that the operatingenvironment 100A shown inFIG. 1A is merely illustrative and that many other implementations might be utilized. For instance, in another embodiment, thestate data 108 is stored at thestate clients 102. In this embodiment, thestate clients 102 are configured to determine when two users are in the same meeting and to display the appropriate meeting-specific state indicator. -
FIG. 1B is a software and network architecture diagram showing anotherillustrative operating environment 100B for the embodiments disclosed herein. In the embodiment shown inFIG. 1B , thestate service 106 operates in conjunction with ameeting service 110. In this example, thestate client 102A might make a request on behalf of an associated user for the state of another user. In response to such a request, thestate service 106 disclosed herein determines whether a meeting is in progress, or about to be in progress, for which both users are invitees. According to one implementation, thestate service 106 communicates with ameeting service 110 to make this determination. Themeeting service 110 might store meetingdata 112 that defines the time and attendees at one or more meetings. Other mechanisms might also be utilized by thestate service 106 to determine whether two users are invitees to the same meeting. - If the
state service 106 determines that both risers are not invitees to the same meeting, thestate service 106 returns a general-purpose state indicator in response to the request from thestate client 102. If thestate service 106 determines that the users are invitees to the same meeting, the state service returns a meeting-specific state indicator. Thestate client 102 that requested the state may then display the meeting-specific state indicator. In this manner, more relevant state indicators 104 may be provided to users attending the same meeting. Users not attending the meeting will be presented with a general-purpose indicator, such as “in a meeting.” In alternate embodiments, users are presented with both a meeting-specific and a general-purpose state indicator. Additional details regarding the operation of thestate clients 102 and thestate service 106 will be described below. - It should be appreciated that while the
state service 106 and themeeting service 110 have been illustrated inFIG. 1B as separate components, the functionality provided by these components may be performed by more or fewer components than illustrated inFIG. 1B . For instance, thepresence data 108 and themeeting data 112 may be combined into a single database. In this regard, it should be generally appreciated that the operatingenvironment 100B shown inFIG. 1B is merely illustrative and that many other implementations might be utilized. -
FIG. 2 is a block diagram illustrating aspects of one mechanism disclosed herein for providing meeting-specific state indicators. In particular,FIG. 2 illustrates how thestate clients 102A-102D are configured to display meeting-specific state indicators 104 for invitees to the same meeting and to display general-purpose state indicators to users that are not meeting invitees. In the example shown inFIG. 2 , fourusers 202A-202D are utilizing thestate clients 102A-102D, respectively. Theusers 202B-202D are invitees to the same meeting. Theuser 202A has specified a general-purpose state indicator indicating that they are online. Theuser 202B has specified a general-purpose state indicator specifying that they are in a meeting and a meeting-specific state indicator indicating that they are checked in to the meeting. Theuser 202C has specified a general-purpose state indicator indicating that they are in a meeting and a meeting-specific state indicator indicating that they are running late for the meeting. Theuser 202D has specified a general-purpose state indicator indicating that they are in a meeting and a meeting-specific state indicator indicating that they cannot attend the meeting, - Because the
user 202A is not a meeting invitee, thestate client 102A will only display general-purpose state indicators for theusers 202B-202D, in particular, in the example shown inFIG. 2 , thestate client 102A displaysstate indicators users 202B-202D, respectively, are in a meeting. - The state client 10213 utilized by the
user 202B displays a general-purpose state indicator 104G for theuser 202A indicating that theuser 202A is online Thestate client 102B displays meeting-specific state indicators 104H and 104I for theusers - The
state client 102C displays a general-purpose indicator 104J for theuser 202A indicating that the user is online. Thestate client 102C displays the meeting-specific state indicators users specific state indicator 104K indicates that the user 20213 has checked in to the meeting. The meeting-specific state indicator 1041L indicates that theuser 202D cannot attend the meeting. - The
state client 102D displays the general-purpose state indicator 104M for theuser 202A indicating that theuser 202A is online. Thestate client 102D also displays the meeting-specific state indicators 104N and 104O for theusers specific state indicator 104N indicates that theuser 202B has checked in to the meeting and the meeting-specific state indicator 1040 indicates that theuser 202C is running late for the meeting. - It should he appreciated that the example shown in
FIG. 2 is merely illustrative, it should also he appreciated that the general-purpose state of each of theusers 202A-202D may he set manually by a user, such as through a user interface provided by astate client 102, or automatically on behalf of the user, such as by themeeting service 110. It should be further appreciated that although fourusers 202A-202D have been illustrated inFIG. 2 , the technologies and concepts disclosed herein may be utilized with many more or fewer users than illustrated inFIG. 2 and described herein. -
FIG. 3 is a flow diagram showing oneillustrative routine 300 showing aspects of the operation of thestate client 102 according to one embodiment disclosed herein. It should be appreciated that the logical operations described herein with respect toFIG. 3 and the other FIGURES are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as operations, structural devices, acts, or modules. These operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof It should also be appreciated that more or fewer operations may be performed than shown in the figures and described herein. These operations may also be performed in a different order than those described herein. - The routine 300 begins at
operation 302, where thestate client 102 determines whether a user has requested to update their state. If a user has not requested to update their state, the routine 300 proceeds tooperation 302 where another such determination is made. If thestate client 102 determines that a user has requested to update their state, the routine 300 proceeds fromoperation 302 tooperation 304 As discussed above, state might also be updated automatically, such as by a shared computer in a meeting room, by themeeting service 110, in response to a user joining an audio or video feed of a meeting, or in another manner. - At
operation 304, thestate client 102 determines if a meeting is in progress for which the associated user is an invitee. For instance, thestate client 102 might contact themeeting service 110 to determine whether a meeting is in progress or about to be in progress for which the associated user is an invitee. Fromoperation 304, the routine 300 proceeds tooperation 306. - If the
state client 102 determines that a meeting is in progress, the routine 300 proceeds tooperation 308 where thestate client 102 provides a user interface for allowing the user to specify their meeting-specific state. One illustrative user interface for specifying a meeting-specific state will be described below with reference toFIG. 4B . Fromoperation 308, the routine 300 proceeds tooperation 312. - If the
state client 102 determines that a meeting is not in progress, the routine 300 proceeds fromoperation 306 tooperation 310. Atoperation 310, thestate client 102 provides a user interface for allowing the associated user to specify a general-purpose state. Art illustrative user interface for specifying a general-purpose state will he described below with reference toFIG. 4A . - From
operations operation 312, where thestate client 102 receives the general-purpose or meeting-specific state from the user via the provided user interface. The routine 300 then proceeds tooperation 314 where thestate client 102 transmits the data identifying the specified state to thestate service 106. As discussed briefly above, thestate service 106 may store the received data as thestate data 108. Fromoperation 314, the routine 300 proceeds tooperation 302 where a user may update their state in the manner described above. - It should be appreciated that the operation of the
state client 102 described inFIG. 3 allows thestate client 102 to provide a user interface for specifying a general-purpose state when the user is not in a meeting, and a user interface for specifying a meeting-specific state when the user is in a meeting. It should be appreciated that, in other implementations, thestate client 102 might provide a single user interface for providing a general-purpose state and/or a meeting-specific state. A user's state may also be specified automatically, such as by themeeting service 110. -
FIGS. 4A-4B are user interface diagrams showing aspects of several illustrative user interfaces generated by astate client 102 according to one embodiment disclosed herein. In particular,FIG. 4A shows auser interface control 402A for specifying a general-purpose state indicator 104P-104T. When theuser interface 402A is specified, thestate indicators 104P-104T are displayed and may be selected by a user. It should be appreciated that the general-purpose state indicators 104P-104T illustrated inFIG. 4A are merely illustrative and other general-purpose state indicators might be specified by theuser interface control 402A. As described briefly above, theuser interface control 402A may be displayed by thestate client 102A when a user requests to modify their state that is not an invitee to an in-progress meeting, -
FIG. 4B shows auser interface control 402B for specifying a meeting-specific state indicator, such as thestate indicators 104U-104W. It should be appreciated that, according to embodiments, theuser interface control 402B might be utilized to specify other meeting-specific state indicators. For instance, according to one implementation, theuser interface control 402B might be utilized to specify a state indicator that identifies an action that a user is performing at a meeting, such as presenting in the meeting, that the user is a next presenter in the meeting, or that the user is currently sharing a computer desktop with other meeting attendees. Theuser interface control 402B might also allow a user to specify a meeting-specific state indicator that identifies a request by the user, such as that the user has a question or would like a meeting presenter to speed up or slow down. - In other embodiments, a user that specifies the
state indicator 104V for indicating that they are running late to a meeting might also be presented with another user interface for providing additional details. For instance, a UI might be presented through which the user can specify a duration of time until they will arrive at the meeting or a free-form comment such as “start without me” or “wait until I get there,” A similar UI might also be provided for other states. For instance, if a user indicates that they cannot attend a meeting, a UI might be provided through which the user can specify a text string indicating why they cannot attend. This information is transmitted to thestate service 106 in the manner described above and may be displayed along with the state indicators 104. - When a user specifies a general-purpose state indicator utilizing the
user interface control 402A or a meeting-specific state indicator utilizing theuser interface control 402B, data identifying the specified state indicator is transmitted to thestate service 106 and stored in thestate data 108. Subsequently, when astate client 102 requests the state of a user, the data stored by thestate service 106 may be retrieved, provided to the requestingstate client 102, and utilized to display a meeting-specific or general-purpose state indicator. Additionally details regarding the operation of thestate service 106 in this regard will be provided below with respect toFIG. 5 . - It should be appreciated that the user interfaces shown in
FIGS. 4A-4B are merely illustrative and that other types of user interfaces might be utilized. As also discussed above, the current state of a user may be specified in ways other than through the use of the user interface controls 402A-402B. For instance, thestate client 102 may specify the current state of the user based upon detected inactivity. Alternately, themeeting service 110 or another component might also specify the current state of a user to thestate service 106, -
FIG. 5 is a flow diagram showing aspects of the operation of astate service 106 according to one embodiment presented herein for providing meeting-specific state indicators. The routine 500 begins atoperation 502 where thestate service 106 receives a request from astate client 102 for the current state of a user. In response to receiving such a request, the routine 500 proceeds fromoperation 502 tooperation 504 where thestate service 106 determines whether the user for which the state was requested and the user requesting the state are invitees to the same meeting. As discussed above, thestate service 106 might utilize ameeting service 110 to make such a determination. - If the
state service 106 determines that a meeting is in progress for which both the user for which state was requested and the user requesting state are invitees, the routine 500 proceeds tooperation 506. Atoperation 506, thestate service 106 returns the meeting-specific state of the user for which state was requested to the requestingstate client 102. If, atoperation 504, thestate service 106 determines that a meeting is not in progress for which the requesting user and the user for which state was requested are invitees, the routine 500 proceeds tooperation 508. Atoperation 508, thestate service 106 returns a general-purpose state indicator 104 for the user for which state was requested in response to the request from thestate client 102. - From
operations operation 510. Atoperation 510, thestate service 106 determines whether state has been requested for more users. If so, the routine 500 proceeds tooperation 502 where the request for a user's state is processed in the manner described above. If not, the routine 500 proceeds fromoperation 510 tooperation 512, where it ends. -
FIG. 6 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing the various embodiments presented herein. The computer architecture shown inFIG. 6 illustrates a conventional desktop, laptop computer, or server computer and may be utilized to execute the various software components described herein, - The computer architecture shown in
FIG. 6 includes acentral processing unit 602. (“CPU”), a system memory 608, including a random access memory 614 (“RAM”) and a read-only memory (“ROM”) 616, and a system bus 604 that couples the memory to theCPU 602. A basic input/output system (“BIOS”) containing the basic routines that help to transfer information between elements within thecomputer 600, such as during startup, is stored in theROM 616. Thecomputer 600 further includes amass storage device 610 for storing anoperating system 618, application programs, and other program modules, which will be described in greater detail below. - The
mass storage device 610 is connected to theCPU 602 through a mass storage controller (not shown) connected to the bus 604. Themass storage device 610 and its associated computer-readable storage media provide non-volatile storage for thecomputer 600. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should he appreciated by those skilled in the all that computer-readable storage media can be any available computer storage media that can be accessed by thecomputer 600. - By way of example, and not limitation, computer-readable storage media may include volatile and non-volatile, 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 For example, computer-readable storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium which can he used to store the desired information and which can be accessed by the
computer 600. - It should be appreciated that the computer-readable media disclosed herein also encompasses communication media. Communication media typically embodies 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” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media. Computer-readable storage media does not encompass communication media.
- According to various embodiments, the
computer 600 may operate in a networked environment using logical connections to remote computers through a network such as thenetwork 620. Thecomputer 600 may connect to thenetwork 620 through anetwork interface unit 606 connected to the bus 604. It should be appreciated that thenetwork interface unit 606 may also be utilized to connect to other types of networks and remote computer systems. Thecomputer 600 may also include an input/output controller 612 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown inFIG. 6 ). Similarly, an input/output controller may provide output to a display screen, a printer, or other type of output device (also not shown inFIG. 6 ), - As mentioned briefly above, a number of program modules and data files may be stored in the
mass storage device 610 andRAM 614 of thecomputer 600, including anoperating system 618 suitable for controlling the operation of a networked desktop, laptop, or server computer. Themass storage device 610 andRAM 614 may also store one or more program modules. In particular, themass storage device 610 and theRAM 614 may store thestate client 102, thestate service 106, themeeting service 110, and/or the other software components described above. Themass storage device 610 andRAM 614 may also store other program modules and data. - In general, software applications or modules may, when loaded into the
CPU 602 and executed transform theCPU 602 and theoverall computer 600 from a general-purpose computing system into a special-purpose computing system customized to perform the functionality presented herein. TheCPU 602 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, theCPU 602 may operate as one or more finite-state machines, in response to executable instructions contained within the software or modules. These computer-executable instructions may transform theCPU 602, by specifying how theCPU 602 transitions between states, thereby physically transforming the transistors or other discrete hardware elements constituting theCPU 602. - Encoding the software or modules onto a mass storage device may also transform the physical structure of the mass storage device or associated computer readable storage media. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the computer readable storage media, whether the computer readable storage media are characterized as primary or secondary storage, and the like. For example, if the computer readable storage media is implemented as semiconductor-based memory, the software or modules may transform the physical state of the semiconductor memory, when the software is encoded therein. For example, the software may transform the states of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory.
- As another example, the computer readable storage media may be implemented using magnetic or optical technology. In such implementations, the software or modules may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.
- Based on the foregoing, it should be appreciated that technologies for providing a meeting-specific state indicator have been presented herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological acts, and computer readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the claims.
- The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.
Claims (20)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/968,332 US9118612B2 (en) | 2010-12-15 | 2010-12-15 | Meeting-specific state indicators |
CN201610808226.3A CN106411697A (en) | 2010-12-15 | 2011-12-14 | Meeting-specific state indicators |
CN2011104432918A CN102546467A (en) | 2010-12-15 | 2011-12-14 | Meeting-specific state indicators |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/968,332 US9118612B2 (en) | 2010-12-15 | 2010-12-15 | Meeting-specific state indicators |
Publications (2)
Publication Number | Publication Date |
---|---|
US20120159347A1 true US20120159347A1 (en) | 2012-06-21 |
US9118612B2 US9118612B2 (en) | 2015-08-25 |
Family
ID=46236147
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/968,332 Active 2031-01-20 US9118612B2 (en) | 2010-12-15 | 2010-12-15 | Meeting-specific state indicators |
Country Status (2)
Country | Link |
---|---|
US (1) | US9118612B2 (en) |
CN (2) | CN102546467A (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8682973B2 (en) | 2011-10-05 | 2014-03-25 | Microsoft Corporation | Multi-user and multi-device collaboration |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US10423301B2 (en) | 2008-08-11 | 2019-09-24 | Microsoft Technology Licensing, Llc | Sections of a presentation having user-definable properties |
US20210281686A1 (en) * | 2019-11-25 | 2021-09-09 | Google Llc | Detecting and flagging acoustic problems in video conferencing |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130145293A1 (en) * | 2011-12-01 | 2013-06-06 | Avaya Inc. | Methods, apparatuses, and computer-readable media for providing availability metaphor(s) representing communications availability in an interactive map |
CN103731405B (en) * | 2012-10-16 | 2017-08-29 | 华为技术有限公司 | The method and apparatus that shared information is presented in data sharing for demonstration end equipment |
USD799534S1 (en) * | 2014-06-24 | 2017-10-10 | Robert Bosch Gmbh | Display screen with graphical user interface |
US10291597B2 (en) | 2014-08-14 | 2019-05-14 | Cisco Technology, Inc. | Sharing resources across multiple devices in online meetings |
US10542126B2 (en) | 2014-12-22 | 2020-01-21 | Cisco Technology, Inc. | Offline virtual participation in an online conference meeting |
US9948786B2 (en) | 2015-04-17 | 2018-04-17 | Cisco Technology, Inc. | Handling conferences using highly-distributed agents |
US10291762B2 (en) | 2015-12-04 | 2019-05-14 | Cisco Technology, Inc. | Docking station for mobile computing devices |
US10574609B2 (en) | 2016-06-29 | 2020-02-25 | Cisco Technology, Inc. | Chat room access control |
US10552801B2 (en) | 2016-09-27 | 2020-02-04 | Cisco Technology, Inc. | Hard stop indicator in a collaboration session |
US10592867B2 (en) | 2016-11-11 | 2020-03-17 | Cisco Technology, Inc. | In-meeting graphical user interface display using calendar information and system |
US10516707B2 (en) | 2016-12-15 | 2019-12-24 | Cisco Technology, Inc. | Initiating a conferencing meeting using a conference room device |
US10515117B2 (en) | 2017-02-14 | 2019-12-24 | Cisco Technology, Inc. | Generating and reviewing motion metadata |
US9942519B1 (en) | 2017-02-21 | 2018-04-10 | Cisco Technology, Inc. | Technologies for following participants in a video conference |
US10440073B2 (en) | 2017-04-11 | 2019-10-08 | Cisco Technology, Inc. | User interface for proximity based teleconference transfer |
US10375125B2 (en) | 2017-04-27 | 2019-08-06 | Cisco Technology, Inc. | Automatically joining devices to a video conference |
US10404481B2 (en) | 2017-06-06 | 2019-09-03 | Cisco Technology, Inc. | Unauthorized participant detection in multiparty conferencing by comparing a reference hash value received from a key management server with a generated roster hash value |
US10375474B2 (en) | 2017-06-12 | 2019-08-06 | Cisco Technology, Inc. | Hybrid horn microphone |
US10477148B2 (en) | 2017-06-23 | 2019-11-12 | Cisco Technology, Inc. | Speaker anticipation |
US10516709B2 (en) | 2017-06-29 | 2019-12-24 | Cisco Technology, Inc. | Files automatically shared at conference initiation |
US10706391B2 (en) | 2017-07-13 | 2020-07-07 | Cisco Technology, Inc. | Protecting scheduled meeting in physical room |
US10091348B1 (en) | 2017-07-25 | 2018-10-02 | Cisco Technology, Inc. | Predictive model for voice/video over IP calls |
US10771621B2 (en) | 2017-10-31 | 2020-09-08 | Cisco Technology, Inc. | Acoustic echo cancellation based sub band domain active speaker detection for audio and video conferencing applications |
Citations (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4831552A (en) * | 1987-01-29 | 1989-05-16 | International Business Machines Corporation | Method for concurrently displaying entries from a plurality of different electronic calendars based on interactively entered non-temporal criteria |
US20040161090A1 (en) * | 2003-02-14 | 2004-08-19 | Convoq, Inc. | Rules based real-time communication system |
US20060004911A1 (en) * | 2004-06-30 | 2006-01-05 | International Business Machines Corporation | Method and system for automatically stetting chat status based on user activity in local environment |
US20060026253A1 (en) * | 2004-07-29 | 2006-02-02 | International Business Machines Corporation | Using windowed user interface z-order with collaboration data for improved management of acknowledge of incoming instant messages |
US20060053380A1 (en) * | 2004-09-03 | 2006-03-09 | Spataro Jared M | Systems and methods for collaboration |
US7035865B2 (en) * | 2001-08-28 | 2006-04-25 | International Business Machines Corporation | Calendar-enhanced awareness for instant messaging systems and electronic status boards |
US20060143064A1 (en) * | 2004-12-23 | 2006-06-29 | Mock Von A | Method and system for managing events |
US20060190547A1 (en) * | 2005-02-24 | 2006-08-24 | Ibm Corporation | Method and apparatus for restricting instant messaging during a scheduled event |
US20070011231A1 (en) * | 2005-07-06 | 2007-01-11 | Microsoft Corporation | Application and user interface for facilitating a meeting |
US7233933B2 (en) * | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US20070168447A1 (en) * | 2006-01-19 | 2007-07-19 | Yen-Fu Chen | Method of scheduling calendar entries via an instant messaging interface |
US7248677B2 (en) * | 2000-08-22 | 2007-07-24 | Symbian Software Ltd. | Method of and apparatus for communicating user related information using a wireless information device |
US20080040187A1 (en) * | 2006-08-10 | 2008-02-14 | International Business Machines Corporation | System to relay meeting activity in electronic calendar applications and schedule enforcement agent for electronic meetings |
US20080040188A1 (en) * | 2006-08-08 | 2008-02-14 | Skadool, Inc. | System and method for providing temporary and limited grants of calendar access |
US20090030766A1 (en) * | 2007-07-23 | 2009-01-29 | International Business Machines Corporation | System and method for facilitating meeting preparedness |
US7571210B2 (en) * | 2002-12-06 | 2009-08-04 | Insors Integrated Communications | Methods and systems for linking virtual meeting attendees over a network |
US20090204671A1 (en) * | 2008-02-08 | 2009-08-13 | Microsoft Corporation | In-meeting presence |
US7606862B2 (en) * | 2004-03-31 | 2009-10-20 | International Business Machines Corporation | Method and system for authorizing a restricted callable status in an instant messaging system |
US7743098B2 (en) * | 2007-10-29 | 2010-06-22 | International Business Machines Corporation | Meeting invitation processing in a calendaring system |
US7774221B2 (en) * | 2002-09-04 | 2010-08-10 | Advanced Health Media, Llc | System and method for a planner |
US7869941B2 (en) * | 2006-12-29 | 2011-01-11 | Aol Inc. | Meeting notification and modification service |
US7984387B2 (en) * | 2004-09-15 | 2011-07-19 | International Business Machines Corporation | Dynamic update of data entry in a user interface |
US7992089B2 (en) * | 2008-01-29 | 2011-08-02 | International Business Machines Corporation | Visualization of meeting invitee status as a method of collaboration |
US8126974B2 (en) * | 2008-05-02 | 2012-02-28 | International Business Machines Corporation | Specifying during meeting establishment when respondents are to be prompted for attendance intentions |
US8150719B2 (en) * | 2001-06-27 | 2012-04-03 | At&T Intellectual Property I, Lp | Location and time sensitive wireless calendaring |
US8161419B2 (en) * | 2007-12-17 | 2012-04-17 | Smooth Productions Inc. | Integrated graphical user interface and system with focusing |
US8204942B2 (en) * | 2003-06-30 | 2012-06-19 | Aol Inc. | Intelligent processing in the context of away and offline instant messages |
US8214748B2 (en) * | 2009-09-22 | 2012-07-03 | International Business Machines Corporation | Meeting agenda management |
US8330795B2 (en) * | 2008-06-13 | 2012-12-11 | Polycom, Inc. | Extended presence for video conferencing systems |
US8358762B1 (en) * | 2005-03-21 | 2013-01-22 | Aol Inc. | Conference calls and meetings via electronic messaging interface |
US8385964B2 (en) * | 2005-04-04 | 2013-02-26 | Xone, Inc. | Methods and apparatuses for geospatial-based sharing of information by multiple devices |
US8437461B1 (en) * | 2009-02-25 | 2013-05-07 | Avaya Inc. | Conference participant finder method and apparatus |
US8452839B2 (en) * | 2004-12-23 | 2013-05-28 | Aol Inc. | Offline away messages |
US8560487B2 (en) * | 2010-12-10 | 2013-10-15 | International Business Machines Corporation | Determining and conveying user availability |
US8583148B2 (en) * | 2010-06-07 | 2013-11-12 | Nokia Corporation | Method and apparatus for suggesting a message segment based on a contextual characteristic in order to draft a message |
US8606517B1 (en) * | 2008-04-02 | 2013-12-10 | Strategic Design Federaton W, Inc. | Travel route system and method |
US8631119B2 (en) * | 2010-03-24 | 2014-01-14 | International Business Machines Corporation | Interruptibility awareness service |
US8768308B2 (en) * | 2009-09-29 | 2014-07-01 | Deutsche Telekom Ag | Apparatus and method for creating and managing personal schedules via context-sensing and actuation |
Family Cites Families (254)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2647239B1 (en) | 1989-05-22 | 1991-07-05 | Bull Sa | METHOD FOR GENERATING INTERFACES FOR USER APPLICATIONS VISUALIZABLE ON THE SCREEN OF A COMPUTER SYSTEM AND DEVICE FOR IMPLEMENTING SAID METHOD |
JPH04257046A (en) | 1991-02-12 | 1992-09-11 | Nippon Telegr & Teleph Corp <Ntt> | Cursor display method |
US5337407A (en) | 1991-12-31 | 1994-08-09 | International Business Machines Corporation | Method and system for identifying users in a collaborative computer-based system |
US5339389A (en) | 1991-12-31 | 1994-08-16 | International Business Machines Corporation | User selectable lock regions |
US5495269A (en) | 1992-04-03 | 1996-02-27 | Xerox Corporation | Large area electronic writing system |
US6061064A (en) | 1993-08-31 | 2000-05-09 | Sun Microsystems, Inc. | System and method for providing and using a computer user interface with a view space having discrete portions |
US6049334A (en) | 1993-12-20 | 2000-04-11 | International Business Machines Corporation | Method and system for graphically indicating the activity of a plurality of users within a shared data collection |
EP0736203A1 (en) | 1993-12-23 | 1996-10-09 | Diacom Technologies, Inc. | Method and apparatus for implementing user feedback |
US5704029A (en) | 1994-05-23 | 1997-12-30 | Wright Strategies, Inc. | System and method for completing an electronic form |
AUPM813394A0 (en) | 1994-09-14 | 1994-10-06 | Dolphin Software Pty Ltd | A method and apparatus for preparation of a database document in a local processing apparatus and loading of the database document with data from remote sources |
US5675752A (en) | 1994-09-15 | 1997-10-07 | Sony Corporation | Interactive applications generator for an interactive presentation environment |
US5572248A (en) | 1994-09-19 | 1996-11-05 | Teleport Corporation | Teleconferencing method and system for providing face-to-face, non-animated teleconference environment |
US5821932A (en) | 1995-05-18 | 1998-10-13 | Sun Microsystems, Inc. | Dynamic dialog box facility for graphical user interface for computer system video display |
US5907324A (en) | 1995-06-07 | 1999-05-25 | Intel Corporation | Method for saving and accessing desktop conference characteristics with a persistent conference object |
US5717869A (en) | 1995-11-03 | 1998-02-10 | Xerox Corporation | Computer controlled display system using a timeline to control playback of temporal data representing collaborative activities |
US5821925A (en) | 1996-01-26 | 1998-10-13 | Silicon Graphics, Inc. | Collaborative work environment supporting three-dimensional objects and multiple remote participants |
US5802299A (en) | 1996-02-13 | 1998-09-01 | Microtouch Systems, Inc. | Interactive system for authoring hypertext document collections |
US6343313B1 (en) | 1996-03-26 | 2002-01-29 | Pixion, Inc. | Computer conferencing system with real-time multipoint, multi-speed, multi-stream scalability |
US6628303B1 (en) | 1996-07-29 | 2003-09-30 | Avid Technology, Inc. | Graphical user interface for a motion video planning and editing system for a computer |
US6016478A (en) | 1996-08-13 | 2000-01-18 | Starfish Software, Inc. | Scheduling system with methods for peer-to-peer scheduling of remote users |
US6230185B1 (en) | 1997-07-15 | 2001-05-08 | Eroom Technology, Inc. | Method and apparatus for facilitating communication between collaborators in a networked environment |
US7596755B2 (en) | 1997-12-22 | 2009-09-29 | Ricoh Company, Ltd. | Multimedia visualization and integration environment |
US6018346A (en) | 1998-01-12 | 2000-01-25 | Xerox Corporation | Freeform graphics system having meeting objects for supporting meeting objectives |
US6208339B1 (en) | 1998-06-19 | 2001-03-27 | International Business Machines Corporation | User-interactive data entry display system with entry fields having distinctive and changeable autocomplete |
US6119147A (en) | 1998-07-28 | 2000-09-12 | Fuji Xerox Co., Ltd. | Method and system for computer-mediated, multi-modal, asynchronous meetings in a virtual space |
US6553417B1 (en) | 1998-08-05 | 2003-04-22 | International Business Machines Corporation | Internet data access acknowledgment applet and method |
US6192395B1 (en) | 1998-12-23 | 2001-02-20 | Multitude, Inc. | System and method for visually identifying speaking participants in a multi-participant networked event |
US6738075B1 (en) | 1998-12-31 | 2004-05-18 | Flashpoint Technology, Inc. | Method and apparatus for creating an interactive slide show in a digital imaging device |
US6564246B1 (en) | 1999-02-02 | 2003-05-13 | International Business Machines Corporation | Shared and independent views of shared workspace for real-time collaboration |
JP2000250826A (en) | 1999-03-01 | 2000-09-14 | Fujitsu Ltd | Method and system for reporting state change |
US7469222B1 (en) | 1999-04-08 | 2008-12-23 | Zap.Com Corporation | System and method of consistent internet web site banners that provide portal-like functionality |
US6633315B1 (en) | 1999-05-20 | 2003-10-14 | Microsoft Corporation | Context-based dynamic user interface elements |
US7228492B1 (en) | 1999-07-06 | 2007-06-05 | Ricoh Company, Ltd. | 2D graph displaying document locations of user-specified concept of interest |
US6307573B1 (en) | 1999-07-22 | 2001-10-23 | Barbara L. Barros | Graphic-information flow method and system for visually analyzing patterns and relationships |
US7171567B1 (en) | 1999-08-02 | 2007-01-30 | Harris Interactive, Inc. | System for protecting information over the internet |
US7299405B1 (en) | 2000-03-08 | 2007-11-20 | Ricoh Company, Ltd. | Method and system for information management to facilitate the exchange of ideas during a collaborative effort |
US7454439B1 (en) | 1999-11-24 | 2008-11-18 | At&T Corp. | System and method for large-scale data visualization |
US7246316B2 (en) | 1999-11-30 | 2007-07-17 | Siebel Systems, Inc. | Methods and apparatus for automatically generating presentations |
US6670970B1 (en) | 1999-12-20 | 2003-12-30 | Apple Computer, Inc. | Graduated visual and manipulative translucency for windows |
JP2003524259A (en) | 2000-02-22 | 2003-08-12 | メタカルタ インコーポレイテッド | Spatial coding and display of information |
US7055095B1 (en) | 2000-04-14 | 2006-05-30 | Picsel Research Limited | Systems and methods for digital document processing |
US7124164B1 (en) | 2001-04-17 | 2006-10-17 | Chemtob Helen J | Method and apparatus for providing group interaction via communications networks |
US7478129B1 (en) | 2000-04-18 | 2009-01-13 | Helen Jeanne Chemtob | Method and apparatus for providing group interaction via communications networks |
US8086672B2 (en) | 2000-06-17 | 2011-12-27 | Microsoft Corporation | When-free messaging |
US7051285B1 (en) | 2000-06-28 | 2006-05-23 | Intel Corporation | Controlling the display of pup-up web browser windows |
US20060010023A1 (en) | 2000-10-02 | 2006-01-12 | On Vantage, Inc. | System, method and computer program product for managing meeting planning operations |
WO2002029724A1 (en) | 2000-10-05 | 2002-04-11 | Kloss Ronald J | Timeline publishing system |
AU2001215798A1 (en) | 2000-10-31 | 2002-05-15 | Netscape Communications Corporation | Click-to-add, jot-it-down, and add banner |
US7546334B2 (en) | 2000-11-13 | 2009-06-09 | Digital Doors, Inc. | Data security system and method with adaptive filter |
US6625261B2 (en) | 2000-12-20 | 2003-09-23 | Southwestern Bell Communications Services, Inc. | Method, system and article of manufacture for bookmarking voicemail messages |
SE519884C2 (en) | 2001-02-02 | 2003-04-22 | Scalado Ab | Method for zooming and producing a zoomable image |
US7107312B2 (en) | 2001-02-06 | 2006-09-12 | Lucent Technologies Inc. | Apparatus and method for use in a data/conference call system for automatically collecting participant information and providing all participants with that information for use in collaboration services |
US7299257B2 (en) | 2001-02-06 | 2007-11-20 | Lucent Technologies Inc. | Apparatus and method for use in collaboration services |
US20040027370A1 (en) | 2001-02-15 | 2004-02-12 | Denny Jaeger | Graphic user interface and method for creating slide shows |
JP2002279141A (en) | 2001-03-19 | 2002-09-27 | Ricoh Co Ltd | Information display system, information display method, information display server and information display program |
US7075513B2 (en) | 2001-09-04 | 2006-07-11 | Nokia Corporation | Zooming and panning content on a display screen |
US7299418B2 (en) | 2001-09-10 | 2007-11-20 | International Business Machines Corporation | Navigation method for visual presentations |
KR20040048933A (en) | 2001-10-04 | 2004-06-10 | 코닌클리케 필립스 일렉트로닉스 엔.브이. | Method of styling a user interface and device with adaptive user interface |
US20030122863A1 (en) | 2001-12-28 | 2003-07-03 | International Business Machines Corporation | Navigation tool for slide presentations |
US20030142133A1 (en) | 2002-01-28 | 2003-07-31 | International Business Machines Corporation | Adjusting transparency of windows to reflect recent use |
US20030158900A1 (en) | 2002-02-05 | 2003-08-21 | Santos Richard A. | Method of and apparatus for teleconferencing |
US7299193B2 (en) | 2002-02-06 | 2007-11-20 | International Business Machines Corporation | Method and meeting scheduler for automated meeting scheduling using delegates, representatives, quorums and teams |
US7636754B2 (en) | 2002-03-21 | 2009-12-22 | Cisco Technology, Inc. | Rich multi-media format for use in a collaborative computing system |
US20030179230A1 (en) | 2002-03-25 | 2003-09-25 | Gerry Seidman | Method and apparatus for providing remote peer-to-peer collaborative user interfaces |
US20040128350A1 (en) | 2002-03-25 | 2004-07-01 | Lou Topfl | Methods and systems for real-time virtual conferencing |
US7213051B2 (en) | 2002-03-28 | 2007-05-01 | Webex Communications, Inc. | On-line conference recording system |
US20030222890A1 (en) | 2002-05-31 | 2003-12-04 | David Salesin | System and method for adaptable presentations |
US7512906B1 (en) | 2002-06-04 | 2009-03-31 | Rockwell Automation Technologies, Inc. | System and methodology providing adaptive interface in an industrial controller environment |
US7260257B2 (en) | 2002-06-19 | 2007-08-21 | Microsoft Corp. | System and method for whiteboard and audio capture |
US7073127B2 (en) | 2002-07-01 | 2006-07-04 | Arcsoft, Inc. | Video editing GUI with layer view |
US20040024822A1 (en) | 2002-08-01 | 2004-02-05 | Werndorfer Scott M. | Apparatus and method for generating audio and graphical animations in an instant messaging environment |
DE10235470B4 (en) | 2002-08-02 | 2005-10-06 | Siemens Ag | Method, subscriber device and radio communication system for transmitting user data messages |
US20040030992A1 (en) | 2002-08-06 | 2004-02-12 | Trandafir Moisa | System and method for management of a virtual enterprise |
US7466334B1 (en) | 2002-09-17 | 2008-12-16 | Commfore Corporation | Method and system for recording and indexing audio and video conference calls allowing topic-based notification and navigation of recordings |
US7555108B2 (en) | 2002-10-01 | 2009-06-30 | Nortel Networks Limited | Presence information for telephony users |
US7818678B2 (en) | 2002-10-31 | 2010-10-19 | Litera Technology Llc | Collaborative document development and review system |
US7129934B2 (en) | 2003-01-31 | 2006-10-31 | Hewlett-Packard Development Company, L.P. | Collaborative markup projection system |
KR20050104382A (en) | 2003-02-19 | 2005-11-02 | 코닌클리케 필립스 일렉트로닉스 엔.브이. | System for ad hoc sharing of content items between portable devices and interaction methods therefor |
US7251786B2 (en) | 2003-02-26 | 2007-07-31 | Microsoft Corporation | Meeting information |
US7730407B2 (en) | 2003-02-28 | 2010-06-01 | Fuji Xerox Co., Ltd. | Systems and methods for bookmarking live and recorded multimedia documents |
US7222305B2 (en) | 2003-03-13 | 2007-05-22 | Oracle International Corp. | Method of sharing a desktop with attendees of a real-time collaboration |
US7451183B2 (en) | 2003-03-21 | 2008-11-11 | Hewlett-Packard Development Company, L.P. | Assembly and method for balancing processors in a partitioned server |
US20040194033A1 (en) | 2003-03-31 | 2004-09-30 | Holzwarth Robert K. | Late binding of stamped page content in a production document workflow |
US20040196286A1 (en) | 2003-04-01 | 2004-10-07 | Microsoft Corporation | Progressive scale graph |
US7269787B2 (en) | 2003-04-28 | 2007-09-11 | International Business Machines Coporation | Multi-document context aware annotation system |
US7203479B2 (en) | 2003-05-02 | 2007-04-10 | Nokia Corporation | Using a mobile station for productivity tracking |
US20040230594A1 (en) | 2003-05-15 | 2004-11-18 | Flam Ran J. | Reject activities in a process control system |
US7257769B2 (en) | 2003-06-05 | 2007-08-14 | Siemens Communications, Inc. | System and method for indicating an annotation for a document |
US7428000B2 (en) | 2003-06-26 | 2008-09-23 | Microsoft Corp. | System and method for distributed meetings |
US7444598B2 (en) | 2003-06-30 | 2008-10-28 | Microsoft Corporation | Exploded views for providing rich regularized geometric transformations and interaction models on content for viewing, previewing, and interacting with documents, projects, and tasks |
US20050005025A1 (en) | 2003-07-04 | 2005-01-06 | Michael Harville | Method for managing a streaming media service |
US20050018828A1 (en) | 2003-07-25 | 2005-01-27 | Siemens Information And Communication Networks, Inc. | System and method for indicating a speaker during a conference |
US7734690B2 (en) | 2003-09-05 | 2010-06-08 | Microsoft Corporation | Method and apparatus for providing attributes of a collaboration system in an operating system folder-based file system |
US20050171830A1 (en) | 2003-09-24 | 2005-08-04 | Greg Miller | System and method for managing and utilizing information |
US8819128B2 (en) | 2003-09-30 | 2014-08-26 | Apple Inc. | Apparatus, method, and computer program for providing instant messages related to a conference call |
US7242389B1 (en) | 2003-10-07 | 2007-07-10 | Microsoft Corporation | System and method for a large format collaborative display for sharing information |
US7911409B1 (en) | 2003-10-07 | 2011-03-22 | Adobe Systems Incorporated | Independent views generated for multiple display devices by a software application |
US7590941B2 (en) | 2003-10-09 | 2009-09-15 | Hewlett-Packard Development Company, L.P. | Communication and collaboration system using rich media environments |
US8230366B2 (en) | 2003-10-23 | 2012-07-24 | Apple Inc. | Dynamically changing cursor for user interface |
US7275212B2 (en) | 2003-10-23 | 2007-09-25 | Microsoft Corporation | Synchronized graphics and region data for graphics remoting systems |
US20050125717A1 (en) | 2003-10-29 | 2005-06-09 | Tsakhi Segal | System and method for off-line synchronized capturing and reviewing notes and presentations |
US7260278B2 (en) | 2003-11-18 | 2007-08-21 | Microsoft Corp. | System and method for real-time whiteboard capture and processing |
US20050125246A1 (en) | 2003-12-09 | 2005-06-09 | International Business Machines Corporation | Participant tool to support online meetings |
US7707503B2 (en) | 2003-12-22 | 2010-04-27 | Palo Alto Research Center Incorporated | Methods and systems for supporting presentation tools using zoomable user interface |
US7401300B2 (en) | 2004-01-09 | 2008-07-15 | Nokia Corporation | Adaptive user interface input device |
US20080288889A1 (en) | 2004-02-20 | 2008-11-20 | Herbert Dennis Hunt | Data visualization application |
CA2560386C (en) | 2004-03-23 | 2013-09-24 | Google Inc. | A digital mapping system |
US8667401B1 (en) | 2004-05-26 | 2014-03-04 | Adobe Systems Incorporated | System and method for archiving collaborative electronic meetings |
US7535481B2 (en) | 2004-06-28 | 2009-05-19 | Microsoft Corporation | Orienting information presented to users located at different sides of a display surface |
US20060010197A1 (en) | 2004-07-06 | 2006-01-12 | Francis Ovenden | Multimedia collaboration and communications |
US7451186B2 (en) | 2004-08-10 | 2008-11-11 | Microsoft Corporation | Method and system of integrating instant messaging with other computer programs |
US20070005752A1 (en) | 2005-06-29 | 2007-01-04 | Jitendra Chawla | Methods and apparatuses for monitoring attention of a user during a collaboration session |
US8270320B2 (en) | 2004-09-30 | 2012-09-18 | Avaya Inc. | Method and apparatus for launching a conference based on presence of invitees |
US20060080610A1 (en) | 2004-10-12 | 2006-04-13 | Kaminsky David L | Methods, systems and computer program products for outline views in computer displayable presentations |
US7292244B2 (en) | 2004-10-18 | 2007-11-06 | Microsoft Corporation | System and method for automatic label placement on charts |
US7505051B2 (en) | 2004-12-16 | 2009-03-17 | Corel Tw Corp. | Method for generating a slide show of an image |
JP4738805B2 (en) | 2004-12-16 | 2011-08-03 | 株式会社リコー | Screen sharing system, screen sharing method, screen sharing program |
US7614000B2 (en) | 2004-12-20 | 2009-11-03 | Microsoft Corporation | File formats, methods, and computer program products for representing presentations |
US20060167996A1 (en) | 2005-01-13 | 2006-07-27 | Orsolini Garry S | System and method for enabling electronic presentations |
US7953794B2 (en) | 2005-01-14 | 2011-05-31 | Microsoft Corporation | Method and system for transitioning between synchronous and asynchronous communication modes |
US7395508B2 (en) | 2005-01-14 | 2008-07-01 | International Business Machines Corporation | Method and apparatus for providing an interactive presentation environment |
US7599989B2 (en) | 2005-01-24 | 2009-10-06 | Microsoft Corporation | System and method for gathering and reporting screen resolutions of attendees of a collaboration session |
US20060168533A1 (en) | 2005-01-27 | 2006-07-27 | Microsoft Corporation | System and method for providing an indication of what part of a screen is being shared |
US7383495B2 (en) | 2005-02-15 | 2008-06-03 | Microsoft Corporation | Presentation viewing tool designed for the viewer |
US7801954B2 (en) | 2005-02-25 | 2010-09-21 | Microsoft Corporation | Method and system for providing expanded presence information when a user is offline |
US7669141B1 (en) | 2005-04-11 | 2010-02-23 | Adobe Systems Incorporated | Visual interface element transition effect |
US8831647B2 (en) | 2005-04-19 | 2014-09-09 | Devereux Research Ab Llc | Presence-enabled mobile access |
US20060239212A1 (en) | 2005-04-22 | 2006-10-26 | Cisco Technology, Inc. | Management of missing conference invitees |
US10467593B2 (en) | 2005-04-29 | 2019-11-05 | Oracle America, Inc. | Providing contextual collaboration within enterprise applications |
US8166402B2 (en) | 2005-05-13 | 2012-04-24 | Microsoft Corporation | User interface for managing master and layout relationships |
US20060265398A1 (en) | 2005-05-23 | 2006-11-23 | Kaufman Jason M | System and method for managing review standards in digital documents |
US8560952B2 (en) | 2005-06-13 | 2013-10-15 | Microsoft Corporation | Adding an arbitrary number of placeholders to a custom layout |
US7554576B2 (en) | 2005-06-20 | 2009-06-30 | Ricoh Company, Ltd. | Information capture and recording system for controlling capture devices |
US7679518B1 (en) | 2005-06-28 | 2010-03-16 | Sun Microsystems, Inc. | Meeting facilitation tool |
US8180663B2 (en) | 2005-06-28 | 2012-05-15 | Microsoft Corporation | Facilitating automated meeting scheduling |
US20070033091A1 (en) | 2005-08-08 | 2007-02-08 | Ravikumar Frederick R | Method And System For Managing A Meeting |
JP4707714B2 (en) | 2005-08-15 | 2011-06-22 | 富士通株式会社 | COMMUNICATION CONTROL METHOD, COMPUTER SYSTEM, CONFERENCE MANAGEMENT SERVER, COMMUNICATION METHOD, AND PORTABLE TERMINAL |
US8176004B2 (en) | 2005-10-24 | 2012-05-08 | Capsilon Corporation | Systems and methods for intelligent paperless document management |
US8099458B2 (en) | 2005-10-27 | 2012-01-17 | Microsoft Corporation | Workgroup application with contextual clues |
US20070112926A1 (en) | 2005-11-03 | 2007-05-17 | Hannon Brett | Meeting Management Method and System |
JP4655892B2 (en) | 2005-11-07 | 2011-03-23 | ソニー株式会社 | Recording / reproducing apparatus and recording method |
US7886001B2 (en) | 2005-12-23 | 2011-02-08 | Cisco Technology, Inc. | Method and apparatus for controlling actions based on triggers in a conference |
US8166061B2 (en) | 2006-01-10 | 2012-04-24 | Aol Inc. | Searching recent content publication activity |
US20070185870A1 (en) | 2006-01-27 | 2007-08-09 | Hogue Andrew W | Data object visualization using graphs |
US8718253B2 (en) | 2006-02-01 | 2014-05-06 | Siemens Enterprise Communications, Inc. | Automatic voice conference actions driven by potential conferee presence |
US20070186166A1 (en) | 2006-02-06 | 2007-08-09 | Anderson Kent R | Creation and use of an electronic presentation slide that includes multimedia content |
US7774703B2 (en) | 2006-02-09 | 2010-08-10 | Microsoft Corporation | Virtual shadow awareness for multi-user editors |
US7764247B2 (en) | 2006-02-17 | 2010-07-27 | Microsoft Corporation | Adaptive heads-up user interface for automobiles |
US7567844B2 (en) | 2006-03-17 | 2009-07-28 | Honeywell International Inc. | Building management system |
US8560946B2 (en) | 2006-03-22 | 2013-10-15 | Vistracks, Inc. | Timeline visualizations linked with other visualizations of data in a thin client |
US20070226299A1 (en) | 2006-03-24 | 2007-09-27 | Cisco Technology, Inc. | Method and system for providing an instant messaging quorum monitoring service |
US20070253424A1 (en) | 2006-05-01 | 2007-11-01 | Herot Christopher F | Web-based system and method of establishing an on-line meeting or teleconference |
WO2007134305A2 (en) | 2006-05-12 | 2007-11-22 | Convenous, Llc | Apparatus, system, method and computer program product for collaboration via one or more networks |
US9241038B2 (en) | 2006-05-23 | 2016-01-19 | Microsoft Technology Licensing, Llc | User presence aggregation at a server |
US20070279416A1 (en) | 2006-06-06 | 2007-12-06 | Cobb Glenn A | Enabling and Rendering Business Components in an Interactive Data Visualization Tool |
US20080001717A1 (en) | 2006-06-20 | 2008-01-03 | Trevor Fiatal | System and method for group management |
US20070294612A1 (en) | 2006-06-20 | 2007-12-20 | Microsoft Corporation | Comparing and Managing Multiple Presentations |
US7653705B2 (en) | 2006-06-26 | 2010-01-26 | Microsoft Corp. | Interactive recording and playback for network conferencing |
US20070300185A1 (en) | 2006-06-27 | 2007-12-27 | Microsoft Corporation | Activity-centric adaptive user interface |
CN101098267B (en) | 2006-06-28 | 2011-07-20 | 华为技术有限公司 | Method and system for establishing cluster conversation |
US20080005235A1 (en) | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Collaborative integrated development environment using presence information |
US8782542B2 (en) | 2006-07-19 | 2014-07-15 | Red Hat, Inc. | Display and management of a service composition candidate inventory |
US8647126B2 (en) | 2006-08-30 | 2014-02-11 | The Boeing Company | System and computer program product for developing and delivering a training course |
US7925982B2 (en) | 2006-09-01 | 2011-04-12 | Cheryl Parker | System and method of overlaying and integrating data with geographic mapping applications |
US20080065580A1 (en) | 2006-09-11 | 2008-03-13 | Microsoft Corporation | Unified user work environment for surfacing cross document relationships and componentized functionality |
US7848265B2 (en) | 2006-09-21 | 2010-12-07 | Siemens Enterprise Communications, Inc. | Apparatus and method for automatic conference initiation |
US7698648B2 (en) | 2006-10-23 | 2010-04-13 | Microsoft Corporation | Animation of icons based on presence |
US20080109406A1 (en) | 2006-11-06 | 2008-05-08 | Santhana Krishnasamy | Instant message tagging |
US7698660B2 (en) | 2006-11-13 | 2010-04-13 | Microsoft Corporation | Shared space for communicating information |
US20080141126A1 (en) | 2006-11-17 | 2008-06-12 | Vincent Lee Johnson | Method and system to aid in viewing digital content |
US20080133551A1 (en) | 2006-11-30 | 2008-06-05 | Ava Mobile, Inc. | System, method, and computer program product for managing rights of media in collaborative environments |
US20080263010A1 (en) | 2006-12-12 | 2008-10-23 | Microsoft Corporation | Techniques to selectively access meeting content |
WO2009075689A2 (en) | 2006-12-21 | 2009-06-18 | Metacarta, Inc. | Methods of systems of using geographic meta-metadata in information retrieval and document displays |
US20080177782A1 (en) | 2007-01-10 | 2008-07-24 | Pado Metaware Ab | Method and system for facilitating the production of documents |
US7730411B2 (en) | 2007-02-01 | 2010-06-01 | Cisco Technology, Inc. | Re-creating meeting context |
US8045489B2 (en) | 2007-03-30 | 2011-10-25 | Cisco Technology, Inc. | Method and system for the automatic configuration of conference resources |
US20080244442A1 (en) | 2007-03-30 | 2008-10-02 | Microsoft Corporation | Techniques to share information between application programs |
US20080263460A1 (en) | 2007-04-20 | 2008-10-23 | Utbk, Inc. | Methods and Systems to Connect People for Virtual Meeting in Virtual Reality |
US20080300944A1 (en) | 2007-05-31 | 2008-12-04 | Cisco Technology, Inc. | Relevant invitee list for conference system |
US8384710B2 (en) | 2007-06-07 | 2013-02-26 | Igt | Displaying and using 3D graphics on multiple displays provided for gaming environments |
US9965132B2 (en) | 2007-06-08 | 2018-05-08 | Apple Inc. | Presenting text messages |
US8392503B2 (en) | 2007-06-19 | 2013-03-05 | Cisco Technology, Inc. | Reporting participant attention level to presenter during a web-based rich-media conference |
US7949952B2 (en) | 2007-06-26 | 2011-05-24 | International Business Machines Corporation | Method and system for providing user representations in real-time collaboration session participant lists reflecting external communications together with user representations in external communication applications indicating current real-time collaboration session participation |
US8266534B2 (en) | 2007-06-28 | 2012-09-11 | Microsoft Corporation | Collaborative generation of meeting minutes and agenda confirmation |
US20090043856A1 (en) | 2007-08-09 | 2009-02-12 | At&T Knowledge Ventures, Lp | Instant Messenger with Visible Attributes on the Presence Line |
JP2009042187A (en) | 2007-08-10 | 2009-02-26 | Aisin Aw Co Ltd | Navigation device and navigation program |
US20090055739A1 (en) | 2007-08-23 | 2009-02-26 | Microsoft Corporation | Context-aware adaptive user interface |
US8050917B2 (en) | 2007-09-27 | 2011-11-01 | Siemens Enterprise Communications, Inc. | Method and apparatus for identification of conference call participants |
US9170997B2 (en) | 2007-09-27 | 2015-10-27 | Adobe Systems Incorporated | Commenting dynamic content |
US20130125051A1 (en) | 2007-09-28 | 2013-05-16 | Adobe Systems Incorporated | Historical review using manipulable visual indicators |
US8719920B2 (en) | 2007-10-25 | 2014-05-06 | International Business Machines Corporation | Arrangements for identifying users in a multi-touch surface environment |
US7962525B2 (en) | 2007-11-05 | 2011-06-14 | Microsoft Corporation | Automated capture of information generated at meetings |
US20090119604A1 (en) | 2007-11-06 | 2009-05-07 | Microsoft Corporation | Virtual office devices |
US7941399B2 (en) | 2007-11-09 | 2011-05-10 | Microsoft Corporation | Collaborative authoring |
US7950064B2 (en) | 2007-11-16 | 2011-05-24 | International Business Machines Corporation | System and method for controlling comments in a collaborative document |
US20090138552A1 (en) | 2007-11-26 | 2009-05-28 | Nortel Networks Limited | Apparatus and method for managing communication between parties |
US20090234721A1 (en) | 2007-12-21 | 2009-09-17 | Bigelow David H | Persistent collaborative on-line meeting space |
US20090210822A1 (en) | 2008-02-18 | 2009-08-20 | Microsoft Corporation | Locating meeting users |
CN101515226B (en) | 2008-02-19 | 2011-07-27 | 联想(北京)有限公司 | Dual-system display method, notebook computer with assistant screen, and assistant display device |
US9824333B2 (en) | 2008-02-29 | 2017-11-21 | Microsoft Technology Licensing, Llc | Collaborative management of activities occurring during the lifecycle of a meeting |
US7890599B2 (en) | 2008-03-07 | 2011-02-15 | Arun Kalmanje | Pause and replay of media content through bookmarks on a server device |
US20090235177A1 (en) | 2008-03-14 | 2009-09-17 | Microsoft Corporation | Multi-monitor remote desktop environment user interface |
JP5368547B2 (en) | 2008-04-05 | 2013-12-18 | ソーシャル・コミュニケーションズ・カンパニー | Shared virtual area communication environment based apparatus and method |
US8032832B2 (en) | 2008-04-21 | 2011-10-04 | Microsoft Corporation | Non-linear presentation canvas |
SG190645A1 (en) | 2008-04-24 | 2013-06-28 | Movideo Pty Ltd | System and method for tracking usage |
US8352870B2 (en) | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
US9177285B2 (en) | 2008-05-06 | 2015-11-03 | Fuji Xerox Co., Ltd. | Method and system for controlling a space based on media content |
EP2304588A4 (en) | 2008-06-11 | 2011-12-21 | Teliris Inc | Surface computing collaboration system, method and apparatus |
US9092053B2 (en) | 2008-06-17 | 2015-07-28 | Apple Inc. | Systems and methods for adjusting a display based on the user's position |
US20090327019A1 (en) | 2008-06-25 | 2009-12-31 | International Business Machines Corporation | Meeting scheduling system |
US20090327425A1 (en) | 2008-06-25 | 2009-12-31 | Microsoft Corporation | Switching between and dual existence in live and recorded versions of a meeting |
US20100031152A1 (en) | 2008-07-31 | 2010-02-04 | Microsoft Corporation | Creation and Navigation of Infinite Canvas Presentation |
US20100037151A1 (en) | 2008-08-08 | 2010-02-11 | Ginger Ackerman | Multi-media conferencing system |
US8489999B2 (en) | 2008-09-02 | 2013-07-16 | Accenture Global Services Limited | Shared user interface surface system |
CN101364886B (en) | 2008-09-18 | 2011-04-06 | 广州飞瑞敖电子科技有限公司 | Wireless meeting system |
US8223156B2 (en) | 2008-09-26 | 2012-07-17 | International Business Machines Corporation | Time dependent virtual universe avatar rendering |
US9569406B2 (en) | 2008-10-08 | 2017-02-14 | Adobe Systems Incorporated | Electronic content change tracking |
US20100095198A1 (en) | 2008-10-15 | 2010-04-15 | Apple Inc. | Shared comments for online document collaboration |
CN101729636A (en) | 2008-10-16 | 2010-06-09 | 鸿富锦精密工业(深圳)有限公司 | Mobile terminal |
US20100131868A1 (en) | 2008-11-26 | 2010-05-27 | Cisco Technology, Inc. | Limitedly sharing application windows in application sharing sessions |
US8464167B2 (en) | 2008-12-01 | 2013-06-11 | Palo Alto Research Center Incorporated | System and method for synchronized authoring and access of chat and graphics |
CN101789871B (en) | 2009-01-23 | 2012-10-03 | 国际商业机器公司 | Method, server device and client device for supporting plurality of simultaneous online conferences |
US8037166B2 (en) | 2009-01-26 | 2011-10-11 | Google Inc. | System and method of displaying search results based on density |
JP2010176320A (en) | 2009-01-28 | 2010-08-12 | Seiko Epson Corp | Image processing method, program of the same, and image processing apparatus |
US8930843B2 (en) | 2009-02-27 | 2015-01-06 | Adobe Systems Incorporated | Electronic content workflow review process |
US9171284B2 (en) | 2009-03-02 | 2015-10-27 | Microsoft Technology Licensing, Llc | Techniques to restore communications sessions for applications having conversation and meeting environments |
GB0904414D0 (en) | 2009-03-13 | 2009-04-29 | Brotherton Lawrence J | Keystep system |
US20100235216A1 (en) | 2009-03-16 | 2010-09-16 | Microsoft Corporation | Integration of pre-meeting and post-meeting experience into a meeting lifecycle |
US9159074B2 (en) | 2009-03-23 | 2015-10-13 | Yahoo! Inc. | Tool for embedding comments for objects in an article |
US8887069B2 (en) | 2009-03-31 | 2014-11-11 | Voispot, Llc | Virtual meeting place system and method |
US8179449B2 (en) | 2009-05-20 | 2012-05-15 | Sony Ericsson Mobile Communications Ab | Portable electronic apparatus including a display and method for controlling display content based on movement of the display and user position |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US8943408B2 (en) | 2009-05-27 | 2015-01-27 | Adobe Systems Incorporated | Text image review process |
US20100306018A1 (en) | 2009-05-27 | 2010-12-02 | Microsoft Corporation | Meeting State Recall |
US20100324963A1 (en) | 2009-06-18 | 2010-12-23 | Microsoft Corporation | Tag presence alerts for groups and meeting |
CN102292713A (en) | 2009-06-30 | 2011-12-21 | 唐桥科技有限公司 | A multimedia collaboration system |
CA2714523A1 (en) | 2009-09-02 | 2011-03-02 | Sophia Learning, Llc | Teaching and learning system |
US20110113351A1 (en) | 2009-11-09 | 2011-05-12 | International Business Machines Corporation | Context restoration via saved history when rejoining a multi-user environment |
US8335763B2 (en) | 2009-12-04 | 2012-12-18 | Microsoft Corporation | Concurrently presented data subfeeds |
US20110154180A1 (en) | 2009-12-17 | 2011-06-23 | Xerox Corporation | User-specific digital document annotations for collaborative review process |
US20110239142A1 (en) | 2010-03-25 | 2011-09-29 | Nokia Corporation | Method and apparatus for providing content over multiple displays |
US20110295879A1 (en) | 2010-05-27 | 2011-12-01 | Neuone, Llc | Systems and methods for document management |
US9032314B2 (en) | 2010-12-01 | 2015-05-12 | Microsoft Technology Licensing, Llc | Proposing visual display components for processing data |
US20120150863A1 (en) | 2010-12-13 | 2012-06-14 | Microsoft Corporation | Bookmarking of meeting context |
US20120150577A1 (en) | 2010-12-14 | 2012-06-14 | Microsoft Corporation | Meeting lifecycle management |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US20120233543A1 (en) | 2011-03-08 | 2012-09-13 | Google, Inc. | Collaborative Electronic Document Editing |
US20130035853A1 (en) | 2011-08-03 | 2013-02-07 | Google Inc. | Prominence-Based Generation and Rendering of Map Features |
US20130246903A1 (en) | 2011-09-11 | 2013-09-19 | Keith Douglas Mukai | System and methods for structured evaluation, analysis, and retrieval of document contents |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
US8682973B2 (en) | 2011-10-05 | 2014-03-25 | Microsoft Corporation | Multi-user and multi-device collaboration |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
-
2010
- 2010-12-15 US US12/968,332 patent/US9118612B2/en active Active
-
2011
- 2011-12-14 CN CN2011104432918A patent/CN102546467A/en active Pending
- 2011-12-14 CN CN201610808226.3A patent/CN106411697A/en active Pending
Patent Citations (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4831552A (en) * | 1987-01-29 | 1989-05-16 | International Business Machines Corporation | Method for concurrently displaying entries from a plurality of different electronic calendars based on interactively entered non-temporal criteria |
US7248677B2 (en) * | 2000-08-22 | 2007-07-24 | Symbian Software Ltd. | Method of and apparatus for communicating user related information using a wireless information device |
US8150719B2 (en) * | 2001-06-27 | 2012-04-03 | At&T Intellectual Property I, Lp | Location and time sensitive wireless calendaring |
US7233933B2 (en) * | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US7035865B2 (en) * | 2001-08-28 | 2006-04-25 | International Business Machines Corporation | Calendar-enhanced awareness for instant messaging systems and electronic status boards |
US7774221B2 (en) * | 2002-09-04 | 2010-08-10 | Advanced Health Media, Llc | System and method for a planner |
US7571210B2 (en) * | 2002-12-06 | 2009-08-04 | Insors Integrated Communications | Methods and systems for linking virtual meeting attendees over a network |
US20040161090A1 (en) * | 2003-02-14 | 2004-08-19 | Convoq, Inc. | Rules based real-time communication system |
US8204942B2 (en) * | 2003-06-30 | 2012-06-19 | Aol Inc. | Intelligent processing in the context of away and offline instant messages |
US7606862B2 (en) * | 2004-03-31 | 2009-10-20 | International Business Machines Corporation | Method and system for authorizing a restricted callable status in an instant messaging system |
US20060004911A1 (en) * | 2004-06-30 | 2006-01-05 | International Business Machines Corporation | Method and system for automatically stetting chat status based on user activity in local environment |
US20060026253A1 (en) * | 2004-07-29 | 2006-02-02 | International Business Machines Corporation | Using windowed user interface z-order with collaboration data for improved management of acknowledge of incoming instant messages |
US20060053380A1 (en) * | 2004-09-03 | 2006-03-09 | Spataro Jared M | Systems and methods for collaboration |
US7984387B2 (en) * | 2004-09-15 | 2011-07-19 | International Business Machines Corporation | Dynamic update of data entry in a user interface |
US20060143064A1 (en) * | 2004-12-23 | 2006-06-29 | Mock Von A | Method and system for managing events |
US8452839B2 (en) * | 2004-12-23 | 2013-05-28 | Aol Inc. | Offline away messages |
US20060190547A1 (en) * | 2005-02-24 | 2006-08-24 | Ibm Corporation | Method and apparatus for restricting instant messaging during a scheduled event |
US8358762B1 (en) * | 2005-03-21 | 2013-01-22 | Aol Inc. | Conference calls and meetings via electronic messaging interface |
US8385964B2 (en) * | 2005-04-04 | 2013-02-26 | Xone, Inc. | Methods and apparatuses for geospatial-based sharing of information by multiple devices |
US20070011231A1 (en) * | 2005-07-06 | 2007-01-11 | Microsoft Corporation | Application and user interface for facilitating a meeting |
US20070168447A1 (en) * | 2006-01-19 | 2007-07-19 | Yen-Fu Chen | Method of scheduling calendar entries via an instant messaging interface |
US20080040188A1 (en) * | 2006-08-08 | 2008-02-14 | Skadool, Inc. | System and method for providing temporary and limited grants of calendar access |
US20080040187A1 (en) * | 2006-08-10 | 2008-02-14 | International Business Machines Corporation | System to relay meeting activity in electronic calendar applications and schedule enforcement agent for electronic meetings |
US7869941B2 (en) * | 2006-12-29 | 2011-01-11 | Aol Inc. | Meeting notification and modification service |
US20090030766A1 (en) * | 2007-07-23 | 2009-01-29 | International Business Machines Corporation | System and method for facilitating meeting preparedness |
US7743098B2 (en) * | 2007-10-29 | 2010-06-22 | International Business Machines Corporation | Meeting invitation processing in a calendaring system |
US8161419B2 (en) * | 2007-12-17 | 2012-04-17 | Smooth Productions Inc. | Integrated graphical user interface and system with focusing |
US7992089B2 (en) * | 2008-01-29 | 2011-08-02 | International Business Machines Corporation | Visualization of meeting invitee status as a method of collaboration |
US20090204671A1 (en) * | 2008-02-08 | 2009-08-13 | Microsoft Corporation | In-meeting presence |
US8606517B1 (en) * | 2008-04-02 | 2013-12-10 | Strategic Design Federaton W, Inc. | Travel route system and method |
US8126974B2 (en) * | 2008-05-02 | 2012-02-28 | International Business Machines Corporation | Specifying during meeting establishment when respondents are to be prompted for attendance intentions |
US8330795B2 (en) * | 2008-06-13 | 2012-12-11 | Polycom, Inc. | Extended presence for video conferencing systems |
US8437461B1 (en) * | 2009-02-25 | 2013-05-07 | Avaya Inc. | Conference participant finder method and apparatus |
US8214748B2 (en) * | 2009-09-22 | 2012-07-03 | International Business Machines Corporation | Meeting agenda management |
US8768308B2 (en) * | 2009-09-29 | 2014-07-01 | Deutsche Telekom Ag | Apparatus and method for creating and managing personal schedules via context-sensing and actuation |
US8631119B2 (en) * | 2010-03-24 | 2014-01-14 | International Business Machines Corporation | Interruptibility awareness service |
US8583148B2 (en) * | 2010-06-07 | 2013-11-12 | Nokia Corporation | Method and apparatus for suggesting a message segment based on a contextual characteristic in order to draft a message |
US8560487B2 (en) * | 2010-12-10 | 2013-10-15 | International Business Machines Corporation | Determining and conveying user availability |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10423301B2 (en) | 2008-08-11 | 2019-09-24 | Microsoft Technology Licensing, Llc | Sections of a presentation having user-definable properties |
US10699244B2 (en) | 2009-05-26 | 2020-06-30 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US11675471B2 (en) | 2010-12-15 | 2023-06-13 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
US10033774B2 (en) | 2011-10-05 | 2018-07-24 | Microsoft Technology Licensing, Llc | Multi-user and multi-device collaboration |
US8682973B2 (en) | 2011-10-05 | 2014-03-25 | Microsoft Corporation | Multi-user and multi-device collaboration |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US11023482B2 (en) | 2011-10-13 | 2021-06-01 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US20210281686A1 (en) * | 2019-11-25 | 2021-09-09 | Google Llc | Detecting and flagging acoustic problems in video conferencing |
US11778106B2 (en) * | 2019-11-25 | 2023-10-03 | Google Llc | Detecting and flagging acoustic problems in video conferencing |
Also Published As
Publication number | Publication date |
---|---|
CN102546467A (en) | 2012-07-04 |
CN106411697A (en) | 2017-02-15 |
US9118612B2 (en) | 2015-08-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9118612B2 (en) | Meeting-specific state indicators | |
US10038619B2 (en) | Providing a monitoring service in a cloud-based computing environment | |
AU2011265626B2 (en) | Role-based presentation views | |
JP2018198069A (en) | Sharing notes in online meetings | |
US20150058425A1 (en) | Smart meeting service | |
US20150170045A1 (en) | Event attendance prediction | |
US10185605B2 (en) | In-order message processing with message-dependency handling | |
US10645088B1 (en) | Generic unified presence detection system | |
US10726082B2 (en) | Social networking information consumption gap resolution | |
US20070271337A1 (en) | Quorum for a Real-Time, Collaborative Electronic Meeting | |
US20120185259A1 (en) | Topic-based calendar availability | |
US20120016708A1 (en) | Dynamic management of invitations to a meeting utilizing a cascaded tier of potential invitees | |
US20170257401A1 (en) | Providing social context to calendar events | |
US20190392399A1 (en) | State-based electronic event processing system | |
EP2812861A1 (en) | Representing remotely available users through working elsewhere status | |
US20170083870A1 (en) | Social planning | |
US10984392B2 (en) | Providing multi-session event invitation | |
US9628629B1 (en) | Providing conference call aid based on upcoming deadline | |
US20180122172A1 (en) | Enriched polling user experience | |
US20210065015A1 (en) | Computerized platform for facilitating group based decision making | |
US11088969B1 (en) | Calendar based auto-reply messages | |
CN115312208A (en) | Method, device, equipment and medium for displaying treatment data | |
US20180365652A1 (en) | Providing anomaly based notification on calendar | |
US20160321615A1 (en) | Inferences and actions based on actions to add worker to job waiting lists | |
US20160063447A1 (en) | Filtering calendar notifications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FISH, NATHAN JAMES;FERGUSON, LESLIE RAE;BERG, JEFFREY;AND OTHERS;SIGNING DATES FROM 20101206 TO 20101207;REEL/FRAME:025551/0453 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0001 Effective date: 20141014 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |