US6012095A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Generic notification framework system and method for enhancing operation of a management station on a network
Assignee: Hewlett Packard Enterprise Development LP
•
Filing: 1997-11-18
•
Granted: 2000-01-04
•
Expires: 2017-11-18
Abstract
Abstract A generic notifications framework (GNF) system integrates information from different protocols in a management station interfaced with a network and permits correlation of the information to make more sophisticated management decisions. The generic notifications framework system has one or more protocol-specific translators in communication with the network, a generic notifications framework in communication with the translators, and one or more consumer components in communication with the framework. The translators receive event data elements corresponding with different management protocols from the network and translate the event data elements into respective canonical data structures. Each of the canonical data structures includes (a) a generic field that is common to generally all of the canonical data structures, (b) one or more attribute fields generated by the translator based upon an examination of a protocol data unit (PDU) associated with each of the event data elements, and (c) a protocol data unit (PDU) that is generally identical to the native PDU that arrived with the event data element. Consumer components register with the framework to receive any canonical data structures having particular attribute fields. The generic notifications framework forwards the appropriate canonical data structures to appropriate consumer components based upon the attribute field values. A correlator may be associated with the framework to correlate the canonical data structures to derive an intelligent event data element, which is essentially the result of an assimilation and logical evaluation of various event data elements.
Inventors
- 👤 Dean R. Thompson
- 👤 Thomas G. Bartz
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-29 19:55
CPC Classifications
H; H04; H04L; H04L41/00; H04L41/02; H04L41/0213; H04L41/022; H04L41/0226; H04L41/06; H04L41/0631; H04L41/12; H04L41/20; H04L41/22; H04L43/00; H04L43/08; H04L43/0805; H04L43/0811; H04L69/00; H04L69/08; H04L69/18
Claims Analysis
Total Claims: 25
Claim 1
Independent Claim
256 words
A system for enhancing operation of a management station on a network by integrating information from different management protocols, comprising: (1) a translator connected to said network to receive event data elements corresponding with different management protocols from said network, said translator configured to translate said event data elements into respective canonical data structures, said translator configured to selectively extract attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; (2) a generic notifications framework connected to said translator to receive said canonical data structures, said generic notifications framework configured to selectively route said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and (3) a consumer component capable of communicating with said framework, said consumer component configured to register with said framework to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 2
Independent Claim
256 words
A system for enhancing operation of a management station on a network by integrating information from different management protocols, comprising: (1) a translator connected to said network to receive event data elements corresponding with different management protocols from said network, said translator configured to translate said event data elements into respective canonical data structures, said translator configured to selectively extract attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; (2) a generic notifications framework connected to said translator to receive said canonical data structures, said generic notifications framework configured to selectively route said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and (3) a consumer component capable of communicating with said framework, said consumer component configured to register with said framework to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 3
Dependent Claim
21 words
The system of claim 1, further comprising a correlator configured to correlate said canonical data structures to derive an intelligent event.
Claim 4
Dependent Claim
30 words
The system of claim 2, further comprising a configurator connected to said framework and configured to specify which of said canonical data structures are to be forwarded to said correlator.
Claim 5
Dependent Claim
80 words
The system of claim 1, further comprising: a plurality of event subsystems connected to said network, each one of said event subsystems adapted to receive event elements from said network having a particular protocol associated said each one; and a plurality of translators, one of which is said translator, each of which are connected to a respective one of said event subsystems, and all of which are connected to said framework to provide said canonical data structures to said framework.
Claim 6
Dependent Claim
36 words
The system of claim 4, further comprising a configurator connected to said translators and configured to specify which of said event data elements are to be communicated by each said translator to said generic notification framework.
Claim 7
Dependent Claim
38 words
The system of claim 5, wherein said configurator is further connected to said translator and is further configured to specify which of said event data elements are to be communicated by said translator to said generic notification framework.
Claim 8
Dependent Claim
240 words
A computer system comprising: (1) a translator connected to a network to receive event data elements corresponding with different management protocols from said network, said translator configured to translate said event data elements into respective canonical data structures, said translator configured to selectively extract attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; (2) a generic notifications framework connected to said translator to receive said canonical data structures, said generic notifications framework configured to selectively route said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and (3) a consumer component capable of communicating with said framework, said consumer component configured to register with said framework to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 9
Dependent Claim
240 words
A computer system comprising: (1) a translator connected to a network to receive event data elements corresponding with different management protocols from said network, said translator configured to translate said event data elements into respective canonical data structures, said translator configured to selectively extract attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; (2) a generic notifications framework connected to said translator to receive said canonical data structures, said generic notifications framework configured to selectively route said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and (3) a consumer component capable of communicating with said framework, said consumer component configured to register with said framework to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 10
Independent Claim
222 words
A system for enhancing operation of a management station on a network by integrating information from different management protocols, comprising: translating means for receiving event data elements corresponding with different management protocols from said network and for translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; framework means for routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and consumer means for communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 11
Independent Claim
222 words
A system for enhancing operation of a management station on a network by integrating information from different management protocols, comprising: translating means for receiving event data elements corresponding with different management protocols from said network and for translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; framework means for routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and consumer means for communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 12
Dependent Claim
20 words
The system of claim 8, further comprising a means for correlating said canonical data structures to derive an intelligent event.
Claim 13
Dependent Claim
31 words
The system of claim 9, further comprising a means for analyzing said canonical data structures to determine which of said canonical data structures are to be correlated by said correlating means.
Claim 14
Dependent Claim
53 words
The system of claim 8, further comprising a means for receiving canonical data structures from a plurality of translators associated with a respective plurality of event subsystems connected to said network, each one of said event subsystems adapted to receive event elements from said network having a particular protocol associated said each one.
Claim 15
Dependent Claim
27 words
The system of claim 8, further comprising a means for evaluating said event data elements to specify which of said event data elements are to be routed.
Claim 16
Dependent Claim
206 words
A computer system comprising: translating means for receive event data elements corresponding with different management protocols from a network and for translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; framework means for routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and consumer means for communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particle one of said predefined attribute fields.
Claim 17
Dependent Claim
206 words
A computer system comprising: translating means for receive event data elements corresponding with different management protocols from a network and for translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; framework means for routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and consumer means for communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particle one of said predefined attribute fields.
Claim 18
Independent Claim
214 words
A method for enhancing operation of a management station on a network by integrating information from different management protocols, comprising the steps of: receiving event data elements corresponding with different management protocols from said network; translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 19
Independent Claim
214 words
A method for enhancing operation of a management station on a network by integrating information from different management protocols, comprising the steps of: receiving event data elements corresponding with different management protocols from said network; translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 20
Dependent Claim
20 words
The method of claim 14, further comprising the step of correlating said canonical data structures to derive an intelligent event.
Claim 21
Dependent Claim
27 words
The method of claim 15, further comprising the step of analyzing said canonical data structures to determine which of said canonical data structures are to be correlated.
Claim 22
Dependent Claim
53 words
The method of claim 14, further comprising the step of receiving canonical data structures from a plurality of translators associated with a respective plurality of event subsystems connected to said network, each one of said event subsystems adapted to receive event elements from said network having a particular protocol associated said each one.
Claim 23
Dependent Claim
27 words
The method of claim 14, further comprising the step of evaluating said event data elements to specify which of said event data elements are to be routed.
Claim 24
Dependent Claim
199 words
A computer programmed to perform the steps of: receiving event data elements corresponding with different management protocols from a network; translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particular one of said predefined attribute fields.
Claim 25
Dependent Claim
199 words
A computer programmed to perform the steps of: receiving event data elements corresponding with different management protocols from a network; translating said event data elements into respective canonical data structures by extracting attribute data from some, but not all of, said event data elements by examination of a native protocol data unit (PDU) associated with each of said event data elements, each of said canonical data structures including: (a) a generic field specifying a source, environment type, time of origin, number of extracted attributes, and length of said PDU of the corresponding event data element; (b) an attribute field having attribute data, when said extraction is possible, created by said translator upon examination of said PDU associated with the corresponding event data element, said attribute data specifying a name, type, length, and value; and (c) protocol data that is an encapsulation of said PDU associated with the corresponding event data element; routing said canonical data structures by forwarding canonical data structures having predefined attribute fields to corresponding consumer components; and communicating with a consumer component and permitting said consumer component to register to receive any of said canonical data structures having a particular one of said predefined attribute fields.
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) | 2003-01-03 | 2003-07-05 | 2004-01-04 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-01-03 | 2007-07-05 | 2008-01-04 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-01-03 | 2011-07-05 | 2012-01-04 | $7700.00 | Window Closed / Lapsed |