WO2017071358A1

WO2017071358A1 - Software upgrade method and apparatus

Info

Publication number: WO2017071358A1
Application number: PCT/CN2016/093111
Authority: WO
Inventors: 田楠; 刘荣
Original assignee: 广州视睿电子科技有限公司
Priority date: 2015-10-26
Filing date: 2016-08-03
Publication date: 2017-05-04
Also published as: CN105302603A; TW201715388A; TWI626593B

Abstract

Disclosed are a software upgrade method and apparatus. The method comprises: a client starting a loader (101); the client acquiring a running environment parameter of software to be upgraded (102); the client invoking the loader to send an upgrade request carrying the running environment parameter to a serving end corresponding to the loader (103); the client invoking the loader to receive an upgrade response sent by the serving end in response to the upgrade request (104), wherein the upgrade response carries a client software upgrade package matching the running environment parameter; and the client using the client software upgrade package to upgrade the software to be upgraded (105). By means of this method, software of a client and a server end can be synchronously upgraded, so as to ensure that upgraded versions of the client and the server end are consistent.

Description

Method and device for software upgrade

Technical field

The present invention relates to the field of network communication and computer technology, and in particular, to a software upgrade method and apparatus.

Background technique

At present, with the development of the Internet, there are more and more scenarios for software applications. When developing software, software developers need to develop software with different architectures for different types of software, such as client/server architecture software, referred to as C/S (Client/Server, client/server) architecture.

After the software is developed, it needs to be put on the market. As the user's needs change, the software needs to be upgraded and maintained. For the software of the C/S architecture, the software of the client and the software of the server are respectively run on different hardware devices, and the operating systems on different hardware devices may be different. Generally, the software of the client and the software of the server are separately upgraded. Because the client software and server software are upgraded separately, the upgraded client software version may be inconsistent with the upgraded server software version.

Summary of the invention

The invention provides a software upgrade method and device, so that the client upgrades according to the version matched with the server, thereby ensuring the consistency of the upgraded version of the client and the server, and improving the user experience.

A first aspect of the present invention discloses a software upgrade method, including:

The client starts the loader;

The client obtains an operating environment parameter of the software to be upgraded;

The client invoking the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader;

The client invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries a client software upgrade package that matches the running environment parameter, and the upgrade The request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package;

The client upgrades the software to be upgraded by using the client software upgrade package.

In conjunction with the first aspect, in a first possible implementation manner of the first aspect, the client, before the loader sends the upgrade request carrying the running environment parameter to the server corresponding to the loader, The method further includes:

The client acquires a current version of the loader;

When the current version of the loader is lower than the latest version of the loader, the client updates the loader according to the latest version of the loader.

In conjunction with the first aspect, in a second possible implementation of the first aspect, the loader is a program plug-in or a hardware device that loads the program.

A second aspect of the present invention discloses a method for software upgrade, the method comprising:

The server receives the client and sends a upgrade request to the loader corresponding to the server, where the upgrade request carries the operating environment parameter of the software to be upgraded by the client;

The server sends an upgrade response to the client in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter;

The server performs the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package version.

With reference to the second aspect, in a first possible implementation manner of the second aspect, before the server receives the client, and the loader corresponding to the server sends an upgrade request, the method further includes: The client software upgrade package is bound to the server software upgrade package.

With reference to the second aspect, in a second possible implementation manner of the second aspect, the method further includes:

When the server upgrades the corresponding software by using the second server software upgrade package, the server pushes the second client software upgrade package with the same version of the second server software upgrade package to the client. To enable the client to perform a simultaneous upgrade.

A third aspect of the present invention discloses a client, including:

a startup module for starting the loader;

An obtaining module, configured to acquire an operating environment parameter of the software to be upgraded by the client;

a calling module, configured to invoke the loader to send an upgrade request carrying the running environment parameter to a server corresponding to the loader;

a receiving module, the client invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries a guest that matches the operating environment parameter a client software upgrade package, where the upgrade request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package;

An upgrade module, where the client upgrades the software to be upgraded by using the client software upgrade package.

With reference to the third aspect, in a first possible implementation manner of the third aspect,

The device also includes a loader acquisition module and a loader update module;

a loader acquisition module for the client to obtain the current version of the loader;

A loader update module for updating the loader according to a latest version of the loader when a current version of the loader is lower than a latest version of the loader.

A fourth aspect of the present invention discloses a server, including:

a calling module, configured to receive, by the server, a loader, and a loader corresponding to the server, to send an upgrade request, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client;

a sending module, the server sends an upgrade response to the client in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter;

The upgrade module, where the server uses the same server software upgrade package as the client software upgrade package to perform the corresponding software upgrade.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the server further includes: a binding module, configured to bind the client software upgrade package to the server software upgrade package .

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, the server further includes: a synchronization upgrade module, configured to: when the upgrade module upgrades the corresponding software by using the second server software upgrade package, The server pushes the second client software upgrade package with the same version of the second server software upgrade package to the client, so that the client performs synchronous upgrade.

It can be seen that, in the technical solution provided by the present invention, since the upgrade software of the client is bound to the upgrade software of the server, the client can send the running environment state parameter to the server by calling the loader, so that the server runs according to the server. The environment determines a software version required by the client, and performs a client software upgrade according to the software version, and the upgrade request is used to trigger the server to use the same server version as the client software upgrade package. The software upgrade package performs the corresponding software upgrade, which solves the problem that the software version mismatch caused by the client and the server need to be updated separately, ensures the consistency of the upgraded version of the client and the server, and improves the user experience.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings to be used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

1 is a schematic flowchart of a method for software upgrade according to an embodiment of the present invention;

2 is a schematic flowchart of another method for software upgrade according to an embodiment of the present invention;

FIG. 3 is a schematic flowchart diagram of another method for software upgrade according to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart diagram of another method for software upgrade according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a client according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a server provided by an embodiment of the present invention;

FIG. 7 is a schematic diagram of a software upgrade system according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a physical structure of a client provided by the present invention; FIG.

FIG. 9 is a schematic diagram of a physical structure of a server provided by the present invention.

detailed description

The invention provides a software upgrade method and device, in order to synchronously upgrade the software of the client and the server, thereby ensuring the consistency of the upgraded version of the client and the server, and improving the user experience.

The technical solutions in the embodiments of the present invention will be clearly described in conjunction with the drawings in the embodiments of the present invention. Some embodiments of the invention, rather than all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of the present invention.

The terms "first", "second" and "third" and the like appearing in the present specification, the claims and the drawings are used to distinguish different objects and are not intended to describe a particular order. Furthermore, the terms "comprises" and "comprising" and "comprising" are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units not listed, or alternatively Other steps or units inherent to these processes, methods, products or equipment.

An embodiment of a method of software upgrade of the present invention. A software upgrade method may include: a client launching a loader; the client acquiring a running environment parameter of the software to be upgraded; the client calling the loader to send a carrying to a server corresponding to the loader An upgrade request of the operating environment parameter; the client invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries a match with the operating environment parameter a client software upgrade package, the upgrade request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package; the client upgrades by using the client software The package upgrades the software to be upgraded.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart diagram of a method for software upgrade according to an embodiment of the present invention. As shown in FIG. 1 , a method for software upgrade provided by an embodiment of the present invention may include the following content:

101. The client starts the loader.

The client may also be referred to as a client, and refers to a program corresponding to a server and providing a local service for the client.

For example, after the development of the Internet, the more commonly used clients include a web browser such as the World Wide Web, an email client for receiving emails, and client software for instant messaging. For this type of application, there is a corresponding server and service program in the network to provide the corresponding services, such as database services, email services or other services.

Alternatively, the client can also be a client.

The client can be a desktop computer, a wireless screen, a mobile phone, a tablet, a laptop, a palmtop, a mobile internet device, or other terminal device.

Wherein, the loader is a program plug-in or a hardware device loading the program.

For example, the loader can be a download program plug-in on the webpage, or can also be a USB flash drive, read-only memory (ROM), random access memory (RAM, Random Access Memory) loaded with the program. ), one of a mobile hard disk, a magnetic disk, or a disc.

102. The client obtains an operating environment parameter of the software to be upgraded.

The running environment parameter may be a type of an operating system.

For example, the operating environment can be a windows system, a Linux system, or other operating system.

Optionally, the operating environment may also be some other software.

For example, the running environment can also be office, CAJViewer or other application software.

Optionally, the running environment may also be a third-party runtime library.

For example, the runtime environment can be DotNet, DirectX, or other third party runtimes.

103. The client invokes the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader.

104. The client invokes the loader to receive an upgrade response sent by the server in response to the upgrade request.

The upgrade response carries a client software upgrade package that matches the running environment parameter.

The upgrade request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package.

105. The client upgrades the software to be upgraded by using the client software upgrade package.

Taking wireless transmission as an example, the wireless transmission system consists of two parts: a transmitting end and a receiving end, and the transmitting end and the receiving end communicate through a self-built wireless network. The transmitter is a small piece of hardware running an embedded system that stores the loader program. The user connects the transmitter to the PC/Mac through the USB interface and recognizes it as a USB mass storage device on the computer. The user can open the device and run the loader program. The loader program establishes communication with the receiving end through the transmitting end hardware and sends operating system (Windows or Mac) information to the server program running on the receiving end. The server program sends the client program corresponding to the requesting operating system to the loader program, and the loader program runs the received client program. The client program obtains information such as a screen image and a sound output from the operating system, and is encoded and transmitted to the server program running on the receiving end through the transmitting end hardware, and the server program performs decoding and presentation to complete the entire wireless screen printing process.

This embodiment is described by taking a wireless screen as an example. However, the embodiment is not limited to wireless screen transmission. The client in this embodiment may be a desktop computer, a wireless screen, a mobile phone, a tablet computer, a notebook computer, a palm computer, or a mobile device. Internet device or other terminal device.

It can be seen that, in the solution of this embodiment, the client sends the running environment to the server by calling the loader, so that the server determines a software version required by the client according to the operating environment, the client And acquiring, by the loader, the software version sent by the server, and performing software upgrade according to the software version. This ensures the consistency of the upgraded version of the client and server and improves the user experience.

Referring to FIG. 2, FIG. 2 is a flow of a software upgrade method according to another embodiment of the present invention. Schematic diagram. The specific method includes the following steps.

201. The client starts the loader.

202. The client obtains an operating environment parameter of the software to be upgraded.

Optionally, the operating environment may also be some other software.

Optionally, the running environment may also be a third-party runtime library.

203. The client acquires a current version of the loader; when a current version of the loader is lower than a latest version of the loader, the client loads the load according to a latest version of the loader. The device is updated.

204. The client invokes the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader.

205. The client invokes the loader to receive an upgrade response sent by the server in response to the upgrade request.

206. The client upgrades the software to be upgraded by using the client software upgrade package.

It can be seen that while upgrading the client, the synchronous update of the loader is guaranteed, which facilitates the communication connection between the loader and the client and the server, thereby ensuring synchronous update of the client software and the server software.

Another embodiment of a method of software upgrade of the present invention. A software upgrade method, the method includes: the server receives a client call, and the loader corresponding to the server sends an upgrade request, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client; The client sends an upgrade response in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter; and the server uses the same server version as the client software upgrade package version. The software upgrade package performs the corresponding software upgrade.

Please refer to FIG. 3. FIG. 3 is a schematic flowchart diagram of another software upgrade method according to an embodiment of the present invention. The specific method includes the following steps.

301. The server receives a client, and sends a upgrade request to the loader corresponding to the server, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client.

302. The server sends an upgrade response to the client in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter.

303. The server uses a server software upgrade package with the same version of the client software upgrade package to perform a corresponding software upgrade.

It can be seen that, in the solution of this embodiment, the upgrade sent by the client may trigger the server to use the server software upgrade package with the same version of the client software upgrade package to perform corresponding software upgrade, which can effectively ensure the server and the server. Synchronous update of client software.

Please refer to FIG. 4. FIG. 4 is a schematic flowchart diagram of another software upgrade method according to an embodiment of the present invention. The specific method includes the following steps.

401. Bind the client software upgrade package to the server software upgrade package.

402. The server receives the client, and sends a upgrade request to the loader corresponding to the server, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client.

403. The server sends an upgrade response to the client in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter.

404. The server uses a server software upgrade package with the same version of the client software upgrade package to perform a corresponding software upgrade.

405. When the server upgrades the corresponding software by using the second server software upgrade package, the server pushes the second client software with the same version of the second server software upgrade package to the client. The upgrade package enables the client to perform a simultaneous upgrade.

It can be seen that, in the solution of this embodiment, when the server preferentially upgrades, the server pushes the client software upgrade package with the same version of the server software upgrade package to the client, thereby ensuring that the client is preferentially upgraded when the server is preferentially upgraded. The terminal can also respond in time to ensure the consistency of the client software and the server software version.

Referring to FIG. 5, FIG. 5 is a schematic structural diagram of a client according to an embodiment of the present invention. As shown in FIG. 5, the client provided by one embodiment of the present invention may include the following content:

a startup module 501, configured to start a loader;

The obtaining module 502 is configured to obtain an operating environment parameter of the software to be upgraded by the client.

The calling module 503 is configured to invoke the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader;

Receiving module 504, the client invoking the loader to receive the server response to the upgrade request And an upgrade response sent by the client, where the upgrade response carries a client software upgrade package that matches the running environment parameter, where the upgrade request is used to trigger the server to use the client software upgrade package version. The same server software upgrade package is upgraded accordingly;

The upgrade module 505 is configured to upgrade the software to be upgraded by using the client software upgrade package.

As can be seen from the above, in the solution of the embodiment, the client sends the running environment to the server by calling the loader, so that the server determines the software version required by the client according to the operating environment, the client And acquiring, by the loader, the software version sent by the server, and performing software upgrade according to the software version. This ensures the consistency of the upgraded version of the client and server and improves the user experience.

Optionally, the client further includes the client further includes a loader obtaining module 506 and a loader updating module 507;

a loader obtaining module 506, configured to acquire a current version of the loader by a client;

The loader update module 507 is configured to update the loader according to the latest version of the loader when the current version of the loader is lower than the latest version of the loader.

Please refer to FIG. 6. FIG. 6 is a schematic structural diagram of a server provided by an embodiment of the present invention. As shown in FIG. 6, the server provided by one embodiment of the present invention may include the following content:

The calling module 601 is configured to receive, by the server, a client, and a loader corresponding to the server, to send an upgrade request, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client;

The sending module 602, the server sends an upgrade response to the client in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter;

The upgrade module 603 is configured to perform a corresponding software upgrade by using the same server software upgrade package as the client software upgrade package.

Optionally, based on the server provided in FIG. 6, the server further includes a binding module 604, configured to bind the client software upgrade package to the server software upgrade package.

Optionally, based on the server provided in FIG. 6, the server further includes a synchronization upgrade module 605, and the same The step upgrade module 605 is configured to: when the upgrade module 603 upgrades the corresponding software by using the second server software upgrade package, the server pushes the second version of the same version of the second server software upgrade package to the client The client software upgrade package enables the client to perform synchronous upgrades.

In another embodiment of the present invention, the upgraded version of the client to be upgraded program is located on the server, and is bound to the upgraded version of the to-be-upgraded program on the corresponding server on the server. When the program to be upgraded on the server is upgraded according to the upgraded version, the server sends an upgraded version of the program to be upgraded to the client, so that the client to be upgraded is upgraded according to the version to be upgraded, thereby causing the client program and the server. The version of the program at the end matches.

Before sending the upgrade version to the client, it is necessary to determine the running environment of the client; and if the upgrade version is sent to the loader of the client through the high-speed connection channel, the work efficiency is improved.

As shown in FIG. 7, the present invention provides a system for software upgrade. The system includes a client 701 and a server 702. The client 701 may be an electronic device such as a personal computer, a tablet computer, or a smart terminal; the server 702 may be an electronic device such as a server.

The client 701 acquires the current version of the loader;

When the current version of the loader is lower than the latest version of the loader, the client 701 updates the loader according to the latest version of the loader;

The client 701 starts the loader and obtains operating environment parameters of the software to be upgraded;

The client 701 establishes a high speed connection with the server 702 through the loader;

The client 701 calls the loader to send an upgrade request carrying the operating environment parameter to the server 702 corresponding to the loader;

The server 702 receives the client 701 and sends a upgrade request to the loader corresponding to the service 702. The upgrade request carries the operating environment parameter of the software to be upgraded by the client.

The server 702 sends an upgrade response to the client 701 in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter; wherein the server 702 receives the client call and the server Before the loader corresponding to the server sends the upgrade request, the client software upgrade package is bound to the server software upgrade package;

The server 702 performs the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package version;

The client 701 invokes the loader to send an upgrade response sent by the server 702 in response to the upgrade request, wherein the upgrade response carries a client software upgrade that matches the runtime environment parameter. a level package, where the upgrade request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package;

The client 701 upgrades the software to be upgraded by using the client software upgrade package.

As shown in FIG. 8, in another embodiment of the present invention, a client is provided, and the client may be an electronic device such as a personal computer, a tablet computer, a smart terminal, or a mobile phone. The client 800 includes hardware such as a central processing unit CPU 801, a memory 802, a display 803, and a bus 804. The CPU executes the server program stored in the memory in advance to upgrade the program to be upgraded by the client, and the execution process specifically includes:

Start the loader;

Obtain the running environment parameters of the software to be upgraded;

Invoking the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader;

Invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries a client software upgrade package that matches the running environment parameter, and the upgrade request is used to trigger The server performs the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package version;

The software to be upgraded is upgraded by using the client software upgrade package.

Optionally, before the client sends the upgrade request that carries the running environment parameter to the server corresponding to the loader, the method further includes:

The client acquires a current version of the loader;

As shown in FIG. 9, in another embodiment of the present invention, a server is provided, and the server may be a server. The server 900 includes hardware such as a CPU 901, a memory 902, a bus 903, and a display 904. The CPU 901 executes a server program stored in advance in the memory to be upgraded to the client. The sequence is upgraded, and the execution process specifically includes:

Receiving, by the client, a loader corresponding to the server to send an upgrade request, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client;

Sending, to the client, an upgrade response in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter;

Use the same server software upgrade package as the client software upgrade package to perform the corresponding software upgrade.

Optionally, before the receiving client sends an upgrade request to the loader corresponding to the server, the method further includes: upgrading the client software upgrade package and the server software upgrade package. Bind.

Optionally, based on the foregoing method, when the corresponding software is upgraded by using the second server software upgrade package, the second client software upgrade package of the same version as the second server software upgrade package is pushed to the client, so that The client performs a synchronous upgrade.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

In the several embodiments provided herein, it should be understood that the disclosed apparatus may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like. .

Claims

A method for software upgrade, characterized in that the method comprises:

The client starts the loader;

The client obtains an operating environment parameter of the software to be upgraded;

The client invoking the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader;

The client invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries a client software upgrade package that matches the running environment parameter, and the upgrade The request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package;

The client upgrades the software to be upgraded by using the client software upgrade package.
The method of claim 1, wherein the method further comprises: the client invoking the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader, the method further comprising:

The client acquires a current version of the loader;

When the current version of the loader is lower than the latest version of the loader, the client updates the loader according to the latest version of the loader.
A software upgrade method, the method comprising:

The server receives the client and sends a upgrade request to the loader corresponding to the server, where the upgrade request carries the operating environment parameter of the software to be upgraded by the client;

The server sends an upgrade response to the client in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter;

The server performs the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package version.
The method according to claim 3, wherein the method further comprises: before the server receives a client call, and the loader corresponding to the server sends an upgrade request, the method further comprises: The software upgrade package is bound to the server software upgrade package.
The method according to claim 3, wherein the method further comprises: when the server upgrades the corresponding software by using the second server software upgrade package, the server pushes the The second server software upgrade package with the same version of the second server software upgrade package enables the client to perform synchronous upgrade.
A client, wherein the client includes:

a startup module for starting the loader;

An obtaining module, configured to acquire an operating environment parameter of the software to be upgraded by the client;

a calling module, configured to invoke the loader to send an upgrade request carrying the running environment parameter to a server corresponding to the loader;

a receiving module, the client invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter, The upgrade request is used to trigger the server to perform a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package;

An upgrade module, where the client upgrades the software to be upgraded by using the client software upgrade package.
The client of claim 6 wherein:

The client further includes a loader acquisition module and a loader update module;

a loader acquisition module for the client to obtain the current version of the loader;

A loader update module for updating the loader according to a latest version of the loader when a current version of the loader is lower than a latest version of the loader.
A server, wherein the server comprises:

a calling module, configured to receive, by the client, a loader corresponding to the server to send an upgrade request, where the upgrade request carries an operating environment parameter of the software to be upgraded by the client;

a sending module, configured to send, to the client, an upgrade response that is responsive to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter;

An upgrade module for upgrading the same server software using the same version of the client software upgrade package The package is upgraded accordingly.
The server of claim 8 wherein said server further comprises:

And a binding module, configured to bind the client software upgrade package to the server software upgrade package.
The server according to claim 8, wherein the server further comprises: a synchronization upgrade module, configured to: when the upgrade module upgrades the corresponding software by using the second server software upgrade package, the server sends the The client pushes the second client software upgrade package with the same version of the second server software upgrade package, so that the client performs synchronous upgrade.