Intra-Vehicle OTA Updates via Peer Vehicles for ECU Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern vehicles face challenges in managing the complexity and frequency of software updates for their electronic control units (ECUs), particularly due to limited network connectivity and the need for frequent, secure, and efficient updates without relying heavily on cloud-based systems.

Innovation Solution

Utilizing network connections between vehicles to transfer ECU software updates, with compatibility checks and minimal cloud-based communication, allowing for secure and efficient updates through vehicle-to-vehicle communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cloud-based systems are used for ECU software updates, then update security and reliability are improved, but network connectivity requirements increase and system complexity worsens

Engineering Contradiction:
Improveupdate securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a peer vehicle as an intermediary node that stores and distributes update files. Instead of directly connecting to complex cloud-based systems, vehicles use neighboring vehicles as intermediaries to exchange update information, thereby reducing dependency on cloud infrastructure while maintaining secure updates through peer verification mechanisms

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Vehicles perform self-update operations by autonomously detecting available updates, verifying their integrity, and installing them without requiring continuous cloud-based system involvement. The system enables vehicles to service themselves by using their own resources and peer vehicles to complete the update process independently

Inventive Principle:
Principle #25Self-service

2Reliability

If frequent ECU updates are performed, then operational reliability is improved, but network connectivity demands increase

Engineering Contradiction:
Improveoperational reliabilityVSAvoidnetwork connectivity
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Update files are prepared, verified, and cached in advance on peer vehicles before actual installation is needed. This preliminary preparation allows vehicles to perform updates frequently without real-time network connectivity, as the update content is already available in the peer vehicle's storage memory

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of continuously downloading update information from remote cloud sources, vehicles create local copies of update files through peer-to-peer transfers. This copying mechanism enables frequent updates by utilizing locally available update data stored in the memory of peer vehicles, significantly reducing ongoing network connectivity requirements

Inventive Principle:
Principle #26Copying

3Reliability

If traditional update methods are used, then update security is maintained, but service disruption increases and customer convenience worsens

Engineering Contradiction:
Improveupdate securityVSAvoidcustomer convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system eliminates the need for customers to visit dealers or experience intrusive recall processes by enabling vehicles to update themselves autonomously. The peer-to-peer update mechanism allows updates to occur automatically in the background, improving customer convenience while maintaining security through peer verification and integrity checking

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Update verification and compatibility checks are performed in advance before installation occurs. This preliminary verification ensures that updates are safe to install, allowing the system to proceed with updates confidently without requiring manual customer intervention or creating service disruptions, thereby improving both security and convenience

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12436756B2Intra-vehicle over-the-air updates
Publication Date: 2025.10.07 RED HAT LLC
  • US12436756B2 patent drawing
  • US12436756B2 patent drawing
  • US12436756B2 patent drawing

AI summary

A method of managing applications of a first vehicle includes establishing, by the first vehicle, a network with a second vehicle in proximity to the first vehicle, receiving, by the first vehicle from the second vehicle over the network, application metadata associated with a plurality of applications executing on the second vehicle, based on the application metadata, transmitting a list to the second vehicle over the network, wherein the list identifies one or more application updates associated with the plurality of applications, and receiving the one or more application updates from the second vehicle over the network.