Vehicle diagnosis management method, device, equipment and computer program product
By receiving the diagnostic function instructions to be performed in the diagnostic device and the safety level classification, combined with the pre -constructed functional management interface setting function mode, the problem of poor data security of the diagnostic device in existing technologies has poor data security. Higher vehicle diagnosis and data transmission security.
Patent Information
- Application Number
- CN202411464705.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-18
- Publication Date
- 2025-01-24
- Estimated Expiration
- 2044-10-18
AI Technical Summary
The existing USB security management methods of diagnostic equipment have poor data security, and it is impossible to detect USB security vulnerabilities in time, which poses a risk of tampering with the diagnostic software.
By receiving the diagnostic function instructions to be executed, based on the pre-generated functional safety level data, the diagnostic function instructions to be executed are classified into safety levels to obtain the function level data to be executed; and then based on the pre-built function management interface, based on the function level data to be executed and The diagnostic function instructions to be executed perform vehicle diagnosis management and set the mode of the function management interface to limit the permissions of the USB interface to transmit data and files.
The security of vehicle diagnosis and data transmission is improved, and the problem of poor data security of the USB security management method in the existing technology is solved.
Smart Images

Figure CN119356284A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle diagnosis technology, and in particular to a vehicle diagnosis management method, device, equipment and computer program product. Background Art
[0002] At present, the USB port of the diagnostic equipment can copy various conventional files, which poses the risk of tampering with the diagnostic software. The existing USB security management method for diagnostic equipment is to regularly learn about the latest USB security vulnerabilities and promptly upgrade the secure USB firmware to improve security, but this method may not be able to detect USB security vulnerabilities in time, and the security is still poor.
[0003] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0004] The main purpose of this application is to provide a vehicle diagnostic management method, device, equipment and computer program product, aiming to solve the technical problem of poor data security in the existing diagnostic equipment USB security management method.
[0005] To achieve the above objectives, the present application proposes a vehicle diagnosis management method, the method comprising:
[0006] receiving a diagnostic function instruction to be executed;
[0007] Based on the pre-generated functional safety level data, the diagnostic function instruction to be executed is classified into a safety level to obtain the functional level data to be executed;
[0008] Based on the pre-built function management interface, vehicle diagnosis management is performed according to the to-be-executed function level data and the to-be-executed diagnostic function instructions to obtain a vehicle diagnosis management result.
[0009] In one embodiment, the step of classifying the diagnostic function instructions to be executed by security level based on the pre-generated functional safety level data and obtaining the functional level data to be executed includes:
[0010] Based on a preset diagnostic protocol, obtaining function identification data 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 to-be-executed function level data.
[0012] In one embodiment, the vehicle diagnostic management result is a first vehicle diagnostic management result, and the vehicle diagnostic management is performed based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction, and the step of obtaining the vehicle diagnostic management result includes:
[0013] When the to-be-executed function level data is a preset first security level, setting the function management interface to an unrestricted mode to obtain a first function management interface;
[0014] Through the first function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is executed on the vehicle to obtain the first vehicle diagnostic management result.
[0015] In one embodiment, the vehicle diagnostic management result is a second vehicle diagnostic management result, and the vehicle diagnostic management is performed based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction, and the step of obtaining the vehicle diagnostic management result includes:
[0016] When the to-be-executed function level data is a preset second security level, setting the function management interface to a whitelist mode to obtain a second function management interface;
[0017] 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.
[0018] In one embodiment, the vehicle diagnostic management result is a third vehicle diagnostic management result, and the vehicle diagnostic management is performed based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction, and the step of obtaining the vehicle diagnostic management result includes:
[0019] When the to-be-executed function level data is a preset third security level, setting the function management interface to a disabled mode to obtain a third function management interface;
[0020] The third vehicle diagnostic management result is generated according to the third function management interface and the diagnostic function instruction to be executed.
[0021] In one embodiment, the step of classifying the diagnostic function instructions to be executed by security level based on the pre-generated functional safety level data, and obtaining the functional level data to be executed further includes:
[0022] Get the diagnostic function instruction data set;
[0023] Performing a function evaluation on the diagnostic function instruction data set to obtain function evaluation data;
[0024] Based on the preset failure mode data, performing risk analysis on the diagnostic function instruction data set to obtain risk analysis data;
[0025] Based on preset safety standard data, standard classification is performed on the diagnostic function instruction data set to obtain standard classification data;
[0026] The functional safety level data is generated according to the functional assessment data, the risk analysis data and the standard classification data.
[0027] In one embodiment, the step of performing vehicle diagnostic management based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction and obtaining the vehicle diagnostic management result further includes:
[0028] Create the initial functional management interface;
[0029] In response to the mode definition instruction, the initial function management interface is mode-defined to obtain a mode-defined interface;
[0030] In response to the file management authority setting instruction, the file management authority is set for the interface after the mode definition to obtain the function management interface.
[0031] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle diagnosis management device, the vehicle diagnosis management device comprising:
[0032] An instruction receiving module, used for receiving a diagnostic function instruction to be executed;
[0033] A level classification module, used to classify the diagnostic function instructions to be executed based on pre-generated functional safety level data, and obtain the functional level data to be executed;
[0034] The diagnosis management module is used to perform vehicle diagnosis management based on a pre-built function management interface and according to the to-be-executed function level data and the to-be-executed diagnosis function instructions to obtain a vehicle diagnosis management result.
[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle diagnostic management device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the vehicle diagnostic management method described above.
[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the vehicle diagnostic management method described above are implemented.
[0037] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the vehicle diagnostic management method described above are implemented.
[0038] The present application provides a vehicle diagnostic management method, which classifies the security levels of diagnostic function instructions to be executed based on pre-generated functional safety level data to obtain the function level data to be executed; then based on a pre-constructed function management interface, performs vehicle diagnostic management according to the function level data to be executed and the diagnostic function instructions to be executed, and obtains a vehicle diagnostic management result. The function management interface sets the vehicle diagnostic mode according to the function level data to be executed, limits the permissions of the USB interface to transmit data and files, solves the problem of poor data security of the existing diagnostic device USB security management method, and improves the security of vehicle diagnosis and data transmission. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0041] Figure 1 A flow chart of the first embodiment of the vehicle diagnostic management method of the present application;
[0042] Figure 2 A flow chart of the second embodiment of the vehicle diagnostic management method of the present application;
[0043] Figure 3 A flowchart of the third embodiment of the vehicle diagnostic management method of the present application is provided;
[0044] Figure 4 A brief flowchart of the vehicle diagnostic management method provided in Example 3 of the present application;
[0045] Figure 5 This is a schematic diagram of the module structure of the vehicle diagnosis management device according to an embodiment of the present application;
[0046] Figure 6 Schematic diagram of the device structure of the hardware operating environment involved in the vehicle diagnostic management method in the embodiment of the present application.
[0047] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0048] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0049] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0050] The main solutions of the embodiments of this application are:
[0051] receiving a diagnostic function instruction to be executed;
[0052] Based on the pre-generated functional safety level data, the diagnostic function instruction to be executed is classified into a safety level to obtain the functional level data to be executed;
[0053] Based on the pre-built function management interface, vehicle diagnosis management is performed according to the to-be-executed function level data and the to-be-executed diagnostic function instructions to obtain a vehicle diagnosis management result.
[0054] In the prior art, the universal serial bus (USB) port of the diagnostic device can copy various conventional files, which poses a risk of tampering with the diagnostic software. The existing USB security management method for diagnostic devices is to regularly learn about the latest USB security vulnerabilities and promptly upgrade the secure USB firmware to improve security. However, this method may not be able to detect USB security vulnerabilities in a timely manner, and the security is still poor.
[0055] The present application provides a solution, which classifies the security levels of diagnostic function instructions to be executed based on pre-generated functional safety level data to obtain the function level data to be executed; then based on a pre-constructed function management interface, performs vehicle diagnosis management according to the function level data to be executed and the diagnostic function instructions to be executed, and obtains a vehicle diagnosis management result. The function management interface sets the vehicle diagnosis mode according to the function level data to be executed, limits the permissions of the USB interface to transmit data and files, solves the problem of poor data security of the existing diagnostic equipment USB security management method, and improves the security of vehicle diagnosis and data transmission.
[0056] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a vehicle diagnostic management system, etc. The following takes the vehicle diagnostic management system as an example to illustrate this embodiment and the following embodiments.
[0057] Based on this, the embodiment of the present application provides a vehicle diagnosis management method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle diagnosis management method of the present application.
[0058] In this embodiment, the vehicle diagnosis management method includes steps S10 to S30:
[0059] Step S10, receiving a diagnostic function instruction to be executed;
[0060] It should be noted that pending diagnostic function instructions usually refer to diagnostic operations that have not yet been executed but have been planned or prepared. These instructions usually 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 instruction to be executed according to the safety level, and 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, obtains the level data of the function to be executed, and determines its safety level. These levels may be divided according to 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. These data define the safety level requirements for different functions or diagnostic data in the system and usually come from system design documents, functional safety analysis reports or relevant safety standards.
[0064] Step S30, based on the pre-built function management interface, vehicle diagnosis management is performed according to the to-be-executed function level data and the to-be-executed diagnostic function instructions to obtain a vehicle diagnosis management result.
[0065] The vehicle diagnostic management system uses pre-designed functional management interfaces to execute diagnostic function instructions based on the function level data to be executed. These interfaces can perform corresponding management operations based on the security level of the data to ensure that the vehicle's diagnostic management is carried out in accordance with predetermined functional safety standards and requirements, thereby improving the safety and reliability of the vehicle and generating diagnostic management results.
[0066] It should be noted that the functional management interface refers to a system interface or module used to process and manage diagnostic data.
[0067] The present embodiment provides a vehicle diagnostic management method, which classifies the security levels of diagnostic function instructions to be executed based on pre-generated functional safety level data to obtain the function level data to be executed; then based on a pre-constructed function management interface, performs vehicle diagnostic management according to the function level data to be executed and the diagnostic function instructions to be executed, and obtains a vehicle diagnostic management result. The function management interface sets the vehicle diagnostic mode according to the function level data to be executed, limits the permissions of the USB interface to transmit data and files, solves the problem of poor data security of existing diagnostic equipment USB security management methods, and improves the security of vehicle diagnosis and data transmission.
[0068] In a feasible implementation manner, before step S30, steps S501 to S503 may also be included:
[0069] Step S501, creating an initial function management interface;
[0070] Step S502, in response to the mode definition instruction, the initial function management interface is mode-defined to obtain a mode-defined interface;
[0071] Step S503, in response to the file management authority setting instruction, setting the file management authority for the interface after the mode definition to obtain the function management interface.
[0072] The vehicle diagnostic management system creates an initial function management interface, which serves as the entry point for management and operating system functions. The interface refers to the standard for communication between different components in the system. Then, in response to the mode definition instruction, according to the mode definition instruction, the required interface behavior and characteristics are analyzed, and the mode definition of the initial function management interface is performed according to the analysis results, such as designing the mode structure, including the operation, state transition and business logic of each mode, determining the input and output requirements of the mode, and how to handle different requests and responses, etc., to obtain the interface after the mode definition, and finally in response to the file management permission setting instruction, the file management permission is set for the interface after the mode definition, such as identifying the files and resources involved in the interface, determining the specific scope of permissions to be set, understanding the access requirements and permission requirements of different users or roles for files, 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, to obtain 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. 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 the file management permission setting instruction ensures the security of the interface. By setting permissions, unauthorized access or operation is prevented, the risk of data leakage or misoperation is reduced, and the security of the system is improved. As a result, the management problems of the interface in terms of functions and permissions are solved. The mode definition and permission setting of the initial interface ensure the precise matching of functions and their security control, and avoid technical problems caused by interface function mismatch or improper permission setting. Through a systematic creation, definition and permission setting process, the efficiency and consistency of interface management can be improved, ensuring that the functions and security requirements of each interface are effectively implemented and managed.
[0075] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 Before step S20, the vehicle diagnosis management method may further include steps S401 to S405:
[0076] Step S401, obtaining a diagnostic function instruction data set;
[0077] Step S402, performing a function evaluation on the diagnostic function instruction data set to obtain function evaluation data;
[0078] Step S403, based on the preset failure mode data, performing risk analysis on the diagnostic function instruction data set to obtain risk analysis data;
[0079] Step S404, based on preset safety standard data, standard classification is performed on the diagnostic function instruction data set to obtain standard classification data;
[0080] Step S405 , generating the functional safety level data according to the functional evaluation data, risk analysis data and standard classification data.
[0081] The vehicle diagnostic management system obtains a diagnostic function instruction data set, and then performs a functional evaluation on the diagnostic function instruction data set to obtain functional evaluation data, wherein the functional evaluation may include performance evaluation, stability evaluation, and effectiveness evaluation, etc. Then, based on the preset failure mode data, a risk analysis is performed on the diagnostic function instruction data set to obtain risk analysis data, and then, based on the preset safety standard data, a standard classification is performed on the diagnostic function instruction data set to obtain standard classification data, and finally, the functional evaluation data, risk analysis data, and standard classification data are integrated to ensure the integrity and consistency of the data and obtain functional safety level data.
[0082] It should be noted that the diagnostic function instruction data set refers to a data set containing all relevant diagnostic function instructions and their parameters. These instructions are used to detect the functions, performance and potential failures of the system. Safety standard data may include regulations, industry standards, internal company standards, etc., such as ISO 26262 and other automotive industry safety standards.
[0083] In this embodiment, potential failure modes and risk points can be identified through risk analysis, and classification through preset safety standards can effectively improve the safety and protection capabilities of the system, ensuring that risks are minimized as much as possible during the diagnosis process. By obtaining diagnostic function instruction data sets, function evaluation, risk analysis and standard classification, the safety and reliability of diagnostic functions can be systematically evaluated. This multi-level analysis ensures a comprehensive review of the functions and classifies them as data that meets safety standards, ensuring that the final functional safety level data is accurate and meets preset standards. This solves the problems that may be missed by a single evaluation or classification method, and comprehensively evaluates functional data, risk analysis results and standard classification data to make the safety level of the diagnostic function more comprehensive and reliable, avoiding safety hazards caused by insufficient evaluation or inconsistent standards, and being able to systematically process and evaluate diagnostic functions, improving the accuracy and efficiency of the entire diagnostic process, thereby optimizing the diagnostic process and improving the overall performance and stability of the system.
[0084] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above description, and will not be described in detail later. Figure 3 , step S20 includes steps S201 to S202:
[0085] Step S201, based on a preset diagnostic protocol, obtaining 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 to-be-executed function level data.
[0087] The vehicle diagnostic management system uses the rules in the diagnostic protocol to parse the diagnostic function instructions to be executed. For example, if the protocol defines a certain format, the system will read the various fields in the instruction according to this format to obtain the function identification data, and then compare the function identification data with the function safety level data to find the corresponding relationship. This usually involves searching the database or using mapping rules to determine the safety level of each function identification 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 usually include data format specifications, parsing rules, field definitions, etc., which define the data format, processing methods, and how to extract function identifiers. Functional service data is identification information extracted from the function instructions to be executed according to the diagnostic protocol, and is used to uniquely identify the service function that needs to be diagnosed.
[0089] In a feasible implementation manner, 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 to-be-executed function level data is a preset first security level, setting the function management interface to an unrestricted mode to obtain a first function management interface;
[0091] Step S3012: Execute the corresponding diagnostic function on the vehicle through the first function management interface according to the diagnostic function instruction to be executed, and obtain the first vehicle diagnostic management result.
[0092] When the level 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 access to the function is not restricted, and obtains the first function management interface to ensure that when specific security level conditions are met, the function management interface can allow full access to the function in order to perform necessary operations, and then uses the first function management interface set to unrestricted mode to diagnose the vehicle according to the diagnostic function instructions to be executed, and obtain the first vehicle diagnostic management result.
[0093] It should be noted that the first security level is a preset security level standard used to determine whether unrestricted access is allowed, and the unrestricted mode is an interface setting that allows full access to functions.
[0094] In this implementation, when the to-be-executed function level data is the preset first safety level, the function management interface is set to an unrestricted mode to obtain a first function management interface; through the first function management interface, according to the to-be-executed diagnostic function instruction, the corresponding diagnostic function is executed on the vehicle to obtain the first vehicle diagnostic management result, and the interface management mode is dynamically adjusted according to the safety level of the function, thereby achieving flexible safety control. Through the first function management interface, comprehensive diagnosis can be ensured under unrestricted conditions, thereby improving the efficiency of function execution and the accuracy of the results. Therefore, diagnosis when set to unrestricted mode can avoid the problem of incomplete or inaccurate function execution due to management interface restrictions, thereby ensuring the comprehensiveness and accuracy of the diagnostic management results, thereby improving the overall effect of vehicle diagnosis.
[0095] In another feasible implementation manner, the vehicle diagnostic management result is a second vehicle diagnostic management result, and step S30 may include steps S3021-S3022:
[0096] Step S3021, when the to-be-executed function level data is a preset second security level, the function management interface is set to a whitelist mode to obtain a 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 executed on the vehicle using a preset whitelist method to obtain the second vehicle diagnostic management result.
[0098] When the data of the level of the function to be executed is the preset first security level, the vehicle diagnostic management system adjusts the function management interface to the whitelist mode to obtain the second function management interface to ensure that only approved functions can be executed, prevent unauthorized or potentially unsafe functions from accessing the system, and reduce security risks. Then, through the second function management interface, according to the diagnostic function instructions 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.
[0099] It should be noted that whitelist mode is a state of system configuration that allows pre-approved functions or operations to pass, while others are rejected. Whitelist mode is a mode that only allows authenticated or approved functions to be executed.
[0100] In this implementation, when the function level data to be executed is the preset second security level, the function management interface is set to the whitelist mode to obtain the second function management interface; through the second function management interface, according to the diagnostic function instructions 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 authenticated and secure functions or instructions to be executed through the interface while ensuring safety, clarifies the authority management, ensures that the execution of the function complies with the preset safety standards and specifications, ensures the security of the system when processing functions of specific security levels, solves the problem of insufficient security control that may exist in function management, and improves the accuracy of the diagnostic management results and the overall security of the system.
[0101] In another feasible implementation manner, the vehicle diagnostic management result is a third vehicle diagnostic management result, and step S30 may include steps S3031-S3032:
[0102] Step S3031, when the to-be-executed function level data is the preset third security level, setting the function management interface to a disabled mode to obtain a third function management interface;
[0103] Step S3032: Generate the third vehicle diagnostic management result according to the third function management interface and the diagnostic function instruction to be executed.
[0104] When the data of the function level to be executed is the preset third security level, the vehicle diagnostic management system switches the function management interface to the disabled mode and obtains the third function management interface to limit access rights to the interface, ensuring that when the function level reaches specific security requirements, the interface can be properly protected when executing high-security level functions to prevent unauthorized access. Finally, in the disabled mode, the third function management interface is used to process the diagnostic function instructions to be executed to generate the third vehicle diagnostic management result.
[0105] It should be noted that the disabled mode is a mode that limits the operation permissions of the functional management interface to prevent unauthorized access or operation.
[0106] In this implementation, when the data of the function level to be executed is the preset third security level, the function management interface is set to a disabled mode to obtain a third function management interface; based on 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 third function management interface in disabled mode ensures that only specific, authorized functions can be activated under the third security level, providing precise control and higher security protection, so that high-risk functions are strictly reviewed and verified before execution.
[0107] In this embodiment, based on the 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, thereby ensuring that each diagnostic function has an appropriate safety level and effectively improving the function execution accuracy of the system. By accurately obtaining the function level data to be executed, the system can perform corresponding safety control and protection according to preset safety standards, reduce potential risks caused by mismatch between function and safety level, and improve the overall safety and reliability of the system. In addition, by generating a third vehicle diagnostic management result, it is ensured that the diagnostic operation in the disabled mode meets the preset safety standards, thereby solving possible operational compliance issues and ensuring the legality and standardization of system operation.
[0108] For example, to help understand the implementation process of the vehicle diagnosis management method obtained by combining this embodiment with the above-mentioned embodiment 3, please refer to Figure 4 , Figure 4A brief flow chart of a vehicle diagnosis management method is provided. Specifically, taking the vehicle diagnosis management system as a diagnostic instrument as an example, the vehicle diagnosis 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 no restriction, 2 represents disabled, and 3 represents whitelist mode.
[0110] 2. The diagnostic instrument APK flexibly sets the current USB usage permissions based on the actual usage scenario.
[0111] Among them, the diagnostic instrument classifies the diagnostic functions according to different safety levels in advance, for example:
[0112] 2.1 Classify the service IDs 19, 14, 22, and 2F in the CAN protocol (ISO 14229) (performing basic diagnostic functions, such as reading codes, clearing codes, reading data streams, and actuation tests) as lower security levels. When the diagnostic instrument uses these commands to communicate with the vehicle, set the USB to unrestricted mode (set the interface parameter in step 1 to 1);
[0113] 2.2 Classify the service IDs in the CAN protocol such as 2E, 31, etc. (performing special diagnostic functions, such as writing some data to the ECU and executing advanced functions) as medium security level. When the diagnostic instrument uses these commands to communicate with the vehicle, set the USB to whitelist mode (set the interface parameter in step 1 to 3), and allow the file names allowed to be copied to be set in the background;
[0114] 2.3 Classify the service IDs 34, 36, 37, etc. (for flashing functions) in the CAN protocol as having a higher security level. When the diagnostic tool uses these commands to communicate with the vehicle, set the USB to disabled mode (set the interface parameter in step 1 to 2).
[0115] It should be noted that the service ID will be different for different diagnostic protocols.
[0116] The present embodiment provides a vehicle diagnostic management method, which classifies the security levels of diagnostic function instructions to be executed based on pre-generated functional safety level data to obtain the function level data to be executed; then based on a pre-constructed function management interface, performs vehicle diagnostic management according to the function level data to be executed and the diagnostic function instructions to be executed, and obtains a vehicle diagnostic management result. The function management interface sets the vehicle diagnostic mode according to the function level data to be executed, limits the permissions of the USB interface to transmit data and files, solves the problem of poor data security of existing diagnostic equipment USB security management methods, and improves the security of vehicle diagnosis and data transmission.
[0117] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the vehicle diagnostic management method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.
[0118] This application also provides a vehicle diagnostic management device, please refer to Figure 5 , the vehicle diagnosis management device comprises:
[0119] The instruction receiving module 10 is used to receive the diagnostic function instruction to be executed;
[0120] The level classification module 20 is used to classify the diagnostic function instruction to be executed based on the pre-generated functional safety level data, and obtain the functional level data to be executed;
[0121] The diagnosis management module 30 is used to perform vehicle diagnosis management based on a pre-built function management interface and according to the to-be-executed function level data and the to-be-executed diagnosis function instructions to obtain a vehicle diagnosis management result.
[0122] Optionally, the level classification module 20 is further used for:
[0123] Based on a preset diagnostic protocol, obtaining function identification data 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 to-be-executed function level data.
[0125] Optionally, the vehicle diagnosis management result is a first vehicle diagnosis management result, and the diagnosis management module 30 is further used to:
[0126] When the to-be-executed function level data is a preset first security level, setting the function management interface to an unrestricted mode to obtain a first function management interface;
[0127] Through the first function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is executed on the vehicle to obtain the first vehicle diagnostic management result.
[0128] Optionally, the vehicle diagnosis management result is a second vehicle diagnosis management result, and the diagnosis management module 30 is further used to:
[0129] When the to-be-executed function level data is a preset second security level, setting the function management interface to a whitelist mode to obtain a second function management interface;
[0130] 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.
[0131] Optionally, the vehicle diagnosis management result is a third vehicle diagnosis management result, and the diagnosis management module 30 is further used to:
[0132] When the to-be-executed function level data is a preset third security level, setting the function management interface to a disabled mode to obtain a third function management interface;
[0133] The third vehicle diagnostic management result is generated according to 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 by security level based on the pre-generated functional safety level data and obtaining the functional level data to be executed, the step further includes:
[0135] Get the diagnostic function instruction data set;
[0136] Performing a function evaluation on the diagnostic function instruction data set to obtain function evaluation data;
[0137] Based on the preset failure mode data, performing risk analysis on the diagnostic function instruction data set to obtain risk analysis data;
[0138] Based on preset safety standard data, standard classification is performed on the diagnostic function instruction data set to obtain standard classification data;
[0139] The functional safety level data is generated according to the functional assessment data, the risk analysis data and the standard classification data.
[0140] Optionally, before the step of performing vehicle diagnostic management based on the pre-built function management interface and the to-be-executed function level data and the to-be-executed diagnostic function instruction and obtaining the vehicle diagnostic management result, the step further includes:
[0141] Create the initial functional management interface;
[0142] In response to the mode definition instruction, the initial function management interface is mode-defined to obtain a mode-defined interface;
[0143] In response to the file management authority setting instruction, the file management authority is set for the interface after the mode definition to obtain the function management interface.
[0144] The vehicle diagnostic management device provided by the present application adopts the vehicle diagnostic management method in the above embodiment, which can solve the technical problem of poor data security of the existing diagnostic device USB security management method. Compared with the prior art, the beneficial effects of the vehicle diagnostic management device provided by the present application are the same as the beneficial effects of the vehicle diagnostic management method provided by the above embodiment, and the other technical features in the vehicle diagnostic management device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0145] The present application provides a vehicle diagnostic management device, which includes: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle diagnostic management method in the above-mentioned embodiment one.
[0146] Reference below Figure 6 , which shows a schematic diagram of the structure of a vehicle diagnostic management device suitable for implementing an embodiment of the present application. The vehicle diagnostic management device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The vehicle diagnostic management device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0147] like Figure 6As shown, the vehicle diagnostic management device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle diagnostic management device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the vehicle diagnostic management device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a vehicle diagnostic management device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.
[0148] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0149] The vehicle diagnostic management device provided by the present application adopts the vehicle diagnostic management method in the above embodiment, which can solve the technical problem of poor data security of the existing diagnostic device USB security management method. Compared with the prior art, the beneficial effects of the vehicle diagnostic management device provided by the present application are the same as the beneficial effects of the vehicle diagnostic management method provided by the above embodiment, and the other technical features in the vehicle diagnostic management device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0150] It should be understood that the various parts disclosed in this application can be implemented by 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 one or more embodiments or examples in a suitable manner.
[0151] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0152] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle diagnostic management method in the above-mentioned embodiment.
[0153] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. 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 combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0154] The computer-readable storage medium may be included in the vehicle diagnosis management device; or may exist independently without being assembled into the vehicle diagnosis management device.
[0155] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the vehicle diagnosis management device, the vehicle diagnosis management device:
[0156] receiving a diagnostic function instruction to be executed;
[0157] Based on the pre-generated functional safety level data, the diagnostic function instruction to be executed is classified into a safety level to obtain the functional level data to be executed;
[0158] Based on the pre-built function management interface, vehicle diagnosis management is performed according to the to-be-executed function level data and the to-be-executed diagnostic function instructions to obtain a vehicle diagnosis management result.
[0159] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may 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 possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0161] The modules involved in the embodiments of the present application may be implemented by software or hardware, wherein the name of the module does not limit the unit itself in some cases.
[0162] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle diagnostic management method, and can solve the technical problem of poor data security in the existing diagnostic device USB security management method. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle diagnostic management method provided by the above-mentioned embodiment, and will not be repeated here.
[0163] The present application also provides a computer program product, including a computer program, which implements the steps of the vehicle diagnostic management method as described above when executed by a processor.
[0164] The computer program product provided by the present application can solve the technical problem of poor data security of the existing diagnostic device USB security management method. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the vehicle diagnostic management method provided by the above embodiment, which will not be repeated here.
[0165] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A vehicle diagnosis management method, characterized in that: The method comprises: receiving a diagnostic function instruction to be executed; Based on the pre-generated functional safety level data, the diagnostic function instruction to be executed is classified into a safety level to obtain the functional level data to be executed; Based on the pre-built function management interface, vehicle diagnosis management is performed according to the to-be-executed function level data and the to-be-executed diagnostic function instructions to obtain a vehicle diagnosis management result.
2. The method according to claim 1, characterized in that The step of classifying the diagnostic function instructions to be executed by security level based on the pre-generated functional safety level data and obtaining the functional level data to be executed comprises: Based on a preset diagnostic protocol, obtaining function identification data according to the diagnostic function instruction to be executed; The function identification data is matched with the function safety level data to obtain the to-be-executed function level data.
3. The method according to claim 1, characterized in that The vehicle diagnostic management result is a first vehicle diagnostic management result. The vehicle diagnostic management is performed based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction. The step of obtaining the vehicle diagnostic management result includes: When the to-be-executed function level data is a preset first security level, setting the function management interface to an unrestricted mode to obtain a first function management interface; Through the first function management interface, according to the diagnostic function instruction to be executed, the corresponding diagnostic function is executed on the vehicle to obtain the first vehicle diagnostic management result.
4. The method according to claim 1, characterized in that The vehicle diagnostic management result is a second vehicle diagnostic management result. The vehicle diagnostic management is performed based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction. The step of obtaining the vehicle diagnostic management result includes: When the to-be-executed function level data is a preset second security level, setting the function management interface to a whitelist mode to obtain a 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 a preset whitelist method to obtain the second vehicle diagnostic management result.
5. The method according to claim 1, characterized in that The vehicle diagnostic management result is a third vehicle diagnostic management result. The vehicle diagnostic management is performed based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction. The step of obtaining the vehicle diagnostic management result includes: When the to-be-executed function level data is a preset third security level, setting the function management interface to a disabled mode to obtain a third function management interface; The third vehicle diagnostic management result is generated according to the third function management interface and the diagnostic function instruction to be executed.
6. The method according to claim 1, characterized in that The step of classifying the diagnostic function instructions to be executed by security level based on the pre-generated functional safety level data and obtaining the functional level data to be executed also includes: Get the diagnostic function instruction data set; Performing a function evaluation on the diagnostic function instruction data set to obtain function evaluation data; Based on the preset failure mode data, performing risk analysis on the diagnostic function instruction data set to obtain risk analysis data; Based on preset safety standard data, standard classification is performed on the diagnostic function instruction data set to obtain standard classification data; The functional safety level data is generated according to the functional assessment data, the risk analysis data and the standard classification data.
7. The method according to claim 1, characterized in that Before the step of performing vehicle diagnostic management based on the pre-built function management interface according to the to-be-executed function level data and the to-be-executed diagnostic function instruction and obtaining the vehicle diagnostic management result, the step further includes: Create the initial functional management interface; In response to the mode definition instruction, the initial function management interface is mode-defined to obtain a mode-defined interface; In response to the file management authority setting instruction, the file management authority is set for the interface after the mode definition to obtain the function management interface.
8. A vehicle diagnostic management device, characterized in that: The device comprises: An instruction receiving module, used for receiving a diagnostic function instruction to be executed; A level classification module, used to classify the diagnostic function instructions to be executed based on pre-generated functional safety level data, and obtain the functional level data to be executed; The diagnosis management module is used to perform vehicle diagnosis management based on a pre-built function management interface and according to the to-be-executed function level data and the to-be-executed diagnosis function instructions to obtain a vehicle diagnosis management result.
9. A vehicle diagnostic management device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the vehicle diagnosis management method according to any one of claims 1 to 7.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the vehicle diagnosis management method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Diagnostic data acquisition control device and control method
CN111045419A
Information security diagnosis method and device
CN117240587A
Vehicle intrusion detection and defense system based on AutoSAR CP
CN117879915A
Vehicle diagnosis method, device and equipment, storage medium and computer program product
CN118338347A
System and method for coordinating operation control and operation maintenance for urban rail transit
US20220317673A1
