Custom vehicle remote diagnosis method based on OTX execution engine

Abstract

The invention discloses a customized vehicle remote diagnosis method based on an OTX execution engine, and the method comprises the steps: a remote diagnosis cloud platform issues a diagnosis command to a vehicle end TBOX, a remote diagnosis main control module of the vehicle end TBOX downloads a diagnosis compression package, the remote diagnosis main control module decompresses the diagnosis compression package, and pulls up an OTX execution engine module. And the OTX execution engine module executes the diagnosis process according to the content in the OTX script file. According to the user-defined vehicle remote diagnosis method based on the OTX execution engine, remote diagnosis and maintenance of the vehicle are realized through cooperative work of the remote diagnosis cloud platform, the remote diagnosis master control module of the vehicle end and the OTX execution engine module issued to the vehicle end, a user can upload a user-defined OTX file through the cloud end, and the user-defined OTX file can be used for remote diagnosis and maintenance of the vehicle. Flexible configuration of diagnosis strategies is achieved, and individual requirements of different users are met.

Description

Technical Field

[0001] The present invention relates to the field of automobile remote diagnosis, and in particular to a user-defined vehicle remote diagnosis method based on an OTX execution engine. Background Art

[0002] With the continuous development of automotive electronic technology, vehicles are becoming more and more intelligent, which places higher demands on vehicle diagnosis and maintenance.

[0003] Traditional vehicle diagnostic technology usually requires professional diagnostic equipment and technicians to go on-site for diagnosis, which has the following defects: (1) Vehicle diagnostic instruments usually can only provide basic diagnostic functions, and may not be able to provide comprehensive diagnostic support for complex faults or special vehicle systems, and their functions are limited; (2) Local diagnostic instruments require technicians to arrive at the fault site, which may take a long time, especially in remote or remote areas, consuming a lot of manpower and time costs; (3) Local diagnostic instruments rely on the experience and skill level of technicians for on-site maintenance, and the requirements for technicians are high. On-site diagnosis is not only costly, but also inefficient.

[0004] With the development of Internet technology, remote diagnosis technology has gradually become a trend. The existing remote diagnosis technology is that the diagnosis platform sends the diagnosis script file to the vehicle terminal, and the terminal directly parses and executes the corresponding diagnosis command. At present, this process requires the diagnosis platform and the vehicle terminal to comply with the development and implementation of fixed business scenarios. There are often problems such as single diagnostic functions and inability to meet personalized needs. In addition, if new diagnostic functions are needed in the future, they need to be redeveloped, which consumes manpower and time costs.

[0005] Therefore, how to realize remote vehicle diagnosis flexibly, openly and efficiently is a technical problem that needs to be solved urgently. Summary of the invention

[0006] In order to address the deficiencies in the prior art, the present invention provides a custom vehicle remote diagnosis method based on an OTX (Open Test sequence exchange format) execution engine. Through the collaborative work of a remote diagnosis cloud platform, a remote diagnosis main control module on the vehicle side, and an OTX execution engine module sent to the vehicle side, remote diagnosis and maintenance of the vehicle are achieved. Users can upload custom OTX files through the cloud to achieve flexible configuration of diagnostic strategies, thereby meeting the personalized needs of different users.

[0007] The embodiment of the present invention provides the following solution:

[0008] An embodiment of the present invention provides a custom vehicle remote diagnosis method based on an OTX execution engine, the method comprising:

[0009] S1. The remote diagnosis cloud platform sends a diagnosis command to the vehicle-side TBOX (Telematics Box, remote communication terminal);

[0010] S2. The remote diagnosis main control module deployed on the vehicle-side TBOX downloads the diagnosis compressed package, which includes the OTX script file and the OTX execution engine module;

[0011] S3, the remote diagnosis main control module decompresses the diagnosis compressed package and pulls up the OTX execution engine module;

[0012] S4. The OTX execution engine module executes the diagnosis process according to the content in the OTX script file.

[0013] In an optional embodiment, the OTX script file described in step S2 is generated by a user through pre-customized configuration and uploaded to the remote diagnosis cloud platform.

[0014] In an optional embodiment, the remote diagnosis cloud platform selects a corresponding OTX script file according to the vehicle and / or ECU (Electronic Control Unit) model to be diagnosed, and packages it with the OTX execution engine module to generate a diagnosis compression package.

[0015] In an optional embodiment, step S4 specifically includes the following process:

[0016] S4.1, the OTX execution engine module parses the OTX script file, obtains the tag and saves it;

[0017] S4.2, poll the tags, for each tag, determine whether the tag is a control tag or an execution tag, if it is a control tag, proceed to step S4.3, if it is an execution tag, proceed to step S4.4;

[0018] S4.3, execute the control flow, if the polling is finished after execution, go to step S4.5, otherwise return to step S4.2 to match the next tag;

[0019] S4.4, parse the execution class tag, and process it according to the type of the execution class tag. After processing, end the polling and enter step S4.5, otherwise return to step S4.2 to match the next tag;

[0020] S4.5. The OTX execution engine module exits and the diagnosis ends.

[0021] In an optional embodiment, the control process described in step S4.3 includes looping, branching, continuing, interrupting and returning.

[0022] In an optional embodiment, the categories of the execution class labels described in step S4.4 include execution processing, allocation of OTX nodes, setting log printing level, logging and appending data.

[0023] In an optional embodiment, the execution process includes one or a combination of two or more of the following processes:

[0024] Open the file,

[0025] Close the file,

[0026] Locate the file location,

[0027] Read the file contents,

[0028] Get the time,

[0029] Program sleep time control,

[0030] int to byte function,

[0031] Endian conversion function,

[0032] Create a doip link,

[0033] Set up the doip link,

[0034] Routing activation,

[0035] Close the doip link.

[0036] doip data sending function,

[0037] 27 service security certification,

[0038] UDS34 service,

[0039] UDS36 service,

[0040] UDS3E Services,

[0041] Get memory wipe information,

[0042] Get the number of segments in the flash file,

[0043] Get the segment information in the flash file,

[0044] Get the CRC check value of the security algorithm file,

[0045] Flash file parsing function,

[0046] Fingerprint generation function.

[0047] In an optional embodiment, during the diagnostic process of step S4, the remote diagnosis main control module monitors the status of the OTX execution engine module, and when the diagnosis is completed, the remote diagnosis main control module feeds back the diagnostic result to the remote diagnosis cloud platform.

[0048] The beneficial effects of the present invention based on its technical solution are:

[0049] (1) The present invention realizes remote diagnosis and maintenance of vehicles through the coordinated work of the remote diagnosis cloud platform, the remote diagnosis main control module on the vehicle side, and the OTX execution engine module sent to the vehicle side. Users can upload customized OTX files through the cloud to realize flexible configuration of diagnostic strategies, thereby meeting the personalized needs of different users.

[0050] (2) The present invention utilizes the remote diagnosis cloud platform to centrally manage OTX scripts and OTX execution engine modules, which can achieve rapid response to changes in market and customer needs, timely update and issue new diagnostic strategies and software updates, and improve the timeliness and flexibility of diagnosis;

[0051] (3) The vehicle-side remote diagnosis control module of the present invention can be deployed in TBOX to achieve real-time diagnosis and monitoring of the vehicle. At the same time, the module can also provide some auxiliary functions, such as diagnostic report generation, fault code query, etc., to facilitate user use. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0053] Figure 1 It is a flow chart of a custom vehicle remote diagnosis method based on an OTX execution engine provided by the present invention.

[0054] Figure 2 This is a schematic diagram of the diagnostic compression package processing process. DETAILED DESCRIPTION

[0055] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention belong to the scope of protection of the embodiments of the present invention.

[0056] This embodiment provides a custom vehicle remote diagnosis method based on the OTX execution engine. Figure 1 , the method comprising:

[0057] S1. The remote diagnosis cloud platform sends a diagnosis command to the vehicle-side TBOX.

[0058] S2, reference Figure 2 , the remote diagnosis main control module deployed on the vehicle-side TBOX downloads the diagnosis compressed package (otx.zip), which includes the OTX script file (script.otx) and the OTX execution engine module (otx_app.bin).

[0059] The OTX script file is generated by the user's pre-customized configuration and uploaded to the remote diagnosis cloud platform. The remote diagnosis cloud platform selects the corresponding OTX script file according to the vehicle and / or ECU model to be diagnosed, and packages (zip) it with the OTX execution engine module to generate a diagnostic compression package.

[0060] The following table shows the correspondence between labels, user-defined functions, and action descriptions in the OTX script file of this embodiment:

[0061]

[0062]

[0063] S3. The remote diagnosis main control module decompresses the diagnosis compressed package and pulls up the OTX execution engine module.

[0064] In this embodiment, the OTX script file script.otx is decompressed to the path: / mnt / sdcard / rmd / pkg / , and the OTX execution engine module otx_app.bin application is decompressed to the path: / usrdata.

[0065] S4. The OTX execution engine module executes the diagnostic process according to the content in the OTX script file, which specifically includes the following processes:

[0066] S4.1. The OTX execution engine module parses the OTX script file, obtains the tag and saves it.

[0067] Parsing script.otx files is mainly divided into two steps. The first step is to parse <otx>< / otx> The first level of the label, such as declarations, signatures, procedures, etc., this step is mainly to obtain the information such as global variables to be used in the program, and the obtained data is saved in the memory otxNodePtr structure for easy access by subsequent programs; the second step is to parse <procedures>< / procedures> The content in the tag will be parsed here <procedure>< / procedure> Tag, which contains the control flow of the entire script.

[0068] The remote diagnosis main control module will match the one named "main" <procedure>The tag in which <flow>< / flow> The tags listed are <action> 、 <branch> 、 <loop>The action tag is used to parse the specific execution process, the branch tag is the branch control process, and the loop tag is the loop control process.

[0069] S4.2, polling tags, and executing different functions by matching tags, so as to realize the customized diagnosis function. For each tag, determine whether the tag is a control tag or an execution tag. If it is a control tag, proceed to step S4.3, and if it is an execution tag, proceed to step S4.4.

[0070] S4.3, execute the control flow, if the polling is finished after execution, go to step S4.5, otherwise return to step S4.2 to match the next tag.

[0071] S4.4, parse the execution class tag, and perform corresponding processing according to the type of the execution class tag. After processing, the polling ends and enters step S4.5, otherwise return to step S4.2 to match the next tag.

[0072] S4.5. The OTX execution engine module exits and the diagnosis ends.

[0073] During the diagnostic process in step S4, the remote diagnosis main control module monitors the status of the OTX execution engine module. When the diagnosis is completed, the remote diagnosis main control module uploads the log file generated by the OTX execution engine module to the remote diagnosis cloud platform.

[0074] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0075] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (modules, systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0076] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0077] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0078] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0079] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.< / loop> < / branch> < / action> < / procedure>

Claims

1. A customized vehicle remote diagnosis method based on OTX execution engine, characterized in that: The method comprises: S1. The remote diagnosis cloud platform sends a diagnosis command to the vehicle-side TBOX; S2. The remote diagnosis main control module deployed on the vehicle-side TBOX downloads the diagnosis compressed package, which includes the OTX script file and the OTX execution engine module; S3, the remote diagnosis main control module decompresses the diagnosis compressed package and pulls up the OTX execution engine module; S4. The OTX execution engine module executes the diagnosis process according to the content in the OTX script file.

2. The customized vehicle remote diagnosis method based on the OTX execution engine according to claim 1, characterized in that: The OTX script file described in step S2 is generated by the user's pre-customized configuration and uploaded to the remote diagnosis cloud platform.

3. The OTX execution engine-based customized vehicle remote diagnosis method according to claim 2, characterized in that: The remote diagnosis cloud platform selects the corresponding OTX script file according to the vehicle and / or ECU model to be diagnosed, and packages it with the OTX execution engine module to generate a diagnostic compression package.

4. The customized vehicle remote diagnosis method based on the OTX execution engine according to claim 1, characterized in that: Step S4 specifically The process includes: S4.1, the OTX execution engine module parses the OTX script file, obtains the tag and saves it; S4.2, poll the tags, for each tag, determine whether the tag is a control tag or an execution tag, if it is a control tag, proceed to step S4.3, if it is an execution tag, proceed to step S4.4; S4.3, execute the control flow, if the polling is finished after execution, go to step S4.5, otherwise return to step S4.2 to match the next tag; S4.4, parse the execution class tag, and process it according to the type of the execution class tag. After processing, end the polling and enter step S4.5, otherwise return to step S4.2 to match the next tag; S4.

5. The OTX execution engine module exits and the diagnosis ends.

5. The OTX execution engine-based customized vehicle remote diagnosis method according to claim 4, characterized in that: The control flow described in step S4.3 includes loop, branch, continue, interrupt and return.

6. The OTX execution engine-based customized vehicle remote diagnosis method according to claim 5, characterized in that: The categories of execution class labels described in step S4.4 include execution processing, allocation of OTX nodes, setting log printing level, logging and appending data.

7. The OTX execution engine-based customized vehicle remote diagnosis method according to claim 4, characterized in that: The execution process includes one or a combination of two or more of the following processes: Open the file, Close the file, Locate the file location, Read the file contents, Get the time, Program sleep time control, int to byte function, Endian conversion function, Create a doip link, Set up the doip link, Routing activation, Close the doip link. doip data sending function, 27 service security certification, UDS34 service, UDS36 service, UDS3E Services, Get memory wipe information, Get the number of segments in the flash file, Get the segment information in the flash file, Get the CRC check value of the security algorithm file, Flash file parsing function, Fingerprint generation function.

8. The OTX execution engine-based customized vehicle remote diagnosis method according to claim 1, characterized in that: During the diagnostic process in step S4, the remote diagnosis main control module monitors the status of the OTX execution engine module. When the diagnosis is completed, the remote diagnosis main control module feeds back the diagnostic results to the remote diagnosis cloud platform.

Images