Vehicle diagnosis database generation method and device, storage medium and electronic equipment

Abstract

This application provides a method, apparatus, storage medium, and electronic device for generating a vehicle diagnostic database. The method includes: obtaining at least one diagnostic database template, wherein the diagnostic database template is a pre-constructed blank diagnostic database with a predetermined structure; obtaining diagnostic data to be transferred from an ECU file; and filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database. Each target diagnostic database corresponds one-to-one with a diagnostic database template, and any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in a corresponding application scenario. The technical solution provided by this application can automatically generate at least one target diagnostic database and can be flexibly applied to different application scenarios.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a method, apparatus, storage medium, and electronic device for generating a vehicle diagnostic database. Background Technology

[0002] Vehicle diagnostics are needed throughout the entire vehicle development, testing, production, and after-sales service process. However, these processes are often handled by different companies or departments. Therefore, a unified vehicle diagnostic database is required to ensure consistency of diagnostic needs and reusability of diagnostic data throughout the entire process. However, based on the existing patent, the technical solution disclosed in application number CN104216978A, while providing a method for generating an ODX diagnostic database that facilitates vehicle diagnostic analysis, suffers from the following technical defects:

[0003] First, the CDD diagnostic database cannot be generated automatically and must be created manually, resulting in low efficiency. Second, the ODX diagnostic database is generated based on the CDD diagnostic database, and the entire solution relies on the third-party commercial tool Vector CANDela, making it unable to run independently; its core functionality is limited by this tool. Third, the internal structure of ODX is highly flexible, and different application tools may support slightly different structures. Because the solution relies on third-party tool interfaces to execute scripts, it cannot fine-tune the ODX diagnostic database structure to match various downstream application tools from different vendors. Fourth, because the CDD diagnostic database is created manually, it cannot guarantee complete consistency with the original design files, which may lead to deviations in the data content of the ODX diagnostic database subsequently generated from the CDD diagnostic database.

[0004] Therefore, how to provide a technical method that can automatically generate a diagnostic database, and how to flexibly apply the generated diagnostic database to different application scenarios, is an urgent technical problem to be solved. Summary of the Invention

[0005] The embodiments of this application provide a method, apparatus, storage medium, and electronic device for generating a vehicle diagnostic database. Based on the technical solution provided in this application, at least one vehicle diagnostic database can be automatically generated, and the internal structure of the generated diagnostic database is adjustable, enabling it to be flexibly applied to different application scenarios and providing applicability of the diagnostic database.

[0006] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0007] According to a first aspect of the embodiments of this application, a method for generating a vehicle diagnostic database is provided. The method includes: obtaining at least one diagnostic database template, wherein the diagnostic database template is a pre-constructed blank diagnostic database with a predetermined structure; obtaining diagnostic data to be transferred from an ECU file; and filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database, wherein the target diagnostic database corresponds one-to-one with the diagnostic database template, and any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in a corresponding application scenario.

[0008] In some embodiments of this application, based on the foregoing scheme, the at least one diagnostic database template includes a CCD database template and a PDX database template.

[0009] In some embodiments of this application, based on the foregoing scheme, the method further includes: performing format validity verification on the diagnostic data to be transferred; if the verification result of the diagnostic data to be transferred is unqualified, then it is prohibited to fill the diagnostic data to be transferred into the at least one diagnostic database template.

[0010] In some embodiments of this application, based on the foregoing scheme, the method further includes: if the verification result of the diagnostic data to be transferred is qualified, then the diagnostic data to be transferred is respectively filled into the at least one diagnostic database template.

[0011] In some embodiments of this application, based on the foregoing scheme, after generating at least one target diagnostic database, the method further includes: obtaining a target structure of a diagnostic database corresponding to a target application scenario; selecting a target diagnostic database corresponding to the target application scenario from the at least one target diagnostic database; and adjusting the set structure of the target diagnostic database corresponding to the target application scenario based on the target structure to adapt to the target application scenario.

[0012] In some embodiments of this application, based on the foregoing scheme, the step of filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database includes: mapping the XML tree structure of each diagnostic database template to target memory; obtaining the target storage location of the diagnostic data to be transferred in the XML tree structure of each diagnostic database template; for each diagnostic database template, filling the diagnostic data to be transferred into the XML tree structure of the diagnostic database according to the target storage location corresponding to the diagnostic database; generating at least one initial diagnostic database in the target memory, wherein the initial diagnostic database corresponds one-to-one with the diagnostic database template; and generating at least one target diagnostic database based on the at least one initial diagnostic database.

[0013] In some embodiments of this application, based on the foregoing scheme, generating at least one target diagnostic database based on the at least one initial diagnostic database includes: mapping the XML tree structure of each initial diagnostic database to a target hard disk; and generating at least one target diagnostic database in the target hard disk.

[0014] According to a second aspect of the embodiments of this application, a vehicle diagnostic database generation apparatus is provided. The apparatus includes: a first acquisition unit, configured to acquire at least one diagnostic database template, wherein the diagnostic database template is a pre-constructed blank diagnostic database with a predetermined structure; a second acquisition unit, configured to acquire diagnostic data to be transferred from an ECU file; and a generation unit, configured to fill the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database, wherein the target diagnostic database corresponds one-to-one with the diagnostic database template, and any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in a corresponding application scenario.

[0015] According to a third aspect of the embodiments of this application, a computer-readable storage medium is provided, characterized in that the computer-readable storage medium stores at least one piece of program code, the at least one piece of program code being loaded and executed by a processor to perform the operations performed by the method described in any of the first aspects above.

[0016] According to a fourth aspect of the present application, an electronic device is provided, including one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, the at least one piece of program code being loaded and executed by the one or more processors to perform the operation as described in any of the first aspects above.

[0017] The technical solution of this application first constructs at least one blank diagnostic database with a predetermined structure to obtain at least one diagnostic database template; then, it obtains diagnostic data to be transferred from the ECU file; finally, it fills the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database corresponding to each diagnostic database template. Thus, any target diagnostic database generated can be used for vehicle diagnostic analysis in its corresponding application scenario. It is evident that, through the technical solution of this application, only a blank diagnostic database template with a predetermined structure needs to be pre-constructed, thereby automatically generating a target diagnostic database template, such as a CCD diagnostic database or a PDX diagnostic database. Based on this, the automatic generation of diagnostic databases in this application can greatly save manpower and ensure that the data in the ECU file is consistent with the data in the generated diagnostic database, thus avoiding the risk of errors caused by manual production. Furthermore, since the generated target diagnostic database is in XML format, its internal structure can be adjusted later using XML processing methods, i.e., adjusting its predetermined structure, thereby flexibly applying it to different application scenarios and improving the applicability of the generated target diagnostic database.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0020] Figure 1 A flowchart illustrating a method for generating a vehicle diagnostic database according to an embodiment of this application is shown;

[0021] Figure 2 A schematic diagram illustrating the configuration structure of a CDD diagnostic database template according to an embodiment of this application is shown;

[0022] Figure 3 A schematic diagram illustrating the configuration structure of a PDX diagnostic database template according to an embodiment of this application is shown;

[0023] Figure 4 A schematic flowchart of a method for generating a vehicle diagnostic database according to an embodiment of this application is shown.

[0024] Figure 5A block diagram of a vehicle diagnostic database generation apparatus according to an embodiment of this application is shown;

[0025] Figure 6 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0026] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0027] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0028] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0029] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily need to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0030] It should be noted that "multiple" in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such uses of these terms can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described.

[0032] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0033] The following detailed description of some embodiments of this application will be provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0034] See Figure 1 The diagram illustrates a flowchart of a method for generating a vehicle diagnostic database according to an embodiment of this application, specifically including steps 110 to 130.

[0035] Step 110: Obtain at least one diagnostic database template, wherein the diagnostic database template is a pre-constructed blank diagnostic database with a set structure.

[0036] It should be noted that each diagnostic database template only needs to be created once and can be fully reused in the future. Each diagnostic database template only needs to include its corresponding setting structure. There is no need to define diagnostic services or fill in diagnostic data. In essence, each diagnostic database is a blank diagnostic database with only structure.

[0037] In some implementations, the diagnostic database template can be one or more of the following: CDD diagnostic database template, PDX diagnostic database template, ARXML diagnostic database template, DEXT diagnostic database template, etc. Specifically, the choice of which diagnostic database template to construct can be made according to the actual situation, and this application does not limit it.

[0038] It is understandable that each diagnostic database template has a different standard, therefore a corresponding configuration structure needs to be created according to the specific requirements. For example, the CDD diagnostic database template is based on the CDD standard, where CDD is a commonly used diagnostic data format used by engineers during the development phase, and is a proprietary format defined by the engineering instrument supplier Vector; the PDX diagnostic database template is based on ODX format data, where ODX format is the universal diagnostic database format of the international standard ISO22901-1.

[0039] In some embodiments, the at least one diagnostic database template includes a CCD database template and a PDX database template.

[0040] The structure of the CCD diagnostic database template can be customized according to actual conditions, and this application does not limit it. For example, in one embodiment, the structure of the CCD diagnostic database template can be as follows: Figure 2 The design is based on the schematic diagram shown.

[0041] The structure of the PDX diagnostic database template can be configured according to actual conditions, and this application does not limit it. For example, in one embodiment, the structure of the PDX diagnostic database template can be as follows: Figure 3 The design is based on the schematic diagram shown.

[0042] See also Figure 1 Step 120: Obtain the diagnostic data to be transferred from the ECU file.

[0043] It should be noted that vehicle manufacturers typically need to develop and maintain different models of vehicles on multiple platforms. Each model includes a dozen to several dozen electronic control units (ECUs). These ECUs are connected via a bus, and each ECU can perform tasks such as functional calibration, engineering testing, data reading, off-line testing, fault diagnosis, and software updates through internationally standardized diagnostic protocols. Therefore, each ECU will have hundreds of diagnostic command data points, and the diagnostic command data for each ECU may differ between different models or platforms.

[0044] In some implementations, the ECU file may contain diagnostic instruction data for one or more ECUs; that is, the diagnostic data to be transferred may be diagnostic instruction data for one ECU or multiple ECUs.

[0045] It should also be noted that ECU files are usually in Excel format, and various programming languages ​​can read and write Excel files. Furthermore, the structure of ECU files is generally fixed, so the data in the cells can be extracted according to the fixed structure, thereby obtaining the diagnostic data to be transferred from the ECU file.

[0046] In some embodiments, after obtaining the diagnostic data to be transferred from the ECU file, the technical solution of this application further includes the following steps 10 to 20.

[0047] Step 10: Perform format validity verification on the diagnostic data to be transferred.

[0048] Step 20: If the verification result of the diagnostic data to be transferred is unqualified, then it is prohibited to fill the diagnostic data to be transferred into the at least one diagnostic database template. Alternatively, if the verification result of the diagnostic data to be transferred is qualified, then the diagnostic data to be transferred is filled into the at least one diagnostic database template.

[0049] In this embodiment, by verifying the format validity of the diagnostic data to be transferred extracted from the ECU file, the correctness and completeness of the diagnostic data filled in the ECU file can be ensured, thereby guaranteeing the correctness and completeness of the data subsequently filled into the diagnostic database.

[0050] See also Figure 1 Step 130: The diagnostic data to be transferred is filled into the at least one diagnostic database template to generate at least one target diagnostic database. The target diagnostic database corresponds one-to-one with the diagnostic database template. Any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in the corresponding application scenario.

[0051] It is understandable that if a certain number of diagnostic database templates are acquired, the corresponding diagnostic data to be transferred will be filled into each of the acquired diagnostic database templates, so that each diagnostic database template stores the same diagnostic data, thus enabling data support for different application scenarios.

[0052] In this embodiment, compared with the prior art, no third-party tools are required throughout the entire operation process, and at least one target diagnostic database can be generated independently.

[0053] In some implementations, the step of filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database can be performed according to the following steps 131 to 135.

[0054] Step 131: Map the XML tree structure of each diagnostic database template to the target memory.

[0055] It is understood that each diagnostic database template is in XML database format, and various programming languages ​​support XML read and write processing. Therefore, the XML tree structure of each diagnostic database template can be mapped to the target memory, which makes it easy to fill the diagnostic data to be transferred into the XML tree structure of each diagnostic database template.

[0056] Step 132: Obtain the target storage location of the diagnostic data to be transferred in the XML tree structure of each diagnostic database template.

[0057] It is understood that the diagnostic data to be transferred contains a large number of different diagnostic data, each describing different content. Therefore, each type of diagnostic data has a corresponding storage location in each diagnostic database template. Furthermore, since each diagnostic database template has a different structure, the storage location of the diagnostic data to be transferred differs across different diagnostic databases.

[0058] Step 133: For each diagnostic database template, according to the target storage location corresponding to the diagnostic database, fill the diagnostic data to be transferred into the XML tree structure of the diagnostic database.

[0059] Step 134: Generate at least one initial diagnostic database in the target memory, wherein the initial diagnostic database corresponds one-to-one with the diagnostic database template.

[0060] It is understandable that once the data to be diagnosed is populated into the XML tree structure of the corresponding diagnostic database template, the corresponding target diagnostic database can be automatically generated.

[0061] Step 135: Generate at least one target diagnostic database based on the at least one initial diagnostic database.

[0062] In this embodiment, the number of target diagnostic databases can be generated as many as the number of diagnostic database templates pre-built. It can be understood that different application scenarios (i.e., downstream application tools of different manufacturers) can only use the diagnostic databases that are compatible with them. Therefore, the technical solution of this application can improve the universality of vehicle diagnostic data.

[0063] In some implementations, the generation of at least one target diagnostic database based on the at least one initial diagnostic database can be performed according to steps 1351 to 1352 below.

[0064] Step 1351: Map the XML tree structure of each initial diagnostic database to the target hard disk.

[0065] Step 1352: Generate at least one target diagnostic database in the target hard disk.

[0066] It is understood that, in this embodiment, at least one initial diagnostic database stored in the target memory can be transferred to the target hard disk to generate at least one target diagnostic database, thereby improving the stability of the target diagnostic database storage and facilitating its use.

[0067] In some embodiments of this application, the method for generating the vehicle diagnostic database further includes steps 100 to 200.

[0068] Step 100: Obtain the target structure of the diagnostic database corresponding to the target application scenario.

[0069] It is understandable that different vendors' downstream application tools (i.e., corresponding to different application scenarios) can only use diagnostic data from diagnostic databases that are compatible with them, and the structures supported by different application tools will differ.

[0070] Step 200: Select the target diagnostic database corresponding to the target application scenario from the at least one target diagnostic database.

[0071] It should be noted that because the PDX diagnostic database is based on an open diagnostic protocol and can be widely used in different application scenarios, in this embodiment, the target diagnostic database corresponding to the target application scenario is generally the PDX diagnostic database. Of course, in some specific application scenarios, there may be other target diagnostic databases.

[0072] Step 300: Adjust the structure of the target diagnostic database corresponding to the target application scenario based on the target structure to adapt to the target application scenario.

[0073] This is understandable, as each target diagnostic database is created by populating data with data based on a pre-built, predetermined structure. Therefore, each target diagnostic database contains its corresponding pre-built, predetermined structure. Since each target diagnostic database is in XML database format, its internal structure can be adjusted using XML processing methods to adapt it to its corresponding application scenario.

[0074] To enable those skilled in the art to better understand this embodiment, it can be combined with Figure 4 The overall process of the technical solution in this application is understood. Figure 4The CDD database template and the PDX database template are used as at least one database template in step 110.

[0075] In some embodiments of this application, at least one blank diagnostic database with a predetermined structure is first constructed to obtain at least one diagnostic database template; then, diagnostic data to be transferred is obtained from the ECU file; finally, the diagnostic data to be transferred is filled into the at least one diagnostic database template to generate at least one target diagnostic database corresponding to the diagnostic database template. Thus, any target diagnostic database generated can be used for vehicle diagnostic analysis in the corresponding application scenario. It is evident that, through the technical solution of this application, only a blank diagnostic database template with a predetermined structure needs to be pre-constructed, thereby automatically generating a target diagnostic database template, such as a CCD diagnostic database or a PDX diagnostic database. Based on this, the technical solution for automatically generating diagnostic databases in this application can greatly save manpower and ensure that the data in the ECU file is consistent with the data in the generated diagnostic database, thereby avoiding the risk of errors caused by manual production. Furthermore, since the generated target diagnostic database is in XML format, the internal structure of the target diagnostic database can be adjusted later using XML processing methods, i.e., adjusting its predetermined structure, thereby flexibly applying it to different application scenarios and improving the applicability of the generated target diagnostic database.

[0076] The following describes an embodiment of the apparatus described in this application, which can be used to execute the vehicle diagnostic database generation method described in the above embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the vehicle diagnostic database generation method described above.

[0077] Figure 5 A block diagram of a vehicle diagnostic database generation apparatus according to an embodiment of this application is shown.

[0078] Reference Figure 5 As shown, a vehicle diagnostic database generation apparatus 500 according to an embodiment of this application includes: a first acquisition unit 501, a second acquisition unit 502, and a generation unit 503.

[0079] The first acquisition unit 501 is used to acquire at least one diagnostic database template, which is a pre-constructed blank diagnostic database with a set structure; the second acquisition unit 502 is used to acquire diagnostic data to be transferred from ECU files; and the generation unit 503 is used to fill the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database, which corresponds one-to-one with the diagnostic database template. Any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in the corresponding application scenario.

[0080] In some embodiments of this application, based on the foregoing scheme, the apparatus of this application further includes a determining unit, which is used to: determine at least one diagnostic database template as a CCD database template and a PDX database template.

[0081] In some embodiments of this application, based on the foregoing scheme, the apparatus of this application further includes a verification unit, which is used to: perform format validity verification on the diagnostic data to be transferred; if the verification result of the diagnostic data to be transferred is unqualified, then the diagnostic data to be transferred is prohibited from being filled into the at least one diagnostic database template.

[0082] In some embodiments of this application, based on the foregoing scheme, the verification unit is further configured to: if the verification result of the diagnostic data to be transferred is qualified, then fill the diagnostic data to be transferred into the at least one diagnostic database template respectively.

[0083] In some embodiments of this application, based on the foregoing scheme, the apparatus of this application further includes an adjustment unit, the adjustment unit being configured to: obtain a target structure of a diagnostic database corresponding to a target application scenario; select a target diagnostic database corresponding to the target application scenario from the at least one target diagnostic database; and adjust the set structure of the target diagnostic database corresponding to the target application scenario based on the target structure to adapt to the target application scenario.

[0084] In some embodiments of this application, based on the foregoing scheme, the generation unit 503 is further configured to: map the XML tree structure of each diagnostic database template to the target memory; obtain the target storage location of the diagnostic data to be transferred in the XML tree structure of each diagnostic database template; for each diagnostic database template, according to the target storage location corresponding to the diagnostic database, fill the diagnostic data to be transferred into the XML tree structure of the diagnostic database; generate at least one initial diagnostic database in the target memory, wherein the initial diagnostic database corresponds one-to-one with the diagnostic database template; and generate at least one target diagnostic database based on the at least one initial diagnostic database.

[0085] In some embodiments of this application, based on the foregoing scheme, the generation unit 503 is further configured to: map the XML tree structure of each initial diagnostic database to the target hard disk; and generate at least one target diagnostic database in the target hard disk.

[0086] Figure 6 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0087] It should be noted that, Figure 6 The computer system 600 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0088] like Figure 6 As shown, the computer system 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 602 or programs loaded from Storage Unit 608 into Random Access Memory (RAM) 603, such as performing the methods described in the above embodiments. The RAM 603 also stores various programs and data required for system operation. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An Input / Output (I / O) interface 605 is also connected to the bus 604.

[0089] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0090] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs various functions defined in the system of this application.

[0091] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

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

[0093] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0094] In another aspect, this application also provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the vehicle diagnostic database generation method described in the above embodiments.

[0095] In another aspect, this application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to implement the vehicle diagnostic database generation method described in the above embodiments.

[0096] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0097] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0098] Other embodiments of this application will readily conceive of by those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. It should be understood that this application is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for generating a vehicle diagnostic database, characterized in that, The method includes: Obtain at least one diagnostic database template, wherein the diagnostic database template is a pre-constructed blank diagnostic database with only a set structure; Obtain the diagnostic data to be transferred from the ECU file; The diagnostic data to be transferred is respectively filled into the at least one diagnostic database template to generate at least one target diagnostic database. The target diagnostic database corresponds one-to-one with the diagnostic database template. Any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in the corresponding application scenario. The step of filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database includes: Map the XML tree structure of each diagnostic database template to the target memory; Obtain the target storage location of the diagnostic data to be transferred in the XML tree structure of each diagnostic database template; For each diagnostic database template, the diagnostic data to be transferred is populated into the XML tree structure of the diagnostic database according to the target storage location corresponding to that diagnostic database; At least one initial diagnostic database is generated in the target memory, and the initial diagnostic database corresponds one-to-one with the diagnostic database template; At least one target diagnostic database is generated based on the at least one initial diagnostic database.

2. The method according to claim 1, characterized in that, The at least one diagnostic database template includes a CCD database template and a PDX database template.

3. The method according to claim 1, characterized in that, The method further includes: The format validity of the diagnostic data to be transferred is verified; If the verification result of the diagnostic data to be transferred is unqualified, it is prohibited to fill the diagnostic data to be transferred into the at least one diagnostic database template.

4. The method according to claim 3, characterized in that, The method further includes: If the verification result of the diagnostic data to be transferred is qualified, the diagnostic data to be transferred will be filled into the at least one diagnostic database template.

5. The method according to claim 1, characterized in that, After generating at least one target diagnostic database, the method further includes: Obtain the target structure of the diagnostic database corresponding to the target application scenario; Select a target diagnostic database corresponding to the target application scenario from the at least one target diagnostic database; Based on the target structure, the structure of the target diagnostic database corresponding to the target application scenario is adjusted to adapt to the target application scenario.

6. The method according to claim 1, characterized in that, The generation of at least one target diagnostic database based on the at least one initial diagnostic database includes: Map the XML tree structure of each initial diagnostic database to the target hard drive; At least one target diagnostic database is generated in the target hard disk.

7. A device for generating a vehicle diagnostic database, characterized in that, The device includes: The first acquisition unit is used to acquire at least one diagnostic database template, wherein the diagnostic database template is a pre-constructed blank diagnostic database with only a set structure; The second acquisition unit is used to acquire diagnostic data to be transferred from the ECU file; The generation unit is used to fill the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database. The target diagnostic database corresponds one-to-one with the diagnostic database template. Any one of the at least one target diagnostic databases is used for vehicle diagnostic analysis in the corresponding application scenario. The step of filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database includes: mapping the XML tree structure of each diagnostic database template to target memory; obtaining the target storage location of the diagnostic data to be transferred in the XML tree structure of each diagnostic database template; for each diagnostic database template, filling the diagnostic data to be transferred into the XML tree structure of that diagnostic database according to the target storage location corresponding to that diagnostic database; generating at least one initial diagnostic database in the target memory, wherein the initial diagnostic database corresponds one-to-one with the diagnostic database template; and generating at least one target diagnostic database based on the at least one initial diagnostic database.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to perform the operations performed by the method as described in any one of claims 1 to 6.

9. An electronic device, characterized in that, The method includes one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, and the at least one piece of program code is loaded and executed by the one or more processors to implement the method as claimed in any one of claims 1 to 6.

Images