METHOD AND SYSTEM FOR DETECTING PATTERS IN DATA STREAMS

• US 20140324530A1
• Filed: 04/29/2014
• Published: 10/30/2014
• Est. Priority Date: 04/30/2013
• Status: Abandoned Application

• Current Assignee: Serenova LLC (Lifesize Communications Incorporated)
• Original Assignee: Liveops Incorporated
• Inventors: THOMPSON, Jeffrey M., BOEROP, Robin A. Bate, BERNARD, Trevor X., COMER, Joshua J., BISHOP, Ian E.
• Application Number:
  US14/264,719
• Publication Number:
  US 20140324530A1
• Time in Patent Office: Days
• US Class Current: 705/7.29
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data

Abstract

A new approach is proposed that contemplates systems and methods to detect patterns in at least one data stream. First, the at least one data stream is received and analyzed to detect an event in the least one data stream, wherein the detected event occurs in relation with an entity and includes at least one attribute indicative of at least one of an identity of the entity, an event type, and contact information for the entity. Once the event is detected and/or received from an external source, it is compared with a plurality of predefined patterns to determine if a match between the event and at least one of the predefined patterns is found. If a match is found successfully, a notification indicative of the entity and/or the event and the at least one predefined pattern that has been successfully matched with the event is generated and transmitted with instructions for actions by another application.

Claims

1. A system for detecting patterns in at least one data stream, comprising:

an event capturing engine running on a host, which in operation, is configured to receive and analyze a data stream to detect at least one event in the data stream that occurred in relation with a given entity and/or indicative of the given entity;

a pattern matching engine running on a host, which in operation, is configured to compare a record of the detected event to a set of predefined patterns to determine whether there is a match between the event and at least one of the predefined patterns;

a notification engine running on a host, which in operation, is configured to generate and transmit a notification with instructions on actions upon a successful match of the event with at least one of the predefined patterns.

2. The system of claim 1, wherein:

the event capturing engine is configured to receive the event detected by an external data source instead of and/or in addition to detecting the event by itself.

3. The system of claim 2, wherein:

the event capturing engine is configured to transmit an acknowledgement receipt of the event back to the external data source once the event has been received and processed.

4. The system of claim 1, wherein:

the event capturing engine is configured to validate the record of the detected event against an event record schema to ensure that all required attributes as defined in the event record schema have been provided, wherein the event record schema defines how the event received and/or detected should be organized and stored for further processing and pattern matching.

5. The system of claim 4, wherein:

the event capturing engine is configured to perform in-band schema change by modifying the event record schema to accommodate modification to the record of the event.

6. The system of claim 1, further comprising:

an augment service engine configured to add one or more data attributes missing or unavailable in the event data as argumentation to the record of the event, wherein these additional attributes are required for the event to be matched with one of the predefined patterns.

7. The system of claim 1, wherein:

each of the predefined patterns includes a plurality of attributes and/or conditions to be matched with the event and the instructions on actions to be taken if the conditions are met.

8. The system of claim 1, wherein:

the pattern matching engine is configured to manage lifecycle of the record of the event until the event has been matched to one of the predefined patterns, expired due to a time-out, or ignored as it does not match any of the predefined patterns.

9. The system of claim 1, wherein:

the pattern matching engine is configured to run the record of the event through a plurality of pattern matchers, wherein each of the pattern matchers evaluates the record of the event against one of the predefined patterns.

10. The system of claim 1, wherein:

the notification engine is configured to retrieve the instructions from “

THEN”

portion of the matched pattern, generate and send the notification to one or more third party applications through a plurality of end points to take the actions according to the instructions.

11. The system of claim 1, wherein:

the notification engine is configured to accept information back from the one or more third party applications through the plurality of end points for further processing.

12. The system of claim 1, wherein:

the notification engine is configured to commit to a reporting service database one or more of the record of the event, pattern matching details, the corresponding actions taken as a result of the pattern matching and the notification for reporting purposes.

13. The system of claim 1, further comprising:

a statistics engine configured to collect performance statistics from various components of the system and to calculate statistical information related to the event and the matched pattern, wherein the calculated the statistics is associated with one or more of a plurality of dimensions over a time interval, wherein the dimensions include a system, which is the top most level of a platform configuration having one or more tenants, and the one or more tenants, which share a single instance of the software running on one or more physical or virtual servers and managed by a system owner.

14. A computer-implemented method for detecting patterns in at least one data stream, comprising:

receiving and analyzing a data stream to detect at least one event in the data stream that occurred in relation with a given entity and/or indicative of the given entity;

comparing a record of the detected event to a set of predefined patterns to determine whether there is a match between the event and at least one of the predefined patterns;

generating and transmitting a notification with instructions on actions upon a successful match of the event with at least one of the predefined patterns.

15. The computer-implemented method of claim 14, further comprising:

receiving the event detected by an external data source.

16. The computer-implemented method of claim 15, further comprising:

transmitting an acknowledgement receipt of the event back to the external data source once the event has been received and processed.

17. The computer-implemented method of claim 14, further comprising:

validating the detected event against an event record schema to ensure that all required attributes as defined in the event record schema have been provided, wherein the event record schema defines how the event received and/or detected should be organized and stored for further processing and pattern matching.

18. The computer-implemented method of claim 17, further comprising:

performing in-band schema change by modifying the event record schema to accommodate modification to the record of the event.

19. The computer-implemented method of claim 14, further comprising:

adding one or more data attributes missing or unavailable in the event data as argumentation to the record for the event, wherein these additional attributes are required for the event to be matched with one of the predefined patterns.

20. The computer-implemented method of claim 14, further comprising:

managing lifecycle of the record of the event until the event has been matched to one of the predefined patterns, expired due to a time-out, or ignored as it does not match any of the predefined patterns.

21. The computer-implemented method of claim 14, further comprising:

running the record of the event through a plurality of pattern matchers, wherein each of the pattern matchers evaluates the record of the event against one of the predefined patterns.

22. The computer-implemented method of claim 14, further comprising:

retrieving the instructions from “

THEN”

portion of the matched pattern, generate and send the notification to one or more third party applications through a plurality of end points to take the actions according to the instructions.

23. The computer-implemented method of claim 22, further comprising:

accepting information back from the one or more third party applications through the plurality of end points for further processing.

24. The computer-implemented method of claim 14, further comprising:

committing to a reporting service database one or more of the record of the event, pattern matching details, the corresponding actions taken as a result of the pattern matching and the notification for reporting purposes.

25. The computer-implemented method of claim 14, further comprising:

collecting performance statistics from various components and calculating statistical information related to the event and the matched pattern, wherein the calculated the statistics is associated with one or more of a plurality of dimensions over a time interval, wherein the dimensions include a system, which is the top most level of a platform configuration having one or more tenants, and the one or more tenants, which share a single instance of the software running on one or more physical or virtual servers and managed by a system owner.

26. A non-transitory computer readable medium having software instructions stored thereon that when executed cause a system to:

receive and analyze a data stream to detect at least one event in the data stream that occurred in relation with a given entity and/or indicative of the given entity;

compare a record of the detected event to a set of predefined patterns to determine whether there is a match between the event and at least one of the predefined patterns;

generate and transmit a notification with instructions on actions upon a successful match of the event with at least one of the predefined patterns.