ECU Configuration Shield for Protected Vehicle Parameter Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques fail to distinguish and protect configuration parameters modified by a technical coordinator from being altered during updates initiated by a car manufacturer, leading to potential loss of customized settings.
Innovation Solution
Implementing a configuration shield with two dedicated programmable update interfaces, one for the technical coordinator and one for the automobile manufacturer, to protect and manage configuration parameters independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single update interface is used for both technical coordinators and car manufacturers, then update operations are simplified, but configuration parameters modified by technical coordinators cannot be protected from being altered during manufacturer-initiated updates
Solution Approach 1:
The update interface is segmented into two distinct interfaces: a first update interface for technical coordinators to modify configuration parameters, and a second update interface for car manufacturers to initiate updates. This segmentation allows the system to differentiate between coordinator-modified parameters (which need protection) and manufacturer-initiated updates, thereby resolving the contradiction between protecting customized parameters and maintaining interface simplicity.
2Productivity
If configuration parameters are updated without distinction between coordinator and manufacturer initiatives, then update processing is streamlined, but customized settings are lost during manufacturer updates
Solution Approach 1:
Before a manufacturer-initiated update is executed, the system performs a preliminary action by identifying configuration parameters that were modified through the first update interface (by technical coordinators). These identified parameters are then protected from being overwritten during the manufacturer's update process, thus preventing loss of customized settings while maintaining efficient update processing.
Solution Approach 2:
The system introduces an intermediary mechanism (the protection logic) that acts between the manufacturer's update command and the configuration parameters. This intermediary identifies which parameters were previously modified by technical coordinators and prevents their alteration during manufacturer updates, thereby preserving customized information while allowing streamlined update processing.
3Ease of manufacture
If all configuration parameters are treated equally during updates, then update implementation is simple, but technical coordinator modifications are overwritten by manufacturer updates
Solution Approach 1:
The update system applies local quality by treating different configuration parameters differently based on their origin. Parameters modified through the first update interface (by technical coordinators) are marked and protected, while other parameters remain updateable by manufacturers. This localized differentiation preserves customization capability while maintaining relatively simple update implementation through automated identification and protection logic.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A device (20) for managing an electronic control unit (10) of a motor vehicle (1), comprising an update module (201) for updating the configuration of the electronic control unit (10), characterized in that the update module (201) comprises: a first programmable update interface (202) configured to update the parameter value associated with at least one configuration parameter and to update the filter value associated with said at least one configuration parameter in response to the update; a second programmable update interface (203) configured to update the parameter values associated with at least part of a set of configuration parameters on the basis of the filter values associated with said configuration parameters.