CN112652089A - Diagnostic method, vehicle, system, and storage medium - Google Patents
Diagnostic method, vehicle, system, and storage medium Download PDFInfo
- Publication number
- CN112652089A CN112652089A CN202011495024.0A CN202011495024A CN112652089A CN 112652089 A CN112652089 A CN 112652089A CN 202011495024 A CN202011495024 A CN 202011495024A CN 112652089 A CN112652089 A CN 112652089A
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- script
- unit
- vehicle
- diagnostic
- 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
Links
- 238000002405 diagnostic procedure Methods 0.000 title claims abstract description 22
- 238000003745 diagnosis Methods 0.000 claims abstract description 367
- 238000013515 script Methods 0.000 claims abstract description 229
- 238000004458 analytical method Methods 0.000 claims abstract description 35
- 230000005540 biological transmission Effects 0.000 claims description 45
- 238000000034 method Methods 0.000 claims description 39
- 230000015654 memory Effects 0.000 claims description 20
- 238000012795 verification Methods 0.000 claims description 12
- 239000000126 substance Substances 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 57
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 7
- 238000004171 remote diagnosis Methods 0.000 description 6
- 230000009286 beneficial effect Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 4
- 239000000463 material Substances 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a diagnostic method, a vehicle, a system and a storage medium, wherein the vehicle comprises: a device management unit for receiving a diagnostic script; the diagnosis analysis unit is used for analyzing the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script; and the diagnosis unit is used for carrying out diagnosis on the target electronic control unit ECU based on at least one diagnosis instruction contained in the diagnosis script to obtain a diagnosis result corresponding to the target ECU.
Description
Technical Field
The present application relates to the field of vehicle control technologies, and in particular, to a diagnostic method, a vehicle, a system, and a storage medium.
Background
Vehicle diagnostics are diagnostics of various components of a vehicle to determine a location of a fault, a cause of the fault, or an operational status of the various components of the vehicle. At present, a vehicle diagnosis method basically receives a diagnosis command sent by a server one by a vehicle, and performs diagnosis according to the diagnosis command in sequence. Since the transmission and execution of the diagnostic command are heavily dependent on the transmission stability of the network, the existing diagnostic method has the problems of poor diagnostic stability and low efficiency due to poor network transmission stability.
Disclosure of Invention
The embodiment of the application provides a diagnosis method, a vehicle, a system and a storage medium, which are used for solving the problems in the related art, and the technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a vehicle, including:
a device management unit for receiving a diagnostic script;
the diagnosis analysis unit is used for analyzing the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script;
and the diagnosis unit is used for carrying out diagnosis on the target electronic control unit ECU based on at least one diagnosis instruction contained in the diagnosis script and obtaining a diagnosis result corresponding to the target ECU.
In a second aspect, an embodiment of the present application provides a diagnostic method, applied to a vehicle, including:
the equipment management unit of the vehicle receives the diagnosis script;
the diagnosis analysis unit of the vehicle analyzes the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script;
the diagnosis unit of the vehicle performs diagnosis on a target Electronic Control Unit (ECU) based on at least one diagnosis instruction contained in the diagnosis script, and obtains a diagnosis result corresponding to the target ECU.
In a third aspect, an embodiment of the present application provides a diagnostic system, including:
a server for sending a diagnostic script to a vehicle;
a vehicle to receive a diagnostic script; analyzing the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script; and executing diagnosis on a target Electronic Control Unit (ECU) based on the at least one diagnosis instruction contained in the diagnosis script to obtain a diagnosis result corresponding to the target ECU.
In a fourth aspect, an embodiment of the present application provides a vehicle, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the embodiments of the second aspect.
In a fifth aspect, embodiments of the present application provide a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are executed on a computer, and the method in any one of the above-described embodiments is performed.
The advantages or beneficial effects in the above technical solution at least include: the device management unit of the vehicle receives the diagnosis script containing one or more diagnosis instructions, so that the receiving efficiency of the diagnosis instructions is improved, the receiving interruption of the diagnosis instructions caused by network interruption is avoided, and the stability of receiving the diagnosis instructions can be improved; moreover, the analysis process of the diagnosis script by the diagnosis analysis unit is carried out at the vehicle end, and the diagnosis unit can directly carry out diagnosis on the target ECU based on the analyzed diagnosis command, so that the stability of diagnosis execution can be effectively improved.
The foregoing summary is provided for the purpose of description only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of the present application will be readily apparent by reference to the drawings and following detailed description.
Drawings
In the drawings, like reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily to scale. It is appreciated that these drawings depict only some embodiments in accordance with the disclosure and are therefore not to be considered limiting of its scope.
FIG. 1 is a first schematic structural diagram of a vehicle according to an embodiment of the present application;
FIG. 2 is a second schematic structural view of a vehicle according to an embodiment of the present application;
FIG. 3 is a third schematic structural view of a vehicle according to an embodiment of the present application;
FIG. 4 is a fourth schematic structural diagram of a vehicle according to an embodiment of the present application;
FIG. 5 is a schematic structural diagram of a vehicle according to an embodiment of the present application;
FIG. 6 is a sixth schematic structural view of a vehicle according to an embodiment of the present application;
FIG. 7 is a first flowchart illustrating a diagnostic method according to an embodiment of the present disclosure;
FIG. 8 is a second flowchart illustrating a diagnostic method according to an embodiment of the present application;
FIG. 9 is a third schematic flow chart of a diagnostic method according to an embodiment of the present application;
FIG. 10 is a fourth schematic flow chart of a diagnostic method according to an embodiment of the present application;
FIG. 11 is a fifth flowchart of a diagnostic method according to an embodiment of the present application;
FIG. 12 is a schematic illustration of an interaction flow of various units in a vehicle according to an embodiment of the present application;
FIG. 13A is a schematic diagram of a diagnostic system according to an embodiment of the present application;
FIG. 13B is a schematic diagram illustrating an interaction flow of various devices in the diagnostic system according to an embodiment of the present application;
fig. 14 is a block diagram of a vehicle for implementing the diagnostic method of the embodiment of the present application.
Detailed Description
In the following, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
Fig. 1 shows a first structural schematic diagram of a vehicle according to an embodiment of the application. As shown in fig. 1, the vehicle 100 may include:
a device management unit 110 for receiving a diagnostic script;
the diagnosis analysis unit 120 is configured to analyze the diagnosis script to obtain at least one diagnosis instruction included in the diagnosis script;
the diagnosis Unit 130 is configured to perform diagnosis on a target ECU140(Electronic Control Unit) based on the at least one diagnosis instruction included in the diagnosis script, and obtain a diagnosis result corresponding to the target ECU 140.
The diagnostic script may include one diagnostic instruction or a plurality of diagnostic instructions.
The diagnostic script and the target ECU140 have a corresponding relationship, where the target ECU140 may be any one of the ECUs of the vehicle 100, and each ECU may include a body area controller, a gateway, an infotainment area controller, an electric power steering control system, an airbag controller, and the like, which is not limited herein. That is to say, the diagnostic script may be an ECU, and different diagnostic scripts may correspond to different ECUs, and of course, different diagnostic scripts may also be determined for the same ECU according to actual situations, which is not exhaustive here.
For example, diagnostic script a may contain one or more diagnostic instructions for a first target ECU and diagnostic script B may contain one or more diagnostic instructions for a second target ECU.
In one example, when the device management unit 110 receives the diagnostic script a, the diagnostic script a may be passed to the diagnostic parsing unit 120; the diagnosis analysis unit 120 analyzes the diagnosis script a to obtain one or more diagnosis instructions corresponding to the first target ECU; the diagnostic resolution unit 120 sends one or more instructions for the first target ECU to the diagnostic unit 130; further, the diagnosing unit 130 executes the one or more diagnostic instructions to the first target ECU, and finally obtains a diagnostic result corresponding to the first target ECU. Here, when the diagnosis unit 130 executes one or more diagnosis instructions, the sub-diagnosis results corresponding to each diagnosis instruction may be received in sequence, and the diagnosis unit 130 may sum up the sub-diagnosis results corresponding to all diagnosis instructions to obtain a total diagnosis result. Therefore, the method is beneficial to executing the specified diagnosis on the specified target ECU, and is convenient for completing the whole diagnosis task process.
It is noted that the diagnostic script received by the device management unit 110 of the vehicle may include one or more; in the case where a plurality of diagnostic scripts are received, the device management unit 110 may sequentially transmit the diagnostic scripts to the diagnostic parsing unit 120, and accordingly, the diagnostic parsing unit 120 may sequentially parse the diagnostic scripts, and the diagnostic unit 130 may sequentially perform diagnosis on the target ECU 140.
For example, when the device management unit 110 receives the diagnosis script a and the diagnosis script B in sequence, the diagnosis parsing unit 120 parses the diagnosis script a and the diagnosis script B in sequence, and the diagnosis unit 130 performs diagnosis on the first target ECU and the second target ECU in sequence; the first target ECU and the second target ECU may be the same or different.
According to the vehicle 100 of the embodiment of the application, the device management unit 110 of the vehicle 100 receives the diagnosis script including one or more diagnosis instructions, so that the receiving efficiency of the diagnosis instructions is improved, the receiving interruption of the diagnosis instructions caused by network interruption is avoided, and the stability of receiving the diagnosis instructions can be improved; furthermore, the analysis process of the diagnosis script by the diagnosis analysis unit 120 is performed on the vehicle side, and the diagnosis unit 130 can directly perform diagnosis on the target ECU140 based on the analyzed diagnosis command, so that the stability of remote diagnosis can be effectively improved.
In one embodiment, the device management unit 110 may be further configured to receive a diagnostic policy corresponding to the diagnostic script; determining an execution time of the diagnostic script based on the diagnostic policy; when the execution time is reached, the corresponding diagnostic script is transmitted to the diagnostic analysis unit 120, so that the diagnostic analysis unit 120 analyzes the diagnostic script, and the diagnostic unit 130 executes the diagnosis.
If the device management unit 110 does not receive the diagnostic policy corresponding to the diagnostic script, the device management unit 110 may directly provide the diagnostic script to the diagnostic parsing unit 120 in real time after receiving the diagnostic script, so that the diagnostic unit 130 performs the diagnosis in real time. Therefore, the execution of diagnosis can be flexibly adjusted according to the diagnosis requirement, and the timeliness of the diagnosis is improved.
In another embodiment of the present invention, the Device Management unit in the vehicle may be referred to as a Device Management Client (Device Management Client), and may also establish a connection with a server in the cloud, so as to obtain the diagnostic script from the server in the cloud.
Correspondingly, the device management unit 110 is configured to obtain the diagnostic script and a configuration file of the diagnostic script from the server through a connection with the server, where the configuration file includes diagnostic parameters corresponding to the diagnostic script.
The method for generating the diagnostic script in the cloud may include: the diagnostic script may be automatically generated using a diagnostic sequence configuration tool or may be written using a programming tool. The generation mode of the diagnostic script is selected and adjusted according to actual needs, and the generation mode of the diagnostic script is not limited in the embodiment of the present application.
The diagnosis sequence configuration tool or the programming tool can be installed on the server in the cloud, so that the diagnosis script can be directly generated on the server; the diagnostic sequence configuration tool or programming tool may also be installed on the computer so that diagnostic scripts may be generated on the computer and uploaded by the computer to the cloud server.
The configuration file of the diagnostic script may be a manifest file of the diagnostic script. The configuration file of the diagnostic script may be generated based on a configuration operation on the server for the diagnostic script, wherein the configuration file may include a correspondence between the diagnostic script and the diagnostic task. For example, the diagnostic script may include an ID (identity document) identifier, and the diagnostic task and the ID tag of the diagnostic script have a one-to-one correspondence or a one-to-many correspondence. Therefore, the whole diagnosis task flow is convenient to complete, and the diagnosis efficiency is improved.
The configuration file of the diagnostic script may include diagnostic parameters required for executing the diagnostic script, and the diagnostic parsing unit 120 may parse the diagnostic script to obtain one or more diagnostic instructions; the diagnosis unit 130 writes the diagnosis parameters into the target ECU through the diagnosis instruction. For example, if the diagnostic script is key matching, and the diagnostic parameters are PN (Pseudo-Noise Code) Code and SK Code for vehicle theft prevention, the diagnostic analysis unit 120 writes the PN Code and SK Code into a BDCM (Body Domain Control) controller according to the diagnostic command obtained by analysis, and triggers the BDCM controller to match the designated key.
The diagnosis result obtained by performing diagnosis on the target ECU140 may be uploaded to the server in the cloud through a remote terminal device.
In one example, as shown in fig. 2, the device management unit 110 may establish a communication connection with a server. The communication mode between the device management unit 110 and the server may be WIFI, 4G, 5G, and the like, which is not limited in this application. Thus, the vehicle 100 is advantageously connected to the server for communication, and the offline diagnosis of the vehicle 100 is performed.
The device management unit 110 may acquire, from the server, a diagnostic script corresponding to a Vehicle Identification Number (VIN) of the Vehicle and a configuration file thereof by using a Payload data transmission manner, where the configuration file includes diagnostic parameters of the diagnostic script; further, the diagnostic script corresponding to the VIN (Vehicle Identification Number) of the Vehicle, and the configuration file and the diagnostic parameter thereof may be transmitted as Payload through the connection between the device management unit 110 and the server.
In one example, the server may include: and the identity management unit is used for performing identity verification and authority management on the specified equipment of the login server.
For example, when a device such as a vehicle diagnostic apparatus, a tablet computer, or a mobile terminal is used to log in a server, the identity information of the device needs to be verified, and the login is allowed only when the identity information is verified. In addition, the server may configure such devices with an appropriate level of authority.
Accordingly, it is possible to improve the security of server access, and thus the security of diagnosis, and to avoid illegal diagnosis of the vehicle 100.
On the basis of the foregoing fig. 1 or fig. 2, in another embodiment of the present invention, as shown in fig. 3, the vehicle 100 may further include:
a downloading unit 310, configured to obtain the diagnostic script from the device management unit 110 and verify the diagnostic script; if the diagnosis script passes the verification, the diagnosis script and the configuration file (including the diagnosis parameters) of the diagnosis script are saved to the file transmission unit 320;
the file transmission unit 320 is configured to store the diagnostic script and a configuration file of the diagnostic script (including diagnostic parameters corresponding to the diagnostic script).
Here, the File Transfer unit 320 may also be referred to as an FTP (File Transfer Protocol) service unit.
In one example, the downloading unit 310 is further configured to parse and convert the diagnostic script to obtain a compressed file of the diagnostic script, and save the compressed file, the configuration file, and the diagnostic parameters of the diagnostic script to the file transmission unit 320 if the diagnostic script passes verification.
The verification performed by the downloading unit 310 on the diagnostic script may include integrity verification, validity verification, and the like, for example, whether the time of the diagnostic script is in the validity period or whether the version of the diagnostic script is correct may be detected, and of course, other verification methods may also be included, which are all within the protection scope of this embodiment, and are not exhaustive.
In the embodiment, the downloading unit 310 verifies the diagnostic script, and stores the diagnostic script and the configuration file thereof to the file transmission unit 320 when the verification is passed, so that the diagnostic unit 130 downloads the diagnostic script, which is beneficial to improving the accuracy of diagnosis and avoiding the unsatisfactory diagnostic script from participating in execution. Moreover, the downloading unit 310 may parse and convert the diagnostic script into a compressed file of the diagnostic script, and may also save the storage space of the file transmission unit 320; in addition, the file transmission unit 320 performs centralized storage on the data related to the diagnostic script, which is also convenient for improving the data transmission and processing efficiency in the subsequent diagnostic execution process, thereby improving the diagnostic efficiency.
In one embodiment, as shown in fig. 4, the vehicle 100 may further include: the distribution unit 410 is configured to obtain a configuration file of the diagnostic script, and analyze the configuration file of the diagnostic script to obtain a diagnostic task; and acquires a diagnosis script corresponding to the diagnosis task from the file transmission unit 320.
In one example, the configuration file of the diagnostic script may include the diagnostic task, and the identification or ID of the diagnostic task may have a corresponding relationship with the ID of the diagnostic script, or the diagnostic task may include the identification (or referred to as ID) of the diagnostic script. The distribution unit 410 obtains the diagnosis task by analyzing the configuration file of the diagnosis script, and further obtains the diagnosis script corresponding to the diagnosis task based on the diagnosis task, and then the distribution unit 410 can accurately obtain the diagnosis script matched with the diagnosis task from the file transmission unit 320, and further the distribution unit 410 sends the corresponding diagnosis script to the diagnosis analysis unit 120, so that the diagnosis analysis unit 120 analyzes the diagnosis script, which is beneficial to improving the transmission efficiency and the analysis efficiency of the diagnosis script, saving the operation resource, and improving the accuracy of diagnosis execution.
Wherein, the distribution unit 410 is also used for checking the vehicle condition; in the case where the vehicle condition satisfies a certain condition, a diagnosis instruction is sent to the diagnosis unit 130, so that the safety of performing diagnosis can be further improved. Here, the distribution unit 410 may check whether the vehicle can be diagnosed, for example, whether the vehicle is in a driving state, or whether the vehicle is powered on all vehicles, or the like, and accordingly, if the current vehicle is in a driving state, it may be that the condition is not satisfied, the transmission of the diagnosis instruction is not performed. The specific inspection content and the corresponding condition may be set according to the actual situation, which is not exhaustive here.
In one embodiment, the diagnosis unit 130 is further configured to send the diagnosis result corresponding to the target ECU140 to the file transmission unit 320; accordingly, the downloading unit 310 is further configured to obtain the corresponding diagnosis result for the target ECU140 from the file transmission unit 320.
In one example, the diagnosing unit 130 may send the diagnosis result corresponding to the target ECU140 to the file transmitting unit 320 for saving through the distributing unit 410, and send a saving success instruction to the downloading unit 310. Accordingly, the download unit 310 may acquire the corresponding diagnosis result for the target ECU140 from the file transmission unit 320 according to the save success instruction, so as to transmit to the device management unit 110.
In this embodiment, the diagnosis unit 130 sends the diagnosis result to the file transmission unit 320 for storage, so that the diagnosis result can be conveniently stored in a centralized manner, the utilization efficiency of storage resources is improved, and the diagnosis result can be prevented from being lost; moreover, the diagnosis process executed by the diagnosis unit 130 is conveniently separated from the diagnosis result downloading and forwarding process of the downloading unit 310, and the diagnosis efficiency is improved.
In one embodiment, the device management unit 110 is further configured to send the diagnosis result for the target ECU140 to the server.
In one example, the server may further include: and a display screen for displaying the received diagnosis result of the target ECU 140.
In one example, the server may further be connected to a terminal device, and the server is configured to transmit the diagnosis result of the target ECU140 to the terminal device, so that the terminal device displays the diagnosis result.
On this basis, analysis and processing of the diagnostic results can be facilitated.
In one embodiment, as shown in fig. 5, the device management unit 110, the downloading unit 310, and the file transmission unit 320 are disposed in an Information Domain controller 510 (IDCM);
the distribution unit 410, the diagnosis analysis unit 120, and the diagnosis unit 130 are provided in a Central Gateway 520 (CGW).
The information domain controller 510 and the central gateway 520 may be two independent devices, where the information domain controller 510 is used for receiving and verifying a diagnostic script, and the like, and the central gateway 520 is used for parsing the diagnostic script and performing diagnosis and collecting a diagnostic result, and the like. In this manner, the interaction cost between the information domain controller 510 and the central gateway 520 may be reduced.
In one embodiment, as shown in fig. 6, the device management unit 110, the download unit 310, the file transfer unit 320, the distribution unit 410, the diagnosis analysis unit 120, and the diagnosis unit 130 are disposed in the central gateway 610.
In the present embodiment, by integrating the respective units of the vehicle into the central gateway 610, the data transmission efficiency and the data transmission stability of the device management unit 110, the download unit 310, the file transmission unit 320, the distribution unit 410, the diagnostic analysis unit 120, and the diagnostic unit 130 can be improved, and the diagnostic efficiency and the stability can be improved.
As shown in fig. 7, an embodiment of the present application further provides a diagnostic method applied to a vehicle, where the diagnostic method may include:
s701, receiving a diagnosis script by a device management unit of a vehicle;
s702, analyzing the diagnosis script by a diagnosis analysis unit of the vehicle to obtain at least one diagnosis instruction contained in the diagnosis script;
and S703, the vehicle diagnosis unit diagnoses the target electronic control unit ECU based on at least one diagnosis instruction contained in the diagnosis script, and obtains a diagnosis result corresponding to the target ECU.
In one example, a diagnostic script may contain one diagnostic instruction or multiple diagnostic instructions.
The diagnostic script and the target ECU have a corresponding relation; the target ECU may be any one of various ECUs of the vehicle, and each ECU may include a body area controller, a gateway, an infotainment area controller, an electric power steering control system, an airbag controller, and the like, which are not limited herein. That is to say, the diagnostic script may be in units of ECUs, and different diagnostic scripts may correspond to different ECUs, and of course, different diagnostic scripts may also be determined for the same ECU according to actual situations, which is not exhaustive here.
For example, diagnostic script a may contain one or more diagnostic instructions for a first target ECU and diagnostic script B may contain one or more diagnostic instructions for a second target ECU.
In one example, when a device management unit of a vehicle receives a diagnostic script a, the diagnostic script a may be passed to the diagnostic parsing unit; the diagnosis analysis unit analyzes the diagnosis script A to obtain one or more diagnosis instructions corresponding to the first target ECU; the diagnosis analysis unit sends one or more instructions aiming at the first target ECU to a diagnosis unit; and the diagnosis unit executes the one or more diagnosis instructions to the first target ECU to finally obtain a diagnosis result corresponding to the first target ECU. Here, when the diagnosis unit executes one or more diagnosis instructions, the diagnosis unit may receive the sub-diagnosis results corresponding to each diagnosis instruction in sequence, and the diagnosis unit may obtain the total diagnosis result after receiving the sub-diagnosis results corresponding to all diagnosis instructions. Therefore, the method is beneficial to executing the specified diagnosis on the specified target ECU, and is convenient for completing the whole diagnosis task process.
It is noted that the diagnostic script received by the device management unit of the vehicle may include one or more; in the case where a plurality of diagnostic scripts are received, the device management unit may sequentially transmit the diagnostic scripts to the diagnostic parsing unit, and accordingly, the diagnostic parsing unit may sequentially parse the diagnostic scripts, and the diagnostic parsing unit may sequentially perform diagnosis on the target ECU.
For example, when the device management unit of the vehicle sequentially receives the diagnosis script a and the diagnosis script B, the diagnosis parsing unit sequentially parses the diagnosis script a and the diagnosis script B, and the diagnosis unit sequentially performs diagnosis on the first target ECU and the second target ECU; wherein, the first target ECU and the second target ECU can be the same or different.
According to the diagnosis method provided by the embodiment of the application, the equipment management unit of the vehicle receives the diagnosis script containing one or more diagnosis instructions, so that the receiving efficiency of the diagnosis instructions is improved, the receiving interruption of the diagnosis instructions caused by network interruption is avoided, and the stability of receiving the diagnosis instructions can be improved; in addition, the diagnostic analysis unit analyzes the diagnostic script at the vehicle end, and the diagnostic unit can directly perform diagnosis on the target ECU based on the analyzed diagnostic command, so that the stability of diagnosis execution can be effectively improved.
In one embodiment, as shown in fig. 8, when receiving the diagnosis script, the diagnosis method may further include:
s801, the device management unit of the vehicle acquires the diagnosis script and the configuration file of the diagnosis script from the server through connection with the server, wherein the configuration file comprises diagnosis parameters corresponding to the diagnosis script.
In one embodiment, as shown in fig. 9, the method may further include:
s901, a downloading unit of the vehicle acquires a diagnosis script from an equipment management unit and verifies the diagnosis script;
s902, the downloading unit of the vehicle saves the diagnosis script and the configuration file of the diagnosis script to the file transmission unit of the vehicle under the condition that the diagnosis script passes the verification.
In one embodiment, as shown in fig. 10, the diagnostic method may further include:
s1001, a distribution unit of a vehicle acquires a configuration file of a diagnosis script and analyzes the configuration file of the diagnosis script to obtain a diagnosis task;
s1002, the vehicle distribution unit acquires a diagnosis script corresponding to the diagnosis task from the file transmission unit.
In one embodiment, as shown in fig. 11, the diagnostic method may further include:
s1101, the diagnosis unit of the vehicle sends a diagnosis result corresponding to the target ECU to the file transmission unit;
s1104, the downloading unit of the vehicle acquires the corresponding diagnosis result aiming at the target ECU from the file transmission unit.
In one embodiment, the diagnostic method may further comprise:
the device management unit of the vehicle transmits the diagnosis result for the target ECU to the server.
In one embodiment, the device management unit, the download unit and the file transfer unit are arranged in the information domain controller IDCM;
the distribution unit, the diagnosis analysis unit and the diagnosis unit are arranged in the central gateway CGW.
In one embodiment, the device management unit, the download unit, the file transmission unit, the distribution unit, the diagnostic analysis unit, and the diagnostic unit are disposed in the central gateway CGW.
Next, the vehicle 100 according to the embodiment of the present application will be described by taking an example of an interaction flow of each unit in the vehicle 100.
As shown in fig. 5 and 12, the diagnosis performed by each unit of the vehicle 100 may include the steps of:
s1201, the server establishes a connection with the device management unit 110 of the vehicle 100 to communicate with the server;
s1202, the device management unit 110 receives a diagnosis script and a configuration file thereof sent by the server through communication connection with the server; wherein the diagnostic script comprises at least one diagnostic instruction; the configuration file comprises diagnosis parameters corresponding to the diagnosis script;
s1203, the downloading unit 310 acquires the diagnosis script and the configuration file thereof from the equipment management unit 110;
s1204, the downloading unit 310 verifies the diagnosis script;
s1205, the downloading unit 310, under the condition that the verification is passed, stores the diagnostic script and its configuration file (including the diagnostic parameter) to the file transmission unit 320;
s1206, the file transmission unit 320 saves the diagnosis script and the configuration file (including the diagnosis parameters) thereof;
s1207, the downloading unit 310 analyzes the configuration file of the diagnosis script to obtain a diagnosis task corresponding to the diagnosis script, and sends the diagnosis task to the distributing unit 410;
s1208, the distributing unit 410 downloads the corresponding diagnosis script from the file transmitting unit 320 according to the corresponding relationship between the diagnosis task and the diagnosis script;
s1209, the distribution unit 410 checks whether the vehicle condition is normal;
s1210, when the distribution unit 410 checks that the vehicle condition is normal, it notifies (or instructs) the diagnosis unit 130 to transmit the start diagnosis;
s1211, the diagnosis unit 130 performs diagnosis and obtains a diagnosis result. Specifically, the diagnostic analysis unit 120 downloads a diagnostic script, and sends a diagnostic instruction obtained by analysis to the diagnostic unit 130; the diagnosis unit 130 writes the diagnosis parameters into the target ECU140 through the diagnosis instruction to perform diagnosis and obtain a diagnosis result;
s1212, the distribution unit 410 obtains the diagnosis result from the diagnosis unit 130;
s1213, the distribution unit 410 uploads the acquired diagnosis result to the file transmission unit 320 for storage;
s1214, in case of saving, the distributing unit 410 further downloads the diagnosis result through the downloading unit 310;
s1215, the downloading unit 310 downloads the corresponding diagnosis result based on the notification of the distributing unit 410;
s1216, after the downloading unit 310 completes downloading, transmitting the diagnosis result to the device management unit 110;
s1217, the device management unit 110 uploads the received diagnosis result to the server for display, analysis or processing.
It should be noted that the functions of the units of the vehicle 100 in the present interaction flow are substantially similar to those in the above embodiment, and are not described again here.
Fig. 13A shows a schematic configuration diagram of a diagnostic system according to an embodiment of the application. As shown in fig. 13A, the diagnostic system includes: a server 1310 and a vehicle 100.
A server 1310 for sending a diagnostic script to a vehicle;
a vehicle 110 for receiving a diagnostic script; analyzing the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script; and executing diagnosis on a target Electronic Control Unit (ECU) based on the at least one diagnosis instruction contained in the diagnosis script to obtain a diagnosis result corresponding to the target ECU.
The server can be a remote diagnosis background or a cloud remote diagnosis background.
The server 1310 is further configured to obtain a diagnostic script; acquiring a configuration file for configuring a diagnosis script; sending the diagnosis script and the configuration file thereof to a vehicle; and receiving the diagnostic result uploaded by the vehicle.
In one example, server 1310 may be used to: acquiring a diagnosis script; acquiring a configuration file for configuring a diagnosis script; pushing the diagnostic script and its configuration file to the vehicle 100 to cause the vehicle 100 to perform the diagnosis; the diagnostic results uploaded by the vehicle 100 are received.
In addition, the diagnostic system may further include: and the remote diagnosis terminal 1320 is configured to display a diagnosis result of the vehicle obtained by the server.
It should be further noted that the diagnostic system may further include: the diagnostic configuration terminal 1330 is configured to generate a diagnostic script and upload the diagnostic script to the server 1310. The process of generating the diagnosis script may be based on the configuration of the operation and maintenance personnel, for example, at least one diagnosis sequence may be configured to generate the diagnosis script, although other configurations may also exist, which is not exhaustive here.
It should be noted that the diagnosis configuration terminal 1330 may be further configured to configure a diagnosis policy indicating at least one of an execution time of the diagnosis script, a vehicle corresponding to the diagnosis script, and an ECU corresponding to the diagnosis script. In one scenario, the configuration of the diagnostic policy may be selectable, for example, when an execution time of a certain diagnostic script needs to be configured, the configuration of the time may be performed through a diagnostic configuration terminal, that is, in a case that the diagnostic script is executed at regular time, an operation and maintenance worker may perform timed configuration on a diagnostic configuration terminal side of the network management system, and further generate the diagnostic policy of the diagnostic script, and upload the diagnostic policy to the server. Further, the server can control that when the execution time corresponding to the diagnosis strategy is reached, the corresponding diagnosis script is sent to the vehicle, and then the vehicle executes diagnosis processing based on the diagnosis script; or, the server sends both the diagnosis script and the corresponding diagnosis strategy to the vehicle, the vehicle can determine the execution time of the diagnosis script by analyzing the diagnosis strategy, and the diagnosis script is analyzed and the like when the execution time is up. Here, the processing performed by the vehicle is the same as in the foregoing embodiment, and therefore, the description thereof is omitted.
It should be noted that the diagnostic configuration terminal 1330 and the remote diagnostic terminal 1320 may be two devices respectively, or may be the same device, and this embodiment does not limit the devices.
Finally, it should be noted that the diagnostic system may further include a management device 1340 for managing the status and authority of the operation and maintenance personnel. For example, it may be managed that the operation and maintenance person is currently in a login state or a non-login state, or whether the operation and maintenance person has an operation right for some functions, or whether the operation and maintenance person has an operation right for some devices, or the like. The management device 1340 may be a device used by a management staff, and may display a management page through the management device, so that the management staff may visually view and manage the state of the operation and maintenance staff on the management page. Of course, the management device 1340 may also have other functions, such as monitoring or viewing or managing the states of various devices (such as the aforementioned diagnostic configuration terminal, remote diagnostic terminal, etc.) on the network side in the diagnostic system, which all may be within the protection scope of the present embodiment, and this is not exhaustive here.
In one example, as shown in fig. 13B, the interaction flow between the devices in the diagnostic system may include:
and S1301, the diagnosis configuration terminal uploads a diagnosis script to the server.
Wherein the diagnostic script may be automatically generated based on the configuration of the diagnostic sequence configuration tool by the diagnostic engineer; the diagnostic sequence configuration tool may be installed on a server or on an external computer.
S1302 (optional), the diagnosis configuration terminal uploads the diagnosis policy of the diagnosis script to the server.
The contents of the diagnostic strategy and the related processing have been described in the foregoing embodiments, and will not be described repeatedly here.
Here, before or during execution of S1301 and S1302, the method may further include: and the management equipment performs identity authentication and authority management on the logged terminal equipment. The authority of the terminal device can be managed through the operation of the management page of the server, for example, the authority of the terminal device or the authority of the user account is subjected to operation management such as adding and deleting.
S1303, the server pushes the diagnosis script and the configuration file (including the diagnosis parameters) thereof to the vehicle.
The diagnostic parameters can be obtained from a remote diagnostic terminal or other external equipment, the obtaining mode of the diagnostic parameters can be selected and adjusted according to actual needs, and the obtaining mode of the diagnostic parameters is not limited in the implementation of the application.
S1304, the vehicle executes diagnosis and obtains a diagnosis result;
s1305, the vehicle uploads a diagnosis result to a server;
and S1306, the server sends the diagnosis result to a remote diagnosis terminal, and the diagnosis result is displayed on the remote diagnosis terminal.
It should be noted that the functions of the devices in the diagnostic system of the embodiment of the present application are substantially similar to the functions of the devices related to the above embodiments, and are not described again here.
For the data processing method and the data interaction method before each unit of the vehicle in each diagnostic method in the embodiment of the present application, reference may be made to corresponding descriptions in the above apparatuses, and details are not repeated here.
Fig. 14 shows a block diagram of a vehicle according to an embodiment of the present application. As shown in fig. 14, the vehicle includes: a memory 1410 and a processor 1420, the memory 1410 having stored therein instructions executable on the processor 1420. The processor 1420, when executing the instructions, implements the diagnostic method in the embodiments described above. The number of the memory 1410 and the processor 1420 may be one or more. The vehicle is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The vehicle may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
The vehicle may further include a communication interface 1430 for communicating with an external device for data interactive transmission. The various devices are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor 1420 may process instructions for execution within the vehicle, including instructions stored in or on a memory to display graphical information of a GUI on an external input/output device (such as a display device coupled to an interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple vehicles may be connected, with each device providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 14, but this is not intended to represent only one bus or type of bus.
Alternatively, in an implementation, if the memory 1410, the processor 1420 and the communication interface 1430 are integrated into a chip, the memory 1410, the processor 1420 and the communication interface 1430 may communicate with each other through an internal interface.
It should be understood that the processor may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an Advanced reduced instruction set machine (ARM) architecture.
Embodiments of the present application provide a computer-readable storage medium (such as the memory 1410 described above) storing computer instructions, which when executed by a processor implement the methods provided in embodiments of the present application.
Alternatively, the memory 1410 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the vehicle of the diagnostic method, and the like. Further, the memory 1410 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 1410 may optionally include memory located remotely from the processor 1420, which may be connected to the vehicle for diagnostic methods over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more (two or more) executable instructions for implementing specific logical functions or steps in the process. And the scope of the preferred embodiments of the present application includes other implementations in which functions may be performed out of the order shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the method of the above embodiments may be implemented by hardware that is configured to be instructed to perform the relevant steps by a program, which may be stored in a computer-readable storage medium, and which, when executed, includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module may also be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various changes or substitutions within the technical scope of the present application, and these should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (20)
1. A vehicle, characterized by comprising:
a device management unit for receiving a diagnostic script;
the diagnosis analysis unit is used for analyzing the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script;
and the diagnosis unit is used for carrying out diagnosis on a target Electronic Control Unit (ECU) based on the at least one diagnosis instruction contained in the diagnosis script to obtain a diagnosis result corresponding to the target ECU.
2. The vehicle of claim 1,
the equipment management unit is further used for establishing connection with a server to acquire the diagnosis script and a configuration file of the diagnosis script from the server, wherein the configuration file contains diagnosis parameters of the diagnosis script.
3. The vehicle of claim 2, further comprising:
the downloading unit is used for acquiring the diagnosis script from the equipment management unit and verifying the diagnosis script; under the condition that the diagnosis script passes verification, saving the diagnosis script and the configuration file of the diagnosis script to a file transmission unit;
and the file transmission unit is used for storing the diagnosis script and the configuration file of the diagnosis script.
4. The vehicle of claim 3, further comprising:
the distribution unit is used for acquiring the configuration file of the diagnosis script and analyzing the configuration file of the diagnosis script to obtain a diagnosis task; and acquiring a diagnosis script corresponding to the diagnosis task from the file transmission unit.
5. The vehicle of claim 3,
the diagnosis unit is also used for sending the diagnosis result corresponding to the target ECU to the file transmission unit;
correspondingly, the downloading unit is further configured to obtain a diagnosis result corresponding to the target ECU from the file transmission unit.
6. The vehicle according to claim 5, wherein the device management unit is further configured to send the diagnosis result for the target ECU to a server.
7. The vehicle of claim 4,
the device management unit, the downloading unit and the file transmission unit are arranged in an Information Domain Controller (IDCM);
the distribution unit, the diagnosis analysis unit and the diagnosis unit are arranged in a central gateway CGW.
8. The vehicle of claim 4,
the device management unit, the download unit, the file transmission unit, the distribution unit, the diagnosis analysis unit and the diagnosis unit are arranged in a central gateway CGW.
9. A diagnostic method, applied to a vehicle, comprising:
receiving a diagnostic script by a device management unit of the vehicle;
the diagnosis analysis unit of the vehicle analyzes the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script;
and the diagnosis unit of the vehicle carries out diagnosis on a target Electronic Control Unit (ECU) based on the at least one diagnosis instruction contained in the diagnosis script to obtain a diagnosis result corresponding to the target ECU.
10. The method of claim 9, wherein upon receiving the diagnostic script, the method further comprises:
and establishing connection between the equipment management unit of the vehicle and a server so as to obtain the diagnosis script and a configuration file of the diagnosis script from the server, wherein the configuration file contains diagnosis parameters corresponding to the diagnosis script.
11. The method of claim 10, further comprising:
the downloading unit of the vehicle acquires the diagnosis script from the equipment management unit and verifies the diagnosis script;
and the downloading unit of the vehicle saves the diagnosis script and the configuration file of the diagnosis script to the file transmission unit of the vehicle under the condition that the diagnosis script passes verification.
12. The method of claim 11, further comprising:
the vehicle distribution unit acquires the configuration file of the diagnosis script and analyzes the configuration file of the diagnosis script to obtain a diagnosis task;
and the distribution unit of the vehicle acquires the diagnosis script corresponding to the diagnosis task from the file transmission unit.
13. The method of claim 11, further comprising:
the diagnosis unit of the vehicle sends a diagnosis result corresponding to the target ECU to the file transmission unit;
the download unit of the vehicle acquires a diagnosis result corresponding to the target ECU from the file transmission unit.
14. The method of claim 13, further comprising:
the device management unit of the vehicle transmits the diagnosis result for the target ECU to a server.
15. The method of claim 12,
the device management unit, the downloading unit and the file transmission unit are arranged in an Information Domain Controller (IDCM);
the distribution unit, the diagnosis analysis unit and the diagnosis unit are arranged in a central gateway CGW.
16. The method of claim 12,
the management unit, the downloading unit, the file transmission unit, the distribution unit, the diagnosis analysis unit and the diagnosis unit are arranged in a central gateway CGW.
17. A diagnostic system, comprising:
a server for sending a diagnostic script to a vehicle;
a vehicle to receive a diagnostic script; analyzing the diagnosis script to obtain at least one diagnosis instruction contained in the diagnosis script; and executing diagnosis on a target Electronic Control Unit (ECU) based on the at least one diagnosis instruction contained in the diagnosis script to obtain a diagnosis result corresponding to the target ECU.
18. The system of claim 17, wherein the server is further configured to obtain a diagnostic script; acquiring a configuration file for configuring a diagnosis script; sending the diagnosis script and the configuration file thereof to a vehicle; and receiving the diagnostic result uploaded by the vehicle.
19. A vehicle, characterized by comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 9-16.
20. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 9-16.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011495024.0A CN112652089A (en) | 2020-12-17 | 2020-12-17 | Diagnostic method, vehicle, system, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011495024.0A CN112652089A (en) | 2020-12-17 | 2020-12-17 | Diagnostic method, vehicle, system, and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112652089A true CN112652089A (en) | 2021-04-13 |
Family
ID=75355495
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011495024.0A Pending CN112652089A (en) | 2020-12-17 | 2020-12-17 | Diagnostic method, vehicle, system, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112652089A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113391877A (en) * | 2021-05-12 | 2021-09-14 | 联合汽车电子有限公司 | Refresh script parsing system |
| CN113433923A (en) * | 2021-06-03 | 2021-09-24 | 江铃汽车股份有限公司 | Vehicle remote diagnosis method, system, readable storage medium and device |
| CN113867327A (en) * | 2021-11-16 | 2021-12-31 | 深圳市齐信科技有限公司 | Real-time online universal diagnosis system |
| CN115695394A (en) * | 2022-09-14 | 2023-02-03 | 广州汽车集团股份有限公司 | Vehicle cloud diagnosis method and device, vehicle and storage medium |
| WO2023125851A1 (en) * | 2021-12-31 | 2023-07-06 | 北京罗克维尔斯科技有限公司 | Remote diagnostics method and apparatus, electronic device and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007034507A (en) * | 2005-07-25 | 2007-02-08 | Nec Corp | Diagnostic method, device, and program for equipment using radio |
| CN107065822A (en) * | 2017-01-18 | 2017-08-18 | 安徽江淮汽车集团股份有限公司 | A kind of vehicle remote diagnosis system, terminal and method |
| DE102016125294A1 (en) * | 2016-12-22 | 2018-06-28 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | Method and system for diagnosing or configuring a vehicle |
| US20180374286A1 (en) * | 2017-06-23 | 2018-12-27 | Hyundai Motor Company | Method for preventing diagnostic errors in vehicle network and apparatus therefor |
| CN109791635A (en) * | 2016-10-04 | 2019-05-21 | 实耐宝公司 | Method and system for updating diagnosis with repairing information |
| CN110162977A (en) * | 2019-04-24 | 2019-08-23 | 北京邮电大学 | A kind of Android vehicle-mounted terminal system leakage location and method |
| CN110722947A (en) * | 2019-10-26 | 2020-01-24 | 深圳市元征科技股份有限公司 | Vehicle control method and device |
| CN111026096A (en) * | 2019-12-30 | 2020-04-17 | 华人运通(江苏)技术有限公司 | Vehicle diagnosis method, apparatus, system, device and computer readable storage medium |
| CN112000396A (en) * | 2020-08-06 | 2020-11-27 | 上海电气集团股份有限公司 | Fuel cell system test control method, device, equipment and storage medium |
-
2020
- 2020-12-17 CN CN202011495024.0A patent/CN112652089A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007034507A (en) * | 2005-07-25 | 2007-02-08 | Nec Corp | Diagnostic method, device, and program for equipment using radio |
| CN109791635A (en) * | 2016-10-04 | 2019-05-21 | 实耐宝公司 | Method and system for updating diagnosis with repairing information |
| DE102016125294A1 (en) * | 2016-12-22 | 2018-06-28 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | Method and system for diagnosing or configuring a vehicle |
| CN107065822A (en) * | 2017-01-18 | 2017-08-18 | 安徽江淮汽车集团股份有限公司 | A kind of vehicle remote diagnosis system, terminal and method |
| US20180374286A1 (en) * | 2017-06-23 | 2018-12-27 | Hyundai Motor Company | Method for preventing diagnostic errors in vehicle network and apparatus therefor |
| CN110162977A (en) * | 2019-04-24 | 2019-08-23 | 北京邮电大学 | A kind of Android vehicle-mounted terminal system leakage location and method |
| CN110722947A (en) * | 2019-10-26 | 2020-01-24 | 深圳市元征科技股份有限公司 | Vehicle control method and device |
| CN111026096A (en) * | 2019-12-30 | 2020-04-17 | 华人运通(江苏)技术有限公司 | Vehicle diagnosis method, apparatus, system, device and computer readable storage medium |
| CN112000396A (en) * | 2020-08-06 | 2020-11-27 | 上海电气集团股份有限公司 | Fuel cell system test control method, device, equipment and storage medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113391877A (en) * | 2021-05-12 | 2021-09-14 | 联合汽车电子有限公司 | Refresh script parsing system |
| CN113433923A (en) * | 2021-06-03 | 2021-09-24 | 江铃汽车股份有限公司 | Vehicle remote diagnosis method, system, readable storage medium and device |
| CN113867327A (en) * | 2021-11-16 | 2021-12-31 | 深圳市齐信科技有限公司 | Real-time online universal diagnosis system |
| WO2023125851A1 (en) * | 2021-12-31 | 2023-07-06 | 北京罗克维尔斯科技有限公司 | Remote diagnostics method and apparatus, electronic device and storage medium |
| CN115695394A (en) * | 2022-09-14 | 2023-02-03 | 广州汽车集团股份有限公司 | Vehicle cloud diagnosis method and device, vehicle and storage medium |
| CN115695394B (en) * | 2022-09-14 | 2024-01-26 | 广州汽车集团股份有限公司 | Vehicle cloud diagnosis method and device, vehicle and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112652089A (en) | Diagnostic method, vehicle, system, and storage medium | |
| US20180293811A1 (en) | Vehicle remote diagnosis method and device | |
| CN110120970B (en) | Data processing method and device based on Internet of vehicles and gateway system | |
| US11240317B2 (en) | Diagnostic method and system for vehicle, and related device thereof | |
| CN109257254B (en) | Network connectivity checking method, device, computer equipment and storage medium | |
| CN111625497B (en) | Deployment method, device and equipment of distributed file system and storage medium | |
| WO2019128299A1 (en) | Test system and test method | |
| CN113382056A (en) | Data reporting method, device, equipment, storage medium and system | |
| CN113672478A (en) | Log obtaining method, device, terminal, server and storage medium | |
| CN110995538B (en) | Network data acquisition method, device, system, equipment and storage medium | |
| CN108713199B (en) | Authority management method and system, mobile terminal, shared charging equipment and server | |
| Lee et al. | Collecting big data from automotive ECUs beyond the CAN bandwidth for fault visualization | |
| CN116224976B (en) | Test method and device | |
| CN114615254B (en) | Remote connection method, device and system, storage medium and electronic equipment | |
| CN116647434B (en) | Operation and maintenance service deployment method and device and operation and maintenance system | |
| CN116011000B (en) | Access method, device and computing equipment | |
| CN114503041B (en) | Vehicle diagnosis method, diagnosis connector and diagnosis device | |
| CN107332821A (en) | It is a kind of to realize the method communicated between client and server, device and server | |
| CN117240739A (en) | Method and device for testing consensus algorithm, electronic equipment and storage medium | |
| CN115811474A (en) | Internet of things equipment binding method, terminal and Internet of things equipment | |
| CN117240587A (en) | Information security diagnosis method and device | |
| CN116775674A (en) | Method, device and system for checking mechanism data and computer equipment | |
| Sharma et al. | Design Approach for CCSDS Complied Command Operation and Frame Operation Procedure for Integrated Spacecraft Checkout | |
| CN116866073A (en) | Diagnostic fault analysis method, device, equipment and medium | |
| CN116841276A (en) | Vehicle-mounted diagnosis system and method based on vehicle-mounted machine |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210413 |