US5892898A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Error management system for supporting the identification and logging of error messages
Assignee: Honeywell Inc
•
Filing: 1996-10-04
•
Granted: 1999-04-06
•
Expires: 2016-10-04
Abstract
Abstract There is provided an event management system and a storage media for identifying and logging event information for a plurality of loosely coupled subsystems. The event management system and the storage media include an application for reporting an event message in response to an occurrence of a particular event, and an event logging routine, responsive to receiving the error message, for identifying a source of the error message and for obtaining detailed error information for the error message at a time frame when the particular event occurs. In addition, the event management system and storage media include an event viewer for viewing the detailed error information.
Inventors
- 👤 Toshihisa Fujii
- 👤 William L. Call
- 👤 Abhijit P. Rane
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-06 22:31
CPC Classifications
G; G06; G06F; G06F11/00; G06F11/07; G06F11/0703; G06F11/0766; G06F11/0787; G06F11/0706; G06F11/0709; G06F11/30; G06F11/32; G06F11/324; G06F11/327
Claims Analysis
Total Claims: 16
Claim 1
Independent Claim
117 words
An event management system for identifying and logging event information for a plurality of coupled subsystems, said system comprising: means for reporting an error message in response to an occurrence of a particular event; means, responsive to receiving said error message, for identifying a source of said error message from a plurality of coupled subsystems; means for obtaining detailed error information for said error message at a time frame when said particular event occurs, according to said source of said error message; a service routine which is capable of receiving logging event information from a particular subsystem and handling a logging operation of another subsystem; and means for providing said detailed error information to an event viewer.
Claim 2
Dependent Claim
117 words
An event management system for identifying and logging event information for a plurality of coupled subsystems, said system comprising: means for reporting an error message in response to an occurrence of a particular event; means, responsive to receiving said error message, for identifying a source of said error message from a plurality of coupled subsystems; means for obtaining detailed error information for said error message at a time frame when said particular event occurs, according to said source of said error message; a service routine which is capable of receiving logging event information from a particular subsystem and handling a logging operation of another subsystem; and means for providing said detailed error information to an event viewer.
Claim 3
Dependent Claim
42 words
The event management system of claim 1 wherein said event message corresponds to an event type that includes at least one event type selected from the group consisting of: an information event type, a warning event type and an error event type.
Claim 4
Dependent Claim
22 words
The event management system of claim 2 wherein said event type is an error event type used to report a non-recoverable problem.
Claim 5
Dependent Claim
32 words
The event management system of claim 1 further comprising a definition table that defines a relationship between an identification of a particular subsystem and a message catalog associated with said particular subsystem.
Claim 6
Dependent Claim
28 words
The event management system of claim 4 wherein said message catalog includes a special event message for identifying logging information that does not originate from said particular subsystem.
Claim 7
Dependent Claim
118 words
A storage media for identifying and logging event information for a plurality of coupled subsystems, said storage media comprising: means for reporting an error message in response to an occurrence of a particular event; means, responsive to receiving said error message, for identifying a source of said error message from said plurality of coupled subsystems; means for obtaining detailed error information for said error message at a time frame when said particular event occurs, according to said source of said error message; a service routine which is capable of receiving logging event information from a particular subsystem and handling a logging operation of another subsystem; and a means for providing said detailed error information to an event viewer.
Claim 8
Dependent Claim
118 words
A storage media for identifying and logging event information for a plurality of coupled subsystems, said storage media comprising: means for reporting an error message in response to an occurrence of a particular event; means, responsive to receiving said error message, for identifying a source of said error message from said plurality of coupled subsystems; means for obtaining detailed error information for said error message at a time frame when said particular event occurs, according to said source of said error message; a service routine which is capable of receiving logging event information from a particular subsystem and handling a logging operation of another subsystem; and a means for providing said detailed error information to an event viewer.
Claim 9
Dependent Claim
41 words
The storage media of claim 1 wherein said event message corresponds to an event type that includes at least one event type selected from the group consisting of: an information event type, a warning event type and an error event type.
Claim 10
Dependent Claim
21 words
The storage media of claim 7 wherein said event type is an error event type used to report a non-recoverable problem.
Claim 11
Dependent Claim
31 words
The storage media of claim 6 further comprising a definition table that defines a relationship between an identification of a particular subsystem and a message catalog associated with said particular subsystem.
Claim 12
Dependent Claim
27 words
The storage media of claim 9 wherein said message catalog includes a special event message for identifying logging information that does not originate from said particular subsystem.
Claim 13
Independent Claim
102 words
A method for identifying and logging event information for a plurality of coupled subsystems, said method comprising the steps of: (a) receiving an error message in response to an occurrence of a particular event; (b) identifying a source of said error message from said plurality of coupled subsystems; (c) obtaining detailed error information for said re message at a time frame when said particular event occurs, according to said source of said error message; (d) receiving logging event information from a particular subsystem and handling a logging operation of another subsystem; and (e) providing said detailed error information to an event view.
Claim 14
Independent Claim
102 words
A method for identifying and logging event information for a plurality of coupled subsystems, said method comprising the steps of: (a) receiving an error message in response to an occurrence of a particular event; (b) identifying a source of said error message from said plurality of coupled subsystems; (c) obtaining detailed error information for said re message at a time frame when said particular event occurs, according to said source of said error message; (d) receiving logging event information from a particular subsystem and handling a logging operation of another subsystem; and (e) providing said detailed error information to an event view.
Claim 15
Dependent Claim
24 words
The method as recited in claim 11 wherein said step of obtaining retrieves said detailed error information from said source of said error message.
Claim 16
Dependent Claim
41 words
The method as recited in claim 11 wherein said step of identifying further identifies an address, associated with said source, for retrieving said detailed error information, said step of obtaining retrieving said detailed error information through the use of said address.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-04-05 | 2002-10-05 | 2003-04-06 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-04-05 | 2006-10-05 | 2007-04-06 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-04-05 | 2010-10-05 | 2011-04-06 | $7700.00 | Window Closed / Lapsed |