Sparse Information Model Hierarchy Population
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Common Information Model (CIM) Object Managers require pre-population of entire information models, leading to resource waste, as they include all classes despite only supporting a fraction of them, and different revisions necessitate separate persistence repositories.
Innovation Solution
A module declares supported classes, triggering a query to ascertain child-parent information, allowing for sparse population of the information model hierarchy, focusing only on the ancestry of declared classes without populating the entire model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the entire information model is pre-populated with all classes, then inheritance-based queries can be supported, but computing resources are wasted due to the large number of unneeded classes
Solution Approach 1:
The patent segments the complete information model into multiple separate persistence repositories, each storing only the classes and associations relevant to specific modules. Instead of maintaining one large monolithic model, the system divides it into manageable portions that can be independently loaded and managed, reducing the memory footprint and processing overhead for each module.
Solution Approach 2:
The patent extracts and removes unnecessary classes and associations from the information model that are not required by the current module. By selectively including only the relevant subset of classes needed for inheritance-based queries, the system eliminates waste of computing resources while preserving query functionality.
2Ease of operation
If all CIM classes are mapped as abstract classes and subclasses, then a natural hierarchy for modeling CIM inheritance is provided, but resources are wasted populating the entire model when only a fraction is supported
Solution Approach 1:
The patent applies local quality by allowing different modules to have different information model configurations tailored to their specific needs. Each module maintains its own customized information model with only the classes and associations it requires, rather than forcing all modules to use the complete information model. This enables efficient resource utilization while maintaining the benefits of hierarchical modeling.
3Stability of the object's composition
If separate persistence repositories are created for different revisions of the model, then model versioning is maintained, but resource waste increases due to pre-populating each repository
Solution Approach 1:
The patent introduces dynamics by making the information model configurable and adaptable at runtime. Modules can dynamically load only the necessary classes and associations from the persistence repositories based on their current requirements, rather than statically pre-populating all possible classes. This dynamic approach maintains model versioning while avoiding the resource waste of populating unnecessary classes.
Data Source
AI summary
A module possessing a class descriptor declares for the module the supported classes. The installation of the module triggers the examination class information model hierarchies possessed by the container on which the module is installed. Finding the established class information model hierarchies to be lacking with respect to the newly installed supported classes, a query is made to ascertain child-parent information for the newly installed supported classes. Using this information, an ancestry of each class is achieved so as to sparsely populate an information model hierarchy for each newly installed supported class.