Audio sequestering and opt-in sequences for a conference session
US-8937888-B2 · Jan 20, 2015 · US
US9853824B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9853824-B2 |
| Application number | US-201113224865-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 2, 2011 |
| Priority date | Sep 2, 2011 |
| Publication date | Dec 26, 2017 |
| Grant date | Dec 26, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. 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. 2. The method of claim 1 , further comprising: storing the request from the third party to inject the content into the collaboration session between the two or more users in a registry. 3. The method of claim 1 , wherein injecting the content into the collaboration session between the two or more users comprises: 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. 4. The method of claim 1 , further comprising: 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. 5. The method of claim 1 , wherein 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 comprises: detecting a fuzzy match associated with: the request to inject the content into the collaboration session between the two or more users, and the qualifying event. 6. The method of claim 1 , further comprising: notifying the third party that requested to inject the content into the collaboration session between the two or more users of whether an action associated with the request to inject the content into the collaboration session between the two or more users was satisfied. 7. The method of claim 1 , further comprising: notifying the third party that requested to inject the content into the collaboration session between the two or more users that the qualifying event has been detected. 8. The method of claim 1 , wherein the collaboration session is at least one of: a telephone call, an instant message chat, a conference call, a unified telephony call, a web conference, an electronic meeting, an email, and a calendaring and scheduling event. 9. 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. 10. The computer program product of claim 9 , further comprising: storing the request from the third party to inject the content into the collaboration session between the two or more users in a registry. 11. The computer program product of claim 9 , wherein injecting the content into the collaboration session between the two or more users comprises: 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. 12. The computer program product of claim 9 , further comprising: 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. 13. The computer program product of claim 9 , wherein 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 comprises: detecting a fuzzy match associated with: the request to inject the content into the collaboration session between the two or more users, and the qualifying event. 14. The computer program product of claim 9 , further comprising: notifying the third party that requested to inject the content into the collaboration session between the two or more users of whether an action associated with the request to inject the co
Workflow collaboration or project management · CPC title
Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.