# US 10,320,858 B2 · Event triggered notifications for collaborative processes

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,320,858 B2
- Document ID: US10320858B2
- Status: Granted
- Kind: B2
- Application number: 15/967,715
- Filed: 2018-05-01
- Published: 2018-08-30
- Granted: 2019-06-11
- Earliest claimed: 2009-07-23
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Cynthia E. Barber-Mingo; Arno Denne; Liam S. Harpur; John Kennedy; Paula Prendergast
- Web page: https://patentgrep.com/patent/US10320858B2

## CPC

- H04L 65/4015: {where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference}
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/10: Office automation; Time management
- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- G06Q 10/109: Time management, e.g. calendars, reminders, meetings or time accounting
- H04L 43/045: for graphical visualisation of monitoring data
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Notifications related to activity associated with a collaborative process are propagated to an originator to alert the originator of activity on the collaborative process. A collaborative process server receives an indication that the originator has initiated a collaborative process that generates collaborative content to be tracked. The collaborative process server is utilized to share the collaborative content associated with the collaborative process with at least one recipient. Computer implemented event(s) associated with the shared collaborative content by recipients are detected. Information associated with the collaborative process is automatically transformed in response to detected event(s) associated with the shared collaborative content, wherein a notification of the occurrence of the event(s) is propagated to the originator. The notification is generated in response to detected event(s) and is based upon the transformed information. Propagating the notification can include evaluating a rule to determine a when or how the notification is propagated.

## Claims

### Claim 1

A method of tracking a collaborative process and propagating a notification of an occurrence of an event to an originator comprising:
receiving at a collaborative process server computer coupled to a network environment, an indication that an originator has initiated, with a first collaborative process application, a computer implemented collaborative process that generates collaborative content associated with the collaborative process;
obtaining by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked;
sharing the generated collaborative content associated with the collaborative process with at least one recipient;
obtaining by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared generated collaborative content other than a communication from any recipient back to the originator;
automatically transforming information associated with the collaborative process in response to at least one detected event associated with the shared generated collaborative content; and
propagating a notification to the originator that informs the originator of the at least one detected event, wherein the notification is generated in response to the at least one detected event and is based upon the transformed information;
wherein:
sharing the generated collaborative content associated with the collaborative process with at least one recipient further comprises:
providing a notice to at least one recipient that events are being tracked to send notifications to the originator, and
providing each recipient that receives the notice with an option to enable sending notifications or disable sending notifications; and
propagating a notification to the originator further comprises:
refraining from propagating the notification when the at least one detected event is associated with a recipient that received the notice and that indicated the option to disable sending notifications, and
evaluating at least one rule to determine at least one of when or how, the notification is propagated to the originator.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving from the originator, by the collaborative process server computer, the at least one rule.

### Claim 3 (depends on 1)

The method of claim 1, wherein the at least one rule specifies a delivery format for the notification.

### Claim 4 (depends on 1)

The method of claim 1, wherein the at least one rule specifies a delivery address for the notification.

### Claim 5 (depends on 1)

The method of claim 1, wherein the at least one rule limits an amount of notifications received over a given period of time.

### Claim 6 (depends on 1)

The method of claim 1, wherein the at least one rule specifies propagating the notification to the originator only within a certain time period after receiving the indication that the originator initiated the computer implemented collaborative process.

### Claim 7 (depends on 1)

The method of claim 1, wherein the at least one rule specifies receiving the notification only during certain hours of a day.

### Claim 8 (depends on 1)

The method of claim 1, wherein the at least one rule specifies varying a delivery address of the notification based on a time of day the notification is generated.

### Claim 9 (depends on 1)

The method of claim 1, wherein the at least one rule specifies varying a delivery format of the notification based on a time of day the notification is generated.

### Claim 10 (depends on 1)

The method of claim 1, wherein the at least one rule is selected by the originator based on the at least one recipient.

### Claim 11

A collaborative process server computer comprising:
a memory device storing executable code; and
a processor in communication with the memory device, wherein the executable code, when executed by the processor, causes the processor to:
receive at the collaborative process server computer, an indication that an originator has initiated, with a first collaborative process application, a computer implemented collaborative process that generates collaborative content associated with the collaborative process;
obtain by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked;
share the generated collaborative content associated with the collaborative process with at least one recipient;
obtain by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared generated collaborative content other than a communication from any recipient back to the originator;
automatically transform information associated with the collaborative process in response to at least one detected event associated with the shared generated collaborative content; and
propagate a notification to the originator that informs the originator of the at least one detected event, wherein the notification is generated in response to the at least one detected event and is based upon the transformed information;
wherein:
sharing the generated collaborative content associated with the collaborative process with at least one recipient further comprises:
providing a notice to at least one recipient that events are being tracked to send notifications to the originator, and
providing each recipient that receives the notice with an option to enable sending notifications or disable sending notifications; and
propagating the notification to the originator further comprises:
refraining from propagating the notification when the at least one detected event is associated with a recipient that received the notice and that indicated the option to disable sending notifications, and
evaluating at least one rule to determine at least one of when or how, the notification is propagated to the originator.

### Claim 12 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule specifies a delivery format for the notification.

### Claim 13 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule specifies a delivery address for the notification.

### Claim 14 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule limits an amount of notifications received over a given period of time.

### Claim 15 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule specifies propagating the notification to the originator only within a certain time period after receiving the indication that the originator initiated the computer implemented collaborative process.

### Claim 16 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule specifies receiving the notification only during certain hours of a day.

### Claim 17 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule specifies varying a delivery address of the notification based on a time of day the notification is generated.

### Claim 18 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule specifies varying a delivery format of the notification based on a time of day the notification is generated.

### Claim 19 (depends on 11)

The collaborative process server computer of claim 11, wherein the at least one rule is selected by the originator based on the at least one recipient.

### Claim 20

A computer program product, comprising:
a computer readable storage medium having program code stored thereon, the program code executable by a data processing system to initiate operations including:
receiving at a collaborative process server computer coupled to a network environment, an indication that an originator has initiated, with a first collaborative process application, a computer implemented collaborative process that generates collaborative content associated with the collaborative process;
obtaining by the collaborative process server computer, a designation that events associated with the initiated collaborative process are to be tracked;
sharing the generated collaborative content associated with the collaborative process with at least one recipient;
obtaining by the collaborative process server computer, information identifying the occurrence of at least one computer detectable event associated with the shared generated collaborative content other than a communication from any recipient back to the originator;
automatically transforming information associated with the collaborative process in response to at least one detected event associated with the shared generated collaborative content; and
propagating a notification to the originator that informs the originator of the at least one detected event, wherein the notification is generated in response to the at least one detected event and is based upon the transformed information;
wherein:
sharing the generated collaborative content associated with the collaborative process with at least one recipient further comprises:
providing a notice to at least one recipient that events are being tracked to send notifications to the originator, and
providing each recipient that receives the notice with an option to enable sending notifications or disable sending notifications; and
propagating a notification to the originator further comprises:
refraining from propagating the notification when the at least one detected event is associated with a recipient that received the notice and that indicated the option to disable sending notifications, and
evaluating at least one rule to determine at least one of when or how, the notification is propagated to the originator.
