Configuration Data Conversion for Cross-Model Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Different data processing systems use incompatible configuration models, preventing the transfer of data objects between them due to configuration incompatibility.
Innovation Solution
The integration of data objects from various configuration models is achieved through a conversion process, where configuration data is transformed to match the model expected by the receiving application server, using a conversion component that determines and adjusts the configuration model of data objects to ensure compatibility across different systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data objects are transferred between different systems, then data sharing capability is improved, but configuration incompatibility prevents successful transfer
Solution Approach 1:
The patent introduces a mediation layer that sits between data objects from different configuration models and the application server. This mediator automatically transforms configuration data from various models (XML, JSON, YAML, etc.) into a unified format that the application server can process, enabling data sharing without requiring the application to handle multiple configuration formats directly.
Solution Approach 2:
The system dynamically changes the parameters and structure of configuration data based on the source configuration model. The mediation layer detects the input configuration format and automatically adjusts the data structure, data types, and organization to match the target unified configuration model, resolving compatibility issues through parameter transformation.
2Adaptability or versatility
If a unified configuration model is implemented, then system integration is improved, but conversion complexity increases
Solution Approach 1:
The conversion process is made self-service through automatic detection and transformation. When configuration data is received, the system automatically identifies the source configuration model type, selects the appropriate conversion rules, and transforms the data without requiring manual intervention or complex configuration management from users.
Solution Approach 2:
The system performs preliminary actions by pre-defining conversion rules and transformation logic for multiple configuration models. These conversion pathways are established in advance, allowing the mediation layer to quickly transform incoming configuration data without performing complex real-time analysis of the conversion process.
3Reliability
If configuration data is transformed for each data object, then compatibility is improved, but processing time increases
Solution Approach 1:
Conversion rules and transformation logic are prepared in advance for each configuration model type. The system pre-compiles and caches the transformation pathways, so when configuration data needs to be converted, the system simply applies the pre-defined rules rather than generating conversion logic on-the-fly, significantly reducing processing time.
Solution Approach 2:
The system performs efficient parameter changes by focusing transformations only on the specific configuration parameters that differ between models. Rather than completely reconstructing each configuration object, the mediation layer identifies and transforms only the necessary parameters, maintaining compatibility while minimizing processing overhead.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Example methods and systems automatically convert configuration data from one format to another, allowing data objects to be used by multiple application servers even though those application servers use different configuration models. In an embedded configuration model, configuration data is embedded in the data object to which the configuration data applies. In a referential configuration model, each data object includes an identifier for the corresponding configuration data. Accessing the configuration data for the data object is achieved by using the identifier to look up the configuration data from another location (e.g., in a database). To support transferring a data object between applications using different configuration models, the configuration model for the data object is changed to match the configuration model expected by the application receiving the data object.