The present invention generally relates to the switching of conversational context in a collaborative environment.
In messaging and/or collaboration applications it is common to conduct “conversations” between individual users and/or groups of users. Such conversations typically comprise communications such as text, voice, images, hyperlinks, and/or media content that are exchanged between the participants of the conversation. Each such communication is typically associated with its contributing participant by user name and/or avatar.
The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:
A method for switching conversational context in a collaborative environment is implemented on a computing device and includes: presenting a group conversation on a display screen associated with the computing device, where the presenting comprises display of at least collaborative communications and associated participant avatars, detecting selection of one of the associated participant avatars in the group conversation, switching from the group conversation to an individual conversation, the individual conversation conducted between individual conversation participants, where the individual conversation participants include a user of the computing device and one of the conversation participants according to the selected participant avatar, and replacing the group conversation on the display screen with a presentation of the individual conversation.
Reference is now made to
For example, as shown, room avatar 20A is associated with room name 21A, i.e., “Team News”. It will be appreciated that a conversation room may be associated with either an individual, i.e., one-to-one, conversation or a group conversation. In an individual conversation, the conversation may be conducted between the user of device 100 and one other participant. For example, room avatars 20C and 20D comprise a thumbnail portrait of a single person, as per profile pictures associated with the individual users participating in the individual conversations. Accordingly, per the example, room name 21C is “Dallas Johnson” to indicate a conversation room for a conversation between the user of device 100 and Dallas Johnson. Room name 21D is “Carrie Johnson”, thereby indicating a conversation room for a conversation between the user of device 100 and Carrie Johnson. It will be appreciated that room names 21 may be assignable by the creator of a room; the examples herein may use the names of the participating individuals for ease of presentation.
As depicted in
In accordance with an exemplary embodiment described herein, device 100 may be configured with a touchscreen interface and the user of device 100 may select to enter the conversation room associated with room avatar 20B (i.e., the “Marketing Group” conversation room) by tapping on room avatar 20B. It will be appreciated by one of ordinary skill in the art that a mouse click or other suitable means may also be used to select room avatar 20B instead, or in addition to, touchscreen functionality.
Reference is now made to
In accordance with embodiments described herein, the user of device 100 may select a participant from among those participating in a group conversation to move to a “private room”, i.e. a one-to-one conversation between the selected participant and the user of device 100. As depicted in
Reference is now made to
Reference is now made to
It will be appreciated by one of skill in the art that user device 100 comprises hardware and software components that may provide at least the functionality of the embodiments of
It will be appreciated that user device 100 may comprise more than one processor 110. For example, one such processor 110 may be a special purpose processor operative to execute client application 140. It will be appreciated that client application 140 may be implemented in software and/or hardware. Client application 140 may be, for example, a collaboration application such as Cisco Spark™, Slack from Slack Technologies. Inc., and/or iOS Messages from Apple, Inc. It will be appreciated by one of ordinary skill in the art that client application 140 may be any suitable application that may provide functionality similar to the collaborative conversation rooms of the embodiments of
Client application 140 comprises room switching module 145. Room switching module 145 may be implemented in software and/or hardware and may be invoked as necessary by client application 140 to detect and process the input of UI gestures for the changing of a conversational context such as the UI gestures depicted in
Reference is now made to
In response, client application 140 may invoke room switching module 145 to change (step 230) the conversational context per the selected participant avatar, e.g., participant avatar 35C as shown in
It will be appreciated by one of skill in the art that the user of device 100 and the selected participant (i.e., “Jaime” per example) may not have a pre-existing individual conversation room. Accordingly, room switching module 145 may check if there is such a pre-existing room (step 240) and if not, it may prompt the user of device 100 to create (step 245) a conversation room per the selection.
Client application 140 may then present (step 250) the individual conversation room on display screen 120 of user device. It will be appreciated by those of skill in the art that in the case of a pre-existing room (per step 240) the presentation of the individual conversation room may include retrieval and presentation of the conversation thread from previous uses of the room, i.e., previously posted contribution by the participants, such as IM chat and shared content. It will also be appreciated that client application 140 may not support multiple concurrent conversational contexts; only one conversation room may be open on device 100 at any given time.
It will also be appreciated that client application 140 may support more than one mode of communication. While the exemplary embodiments of
In accordance with embodiments described herein, room switching module 145 may be configured to autonomously switch the conversational context in accordance with a current mode of communication. User device 100 and client application 140 may be configured to support multiple modes of communication between participants of a conversation room. For example, user device 100 may be a communication device such as a smartphone that may provide voice functionality via I/O module 130. User device 100 may also be implemented as a personal computer or laptop computer that may be similarly configured to provide voice functionality via I/O module 130. Similarly, user device 100 may also be configured with a camera that may provide video functionality.
Accordingly, if a current mode of communication is IM chat, then process 200 may be used to open an individual conversation room for IM chat as described hereinabove. If a current mode of communication is an audio conference call, then process 200 may be used to switch the conversational context to a private, one-to-one voice call. If a current mode of communication is a video conference call, then process 200 may be used to switch the conversational context to a private, one-to-one video call. Regardless of the mode of communication, the steps of process 200 may be used to present the conversation (step 210), detect selection of a participant avatar (step 220), change the conversational context (step 230) per the selected avatar, determine whether or not to open a new conversation room (Steps 240, 245), and present the new conversation room.
In accordance with embodiments described herein, client application 140 may be configured to maintain a current communication mode when invoking room switching module 145, thereby streamlining the process and enabling the user of user device 100 to seamlessly switch to a private, one-to-one context with a minimum of steps.
It is appreciated that software components of the present invention may, if desired, be implemented in ROM (read only memory) form. The software components may, generally, be implemented in hardware, if desired, using conventional techniques. It is further appreciated that the software components may be instantiated, for example: as a computer program product or on a tangible medium. In some cases, it may be possible to instantiate the software components as a signal interpretable by an appropriate computer, although such an instantiation may be excluded in certain embodiments of the present invention.
It is appreciated that various features of the invention which are, for clarity, described in the contexts of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable subcombination.
It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the invention is defined by the appended claims and equivalents thereof: