Battery Data Standardization Using Parsing Scripts and Device Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The diversity of data standards for battery data, including national, enterprise, and custom standards, results in varied content that cannot be effectively used downstream, hindering efficient data utilization.
Innovation Solution
A data processing system with an access layer, configuration layer, and data layer is implemented, utilizing message parsing scripts and device models to convert and map data into standard formats, allowing for flexible adaptation to different standards and efficient downstream use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data from multiple standards (national, enterprise, custom) are collected directly, then data coverage is improved, but data compatibility and usability downstream deteriorate
Solution Approach 1:
The patent introduces a standardized data table as an intermediary layer between diverse data sources and downstream applications. The access layer collects data from multiple standards, converts them through message parsing scripts into standardized formats, and maps them to a unified data table structure. This intermediary standardized table enables both broad data coverage and consistent usability without requiring changes to downstream systems.
Solution Approach 2:
The patent transforms data from various standards by changing their parameters and formats into a unified standardized structure. The message parsing scripts perform parameter transformation, converting diverse data formats (national standards, enterprise standards, custom standards) into a common standardized format that can be consistently processed downstream, thus resolving the contradiction between maintaining data diversity and ensuring usability.
2Ease of operation
If data conversion and standardization processes are implemented, then data usability is improved, but processing complexity increases
Solution Approach 1:
The patent segments the data processing system into distinct layers: access layer for data collection, message parsing layer for format conversion, and data layer for standardized storage. Each layer handles specific conversion tasks independently, which reduces overall processing complexity by breaking down the complex standardization process into manageable, modular segments that can be developed and maintained separately.
Solution Approach 2:
The system performs preliminary data standardization and conversion at the access and message parsing layers before data reaches the downstream applications. By pre-converting diverse data formats into standardized structures in advance, the system eliminates the need for complex real-time conversion processes downstream, thereby reducing processing complexity where it matters most for usability.
3Adaptability or versatility
If message parsing scripts and device models are used for conversion, then adaptability to different standards is improved, but system complexity increases
Solution Approach 1:
The patent creates a universal message parsing script framework that can handle multiple data standards through a single standardized interface. The device models serve as universal templates that define standardized data structures applicable across different standards. This multi-functional approach allows the system to adapt to various standards without requiring separate processing logic for each, thereby improving adaptability while controlling system complexity through reusability.
Data Source
AI summary
A data processing method implemented based on a data processing system. The data processing system includes an access layer, a configuration layer, and a data layer. The method includes: accessing, through the access layer, data under processing; obtaining, through the access layer, a message parsing script set by the configuration layer, and converting the data under processing into standard data; and obtaining, through the data layer, a device model set by the configuration layer, and mapping the standard data to a data table corresponding to the device model.