Data import method and device, computer equipment and computer readable storage medium

By automatically importing the diagnostic update data after checking the form and content of the diagnostic update data, the problems of low update efficiency and poor accuracy in the existing technology are solved, and efficient and accurate diagnostic update data import is achieved.

CN118938861APending Publication Date: 2024-11-12CHINA FAW CO LTD
View PDF 13 Cites 0 Cited by

Patent Information

Application Number
CN202411000787.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-24
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The prior art is inefficient and prone to errors when updating the DCT list in the automotive electronic control module (ECU) diagnostic instrument, and cannot guarantee the accuracy of the update.

Method used

By obtaining the diagnostic update data of the diagnostic instrument, conducting a form check of the controller identification and fault position code, as well as the content check of the fault type code and fault description data, the diagnostic instrument will only be imported when the inspection results are passed to avoid incorrect import.

Benefits of technology

It realizes automatic import of diagnostic update data, improves update efficiency and accuracy, and avoids importing of form and content errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118938861A_ABST
    Figure CN118938861A_ABST
Patent Text Reader

Abstract

The invention relates to a data importing method and device, computer equipment and a computer readable storage medium. The method comprises the following steps: acquiring diagnosis update data of a diagnostic instrument; performing form check on the controller identifier of the controller and the corresponding fault part code to obtain a form check result of the diagnosis update data; performing content inspection on the fault type code and the fault description data to obtain a content inspection result of the diagnosis update data; and if the formal inspection result and the content inspection result both indicate that the inspection is passed, the diagnosis update data is imported into the diagnostic instrument. By adopting the method, the import efficiency of the diagnosis update data can be improved, the diagnosis update data with form errors and content errors are prevented from being imported into the diagnosis instrument, and the import accuracy of the diagnosis update data is further improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data import method, device, computer equipment and computer-readable storage medium. Background Art

[0002] As automotive technology develops towards intelligence, networking, electrification and sharing, the functions that cars can provide are becoming more comprehensive. In order to better realize multi-dimensional functions such as intelligent driving, intelligent enjoyment and intelligent control, more and more automotive electronic control modules (Engine Control Unit, ECU) are installed in cars. In this case, OEM (Original Equipment Manufacturer) and ECU suppliers will formulate a DCT (Diagnostic Trouble Code) list and import the DCT list into the ODX (Open Diagnostic Data Exchange) file of the diagnostic instrument. Fault detection personnel can diagnose ECU faults based on the DCT in the diagnostic instrument. However, whenever the DCT list is updated, the DCT list needs to be re-imported into the diagnostic instrument to update the DCT in the diagnostic instrument.

[0003] At present, the updated DCT list is generally imported into the diagnostic instrument manually to update the DCT in the diagnostic instrument. However, a large number of repeated operations are required to manually update the DCT in the diagnostic instrument, which has a low update efficiency. In addition, during the update process, it is easy to import the wrong DCT into the diagnostic instrument, and the update accuracy cannot be guaranteed. Summary of the invention

[0004] Based on this, it is necessary to provide a data import method, device, computer equipment and computer-readable storage medium to address the above technical problems, so as to improve the data update efficiency and reduce the update error rate.

[0005] In a first aspect, the present application provides a data import method, comprising:

[0006] Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0007] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0008] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0009] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0010] In one of the embodiments, a formal check is performed on the controller identification and the corresponding fault location code of the controller to obtain the formal check result of the diagnostic update data, including: determining the formal check result of the diagnostic update data based on the controller identification of the controller in the first mapping relationship table and the search and match of the fault location code corresponding to the controller.

[0011] In one of the embodiments, a formal check result of the diagnostic update data is determined based on the controller identifier of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller, including: if the controller identifier is not found in the first mapping relationship table, a first formal check result of the unknown controller is generated; if the controller identifier of the controller is found in the first mapping relationship table, a second formal check result of the diagnostic update data is generated based on the match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table.

[0012] In one of the embodiments, a second form of inspection result of the diagnostic update data is generated based on the match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table, including: if the controller identifier of the controller is found from the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table, then a second form of inspection result is generated that the fault code does not correspond to the controller; if the controller identifier of the controller is found from the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping relationship table, then a second form of inspection result is generated that the fault code corresponds to the controller.

[0013] In one of the embodiments, a content check is performed on the fault type code and the fault description data to obtain a content check result of the diagnostic update data, including: extracting component description data corresponding to the fault component code from the fault description data; wherein the fault component code includes a fault location code and a fault type code; and determining the content check result of the diagnostic update data based on the search and match of the fault component code and the corresponding component description data in the second mapping relationship table.

[0014] In one of the embodiments, the content check result of the diagnostic update data is determined based on the search and matching of the fault component code and the corresponding component description data in the second mapping relationship table, including: if the fault component code is not found in the second mapping relationship table, a first content check result of the unknown fault component is generated; if the fault component code is found in the second mapping relationship table, a second content check result of the diagnostic update data is determined based on the match between the component description data and the standard description data corresponding to the fault component code in the second mapping relationship table.

[0015] In one of the embodiments, a second content check result of the diagnostic update data is determined based on a match between the component description data and the standard description data corresponding to the fault component code in the second mapping relationship table, including: if the fault component code is found from the second mapping relationship table, but the component description data and the standard description data corresponding to the fault component code in the second mapping relationship table do not match, then a second content check result is generated in which the fault component code does not correspond to the component description data; if the fault component code is found from the second mapping relationship table, and the component description data matches the standard description data corresponding to the fault component code in the second mapping relationship table, then a second content check result is generated in which the fault component code corresponds to the component description data.

[0016] In a second aspect, the present application also provides a data import device, comprising:

[0017] An acquisition module, used for acquiring diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0018] A formal inspection module, used for performing a formal inspection on a controller identification and a corresponding fault location code of the controller to obtain a formal inspection result of the diagnosis update data;

[0019] A content inspection module is used to perform content inspection on the fault type code and the fault description data to obtain a content inspection result of the diagnosis update data;

[0020] The import module is used to import the diagnostic update data into the diagnostic instrument if both the form inspection result and the content inspection result indicate that the inspection is passed.

[0021] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0022] Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0023] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0024] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0025] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0026] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0027] Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0028] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0029] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0030] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0031] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0032] Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0033] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0034] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0035] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0036] The above-mentioned data import method, device, computer equipment and computer-readable storage medium obtain the diagnostic update data of the diagnostic instrument; perform a formal check on the controller identification and the corresponding fault location code of the controller to obtain the formal check result of the diagnostic update data; perform a content check on the fault type code and the fault description data to obtain the content check result of the diagnostic update data; if the formal check result and the content check result both indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument. By executing the above-mentioned method, the automatic import of the diagnostic update data can be realized, and compared with the method of manually importing the diagnostic update data in the prior art, the import efficiency of the diagnostic update data can be improved. In the above-mentioned method, the diagnostic update data is respectively subjected to a formal check and a content check, and the diagnostic update data is imported into the diagnostic instrument only on the premise that the diagnostic update data passes the formal check and the content check, which can avoid the diagnostic update data with formal errors and content errors from being imported into the diagnostic instrument, thereby improving the import accuracy of the diagnostic update data. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 1 A schematic diagram of a flow chart of a data import method in one embodiment;

[0039] Figure 2 A schematic flow chart of a step of determining a form check result in one embodiment;

[0040] Figure 3 A flowchart of a step of determining a content inspection result in one embodiment;

[0041] Figure 4 A schematic diagram of a flow chart of a data import method in another embodiment;

[0042] Figure 5 is a structural block diagram of a data import device in an embodiment;

[0043] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0045] In one embodiment, Figure 1 As shown, a data import method is provided. This embodiment uses the method applied to a terminal as an example for illustration. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0046] S110, obtaining diagnostic update data of the diagnostic instrument.

[0047] Among them, the diagnostic instrument can be understood as an instrument used to diagnose the fault condition of the ECU (Engine Control Unit). A vehicle can be equipped with at least one ECU, and each ECU can include at least one controller for controlling and managing the vehicle system. Each ECU can generate actual diagnostic data based on the actual operating data of each controller. The actual diagnostic data can be understood as the diagnostic data corresponding to the fault condition that may actually exist in the ECU. The diagnostic update data can be understood as the update data used to update the diagnostic reference data in the diagnostic instrument. The diagnostic reference data can be understood as the reference data used to determine the fault condition represented by the actual diagnostic data. It can be supplemented that the diagnostic instrument can obtain the actual diagnostic data of each ECU by communicating with at least one ECU, and then determine the specific fault condition by comparing the actual fault data and the diagnostic update data.

[0048] Furthermore, the diagnostic update data may include the controller identification of each controller corresponding to the diagnostic instrument, the fault diagnostic code corresponding to the controller, and the fault description data of each fault diagnostic code. The controller identification can be understood as the identification corresponding to the controller in the ECU. The fault diagnostic code is also known as DTC (Diagnostic Trouble Code), which can be understood as a code combination used to indicate the fault condition of the controller. The fault diagnostic code can be composed of a fault location code and a fault type code. The fault location code can be understood as a code combination used to indicate the fault location of the controller, and the fault type code can be understood as a code combination used to indicate the fault type of the controller. The fault description data can be understood as data used to describe the fault condition indicated by the fault diagnostic code. Exemplarily, the fault diagnostic code in the diagnostic update data can be P01151D, and the fault description data corresponding to the fault diagnostic code can be "the current of the engine coolant temperature sensor circuit is out of range". Among them, P0115 is the fault location code, indicating the engine coolant temperature sensor circuit, and 1D is the fault type code, indicating that the current is out of range. It should be noted that the composition rules of the fault diagnosis code, fault location code and fault type code can be set or adjusted by technical personnel according to needs or experience, or determined through a large number of experiments, and this application does not impose any limitations on this.

[0049] S120, performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnosis update data.

[0050] Optionally, the formal check may include at least one of checking whether the controller identification and the corresponding fault part code match, and checking whether the fault diagnosis code complies with the composition rule of the fault diagnosis code. Exemplarily, according to the composition rule of the fault diagnosis code, a regular expression corresponding to the composition rule may be determined; according to the matching result between the regular expression and the fault diagnosis code, it is determined whether the fault diagnosis code complies with the composition rule.

[0051] S130, performing content check on the fault type code and the fault description data to obtain a content check result of the diagnosis update data.

[0052] Optionally, the content check may include checking whether the fault type represented by the fault description data matches the fault type code, etc.

[0053] S140, if both the form inspection result and the content inspection result indicate that the inspection is passed, the diagnostic update data is imported into the diagnostic instrument.

[0054] Optionally, an excel file storing diagnostic update data may be maintained on a terminal or server; when the diagnostic reference data in the diagnosis needs to be updated, the diagnostic update data in the excel file may be read; the software window corresponding to the diagnostic instrument may be obtained through a preset window acquisition function (such as a Pywin32 library function), and the software window may be placed in the foreground; the mouse movement and click operations, as well as keyboard input operations may be simulated through a preset operation simulation library (such as a pyautogui library) to import the diagnostic update data into the diagnostic instrument to update the diagnostic reference data in the diagnostic instrument. In the case of modifying the diagnostic reference data in the diagnostic instrument, the original diagnostic reference data in the diagnostic instrument may be deleted first, and then the diagnostic update data may be entered as a whole. Furthermore, a log may be recorded and saved based on the import of the diagnostic update data. The log may include at least one of the number of fault codes that were successfully imported, the fault description data that failed to be imported, and the corresponding reason for the import failure.

[0055] In this embodiment, the diagnostic update data of the diagnostic instrument is obtained; a formal check is performed on the controller identification and the corresponding fault location code of the controller to obtain the formal check result of the diagnostic update data; a content check is performed on the fault type code and the fault description data to obtain the content check result of the diagnostic update data; if both the formal check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument. By executing the above method, the automatic import of the diagnostic update data can be realized, and compared with the method of manually importing the diagnostic update data in the prior art, the import efficiency of the diagnostic update data can be improved. In the above method, the diagnostic update data is respectively subjected to a formal check and a content check, and the diagnostic update data is imported into the diagnostic instrument only on the premise that the diagnostic update data passes the formal check and the content check, which can avoid the diagnostic update data with formal errors and content errors from being imported into the diagnostic instrument, thereby improving the import accuracy of the diagnostic update data.

[0056] Based on the technical solutions of the above embodiments, the present application also provides an optional embodiment, in which the steps for determining the formal inspection results are refined.

[0057] See also Figure 2 The steps for determining the results of the formal inspection shown include:

[0058] S210, determining a form check result of the diagnostic update data according to a controller identifier of the controller in the first mapping relationship table and a search and match condition of a fault location code corresponding to the controller.

[0059] It should be noted that the controller includes at least one controller part, and each controller part has a corresponding fault part code. If in the diagnostic update data, the controller identifier and the fault part code do not match, it means that the controller part represented by the fault part code may not belong to the controller. Among them, the first mapping relationship table is used to represent the standard mapping relationship between the controller identifier and the fault part code. The first mapping relationship table may include at least one controller identifier, and a standard fault part code that correctly corresponds to each controller identifier. It is further noted that the first mapping relationship table can be set or adjusted by technical personnel according to needs or experience, or determined through a large number of experiments, and this application does not impose any restrictions on this.

[0060] In an optional embodiment, if the controller identifier is not found from the first mapping relationship table, a first form check result of the unknown controller is generated; if the controller identifier of the controller is found from the first mapping relationship table, a second form check result of the diagnostic update data is generated based on the match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table.

[0061] The standard part code may be understood as the fault part code correctly corresponding to the fault part code identified by the controller.

[0062] Optionally, if the controller identifier is not found in the first mapping table, it means that the controller identifier in the diagnostic update data does not exist in the first mapping table, and it is impossible to verify whether the controller identifier is correct, so a first form check result that the controller is an unknown controller is generated. If the controller identifier is found in the first mapping table, it means that the controller identifier itself is correct, and it can be further determined whether the controller identifier matches the corresponding fault location code.

[0063] In an optional embodiment, if the controller identifier of the controller is found from the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form inspection result is generated in which the fault code does not correspond to the controller; if the controller identifier of the controller is found from the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form inspection result is generated in which the fault code corresponds to the controller.

[0064] Further, if a first formal check result is generated indicating that the controller is an unknown controller, or a second formal check result is generated indicating that the fault code does not correspond to the controller, it indicates that the diagnostic update data has not passed the formal check. If a second formal check result is generated indicating that the fault code corresponds to the controller, it indicates that the diagnostic update data has passed the formal check.

[0065] In this embodiment, based on the controller identifier of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller, it is possible to determine whether the controller identifier exists in the first mapping relationship table and whether the fault location code matches the controller, thereby determining the formal inspection result of the diagnostic update data, thereby improving the accuracy of the formal inspection.

[0066] Based on the technical solutions of the above embodiments, the present application also provides an optional embodiment, in which the steps for determining the content inspection results are refined.

[0067] See also Figure 3 The steps for determining the content inspection result shown include:

[0068] S310, extracting component description data corresponding to the fault component code from the fault description data.

[0069] The fault component code can be understood as a coding segment used to form a fault diagnosis code. The fault component code can include a fault location code and a fault type code. Correspondingly, the component description data can include first description data corresponding to the fault location code and second description data corresponding to the fault type code.

[0070] Optionally, a pre-trained content inspection model may be used to extract the fault location code and the fault type code from the fault diagnosis code, and to extract the first description data and the second description data from the fault description data.

[0071] The content inspection model may be a NLP (Natural Language Processing) model.

[0072] S320: Determine the content check result of the diagnosis update data according to the search and matching status of the fault component code and the corresponding component description data in the second mapping relationship table.

[0073] Among them, the second mapping relationship table is used to represent the standard mapping relationship between the fault composition code and the composition description data. The second mapping relationship table may include each fault composition code and its corresponding standard description data. The standard description data can be understood as the standard description data that correctly corresponds to the fault composition code. Furthermore, the second mapping relationship table may include each fault location code, the first standard description data corresponding to each fault location code, each fault type code, and the second standard description data corresponding to each fault type code. It should be noted that the second mapping relationship table can be set or adjusted by technical personnel according to needs or experience, or determined through a large number of experiments, and this application does not impose any restrictions on this.

[0074] In an optional embodiment, if the fault composition code is not found from the second mapping relationship table, a first content check result of the unknown fault composition is generated; if the fault composition code is found from the second mapping relationship table, a second content check result of the diagnostic update data is determined based on the match between the composition description data and the standard description data corresponding to the fault composition code in the second mapping relationship table.

[0075] If the fault composition code is not found in the second mapping relationship table, it means that the fault composition code in the diagnostic update data does not exist in the second mapping relationship table, and it is impossible to verify whether the fault composition code is correct, so the first content check result of the unknown fault composition is generated. If the fault composition code is found in the second mapping relationship table, it means that the fault composition code itself is correct, and it can be further determined whether the fault composition code matches the corresponding composition description data.

[0076] Optionally, the fault location code and the fault type code can be extracted from the fault diagnosis code through the content inspection model; if the fault location code is not found in the second mapping table, a first content inspection result of the unknown fault location is generated; if the fault type code is not found in the second mapping table, a first content inspection result of the unknown fault type is generated; if the fault location code and the fault type code are found in the second mapping table, the second content inspection result of the diagnostic update data is determined based on the match between the fault description data and the standard description data corresponding to the fault diagnosis code in the second mapping relationship table.

[0077] In an optional embodiment, if a fault composition code is found from the second mapping relationship table, but the composition description data does not match the standard description data corresponding to the fault composition code in the second mapping relationship table, a second content check result is generated in which the fault composition code does not correspond to the composition description data; if a fault composition code is found from the second mapping relationship table, and the composition description data matches the standard description data corresponding to the fault composition code in the second mapping relationship table, a second content check result is generated in which the fault composition code corresponds to the composition description data.

[0078] The standard description data may be understood as the component description data that correctly corresponds to the fault component code.

[0079] Optionally, a content inspection model can be used to extract a fault component code from a fault diagnostic code; a standard fault code that is identical to the fault component code is matched from a second mapping relationship table; standard description data corresponding to the standard fault code is obtained; and based on whether the standard description data and component description data corresponding to the fault component code are consistent, it is determined whether the fault component code and the corresponding component description data match.

[0080] In an optional embodiment, the fault part code can be extracted from the fault diagnostic code through a content inspection model; the standard fault code that is the same as the fault part code is matched from the second mapping relationship table; the standard description data corresponding to the standard fault code is obtained; and based on whether the standard description data and the first description data corresponding to the fault part code are consistent, it is determined whether the fault part code and the corresponding first description data match.

[0081] In another optional embodiment, the fault type code can be extracted from the fault diagnostic code through a content inspection model; the standard fault code that is the same as the fault type code is matched from the second mapping relationship table; the standard description data corresponding to the standard fault code is obtained; and based on whether the standard description data and the second description data corresponding to the fault type code are consistent, it is determined whether the fault type code and the corresponding second description data match.

[0082] Furthermore, for the same fault diagnostic code in the diagnostic update data, if the fault location code matches the corresponding first description data, and the fault type code matches the second description data, then it is determined that the fault diagnostic code matches the corresponding fault description data, and a second content check result corresponding to the fault diagnostic code and the fault description data is generated; if the fault location code does not match the corresponding first description data, or the fault type code does not match the second description data, then it is determined that the fault diagnostic code does not match the corresponding fault description data, and a second content check result corresponding to the fault diagnostic code and the fault description data is generated.

[0083] Furthermore, if a first content check result is generated for an unknown fault component, or a second content check result is generated in which a fault diagnostic code does not correspond to the fault description data, it indicates that the diagnostic update data has not passed the content check; if a second content check result is generated in which a fault diagnostic code corresponds to the fault description data, it indicates that the diagnostic update data has passed the content check.

[0084] In this embodiment, the component description data corresponding to the fault component code is extracted from the fault description data. According to the search and matching situation of the fault component code and the corresponding component description data in the second mapping relationship table, it is possible to determine whether the fault component code exists in the second mapping relationship table and whether the fault component code corresponds to the corresponding component description data, thereby determining the content check result of the diagnostic update data, thereby improving the accuracy of the content check.

[0085] Based on the technical solutions of the above embodiments, the present application also provides an optional embodiment, in which the data import method is described in detail.

[0086] See also Figure 4 A data import method shown includes:

[0087] S401, obtaining diagnostic update data of the diagnostic instrument.

[0088] S402: If the controller identifier is not found in the first mapping relationship table, a first form check result of an unknown controller is generated.

[0089] S403, if the controller identifier of the controller is found in the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form inspection result indicating that the fault code does not correspond to the controller is generated.

[0090] S404: If the controller identifier of the controller is found in the first mapping table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping table, a second form inspection result corresponding to the fault code and the controller is generated.

[0091] S405, extracting component description data corresponding to the fault component code from the fault description data, wherein the fault component code includes a fault location code and a fault type code.

[0092] S406: If the fault component code is not found in the second mapping relationship table, a first content check result of the unknown fault component is generated.

[0093] S407, if the fault component code is found in the second mapping relationship table, but the component description data does not match the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result indicating that the fault component code does not correspond to the component description data is generated.

[0094] S408, if the fault component code is found in the second mapping relationship table, and the component description data matches the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result corresponding to the fault component code and the component description data is generated.

[0095] S409, if both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0096] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0097] Based on the same inventive concept, the embodiment of the present application also provides a data import device for implementing the data import method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more data import device embodiments provided below can refer to the limitations on the data import method above, and will not be repeated here.

[0098] In an exemplary embodiment, Figure 5 As shown, a data import device is provided, comprising: an acquisition module 510, a form checking module 520, a content checking module 530 and an import module 540, wherein:

[0099] The acquisition module 510 is used to obtain the diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes the controller identification of each controller in the diagnostic instrument, the fault diagnostic code corresponding to the controller and the fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining the fault location code and the fault type code.

[0100] The formal inspection module 520 is used to perform a formal inspection on the controller identification and the corresponding fault location code of the controller to obtain a formal inspection result of the diagnosis update data.

[0101] The content checking module 530 is used to perform content checking on the fault type code and the fault description data to obtain a content checking result of the diagnosis update data.

[0102] The import module 540 is used to import the diagnostic update data into the diagnostic instrument if both the form inspection result and the content inspection result indicate that the inspection is passed.

[0103] In one embodiment, the formal check module 520 includes: a first determination unit, which is used to determine the formal check result of the diagnostic update data according to the controller identifier of the controller in the first mapping relationship table and the search and match status of the fault part code corresponding to the controller.

[0104] In one embodiment, the first determination unit includes: a first generation subunit, which is used to generate a first form check result of an unknown controller if the controller identifier is not found in the first mapping relationship table; and a second generation subunit, which is used to generate a second form check result of diagnostic update data based on a match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table if the controller identifier of the controller is found in the first mapping relationship table.

[0105] In one of the embodiments, the second generating sub-unit is also used to generate a second form inspection result indicating that the fault code does not correspond to the controller if the controller identifier of the controller is found from the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table; and to generate a second form inspection result indicating that the fault code corresponds to the controller if the controller identifier of the controller is found from the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping relationship table.

[0106] In one embodiment, the content inspection module 530 includes: a first extraction unit, used to extract component description data corresponding to the fault component code from the fault description data; wherein the fault component code includes a fault location code and a fault type code; a second determination unit, which determines the content inspection result of the diagnostic update data based on the search and matching of the fault component code and the corresponding component description data in the second mapping relationship table.

[0107] In one embodiment, the second determination unit includes: a third generation subunit, used to generate a first content check result of an unknown fault type if the fault type code is not found from the second mapping relationship table; a first determination subunit, used to determine the second content check result of the diagnostic update data based on a match between the fault type description and a standard type description corresponding to the fault type code in the second mapping relationship table if the fault type code is found from the second mapping relationship table.

[0108] In one of the embodiments, the first determination subunit is also used to generate a second content check result in which the fault type code does not correspond to the fault type description if a fault type code is found from the second mapping relationship table, but the fault type description does not match the standard type description corresponding to the fault type code in the second mapping relationship table; if the fault type code is found from the second mapping relationship table, and the fault type description matches the standard type description corresponding to the fault type code in the second mapping relationship table, then generate a second content check result in which the fault type code corresponds to the fault type description.

[0109] Each module in the above data import device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0110] In an exemplary embodiment, a computer device is provided, the internal structure of which can be shown as follows: Figure 6 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a data import method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0111] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0112] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0113] Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0114] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0115] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0116] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0117] In one embodiment, when the processor executes the computer program, the following steps are also implemented: according to the controller identification of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller, the formal check result of the diagnostic update data is determined.

[0118] In one embodiment, when the processor executes the computer program, the following steps are also implemented: if the controller identifier is not found from the first mapping relationship table, a first form check result of the unknown controller is generated; if the controller identifier of the controller is found from the first mapping relationship table, a second form check result of the diagnostic update data is generated based on the match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table.

[0119] In one embodiment, the processor also implements the following steps when executing the computer program: if the controller identifier of the controller is found from the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form inspection result is generated that the fault code does not correspond to the controller; if the controller identifier of the controller is found from the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form inspection result is generated that the fault code corresponds to the controller.

[0120] In one embodiment, when the processor executes the computer program, the following steps are also implemented: extracting component description data corresponding to the fault component code from the fault description data; wherein the fault component code includes a fault location code and a fault type code; and determining the content check result of the diagnostic update data based on the search and matching of the fault component code and the corresponding component description data in the second mapping relationship table.

[0121] In one embodiment, when the processor executes the computer program, the following steps are also implemented: if the fault composition code is not found from the second mapping relationship table, a first content check result of the unknown fault composition is generated; if the fault composition code is found from the second mapping relationship table, a second content check result of the diagnostic update data is determined based on the match between the composition description data and the standard description data corresponding to the fault composition code in the second mapping relationship table.

[0122] In one embodiment, the processor further implements the following steps when executing the computer program: if a fault component code is found from the second mapping relationship table, but the component description data does not match the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result is generated in which the fault component code does not correspond to the component description data; if a fault component code is found from the second mapping relationship table, and the component description data matches the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result is generated in which the fault component code corresponds to the component description data.

[0123] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0124] Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identifier of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code;

[0125] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0126] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0127] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0128] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining the form check result of the diagnostic update data according to the controller identification of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller.

[0129] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the controller identifier is not found in the first mapping relationship table, a first form check result of the unknown controller is generated; if the controller identifier of the controller is found in the first mapping relationship table, a second form check result of the diagnostic update data is generated based on the match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table.

[0130] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the controller identifier of the controller is found from the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form of inspection result is generated indicating that the fault code does not correspond to the controller; if the controller identifier of the controller is found from the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form of inspection result is generated indicating that the fault code corresponds to the controller.

[0131] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: extracting component description data corresponding to the fault component code from the fault description data; wherein the fault component code includes a fault location code and a fault type code; and determining the content check result of the diagnostic update data based on the search and matching of the fault component code and the corresponding component description data in the second mapping relationship table.

[0132] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the fault composition code is not found from the second mapping relationship table, a first content check result of the unknown fault composition is generated; if the fault composition code is found from the second mapping relationship table, a second content check result of the diagnostic update data is determined based on the match between the composition description data and the standard description data corresponding to the fault composition code in the second mapping relationship table.

[0133] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if a fault component code is found from the second mapping relationship table, but the component description data does not match the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result is generated in which the fault component code does not correspond to the component description data; if a fault component code is found from the second mapping relationship table, and the component description data matches the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result is generated in which the fault component code corresponds to the component description data.

[0134] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0135] Obtaining diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes the controller identification of each controller matched by the diagnostic instrument, the fault diagnostic code corresponding to the controller and the fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining the fault location code and the fault type code;

[0136] Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data;

[0137] Performing content check on the fault type code and fault description data to obtain content check results of the diagnostic update data;

[0138] If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

[0139] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining the form check result of the diagnostic update data according to the controller identification of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller.

[0140] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the controller identifier is not found in the first mapping relationship table, a first form check result of the unknown controller is generated; if the controller identifier of the controller is found in the first mapping relationship table, a second form check result of the diagnostic update data is generated based on the match between the fault location code and the standard location code corresponding to the controller identifier in the first mapping relationship table.

[0141] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the controller identifier of the controller is found from the first mapping relationship table, but the fault location code does not match the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form of inspection result is generated indicating that the fault code does not correspond to the controller; if the controller identifier of the controller is found from the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identifier in the first mapping relationship table, a second form of inspection result is generated indicating that the fault code corresponds to the controller.

[0142] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: extracting component description data corresponding to the fault component code from the fault description data; wherein the fault component code includes a fault location code and a fault type code; and determining the content check result of the diagnostic update data based on the search and matching of the fault component code and the corresponding component description data in the second mapping relationship table.

[0143] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the fault composition code is not found from the second mapping relationship table, a first content check result of the unknown fault composition is generated; if the fault composition code is found from the second mapping relationship table, a second content check result of the diagnostic update data is determined based on the match between the composition description data and the standard description data corresponding to the fault composition code in the second mapping relationship table.

[0144] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if a fault component code is found from the second mapping relationship table, but the component description data does not match the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result is generated in which the fault component code does not correspond to the component description data; if a fault component code is found from the second mapping relationship table, and the component description data matches the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result is generated in which the fault component code corresponds to the component description data.

[0145] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0146] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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 application.

[0147] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A data import method, characterized in that: include: Acquire diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes controller identifications of each controller corresponding to the diagnostic instrument, fault diagnostic codes corresponding to the controllers, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code; Performing a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data; Performing content check on the fault type code and the fault description data to obtain a content check result of the diagnostic update data; If both the form check result and the content check result indicate that the check is passed, the diagnostic update data is imported into the diagnostic instrument.

2. The method according to claim 1, characterized in that The performing of a formal check on the controller identification and the corresponding fault location code of the controller to obtain a formal check result of the diagnostic update data includes: The form check result of the diagnostic update data is determined according to the controller identification of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller.

3. The method according to claim 2, characterized in that The determining of the form check result of the diagnostic update data according to the controller identification of the controller in the first mapping relationship table and the search and matching status of the fault location code corresponding to the controller includes: If the controller identifier is not found in the first mapping relationship table, generating a first form check result of an unknown controller; If the controller identification of the controller is found in the first mapping relationship table, a second form check result of the diagnostic update data is generated according to the matching condition between the fault location code and the standard location code corresponding to the controller identification in the first mapping relationship table.

4. The method according to claim 3, characterized in that Generating a second form of inspection result of the diagnostic update data according to a matching condition between the fault part code and the standard part code corresponding to the controller identifier in the first mapping relationship table includes: If the controller identifier of the controller is found in the first mapping relationship table, but the fault part code does not match the standard part code corresponding to the controller identifier in the first mapping relationship table, a second form check result that the fault code does not correspond to the controller is generated; If the controller identification of the controller is found in the first mapping relationship table, and the fault location code matches the standard location code corresponding to the controller identification in the first mapping relationship table, a second form inspection result corresponding to the fault code and the controller is generated.

5. The method according to claim 1, characterized in that The performing of content inspection on the fault type code and the fault description data to obtain the content inspection result of the diagnostic update data includes: Extracting component description data corresponding to the fault component code from the fault description data; wherein the fault component code includes a fault location code and a fault type code; The content check result of the diagnosis update data is determined according to the search and matching status of the fault component code and the corresponding component description data in the second mapping relationship table.

6. The method according to claim 5, characterized in that Determining the content check result of the diagnostic update data according to the search and matching status of the fault component code and the corresponding component description data in the second mapping relationship table includes: If the fault component code is not found in the second mapping relationship table, generating a first content check result of an unknown fault component; If the fault component code is found in the second mapping relationship table, the second content check result of the diagnostic update data is determined according to the matching condition between the component description data and the standard description data corresponding to the fault component code in the second mapping relationship table.

7. The method according to claim 6, characterized in that The determining the second content check result of the diagnostic update data according to a match between the component description data and the standard description data corresponding to the fault component code in the second mapping relationship table includes: If the fault component code is found in the second mapping relationship table, but the component description data does not match the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result indicating that the fault component code does not correspond to the component description data is generated; If the fault component code is found in the second mapping relationship table, and the component description data matches the standard description data corresponding to the fault component code in the second mapping relationship table, a second content check result corresponding to the fault component code and the component description data is generated.

8. A data import device, characterized in that: The device comprises: An acquisition module, used for acquiring diagnostic update data of the diagnostic instrument; wherein the diagnostic update data includes a controller identification of each controller corresponding to the diagnostic instrument, a fault diagnostic code corresponding to the controller, and fault description data of each fault diagnostic code; the fault diagnostic code is generated by combining a fault location code and a fault type code; A formal inspection module, used for performing a formal inspection on the controller identification and the corresponding fault location code of the controller to obtain a formal inspection result of the diagnostic update data; A content inspection module, used for performing a content inspection on the fault type code and the fault description data to obtain a content inspection result of the diagnostic update data; The import module is used to import the diagnostic update data into the diagnostic instrument if both the form inspection result and the content inspection result indicate that the inspection is passed.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Citation Information

Patent Citations

  • Vehicle diagnostic instrument update detecting system and method

    CN102929269A

  • Updating method, device and system for automobile diagnosis equipment

    CN103634380A

  • Automatic generation method and system for vehicle diagnosis database

    CN104216978A

  • Online updating method for guide program of vehicle electric control unit (ECU)

    CN104572141A

  • Internet-of-things-based fault data updating, displaying and alarming method for intelligent terminal of agricultural machinery

    CN107038187A