US 9,853,824 B2 · Injecting content in collaboration sessions

Abstract

A method, computer program product, and system for injecting content in collaboration sessions is described. A method may comprise receiving, via one or more computing devices, a request from a third party to inject content into a collaboration session between two or more users. The method may further comprise monitoring, via the one or more computing devices, one or more communication platforms to detect a qualifying event associated with the request from the third party to inject the content into the collaboration session between the two or more users. The method may additionally comprise, in response, at least in part, to detecting the qualifying event associated with the request from the third party to inject the content into the collaboration session between the two or more users, injecting, via the one or more computing devices, the content into the collaboration session between the two or more users.

Drawings

Drawings are temporarily unavailable. Open the PDF at USPTO

Drawings

Claims21

Dependent claims

A method comprising:

receiving, via one or more computing devices, a request from a third party, via a
graphical user interface utilized by the third party, to inject content into a collaboration session between two or more users, wherein the request includes a selection of the two or more users, a selection of a topic of the collaboration session between the two or more users, and the content to be injected into the collaboration session made by the third party via the graphical user interface;
monitoring, via the one or more computing devices, one or more communication platforms to detect a qualifying event and a plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, wherein the qualifying event includes initiation of the collaboration session between the two or more users identified in the request;
detecting that the two or more users selected by the third party in the request are in the collaboration session as one of the plurality of condition precedents;
detecting that the topic of the collaboration session between the two or more users selected by the third party in the request is in the collaboration session as another one of the plurality of condition precedents, wherein the request from the third party to inject the content into the collaboration session between the two or more users identifies the topic and the two or more users selected by the third party in the request;
and
in response, at least in part, to detecting the qualifying event and satisfying the plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, injecting, via the one or more computing devices, the content into the collaboration session between the two or more users based, at least in part, upon an access rule defining a subset of the two or more users to receive the injected content;
wherein the injected content includes an associated action corresponding to the topic of the collaboration session.

5 more elements

A computer program product residing on a non-transitory computer readable storage medium having a plurality of instructions stored thereon, which, when executed by a processor, cause the processor to perform operations comprising:

receiving a request from a third party, via a graphical user interface utilized by the third party, to inject content into a collaboration session between two or more users, wherein the request includes a selection of the two or more users, a selection of a topic of the collaboration session between the two or more users, and the content to be injected into the collaboration session made by the third party via the graphical user interface;
monitoring one or more communication platforms to detect a qualifying event and a plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, wherein the qualifying event includes initiation of the collaboration session between the two or more users identified in the request;
detecting that the two or more users selected by the third party in the request are in the collaboration session as one of the plurality of condition precedents;
detecting that the topic of the collaboration session between the two or more users selected by the third party in the request is in the collaboration session as another one of the plurality of condition precedents, wherein the request from the third party to inject the content into the collaboration session between the two or more users identifies the topic and the two or more users selected by the third party in the request;
and
in response, at least in part, to detecting the qualifying event and satisfying the plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, injecting the content into the collaboration session between the two or more users based, at least in part, upon an access rule defining a subset of the two or more users to receive the injected content;
wherein the injected content includes an associated action corresponding to the topic of the collaboration session.

4 more elements

A computing system including one or more processors and one or more memories configured to perform operations comprising:

receiving a request from a third party, via a graphical user interface utilized by the third party, to inject content into a collaboration session between two or more users, wherein the request includes a selection of the two or more users, a selection of a topic of the collaboration session, and the content to be injected into the collaboration session made by the third party via the graphical user interface;
monitoring one or more communication platforms to detect a qualifying event and a plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, wherein the qualifying event includes initiation of the collaboration session between the two or more users identified in the request;
detecting that the two or more users selected by the third party in the request are in the collaboration session as one of the plurality of condition precedents;
detecting that the topic of the collaboration session between the two or more users selected by the third party in the request is in the collaboration session as another one of the plurality of condition precedents, wherein the request from the third party to inject the content into the collaboration session between the two or more users identifies the topic and the two or more users selected by the third party in the request;
and
in response, at least in part, to detecting the qualifying event and satisfying the plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, injecting the content into the collaboration session between the two or more users based, at least in part, upon an access rule defining a subset of the two or more users to receive the injected content;
wherein the injected content includes an associated action corresponding to the topic of the collaboration session.

4 more elements

A method comprising:

receiving, via one or more computing devices, a request through, at least in part, a graphical user interface associated with a collaboration application, to inject content into a collaboration session between two or more users, wherein the request includes a selection of the two or more users, a selection of a topic of the collaboration session, and the content to be injected into the collaboration session made by the third party via the graphical user interface;
monitoring, via the one or more computing devices, one or more communication platforms to detect a qualifying event and a plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between two or more users, wherein the qualifying event is based upon, at least in part, at least one of:
initiation of the collaboration session between the two or more users identified in the request, and the topic of the collaboration session;
detecting that the two or more users selected by the third party in the request are in the collaboration session as one of the plurality of condition precedents;
detecting that the topic of the collaboration session between the two or more users selected by the third party in the request is in the collaboration session as another one of the plurality of condition precedents, wherein the request from the third party to inject the content into the collaboration session between the two or more users identifies the topic and the two or more users selected by the third party in the request;
and
in response, at least in part, to detecting the qualifying event and satisfying the plurality of condition precedents associated with the request from the third party to inject the content into the collaboration session between the two or more users, injecting, via the one or more computing devices, the content into the collaboration session between the two or more users based, at least in part, upon an access rule defining a subset of the two or more users to receive the injected content, and through, at least in part, at least one of an instant messaging application, a unified telephony application, a web conferencing application, and a text message;
wherein the injected content includes an associated action corresponding to the topic of the collaboration session.

5 more elements

Dependencies are inferred from the claim text.

Description7,536 words

Summary1,779 words

#Collaborative sessions, such as instant message chats, unified telephony calls, and web conferences, may be ways for collaborators to share ideas and have discussions. While collaborators present in a collaborative session may take advantage of the resulting collaboration opportunity, those outside (e.g., not invited to, not present for) the collaborative session may be unable to share ideas or influence the flow of discussions in the collaboration session. In some situations, those outside the collaborative session may not have knowledge that a collaborative session is taking place, or may not know who is collaborating in the collaborative session.

#In an embodiment, a method may include receiving, via one or more computing devices, a request from a third party to inject content into a collaboration session between two or more users. The method may further include monitoring, via the one or more computing devices, one or more communication platforms to detect a qualifying event associated with the request from the third party to inject the content into the collaboration session between the two or more users. The method may also include, in response, at least in part, to detecting the qualifying event associated with the request from the third party to inject the content into the collaboration session between the two or more users, injecting, via the one or more computing devices, the content into the collaboration session between the two or more users.

#One or more of the following features may be included. The method may include storing the request from the third party to inject the content into the collaboration session between the two or more users in a registry. Injecting the content into the collaboration session between the two or more users may include displaying the content requested by the third party to be injected into the collaboration session between the two or more users in the collaboration session between the two or more users. The method may additionally include identifying the third party that requested to inject the content into the collaboration session between the two or more users to the two or more users.

Brief description of the drawings6 figures

#FIG. 1 is a diagrammatic view of a content injection process coupled to a distributed computing network;

#FIG. 2 is a flowchart of the content injection process of FIG. 1;

#FIG. 3 is an exemplary graphical user interface which may be associated with the content injection process of FIG. 1;

Detailed description5,643 words

#Referring to FIGS. 1 & 2, there is shown a content injection process 10. As will be discussed below, content injection process 10 may receive 100, a request from a third party to inject content into a collaboration session between two or more users. Content injection process 10 may also monitor 102 one or more communication platforms to detect a qualifying event associated with the request from the third party to inject the content into the collaboration session between the two or more users. Content injection process 10 may additionally, in response to detecting the qualifying event associated with the request from the third party to inject the content into the collaboration session between the two or more users, inject 104 the content into the collaboration session between the two or more users.

#The content injection (CI) process may be a server-side process (e.g., server-side CI process 10), a client-side process (e.g., client-side CI process 12, client-side CI process 14, client-side CI process 16, or client-side CI process 18), or a hybrid server-side/client-side process (e.g., the combination of server-side CI process 10 and one or more of client-side CI processes 12, 14, 16, 18).

#Server-side CI process 10 may reside on and may be executed by server computer 20, which may be connected to network 22 (e.g., the Internet or a local area network). Examples of server computer 20 may include, but are not limited to: a personal computer, a server computer, a series of server computers, a mini computer, and/or a mainframe computer. Server computer 20 may be a web server (or a series of servers) running a network operating system, examples of which may include but are not limited to: Microsoft Windows Server; Novell Netware; or Red Hat Linux, for example.

Facts

Application

13/224,865Filed 2 Sep 2011

Published

US 2013/0060849 A17 Mar 2013

Granted

26 Dec 2017

Term ends

6 Jun 2034

Estimated · how

20 years from earliest known nonprovisional domestic filing plus recorded patent term adjustment, including 1,008 days of adjustment. Maintenance-fee lapses, terminal disclaimers and statutory extensions have not been checked. The continuity chain may be incomplete; this is not an enforceability determination.

Classification4 codes

H04L 12/1822
For computer conferences, e.g. chat rooms: conducting the conference, e.g. admission, detection, selection or grouping of participants,…
G06Q 10/103
Office automation; Time management: workflow collaboration or project management
H04L
Digital communication
G06Q
Information and communication technology [ict] specially adapted for administrative, commercial, financial, managerial

Timeline

2 Sep 2011Application filedUS 13/224,865
1 Nov 2011Assigned to International Business Machines Corporationassignment of assignor's interest
7 Mar 2013PublishedUS 2013/0060849 A1
26 Dec 2017GrantedUS 9,853,824 B2
12 Oct 2026TodayWithin its term
6 Jun 2034Term endsEstimated, includes 1,008 days of adjustment

Injecting content in collaboration sessions

Life of this patent

Injecting content in collaboration sessions

Life of this patent

Life of this patent

Abstract

Drawings

Drawings

Claims21

Description7,536 words

Drawings

Classification4 codes

Life of this patent

Description7,536 words