CN113835729A

CN113835729A - Upgrading method and device, terminal equipment and computer readable storage medium

Info

Publication number: CN113835729A
Application number: CN202111114222.2A
Authority: CN
Inventors: 刘均; 樊球
Original assignee: Shenzhen Launch Technology Co Ltd
Current assignee: Shenzhen Launch Technology Co Ltd
Priority date: 2021-09-23
Filing date: 2021-09-23
Publication date: 2021-12-24
Anticipated expiration: 2041-09-23
Also published as: CN113835729B

Abstract

The application is applicable to the technical field of vehicle diagnosis equipment, and provides an upgrading method, an upgrading device, terminal equipment and a computer-readable storage medium, wherein the upgrading method comprises the following steps: acquiring the version number of a first interface communication library according to the registry of the software client, wherein the first interface communication library is an executable file which can be identified by the software client and is used for processing communication between the software client and a second interface lower computer, and the second interface lower computer is used for communicating with an electronic control unit of a vehicle; acquiring the version number of the second interface lower computer; and if the acquired version number of the first interface communication library is lower than the version number of the first interface communication library stored by the server, and/or if the acquired version number of the second interface lower computer is lower than the version number of the second interface lower computer stored by the server, upgrading the first interface communication library and/or the second interface lower computer of the software client. By the method, the success rate of upgrading can be improved.

Description

Upgrading method and device, terminal equipment and computer readable storage medium

Technical Field

The application belongs to the technical field of vehicle diagnosis equipment, and particularly relates to an upgrading method, an upgrading device, terminal equipment and a computer-readable storage medium.

Background

With the continuous development of automotive electronics, automotive diagnostic technology is also continuously updated. In order to solve the problem of inconsistent Diagnostic Interfaces of different manufacturers, a standardized vehicle communication interface (D-PDU) is proposed and widely used.

The diagnostic equipment based on the D-PDU consists of a Vehicle Communication Interface (VCI) lower computer and a D-PDU Communication library. In the actual use process, the situation that the VCI lower computer or the D-PDU communication library needs to be upgraded and updated sometimes occurs.

The existing upgrading is generally carried out in two ways, one way is that an upgrading installation package is sent to a client needing upgrading independently, and then manual upgrading is carried out by a user. The other method is upgrading and pushing through a network, the method comprises the steps that a client extracts corresponding version numbers from version information of VCI and D-PDU stored in a local configuration file, the extracted version numbers of the VCI and the D-PDU are sent to a server, the server compares the stored version numbers of the VCI and the D-PDU with the version numbers of the VCI and the D-PDU received from the client, and finally, whether upgrading and pushing are carried out or not is selected according to a comparison result.

In the upgrading method, the first upgrading mode is very complicated, the workload is very large, and the upgrading method is not intelligent. In the second upgrading mode, since the configuration file storing the version information is stored in the local computer, the configuration file may be changed or deleted by mistake by the user, which may cause upgrading problems.

Disclosure of Invention

The embodiment of the application provides an upgrading method, an upgrading device, terminal equipment and a computer readable storage medium, and can solve the problems that the existing method is not intelligent and cannot be upgraded normally.

In a first aspect, an embodiment of the present application provides an upgrade method, applied to a software client, including:

acquiring the version number of a first interface communication library according to a registry of the software client, wherein the registry stores a storage path of the first interface communication library, the first interface communication library is used for processing communication between the software client and a second interface lower computer, and the second interface lower computer is used for communicating with an electronic control unit of a vehicle;

acquiring the version number of the second interface lower computer;

and if the acquired version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server, and/or if the acquired version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server, prompting to upgrade the first interface communication library and/or the second interface lower computer of the software client.

Optionally, the obtaining a version number of the first interface communication library according to the registry of the software client includes:

reading a storage path of the first interface communication library from a registry of the software client;

and searching the corresponding first interface communication library according to the storage path of the first interface communication library, and reading the version number of the searched first interface communication library.

Optionally, before the obtaining of the version number of the first interface communication library according to the registry of the software client, the method includes:

when the driver installation package is installed on the software client, a first interface communication library in the driver installation package is stored in a local directory, and a storage path of the first interface communication library is written into a registry of the software client.

Optionally, the obtaining of the version number of the second interface lower computer includes:

sending a version number reading command to the second interface lower computer through the first interface communication library;

and receiving the version number of the second interface lower computer returned by the second interface lower computer through the first interface communication library.

Optionally, before the prompting to upgrade the first interface communication library and/or the second interface lower computer of the software client, the method includes:

sending an upgrade request to the server, wherein the upgrade request comprises a unique identifier of the second interface lower computer, and the software client sends the unique identifier of the second interface lower computer, the current version number of the second interface lower computer, the media access control address of the terminal equipment where the software client is located and the current version number of the first interface communication library in the software client to the server in advance for binding storage;

correspondingly, after the prompt is to upgrade the first interface communication library of the software client and/or the second interface lower computer, the method comprises the following steps:

receiving an upgrade installation package of a first interface communication library and/or a second interface lower computer sent by the server based on the upgrade request;

and upgrading the first interface communication library and/or the second interface lower computer according to the upgrading installation package.

Optionally, after the first interface communication library of the software client and/or the second interface lower computer are/is upgraded, the method further includes:

and sending the unique identifier of the second interface lower computer, the current version number of the first interface communication library of the software client and the version number of the second interface lower computer to the server.

Optionally, the method further comprises:

if a history version backtracking instruction sent by a user is received, sending a history version request to the server, wherein the history version request carries a unique identifier of the lower computer of the second interface;

receiving historical version information returned by the server, wherein the historical version information comprises: before the current moment, each version number of a first interface communication library and each version number of a second interface lower computer which are installed by the software client are determined;

displaying the historical version information, and a backtracking inlet corresponding to each version number of a first interface communication library and a backtracking inlet corresponding to each version number of a second interface lower computer which are installed by the software client;

and if the condition that the user accesses one backtracking inlet is detected, updating the first interface communication library of the software client into the first interface communication library corresponding to the backtracking inlet, and/or updating the second interface lower computer of the software client into the second interface lower computer corresponding to the backtracking inlet.

In a second aspect, an embodiment of the present application provides an upgrading apparatus, which is applied to a software client, and includes:

the version number acquisition module of the first interface communication library is used for acquiring the version number of the first interface communication library according to a registry of the software client, the registry stores a storage path of the first interface communication library, the first interface communication library is used for processing communication between the software client and a second interface lower computer, and the second interface lower computer is used for communicating with an electronic control unit of a vehicle;

the version number acquisition module of the second interface lower computer is used for acquiring the version number of the second interface lower computer;

and the upgrading prompting module is used for prompting upgrading of the first interface communication library and/or the second interface lower computer of the software client if the acquired version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server and/or the acquired version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server.

In a third aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the method according to any one of the first aspect when executing the computer program.

In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the method according to any one of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product, which, when run on a software client, causes the software client to perform the method of any one of the above first aspects.

Compared with the prior art, the embodiment of the application has the advantages that:

in the embodiment of the application, because the version number of the first interface communication library is obtained according to the registry of the software client, and the information recorded by the registry is usually difficult to change, the accurate version number of the first interface communication library can be obtained by the above method, so that the accuracy of the subsequent comparison result is ensured, the success rate of the subsequent upgrade is further improved, and the good experience of the user is further improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.

FIG. 1 is a schematic diagram of a prior art method for storing a version number of a D-PDU and a version number of a VCI in a local configuration file;

FIG. 2 is a flowchart illustrating a first upgrading method according to an embodiment of the present application;

FIG. 3 is a flowchart illustrating a second upgrading method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an application scenario of a software client interacting with a server, a VCI and a vehicle according to an embodiment of the present application;

fig. 5 is a schematic view of a setting interface for setting information of an upgrade installation package according to another embodiment of the present application;

FIG. 6 is a schematic diagram of an upgrade prompt provided by an embodiment of the present application;

FIG. 7 is a block diagram of an upgrade apparatus according to another embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise.

The first embodiment is as follows:

in the existing upgrading method of the diagnostic equipment, if an upgrading installation package is sent to a client needing upgrading independently and then manual upgrading is carried out by a user, the workload is very large and the experience for the user is not good; if the upgrade pushing is performed through the network, the version number of the diagnostic device extracted by the method is extracted from a local configuration file (an example of the local configuration file is shown in fig. 1, the version number of the D-PDU is v1.0.0.4, and the version number of the VCI is v10.03), and the local configuration file may be modified or deleted by the user by mistake, so the method may cause the upgrade pushing to fail.

In order to solve the above technical problem, an embodiment of the present application provides an upgrading method, in which a software client obtains a version number of a first interface communication library and a version number of a second interface lower computer according to a registry, and then upgrades a first interface communication library and/or the second interface lower computer of the software client according to a corresponding comparison result of the obtained version number of the first interface communication library, the obtained version number of the second interface lower computer, a latest version number of the first interface communication library stored by a server, and the latest version number of the second interface lower computer.

The version number of the first interface communication library is obtained according to the registry, and the information recorded by the registry is usually difficult to change, so that the accuracy of the obtained version number of the first interface communication library is ensured, and the accuracy of a subsequent comparison result is further ensured. Meanwhile, after the version number of the second interface lower computer is obtained, if the obtained version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server, and/or if the obtained version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server, the first interface communication library and/or the second interface lower computer of the software client side are/is upgraded, so that manual upgrading of a user is not needed, and good experience of the user is improved.

The following describes an upgrade method provided in an embodiment of the present application with reference to the drawings.

Fig. 2 is a schematic flowchart illustrating a first upgrading method provided in an embodiment of the present application, where the upgrading method is applied to a software client, where the software client may be diagnostic software installed in a terminal device, and the upgrading method in the embodiment of the present application is detailed as follows:

and step S21, acquiring the version number of a first interface communication library according to the registry of the software client, wherein the registry stores the storage path of the first interface communication library, the first interface communication library is used for processing the communication between the software client and a second interface lower computer, and the second interface lower computer is used for communicating with an electronic control unit of the vehicle.

The first interface communication library is an executable file which can be identified by the software client.

In this embodiment, the registry of the software client records relevant information of the first interface communication library, for example, records a storage path of the first interface communication library, finds the first interface communication library through the storage path, and then directly obtains current accurate version number information from the first interface communication library itself. In some other embodiments, the current version number of the first interface library may also be recorded in the registry and updated after each upgrade. In some embodiments, the first interface communication library is a D-PDU communication library, and the second interface lower computer is a VCI lower computer.

In this embodiment, in order to conveniently and timely determine whether the first interface communication library and the second interface lower computer need to execute the upgrade operation subsequently, after the software client (equivalent to the diagnostic software) is started each time, the software client acquires the version number of the first interface communication library according to the registry.

And step S22, acquiring the version number of the second interface lower computer.

In this embodiment, it is considered that the second interface lower computer may also have an update, and therefore the software client needs to obtain the current version number of the second interface lower computer.

And step S23, if the obtained version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server, and/or if the obtained version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server, prompting to upgrade the first interface communication library and/or the second interface lower computer of the software client.

In this embodiment, the comparison process of the version numbers may be executed at the software client, or may be executed at the server.

When the software client executes the comparison process of the version numbers, the software client needs to acquire the latest version number of the first interface communication library and the latest version number of the second interface lower computer stored in the server from the server, compare the version number of the first interface communication library stored in the software client with the latest version number of the first interface communication library acquired from the server, and compare the version number of the second interface lower computer stored in the software client with the latest version number of the second interface lower computer acquired from the server.

When the server executes the comparison process of the version numbers, the software client sends the unique identifier of the second interface lower computer, the version number of the second interface lower computer and the version number of the first interface communication library to the server, and the server compares the stored latest version number of the first interface communication library with the version number of the first interface communication library received from the software client and compares the stored latest version number of the second interface lower computer with the version number of the second interface lower computer received from the software client.

In this embodiment, when it is determined that the first interface communication library and/or the second interface lower computer meet the upgrade condition, the upgrade of the first interface communication library and/or the second interface lower computer of the software client is automatically prompted.

In the embodiment of the application, because the version number of the first interface communication library is obtained according to the registry of the software client, and the information recorded by the registry is usually difficult to change, the accuracy of the obtained version number of the first interface communication library is ensured, so that the accuracy of a subsequent comparison result is ensured, and the success rate of subsequent upgrading is further improved. Meanwhile, after the version number of the second interface lower computer is obtained, if the obtained version number of the first interface communication library is lower than the version number of the first interface communication library stored by the server, and/or if the obtained version number of the second interface lower computer is lower than the version number of the second interface lower computer stored by the server, the first interface communication library of the software client and/or the second interface lower computer are prompted to be upgraded, so that the generated prompt can be more accurate, a user does not need to manually upgrade, and good experience of the user is improved.

Example two:

fig. 3 shows a schematic flowchart of a second upgrading method provided in this embodiment, where this embodiment mainly further describes step S21, and step S33 and step S34 are respectively the same as step S22 and step S23 in the first embodiment, and are not repeated here:

step S31, reading the storage path of the first interface communication library from the registry of the software client.

In this embodiment, since the information recorded in the registry is very detailed and the probability of the information recorded in the registry being deleted by mistake is very small, the storage path of the first interface communication library can be safely and quickly read from the registry. Specifically, assuming that the name of the diagnostic software is "SmartBox", the storage path of the diagnostic software at the terminal device is searched in the registry according to the SmartBox.

Step S32, finding the corresponding first interface communication library according to the storage path of the first interface communication library, and reading the version number of the found first interface communication library.

Specifically, assume that the storage path found in the registry according to the SmartBox is "C: \\ Program Files (x86) \ SmartBox3.0\ SmartBox3.0\ D-PDU', indicating that the SmartBox is stored in the C disk of the terminal equipment, finding the D-PDU communication library according to the storage path, and reading the corresponding version number from the file version field in the detailed information of the D-PDU communication library.

And step S33, acquiring the version number of the second interface lower computer.

And step S34, if the obtained version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server, and/or if the obtained version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server, prompting to upgrade the first interface communication library and/or the second interface lower computer of the software client.

In the embodiment of the application, the software client reads the storage path of the first interface communication library from the registry, then finds the corresponding first interface communication library according to the storage path, and reads the version number of the first interface communication library. The version number of the first interface communication library is directly read from the first interface communication library, so that the accuracy of the read version number can be ensured.

In some embodiments, before the step S21, the method further includes:

when the driver installation package is installed on the software client, the first interface communication library in the driver installation package is stored in a local directory, and the storage path of the first interface communication library is written into the registry of the software client.

In this embodiment, the software client is equivalent to diagnostic software, and when the diagnostic software is installed for the first time on the terminal device, the diagnostic software automatically installs the corresponding driver installation package, and writes the storage path of the first interface communication library included in the driver installation package into the registry of the software client, so that the storage path of the first interface communication library can be read from the registry in the following process.

In some embodiments, in order to obtain a more accurate version number of the second interface lower computer, the step S22 (or the step S33) includes:

a1, sending a version number reading command to the second interface lower computer through the first interface communication library.

The version number reading command is used for indicating the second interface lower computer to return the version number of the second interface lower computer to the first interface communication library.

And A2, receiving the version number of the second interface lower computer returned by the second interface lower computer through the first interface communication library.

In the step a1 and the step a2, the software client communicates with the second interface lower computer through the first interface communication library, and obtains the version number of the second interface lower computer. The version number of the second interface lower computer is directly obtained from the second interface lower computer and is not obtained from a configuration file which is easy to be deleted by a user, so that the accuracy of the obtained version number of the second interface lower computer can be ensured.

In some embodiments, before the prompting in the step S23 (or the step S34) is to upgrade the first interface communication library and/or the second interface lower computer of the software client, the method includes:

and sending an upgrade request to the server, wherein the upgrade request comprises the unique identifier of the second interface lower computer, and the software client sends the unique identifier of the second interface lower computer, the current version number of the second interface lower computer, the media access control address of the terminal equipment where the software client is located and the current version number of the first interface communication library in the software client to the server in advance for binding storage.

The unique identification of the second interface lower computer can be a serial number of the second interface lower computer.

In this embodiment, when the software client determines that the software needs to be upgraded, an upgrade request including the unique identifier of the second interface lower computer is sent to the server. The server stores the corresponding relation between the unique identifier of the second interface lower computer and the current version number of the second interface lower computer, the media access control address of the terminal equipment where the software client is located and the current version number of the first interface communication library in the software client in advance, so that after receiving an upgrade request sent by the software client, the server can search the media access control address of the terminal equipment where the software client is located, the current version number of the first interface communication library and the current version number of the second interface lower computer according to the unique identifier of the second interface lower computer included in the upgrade request, determine an upgrade installation package corresponding to the software client, and send the upgrade installation package to the software client according to the stored media access control address of the terminal equipment.

Correspondingly, after the above step S23 (or step S34), the method includes:

and B1, receiving the upgrade installation package of the first interface communication library and/or the second interface lower computer sent by the server based on the upgrade request.

And B2, upgrading the first interface communication library and/or the second interface lower computer according to the upgrading installation package.

In this embodiment, since the upgrade request is sent to the server before the upgrade is prompted, the corresponding upgrade installation package can be acquired faster after the upgrade is prompted, and then the first interface communication library and/or the second interface lower computer can be upgraded faster, so that good experience of a user is improved.

In some embodiments, after sending the upgrade request to the server, the method includes:

and receiving attribute information sent by the server based on the upgrading request, wherein the attribute information is used for indicating whether the upgrading is forced upgrading or not.

For example, when the value of the attribute information is 1, it indicates that the upgrade is a forced upgrade, and when the value of the attribute information is 0, it indicates that the upgrade is a non-forced upgrade.

Correspondingly, the step B1 specifically includes: and if the attribute information indicates that the upgrade is forced upgrade, receiving an upgrade installation package of the first interface communication library and/or the second interface lower computer sent by the server based on the upgrade request. And if the attribute information indicates that the upgrade is not forced upgrade, and after a user sends an upgrade confirmation command based on an upgrade prompt, receiving an upgrade installation package of the first interface communication library and/or the second interface lower computer sent by the server based on the upgrade request.

In this embodiment, if the upgrade only needs to upgrade the first interface communication library, the first interface communication library is directly upgraded; and if the upgrade needs to upgrade the first interface communication library and the second interface lower computer at the same time, directly upgrading the first interface communication library and the second interface lower computer.

In some embodiments, the update of the first interface communication library and/or the second interface lower computer of the software client may be prompted through a prompt box. In the prompt box, the current version number of the first interface communication library of the software client, the current version number of the second interface lower computer of the software client, the version number of the first interface communication library to be upgraded of the software client and the version number of the second interface lower computer to be upgraded of the software client can be displayed. Furthermore, the prompt box can also display the newly added functions of the first interface communication library after the upgrading, and/or the newly added functions of the second interface lower computer and the like. The information is displayed in the prompt box, so that the user can acquire more related information of the software client.

It should be noted that, if the upgrade is a forced upgrade, the user is not provided with an option of not upgrading in the prompt box, such as only providing a "confirm" button and not providing a "cancel" button. If the upgrade is not forced upgrade, providing 'confirm' button and 'cancel' button at the same time. That is, in this embodiment, if the upgrade is a forced upgrade, the prompt box only has a prompt function, and the upgrade operation is directly performed after the prompt; if the upgrade is not forced upgrade, the prompt box not only has the function of prompting, but also has the function of allowing the user to select whether to execute the upgrade operation. And after the user clicks a 'confirmation' button, the software client judges that the user sends a confirmation upgrading command based on upgrading prompt, and upgrades the first interface communication library and/or the second interface lower computer of the software client according to an upgrading installation package obtained from the server. Because the software client can judge whether the upgrade is the forced upgrade according to the attribute information received from the server, and the forced upgrade is usually set only because the old version has a serious bug and the like, when the upgrade is the forced upgrade, the software client does not provide an option of not upgrading but directly upgrades, thereby being capable of reducing the probability of the software client that an error occurs in the subsequent use process. Meanwhile, when the upgrade is not forced upgrade, options of upgrade and non-upgrade are provided for the user, namely certain authority is given to the user, so that the upgrade experience of the user is improved.

In some embodiments, after step S23 (or step S34), the method further includes:

In this embodiment, after installation and upgrade, the software client sends the unique identifier of the second interface lower computer, the current version number of the first interface communication library of the software client, and the version number of the second interface lower computer corresponding to the software client to the server, so that the server can store the unique identifier, the version number of the first interface communication library, and the version number of the second interface lower computer corresponding to the software client. The subsequent server may perform corresponding statistics according to the stored information, for example, count the number of the second interface lower computers using the first interface communication library with a certain version number. And after receiving the newly added upgrade installation package of the administrator, the server can judge which first interface communication library (or second interface lower computer) corresponding to the unique identifier of the second interface lower computer needs to be upgraded according to the stored information.

In some embodiments, the upgrade method further comprises:

and C1, if a history version backtracking instruction sent by a user is received, sending a history version request to the server, wherein the history version request carries the unique identifier of the lower computer of the second interface.

In this embodiment, an interface of the software client has a history version backtracking entry, and when a user clicks the history version backtracking entry, the software client receives a history version backtracking instruction sent by the user.

C2, receiving the history version information returned by the server, wherein the history version information includes: before the current moment, the software client side installs each version number of the first interface communication library and each version number of the second interface lower computer.

After the software client is upgraded, the unique identifier of the second interface lower computer, the current version number of the first interface communication library of the software client and the version number of the second interface lower computer are sent to the server, so that the server stores the version numbers of the first interface communication library and the second interface lower computer corresponding to the second interface lower computers. The server can return the historical version information to the software client after receiving the historical version request sent by the software client.

And C3, displaying the historical version information, and a backtracking entry corresponding to each version number of the first interface communication library and a backtracking entry corresponding to each version number of the second interface lower computer which are installed by the software client.

In this embodiment, in order to improve the flexibility of backtracking, the version number of each first interface communication library and the version number of each second interface lower computer are made to correspond to one backtracking entry, so that a user can select the version of only backtracking the first interface communication library according to a requirement, or select the version of only backtracking the second interface lower computer, or select the version of backtracking the first interface communication library and the version of the second interface lower computer at the same time.

In some embodiments, the backtracking portal may be an "upgrade" button displayed by the software client.

And C4, if it is detected that the user accesses one of the backtracking entries, updating the first interface communication library of the software client into the first interface communication library corresponding to the backtracking entry, and/or updating the second interface lower computer of the software client into the second interface lower computer corresponding to the backtracking entry.

In this embodiment, when the user accesses the backtracking entry of the first interface communication library, the software client only updates the first interface communication library, when the user accesses the backtracking entry of the second interface lower computer, the software client only updates the second interface lower computer, and when the user accesses both the backtracking entry of the first interface communication library and the backtracking entry of the second interface lower computer, the software client simultaneously updates the first interface communication library and the second interface lower computer.

In the step C1 to the step C4, the user obtains the historical version information of the software client by sending a historical version request to the software client, and then performs version backtracking on the first interface communication library and/or the second interface lower computer according to a backtracking entry corresponding to the historical version information. Because the user can backtrack the versions, the user can select the version which the user wants to use, and the good experience of the user is improved.

In some embodiments, the software client records version backtracking information, wherein the version backtracking information comprises a version number of the first interface communication library and a version number of the second interface lower computer, which are stored by the server when the version backtracking is carried out. Prior to the above step S23 (or step S34), the method includes:

and judging whether the latest version number of the first interface communication library stored in the server is the same as the version number of the first interface communication library in the version backtracking information, and judging whether the latest version number of the second interface lower computer stored in the server is the same as the version number of the second interface lower computer in the version backtracking information.

Correspondingly, the step S23 (or step S34) specifically includes:

and if the latest version number of the first interface communication library stored in the server is different from the version number of the first interface communication library in the version backtracking information, the obtained version number of the first interface communication library is lower than the latest version number of the first interface communication library stored in the server, and/or the latest version number of the second interface lower computer stored in the server is different from the version number of the second interface lower computer in the version backtracking information, and the obtained version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored in the server, prompting to upgrade the first interface communication library and/or the second interface lower computer of the software client.

In this embodiment, only when the software client performs version backtracking and the server has a new upgrade installation package, the user is prompted to perform upgrade operation, and when the server does not have a new upgrade installation package, the user is not prompted to perform upgrade operation, so that the user can be prevented from being disturbed many times, and good experience of the user is improved.

In order to more clearly describe the upgrading method provided by the embodiment of the present application, a specific application scenario is described below.

Referring to fig. 4, the first interface communication library is a D-PDU communication library, the second interface lower computer is a VCI lower computer, the personal computer with the diagnostic software installed therein is a software client, the software client communicates with a server, the server is configured to issue an upgrade installation package managed by a user to the software client, and the software client is configured to upload data to the server.

The client side comprises a D-PDU communication library, and the storage path of the D-PDU communication library is written in a registry of the personal computer. And the user operates the client, and the client communicates with the VCI lower computer by calling the D-PDU communication library, so that the vehicle is diagnosed. Wherein the version of the D-PDU communication library is scalable.

The VCI lower computer contains chip and is communicated with automobile bus, data message can be real-time returned to D-PDU communication library, and the version of VCI lower computer can be upgraded.

When the administrator stores a new upgrade installation package in the server, it needs to set the upgrade installation package, and the setting interface of the information is as shown in fig. 5. In fig. 5, the VCI version, the D-PDU version, the version upgrade content, and whether the version is a forced upgrade version in the setting interface may all be displayed in the prompt box generated in the embodiment of the present application. In addition, the setting interface also comprises a historical version of a VCI lower computer and a D-PDU communication library and the like.

And after the client is started, acquiring the version number of the D-PDU communication library from the registry of the software client, and acquiring the version number of the VCI lower computer through the D-PDU communication library. And if the upgrading operation is judged to be executed according to the acquired version number of the D-PDU communication library and the version number of the VCI lower computer, displaying corresponding prompt information on a prompt box to prompt the upgrading of the first interface communication library and/or the second interface lower computer of the software client. If the upgrade is not a forced upgrade version, the prompt information displayed by the prompt box may be as shown in fig. 6. If the upgrade is the forced upgrade version, the prompt box has no 'cancel' button.

And when the user clicks a 'confirmation' button, the user indicates that the user selects upgrading, and after the upgrading is finished, the result (the unique identifier of the lower computer of the second interface, the current version number of the first interface communication library of the software client and the version number of the lower computer of the second interface) is returned to the server.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Example three:

fig. 7 shows a block diagram of an upgrading apparatus provided in the embodiment of the present application, corresponding to the above-described upgrading method in the above embodiment, and only the parts related to the embodiment of the present application are shown for convenience of description.

Referring to fig. 7, the upgrade apparatus 7 is applied to a software client, and includes: a version number obtaining module 71 of the first interface communication library, a version number obtaining module 72 of the second interface lower computer and an upgrading module 73. Wherein:

and the version number obtaining module 71 of the first interface communication library is used for obtaining the version number of the first interface communication library according to the registry of the software client, the first interface communication library is used for processing communication between the software client and a second interface lower computer, and the second interface lower computer is used for communicating with an electronic control unit of the vehicle.

And the version number obtaining module 72 of the second interface lower computer is used for obtaining the version number of the second interface lower computer.

And the upgrade prompting module 73 is configured to prompt to upgrade the first interface communication library and/or the second interface lower computer of the software client if the acquired version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server and/or if the acquired version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server.

Specifically, when the software client executes the comparison process of the version numbers, the software client needs to obtain the latest version number of the first interface communication library and the latest version number of the second interface lower computer stored in the server from the server, compare the version number of the first interface communication library stored in the software client with the latest version number of the first interface communication library obtained from the server, and compare the version number of the second interface lower computer stored in the software client with the latest version number of the second interface lower computer obtained from the server.

In the embodiment of the application, because the version number of the first interface communication library is obtained according to the registry of the software client, and the information recorded by the registry is usually difficult to change, the accurate version number of the first interface communication library can be obtained by the above method, so that the accuracy of the subsequent comparison result is ensured, and the success rate of the subsequent upgrade is further improved. Meanwhile, after the version number of the second interface lower computer is obtained, if the obtained version number of the first interface communication library is lower than the latest version number of the first interface communication library stored by the server, and/or if the obtained version number of the second interface lower computer is lower than the latest version number of the second interface lower computer stored by the server, the first interface communication library and/or the second interface lower computer of the software client are/is prompted to be upgraded, so that the generated prompt can be more accurate, and the good experience of a user is improved.

In some embodiments, the version number obtaining module 71 of the first interface communication library is specifically configured to:

reading the storage path of the first interface communication library from the registry of the software client; and searching the corresponding first interface communication library according to the storage path of the first interface communication library, and reading the version number of the searched first interface communication library.

In some embodiments, the upgrade apparatus 7 further includes:

and the storage path writing module is used for storing a first interface communication library in the driver installation package in a local directory and writing the storage path of the first interface communication library into the registry of the software client when the driver installation package is installed on the software client.

In some embodiments, the version number obtaining module 72 of the second interface lower computer is specifically configured to:

sending a version number reading command to the second interface lower computer through the first interface communication library; and receiving the version number of the second interface lower computer returned by the second interface lower computer through the first interface communication library.

In some embodiments, the upgrade apparatus 7 further includes:

and the upgrade request sending module is used for sending an upgrade request to the server, wherein the upgrade request comprises the unique identifier of the second interface lower computer, and the software client sends the unique identifier of the second interface lower computer, the current version number of the second interface lower computer, the media access control address of the terminal equipment where the software client is located and the current version number of the first interface communication library in the software client to the server in advance for binding storage.

And the upgrade installation package receiving module is used for receiving the upgrade installation package of the first interface communication library and/or the second interface lower computer sent by the server based on the upgrade request.

And the upgrading module is used for upgrading the first interface communication library and/or the second interface lower computer according to the upgrading installation package.

In some embodiments, the upgrade apparatus 7 further includes:

and the attribute information receiving module is used for receiving the attribute information sent by the server based on the upgrading request, and the attribute information is used for indicating whether the upgrading is forced upgrading or not.

Correspondingly, the upgrade installation package receiving module is specifically configured to:

and if the attribute information indicates that the upgrade is forced upgrade, receiving an upgrade installation package of the first interface communication library and/or the second interface lower computer sent by the server based on the upgrade request. And if the attribute information indicates that the upgrade is not forced upgrade, and after a user sends an upgrade confirmation command based on an upgrade prompt, receiving an upgrade installation package of the first interface communication library and/or the second interface lower computer sent by the server based on the upgrade request.

In some embodiments, the upgrade apparatus 7 further includes:

and the upgrading result returning module is used for sending the unique identifier of the second interface lower computer, the current version number of the first interface communication library of the software client and the version number of the second interface lower computer to the server.

In some embodiments, the upgrade apparatus 7 further includes:

and the historical version backtracking instruction receiving module is used for sending a historical version request to the server if a historical version backtracking instruction sent by a user is received, wherein the historical version request carries the unique identifier of the lower computer of the second interface.

A history version information receiving module, configured to receive history version information returned by the server, where the history version information includes: before the current moment, the software client side installs each version number of the first interface communication library and each version number of the second interface lower computer.

And the backtracking entry display module is used for displaying the historical version information, backtracking entries corresponding to the version numbers of the first interface communication library installed by the software client and backtracking entries corresponding to the version numbers of the second interface lower computer.

And the backtracking module is used for updating the first interface communication library of the software client to the first interface communication library corresponding to the backtracking entry and/or updating the second interface lower computer of the software client to the second interface lower computer corresponding to the backtracking entry if the condition that the user accesses one of the backtracking entries is detected.

In some embodiments, the upgrade apparatus 7 further includes:

and the version number comparison module is used for judging whether the latest version number of the first interface communication library stored in the server is the same as the version number of the first interface communication library in the version backtracking information or not and judging whether the latest version number of the second interface lower computer stored in the server is the same as the version number of the second interface lower computer in the version backtracking information or not.

Correspondingly, the upgrade prompting module 73 is specifically configured to:

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

Example four:

fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 8, the terminal device 8 of this embodiment includes: at least one processor 80 (only one processor is shown in fig. 8), a memory 81, and a computer program 82 stored in the memory 81 and executable on the at least one processor 80, wherein the steps of any of the method embodiments described above are implemented when the computer program 82 is executed by the processor 80.

The terminal device 8 may be a desktop computer, a notebook, a palm computer, or other computing devices. The terminal device may include, but is not limited to, a processor 80, a memory 81. Those skilled in the art will appreciate that fig. 8 is merely an example of the terminal device 8, and does not constitute a limitation of the terminal device 8, and may include more or less components than those shown, or combine some components, or different components, such as an input-output device, a network access device, and the like.

The Processor 80 may be a Central Processing Unit (CPU), and the Processor 80 may be 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 device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 81 may be an internal storage unit of the terminal device 8, such as a hard disk or a memory of the terminal device 8. In other embodiments, the memory 81 may also be an external storage device of the terminal device 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 8. Further, the memory 81 may include both an internal storage unit and an external storage device of the terminal device 8. The memory 81 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as a program code of the computer program. The above-mentioned memory 81 can also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above method embodiments.

The embodiments of the present application provide a computer program product, which when running on a terminal device, enables the terminal device to implement the steps in the above method embodiments when executed.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. 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.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. An upgrading method applied to a software client side comprises the following steps:

acquiring the version number of the second interface lower computer;

2. The upgrading method of claim 1, wherein the obtaining the version number of the first interface repository according to the registry of the software client comprises:

3. The upgrading method according to claim 2, before obtaining the version number of the first interface repository according to the registry of the software client, comprising:

4. The upgrading method according to claim 1, wherein the obtaining of the version number of the second interface lower computer comprises:

5. The upgrading method according to claim 1, wherein before the prompting to upgrade the first interface communication library and/or the second interface lower computer of the software client, the method comprises:

6. The upgrading method according to claim 1, further comprising, after the upgrading of the first interface communication library and/or the second interface lower computer of the software client:

7. The upgrade method according to claim 6, further comprising:

8. An upgrading device applied to a software client comprises:

9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.