The present invention relates to telecommunications, and more particularly to collaborative communications.
A user of an electronic document (e.g., a Word™ file, an Excel™ file, an e-mail file, etc.) might, at times, need to reach others that are in some way associated (e.g., co-authors, etc.) with the document. For example, assume that one of three co-workers is drafting a document that summarizes the collective efforts of the three co-workers on a project. The drafter requires information from the other two co-workers. To obtain the required information, the drafter might send (e.g., via e-mail, etc.) an electronic copy of the document to the co-workers and attempt to establish a conference call. This will require that the drafter obtain contact numbers (e.g., URL, phone number, etc.) of the co-workers, send the document to them and place the telephone calls. Of course, attempts at communication can be frustrated by an inability to reach one or both of the co-workers.
As a consequence, it would be beneficial if this process of communication and collaboration could be streamlined.
The present invention provides a mechanism for streamlining the collaborative process. In accordance with the illustrative embodiment, a user of an electronic device (e.g., PC, PDA, etc.) initiates communication with other individuals that are associated with a specific document or application of interest that is stored in the electronic device. The identity of the individuals that are to participate in the communication is determined based on what the user is doing with the electronic device; that is, which document or application is active.
In the illustrative embodiment, communication is established by (1) activating the document or application of interest (if it's not already active) and then (2) initiating communications between the associated individuals via a single action. The action can be, for example, activating a single soft key or issuing a voice command via the telecommunication capabilities of the electronic device in which the document or application is stored.
Once action is taken to initiate communications, the electronic device, in conjunction with contextual communications software:
The communication can be a notification (i.e., a call, a voice mail, or text message on devices specified in the contact information), a conference (i.e., voice, IM session, etc.) or a collaboration (i.e., conference plus sharing the document or application). Communications are supported by, for example, an IP network, the public-switched telephone network, or cellular-phone network.
By handling communications in the context of the document or application of interest, the illustrative embodiment of the present invention eliminates having to set up the communication in a more manual and typically less efficient fashion.
Referring now to
A variety of documents and programs can be “open” on the desktop of a personal computer at one time. In particular, in the Microsoft Windows graphical interface, each open document or application resides in a different window. But only one window, and, hence, one document or application, can be active at one time. For example, in FIG. 2, there are two documents, 202 and 204, that are open in desktop 200. The active document (i.e., the document that has the “focus” of the electronic device) is document 202.
A user activates a document or program of interest among several open documents and applications by, for example, “clicking” on the window or ikon that is associated with the document or application. The window that has the focus of the electronic device, which is the window in which the activated document or application resides, is referred to herein as the “contextual window.” The contextual window is the window to which contextual communication software looks to find the document or application that is to be the focus of contextual communications.
At task 104, a user initiates communication between at least two individuals that are associated with the active document or application. As described in further detail later in this specification, an “associated” individual is someone that is involved in some manner with the document or application of interest. This task is performed using a single command, such as by clicking on a single soft key or verbalizing the request using a voice interface. The communication can be a “notification,” a “conference,” or a “collaboration;” these concepts are described in detail later in this specification. In some embodiments, a user selects the type of communication that is desired by clicking on one of three different soft keys, etc., one for “notification,” one for “conference,” and one for “collaboration.”
At task 306, a command is received to establish communication between at least two individuals that are associated with the active electronic document or application.
To perform task 306, the active document or application is identified. This is accomplished in task 308 by contextual communications software (running on the electronic device), which utilizes information in the electronic device that indicates which window is the contextual window or otherwise indicates which document or application is active. Those skilled in the art are familiar with what this information is and how to access it.
At task 310, the electronic device, in conjunction with the contextual communications software, establishes communication between at least two individuals that are associated with the electronic document or application of interest.
Referring now to
In a first example, four co-workers have developed a product. A document is being prepared to summarize the co-workers' efforts. The four co-workers are “associated” with the document. In a second example, a patent application is being prepared by a patent attorney at the request of the general counsel of a technology company. The “associated” individuals might be the patent attorney, the general counsel, and the inventors of the subject matter that is being disclosed in the patent application. In a third example, four individuals regularly compete against one another on an interactive electronic game. Those four individuals are associated with the application (game).
There are a variety of mechanisms or structures by which contextual communications software can identify an individual as being “associated” with a document or application. A few of these structures are described below.
For a Microsoft Office data file (e.g., a Word file, etc.), associated individuals can be listed in the “Properties” table of the data file under “Author,” etc. For non-generic documents, the appropriate section of the data file can be flagged as a direction to the contextual communications software to look to that section for the associated individuals. For an e-mail, associated individuals appear can appear in any one or more of the “From,” “To,” “cc,” and “bcc” lists. For applications that do not have structures from which to determine the associated individuals, a list of associated individuals can be created by the user.
In accordance with the illustrative embodiment, the originator of the communication can select a subset of individuals for communication from the list of associated individuals. In other words, the user has the opportunity to drop (or add) associated individuals before contact (i.e., notification, conference, or collaboration) is made. In some embodiments, this is implemented as follows. After the command to initiate communications is given, an “initiate dialog” box appears with a list of associated individuals. In some embodiments, an indication is provided as to the availability of each listed individual, as determined, for example, by a presence server (discussed further below). The originator can then select some or all of individuals for participation in the forthcoming communication. Furthermore, the originator can decide to cancel the communication. This might occur, for example, if an insufficient number of individuals were available for the conference, or perhaps, if a key individual is not available.
Returning to the description of the sub-tasks of task 310 (see
In some embodiments, contact number(s) (e.g., phone number, SIP URL, IP address, etc.) are maintained in an associated-individuals profile database, such as an SIP registrar that contains information pertaining to associated individuals' active communications devices. In some other embodiments, a presence server keeps track of current contact information for associated individuals. Associated individuals can register several numbers with the presence server. For example, an associated individual can provide a cell-phone number, a PSTN number, an e-mail address, etc. As described in further detail later in this specification, the presence server can be used to determine if an associated individual is “present.” In particular, assuming that the contact number is a cell-phone number, the presence server can determine whether or not that cell-phone is on.
At sub-task 416, communication is launched. In some embodiments, the communication is a “notification.” The notification can specify that a “conference” and/or “collaboration” is to begin immediately or at some time in the future. As used in this specification, the term “notification,” means a message (e.g., phone call, e-mail, etc.) that is electronically sent to an associated individual to inform them of a desire, on the part of an originator, to conference or collaborate.
In some embodiments, the electronic device receives a response to the notifications at sub-task 418. The electronic device then adds, to a conference, respondents that have agreed to participate, as per sub-task 420. As used in this specification, the term “conference” means interactive communication between two or more individuals. The communication can be via voice or otherwise (e.g., an IM session, etc.).
As an example of a conference, a user (e.g., a vice president of sales, etc.) associated with a regularly-updated document of divisional performance figures is tracking those figures. The data is presented on the user's personal digital assistant, and the user continually monitors the data. If the user notices that the projections are trending in a downward direction, the user wants to conference immediately with the user's regional sales directors. The user had previously set up the contact list of other individuals (i.e., the regional sales directors) that are associated with the document. The user clicks the contextual conference button after having activated the relevant document. All of the users are then brought into a conference call, in accordance with the illustrative embodiment of the present invention.
As is often desirable, the communication can be a “collaboration.” As used in this specification, the term “collaboration” refers to when a document or application is shared between two or more individuals. A “collaboration” can accompany a “conference,” and is accomplished at sub-task 422.
Document or application sharing is accomplished by a data-sharing application, such as Microsoft's NetMeeting, or via a web collaboration portal. If an associated individual responds affirmatively to a notification for collaboration, they would, in some embodiments, log into a data-sharing application or web collaboration portal wherein the document or application is pushed to them.
As an example of a collaboration, consider the two opened documents seen on computer desktop 200 in
The following example provides further detail as to the mechanics of implementing a collaboration in accordance with the illustrative embodiment of the present invention. For this example, the context for communications is an e-mail.
Assume the John types an e-mail with an attachment that is to be sent to Jim and Jamie. Before sending the e-mail, John decides that he would prefer to have a conference with Jim and Jamie. Using a speech interface, John says, “contextual conference with Jim and Jamie.” Alternatively, a “start collaboration” button could be clicked. A call is then automatically placed to Jim, Jamie and John (i.e., each party's phone will ring without John having dialed any number). All three individuals will get a notification on the personal computer that they are requested to join a collaboration. The notification can be sent, for example, through WebEx, NetMeeting, etc., and is received, for example, on each party's personal computer. To the extent that each party affirmatively responds to the notification, such as by clicking on a “join collaboration” soft key, the e-mail and its attachment are automatically sent to them.
The tasks that are undertaken by John and his personal computer (“PC”), in conjunction with contextual communications software, to accomplish this collaboration are as follows:
It will be clear to those skilled in the art which of the tasks depicted in
It is to be understood that the above-described embodiments are merely illustrative of the present invention and that many variations of the above-described embodiments can be devised by those skilled in the art without departing from the scope of the invention. It is therefore intended that such variations be included within the scope of the following claims and their equivalents. What is claimed is:
This application claims the benefit of U.S. provisional patent application Ser. No. 60/507067, filed 29 Sep. 2003, entitled “Contextual Communications,” which is also incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60507067 | Sep 2003 | US |