CN111427595B

CN111427595B - Client upgrading method, device and system

Info

Publication number: CN111427595B
Application number: CN201910825917.8A
Authority: CN
Inventors: 顾晨辉
Original assignee: Hangzhou Hikvision Digital Technology Co Ltd
Current assignee: Hangzhou Hikvision Digital Technology Co Ltd
Priority date: 2019-09-03
Filing date: 2019-09-03
Publication date: 2024-03-05
Anticipated expiration: 2039-09-03
Also published as: CN111427595A

Abstract

The embodiment of the invention discloses a method, a device and a system for upgrading a client, relates to the field of software upgrading, and solves the problem of poor user experience during version updating of the client. The method comprises the following steps: acquiring a current version number of a client; determining the latest version number and the first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading; and sending the upgrading mode for the client to upgrade according to the upgrading mode to the client. The method and the device can be applied to the scene of version upgrading of clients on the market when the new version is released.

Description

Client upgrading method, device and system

Technical Field

The present invention relates to the field of software upgrade, and in particular, to a method, an apparatus, and a system for upgrading a client.

Background

The client refers to software corresponding to the server and matched with the server to provide local service for the user. The existing client upgrading mechanism prompts a user when a new version is released, so that the user can select whether to upgrade. On the one hand, because each version update prompts a user, particularly when small version update or defect repair is performed, the software product does not have a significant framework to adjust or increase characteristic functions, and too frequent update prompts can cause harassment to the user, so that the user feels inconvenient to use and the experience of the user is influenced; on the other hand, because the user cannot accurately judge the necessity of upgrading, if the user does not select upgrading all the time under the condition that the user selects whether to upgrade, the defect is not repaired all the time, and therefore the follow-up normal use of the user is affected.

Disclosure of Invention

The embodiment of the invention discloses a method, a device and a system for upgrading a client so as to improve user experience.

In order to achieve the above object, an embodiment of the present invention discloses a method for upgrading a client, including:

acquiring a current version number of a client;

determining the latest version number and the first version number of the client;

under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading;

and sending the upgrading mode for the client to upgrade according to the upgrading mode to the client.

In a second aspect, to achieve the above objective, an embodiment of the present invention further discloses another method for upgrading a client, where the method includes:

determining a current version number of the client;

acquiring the latest version number and the first version number of the client;

and upgrading the client to the latest version in an upgrade mode of silent upgrade under the condition that the current version number of the client is lower than the latest version number and higher than the first version number.

In order to achieve the above object, the embodiment of the present invention further discloses a client upgrade apparatus, where the apparatus includes:

The acquisition module is used for acquiring the current version number of the client;

a determining module, configured to determine a latest version number and a first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading;

and the sending module is used for sending the upgrading mode for the client to upgrade according to the upgrading mode to the client.

In order to achieve the above object, the embodiment of the present invention further discloses another device for upgrading a client, where the device includes:

the acquisition module is used for acquiring the latest version number and the first version number of the client;

the determining module is used for determining the current version number of the client;

and the upgrading module is used for upgrading the client to the latest version in a silent upgrading mode under the condition that the current version number of the client is lower than the latest version number and higher than the first version number.

In a fifth aspect, to achieve the above object, an embodiment of the present invention further discloses a client upgrade system, where the system includes:

the server is used for acquiring the current version number of the client; determining the latest version number and the first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading; sending the upgrading mode for the client to upgrade according to the upgrading mode to the client;

The client is used for sending the current version number of the client to the server; acquiring the upgrading mode; upgrading the client to the latest version according to the upgrading mode; or alternatively

The system comprises:

the server is used for sending the latest version number and the first version number of the client to the client;

the client is used for determining the current version number of the client; acquiring the latest version number and the first version number of the client; and upgrading the client to the latest version in an upgrade mode of silent upgrade under the condition that the current version number of the client is lower than the latest version number and higher than the first version number.

In a sixth aspect, to achieve the above object, an embodiment of the present invention further discloses an electronic device, including a processor, a memory, wherein,

a memory for storing a computer program;

and the processor is used for realizing the steps of the client upgrading method provided in the first aspect when executing the program stored in the memory.

In a seventh aspect, to achieve the above object, an embodiment of the present invention further discloses another electronic device, including a processor, a memory, where,

a memory for storing a computer program;

And the processor is used for realizing the steps of the client upgrading method provided in the second aspect when executing the program stored in the memory.

In an eighth aspect, to achieve the above object, an embodiment of the present invention further discloses a computer readable storage medium, where a computer program is stored, where the computer program is executed by a processor to implement the steps of a client upgrade method provided in the first aspect.

In a ninth aspect, to achieve the above object, an embodiment of the present invention further discloses another computer readable storage medium, where a computer program is stored, where the computer program is executed by a processor to implement the steps of a client upgrade method provided in the second aspect.

In a tenth aspect, to achieve the above object, an embodiment of the present invention further discloses a computer program product, which when run on a computer, causes the computer to perform the steps of implementing a client upgrade method provided in the first aspect.

In an eleventh aspect, to achieve the above object, an embodiment of the present invention further discloses another computer program product, where the computer program product when run on a computer causes the computer to perform the steps of implementing a client upgrade method provided in the second aspect.

By applying the scheme provided by the embodiment of the invention, the first version number can be set by a developer, and the silent upgrading of the client side to the latest version can be realized under the condition that the current version number of the client side of the user is lower than the latest version number and higher than the first version number, so that the client side of the user can be upgraded under the condition that the user is not easy to perceive, the number of times of upgrading selected by the user is reduced, the subsequent use process of the user on the client side is optimized after the upgrading, and the user experience is improved; in the use process of the user, the number of times that the user selects to upgrade due to the fact that the jump-out prompt needs to repair the defect is reduced, so that the number of times that the user perceives the defect repair of the client is reduced, and the trust degree of the user to the client is improved; in addition, the developer can realize silent upgrading of clients with version numbers between the first version number and the latest version number to the latest version by setting the first version number, thereby improving the controllability of the developer on the versions of the clients on the market and reducing the maintenance cost of the clients with the version numbers between the first version number and the latest version number.

Drawings

In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of a client upgrading method according to an embodiment of the present invention;

fig. 2 is a flow chart of another client upgrading method according to an embodiment of the present invention;

FIG. 3 is a flowchart of a method for upgrading a client according to an embodiment of the present invention;

fig. 4 is a schematic flow chart of a method for upgrading a client according to an embodiment of the present invention;

fig. 5 is a flow chart of an upgrade method of another client according to an embodiment of the present invention;

FIG. 6 is a flowchart of an upgrade method of another client according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a client upgrade apparatus according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of another client upgrade apparatus according to an embodiment of the present invention;

Fig. 9 is a schematic structural diagram of a client upgrade system according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of another client upgrade system according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of another electronic device according to an embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

Referring to fig. 1, fig. 1 is a flow chart of a client upgrade method according to an embodiment of the present invention, where the method includes:

s101: and the client sends the current version number of the client to the server.

Specifically, after the client is operated locally, the client sends a request to the server to acquire relevant upgrade information, wherein the request carries the current version number of the client. In this way, the server may determine the upgrade mode of the client according to the current version number of the client.

S102: the server obtains the current version number of the client.

S103: the server determines a latest version number and a first version number of the client.

The server stores the latest version upgrade related file of the client, and the server has a configuration first version number. Specifically, the developer may package the file included in the latest version of the client and an XML (Extensible Markup Language ) file containing the file feature code of the file included in the latest version into a compressed package, and upload the compressed package to the server, where the file feature code may be an MD5 value, and after decompressing the compressed package, the server obtains the file included in the latest version of the client and the XML file, and determines the latest version number of the client. Meanwhile, a developer may configure a first version number in the server, which may be lower than the latest version number.

S104: and the server determines the upgrading mode of the client.

Specifically, in the case that the current version number of the client is lower than the latest version number and higher than the first version number, the server determines that the upgrade mode of the client is silent upgrade. Under the condition that the upgrading mode of the client is silent upgrading, the client directly executes the upgrading task, a user is not prompted on a client interface, and an instruction input by the user is not required to be received. Therefore, a developer can realize silent upgrading of clients with version numbers between the first version number and the latest version number on the market to the latest version by setting the first version number in the server, thereby improving the controllability of the developer on the versions of the clients on the market and reducing the maintenance cost of the clients with the version numbers between the first version number and the latest version number; meanwhile, due to the upgrading mode of silent upgrading, the client can be upgraded under the condition that the user is not easy to perceive, so that the number of times of upgrading selected by the user is reduced, the subsequent use process of the client by the user is optimized after the upgrading, and the user experience is improved; in addition, in the use process of the user, the number of times that the user selects to upgrade due to the fact that the jump-out prompt needs to repair the defect is reduced, so that the number of times that the user perceives the defect repair of the client is reduced, and the trust degree of the user to the client is improved.

Preferably, the first version number may be satisfied: and in the case that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for performing defect repair on the basis of the current version of the client. For example, the latest version number is 2.1.2, and the first version number may be configured to be 2.1.0, so that in the case that the current version number of the client is 2.1.1, the 2.1.2 version is defect repair based on the 2.1.1 version. In this way, when the current version number of the client is lower than the latest version number and higher than the first version number, the client is quietly upgraded to the latest version, and the quietly upgrading speed is higher because the modification of defect repair is smaller, so that the defect repair can be performed on the client under the condition that a user is not easy to perceive the upgrading consumed time and upgrading modified content, the subsequent use process of the client by the user is optimized after the defect repair, and the user experience is improved; in addition, in the use process of the user, the frequency of the user for detecting the repairing defect of the client is reduced, and the trust degree of the user to the client is improved.

It should be noted that, when the current version number of the client is the latest version, the server may determine that the upgrade mode of the client is not upgrade; when the current version number of the client is equal to or lower than the first version number, the server can determine that the upgrading mode of the client is silent upgrading, can select upgrading or can be forced upgrading. Here, when the upgrade mode of the client is selected upgrade, the client interface pops up a window to prompt the user to select whether to upgrade, after receiving the instruction of the user to select upgrade, the client executes the upgrade task, after receiving the instruction of the user to select not to upgrade, the window is closed, and the user can operate the current version of the client; and under the condition that the upgrading mode of the client is forced upgrading, the client interface prompts a user to upgrade, and if the user wants to operate the client, the user must click the upgrading to enable the client to execute the upgrading task, or else the user exits the client.

In one embodiment of the present invention, in step S103, the server may further determine the second version number of the client, in particular, the second version number may be configured in the server by a developer, and the second version number may be lower than the first version number. In the step S104, in the case that the current version number of the client is lower than the first version number and higher than the second version number, the server may determine that the upgrade mode of the client is a selected upgrade; under the condition that the current version number of the client is lower than the second version number, the server can determine that the upgrading mode of the client is forced upgrading; under the condition that the current version number of the client is equal to the first version number, the server can determine that the upgrading mode of the client is silent upgrading or selective upgrading; and under the condition that the current version number of the client is equal to the second version number, the server can determine that the upgrading mode of the client is selected to be upgraded or forced to be upgraded. Therefore, the developer can realize forced upgrade of clients with version numbers lower than the second version number to the latest version by further setting the second version number in the server, thereby improving the controllability of the developer on the version of the clients on the market and reducing the maintenance cost of the clients lower than the second version number; meanwhile, for the client with the version number between the second version number and the first version number, the opportunity of whether the user selects upgrading is provided, the man-machine interaction friendliness is improved, and further balance is formed between the user experience sense and the control of the developer on the version.

Preferably, the second version number may satisfy: in the case where the current version number of the client is lower than the second version number, the latest version of the client may be a version that is architecture-adjusted based on the current version of the client. In the case that the current version number of the client is lower than the first version number and higher than the second version number, the latest version of the client may be a version in which a function is newly added on the basis of the current version of the client. For example, the latest version number is 2.2.2, the second version number may be configured to be 2.0.0, and the first version number may be configured to be 2.2.0, so that in the case that the current version number of the client is 1.0.1, the 2.2.2 version is subjected to architecture adjustment based on the 1.0.1 version; under the condition that the current version number of the client is 2.1.0, the 2.2.2 version is newly added with functions on the basis of the 2.1.0 version; and under the condition that the current version number of the client is 2.2.1, performing defect repair on the basis of the version 2.2.1 by the version 2.2.2. After determining the upgrade mode of the client, the server adopts forced upgrade for the latest version of the client which is adjusted by the framework based on the current version, so that the maintenance cost for a low version can be reduced, and because the client is changed greatly after the low version is upgraded, a user upgrade prompt is provided through forced upgrade instead of silent upgrade, so that the user can know that the client needs to be upgraded, and the man-machine interaction is more friendly; the latest version of the client is selected and updated for the newly added function based on the current version, so that a user can select whether the newly added function of the latest version is needed or not by himself, the man-machine interaction friendliness is improved, and balance is formed between user experience and control of a developer on the version.

S105: the server sends the upgrading mode for the client to upgrade according to the upgrading mode to the client.

After the server determines the upgrading mode, the upgrading mode is sent to the client, so that the client can be upgraded according to the upgrading mode.

In one embodiment of the present invention, the server may further send a file feature code of a file included in the latest version of the client to the client. Specifically, the server sends the XML file containing the file feature code of the file contained in the latest version to the client, so that the client can determine the upgrade file list according to the XML file.

S106: and the client acquires the upgrading mode and upgrades the client to the latest version according to the upgrading mode.

Specifically, in the case that the acquired upgrade mode is silent upgrade, the client will directly upgrade the client to the latest version, without prompting the user on a client interface; under the condition that the obtained upgrading mode is selected for upgrading, the client interface pops up a window to prompt a user to select whether to upgrade, after receiving an instruction of the user to select upgrading, the client responds to an upgrading trigger signal to upgrade the client to the latest version, after receiving an instruction of the user to select not to upgrade, the window is closed, and the user can operate the current version of the client; under the condition that the obtained upgrading mode is forced upgrading, the client interface pops up a window to prompt a user to upgrade, only one upgrading button can be arranged in the window, after the user clicks the upgrading button, the client responds to an upgrading trigger signal to upgrade the client to the latest version, and the client can be operated only after the user clicks the upgrading button to upgrade the client to the latest version, otherwise, the client is quitted; and under the condition that the obtained upgrading mode is not upgrading, the client does not execute upgrading operation, and a user can operate the current version of the client.

In one embodiment of the present invention, the client may obtain, in addition to the upgrade mode, a file feature code of a file included in the latest version of the client, and in step S106, the step of upgrading the client to the latest version may refer to steps S11 to S15.

S11: and the client determines an upgrade file list according to the file feature codes of the files contained in the latest version of the client and the file feature codes of the files contained in the current version of the client.

Specifically, the client compares the file feature code of the file contained in the latest version of the client with the file feature code of the file contained in the current version of the client after responding to the upgrade trigger signal under the condition that the upgrade mode is silent upgrade or under the condition that the upgrade mode is selective upgrade or forced upgrade, and adds the file feature code of the file into an upgrade file list for each file in the file contained in the latest version of the client under the condition that the file feature code of the file is different from the file feature code of the file corresponding to the current version or under the condition that the file corresponding to the file does not exist in the file contained in the current version.

S12: and the client sends the upgrade file list to the server.

S13: and the server sends the upgrade file corresponding to the upgrade file list to the client.

Specifically, after the server obtains the upgrade file list, according to the file feature code in the upgrade file list, determining an upgrade file corresponding to the upgrade file list in files included in the latest version of the client, and sending the upgrade file to the client.

Therefore, the server only needs to issue the files which are different from the files contained in the current version in the files contained in the latest version of the client to the client, and does not need to repeatedly issue the files which are the same as the files contained in the current version in the files contained in the latest version, so that the utilization rate and the upgrading speed of network resources are improved.

S14: and the client acquires the upgrade files corresponding to the upgrade file list, and updates the files contained in the current version according to the upgrade files.

Specifically, after the client acquires the upgrade file, for the file which belongs to the upgrade file and is modified based on the file contained in the current version, replacing the corresponding file in the file contained in the current version with the modified file; and adding the newly added file to the file contained in the current version for the file which belongs to the newly added file on the basis of the file contained in the current version in the upgrade file.

S15: restarting the client.

Specifically, after the update of the file included in the current version is completed according to the upgrade file, the client is restarted, so that the client is upgraded to the latest version.

The embodiment of the invention provides a client upgrading method, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 2, fig. 2 is a flowchart of another client upgrade method according to an embodiment of the present invention, where the method may be applied to a server, and the method includes:

s201: and obtaining the current version number of the client.

Specifically, after the client runs, the client sends a request to the server, where the request carries the current version number of the client. In this way, the server obtains the current version number of the client, so that the upgrade mode of the client can be determined later according to the current version number of the client.

S202: the latest version number and the first version number of the client are determined.

The specific description of step S202 is shown in step S103, and the embodiments of the present invention are not described herein again.

S203: and under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading.

Specifically, in the case that the current version number of the client is lower than the latest version number and higher than the first version number, the upgrade mode of the client is determined to be silent upgrade. Therefore, a developer can realize silent upgrading of clients with version numbers between the first version number and the latest version number on the market to the latest version by setting the first version number in the server, thereby improving the controllability of the developer on the versions of the clients on the market and reducing the maintenance cost of the clients with the version numbers between the first version number and the latest version number; meanwhile, due to the upgrading mode of silent upgrading, the client can be upgraded under the condition that the user is not easy to perceive, so that the number of times of upgrading selected by the user is reduced, the subsequent use process of the client by the user is optimized after the upgrading, and the user experience is improved; in addition, in the use process of the user, the number of times that the user selects to upgrade due to the fact that the jump-out prompt needs to repair the defect is reduced, so that the number of times that the user perceives the defect repair of the client is reduced, and the trust degree of the user to the client is improved.

Preferably, the first version number may be satisfied: and in the case that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for performing defect repair on the basis of the current version of the client. In this way, when the current version number of the client is lower than the latest version number and higher than the first version number, the client is quietly upgraded to the latest version, and the quietly upgrading speed is higher because of smaller modification of defect repairing, so that the defect repairing can be carried out on the client under the condition that a user is not easy to perceive upgrading consumed time and upgrading modified content, and the subsequent use process of the client by the user is optimized after the defect repairing, and the user experience is improved; in addition, in the use process of the user, the frequency of the user for detecting the repairing defect of the client is reduced, and the trust degree of the user to the client is improved.

S204: and sending the upgrading mode for the client to upgrade according to the upgrading mode to the client.

The embodiment of the invention provides another client upgrading method, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 3, fig. 3 is a flowchart of another client upgrade method according to an embodiment of the present invention, where the method may be applied to a server, and the method includes:

s301: and obtaining the current version number of the client.

The specific description of step S301 is shown in step S201, and the embodiments of the present invention are not described herein again.

S302: and determining the latest version number, the first version number and the second version number of the client.

The server stores the latest version upgrade related file of the client, and the server stores a configuration first version number and a second version number. Specifically, a developer may package a file included in the latest version of the client and an XML file containing a file feature code of the file included in the latest version into a compressed package, and upload the compressed package to the server, where the file feature code may be an MD5 value, and after decompressing the compressed package, the server obtains the file included in the latest version of the client and the XML file, and determines the latest version number of the client. Meanwhile, a developer may configure a first version number, which may be lower than the latest version number, and a second version number, which may be lower than the first version number, in the server.

S303: and determining the upgrading mode of the client.

Under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading; determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number; under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading; under the condition that the current version number of the client is equal to the first version number, determining that the upgrading mode of the client is silent upgrading or selecting upgrading; under the condition that the current version number of the client is equal to the second version number, determining that the upgrading mode of the client is selected for upgrading or forced upgrading; and under the condition that the current version number of the client is the latest version number, determining that the upgrading mode of the client is not upgrading.

Therefore, a developer can realize forced upgrade of clients with version numbers lower than the second version number to the latest version by setting the first version number and the second version number in the server, thereby improving controllability of the developer on the versions of the clients on the market and reducing maintenance cost of the clients lower than the second version number; for the clients with version numbers between the second version number and the first version number, the opportunity of whether the user selects upgrading is provided, and the friendliness of man-machine interaction is improved; the client with the version number between the first version number and the latest version number is quietly upgraded to the latest version, so that the maintenance cost of the client with the version number between the first version number and the latest version number is reduced, the client can be upgraded under the condition that the client is not easy to perceive by a user, the number of times of upgrading is reduced, the subsequent use process of the client by the user is optimized after upgrading, the user experience is improved, the number of times that the user perceives the repairing defect of the client is reduced, the trust degree of the user to the client is improved, and further balance is formed between the user experience and the control of the developer on the version.

Preferably, the first version number may be satisfied: and in the case that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for performing defect repair on the basis of the current version of the client. The second version number may satisfy: in the case that the current version number of the client is lower than the second version number, the latest version of the client may be a version that is architecture-adjusted based on the current version of the client; in the case that the current version number of the client is lower than the first version number and higher than the second version number, the latest version of the client may be a version in which a function is newly added on the basis of the current version of the client. In this way, the maintenance cost for the low version can be reduced by adopting forced upgrade for the latest version of the client for framework adjustment based on the current version, and the user can know that the client needs to be upgraded by providing a user upgrade prompt instead of adopting silent upgrade through forced upgrade because the client is changed greatly after the low version is upgraded, so that man-machine interaction is more friendly; the latest version of the client is selected and updated for the newly added function based on the current version, so that a user can select whether the newly added function of the latest version is needed or not by himself, and the friendliness of man-machine interaction is improved; the latest version of the client adopts silent upgrading for defect repairing based on the current version, and the defect repairing is changed slightly, so that the speed of the silent upgrading is high, the defect repairing can be carried out on the client under the condition that a user is not easy to perceive upgrading consumption time and upgrading changing content, the subsequent use process of the client by the user is optimized after the defect repairing, the user experience is improved, the times that the user perceives the defect of the client repairing is reduced, the trust degree of the user to the client is improved, and further, the balance between the user experience and the control of the developer to the version is realized.

S304: and sending the upgrading mode for the client to upgrade according to the upgrading mode to the client, and sending the file feature code of the file contained in the latest version of the client to the client.

Specifically, after determining the upgrade mode, the server sends the upgrade mode and an XML file containing the file feature code of the file contained in the latest version to the client, so that the client can upgrade according to the upgrade mode, and the client determines an upgrade file list according to the XML file.

S305: and acquiring an upgrade file list, wherein the upgrade file list is a file list determined according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client.

Specifically, after receiving the update mode as silent update, or receiving the update mode as selective update or forced update, the client compares the file feature code of the file contained in the latest version of the client with the file feature code of the file contained in the current version, and adds the file feature code of the file to the update file list for each file in the file contained in the latest version of the client when the file feature code of the file is different from the file feature code of the file corresponding to the current version, or when the file corresponding to the file does not exist in the file contained in the current version. And the client sends the finally determined upgrade file list to the server, and the server acquires the upgrade file list.

S306: and sending the upgrade files corresponding to the upgrade file list to the client.

The specific description of step S306 is shown in step S13, and the embodiment of the present invention will not be described herein.

And sending an upgrade file corresponding to the upgrade file list to the client, so that the client can update the file contained in the current version of the client according to the upgrade file after acquiring the upgrade file, and upgrade the client to the latest version.

The embodiment of the invention provides a client upgrading method, which realizes forced upgrading of clients with version numbers lower than a second version number to the latest version by setting the first version number and the second version number by a developer, improves the controllability of the developer to the versions of the clients on the market, and reduces the maintenance cost of the clients with version numbers lower than the second version number; for the clients with version numbers between the second version number and the first version number, the opportunity of whether the user selects upgrading is provided, and the friendliness of man-machine interaction is improved; the method has the advantages that the client with the version number between the first version number and the latest version number is quietly upgraded to the latest version, the maintenance cost of the client with the version number between the first version number and the latest version number is reduced, the number of times of upgrading selected by a user is reduced, the subsequent use process of the client by the user is optimized, the user experience is improved, the number of times that the user perceives the repairing defect of the client is reduced, the trust degree of the user to the client is improved, and further balance between the user experience and the control of the developer on the version is realized.

Referring to fig. 4, fig. 4 is a flowchart of a method for upgrading a client according to an embodiment of the present invention, where the method includes:

s401: the client sends a request to the server.

Specifically, after a client is locally run, the client sends a request to the server to obtain the latest version number and the first version number of the client.

S402: the server sends the latest version number and the first version number of the client to the client.

The relevant description of the latest version number and the first version number of the client is detailed in step S103.

And after receiving the request sent by the client, the server sends the latest version number and the first version number of the client to the client.

S403: and the client acquires the latest version number and the first version number of the client and determines the current version number of the client.

S404: and upgrading the client to the latest version in an upgrade mode of silent upgrade under the condition that the current version number of the client is lower than the latest version number and higher than the first version number.

Therefore, a developer can realize silent upgrading of clients with version numbers between the first version number and the latest version number on the market to the latest version by setting the first version number in the server, thereby improving the controllability of the developer on the versions of the clients on the market and reducing the maintenance cost of the clients with the version numbers between the first version number and the latest version number; meanwhile, due to the upgrading mode of silent upgrading, the client can be upgraded under the condition that the user is not easy to perceive, so that the number of times of upgrading selected by the user is reduced, the subsequent use process of the client by the user is optimized after the upgrading, and the user experience is improved; in addition, in the use process of the user, the number of times that the user selects to upgrade due to the fact that the jump-out prompt needs to repair the defect is reduced, so that the number of times that the user perceives the defect repair of the client is reduced, and the trust degree of the user to the client is improved.

It should be noted that, when the current version number of the client is the latest version, the client may determine that the upgrade mode of the client is not upgrade; when the current version number of the client is equal to or lower than the first version number, the client can determine that the upgrading mode of the client is silent upgrading, can select upgrading or can be forced upgrading. Here, when the upgrade mode of the client is selected upgrade, the client interface pops up a window to prompt the user to select whether to upgrade, after receiving the instruction of the user to select upgrade, the client responds to an upgrade trigger signal to upgrade the client to the latest version, after receiving the instruction of the user to select not to upgrade, the window is closed, and the user can operate the current version of the client; under the condition that the upgrading mode of the client is forced upgrading, the client interface pops up a window to prompt a user to upgrade, only one upgrading button can be arranged in the window, after the user clicks the upgrading button, the client responds to an upgrading trigger signal to upgrade the client to the latest version, and the client can be operated only after the user clicks the upgrading button to upgrade the client to the latest version, otherwise, the client is exited.

In one embodiment of the present invention, a second version number is further configured in the server, where the second version number may be lower than the first version number, and the server further sends the second version number to the client. Under the condition that the current version number of the client is lower than the first version number and higher than the second version number, the upgrading mode of the client can be determined to be selected for upgrading; and under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading. It should be noted that, in the case that the current version number of the client is equal to the first version number, it may be determined that the upgrade mode of the client is silent upgrade or selective upgrade; and under the condition that the current version number of the client is equal to the second version number, determining the upgrading mode of the client to be selected for upgrading or forced upgrading. Therefore, the developer can realize forced upgrade of clients with version numbers lower than the second version number to the latest version by further setting the second version number in the server, thereby improving the controllability of the developer on the version of the clients on the market and reducing the maintenance cost of the clients lower than the second version number; meanwhile, for the client with the version number between the second version number and the first version number, the opportunity of whether the user selects upgrading is provided, the man-machine interaction friendliness is improved, and further balance is formed between the user experience sense and the control of the developer on the version.

Preferably, the second version number may satisfy: in the case where the current version number of the client is lower than the second version number, the latest version of the client may be a version that is architecture-adjusted based on the current version of the client. In the case that the current version number of the client is lower than the first version number and higher than the second version number, the latest version of the client may be a version in which a function is newly added on the basis of the current version of the client. In this way, the maintenance cost for the low version can be reduced by adopting forced upgrade for the latest version of the client for framework adjustment based on the current version, and the user can know that the client needs to be upgraded by providing a user upgrade prompt instead of adopting silent upgrade through forced upgrade because the client is changed greatly after the low version is upgraded, so that man-machine interaction is more friendly; the latest version of the client is selected and updated for the newly added function based on the current version, so that a user can select whether the newly added function of the latest version is needed or not by himself, the man-machine interaction friendliness is improved, and balance is formed between user experience and control of a developer on the version.

In an embodiment of the present invention, the server further sends a file feature code of a file included in the latest version of the client to the client, the client may further obtain the file feature code of the file included in the latest version of the client, and the step of upgrading the client to the latest version may refer to S11 to S15.

The embodiment of the invention also provides a client upgrading method, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 5, fig. 5 is a flowchart of another method for upgrading a client according to an embodiment of the present invention, where the method may be applied to a client, and the method includes:

s501: the current version number of the client is determined.

After the client runs, the current version number of the client can be determined.

S502: and acquiring the latest version number and the first version number of the client.

Specifically, after the client runs, a request is sent to the server, and after the server receives the request, the latest version number and the first version number of the client are sent to the client.

S503: and upgrading the client to the latest version in an upgrade mode of silent upgrade under the condition that the current version number of the client is lower than the latest version number and higher than the first version number.

Referring to fig. 6, fig. 6 is a flowchart of another client upgrade method according to an embodiment of the present invention, where the method may be applied to a client, and the method includes:

s601: the current version number of the client is determined.

S602: and acquiring the latest version number, the first version number and the second version number of the client and file feature codes of files contained in the latest version of the client.

Specifically, after the client runs, a request is sent to the server, and after the server receives the request, the latest version number, the first version number, the second version number and an XML file containing file feature codes of files contained in the latest version of the client are sent to the client.

The latest version number, the first version number, the second version number of the client and the related description of the XML file are detailed in step S302.

S603: and determining the upgrading mode of the client.

The specific description of step S603 is shown in step S303, and the embodiment of the present invention is not described herein again.

S604: and determining an upgrade file list according to the file feature codes of the files contained in the latest version of the client and the file feature codes of the files contained in the current version of the client.

The specific description of step S604 is shown in step S11, and the embodiment of the present invention will not be described herein.

S605: and acquiring an upgrade file corresponding to the upgrade file list, and updating the file contained in the current version according to the upgrade file.

Specifically, after determining the upgrade file list, the client sends the upgrade file list to the server, after the server obtains the upgrade file list, according to the file feature code in the upgrade file list, determining an upgrade file corresponding to the upgrade file list in files included in the latest version of the client, and sending the upgrade file to the client, where the client obtains the upgrade file corresponding to the upgrade file list. Here, the server only issues the files different from the files included in the current version in the files included in the latest version of the client to the client, and does not need to repeatedly issue the files identical to the files included in the current version in the files included in the latest version, so that the utilization rate and the upgrading speed of network resources are improved.

After the client acquires the upgrade file, for the file which belongs to the upgrade file and is modified on the basis of the file contained in the current version, replacing the corresponding file in the file contained in the current version with the modified file; and adding the newly added file to the file contained in the current version for the file which belongs to the newly added file on the basis of the file contained in the current version in the upgrade file.

S606: restarting the client.

The embodiment of the invention provides another client upgrading method, which realizes forced upgrading of clients with version numbers lower than the second version number to the latest version by setting the first version number and the second version number by a developer, improves the controllability of the developer to the versions of the clients on the market, and reduces the maintenance cost of the clients with version numbers lower than the second version number; for the clients with version numbers between the second version number and the first version number, the opportunity of whether the user selects upgrading is provided, and the friendliness of man-machine interaction is improved; the method has the advantages that the client with the version number between the first version number and the latest version number is quietly upgraded to the latest version, the maintenance cost of the client with the version number between the first version number and the latest version number is reduced, the number of times of upgrading selected by a user is reduced, the subsequent use process of the client by the user is optimized, the user experience is improved, the number of times that the user perceives the repairing defect of the client is reduced, the trust degree of the user to the client is improved, and further balance between the user experience and the control of the developer on the version is realized.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a client upgrade apparatus according to an embodiment of the present invention, where the apparatus includes:

an obtaining module 701, configured to obtain a current version number of a client;

a determining module 702, configured to determine a latest version number and a first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading;

and the sending module 703 is configured to send the upgrade mode for the client to upgrade according to the upgrade mode to the client.

In one embodiment of the present invention, the determining module is further configured to determine a second version number of the client, where the second version number is lower than the first version number; determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number; under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading; under the condition that the current version number of the client is equal to the first version number, determining that the upgrading mode of the client is silent upgrading or selecting upgrading; and under the condition that the current version number of the client is equal to the second version number, determining the upgrading mode of the client to be selected for upgrading or forced upgrading.

In one embodiment of the present invention, the obtaining module is further configured to obtain an upgrade file list, where the upgrade file list is a file list determined according to a file feature code of a file included in a latest version of the client and a file feature code of a file included in a current version of the client;

the sending module is further configured to send a file feature code of a file included in the latest version of the client to the client; after the upgrade file list is obtained, the upgrade file corresponding to the upgrade file list is sent to the client.

In one embodiment of the present invention, the first version number satisfies: and in the case that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for performing defect repair on the basis of the current version of the client.

In one embodiment of the present invention, the second version number satisfies: and under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment based on the current version of the client.

The embodiment of the invention provides a client upgrading device, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 8, fig. 8 is a schematic structural diagram of another client upgrade apparatus according to an embodiment of the present invention, where the apparatus includes:

an obtaining module 801, configured to obtain a latest version number and a first version number of the client;

a determining module 802, configured to determine a current version number of a client;

and the upgrade module 803 is configured to upgrade the client to the latest version in an upgrade mode of silent upgrade if the current version number of the client is lower than the latest version number and higher than the first version number.

In one embodiment of the present invention, the obtaining module is further configured to obtain a second version number of the client, where the second version number is lower than the first version number;

the determining module is further configured to determine that an upgrade mode of the client is a selective upgrade if a current version number of the client is lower than the first version number and higher than the second version number; under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading; under the condition that the current version number of the client is equal to the first version number, determining that the upgrading mode of the client is silent upgrading or selecting upgrading; under the condition that the current version number of the client is equal to the second version number, determining that the upgrading mode of the client is selected for upgrading or forced upgrading;

The upgrade module is further configured to respond to an upgrade trigger signal to upgrade the client to the latest version when the upgrade mode of the client is upgrade selection or forced upgrade.

In one embodiment of the present invention, the obtaining module is further configured to obtain a file feature code of a file included in the latest version of the client;

the upgrading module is further used for determining an upgrading file list according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client; acquiring an upgrade file corresponding to the upgrade file list; for the files belonging to the update files modified on the basis of the files contained in the current version, replacing the corresponding files in the files contained in the current version with the modified files; and adding the newly added file to the file contained in the current version for the file which belongs to the newly added file on the basis of the file contained in the current version in the upgrade file.

The embodiment of the invention provides another client upgrading device, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 9, fig. 9 is a schematic structural diagram of a client upgrade system according to an embodiment of the present invention, where the system includes:

a server 901, configured to obtain a current version number of a client; determining the latest version number and the first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading; sending the upgrading mode for the client to upgrade according to the upgrading mode to the client;

A client 902, configured to send a current version number of the client to the server; acquiring the upgrading mode; and upgrading the client to the latest version according to the upgrading mode.

In one embodiment of the present invention, the server is further configured to determine a second version number of the client, where the second version number is lower than the first version number; determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number; under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading; under the condition that the current version number of the client is equal to the first version number, determining that the upgrading mode of the client is silent upgrading or selecting upgrading; under the condition that the current version number of the client is equal to the second version number, determining that the upgrading mode of the client is selected for upgrading or forced upgrading; transmitting file feature codes of files contained in the latest version of the client to the client; after an upgrade file list is obtained, an upgrade file corresponding to the upgrade file list is sent to the client;

The client is also used for acquiring file feature codes of files contained in the latest version of the client; determining an upgrade file list according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client; sending the upgrade file list to the server; acquiring an upgrade file corresponding to the upgrade file list; for the files belonging to the update files modified on the basis of the files contained in the current version, replacing the corresponding files in the files contained in the current version with the modified files; and adding the newly added file to the file contained in the current version for the file which belongs to the newly added file on the basis of the file contained in the current version in the upgrade file.

The embodiment of the invention provides a client upgrading system, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 10, fig. 10 is a schematic structural diagram of another client upgrade system according to an embodiment of the present invention, where the system includes:

the server 1001 is configured to send the latest version number and the first version number of the client to the client.

A client 1002, configured to determine a current version number of the client; acquiring the latest version number and the first version number of the client; and upgrading the client to the latest version in an upgrade mode of silent upgrade under the condition that the current version number of the client is lower than the latest version number and higher than the first version number.

In one embodiment of the present invention, the server is further configured to send a second version number of the client to the client; the file feature codes are used for sending the files contained in the latest version of the client to the client; the method comprises the steps of after an upgrade file list is acquired, sending an upgrade file corresponding to the upgrade file list to the client;

The client is further configured to obtain a second version number of the client; determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number; under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading; under the condition that the current version number of the client is equal to the first version number, determining that the upgrading mode of the client is silent upgrading or selecting upgrading; under the condition that the current version number of the client is equal to the second version number, determining that the upgrading mode of the client is selected for upgrading or forced upgrading; acquiring file feature codes of files contained in the latest version of the client; determining an upgrade file list according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client; sending the upgrade file list to the server; acquiring an upgrade file corresponding to the upgrade file list; for the files belonging to the update files modified on the basis of the files contained in the current version, replacing the corresponding files in the files contained in the current version with the modified files; and adding the newly added file to the file contained in the current version for the file which belongs to the newly added file on the basis of the file contained in the current version in the upgrade file.

The embodiment of the invention provides another client upgrading system, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 11, fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, where the apparatus includes:

a memory 1101 for storing a computer program;

The processor 1102 is configured to implement the steps of a client upgrade method according to the embodiment of the present invention corresponding to fig. 2 or fig. 3 when executing a program stored in a memory.

In one embodiment of the present invention, the electronic device may further include a communication interface, a communication bus, an input-output interface, and a display, wherein the memory, the processor, the input-output interface, the display, and the communication interface perform communication with each other through the communication bus.

The embodiment of the invention provides the electronic equipment, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Referring to fig. 12, fig. 12 is a schematic structural diagram of another electronic device according to an embodiment of the present invention, where the apparatus includes:

a memory 1201 for storing a computer program;

the processor 1202 is configured to implement the steps of a client upgrade method according to the embodiment of the present invention corresponding to fig. 5 or fig. 6 when executing a program stored in a memory.

The embodiment of the invention provides another electronic device, reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user, and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

The embodiment of the invention provides a computer readable storage medium, which stores a computer program, wherein the computer readable storage medium can be read-only memory, random access memory, read-only optical disk, magnetic tape, floppy disk, optical data storage device and the like, and the steps of a client upgrading method provided by the embodiment corresponding to the fig. 2 or 3 of the invention are realized when the computer program is executed by a processor, so that the number of times of upgrading selected by a user is reduced, the subsequent use process of the client by the user is optimized, and the user experience is improved; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

The embodiment of the invention provides another computer readable storage medium, which stores a computer program, wherein the computer readable storage medium can be read-only memory, random access memory, read-only optical disk, magnetic tape, floppy disk, optical data storage device and the like, and the steps of the client upgrading method provided by the embodiment corresponding to the embodiment of the invention shown in fig. 5 or 6 are realized when the computer program is executed by a processor, so that the number of times of upgrading selected by a user is reduced, the subsequent use process of the client by the user is optimized, and the user experience is improved; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Embodiments of the present invention provide a computer program product that may include one or more computer instructions that when run on a computer implement the steps of a client upgrade method provided by the corresponding embodiments of fig. 2 or 3 of the present invention. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium, an optical medium, or a semiconductor medium, etc. The embodiment of the invention provides a computer program product, which reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user and improves the experience of the user; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

Embodiments of the present invention provide another computer program product, which may include one or more computer instructions, which when run on a computer implement the steps of a client upgrade method provided by the corresponding embodiments of fig. 5 or 6 of the present invention. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium, an optical medium, or a semiconductor medium, etc. The embodiment of the invention provides another computer program product, reduces the number of times of upgrading selected by a user, optimizes the subsequent use process of the client by the user, and improves the user experience; the number of times that the user perceives the repairing defect of the client is reduced, and the trust degree of the user to the client is improved; the controllability of the developer to the client version on the market is improved, and the maintenance cost of the client version is reduced.

For apparatus, systems, electronic devices, computer readable storage media, and computer program product embodiments, the description is relatively simple as it is substantially similar to method embodiments, with reference to the accompanying descriptive matter in which method embodiments are described.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Those of ordinary skill in the art will appreciate that implementing all or part of the steps in the above-described method embodiments may be accomplished by programming instructions in a computer readable storage medium, such as: ROM/RAM, magnetic disks, optical disks, etc.

The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for upgrading a client, the method comprising:

acquiring a current version number of a client;

determining the latest version number and a first version number of the client, wherein the first version number meets the following conditions: under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for repairing defects on the basis of the current version of the client;

determining a second version number of the client, the second version number being lower than the first version number, wherein the second version number satisfies: under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment on the basis of the current version of the client;

Determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number;

under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading;

2. The method of claim 1, wherein prior to said sending the upgrade to the client, the method further comprises:

under the condition that the current version number of the client is equal to the first version number, determining that the upgrading mode of the client is silent upgrading or selecting upgrading;

and under the condition that the current version number of the client is equal to the second version number, determining the upgrading mode of the client to be selected for upgrading or forced upgrading.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

transmitting file feature codes of files contained in the latest version of the client to the client;

acquiring an upgrade file list, wherein the upgrade file list is a file list determined according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client;

And sending the upgrade files corresponding to the upgrade file list to the client.

4. A method for upgrading a client, the method comprising:

determining a current version number of the client;

obtaining the latest version number and a first version number of the client, wherein the first version number meets the following conditions: under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for repairing defects on the basis of the current version of the client;

obtaining a second version number of the client, wherein the second version number is lower than the first version number, and the second version number meets the following conditions: under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment on the basis of the current version of the client;

under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, upgrading the client to the latest version in an upgrade mode of silent upgrade;

And under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading.

5. The method according to claim 4, wherein the method further comprises:

under the condition that the current version number of the client is equal to the second version number, determining that the upgrading mode of the client is selected for upgrading or forced upgrading;

and under the condition that the upgrading mode of the client is selected to be upgraded or forced to be upgraded, responding to an upgrading trigger signal to upgrade the client to the latest version.

6. The method according to claim 4 or 5, characterized in that the method further comprises:

acquiring file feature codes of files contained in the latest version of the client;

the upgrading the client to the latest version includes:

determining an upgrade file list according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client;

acquiring an upgrade file corresponding to the upgrade file list;

For the files belonging to the update files modified on the basis of the files contained in the current version, replacing the corresponding files in the files contained in the current version with the modified files;

and adding the newly added file to the file contained in the current version for the file which belongs to the newly added file on the basis of the file contained in the current version in the upgrade file.

7. A client upgrade apparatus, the apparatus comprising:

a determining module, configured to determine a latest version number and a first version number of the client; and under the condition that the current version number of the client is lower than the latest version number and higher than a first version number, determining that the upgrading mode of the client is silent upgrading, wherein the first version number meets the following conditions: under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for repairing defects on the basis of the current version of the client;

the sending module is used for sending the upgrading mode for the client to upgrade according to the upgrading mode to the client;

The determining module is further configured to determine a second version number of the client, where the second version number is lower than the first version number; determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number; under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading; wherein the second version number satisfies: and under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment based on the current version of the client.

8. The apparatus of claim 7, wherein the determining module is further configured to determine that an upgrade mode of the client is silent upgrade or select upgrade if a current version number of the client is equal to the first version number; and under the condition that the current version number of the client is equal to the second version number, determining the upgrading mode of the client to be selected for upgrading or forced upgrading.

9. The apparatus according to claim 7 or 8, wherein the sending module is further configured to send a file feature code of a file included in the latest version of the client to the client; after an upgrade file list is obtained, an upgrade file corresponding to the upgrade file list is sent to the client, wherein the upgrade file list is a file list determined according to file feature codes of files contained in the latest version of the client and file feature codes of files contained in the current version of the client;

the acquisition module is also used for acquiring the upgrade file list.

10. A client upgrade apparatus, the apparatus comprising:

the upgrade module is used for upgrading the client to the latest version in a silent upgrade mode under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, wherein the first version number meets the following conditions: under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for repairing defects on the basis of the current version of the client;

The obtaining module is further configured to obtain a second version number of the client, where the second version number is lower than the first version number; wherein the second version number satisfies: under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment on the basis of the current version of the client;

the determining module is further configured to determine that an upgrade mode of the client is a selective upgrade if a current version number of the client is lower than the first version number and higher than the second version number; and under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading.

11. The apparatus of claim 10, wherein the determining module is further configured to determine that an upgrade mode of the client is silent upgrade or select upgrade if a current version number of the client is equal to the first version number; under the condition that the current version number of the client is equal to the second version number, determining that the upgrading mode of the client is selected for upgrading or forced upgrading;

12. The apparatus according to claim 10 or 11, wherein the obtaining module is further configured to obtain a file feature code of a file included in the latest version of the client;

13. A client upgrade system, the system comprising:

the server is used for acquiring the current version number of the client; determining the latest version number and the first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, determining that the upgrading mode of the client is silent upgrading; sending the upgrading mode for the client to upgrade according to the upgrading mode to the client, wherein the first version number meets the following conditions: under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for repairing defects on the basis of the current version of the client;

The server is further configured to determine a second version number of the client, where the second version number is lower than the first version number, and determine that an upgrade mode of the client is a selective upgrade if a current version number of the client is lower than the first version number and higher than the second version number; and under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading, wherein the second version number meets the following conditions: under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment on the basis of the current version of the client;

The system comprises:

the server is used for sending the latest version number and the first version number of the client to the client, wherein the first version number meets the following conditions: under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, the latest version of the client is a version for repairing defects on the basis of the current version of the client;

The server is further configured to send a second version number of the client to the client, where the second version number satisfies: under the condition that the current version number of the client is lower than the second version number, the latest version of the client is a version which is subjected to architecture adjustment on the basis of the current version of the client;

the client is used for determining the current version number of the client; acquiring the latest version number and the first version number of the client; under the condition that the current version number of the client is lower than the latest version number and higher than the first version number, upgrading the client to the latest version in an upgrade mode of silent upgrade;

the client is further configured to obtain a second version number of the client, where the second version number is lower than the first version number; determining that the upgrading mode of the client is selected upgrading under the condition that the current version number of the client is lower than the first version number and higher than the second version number; and under the condition that the current version number of the client is lower than the second version number, determining that the upgrading mode of the client is forced upgrading.