Diagnostic database matching method, system and device for a vehicle

Abstract

This application discloses a method, system, and device for matching vehicle diagnostic databases. The method includes: acquiring a vehicle broadcast file, wherein the broadcast file includes the name and feature code of the vehicle controller; filtering candidate diagnostic database files from a diagnostic database based on the name of the vehicle controller, wherein each candidate diagnostic database file includes a corresponding feature code; when there are multiple candidate diagnostic database files, performing a consistency judgment between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file; and determining the final diagnostic database file based on the consistency judgment result. Using this application effectively improves the accuracy of diagnostic database matching, enhances diagnostic efficiency, improves system compatibility, and reduces maintenance costs.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method, system and device for matching vehicle diagnostic databases. Background Technology

[0002] In the development and after-sales diagnostics of vehicle electronic control units (ECUs), the same controller is often developed by different manufacturers in terms of both hardware and software, resulting in differences in the content of their diagnostic databases. Traditional diagnostic tools typically rely on manual selection or simple filename matching when matching diagnostic databases, which cannot effectively distinguish between multiple database versions of the same controller corresponding to different manufacturers or platforms. This can easily lead to diagnostic errors, inefficiency, and even system failures.

[0003] In existing technologies, the identification of diagnostic databases is mostly based on direct matching of controller names (ECUNAME). When there are multiple database files with the same name but incompatible content, the system cannot automatically select the correct version, requiring manual intervention, which reduces the automation and reliability of diagnosis. Summary of the Invention

[0004] Therefore, it is necessary to address the aforementioned technical issues by providing a vehicle diagnostic database matching method, system, and device. This effectively improves the accuracy of diagnostic database matching; specifically, through dual matching of controller names and feature codes, it can accurately distinguish diagnostic databases from different manufacturers or versions, avoiding mismatches. It also enhances diagnostic efficiency, as the automated matching process effectively reduces manual intervention and shortens diagnostic preparation time, making it particularly suitable for complex vehicle platforms with multiple models and configurations. Furthermore, it enhances system compatibility by supporting various logical operators, handling complex feature code combinations, and adapting to different development specifications and platform differences. Finally, it reduces maintenance costs, as standardized file naming and matching logic simplify database updates and expansions, facilitating long-term maintenance and upgrades.

[0005] Firstly, a method for matching vehicle diagnostic databases is provided, including: Obtain the vehicle's broadcast file, wherein the broadcast file includes the name and signature code of the vehicle controller; Based on the name of the vehicle controller, candidate diagnostic database files are selected from the diagnostic database, wherein each candidate diagnostic database file includes a corresponding feature code; When there are multiple candidate diagnostic database files, a consistency judgment is made between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file. Based on the consistency assessment results, the final diagnostic database file is determined.

[0006] In some examples, after filtering candidate diagnostic database files from the diagnostic database based on the name of the vehicle controller, the process further includes: When there is only one candidate diagnostic data file, the candidate diagnostic data file is used as the final diagnostic data file; If the candidate diagnostic data file does not exist, a message indicating that no diagnostic data file was found will be displayed.

[0007] In some examples, when there are multiple candidate diagnostic database files, the consistency determination based on the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file includes: Compare the logical relationship between the feature codes carried in the broadcast file and the feature codes of each candidate diagnostic database file; If the logical relationships are inconsistent, the corresponding candidate diagnostic database file is removed; otherwise, the corresponding candidate diagnostic database file is retained.

[0008] In some examples, logical relations include at least one or a combination of logical include, logical AND, logical OR, and logical NOT.

[0009] In some examples, determining the final diagnostic database file based on the consistency assessment results includes: Determine whether the retained candidate diagnostic database file is unique; If so, the only remaining candidate diagnostic database file will be used as the final diagnostic database file; If it is not unique, then a warning will be given indicating that the diagnostic database is not unique; If no candidate diagnostic database file is retained, a message indicating that no diagnostic data file was matched will be displayed.

[0010] In some examples, before filtering candidate diagnostic database files from the diagnostic database based on the name of the vehicle controller, the process further includes: The diagnostic database files in the diagnostic database are named according to the file naming convention.

[0011] In some examples, the file naming includes a combination of control names, fixed identifiers, and signature codes.

[0012] Secondly, a vehicle diagnostic database matching system is provided, including: An acquisition module is used to acquire the vehicle's broadcast file, wherein the broadcast file includes the name and characteristic code of the vehicle controller; The filtering module is used to filter candidate diagnostic database files from the diagnostic database according to the name of the vehicle controller, wherein each candidate diagnostic database file includes a corresponding feature code; The judgment module is used to determine the consistency between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file when there are multiple candidate diagnostic database files. The determination module is used to determine the final diagnostic database file based on the consistency judgment results.

[0013] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the steps of the vehicle diagnostic database matching method of the first aspect and any possible implementation thereof.

[0014] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the vehicle diagnostic database matching method of the first aspect and any possible implementation thereof.

[0015] Fifthly, a computer program product is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the vehicle diagnostic database matching method of the first aspect and any possible implementation thereof.

[0016] The embodiments of this application allow for the selection of candidate diagnostic database files from a diagnostic database based on the acquired vehicle broadcast files. Then, a consistency judgment is performed between the feature codes carried in the broadcast files and the feature codes of each candidate diagnostic database file. Finally, the final diagnostic database file is determined based on the consistency judgment result. This effectively improves the accuracy of diagnostic database matching; by using dual matching of controller names and feature codes, it can accurately distinguish diagnostic databases from different manufacturers or versions, avoiding mismatches. It also improves diagnostic efficiency, as the automated matching process effectively reduces manual intervention and shortens diagnostic preparation time, making it particularly suitable for complex vehicle platforms with multiple models and configurations. Furthermore, it enhances system compatibility by supporting multiple logical operators, enabling the handling of complex feature code combinations, and adapting to different development specifications and platform differences. Finally, it reduces maintenance costs, as standardized file naming and matching logic simplifies database updates and expansions, facilitating long-term maintenance and upgrades. Attached Figure Description

[0017] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 A flowchart illustrating the vehicle diagnostic database matching method provided in this application embodiment; Figure 2 A structural block diagram of the vehicle diagnostic database matching system provided in this application embodiment; Figure 3 This is a structural block diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0018] The present application will now be described in further detail with reference to the embodiments and accompanying drawings. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the application. Furthermore, it should be noted that, for ease of description, only the parts relevant to the application are shown in the accompanying drawings.

[0019] It should be noted that, unless otherwise specified, the embodiments and features of the embodiments in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0020] The diagnostic database matching method, system, and device for vehicles according to embodiments of this application are described in detail below with reference to the accompanying drawings.

[0021] The embodiments of this application, through standardized diagnostic database file naming, can perform dual filtering during matching by combining the logical relationship between controller name and feature code. This enables automatic and accurate identification of the diagnostic database version applicable to a specific vehicle controller, effectively solving database compatibility issues caused by different manufacturers' development. This improves the automation and reliability of diagnostics, and is suitable for vehicle manufacturing and after-sales diagnostic services.

[0022] Figure 1 This is a flowchart of a vehicle diagnostic database matching method according to an embodiment of this application. Figure 1 As shown, the vehicle diagnostic database matching method according to an embodiment of this application includes the following steps: S101: Obtain the vehicle's broadcast file, wherein the broadcast file includes the name and signature code of the vehicle controller.

[0023] For example, using a diagnostic tool, a broadcast file of the vehicle is obtained from the vehicle manufacturing system via a wireless network. This broadcast file contains the controller name ECUNAME on the vehicle and its corresponding feature code, wherein the corresponding feature code is preset.

[0024] S102: Based on the name of the vehicle controller, candidate diagnostic database files are selected from the diagnostic database, wherein each candidate diagnostic database file includes a corresponding feature code.

[0025] The diagnostic database for each vehicle controller is stored as an independent file, named in the format: "ECUNAME"_"feature"_"feature codes", where: ECUNAME is the controller name; The feature is a fixed identifier; Feature codes are characteristic codes that support various logical operators, such as parentheses "()", logical AND or &, logical OR or / , logical NOT or !", etc. As a concrete example, the filename of a vehicle controller might be ADCU3_feature_ZR02 or ZR03.xlsm, where ADCU3 is the name of the vehicle controller, feature is a fixed identifier, and ZR02 or ZR03 are the feature codes for that file.

[0026] In other words, before selecting candidate diagnostic database files from the diagnostic database based on the name of the vehicle controller, the process also includes: naming each diagnostic database file in the diagnostic database according to a file naming convention, such as ADCU3_feature_ZR02 or ZR03.xlsm as mentioned above. That is, the file name includes a combination of the control name, a fixed identifier, and a feature code.

[0027] S103: When there are multiple candidate diagnostic database files, a consistency judgment is made between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file.

[0028] In one embodiment of this application, when there are multiple candidate diagnostic database files, the consistency judgment based on the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file includes: comparing the logical relationship between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file; if the logical relationship is inconsistent, the corresponding candidate diagnostic database file is removed; otherwise, the corresponding candidate diagnostic database file is retained.

[0029] In the above description, logical relationships include, but are not limited to, at least one or a combination of logical include, logical AND, logical OR, and logical NOT.

[0030] Of course, in another example of this application, it also includes: when there is only one candidate diagnostic data file, using the candidate diagnostic data file as the final diagnostic data file; and when there is no candidate diagnostic data file, providing a prompt that no diagnostic data file was matched.

[0031] S104: Based on the consistency judgment results, determine the final diagnostic database file.

[0032] In one embodiment of this application, determining the final diagnostic database file based on the consistency judgment result includes: determining whether the retained candidate diagnostic database files are unique; if so, using the retained unique candidate diagnostic database file as the final diagnostic database file; if not unique, providing a prompt that the diagnostic database is not unique; if no retained candidate diagnostic database files are found, providing a prompt that no diagnostic data file was matched.

[0033] Specifically, based on the vehicle controller name ECUNAME in the broadcast file, all files with the same ECUNAME in their filenames are filtered in the diagnostic database file library.

[0034] If the screening result contains only one diagnostic database file, it is directly determined to be the correct database corresponding to the controller, and the match is successful; if the screening result contains multiple diagnostic database files, the feature code in the broadcast file is logically compared with the feature code in each candidate database file name: If there is one and only one candidate file whose filename feature code is logically identical to the feature code in the broadcast file, it is determined to be the correct database for the controller; if multiple candidate files all satisfy the logical relationship, the message "Diagnostic database is not unique" is output; if all candidate files do not satisfy the logical relationship, the message "No diagnostic database matched" is output.

[0035] In the above description, the supported logical operators for comparing feature codes include: Parentheses “()”: indicate logical inclusion and are used to combine complex logical conditions; Logical AND ("and" or "&"): indicates that multiple conditions must be met simultaneously; Logical OR ("or" or " / "): indicates that at least one of the conditions must be met. Logical NOT ("not") or "!": indicates that the condition is negated.

[0036] The diagnostic database file is in Excel format (e.g., .xlsm), which facilitates development and maintenance.

[0037] The vehicle diagnostic database matching method according to embodiments of this application can filter candidate diagnostic database files from the diagnostic database based on the acquired vehicle broadcast file. Then, it performs a consistency judgment between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file. Finally, based on the consistency judgment result, the final diagnostic database file is determined. This effectively improves the accuracy of diagnostic database matching, namely, by using dual matching of controller name and feature code, it can accurately distinguish diagnostic databases from different manufacturers or versions, avoiding mismatches. It can also improve diagnostic efficiency, namely, the automated matching process effectively reduces manual intervention and shortens diagnostic preparation time, especially suitable for complex vehicle platforms with multiple models and configurations. It enhances system compatibility, namely, it supports multiple logical operators, can handle complex feature code combinations, and adapts to different development specifications and platform differences. It reduces maintenance costs, namely, the standardized file naming and matching logic makes database updates and expansions easier, which is beneficial for long-term maintenance and upgrades.

[0038] Figure 2 This is a structural block diagram of a vehicle diagnostic database matching system according to an embodiment of this application. Figure 2 As shown, a vehicle diagnostic database matching system according to an embodiment of this application includes: an acquisition module 210, a filtering module 220, a judgment module 230, and a determination module 240, wherein: The acquisition module 210 is used to acquire the vehicle's broadcast file, wherein the broadcast file includes the name and feature code of the vehicle controller; The filtering module 220 is used to filter candidate diagnostic database files from the diagnostic database according to the name of the vehicle controller, wherein each candidate diagnostic database file includes a corresponding feature code; The judgment module 230 is used to make a consistency judgment based on the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file when there are multiple candidate diagnostic database files. The determination module 240 is used to determine the final diagnostic database file based on the consistency judgment results.

[0039] The vehicle diagnostic database matching system according to embodiments of this application can filter candidate diagnostic database files from the diagnostic database based on the acquired vehicle broadcast files. Then, it performs a consistency judgment between the feature codes carried in the broadcast files and the feature codes of each candidate diagnostic database file. Finally, based on the consistency judgment result, the final diagnostic database file is determined. This effectively improves the accuracy of diagnostic database matching, namely, by using dual matching of controller names and feature codes, it can accurately distinguish diagnostic databases from different manufacturers or versions, avoiding mismatches. It also improves diagnostic efficiency, namely, the automated matching process effectively reduces manual intervention and shortens diagnostic preparation time, especially suitable for complex vehicle platforms with multiple models and configurations. It enhances system compatibility, namely, it supports multiple logical operators, can handle complex feature code combinations, and adapts to different development specifications and platform differences. It reduces maintenance costs, namely, the standardized file naming and matching logic makes database updates and expansions easier, which is beneficial for long-term maintenance and upgrades.

[0040] Specific limitations regarding the vehicle diagnostic database matching system can be found in the limitations of the vehicle diagnostic database matching method described above, and will not be repeated here. Each module of the aforementioned vehicle diagnostic database matching system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the computer device's memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0041] In one embodiment, a computer device is provided. Figure 3 This is a structural block diagram of the computer device provided in the embodiments of this application, with reference to... Figure 3 The computer device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned vehicle diagnostic database matching method embodiment. For example, it executes: acquiring a vehicle broadcast file, wherein the broadcast file includes the name and characteristic code of the vehicle controller; Based on the name of the vehicle controller, candidate diagnostic database files are selected from the diagnostic database, wherein each candidate diagnostic database file includes a corresponding feature code; When there are multiple candidate diagnostic database files, a consistency judgment is made between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file. Based on the consistency assessment results, the final diagnostic database file is determined.

[0042] This application also provides a computer-readable storage medium storing a computer program. When a processor executes the computer program, it implements the aforementioned vehicle diagnostic database matching method embodiment. For example, it executes: obtaining a vehicle broadcast file, wherein the broadcast file includes the name and characteristic code of the vehicle controller; Based on the name of the vehicle controller, candidate diagnostic database files are selected from the diagnostic database, wherein each candidate diagnostic database file includes a corresponding feature code; When there are multiple candidate diagnostic database files, a consistency judgment is made between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file. Based on the consistency assessment results, the final diagnostic database file is determined.

[0043] This application provides a computer program product including instructions that, when executed, cause the method described in this application embodiment to be performed. For example, it can execute... Figure 1 The steps of the vehicle diagnostic database matching method shown include, for example, obtaining the vehicle's broadcast file, wherein the broadcast file includes the name and characteristic code of the vehicle controller; Based on the name of the vehicle controller, candidate diagnostic database files are selected from the diagnostic database, wherein each candidate diagnostic database file includes a corresponding feature code; When there are multiple candidate diagnostic database files, a consistency judgment is made between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file. Based on the consistency assessment results, the final diagnostic database file is determined.

[0044] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0045] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0046] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A diagnostic database matching method of a vehicle, characterized by, include: Obtain the vehicle's broadcast file, wherein the broadcast file includes the name and signature code of the vehicle controller; Based on the name of the vehicle controller, candidate diagnostic database files are selected from the diagnostic database, wherein each candidate diagnostic database file includes a corresponding feature code; When there are multiple candidate diagnostic database files, a consistency judgment is made between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file. Based on the consistency assessment results, the final diagnostic database file is determined.

2. The diagnostic database matching method of a vehicle according to claim 1, characterized by, After filtering candidate diagnostic database files from the diagnostic database based on the name of the vehicle controller, the process further includes: When there is only one candidate diagnostic data file, the candidate diagnostic data file is used as the final diagnostic data file; If the candidate diagnostic data file does not exist, a message indicating that no diagnostic data file was found will be displayed.

3. The diagnostic database matching method of a vehicle according to claim 1, characterized by, When there are multiple candidate diagnostic database files, the consistency judgment based on the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file includes: Compare the logical relationship between the feature codes carried in the broadcast file and the feature codes of each candidate diagnostic database file; If the logical relationships are inconsistent, the corresponding candidate diagnostic database file is removed; otherwise, the corresponding candidate diagnostic database file is retained.

4. The diagnostic database matching method of a vehicle according to claim 3, characterized by, Logical relations include at least one or a combination of logical include, logical AND, logical OR, and logical NOT.

5. The diagnostic database matching method of a vehicle according to claim 3, characterized by, The step of determining the final diagnostic database file based on the consistency judgment result includes: Determine whether the retained candidate diagnostic database file is unique; If so, the only remaining candidate diagnostic database file will be used as the final diagnostic database file; If it is not unique, then a warning will be given indicating that the diagnostic database is not unique; If no candidate diagnostic database file is retained, a message indicating that no diagnostic data file was matched will be displayed.

6. The diagnostic database matching method of a vehicle according to any one of claims 1 to 5, characterized in that, Before filtering candidate diagnostic database files from the diagnostic database based on the name of the vehicle controller, the process also includes: The diagnostic database files in the diagnostic database are named according to the file naming convention.

7. The diagnostic database matching method of a vehicle according to claim 6, characterized by, The file naming includes a combination of control name, fixed identifier, and characteristic code.

8. A diagnostic database matching system for a vehicle, characterized by include: An acquisition module is used to acquire the vehicle's broadcast file, wherein the broadcast file includes the name and characteristic code of the vehicle controller; The filtering module is used to filter candidate diagnostic database files from the diagnostic database according to the name of the vehicle controller, wherein each candidate diagnostic database file includes a corresponding feature code; The judgment module is used to determine the consistency between the feature code carried in the broadcast file and the feature code of each candidate diagnostic database file when there are multiple candidate diagnostic database files. The determination module is used to determine the final diagnostic database file based on the consistency judgment results.

9. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the vehicle diagnostic database matching method according to any one of claims 1-7.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, When the computer program is executed by the processor, it implements the vehicle diagnostic database matching method according to any one of claims 1-7.

Images