Vehicle Configuration Update Engine for Consistent Parameter Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of efficiently updating configuration files in vehicles to address changes made by user entities, ensuring consistent application without errors, especially when large quantities of changes are involved, is not adequately addressed by existing technologies.

Innovation Solution

A configuration update engine applies update configuration files in a specified order, validating changes and ensuring consistency by using configuration schema information, thereby generating final configuration parameters for vehicle processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual updating of configuration files is performed, then flexibility in making changes is improved, but time consumption and error rate increase when large quantities of changes are involved

Engineering Contradiction:
Improveflexibility in making changesVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses templates to define configuration parameters and their valid values. Instead of manually updating each configuration file individually, the system copies template definitions across multiple configuration files, ensuring consistency and reducing manual effort when large quantities of changes are needed.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system allows configuration parameters to be defined once in templates and then dynamically instantiated across multiple configuration files. Changes to parameters can be propagated systematically through the configuration hierarchy, reducing time consumption while maintaining flexibility.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If manual updating of configuration files is performed, then flexibility in making changes is improved, but error rate increases when large quantities of changes are involved

Engineering Contradiction:
Improveflexibility in making changesVSAvoiderror rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

By copying template definitions across configuration files, the system ensures that changes are applied consistently throughout the configuration hierarchy, reducing the risk of errors that would occur with manual updates.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system validates configuration parameters against defined templates and schemas, providing feedback mechanisms that detect errors automatically. This validation process ensures that changes conform to expected formats and constraints, reducing error rates.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If configuration files are updated without systematic validation, then ease of updating is improved, but consistency and reliability deteriorate

Engineering Contradiction:
Improveease of updatingVSAvoidconsistency
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary validation by defining templates and schemas before configuration files are updated. This preliminary structure ensures that updates maintain consistency and reliability while remaining easy to perform, as the validation rules are already in place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Automatic validation provides feedback on whether configuration updates are consistent with defined templates and schemas. This feedback mechanism maintains reliability and consistency without making the updating process difficult.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4582938A1Configuration information changes
Publication Date: 2025.07.09 BLACKBERRY LTD
  • EP4582938A1 patent drawingFigure 1
  • EP4582938A1 patent drawingFigure 2
  • EP4582938A1 patent drawingFigure 3

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.