CONSOLIDATING INFORMATION FROM DIFFERENT SIGNALS INTO AN EVENT

• US 20190310997A1
• Filed: 02/25/2019
• Published: 10/10/2019
• Est. Priority Date: 04/06/2018
• Status: Active Grant

• Current Assignee: Banjo, Inc.
• Original Assignee: Banjo, Inc.
• Inventors: Gratton, Christian, Patton, Damien, Mehta, Rish, Leung, KW Justin
• Granted Patent: US 10,452,689 B1
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

The present invention extends to methods, systems, and computer program products for consolidating information from different signals into an event. Aspects of the invention used a multiphase approach to consolidating information from different signals into (e.g., deduplicating) an event. Detected events are held in the event holding cache for some amount of time after detection in accordance event holding criteria. As events are detected, an information consolidator compares currently detected events to previously cached events. Events determined to be the same event are grouped into an event group. When holding criteria expire for an event in the event group, the event group is published to one or more entities. As such, each new detection of the event does not trigger a corresponding new notification. Different portions of content from the same signal can also be monitored to reduce duplicate detections based on different content types in the same signal.

Claims

1. A computer-implemented method comprising:

detecting an event from content of a normalized signal, including;

assigning a unique identifier to the normalized signal;

submitting a first signal content type along with the unique identifier to a first pipeline of models configured to process content of the first signal content type;

submitting a second signal content type along with the unique identifier to a second pipeline of models configured to process content of the second content type;

receiving first output associated with the unique identifier from the first pipeline;

receiving second output associated with the unique identifier from the second pipeline;

determining that the first output and the second output are both associated with the signal based on association with the unique identifier;

aggregating the first output and second output into aggregate output; and

detecting the event from the aggregate output;

comparing the event to previously cached events in an event holding cache;

determining that the event is not a redetection of a cached event;

caching the event in the event holding cache until a specified holding period expires;

detecting another event from content of another normalized signal;

comparing the other event to the event cached in the event holding cache;

determining that the other event is redetection of the event;

grouping the event and the other event into an event group;

publishing the event group, including the event and the other event, to a recipient when the specified holding period expires; and

removing the event and the other event from the event holding cache concurrently with publishing the event group.

2. The method of claim 1, further comprising caching the event group in a sent group cached until a second specified holding period expires.

3. The method of claim 2, wherein caching the event group in a sent group cache comprises caching the event group in the event group cache concurrently with publishing the event group to the recipient.

4. The method of claim 2, further comprising accessing the holding period and the second holding period from administrator settings.

5. The method of claim 2, further comprising accessing the holding period and the second holding period from recipient preferences.

6. The method of claim 2, further comprising:

detecting a further event from content of a further normalized signal;

comparing the further event to one or more event groups cached in the sent groups cache, including comparing the further event to the event group;

determining that the further event belongs to the event group; and

publishing the further event to the recipient supplementing publication of the event group.

7. The method of claim 1, further comprising configuring the holding period based on computation processing times.

8. (canceled)

9. A computer system comprising:

a processor;

system memory coupled to the processor and storing instructions configured to cause the processor to;

detect an event from content of a normalized signal, including;

assign a unique identifier to the normalized signal;

submit a first signal content type along with the unique identifier to a first pipeline of models configured to process content of the first signal content type;

submit a second signal content type along with the unique identifier to a second pipeline of models configured to process content of the second content type;

receive first output associated with the unique identifier from the first pipeline;

receive second output associated with the unique identifier from the second pipeline;

determine that the first output and the second output are both associated with the signal based on association with the unique identifier;

aggregate the first output and second output into aggregate output; and

detect the event from the aggregate output;

compare the event to previously cached events in an event holding cache;

determine that the event is not a redetection of a cached event;

cache the event in the event holding cache until a specified holding period expires;

detect another event from content of another normalized signal;

compare the other event to the event cached in the event holding cache;

determine that the other event is redetection of the event;

group the event and the other event into an event group;

publish the event group, including the event and the other event, to a recipient when the specified holding period expires; and

remove the event and the other event from the event holding cache concurrently with publishing the event group.

10. The computer system of claim 9, further comprising instructions configured to cause the processor to cache the event group in a sent group cached until a second specified holding period expires.

11. The computer system of claim 10, wherein instructions configured to cache the event group in a sent group cache comprise instructions configured to cache the event group in the event group cache concurrently with publishing the event group to the recipient.

12. The computer system of claim 10, further comprising instructions configured to access the holding period and the second holding period from administrator settings.

13. The computer system of claim 10, further comprising instructions configured to access the holding period and the second holding period from recipient preferences.

14. The computer system of claim 10, further comprising instructions configured to:

detect a further event from content of a further normalized signal;

compare the further event to one or more event groups cached in the sent groups cache, including comparing the further event to the event group;

determine that the further event belongs to the event group; and

publish the further event to the recipient supplementing publication of the event group.

15. The computer system of claim 9, further comprising instructions configured to configure the holding period based on computation processing times.

16. (canceled)