Vehicle Configuration Update Engine for Validated File Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of efficiently and accurately updating configuration files in vehicles to address changes made by user entities, ensuring consistency and preventing errors, particularly when large quantities of changes are involved.

Innovation Solution

The use of update configuration files applied in a specified order by a configuration update engine, which validates and applies changes to an initial configuration file, including modifications, insertions, and deletions, to produce final configuration parameters without altering the original file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If update configuration files are applied manually to initial configuration files, then configuration changes can be made, but the process becomes tedious and time-consuming with large quantities of changes

Engineering Contradiction:
Improveconfiguration update efficiencyVSAvoidtime to apply changes
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically detecting changes between configuration files and generating update configuration files in advance. The configuration update engine pre-processes the differences and prepares the update package, so that when deployment is needed, the changes are already prepared and can be applied efficiently without manual intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary configuration update engine that mediates between the initial configuration file and the updated configuration file. This engine automatically generates update configuration files that capture the differences, serving as an intermediary representation that can be efficiently applied to update systems without requiring manual comparison and modification of numerous configuration parameters.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If manual updates are performed on configuration files, then changes can be applied, but errors may occur when large quantities of changes are involved

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidupdate accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The configuration update engine implements feedback by automatically detecting changes, generating update configuration files, and validating the updates. The system provides feedback loops that verify the correctness of configuration changes, ensuring that updates are applied accurately without manual errors. The engine can detect inconsistencies and prevent erroneous updates from being applied.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-service by automatically generating update configuration files without requiring manual intervention. The configuration update engine autonomously compares configuration files, identifies changes, and creates the necessary update packages, eliminating human error in the update process while maintaining flexibility in configuration management.

Inventive Principle:
Principle #25Self-service

3Productivity

If the original configuration file is modified directly, then updates can be applied, but the original file is altered and consistency is lost

Engineering Contradiction:
Improveupdate application speedVSAvoidconfiguration file consistency
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The patent uses copying by creating update configuration files that represent the differences between configurations, rather than directly modifying the original configuration file. The update configuration file is a copy or representation of the changes that can be applied to generate the updated configuration, preserving the original file's integrity while enabling efficient updates.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The configuration update process is segmented into separate components: the original configuration file, the update configuration file (containing only the changes), and the final updated configuration file. This segmentation allows the original file to remain unchanged and consistent while enabling efficient application of updates through the separate update configuration file.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250224966A1Configuration information changes
Publication Date: 2025.07.10 BLACKBERRY LTD
  • US20250224966A1 patent drawing
  • US20250224966A1 patent drawing
  • US20250224966A1 patent drawing

AI summary

In some examples, a system reads a first configuration file comprising a first configuration parameter that affects an execution of a process in a vehicle, and determines whether any update configuration file is present by checking for a storage location having an identifier based on a property of the first configuration file, the update configuration file comprising an entry specifying a change for the first configuration file. The system applies the update configuration file to the first configuration file to determine configuration parameters to apply for the process when executed in the vehicle.