Asset Management Mapping Specification for Protocol Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network management systems require detailed knowledge of the application programming interface (API) of managed assets, making it complex to manage diverse assets through a common interface without specific protocol knowledge.

Innovation Solution

A method and system that utilize an information model request in an information model format, mapping specification, and data acquisition (DAQ) format to translate management requests, allowing management of assets without knowing the API of the asset, using a mapping specification to translate requests between the information model and DAQ formats, enabling management of various asset types through a common interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If detailed knowledge of the asset's API is required for management, then the management operation can be performed accurately, but the complexity of the system increases and diverse assets cannot be managed through a common interface

Engineering Contradiction:
ImproveEase of asset managementVSAvoidSystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer consisting of information models and mapping specifications that sit between the management application and the asset's native API. This intermediary translates generic management requests into asset-specific operations without requiring the management application to know the underlying API details, thereby reducing system complexity while maintaining management capability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the asset management system into distinct layers: the management application layer, the information model layer, the mapping specification layer, and the asset-specific API layer. This segmentation allows each layer to operate independently with well-defined interfaces, reducing overall system complexity while enabling diverse assets to be managed through a common interface

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a common interface is used to manage diverse assets, then the adaptability of the system improves, but the ability to perform accurate management operations deteriorates without specific protocol knowledge

Engineering Contradiction:
ImproveAbility to manage diverse assetsVSAvoidAccuracy of management operation
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates information model copies that represent the essential structure and behavior of diverse assets in a standardized format. These information models capture the key attributes and operations of different asset types, allowing the common interface to interact with various assets through their standardized representations while maintaining the ability to perform accurate management operations

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent utilizes parameter changes in the mapping specifications to adapt the generic information model requests to the specific requirements of different asset types. By dynamically adjusting mapping parameters based on the target asset's characteristics, the system maintains both adaptability to diverse assets and reliability of management operations

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7562084B2System and method for mapping between instrumentation and information model
Publication Date: 2009.07.14 ORACLE AMERICAN INC
  • US7562084B2 patent drawing
  • US7562084B2 patent drawing
  • US7562084B2 patent drawing

AI summary

A method for managing an asset that includes acquiring an information model request for managing the asset, wherein the information model request is in an information model format, identifying a name and a type of an attribute from the information model request, obtaining a mapping specification entry matching the name and the type of the attribute, translating the information model request from the information model format to a data acquisition (DAQ) format based on the mapping specification entry to create a translated request, managing the asset according to the translated request to obtain management information, and transmitting the management information to an information model.