Data Identification ID for Global Numerical Value Uniqueness
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data communication systems lack unified standards for data tables and communication protocols, leading to inconsistencies and challenges in data interpretation across different measuring instruments and systems, particularly in photovoltaic power generation systems.
Innovation Solution
A novel data structure comprising a logical database and a data identification ID system, where the data identification ID includes a unit ID and a type ID, enabling global identification of numerical values and data, even without a local protocol specification, and allowing for centralized management of data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If local protocol specifications are used for data communication, then data can be transmitted within a single measurement terminal or system, but channel numbers overlap when multiple measurement terminals are used and global uniqueness cannot be achieved
Solution Approach 1:
The data identification mechanism is segmented into two parts: a fixed protocol specification portion (channel table format) and a dynamic identification portion (timestamp-based data identification ID). This segmentation allows the protocol structure to remain simple and familiar while the identification IDs provide global uniqueness through timestamp differentiation, resolving the contradiction between local simplicity and global adaptability.
Solution Approach 2:
The invention adds a temporal dimension (timestamp) to the data identification process. Instead of relying solely on spatial/channel numbering that overlaps across multiple terminals, the system incorporates time-based identification, creating a multi-dimensional identification space where data from multiple terminals can be uniquely distinguished without increasing protocol complexity.
2Reliability
If protocol specifications are frequently updated to improve data communication standards, then data meaning can be accurately represented, but version management becomes necessary and installation site problems occur
Solution Approach 1:
The system performs preliminary action by embedding the data identification ID (including timestamp) directly into the data packet at the source. This preliminary identification eliminates the need for subsequent version matching and interpretation, as the data carries its own unique identifier that ensures accurate meaning representation regardless of protocol updates, reducing installation site problems.
Solution Approach 2:
The data identification ID acts as an intermediary between the protocol specification and the actual data meaning. Instead of requiring the protocol specification to directly define every data meaning (which requires frequent updates), the identification ID serves as a mediator that provides stable, unique identification, decoupling the protocol structure from the need for frequent updates while maintaining data accuracy.
3Productivity
If channel numbers are used for data identification within a measurement terminal, then data can be locally identified, but overlapping occurs when multiple measurement terminals are used
Solution Approach 1:
The invention merges two identification approaches: the local channel number system (for efficient terminal-internal identification) and the global timestamp-based identification ID (for unique cross-terminal identification). By combining these approaches, the system maintains the productivity benefits of local channel numbering while achieving the reliability of global uniqueness through the integrated data identification ID that includes timestamp information.
Data Source
AI summary
A pair of logical data structures includes: a logical database in a database server in which numerical data including numerical values associated with a timestamp is recorded; and a data identification ID identifying an attribute of the numerical values. The data identification ID includes a unit ID, having a character string of at least two bytes defining a unit of the numerical data, and an item ID, of at least four bytes and made up of an item number constituted of an integer value of at least two bytes for defining a type ID of at least two bytes for defining a type of the numerical data and for identifying the type ID, and the type ID, the unit ID is associated with a name and a unit character string, and the type ID includes a character string corresponding to each type ID and the unit ID.