Vehicle Unit Autonomous Software Installation via Segmented Data Packets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for diagnosing and configuring vehicle software via remote air interface are hindered by high latency and failure rates in mobile radio links, leading to costly and time-intensive recall actions, and lack flexibility in handling various diagnostic tasks such as error reading and ECU configuration.
Innovation Solution
A method involving a back end unit sending a data packet with orders and executable scripts to a vehicle unit via an air interface, where the vehicle unit evaluates and initiates the diagnosis or configuration, allowing for flexible remote-controlled operations and autonomous software installation without requiring a stable mobile radio link during writing, with logging and back documentation for fault analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If software is applied directly to the control device via mobile radio air interface, then remote software update is enabled, but high latency and failure times lead to high probability of faulty installation
Solution Approach 1:
The software update process is segmented into two distinct phases: (1) download phase where software is transferred via air interface to onboard storage, and (2) installation phase where software is autonomously written to control device. This segmentation allows the unreliable air interface to be used only for data transfer, while the critical installation occurs autonomously without requiring continuous communication.
Solution Approach 2:
The complete software package is downloaded and stored in the vehicle's onboard memory before the actual installation begins. This preliminary action ensures that all necessary data is available locally, eliminating the need for continuous air interface connection during the critical writing phase and allowing installation to proceed autonomously.
2Productivity
If diagnostic runtime scripts are used for vehicle component diagnosis, then standardized diagnostic procedures are enabled, but flexibility in handling various diagnostic tasks such as error reading and ECU configuration is limited
Solution Approach 1:
The system uses a universal data packet structure that can encapsulate multiple types of diagnostic and configuration tasks. The back end unit can send composite orders containing error reading commands, ECU configuration parameters, software updates, and test sequences all in a single standardized packet format, allowing one interface to handle diverse diagnostic functions.
Solution Approach 2:
The diagnostic script execution is made dynamic by allowing the vehicle control unit to autonomously evaluate received data packets and determine whether diagnosis or configuration should be undertaken. The system can adaptively select and execute different diagnostic routines based on vehicle state, error conditions, and configuration requirements, rather than following rigid predetermined sequences.
Data Source
AI summary
A method for the diagnosis and/or configuration of a vehicle includes sending, by a back end unit via an air interface to a vehicle unit, a data packet which comprises an order for the diagnosis and/or configuration of the vehicle, evaluating, by the vehicle unit, whether the diagnosis and/or a configuration of the vehicle is to be undertaken, and initiating, by the vehicle unit, the diagnosis and/or a configuration of the vehicle.