ECU Processing Anomaly Detection for Low-Downtime Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating Electronic Control Unit (ECU) software in vehicles are inefficient, requiring significant memory and downtime, and often introduce bugs or are costly, especially when dealing with differential updates or rolling back software versions without reprogramming memory.
Innovation Solution
The use of delta files and a virtual file system to manage and track ECU software versions, allowing for efficient updates and rollbacks by updating memory addresses and variables without interrupting ECU operations, and utilizing an orchestrator for anomaly detection and control actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional ECU software update methods are used, then software can be updated, but significant memory space is required and downtime is needed
Solution Approach 1:
The patent segments the software update process into multiple components: delta files containing only the differences between software versions, virtual file system layers, and incremental update packages. This segmentation allows updates to be applied without requiring the entire software image in memory simultaneously, reducing peak memory requirements while maintaining update reliability
2Reliability
If traditional ECU software update methods are used, then software can be updated, but significant downtime is required
Solution Approach 1:
The patent implements preliminary actions by downloading and validating delta files before the actual update execution, preparing the virtual file system in advance, and staging update packages in buffer memory. This preliminary preparation allows the actual update application to proceed quickly with minimal downtime, as the heavy lifting of data preparation is completed beforehand
Solution Approach 2:
The patent enables continuous operation during updates by implementing a dual-layer virtual file system where the old software version remains accessible while the new version is being applied. This allows the ECU to maintain functional continuity, processing requests and executing critical functions even during the software transition, thereby minimizing perceived downtime
3Reliability
If OBD ports are used for fixes, then vulnerabilities can be addressed, but attack surfaces are increased
Solution Approach 1:
The patent extracts the software update functionality from traditional OBD port dependencies by implementing over-the-air update capabilities through wireless communication modules. This extraction removes the physical OBD port interface from the update pathway, eliminating it as an attack surface while preserving the ability to receive and apply vulnerability fixes remotely
4Ease of operation
If over-the-air fixes are used, then convenience is improved, but bugs may be introduced and efficiency is reduced
Solution Approach 1:
The patent implements comprehensive feedback mechanisms including pre-update validation of delta files against the current software version, post-update verification that the new version was correctly applied, and rollback capabilities if validation fails. This feedback loop ensures update integrity and prevents buggy versions from being deployed, maintaining reliability while preserving over-the-air convenience
Data Source
AI summary
Disclosed embodiments relate to identifying Electronic Control Unit (ECU) anomalies in a vehicle. Operations may include monitoring, in the vehicle, data representing real-time processing activity of the ECU; accessing, in the vehicle, historical data relating to processing activity of the ECU, the historical data representing expected processing activity of the ECU; comparing, in the vehicle, the real-time processing activity data with the historical data, to identify at least one anomaly in the real-time processing activity of the ECU; and implementing a control action for the ECU when the at least one anomaly is identified.