Metadata-Driven Asset Management via Relative URIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network management systems require detailed knowledge of application programming interfaces (APIs) and specific protocols for managing assets, making it complex to manage diverse asset types and networks efficiently.
Innovation Solution
The system employs relative Uniform Resource Identifiers (URIs) and a data acquisition (DAQ) runtime to abstract API management, allowing management applications to operate assets without knowing the API, using a common interface for various asset types through native asset interface definitions and protocol handlers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If detailed knowledge of APIs and specific protocols is required for managing assets, then precise control and management of individual assets is achieved, but the complexity of managing diverse asset types increases significantly
Solution Approach 1:
The patent introduces a metadata-driven intermediary layer that sits between management applications and diverse asset APIs. This metadata layer contains standardized interface definitions that abstract away protocol-specific details, allowing management applications to interact with all assets through a common interface while the metadata layer handles the translation to asset-specific protocols.
Solution Approach 2:
The patent creates a universal management interface that can handle multiple asset types through a single standardized protocol. The metadata-driven architecture enables one management application to manage diverse assets (different protocols, devices, and formats) through a unified interface, eliminating the need for separate management code for each asset type.
2Reliability
If management applications require knowledge of specific APIs and protocols for each asset type, then accurate asset control is achieved, but the ease of operation and integration of new assets deteriorates
Solution Approach 1:
The patent implements a self-service mechanism where the metadata layer automatically discovers and configures the appropriate API and protocol for each asset type. When a new asset is introduced, the system automatically retrieves its metadata definition, which contains the necessary interface specifications, eliminating the need for manual configuration or expert knowledge of specific protocols.
Solution Approach 2:
The patent performs preliminary action by pre-defining standardized interface specifications in the metadata layer for various asset types. These pre-configured metadata definitions contain all necessary API and protocol information, so when an asset is introduced, the system already has the templates needed to manage it without requiring real-time analysis or expert intervention.
3Reliability
If extensive framework code and knowledge of network topology are required, then comprehensive asset management is achieved, but the productivity and speed of deployment deteriorates
Solution Approach 1:
The patent extracts protocol-specific and topology-specific knowledge from the management application logic and places it into the metadata layer. This separation allows the core management application to remain simple and protocol-agnostic, while all the complex protocol handling rules are extracted into reusable metadata definitions that can be applied automatically to different assets without modifying the core application code.
Data Source
AI summary
A method for managing an asset that includes identifying a relative location of a scheme, wherein the scheme is used to manage the asset, creating a relative Uniform Resource Identifier (URI) using the relative location, wherein the relative URI that includes at least one variable, and creating an entry in a native access interface definition, wherein the entry that includes the relative URI, wherein the native asset interface definition is bound to a data acquisition (DAQ) definition, and wherein the DAQ definition is an interface between a protocol handler and an information model, wherein managing the asset is performed using an actual URI to obtain management information, wherein the actual URI is obtained by replacing the at least one variable of the relative URI, and wherein the management information is transmitted to a management application.