Vehicle Unit Remote Configuration via Network Entity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current vehicle unit configurations, such as tachographs, are inefficient and time-consuming to update, especially when it comes to keeping devices compliant with changing legislation, as they require manual updates at workshops and do not allow for simultaneous configuration of multiple vehicles.

Innovation Solution

Enabling vehicle units to communicate with a network entity for sharing and updating configuration information, allowing remote reconfiguration of vehicle units, including tachographs, which can transmit and receive configuration settings, recording frequencies, and user preferences, thereby facilitating centralized management and simultaneous updates across a fleet.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If vehicle units are configured manually at workshops, then configuration accuracy is ensured, but configuration time and operational efficiency deteriorate

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements configuration templates that store standardized vehicle unit settings. These templates can be copied and applied to multiple vehicle units simultaneously, ensuring configuration accuracy through template validation while dramatically reducing configuration time. The system maintains configuration integrity by using pre-validated templates that can be reused across the fleet.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent pre-configures vehicle unit settings in templates before actual deployment. Configuration parameters, validation rules, and compliance settings are prepared in advance, allowing rapid deployment to multiple vehicles without manual configuration at the time of vehicle commissioning or updates.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If vehicle units are updated individually at workshops, then update reliability is maintained, but fleet management efficiency and productivity deteriorate

Engineering Contradiction:
Improveupdate reliabilityVSAvoidfleet management efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent combines multiple vehicle unit configurations into a single centralized management system. Configuration templates and update packages are created once and can be deployed to multiple vehicle units simultaneously through the network, maintaining reliability through centralized validation while dramatically improving fleet management productivity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal configuration templates that can be applied across different vehicle units in the fleet. A single template can serve multiple vehicles, and the system provides both individual vehicle configuration capabilities and fleet-wide bulk configuration capabilities, making the system adaptable to various management needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Device complexity

If configuration updates require physical workshop visits, then configuration control is maintained, but operational flexibility and adaptability deteriorate

Engineering Contradiction:
Improveconfiguration controlVSAvoidoperational flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a network server as an intermediary between fleet managers and vehicle units. This intermediary maintains configuration control through centralized authentication and validation while enabling flexible remote updates. The server acts as a gatekeeper that ensures configuration integrity while allowing adaptable deployment across the fleet without physical workshop visits.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical process of physical workshop visits with electronic communication through networks. Configuration updates are transmitted digitally to vehicle units, eliminating the need for physical presence at workshops while maintaining security and control through encrypted communication and authenticated access.

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

4Adaptability or versatility

If multiple vehicle units require separate configuration, then individual vehicle requirements are met, but time consumption and operational efficiency deteriorate

Engineering Contradiction:
Improveindividual vehicle requirementsVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments configuration management into two levels: fleet-wide common parameters defined in templates, and vehicle-specific parameters that can be customized. This segmentation allows bulk configuration of common settings to meet individual requirements efficiently, while still permitting vehicle-specific customizations when needed, significantly reducing overall configuration time.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4488967A1Vehicle unit configuration
Publication Date: 2025.01.08 STONERIDGE ELECTRONICS
  • EP4488967A1 patent drawingFigure 1a~1b
  • EP4488967A1 patent drawingFigure 2
  • EP4488967A1 patent drawingFigure 3

AI summary

Described is among other things a method performed by a vehicle unit (10), the vehicle unit (10) is communicatively connected to a network entity (20), the method comprises transmitting (202) configuration information of the vehicle unit (10) to the network entity (20).