Vehicle DTC Authentication via Identity Marker Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method for storing diagnostic trouble codes (DTCs) in motor vehicle systems loses consistency between volatile and nonvolatile memory when powered down, making it susceptible to hacker attacks and manipulation of fault information.
Innovation Solution
A method that generates a diagnostic trouble code and an identity marker using a fault detection algorithm, stores them as an authentication data record in nonvolatile memory, and authenticates the code upon ignition using the stored identity marker and fault detection algorithm to detect any manipulation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If diagnostic trouble codes are stored in nonvolatile memory after ignition off, then fault information is preserved across power cycles, but consistency and integrity of the stored data cannot be guaranteed against manipulation
Solution Approach 1:
The patent applies preliminary action by generating and storing an identity marker in nonvolatile memory before the ignition is switched off. This identity marker serves as a reference that will later be used to authenticate the diagnostic trouble codes. By preparing the authentication mechanism in advance, the system ensures that when DTCs are loaded back into volatile memory after ignition on, their integrity can be verified against the pre-stored identity marker, thus preventing manipulation while maintaining fault information across power cycles.
Solution Approach 2:
The patent implements feedback by comparing the fault detection algorithm with the stored identity marker to authenticate the diagnostic trouble code. This closed-loop verification process provides feedback on whether the DTC has been manipulated or altered. If the comparison fails, the system can detect the manipulation and take appropriate corrective action, thereby maintaining data integrity while preserving fault information across ignition cycles.
2Adaptability or versatility
If fault detection algorithms are updated or modified, then diagnostic capabilities improve, but existing stored diagnostic trouble codes may no longer be authenticatable
Solution Approach 1:
The system performs preliminary action by capturing and storing the specific version of the fault detection algorithm as an identity marker at the moment the diagnostic trouble code is generated. This creates a timestamped snapshot of the algorithm state. When the system is later updated with a new or modified fault detection algorithm, previously stored DTCs can still be authenticated against their original algorithm version, while new DTCs will use the updated algorithm. This allows continuous diagnostic capability improvement without compromising the authentication validity of historical data.
3Object-affected harmful factors
If volatile memory is erased after ignition off, then security is improved by preventing access to fault information, but the ability to diagnose faults after restart is lost
Solution Approach 1:
The patent extracts the critical authentication element (identity marker) from the volatile memory and stores it separately in nonvolatile memory before the volatile memory is erased. This separation allows the volatile memory to be securely erased after ignition off, preventing hackers from accessing fault information in volatile memory. Meanwhile, the identity marker preserved in nonvolatile memory enables authentication of DTCs when they are reloaded after ignition on, thus maintaining both security and diagnostic capability.
Data Source
AI summary
A method for authenticating at least one diagnostic trouble code (DTC) generated by a motor vehicle system of a vehicle. The method generates a DTC by a fault detection algorithm, stores the DTC in a volatile fault memory, generates an identity marker denoting the fault detection algorithm at the time of generation of the DTC, stores the identity marker in NVM, stores the DTC in the NVM when an ignition-off request signal is present, loads the DTC from the NVM into the volatile memory when an ignition-on request signal is present, and authenticates the DTC by the authentication data record by, initially by determining the fault detection algorithm by which the fault event was detected, subsequently this fault detection algorithm being compared with the fault detection algorithm indicated by the identity marker, and an absence of concordance resulting in a manipulation of the DTC being indicated.