Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, 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 should 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 any and all possible combinations of one or more of the associated listed items, and includes such combinations.
In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
Reference in the 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 application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise.
Embodiment one:
in the existing upgrading method of the diagnostic equipment, if an upgrading installation package is sent to a client to be upgraded independently and then manually upgraded by a user, the workload is very large, and the experience of the user is poor; if the upgrade push is performed through the network, the version number of the diagnostic device is extracted from the local configuration file (the version number of the local configuration file is v1.0.0.4 in fig. 1 and the version number of the VCI is v10.03 in fig. 1, for example) and the local configuration file may be changed or deleted by a user by mistake, so that the upgrade push may fail.
In order to solve the above technical problems, in the upgrade method, a software client obtains a version number of a first interface communication library according to a registry, obtains a version number of a second interface lower computer, and upgrades the first interface communication library and/or the second interface lower computer of the software client according to the obtained version number of the first interface communication library, the version number of the second interface lower computer, and a corresponding comparison result of the latest version number of the first interface communication library and the latest version number of the second interface lower computer stored in a server.
Because the version number of the first interface communication library is obtained according to the registry, and the information recorded by the registry is difficult to change, 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 acquired, 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, the first interface communication library and/or the second interface lower computer of the software client is updated, so that manual updating of a user is not needed, and the good experience of the user is improved.
The upgrading method provided by the embodiment of the application is described below with reference to the accompanying drawings.
Fig. 2 shows a flowchart of a first upgrade method provided in an embodiment of the present application, where the upgrade method is applied to a software client, and the software client may be diagnostic software installed in a terminal device, and the upgrade method in an embodiment of the present application is described in detail below:
step S21, the version number of a first interface communication library is obtained 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.
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 the related information of the first interface communication library, for example, records the storage path of the first interface communication library, then finds the first interface communication library through the storage path, and then directly obtains the current accurate version number information from the first interface communication library. 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 facilitate the subsequent more timely determination of whether the first interface communication library and the second interface lower computer need to perform the upgrade operation, after each start of the software client (corresponding to the diagnostic software), the software client will obtain the version number of the first interface communication library according to the registry.
Step S22, obtaining the version number of the second interface lower computer.
In this embodiment, since the second interface lower computer may have an update, the software client needs to acquire the current version number of the second interface lower computer.
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 in 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 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, the comparison process of the version numbers may be performed at the software client, or may be performed 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, then 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 identification 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 latest version number of the first interface communication library stored by the server with the version number of the first interface communication library received from the software client and compares the latest version number of the second interface lower computer stored by the server 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 is automatically prompted to be performed on the first interface communication library and/or the second interface lower computer of the software client.
In the embodiment of the application, since 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 difficult to change, the accuracy of the obtained version number of the first interface communication library is ensured, 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 acquired, 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, the first interface communication library of the software client and/or the second interface lower computer is prompted to be updated, so that the generated prompt can be ensured to be more accurate, and the user does not need to manually update, thereby improving the good experience of the user.
Embodiment two:
fig. 3 is a flow chart illustrating a second upgrading method provided in the embodiment of the present application, and in this embodiment, step S21 is mainly further described, and step S33 and step S34 are 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 detailed and the probability of the information recorded in the registry being deleted by mistake is 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 thereof at the terminal device is looked up in the registry in accordance with the SmartBox.
Step S32, 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.
Specifically, assume that the storage path found in the registry according to the SmartBox is "C: program Files (x 86) \SmartBox3.0\SmartBox3.0\D-PDU ", then the SmartBox is indicated to be stored in a C disc of terminal equipment, a D-PDU communication library is found according to the storage path, and then a corresponding version number is read from a file version field in detailed information of the D-PDU communication library.
Step S33, obtaining the version number of the second interface lower computer.
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 in 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 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 of the present application, the software client first reads a storage path of the first interface communication library from the registry, then searches for a corresponding first interface communication library according to the storage path, and reads a version number of the first interface communication library. Because the version number of the first interface communication library is directly read from the first interface communication library, the accuracy of the read version number can be ensured.
In some embodiments, before the step S21, the method includes:
when the software client installs the drive installation package, the first interface communication library in the drive 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 corresponds to diagnostic software, and when the terminal device installs the diagnostic software for the first time, the diagnostic software will automatically install the corresponding driver installation package, and write 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 subsequently.
In some embodiments, in order to obtain a more accurate version number of the second interface lower computer, the step S22 (or step S33) includes:
a1, transmitting 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.
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. Because the version number of the second interface lower computer is directly obtained from the second interface lower computer and is not obtained from the configuration file which is easy to be deleted by a user by mistake, 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) upgrades the first interface communication library of the software client and/or the second interface lower computer, 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 identifier of the second interface lower computer may be a serial number of the second interface lower computer.
In this embodiment, when the software client determines that the upgrade is required, an upgrade request including the unique identifier of the lower computer of the second interface 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 the upgrade request sent by the software client, the server can find 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), it includes:
b1, 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 B2, upgrading the first interface communication library and/or the second interface lower computer according to the upgrade 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 obtained more quickly after the upgrade is prompted, and the first interface communication library and/or the second interface lower computer can be upgraded more quickly, so that the good experience of the 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 upgrade request, wherein the attribute information is used for indicating whether the upgrade is forced upgrade or not.
For example, when the value of the attribute information is 1, the current upgrade is indicated as the forced upgrade, and when the value of the attribute information is 0, the current upgrade is indicated as the 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. If the attribute information indicates that the upgrade is not forced, and after the user sends out a confirmation upgrade command based on the 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 upgrade is directly performed on the first interface communication library; if the upgrade is needed to upgrade the first interface communication library and the second interface lower computer at the same time, the upgrade is directly performed on the first interface communication library and the second interface lower computer.
In some embodiments, the upgrade of the first interface communication library of the software client and/or the second interface lower computer may be prompted by a prompt box. In the prompt box, the version number of the current first interface communication library of the software client, the version number of the current 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. Further, the prompt box can also display the newly added function of the first interface communication library after upgrading, and/or the newly added function of the second interface lower computer. By displaying the information on the prompt box, the user can acquire more relevant information with the software client.
It should be noted that if the upgrade is forced upgrade, the user is not provided with an option of not upgrading in the prompt box, for example, only a "confirm" button is provided, and a "cancel" button is not provided. If the upgrade is not forced upgrade, a 'confirm' button and a 'cancel' button are provided at the same time. That is, in this embodiment, if the upgrade is forced upgrade, the prompt box only has a prompt function, and the upgrade operation will be directly performed after the prompt; if the upgrade is not forced, the prompt box has the function of prompting and the function of enabling the user to select whether to execute the upgrade operation. After the user clicks the 'confirm' button, the software client judges that the user sends a confirm upgrade command based on the upgrade prompt, and upgrades the first interface communication library and/or the second interface lower computer of the software client according to the upgrade installation package obtained from the server. Because the software client can judge whether the upgrade is forced according to the attribute information received from the server, the forced upgrade is usually set only by the existence of a relatively serious vulnerability of the old version, and the like, when the upgrade is forced upgrade, the software client is not provided with an option of not upgrading, but directly upgraded, so that the probability of error occurrence of the software client in the subsequent use process can be reduced. Meanwhile, when the upgrade is not forced, the user is provided with options of upgrade and non-upgrade, 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), further comprising:
and transmitting the unique identifier of the second interface lower computer, the version number of the current first interface communication library of the software client and the version number of the second interface lower computer to the server.
In this embodiment, after the software client is installed and after the software client is upgraded, the unique identifier of the second interface lower computer, the version number of the current first interface communication library of the software client and the version number of the second interface lower computer corresponding to the software client are sent to the server, so that the server stores the unique identifier. The subsequent server may perform corresponding statistics according to the stored information, for example, statistics on the number of second interface lower computers using the first interface communication library of a certain version number. The server can also judge which second interface lower computer's unique identification corresponds to the first interface communication library (or second interface lower computer) to upgrade according to the stored information after receiving the upgrade installation package newly added by the administrator.
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 second interface lower computer.
In this embodiment, a history version backtracking portal is provided on an interface of the software client, the user clicks the history version backtracking portal, and the software client receives a history version backtracking instruction sent by the user.
And C2, receiving history version information returned by the server, wherein the history version information comprises: before the current moment, each version number of the first interface communication library installed by the software client and each version number of the second interface lower computer are installed.
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 corresponding to the second interface lower computers and the version numbers of the second interface lower computers. The server is able to return historical version information to the software client after receiving the historical version request sent by the software client.
And C3, displaying the history version information, and 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.
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 correspond to one backtracking entry, so that a user may select to backtrack only the version of the first interface communication library, or select to backtrack only the version of the second interface lower computer, or select to backtrack both the version of the first interface communication library and the version of the second interface lower computer.
In some embodiments, the backtracking portal may be an "upgrade" button displayed by the software client.
And C4, if the fact that the user accesses one of the backtracking entries is detected, 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 portal of the first interface communication library, the software client only updates the first interface communication library, when the user accesses the backtracking portal of the second interface lower computer, the software client only updates the second interface lower computer, and when the user accesses both the backtracking portal of the first interface communication library and the backtracking portal of the second interface lower computer, the software client will update both the first interface communication library and the second interface lower computer.
In the steps C1 to C4, the user obtains the history version information of the software client by sending the history 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 the backtracking entry corresponding to the history version information. Because the user can trace back the version, the user can select the version which the user wants to use, thereby being beneficial to improving the good experience of the user.
In some embodiments, the software client records version backtracking information including a version number of the first interface communication library and a version number of the second interface lower computer stored by the server at the time of version backtracking. Before the step S23 (or step S34), the method includes:
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:
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 and the acquired 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 if 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 acquired 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, since the update operation is only indicated when the software client performs version backtracking and the server has a new update installation package, and the update operation is not indicated when the server does not have a new update installation package, the user can be prevented from being disturbed many times, thereby improving the good experience of the user.
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 having 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 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. The user operates the client, and the client communicates with the VCI lower computer by calling the D-PDU communication library, so that diagnosis of the vehicle is realized. Wherein the version of the D-PDU communication library is upgradeable.
The VCI lower computer contains a chip and communicates with the automobile bus, the data message can be returned to the D-PDU communication library in real time, and the version of the VCI lower computer can be upgraded.
When an administrator stores a new upgrade installation package in a server, it needs to set the upgrade installation package, and the setting interface of information is shown in fig. 5. In fig. 5, the VCI version, D-PDU version, version upgrade content, whether it is a forced upgrade version, etc. in the setup interface may be displayed in a prompt box generated in the embodiment of the present application. In addition, the setting interface also comprises a VCI lower computer, a history version of the D-PDU communication library and the like.
When the client is started, the version number of the D-PDU communication library is obtained from the registry of the software client, and then the version number of the VCI lower computer is obtained through the D-PDU communication library. If the update operation is judged to be executed according to the version number of the obtained D-PDU communication library and the version number of the VCI lower computer, corresponding prompt information is displayed on a prompt box so as to prompt the update of the first interface communication library and/or the second interface lower computer of the software client. If the upgrade is not the forced upgrade version, the prompt information displayed by the prompt box may be as shown in fig. 6. If the upgrade is a forced upgrade version, the prompt box has no cancel button.
When the user clicks the 'confirm' button, the user selects the upgrade, and after the upgrade is finished, the result (the unique identification of the second interface lower computer, the version number of the current first interface communication library of the software client and the version number of the second interface lower computer) is returned to the server.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Embodiment III:
corresponding to the upgrade method described in the above embodiments, fig. 7 shows a block diagram of the upgrade apparatus provided in the embodiment of the present application, and for convenience of explanation, only the portions relevant to the embodiment of the present application are shown.
Referring to fig. 7, the upgrading device 7 is applied to a software client, and includes: the system comprises a version number acquisition module 71 of the first interface communication library, a version number acquisition module 72 of the second interface lower computer and an upgrade prompting module 73.
Wherein:
the version number obtaining module 71 of the first interface communication library is configured to obtain the version number of the first interface communication library according to the registry of the software client, where the first interface communication library is configured to process communications between the software client and a second interface lower computer, and the second interface lower computer is configured to communicate with an electronic control unit of a vehicle.
The version number obtaining module 72 of the second interface lower computer is configured to obtain the version number of the second interface lower computer.
And the upgrade prompting module 73 is configured to prompt the upgrade of the first interface communication library and/or the second interface lower computer of the software client 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 in 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 in the server.
Specifically, when the comparison process of the version numbers is performed at the software client, 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 server 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 server 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 identification 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 latest version number of the first interface communication library stored by the server with the version number of the first interface communication library received from the software client and compares the latest version number of the second interface lower computer stored by the server with the version number of the second interface lower computer received from the software client.
In the embodiment of the application, since 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 difficult to change, the version number of the accurate first interface communication library can be obtained by the method, so that the accuracy of a 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 acquired, 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, the first interface communication library of the software client and/or the second interface lower computer is/are prompted to be updated, so that the generated prompt can be ensured to be more accurate, and the good experience of a user is improved.
In some embodiments, the version number acquisition module 71 of the first interface communication library is specifically configured to:
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.
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 drive installation package in a local directory when the drive installation package is installed on the software client, and writing the storage path of the first interface communication library into a registry of the software client.
In some embodiments, the version number acquisition module 72 of the second interface lower computer is specifically configured to:
transmitting 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 comprises:
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 comprises:
the attribute information receiving module is used for receiving attribute information sent by the server based on the upgrade request, wherein the attribute information is used for indicating whether the upgrade is forced upgrade 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. If the attribute information indicates that the upgrade is not forced, and after the user sends out a confirmation upgrade command based on the 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 of the first interface communication library of the software client and/or the second interface lower computer may be prompted by a prompt box. In the prompt box, the version number of the current first interface communication library of the software client, the version number of the current 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. Further, the prompt box can also display the newly added function of the first interface communication library after upgrading, and/or the newly added function of the second interface lower computer. By displaying the information on the prompt box, the user can acquire more relevant information with the software client.
In some embodiments, the upgrade apparatus 7 further comprises:
and the upgrade result return module is used for sending the unique identifier of the second interface lower computer, the version number of the current 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 comprises:
and the historical version backtracking instruction receiving module is used for sending a historical version request to the server if receiving the historical version backtracking instruction sent by the user, wherein the historical version request carries the unique identifier of the second interface lower computer.
The historical version information receiving module is used for receiving historical version information returned by the server, and the historical version information comprises: before the current moment, each version number of the first interface communication library installed by the software client and each version number of the second interface lower computer are installed.
And the backtracking entry display module is used for displaying the history version information, and 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 into the first interface communication library corresponding to the backtracking entrance if one backtracking entrance is detected to be accessed by the user, and/or updating the second interface lower computer of the software client into the second interface lower computer corresponding to the backtracking entrance.
In some embodiments, the upgrade apparatus 7 further comprises:
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, 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 upgrade prompting module 73 is specifically configured to:
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 and the acquired 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 if 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 acquired 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.
It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.
Embodiment 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, the steps of any of the various method embodiments described above being implemented when the processor 80 executes the computer program 82.
The terminal device 8 may be a desktop computer, a notebook computer, a palm computer, or the like. The terminal device may include, but is not limited to, a processor 80, a memory 81. It will be appreciated by those skilled in the art that fig. 8 is merely an example of the terminal device 8 and is not limiting of the terminal device 8, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The processor 80 may be a central processing unit (Central Processing Unit, CPU), the processor 80 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 81 may in some embodiments be an internal storage unit of the terminal device 8, such as a hard disk or a memory of the terminal device 8. The memory 81 may also be an external storage device of the terminal device 8 in other embodiments, for example, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 8. Further, the memory 81 may include both the internal storage unit and the external storage device of the terminal device 8. The memory 81 is used for storing an operating system, an application program, a boot loader (BootLoader), data, other programs, and the like, such as program codes of the computer programs. The above-described memory 81 may 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-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a 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 process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program is executed by a processor to implement steps in each of the method embodiments described above.
The present embodiments provide a computer program product which, when run on a terminal device, causes the terminal device to perform steps that enable the respective method embodiments described above to be implemented.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, 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 device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
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 solution. 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 manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; 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 scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.