Method for identifying motor vehicle OBD (On-Board Diagnostic) added simulator

Abstract

The embodiment of the invention provides a method and a device for identifying a simulator additionally arranged at an OBD port of a motor vehicle, and the method comprises the steps: collecting CAN bus data, OBD vehicle detection data, ready state data, fault data, mileage data after a fault lamp is turned on, OBD data flow items supported by a vehicle, a vehicle identification code, an IUPR rate, an ECU name, an OBD model and a freezing frame in the motor vehicle; determining a plurality of early warning judgment results according to CAN bus data, OBD vehicle inspection data, ready state data, fault data, mileage data after a fault lamp is turned on, OBD data flow items supported by a vehicle, a vehicle identification code, an IUPR rate, an ECU name, an OBD model and a freezing frame; if the plurality of early warning judgment results are consistent, judging that the simulator is not additionally arranged at the OBD port of the motor vehicle; and if a different result appears in the plurality of early warning judgment results, judging the suspicion that the simulator is additionally arranged at the OBD port of the motor vehicle, and outputting a judgment basis. And the accuracy of detecting the OBD port of the motor vehicle is improved through a plurality of discrimination modes.

Description

Technical Field

[0001] This document relates to the field of motor vehicle emission detection, and in particular to a method, device and storage medium for identifying a motor vehicle OBD-installed simulator. Background Art

[0002] Motor vehicle OBD (On-Board Diagnostics) can record the vehicle's harmful gas emissions in real time, thereby reducing environmental pollution.

[0003] The existing technology mainly detects the CAL ID of a motor vehicle. The CAL ID is a unique identification code used by the vehicle manufacturer to calibrate the emission control software. When performing an OBD inspection, it ensures that the vehicle's CAL ID can be read correctly. If the read CALID is consistent with the judgment value during the inspection, it is determined that the vehicle is equipped with a simulator.

[0004] However, existing technology can modify the CAL ID by installing a simulator. After the modification, it will be impossible to judge, thereby affecting the detection effect, causing motor vehicles to exceed the emission standards of other harmful substances and seriously pollute the environment. Summary of the Invention

[0005] In view of the above solution, the present application aims to propose a method, device and storage medium for identifying a simulator installed at the OBD port of a motor vehicle, so as to solve at least one of the above technical problems.

[0006] In a first aspect, one or more embodiments of this specification provide a method for identifying a simulator installed in an OBD port of a motor vehicle, comprising:

[0007] Collect CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame in the motor vehicle;

[0008] Determine multiple early warning judgment results based on CAN bus data, OBD vehicle inspection data, readiness status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame;

[0009] If the multiple warning judgment results are consistent, it is determined that the vehicle OBD port is not equipped with a simulator; and

[0010] If a different result appears in multiple early warning judgment results, it is judged that there is a suspicion that a simulator is installed at the OBD port of the motor vehicle, and the judgment basis is output.

[0011] Furthermore, the CAN bus data represents a data format and protocol for communication between controllers;

[0012] Determine whether CAN bus data can be collected,

[0013] If CAN bus data can be collected, the simulator is not installed;

[0014] If the CAN bus data cannot be collected, the OBD vehicle inspection data is used to continue the judgment.

[0015] Further, it is determined whether the OBD vehicle inspection data contains multiple system response data or a single system response data,

[0016] If multiple system response data are included, the simulator is not installed;

[0017] If single system response data is included, identifying the readiness status of the single system;

[0018] Determine whether the readiness state of the single system is fully completed,

[0019] If all the ready items are not completed, the simulator is not installed;

[0020] If all the ready items are completed, there is suspicion of installing a simulator.

[0021] Further, the fault data and the mileage after the fault light is turned on are determined,

[0022] If the fault data and the mileage after the fault light turns on do not exist, it is determined that the simulator is not installed;

[0023] If the fault data and the mileage after the fault light comes on exist, it is determined that there is suspicion of the simulator being installed.

[0024] Further, it is determined whether the OBD data stream items supported by the vehicle can respond normally.

[0025] If it responds normally, the simulator is not installed;

[0026] If it fails to respond normally, it is suspected that a simulator has been installed.

[0027] Further, the vehicle identification code includes a vehicle identification number (VIN), a software calibration identification code (CALID), and a calibration verification code (CVN);

[0028] Determine whether the vehicle identification number (VIN), software calibration identification number (CALID), and calibration verification number (CVN) are consistent with preset values,

[0029] If it is inconsistent with the preset value, the simulator is not installed;

[0030] If it is consistent with the preset value, there is suspicion that a simulator has been installed.

[0031] Further, it is determined whether the IUPR rate can respond normally.

[0032] If it responds normally, the simulator is not installed;

[0033] If it fails to respond normally, it is suspected that a simulator has been installed.

[0034] Further, it is determined whether the ECU name is consistent with the preset name,

[0035] If they are consistent, the simulator is not installed;

[0036] If there is any inconsistency, there is a suspicion that a simulator has been installed.

[0037] Further, it is determined whether the OBD model is consistent with the preset model,

[0038] If they are consistent, the simulator is not installed;

[0039] If not, identifying the frozen frame;

[0040] Determine whether the freeze frame responds normally,

[0041] If it responds normally, the simulator is not installed;

[0042] If it fails to respond normally, it is suspected that a simulator has been installed.

[0043] In a second aspect, an embodiment of the present application provides a device for identifying a simulator installed in an OBD port of a motor vehicle, comprising:

[0044] The acquisition module is used to collect CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame in the motor vehicle;

[0045] The discrimination module is used to determine multiple warning judgment results based on CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame;

[0046] A first judgment module is configured to judge that the OBD port of the motor vehicle is not equipped with a simulator if multiple warning judgment results are consistent;

[0047] The second judgment module is used to judge that there is suspicion that a simulator is installed in the OBD port of the motor vehicle if a different result appears in the multiple warning judgment results, and output the judgment basis.

[0048] Compared with the existing technology, this application can at least achieve the following technical effects:

[0049] This application can use different judgment methods to obtain multiple early warning judgment results, so as to more accurately reflect whether the OBD port of the motor vehicle is equipped with a simulator, improve the accuracy of motor vehicle emission detection, and reduce the source of environmental pollution. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0051] Figure 1 A flow chart of a method for identifying a simulator installed in the OBD port of a motor vehicle provided in one or more embodiments of this specification;

[0052] Figure 2 A schematic diagram of the structure of a device for identifying a simulator installed at the OBD port of a motor vehicle provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0053] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0054] Currently, vehicle inspection agencies are using OBD simulators to cheat when conducting OBD tests. This seriously impacts the effectiveness of vehicle emissions testing, causing vehicles to emit excessive amounts of other harmful substances, severely polluting the environment. Vehicle exhaust emissions are a significant source of air pollution, yet news reports of cheating violations are constantly emerging in China.

[0055] In response to the above technical problems, this application proposes a method for identifying a simulator installed on the OBD port of a motor vehicle, such as Figure 1The specific steps are as follows:

[0056] Step S1, collecting CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame in the motor vehicle.

[0057] In the embodiments of this application, the CAN (Controller Area Network) bus is a high-speed communication network within the vehicle used to transmit data between various sensors and control units. A dedicated CAN bus data acquisition device is connected to the CAN bus via an OBD interface or a vehicle-specific diagnostic interface to collect and analyze data in real time. The OBD (On-Board Diagnostics) system is used to monitor the operating status of the vehicle's emission control system and other key systems. The vehicle's diagnostic information, including engine operating status and emission system status, is read through the OBD interface. Ready status refers to the status of various items in the vehicle's engine monitoring system. For example, the engine system monitors the vehicle's misfire, fuel system, integrated components, DOC (Diesel Oxidation Catalyst), SCR (Selective Catalytic Reduction), boost pressure system, exhaust gas sensors, DPF (Diesel Particulate Filter), Exhaust Gas Recirculation (EGR), and POC (Particulate Oxidation Catalyst). The system checks to see if data is returned. If data is returned, the test is complete. If not, the test is not applicable for this vehicle and is indicated as "Not Applicable." Fault data is generated by the OBD system when a component fault occurs during real-time monitoring of the vehicle's operating status. Post-malfunction mileage data indicates the vehicle's mileage since the malfunction indicator light (MIL) illuminated. The MIL status and related mileage data are read through the OBD system. The OBD data stream items supported by the vehicle indicate that the OBD data stream items supported by different vehicles may vary, including various sensor data, control unit status, etc.; the list of data stream items supported by the vehicle can be queried through the OBD system. The vehicle identification code includes the vehicle identification number (VIN), the software calibration identification code (CALID), and the calibration verification code (CVN). Among them, the VIN is used to identify and confirm vehicle information; the CALID is used to distinguish and identify the control unit inside the vehicle; and the CVN is a number calculated for all OBD (on-board diagnostic system) on-board diagnostic SWE (software, hardware, calibration, etc.) related to the ECU (engine control unit). It is mainly used to ensure that the vehicle's emission control system software has not been illegally tampered with, thereby ensuring that the vehicle's emission control system can work normally and meet relevant emission standards. The IUPR (In-Use Performance Ratio) rate is used to monitor the frequency of diagnostic function operation during normal use of the vehicle.The ECU name is the name of the electronic control unit (ECU), which identifies the computer module that controls various vehicle systems. ECU information is accessed through the OBD system or vehicle-specific diagnostic tools. The OBD model number is the version or model of the OBD system, indicating the emission standards and diagnostic protocols that the vehicle complies with. The OBD system is used to read vehicle information and determine the OBD system model or version. A freeze frame is a recording of vehicle status data at the time of a vehicle malfunction, including vehicle speed, engine speed, coolant temperature, and other information. The stored freeze frame data is accessed through the OBD system.

[0058] Step S2, determining multiple warning judgment results based on CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame.

[0059] In the embodiment of the present application, in order to prevent the installation of a simulator on the OBD port of a motor vehicle, thereby causing excessive exhaust emissions and affecting air quality, a variety of identification methods are used to detect the OBD port of the motor vehicle from different angles. The specific identification methods are as follows:

[0060] Judgment method 1: judge whether CAN bus data can be collected. If CAN bus data can be collected, the simulator is not installed; if CAN bus data cannot be collected, other judgment methods are used to continue judgment.

[0061] After the OBD monitoring terminal is plugged into the vehicle's OBD port, it begins collecting CAN bus data from the OBD port's multiple pins. If CAN bus data is collected, it can be considered that the OBD port is not equipped with a simulator under this judgment standard. If no CAN bus data is collected, it may be suspected and other methods need to be used for further judgment. This method can be upgraded and expanded. The OBD monitoring terminal can add a bus data detection mechanism to prevent simulator function upgrades from evading the OBD monitoring terminal's detection method.

[0062] Judgment method 2 is to determine whether the OBD vehicle inspection data contains multiple system response data or a single system response data. If it contains multiple system response data, the simulator is not installed; if it contains a single system response data, the ready state of the single system is identified; and whether the ready state of the single system is fully completed. If the ready items are not fully completed, the simulator is not installed; if the ready items are fully completed, there is a suspicion that a simulator is installed.

[0063] For example, OBD vehicle inspection data includes detection of the engine system, transmission system, and instrument system. How many system response data are there?

[0064] In case 1, if the OBD inspection data of a vehicle can only detect data from the engine system, it is necessary to further determine the status of each ready item in the engine system. If the values of all ready items are displayed as completed, it is suspected that the OBD port has been installed with a simulator under this judgment standard; otherwise, if some of the values are displayed as not applicable, it is determined that the OBD port has not been installed with a simulator under this judgment standard, as shown in Table 1;

[0065] Case 2: If the OBD vehicle inspection data of a vehicle detects engine system data, transmission system data and instrument system data, then under this judgment standard, it is directly judged that the OBD port has not been installed with a simulator.

[0066] Table 1 Ready state table

[0067]

[0068]

[0069] Judgment method 3 is to judge the fault data and the mileage after the fault light comes on. If the fault data and the mileage after the fault light comes on do not exist, it is judged that the simulator is not installed; if the fault data and the mileage after the fault light comes on exist, it is judged that there is suspicion of installing a simulator.

[0070] For example: read the motor vehicle fault data and the mileage after the fault light is on. If there is no current fault data and the fault mileage is 0, then under this judgment standard, it is judged that the OBD port has not been installed with a simulator; if there is fault data and the fault mileage is not 0, then it is judged that the motor vehicle OBD is suspected of having a simulator installed; if there are other situations, this judgment standard will not be counted in the subsequent results.

[0071] Judgment method 4 is to judge whether the OBD data stream items supported by the vehicle can respond normally. If they can respond normally, no simulator is installed; if they cannot respond normally, there is a suspicion that a simulator is installed.

[0072] Different motor vehicles have different supported OBD data stream items, but their OBD vehicle inspection data are fixed. Therefore, the OBD data stream items supported by the vehicle are composed of OBD vehicle inspection data and other OBD data items except the vehicle OBD annual inspection data stream. If the supported data stream items cannot respond normally or the data is abnormal, there is a suspicion that a simulator has been installed; otherwise, under this judgment standard, it is judged that the OBD port has not been installed with a simulator.

[0073] Judgment method 5 is to determine whether the vehicle identification code (VIN), software calibration identification code (CALID), and calibration verification code (CVN) are consistent with the preset values. If they are inconsistent with the preset values, the simulator is not installed; if they are consistent with the preset values, there is suspicion that a simulator has been installed.

[0074] In this application, if the VIN code is LSG (vehicles produced by Shanghai GM) and the CALID / CVN is at least 3 groups, then GM / Chevrolet vehicles of a certain model year or later are judged under this judgment standard to have no simulator installed in the OBD port. If the VIN code is LSG and the CALID / CVN is less than 3 groups, then GM / Chevrolet vehicles of a certain model year or later are suspected of having a simulator installed in the OBD port.

[0075] Judgment method 6 is to judge whether the IUPR rate can respond normally. If it can respond normally, the simulator is not installed; if it cannot respond normally, it is suspected that the simulator is installed.

[0076] In this application, when a vehicle's IUPR rate responds normally, meaning the OBD system is operating normally and is not subject to external interference (such as the installation of a simulator), and the IUPR rate can normally reflect the vehicle's performance status, then under this criterion, it is determined that the OBD port has not been installed with a simulator. When a vehicle's IUPR rate does not respond normally, meaning the OBD system has been interfered with or tampered with in some way, it is determined that the OBD port is suspected of having a simulator installed. The simulator is a device that can simulate OBD system signals, thereby achieving the purpose of deceiving emissions testing.

[0077] Judgment method 7 is to judge whether the ECU name is consistent with the preset name. If they are consistent, no simulator is installed; if they are inconsistent, there is a suspicion that a simulator is installed.

[0078] The motor vehicle OBD data supports reading the ECU name. If the ECU name starts with ECM, it is determined under this judgment standard that no simulator is installed in the OBD port, and the judgment ends. If the ECU name does not start with ECM, the motor vehicle OBD port is suspected of having a simulator installed.

[0079] Judgment method 8, judge whether the OBD model is consistent with the preset model, if consistent, the simulator is not installed; if inconsistent, identify the freeze frame; judge whether the freeze frame responds normally, if normal response, the simulator is not installed; if not normal response, there is suspicion of a simulator installed.

[0080] After the OBD monitoring terminal is inserted into the OBD port of a motor vehicle, it reads the OBD data of the motor vehicle. If the OBD model of a vehicle manufactured after 2019 is 0x29 / 0x2A / 0x2B, then under this judgment standard, it is judged that the OBD port is not equipped with a simulator. If the OBD model is not 0x29 / 0x2A / 0x2B, then the read freeze frame scan is judged to respond normally, and then the motor vehicle OBD port is not equipped with a simulator. If it cannot respond correctly, there is suspicion that a simulator is installed.

[0081] Step S3: If the multiple warning judgment results are consistent, it is determined that the OBD port of the motor vehicle is not equipped with a simulator.

[0082] In an embodiment of the present application, if the judgment results of CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame are all that the simulator is not installed, the final result is output that the vehicle is not equipped with a simulator.

[0083] Step S4: If a different result appears in the multiple warning judgment results, it is determined that there is a suspicion that a simulator is installed in the OBD port of the motor vehicle.

[0084] In an embodiment of the present application, if the output result of one of the judgment criteria among the CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame is suspected of installation, the final result is output that the vehicle is suspected of having a simulator installed, and the basis for the judgment is output.

[0085] For example, if the result of the CAN bus data indicates that a simulator is suspected to be installed, and the judgment results of other items are all that a simulator is not installed, then the final result is that the vehicle is suspected to have a simulator installed, and the judgment is based on the CAN bus data.

[0086] This application monitors various aspects of a motor vehicle, thereby being able to more accurately determine whether a motor vehicle is equipped with a simulator, and improves the accuracy of motor vehicle emission testing, reducing the sources of environmental pollution.

[0087] This application provides a device for identifying a simulator installed on the OBD port of a motor vehicle, such as Figure 2 Shown, including:

[0088] The acquisition module 101 is used to collect CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame in the motor vehicle;

[0089] The judgment module 102 is used to determine multiple warning judgment results based on CAN bus data, OBD vehicle inspection data, ready state data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame;

[0090] The first judgment module 103 is configured to judge that the OBD port of the motor vehicle is not equipped with a simulator if the multiple warning judgment results are consistent;

[0091] The second judgment module 104 is configured to judge that the OBD port of the motor vehicle is suspected of being equipped with a simulator if a different result appears in the multiple warning judgment results, and output a judgment basis.

[0092] An embodiment of the present application provides a storage medium for storing computer-executable instructions, characterized in that when the computer-executable instructions are executed, the steps of the method for identifying a simulator installed at the OBD port of a motor vehicle as described in any one of the above embodiments are implemented.

[0093] It should be noted that the embodiment of the storage medium in this specification and the embodiment of the blockchain-based service provision method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the corresponding blockchain-based service provision method mentioned above, and the repeated parts will not be repeated.

[0094] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0095] In the 1930s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0096] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

[0097] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0098] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0099] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0100] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0101] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0102] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0103] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0104] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0105] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0106] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0107] One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0108] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0109] The foregoing description is merely an example of the present invention and is not intended to limit the present invention. Persons skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims herein.

Claims

1. A method for identifying a simulator installed on an OBD port of a motor vehicle, characterized in that include: Collect CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame in the motor vehicle; Determine multiple early warning judgment results based on CAN bus data, OBD vehicle inspection data, readiness status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame; If the results of multiple warning judgments are consistent, it is determined that the vehicle's OBD port is not equipped with a simulator; as well as If a different result appears in multiple early warning judgment results, it is judged that there is a suspicion that a simulator is installed at the OBD port of the motor vehicle, and the judgment basis is output.

2. The method according to claim 1, characterized in that The method comprises: The CAN bus data represents a data format and protocol for communication between controllers; Determine whether CAN bus data can be collected, If CAN bus data can be collected, the simulator is not installed; and If the CAN bus data cannot be collected, the OBD vehicle inspection data is used to continue the judgment.

3. The method according to claim 1, characterized in that The method comprises: Determine whether the OBD vehicle inspection data contains multiple system response data or a single system response data, If multiple system response data are included, the simulator is not installed; If single system response data is included, identifying the readiness status of the single system; Determine whether the readiness state of the single system is fully completed, If the readiness items are not fully completed, the simulator is not installed; and If all the ready items are completed, there is suspicion of installing a simulator.

4. The method according to claim 1, characterized in that The method comprises: Determine the fault data and the mileage after the fault light turns on, If the fault data and the mileage after the fault light turns on do not exist, it is determined that the simulator is not installed; and If the fault data and the mileage after the fault light comes on exist, it is determined that there is suspicion of the simulator being installed.

5. The method according to claim 1, characterized in that The method comprises: Determine whether the OBD data stream items supported by the vehicle can respond normally, If it responds normally, then the simulator is not installed; and If it fails to respond normally, it is suspected that a simulator has been installed.

6. The method according to claim 1, characterized in that The method comprises: The vehicle identification code includes a vehicle identification number (VIN), a software calibration identification code (CALID), and a calibration verification code (CVN); Determine whether the vehicle identification number (VIN), software calibration identification number (CALID), and calibration verification number (CVN) are consistent with preset values, If it is inconsistent with the preset value, the simulator is not installed; and If it is consistent with the preset value, there is suspicion that a simulator has been installed.

7. The method according to claim 1, characterized in that The method comprises: Determine whether the IUPR rate can respond normally, If it responds normally, then the simulator is not installed; and If it fails to respond normally, it is suspected that a simulator has been installed.

8. The method according to claim 1, characterized in that The method comprises: Determine whether the ECU name is consistent with the preset name, If they match, then the simulator is not installed; and If there is any inconsistency, there is a suspicion that a simulator has been installed.

9. The method according to claim 1, characterized in that include: Determine whether the OBD model is consistent with the preset model, If they are consistent, the simulator is not installed; If not, identifying the frozen frame; Determine whether the freeze frame responds normally, If it responds normally, the simulator is not installed; as well as If it fails to respond normally, it is suspected that a simulator has been installed.

10. A device for identifying a simulator installed on an OBD port of a motor vehicle, characterized in that include: The acquisition module is used to collect CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame in the motor vehicle; The discrimination module is used to determine multiple warning judgment results based on CAN bus data, OBD vehicle inspection data, ready status data, fault data, mileage data after the fault light is on, OBD data stream items supported by the vehicle, vehicle identification code, IUPR rate, ECU name, OBD model and freeze frame; A first judgment module is configured to judge that the OBD port of the motor vehicle is not equipped with a simulator if multiple warning judgment results are consistent; as well as The second judgment module is used to judge that there is suspicion that a simulator is installed in the OBD port of the motor vehicle if a different result appears in the multiple warning judgment results, and output the judgment basis.

Images