CN112148803A - Method, device, device and readable storage medium for invoking tasks in blockchain - Google Patents

Abstract

The present disclosure provides a method, device, device and readable storage medium for invoking a task in a blockchain, the method comprising: sending an identifier of the task and an execution condition to a server; wherein, the execution condition of the task is determined when the task is created; The target task identification sent by the server is received, and the corresponding task is executed according to the target task identification; the target task identification is determined by the server according to the task identification and execution conditions. The method, device, device and readable storage medium provided by the present disclosure can send the execution condition of the task and the task identifier to the server, monitor whether the execution condition of the task is satisfied through the server, and the server feedback to the blockchain platform that the execution condition is satisfied Therefore, the method, device, device and readable storage medium provided by the present disclosure can trigger the execution of the task according to preset conditions, and satisfy the user's requirement for the task triggering mechanism. need.

Description

Method, device, device and readable storage medium for invoking tasks in blockchain

technical field

The present disclosure relates to blockchain technology, and in particular, to a method, apparatus, device and readable storage medium for invoking tasks in the blockchain.

Background technique

With the widespread application of blockchain technology, many enterprises will set up the blockchain architecture as the underlying platform and conduct business processing based on the blockchain platform.

The business in the blockchain platform in the prior art is triggered by the external server directly calling the method in the blockchain platform according to the parameters involved in the business. For example, the external server sends a transaction request to the blockchain platform, and the block Each node in the chain platform can verify this request.

Therefore, the blockchain transaction triggering mechanism in the prior art is single and cannot meet current user needs.

SUMMARY OF THE INVENTION

The present disclosure provides a method, device, device, and readable storage medium for invoking tasks in a blockchain, so as to solve the technical problem of a single transaction trigger mechanism in the blockchain in the prior art.

A first aspect of the present disclosure is to provide a method for invoking tasks in a blockchain, including:

Send the identification of the task and the execution condition to the server; wherein, the execution condition of the task is determined when the task is created;

The target task identifier sent by the server is received, and a corresponding task is executed according to the target task identifier; the target task identifier is determined by the server according to the task identifier and the execution condition.

A second aspect of the present disclosure is to provide a method for invoking tasks in a blockchain, including:

Receive the task identifier and execution condition sent by the blockchain platform; wherein, the execution condition of the task is determined when the task is created;

The target task identifier is determined according to the task identifier and the execution condition, and the target task identifier is sent to the blockchain platform, so that the blockchain platform executes the task corresponding to the target task identifier.

A third aspect of the present disclosure is to provide a device for invoking tasks in a blockchain, including:

A sending module, used for sending the identification of the task and the execution condition to the server; wherein, the execution condition of the task is determined when the task is created;

The first receiving module is used to receive the target task identification sent by the server, and execute the corresponding task according to the target task identification; the target task identification is determined by the server according to the task identification and the execution condition. .

A fourth aspect of the present disclosure is to provide a device for invoking tasks in a blockchain, including:

a receiving module, configured to receive the task identifier and execution condition sent by the blockchain platform; wherein, the execution condition of the task is determined when the task is created;

A determination module, configured to determine the target task identifier according to the task identifier and the execution condition, and send the target task identifier to the blockchain platform, so that the blockchain platform executes the target task identifier corresponding to the task.

A fifth aspect of the present disclosure is to provide a device for invoking tasks in a blockchain, including:

memory;

processor; and

Computer program;

Wherein, the computer program is stored in the memory and configured to be executed by the processor to implement the method for invoking a task in the blockchain as described in the first aspect or the second aspect.

A sixth aspect of the present disclosure is to provide a computer-readable storage medium on which a computer program is stored, the computer program being executed by a processor to implement the blockchain as described in the first or second aspect above The calling method of the task in .

The technical effects of the method, device, device and readable storage medium for invoking tasks in the blockchain provided by the present disclosure are:

The method, device, device and readable storage medium for invoking tasks in the blockchain provided by the present disclosure include: sending the identification of the task and execution conditions to the server; wherein, the execution conditions of the task are determined when the task is created; receiving the server Send the target task identifier, and execute the corresponding task according to the target task identifier; the target task identifier is determined by the server according to the task identifier and execution conditions. The method, device, device and readable storage medium provided by the present disclosure can send the execution condition of the task and the task identifier to the server, monitor whether the execution condition of the task is satisfied through the server, and the server feedback to the blockchain platform that the execution condition is satisfied Therefore, the method, device, device and readable storage medium provided by the present disclosure can trigger the execution of the task according to preset conditions and satisfy the user's requirement for the task triggering mechanism. need.

Description of drawings

1 is a flowchart of a method for invoking a task in a blockchain according to an exemplary embodiment of the present invention;

2 is a flowchart of a method for invoking a task in a blockchain according to another exemplary embodiment of the present invention;

Fig. 2A is a task identification display diagram according to an exemplary embodiment of the present invention;

3 is a flowchart of a method for invoking a task in a blockchain according to another exemplary embodiment of the present invention;

4 is a flowchart of a method for invoking a task in a blockchain according to yet another exemplary embodiment of the present invention;

5 is a structural diagram of an apparatus for invoking tasks in a blockchain according to an exemplary embodiment of the present invention;

6 is a structural diagram of an apparatus for invoking tasks in a blockchain according to another exemplary embodiment of the present invention;

7 is a structural diagram of an apparatus for invoking tasks in a blockchain according to another exemplary embodiment of the present invention;

FIG. 8 is a structural diagram of an apparatus for invoking a task in a blockchain according to yet another exemplary embodiment of the present invention.

Detailed ways

In the blockchain-based platform in the prior art, the server needs to send an instruction to execute the task to the blockchain platform, thereby triggering the blockchain platform to execute the corresponding task according to the instruction. For example, the server can send an instruction to create a transaction to the blockchain platform, and at this time, the blockchain platform can create a transaction according to the instruction. However, in this mechanism, there is a single way of triggering tasks, and corresponding methods cannot be executed according to some preset conditions. For example, tasks cannot be triggered based on time, and tasks cannot be triggered based on block height in the blockchain.

The method for invoking a task in the blockchain provided by this embodiment can execute a corresponding task based on a preset task trigger condition, so as to meet the needs of the user.

FIG. 1 is a flowchart of a method for invoking a task in a blockchain according to an exemplary embodiment of the present invention.

As shown in Figure 1, the method for invoking tasks in the blockchain provided by this embodiment includes:

Step 101: Send the task identifier and execution condition to the server; wherein, the execution condition of the task is determined when the task is created.

The method provided in this embodiment may be executed by a blockchain platform or system. A blockchain platform or system may include multiple network nodes, which are connected through the network to form a blockchain network. The blockchain itself is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. It can be considered as a distributed storage method, and the same blocks can be stored in each blockchain node The chain, that is, stores the same data content.

Specifically, each network node may store a smart contract for processing transactions in the blockchain based on the smart contract. Developers can write tasks on the user terminal and upload the task information to the blockchain network platform. For example, a client for connecting to the blockchain platform can be installed on the user terminal, thereby uploading tasks through the client. After the blockchain platform receives the task, it can store the task-related information in the smart contract.

A smart contract can be thought of as a computer program that can be executed automatically, which is itself a system participant. It responds to the information it receives, it can receive and store value, and it can send information and value out.

Further, when a developer writes a task, the task information may specifically include: the method identifier to be called, the task execution condition, and the parameters used when the method is called. The method identifier can be an identifier of an existing method in the smart contract, so that when the task is performed, the method in the smart contract can be called directly. The task execution condition refers to the trigger condition of the task. When this condition is met, the blockchain platform will be triggered to execute the task. Generally speaking, when calling a method, it needs to have input parameters. For example, if a method is used to calculate the sum of variables a and b, when the method is executed, the specific values of a and b need to be obtained, that is, input parameters.

In practical application, the method provided in this embodiment can provide the developer with a method for creating a task, for example, "creatTimerTask()", and the developer can call this method to create a new task.

After the blockchain platform receives the task uploaded by the developer, it can obtain the execution conditions of the task from it, and can also determine the task identifier corresponding to the task. In order to facilitate the distinction of each task, a preset rule may be set for determining the identifier corresponding to each task. For example, tasks can be named according to an incremental rule, starting at 1 until a preset threshold is reached. You can also get the information in the task and name the task based on the task information.

The task identification interval can also be set according to numbers, for example, an integer of 100-199 is used as the task identification. When the blockchain platform receives the task, it determines the task identification in the order of 100 to 199. When the identification reaches 199, the executed task can be determined from 100-199, and the identification of the executed task can be determined. Determined as the ID of the new task. For example, when the task ID has reached 199, the blockchain platform receives a new task. At this time, it can traverse 100-199 to determine the ID corresponding to the task that has been executed. For example, it can be 120. 120 as the identifier for the new task. Task execution conditions, task identifiers, and task parameters can be stored in smart contracts.

Specifically, in the method provided by this embodiment, the task has execution conditions, and when the conditions are met, the task will be executed. At this time, the task can be considered as "one-time", and after the execution is completed, the corresponding task can be deleted. task, then its corresponding identifier will be released. Therefore, the task identifier can be used multiple times, thereby reducing the storage space occupied by storing the task identifier.

Further, the blockchain platform can send the task identification and execution conditions to the server, so that the server can monitor the task according to the execution conditions. There is no need to send the parameters of the task during execution to the server, so as to achieve the effect that the parameters will not be leaked. In the method of this embodiment, the task is sealed in the smart contract, and the parameters corresponding to the task will not be sent out, and only the task identifier and the task execution conditions can be sent to the server.

Step 102: Receive the target task identification sent by the server, and execute the corresponding task according to the target task identification; the target task identification is determined by the server according to the task identification and execution conditions.

In practical applications, the server can store the task identifier and task execution conditions sent by the blockchain platform. And based on the task execution condition, determine the target task identifier that satisfies the condition. For example, the execution condition of task A is that the time is 2018-12-17, 11:29, that is, when the time reaches 2018-12-17, 11:29, task A is executed. The server can monitor the time, and when the time satisfies the execution condition, determines the task A as the target task identifier.

The server can also be a node in the blockchain platform, and the blockchain can also be stored in the node. When the execution condition includes the block height, the server can monitor the block height according to the stored blockchain, and then determine whether the task execution condition is satisfied.

Specifically, the server may also periodically poll the stored task execution conditions, so as to timely determine the tasks that meet the conditions.

Further, after determining that the execution conditions of the tasks are satisfied, the server can send the target task identifiers that satisfy the conditions to the blockchain platform, so that the blockchain platform can execute the corresponding tasks. In the smart contract of the blockchain platform, task information is stored, including the method identifier to be called, the parameters required to execute the method, and the conditions for executing the task. The platform can again determine whether the task execution conditions are met, and if so, execute the method included in the task according to the parameters of the task.

In practical applications, the server can send the target task identifier to the blockchain platform to trigger the blockchain platform to execute the method of running the task. This method can be runTask(), and the target task identifier received by the blockchain platform can be the execution runTask. () parameter. For example, if the blockchain platform receives the target task identifier A sent by the server, the blockchain platform can call runTask() in the smart contract for task A. In the process of running runTask(), you can first determine whether the execution conditions of task A are indeed satisfied. If so, you can obtain the parameters of task A in the smart contract, and call the method in task A to identify the corresponding method, for example, the possible method The identity is m, then method m is run based on the obtained parameters.

The method provided in this embodiment is used to invoke a method in a smart contract in a blockchain platform, and the method is executed by a device provided with the method provided in this embodiment, and the device is usually implemented in hardware and/or software.

The method for invoking a task in a blockchain provided by this embodiment includes: sending a task identifier and an execution condition to a server; wherein, the task execution condition is determined when the task is created; receiving the target task identifier sent by the server, and according to The target task identifier executes the corresponding task; the target task identifier is determined by the server according to the task identifier and execution conditions. In the method provided in this embodiment, the execution conditions of the task and the task identifier can be sent to the server, the server monitors whether the execution conditions of the task are met, and the server feeds back the target task identifier that satisfies the execution conditions to the blockchain platform, thereby triggering the block chain. The blockchain platform executes the target task. Therefore, the method provided in this embodiment can trigger the execution of the task according to the preset conditions, so as to satisfy the user's requirement for the task triggering mechanism.

FIG. 2 is a flowchart of a method for invoking a task in a blockchain according to another exemplary embodiment of the present invention.

As shown in Figure 2, the method for invoking tasks in the blockchain provided by this embodiment includes:

Step 201: Receive key information corresponding to the task sent by the user terminal.

The user terminal here refers to the terminal used by the user who creates the task, for example, it may be the user terminal used by the developer. The developer can call the method used to create the task in the user terminal, such as calling the creatTimerTask() method, and set the key information of the task, including the method ID that the task needs to call, the execution conditions of the task, and the required information when calling the method. parameter. On the premise that the task information is correct, the developer can upload the key information of the task through the user terminal, so that the blockchain platform can receive the key information corresponding to the task.

Specifically, the user terminal can be connected to the blockchain platform through the network, so that key information of the task can be sent to the blockchain platform. The key information includes at least: method identification, execution conditions, and execution parameters. The method identifier refers to the method invoked when the task is executed, the execution condition refers to the preset condition that needs to be satisfied to execute the task, and the execution parameter refers to the parameter input when the method is invoked.

Step 202: Determine the task identifier corresponding to the task according to the preset rule, and store the task identifier and key information in the smart contract.

Further, after receiving the task information uploaded by the user terminal, the blockchain platform can determine the task ID (taskID) corresponding to the task. A preset rule for determining the task identifier can be set, so that the task identifier corresponding to the task is determined according to the rule.

In practical application, the task can be named according to its key information. For example, a hash value can be generated according to the key information of the task, and the hash value can be determined as the identifier corresponding to the task. The task identification of the task may also be determined by numbers, for example, the identification of the first received task may be determined as 1, and the identification of the second received task may be determined as 2.

Since the storage resources in the smart contract are limited, the method provided in this embodiment can determine the task identifier by means of circular numbering.

Wherein, in the method provided by this embodiment, the task identifier may be a number, and in this case, determining the task identifier corresponding to the task according to the preset rule may specifically include:

Obtain the maximum task ID existing in the smart contract. If the maximum task ID is less than the preset upper limit value, the task ID corresponding to the task is determined according to the increment rule.

Specifically, a numerical range corresponding to the task identifier can be preset, for example, it can be 100-199, that is, an integer between 100-199 can be used as the task identifier. After receiving the tasks sent by the user terminal, the tasks can be identified in ascending order, for example, the first task is identified as 100, the second task is identified as 101, and finally the task can be identified as 199.

In the specific implementation process, before identifying the task, the largest existing task identification in the smart contract can be obtained. If the maximum task identification is smaller than the preset upper limit value, that is, the maximum value in the numerical range, the task can be determined according to the increment rule. For the corresponding task identification, specifically, 1 may be added to the maximum task identification to obtain the task identification corresponding to the task. For example, if the current largest task identifier is 125, which is less than the preset upper limit value of 199, the identifier of the newly received task may be determined as 126.

Among them, if the maximum task ID is equal to the preset upper limit value, for example, the maximum task ID is equal to 199, obtain the existing minimum task ID in the smart contract, and if the minimum task ID is greater than the preset lower limit value, determine the corresponding task according to the decrement rule. Task ID. Since the task identification has reached the upper limit value, at this time, the incremental principle can no longer be used to determine the task identification on the basis of 199. Therefore, the task ID corresponding to each unexecuted task in the smart contract can be obtained, and the minimum task ID is determined in it, and then on the basis of the minimum task ID, the task ID corresponding to the newly received task is determined by the principle of decreasing.

Determining the task identifier corresponding to the task according to the decrement rule may include: subtracting 1 from the minimum task identifier to obtain the task identifier corresponding to the task. For example, if the minimum task ID is 145, the newly determined task ID is 144.

Specifically, the method provided by this embodiment further includes: deleting the executed task in the smart contract, thereby releasing the task identifier corresponding to the executed task. Therefore, the task identifiers obtained from the smart contract are the identifiers corresponding to the unexecuted tasks.

Further, in the method provided by this embodiment, a flag bit for determining the task identifier in an incrementing or decrementing manner may also be set. Before executing step 202, the blockchain platform can read the task identifiers already contained in the smart contract, and determine the flag bit based on these task identifiers. The maximum value in the task identifier may be determined first, and if the maximum value is less than the upper limit value, the flag bit may be determined as a value corresponding to the increment rule, for example, 1. If the maximum value is equal to the preset upper limit value, the minimum value in the existing task identifiers can be further determined, and if the minimum value is greater than the preset lower limit value, the flag bit is determined as the value corresponding to the decrement rule, such as 0 .

In practical application, before step 202 is executed, the flag bit may be read first, and then the task identifier corresponding to the task is determined according to the flag bit. For example, if the flag bit is 1, the maximum value of the existing task IDs is obtained, and the increment rule is used to determine the new task ID. If the flag bit is 0, the minimum value of the existing task IDs is obtained, and the decrement rule is used to determine the new task ID.

Among them, after the task is executed, the task information in the smart contract can be deleted, thereby releasing the task identifier corresponding to the task.

FIG. 2A is a display diagram of task identification according to an exemplary embodiment of the present invention.

FIG. 2A is only for the convenience of understanding the cyclic coding method provided by this embodiment. In the actual application process, it is not necessary to display the task identifier in the style of FIG. 2A .

As shown in FIG. 2A , the interval of the mark is 100-199, that is, the initial value of the mark can be 100. When the task is initially received, the task can be marked in a clockwise direction. When the mark reaches the maximum value (also the preset upper limit value) ) 199, you can traverse all the task identifiers in the smart contract, and determine the minimum value of the task identifiers that have not been executed. For example, if the minimum value is 194, the task will be identified from 193 in a counterclockwise direction. After reaching the minimum value of 100, read the largest task identification in the task identification in the smart contract, and then mark the task in a clockwise direction, so that the task identification can be recycled many times.

During the execution of the method provided by this embodiment, tasks are continuously created, executed, and deleted. Therefore, task identification intervals can be set according to actual requirements so that they will not be all occupied at the same time. If the task identifiers are all occupied due to various reasons, the task identifiers can be automatically updated to obtain a new task identifier interval, for example, the task identifiers of 200-299 can be updated.

Step 203: Receive a target task identifier sent by the server, where the target task identifier is determined by the server according to the task identifier and execution conditions.

Step 203 is similar to the specific principle and implementation manner of receiving the target task identifier in step 102, and will not be repeated here.

Step 204: Obtain key information corresponding to the target task identifier in the smart contract.

Among them, after receiving the target task identification sent by the server, the blockchain platform can obtain the key task information corresponding to the target task identification in the smart contract. For example, in a smart contract, you can store: taskID1: taskContext1; taskID2: taskContext2; taskID3: taskContext3, etc. The number after the taskID can be a specific task identifier, and the taskContext is specific task key information. The server can send a task ID that only includes numbers to the blockchain platform, or it can send a task ID that includes both taskID and numbers.

Specifically, the method identification, parameters, execution conditions and other information obtained by the blockchain platform from the smart contract.

Step 205, judging whether the execution conditions included in the key information are satisfied.

Further, according to the acquired execution condition, it can be determined whether the execution condition is currently satisfied. If the execution condition is time information, it can be determined whether the time has been reached. If the execution condition is blockchain height information, it can be determined whether the newly generated block height value in the blockchain is consistent with the execution condition.

The runTask() method can be set in the smart contract. After the server sends the target task identifier to the blockchain platform, the blockchain platform can call runTask() and use the target task identifier as the input parameter of this method. For example, if the target task identifier sent by the server is taskID1, the blockchain platform executes runTask() based on taskID1. In the runTask() method, an if judgment statement may be specifically included to judge whether the current condition satisfies the execution condition included in the key information.

Step 206 , if yes, run the method identification included in the key information based on the execution parameters in the key information and the corresponding method.

If the judgment result in step 205 is yes, it means that the preset conditions for executing the task are met, and therefore, the task can be executed according to the key information corresponding to the task.

Specifically, the method corresponding to the method identifier included in the key information may be run based on the execution parameters in the key information. For example, the corresponding method can be called according to the method identifier included in the key information, and the execution parameter in the key information can be used as the input parameter of the method. The method corresponding to the method identifier can be stored in the smart contract.

If the judgment result in step 205 is no, it can be considered that the execution conditions of the task are not satisfied, and therefore, the method in the smart contract will not be called based on the key information of the task.

Further, the execution condition in the key information may include time and/or block height.

FIG. 3 is a flowchart of a method for invoking a task in a blockchain according to another exemplary embodiment of the present invention.

As shown in Figure 3, the method for invoking tasks in the blockchain provided by this embodiment includes:

Step 301: Receive the task identifier and execution conditions sent by the blockchain platform; wherein, the execution conditions of the task are determined when the task is created.

The method provided in this embodiment may be executed by a server connected to the blockchain platform or system. A blockchain platform or system may include multiple network nodes, which are connected through the network to form a blockchain network. The blockchain itself is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. It can be considered as a distributed storage method, and the same blocks can be stored in each blockchain node The chain, that is, stores the same data content.

A server can be a computing-capable device, such as a computer, tablet, or smartphone.

Specifically, each network node may store a smart contract for processing transactions in the blockchain based on the smart contract. Developers can write tasks on the user terminal and upload the task information to the blockchain network platform. For example, a client for connecting to the blockchain platform can be installed on the user terminal, thereby uploading tasks through the client. After the blockchain platform receives the task, it can store the task-related information in the smart contract.

Further, when a developer writes a task, the task information may specifically include: the method identifier to be called, the task execution condition, and the parameters used when the method is called. The method identifier can be an identifier of an existing method in the smart contract, so that when the task is performed, the method in the smart contract can be called directly. The task execution condition refers to the trigger condition of the task. When this condition is met, the blockchain platform will be triggered to execute the task. Generally speaking, when calling a method, it needs to have input parameters. For example, if a method is used to calculate the sum of variables a and b, when the method is executed, the specific values of a and b need to be obtained, that is, input parameters.

After the blockchain platform receives the task uploaded by the developer, it can obtain the execution conditions of the task from it, and can also determine the task identifier corresponding to the task. The blockchain platform can send the task identification and execution conditions to the server, so that the server can monitor the task according to the execution conditions. There is no need to send the parameters of the task during execution to the server, so as to achieve the effect that the parameters will not be leaked. In the method of this embodiment, the task is sealed in the smart contract, and the parameters corresponding to the task will not be sent out, and only the task identifier and the task execution conditions can be sent to the server.

Step 302: Determine the target task ID according to the task ID and execution conditions, and send the target task ID to the blockchain platform, so that the blockchain platform executes the task corresponding to the target task ID.

In practical applications, the server can store the task identifier and task execution conditions sent by the blockchain platform. And based on the task execution condition, determine the target task identifier that satisfies the condition. For example, the execution condition of task A is that the time is 2018-12-17, 11:29, that is, when the time reaches 2018-12-17, 11:29, task A is executed. The server can monitor the time, and when the time satisfies the execution condition, determines the task A as the target task identifier.

The server can also be a node in the blockchain platform, and the blockchain can also be stored in the node. When the execution condition includes the block height, the server can monitor the block height according to the stored blockchain, and then determine whether the task execution condition is satisfied.

Specifically, the server may also periodically poll the stored task execution conditions, so as to timely determine the tasks that meet the conditions.

Further, after determining that the execution conditions of the tasks are satisfied, the server can send the target task identifiers that satisfy the conditions to the blockchain platform, so that the blockchain platform can execute the corresponding tasks. In the smart contract of the blockchain platform, task information is stored, including the method identifier to be called, the parameters required to execute the method, and the conditions for executing the task. The platform can again determine whether the task execution conditions are met, and if so, execute the method included in the task according to the parameters of the task.

In practical applications, the server can send the target task identifier to the blockchain platform to trigger the blockchain platform to execute the method of running the task. This method can be runTask(), and the target task identifier received by the blockchain platform can be the execution runTask. () parameter. For example, if the blockchain platform receives the target task identifier A sent by the server, the blockchain platform can call runTask() in the smart contract for task A. In the process of running runTask(), you can first determine whether the execution conditions of task A are indeed satisfied. If so, you can obtain the parameters of task A in the smart contract, and call the method in task A to identify the corresponding method, for example, the possible method The identity is m, then method m is run based on the obtained parameters.

The method provided in this embodiment is used to invoke a method in a smart contract in a blockchain platform, and the method is executed by a device provided with the method provided in this embodiment, and the device is usually implemented in hardware and/or software.

The method provided by this embodiment, the method for invoking a task in a blockchain, includes: receiving a task identifier and an execution condition sent by the blockchain platform; wherein, the execution condition of the task is determined when the task is created; The condition determines the target task identification, and sends the target task identification to the blockchain platform, so that the blockchain platform executes the task corresponding to the target task identification. In the method provided by this embodiment, the server can monitor whether the execution conditions of the task are met according to the execution conditions of the task and the task identifier, and the server can feed back the target task identifier that satisfies the execution conditions to the blockchain platform, thereby triggering the execution of the blockchain platform. For the target task, therefore, the method provided by this embodiment can trigger the execution of the task according to the preset condition, so as to satisfy the user's requirement for the task triggering mechanism.

FIG. 4 is a flowchart of a method for invoking a task in a blockchain according to another exemplary embodiment of the present invention.

As shown in Figure 4, the method for invoking tasks in the blockchain provided by this embodiment includes:

Step 401: Receive the task identifier and execution conditions sent by the blockchain platform; wherein, the execution conditions of the task are determined when the task is created.

Step 401 is similar to the specific principle and implementation manner of receiving the task identifier and the execution condition in step 301, and will not be repeated here.

Step 402 , traverse the execution conditions according to the preset frequency, determine the satisfied execution conditions, and determine the corresponding task identifier as the target task identifier.

The server may store the received task identifiers and their corresponding execution conditions, and traverse these execution conditions according to a preset frequency, so as to determine the satisfiable execution conditions. For example, you can set a fixed frequency, such as traversing the execution condition every 0.1 seconds. The specific frequency can be set according to requirements, which is not limited in this embodiment.

Specifically, the execution condition may include execution time and/or block height.

Step 403: Send the target task identifier to the blockchain platform, so that the blockchain platform executes the task corresponding to the target task identifier.

Step 401 is similar to the specific principle and implementation manner of sending the target task identifier in step 302, which will not be repeated here.

FIG. 5 is a structural diagram of an apparatus for invoking tasks in a blockchain according to an exemplary embodiment of the present invention.

As shown in Figure 5, the invoking device for tasks in the blockchain provided by this embodiment includes:

The sending module 51 is used to send the identification of the task and the execution condition to the server; wherein, the execution condition of the task is determined when the task is created;

The first receiving module 52 is configured to receive the target task identification sent by the server, and execute the corresponding task according to the target task identification; the target task identification is determined by the server according to the task identification and the execution condition. of.

The device for invoking a task in the blockchain provided by this embodiment includes: a sending module for sending the identification of the task and the execution condition to the server; wherein, the execution condition of the task is determined when the task is created; the first receiving module, It is used to receive the target task identification sent by the server, and execute the corresponding task according to the target task identification; the target task identification is determined by the server according to the task identification and execution conditions. The device provided in this embodiment can send the execution conditions of the task and the task identification to the server, monitor whether the execution conditions of the task are met through the server, and the server feeds back the identification of the target task that meets the execution conditions to the blockchain platform, thereby triggering the zone The blockchain platform executes the target task. Therefore, the device provided in this embodiment can trigger the execution of the task according to a preset condition, so as to satisfy the user's requirement for the task triggering mechanism.

The specific principles and implementation manners of the apparatus for invoking tasks in the blockchain provided by this embodiment are similar to the embodiment shown in FIG. 1 , and details are not described herein again.

FIG. 6 is a structural diagram of an apparatus for invoking a task in a blockchain according to another exemplary embodiment of the present invention.

As shown in FIG. 6 , on the basis of the above embodiment, the invoking device for tasks in the blockchain provided by this embodiment further includes:

The second receiving module 53 is configured to receive the key information corresponding to the task sent by the user terminal;

The storage module 54 is configured to determine the task identifier corresponding to the task according to a preset rule, and store the task identifier and the key information in the smart contract.

Optionally, the key information includes at least:

Device identification, the execution conditions, and execution parameters.

Optionally, the task identifier is a number; the storage module 54 is specifically used for:

Acquire the existing maximum task identification in the smart contract, and if the maximum task identification is less than a preset upper limit value, determine the task identification corresponding to the task according to an increment rule.

The storage module 54 is specifically configured to add 1 to the maximum task identifier to obtain the task identifier corresponding to the task.

Optionally, if the maximum task identifier is equal to a preset upper limit value, the storage module 54 is also used to:

Obtain the existing minimum task identifier in the smart contract, and if the minimum task identifier is greater than a preset lower limit value, determine the task identifier corresponding to the task according to the decrement rule.

Optionally, the storage module 54 is specifically used for:

The task identifier corresponding to the task is obtained by subtracting 1 from the minimum task identifier.

Optionally, the first receiving module 52 is specifically used for:

Acquire the key information corresponding to the target task identifier in the smart contract;

judging whether the execution conditions included in the key information are satisfied;

If so, run the device corresponding to the device identifier included in the key information based on the execution parameter in the key information.

Optionally, the execution condition includes execution time and/or block height.

The specific principles and implementation manners of the apparatus for invoking tasks in the blockchain provided by this embodiment are similar to the embodiment shown in FIG. 2 , and details are not described herein again.

FIG. 7 is a structural diagram of an apparatus for invoking a task in a blockchain according to another exemplary embodiment of the present invention.

As shown in FIG. 7 , the invoking device for tasks in the blockchain provided by this embodiment includes:

The receiving module 71 is used to receive the task identifier and execution condition sent by the blockchain platform; wherein, the execution condition of the task is determined when the task is created;

A determination module 72, configured to determine a target task identifier according to the task identifier and the execution condition, and send the target task identifier to the blockchain platform, so that the blockchain platform executes the target task identifier corresponding task.

The device for invoking tasks in the blockchain provided by this embodiment includes a receiving module for receiving the task identifier and execution conditions sent by the blockchain platform; wherein, the execution conditions of the task are determined when the task is created; the determining module, It is used to determine the target task identification according to the task identification and execution conditions, and send the target task identification to the blockchain platform, so that the blockchain platform executes the task corresponding to the target task identification. With the device provided in this embodiment, the server can monitor whether the execution conditions of the task are met according to the execution conditions of the task and the task identifier, and the server can feed back the target task identifier that satisfies the execution conditions to the blockchain platform, thereby triggering the execution of the blockchain platform. For the target task, therefore, the device provided in this embodiment can trigger the execution of the task according to a preset condition, so as to satisfy the user's requirement for the task triggering mechanism.

The specific principles and implementation manners of the apparatus for invoking tasks in the blockchain provided in this embodiment are similar to the embodiment shown in FIG. 3 , and details are not described herein again.

On the basis of the above embodiment, in the apparatus for invoking tasks in the blockchain provided by this embodiment, the root determination module 72 is specifically used for:

The execution conditions are traversed according to the preset frequency, the satisfied execution conditions are determined, and the corresponding task identifier is determined as the target task identifier.

Optionally, the execution condition includes execution time and/or block height.

FIG. 8 is a structural diagram of a device invoking a task in a blockchain according to an exemplary embodiment of the present invention.

As shown in FIG. 8 , the calling device of the task in the blockchain provided by this embodiment includes:

memory 81;

processor 82; and

Computer program;

Wherein, the computer program is stored in the memory 81 and configured to be executed by the processor 82 to implement any method for invoking tasks in the blockchain as described above.

This embodiment also provides a computer-readable storage medium on which a computer program is stored,

The computer program is executed by the processor to implement any method for invoking tasks in the blockchain as described above.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by program instructions related to hardware. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps including the above method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features thereof can be equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the embodiments of the present invention. scope.

Claims (16)

1. A method for invoking tasks in a blockchain, comprising: Send the identification of the task and the execution condition to the server; wherein, the execution condition of the task is determined when the task is created; The target task identifier sent by the server is received, and a corresponding task is executed according to the target task identifier; the target task identifier is determined by the server according to the task identifier and the execution condition. 2. The method of claim 1, further comprising: receiving key information corresponding to the task sent by the user terminal; The task identifier corresponding to the task is determined according to a preset rule, and the task identifier and the key information are stored in the smart contract. 3. The method according to claim 2, wherein the key information at least comprises: Method identification, the execution condition, and execution parameters. 4. The method according to claim 2, wherein the task identifier is a number; the determining the task identifier corresponding to the task according to a preset rule comprises: Acquire the existing maximum task identification in the smart contract, and if the maximum task identification is less than a preset upper limit value, determine the task identification corresponding to the task according to an increment rule. 5. The method according to claim 4, wherein the determining the task identifier corresponding to the task according to an incremental rule comprises: Add 1 to the maximum task identification to obtain the task identification corresponding to the task. 6. The method according to claim 4 or 5, characterized in that, if the maximum task identification is equal to a preset upper limit value, the existing minimum task identification in the smart contract is obtained, and if the minimum task identification is If it is greater than the preset lower limit value, the task identifier corresponding to the task is determined according to the decreasing rule. 7. The method according to claim 6, wherein the determining the task identifier corresponding to the task according to a decrement rule comprises: The task identifier corresponding to the task is obtained by subtracting 1 from the minimum task identifier. 8. The method according to claim 3, wherein the performing the corresponding task according to the target task identifier comprises: Acquire the key information corresponding to the target task identifier in the smart contract; judging whether the execution conditions included in the key information are satisfied; If so, run the method identification corresponding method included in the key information based on the execution parameter in the key information. 9. The method according to any one of claims 1-5, 7, and 8, wherein the execution condition includes execution time and/or block height. 10. A method for invoking tasks in a blockchain, comprising: Receive the task identifier and execution condition sent by the blockchain platform; wherein, the execution condition of the task is determined when the task is created; The target task identifier is determined according to the task identifier and the execution condition, and the target task identifier is sent to the blockchain platform, so that the blockchain platform executes the task corresponding to the target task identifier. 11. The method according to claim 10, wherein the determining the target task identifier according to the task identifier and the execution condition comprises: The execution conditions are traversed according to the preset frequency, the satisfied execution conditions are determined, and the corresponding task identifier is determined as the target task identifier. 12. The method according to claim 10 or 11, wherein the execution condition includes execution time and/or block height. 13. A device for invoking tasks in a blockchain, comprising: A sending module, used for sending the identification of the task and the execution condition to the server; wherein, the execution condition of the task is determined when the task is created; The first receiving module is used to receive the target task identification sent by the server, and execute the corresponding task according to the target task identification; the target task identification is determined by the server according to the task identification and the execution condition. . 14. A device for invoking tasks in a blockchain, comprising: a receiving module, configured to receive the task identifier and execution condition sent by the blockchain platform; wherein, the execution condition of the task is determined when the task is created; A determination module, configured to determine the target task identifier according to the task identifier and the execution condition, and send the target task identifier to the blockchain platform, so that the blockchain platform executes the target task identifier corresponding to the task. 15. A device for invoking tasks in a blockchain, comprising: memory; processor; and Computer program; wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any of claims 1-9 or 10-12. 16. A computer-readable storage medium, characterized in that a computer program is stored thereon, The computer program is executed by a processor to implement the method of any of claims 1-9 or 10-12.

Images