Payment equipment upgrading task distribution method, upgrading method and electronic equipment

Abstract

The invention relates to the technical field of remote upgrading, in particular to a payment equipment upgrading task distribution method, an upgrading method and electronic equipment. A payment device upgrade task allocation method is applied to a cloud server, the cloud server is connected with a payment device, the payment device is further connected with a node server, and the cloud server is connected with the node server, and the method comprises the steps of obtaining an upgrade request of the payment device; before the payment equipment is upgraded, acquiring historical pressure conditions of all node servers and current pressure conditions of the node servers; wherein the historical pressure condition and the current pressure condition are associated with the number of payment devices connected with the node server; determining an execution node server from all the node servers based on the historical pressure condition and the current pressure condition; and allocating an upgrading task corresponding to the upgrading request to an execution node server for execution.

Description

Technical Field

[0001] This invention relates to the field of remote upgrade technology, specifically to a method for allocating upgrade tasks for payment devices, an upgrade method, and an electronic device. Background Technology

[0002] In related technologies, POS (Point of Sales) terminal upgrade solutions often download upgrade packages from fixed upgrade server addresses, which leads to problems such as uneven load distribution, poor disaster recovery, low resource utilization, and security risks. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a method for allocating upgrade tasks for payment devices, so as to realize the dynamic and intelligent allocation of upgrade tasks among multiple service nodes.

[0004] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: A method for allocating upgrade tasks for payment devices, applied to a cloud server, wherein the cloud server is connected to a payment device, the payment device is also connected to a node server, and the cloud server is connected to the node server, the method comprising: Obtain an upgrade request for the payment device; Before the payment device is upgraded, the historical load information and current load information of all the node servers are obtained; wherein the historical load information and current load information are related to the number of payment devices connected to the node server. Based on the historical and current pressure conditions, the execution node server is determined from all the node servers. The upgrade task corresponding to the upgrade request is assigned to the execution node server for execution.

[0005] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows: A method for upgrading a payment device, applied to a payment device connected to a node server and a cloud server, wherein the node server is also connected to the cloud server, the method comprising: The address allocation table is received from the cloud server, and the execution node server in the address allocation table is obtained through the payment device upgrade task allocation method described above. Get the node switching strategy; Send an upgrade task polling request to the execution node server; Receive the response information corresponding to the polling request; if the response information contains an upgrade task, send a request to download the upgrade package to the execution node server. Determine the availability of the execution node server; if it is unavailable, determine another execution node server in the address allocation table according to the node switching strategy. Using the other execution node server as the new round of execution node server, the step of sending the upgrade task polling request to the execution node server is executed.

[0006] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows: A payment device upgrade method is applied to a node server, wherein the node server is connected to the payment device and a cloud server, and the payment device is also connected to the cloud server. The method includes: The payment device obtains a polling request and sends the polling request to the execution node server obtained in the above-described payment device upgrade task allocation method. Obtain the upgrade task corresponding to the polling request and send a response message to the payment device; Request to download upgrade package; Match the corresponding upgrade data based on the download upgrade package request; The upgrade data is sent to the payment device through a secure channel.

[0007] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows: An electronic device includes a memory and a processor, the memory storing a computer program, characterized in that, when the processor executes the computer program, it implements the steps of the above-described payment device upgrade task allocation method or the steps of the above-described payment device upgrade method.

[0008] The beneficial effects of this invention are as follows: This application addresses the problem in related technologies where the allocation of upgrade tasks for payment devices does not adequately consider the load of node servers, easily leading to uneven allocation and affecting upgrade efficiency. It proposes a new method for allocating upgrade tasks for payment devices. This method first obtains the upgrade request from the payment device and, before upgrading, comprehensively acquires the historical and current load conditions of all node servers, where the load condition is correlated with the number of connected payment devices. Then, based on the historical and current load conditions, it determines the execution node server from all node servers. Finally, it sends the execution node server information to the payment device to instruct it to request an upgrade. The historical load conditions reflect the long-term load capacity and stability of the server, while the current load conditions provide real-time load awareness. This dual load assessment mechanism ensures that the selected execution node servers have relatively balanced loads and appropriate processing capabilities, thereby achieving reasonable allocation of upgrade tasks, effectively avoiding single-point overload, and improving upgrade success rate and security. Attached Figure Description

[0009] Figure 1 A flowchart illustrating the steps of a payment device upgrade task allocation method provided in an embodiment of the present invention; Figure 2 This is a flowchart illustrating the steps of a payment device upgrade method applied to a payment device, as provided in an embodiment of the present invention. Figure 3 This is a flowchart illustrating the steps of a payment device upgrade method applied to a node server, as provided in an embodiment of the present invention. Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention; Figure 5 This is a timing diagram of a payment device upgrade task allocation method provided in an embodiment of the present invention. Detailed Implementation

[0010] To make the technical problems, technical solutions, and beneficial effects to be solved by this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this application.

[0011] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0012] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0013] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0014] In related technologies, when POS terminals undergo software upgrades, they typically download upgrade packages from a fixed upgrade server address or directly poll the upgrade task via polling. This existing technology suffers from the following technical contradictions: Firstly, the upgrade load cannot be balanced; when a large number of terminals simultaneously initiate polling or upgrade requests, some service nodes are prone to overload due to concentrated requests. Secondly, the system's disaster recovery capability is insufficient; when a node fails, the terminal cannot automatically switch to a backup upgrade entry point, potentially causing upgrade interruptions. The root cause of these contradictions lies in the fact that existing upgrade strategies, employing fixed allocation or real-time polling mechanisms, cannot dynamically allocate upgrade tasks based on the real-time load capacity of each node, resulting in low resource utilization. Furthermore, the fixed upgrade entry address poses a security risk if it is tampered with or hijacked during transmission, leading to the injection of forged upgrade packages. Therefore, it is necessary to introduce a pre-scheduling mechanism before the terminal executes the upgrade to rationally allocate upgrade nodes and entry points, achieve balanced load distribution, support rapid disaster recovery in case of failure, and ensure the security and controllability of the upgrade process.

[0015] To address the aforementioned problems, this application provides a method for allocating tasks for payment device upgrades. The following is a detailed description of this method.

[0016] The following describes in detail a payment device upgrade task allocation method of the present invention. This method is applied to a cloud server, the cloud server is connected to a payment device, the payment device is also connected to a node server, and the cloud server is connected to the node server. See attached figure. Figure 1 This includes steps 110 to 140.

[0017] Step 110: Obtain an upgrade request for the payment device; where the payment device includes payment terminals such as POS terminals and cash registers.

[0018] Step 120: Before upgrading the payment devices, obtain the historical and current load information of all node servers; the historical and current load information is related to the number of payment devices connected to the node servers. Step 130: Based on historical and current load conditions, determine the execution node server from all node servers; Step 140: Assign the upgrade task corresponding to the upgrade request to the execution node server for execution; As described above, this embodiment first obtains the upgrade request from the payment device, and before the upgrade, comprehensively obtains the historical and current load conditions of all node servers, where the load condition is related to the number of connected payment devices. Then, based on the historical and current load conditions, it determines the execution node server from all node servers. Finally, it sends the execution node server information to the payment device to instruct it to request an upgrade. Historical load conditions reflect the long-term load capacity and stability of the server, while current load conditions allow for real-time load assessment. This dual load judgment mechanism ensures that the selected execution node server has a relatively balanced load and suitable processing capacity, thereby achieving a reasonable allocation of upgrade tasks, effectively avoiding single-point overload, and improving the upgrade success rate and security.

[0019] In one embodiment of this application, step 120, prior to the payment device upgrade, further includes: Step 210: Collect node attributes of all node servers at preset time intervals to assess node stress. Specifically, the cloud server creates a pre-scheduling service (ALLOC service) to collect data, including node attributes such as CPU utilization, bandwidth usage, concurrent requests, and upgrade success rate of the node server.

[0020] Step 220: Save the node stress information to the historical stress information database; in addition to saving the node server's CPU utilization, bandwidth usage, concurrent requests and upgrade success rate as a record to the historical stress information database, this record also stores the node server's region and the corresponding time.

[0021] Specifically, by periodically collecting and storing the node pressure data of the node servers, a historical pressure database was built, which can quantitatively reflect the real-time load status and changing trends of each node.

[0022] As described above, this embodiment collects node stress data at intervals and saves it to a historical stress database. This allows payment device upgrades to allocate nodes based on their stress levels. Thus, this embodiment provides a node allocation basis for payment device upgrades based on historical stress data, enabling upgrade tasks to be prioritized for execution on nodes with lower loads. This balances system resource utilization, avoids exacerbating performance pressure on high-load nodes due to upgrade operations, and improves the reliability and efficiency of the upgrade process.

[0023] In one embodiment of this application, step 130, determining the execution node server from all node servers based on historical and current load conditions, includes: Step 310: Analyze historical and current pressure conditions to obtain pressure analysis results; Step 320: Based on the stress analysis results and the terminal characteristics of the payment device, query the intermediate node server from all node servers; where terminal characteristics include the terminal model, the merchant type of the terminal, and the terminal upgrade history; Step 330: Obtain the address allocation table from the intermediate node server. The address allocation table corresponds one-to-one with the payment device. The address allocation table includes the stress analysis results of the intermediate node server, the connection information of the intermediate node server, and the corresponding digital signature. Among them, the connection information refers to IP address information (Internet Protocol Address) and geographical information. The digital signature is used for security verification.

[0024] Step 340: Determine the execution node server based on the address allocation table; As described above, this embodiment, by comprehensively analyzing historical and current load conditions and combining them with terminal characteristics, queries suitable intermediate node servers from all node servers. Then, based on these intermediate node servers, it generates an address allocation table containing digital signatures. This accurately assesses node load capacity and terminal compatibility requirements. Therefore, this embodiment achieves intelligent selection of execution node servers, ensuring that upgrade tasks are assigned to nodes with appropriate loads. Furthermore, it improves the targeting and success rate of upgrades through terminal characteristic matching. The addition of digital signatures ensures the authenticity of node identities and the integrity of data transmission, guaranteeing the secure and stable successful execution of every upgrade task.

[0025] In one embodiment of this application, determining the execution node server based on the address allocation table further includes: Step 410: Determine whether there is a secure node server with an established bidirectional secure channel between the node server in the address allocation table and the cloud server. If so, select the secure node server as the execution node server. Step 140, which assigns the upgrade task corresponding to the upgrade request to the execution node server for execution, also includes: assigning the upgrade task corresponding to the upgrade request to the execution node server for execution through a secure channel; As described above, this embodiment enhances security protection during the upgrade data transmission process, effectively preventing data tampering and unauthorized access, while prioritizing existing secure channels for upgrade task allocation. This reduces the overhead of establishing new connections and improves the efficiency and reliability of upgrade task allocation.

[0026] In one embodiment of this application, it further includes: Step 510: Calculate the hash value of the address allocation table; wherein, the algorithms for calculating the hash value include MD5 and SHA-256.

[0027] Step 520: Obtain the pre-set private key and use it to encrypt the hash value to obtain a digital signature; specifically, retrieve the pre-deployed private key from the secure storage medium of the cloud server. The private key is the confidential part of an asymmetric key pair. Call the signature function (such as RSA_private_encrypt or ECDSA_sign) of the corresponding cryptographic library (such as OpenSSL), taking the hash value as input, and the output is the unique digital signature.

[0028] Step 530: Send the address allocation table and digital signature to the payment device, so that the payment device, after successfully verifying the digital signature, requests the execution node server in the address allocation table to execute the upgrade request.

[0029] As described above, this embodiment prevents the address allocation table from being tampered with during transmission, ensuring that the node server information obtained by the payment device is accurate and reliable. At the same time, it realizes the identity authentication of the cloud server through the digital signature mechanism, thereby improving the security of the entire upgrade process.

[0030] In one embodiment of this application, step 340, determining the execution node server according to the address allocation table, includes: Step 610: Obtain the first geographical region and stress analysis results for each node server in the address allocation table; Step 620: Obtain the second geographic region of the payment device; specifically, obtain the satellite positioning location of the payment device. For example, if the satellite positioning location of the payment device is China, then its second geographic region is China.

[0031] Step 630: Determine the execution node server based on the stress analysis results. If the number of execution node servers exceeds one, match the nearest target first geographical region based on the second geographical region, and use the execution node server corresponding to the target first geographical region as the target execution node server. For example, when there are two execution node servers, their geographical regions are China and Europe, and the geographical region of the payment device is China, then the execution node server with the geographical region of China will be preferentially matched as the target execution node server.

[0032] In step 530, instructing the payment device to request the execution node server in the address allocation table to perform the task further includes: instructing the payment device to request the target execution node server in the address allocation table to perform the task; As described above, this embodiment achieves the synergistic effect of load balancing and network latency optimization, which not only avoids the risk of overloading a single node, but also reduces data transmission latency through geographical proximity, thereby improving the execution efficiency of the upgrade task and the end-user experience.

[0033] In one embodiment of this application, it further includes: Step 710: When the upgrade task assignment fails, a second execution node server will be reselected from all node servers based on historical and current pressure conditions and according to a switching strategy that includes geographical region, network latency, and security level. For example, nodes that are geographically located in the same geographical region as the payment device, have a network latency of less than 30ms, and have established a secure channel will be given priority as the second execution node server.

[0034] As described above, this embodiment achieves dynamic fault tolerance and load optimization when upgrade task allocation fails by reselecting the second execution node server based on historical and real-time stress data and a switching strategy that includes geographical region, network latency, and security level. Thus, this embodiment not only ensures the reliability of node selection through multi-dimensional index evaluation, but also adapts to changes in the network environment using real-time data, thereby effectively reducing task interruption time and improving system service continuity. At the same time, it reduces transmission latency through geographical region matching and ensures communication security through security level screening, comprehensively improving the robustness and execution efficiency of the upgrade process.

[0035] This invention also provides a payment device upgrade method applied to payment devices, wherein the payment devices include POS terminals, cash registers, and other payment terminals. The payment device connects to a node server and a cloud server, and the node server is also connected to the cloud server, as shown in the appendix. Figure 2 This includes steps 810 to 860: Step 810: Receive the address allocation table from the cloud server. The execution node server in the address allocation table is obtained through the payment device upgrade task allocation method described above. Step 820: Obtain the node switching strategy; Step 830: Send an upgrade task polling request to the execution node server; wherein, the upgrade task polling request is used to inquire whether there is an upgrade task; Step 840: Receive the response information corresponding to the polling request. If the response information contains an upgrade task, send a request to download the upgrade package to the execution node server. Step 850: Determine the availability of the execution node server. If it is unavailable, determine another execution node server in the address allocation table according to the node switching policy; record the switching log and upload it to the node server.

[0036] Step 860: Using another execution node server as the new round of execution node server, execute the step of sending an upgrade task polling request to the execution node server; As described above, the payment device in this embodiment obtains a pre-allocated address allocation table from the cloud server and implements dynamic server selection by combining a node switching strategy. When the currently executing node server is detected to be unavailable, it automatically switches to a backup node. This not only ensures the reliability of the upgrade task acquisition, but also achieves high service availability through a polling mechanism and dynamic switching. It effectively avoids upgrade interruptions caused by single points of failure and improves the upgrade success rate and system stability of the payment device in complex network environments.

[0037] This invention also provides a payment device upgrade method applied to a node server, wherein the node server is connected to the payment device, and the payment device is also connected to a cloud server, as shown in the appendix. Figure 3 This includes steps 910 to 950: Step 910: Obtain the polling request from the payment device. The payment device sends the polling request to the execution node server obtained in the above-mentioned payment device upgrade task allocation method. Step 920: Obtain the upgrade task corresponding to the polling request and send the response information to the payment device; Step 930: Obtain the request to download the upgrade package; Step 940: Match the corresponding upgrade data based on the download upgrade package request; Step 950: Send upgrade data to the payment device through the secure channel; if the upgrade is successful, receive the upgrade result log sent by the payment device and record the log in the log database.

[0038] As described above, this embodiment obtains the polling requests from payment devices and matches them with corresponding upgrade tasks. Upon receiving a download request, it transmits upgrade data through a secure channel. Thus, this embodiment achieves efficient matching between upgrade tasks and payment device requirements. It ensures the real-time nature of task distribution through a polling mechanism and safeguards the integrity and confidentiality of data transmission through a secure channel. This reduces network resource consumption while effectively preventing data tampering and leakage risks, significantly improving the security and reliability of the payment device upgrade process.

[0039] The following details the application embodiments of this application, which demonstrate how the above solution can be applied to a POS terminal. (Refer to the appendix.) Figure 5 This includes steps A through M: Step A: The cloud server's front-end scheduling service (ALLOC service) periodically collects stress data from the upgrade nodes to prepare for upgrade access allocation; this step corresponds to step 120 above. Step B: The upgraded node returns the stress data to the ALLOC service; Step C: The POS terminal obtains an access address from the ALLOC service; Step D: The ALLOC service generates an address allocation table based on node load and terminal characteristics (model, merchant type, upgrade history), and then sends the address allocation table to the terminal through a secure channel; this corresponds to steps 130 and 810 above. Step E: The POS terminal initiates a polling request to the master node entry of the execution node server (corresponding to the upgrade node in the diagram) according to the address allocation table to inquire whether there is an upgrade task. If the node returns that there is a task: proceed to the download step.

[0040] Step F: The POS terminal requests the download of the upgrade package from the main entry point of the execution node server (corresponding to step 840 above).

[0041] Step G: The execution node server returns the upgrade data to the POS terminal; Step H: Download successful, the terminal completes the upgrade and uploads the upgrade result log to the execution node server.

[0042] Step 1: If the download fails or times out, the terminal uploads the failure log to the execution node server; Step J: Switch to the standby upgrade node (corresponding to the other execution node server mentioned above) to continue the download (corresponding to step 850 above).

[0043] Step K: The backup upgrade node returns upgrade data to the POS terminal; Step L: After the switchover operation is completed, upload the switchover log to the ALLOC service for scheduling and risk control analysis.

[0044] Step M: If the execution node server returns no task: the POS terminal waits for a period of time and then re-polles, or tries to poll the backup upgrade node / entry point; this step corresponds to step 830 above.

[0045] Please refer to the appendix. Figure 5 The present invention also provides an electronic device 400, including a memory 402 and a processor 401, and a computer program stored on the memory 402 and running on the processor 401. When the processor 401 executes the computer program, it implements the various steps in the payment device upgrade task allocation method described above.

[0046] The beneficial effects of the electronic device of the present invention are the same as those of the method described above, and will not be repeated here.

[0047] In summary, this invention provides a method for allocating upgrade tasks for payment devices, an upgrade method, and an electronic device. First, it obtains an upgrade request from the payment device and, before the upgrade, comprehensively acquires the historical and current load conditions of all node servers, where the load condition is correlated with the number of connected payment devices. Then, based on the historical and current load conditions, it determines the execution node server from all node servers. Finally, it sends the execution node server information to the payment device to instruct it to request an upgrade. Historical load conditions reflect the long-term load capacity and stability of the server, while current load conditions allow for real-time load perception. This dual load judgment mechanism ensures that the selected execution node server has a relatively balanced load and suitable processing capacity, thereby achieving reasonable allocation of upgrade tasks, effectively avoiding single-point overload, and improving upgrade success rate and security. By obtaining a pre-allocated address allocation table from the cloud server and combining it with a node switching strategy to achieve dynamic server selection, it automatically switches to a backup node when the current execution node server is detected as unavailable. This ensures the reliability of upgrade task acquisition and achieves high service availability through a polling mechanism and dynamic switching, effectively avoiding upgrade interruptions caused by single-point failures and improving the upgrade success rate and system stability of payment devices in complex network environments. By employing a polling mechanism to ensure real-time task distribution and utilizing a secure channel to guarantee the integrity and confidentiality of data transmission, the system effectively prevents data tampering and leakage risks while reducing network resource consumption, significantly improving the security and reliability of the payment device upgrade process. A complete closed loop is formed by integrating polling records, download status, and switching information, supporting traceability for large-scale terminal upgrades.

[0048] The above are merely embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention's specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for allocating upgrade tasks for payment devices, characterized in that, Applied to a cloud server, wherein the cloud server is connected to a payment device, the payment device is also connected to a node server, and the cloud server is connected to the node server, the method includes: Obtain an upgrade request for the payment device; Before the payment device is upgraded, the historical load information and current load information of all the node servers are obtained; wherein the historical load information and current load information are related to the number of payment devices connected to the node server. Based on the historical and current pressure conditions, the execution node server is determined from all the node servers. The upgrade task corresponding to the upgrade request is assigned to the execution node server for execution.

2. The payment device upgrade task allocation method according to claim 1, characterized in that, Prior to the upgrade of the payment device, the method also includes: At preset time intervals, collect the node attributes of all the node servers to determine the node pressure. Save the node pressure data to historical pressure data.

3. The payment device upgrade task allocation method according to claim 1, characterized in that, The step of determining the execution node server from all the node servers based on the historical and current pressure conditions includes: The pressure analysis results are obtained by analyzing the historical pressure conditions and the current pressure conditions; Based on the stress analysis results and the terminal characteristics of the payment device, query the intermediate node server from all the node servers; The address allocation table obtained from the intermediate node server corresponds one-to-one with the payment device. The address allocation table includes the stress analysis results of the intermediate node server, the connection information of the intermediate node server, and the corresponding digital signature. The execution node server is determined based on the address allocation table.

4. The payment device upgrade task allocation method according to claim 3, characterized in that, The step of determining the execution node server according to the address allocation table further includes: Determine whether the intermediate node server has a secure node server that has established a two-way secure channel with the cloud server. If it does, select the secure node server as the execution node server. The step of assigning the upgrade task corresponding to the upgrade request to the execution node server for execution further includes: The upgrade task corresponding to the upgrade request is assigned to the execution node server for execution through the secure channel.

5. The payment device upgrade task allocation method according to claim 3, characterized in that, Also includes: Calculate the hash value of the address allocation table; Obtain a preset private key, and use the private key to encrypt the hash value to obtain a digital signature; The address allocation table and the digital signature are sent to the payment device, instructing the payment device to request the execution node server in the address allocation table to execute an upgrade request after successfully verifying the digital signature.

6. The payment device upgrade task allocation method according to claim 3, characterized in that, The step of determining the execution node server according to the address allocation table includes: Obtain the first geographical region and stress analysis results for each node server in the address allocation table; Obtain the second geographical region of the payment device; The execution node server is determined based on the stress analysis results. If the number of execution node servers exceeds one, the nearest target first geographical region is matched according to the second geographical region, and the execution node server corresponding to the target first geographical region is taken as the target execution node server. The step of determining the execution node server according to the address allocation table also includes: This instructs the payment device to request the target execution node server in the address allocation table to perform a task.

7. The payment device upgrade task allocation method according to claim 1, characterized in that, Also includes: When the upgrade task allocation fails, based on the historical pressure situation and the current pressure situation, and according to the switching strategy including geographical region, network latency and security level, a second execution node server is reselected from all node servers.

8. A method for upgrading a payment device, characterized in that, The method, applied to a payment device connected to a node server and a cloud server, wherein the node server is also connected to a cloud server, includes: The address allocation table is received from the cloud server, and the execution node server in the address allocation table is obtained by the payment device upgrade task allocation method according to any one of claims 1 to 7. Get the node switching strategy; Send a polling request for the upgrade task to the execution node server; Receive the response information corresponding to the polling request; if the response information contains an upgrade task, send a request to download the upgrade package to the execution node server. Determine the availability of the execution node server; if it is unavailable, determine another execution node server in the address allocation table according to the node switching strategy. Using the other execution node server as the new round of execution node server, the step of sending the upgrade task polling request to the execution node server is executed.

9. A method for upgrading a payment device, characterized in that, The method, applied to a node server connected to a payment device and a cloud server, wherein the payment device is also connected to the cloud server, includes: The payment device obtains a polling request and sends the polling request to the execution node server obtained in the payment device upgrade task allocation method according to any one of claims 1 to 7. Obtain the upgrade task corresponding to the polling request and send a response message to the payment device; Request to download upgrade package; Match the corresponding upgrade data based on the download upgrade package request; The upgrade data is sent to the payment device through a secure channel.

10. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the payment device upgrade task allocation method according to any one of claims 1 to 7, the steps of the payment device upgrade method according to claim 8, or the steps of the payment device upgrade method according to claim 9.

Images