A blockchain-based task scheduling method, device and storage medium

Abstract

The application discloses a kind of based on the task scheduling method of blockchain, equipment and storage medium.Method includes: based on the front-end interactive interface provided by scheduling service in cluster system, determine the current task allocation rule corresponding to execution service;Wherein, execution service includes several execution instances;Current task allocation rule is polling task allocation rule or weight matching task allocation rule;In the case where the execution request of to-be-executed task is received by cluster system, scheduling service calls the to-be-interacted smart contract corresponding to execution service pre-stored in blockchain, to determine the task execution state of current task allocation rule, and based on task execution state, determine the to-be-executed instance identifier corresponding to to-be-executed task;Based on to-be-executed instance identifier, call corresponding to-be-executed instance to execute to-be-executed task, and return execution result to scheduling service.The application guarantees that the task execution of cluster system is not repeated by the above method.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a blockchain-based task scheduling method, device, and storage medium. Background Technology

[0002] In cluster systems, execution services often have multiple execution instances. When a cluster system executes a task, it needs to determine which execution instance should be responsible for it. Existing cluster systems sometimes experience the same task being executed repeatedly.

[0003] Therefore, ensuring that tasks in a cluster system are not duplicated has become a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a blockchain-based task scheduling method, device, and storage medium to solve the following technical problem: how to ensure that task execution in a cluster system is not duplicated.

[0005] In a first aspect, embodiments of this application provide a blockchain-based task scheduling method, characterized in that the method includes: determining the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system; wherein the execution service includes several execution instances; the current task allocation rule is a round-robin task allocation rule or a weight-matching task allocation rule; when the cluster system receives an execution request for a task to be executed, the scheduling service calls the pre-stored smart contract corresponding to the execution service in the blockchain to determine the task execution status of the current task allocation rule, and determines the identifier of the execution instance corresponding to the task to be executed based on the task execution status; based on the identifier of the execution instance, calling the corresponding execution instance to execute the task to be executed, and returning the execution result to the scheduling service.

[0006] In one implementation of this application, before determining the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system, the method further includes: deploying the smart contract to be interacted corresponding to the current task allocation rule on the blockchain and determining the unique number corresponding to the smart contract to be interacted; after determining the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system, the method further includes: the scheduling service recording the unique number of the smart contract to be interacted in the cluster system database.

[0007] In one implementation of this application, the scheduling service calls the smart contract to be interacted with, which is pre-stored in the blockchain, to determine the task execution status of the current task allocation rule. Specifically, the scheduling service reads the cluster system database to obtain a unique number and identifies the smart contract to be interacted with in the blockchain based on the unique number; calls the smart contract to be interacted with; and the smart contract to be interacted with determines the number of executions of each execution instance stored therein, which is the task execution status of the current task allocation rule corresponding to the execution service.

[0008] In one implementation of this application, determining the execution instance identifier corresponding to the task to be executed based on the task execution status specifically includes: the smart contract to be interacted with determines whether the execution count of each execution instance is 0, and if the execution count of each execution instance is determined to be 0, the execution instance identifier corresponding to the first execution instance in the execution service is determined as the execution instance identifier; wherein, the first execution instance is the execution instance that is first in the execution service; if it is determined that the execution count of any execution instance is not 0, the execution instance identifier corresponding to the task to be executed is determined based on the contract content of the smart contract to be interacted with.

[0009] In one implementation of this application, determining the identifier of the execution instance corresponding to the task to be executed based on the contract content of the smart contract to be interacted with specifically includes: determining whether the task allocation rule corresponding to the smart contract to be interacted with is a round-robin task allocation rule or a weighted matching task allocation rule; if the task allocation rule corresponding to the smart contract to be interacted with is a round-robin task allocation rule, the smart contract to be interacted with arranges each execution instance according to its position in the execution service, and compares the execution count of each execution instance in the execution service with the execution count of the first execution instance in turn to determine whether there is an execution instance with a different execution count than the first execution instance; if it is determined that there is no execution instance with a different execution count than the first execution instance, then the identifier of the first execution instance is confirmed as the identifier of the execution instance corresponding to the task to be executed; if it is determined that there is an execution instance with a different execution count than the first execution instance, then the identifier of the first execution instance in the execution service with a different execution count than the first execution instance is confirmed as the identifier of the execution instance corresponding to the task to be executed.

[0010] In one implementation of this application, the method further includes: when the task allocation rule corresponding to the smart contract to be interacted with is a weight-matching task allocation rule, determining whether the execution count of each execution instance has reached the periodic weight allocation count; when it is determined that the execution count of each execution instance has reached the periodic weight allocation count, determining the identifier of the first execution instance as the identifier of the execution instance corresponding to the task to be executed; when it is determined that the execution count of each execution instance has not reached the periodic weight allocation count, determining the identifier of the first execution instance that has not reached the periodic weight allocation count as the identifier of the execution instance corresponding to the task to be executed, based on the position arrangement of each execution instance in the execution service.

[0011] In one implementation of this application, after returning the execution result to the scheduling service, the method further includes: the scheduling service determining whether the task to be executed was successfully executed based on the execution result; and uploading the execution result to the blockchain.

[0012] In one implementation of this application, the method further includes: if it is determined that the task to be executed has failed, the scheduling service sends the instance identifier to the blockchain to trigger the smart contract to be interacted with to retry the execution; if the number of execution retries reaches a preset threshold, an alarm message is generated and sent to the front-end interactive interface provided by the scheduling service.

[0013] Secondly, embodiments of this application also provide a blockchain-based task scheduling device, characterized in that the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: determine the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system; wherein the execution service includes several execution instances; the current task allocation rule is a round-robin task allocation rule or a weight-matching task allocation rule; when the cluster system receives an execution request for a task to be executed, the scheduling service calls the pre-stored smart contract corresponding to the execution service in the blockchain to determine the task execution status of the current task allocation rule, and determines the identifier of the execution instance corresponding to the task to be executed based on the task execution status; based on the identifier of the execution instance, calls the corresponding execution instance to execute the task to be executed, and returns the execution result to the scheduling service.

[0014] Thirdly, embodiments of this application also provide a non-volatile computer storage medium for blockchain-based task scheduling, storing computer-executable instructions. The computer-executable instructions are configured to: determine the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system; wherein the execution service includes several execution instances; the current task allocation rule is a round-robin task allocation rule or a weighted matching task allocation rule; when the cluster system receives an execution request for a task to be executed, the scheduling service calls the pre-stored smart contract corresponding to the execution service in the blockchain to determine the task execution status of the current task allocation rule, and based on the task execution status, determines the identifier of the execution instance corresponding to the task to be executed; based on the execution instance identifier, calls the corresponding execution instance to execute the task to be executed, and returns the execution result to the scheduling service.

[0015] This application provides a blockchain-based task scheduling method, device, and storage medium. By interacting with the blockchain through a scheduling service, it allocates execution instances for tasks to be executed, ensuring that each task is successfully executed only once. This guarantees correct task completion while preventing duplicate execution. Furthermore, leveraging the immutability and data sharing characteristics of blockchain, it preserves the execution details of the tasks. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0017] Figure 1 A flowchart of a blockchain-based task scheduling method provided in this application embodiment;

[0018] Figure 2 This is a schematic diagram of the internal structure of a blockchain-based task scheduling device provided in an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] This application provides a blockchain-based task scheduling method, device, and storage medium to solve the following technical problem: how to ensure that task execution in a cluster system is not duplicated.

[0021] The technical solutions proposed in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0022] Figure 1 A flowchart illustrating a blockchain-based task scheduling method provided in this application embodiment. Figure 1 As shown in the figure, the blockchain-based task scheduling method provided in this application embodiment specifically includes the following steps:

[0023] Step 101: Based on the front-end interactive interface provided by the scheduling service in the cluster system, determine the current task allocation rules corresponding to the execution service.

[0024] In one embodiment of this application, in order to ensure that the task execution of the cluster system is not duplicated, before determining the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system, it is necessary to deploy the smart contract to be interacted with corresponding to the current task allocation rule on the blockchain and determine the unique number corresponding to the smart contract to be interacted with.

[0025] In one embodiment of this application, the execution service includes several execution instances, and the current task allocation rule is either a round-robin task allocation rule or a weight-matching task allocation rule.

[0026] In one embodiment of this application, after determining the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system, the scheduling service records the unique number of the smart contract to be interacted with in the cluster system database.

[0027] Step 102: When the cluster system receives the execution request of the task to be executed, the scheduling service calls the smart contract to be interacted with corresponding to the execution service pre-stored in the blockchain to determine the task execution status of the current task allocation rule, and determines the execution instance identifier corresponding to the task to be executed based on the task execution status.

[0028] In one embodiment of this application, when the cluster system receives an execution request for a task to be executed, the scheduling service reads the cluster system database to obtain a unique number, and identifies the smart contract to be interacted with in the blockchain based on the unique number.

[0029] Furthermore, the smart contract to be interacted with is invoked; the smart contract to be interacted with determines the number of executions of each execution instance stored therein, and assigns the task execution status of the current task corresponding to the execution service according to the rules.

[0030] In one embodiment of this application, after determining the task execution status of the current task allocation rule, the smart contract to be interacted with determines whether the execution count of each execution instance is 0, and if the execution count of each execution instance is 0, determines the execution instance identifier corresponding to the first execution instance in the execution service as the execution instance identifier to be executed; wherein, the first execution instance is the execution instance whose position is the first in the execution service.

[0031] Furthermore, if it is determined that the execution count of any execution instance is not zero, the execution instance identifier corresponding to the task to be executed is determined based on the contract content of the smart contract to be interacted with.

[0032] In one embodiment of this application, determining the identifier of the execution instance corresponding to the task to be executed based on the contract content of the smart contract to be interacted with specifically includes: determining whether the task allocation rule corresponding to the smart contract to be interacted with is a round-robin task allocation rule or a weighted matching task allocation rule; if the task allocation rule corresponding to the smart contract to be interacted with is a round-robin task allocation rule, the smart contract to be interacted with is arranged according to the position of each execution instance in the execution service, and compares the execution count of each execution instance in the execution service with the execution count of the first execution instance in turn to determine whether there is an execution instance with a different execution count than the first execution instance; if it is determined that there is no execution instance with a different execution count than the first execution instance, the identifier of the first execution instance is confirmed as the identifier of the execution instance corresponding to the task to be executed; if it is determined that there is an execution instance with a different execution count than the first execution instance, the identifier of the first execution instance in the execution service with a different execution count than the first execution instance is confirmed as the identifier of the execution instance corresponding to the task to be executed.

[0033] In one embodiment of this application, the method further includes: when the task allocation rule corresponding to the smart contract to be interacted with is a weight-matching task allocation rule, determining whether the execution count of each execution instance has reached the periodic weight allocation count; when it is determined that the execution count of each execution instance has reached the periodic weight allocation count, determining the identifier of the first execution instance as the identifier of the execution instance corresponding to the task to be executed; when it is determined that the execution count of each execution instance has not reached the periodic weight allocation count, determining the identifier of the first execution instance that has not reached the periodic weight allocation count as the identifier of the execution instance corresponding to the task to be executed, based on the position arrangement of each execution instance in the execution service.

[0034] For example, an execution service contains three execution instances: Execution Instance 1, Execution Instance 2, and Execution Instance 3, with corresponding periodic weight allocation counts of 1, 2, and 7, respectively. If it is determined that the current periodic weight allocation counts for Execution Instance 1, Execution Instance 2, and Execution Instance 3 are already 1, 2, and 7, respectively, then the next task allocation cycle begins, starting directly from Execution Instance 1. If the current periodic weight allocation counts for Execution Instance 1, Execution Instance 2, and Execution Instance 3 are 1, 1, and 0 (i.e., it is determined that the execution counts of each execution instance have not all reached the periodic weight allocation count), then the current task to be executed is assigned to Execution Instance 2 according to the execution instance's position. If further task allocations occur, since Execution Instance 2 has reached its corresponding periodic weight allocation count of 2, the task is assigned to Execution Instance 3 until Execution Instance 3 reaches its periodic weight allocation count, at which point a new task allocation cycle begins.

[0035] Step 103: Based on the identifier of the instance to be executed, call the corresponding instance to be executed to execute the task to be executed, and return the execution result to the scheduling service.

[0036] In one embodiment of this application, after determining the identifier of the execution instance corresponding to the task to be executed, the corresponding execution instance is invoked to execute the task based on the execution instance identifier, and the execution result is returned to the scheduling service. After returning the execution result to the scheduling service, the scheduling service determines whether the task to be executed was successful based on the execution result; and uploads the execution result to the blockchain.

[0037] Furthermore, if it is determined that the task to be executed has failed, the scheduling service will send the instance identifier to the blockchain to trigger the smart contract to be interacted with to retry the execution; if the number of execution retries reaches a preset threshold, an alarm message will be generated and sent to the front-end interactive interface provided by the scheduling service.

[0038] The above are embodiments of the method proposed in this application. Based on the same inventive concept, embodiments of this application also provide a blockchain-based task scheduling device, the structure of which is as follows: Figure 2 As shown.

[0039] Figure 2 This is a schematic diagram of the internal structure of a blockchain-based task scheduling device provided in an embodiment of this application. Figure 2 As shown, the device includes:

[0040] At least one processor 201;

[0041] And a memory 202 that is communicatively connected to at least one processor;

[0042] The memory 202 stores instructions executable by at least one processor, which are executed by at least one processor 201 to enable at least one processor 201 to:

[0043] Based on the front-end interactive interface provided by the scheduling service in the cluster system, the current task allocation rule corresponding to the execution service is determined; wherein, the execution service includes several execution instances; the current task allocation rule is either a round-robin task allocation rule or a weight-matching task allocation rule;

[0044] When the cluster system receives an execution request for a task to be executed, the scheduling service calls the smart contract to be interacted with corresponding to the execution service pre-stored in the blockchain to determine the task execution status of the current task allocation rule, and determines the execution instance identifier corresponding to the task to be executed based on the task execution status.

[0045] Based on the identifier of the instance to be executed, the corresponding instance to be executed is invoked to execute the task to be executed, and the execution result is returned to the scheduling service.

[0046] Some embodiments of this application provide corresponding to Figure 1 A non-volatile computer storage medium for blockchain-based task scheduling, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0047] Based on the front-end interactive interface provided by the scheduling service in the cluster system, the current task allocation rule corresponding to the execution service is determined; wherein, the execution service includes several execution instances; the current task allocation rule is either a round-robin task allocation rule or a weight-matching task allocation rule;

[0048] When the cluster system receives an execution request for a task to be executed, the scheduling service calls the smart contract to be interacted with corresponding to the execution service pre-stored in the blockchain to determine the task execution status of the current task allocation rule, and determines the execution instance identifier corresponding to the task to be executed based on the task execution status.

[0049] Based on the identifier of the instance to be executed, the corresponding instance to be executed is invoked to execute the task to be executed, and the execution result is returned to the scheduling service.

[0050] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for IoT devices and media are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0051] The systems, media, and methods provided in this application are one-to-one correspondences. Therefore, the systems and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the systems and media will not be repeated here.

[0052] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0053] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0054] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0055] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0056] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0057] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0058] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0059] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0060] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A task scheduling method based on blockchain, characterized in that, The method includes: Based on the front-end interactive interface provided by the scheduling service in the cluster system, the current task allocation rule corresponding to the execution service is determined; wherein, the execution service includes several execution instances; the current task allocation rule is a round-robin task allocation rule or a weight-matching task allocation rule; When the cluster system receives an execution request for a task to be executed, the scheduling service calls the smart contract corresponding to the execution service pre-stored in the blockchain to determine the task execution status of the current task allocation rule, and determines the execution instance identifier corresponding to the task to be executed based on the task execution status. Based on the identifier of the instance to be executed, the corresponding instance to be executed is invoked to execute the task to be executed, and the execution result is returned to the scheduling service; Before determining the current task allocation rule corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system, the method further includes: deploying the smart contract to be interacted corresponding to the current task allocation rule on the blockchain, and determining the unique number corresponding to the smart contract to be interacted. After determining the current task allocation rules corresponding to the execution service based on the front-end interactive interface provided by the scheduling service in the cluster system, the method further includes: the scheduling service recording the unique number of the smart contract to be interacted with in the cluster system database; The scheduling service calls the smart contract to be interacted with corresponding to the execution service pre-stored in the blockchain to determine the task execution status of the current task allocation rule. Specifically, the scheduling service reads the cluster system database to obtain the unique number, and identifies the smart contract to be interacted with in the blockchain based on the unique number; calls the smart contract to be interacted with; the smart contract to be interacted with determines the number of executions of each execution instance stored therein, which is the task execution status of the current task allocation rule corresponding to the execution service. Based on the task execution status, the identifier of the pending execution instance corresponding to the pending task is determined, specifically including: the smart contract to be interacted with determines whether the execution count of each execution instance is 0, and if the execution count of each execution instance is determined to be 0, the execution instance identifier corresponding to the first execution instance in the execution service is determined as the pending execution instance identifier; wherein, the first execution instance is the execution instance whose position is first in the execution service; if it is determined that the execution count of any execution instance is not 0, the identifier of the pending execution instance corresponding to the pending task is determined based on the contract content of the smart contract to be interacted with. Based on the contract content of the smart contract to be interacted with, the identifier of the execution instance corresponding to the task to be executed is determined, specifically including: determining whether the task allocation rule corresponding to the smart contract to be interacted with is a round-robin task allocation rule or a weighted matching task allocation rule; if the task allocation rule corresponding to the smart contract to be interacted with is a round-robin task allocation rule, the smart contract to be interacted with is arranged according to the position of each execution instance in the execution service, and the execution count of each execution instance in the execution service is compared with the execution count of the first execution instance to determine whether there is an execution instance with a different execution count than the first execution instance; if it is determined that there is no execution instance with a different execution count than the first execution instance, the identifier of the first execution instance is confirmed as the identifier of the execution instance corresponding to the task to be executed; if it is determined that there is an execution instance with a different execution count than the first execution instance, the identifier of the first execution instance in the execution service with a different execution count than the first execution instance is confirmed as the identifier of the execution instance corresponding to the task to be executed. The method further includes: when the task allocation rule corresponding to the smart contract to be interacted with is a weight-matching task allocation rule, determining whether the execution count of each execution instance has reached the periodic weight allocation count; when it is determined that the execution count of each execution instance has reached the periodic weight allocation count, determining the identifier of the first execution instance as the identifier of the execution instance corresponding to the task to be executed; when it is determined that the execution count of each execution instance has not reached the periodic weight allocation count, based on the position arrangement of each execution instance in the execution service, determining the identifier of the first execution instance that has not reached the periodic weight allocation count as the identifier of the execution instance corresponding to the task to be executed.

2. The task scheduling method based on blockchain according to claim 1, characterized in that, After returning the execution result to the scheduling service, the method further includes: The scheduling service determines whether the task to be executed was successful based on the execution result; and, The execution results are uploaded to the blockchain.

3. The task scheduling method based on blockchain according to claim 2, characterized in that, The method further includes: If the task to be executed is determined to have failed, the scheduling service will send the instance identifier to the blockchain to trigger the smart contract to be interacted with to retry the execution. If the number of retries reaches a preset threshold, an alarm message is generated and sent to the front-end interactive interface provided by the scheduling service.

4. A task scheduling device based on blockchain, characterized in that, The device includes: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform a blockchain-based task scheduling method as described in any one of claims 1-3.

5. A non-volatile computer storage medium for task scheduling based on blockchain, storing computer-executable instructions, characterized in that, The computer-executable instructions are configured to, when executed, implement a blockchain-based task scheduling method as described in any one of claims 1-3.

Images