Remote ECU Software Reflashing via Wireless Telematics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software update methods for vehicle electronic control units (ECUs) are inconvenient for owners, costly for manufacturers, and can result in sub-optimal vehicle performance due to compatibility issues between ECUs, as they require physical visits to dealerships and manual updating processes.

Innovation Solution

A method and system for remote reflashing of ECU software using a mobile vehicle communication system, which identifies vehicle groups, prepares and transmits software update packages wirelessly to telematics devices, and installs the updates in target ECUs, ensuring compatibility and reducing the need for physical visits.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If software updates are performed through physical dealership visits, then software can be updated, but owner convenience deteriorates and manufacturer costs increase

Engineering Contradiction:
Improvesoftware update convenienceVSAvoidtime and effort for vehicle visits
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent replaces the mechanical/physical system of dealership visits with a wireless communication system. Software updates are transmitted electronically to vehicles through cellular networks, eliminating the need for physical transportation of vehicles to dealerships. This substitution of mechanical processes with electronic/digital processes directly resolves the contradiction by improving convenience while reducing time loss.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables vehicles to receive software updates automatically without requiring owner intervention or dealership involvement. The vehicle's onboard communication system receives update packages wirelessly and performs self-updating, allowing the vehicle to service itself remotely. This self-service capability eliminates the need for owner time and effort while maintaining update functionality.

Inventive Principle:
Principle #25Self-service

2Ease of manufacture

If software updates are performed manually at dealerships, then updates can be installed, but manufacturer reimbursement expenses increase

Engineering Contradiction:
Improveupdate installation capabilityVSAvoidmanufacturer reimbursement cost
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The patent replaces the manual dealership update process with an automated wireless update system. Instead of dealers physically installing updates using specialized equipment, the system uses electronic transmission through cellular networks to deliver software packages directly to vehicles. This substitution eliminates the need for dealership infrastructure and manufacturer reimbursement, maintaining update capability while reducing costs.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent extracts the software update function from the dealership environment and transfers it to the vehicle's onboard system. By removing the dependency on dealership facilities and personnel, the system eliminates the cost component while preserving the essential update installation capability. The update process is extracted from the service center context and embedded in the vehicle's own communication and control systems.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If ECUs are updated individually, then specific ECU software can be updated, but compatibility issues with other ECUs arise

Engineering Contradiction:
ImproveECU software version flexibilityVSAvoidECU compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent merges the update process for multiple ECUs into a single coordinated operation. The system identifies all ECUs requiring updates and transmits a comprehensive software package that includes updates for multiple ECUs simultaneously. This merging of update operations ensures that all ECUs are updated to compatible versions together, maintaining system reliability while preserving the flexibility to update specific ECUs as needed.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system employs feedback mechanisms to monitor ECU software versions and compatibility requirements. Before executing updates, the system checks the current state of all ECUs and determines the appropriate update sequence and package contents. This feedback loop ensures that updates are applied in a manner that maintains compatibility across all ECUs, resolving the contradiction between version flexibility and compatibility reliability.

Inventive Principle:
Principle #23Feedback

4Productivity

If replacement ECU software is not synchronized with other ECUs, then replacement can proceed quickly, but vehicle performance deteriorates

Engineering Contradiction:
ImproveECU replacement speedVSAvoidvehicle performance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary identification and preparation of software packages for all ECUs before the replacement process begins. By pre-determining the required software versions and preparing comprehensive update packages in advance, the system ensures that compatibility is established before physical replacement occurs. This preliminary action enables quick replacement while guaranteeing that the new ECU will be compatible with other system components, maintaining both productivity and reliability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7366589B2Method and system for remote reflash
Publication Date: 2008.04.29 GENERAL MOTORS LLC
  • US7366589B2 patent drawing
  • US7366589B2 patent drawing
  • US7366589B2 patent drawing

AI summary

A system and method for remote reflashing of software for electronic control units (ECUs). A method includes identifying vehicle groups for software updating 200, determining vehicles within the vehicle groups, each of the vehicles having a telematics device and a plurality of ECUs 202, preparing a software update package for each of the vehicles 204, transmitting the software update package over a wireless carrier system to the telematics device of each of the vehicles 206, and installing the software update package in at least one target ECU for each of the vehicles 208.