Automated Meta-Model File Conversion for Device Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Changing the data format of communication data in device communication, such as from XML to Protobuf, requires significant manual effort and is error-prone, involving the replacement of serializers and meta-model files, which is not feasible with hundreds of message types.
Innovation Solution
Automating the conversion of meta-model files from the original data format to the target data format using a transformation rule, allowing for the generation of new meta-model files that can be used by communication partners to change their transmission behavior without manual adjustment, thereby minimizing effort and risk of errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual conversion of meta-model files is performed to change data format, then data format can be changed, but the work amount increases considerably and errors occur frequently
Solution Approach 1:
The system performs automatic conversion of meta-model files from source format to target format using a conversion script, eliminating the need for manual intervention. The conversion process is self-executing and generates the necessary meta-model files automatically, reducing both work effort and error rates.
Solution Approach 2:
The manual mechanical process of converting meta-model files is replaced by an automated computational system. A conversion script automatically transforms the meta-model files from the source data format to the target data format, substituting human effort with an automated software-based solution.
2Adaptability or versatility
If serializer is replaced to change data format, then new data format can be used, but the complexity of replacement increases with hundreds of message types
Solution Approach 1:
The conversion script serves as a universal tool that can convert any meta-model file from the source data format to the target data format, regardless of the specific message type. This single multi-functional solution replaces the need for individual conversion processes for each of the hundreds of message types.
Solution Approach 2:
The system separates the conversion function into an independent conversion script that operates separately from the serializers. This segmentation allows the meta-model files to be converted automatically without requiring manual replacement of each serializer, simplifying the overall process.
3Reliability
If external communication partner requires new meta-model files when data format changes, then communication compatibility is maintained, but the overall work amount doubles
Solution Approach 1:
The conversion script acts as an intermediary that automatically generates the meta-model files needed by external communication partners. Instead of manually providing files to multiple partners, the automated script generates all necessary files, reducing the total work effort while ensuring compatibility.
Solution Approach 2:
The system performs preliminary automatic conversion of meta-model files before communication occurs. By pre-generating the necessary meta-model files in the target format, the system ensures communication partners receive compatible files without requiring manual intervention at the time of communication setup.
Data Source
AI summary
The invention relates to a method for changing a data format of communication data (14) of a device communication, wherein the respective communication partner (11, 12) is configured such that it converts memory data (17) to be sent into the original data format (22) by means of a first serializer (20) on the basis of a first metamodel file (21). The invention provides for a processor device (18) to generate a second metamodel file (27) from the first metamodel file (21) by means of a transformation rule (29), wherein the transformation rule (29) assigns a respective structural element (S) of the first metamodel file (21) to a respective corresponding structural element (S'), so that the second metamodel file (27) defines all of the structural elements (S') to be sent in the target data format, and in the respective communication partner (11, 12) the first serializer (20) thereof is replaced by a second serializer (20') for the target data format and the first metamodel file (21) thereof is replaced by the second metamodel file (27).