Function authority management method and device of diagnostic equipment, equipment and medium

Abstract

The invention discloses a function authority management method and device of diagnostic equipment, equipment and a medium, and relates to the technical field of equipment authority management, and the method comprises the steps: identifying a diagnostic function selected by an operation object; displaying a security code input prompt box to prompt the operation object to input a security code corresponding to the selected diagnosis function; different types of diagnosis functions correspond to different security codes; generating a security code corresponding to the diagnosis function selected by the operation object; checking the security code input by the operation object according to the generated security code; and if the verification is passed, executing the diagnosis function selected by the operation object. According to the method, the function authority management of the diagnostic equipment can be realized without a background management system, the function authority management investment can be reduced, and the cost is saved.

Description

Technical Field

[0001] The present application relates to the technical field of device authority management, and in particular to a method, apparatus, device and computer-readable storage medium for managing functional authority of a diagnostic device. Background Art

[0002] The diagnostic functions of a vehicle's diagnostic equipment often include multiple functions, such as reading fault codes, clearing codes, reading data streams, key matching, replacing anti-theft devices, and so on. Among them, some functions are not open to all users, but only to users who have the right to use the function. Therefore, permission management is required for the diagnostic functions of the diagnostic equipment. At present, the permission management of the diagnostic functions of diagnostic equipment requires the support of the background management system, which implements registration, login, and permission management. Under the management of the background management system, users of different levels correspond to different permissions. However, the investment in permission management by the background management system is large and the cost is high. Therefore, providing a functional permission management solution without a background management system has become a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0003] The purpose of this application is to provide a method, device, equipment and medium for functional authority management of diagnostic equipment, which can realize functional authority management of diagnostic equipment without a background management system, reduce the investment in functional authority management and save costs.

[0004] In order to solve the above technical problems, the present application provides a method for managing the function permissions of a diagnostic device, which is applied to the diagnostic device, and includes:

[0005] Identify diagnostic functions for operation object selection;

[0006] Displaying a security code input prompt box to prompt the operation object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes;

[0007] generating a security code corresponding to the diagnostic function selected by the operation object;

[0008] Verifying the security code input by the operation object according to the generated security code;

[0009] If the verification passes, the diagnostic function selected by the operation object is executed.

[0010] In some embodiments, generating a security code corresponding to the diagnostic function selected by the operation object includes:

[0011] Get target information;

[0012] Determine a character string according to the target information;

[0013] The character string is encrypted using an encryption algorithm corresponding to the diagnostic function selected by the operation object to generate a security code corresponding to the diagnostic function selected by the operation object; different types of diagnostic functions have different corresponding encryption algorithms.

[0014] In some embodiments, the target information includes any one or more of a product serial number, a vehicle model software code, a diagnostic protocol name, and a diagnostic software version.

[0015] In some embodiments, the types of diagnostic functions include basic diagnostic functions and special diagnostic functions; the basic diagnostic functions include reading fault codes, clearing codes, and reading data streams; the special diagnostic functions include flashing electronic controllers, key matching, and replacing anti-theft devices.

[0016] In some embodiments, verifying the security code input by the operation object according to the generated security code includes:

[0017] Determining whether the security code input by the operation object is within the validity period;

[0018] Comparing the generated security code with the security code input by the operation subject;

[0019] If the security code input by the operation object is within the validity period and the generated security code is consistent with the security code input by the operation object, the security code input by the operation object passes the verification;

[0020] If the security code input by the operation object is not within the validity period and / or the generated security code is inconsistent with the security code input by the operation object, the security code input by the operation object fails the verification.

[0021] In some embodiments, different types of diagnostic functions may correspond to security codes with different validity periods.

[0022] In some embodiments, the validity period of the security code corresponding to the basic diagnostic function is longer than that of the special diagnostic function.

[0023] In order to solve the above technical problems, the present application also provides a function permission management device for a diagnostic device, which is applied to the diagnostic device and includes:

[0024] An identification module, used to identify the diagnostic function selected by the operation object;

[0025] A display module, used to display a security code input prompt box to prompt the operation object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes;

[0026] A generating module, used for generating a security code corresponding to the diagnostic function selected by the operation object;

[0027] A verification module, used to verify the security code input by the operation object according to the generated security code;

[0028] The execution module is used to execute the diagnostic function selected by the operation object if the verification passes.

[0029] In order to solve the above technical problems, the present application also provides a function permission management device for a diagnostic device, including:

[0030] Memory for storing computer programs;

[0031] The processor is used to implement the steps of the function permission management method of the diagnostic device as described above when executing the computer program.

[0032] In order to solve the above technical problems, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the function permission management method of the diagnostic device as described above are implemented.

[0033] The function permission management method of the diagnostic device provided in the present application is applied to the diagnostic device, including: identifying the diagnostic function selected by the operation object; displaying a security code input prompt box to prompt the operation object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes; generating a security code corresponding to the diagnostic function selected by the operation object; verifying the security code input by the operation object according to the generated security code; if the verification passes, executing the diagnostic function selected by the operation object.

[0034] It can be seen that in the function permission management method of the diagnostic device provided by the present application, different categories of diagnostic functions correspond to different security codes. If a user wants to use a certain diagnostic function, he needs to enter the security code corresponding to the diagnostic function. If the security code entered by the user passes the verification, the diagnostic function is allowed to be executed, otherwise, it is not allowed. This method does not require a background management system to verify the user's permissions. The diagnostic device only needs to verify the security code entered by the user. In the absence of a background management system, the function permission management of the diagnostic device can be realized, which can reduce the investment in function permission management and save costs.

[0035] The functional authority management device, device and computer-readable storage medium of the diagnostic device provided in this application all have the above-mentioned technical effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the prior art and the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0037] Figure 1 A flowchart of a method for managing functional permissions of a diagnostic device provided in an embodiment of the present application;

[0038] Figure 2 A flowchart of a specific embodiment of a method for managing functional permissions of a diagnostic device provided in an embodiment of the present application;

[0039] Figure 3 A schematic diagram of a function permission management device for a diagnostic device provided in an embodiment of the present application;

[0040] Figure 4 A schematic diagram of a function authority management device for a diagnostic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] The core of this application is to provide a method, device, equipment and medium for functional authority management of diagnostic equipment, which can realize functional authority management of diagnostic equipment without a background management system, reduce the investment in functional authority management and save costs.

[0042] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0043] Please refer to Figure 1 , Figure 1 A flowchart of a method for managing the functional rights of a diagnostic device provided in an embodiment of the present application is provided. Figure 1 As shown, the method includes:

[0044] S101: Identify the diagnostic function selected by the operation object;

[0045] The executor of the function permission management method of the diagnostic device provided in this embodiment is the diagnostic device, and the diagnostic device implements function permission management by executing APP (Application). After the diagnostic device is turned on, the application is started. The diagnostic device displays various diagnostic functions for users to choose. Among them, the diagnostic functions of the diagnostic device include reading fault codes, clearing codes, reading data streams, ECU (Electronic Control Unit) flashing, key matching, replacing anti-theft, etc. After the user selects the diagnostic function by clicking, the diagnostic device identifies the diagnostic function selected by the user, i.e., the operating object.

[0046] S102: Displaying a security code input prompt box to prompt the operation object to input a security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes;

[0047] After identifying the diagnostic function selected by the user, the diagnostic device displays a security code input prompt box to prompt the user to enter the security code corresponding to the selected diagnostic function. Different types of diagnostic functions correspond to different security codes.

[0048] Among them, the user can contact the OEM's security code management department to obtain the security code, and then input the obtained security code into the diagnostic device.

[0049] S103: generating a security code corresponding to the diagnostic function selected by the operation object;

[0050] S104: verifying the security code input by the operation object according to the generated security code;

[0051] In addition to the security code corresponding to the diagnostic function selected by the user, the diagnostic device automatically generates a security code corresponding to the diagnostic function selected by the user to verify the security code input by the user based on the security code generated by the diagnostic device itself.

[0052] The execution order of step S102 and step S103 can be set differently. Step S102 can be executed first and then step S103, or step S103 can be executed first and then step S102, or step S102 and step S103 can be executed simultaneously.

[0053] In some embodiments, generating a security code corresponding to the diagnostic function selected by the operation object includes:

[0054] Get target information;

[0055] Determine a character string according to the target information;

[0056] The character string is encrypted using an encryption algorithm corresponding to the diagnostic function selected by the operation object to generate a security code corresponding to the diagnostic function selected by the operation object; different types of diagnostic functions have different corresponding encryption algorithms.

[0057] The target information is the pre-set information used to generate the security code. Different encryption algorithms can be set for different types of diagnostic functions. On the basis of obtaining the target information, the target information can be combined to obtain a string, and then the string is encrypted using the encryption algorithm corresponding to the diagnostic function selected by the user to generate the corresponding security code.

[0058] It is clear that if there is one target information, the target information can be directly encrypted as a string to generate a corresponding security code. If there are two or more target information, the target information is combined to obtain a string.

[0059] In some embodiments, the target information includes any one or more of a product serial number, a vehicle model software code, a diagnostic protocol name, and a diagnostic software version.

[0060] The target information may be any one or more of the product serial number, vehicle model software code, diagnostic protocol name, and diagnostic software version. The type of target information may also be expanded according to actual application conditions.

[0061] Exemplarily, the target information includes the product serial number, vehicle model software code (e.g., chery, geely, etc.), and the diagnostic protocol name (e.g., can, doip, etc.). The product serial number is 123456, the vehicle model software code is chery, and the diagnostic protocol name is can. Then, the string obtained by combining the product serial number, vehicle model software code, and diagnostic protocol name may be 123456cherycan.

[0062] Different product serial numbers will generate different security codes; different vehicle model software codes will generate different security codes; different diagnostic protocol names will generate different security codes; different diagnostic software versions will generate different security codes.

[0063] When the diagnostic device generates a security code based on the target information, the user provides the target information to the host factory security code management department when contacting the host factory security code management department to obtain the security code, so that the host factory security code management department can generate a security code based on the target information and provide it to the user.

[0064] In order to facilitate the user to learn the target information, the diagnostic device can display the target information for the user to view when prompting the user to enter the security code. For example, the target information can be displayed in the security code input prompt box.

[0065] In some embodiments, the types of diagnostic functions include basic diagnostic functions and special diagnostic functions; the basic diagnostic functions include reading fault codes, clearing codes, and reading data streams; the special diagnostic functions include flashing electronic controllers, key matching, and replacing anti-theft devices.

[0066] In this embodiment, the diagnostic functions include two categories, one is basic diagnostic functions, and the other is special diagnostic functions. Basic diagnostic functions include reading fault codes, clearing codes, and reading data streams. Special diagnostic functions include electronic controller flashing, key matching, and replacing anti-theft. Different types of diagnostic functions correspond to different encryption algorithms. Different encryption algorithms are used, and different security codes are generated.

[0067] Since the special diagnostic function is not open to all users and has the highest security level, the encryption algorithm corresponding to the special diagnostic function is more complex and has a higher security level. For example, the encryption algorithm corresponding to the basic diagnostic function is the AES (Advanced Encryption Standard) encryption algorithm, and the encryption algorithm corresponding to the special diagnostic function is an encryption algorithm that is more complex and has a higher security level than the AES encryption algorithm.

[0068] In some embodiments, verifying the security code input by the operation object according to the generated security code includes:

[0069] Determining whether the security code input by the operation object is within the validity period;

[0070] Comparing the generated security code with the security code input by the operation subject;

[0071] If the security code input by the operation object is within the validity period and the generated security code is consistent with the security code input by the operation object, the security code input by the operation object passes the verification;

[0072] If the security code input by the operation object is not within the validity period and / or the generated security code is inconsistent with the security code input by the operation object, the security code input by the operation object fails the verification.

[0073] The diagnostic device verifies the security code input by the user according to the security code generated by itself, including verifying the timeliness and correctness of the security code input by the user. It can be first determined whether the timeliness of the security code input by the user is valid. If invalid, it is directly determined that the security code input by the user has not been verified. If valid, the generated security code is further compared with the security code input by the user. If the generated security code is consistent with the security code input by the user, the security code input by the user has been verified; if the generated security code is inconsistent with the security code input by the user, the security code input by the user has not been verified. It is also possible to first compare the generated security code with the security code input by the user; if the generated security code is inconsistent with the security code input by the user, it is directly determined that the security code input by the user has not been verified. If the generated security code is consistent with the security code input by the user, it is further determined whether the timeliness of the security code input by the user is valid. If valid, it is determined that the security code input by the user has been verified; if invalid, it is determined that the security code input by the user has not been verified. Alternatively, it is also possible to synchronously determine whether the security code input by the user is within the timeliness period, and compare the generated security code with the security code input by the user. If the security code entered by the user is within the validity period and the generated security code is consistent with the security code entered by the user, the verification of the security code entered by the user passes; if the security code entered by the user is not within the validity period and / or the generated security code is inconsistent with the security code entered by the user, the verification of the security code entered by the user fails.

[0074] In some embodiments, the validity period of the security code corresponding to different types of diagnostic functions is different. The validity period of the security code corresponding to the basic diagnostic function is longer than that of the special diagnostic function.

[0075] This embodiment sets different validity periods for security codes corresponding to different types of diagnostic functions. The validity period of the security code corresponding to the basic diagnostic function is longer than the validity period of the security code corresponding to the special diagnostic function. For example, the validity period of the security code corresponding to the basic diagnostic function is 24 hours, and the validity period of the security code corresponding to the special diagnostic function is 12 hours.

[0076] S105: If the verification passes, the diagnostic function selected by the operation object is executed.

[0077] If the security code corresponding to the diagnostic function selected by the user passes the verification, the diagnostic function selected by the user is executed. If the security code corresponding to the diagnostic function selected by the user fails the verification, the diagnostic function selected by the user is not executed.

[0078] When the security code verification corresponding to the diagnostic function selected by the user fails, the diagnostic device can also display the reason for the failure. For example, if the security code is not within the corresponding validity period, the reason for failure can be displayed as not within the validity period. If the security code is incorrect, the security code incorrect can be displayed.

[0079] refer to Figure 2 As shown, a specific embodiment is described below:

[0080] Diagnose device startup application.

[0081] The application obtains the product serial number, vehicle model software code, diagnostic protocol type, etc.

[0082] The diagnostic device displays different diagnostic functions.

[0083] The diagnostic device recognizes the diagnostic function selected by the user.

[0084] When the diagnostic function selected by the user is a conventional function, the application generates a security code by calling the first encryption algorithm based on the obtained product serial number, vehicle model software code and other information.

[0085] When the user selects the diagnostic function as a special diagnostic function, the application calls the second encryption algorithm to generate a security code based on the obtained product serial number, vehicle model software code, etc. The second encryption algorithm is more complex than the first encryption algorithm and has a higher security level.

[0086] The diagnostic device prompts the user to enter a security code in a pop-up window.

[0087] The diagnostic device verifies the timeliness and correctness of the security code entered by the user.

[0088] If the security code entered by the user passes the verification, the diagnostic function selected by the user is executed.

[0089] If the security code entered by the user fails to pass the verification, the process ends without executing the diagnostic function selected by the user.

[0090] In summary, the functional permission management method of the diagnostic device provided by the present application corresponds to different security codes for different categories of diagnostic functions. If a user wants to use a certain diagnostic function, he needs to enter the security code corresponding to the diagnostic function. If the security code entered by the user passes the verification, the diagnostic function is allowed to execute, otherwise, it is not allowed. This method does not require a background management system to verify the user's permissions. The diagnostic device only needs to verify the security code entered by the user. In the absence of a background management system, the functional permission management of the diagnostic device can be realized, which can reduce the investment in functional permission management and save costs.

[0091] The present application also provides a function permission management device for a diagnostic device. The device described below can be referred to in correspondence with the method described above. Figure 3 , Figure 3 A schematic diagram of a function permission management device for a diagnostic device provided in an embodiment of the present application, combined with Figure 3 As shown, the device comprises:

[0092] An identification module 10, for identifying a diagnostic function selected by an operation object;

[0093] The display module 20 is used to display a security code input prompt box to prompt the operation object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes;

[0094] A generating module 30, for generating a security code corresponding to the diagnostic function selected by the operation object;

[0095] A verification module 40, used to verify the security code input by the operation object according to the generated security code;

[0096] The execution module 50 is used to execute the diagnostic function selected by the operation object if the verification passes.

[0097] Based on the above embodiment, as a specific implementation, the generation module 30 includes:

[0098] An acquisition unit, used for acquiring target information;

[0099] A determination unit, configured to determine a character string according to the target information;

[0100] The generating unit is used to encrypt the character string by adopting the encryption algorithm corresponding to the diagnostic function selected by the operating object, and generate a security code corresponding to the diagnostic function selected by the operating object; different types of diagnostic functions correspond to different encryption algorithms.

[0101] Based on the above embodiment, as a specific implementation method, the target information includes any one or more of the product serial number, vehicle model software code, diagnostic protocol name, and diagnostic software version.

[0102] On the basis of the above embodiments, as a specific implementation method, the types of diagnostic functions include basic diagnostic functions and special diagnostic functions; the basic diagnostic functions include reading fault codes, clearing codes, and reading data streams; the special diagnostic functions include flashing electronic controllers, key matching, and replacing anti-theft devices.

[0103] Based on the above embodiment, as a specific implementation, the verification module 40 includes:

[0104] A judging unit, used to judge whether the security code input by the operation object is within the validity period;

[0105] A comparison unit, used for comparing the generated security code with the security code input by the operation object;

[0106] A first determination unit, configured to determine that the security code input by the operation object passes verification if the security code input by the operation object is within a validity period and the generated security code is consistent with the security code input by the operation object;

[0107] The second determination unit is configured to determine that the security code input by the operation object fails the verification if the security code input by the operation object is not within a validity period and / or the generated security code is inconsistent with the security code input by the operation object.

[0108] Based on the above embodiment, as a specific implementation mode, different types of diagnostic functions correspond to security codes with different validity periods.

[0109] Based on the above embodiment, as a specific implementation mode, the validity period of the security code corresponding to the basic diagnostic function is longer than the validity period of the special diagnostic function.

[0110] The function permission management device of the diagnostic device provided by the present application has different security codes corresponding to different categories of diagnostic functions. If a user wants to use a certain diagnostic function, he needs to enter the security code corresponding to the diagnostic function. If the security code entered by the user passes the verification, the diagnostic function is allowed to be executed, otherwise, it is not allowed. This method does not require a background management system to verify the user's permissions. The diagnostic device only needs to verify the security code entered by the user. In the absence of a background management system, the function permission management of the diagnostic device can be realized, which can reduce the investment in function permission management and save costs.

[0111] This application also provides a diagnostic device function permission management device, reference Figure 4 As shown, the device includes a memory 1 and a processor 2 .

[0112] Memory 1, used for storing computer programs;

[0113] Processor 2 is used to execute the computer program to implement the following steps:

[0114] Identify the diagnostic function selected by the operating object; display a security code input prompt box to prompt the operating object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes; generate a security code corresponding to the diagnostic function selected by the operating object; verify the security code input by the operating object based on the generated security code; if the verification passes, execute the diagnostic function selected by the operating object.

[0115] For an introduction to the equipment provided in this application, please refer to the above method embodiments, and this application will not go into details here.

[0116] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the following steps can be implemented:

[0117] Identify the diagnostic function selected by the operating object; display a security code input prompt box to prompt the operating object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes; generate a security code corresponding to the diagnostic function selected by the operating object; verify the security code input by the operating object based on the generated security code; if the verification passes, execute the diagnostic function selected by the operating object.

[0118] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0119] For an introduction to the computer-readable storage medium provided in this application, please refer to the above method embodiment, and this application will not go into details here.

[0120] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the devices, equipment, and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0121] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0122] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0123] The functional permission management method, device, equipment and computer-readable storage medium of the diagnostic equipment provided by the present application are introduced in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core idea of ​​the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A method for managing the functional rights of a diagnostic device, characterized in that: Applications in diagnostic equipment, including: Identify diagnostic functions for operation object selection; Displaying a security code input prompt box to prompt the operation object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes; generating a security code corresponding to the diagnostic function selected by the operation object; Verifying the security code input by the operation object according to the generated security code; If the verification passes, the diagnostic function selected by the operation object is executed.

2. The method for managing the function rights of a diagnostic device according to claim 1, characterized in that: Generating a security code corresponding to the diagnostic function selected by the operation object includes: Get target information; Determine a character string according to the target information; The character string is encrypted using an encryption algorithm corresponding to the diagnostic function selected by the operation object to generate a security code corresponding to the diagnostic function selected by the operation object; different types of diagnostic functions have different corresponding encryption algorithms.

3. The method for managing the function rights of a diagnostic device according to claim 2, characterized in that: The target information includes any one or more of the product serial number, vehicle model software code, diagnostic protocol name, and diagnostic software version.

4. The method for managing the function rights of a diagnostic device according to claim 1, characterized in that: The types of diagnostic functions include basic diagnostic functions and special diagnostic functions; the basic diagnostic functions include reading fault codes, clearing codes, and reading data streams; the special diagnostic functions include flashing electronic controllers, key matching, and replacing anti-theft devices.

5. The method for managing the function rights of a diagnostic device according to claim 1, characterized in that: Verifying the security code input by the operation object according to the generated security code includes: Determining whether the security code input by the operation object is within the validity period; Comparing the generated security code with the security code input by the operation subject; If the security code input by the operation object is within the validity period and the generated security code is consistent with the security code input by the operation object, the security code input by the operation object passes the verification; If the security code input by the operation object is not within the validity period and / or the generated security code is inconsistent with the security code input by the operation object, the security code input by the operation object fails the verification.

6. The method for managing the function rights of a diagnostic device according to claim 5, characterized in that: The validity period of the security code corresponding to different types of diagnostic functions is different.

7. The method for managing the function rights of a diagnostic device according to claim 4, characterized in that: The validity period of the security code corresponding to the basic diagnostic function is longer than that of the special diagnostic function.

8. A function permission management device for a diagnostic device, characterized in that: Applications in diagnostic equipment, including: An identification module, used to identify the diagnostic function selected by the operation object; A display module, used to display a security code input prompt box to prompt the operation object to input the security code corresponding to the selected diagnostic function; different types of diagnostic functions correspond to different security codes; A generating module, used for generating a security code corresponding to the diagnostic function selected by the operation object; A verification module, used to verify the security code input by the operation object according to the generated security code; The execution module is used to execute the diagnostic function selected by the operation object if the verification passes.

9. A function authority management device for a diagnostic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the method for managing functional permissions of a diagnostic device as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for managing the functional authority of a diagnostic device according to any one of claims 1 to 7 are implemented.

Images