In-Vehicle Data Normalization for Cross-Model ECU Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicle data acquired through in-vehicle network communication lacks a standardized format, making it inaccessible to users due to variations in data structure across different vehicle manufacturers, models, and shipping timelines, requiring technical knowledge of specific CAN communication frames.
Innovation Solution
An in-vehicle device with a processor and memory that normalizes and structures vehicle data into a predetermined format, enabling standardized data transmission to a management center, independent of vehicle manufacturer or model, allowing access by specific data names or categories.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If vehicle data is acquired through in-vehicle network communication from different manufacturers and models, then the quantity of data increases, but the data lacks standardized format and becomes inaccessible to users
Solution Approach 1:
The patent introduces an in-vehicle device as an intermediary component between the ECU and external users. This device acquires raw vehicle data from the ECU, applies normalization processing to convert it into standardized formats, and then provides the processed data to users. The intermediary transforms incompatible proprietary formats into universal accessible formats, resolving the contradiction between data quantity and accessibility.
Solution Approach 2:
The normalization processing changes the format parameters of vehicle data from manufacturer-specific proprietary formats to standardized universal formats. By transforming data parameters (encoding schemes, data structures, communication protocols), the system enables users to access diverse vehicle data without needing specialized knowledge of each manufacturer's format, thus resolving the accessibility issue while maintaining data quantity.
2Adaptability or versatility
If proprietary data formats are used by different vehicle manufacturers, then each manufacturer can optimize for their specific vehicle architecture, but users require technical knowledge of specific CAN communication frames to access the data
Solution Approach 1:
The in-vehicle device serves as a mediator that handles the complexity of proprietary formats internally. It receives data in various manufacturer-specific formats from the ECU, performs normalization to convert these formats into standardized universal formats, and presents the simplified data to users. This intermediary approach maintains adaptability to different vehicle architectures while reducing the technical knowledge burden on users.
Solution Approach 2:
The system creates standardized copies of proprietary vehicle data through normalization processing. Instead of requiring users to directly access complex proprietary CAN communication frames, the in-vehicle device creates simplified standardized versions of the data that retain the essential information while eliminating format complexity. This copying approach preserves adaptability while reducing user complexity requirements.
3Speed
If raw vehicle data is transmitted without normalization, then data transmission speed is maintained, but the data structure varies across manufacturers making it unusable for general applications
Solution Approach 1:
The system performs preliminary normalization processing of vehicle data within the in-vehicle device before transmission to external systems. By pre-converting proprietary formats into standardized formats at the source, the data is ready for immediate use in various applications without requiring additional format conversion at the receiving end. This preliminary action ensures both fast transmission and universal usability.
Solution Approach 2:
The in-vehicle device acts as an intermediary that performs format standardization between data acquisition and external transmission. It receives raw data from the ECU, normalizes it to universal formats, and then transmits the standardized data. This intermediary processing ensures that transmission speed is maintained while simultaneously improving data usability across different applications and manufacturers.
Data Source
AI summary
An in-vehicle device mounted in a vehicle includes: at least one processor; and at least one memory storing computer program code. The computer program code, when executed by the at least one processor, causes the at least one processor to serve as a unit that is configured to communicate data with a center configured to manage vehicle data. The unit includes: a normalization portion that is configured to normalize a plurality of pieces of the vehicle data acquired from an electronic control unit mounted in the vehicle; a data structuring portion that is configured to structure the plurality of pieces of the vehicle data that are normalized by the normalization portion into a predetermined data structure; and a data transmission portion that is configured to transmit the plurality of pieces of the vehicle data that are structured by the data structuring portion to the center through a communicator.