Decentralized Transport Software Update Propagation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software update management for transports is inefficient and insecure, relying on centralized systems that lack comprehensive testing and secure propagation mechanisms.

Innovation Solution

A decentralized method for software updates in transports, involving validation based on usage time and number of utilizations, propagation to larger subsets of transports, and secure distribution using blockchain technology.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software updates are distributed through a centralized server using WAN, then software updates can be delivered to transports, but the system becomes inefficient and insecure

Engineering Contradiction:
Improvesecurity of software update distributionVSAvoidefficiency of software update distribution
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the centralized update distribution system into multiple decentralized transport nodes that can independently validate and propagate updates. Each transport acts as both a receiver and a distributor, breaking the monopoly of the central server and creating a distributed network architecture that improves both security through diversity and efficiency through parallel propagation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces transport nodes as intermediaries between the central server and the broader transport network. These intermediary transports receive updates from the server, validate them locally, and then propagate them to other transports in their vicinity, creating a multi-hop distribution chain that reduces direct WAN dependency while maintaining security through layered validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If software updates are sent to all transports immediately, then updates are distributed quickly, but insufficient testing occurs before wide propagation

Engineering Contradiction:
Improvespeed of software update distributionVSAvoidadequacy of software update testing
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by requiring transport nodes to validate and test software updates before propagating them to the broader network. Each transport acts as a staging point where updates are verified for compatibility and security issues before being released to the next tier of transports, ensuring thorough testing precedes wide distribution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies dynamics by creating a tiered propagation system where the speed and scope of update distribution are dynamically adjusted based on validation results. Updates that pass initial testing can propagate faster to larger subsets, while those requiring further validation are held back, creating a dynamic, adaptive distribution pace that balances speed with thoroughness.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If a centralized system collects information from millions of transports, then comprehensive data is gathered, but the system lacks security and efficiency

Engineering Contradiction:
Improvecompleteness of software update information collectionVSAvoidsecurity of information collection
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent implements self-service by enabling transport nodes to autonomously collect, validate, and propagate software update information without requiring centralized coordination for each interaction. Each transport maintains local records of updates it has received and propagated, and can independently verify the authenticity of updates from peer transports, reducing the security risks associated with centralized data collection while maintaining information completeness through distributed recording.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250190211A1Management of transport software updates
Publication Date: 2025.06.12 TOYOTA MOTOR NORTH AMERICA INC
  • US20250190211A1 patent drawing
  • US20250190211A1 patent drawing
  • US20250190211A1 patent drawing

AI summary

An example operation may include one or more of receiving a software update at a transport of a subset of transports, validating the software update based on one or more of: a period of time when the software update is in use, and a number of utilizations of the software update by the subset of the transports, propagating the software update based on the validating, to a further subset of transports, wherein the further subset of the transports is larger than the subset of the transports.