Implicit process detection and automation from unstructured activity

US9836599B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9836599-B2
Application numberUS-201514657646-A
CountryUS
Kind codeB2
Filing dateMar 13, 2015
Priority dateMar 13, 2015
Publication dateDec 5, 2017
Grant dateDec 5, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An unstructured event is detected and an unstructured event record is generated for the detected event. Case identifier (ID) conflation is performed to estimate a case ID that corresponds to the detected event, and event type identification is performed to estimate a type of the unstructured event. A business process model is applied to the unstructured event record, to identify a process that the unstructured event is related to. A user experience is generated based upon the event type, the case ID, and the corresponding process identified for the detected event.

First claim

Opening claim text (preview).

What is claimed is: 1. A computing system, comprising: a processor; and memory storing instructions executable by the processor, wherein the instructions, when executed, configure the computing system to: receive an unstructured event record with event information indicative of an unstructured event, the unstructured event comprising an event other than a structured event that has a predefined event type and is configured to occur according to a predefined workflow associated with the computing system; access an event type identifier model; identify an event type corresponding to the unstructured event based on the event information and the event type identifier model; generate an event type label, indicative of the event type, corresponding to the unstructured event record; access a process model and a set of logged computing system processes to identify a process; based on the unstructured event record, determine that the unstructured event corresponds to the identified process; identify a workflow based on the identified process and the identified event type corresponding to the unstructured event record; identify an anomaly in an activity pattern based on the identified process; modify the workflow based on the identified anomaly; generate a representation of a user interface display that includes the modified workflow and a user input mechanism; and based on an indication of user actuation of the user input mechanism, perform an action with respect to the modified workflow. 2. The computing system of claim 1 wherein the instructions configure the computing system to detect an unstructured activity pattern associated with a particular user. 3. The computing system of claim 2 , wherein the instructions configure the computing system to detect whether the unstructured event is part of the activity pattern associated with the particular user and identity that the activity pattern relates to the identified process. 4. The computing system of claim 3 , wherein the instructions configure the computing system to: compare the unstructured activity record against the activity pattern for the particular user and identify the anomaly in the activity pattern for the user, based on the comparison. 5. The computing system of claim 1 , wherein the instructions configure the computing system to: generate a recommended action based on the anomaly. 6. The computing system of claim 5 wherein the instructions configure the computing system to: generate a representation of an action user input mechanism; and based on an indication of user actuation of the action user input mechanism, perform the recommended action. 7. The computing system of claim 1 wherein the instructions configure the computing system to: identify a computing system object corresponding to the unstructured event record and open the computing system object in an application context based on the unstructured event record. 8. The computing system of claim 1 , wherein the instructions configure the computing system to: access a case identifier (ID) conflation model to associate the unstructured event record with a case in the computing system. 9. The computing system of claim 1 wherein the instructions configure the computing system to: detect the unstructured event; extract the event information; and generate the unstructured event record. 10. The computing system of claim 1 wherein the instructions configure the computing system to: classify the unstructured event record into an event type. 11. A computing system comprising: a processor; and memory storing instructions executable by the processor, wherein the instructions, when executed, configure the computing system to: receive a labeled unstructured event record that includes event information indicative of an unstructured user interface event in the computing system, the unstructured event record being labeled with an event type, the unstructured user interface event comprising an event other than a structured event that has a predefined event type and is configured to occur according to a predefined workflow associated with the computing system; access a process model and a set of logged computing system processes to identify a process; based on the unstructured event record, determine that the unstructured event record corresponds to the identified process; identify a workflow based on the process and the event type corresponding to the unstructured event record; identify an anomaly in an activity pattern based on the identified process; modify the workflow based on the identified anomaly; and generate a representation of a user interface display that represents the modified workflow. 12. The computing system of claim 11 , wherein the instructions configure the computing system to: receive the unstructured event record and access an event identification model to identify an event type corresponding to the unstructured event record. 13. The computing system of claim 12 wherein the event identification model comprises a classifier. 14. The computing system of claim 12 and further comprising: receive the unstructured event record; access a case identifier (ID) conflation model; and based on the accessed case ID conflation model, identify a case ID within the computing system to which the unstructured event record corresponds. 15. The computing system of claim 14 wherein the instructions configure the computing system to: determine that the activity pattern comprises an unstructured activity pattern; and determine whether the unstructured event record is part of the unstructured activity pattern. 16. The computing system of claim 15 wherein the instructions configure the computing system to: determine whether the unstructured event record represents an anomaly in the unstructured activity pattern. 17. The computing system of claim 16 wherein the instructions configure the computing system to: generate the representation of the user interface display to include a recommendation, the recommendation being based on a determination that the unstructured event record represents an anomaly. 18. A computer implemented method, comprising: detecting an unstructured event in a computing system, the unstructured event comprising an event other than a structured event that has a predefined event type and is configured to occur according to a predefined workflow associated with the computing system; extracting information indicative of the unstructured event to generate an unstructured event record; classifying the unstructured event record to identify a corresponding event type; accessing a process model and a set of logged computing system processes to identify a process; based on the unstructured event record, determining that the unstructured event corresponds to the identified process; identifying a workflow in the computing system based on the identified process and the identified event type corresponding to the unstructured event record; identifying an anomaly in an activity pattern based on the identified process; modifying the workflow based on the identified anomaly; and generating a representation of a user interface display that includes the modified workflow. 19. The computer implemented method of claim 18 , wherein the activity pattern comprises a series of executed events corresponding to a given user, and further comprising: determining whether the unstructured activity record represents the anomaly in the activity pattern; based on th

Assignees

Inventors

Classifications

  • G06F21/554Primary

    involving event detection and direct action · CPC title

  • Risk analysis of enterprise or organisation activities · CPC title

  • Workflow analysis · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9836599B2 cover?
An unstructured event is detected and an unstructured event record is generated for the detected event. Case identifier (ID) conflation is performed to estimate a case ID that corresponds to the detected event, and event type identification is performed to estimate a type of the unstructured event. A business process model is applied to the unstructured event record, to identify a process that …
Who is the assignee on this patent?
Microsoft Technology Licensing Llc
What technology area does this patent fall under?
Primary CPC classification G06F21/554. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Dec 05 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).