Vehicular Gateway ECU Local Configuration Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicular electronic control systems cannot verify the properness of updated configuration information without a contracted OTA service, as they rely on communication with a center device, which is not possible before the service contract is made.
Innovation Solution
A vehicular electronic control device acquires update data from a wired tool via wired communication, updates the software of an update target node, and collates the updated configuration information with information from a management target node to determine consistency, allowing verification even without a contracted OTA service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system relies on communication with a center device to verify updated configuration information, then verification can be performed through centralized control, but verification is not possible before the OTA service contract is made
Solution Approach 1:
The gateway ECU acts as an intermediary between the update target ECU and the verification process. It collects updated configuration information from the update target ECU, collates it with reference configuration information, and determines consistency locally, eliminating the need for direct center device communication in the verification process.
Solution Approach 2:
The verification process transitions from a centralized dimension (center device verification) to a distributed dimension (gateway ECU verification). This allows verification to occur at multiple levels and times, including before the OTA service contract is made, by empowering the gateway ECU to perform verification independently.
2Ease of operation
If update data is downloaded from a center device via wireless communication, then OTA update can be performed, but verification of updated configuration information cannot be performed before service contract
Solution Approach 1:
The gateway ECU performs verification of updated configuration information in advance, before the OTA service contract is made. By collecting and verifying configuration information upfront, the system ensures reliability is established prior to formal service activation, preventing potential issues from arising later.
Solution Approach 2:
The system implements a feedback mechanism where the gateway ECU continuously monitors and verifies configuration information from update target ECUs. This feedback loop ensures that any inconsistencies are detected and can be addressed, maintaining system reliability throughout the update process regardless of service contract status.
3Stability of the object's composition
If centralized verification through center device is used, then consistent configuration management is achieved, but system complexity and communication requirements increase
Solution Approach 1:
The verification function is segmented from the center device and assigned to the gateway ECU. This segmentation allows the gateway to handle verification tasks locally, reducing the communication burden on the center device and simplifying the overall system architecture while maintaining configuration consistency through distributed verification.
Data Source
AI summary
A vehicular electronic control device is configured to acquire update data from a wired tool via wired communication, acquire, as first updated configuration information, updated configuration information from the wired tool, update software of an update target node by writing the update data to the update target node, acquire, as second updated configuration information, updated configuration information from a management target node including the update target node, and collate the first updated configuration information with the second updated configuration information to determine consistency of the updated configuration information.