Vehicle ECU Delta Updates for Low-Memory Coordinated Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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 dealing with differential updates and managing dependencies between ECUs.

Innovation Solution

A system that uses delta files to update ECU software remotely, allowing for incremental updates without requiring entire software package downloads, utilizing a virtual file system to manage and track versions, and coordinating updates across ECUs to minimize disruptions and memory usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional ECU software update methods are used, then complete software packages can be updated, but significant memory space is required and downtime occurs

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoidmemory space required
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The software update process is segmented into multiple components: delta files containing only the differences between software versions, rather than requiring complete software package downloads. This segmentation reduces memory requirements from storing entire software images to storing only incremental difference data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and transmits only the essential update information (delta files) from the complete software package, separating the update mechanism from the full software image. This extraction approach allows updates to be applied without requiring the full software package to be present in memory simultaneously.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If traditional ECU software update methods are used, then complete software packages can be updated, but downtime occurs during the update process

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoidECU downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Delta files are generated and prepared in advance before the update process begins. The update mechanism is pre-configured with the difference data needed, allowing the actual update application to proceed quickly without requiring time-consuming complete package transfers or complex installation sequences.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update process is designed to maintain continuous operation where possible, with delta file application occurring in a manner that minimizes interruption to the ECU's useful functions. The incremental nature of delta updates allows for more efficient processing compared to complete package installations.

Inventive Principle:
Principle #20Continuity of useful action

3Ease of manufacture

If traditional ECU software update methods are used, then updates can be applied, but additional bugs may be introduced

Engineering Contradiction:
Improveupdate application easeVSAvoidsoftware stability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system incorporates feedback mechanisms to verify the integrity and correct application of delta files. By tracking update states and validating delta file application, the system can detect and prevent buggy updates from being applied, providing feedback loops that ensure update reliability before completing the update process.

Inventive Principle:
Principle #23Feedback

4Quantity of substance

If delta files are used for updates, then memory requirements are reduced, but coordination between ECUs becomes more complex

Engineering Contradiction:
Improvememory space requiredVSAvoidupdate coordination complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

An intermediary update management system is introduced to coordinate delta file distribution and application across multiple ECUs. This intermediary layer handles the complexity of dependency resolution and coordination, shielding individual ECU update processes from the full complexity of system-wide update management while enabling efficient memory usage through delta files.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12169710B2Self-healing learning system for one or more controllers
Publication Date: 2024.12.17 AURORA LABS LTD
  • US12169710B2 patent drawing
  • US12169710B2 patent drawing
  • US12169710B2 patent drawing

AI summary

Disclosed embodiments relate to automatically providing updates to at least one vehicle. Operations may include receiving, at a server remote from the at least one vehicle, Electronic Control Unit (ECU) activity data from the at least one vehicle, the ECU activity data corresponding to actual operation of the ECU in the at least one vehicle; determining, at the server and based on the ECU activity data, a software vulnerability affecting the at least one vehicle, the software vulnerability being determined based on a deviation between the received ECU activity data and expected ECU activity data; identifying, at the server, an ECU software update based on the determined software vulnerability; and sending, from the server, a delta file configured to update software on the ECU with a software update corresponding to the identified ECU software update.