US6446136B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for dynamic correlation of events
Assignee: CA Inc
•
Filing: 1998-12-31
•
Granted: 2002-09-03
•
Expires: 2018-12-31
Abstract
Abstract An event management system including an event manager, an alarm rule store, an event correlator, and a response engine. The event manager provides and receives events. The event correlator correlates at least one of the events provided by the event manager based on the alarm rules stored in the alarm rule store. The response engine executes a response policy based on the correlation of events by the event correlator.
Inventors
- 👤 William N. Pohlmann
- 👤 Kenneth D. Matson
- 👤 Paul Cantrell
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-29 18:32
CPC Classifications
G; G06; G06F; G06F15/00; G06F11/00; G06F11/30; G06F11/3065; G06F11/3072; G06F11/3003; G06F11/3006; G06F11/32; G06F11/324; G06F11/327; H; H04; H04L; H04L41/00; H04L41/06; H04L41/0631; G06F2201/00; G06F2201/86; Y; Y10; Y10S; Y10S707/00; Y10S707/99941; Y10S707/99944; Y10S707/99945; Y10S707/99948
Claims Analysis
Total Claims: 14
Claim 1
Independent Claim
170 words
An event management system comprising: an event manager, the event manager receiving one or more subscription requests for one or more event data from one or more subscribers, the event manager receiving one or more events and if the one or more events matches an existing condition, applying the one or more events as an update to the existing condition, the event manager further routing the one or more event data to the one or more subscribers; an alarm rule store, the alarm rule store storing alarm rules; an event correlator coupled to the event manager and to the alarm rule store, the event correlator correlating the one or more event data provided by the event manager based on the alarm rules, the event correlator further dynamically determining whether a rule was changed, added or deleted to dynamically execute the added or modified rule; and a response engine coupled to the event manager, the response engine executing a response policy based on the correlation of events by the event correlator.
Claim 2
Dependent Claim
170 words
An event management system comprising: an event manager, the event manager receiving one or more subscription requests for one or more event data from one or more subscribers, the event manager receiving one or more events and if the one or more events matches an existing condition, applying the one or more events as an update to the existing condition, the event manager further routing the one or more event data to the one or more subscribers; an alarm rule store, the alarm rule store storing alarm rules; an event correlator coupled to the event manager and to the alarm rule store, the event correlator correlating the one or more event data provided by the event manager based on the alarm rules, the event correlator further dynamically determining whether a rule was changed, added or deleted to dynamically execute the added or modified rule; and a response engine coupled to the event manager, the response engine executing a response policy based on the correlation of events by the event correlator.
Claim 3
Dependent Claim
35 words
The event management system according to claim 1 , wherein the event manager includes a plurality of event managers, wherein each of the plurality of event managers is on a respective node of a network.
Claim 4
Dependent Claim
32 words
The event management system according to claim 2 , wherein the event correlator correlates at least two events respectively provided by each of at least two of the plurality of event managers.
Claim 5
Dependent Claim
60 words
The event management system according to claim 1 , further comprising an event archive coupled to the event manager, the event archive including an event archive file and an event archive service processor, wherein the event manager stores event data in the event archive file and the event archive service processor processes the event data in the event archive file.
Claim 6
Independent Claim
130 words
A method for dynamically executing at least one of a modified rule and a new rule, the method comprising the following steps: publishing a rule event in response to receiving at least one of the modified rule and the new rule; requesting a first rule set from a storage device in response to receiving the published rule event; changing any of the respective rules from a second rule set that have been changed in the first rule set, adding a rule to the second rule set that has been added to the first rule set, and removing a rule to the second rule set that has been removed from the first rule set; and executing the rules of the second rule set that have been one of changed and added.
Claim 7
Independent Claim
130 words
A method for dynamically executing at least one of a modified rule and a new rule, the method comprising the following steps: publishing a rule event in response to receiving at least one of the modified rule and the new rule; requesting a first rule set from a storage device in response to receiving the published rule event; changing any of the respective rules from a second rule set that have been changed in the first rule set, adding a rule to the second rule set that has been added to the first rule set, and removing a rule to the second rule set that has been removed from the first rule set; and executing the rules of the second rule set that have been one of changed and added.
Claim 8
Independent Claim
82 words
A method of dynamically correlating events comprising: receiving one or more subscriptions to one or more events; receiving event data; determining a subscriber of the event data from the one or more subscriptions; routing the event data to the subscriber; dynamically determining whether a rule was changed, added or deleted; and if a rule was changed or added executing the added or changed rule, wherein the subscriber receiving the event data runs one or more predetermined rules associated with the event data.
Claim 9
Independent Claim
82 words
A method of dynamically correlating events comprising: receiving one or more subscriptions to one or more events; receiving event data; determining a subscriber of the event data from the one or more subscriptions; routing the event data to the subscriber; dynamically determining whether a rule was changed, added or deleted; and if a rule was changed or added executing the added or changed rule, wherein the subscriber receiving the event data runs one or more predetermined rules associated with the event data.
Claim 10
Dependent Claim
32 words
The method of dynamically correlating events as claimed in claim 6 , wherein the receiving one or more subscriptions includes receiving the one more subscriptions from a plurality of distributed computer nodes.
Claim 11
Dependent Claim
56 words
The method of dynamically correlating events as claimed in claim 6 , wherein the receiving one or more subscriptions includes receiving one or more subscriptions to one or more events, the events including one or more new events added dynamically by creating one or more key value pairs to define the one or more new events.
Claim 12
Dependent Claim
26 words
The method of dynamically correlating events as claimed in claim 6 , further including: maintaining a list of the one or more subscriptions and corresponding subscribers.
Claim 13
Dependent Claim
33 words
The method of dynamically correlating events as claimed in claim 9 , further including: removing a selected subscription from the list of the one or more subscriptions when the selected subscription is canceled.
Claim 14
Dependent Claim
35 words
The method of dynamically correlating events as claimed in claim 6 , wherein the one or more subscriptions include one or more subscriptions to an occurrence of an event matching one or more predetermined criteria.
References Cited (Backward Citations)
US5165018A
Cited
US5063523A
Cited
US5459717A
Cited
US5528516A
Cited
US5661668A
Cited
US5809238A
Cited
US5881315A
Cited
US5870605A
Cited
US5974417A
Cited
US6021443A
Cited
US5872931A
Cited
US6108700A
Cited
US6272537B1
Cited
US6216132B1
Cited
US6148338A
Cited
US6289384B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2005-09-02 | 2006-03-04 | 2006-09-03 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2009-09-02 | 2010-03-04 | 2010-09-03 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2013-09-02 | 2014-03-04 | 2014-09-03 | $7700.00 | Window Closed / Lapsed |