CN110716538A - Vehicle diagnosis method, device, equipment and readable storage medium - Google Patents
Vehicle diagnosis method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN110716538A CN110716538A CN201911158880.4A CN201911158880A CN110716538A CN 110716538 A CN110716538 A CN 110716538A CN 201911158880 A CN201911158880 A CN 201911158880A CN 110716538 A CN110716538 A CN 110716538A
- Authority
- CN
- China
- Prior art keywords
- file
- vehicle
- diagnosis
- diagnostic
- target
- 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
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0262—Confirmation of fault detection, e.g. extra checks to confirm that a failure has indeed occurred
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a vehicle diagnosis method, a device, equipment and a readable storage medium, wherein the method comprises the following steps: carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period; receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis; acquiring the latest diagnosis file version number of the target vehicle type from a server; acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file; and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result. It can be seen that, in the method, corresponding vehicle terminal files are respectively stored according to vehicle types, the local storage validity period is set, the vehicle terminal files are cleared when the vehicle terminal files are expired, and when vehicle diagnosis is needed, the latest diagnosis file version number is taken as a link to obtain a target diagnosis file to complete diagnosis. The safety of the vehicle diagnosis file is guaranteed, and the reliability of the vehicle diagnosis result is guaranteed.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a vehicle diagnosis method, apparatus, device, and readable storage medium.
Background
With the continuous update of vehicle technologies, the data of vehicle ECUs (Electronic Control units, also called "traveling computers", "vehicle-mounted computers", etc.) is increasing, which is a great challenge for traditional diagnosis.
In order to solve the problems, the ODX technology is proposed, and OXD is an open diagnostic data format used for interaction of diagnostic data in the life cycle of the whole vehicle. Because the ODX data has the attributes of open source and standardization, the ODX is used as a data exchange format in the whole vehicle diagnosis process, the whole process is easier and quicker, and the error probability is lower.
With the maturity of the technology, if the diagnostic after-sale software supports the standard ODX protocol, the data file required for diagnosis can be obtained only by analyzing the PDX file (a common diagnostic data storage format file), so as to complete the diagnosis of the vehicle. Although the vehicle diagnosis can be quickly completed in the PDX file, the data content in the PDX file is leaked, which may cause the core technology in the vehicle manufacturer/vehicle development center to be stolen.
In summary, how to effectively ensure the safety of the vehicle diagnostic document is a technical problem that needs to be solved urgently by those skilled in the art.
Disclosure of Invention
The invention aims to provide a vehicle diagnosis method, a vehicle diagnosis device, vehicle diagnosis equipment and a readable storage medium, which can reduce the possibility of leakage so as to ensure the safety of vehicle diagnosis files.
In order to solve the technical problem, the application provides the following technical scheme:
a vehicle diagnostic method comprising:
carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period;
receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis;
acquiring the latest diagnosis file version number of the target vehicle type from a server;
acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file;
and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
Preferably, the obtaining of the target diagnostic file corresponding to the version number of the latest diagnostic file includes:
judging whether a diagnosis file corresponding to the target vehicle type is stored locally;
if not, acquiring the target diagnosis file from the server;
if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
Preferably, when the version number of the diagnostic file is lower than the latest diagnostic file version number, the diagnostic file is deleted, and the target diagnostic file is acquired from the server.
Preferably, the obtaining the target diagnosis file from the server includes:
when the current user is determined to have the downloading right, sending a file downloading request carrying the target vehicle type to the server;
and receiving and storing the target diagnosis file fed back by the server.
Preferably, the method further comprises the following steps:
and outputting prompt information of the unauthorized downloading of the diagnosis file when the current user is determined to have no downloading authorization.
Preferably, the receiving and storing the target diagnosis file fed back by the server includes:
and when the target diagnosis file and the authorized validity period of the target diagnosis file are received and stored, setting the authorized validity period and the downloading date of the target diagnosis file in a configuration file.
Preferably, the performing an authorization check on the locally stored vehicle diagnostic file and deleting the vehicle diagnostic file exceeding the authorization validity period includes:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
judging whether the vehicle diagnosis file exceeds the authorized effective period or not by combining the authorized effective period and the downloading date;
if not, the vehicle diagnosis file is reserved; and if so, deleting the vehicle diagnosis file.
A vehicle diagnostic device comprising:
the file checking module is used for carrying out authorization checking on the vehicle diagnosis files stored locally and deleting the vehicle diagnosis files exceeding the authorization validity period;
the diagnosis request receiving module is used for receiving and analyzing a vehicle diagnosis request and determining a target vehicle type requiring diagnosis;
the version number acquisition module is used for acquiring the latest diagnostic file version number of the target vehicle type from a server;
the diagnostic file acquisition module is used for acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file;
and the vehicle diagnosis module is used for diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
Preferably, the diagnostic file obtaining module is specifically configured to determine whether a diagnostic file corresponding to the target vehicle type is stored locally; if not, acquiring the target diagnosis file from the server; if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
In a specific embodiment of the present application, the diagnostic file obtaining module is specifically configured to delete the diagnostic file and obtain the target diagnostic file from the server when the version number of the diagnostic file is lower than the latest diagnostic file version number.
In a specific embodiment of the present application, the diagnostic file obtaining module is specifically configured to send a file download request carrying the target vehicle type to the server when it is determined that the current user has the download right; and receiving and storing the target diagnosis file fed back by the server.
In a specific embodiment of the application, the diagnostic file obtaining module is further configured to output a prompt message for downloading the unauthorized diagnostic file when it is determined that the current user does not have the download right.
In an embodiment of the present application, the file detection module is specifically configured to set the authorized effective period and the download date of the target diagnostic file in a configuration file when receiving and storing the target diagnostic file and the authorized effective period of the target diagnostic file.
In one embodiment of the present application, the file authorization detection module is specifically configured to read a download date of the vehicle diagnostic file in the configuration file and the authorization validity period; judging whether the vehicle diagnosis file exceeds the authorized effective period or not by combining the authorized effective period and the downloading date; if not, the vehicle diagnosis file is reserved; and if so, deleting the vehicle diagnosis file.
A vehicle diagnostic apparatus comprising:
a memory for storing a computer program;
a processor for implementing the following steps when executing the computer program:
carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period;
receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis;
acquiring the latest diagnosis file version number of the target vehicle type from a server;
acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file;
and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
Preferably, the processor is configured to implement the following steps when executing the computer program:
acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file, wherein the target diagnostic file comprises:
judging whether a diagnosis file corresponding to the target vehicle type is stored locally;
if not, acquiring the target diagnosis file from the server;
if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
Preferably, the processor is configured to implement the following steps when executing the computer program:
and when the version number of the diagnostic file is lower than the version number of the latest diagnostic file, deleting the diagnostic file and acquiring the target diagnostic file from the server.
Preferably, the processor is configured to implement the following steps when executing the computer program:
obtaining the target diagnosis file from the server, including:
when the current user is determined to have the downloading right, sending a file downloading request carrying the target vehicle type to the server;
and receiving and storing the target diagnosis file fed back by the server.
Preferably, the processor, when executing the computer program, further implements the following steps:
and outputting prompt information of the unauthorized downloading of the diagnosis file when the current user is determined to have no downloading authorization.
Preferably, the processor is configured to implement the following steps when executing the computer program:
the receiving and storing the target diagnosis file fed back by the server comprises:
and when the target diagnosis file and the authorized validity period of the target diagnosis file are received and stored, setting the authorized validity period and the downloading date of the target diagnosis file in a configuration file.
Preferably, the processor is configured to implement the following steps when executing the computer program:
the checking the authorization of the vehicle diagnosis file stored locally and deleting the vehicle diagnosis file exceeding the authorized validity period includes:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
judging whether the vehicle diagnosis file exceeds the authorized effective period or not by combining the authorized effective period and the downloading date;
if not, the vehicle diagnosis file is reserved; and if so, deleting the vehicle diagnosis file.
A readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period;
receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis;
acquiring the latest diagnosis file version number of the target vehicle type from a server;
acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file;
and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
Preferably, the computer program when executed by a processor embodies the steps of:
acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file, wherein the target diagnostic file comprises:
judging whether a diagnosis file corresponding to the target vehicle type is stored locally;
if not, acquiring the target diagnosis file from the server;
if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
Preferably, the computer program when executed by a processor embodies the steps of:
and when the version number of the diagnostic file is lower than the version number of the latest diagnostic file, deleting the diagnostic file and acquiring the target diagnostic file from the server.
Preferably, the computer program when executed by a processor embodies the steps of:
obtaining the target diagnosis file from the server, including:
when the current user is determined to have the downloading right, sending a file downloading request carrying the target vehicle type to the server;
and receiving and storing the target diagnosis file fed back by the server.
Preferably, the computer program when executed by the processor further implements the steps of:
and outputting prompt information of the unauthorized downloading of the diagnosis file when the current user is determined to have no downloading authorization.
Preferably, the computer program when executed by a processor embodies the steps of:
the receiving and storing the target diagnosis file fed back by the server comprises:
and when the target diagnosis file and the authorized validity period of the target diagnosis file are received and stored, setting the authorized validity period and the downloading date of the target diagnosis file in a configuration file.
Preferably, the computer program when executed by a processor embodies the steps of:
the checking the authorization of the vehicle diagnosis file stored locally and deleting the vehicle diagnosis file exceeding the authorized validity period includes:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
judging whether the vehicle diagnosis file exceeds the authorized effective period or not by combining the authorized effective period and the downloading date;
if not, the vehicle diagnosis file is reserved; and if so, deleting the vehicle diagnosis file.
By applying the method provided by the embodiment of the application, the vehicle diagnosis file stored locally is subjected to authorization check, and the vehicle diagnosis file exceeding the authorization validity period is deleted; receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis; acquiring the latest diagnosis file version number of the target vehicle type from a server; acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file; and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
In the method, in order to ensure the safety of the vehicle diagnosis file, the vehicle diagnosis file stored locally can be subjected to authorization detection, and then the vehicle diagnosis file exceeding the authorization validity period is deleted. That is, the client-stored vehicle diagnostic file has an authorization expiration date, and is cleared when the authorization expires. Thus, the risk of leakage of the vehicle diagnostic file can be reduced. When the vehicle diagnosis is required, the target vehicle type for which the diagnosis is requested is first determined. And then, acquiring the latest diagnosis file version number of the target vehicle type from the server. Thus, the target diagnostic file corresponding to the version number of the latest diagnostic file can be obtained. The reliability of the terminal result can be guaranteed by utilizing the target diagnosis file to diagnose the vehicle. It can be seen that, in the method, corresponding vehicle terminal files are respectively stored according to vehicle types, the local storage validity period is set, the vehicle terminal files are cleared when the vehicle terminal files are expired, and when vehicle diagnosis is needed, the latest diagnosis file version number is taken as a link to obtain a target diagnosis file to complete diagnosis. The safety of the vehicle diagnosis file is guaranteed, and the reliability of the vehicle diagnosis result is guaranteed.
Accordingly, embodiments of the present application further provide a vehicle diagnostic apparatus, a device and a readable storage medium corresponding to the vehicle diagnostic method, which have the above technical effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart illustrating an implementation of a vehicle diagnostic method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a business process in an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating a process of updating a diagnostic file of a vehicle at a service end in an embodiment of the present application;
FIG. 4 is a schematic flow chart illustrating an embodiment of a client vehicle diagnostic process according to the present disclosure;
FIG. 5 is a schematic structural diagram of a vehicle diagnostic apparatus according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram of a vehicle diagnostic apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a vehicle diagnostic apparatus according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The first embodiment is as follows:
referring to fig. 1, fig. 1 is a flowchart of a vehicle diagnosis method in an embodiment of the present application, where the method is applicable to a client of a vehicle diagnosis system, and the method includes the following steps:
s101, carrying out authorization check on the vehicle diagnosis files stored locally, and deleting the vehicle diagnosis files exceeding the authorization validity period.
In the present embodiment, the vehicle diagnostic files corresponding to the vehicle models, that is, different vehicle models have respective matching vehicle diagnostic files.
The authorization check may specifically be to sequentially determine whether each locally stored vehicle diagnostic file exceeds the authorization validity period by using the authorization validity period and the file download date recorded in the configuration file. Then, the vehicle diagnostic file that exceeds the authorized validity period is deleted. Specifically, the authorized validity period may be set according to the confidential requirements of the vehicle manufacturers/research and development centers of different vehicle types, and of course, the authorized validity periods corresponding to different user authorities are different, for example, the authorized validity period of the temporary registered user is shorter than that of the old user. For example, it may be set in units of days such as 3 days; it may be set in units of hours such as 5 hours.
The clearing implementation process of the vehicle diagnostic file comprises the following steps:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
step two, judging whether the vehicle diagnosis file exceeds the authorized validity period or not by combining the authorized validity period and the downloading date;
if not, reserving the vehicle diagnosis file;
and step four, if so, deleting the vehicle diagnosis file.
For convenience of description, the above four steps will be described in combination.
The vehicle manufacturer/research and development center develops corresponding vehicle diagnosis files, such as PDX files, aiming at vehicle types, stores the vehicle diagnosis files on the server after the development is finished, records corresponding versions, and based on data security consideration, the vehicle diagnosis files stored on the client exceed the authorized validity period and are cleared (technicians of the vehicle manufacturer/research and development center can set clearing time on the server, and certainly, the client can apply for the time limit of the authorized validity period by itself and store the time limit in the configuration file of the client). Specifically, the client may periodically or aperiodically read the authorized validity period and the download date in the configuration file, then determine whether the locally stored vehicle diagnostic file is in the authorized period, and finally remove the vehicle diagnostic file exceeding the authorized validity period from the local. That is, only clients within the authorized validity period can maintain the corresponding vehicle diagnostic file. Therefore, the safety of the vehicle diagnostic file can be guaranteed, and the possibility of leakage is reduced.
It should be noted that the execution timing of step S101 does not necessarily have to be in the order of steps S102, S103, S104 and S105. That is, step S101 may be performed periodically (e.g., every other day), or may be performed in real time (i.e., continuously performing authorization check of the vehicle diagnostic file stored locally), and steps S102 to S105 are performed sequentially when the vehicle diagnostic request is received. For example, the execution may be performed in the execution sequence shown in fig. 1, or may not be performed in the execution sequence shown in fig. 1 (e.g., only step S101 is performed before the vehicle diagnosis request is not received).
And S102, receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis.
Vehicle diagnostic files are also continually being improved over newer versions due to their limited local storage time. Therefore, when the vehicle is diagnosed, the vehicle diagnostic file for diagnosis is determined to be the final version.
Based on the method, when the vehicle diagnosis request is received and analyzed, the target vehicle type requiring diagnosis is determined at first. Specifically, the vehicle diagnosis request may carry information of a vehicle type to be diagnosed, and the target vehicle type for which diagnosis is requested may be determined based on the vehicle type information.
S103, acquiring the latest diagnosis file version number of the target vehicle type from the server.
After the target vehicle type is determined, communication interaction can be carried out with the server, and the final diagnosis file version number of the target vehicle type is obtained from the server.
In other words, the client inquires the diagnostic data information of the target vehicle type of the server and obtains the latest diagnostic file version number of the target vehicle type stored in the server.
And S104, acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file.
After the version number of the latest diagnostic file is determined, the latest diagnostic file of the target vehicle type, that is, the target diagnostic file, can be obtained based on the version number of the latest diagnostic file.
Specifically, it is considered that the target diagnosis file may be retained for a certain period of time in the client, so that the client may directly obtain the target diagnosis file from the local, and may also obtain the target diagnosis file from the server by downloading.
The acquisition process of the target diagnosis file can comprise the following steps:
judging whether a diagnosis file corresponding to a target vehicle type is stored locally;
step two, if not, acquiring a target diagnosis file from the server;
and step three, if so, determining the diagnostic file as a target diagnostic file when the version number of the diagnostic file is the same as the version number of the latest diagnostic file.
For convenience of description, the above three steps will be described in combination.
The client checks the vehicle diagnosis files stored locally at first, and determines whether the diagnosis files corresponding to the target vehicle type exist. If the target diagnosis file does not exist, the target diagnosis file can be directly downloaded from the server; if so, the locally stored diagnostic file may be determined to be the target diagnostic file upon determining that the version number of the diagnostic file is the same as the final diagnostic file version number.
Preferably, since the vehicle diagnostic file is updated, the version of the vehicle diagnostic file saved in the server is updated, and the version of the vehicle diagnostic file saved in the client is older. Therefore, when the version number of the diagnostic file is lower than the latest diagnostic file version number, the diagnostic file is deleted and the target diagnostic file is acquired from the server.
Preferably, to further ensure the security of the diagnostic file, before the client downloads the target diagnostic file from the server, it may be determined whether the current user has a download right. Namely, the target diagnosis file is obtained from the server, and the method comprises the following steps:
step 1, when determining that the current user has the downloading right, sending a file downloading request carrying a target vehicle type to a server;
step 2, receiving and storing a target diagnosis file fed back by the server;
and 3, outputting prompt information of the unauthorized downloading of the diagnosis file when the current user is determined to have no downloading authority.
The download authority may be preset, for example, the download authority is given to the user who is legally registered and successfully authenticated. Therefore, the target diagnosis file can be downloaded from the server only when the current user has the downloading right; when the current user has no download right, prompt information of the unauthorized download diagnosis file can be output to the user, so that the unauthorized download current user can find related personnel to solve the vehicle diagnosis problem in time.
It should be noted that, when feeding back the target diagnosis file, the server may enable the configuration file of the client to record an authorization validity period and a download date required for the authorization check of the target diagnosis file. That is, when receiving and storing the target diagnosis file and the authorized validity period of the target diagnosis file, the client sets the authorized validity period and the download date of the target diagnosis file in the configuration file. Therefore, the target diagnosis file can be deleted after exceeding the authorized validity period according to the configuration file, so that the safety of the target diagnosis file is guaranteed.
And S105, diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
After the target diagnosis file is obtained, the vehicle can be diagnosed by using the target diagnosis file, and a corresponding diagnosis result is obtained. Specifically, how to diagnose the vehicle by using the target terminal file may specifically refer to the existing diagnosis process, which is not described in detail herein.
By applying the method provided by the embodiment of the application, the vehicle diagnosis file stored locally is subjected to authorization check, and the vehicle diagnosis file exceeding the authorization validity period is deleted; receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis; acquiring the latest diagnosis file version number of the target vehicle type from a server; acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file; and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
In the method, in order to ensure the safety of the vehicle diagnosis file, the vehicle diagnosis file stored locally can be subjected to authorization detection, and then the vehicle diagnosis file exceeding the authorization validity period is deleted. That is, the client-stored vehicle diagnostic file has an authorization expiration date, and is cleared when the authorization expires. Thus, the risk of leakage of the vehicle diagnostic file can be reduced. When the vehicle diagnosis is required, the target vehicle type for which the diagnosis is requested is first determined. And then, acquiring the latest diagnosis file version number of the target vehicle type from the server. Thus, the target diagnostic file corresponding to the version number of the latest diagnostic file can be obtained. The reliability of the terminal result can be guaranteed by utilizing the target diagnosis file to diagnose the vehicle. It can be seen that, in the method, corresponding vehicle terminal files are respectively stored according to vehicle types, the local storage validity period is set, the vehicle terminal files are cleared when the vehicle terminal files are expired, and when vehicle diagnosis is needed, the latest diagnosis file version number is taken as a link to obtain a target diagnosis file to complete diagnosis. The safety of the vehicle diagnosis file is guaranteed, and the reliability of the vehicle diagnosis result is guaranteed.
In order to facilitate those skilled in the art to better understand the vehicle diagnosis method provided in the present application, the following describes the vehicle diagnosis method in detail with reference to a specific application scenario as an example.
As shown in fig. 2, a host factory developer develops a PDX file of diagnostic data according to a vehicle type, uploads the PDX file to a server, marks a version number, and accesses the server through the read vehicle type name to obtain a latest diagnostic data version number, compares the latest diagnostic data version number with a local server, and intelligently downloads the latest diagnostic data for vehicle diagnosis, and please refer to fig. 2 and 3 for detailed steps.
Wherein fig. 2 updates the vehicle diagnostic file in the server and sets the user download authority, authorization validity period (number of days shown in the figure that can be saved locally). Namely, a host factory developer can develop a diagnostic data PDX file through a vehicle type, upload the diagnostic data PDX file to a server, identify the version number, set the number of days of local storage of the PDX file of each vehicle type, and set the downloading authority of a user. In the figure, a vehicle model corresponds to a diagnostic data file, wherein Vxx-xxx represents the version number of the vehicle model diagnostic data file. For example, NC-31.PDX, which represents that the diagnostic data file is diagnostic data of an NC-31 vehicle model, V22.13 indicates that its version number is 22.13.
Fig. 3 is a processing flow corresponding to the client. The specific process is as follows:
after the user starts the client, the client judges whether the vehicle diagnosis file stored locally needs to be deleted. Specifically, if the authorized validity period is exceeded, the local diagnostic data file (the in-vehicle diagnostic file) is deleted. Whether the current authorization retention days are larger than 0 can be adopted to determine whether the authorization validity period is exceeded, namely, the current authorization retention days are larger than 0, which indicates that the authorization validity period is still within; and if the current authorized retention days are less than or equal to 0, indicating that the local vehicle diagnosis file exceeds the authorized validity period.
And when the vehicle diagnosis file does not exceed the authorized validity period, reading the vehicle information, transmitting the vehicle information to the server under the networking condition, and returning the latest version number of the target diagnosis file matched with the vehicle information by the server according to the information. If the local diagnostic file does not exist and the user has the right to download the vehicle type diagnostic data, directly downloading the latest diagnostic data file (the same as the target diagnostic file) from the server; if the corresponding diagnostic data file exists locally, comparing the local version with the version on the server, and downloading the latest diagnostic data file to cover the original version when the server is the latest version and the user has the downloading right. If the user has no download authority, the user can contact the host computer factory after-sales personnel. After the latest diagnosis data file is downloaded, the version number of the latest diagnosis data file is transferred to the local configuration file, and the date of the downloaded file is updated, so that the next comparison is facilitated. After the latest diagnostic data file is obtained, the file can be analyzed to perform vehicle diagnosis.
Therefore, the vehicle diagnosis method provided by the embodiment of the application is mainly used for automatically issuing the PDX file for configuring the client side through the server, the client side intelligently updates the PDX file according to the vehicle type by comparing the versions of the PDX file on the local side and the PDX file on the server, the PDX file can be periodically cleared, the local side cannot be always reserved, and the safety of core data is ensured.
Example two:
corresponding to the above method embodiments, the present application embodiment also provides a vehicle diagnosis device, and the vehicle diagnosis device described below and the vehicle diagnosis method described above can be referred to correspondingly.
Referring to fig. 5, the apparatus includes the following modules:
the file cleaning module 101 is used for performing authorization check on the locally stored vehicle diagnostic files and deleting the vehicle diagnostic files exceeding the authorization validity period;
the diagnosis request receiving module 102 is used for receiving and analyzing a vehicle diagnosis request and determining a target vehicle type for requesting diagnosis;
a version number obtaining module 103, configured to obtain a latest diagnostic file version number of the target vehicle type from the server;
a diagnostic file obtaining module 104, configured to obtain a target diagnostic file corresponding to the latest diagnostic file version number;
and the vehicle diagnosis module 105 is used for diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
The device provided by the embodiment of the application is applied to carry out authorization check on the vehicle diagnosis file stored locally and delete the vehicle diagnosis file exceeding the authorization validity period; receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis; acquiring the latest diagnosis file version number of the target vehicle type from a server; acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file; and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
In the method, in order to ensure the safety of the vehicle diagnosis file, the vehicle diagnosis file stored locally can be subjected to authorization detection, and then the vehicle diagnosis file exceeding the authorization validity period is deleted. That is, the client-stored vehicle diagnostic file has an authorization expiration date, and is cleared when the authorization expires. Thus, the risk of leakage of the vehicle diagnostic file can be reduced. When the vehicle diagnosis is required, the target vehicle type for which the diagnosis is requested is first determined. And then, acquiring the latest diagnosis file version number of the target vehicle type from the server. Thus, the target diagnostic file corresponding to the version number of the latest diagnostic file can be obtained. The reliability of the terminal result can be guaranteed by utilizing the target diagnosis file to diagnose the vehicle. It can be seen that, in the method, corresponding vehicle terminal files are respectively stored according to vehicle types, the local storage validity period is set, the vehicle terminal files are cleared when the vehicle terminal files are expired, and when vehicle diagnosis is needed, the latest diagnosis file version number is taken as a link to obtain a target diagnosis file to complete diagnosis. The safety of the vehicle diagnosis file is guaranteed, and the reliability of the vehicle diagnosis result is guaranteed.
In a specific embodiment of the present application, the diagnostic file obtaining module 104 is specifically configured to determine whether a diagnostic file corresponding to a target vehicle type is stored locally; if not, acquiring a target diagnosis file from the server; if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
In an embodiment of the present application, the diagnostic file obtaining module 104 is specifically configured to delete the diagnostic file and obtain the target diagnostic file from the server when the version number of the diagnostic file is lower than the latest version number of the diagnostic file.
In a specific embodiment of the present application, the diagnostic file obtaining module 104 is specifically configured to send a file download request carrying a target vehicle type to a server when it is determined that a current user has a download right; and receiving and storing the target diagnosis file fed back by the server.
In a specific embodiment of the present application, the diagnostic file obtaining module 104 is further configured to output a prompt message for downloading the unauthorized diagnostic file when it is determined that the current user has no download right.
In an embodiment of the present application, the diagnostic file obtaining module 104 is specifically configured to, when receiving and storing the target diagnostic file and the authorized validity period of the target diagnostic file, set the authorized validity period and the download date of the target diagnostic file in the configuration file
In one embodiment of the present application, the file authorization detection module 101 is specifically configured to read a download date and an authorization validity period of a vehicle diagnostic file in a configuration file; judging whether the vehicle diagnosis file exceeds the authorized validity period or not by combining the authorized validity period and the downloading date; if not, reserving the vehicle diagnosis file; and if so, deleting the vehicle diagnosis file.
Example three:
corresponding to the above method embodiment, the present application embodiment also provides a vehicle diagnosis device, and a vehicle diagnosis device described below and a vehicle diagnosis method described above can be correspondingly referred to each other.
Referring to fig. 6, the vehicle diagnosis apparatus includes:
a memory D1 for storing computer programs;
a processor D2, configured to implement the following steps when executing the computer program:
carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period;
receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis;
acquiring the latest diagnosis file version number of the target vehicle type from a server;
acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file;
and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
Preferably, the processor, when executing the computer program, is configured to implement the following steps:
acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file, wherein the target diagnostic file comprises:
judging whether a diagnosis file corresponding to a target vehicle type is stored locally;
if not, acquiring a target diagnosis file from the server;
if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
Preferably, the processor, when executing the computer program, is configured to implement the following steps:
and when the version number of the diagnostic file is lower than the latest diagnostic file version number, deleting the diagnostic file and acquiring the target diagnostic file from the server.
Preferably, the processor, when executing the computer program, is configured to implement the following steps:
obtaining a target diagnosis file from a server, comprising:
when determining that the current user has the downloading right, sending a file downloading request carrying a target vehicle type to a server;
and receiving and storing the target diagnosis file fed back by the server.
Preferably, the processor, when executing the computer program, further performs the steps of:
and when the current user is determined not to have the download right, outputting prompt information of the unauthorized download diagnosis file.
Preferably, the processor, when executing the computer program, is configured to implement the following steps:
receiving and storing a target diagnosis file fed back by a server, wherein the target diagnosis file comprises:
and when the target diagnosis file and the authorized validity period of the target diagnosis file are received and stored, the authorized validity period and the downloading date of the target diagnosis file are set in the configuration file.
Preferably, the processor, when executing the computer program, is configured to implement the following steps:
the method for checking the authorization of the vehicle diagnostic files stored locally and deleting the vehicle diagnostic files exceeding the authorized validity period comprises the following steps:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
judging whether the vehicle diagnosis file exceeds the authorized validity period or not by combining the authorized validity period and the downloading date;
if not, reserving the vehicle diagnosis file; and if so, deleting the vehicle diagnosis file.
Specifically, referring to fig. 7, a specific structure diagram of a vehicle diagnostic device provided in this embodiment is shown, where the vehicle diagnostic device may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing an application 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the storage medium 330 to execute a series of instruction operations in the storage medium 330 on the vehicle diagnostic apparatus 301.
The vehicle diagnostic apparatus 301 may also include one or more power sources 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341. Such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps in the vehicle diagnostic method described above may be implemented by the structure of the vehicle diagnostic apparatus.
Example four:
corresponding to the above method embodiment, the present application embodiment further provides a readable storage medium, and a readable storage medium described below and a vehicle diagnosis method described above may be correspondingly referred to each other.
A readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period;
receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis;
acquiring the latest diagnosis file version number of the target vehicle type from a server;
acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file;
and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
Preferably, the computer program when executed by the processor embodies the steps of:
acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file, wherein the target diagnostic file comprises:
judging whether a diagnosis file corresponding to a target vehicle type is stored locally;
if not, acquiring a target diagnosis file from the server;
if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
Preferably, the computer program when executed by the processor embodies the steps of:
and when the version number of the diagnostic file is lower than the latest diagnostic file version number, deleting the diagnostic file and acquiring the target diagnostic file from the server.
Preferably, the computer program when executed by the processor embodies the steps of:
obtaining a target diagnosis file from a server, comprising:
when determining that the current user has the downloading right, sending a file downloading request carrying a target vehicle type to a server;
and receiving and storing the target diagnosis file fed back by the server.
Preferably, the computer program when executed by the processor further implements the steps of:
and when the current user is determined not to have the download right, outputting prompt information of the unauthorized download diagnosis file.
Preferably, the computer program when executed by the processor embodies the steps of:
receiving and storing a target diagnosis file fed back by a server, wherein the target diagnosis file comprises:
and when the target diagnosis file and the authorized validity period of the target diagnosis file are received and stored, the authorized validity period and the downloading date of the target diagnosis file are set in the configuration file.
Preferably, the computer program when executed by the processor embodies the steps of:
the method for checking the authorization of the vehicle diagnostic files stored locally and deleting the vehicle diagnostic files exceeding the authorized validity period comprises the following steps:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
judging whether the vehicle diagnosis file exceeds the authorized validity period or not by combining the authorized validity period and the downloading date;
if not, reserving the vehicle diagnosis file; and if so, deleting the vehicle diagnosis file.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
Claims (10)
1. A vehicle diagnostic method, characterized by comprising:
carrying out authorization check on the vehicle diagnostic files stored locally, and deleting the vehicle diagnostic files exceeding the authorization validity period;
receiving and analyzing a vehicle diagnosis request, and determining a target vehicle type requiring diagnosis;
acquiring the latest diagnosis file version number of the target vehicle type from a server;
acquiring a target diagnosis file corresponding to the version number of the latest diagnosis file;
and diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
2. The vehicle diagnostic method of claim 1, wherein obtaining the target diagnostic file corresponding to the latest diagnostic file version number comprises:
judging whether a diagnosis file corresponding to the target vehicle type is stored locally;
if not, acquiring the target diagnosis file from the server;
if so, determining the diagnostic file as the target diagnostic file when the version number of the diagnostic file is the same as the latest diagnostic file version number.
3. The vehicle diagnostic method according to claim 2, characterized in that, when the version number of the diagnostic file is lower than the latest diagnostic file version number, the diagnostic file is deleted and the target diagnostic file is acquired from the server.
4. The vehicle diagnostic method of claim 2, wherein obtaining the target diagnostic file from the server comprises:
when the current user is determined to have the downloading right, sending a file downloading request carrying the target vehicle type to the server;
and receiving and storing the target diagnosis file fed back by the server.
5. The vehicle diagnostic method according to claim 4, characterized by further comprising:
and outputting prompt information of the unauthorized downloading of the diagnosis file when the current user is determined to have no downloading authorization.
6. The vehicle diagnostic method of claim 4, wherein said receiving and storing said target diagnostic file fed back by said server comprises:
and when the target diagnosis file and the authorized validity period of the target diagnosis file are received and stored, setting the authorized validity period and the downloading date of the target diagnosis file in a configuration file.
7. The vehicle diagnostic method of claim 1, wherein the performing an authorization check on the locally stored vehicle diagnostic file and deleting the vehicle diagnostic file that exceeds an authorization validity period comprises:
reading the download date and the authorized validity period of the vehicle diagnosis file in the configuration file;
judging whether the vehicle diagnosis file exceeds the authorized effective period or not by combining the authorized effective period and the downloading date;
if not, the vehicle diagnosis file is reserved; and if so, deleting the vehicle diagnosis file.
8. A vehicle diagnostic device characterized by comprising:
the file authorization detection module is used for carrying out authorization check on the vehicle diagnostic files stored locally and deleting the vehicle diagnostic files exceeding the authorization validity period;
the diagnosis request receiving module is used for receiving and analyzing a vehicle diagnosis request and determining a target vehicle type requiring diagnosis;
the version number acquisition module is used for acquiring the latest diagnostic file version number of the target vehicle type from a server;
the diagnostic file acquisition module is used for acquiring a target diagnostic file corresponding to the version number of the latest diagnostic file;
and the vehicle diagnosis module is used for diagnosing the vehicle by using the target diagnosis file to obtain a diagnosis result.
9. A vehicle diagnostic apparatus characterized by comprising:
a memory for storing a computer program;
a processor for implementing the steps of the vehicle diagnostic method according to any one of claims 1 to 7 when executing the computer program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the vehicle diagnostic method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911158880.4A CN110716538A (en) | 2019-11-22 | 2019-11-22 | Vehicle diagnosis method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911158880.4A CN110716538A (en) | 2019-11-22 | 2019-11-22 | Vehicle diagnosis method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110716538A true CN110716538A (en) | 2020-01-21 |
Family
ID=69216336
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911158880.4A Pending CN110716538A (en) | 2019-11-22 | 2019-11-22 | Vehicle diagnosis method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110716538A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111742354A (en) * | 2020-05-29 | 2020-10-02 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, system, equipment and server |
| CN112729868A (en) * | 2020-12-25 | 2021-04-30 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and medium |
| CN113050601A (en) * | 2021-03-22 | 2021-06-29 | 深圳市元征科技股份有限公司 | Vehicle offline diagnosis method and device, diagnosis equipment and storage medium |
| CN113759883A (en) * | 2021-10-26 | 2021-12-07 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, vehicle gateway device, server, and storage medium |
| CN114281361A (en) * | 2021-12-22 | 2022-04-05 | 深圳市元征科技股份有限公司 | Software processing method and device, electronic equipment and storage medium |
| CN115220416A (en) * | 2021-12-07 | 2022-10-21 | 广州汽车集团股份有限公司 | Vehicle diagnosis method, vehicle-mounted terminal, system and storage medium |
| CN116560721A (en) * | 2023-07-06 | 2023-08-08 | 北京集度科技有限公司 | Vehicle diagnosis system, method and electronic equipment |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1388926A (en) * | 2000-07-03 | 2003-01-01 | 株式会社阿克赛思 | Mobile information terminal device, storage server, and method for providing storage region |
| CN101059759A (en) * | 2006-04-21 | 2007-10-24 | 鸿富锦精密工业（深圳）有限公司 | Procedure dynamic burning system |
| JP2008052660A (en) * | 2006-08-28 | 2008-03-06 | Hitachi Ltd | Diagnostic device for moving body, diagnostic terminal for moving body, and inverter device |
| US20130138675A1 (en) * | 2011-11-25 | 2013-05-30 | Lsis Co., Ltd | Method of managing program for electric vehicle |
| CN103345243A (en) * | 2013-06-27 | 2013-10-09 | 深圳市元征科技股份有限公司 | Method and device for brushing vehicle electronic control unit program |
| CN103576668A (en) * | 2012-07-26 | 2014-02-12 | 博世汽车检测设备(深圳)有限公司 | Method and device for vehicle diagnosis |
| CN104656637A (en) * | 2015-01-15 | 2015-05-27 | 深圳市元征软件开发有限公司 | Method and system for backing up data of automobile diagnostic equipment |
| CN109164783A (en) * | 2018-07-26 | 2019-01-08 | 深圳市元征科技股份有限公司 | Vehicular diagnostic method, device, equipment and medium |
| CN109918361A (en) * | 2019-03-11 | 2019-06-21 | 威马智慧出行科技（上海）有限公司 | The creation method and device and data-storage system of vehicle diagnosis database |
| CN110109443A (en) * | 2019-05-13 | 2019-08-09 | 上海英恒电子有限公司 | Safety communicating method, device, storage medium and the equipment of vehicle diagnostics |
-
2019
- 2019-11-22 CN CN201911158880.4A patent/CN110716538A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1388926A (en) * | 2000-07-03 | 2003-01-01 | 株式会社阿克赛思 | Mobile information terminal device, storage server, and method for providing storage region |
| CN101059759A (en) * | 2006-04-21 | 2007-10-24 | 鸿富锦精密工业（深圳）有限公司 | Procedure dynamic burning system |
| JP2008052660A (en) * | 2006-08-28 | 2008-03-06 | Hitachi Ltd | Diagnostic device for moving body, diagnostic terminal for moving body, and inverter device |
| US20130138675A1 (en) * | 2011-11-25 | 2013-05-30 | Lsis Co., Ltd | Method of managing program for electric vehicle |
| CN103576668A (en) * | 2012-07-26 | 2014-02-12 | 博世汽车检测设备(深圳)有限公司 | Method and device for vehicle diagnosis |
| CN103345243A (en) * | 2013-06-27 | 2013-10-09 | 深圳市元征科技股份有限公司 | Method and device for brushing vehicle electronic control unit program |
| CN104656637A (en) * | 2015-01-15 | 2015-05-27 | 深圳市元征软件开发有限公司 | Method and system for backing up data of automobile diagnostic equipment |
| CN109164783A (en) * | 2018-07-26 | 2019-01-08 | 深圳市元征科技股份有限公司 | Vehicular diagnostic method, device, equipment and medium |
| CN109918361A (en) * | 2019-03-11 | 2019-06-21 | 威马智慧出行科技（上海）有限公司 | The creation method and device and data-storage system of vehicle diagnosis database |
| CN110109443A (en) * | 2019-05-13 | 2019-08-09 | 上海英恒电子有限公司 | Safety communicating method, device, storage medium and the equipment of vehicle diagnostics |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111742354A (en) * | 2020-05-29 | 2020-10-02 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, system, equipment and server |
| WO2021237648A1 (en) * | 2020-05-29 | 2021-12-02 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, system, and device, and server |
| CN112729868A (en) * | 2020-12-25 | 2021-04-30 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and medium |
| CN113050601A (en) * | 2021-03-22 | 2021-06-29 | 深圳市元征科技股份有限公司 | Vehicle offline diagnosis method and device, diagnosis equipment and storage medium |
| CN113759883A (en) * | 2021-10-26 | 2021-12-07 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, vehicle gateway device, server, and storage medium |
| CN115220416A (en) * | 2021-12-07 | 2022-10-21 | 广州汽车集团股份有限公司 | Vehicle diagnosis method, vehicle-mounted terminal, system and storage medium |
| CN114281361A (en) * | 2021-12-22 | 2022-04-05 | 深圳市元征科技股份有限公司 | Software processing method and device, electronic equipment and storage medium |
| CN116560721A (en) * | 2023-07-06 | 2023-08-08 | 北京集度科技有限公司 | Vehicle diagnosis system, method and electronic equipment |
| CN116560721B (en) * | 2023-07-06 | 2023-11-17 | 北京集度科技有限公司 | Vehicle diagnosis system, method and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110716538A (en) | Vehicle diagnosis method, device, equipment and readable storage medium | |
| US7366589B2 (en) | Method and system for remote reflash | |
| CN108418787B (en) | Method for acquiring enterprise resource planning data, terminal device and medium | |
| CN110888662A (en) | Vehicle remote silent upgrading method and device, vehicle and storage medium | |
| US10942728B2 (en) | Deploying device campaign updates to IoT devices | |
| CN104572320A (en) | Method for confirming correction program and information processing apparatus | |
| CN110928561B (en) | Vehicle controller software version management method and device, vehicle and storage medium | |
| CN109818962B (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN113595788B (en) | API gateway management method and device based on plug-in | |
| CN107623735B (en) | Accurate updating and upgrading system and method based on openssl in credit investigation machine system | |
| CN113569285A (en) | Identity authentication and authorization method, device, system, equipment and storage medium | |
| CN111694590A (en) | Upgrading method of intelligent water meter | |
| CN116257270A (en) | Vehicle, upgrading method and device of vehicle | |
| CN113824554B (en) | Dynamic authentication method, device and computer medium for data transmission between middleware | |
| CN114138303A (en) | Vehicle application program updating method, device, medium and vehicle | |
| CN113221151A (en) | Data processing method and device based on block chain and storage medium | |
| CN112084114A (en) | Method and apparatus for testing an interface | |
| CN111459525A (en) | Application update data processing system, application update data processing method, storage medium, and computer | |
| CN111949980A (en) | Target client monitoring method and device, storage medium and electronic device | |
| CN114144759A (en) | Method and device for updating software of a vehicle computer comprising an execution memory, a backup memory and a check memory | |
| CN111143832A (en) | Mobile terminal SDK (software development kit) suitable for multiple scenes and hybrid authorization method thereof | |
| CN117156474B (en) | Remote intelligent operation and maintenance system and operation and maintenance method thereof | |
| CN112055849A (en) | Exclusive control system and exclusive control method | |
| CN115167887B (en) | Upgrading method and device, storage medium and electronic equipment | |
| CN115695529B (en) | Intelligent remote operation and maintenance method and device, computer equipment and storage medium |
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 |
Application publication date: 20200121 |
|
| RJ01 | Rejection of invention patent application after publication |