Vehicle ECU Reconfiguration Using Cloud-Based Touch Files

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional vehicle embedded software is static and difficult to update, leading to delayed feature introductions, lost revenue opportunities, and interoperability issues with proprietary platforms being expensive and error-prone manual changes.

Innovation Solution

A dynamically configurable software platform using touch files that allow real-time behavior changes without manual configuration, enabling remote updates and standardization across models and manufacturers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional static embedded software is used in ECUs, then system stability is maintained, but the ability to update features and adapt to market trends is severely limited

Engineering Contradiction:

Improveability to update featuresVSAvoiddevelopment and testing cycles

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent transforms static embedded software into a dynamic system by introducing a configuration management mechanism that allows runtime reconfiguration of ECU behavior through external configuration files and cloud-based updates, enabling the system to adapt to changing market trends without lengthy development cycles

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent separates the core embedded software from configurable parameters by using external configuration files that define software behavior. This segmentation allows the configuration layer to be updated independently from the core software, enabling rapid feature updates without full firmware re deployment

Inventive Principle:

Principle #1Segmentation

2Productivity

If periodic firmware updates are implemented, then new features can be introduced, but long development and testing cycles cause delayed feature introductions and lost revenue

Engineering Contradiction:

Improvefeature introduction speedVSAvoiddevelopment and testing cycles

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent prepares multiple configuration files in advance that define different software behaviors and features. These pre-prepared configurations can be rapidly deployed without extensive testing cycles, as the core software remains unchanged and only configuration parameters need validation

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses configuration files that can be copied and distributed rapidly across multiple ECUs. Instead of updating core firmware, the system copies new configuration files to ECUs, enabling fast feature propagation across the vehicle fleet

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If manual configuration changes are employed, then flexibility is achieved, but the process is error prone and does not scale well

Engineering Contradiction:

Improveconfiguration flexibilityVSAvoiderror rate

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements automated configuration management where the system itself handles configuration updates, validation, and deployment without manual intervention. The ECU automatically retrieves and applies new configuration files from the cloud, eliminating human error while maintaining flexibility

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent incorporates validation mechanisms that provide feedback during configuration updates. The system validates configuration files before application and can roll back changes if validation fails, ensuring reliability while maintaining automated flexibility

Inventive Principle:

Principle #23Feedback

4Adaptability or versatility

If proprietary platforms are developed for more flexibility, then adaptability improves, but the platforms are expensive to build and maintain with interoperability issues

Engineering Contradiction:

Improveplatform flexibilityVSAvoidplatform cost and maintenance

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal configuration management architecture that can work with standard embedded systems without requiring proprietary platforms. The configuration file format and update mechanism are platform-agnostic, enabling multi-functionality across different ECU types and manufacturers while reducing complexity and cost

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20260064399A1System and method to dynamically reconfigure vehicle software using touch files

Publication Date: 2026.03.05 FCA US LLC

AI summary

A method for dynamically configuring a software platform for a vehicle associated with an original equipment manufacturer (OEM) includes providing an electronic control unit (ECU) of the vehicle, establishing a cloud-based network configured to store a plurality of touch files, each touch file defining a set of vehicle configuration parameters, accessing, by the ECU, the cloud-based network to update and store the plurality of touch files, receiving and storing, by the ECU, a software code, wherein the software code identifies a particular touch file of the plurality of touch files, and executing, by the ECU, the software code using the set of vehicle configuration parameters specified by the particular touch file. Each touch file can be an empty file created using a Linux touch command and having a unique or distinct filename that is specified by the software code.