Terminal automatic upgrading software and operation method

Abstract

The invention relates to the field of terminal automatic upgrading, and provides terminal automatic upgrading software and an operation method, and is characterized in that the terminal automatic upgrading software comprises a server version installed at a server and a terminal version installed at a point-of-sale terminal; the server version at least comprises a point-of-sale terminal management background and an upgrade package creation program; when the server receives an upgrading operation of a user, the upgrading package creation program creates an upgrading package, and the sales terminal management background generates an upgrading task and issues the upgrading task to each sales terminal; and when the sales terminal receives the upgrading task, automatic upgrading is started. The terminal automatic upgrading software provided by the invention is controlled by the server to send the upgrading task with the upgrading related tool to each to-be-upgraded sales terminal, and the sales terminal can automatically complete upgrading according to the upgrading task and the tool issued by the server only by starting the sales terminal by a worker of a service station; the upgrading of the sales terminal is improved, and the personnel investment in the aspect of upgrading is reduced.

Description

Technical Field

[0001] The present disclosure relates to the technical field of terminal automatic upgrade, and in particular to terminal automatic upgrade software and an operation method. Background Art

[0002] Generally, users go to the service station to make purchases by themselves, and the staff of the service station uses the equipment to complete the purchase for the users. The equipment that provides purchase and ticket issuance is temporarily called a sales terminal. During use, the sales terminal also needs to be continuously upgraded according to the improvement of the seller. At this stage, the upgrade has realized the functions of task management, download reporting, terminal upgrade, etc. that support the iterative update of traditional terminal versions. However, due to the lack of fault tolerance of the software itself, it is easy to encounter various upgrade failures, environmental damage, and unstable system operation during the upgrade process. If manual upgrades are used every time, it will consume a lot of manpower and material resources. Therefore, how to reduce personnel participation and improve the efficiency of sales terminal version upgrades has become an urgent problem to be solved. Summary of the invention

[0003] In view of this, the embodiments of the present disclosure provide a terminal automatic upgrade software and an operation method to solve the problem in the prior art of how to reduce personnel participation and improve the efficiency of sales terminal version upgrades.

[0004] According to a first aspect of the disclosed embodiments, a terminal automation upgrade software is provided, characterized in that the terminal automation upgrade software comprises: a server version installed on a server and a terminal version installed on a sales terminal; the server version comprises at least: a sales terminal management background and an upgrade package creation program; the terminal version comprises at least: a traditional terminal program, a launcher program, and an upgrade installation program; when the server receives an upgrade operation from a user, the upgrade package creation program creates an upgrade package, and the sales terminal management background generates an upgrade task and publishes it to each sales terminal; when the sales terminal receives the upgrade task and waits to be started, automatic upgrade is enabled when it is started.

[0005] In some optional implementation methods of some embodiments, the above-mentioned sales terminal management background is used to manage terminal devices, including at least the following functions: determining terminal upgrade strategies, issuing terminal tasks, and managing upgrade exception device information; the above-mentioned upgrade package creation program is used to create upgrade package files, including at least the following functions: calculating difference files, generating terminal upgrade verification rule files, and adding custom extension scripts; the above-mentioned traditional terminal program is used to support various services of sales terminals with terminal versions installed, and issue upgrade commands to the above-mentioned launcher program to initiate the upgrade function; the above-mentioned launcher program is used for directory switching, upgrade backup, and starting other programs; the above-mentioned upgrade installation program is used to obtain upgrade tasks, download upgrade packages, decompress and install upgrade packages, support upgrading custom extension scripts, and report exceptions.

[0006] A second aspect of the disclosed embodiments provides a method for running terminal automated upgrade software, which is characterized by comprising: when a server receives an upgrade operation from a user, the server starts an upgrade package creation program; after starting, an installation package and an upgrade extension script are selected in the upgrade package creation program to complete the creation of the upgrade package; logging into the sales terminal management background to create an upgrade task; publishing the upgrade task through the sales terminal management background; the sales terminal that receives the upgrade task is automatically upgraded, and the upgrade is completed.

[0007] In some optional implementations of some embodiments, the above-mentioned logging into the sales terminal management background to create an upgrade task includes: logging into the sales terminal management background to create a basic upgrade task; determining the terminal upgrade strategy through the above-mentioned sales terminal management background; uploading the above-mentioned upgrade package to the above-mentioned sales terminal management background; and confirming that the creation of the upgrade task is successful based on the completion of the basic upgrade task creation, determination of the terminal upgrade strategy, and completion of the upload of the above-mentioned upgrade package.

[0008] In some optional implementations of some embodiments, the above-mentioned upgrade task is released through the above-mentioned sales terminal management background, including: when the upgrade task is successfully created, the above-mentioned upgrade task is released to each sales terminal with a terminal version of the terminal automation upgrade software installed through the above-mentioned sales terminal management background, and wait for the sales terminal to start.

[0009] In some optional implementation methods of some embodiments, the sales terminal that receives the above-mentioned upgrade task is automatically upgraded, and the upgrade is completed, including: when the sales terminal that receives the above-mentioned upgrade task is started, the traditional terminal program initiates a startup command to the launcher program to control the startup of the upgrade installation program; downloads the above-mentioned upgrade package through the local upgrade installation program; and decompresses and installs the above-mentioned upgrade package.

[0010] In some optional implementations of some embodiments, the above method also includes: re-logging into the above sales terminal management background to view the management upgrade exception device information; determining whether there is upgrade exception device information registered for the abnormal report of this upgrade; if not, determining that the upgrade is successful; if so, determining that there is a sales terminal that failed to upgrade.

[0011] In some optional implementations of some embodiments, after determining whether there is any upgrade abnormality device information registered for abnormal reporting of this upgrade, the method further includes: restarting the sales terminal that has not reported the upgrade abnormality device information.

[0012] In some optional implementations of some embodiments, if the above exists, after determining that there is a sales terminal that failed to upgrade, the above method also includes: downloading the log information of the sales terminal corresponding to the above-mentioned upgrade abnormal device information, and determining the upgrade failure problem based on the above-mentioned log information; based on the above-mentioned upgrade failure problem, matching the upgrade plan.

[0013] Compared with the prior art, the embodiments of the present disclosure have the following beneficial effects: the terminal automation upgrade software provided by the present disclosure includes: a server version installed on the server and a terminal version installed on the sales terminal; the server version at least includes: a sales terminal management background and an upgrade package creation program; the terminal version at least includes: a traditional terminal program, a launcher program, and an upgrade installation program; when the server receives the user's upgrade operation, the upgrade package creation program creates an upgrade package, and the sales terminal management background generates an upgrade task and publishes it to each sales terminal; when the sales terminal receives the upgrade task waiting to be started, the automatic upgrade is turned on when it is started. The terminal automation upgrade software provided by the present disclosure is controlled by the server to send an upgrade task with upgrade-related tools (such as an upgrade package) to each sales terminal to be upgraded. The staff of the service station only needs to start the sales terminal, and the sales terminal can complete the upgrade (version update) by itself according to the upgrade task and tools issued by the server, thereby improving the upgrade efficiency of the sales terminal. There is no need for personnel to perform specific operations in the upgrade process, thereby reducing the personnel investment in the upgrade. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0015] Figure 1 is a schematic diagram of the structure and function of terminal automatic upgrade software according to some embodiments of the present disclosure;

[0016] Figure 2 is a flow chart of a method for running terminal automatic upgrade software according to some embodiments of the present disclosure;

[0017] Figure 3 It is a schematic diagram of a sales terminal upgrade process according to a terminal automation upgrade software operation method of some embodiments of the present disclosure. DETAILED DESCRIPTION

[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0019] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0020] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0021] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0022] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0023] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0024] Figure 1 FIG. 1 is a schematic diagram of the structure and function of terminal automatic upgrade software according to some embodiments of the present disclosure. Figure 1 As shown, the terminal automation upgrade software 101 includes: a server version 102 installed on the server and a terminal version 103 installed on the sales terminal. The above-mentioned server version 102 includes at least: a sales terminal management background 104 and an upgrade package creation program 105. The above-mentioned terminal version 103 includes at least: a traditional terminal program 106, a launcher program 107, and an upgrade installation program 108. When the server receives the user's upgrade operation, the upgrade package creation program 105 creates an upgrade package, and the above-mentioned sales terminal management background 104 generates an upgrade task and publishes it to each sales terminal. When the sales terminal receives the above-mentioned upgrade task and waits to be started, automatic upgrade is enabled when it is started. It is worth noting that the server version not only includes the sales terminal management background and the upgrade package creation program, but also includes other programs. Here, only the inconsistencies with the terminal version are introduced.

[0025] In some optional implementations of some embodiments, the above-mentioned sales terminal management background 104 is used to manage terminal devices, including at least the following functions: determining terminal upgrade strategies 1041, publishing terminal tasks 1042, and managing upgrade exception device information 1043; the above-mentioned upgrade package creation program 105 is used to create upgrade package files, including at least the following functions: calculating difference files 1051, generating terminal upgrade verification rule files 1052, and adding custom extension scripts 1053; the above-mentioned traditional terminal program 106 is used to support various businesses of sales terminals with terminal versions installed, and issue upgrade commands 106 to the above-mentioned launcher program to initiate the upgrade function; the above-mentioned launcher program 107 is used for directory switching 1071, upgrade backup 1072, and starting other programs 1073; the above-mentioned upgrade installation program 108 is used to obtain upgrade tasks 1081, download upgrade packages 1082, decompress and install upgrade packages 1083, support upgrade custom extension scripts 1084, and report exceptions 1085.

[0026] Compared with the prior art, the disclosed embodiment has the following beneficial effects: the terminal automatic upgrade software provided by the disclosed embodiment is controlled by the server to send the upgrade task with the upgrade-related tools (such as upgrade packages) to each sales terminal to be upgraded. The staff of the service station only needs to start the sales terminal, and the sales terminal can complete the upgrade (version update) by itself according to the upgrade task and tools issued by the server, thereby improving the upgrade efficiency of the sales terminal. There is no need for personnel to perform specific operations in the upgrade process, thereby reducing the personnel investment in the upgrade.

[0027] It should be understood that Figure 1 The number of sales terminals in the description is only illustrative. Any number of sales terminals may be provided according to implementation requirements.

[0028] Figure 2 It is a flowchart of a terminal automatic upgrade software operation method according to some embodiments of the present disclosure. Figure 2 The terminal automatic upgrade software operation method is as follows: Figure 1 The terminal automatic upgrade software is executed.

[0029] like Figure 2 As shown, the terminal automatic upgrade software operation method includes the following steps:

[0030] Step S201: When the server receives an upgrade operation from the user, the server starts an upgrade package creation program.

[0031] In some embodiments, the execution subject of the terminal automatic upgrade software operation method (such as Figure 1The terminal automation upgrade software 101 shown can start the upgrade package creation program after receiving the upgrade operation of the server administrator at the server. Here, the user's upgrade operation can be understood as the user's instruction upgrade operation performed on the terminal device installed with the server version of the terminal automation upgrade software.

[0032] Step S202, after startup, select the installation package and the upgrade extension script in the above upgrade package creation program to complete the upgrade package creation.

[0033] In some embodiments, after startup, the above-mentioned execution subject can select the installation package and upgrade extension script used for this upgrade in the above-mentioned upgrade package creation program, and when the operation is completed, it is determined that the upgrade package creation has been completed. Here, the installation package is compiled and generated by Jenkins, including all dependent libraries and driver installations, and the upgrade package is the upgrade package obtained by incrementally comparing the installation package at the last upgrade (the old installation package that is running) with the installation package (new installation package) of this upgrade. The above-mentioned upgrade extension script includes a pre-upgrade script and a post-upgrade script. The pre-upgrade script is mainly used for pre-processing-environment cleaning, such as cleaning the hard disk and deleting error files. The post-upgrade script is mainly used for post-upgrade configuration, and the configuration before the upgrade can be replaced with a new configuration. It also supports upgrading custom extension scripts. Creating an upgrade package through an upgrade package creation program can avoid the error problem caused by manual extraction during the incremental upgrade package, which provides important protection for the upgrade work. In addition, the created upgrade package also includes identity authentication information (fingerprint information), which is used for the sales terminal to confirm whether it is an upgrade initiated by the service-side manager.

[0034] Step S203, log in to the sales terminal management backend to create an upgrade task.

[0035] In some embodiments, the above-mentioned execution subject can log in to the above-mentioned sales terminal management background and create a basic upgrade task. Here, the basic upgrade task can be understood as a primary upgrade task framework. Then, the above-mentioned execution subject can select and determine the terminal upgrade strategy through the above-mentioned sales terminal management background. There are terminal upgrade policies related to upgrades in the sales terminal management background, such as upgrading the sales terminals in a certain area to a certain version number, upgrading all sales terminals, or upgrading which version number. The above-mentioned execution subject can determine which terminal upgrade strategy to adopt according to the needs of this upgrade. Afterwards, the above-mentioned execution subject can upload the above-mentioned upgrade package to the above-mentioned sales terminal management background. Finally, after the basic upgrade task is created, the terminal upgrade strategy has been selected and the upgrade package has been uploaded, and it can be confirmed that the creation of this upgrade task is successful.

[0036] Step S204: issuing the upgrade task through the sales terminal management backend.

[0037] In some embodiments, when the upgrade task is successfully created, the execution subject can publish the upgrade task to each sales terminal with the terminal version of the terminal automation upgrade software installed through the sales terminal management background, and wait for the sales terminal to start. Here, the release of the upgrade task is targeted. For some old devices that are older, the current new program can no longer run, so the automatic upgrade is only for the sales terminal that has installed the terminal version of the terminal automation upgrade software.

[0038] Step S205: the sales terminal that receives the upgrade task automatically upgrades, and the upgrade is completed.

[0039] In some embodiments, when the execution subject completes steps S201 to S204, it waits for the sales terminal to complete the following execution operations and then confirms that the automatic upgrade is completed. Specifically, when the sales terminal that receives the upgrade task is started, for one of the started sales terminals: the traditional terminal program of the sales terminal sends a startup command to the launcher program to control the startup of the upgrade installation program; after the upgrade installation program is started, it can download the attached upgrade package from the upgrade task; when the upgrade package is downloaded, the upgrade installation program can decompress and install the upgrade package.

[0040] In some optional implementations of some embodiments, the method further includes: the execution subject re-logs into the sales terminal management background to view the management upgrade abnormal device information; determines whether there is abnormal upgrade device information registered for this upgrade; if not, the execution subject can determine that the upgrade is successful; if so, the execution subject can determine that there is a sales terminal that failed to upgrade. Here, when the sales terminal upgrade is completed, the version number of the upgraded version is uploaded to the sales terminal management background. The execution subject can compare the version number uploaded by the sales terminal with the version number in the terminal upgrade policy of this upgrade. If they are consistent, the execution subject can determine that the sales terminal has been successfully upgraded. In addition, if the version number comparison is inconsistent, the execution subject can determine that the sales terminal has failed to upgrade, and re-issue the upgrade task to the sales terminal for upgrading. The sales terminal management background can view the upgrade status of the sales terminal in real time, and can remotely check the abnormalities reported by the terminal device that failed to upgrade.

[0041] In some optional implementations of some embodiments, the above method also includes: the sales terminal that has not reported the upgrade abnormal device information is restarted, and the upgrade is confirmed to be completed and ready for use.

[0042] In some optional implementations of some embodiments, if the above exists, after determining that there is a sales terminal that has failed to upgrade, the above method also includes: the above execution subject can download the log information of the sales terminal corresponding to the above upgrade abnormal device information; then, the above execution subject can determine the upgrade failure problem based on the above log information; finally, the above execution subject can generate an upgrade plan based on the above upgrade failure problem to re-upgrade the sales terminal. Here, the upgrade failure problem can be loss during data transmission, version mismatch, incompatibility, or hardware damage that cannot be upgraded. Specifically, the upgrade failure problem is determined based on the log information, and the upgrade plan is matched according to the upgrade failure problem. For example, the upgrade plan corresponding to data loss during transmission can be retransmission or transmission in other ways, the system problem can be re-system, and the upgrade plan for hardware damage that cannot be upgraded can be displayed on the display of the server or generate reporting information to be transmitted to the mobile device of the server administrator.

[0043] Compared with the prior art, the disclosed embodiment has the following beneficial effects: first, when the server receives the user's upgrade operation, the server starts the upgrade package creation program; then, after startup, the upgrade package and upgrade extension script are determined in the upgrade package creation program to complete the upgrade package creation; then, the sales terminal management background is logged in to create an upgrade task; then, the upgrade task is released through the sales terminal management background; finally, the sales terminal that receives the upgrade task is automatically upgraded, and the upgrade is completed. Through the collaborative operation of multiple programs, the upgrade, backup, and abnormal reporting of the sales terminal are completed to keep the software of the sales terminal running safely and stably, and to ensure the normal operation of the sales business.

[0044] Figure 3 FIG. 1 is a schematic diagram of a sales terminal upgrade process according to a terminal automation upgrade software operation method of some embodiments of the present disclosure. Figure 3 As shown in the figure, the automatic upgrade process of the sales terminal in actual application is as follows:

[0045] The first step is that after the user starts the sales terminal, the launcher program is run. At this time, process communication is started, directory management is run, and auxiliary programs are started. The operation of the sales terminal is started and monitored to confirm that the sales terminal has been successfully started. Here, the user can be understood as the management staff of the sales terminal. After the user starts the sales terminal, the launcher program starts and runs by default and starts other auxiliary programs.

[0046] In the second step, when the user enters the user name and password to log in to the sales terminal, the sales terminal management backend service interface can perform login verification. If the verification is successful, the login is successful. Here, the sales terminal management backend service interface is an external interface provided by the server for the front-end service. If the verification fails, the interface rejects the upgrade request. After successful login, the sales terminal initiates an upgrade query message, which can be understood as each successful startup and login of the sales terminal will query whether there is an upgrade task issued by the server. The upgrade query message includes terminal installation authentication parameter information. Optionally, it can be displayed here after the last upgrade, abnormalities found during operation, and abnormal information recorded for pop-up prompts. If there is no abnormality after the last upgrade, no pop-up prompts will be generated. When the upgrade task is queried, the upgrade installation program is started and the terminal security authentication parameter information is forwarded, and the upgrade package is downloaded for decompression and installation. The download of the upgrade package supports file breakpoint continuation. The terminal installation authentication parameter information is used as a verification of the upgrade environment. After downloading, it is verified by the national secret algorithm. The terminal installation authentication parameter information includes fingerprint information, which can be verified with the fingerprint information saved locally to confirm whether to upgrade. During the decompression and installation process, you can verify the version information and determine whether the software environment is normal. If the verification fails, the upgrade will not be performed to prevent local files from being tampered with or missing, ensuring upgrade safety.

[0047] The third step is to report any abnormalities detected during the decompression / installation process. Specifically, the launcher monitors the sales terminal for abnormalities in the upgrade and installation, and reports the abnormal information after the upgrade. When the abnormal operation is rolled back, the management staff of the sales terminal needs to provide the rollback verification code for the local area. Monitoring abnormalities and reporting them in a timely manner solves the problem of being unable to roll back when the upgrade fails due to upgrade environment problems or library problems during the upgrade process, saving time to determine upgrade failures, helping to remotely troubleshoot upgrade problems, and improving the efficiency of upgrade work.

[0048] The fourth step is to re-query the upgrade task and download the upgrade package after the exception is reported. Here, it is a verification upgrade to prevent the upgrade failure caused by download problems after the exception is reported. If the upgrade fails, wait for the server to issue a new upgrade plan or the management staff of the sales terminal to handle it.

[0049] Step 5: After re-downloading the upgrade package, copy the running directory, decompress the upgrade package, and verify the installation of the upgrade package. When the installation is successful, the restart interface is displayed to prompt the management staff of the user's sales terminal to restart the sales terminal.

[0050] In some optional implementations of some embodiments, it also includes: the sales terminal runs a launcher program to start process communication. Execute running directory management, find the upgrade directory, back up the current running directory, enable the upgrade directory, start the sales terminal auxiliary program, and finally start and monitor the running status of the sales terminal, and the sales terminal runs normally. The main function here is the backup function for this upgrade. If there is an abnormal operation, it can be automatically re-upgraded. When the sales terminal runs abnormally after the upgrade, the user can be prompted for the abnormal situation. When the user chooses to back up and restart the sales terminal, the running directory is switched to the backup directory, and the upgrade abnormal event is recorded. Here, the sales device is restarted, the launcher program starts the upgrade installation program and forwards the upgrade abnormal event. The upgrade installation program reports the upgrade abnormality and waits for the server to issue a new upgrade plan or the management staff of the sales terminal to handle it.

[0051] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0052] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0053] The units described in some embodiments of the present disclosure may be implemented by software or hardware, and the described units may also be set in a processor.

[0054] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0055] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above invention concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure.

Claims

1. A terminal automatic upgrade software, characterized in that: The terminal automation upgrade software includes: A server version installed on the server and a terminal version installed on the sales terminal; the server version at least includes: a sales terminal management background and an upgrade package creation program; the terminal version at least includes: a traditional terminal program, a launcher program, and an upgrade installation program; When the server receives the user's upgrade operation, the upgrade package creation program creates an upgrade package, and the sales terminal management background generates an upgrade task and publishes it to each sales terminal; When the sales terminal receives the upgrade task waiting to be started, the automatic upgrade is started when it is started.

2. A terminal automatic upgrade software according to claim 1, characterized in that: The sales terminal management backend is used to manage terminal devices, including at least the following functions: determining terminal upgrade strategies, issuing terminal tasks, and managing upgrade abnormal device information; The upgrade package creation program is used to create an upgrade package file, including at least the following functions: calculating difference files, generating terminal upgrade verification rule files, and adding custom extension scripts; the traditional terminal program is used to support various services of the sales terminal installed with the terminal version, and to issue an upgrade command to the launcher program to initiate the upgrade function; the launcher program is used for directory switching, upgrade backup, and starting other programs; The upgrade installation program is used to obtain upgrade tasks, download upgrade packages, decompress and install upgrade packages, support upgrading custom extension scripts, and report exceptions.

3. A terminal automatic upgrade software operation method according to claim 1, characterized in that: include: When the server receives the user's upgrade operation, the server starts the upgrade package creation program; After startup, select the installation package and upgrade extension script in the upgrade package creation program to complete the upgrade package creation; Log in to the sales terminal management backend to create an upgrade task; Publishing the upgrade task through the sales terminal management backend; The sales terminal that receives the upgrade task automatically upgrades, and the upgrade is completed.

4. A terminal automatic upgrade software operation method as claimed in claim 3, characterized in that: The step of logging into the sales terminal management backend to create an upgrade task includes: Log in to the sales terminal management backend to create basic upgrade tasks; Determine the terminal upgrade strategy through the sales terminal management background; Upload the upgrade package to the sales terminal management backend; According to the completion of the creation of the basic upgrade task, the determination of the terminal upgrade strategy, and the completion of uploading the upgrade package, it is confirmed that the creation of the upgrade task is successful.

5. A terminal automatic upgrade software operation method as claimed in claim 3, characterized in that: The issuing of the upgrade task through the sales terminal management backend includes: When the upgrade task is successfully created, the upgrade task is published to each sales terminal with a terminal version of the terminal automation upgrade software installed through the sales terminal management background, waiting for the sales terminal to start.

6. A terminal automatic upgrade software operation method as claimed in claim 5, characterized in that: The sales terminal receiving the upgrade task automatically upgrades, and the upgrade is completed, including: When the sales terminal receiving the upgrade task is started, the traditional terminal program sends a startup command to the launcher program to control the startup of the upgrade installation program; Download the upgrade package through the local upgrade installation program; Decompress and install the upgrade package.

7. A terminal automatic upgrade software operation method as claimed in claim 3, characterized in that: The method further comprises: Log in to the sales terminal management backend again to check the device information with abnormal management upgrade; Determine whether there is any upgrade abnormal device information registered for the abnormal report of this upgrade; If it does not exist, it is determined that the upgrade is successful; If so, it is determined that there is a sales terminal that has failed to upgrade.

8. A terminal automatic upgrade software operation method as claimed in claim 7, characterized in that: After determining whether there is upgrade abnormal device information registered for abnormal reporting of this upgrade, the method further includes: The sales terminals that did not report the abnormal device information for upgrade were restarted.

9. A terminal automatic upgrade software operation method as claimed in claim 7, characterized in that: If so, after determining that there is a sales terminal that has failed to upgrade, the method further includes: Download the log information of the sales terminal corresponding to the upgrade abnormal device information, Determine the upgrade failure problem based on the log information; Based on the upgrade failure problem, an upgrade solution is matched.

Images