# US 2014/0208172 A1 · Monitoring of Computer Events

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

- Number: US 2014/0208172 A1
- Document ID: US20140208172A1
- Status: Published application
- Kind: A1
- Application number: 14/220,267
- Filed: 2014-03-20
- Published: 2014-07-24
- Earliest claimed: 2007-03-15
- Assignees: Verint Americas Inc.
- Applicants: Verint Americas Inc.
- Inventors: Christopher Schnurr; Frank Maurer
- Web page: https://patentgrep.com/patent/US20140208172A1

## CPC

- G06F 9/4806: {Task transfer initiation or dispatching}
- G06F 11/3438: {monitoring of user actions (tracking the activity of the user H04L67/535)}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- G06F 11/349: {for interfaces, buses}
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 2201/86: Event-based monitoring
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A data processing system (1) is programmed with an interface (2) for capturing events which arise, and a process engine (3) for automatically monitoring captured events to identify completion of steps, each comprising a plurality of events linked by dependency relationships; and to identify completion of processes, each comprising a plurality of steps linked by dependency relationships. Software functions (5) execute in response to output of the process engine (3). The process engine (3) processes events to recognise a plurality of potential steps, but terminates other potential steps when completion of a step is determined. The process engine (3) processes steps to recognise a plurality of potential processes, but terminates other potential process when completion of a process is determined. The dependency relationships include Boolean AND operators and Boolean OR operators. There is a discrete start event for each step and a discrete start step for each process. The engine executes a plurality of processes simultaneously, applying captured events in real time to relevant steps, some events being applied to a plurality of steps.

## Claims

### Claim at position 1

1-25. (canceled)

### Claim 26

A data processing system comprising a processor, a memory, and a storage device, wherein the processor comprises;
an interface for capturing user interaction events which arise in the system,
a process engine for automatically monitoring the user interaction events to:
identify completion of steps, each of the steps comprising a plurality of events of the user interaction events, wherein the plurality of events are linked by a first set of dependency relationships; and
identify completion of processes, each of the processes comprising a plurality of the steps, wherein the plurality of steps are linked by a second set of dependency relationships,
generate process data from the completed processes for transference to a trigger engine;
the trigger engine for receiving and processing the process data to:
determine whether at least one of the completed processes meet one of a plurality of trigger criteria;
in response to the at least one of the completed processes meeting a trigger criteria, call a software function;
a database manager for saving the process data generated by the process engine;
a reporting engine for generating reports according to the saved process data, wherein the interface comprises means for capturing an even by querying an operating system for display controls, receiving a list of controls from the operating system, applying a pattern signature to a returned list to identify a target control, making a query to the opening system concerning the target control, and receiving a response with data for the target control.

### Claim 27 (depends on 26)

The data processing system as claimed in claim 26, wherein the process engine processes the user interaction events to simultaneously recognise a plurality of potential steps, wherein each potential step is a step that may result from additional user interaction events that have not yet been identified, and once a completed step has been identified from the plurality of potential steps, abandons the remaining potential steps of the plurality of potential steps.

### Claim 28 (depends on 26)

The data processing engine as claimed in claim 26, wherein the process engine processes the steps to simultaneously recognise a plurality of potential processes, wherein each potential process is a process that may result from additional steps that have not yet been identified, and once a completed step has been identified from the plurality of potential steps, abandons the remaining potential processes.

### Claim 29 (depends on 26)

The data processing system as claimed in claim 26, wherein the process engine processes the user interaction events to simultaneously recognise a plurality of potential steps, and abandons other potential steps when completion of a step is determined; and wherein the first and second set of dependency relationships include Boolean AND operators.

### Claim 30 (depends on 26)

The data processing system as claimed in any of claim 26, wherein the process engine processes the user interaction events to simultaneously recognise a plurality of potential steps, and abandons other potential steps when completion of a step is determined; and wherein the first and second set of dependency relationships include Boolean OR operators.

### Claim 31 (depends on 26)

The data processing system as claimed in claim 26, wherein the process engine processes the user interaction events to simultaneously recognize a plurality of potential steps, and abandons other potential steps when completion of a step is determined; and wherein the first and second set of dependency relationships include Boolean NOT operators.

### Claim 32 (depends on 26)

The data processing system as claimed in claim 26, wherein there is a discrete start event for each step and a discrete start step for each process.

### Claim 33 (depends on 32)

The data processing system as claimed in claim 32, wherein the process engine treats a step as current if its start event is received.

### Claim 34 (depends on 26)

The data processing system as claimed in claim 26, wherein each step has an end event.

### Claim 35 (depends on 26)

The data processing system as claimed in claim 26, wherein the process engine stores event lists defining the steps and said event lists are stored as mark-up language documents.

### Claim 36 (depends on 26)

The data processing system as claimed in claim 26, wherein the process engine stores step lists defining, the processes and said step lists are stored as mark-up language documents.

### Claim 37 (depends on 35)

The data processing system as claimed in claim 35, wherein the mark-up language is XML.

### Claim 38 (depends on 26)

The data processing system as claimed in claim 26, wherein the criteria comprises criteria for process interdependencies and rules specifying parameter ranges or thresholds.

### Claim 39 (depends on 26)

The data processing system as claimed in claim 26, wherein the trigger engine comprises feedback means for generating events and feeding the events to the process engine.

### Claim 40 (depends on 26)

The data processing system as claimed in claim 26, wherein the process engine comprises means for associating real time stamps with events and with completed processes, and the database manager saves said real time stamps.

### Claim 41 (depends on 26)

The data processing system as claimed in claim 26, wherein the reporting engine correlates event and process times with a real time axis for display.

### Claim 42 (depends on 26)

The data processing system as claimed, in claim 26, wherein the reporting engine correlates event and process times with as real time axis for display; and wherein the reporting engine comprises means for generating an output of event data indicating when events, steps, and processes occurred, for generating a graphical user interface allowing a user to configure said events into new steps and to configure said steps into new processes.

### Claim 43 (depends on 26)

The data processing system as claimed in claim 26, wherein the interface comprises means for capturing a user interaction event by querying an operating system for display controls, receiving a list of controls from the operating system, applying is pattern signature to a returned list to identify a target control, making a query to the operating system concerning the target control, and receiving a response with data, for the target control; and wherein a query is a request for an operating system document object model for a web page interface screen.

### Claim 44 (depends on 43)

The data processing system as claimed in claim 43, wherein the pattern signature is applied to all objects in the operating system document object model.

### Claim 45 (depends on 26)

The data processing system as claimed in claim 26, wherein the interface comprises means for capturing it user interaction event by querying an operating system for display controls, receiving a list of controls from the operating system, applying a pattern signature to the returned list to identify a target control, making a query to the operating system concerning the target control, and receiving a response with data for the target control; and a query is a request for a visually-impaired accessibility stream output via an API.

### Claim 46 (depends on 26)

The data processing system as claimed in claim 26, wherein the interface recognizes passback events which are not included in steps, but are processed in parallel to provide data grams to the trigger engine or the database manager.

### Claim 47 (depends on 46)

The data processing system as claimed in claim 46, wherein the process engine links trails of passback events to provide a log concerning an activity.

### Claim 48 (depends on 45)

The data processing system as claimed in claim 45, wherein the process engine applies passback event datagrams with notifications of processes being completed.

### Claim 49

A data processing system comprising a processor, a memory, and a storage device, wherein the processor comprises:
an interface for capturing user interaction events which arise in the system,
a process engine for automatically monitoring the user interaction events to:
identify completion of steps, each comprising as plurality of events of the user interaction events linked by dependency relationships; and
identify completion of processes, each comprising a plurality of the steps linked by dependency relationships,
generate process data from the completed processes for transference to a trigger engine;
the trigger engine for receiving and processing the process data to:
determine whether at least One of the completed processes meet one of a plurality of trigger criteria;
in response to the at least one of the completed processes meeting a trigger criteria, call a software function:
a database manager for saving the process data generated by the process engine;
a reporting engine for generating reports according to the saved process data, wherein the interface comprises means for capturing a user interaction event by querying an operating system for display controls, receiving as list of controls from the operating system, applying a pattern signature to a returned list to identify a target control, making a query to the operating system concerning the target control, and receiving a response with data for the target control; and wherein a query is a request for an operating system document object model for a web page interface screen.

### Claim 50 (depends on 49)

The data processing system as claimed in claim 49, wherein the pattern signature is applied to all objects in the operating system document object model.

### Claim 51

A data processing system comprising a processor, a memory, and a storage device, wherein the processor comprises:
an interface for capturing user interaction events which arise in the system,
a process engine for automatically monitoring the user interaction events to:
identify completion of steps, each of the steps comprising a plurality of events of the user interaction events, wherein the plurality of events are linked by a first set of dependency relationships; and
identify completion of processes, each of the processes comprising a plurality of the steps, wherein the plurality of steps are linked by a second set of dependency relationships,
generate process data from the completed processes for transference to a trigger engine;
the trigger engine for receiving and processing the process data to:
determine whether at least one of the completed processes meet one of a plurality of trigger criteria;
in response to the at least one of the completed processes meeting a trigger criteria, call a software function;
a database manager for saving the process data generated by the process engine;
a reporting engine for generating reports according to the saved process data, wherein the interface comprises means for capturing a user interaction event by querying an operating system for display controls, receiving a list of controls from the operating system, applying, a pattern signature to the returned list to identify a target control, making a query to the operating system concerning the target control, and receiving a response with data for the target control; and a query is a request for a visually-impaired accessibility stream output via an API.
