Vehicle Onboard Software Reset for Fast Tamper Mitigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for detecting and mitigating software manipulations in vehicles require significant time and can disrupt vehicle operation, necessitating improved techniques for rapid and secure correction of manipulated software.
Innovation Solution
A central device within the vehicle's onboard network detects software manipulations and initiates countermeasures using security and unalterable modules to reset compromised components, ensuring secure and efficient mitigation of software manipulations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software manipulation is detected and mitigated using existing methods (repair workshop reset or remote computer system reset), then the manipulation is corrected, but considerable time delays occur and vehicle operation may be interrupted
Solution Approach 1:
The patent stores authentic software components and security/unalterable modules within the vehicle's onboard network before manipulation occurs. When manipulation is detected, the system can immediately retrieve and restore the authentic software without external intervention, eliminating time delays associated with repair workshops or remote systems.
Solution Approach 2:
The patent introduces a central device as an intermediary that coordinates between detection devices, security modules, and software storage. This intermediary enables rapid automated response by managing the restoration process internally, avoiding the need for external repair systems and reducing mitigation time while maintaining software security.
2Reliability
If software manipulation is reset at a repair workshop or via remote system, then the manipulation is corrected, but the process requires external intervention and cannot be performed immediately
Solution Approach 1:
The patent enables the vehicle's onboard network to perform self-diagnosis and self-restoration of manipulated software. Detection devices identify manipulation, and the central device automatically retrieves authentic software from onboard storage and restores it using security modules, eliminating the need for repair workshop visits or remote system intervention.
Solution Approach 2:
The system pre-stores authentic software components and security modules within the vehicle before manipulation occurs. This preliminary preparation enables immediate self-restoration when manipulation is detected, providing both software integrity and operational ease without requiring external systems.
3Ease of manufacture
If standard modules are used for software reset, then the reset process is simple, but intruders may compromise the reset process
Solution Approach 1:
The patent differentiates between standard modules for simple operations and specialized security/unalterable modules for critical security functions. The security modules have enhanced protection against manipulation, while standard modules handle routine tasks. This local differentiation maintains overall system simplicity while securing the critical reset process against intruder compromise.
Solution Approach 2:
The system segments the software architecture into standard modules and dedicated security modules with distinct functions. The security modules are isolated and protected, handling only authentication and verification of the reset process, while standard modules handle general operations. This segmentation maintains ease of manufacture for standard functions while ensuring reset security through specialized protected modules.
Data Source
AI summary
A computer-implemented method for detecting the possibility of a manipulation of the software of a first component of a multiplicity of components of an onboard network of a vehicle in a central device for mitigating a manipulation of software. The central device for mitigating a manipulation is part of the onboard network and configured for the mitigation of software in each of the multiplicity of components of the onboard network. The method includes the initiation of a countermeasure for mitigating the manipulation of the software of the first component by the central device for mitigating a manipulation and the implementation of the countermeasure for mitigating the manipulation of the software of the first component. The countermeasure against the manipulation includes resetting the software of the first component using a security module of the first component and/or an unalterable module of the first component.


