Method and device for intercepting malicious behavior of obd equipment
A technology of equipment and behavior, applied in the field of vehicle information security, can solve problems such as hidden dangers of vehicles, and achieve the effect of ensuring safety
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0027] Embodiment 1: a kind of method of intercepting OBD equipment malicious behavior, comprising:
[0028] S1. Monitor the OBD data in the OBD device diagnostic protocol that reflects the action behavior of the OBD device;
[0029] S2. When the OBD data is acquired, execute step S3;
[0030] S3. Reply the error code (0x7F) corresponding to the OBD data of the OBD device. For example, the command to remotely control the car window rise is 0x31 0xB9 0x02. The hardware that intercepts the malicious behavior of the OBD device immediately returns 0x7F 0x31 0x11, and the OBD device receives the error code , then it is determined that the action behavior of the OBD device reflected by the OBD data is invalid, and the operation of the vehicle is stopped. And upload the interception record to APP or cloud platform.
Embodiment 2
[0031] Embodiment 2: have the technical scheme identical with embodiment 1, more specifically: wherein: described OBD data is in the OBD data of the diagnosis agreement of CAN application layer (ISO14229) and the diagnosis agreement of K application layer (ISO14230) At least one of: electronic control unit reset (0x11), security entry (0x27), write data by identifier (0x2E); write memory by address (0x3D), clear diagnostic information (0x14), remote control (0x31).
Embodiment 3
[0032] Embodiment 3: have the technical scheme identical with embodiment 1 or 2, more specifically: when obtaining this OBD data, first perform the following steps,
[0033] Store the OBD data and notify the user that the action is about to be executed;
[0034] The user judges whether the action can be executed, and if it is judged to be executable, the stored OBD data is sent to the vehicle for execution; if it is judged to be unexecutable, step S3 is executed. This step makes it possible to provide the user with an operation interface when the real OBD acts maliciously, to prevent malicious modification of the user's vehicle; to ensure the safety of the vehicle bus, and to prevent the "paralysis" of the vehicle ECU due to incorrect operation.
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


