Table Definition Language Generation via Inheritance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of updating table definition language files for smart meters is time-consuming and costly, as manufacturers need to completely rewrite these files for each modification, requiring a substantial number of new files to reflect firmware changes and varying meter types.
Innovation Solution
A meter management system that generates subsequent table definition languages by applying modifications to existing files through inheritance, allowing only the changes to be implemented, rather than rewriting entire files, thereby reducing effort, cost, and time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If table definition language files are completely rewritten for each modification, then the definitions accurately reflect firmware changes and meter types, but the process becomes time-consuming and costly
Solution Approach 1:
The TDL file creation process is segmented into template portions and modification portions. A master template contains the complete TDL structure, and modifications are applied as separate fragments or patches. This segmentation allows the system to reuse the stable template portion across multiple meter types and firmware versions, while only rewriting the specific modification portions when changes are needed.
Solution Approach 2:
A master TDL template is created in advance containing the complete structure and definitions. This preliminary action establishes a reusable foundation that eliminates the need to create TDL files from scratch for each new meter type or firmware version. The template is prepared beforehand and can be systematically modified through inheritance and patching mechanisms.
2Reliability
If complete TDL files are rewritten for each meter type and firmware modification, then all attributes and functionalities are properly defined, but the effort and cost increase substantially
Solution Approach 1:
A universal master TDL template is created that serves multiple meter types and firmware versions. This single template can be reused across different applications through inheritance and selective modification, eliminating the need to create separate complete TDL files for each scenario. The template maintains universality while allowing specific customizations through the patching mechanism.
Solution Approach 2:
Instead of creating original TDL files from scratch for each meter type, the system copies the master template and applies modifications. The copying mechanism preserves the complete and reliable structure of the original template while allowing efficient reproduction and adaptation. Modifications are applied as patches or fragments rather than requiring complete rewriting.
3Adaptability or versatility
If numerous TDL files are created to reflect all firmware modifications and meter types, then each meter has its own customized definition file, but the number of files becomes substantial and difficult to manage
Solution Approach 1:
The TDL file structure implements a nested hierarchy where a master template contains base definitions, which in turn contain or reference module-specific definitions. Modifications are nested within this hierarchy as patches or fragments that inherit from parent templates. This nesting allows multiple levels of customization without creating separate files for each combination, as smaller nested units can be selectively applied and combined.
Solution Approach 2:
Multiple TDL definitions are merged through inheritance and composition rather than maintained as separate files. The system combines the master template with modification fragments and module-specific definitions into a unified TDL file at runtime or during compilation. This merging approach consolidates what would otherwise require numerous separate files into a manageable set of core templates and patches.
Data Source
AI summary
A non-transitory computer readable medium is provided that includes instructions to interpret a table definition language fragment, that includes modifications of attributes and functionalities defined in a first table definition language. The non-transitory computer readable medium also includes instructions to generate a second table definition language with the subsequent modifications based at least upon applying the modifications in the table definition language fragment to the first table definition language.