Vehicle VM Software Verification Reuse for Startup Time Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing number of virtual machines (VMs) in vehicle control systems prolongs the startup time due to proportional verification time requirements for software authenticity, leading to inefficiencies in the verification process.
Innovation Solution
A vehicle control device that re-uses the verification result of common software among VMs, based on an assigned index, to shorten the verification duration, thereby reducing the time needed for authenticating multiple VMs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the number of VMs is increased to integrate more ECU functions, then the functional integration is improved, but the startup time increases proportionally due to repeated verification of common software
Solution Approach 1:
The verification of common software is performed in advance before VM startup. The verification result is stored and reused when VMs are started, eliminating the need to re-verify the same common software multiple times. This preliminary verification action resolves the contradiction by maintaining functional integration through multiple VMs while significantly reducing the cumulative verification time during startup.
2Reliability
If software verification is performed for each VM individually, then the authenticity verification is ensured, but the verification duration increases proportionally with the number of VMs
Solution Approach 1:
The common software verification process is designed to serve multiple VMs simultaneously. A single verification result of the common software is universally applied to authenticate multiple VMs that share this common software, rather than performing separate verifications for each VM. This universal verification approach maintains reliability by ensuring authenticity while dramatically improving verification efficiency by reducing redundant operations.
3Quantity of substance
If common software is shared among multiple VMs to save memory and shorten VM startup, then the memory usage is reduced, but the verification time increases due to repeated authentication requirements
Solution Approach 1:
The verification of common software is performed in advance and the result is cached. When VMs need to start up and share this common software, the pre-computed verification result is reused instead of performing repeated authentication. This preliminary verification action resolves the contradiction by maintaining memory efficiency through software sharing while eliminating the time penalty that would otherwise result from repeated verification of the same common software.
Data Source
AI summary
A vehicle control device includes a re-use determination section and a verification section. When the software of a virtual machine is to be verified, the re-use determination section decides, in accordance with an index assigned beforehand to the virtual machine, whether or not to re-use a verification result of common software that has been obtained in verification of the software of another virtual machine. When the re-use determination section decides to re-use the verification result of the common software obtained in the verification of the software of the other virtual machine, the verification section re-uses the verification result of the common software obtained in the verification of the software of the other virtual machine and verifies VM software of the virtual machine.