Alert event platform
First Claim
1. A system for processing alert event information, the system comprising:
- a processor configured for receiving event data, including alert event data, from one or more source systems and storing the data in a non-transitory data storage media;
wherein the processor is further configured for directing the function of at least the following modules;
a batch processing module programmed for processing batch transactions including alert events and also programmed-for processing real-time transactions including alert events;
an alert capture module programmed for accepting alert events and performing validation of the alert events, wherein the alert capture module is programmed to map each alert event into an alert common format for use by multiple modules and components of the system;
a decision making module including;
(i) an alert subscription filter programmed to match the alert events with one or more corresponding subscription preferences stored in an alert preferences database operatively associated with the decision making module, and,(ii) a rules processing component programmed to receive the alert events, to combine the alert events with the subscription preferences, wherein the subscription preferences are added to the alert events, to invoke one or more business rules in association with the alert events and the subscription preferences with a business rules engine operatively associated with the decision making module, and to assign a unique alert identifier to each new alert event; and
,an alert subscription module programmed for routing alert notifications to one or more subscriber systems based on one or more subscription decisions made by the rules processing component of the decision making module; and
wherein the batch processing module is programmed to read from a flat file and separate data records into individual alert event records such that data associated with each alert event record is identified; and
wherein the data associated with each alert event record comprises at least one of a sender by file name, a directory of a file drop, and a file format or record format; and
wherein the electronic computer processor determines whether the unique alert identifier corresponds to an aggregation key identifier;
upon determining that the unique alert identifier corresponds to an aggregation key identifier;
the electronic computer processor filters alert event data by the aggregation key identifier and by a delivery date for grouping related alert events into an ordered list;
the electronic computer processor designates at least one alert event for deferred processing;
the electronic computer processor calculates a time of delivery for the at least one designated alert event for deferred processing; and
the electronic computer processor communicates the alert events designated for deferred processing to a deferral and aggregation queue;
upon determining that the unique alert identifier does not correspond to an aggregation key identifier;
the electronic computer processor designates at least one alert event for immediate processing;
the electronic computer processor communicates the alert events designated for immediate processing to a real time queue; and
the electronic computer processor communicates at least one of the alert events designated for deferred processing in the deferral and aggregation queue to the real time queue after the calculated time of delivery; and
wherein the electronic computer processor routes the alert notifications to the one or more subscriber systems according to the alert events in the real time queue based on the one or more subscription decisions made by the rules processing component of the decision making module.
1 Assignment
0 Petitions
Accused Products
Abstract
Various systems, processes, tools and techniques are provided for managing and processing alerts associated with different business events that impact a corporate entity. In various aspects, the system may employ an event-driven architecture to process business events and then provide customers and other system users with a mechanism for having have visibility into those business events through a subscription process, for example. Subscribers may be offered the ability to tap into different streams of business events, filter the event streams to obtain information only for events of interest, and then receive alerts associated with the events via one or more communication media or channels.
-
Citations
20 Claims
-
1. A system for processing alert event information, the system comprising:
-
a processor configured for receiving event data, including alert event data, from one or more source systems and storing the data in a non-transitory data storage media; wherein the processor is further configured for directing the function of at least the following modules; a batch processing module programmed for processing batch transactions including alert events and also programmed-for processing real-time transactions including alert events; an alert capture module programmed for accepting alert events and performing validation of the alert events, wherein the alert capture module is programmed to map each alert event into an alert common format for use by multiple modules and components of the system; a decision making module including; (i) an alert subscription filter programmed to match the alert events with one or more corresponding subscription preferences stored in an alert preferences database operatively associated with the decision making module, and, (ii) a rules processing component programmed to receive the alert events, to combine the alert events with the subscription preferences, wherein the subscription preferences are added to the alert events, to invoke one or more business rules in association with the alert events and the subscription preferences with a business rules engine operatively associated with the decision making module, and to assign a unique alert identifier to each new alert event; and
,an alert subscription module programmed for routing alert notifications to one or more subscriber systems based on one or more subscription decisions made by the rules processing component of the decision making module; and wherein the batch processing module is programmed to read from a flat file and separate data records into individual alert event records such that data associated with each alert event record is identified; and wherein the data associated with each alert event record comprises at least one of a sender by file name, a directory of a file drop, and a file format or record format; and wherein the electronic computer processor determines whether the unique alert identifier corresponds to an aggregation key identifier; upon determining that the unique alert identifier corresponds to an aggregation key identifier; the electronic computer processor filters alert event data by the aggregation key identifier and by a delivery date for grouping related alert events into an ordered list; the electronic computer processor designates at least one alert event for deferred processing; the electronic computer processor calculates a time of delivery for the at least one designated alert event for deferred processing; and the electronic computer processor communicates the alert events designated for deferred processing to a deferral and aggregation queue; upon determining that the unique alert identifier does not correspond to an aggregation key identifier; the electronic computer processor designates at least one alert event for immediate processing; the electronic computer processor communicates the alert events designated for immediate processing to a real time queue; and the electronic computer processor communicates at least one of the alert events designated for deferred processing in the deferral and aggregation queue to the real time queue after the calculated time of delivery; and wherein the electronic computer processor routes the alert notifications to the one or more subscriber systems according to the alert events in the real time queue based on the one or more subscription decisions made by the rules processing component of the decision making module. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification