Vehicle Module Configuration Update Detection and Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicle telematics systems face challenges in updating vehicle software and firmware configurations, as user-implemented or dealer-implemented updates often go unrecorded, leading to updates based on outdated information, resulting in potential errors.
Innovation Solution
A system that includes a processor to detect module updates, create identifiers for updated modules, and request subscription to specific topics on a remote server, ensuring the backend system is aware of the current configuration and can provide accurate future updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user-implemented or dealer-implemented updates are performed, then the vehicle module functionality is improved, but the backend system loses track of the current configuration
Solution Approach 1:
The system implements a feedback mechanism where the vehicle module automatically reports update status and configuration changes to the backend system. After an update is performed, the module detects the configuration change and sends this information back to the backend, ensuring the backend maintains accurate knowledge of the current vehicle state without requiring manual reporting.
Solution Approach 2:
The vehicle module performs self-service by automatically detecting its own configuration changes and reporting them to the backend system. This eliminates the need for manual intervention or external tracking, as the module itself monitors and communicates its updated state, ensuring the backend receives accurate configuration information.
2Extent of automation
If OTA updates are used, then the update process is automated, but the backend system cannot verify updates performed outside OTA channels
Solution Approach 1:
The system dynamically adapts to different update sources (OTA, user-implemented, dealer-implemented) by implementing a universal detection mechanism. Rather than having separate verification processes for each update type, the system uses a dynamic approach where the module detects configuration changes regardless of the update source and reports them uniformly to the backend, ensuring reliable verification across all automation channels.
3Ease of manufacture
If the backend system creates updates based on outdated configuration information, then update development is simplified, but update errors occur
Solution Approach 1:
The system performs preliminary action by having the vehicle module detect and report configuration changes to the backend system before update development begins. This ensures the backend receives current configuration information in advance, allowing update developers to create accurate updates without having to guess the current vehicle state, thereby improving both ease of manufacture and configuration accuracy.
Data Source
AI summary
A system includes a processor configured to detect that a vehicle module update has been performed. The processor is further configured to create an identifier associated with a module that indicates an updated status and for each module having an identifier indicating an updated status associated therewith, requesting subscription to a topic, corresponding to the updated module, and specific to an individual vehicle, from a remote server.