US6317748B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Management information to object mapping and correlator
Assignee: Microsoft Technology Licensing LLC
•
Filing: 1998-05-08
•
Granted: 2001-11-13
•
Expires: 2018-05-08
Abstract
Abstract A method and system to provide management information of network devices by mapping between SNMP MIB module schema and Common Information Model (CIM) schema. MIB modules are tree-structured lists of objects for describing SNMP network device information, whereas CIM schema employs user-intuitive, object-oriented classes to model such information. A mapping process enumerates the MIB objects and then maps the objects into CIM Managed Object Format (MOF) classes using defined mapping tables. A correlation mechanism is further provided to efficiently determine in real time which MIBs (or portions thereof) and corresponding CIM classes a network device supports.
Inventors
- 👤 Steven J. Menzies
- 👤 Syed N. Ahmed
- 👤 Kenneth M. Osborne
- 👤 Rajeev Byrisetty
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-05 18:40
CPC Classifications
H; H04; H04L; H04L41/00; H04L41/02; H04L41/0233; G; G06; G06F; G06F16/00; G06F16/20; G06F16/25; G06F16/258; H04L41/0213; H04L41/04; H04L41/046; Y; Y10; Y10S; Y10S707/00; Y10S707/99941; Y10S707/99944; Y10S707/99946
Claims Analysis
Total Claims: 20
Claim 1
Independent Claim
107 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class and maintaining the mapping for subsequent data modeling, and if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances and maintaining the mapping for subsequent data modeling.
Claim 2
Dependent Claim
107 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class and maintaining the mapping for subsequent data modeling, and if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances and maintaining the mapping for subsequent data modeling.
Claim 3
Dependent Claim
15 words
The method of claim 1 wherein the object classes comprise managed object format (MOF) classes.
Claim 4
Dependent Claim
34 words
The method of claim 1 wherein determining whether the MIB object corresponds to a scalar collection or a table collection comprises determining if a direct parent in a MIB tree is a named node.
Claim 5
Dependent Claim
37 words
The method of claim 1 wherein the MIB object corresponds to a scalar collection, and wherein determining whether the MIB object corresponds to a scalar collection or a table collection comprises evaluating syntax in the MIB object.
Claim 6
Dependent Claim
30 words
The method of claim 1 wherein the MIB object corresponds to a scalar collection, and wherein mapping the MIB object information to the singleton class includes accessing a mapping table.
Claim 7
Dependent Claim
32 words
The method of claim 1 wherein the MIB object corresponds to a scalar collection, and wherein mapping the MIB object information to the singleton class includes extracting properties from the MIB object.
Claim 8
Dependent Claim
35 words
The method of claim 1 wherein the MIB object corresponds to a scalar collection, and wherein mapping the MIB object information to the singleton class comprises translating the MIB object information to MOF class information.
Claim 9
Dependent Claim
41 words
The method of claim 1 wherein the MIB object corresponds to a scalar collection, and wherein mapping the MIB object information to a singleton class includes extracting the MIB object name from the scalar collection, and basing a class name thereon.
Claim 10
Dependent Claim
36 words
The method of claim 1 wherein the MIB object corresponds to a table collection, and wherein mapping the MIB object information to the class capable of describing a plurality of instances comprises accessing a mapping table.
Claim 11
Dependent Claim
42 words
The method of claim 1 wherein the MIB object corresponds to a table collection, and wherein mapping the MIB object information to the class capable of describing a plurality of instances comprises extracting keys of a keyed class of the table collection.
Claim 12
Dependent Claim
42 words
The method of claim 1 wherein the MIB object corresponds to a table collection, and wherein mapping the MIB object information to the class capable of describing a plurality of instances comprises mapping the MIB object information to a keyed MOF object.
Claim 13
Dependent Claim
38 words
The method of claim 1 wherein the MIB object corresponds to a table collection, and wherein mapping the MIB object information to the class capable of describing a plurality of instances includes extracting properties from the MIB object.
Claim 14
Dependent Claim
14 words
A computer-readable medium having computer-executable instructions for performing the method of claim 1 .
Claim 15
Dependent Claim
120 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class by translating the MIB object information to (Managed Object Format) MOF class information, and maintaining the mapping for subsequent data modeling, and, if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances and maintaining the mapping for subsequent data modeling.
Claim 16
Dependent Claim
120 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class by translating the MIB object information to (Managed Object Format) MOF class information, and maintaining the mapping for subsequent data modeling, and, if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances and maintaining the mapping for subsequent data modeling.
Claim 17
Dependent Claim
118 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class and maintaining the mapping for subsequent data modeling, and if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances by extracting keys of a keyed class of the table collection, and maintaining the mapping for subsequent data modeling.
Claim 18
Dependent Claim
118 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class and maintaining the mapping for subsequent data modeling, and if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances by extracting keys of a keyed class of the table collection, and maintaining the mapping for subsequent data modeling.
Claim 19
Dependent Claim
121 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class and maintaining the mapping for subsequent data modeling, and if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances by mapping the MIB object information to a keyed (Managed Object Format) MOF object, and maintaining the mapping for subsequent data modeling.
Claim 20
Dependent Claim
121 words
In a computer system, a method of mapping Management Information Base (MIB) objects to non-MIB object-oriented managed object classes, comprising, enumerating the MIB objects of a MIB module, and for each MIB object, determining whether the MIB object corresponds to a scalar collection or a table collection, and if the MIB object corresponds to a scalar collection, mapping the MIB object information to a singleton class and maintaining the mapping for subsequent data modeling, and if the MIB object corresponds to a table collection, mapping the MIB object information to a class capable of describing a plurality of instances by mapping the MIB object information to a keyed (Managed Object Format) MOF object, and maintaining the mapping for subsequent data modeling.
References Cited (Backward Citations)
US5291583A
Cited
US5659736A
Cited
US5951649A
Cited
US5509123A
Cited
US5729739A
Cited
US5696697A
Cited
US6003035A
Cited
US5797137A
Cited
US5893107A
Cited
US5983233A
Cited
US5794248A
Cited
US6081808A
Cited
US5870749A
Cited
US5956730A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2004-11-12 | 2005-05-14 | 2005-11-13 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2008-11-12 | 2009-05-14 | 2009-11-13 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2012-11-12 | 2013-05-14 | 2013-11-13 | $7700.00 | Window Closed / Lapsed |