ECU Processing Anomaly Detection for Low-Downtime Software Rollback
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 additional bugs or vulnerabilities.
Innovation Solution
The use of non-transitory computer readable media and methods that monitor real-time and historical ECU processing activity to identify anomalies, and implement control actions such as software version adjustments using delta files, without requiring significant memory or downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional ECU software update methods are used (distributing entire software packages), then software updates can be provided to vehicles, but significant memory space is required and update time is increased
Solution Approach 1:
The patent extracts and transmits only the differential portions (delta files) of software updates rather than entire ECU software packages. This extraction approach reduces the data volume from megabytes to kilobytes, significantly decreasing memory space requirements and transmission time while maintaining complete software functionality.
Solution Approach 2:
The software update process is segmented into identifying specific changed portions and transmitting only those segments. The system divides the update into minimal necessary changes (delta files) that can be applied to the existing software, avoiding transmission of unchanged code sections.
2Reliability
If traditional ECU software update methods are used (erasing current version and copying replacement), then software updates can be installed, but ECU downtime occurs and update complexity increases
Solution Approach 1:
The patent performs preliminary actions by receiving and storing delta files in available memory space before they are needed for application. This preliminary preparation eliminates the need for urgent memory management during actual updates and allows updates to be applied immediately without downtime when ready.
Solution Approach 2:
The system enables continuous ECU operation during the update process by applying delta files in memory without erasing current software or requiring system shutdown. The ECU maintains uninterrupted useful action throughout the update, eliminating traditional downtime periods.
3Reliability
If traditional ECU software update methods are used (storing replacement package in spare memory), then software updates can be installed, but significant memory management overhead is required
Solution Approach 1:
The patent extracts only the essential update information (delta files) from complete software packages, removing the need for complex memory management of large replacement packages. This extraction reduces memory management from handling entire software images to managing minimal differential data.
Solution Approach 2:
Instead of copying entire software packages to spare memory, the system copies only minimal delta files to available memory space. This selective copying approach dramatically reduces memory management overhead and eliminates the need for extensive spare memory allocation.
4Ease of operation
If OBD ports are used for ECU updates, then software fixes can be provided, but security vulnerabilities are introduced
Solution Approach 1:
The patent extracts the update functionality from traditional OBD port communication and implements it through the existing delta file infrastructure. This extraction eliminates the need for additional update interfaces that would expand the attack surface, maintaining security while preserving update accessibility.
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.