Vehicle diagnostic management methods, devices, equipment and computer program products

Abstract

This application discloses a vehicle diagnostic management method, apparatus, device, and computer program product, relating to the field of vehicle diagnostic technology. The vehicle diagnostic management method includes: receiving a diagnostic function instruction to be executed; classifying the instruction by safety level based on pre-generated functional safety level data to obtain functional safety level data; and performing vehicle diagnostic management based on a pre-built function management interface, according to the functional safety level data and the diagnostic function instruction, to obtain a vehicle diagnostic management result. The function management interface in this application sets the vehicle diagnostic mode according to the functional safety level data, restricting the permissions for data and file transmission via the USB interface. This solves the problem of poor data security in existing diagnostic device USB security management methods, improving the security of vehicle diagnostics and data transmission.

Description

Technical Field

[0001] This application relates to the field of vehicle diagnostic technology, and in particular to a vehicle diagnostic management method, device, equipment, and computer program product. Background Technology

[0002] Currently, the USB port on diagnostic devices allows for the copying of various common files, posing a risk of tampering with diagnostic software. Existing methods for managing USB security in diagnostic devices involve regularly monitoring for the latest USB security vulnerabilities and promptly upgrading to secure USB firmware to improve security. However, this approach may not be able to detect USB security vulnerabilities in a timely manner, and therefore, security remains relatively poor.

[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main objective of this application is to provide a vehicle diagnostic management method, device, equipment, and computer program product, which aims to solve the technical problem of poor data security in existing diagnostic equipment USB security management methods.

[0005] To achieve the above objectives, this application proposes a vehicle diagnostic management method, the method comprising:

[0006] Receive instructions for diagnostic functions to be performed;

[0007] Based on pre-generated functional safety level data, the diagnostic function instructions to be executed are classified by safety level to obtain functional level data to be executed.

[0008] Based on the pre-built function management interface, vehicle diagnostic management is performed according to the data of the function level to be executed and the diagnostic function instructions to be executed, and the vehicle diagnostic management results are obtained.

[0009] In one embodiment, the step of classifying the diagnostic function instruction to be executed based on pre-generated functional safety level data to obtain the functional level data to be executed includes:

[0010] Based on a preset diagnostic protocol, function identification data is obtained according to the diagnostic function instruction to be executed;

[0011] The function identification data is matched with the function safety level data to obtain the function level data to be executed.

[0012] In one embodiment, the vehicle diagnostic management result is a first vehicle diagnostic management result. The step of performing vehicle diagnostic management based on a pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instruction to be executed, to obtain the vehicle diagnostic management result includes:

[0013] When the function level data to be executed is the preset first security level, the function management interface is set to the unrestricted mode to obtain the first function management interface;

[0014] Through the first function management interface, the corresponding diagnostic function is performed on the vehicle according to the diagnostic function instruction to be executed, and the first vehicle diagnostic management result is obtained.

[0015] In one embodiment, the vehicle diagnostic management result is a second vehicle diagnostic management result. The step of performing vehicle diagnostic management based on the pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instruction to be executed, to obtain the vehicle diagnostic management result includes:

[0016] When the data of the function to be executed is the preset second security level, the function management interface is set to whitelist mode to obtain the second function management interface;

[0017] Through the second function management interface, the corresponding diagnostic function is performed on the vehicle according to the diagnostic function instruction to be executed, using a preset whitelist method, to obtain the second vehicle diagnostic management result.

[0018] In one embodiment, the vehicle diagnostic management result is a third vehicle diagnostic management result. The step of performing vehicle diagnostic management based on the pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instruction to be executed, to obtain the vehicle diagnostic management result includes:

[0019] When the data of the function to be executed is the preset third security level, the function management interface is set to the disabled mode to obtain the third function management interface;

[0020] The third vehicle diagnostic management result is generated based on the third function management interface and the diagnostic function instruction to be executed.

[0021] In one embodiment, the step of classifying the diagnostic function instruction to be executed based on pre-generated functional safety level data to obtain the functional safety level data to be executed further includes:

[0022] Obtain the diagnostic function instruction dataset;

[0023] The diagnostic function instruction dataset is subjected to a functional evaluation to obtain functional evaluation data;

[0024] Based on preset fault mode data, risk analysis is performed on the diagnostic function instruction dataset to obtain risk analysis data;

[0025] Based on preset safety standard data, the diagnostic function instruction dataset is classified according to standard to obtain standard classification data;

[0026] The functional safety level data is generated based on the functional assessment data, risk analysis data, and standard classification data.

[0027] In one embodiment, before the step of performing vehicle diagnostic management based on the pre-built function management interface, according to the function level data to be executed and the diagnostic function instruction to be executed, and obtaining the vehicle diagnostic management result, the method further includes:

[0028] Create the initial function management interface;

[0029] In response to the pattern definition instruction, the initial function management interface is pattern defined to obtain the interface after pattern definition;

[0030] In response to the file management permission setting instruction, file management permissions are set on the interface defined in the mode to obtain the function management interface.

[0031] Furthermore, to achieve the above objectives, this application also proposes a vehicle diagnostic management device, which includes:

[0032] The instruction receiving module is used to receive diagnostic function instructions to be executed.

[0033] The safety level classification module is used to classify the diagnostic function instruction to be executed based on pre-generated functional safety level data to obtain the functional level data to be executed.

[0034] The diagnostic management module is used to perform vehicle diagnostic management based on the pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instructions to be executed, and to obtain the vehicle diagnostic management results.

[0035] In addition, to achieve the above objectives, this application also proposes a vehicle diagnostic management device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the vehicle diagnostic management method as described above.

[0036] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and which, when executed by a processor, implements the steps of the vehicle diagnostic management method described above.

[0037] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the vehicle diagnostic management method described above.

[0038] This application provides a vehicle diagnostic management method. Based on pre-generated functional safety level data, the method classifies the diagnostic function instructions to be executed into safety levels to obtain the function level data to be executed. Then, based on a pre-built function management interface, the method performs vehicle diagnostic management according to the function level data and the diagnostic function instructions to be executed, resulting in vehicle diagnostic management results. The function management interface sets the vehicle diagnostic mode according to the function level data to be executed, restricting the permissions for data and file transmission via the USB interface. This solves the problem of poor data security in existing diagnostic device USB security management methods and improves the security of vehicle diagnostics and data transmission. Attached Figure Description

[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 This is a flowchart illustrating an embodiment of the vehicle diagnostic management method of this application.

[0042] Figure 2 This is a flowchart illustrating Embodiment 2 of the vehicle diagnostic management method of this application;

[0043] Figure 3 This is a flowchart illustrating Embodiment 3 of the vehicle diagnostic management method of this application;

[0044] Figure 4 A simplified flowchart illustrating the vehicle diagnostic management method provided in Embodiment 3 of this application;

[0045] Figure 5 This is a schematic diagram of the module structure of the vehicle diagnostic management device according to an embodiment of this application;

[0046] Figure 6 This is a schematic diagram of the hardware operating environment involved in the vehicle diagnostic management method in this application.

[0047] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0048] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0049] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0050] The main solution in this application's embodiments is:

[0051] Receive instructions for diagnostic functions to be performed;

[0052] Based on pre-generated functional safety level data, the diagnostic function instructions to be executed are classified by safety level to obtain functional level data to be executed.

[0053] Based on the pre-built function management interface, vehicle diagnostic management is performed according to the data of the function level to be executed and the diagnostic function instructions to be executed, and the vehicle diagnostic management results are obtained.

[0054] Because existing technologies allow the copying of various common files via the USB port on diagnostic devices, there is a risk of tampering with the diagnostic software. Current methods for managing USB security in diagnostic devices involve regularly monitoring for the latest USB security vulnerabilities and promptly upgrading to secure USB firmware to improve security. However, this approach may not be able to detect USB security vulnerabilities in a timely manner, and therefore security remains relatively poor.

[0055] This application provides a solution that, based on pre-generated functional safety level data, classifies the diagnostic function instructions to be executed according to their safety levels to obtain the functional level data to be executed; then, based on a pre-built function management interface, performs vehicle diagnostic management according to the functional level data to be executed and the diagnostic function instructions to be executed, obtaining the vehicle diagnostic management results. The function management interface sets the vehicle diagnostic mode according to the functional level data to be executed, restricting the permissions for data and file transmission via the USB interface, thus solving the problem of poor data security in existing diagnostic device USB security management methods and improving the security of vehicle diagnostics and data transmission.

[0056] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or vehicle diagnostic management system capable of performing the above functions. The following description uses a vehicle diagnostic management system as an example to illustrate this embodiment and the subsequent embodiments.

[0057] Based on this, embodiments of this application provide a vehicle diagnostic management method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle diagnostic management method of this application.

[0058] In this embodiment, the vehicle diagnostic management method includes steps S10 to S30:

[0059] Step S10: Receive the diagnostic function instruction to be executed;

[0060] It should be noted that diagnostic function instructions to be executed usually refer to diagnostic operations that have not yet been executed but are planned or prepared to be performed. These instructions typically include tasks such as fault detection, system analysis, and performance evaluation to ensure the normal operation and timely maintenance of equipment or systems.

[0061] Step S20: Based on the pre-generated functional safety level data, classify the diagnostic function instructions to be executed according to their safety level to obtain the functional level data to be executed;

[0062] The vehicle diagnostic management system uses preset safety level standards to classify the diagnostic function data to be executed, obtain the function level data to be executed, and determine its safety level. These levels may be classified based on factors such as the importance of the function and its impact on vehicle safety.

[0063] It should be noted that functional safety level data is safety level data generated during the design phase based on functional safety standards and system requirements. This data defines the safety level requirements for different functions or diagnostic data in the system and usually comes from system design documents, functional safety analysis reports, or relevant safety standards.

[0064] Step S30: Based on the pre-built function management interface, perform vehicle diagnostic management according to the data of the function level to be executed and the diagnostic function instructions to be executed, and obtain the vehicle diagnostic management result.

[0065] The vehicle diagnostic management system uses pre-designed function management interfaces to execute diagnostic function instructions based on the function level data to be executed. These interfaces can perform corresponding management operations according to the security level of the data, ensuring that vehicle diagnostic management is carried out in accordance with predetermined functional safety standards and requirements, thereby improving vehicle safety and reliability and generating diagnostic management results.

[0066] It should be noted that the function management interface refers to the system interface or module used to process and manage diagnostic data.

[0067] This embodiment provides a vehicle diagnostic management method. Based on pre-generated functional safety level data, the method classifies the diagnostic function instructions to be executed according to their safety levels to obtain the functional level data to be executed. Then, based on a pre-built function management interface, the method performs vehicle diagnostic management according to the functional level data and the diagnostic function instructions to be executed, resulting in vehicle diagnostic management results. The function management interface sets the vehicle diagnostic mode according to the functional level data to be executed, restricting the permissions for data and file transmission via the USB interface. This solves the problem of poor data security in existing diagnostic device USB security management methods and improves the security of vehicle diagnostics and data transmission.

[0068] In one feasible implementation, steps S501 to S503 may be included before step S30:

[0069] Step S501: Create the initial function management interface;

[0070] Step S502: In response to the mode definition instruction, the initial function management interface is mode defined to obtain the interface after mode definition;

[0071] Step S503: In response to the file management permission setting instruction, file management permissions are set for the interface defined in the mode to obtain the function management interface.

[0072] The vehicle diagnostic management system creates an initial function management interface. This interface serves as the entry point for managing and operating system functions. An interface refers to the standard for communication between different components in the system. Then, in response to pattern definition instructions, the system analyzes the required interface behaviors and characteristics. Based on the analysis results, it defines patterns for the initial function management interface, such as designing the pattern structure, including the operation, state transitions, and business logic of each pattern, determining the input and output requirements of the patterns, and how to handle different requests and responses. This results in the interface after pattern definition. Finally, in response to file management permission setting instructions, it sets file management permissions for the interface after pattern definition. This includes identifying the files and resources involved in the interface, determining the specific scope of permissions to be set, understanding the access needs and permission requirements of different users or roles, formulating file management permission policies, defining permission settings for different user roles or groups, and determining file access control rules, such as who can access, modify, or delete files. This results in the function management interface.

[0073] It should be noted that the initial function management interface is an interface for basic function management and is the infrastructure for function management. The mode definition instruction is an instruction or configuration file used to define the interface operation mode, and the file management permission setting instruction is an instruction or configuration file used to configure interface permissions.

[0074] In this implementation, by creating an initial function management interface and defining its mode, personalized configuration of the interface can be achieved to meet specific functional requirements and business scenarios, thereby improving the flexibility and adaptability of the interface. The response to file management permission setting instructions ensures the security of the interface. By setting permissions, unauthorized access or operation is prevented, reducing the risk of data leakage or misoperation and improving system security. Thus, the management problems of interface in terms of function and permission are solved. The mode definition and permission setting of the initial interface ensure accurate matching of functions and their security control, avoiding technical problems caused by interface function mismatch or improper permission settings. Through a systematic creation, definition and permission setting process, the efficiency and consistency of interface management can be improved, ensuring that the functional and security requirements of each interface are effectively implemented and managed.

[0075] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 Before step S20, the vehicle diagnostic management method may further include steps S401 to S405:

[0076] Step S401: Obtain the diagnostic function instruction dataset;

[0077] Step S402: Perform a functional evaluation on the diagnostic function instruction dataset to obtain functional evaluation data;

[0078] Step S403: Based on preset fault mode data, perform risk analysis on the diagnostic function instruction dataset to obtain risk analysis data;

[0079] Step S404: Based on preset safety standard data, perform standard classification on the diagnostic function instruction dataset to obtain standard classification data;

[0080] Step S405: Generate the functional safety level data based on the functional assessment data, risk analysis data, and standard classification data.

[0081] The vehicle diagnostic management system acquires a diagnostic function instruction dataset, then performs a functional evaluation on the dataset to obtain functional evaluation data. This evaluation may include performance, stability, and effectiveness assessments. Next, based on preset failure mode data, a risk analysis is performed on the dataset to obtain risk analysis data. Then, based on preset safety standard data, the dataset is classified according to standards to obtain standard classification data. Finally, the functional evaluation data, risk analysis data, and standard classification data are integrated to ensure data integrity and consistency, resulting in functional safety level data.

[0082] It should be noted that the diagnostic function instruction dataset refers to a data set containing all relevant diagnostic function instructions and their parameters. These instructions are used to detect the function, performance, and potential faults of the system. Safety standard data may include regulations, industry standards, company internal standards, etc., such as automotive industry safety standards like ISO 26262.

[0083] In this embodiment, risk analysis identifies potential failure modes and risk points, and classification using preset safety standards effectively improves system security and protection capabilities, ensuring that risks are minimized during the diagnostic process. By acquiring diagnostic function instruction datasets, function assessments, risk analysis, and standard classifications, the safety and reliability of diagnostic functions can be systematically evaluated. This multi-layered analysis ensures a comprehensive review of functions and categorizes them into data that meets safety standards, ensuring that the final functional safety level data is accurate and conforms to preset standards. This solves the problem of potential omissions by single assessment or classification methods. By comprehensively evaluating functional data, risk analysis results, and standard classification data, the safety level of diagnostic functions becomes more comprehensive and reliable, avoiding safety hazards caused by insufficient assessment or inconsistent standards. It can systematically process and evaluate diagnostic functions, improving the accuracy and efficiency of the entire diagnostic process, thereby optimizing the diagnostic workflow and improving the overall performance and stability of the system.

[0084] Based on the first embodiment of this application, in the third embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 3 Step S20 includes steps S201 to S202:

[0085] Step S201: Based on the preset diagnostic protocol, obtain function identification data according to the diagnostic function instruction to be executed;

[0086] Step S202: Match the function identification data with the function safety level data to obtain the function level data to be executed.

[0087] The vehicle diagnostic management system uses the rules in the diagnostic protocol to parse the instructions for the diagnostic functions to be executed. For example, if the protocol defines a certain format, the system will read the various fields in the instructions according to this format to obtain the function identification data. Then, it will compare the function identification data with the function safety level data to find the correspondence. This usually involves searching the database or using mapping rules to determine the safety level of each function identifier and obtain the function level data to be executed.

[0088] It should be noted that the preset diagnostic protocol is a standardized protocol or rule set used to parse and process diagnostic data. These protocols typically include data format specifications, parsing rules, field definitions, etc., defining the data format, processing methods, and how to extract function identifiers. Function service data is the identification information extracted from the function instructions to be executed according to the diagnostic protocol, used to uniquely identify the service function that needs to be diagnosed.

[0089] In one feasible implementation, the vehicle diagnostic management result is a first vehicle diagnostic management result, and step S30 may include steps S3011 to S3012:

[0090] Step S3011: When the function level data to be executed is a preset first security level, the function management interface is set to the unrestricted mode to obtain the first function management interface.

[0091] Step S3012: Through the first function management interface, perform the corresponding diagnostic function on the vehicle according to the diagnostic function instruction to be executed, and obtain the first vehicle diagnostic management result.

[0092] When the data of the function to be executed reaches the preset first security level, the vehicle diagnostic management system sets the function management interface to unrestricted mode, which means that there is no restriction on access to the function. The first function management interface is obtained to ensure that when the specific security level conditions are met, the function management interface can allow full access to the function in order to perform the necessary operations. Then, using the first function management interface set to unrestricted mode, the vehicle is diagnosed according to the diagnostic function instructions to be executed, and the first vehicle diagnostic management result is obtained.

[0093] It should be noted that the first security level is a preset security level standard used to determine whether unrestricted access can be allowed. Unrestricted mode is an interface setting that allows full access to functions.

[0094] In this embodiment, when the data of the function to be executed is a preset first security level, the function management interface is set to an unrestricted mode to obtain a first function management interface. Through the first function management interface, the corresponding diagnostic function is executed on the vehicle according to the diagnostic function instruction to be executed, and the first vehicle diagnostic management result is obtained. The interface management mode is dynamically adjusted according to the security level of the function, thereby achieving flexible safety control. Through the first function management interface, comprehensive diagnosis can be ensured under unrestricted conditions, improving the efficiency of function execution and the accuracy of results. Therefore, diagnosis in the unrestricted mode can avoid the problem of incomplete or inaccurate function execution due to management interface restrictions, ensuring the comprehensiveness and accuracy of diagnostic management results, thereby improving the overall effect of vehicle diagnosis.

[0095] In another feasible implementation, the vehicle diagnostic management result is a second vehicle diagnostic management result, and step S30 may include steps S3021 to S3022:

[0096] Step S3021: When the function level data to be executed is the preset second security level, the function management interface is set to whitelist mode to obtain the second function management interface.

[0097] Step S3022: Through the second function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is performed on the vehicle using a preset whitelist method to obtain the second vehicle diagnostic management result.

[0098] When the data for the function to be executed is the preset first security level, the vehicle diagnostic management system adjusts the function management interface to whitelist mode to obtain the second function management interface. This ensures that only approved functions can be executed, preventing unauthorized or potentially unsafe functions from accessing the system and reducing security risks. Then, through the second function management interface, the corresponding diagnostic function is executed on the vehicle according to the diagnostic function instruction to be executed, using the preset whitelist method, to obtain the second vehicle diagnostic management result.

[0099] It should be noted that whitelist mode is a system configuration state that allows pre-approved functions or operations to pass through, while others are rejected. Whitelist mode is a mode that only allows certified or approved functions to be executed.

[0100] In this embodiment, when the data of the function to be executed is the preset second security level, the function management interface is set to whitelist mode to obtain the second function management interface. Through the second function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is executed on the vehicle using the preset whitelist method to obtain the second vehicle diagnostic management result. Compared with the unrestricted mode, the whitelist mode allows only certified and secure functions or instructions to be executed through the interface while ensuring security. It clarifies the permission management, ensures that the execution of functions conforms to the preset security standards and specifications, ensures the security of the system when processing functions of specific security levels, solves the problem of insufficient security control in function management, and improves the accuracy of diagnostic management results and the overall security of the system.

[0101] In another feasible implementation, the vehicle diagnostic management result is a third vehicle diagnostic management result, and step S30 may include steps S3031 to S3032:

[0102] Step S3031: When the function level data to be executed is the preset third security level, the function management interface is set to disabled mode to obtain the third function management interface.

[0103] Step S3032: Generate the third vehicle diagnostic management result based on the third function management interface and the diagnostic function instruction to be executed.

[0104] When the data for the function to be executed is the preset third security level, the vehicle diagnostic management system switches the function management interface to disabled mode to obtain the third function management interface, thereby restricting access to the interface. This ensures that when the function level meets specific security requirements, the interface can be properly protected when executing high-security-level functions to prevent unauthorized access. Finally, in disabled mode, the third function management interface is used to process the diagnostic function instructions to be executed and generate the third vehicle diagnostic management result.

[0105] It should be noted that the disabled mode is a mode that restricts the operation permissions of the function management interface to prevent unauthorized access or operation.

[0106] In this embodiment, when the data of the function to be executed is the preset third security level, the function management interface is set to the disabled mode to obtain the third function management interface; according to the third function management interface and the diagnostic function instruction to be executed, the third vehicle diagnostic management result is generated. The application of the disabled mode of the third function management interface ensures that only specific, authorized functions can be activated under the third security level, providing precise control and higher security, and ensuring that high-risk functions are strictly reviewed and verified before execution.

[0107] In this embodiment, based on a preset diagnostic protocol, function identification data is obtained according to the diagnostic function instruction to be executed. The function identification data is matched with the function safety level data to obtain the function level data to be executed, ensuring that each diagnostic function has an appropriate safety level, effectively improving the system's function execution accuracy. By accurately obtaining the function level data to be executed, the system can perform corresponding safety control and protection according to preset safety standards, reducing potential risks caused by mismatch between function and safety level, and improving the overall safety and reliability of the system. In addition, by generating third-party vehicle diagnostic management results, it is ensured that diagnostic operations in disabled mode comply with preset safety standards, thereby solving potential operational compliance issues and ensuring the legality and standardization of system operation.

[0108] For example, to help understand the implementation flow of the vehicle diagnostic management method obtained by combining this embodiment with the above-described embodiment three, please refer to... Figure 4 , Figure 4A simplified flowchart of a vehicle diagnostic management method is provided. Specifically, taking a vehicle diagnostic management system as an example of a diagnostic instrument, the vehicle diagnostic management method includes the following steps:

[0109] 1. Modify the operating system of the diagnostic instrument host (tablet) and establish a USB file management interface with the application APK. For example, parameter 1 represents unlimited, 2 represents disabled, and 3 represents whitelist mode.

[0110] 2. The diagnostic tool allows the APK to flexibly set the current USB usage permissions according to the actual usage scenario.

[0111] The diagnostic instrument pre-classifies its diagnostic functions according to different safety levels, for example:

[0112] 2.1 Service IDs 19, 14, 22, and 2F in the CAN protocol (ISO 14229) (which perform basic diagnostic functions such as code reading, code clearing, data stream reading, and action testing) are classified as having a lower security level. When the diagnostic tool uses these commands to communicate with the vehicle, the USB is set to unrestricted mode (the interface parameter in step 1 is set to 1).

[0113] 2.2 Classify the service IDs in the CAN protocol, such as 2E and 31 (which perform special diagnostic functions, such as writing some data to the ECU or performing advanced functions), as medium security level. When the diagnostic tool uses these commands to communicate with the vehicle, set the USB to whitelist mode (set the interface parameter in step 1 to 3) to allow setting the file names that can be copied in the background.

[0114] 2.3 Service IDs 34, 36, 37, etc. in the CAN protocol (for performing flashing functions) are classified as having a higher security level. When the diagnostic tool uses these commands to communicate with the vehicle, the USB is set to disabled mode (the interface parameter in step 1 is set to 2).

[0115] It should be noted that the service ID will be different for different diagnostic protocols.

[0116] This embodiment provides a vehicle diagnostic management method. Based on pre-generated functional safety level data, the method classifies the diagnostic function instructions to be executed according to their safety levels to obtain the functional level data to be executed. Then, based on a pre-built function management interface, the method performs vehicle diagnostic management according to the functional level data and the diagnostic function instructions to be executed, resulting in vehicle diagnostic management results. The function management interface sets the vehicle diagnostic mode according to the functional level data to be executed, restricting the permissions for data and file transmission via the USB interface. This solves the problem of poor data security in existing diagnostic device USB security management methods and improves the security of vehicle diagnostics and data transmission.

[0117] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the vehicle diagnostic management method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0118] This application also provides a vehicle diagnostic management device; please refer to... Figure 5 The vehicle diagnostic management device includes:

[0119] Instruction receiving module 10 is used to receive diagnostic function instructions to be executed;

[0120] The classification module 20 is used to classify the diagnostic function instruction to be executed according to the pre-generated functional safety level data to obtain the functional safety level data to be executed.

[0121] The diagnostic management module 30 is used to perform vehicle diagnostic management based on the pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instruction to be executed, and to obtain the vehicle diagnostic management result.

[0122] Optionally, the classification module 20 is further configured to:

[0123] Based on a preset diagnostic protocol, function identification data is obtained according to the diagnostic function instruction to be executed;

[0124] The function identification data is matched with the function safety level data to obtain the function level data to be executed.

[0125] Optionally, the vehicle diagnostic management result is a first vehicle diagnostic management result, and the diagnostic management module 30 is further used for:

[0126] When the function level data to be executed is the preset first security level, the function management interface is set to the unrestricted mode to obtain the first function management interface;

[0127] Through the first function management interface, the corresponding diagnostic function is performed on the vehicle according to the diagnostic function instruction to be executed, and the first vehicle diagnostic management result is obtained.

[0128] Optionally, the vehicle diagnostic management result is a second vehicle diagnostic management result, and the diagnostic management module 30 is further used for:

[0129] When the data of the function to be executed is the preset second security level, the function management interface is set to whitelist mode to obtain the second function management interface;

[0130] Through the second function management interface, the corresponding diagnostic function is performed on the vehicle according to the diagnostic function instruction to be executed, using a preset whitelist method, to obtain the second vehicle diagnostic management result.

[0131] Optionally, the vehicle diagnostic management result is a third vehicle diagnostic management result, and the diagnostic management module 30 is further used for:

[0132] When the data of the function to be executed is the preset third security level, the function management interface is set to the disabled mode to obtain the third function management interface;

[0133] The third vehicle diagnostic management result is generated based on the third function management interface and the diagnostic function instruction to be executed.

[0134] Optionally, before the step of classifying the diagnostic function instructions to be executed based on pre-generated functional safety level data to obtain the functional safety level data to be executed, the method further includes:

[0135] Obtain the diagnostic function instruction dataset;

[0136] The diagnostic function instruction dataset is subjected to a functional evaluation to obtain functional evaluation data;

[0137] Based on preset fault mode data, risk analysis is performed on the diagnostic function instruction dataset to obtain risk analysis data;

[0138] Based on preset safety standard data, the diagnostic function instruction dataset is classified according to standard to obtain standard classification data;

[0139] The functional safety level data is generated based on the functional assessment data, risk analysis data, and standard classification data.

[0140] Optionally, before the step of performing vehicle diagnostic management based on the pre-built function management interface, according to the function level data to be executed and the diagnostic function instruction to be executed, and obtaining the vehicle diagnostic management result, the method further includes:

[0141] Create the initial function management interface;

[0142] In response to the pattern definition instruction, the initial function management interface is pattern defined to obtain the interface after pattern definition;

[0143] In response to the file management permission setting instruction, file management permissions are set on the interface defined in the mode to obtain the function management interface.

[0144] The vehicle diagnostic management device provided in this application, employing the vehicle diagnostic management method described in the above embodiments, can solve the technical problem of poor data security in existing diagnostic device USB security management methods. Compared with the prior art, the beneficial effects of the vehicle diagnostic management device provided in this application are the same as those of the vehicle diagnostic management method provided in the above embodiments, and other technical features in the vehicle diagnostic management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0145] This application provides a vehicle diagnostic management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the vehicle diagnostic management method in Embodiment 1 above.

[0146] The following is for reference. Figure 6 The diagram illustrates a structural schematic suitable for implementing vehicle diagnostic management equipment according to embodiments of this application. The vehicle diagnostic management equipment in embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The vehicle diagnostic management device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of this application.

[0147] like Figure 6As shown, the vehicle diagnostic management device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the vehicle diagnostic management device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows the vehicle diagnostic management device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows a vehicle diagnostic management device with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0148] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0149] The vehicle diagnostic management device provided in this application, employing the vehicle diagnostic management method described in the above embodiments, can solve the technical problem of poor data security in existing diagnostic device USB security management methods. Compared with the prior art, the beneficial effects of the vehicle diagnostic management device provided in this application are the same as those of the vehicle diagnostic management method provided in the above embodiments, and other technical features of this vehicle diagnostic management device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0150] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0151] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0152] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the vehicle diagnostic management method in the above embodiments.

[0153] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0154] The aforementioned computer-readable storage medium may be included in the vehicle diagnostic management device; or it may exist independently and not be installed in the vehicle diagnostic management device.

[0155] The aforementioned computer-readable storage medium carries one or more programs that, when executed by the vehicle diagnostic management device, cause the vehicle diagnostic management device to:

[0156] Receive instructions for diagnostic functions to be performed;

[0157] Based on pre-generated functional safety level data, the diagnostic function instructions to be executed are classified by safety level to obtain functional level data to be executed.

[0158] Based on the pre-built function management interface, vehicle diagnostic management is performed according to the data of the function level to be executed and the diagnostic function instructions to be executed, and the vehicle diagnostic management results are obtained.

[0159] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0160] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0161] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0162] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described vehicle diagnostic management method. This addresses the technical problem of poor data security in existing diagnostic device USB security management methods. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the vehicle diagnostic management method provided in the above embodiments, and will not be elaborated upon here.

[0163] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the vehicle diagnostic management method described above.

[0164] The computer program product provided in this application can solve the technical problem of poor data security in existing diagnostic device USB security management methods. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the vehicle diagnostic management method provided in the above embodiments, and will not be repeated here.

[0165] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A vehicle diagnostic management method, characterized in that, The method includes: Receive instructions for diagnostic functions to be performed; Based on pre-generated functional safety level data, the diagnostic function instructions to be executed are classified by safety level to obtain functional level data to be executed. This includes acquiring the diagnostic function instruction dataset; The diagnostic function instruction dataset is subjected to a functional evaluation to obtain functional evaluation data; Based on preset fault mode data, risk analysis is performed on the diagnostic function instruction dataset to obtain risk analysis data; Based on preset safety standard data, the diagnostic function instruction dataset is classified according to standard to obtain standard classification data; The functional safety level data is generated based on the functional assessment data, risk analysis data, and standard classification data. Based on a preset diagnostic protocol, function identification data is obtained according to the diagnostic function instruction to be executed; The function identification data is matched with the function safety level data to obtain the function level data to be executed; Based on the pre-built function management interface, vehicle diagnostic management is performed according to the data of the function level to be executed and the diagnostic function instructions to be executed, and the vehicle diagnostic management results are obtained. Wherein, when the function level data to be executed is the preset first security level, the function management interface is set to the unrestricted mode to obtain the first function management interface. The unrestricted mode is a mode that allows the function management interface to have full access to the function. Through the first function management interface, the corresponding diagnostic function is performed on the vehicle according to the diagnostic function instruction to be executed, and the first vehicle diagnostic management result is obtained; When the function level data to be executed is the preset second security level, the function management interface is set to whitelist mode to obtain the second function management interface. The whitelist mode is a mode that allows the function management interface to execute certified or approved functions. Through the second function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is executed on the vehicle using a preset whitelist method to obtain the second vehicle diagnostic management result; When the data of the function to be executed is the preset third security level, the function management interface is set to the disabled mode to obtain the third function management interface. The disabled mode is a mode that restricts the operation permissions of the function management interface. Based on the third function management interface and the diagnostic function instructions to be executed, a third vehicle diagnostic management result is generated.

2. The method as described in claim 1, characterized in that, Before the step of performing vehicle diagnostic management based on the pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instruction to be executed, and obtaining the vehicle diagnostic management result, the method further includes: Create the initial function management interface; In response to the pattern definition instruction, the initial function management interface is pattern defined to obtain the interface after pattern definition; In response to the file management permission setting instruction, file management permissions are set on the interface defined in the mode to obtain the function management interface.

3. A vehicle diagnostic management device, characterized in that, The device includes: The instruction receiving module is used to receive diagnostic function instructions to be executed. The safety level classification module is used to classify the diagnostic function instruction to be executed based on pre-generated functional safety level data to obtain the functional level data to be executed. The grade classification module is also used to obtain a diagnostic function instruction dataset; The diagnostic function instruction dataset is subjected to a functional evaluation to obtain functional evaluation data; Based on preset fault mode data, risk analysis is performed on the diagnostic function instruction dataset to obtain risk analysis data; Based on preset safety standard data, the diagnostic function instruction dataset is classified according to standard to obtain standard classification data; The functional safety level data is generated based on the functional assessment data, risk analysis data, and standard classification data. Based on a preset diagnostic protocol, function identification data is obtained according to the diagnostic function instruction to be executed; The function identification data is matched with the function safety level data to obtain the function level data to be executed; The diagnostic management module is used to perform vehicle diagnostic management based on the pre-built function management interface, according to the data of the function level to be executed and the diagnostic function instruction to be executed, and to obtain the vehicle diagnostic management result. The diagnostic management module is further configured to set the function management interface to an unrestricted mode when the data of the function to be executed is a preset first security level, thereby obtaining a first function management interface. The unrestricted mode is a mode that allows the function management interface to have full access to the function. Through the first function management interface, the corresponding diagnostic function is performed on the vehicle according to the diagnostic function instruction to be executed, and the first vehicle diagnostic management result is obtained; When the function level data to be executed is the preset second security level, the function management interface is set to whitelist mode to obtain the second function management interface. The whitelist mode is a mode that allows the function management interface to execute certified or approved functions. Through the second function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is executed on the vehicle using a preset whitelist method to obtain the second vehicle diagnostic management result; When the data of the function to be executed is the preset third security level, the function management interface is set to the disabled mode to obtain the third function management interface. The disabled mode is a mode that restricts the operation permissions of the function management interface. Based on the third function management interface and the diagnostic function instructions to be executed, a third vehicle diagnostic management result is generated.

4. A vehicle diagnostic management device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the vehicle diagnostic management method as described in any one of claims 1 to 2.

5. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the vehicle diagnostic management method as described in any one of claims 1 to 2.

Images