Dual Memory Vehicle Computing System for Seamless Software Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current vehicle software update processes require the vehicle to be inoperable and unattended, which is inconvenient for customers, as existing systems cannot update software without disabling the vehicle's electronics during the update process.

Innovation Solution

A vehicle computing system with two memory devices, where one is dedicated to vehicle operation and the other for software updates, allowing seamless switching between them, enabling software updates during vehicle operation without interrupting its functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the vehicle uses a single memory device for software updates, then the update process can be simple, but the vehicle must be inoperable during the update

Engineering Contradiction:
Improvememory device configurationVSAvoidvehicle operability during update
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The system divides the memory storage function into two separate memory devices: a first memory device for storing vehicle operation software and a second memory device for storing update software. This segmentation allows the vehicle to access different software sources independently, enabling updates without interrupting vehicle operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A switch circuit is introduced as an intermediary component that selectively connects the processor to either the first memory device or the second memory device. This mediator enables seamless transition between operational software and update software, maintaining vehicle functionality throughout the update process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of repair

If the vehicle is driven to a dealership for manual software updates, then the update can be performed with technician assistance, but the vehicle remains inoperable during the update process

Engineering Contradiction:
Improvesoftware update capabilityVSAvoidvehicle inoperable period
Core Design Contradiction:
Ease of repairVSLoss of time

Solution Approach 1:

The update software is pre-loaded into the second memory device before the update process begins. This preliminary preparation allows the vehicle to execute updates autonomously without requiring technician presence or vehicle transport to a dealership, eliminating downtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The vehicle's processor can autonomously execute the update process by switching to the second memory device and running the update software without external assistance. This self-service capability eliminates the need for dealership visits and technician intervention, allowing updates to be performed at the user's convenience.

Inventive Principle:
Principle #25Self-service

3Loss of information

If the system manually applies software updates and records changes, then the update process can be tracked, but the process requires technician intervention and vehicle inoperability

Engineering Contradiction:
Improveupdate tracking capabilityVSAvoidupdate application process
Core Design Contradiction:
Loss of informationVSExtent of automation

Solution Approach 1:

The system incorporates a notification mechanism that automatically informs the processor when update software is available in the second memory device. This feedback loop enables the system to autonomously manage the update process, eliminating the need for manual tracking and technician intervention while maintaining full update history.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10282194B2Methods and systems to update a vehicle computing system
Publication Date: 2019.05.07 FORD GLOBAL TECH LLC
  • US10282194B2 patent drawing
  • US10282194B2 patent drawing
  • US10282194B2 patent drawing

AI summary

A vehicle computing system for a vehicle includes a first and second memory device (e.g., erasable programmable read only memory (EEPROM)). The system further includes a circuit that selectively switches between the first and second memory device. The system further includes a first vehicle control module configured to receive notification that a software update is available at the second memory device. The first vehicle control module controls the circuit to switch from the first memory device to the second memory device at an initialization event. The first vehicle control module executes the software update based on communication with the second memory device.