Vehicle ECU Software Updating With Real-Time Compliance Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software update procedures for vehicles are prone to human error, cybersecurity threats, and cannot validate compliance with automotive regulations in real-time, especially when the vehicle is not at a repair shop.
Innovation Solution
A method and device that utilize diagnostic equipment to evaluate vehicle compliance with automotive regulations by comparing vehicle type and status databases, performing secure software updates, and ensuring integrity verification through electronic signatures, even when the vehicle is in operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual software update procedures are performed at repair shops, then software updates can be applied to vehicles, but human error may cause incorrect software versions to be installed and cybersecurity threats may compromise update integrity
Solution Approach 1:
The vehicle's execution controllers autonomously perform software updates by receiving update packages, verifying electronic signatures, and installing updates without requiring manual intervention from mechanics. The management controller coordinates this self-service process, enabling the vehicle to update its own software securely and reliably
Solution Approach 2:
Electronic signatures serve as an intermediary verification mechanism between the software update source and the vehicle's control systems. The management controller verifies these signatures to ensure update authenticity and integrity, acting as a mediator that prevents unauthorized or corrupted software from being installed
2Reliability
If software updates are performed manually at repair shops, then compliance with automotive regulations can be maintained, but validation is only possible when the vehicle is at the repair shop and not during operation
Solution Approach 1:
The compliance validation system transitions from a static, repair-shop-only model to a dynamic model where the management controller continuously monitors and validates software versions and regulatory compliance while the vehicle is in operation. This enables real-time compliance assurance regardless of the vehicle's location
Solution Approach 2:
The management controller continuously collects software version information from execution controllers and compares it against regulatory requirements, providing ongoing feedback on compliance status. This feedback mechanism enables real-time validation and alerting without requiring the vehicle to be at a repair shop
3Measurement precision
If comprehensive database comparisons are performed to evaluate regulatory compliance, then accurate compliance determination is achieved, but processing time and computational resources increase
Solution Approach 1:
The compliance evaluation process is segmented into two levels: execution controllers independently verify their own software versions against regulatory requirements, and the management controller performs a secondary determination by comparing results from multiple execution controllers. This segmentation distributes computational workload and reduces centralized processing time
Solution Approach 2:
Execution controllers perform preliminary compliance checks by comparing their software versions against regulatory requirements before submitting results to the management controller. This preliminary action filters and pre-processes data, reducing the computational burden on the management controller and accelerating overall compliance evaluation
Data Source
AI summary
Provided are a method and device for evaluating whether an individual vehicle is in compliance with automotive regulations. The method of evaluating whether an individual vehicle is in compliance with automotive regulations includes, based on confirming a connection to a vehicle, collecting, from a management controller, a primary determination result on whether the vehicle is in compliance with automotive regulations, comparing a version of a vehicle type database collected from the management controller, with a version of a master database, to determine whether the versions are identical to each other, and generating a secondary determination result on whether the vehicle is in compliance with the automotive regulations, based on the primary determination result and a determination result on whether the version of the vehicle type database and the version of the master database are identical to each other.