Vehicle Software Update Management via Server Manifest

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle computing systems require manual intervention for updating application files, which is inefficient and may not ensure timely updates, especially during regular maintenance or when diagnostic codes are set, necessitating the replacement of entire application files.

Innovation Solution

A system and method for wirelessly updating one or more application files in a vehicle computing system using a transceiver to communicate with a server, where a processor receives a file manifest, transmits a list of to-be-updated files, and flashes the files based on destination, installation type, and file identification, enabling remote management and transparency to the user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual intervention is required for updating application files, then system security and control are maintained, but update efficiency and timeliness deteriorate

Engineering Contradiction:
Improveupdate efficiencyVSAvoidmanual intervention requirement
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The vehicle computing system automatically detects its own software version, queries the server for update information, downloads updates, and installs them without requiring manual user intervention. The system serves itself by autonomously managing the entire update lifecycle from detection to installation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by automatically detecting software version mismatches before updates are needed, pre-querying the server for available updates, and preparing update files in advance. This ensures updates are ready and can be applied immediately when needed, improving timeliness.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If entire application files are replaced during maintenance, then system reliability is ensured, but maintenance time and complexity increase

Engineering Contradiction:
Improvesystem update reliabilityVSAvoidmaintenance time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of replacing entire application files, the system extracts and updates only the specific modules or components that require updates. The server provides selective update packages containing only the necessary changes, reducing the amount of data transferred and installed while maintaining reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies partial updates rather than complete replacements, updating only the specific application files or modules that have changed. This partial action approach reduces maintenance time and data handling requirements while still ensuring system reliability through targeted updates.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of time

If remote update capability is implemented, then update timeliness is improved, but system complexity and security requirements increase

Engineering Contradiction:
Improveupdate timelinessVSAvoidremote management system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

A server acts as an intermediary between the vehicle computing system and the update source. The server handles complex tasks such as version comparison, update package generation, and secure file transmission, while the vehicle system maintains relatively simple client-side functionality for querying and installing updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The server provides universal update management capabilities that can serve multiple vehicle systems simultaneously. It handles version detection, update generation, secure transmission, and installation coordination through a single multi-functional platform, reducing overall system complexity.

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

4Ease of operation

If wireless communication is used for updates, then ease of operation is improved, but data transmission security risks increase

Engineering Contradiction:
Improvewireless update operationVSAvoiddata transmission security risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system implements feedback mechanisms where the vehicle computing system sends version information to the server, receives confirmation of update receipt, and verifies installation completion. This feedback loop ensures secure and reliable updates while maintaining ease of operation through automated verification processes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system prepares for security risks by implementing pre-verification of update sources, using secure communication protocols before data transmission, and preparing rollback mechanisms in case of transmission failures or security issues. This beforehand cushioning protects against security risks while maintaining wireless update convenience.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS9436456B2System and method for management of software updates at a vehicle computing system
Publication Date: 2016.09.06 LIVIO INC
  • US9436456B2 patent drawing
  • US9436456B2 patent drawing
  • US9436456B2 patent drawing

AI summary

A vehicle software management system includes a transceiver configured to communicate information with a server, and a processor in communication with the transceiver. The processor may be configured to receive a file manifest from the server and transmit a list of to-be updated application file(s) based on the file manifest to the server. The processor may be further configured to receive one or more application files from the server based on the list. The processor may be further configured to flash one or more systems using the one or more application files based on at least one of destination file location, installation type, and file identification.