CN116662610A - Vehicle diagnosis database generation method and device, storage medium and electronic equipment - Google Patents

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

Info

Publication number
CN116662610A
CN116662610A CN202310524855.3A CN202310524855A CN116662610A CN 116662610 A CN116662610 A CN 116662610A CN 202310524855 A CN202310524855 A CN 202310524855A CN 116662610 A CN116662610 A CN 116662610A
Authority
CN
China
Prior art keywords
database
diagnostic
target
diagnosis
template
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310524855.3A
Other languages
Chinese (zh)
Inventor
王恺轶
袁榆华
武亭
司华超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lantu Automobile Technology Co Ltd
Original Assignee
Lantu Automobile Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lantu Automobile Technology Co Ltd filed Critical Lantu Automobile Technology Co Ltd
Priority to CN202310524855.3A priority Critical patent/CN116662610A/en
Publication of CN116662610A publication Critical patent/CN116662610A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/81—Indexing, e.g. XML tags; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/84—Mapping; Conversion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G06F16/9027—Trees
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)

Abstract

The embodiment of the application provides a method and a device for generating a vehicle diagnosis database, a storage medium and electronic equipment, wherein the method comprises the following steps: obtaining at least one diagnosis database template, wherein the diagnosis database template is a blank diagnosis database with a preset structure, and the blank diagnosis database is constructed in advance; obtaining diagnostic data to be transferred from an ECU file; and filling the diagnosis data to be transferred into the at least one diagnosis database template respectively to generate at least one target diagnosis database, wherein the target diagnosis databases are in one-to-one correspondence with the diagnosis database templates, and any one of the at least one target diagnosis databases is used for carrying out vehicle diagnosis analysis on corresponding application scenes. The technical scheme provided by the embodiment of the application can automatically generate at least one target diagnosis database and can be flexibly applied to different application scenes.

Description

Vehicle diagnosis database generation method and device, storage medium and electronic equipment
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method and apparatus for generating a vehicle diagnosis database, a storage medium, and an electronic device.
Background
In the development, test, production and after-sales service processes of the whole vehicle, the vehicle diagnosis function is needed, but the vehicle diagnosis function is completed by different companies or departments, so that a diagnosis database of the vehicle needs to be unified to ensure consistency of diagnosis requirements and reusability of diagnosis data in the whole process. However, based on the prior art, the technical solution disclosed in the application number CN104216978A, although the technical solution of the patent provides a method for generating an ODX diagnostic database, which is beneficial to the diagnostic analysis of the vehicle, the technical solution of the patent has the following technical drawbacks:
firstly, the CDD diagnosis database cannot be automatically generated and needs to be manually manufactured, so that the manufacturing efficiency of the CDD diagnosis database is low; the second point, the generation of the ODX diagnostic database is based on the CDD diagnostic database conversion, and the whole set of scheme relies on the third party business tool Vector CANDela, which cannot run completely independently, and the core function is limited by the third party tool; third, the internal structure of ODX is very flexible, and the structures supported by different application tools may be slightly different, in which the structure of ODX diagnostic database cannot be finely tuned to match with the downstream application tools of various vendors because the script is executed based on the third-party tool interface; fourth, the CDD diagnostic database cannot be guaranteed to be completely consistent with the original design file content due to manual production, so that the data content in the ODX diagnostic database generated by the conversion of the CDD diagnostic database may deviate.
Based on the above, how to provide a technical method capable of automatically generating a diagnostic database, and the generated diagnostic database can be flexibly applied to different application scenarios is a technical problem to be solved.
Disclosure of Invention
The embodiment of the application provides a method, a device, a storage medium and electronic equipment for generating a vehicle diagnosis database, which can automatically generate at least one vehicle diagnosis database based on the technical scheme provided by the application, and the internal structure of the generated diagnosis database is adjustable, so that the method and the device can be flexibly applied to different application scenes, and provide the applicability of the diagnosis database.
Other features and advantages of the application will be apparent from the following detailed description, or may be learned by the practice of the application.
According to a first aspect of an embodiment of the present application, there is provided a method for generating a vehicle diagnosis database, the method including: obtaining at least one diagnosis database template, wherein the diagnosis database template is a blank diagnosis database with a preset structure, and the blank diagnosis database is constructed in advance; obtaining diagnostic data to be transferred from an ECU file; and filling the diagnosis data to be transferred into the at least one diagnosis database template respectively to generate at least one target diagnosis database, wherein the target diagnosis databases are in one-to-one correspondence with the diagnosis database templates, and any one of the at least one target diagnosis databases is used for carrying out vehicle diagnosis analysis on corresponding application scenes.
In some embodiments of the application, based on the foregoing, the at least one diagnostic database template comprises a CCD database template and a PDX database template.
In some embodiments of the application, based on the foregoing, the method further comprises: performing format validity check on the diagnostic data to be transferred; and if the verification result of the to-be-transferred diagnostic data is unqualified, respectively filling the to-be-transferred diagnostic data into the at least one diagnostic database template.
In some embodiments of the application, based on the foregoing, the method further comprises: and if the verification result of the to-be-transferred diagnostic data is qualified, filling the to-be-transferred diagnostic data into the at least one diagnostic database template respectively.
In some embodiments of the application, based on the foregoing, after the generating the at least one target diagnostic database, the method further comprises: acquiring a target structure of a diagnosis database corresponding to a target application scene; selecting a target diagnosis database corresponding to the target application scene from the at least one target diagnosis database; and adjusting the setting structure of the target diagnosis database corresponding to the target application scene based on the target structure so as to adapt to the target application scene.
In some embodiments of the present application, based on the foregoing solution, the filling the diagnostic data to be transferred into the at least one diagnostic database template respectively, to generate at least one target diagnostic database includes: mapping the XML tree structure of each diagnosis database template to a target memory; acquiring target storage positions of the diagnostic data to be transferred in XML tree structures of each diagnostic database template; for each diagnosis database template, filling the diagnosis data to be transferred into an XML tree structure of the diagnosis database according to a target storage position corresponding to the diagnosis database; generating at least one initial diagnosis database in the target memory, wherein the initial diagnosis database corresponds to the diagnosis database templates one by one; at least one target diagnostic database is generated based on the at least one initial diagnostic database.
In some embodiments of the application, based on the foregoing, the generating at least one target diagnostic database based on the at least one initial diagnostic database comprises: mapping the XML tree structure of each initial diagnosis database to a target hard disk; at least one target diagnostic database is generated in the target hard disk.
According to a second aspect of an embodiment of the present application, there is provided a generation apparatus of a vehicle diagnosis database, the apparatus including: a first acquisition unit configured to acquire at least one diagnostic database template, the diagnostic database template being a blank diagnostic database having a set structure constructed in advance; a second acquisition unit for acquiring diagnostic data to be transferred from the ECU file; the generating unit is used for respectively filling 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 databases are in one-to-one correspondence with the diagnostic database templates, and any one of the at least one target diagnostic databases is used for carrying out vehicle diagnostic analysis on corresponding application scenes.
According to a third aspect of embodiments of the present application, there is provided a computer readable storage medium having stored therein at least one program code loaded and executed by a processor to implement operations performed by a method as described in any of the first aspects above.
According to a fourth aspect of embodiments of the present application, there is provided an electronic device comprising one or more processors and one or more memories having stored therein at least one piece of program code loaded and executed by the one or more processors to implement the operations performed by the method as described in any of the first aspects above.
According to the technical scheme, at least one blank diagnosis database with a set structure is firstly constructed, so that at least one diagnosis database template is obtained; obtaining diagnosis data to be transferred from the ECU file; and finally, filling the diagnosis data to be transferred into at least one diagnosis database template respectively to generate at least one target diagnosis database corresponding to the diagnosis database templates one by one, so that any one generated target diagnosis database can be used for vehicle diagnosis analysis in a corresponding application scene. Therefore, according to the technical scheme of the application, only the blank diagnosis database template with the set structure is needed to be constructed in advance, so that the target diagnosis database template, such as a CCD diagnosis database or a PDX diagnosis database, can be automatically generated. In addition, the generated target diagnosis database is in an XML format, and the internal structure of the target diagnosis database can be adjusted by using an XML processing method in the later period, namely the setting structure of the target diagnosis database is adjusted, so that the target diagnosis database can be flexibly applied to different application scenes, and the applicability of the generated target diagnosis database is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is evident that the drawings in the following description are only some embodiments of the present application and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:
FIG. 1 illustrates a flow diagram of a method of generating a vehicle diagnostic database according to one embodiment of the application;
FIG. 2 is a schematic diagram showing the configuration of a CDD diagnostic database template according to one embodiment of the present application;
FIG. 3 is a schematic diagram showing the configuration of a PDX diagnostic database template according to one embodiment of the application;
FIG. 4 illustrates an overall flow diagram of a method of generating a vehicle diagnostic database according to one embodiment of the application;
FIG. 5 shows a block diagram of a generation apparatus of a vehicle diagnosis database according to an embodiment of the present application;
fig. 6 shows a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the application may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
It should be noted that: references herein to "a plurality" means two or more. "and/or" describes an association relationship of an association object, meaning that there may be three relationships, e.g., a and/or B may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and in the above-described figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the objects so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in other sequences than those illustrated or otherwise described.
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
Referring to fig. 1, a flowchart of a method for generating a vehicle diagnostic database according to an embodiment of the present application is shown, and specifically includes steps 110 to 130.
Step 110, at least one diagnosis database template is obtained, wherein the diagnosis database template is a blank diagnosis database with a preset structure.
It should be noted that, various diagnostic database templates only need to be manufactured once, and can be completely reused later, and the various diagnostic database templates only comprise the corresponding setting structures, so that the diagnostic service is not required to be defined and the diagnostic data is not required to be filled, which is equivalent to the blank diagnostic database with only the structures of various diagnostic databases.
In some embodiments, the diagnostic database template may be one or more of a CDD diagnostic database template, a PDX diagnostic database template, an ARXML diagnostic database template, a next diagnostic database template, and the like diagnostic database templates. Specifically, what diagnosis database template is selected and constructed can be made according to actual situations, and the application is not limited herein.
It will be appreciated that the criteria for each diagnostic database template will be different and therefore, it will be necessary to make an appropriate configuration according to the corresponding requirements. Illustratively, the CDD diagnostic database template is based on CDD standards, wherein CDD is a diagnostic data format used in a common engineering development stage and is a proprietary format defined by engineering instrument suppliers Vector; the PDX diagnostic database template is data based on an ODX format, wherein the ODX format is a universal diagnostic database format of International Standard ISO 22901-1.
In some embodiments, the at least one diagnostic database template comprises a CCD database template and a PDX database template.
The configuration of the CCD diagnostic database template may be set according to the actual situation, which is not limited herein, and in an exemplary embodiment, the configuration of the CDD diagnostic database template may be designed as shown in the schematic diagram of fig. 2.
The setting structure of the PDX diagnostic database template may be set according to the actual situation, which is not limited herein, and in an exemplary embodiment, the setting structure of the PDX diagnostic database template may be designed as shown in the schematic diagram of fig. 3.
With continued reference to FIG. 1, at step 120, diagnostic data to be transferred is obtained from the ECU file.
It should be noted that, in general, a manufacturer of a whole vehicle needs to develop and maintain vehicles of different models on multiple platforms, where each vehicle model includes ten or more to several tens of electronic control units, i.e., ECU. The ECUs are communicated through a bus, and each ECU can perform functions such as functional calibration, engineering test, data reading, offline detection, fault diagnosis, refreshing software, etc. through an internationally standardized diagnostic protocol, so that hundreds of diagnostic command data may exist for each ECU, and the diagnostic command data may be different in different vehicle models or different platforms.
In some embodiments, the ECU file may include diagnostic instruction data of one or more ECUs, that is, the diagnostic data to be transferred may be diagnostic instruction data of one ECU or a plurality of ECUs.
It should be further noted that, in general, the ECU file is in an Excel format, and various programming languages can perform read-write operations on the Excel, and the structure of the ECU file is generally cured, so that the data of the unit cells can be extracted according to the cured structure, so that the diagnostic data to be transferred of the ECU file can be obtained.
In some embodiments, after the diagnostic data to be transferred is obtained from the ECU file, the technical solution of the present application further includes the following steps 10 to 20.
And step 10, carrying out format validity check on the diagnostic data to be transferred.
And step 20, if the verification result of the to-be-transferred diagnostic data is unqualified, respectively filling the to-be-transferred diagnostic data into the at least one diagnostic database template is forbidden. Or if the verification result of the to-be-transferred diagnostic data is qualified, filling the to-be-transferred diagnostic data into the at least one diagnostic database template respectively.
In this embodiment, by verifying the format validity of the diagnostic data to be transferred extracted from the ECU file, the correctness and the integrity of the diagnostic data filled in the ECU file can be ensured, so that the correctness and the integrity of the data filled in the subsequent diagnostic database can be ensured.
With continued reference to fig. 1, step 130 is to fill the diagnostic data to be transferred into the at least one diagnostic database template respectively, and generate at least one target diagnostic database, where the target diagnostic databases are in one-to-one correspondence with the diagnostic database templates, and any one of the at least one target diagnostic databases is used for performing vehicle diagnostic analysis in a corresponding application scenario.
It can be understood that if how many diagnostic database templates are obtained, the corresponding diagnostic data to be transferred will be respectively filled into the obtained how many diagnostic database templates, so that the same diagnostic data is stored in each diagnostic database template, and data support for different application fields can be realized.
In this embodiment, compared with the prior art, the generation of at least one target diagnosis database can be completely independently realized without any third-party tool in the whole operation flow.
In some embodiments, the filling the diagnostic data to be transferred into the at least one diagnostic database template to generate at least one target diagnostic database may be performed according to the following steps 131 to 135.
Step 131, the XML tree structure of each diagnostic database template is mapped to the target memory.
It can be understood that each diagnostic database template is in an XML database format, and various programming languages support XML read-write processing, so that the XML tree structure of each diagnostic database template can be mapped to the target memory, thereby facilitating the filling of the diagnostic data to be transferred into the XML tree structure of each diagnostic database template.
And step 132, obtaining target storage positions of the diagnosis data to be transferred in the XML tree structure of each diagnosis database template.
It will be appreciated that there is a large number of different diagnostic data in the diagnostic data to be transferred, wherein each different diagnostic data is described differently, and therefore each diagnostic data in the diagnostic data to be transferred has a storage location corresponding thereto in each diagnostic database template. In addition, due to the different structure of each diagnostic database template design, it means that the storage positions of the diagnostic data to be transferred in different diagnostic databases are different.
And step 133, filling the diagnosis data to be transferred into an XML tree structure of the diagnosis database according to a target storage position corresponding to the diagnosis database aiming at each diagnosis database template.
Step 134, generating at least one initial diagnosis database in the target memory, wherein the initial diagnosis database corresponds to the diagnosis database templates one by one.
It can be appreciated that after the data to be diagnosed is filled into the XML tree structure of the corresponding diagnostic database template, the corresponding target diagnostic database can be automatically obtained.
At step 135, at least one target diagnostic database is generated based on the at least one initial diagnostic database.
In this embodiment, how many kinds of diagnostic database templates are constructed in advance to generate how many kinds of corresponding target diagnostic databases, and it can be understood that different application scenarios (i.e., downstream application tools of different manufacturers) can only use diagnostic databases adapted thereto, so that the technical scheme of the application can improve the versatility of vehicle diagnostic data.
In some embodiments, the generating at least one target diagnostic database based on the at least one initial diagnostic database may be performed as follows steps 1351 through 1352.
Step 1351, the XML tree structure of each initial diagnostic database is mapped to the target hard disk.
At step 1352, at least one target diagnostic database is generated in the target hard disk.
It can be appreciated that in this embodiment, the at least one initial diagnostic database stored in the target memory may be transferred to the target hard disk, so as to generate at least one target diagnostic database, thereby improving the storage stability of the target diagnostic database and facilitating the call and use.
In some embodiments of the present application, the method for generating a vehicle diagnosis database further includes the following steps 100 to 200.
Step 100, obtaining a target structure of a diagnostic database corresponding to a target application scene.
It will be appreciated that downstream application tools of different vendors (i.e., corresponding to different application scenarios) can only use diagnostic data of the diagnostic database that is compatible with them, and that the structures supported by the different application tools will differ.
Step 200, selecting a target diagnosis database corresponding to the target application scene from the at least one target diagnosis database.
It should be noted that, because the PDX diagnosis database is a database based on an open diagnosis protocol, and can be widely applied to different application scenarios, in this embodiment, the target diagnosis database corresponding to the target application scenario is generally a PDX diagnosis database. Of course, in some specific application scenarios, various other target diagnostic databases may be corresponded.
And 300, adjusting the setting structure of the target diagnosis database corresponding to the target application scene based on the target structure so as to adapt to the target application scene.
It will be appreciated that, because each of the target diagnostic databases is data-populated according to a pre-built configuration, each of the target diagnostic databases has a pre-built configuration corresponding thereto. Because each target diagnosis database is in an XML database format, the internal structure of the target diagnosis database can be adjusted by using an XML processing method, so that the target diagnosis database can be suitable for the corresponding application scene.
In order to enable those skilled in the art to better understand the present embodiment, the overall flow of the technical solution of the present application may be understood in conjunction with fig. 4. Wherein fig. 4 illustrates a CDD database template and a PDX database template as at least one database template described in step 110.
In some embodiments of the present application, at least one blank diagnostic database with a set structure is first constructed, so as to obtain at least one diagnostic database template; obtaining diagnosis data to be transferred from the ECU file; and finally, filling the diagnosis data to be transferred into at least one diagnosis database template respectively to generate at least one target diagnosis database corresponding to the diagnosis database templates one by one, so that any one generated target diagnosis database can be used for vehicle diagnosis analysis in a corresponding application scene. Therefore, according to the technical scheme of the application, only the blank diagnosis database template with the set structure is needed to be constructed in advance, so that the target diagnosis database template, such as a CCD diagnosis database or a PDX diagnosis database, can be automatically generated. In addition, the generated target diagnosis database is in an XML format, and the internal structure of the target diagnosis database can be adjusted by using an XML processing method in the later period, namely the setting structure of the target diagnosis database is adjusted, so that the target diagnosis database can be flexibly applied to different application scenes, and the applicability of the generated target diagnosis database is improved.
The following describes an embodiment of the apparatus of the present application, which may be used to perform the method of generating a vehicle diagnostic database in the above-described embodiment of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method for generating a vehicle diagnosis database according to the present application.
Fig. 5 shows a block diagram of a generation apparatus of a vehicle diagnosis database according to an embodiment of the present application.
Referring to fig. 5, a vehicle diagnosis database generation apparatus 500 according to an embodiment of the present application includes: a first acquisition unit 501, a second acquisition unit 502, and a generation unit 503.
Wherein, the first obtaining unit 501 is configured to obtain at least one diagnostic database template, where the diagnostic database template is a blank diagnostic database with a preset structure; a second acquisition unit 502 for acquiring diagnostic data to be transferred from the ECU file; and the generating unit 503 is used for respectively filling 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 databases are in one-to-one correspondence with the diagnostic database templates, and any one of the at least one target diagnostic databases is used for carrying out vehicle diagnostic analysis on the corresponding application scene.
In some embodiments of the present application, based on the foregoing, the apparatus of the present application further comprises a determining unit configured to: at least one diagnostic database template is determined as a CCD database template and a PDX database template.
In some embodiments of the present application, based on the foregoing solution, the apparatus of the present application further includes a verification unit, where the verification unit is configured to: performing format validity check on the diagnostic data to be transferred; and if the verification result of the to-be-transferred diagnostic data is unqualified, respectively filling the to-be-transferred diagnostic data into the at least one diagnostic database template.
In some embodiments of the present application, based on the foregoing scheme, the verification unit is further configured to: and if the verification result of the to-be-transferred diagnostic data is qualified, filling the to-be-transferred diagnostic data into the at least one diagnostic database template respectively.
In some embodiments of the present application, based on the foregoing, the apparatus of the present application further comprises an adjusting unit for: acquiring a target structure of a diagnosis database corresponding to a target application scene; selecting a target diagnosis database corresponding to the target application scene from the at least one target diagnosis database; and adjusting the setting structure of the target diagnosis database corresponding to the target application scene based on the target structure so as to adapt to the target application scene.
In some embodiments of the present application, based on the foregoing scheme, the generating unit 503 is further configured to: mapping the XML tree structure of each diagnosis database template to a target memory; acquiring target storage positions of the diagnostic data to be transferred in XML tree structures of each diagnostic database template; for each diagnosis database template, filling the diagnosis data to be transferred into an XML tree structure of the diagnosis database according to a target storage position corresponding to the diagnosis database; generating at least one initial diagnosis database in the target memory, wherein the initial diagnosis database corresponds to the diagnosis database templates one by one; at least one target diagnostic database is generated based on the at least one initial diagnostic database.
In some embodiments of the present application, based on the foregoing scheme, the generating unit 503 is further configured to: mapping the XML tree structure of each initial diagnosis database to a target hard disk; at least one target diagnostic database is generated in the target hard disk.
Fig. 6 shows a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
It should be noted that, the computer system 600 of the electronic device shown in fig. 6 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 6, the computer system 600 includes a central processing unit (Central Processing Unit, CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 602 or a program loaded from a storage section 608 into a random access Memory (Random Access Memory, RAM) 603, for example, performing the method described in the above embodiment. In the RAM603, various programs and data required for system operation are also stored. The CPU601, ROM 602, and RAM603 are connected to each other through a bus 604. An Input/Output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and a speaker, etc.; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. When executed by a Central Processing Unit (CPU) 601, performs the various functions defined in the system of the present application.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the computer device performs the vehicle diagnosis database generation method described in the above embodiment.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer-readable medium carries one or more programs that, when executed by one of the electronic devices, cause the electronic device to implement the vehicle diagnosis database generation method described in the above embodiment.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A method of generating a vehicle diagnostic database, the method comprising:
obtaining at least one diagnosis database template, wherein the diagnosis database template is a blank diagnosis database with a preset structure, and the blank diagnosis database is constructed in advance;
obtaining diagnostic data to be transferred from an ECU file;
and filling the diagnosis data to be transferred into the at least one diagnosis database template respectively to generate at least one target diagnosis database, wherein the target diagnosis databases are in one-to-one correspondence with the diagnosis database templates, and any one of the at least one target diagnosis databases is used for carrying out vehicle diagnosis analysis on corresponding application scenes.
2. The method of claim 1, wherein the at least one diagnostic database template comprises a CCD database template and a PDX database template.
3. The method according to claim 1, wherein the method further comprises:
performing format validity check on the diagnostic data to be transferred;
and if the verification result of the to-be-transferred diagnostic data is unqualified, respectively filling the to-be-transferred diagnostic data into the at least one diagnostic database template.
4. A method according to claim 3, characterized in that the method further comprises:
and if the verification result of the to-be-transferred diagnostic data is qualified, filling the to-be-transferred diagnostic data into the at least one diagnostic database template respectively.
5. The method of claim 1, wherein after said generating at least one target diagnostic database, the method further comprises:
acquiring a target structure of a diagnosis database corresponding to a target application scene;
selecting a target diagnosis database corresponding to the target application scene from the at least one target diagnosis database;
and adjusting the setting structure of the target diagnosis database corresponding to the target application scene based on the target structure so as to adapt to the target application scene.
6. The method according to claim 1, wherein said populating the diagnostic data to be transferred into the at least one diagnostic database template, respectively, to generate at least one target diagnostic database, comprises:
mapping the XML tree structure of each diagnosis database template to a target memory;
acquiring target storage positions of the diagnostic data to be transferred in XML tree structures of each diagnostic database template;
for each diagnosis database template, filling the diagnosis data to be transferred into an XML tree structure of the diagnosis database according to a target storage position corresponding to the diagnosis database;
generating at least one initial diagnosis database in the target memory, wherein the initial diagnosis database corresponds to the diagnosis database templates one by one;
at least one target diagnostic database is generated based on the at least one initial diagnostic database.
7. The method of claim 1, wherein the generating at least one target diagnostic database based on the at least one initial diagnostic database comprises:
mapping the XML tree structure of each initial diagnosis database to a target hard disk;
at least one target diagnostic database is generated in the target hard disk.
8. A vehicle diagnostic database generation apparatus, characterized by comprising:
a first acquisition unit configured to acquire at least one diagnostic database template, the diagnostic database template being a blank diagnostic database having a set structure constructed in advance;
a second acquisition unit for acquiring diagnostic data to be transferred from the ECU file;
the generating unit is used for respectively filling 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 databases are in one-to-one correspondence with the diagnostic database templates, and any one of the at least one target diagnostic databases is used for carrying out vehicle diagnostic analysis on corresponding application scenes.
9. A computer readable storage medium having stored therein at least one program code loaded and executed by a processor to implement operations performed by the method of any of claims 1 to 7.
10. An electronic device comprising one or more processors and one or more memories, the one or more memories having stored therein at least one piece of program code that is loaded and executed by the one or more processors to implement the method of any of claims 1-7.
CN202310524855.3A 2023-05-10 2023-05-10 Vehicle diagnosis database generation method and device, storage medium and electronic equipment Pending CN116662610A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310524855.3A CN116662610A (en) 2023-05-10 2023-05-10 Vehicle diagnosis database generation method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310524855.3A CN116662610A (en) 2023-05-10 2023-05-10 Vehicle diagnosis database generation method and device, storage medium and electronic equipment

Publications (1)

Publication Number Publication Date
CN116662610A true CN116662610A (en) 2023-08-29

Family

ID=87708901

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310524855.3A Pending CN116662610A (en) 2023-05-10 2023-05-10 Vehicle diagnosis database generation method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN116662610A (en)

Similar Documents

Publication Publication Date Title
CN112052172B (en) Rapid test method and device for third-party channel and electronic equipment
CN108874678B (en) Automatic testing method and device for intelligent program
CN105786695A (en) Data test method and system
CN109933521A (en) Automated testing method, device, computer equipment and storage medium based on BDD
CN111103861B (en) Method and apparatus for developing an integrated system based on vehicle after-market diagnostic needs
CN110134596A (en) The generation method and terminal device of test document
CN113608518A (en) Data generation method, device, terminal equipment and medium
CN111291443A (en) Automatic generation method, device, equipment and storage medium for I/O module model of vehicle control unit software
CN111078529B (en) Client writing module testing method and device and electronic equipment
CN116662610A (en) Vehicle diagnosis database generation method and device, storage medium and electronic equipment
CN113705143A (en) Automatic simulation system and automatic simulation method
CN116090252A (en) Matlab-based method, device, equipment and medium for automatically generating input interface model
CN113535581B (en) Test script generation method, device, equipment and computer readable storage medium
CN103744757A (en) DF file verification method based on ARINC661
CN115437913A (en) Software in-loop testing method, device, system and storage medium
CN113836825A (en) Application method of key standard and verification chip of neural network processor
CN113626022A (en) Object model creating method and device, storage medium and electronic equipment
CN108804309B (en) Automatic test method and test tool for contract management system
CN112948195A (en) Interface testing method and device, electronic equipment and storage medium
CN112084278A (en) Verification method and device for map data conversion customized product
CN112784434A (en) Model-based avionics design method
CN112561690B (en) Method, system, equipment and storage medium for testing credit card staged service interface
CN117407048B (en) Flow configuration method and system of plug-in data processing software
CN109800155B (en) Method and device for testing QTE interlocking application software based on Probe
CN116521143B (en) DID read-write service processing method and device for fault diagnosis

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination