System, Method and Storage Medium for Preventing Illegal Flashing of Commercial Vehicle Diagnostic Instruments

Abstract

The present invention relates to the technical fields of vehicle fault diagnosis and vehicle information security, and particularly relates to a system, method and storage medium for preventing illegal flashing of a commercial vehicle diagnostic instrument. A user obtains a passing variable code and inputs the passing variable code into the diagnostic instrument; a security algorithm interface compares the passing variable code input by the user with the passing variable code predefined in the security algorithm interface; if the passing variable codes are consistent, the diagnostic instrument is allowed to execute subsequent flashing processes; otherwise, subsequent operations of the diagnostic instrument are prohibited. By defining a passing variable to be verified in the security algorithm interface, identity verification before flashing is realized, illegal flashing of the commercial vehicle diagnostic instrument caused by illegal acquisition of the security algorithm interface is prevented, and the safety of the vehicle is improved.

Description

Technical Field

[0001] The present invention relates to the technical fields of vehicle fault diagnosis and vehicle information security, and particularly relates to a system, a method and a storage medium for preventing illegal flashing of a commercial vehicle diagnostic instrument. Background Art

[0002] At present in China, the flashing function of commercial vehicle diagnostic instruments is easily cracked by external manufacturers. Flashing of in-vehicle controllers requires the corresponding controller's security algorithm, the corresponding flashing file, and the UDS flashing process. The security algorithm is provided in the form of a DLL. The flashing file is provided in forms such as AES, S19, HEX, etc. In terms of the flashing process, it can be obtained through the UDS diagnostic protocol and the flashing LOG.

[0003] Regarding information security during the flashing process, service 27 of UDS is adopted, and its security is relatively weak. There is a possibility that the flashing file can be obtained. There is also a possibility that the security algorithm can be obtained. After the crackers obtain the UDS flashing process, the flashing file, and the security algorithm at the same time, they can simulate the diagnostic instrument to perform flashing.

[0004] As Figure 1 shown, in the prior art, when the diagnostic instrument IDS flashes the corresponding controller, it calls the security algorithm DLL. Since the security algorithm DLL has no security measures, when the security algorithm DLL itself is obtained, the diagnostic instrument can perform subsequent operations, resulting in illegal flashing of the vehicle diagnostic instrument. Summary of the Invention

[0005] The purpose of the present invention is to address the deficiencies of the prior art, and provide a system, a method and a storage medium for preventing illegal flashing of a commercial vehicle diagnostic instrument. By defining a passing variable to be verified within the security algorithm interface, identity verification before flashing is achieved, preventing illegal flashing of the commercial vehicle diagnostic instrument caused by illegal acquisition of the security algorithm interface, and improving the security of the vehicle.

[0006] The present invention provides a method for preventing illegal flashing of a commercial vehicle diagnostic instrument, including the following steps:

[0007] The user obtains a passing variable code and inputs the passing variable code into the diagnostic instrument;

[0008] The security algorithm interface compares the passing variable code input by the user with the passing variable code predefined within the security algorithm interface;

[0009] If the passing variable codes are the same, the diagnostic instrument is allowed to execute the subsequent flashing process; otherwise, the subsequent operations of the diagnostic instrument are prohibited.

[0010] Preferably, the way for the user to obtain the passing variable code is:

[0011] The user logs in to the after-sales service system through an account and password, and obtains a passing variable code from within the after-sales service system.

[0012] More preferably, the passing variable code is a dynamically changing variable code.

[0013] More preferably, the interface definition of the security algorithm is implemented by a security algorithm interface in the form of a DLL file, and a passing variable code to be verified is predefined within the security algorithm interface.

[0014] More preferably, the passing variable code is the 27-service passing variable defined in the interface definition of the security algorithm within the diagnostic instrument.

[0015] The present invention also provides a system for preventing illegal flashing of a commercial vehicle diagnostic instrument, including

[0016] A diagnostic instrument software module, integrated within the diagnostic instrument, for allowing a user to input a passing variable code and for implementing data flashing of the diagnostic instrument after the passing variable code passes verification;

[0017] A security algorithm module, integrated within the DLL security algorithm interface, for comparing the passing variable code input by the user with the predefined passing variable code to implement verification of the passing variable code;

[0018] An after-sales service system platform module, for providing a passing variable code to the user or the DLL security algorithm interface.

[0019] More preferably, the diagnostic instrument software module includes:

[0020] A data flashing module, for implementing data flashing of the diagnostic instrument, and for jumping to the passing variable input module when the flashing process reaches service 27, and for jumping to the security algorithm interface definition module after obtaining the passing variable;

[0021] A security algorithm interface definition module, for defining a passing variable and sending the defined passing variable to the security algorithm module, and the defined passing variable is obtained from the after-sales service system platform module;

[0022] A passing variable input module, for providing a UI interface for the user to input a passing variable code and for sending the passing variable code input by the user to the security algorithm module.

[0023] More preferably, after the verification of the passing variable code is completed, the DLL security algorithm interface feeds back a status code to the diagnostic instrument, and the diagnostic instrument determines whether the verification has passed through the status code. If the verification fails, subsequent operations of the diagnostic instrument are prohibited.

[0024] More preferably, after receiving the account number and password input by the user, the after-sales service system platform module feeds back a dynamic access variable code to the user.

[0025] The present invention also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the steps of the method described above are implemented.

[0026] The beneficial effects of the present invention are as follows: Before a user uses the function of the diagnostic instrument to brush the controller, the user needs to log in to the after-sales service system (CRM), and obtain a dynamic and variable access variable code in the system according to the type of controller to be brushed. Before the diagnostic instrument software brushes the corresponding controller, the access variable obtained in the after-sales service system (CRM) needs to be input on the UI interface of the diagnostic instrument. In addition, this access variable code is also implanted in the security algorithm of the corresponding controller. The security algorithm can obtain this access variable code in real time from the after-sales service system (CRM) by itself. If the access variable input by the user on the UI interface of the diagnostic instrument is consistent with the access variable code obtained by the security algorithm in real time from the after-sales service system (CRM) by itself, the diagnostic instrument can perform the next operation. This invention protects the security algorithm itself, solves the problem that external manufacturers could brush the controller at will after obtaining the corresponding security algorithm of the controller before, and improves the safety of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a schematic diagram of internal data interaction of the prior art;

[0028] Figure 2 It is a schematic diagram of the method flow of the present invention;

[0029] Figure 3 It is a schematic diagram of the system connection principle of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0030] In order to make the technical problems, technical solutions and beneficial effects to be solved by the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0031] In the following description, specific details such as specific system structures and technologies are proposed for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the present application can also be implemented in other embodiments without these specific details. In other cases, the detailed descriptions of well-known systems, devices, circuits and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0032] It should be understood that when used in the specification of this application and the appended claims, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or their combinations.

[0033] It should also be understood that the term "and / or" used in the specification of this application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0034] As used in the specification of this application and the appended claims, the term "if" may be construed, depending on the context, as "when", "once", "in response to determining", or "in response to detecting". Similarly, the phrase "if determined" or "if [the described condition or event] is detected" may be construed, depending on the context, as meaning "once determined", "in response to determining", "once [the described condition or event] is detected", or "in response to detecting [the described condition or event]".

[0035] In addition, in the description of the specification of this application and the appended claims, the terms "first", "second", "third", etc. are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0036] Reference to "one embodiment" or "some embodiments" etc. described in the specification of this application means that a particular feature, structure, or characteristic described in connection with that embodiment is included in one or more embodiments of this application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "comprising", "including", "having", and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways. "Plurality" means "two or more".

[0037] Embodiment 1

[0038] Figure 2 The flowchart shows a method for preventing illegal flashing of a commercial vehicle diagnostic instrument provided by a preferred embodiment of this application. For the sake of convenience of description, only the parts related to this embodiment are shown and are described in detail as follows:

[0039] The present invention provides a method for preventing illegal flashing of a commercial vehicle diagnostic instrument, including the following steps:

[0040] Step 1, the user obtains a passing variable code;

[0041] Step 2, the user inputs the access variable code into the diagnostic instrument;

[0042] Step 3, the security algorithm interface compares the access variable code input by the user with the access variable code predefined in the security algorithm interface. If the access variable codes are the same, the diagnostic instrument is allowed to execute the subsequent flashing process; otherwise, the subsequent operations of the diagnostic instrument are prohibited.

[0043] In one embodiment, in Step 1, the way for the user to obtain the access variable code is:

[0044] The user logs in to the after-sales service system through the account number and password, and obtains the access variable code from the after-sales service system.

[0045] In one embodiment, the access variable code is a dynamically changing variable code.

[0046] In one embodiment, the interface definition of the security algorithm is implemented by a security algorithm interface in the form of a DLL file, and a predefined access variable code to be verified is in the security algorithm interface.

[0047] In one embodiment, the access variable code is the 27 service access variable defined in the interface definition of the security algorithm in the diagnostic instrument.

[0048] In this embodiment, the implementation of the security algorithm by the diagnostic instrument requires the interface definition of the security algorithm in the diagnostic instrument software, the implementation of the security algorithm interface in the form of a DLL file, and the 27 services of UDS implemented in the diagnostic instrument software;

[0049] A 27 service access variable is defined in the interface definition of the security algorithm in the diagnostic instrument software. When the controller performs flashing and reaches the 27 services of UDS, when implemented using the security algorithm interface in the form of a DLL file, it is necessary to check the 27 service access variable defined in the interface definition of the security algorithm in the diagnostic instrument software. Only when the check is successful can the security algorithm pass; otherwise, it is regarded as a failure of the security algorithm to pass.

[0050] A 27 service access variable is defined in the interface definition of the security algorithm in the diagnostic instrument software. This variable needs to be input by the user in the corresponding controller interface of the diagnostic instrument software. The user needs to obtain the corresponding variable through his own account password on the after-sales service system platform, and this variable changes dynamically. In the implementation of the security algorithm interface in the form of a DLL file, the consistency between the variable (input by the user) defined in the interface definition of the security algorithm in the diagnostic instrument software and the variable provided on the after-sales service system platform is checked. If they are the same, the next step of flashing can be carried out; otherwise, the next step of flashing cannot be carried out.

[0051] The implementation of the safety algorithm for the diagnostic instrument requires the interface definition of the safety algorithm in the diagnostic instrument software, the implementation of the safety algorithm interface in the form of a DLL file, and the 27 services of UDS implemented in the diagnostic instrument software, including:

[0052] According to the UDS flashing process, when the diagnostic instrument reaches the 27 service in the flashing process, the 27 service needs to be implemented with the safety algorithm interface in the form of a DLL file. The diagnostic instrument calls the DLL through the interface definition of the safety algorithm in the diagnostic instrument software.

[0053] Define a variable in the interface definition of the safety algorithm in the diagnostic instrument software. When the controller performs flashing and reaches the 27 service of UDS, when using the safety algorithm interface implemented in the form of a DLL file, it is necessary to check the variable defined in the interface definition of the safety algorithm in the diagnostic instrument software. Only when the check is successful can the safety algorithm pass, otherwise it is regarded as a failure of the safety algorithm to pass; Define a variable in the interface definition of the safety algorithm in the diagnostic instrument software. This variable needs to be input by the user on the corresponding controller interface of the diagnostic instrument software. The user needs to obtain the corresponding variable through their own account password on the after-sales service system platform, and this variable changes dynamically. Check the consistency between the variable defined (user input) in the interface definition of the safety algorithm in the diagnostic instrument software and the variable provided on the after-sales service system platform in the implementation of the safety algorithm interface in the form of a DLL file. If they are consistent, the next step of flashing can be carried out, otherwise the next step of flashing cannot be carried out. Including:

[0054] A variable defined in the interface definition of the safety algorithm in the diagnostic instrument software can be manually input on the corresponding controller interface of the diagnostic instrument software after the corresponding controller of the diagnostic instrument is successfully connected.

[0055] The above variable can be obtained by the diagnostic instrument user by logging in with their account password on the after-sales service system platform, and this variable changes dynamically.

[0056] Only when the variable manually input on the corresponding controller interface of the diagnostic instrument software is consistent with the variable obtained by the DLL from the after-sales service system platform, will the 27 service be carried out in the UDS flashing process.

[0057] Embodiment 2

[0058] Figure 3 The flowchart of a method for preventing illegal flashing of a commercial vehicle diagnostic instrument provided by a preferred embodiment of the present application is shown. For the sake of convenience of description, only the parts related to this embodiment are shown and are described in detail as follows:

[0059] A system for preventing illegal flashing of a commercial vehicle diagnostic instrument includes

[0060] The diagnostic instrument software module, integrated within the diagnostic instrument, is used for the user to input a passing variable code and to perform data flashing of the diagnostic instrument after the passing variable code passes the verification;

[0061] The security algorithm module, integrated within the DLL security algorithm interface, is used to compare the passing variable code input by the user with a predefined passing variable code to achieve the verification of the passing variable code;

[0062] The after-sales service system platform module is used to provide the passing variable code to the user or the DLL security algorithm interface.

[0063] Preferably, the diagnostic instrument software module includes:

[0064] The data flashing module is used to perform data flashing of the diagnostic instrument, and when the flashing process reaches service 27, it jumps to the passing variable input module, and after obtaining the passing variable, it jumps to the security algorithm interface definition module;

[0065] When the data flashing module reaches service 27, it will jump to the security algorithm interface definition module, thereby calling the security algorithm interface in the form of a DLL file to implement. Before calling the security algorithm interface in the form of a DLL file to implement, it will enter the passing variable input module for service 27. After verification, it will call the security algorithm interface in the form of a DLL file to implement, and then continue to complete the remaining process of the data flashing module.

[0066] The security algorithm interface definition module is used to define a passing variable and send the defined passing variable to the security algorithm module. The defined passing variable is obtained from the after-sales service system platform module; since the DLL is obtained by the outside world, now in order to enable the DLL to still be used normally when it is obtained, so before the diagnostic instrument hardware identifies the vehicle-mounted controller, a judgment logic is pre-set to judge whether the user is an authorized user. This pre-set logic is used to compare the passing variable code input by the user in the flashing module with the passing variable code obtained by the DLL from the website to achieve the verification of the passing variable code. In addition to defining this passing variable in the security algorithm interface definition module, multiple variables for implementing other functions are also defined. The passing variable mentioned in this embodiment is only used for verification when interacting with the vehicle-mounted controller.

[0067] The passing variable input module is used to provide a UI interface for the user to input the passing variable code and send the passing variable code input by the user to the security algorithm module.

[0068] In one embodiment, after the verification of the passing variable code is completed, the DLL security algorithm interface feeds back a status code to the diagnostic instrument. The diagnostic instrument judges whether the verification passes through the status code. If the verification fails, subsequent operations of the diagnostic instrument are prohibited.

[0069] In one embodiment, after receiving the account number and password input by the user, the after-sales service system platform module feeds back a dynamic access variable code to the user. Service stations can all log in to the CRM system normally, and external manufacturers cannot log in to the CRM system by normal means. After logging in, the access variables required for flashing the controller can be obtained manually.

[0070] The present invention also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the steps of the method described above are implemented.

[0071] It should be understood that the specific order or hierarchy of steps in the disclosed process is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process can be rearranged without departing from the protection scope of the present disclosure. The appended method claims present the elements of various steps in an exemplary order and are not intended to be limited to the specific order or hierarchy described.

[0072] In the above detailed description, various features are combined in a single embodiment to simplify the present disclosure. This method of disclosure should not be interpreted as reflecting an intention that the embodiments of the claimed subject matter require more features than those clearly recited in each claim. On the contrary, as reflected in the appended claims, the present invention lies in a state with fewer features than all the features of the disclosed single embodiment. Therefore, the appended claims are hereby expressly incorporated into the detailed description, where each claim stands alone as a separate preferred embodiment of the present invention.

[0073] In order for any person skilled in the art to implement or use the present invention, the disclosed embodiments have been described above. For those skilled in the art, various modification methods of these embodiments are obvious, and the general principles defined herein can also be applied to other embodiments without departing from the spirit and protection scope of the present disclosure. Therefore, the present disclosure is not limited to the embodiments given herein, but is consistent with the broadest scope of the principles and novel features disclosed in this application.

[0074] The foregoing description includes examples of one or more embodiments. Of course, it is not possible to describe all possible combinations of components or methods for the purpose of describing the above embodiments, but those of ordinary skill in the art should recognize that the various embodiments can be further combined and arranged. Accordingly, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. In addition, with respect to the term "comprising" used in the specification or claims, this term is inclusive in a manner similar to the term "including", as "including" is interpreted when used as a transitional word in a claim. In addition, any use of the term "or" in the claims or the specification is to mean "non-exclusive or".

[0075] Those skilled in the art will also appreciate that the various illustrative logical blocks, units, and steps listed in the embodiments of the present invention can be implemented by electronic hardware, computer software, or a combination of both. To clearly show the interchangeability of hardware and software, the various illustrative components, units, and steps have been generally described in terms of their functions. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the overall system. Those skilled in the art can use various methods to implement the described functions for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present invention.

[0076] The various illustrative logical blocks or units described in the embodiments of the present invention can be implemented or operated to perform the described functions by a general-purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the above designs. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

[0077] In the embodiments of the present invention, the steps of the methods or algorithms described can be directly embedded in hardware, software modules executed by a processor, or a combination of the two. The software modules can be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and the storage medium can be provided in an ASIC, and the ASIC can be provided in a user terminal. Optionally, the processor and the storage medium can also be provided in different components of the user terminal.

[0078] In one or more exemplary designs, the above-described functions in the embodiments of the present invention can be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium in the form of one or more instructions or codes. A computer-readable medium includes a computer storage medium and a communication medium that facilitates the transfer of a computer program from one place to another. The storage medium can be any available medium accessible by a general-purpose or special-purpose computer. For example, such a computer-readable medium can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other forms readable by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. In addition, any connection can be properly defined as a computer-readable medium. For example, if software is transmitted from a website, a server, or other remote resources via a coaxial cable, an optical fiber cable, a twisted pair, a digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the defined computer-readable medium. The disks (disk) and discs (disc) include compact disks, laser disks, optical discs, DVDs, floppy disks, and Blu-ray discs. Disks usually reproduce data magnetically, while discs usually reproduce data optically by laser. The above combinations can also be included in the computer-readable medium.

[0079] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for preventing illegal flashing of a commercial vehicle diagnostic instrument, characterized in that, It includes the following steps: The user obtains a passing variable code and inputs the passing variable code into the diagnostic instrument. The security algorithm interface compares the passing variable code input by the user with the passing variable code predefined in the security algorithm interface. If the passing variable codes are the same, the diagnostic instrument is allowed to execute the subsequent flashing process. Otherwise, subsequent operations of the diagnostic instrument are prohibited. The interface definition of the security algorithm is implemented by a security algorithm interface in the form of a DLL file, and a passing variable code to be verified is predefined in the security algorithm interface. The passing variable code predefined in the security algorithm interface is obtained in real time from the after-sales service system. The way for the user to obtain the passing variable code is as follows: The user logs in to the after-sales service system through an account and password and obtains the passing variable code from the after-sales service system. The passing variable code is a dynamically changing variable code.

2. The method for preventing illegal flashing of a commercial vehicle diagnostic instrument according to claim 1, characterized in that, The passing variable code is the 27-service passing variable defined in the interface definition of the security algorithm in the diagnostic instrument.

3. A system for preventing illegal flashing of a commercial vehicle diagnostic instrument for implementing the method according to claim 1 or 2, characterized in that: It includes A diagnostic instrument software module, integrated in the diagnostic instrument, for the user to input a passing variable code and to implement data flashing of the diagnostic instrument after the passing variable code is verified. A security algorithm module, integrated in the DLL security algorithm interface, for comparing the passing variable code input by the user with the predefined passing variable code to implement verification of the passing variable code. An after-sales service system platform module for providing the passing variable code to the user or the DLL security algorithm interface. The interface definition of the security algorithm is implemented by a security algorithm interface in the form of a DLL file, and a passing variable code to be verified is predefined in the security algorithm interface. The passing variable code predefined in the security algorithm interface is obtained in real time from the after-sales service system.

4. The system for preventing illegal flashing of a commercial vehicle diagnostic instrument according to claim 3, characterized in that, The diagnostic instrument software module includes: A data flashing module for implementing data flashing of the diagnostic instrument, jumping to the passing variable input module when the flashing process reaches service 27, and jumping to the security algorithm interface definition module after obtaining the passing variable. A security algorithm interface definition module for defining a passing variable and sending the defined passing variable to the security algorithm module, and the defined passing variable is obtained from the after-sales service system platform module. A passing variable input module for providing a UI interface for the user to input the passing variable code and sending the passing variable code input by the user to the security algorithm module.

5. The system for preventing illegal flashing of a commercial vehicle diagnostic instrument according to claim 3, characterized in that: After the verification of the passing variable code is completed, the DLL security algorithm interface feeds back a status code to the diagnostic instrument. The diagnostic instrument judges whether the verification is passed through the status code. If the verification fails, subsequent operations of the diagnostic instrument are prohibited.

6. The system for preventing illegal flashing of a commercial vehicle diagnostic instrument according to claim 3, characterized in that: After receiving the account and password input by the user, the after-sales service system platform module feeds back a dynamic passing variable code to the user.

7. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 2.

Images