Onboard Communication Device Version Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In vehicle data communication systems, program updates can change memory addresses, leading to mistakenly selected data being transmitted from control units to management servers, as the relationship between memory addresses and data is not always recognized by onboard communication devices.
Innovation Solution
Incorporating a version identifier system where the onboard communication device compares and updates memory address information with a management server when the version identifier stored in the control unit does not match the onboard communication device's version identifier, ensuring accurate data transmission by designating the correct memory address.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If program updates are performed in control units, then system functionality is improved, but memory address relationships become outdated in onboard communication devices, leading to data transmission errors
Solution Approach 1:
The patent applies preliminary action by having the onboard communication device obtain version information from the control unit before data transmission. This allows the communication device to proactively check for program updates and retrieve updated memory address relationships in advance, preventing transmission errors caused by outdated address information.
Solution Approach 2:
The patent implements feedback through a version information checking mechanism. The onboard communication device continuously monitors version information from the control unit, compares it with stored version information, and automatically updates memory address relationships when version differences are detected. This closed-loop feedback ensures synchronization between the communication device and control unit.
2Reliability
If version checking and update mechanisms are implemented, then data transmission accuracy is improved, but communication frequency and system complexity increase
Solution Approach 1:
The patent applies local quality by implementing version checking specifically for memory address relationships rather than checking all data transmissions. The system selectively manages version information only where program updates occur in control units, reducing unnecessary communication overhead while maintaining accuracy where it matters most.
Solution Approach 2:
The onboard communication device performs self-service by autonomously checking version information, determining whether updates are needed, and updating its own memory address relationships without requiring external intervention. This reduces system complexity by eliminating the need for centralized update management.
Data Source
AI summary
A vehicle includes a control unit and an onboard communication device. The control unit includes a memory and is configured to store a program and a first version identifier in the memory. The program is updated at any program update timing. The first version identifier is directed to identifying of a version of the updated program. The onboard communication device is configured to hold information relating to memory addresses of the memory and hold a second version identifier that is updated at predetermined timing independent of the program update timing. The onboard communication device is configured to obtain, at the predetermined timing, the first version identifier in the memory from the control unit and to update the information relating to the memory addresses by communicating with the management server when the first version identifier in the memory does not agree with the second version identifier in the onboard communication device.