TWI626593B - Method and device for upgrading software - Google Patents

Abstract

The present invention discloses a software upgrade method and apparatus, wherein the method includes a client-side boot loader; the client acquires an operating environment parameter of the software to be upgraded; the client invokes the loader to and The server corresponding to the loader sends an upgrade request carrying the operating environment parameter; the user invokes 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; and the user terminal upgrades the software to be upgraded by using the client software upgrade package. By adopting the invention, the software of the client end and the server end can be synchronously upgraded, thereby ensuring the consistency of the upgraded version of the client end and the server end.

Description

Method and device for upgrading software

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

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 running 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 respectively required. Upgrade. Because the client software and the server software are upgraded separately, the upgraded client software version may be inconsistent with the upgraded server software version.

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

A first aspect of the present invention discloses a method for upgrading a software, comprising: a client launching a loader; the client acquiring a running environment parameter of the software to be upgraded; the client calling the loader to correspond to the loader The server sends an upgrade request carrying the operating environment parameter; the client invokes the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries the a client software upgrade package that matches the running environment parameter, 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; and the user end The software to be upgraded is 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 user, before the calling, sends the upgrade request that carries the running environment parameter to the server corresponding to the loader, The method further includes: the client acquiring a current version of the loader; when the current version of the loader is lower than a latest version of the loader, the user is based on a latest version of the loader Update 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 upgrading a software, the method comprising: receiving, by a server, a loader that is sent by a client and corresponding to the server to send an upgrade request, where the upgrade request carries the software to be upgraded by the user Running the environment parameter; the server sends an upgrade response to the user end in response to the upgrade request, the upgrade response carrying a client software upgrade package matching the running environment parameter; and the server utilizing The client software upgrade package with the same version of the client software upgrade package performs the corresponding software upgrade.

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 the 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 Pushing the second client software upgrade package with the same version of the second server software upgrade package to the user end, so that the user end performs synchronous upgrade.

The third party of the present invention discloses a user terminal, which comprises: a startup module, an acquisition module, a calling module, a receiving module and an upgrade module. The boot module is used to start the loader. The obtaining module is configured to obtain an operating environment parameter of the software to be upgraded by the user end. The calling module is configured to invoke the loader to send an upgrade request carrying the operating environment parameter to a server corresponding to the loader. The receiving module is configured to invoke 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, and the upgrade request is used to trigger the server to use the same server software upgrade package as the client software upgrade package. Perform the corresponding software upgrade. The upgrade module is configured to upgrade the software to be upgraded by using the client software upgrade package.

In conjunction with the third vendor, in a first possible implementation manner, the device further includes a loader acquisition module and a loader update module; and a loader acquisition module for the user to acquire the loader a current version; a loader update module, configured to update 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, a transmitting module, and an upgrade module. The calling module is configured to receive, by the server, the client to send an 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 user. The sending module sends, by the server, an upgrade response that is responsive to the upgrade request, and the upgrade response carries a client software upgrade package that matches the running environment parameter. The upgrade module is configured to perform the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package.

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 perform the client software upgrade package and the server software upgrade package Bind.

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 use the second server software upgrade package to upgrade the upgrade module In the software, 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 user performs the synchronization upgrade.

It can be seen that, in the technical solution provided by the present invention, since the upgrade software of the client end is bound to the upgrade software of the server end, the user terminal can send the running environment state parameter to the server by calling the loader to make the server. Determining a software version required by the client according to the operating environment, and performing a client software upgrade according to the software version, and the upgrade request is used to trigger the server to use the client software upgrade package version. The same software upgrade package of the server software performs the corresponding software upgrade, which solves the problem that the software version does not match the update between the client and the server, and ensures the consistency of the upgraded version between the client and the server. Improved user experience.

The invention provides a software upgrade method and device, so as 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 below in conjunction with the drawings in the embodiments of the present invention. It is merely an embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope should 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 items, and are not intended to describe a particular order. Furthermore, the terms "comprising" and "having," and "the" 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 includes additional steps or units not listed, or alternatively further 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 loader; the client acquiring a running environment parameter of the software to be upgraded; the client calling the loader to send a carrying place to a server corresponding to the loader An upgrade request of the operating environment parameter; the user invoking the loader to receive an upgrade response sent by the server in response to the upgrade request, wherein the upgrade response carries a user that matches the running environment parameter The software upgrade package is configured to trigger the server to perform a software upgrade by using a server software upgrade package with the same version of the client software upgrade package; the user end is upgraded by using the client software. The package upgrades the software to be upgraded.

Referring 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 upgrading a software provided by an embodiment of the present invention may include the following contents:

Step 101: The client starts the loader.

The client may also be referred to as a client, and refers to a program that provides a native service to the client corresponding to the server.

For example, after the development of the Internet, the more commonly used clients include web browsers such as the World Wide Web, email clients when 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 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 computer, a mobile internet device, or other terminal device.

The loader is a program plug-in program or a hardware device that loads 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) loaded with the program. , one of the Random Access Memory), a mobile hard drive, a disk, or a disc.

Step 102: The client acquires an operating environment parameter of the software to be upgraded.

The operating environment parameter may be a type of the operating system.

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

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

For example, the operating environment can also be Office, CAJViewer, or other application software.

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

For example, the runtime environment can be a DotNet, DirectX, or other third-party vendor runtime.

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

Step 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.

Step 105: The user end upgrades the software to be upgraded by using the client software upgrade package.

Taking wireless transmission as an example, a wireless screen transmission system is composed of a transmitting end and a receiving end, and the transmitting end and the receiving end communicate by using a self-built wireless network. The transmitter is a small hardware running an embedded system in which the loader program is stored. The user connects the transmitter to the PC/Mac through the USB interface, and recognizes it as a USB large storage area device on the computer. The user can open the device and run the loader program. The loader program communicates with the receiving end by the transmitting end hardware and sends the 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 then runs the received client program. The client program obtains information such as the screen image and the sound output from the operating system. After being encoded, the client sends the firmware to the server program running on the receiving end, and the server program decodes and renders the entire wireless screen.

In this embodiment, the wireless screen is taken as an example for description, but the embodiment is not limited to the wireless screen. The user terminal of this embodiment may be a desktop computer, a wireless screen, a mobile phone, a tablet computer, a notebook computer, or a palm. Computer, mobile internet device or other terminal device.

It can be seen that, in the solution of the embodiment, the user end sends the running environment to the server by calling the loader, so that the server determines the software version required by the user terminal according to the operating environment. The user end acquires the software version sent by the server by using the loader, and performs software upgrade according to the software version. Therefore, the consistency between the upgraded version of the client and the server is ensured, and the user experience is improved.

Referring to FIG. 2, FIG. 2 is a schematic flowchart diagram of a method for upgrading a software according to another embodiment of the present invention. The specific method includes the following steps.

Step 201: The client starts the loader.

Step 202: The client acquires an operating environment parameter of the software to be upgraded.

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

For example, the operating environment can also be Office, CAJViewer, or other application software.

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

Step 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 user end is configured according to a latest version of the loader. The loader is updated.

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

Step 205: 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.

Step 206: The user end 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 ensured, 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 may include: 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 user; the server sends the user to the user Sending, by the terminal, 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; the server uses the same server software version as the client software upgrade package version. Upgrade the package to perform the corresponding software upgrade.

Referring 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.

Step 301: The server receives the client to call the loader corresponding to the server to send an upgrade request, where the upgrade request carries the operating environment parameter of the software to be upgraded by the user.

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

Step 303: The server performs the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package.

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

Referring 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.

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

Step 402: 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 user.

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

Step 404: The server performs the corresponding software upgrade by using the same server software upgrade package as the client software upgrade package.

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

It can be seen that, in the solution of the 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 user is preferentially upgraded when the server is preferentially upgraded. The terminal can also respond in time, thus ensuring the consistency between the client software and the server software version.

Referring to FIG. 5, FIG. 5 is a schematic structural diagram of a user end 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:

The startup module 501 is configured to start the loader;

The obtaining module 502 is configured to obtain an operating environment parameter of the software to be upgraded by the user end;

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;

The receiving module 504 is configured to invoke 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;

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 user end sends the running environment to the server by calling the loader, so that the server determines the software version required by the user terminal according to the operating environment. The user end acquires the software version sent by the server by using the loader, and performs software upgrade according to the software version. Therefore, the consistency between the upgraded version of the client and the server is ensured, and the user experience is improved.

Optionally, the client further includes a loader acquisition module 506 and a loader update module 507;

a loader acquisition 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.

Referring 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, the client to send an 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 user end;

The sending module 602, the server sends an upgrade response to the user end, and 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 a server software upgrade package with the same version of the client software upgrade package.

It can be seen that, in the solution of the 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 user is preferentially upgraded when the server is preferentially upgraded. The terminal can also respond in time, thus ensuring the consistency between the client software and the server software version.

Optionally, based on the server provided in FIG. 6 , the server further includes a binding module 604, where the binding module 604 is configured to perform the client software upgrade package and the server software upgrade package. Bind.

Optionally, based on the server provided in FIG. 6 , the server further includes a synchronization upgrade module 605, where the synchronization upgrade module 605 is configured to use the second server software upgrade package to upgrade In the software, 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 user performs the synchronization upgrade.

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 program to be upgraded 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 program to be upgraded by the client is upgraded according to the version to be upgraded, thereby enabling the client program and the server. The version of the program on the terminal side matches.

Before sending the upgrade version to the client, it is necessary to determine the operating 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 Figure 7, the present invention provides a software upgrade system. The system includes a client 701 and a server 702. The client 701 can be an electronic device such as a personal computer, a tablet computer, or a smart terminal; the server 702 can 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 the running environment parameters of the software to be upgraded;

The client 701 establishes a high speed connection with the server 702 by 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 loader sent by the client 701 to the loader corresponding to the service 702, and the upgrade request carries the operating environment parameter of the software to be upgraded by the user.

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 upgrade response sent by the loader server 702 in response to the upgrade request, where the upgrade response carries a client software upgrade package that matches the running environment parameter, and the upgrade request The software upgrade is performed to trigger the server to perform a software upgrade by using the same server software upgrade package as 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 user terminal is provided, and the user terminal may be an electronic device such as a personal computer, a tablet computer, a smart terminal device, 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 a server program pre-stored in the memory 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, where 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 a corresponding software upgrade by using a server software upgrade package with the same version of the client software upgrade package;

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

Optionally, before the user invokes the loader to send an 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.

It can be seen that, in the solution of the embodiment, the user end sends the running environment to the server by calling the loader, so that the server determines the software version required by the user terminal according to the operating environment. The user end acquires the software version sent by the server by using the loader, and performs software upgrade according to the software version. Therefore, the consistency between the upgraded version of the client and the server is ensured, and the user experience is improved.

As shown in FIG. 9, in another embodiment of the present invention, a server is provided, which may be a server. The server 900 includes hardware such as a central processing unit (CPU) 901, a memory 902, a bus 903, and a display 904. The CPU 901 executes a server program that is pre-stored in the memory to upgrade the program to be upgraded by the client. The execution process specifically includes:

The receiving client invokes 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 user end;

Sending, to the user end, 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;

The software upgrade is performed by using the same server software upgrade package as the client software upgrade package.

Optionally, before the receiving client calls the loader corresponding to the server to send an upgrade request, the method further includes: upgrading the client software upgrade package and the server software by using the foregoing method. The package is bound.

Alternatively, 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 with the same version of the second server software upgrade package is pushed to the user terminal. , so that the user side to synchronize upgrade.

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

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 by the present application, it should be understood that the disclosed device can be implemented in other manners. 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 integrated. Go to 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 a hardware or 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, can be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute 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: USB flash drive, read-only memory (ROM), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, and the like. The medium of the code. The above are only the preferred embodiments of the present invention, and all changes and modifications made to the scope of the present invention should be within the scope of the present invention.

101 to 105, 201 to 206, 301 to 303, 401 to 405 ‧ ‧ steps

501‧‧‧Starting module

502‧‧‧Getting module

503‧‧‧call module

504‧‧‧ receiving module

505‧‧‧Upgrade Module

506‧‧‧Loader acquisition module

507‧‧‧Loader Update Module

601‧‧‧call module

602‧‧‧Send module

603‧‧‧Upgrade module

604‧‧‧Binding module

605‧‧‧Synchronous upgrade module

701, 800‧‧‧ client

702, 900‧‧‧ server

801, 901‧‧‧ central processor

802, 902‧‧‧ memory

803, 903‧‧‧ display

804, 904‧‧ ‧ busbar

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present invention, Those skilled in the art will be able to obtain other schemas based on these schemas without paying for creative labor. FIG. 1 is a schematic flowchart diagram of a method for upgrading a software according to an embodiment of the present invention. FIG. 2 is a schematic flowchart diagram 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 invention. FIG. 4 is a schematic flowchart diagram of another method for software upgrade according to an embodiment of the present invention. FIG. 5 is a schematic structural diagram of a user end according to an embodiment of the present invention. 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 showing the physical structure of a client provided by the present invention. Figure 9 is a schematic diagram showing the physical structure of the server provided by the present invention.

Claims (10)

A software upgrade method includes: a client starts a loader; the client acquires a running environment parameter of the software to be upgraded; the client calls the loader to send and carry the running environment to a server corresponding to the loader The upgrade request of the parameter; the client invokes 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 matching the running environment parameter, and the upgrade request is further The server is used to trigger the server to use the server software upgrade package with the same version of the client software upgrade package to perform the corresponding software upgrade; and the user uses the client software upgrade package to upgrade the software to be upgraded. . The method of claim 1, wherein the method, after the client calls the loader to send an upgrade request carrying the running environment parameter to a server corresponding to the loader, the method further comprises: the user acquiring the loader The current version; and 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 includes: receiving, by the server, an upgrade request sent by the user end by calling a loader corresponding to the server end, where the upgrade request carries an operating environment parameter of the software to be upgraded by the user end; the server sends the service environment parameter to the user Sending an upgrade response to the upgrade request, the upgrade response carrying the client software upgrade package matching the running environment parameter; and the server being triggered by the upgrade request to utilize the same version as the client software upgrade package of The server software upgrade package performs the corresponding software upgrade. The method of claim 3, wherein the server receives the client to call the loader corresponding to the server to send an upgrade request, the method further comprises: performing the client software upgrade package and the server software upgrade package Bind. The method of claim 3, further comprising: when the server upgrades the corresponding software by using the second server software upgrade package, the server pushes the same version of the second server software upgrade package to the client. The second client software upgrade package enables the user to perform synchronous upgrade. A user terminal, comprising: a startup module, configured to start a loader; an acquisition module, configured to acquire a running environment parameter of the software to be upgraded by the user end; and a calling module, configured to invoke the loader to The server corresponding to the loader sends an upgrade request carrying the operating environment parameter; a receiving module is configured to invoke the loader to receive an upgrade response sent by the server to respond to the upgrade request, where the upgrade response carries the The client software upgrade package matching the running environment parameter, the upgrade request is further used to trigger the server, so that the server uses the server software upgrade package with the same version of the client software upgrade package to perform the corresponding software upgrade; An upgrade module is configured to upgrade the software to be upgraded by using the client software upgrade package. The client according to claim 6, wherein the client further includes a loader acquisition module and a loader update module; Wherein the loader acquisition module is used by the client to obtain the current version of the loader; and wherein the loader update module is configured to use the latest version of the loader when the current version of the loader is lower than the latest version of the loader The latest version of the loader updates the loader. A server includes: a calling module, configured to receive, by a 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 user; Sending an upgrade response to the client to the upgrade request, the upgrade response carrying the client software upgrade package matching the running environment parameter; and an upgrade module for being triggered by the upgrade request to utilize The client software upgrade package with the same version of the client software upgrade package performs the corresponding software upgrade. The server of claim 8, further comprising: a binding module, configured to bind the client software upgrade package to the server software upgrade package. The server of claim 8, further comprising: 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 server to the client The second client software upgrade package with the same version of the second server software upgrade package enables the user to perform synchronous upgrade.