Event Notification Management System Priority Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional event notification management systems (ENMS) face latency issues in responding to events, as they direct all incoming notifications to a database regardless of alert necessity, leading to delayed alert generation and potential device compromise.
Innovation Solution
Implement a priority-based system where event notifications are tagged as high or normal priority, with high-priority notifications sent directly to an alert evaluation module and both priorities stored in a database, ensuring quick alert generation while maintaining compliance with reporting requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all incoming event notifications are directed to the database regardless of alert necessity, then reporting requirements are met, but latency in generating alerts increases and device compromise risk increases
Solution Approach 1:
The patent segments incoming event notifications into two categories: alert-worthy events and non-alert events. The event collector evaluates each notification against alert rules and directs only alert-worthy events to the alert evaluation module, while routing all events to the database for reporting compliance. This segmentation eliminates unnecessary alert processing for non-critical events, reducing latency without compromising reporting requirements.
Solution Approach 2:
The patent performs preliminary evaluation of event notifications against alert rules before they reach the alert evaluation module. The event collector pre-filters notifications by checking them against defined alert rules, identifying which events warrant alert generation. This preliminary action prevents the alert evaluation module from processing non-critical events, significantly reducing processing latency while maintaining complete reporting coverage.
2Loss of time
If event notifications are sent directly to the alert evaluation module without database storage, then alert generation latency is reduced, but compliance with reporting requirements is compromised
Solution Approach 1:
The patent extracts the alert evaluation function from the general event processing flow. The event collector identifies alert-worthy events and extracts them for immediate evaluation by the alert evaluation module, bypassing the database storage step that would cause latency. Meanwhile, a separate mechanism ensures all events are still stored in the database for reporting compliance, decoupling the alert generation path from the reporting storage path.
3Productivity
If copies of all event notifications are generated and sent to the alerting system, then alert generation speed improves, but system resource consumption increases
Solution Approach 1:
The patent applies partial action by generating and processing only the necessary subset of event notifications for alerting. The event collector evaluates each notification against alert rules and generates alert evaluation requests only for events that match alert criteria, rather than creating copies of all notifications. This partial processing approach improves alert generation speed for critical events while avoiding the excessive resource consumption of processing all events.
Data Source
AI summary
An improved technique of identifying particular events for alerting within an ENMS involves tagging each incoming event notification as having high priority or normal priority according to a set of rules. Those event notifications tagged as having a normal priority are sent directly to a reporting database, while those tagged as having a high priority are sent directly to an alert evaluation module which is configured to generate an alert as a result of an alert evaluation operation performed on an event notification. In order to comply with reporting requirements, however, the improved technique further involves generating a copy of the event notifications tagged as high priority and sending the copies to the reporting database.