In-Vehicle Software Updates Using Shared Packages and Vehicle Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing software updating systems for in-vehicle terminals require significant server processing load and storage capacity due to the need for individual software updates for each vehicle, leading to inefficiencies and increased resource utilization.

Innovation Solution

A software updating system that divides update data into common packages shared among multiple vehicles and identification packages containing vehicle-specific information, allowing vehicles to authenticate and retrieve the correct update data efficiently, thereby reducing server load and storage requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If individual software updates are prepared for each vehicle, then the software can be customized for specific vehicle requirements, but the server processing load and storage capacity are significantly increased

Engineering Contradiction:
Improvesoftware customizationVSAvoidstorage capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The software update package is segmented into two distinct components: a common package containing software common to multiple vehicles, and an identification package containing vehicle-specific identification information. This segmentation allows the server to store one copy of the common software package that can serve multiple vehicles, while only storing minimal vehicle-specific identification data, thereby significantly reducing the storage capacity required compared to storing complete individualized update packages for each vehicle.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The common package is designed to be universal and can be used by multiple vehicles that share the same software requirements. By making the software package multi-functional and applicable to several vehicles simultaneously, the system eliminates the need to store duplicate copies of the same software for different vehicles, thus reducing overall storage requirements while maintaining the ability to provide customized updates through the identification package.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If individual software updates are prepared for each vehicle, then the software can be customized for specific vehicle requirements, but the server processing load is significantly increased

Engineering Contradiction:
Improvesoftware customizationVSAvoidserver processing load
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The update process is segmented into two distinct phases: first, the server transmits only the small identification package to the terminal device, which contains vehicle-specific identification information; second, the terminal device uses this identification information to retrieve the appropriate common package from its local storage or request it from the server. This segmentation reduces the server's processing load during the initial transmission phase, as the server only needs to handle small identification data rather than large individualized software packages for each vehicle.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-storing common software packages on the server or in a accessible location. When a vehicle needs an update, the server first transmits the identification package that contains the key information needed to access the pre-prepared common package. This preliminary transmission of identification information allows the actual software update to be efficiently retrieved and applied without requiring the server to process and transmit complete individualized packages for each vehicle in real-time, thereby reducing server processing load.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If complete individualized update packages are transmitted to each vehicle, then the software update can be performed accurately for each vehicle, but the data transmission volume and storage requirements are increased

Engineering Contradiction:
Improveupdate accuracyVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The update data is segmented into an identification package containing vehicle-specific identification information and a common package containing the actual software update. The identification package is transmitted to the terminal device, which then uses this information to accurately retrieve and apply the appropriate common package. This segmentation ensures update accuracy by matching vehicles with their correct software updates through the identification information, while minimizing data transmission volume by only transmitting the small identification package rather than complete individualized packages for each vehicle.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12436753B2Software updating device, in-vehicle terminal, and software updating system
Publication Date: 2025.10.07 NISSAN MOTOR CO LTD
  • US12436753B2 patent drawing
  • US12436753B2 patent drawing
  • US12436753B2 patent drawing

AI summary

A software updating device includes a controller and a storage device. The software updating device uses software update data of a vehicle for updating the software. The storage device stores a common package including at least the update data, and an identification package including common package identification information assigned to the common package and vehicle identification information that is associated with the common package identification information and that identifies the vehicle. The controller transmits, to a target vehicle subject to software update, the identification package including the vehicle identification information associated with the target vehicle, and transmits, to the target vehicle in accordance with a request from the target vehicle, the common package to which is assigned the common package identification information included in the identification package.