Vehicle ECU Software Updates Using Delta Files and Safe Mode Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating Electronic Control Unit (ECU) software in vehicles are inefficient, requiring significant memory, causing downtime, and introducing additional bugs, especially when updating entire software modules over-the-air, and lack efficient mechanisms for differential updates, anomaly detection, and managing dependencies between ECUs.
Innovation Solution
The system opportunistically updates ECU software by delaying updates until safe operational conditions are met, using delta files to transmit only the necessary changes, and employing a virtual file system to manage and track software versions without requiring significant memory or downtime, while also enabling rollback to previous versions without reprogramming.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entire ECU software modules are updated over-the-air, then software vulnerabilities can be fixed, but significant memory space is required and additional bugs may be introduced
Solution Approach 1:
The patent segments the ECU software update process into separate components: the main ECU software remains intact in primary memory, while only the necessary update patches (delta files) are transmitted and stored in secondary memory. This segmentation allows vulnerability fixes without requiring the entire software module to be replaced, thereby reducing memory space requirements.
Solution Approach 2:
The patent extracts only the essential update content (delta files) from the complete ECU software package. By transmitting and applying only the differential changes rather than the entire software module, the system fixes vulnerabilities while minimizing the quantity of data that must be stored and processed, thus reducing memory space requirements.
2Reliability
If entire ECU software modules are updated over-the-air, then software vulnerabilities can be fixed, but update efficiency is reduced and downtime increases
Solution Approach 1:
The update process is segmented into independent stages: delta file reception, validation, staged application, and verification. This segmentation allows the update process to be more efficient and flexible, enabling partial updates without requiring complete software replacement, thereby improving update efficiency and reducing downtime.
Solution Approach 2:
The patent implements preliminary validation and testing of delta files before applying them to the running ECU software. By performing these preparatory actions in advance and using staged application processes, the system ensures update reliability while minimizing the time the ECU is non-operational, thus improving overall update efficiency.
3Duration of action of moving object
If ECU software is updated while operating, then continuous operation is maintained, but update safety is compromised
Solution Approach 1:
The patent introduces a virtual file system as an intermediary layer between the incoming delta files and the running ECU software. This intermediary provides a safe environment for validating, staging, and managing update content before it is applied to the operational software, thereby maintaining both continuous operation and update safety through isolated processing.
Solution Approach 2:
The patent implements beforehand cushioning by creating a virtual file system buffer that stores and validates delta files before they are applied to the running ECU software. This preparatory buffering allows validation and error checking to occur in advance, preventing unsafe updates from compromising the operating system while maintaining continuous operation.
4Quantity of substance
If differential updates are implemented, then memory usage is reduced, but mechanisms for managing dependencies between ECUs are required
Solution Approach 1:
The virtual file system is designed as a universal platform that handles multiple functions: storing delta files, validating updates, managing dependencies between different ECU software components, and coordinating updates across multiple ECUs. This multi-functional approach manages the complexity of dependency tracking while maintaining reduced memory usage through differential updates.
Data Source
AI summary
Disclosed embodiments relate to opportunistically updating Electronic Control Unit (ECU) software in a vehicle. Operations may include receiving, at a controller in a vehicle, a wireless transmission indicating a need to update software running on at least one ECU in the vehicle; monitoring an operational status of the vehicle to determine whether the vehicle is in a first mode of operation in which an ECU software update is prohibited; delaying the ECU software update when the operational status is prohibited; continuing to monitor the operational status of the vehicle to determine whether the vehicle is in a second mode of operation in which the ECU software update is permitted; and enabling updating of the at least one ECU with the delayed ECU software update when it is determined that the vehicle is in the second mode of operations.