WO2023207078A1 - Data processing method and apparatus, electronic device, and storage medium - Google Patents

Abstract

A data processing method and apparatus, an electronic device, and a storage medium. The method is applied to a first node device that is deployed with a first blockchain node, and an off-chain calculation contract maintains the execution logic of a node device where each participant node corresponding to an off-chain calculation task is located in the off-chain calculation task. The method comprises: when an authorization application event generated by an off-chain calculation contract is monitored and it is determined that a first blockchain node belongs to first participant nodes, obtaining the first execution logic of a first node device in an off-chain calculation task; and examining and approving the first execution logic to generate a first authorization result corresponding to the off-chain calculation task, and initiating a first authorization transaction carrying the first authorization result to the off-chain calculation contract, wherein the off-chain calculation contract is used for: in response to an authorization transaction initiated by each participant node, when each authorization result corresponding to the off-chain calculation task is used for representing that authorization is passed, allowing the off-chain calculation contract to generate a task event related to the off-chain calculation task.

Description

A data processing method, device, electronic equipment and storage medium Technical field

The embodiments of the present disclosure belong to the field of blockchain technology, and in particular relate to a data processing method, device, electronic device and storage medium.

Background technique

Blockchain is a new application model of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. In the blockchain system, data blocks are combined into a chained data structure in a chronological manner and are cryptographically guaranteed to be an untamperable and unforgeable distributed ledger. Due to the characteristics of blockchain, such as decentralization, non-tamperable information, and autonomy, blockchain has also received more and more attention and applications.

The blockchain network can undertake off-chain computing tasks based on smart contract definitions. At this time, each node device of each blockchain node in the blockchain network will call the locally deployed off-chain device under the guidance of events generated by the smart contract. The computing engine is used to implement off-chain computing tasks. For collaborative computing tasks, that is, off-chain computing tasks that require multiple node devices to work together, there is often a need for data in a certain node device to be read by an off-chain computing engine in another external node device to provide data. Node devices often need to perform identity confirmation and authentication on the off-chain computing engine as the data demander to ensure that data is only provided to legitimate off-chain computing engines. However, this identity-based authentication mechanism makes the authorized chain The lower computing engine can obtain the data in the authorizer's node device even when it is not processing collaborative computing tasks. On the one hand, it cannot control the scope and timing of the authorized party's acquisition of data, which poses certain security risks; on the other hand, it cannot distinguish the same chain. The data access rights of the off-chain computing engine in different off-chain computing tasks affect the functional independence of the same off-chain computing engine in different off-chain computing tasks.

Contents of the invention

The purpose of this disclosure is to provide a data processing method, device, electronic device and storage medium.

According to a first aspect of one or more embodiments of this specification, a data processing method is proposed, which is applied to a first node device where a first blockchain node is deployed, and a blockchain network to which the first blockchain node belongs. An off-chain computing contract is deployed, and the off-chain computing contract maintains the execution logic of the node device where each participant node corresponding to the off-chain computing task is located in the off-chain computing task; the method includes: after monitoring When the authorization application event generated by the off-chain computing contract and it is determined that the first blockchain node belongs to the first participant node, obtain the first execution logic of the first node device in the off-chain computing task; An execution logic performs approval to generate the first authorization result corresponding to the off-chain computing task, and initiates the first authorization transaction carrying the first authorization result to the off-chain computing contract through the first blockchain node. The off-chain computing contract is used to allow the off-chain computing contract to be generated in response to the authorization transactions initiated by each participant node and when each authorization result corresponding to the off-chain computing task is used to represent the authorization. Task events related to the off-chain computing task; monitor the first task event generated by the off-chain computing contract, and the first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining the first blockchain When the node belongs to the computing provider node corresponding to the collaborative computing task, the off-chain computing engine deployed by the first node device is called to execute the collaborative computing task, and the off-chain computing engine is used to: perform the collaborative computing During the task, the data read from the second node device by the proxy access engine deployed on the second node device where the data provider node corresponding to the collaborative computing task is located is obtained.

According to the second aspect of one or more embodiments of this specification, a data processing method is proposed, which is applied to a second node device deployed with a second blockchain node, and a blockchain network to which the second blockchain node belongs. An off-chain computing contract is deployed, and the off-chain computing contract maintains the execution logic of the node device where each participant node corresponding to the off-chain computing task is located in the off-chain computing task; the method includes: after monitoring When the authorization application event generated by the off-chain computing contract and it is determined that the second blockchain node belongs to the second participant node, obtain the second execution logic of the second node device in the off-chain computing task; The second execution logic performs approval to generate a second authorization result corresponding to the off-chain computing task, and initiates a second authorization transaction carrying the second authorization result to the off-chain computing contract through the second blockchain node. The off-chain computing contract is used to allow the off-chain computing contract to be generated in response to the authorization transactions initiated by each participant node and when each authorization result corresponding to the off-chain computing task is used to represent the authorization. Task events related to the off-chain computing task; monitor the first task event generated by the off-chain computing contract, and the first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining the second blockchain When the node belongs to the data provider node corresponding to the collaborative computing task, the proxy access engine deployed on the second node device is called to execute the collaborative computing task, and the proxy access engine is used to: execute the collaborative computing task. During the process, the data read from the second node device is provided to an off-chain computing engine deployed on the first node device where the computing provider node corresponding to the collaborative computing task is located.

According to the third aspect of one or more embodiments of this specification, a data processing device is proposed, which is applied to a first node device where a first blockchain node is deployed, and a blockchain network to which the first blockchain node belongs. An off-chain computing contract is deployed, and the off-chain computing contract maintains the execution logic of the node equipment of each participant node corresponding to the off-chain computing task in the off-chain computing task; the device includes: a first execution A logical acquisition unit configured to acquire the off-chain computing tasks of the first node device when the authorization application event generated by the off-chain computing contract is monitored and the first blockchain node is determined to belong to the first participant node. The first execution logic in The off-chain computing contract initiates the first authorization transaction carrying the first authorization result. The off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, each authorization corresponding to the off-chain computing task The results are used to represent that when authorization is passed, the off-chain computing contract is allowed to generate task events related to the off-chain computing task; the data acquisition unit is used to monitor the first task event generated by the off-chain computing contract. A task event corresponds to a collaborative computing task related to the off-chain computing task; when it is determined that the first blockchain node belongs to the computing provider node corresponding to the collaborative computing task, the off-chain device deployed by the first node device is called. The computing engine executes the collaborative computing task, and the off-chain computing engine is configured to: during the process of executing the collaborative computing task, obtain the data provider node corresponding to the collaborative computing task and deploy it on the second node device. The proxy access engine reads the data from the second node device.

According to the fourth aspect of one or more embodiments of this specification, it is proposed that a data processing device is applied to a second node device deployed with a second blockchain node, and the blockchain network to which the second blockchain node belongs is deployed There is an off-chain computing contract, and the off-chain computing contract maintains the execution logic of the node equipment of each participant node corresponding to the off-chain computing task in the off-chain computing task; the device includes: second execution logic An acquisition unit, configured to acquire the performance of the second node device in the off-chain computing task after monitoring the authorization application event generated by the off-chain computing contract and determining that the second blockchain node belongs to the second participant node. The second execution logic; the second authorized transaction initiating unit, used to approve the second execution logic to generate the second authorization result corresponding to the off-chain computing task, and send the off-chain information to the off-chain through the second blockchain node. The computing contract initiates a second authorization transaction carrying a second authorization result. The off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, calculate each authorization result corresponding to the off-chain computing task. Both are used to represent that when authorization is passed, the off-chain computing contract is allowed to generate task events related to the off-chain computing task; the data providing unit is used to monitor the first task event generated by the off-chain computing contract, the first The task event corresponds to the collaborative computing task related to the off-chain computing task; when it is determined that the second blockchain node belongs to the data provider node corresponding to the collaborative computing task, the proxy access engine deployed by the second node device is called Execute the collaborative computing task, and the proxy access engine is configured to: during the process of executing the collaborative computing task, provide data read from the second node device to the computing provider node corresponding to the collaborative computing task. The off-chain computing engine deployed on the first node device.

According to a fifth aspect of one or more embodiments of this specification, an electronic device is proposed, including: a processor; a memory for storing executable instructions by the processor; wherein the processor executes the executable instructions To implement the method described in the first aspect or the second aspect.

According to the sixth aspect of one or more embodiments of this specification, a computer-readable storage medium is proposed, which stores computer instructions. When the instructions are executed by a processor, the method described in the first or second aspect is implemented. A step of.

In the embodiment of this specification, after listening to the authorization application event generated by the off-chain computing contract, the node device where each participant node corresponding to the off-chain computing task is located will separately review the execution logic of each off-chain computing task. Generate authorization results for off-chain computing tasks, and initiate authorization transactions carrying respective authorization results to the off-chain computing contract to complete the authorization of off-chain computing tasks. After completing the authorization of off-chain computing tasks, the off-chain computing contract Only then will it be allowed to generate task events related to off-chain computing tasks, thereby guiding each node device to perform collaborative computing tasks related to off-chain computing tasks through the event listening mechanism, so that the second node device where the data provider node is located can access the engine through the proxy The data read from the second node device is provided to the first node device where the computing provider node is located, thereby limiting data interaction between node devices to the execution of authorized off-chain computing tasks. On the one hand, The scope and timing of data acquisition by data demanders are limited to the execution logic of authorized off-chain computing tasks, reducing security risks; on the other hand, the same off-chain computing engine can participate in different execution logics in different off-chain computing tasks. , which means that the data access rights of the same off-chain computing engine in different off-chain computing tasks can be designed differently, so the functional independence of the same off-chain computing engine in different collaborative computing tasks can be achieved.

Description of the drawings

In order to explain the technical solutions of the embodiments of this specification more clearly, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some of the embodiments recorded in this specification. , for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a flow chart of a data processing method provided by an exemplary embodiment.

Figure 2 is a flow chart of another data processing method provided by an exemplary embodiment.

Figure 3 is a schematic diagram of a node device interaction scenario provided by an exemplary embodiment.

Figure 4 is a schematic structural diagram of a device provided by an exemplary embodiment.

Figure 5 is a block diagram of a data processing device provided in an exemplary embodiment.

FIG. 6 is a block diagram of another data processing device provided by an exemplary embodiment.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described The embodiments are only some of the embodiments of this specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of this specification.

Figure 1 is a flow chart of a data processing method provided by an exemplary embodiment. This method is applied to the first node device deployed with the first blockchain node. The blockchain network to which the first blockchain node belongs is deployed with an off-chain computing contract. The off-chain computing contract maintains a corresponding off-chain computing task. The execution logic of the node device where each participant node is located in the off-chain computing task; the method includes S102 to S106.

S102: After monitoring the authorization application event generated by the off-chain computing contract and determining that the first blockchain node belongs to the first participant node, obtain the first node device in the off-chain computing task. Execute logic.

The data processing method involved in the embodiments of this specification is specifically applied to the first calling engine deployed on the first node device. The first calling engine is responsible for monitoring events generated by off-chain computing contracts, managing the orderly progress of off-chain computing tasks, Functions such as calling the resource engine on the first node device and initiating transactions to off-chain computing contracts are the connectors between on-chain resources and off-chain resources.

In the embodiment of this specification, the authorization application event records the description information of each participant node corresponding to the off-chain computing task. Each participant node corresponding to the off-chain computing task refers to each participant involved in executing the off-chain computing task. Each blockchain node is deployed separately in the blockchain network where the node device is located. It is easy to understand that not all blockchain nodes in the blockchain network belong to the participant nodes corresponding to the off-chain computing tasks, but the off-chain computing tasks The corresponding participant nodes must belong to the blockchain nodes in the blockchain network. After listening to the authorization application event, the first node device can determine the first zone by checking whether the identification information of the first blockchain node deployed by itself is included in the description information of each participant node recorded in the authorization application event. Whether the blockchain node is a participant node corresponding to the off-chain computing task. For example, when the first node device checks that the identification information of the first blockchain corresponds to the description information of the first participant node among the participant nodes, it will determine that the first blockchain node belongs to the first participant node; and when it is checked that the identification information of the first blockchain does not correspond to the description information of any of the participant nodes, it will be determined that the first blockchain node does not belong to the off-chain computing task The corresponding participant node.

When the first node device determines that the first blockchain node belongs to the first participant node, the first node device determines that it needs to participate in the execution of off-chain computing tasks in order to be able to know in advance the subsequent execution of the chain by the first node device. The first node device further acquires the first execution logic of the first node device in the off-chain computing task. The first execution logic involved in the embodiments of this specification includes: the calling status of each resource engine deployed on the first node device and/or the data interaction status between each resource engine and other resource engines deployed on other node devices. . Since off-chain computing tasks often involve multiple node devices participating in the execution, each node device participating in the execution will assume relatively independent task execution logic, so that the off-chain computing task can be completed through the cooperation of each node device. Therefore, the execution logic of each participant node device (node device with a participant node corresponding to the off-chain computing task) in the off-chain computing task can be regarded as part of the overall execution logic of the off-chain computing task. For example, the first execution logic of the first node device in the off-chain computing task includes how the first node device should call when it monitors various task events related to the off-chain computing task generated by the off-chain computing contract. Each resource engine (including off-chain computing engine, data engine, etc.) deployed locally on the first node device, and what kind of data interaction guidance information needs to be carried in the corresponding call request when calling these resource engines to instruct the local resource engine What kind of data is exchanged with which resource engines deployed on which other node devices? By understanding its first execution logic in the off-chain computing task, the first node device can learn how it should participate in the execution of the off-chain computing task, and the relationship between it and other node devices in the process of participating in the execution of the off-chain computing task. The data interaction situation provides a material basis for subsequent approval of off-chain computing tasks.

In the embodiment of this specification, the off-chain computing contract is used to trigger the generation of the authorization application event during the initialization phase of successful deployment or in response to an authorization application transaction. In the embodiment of this specification, when the off-chain computing contract is successfully deployed in the blockchain network, the off-chain computing contract will trigger the execution of the initialization program, which includes generating an authorization application event, so that each node's After listening to the authorization application event, the device returns the authorization result for the off-chain computing task through the transaction callback mechanism. In addition, you can also actively initiate an authorization application transaction to the off-chain computing contract, so that the off-chain computing contract triggers and generates an authorization application event in response to the authorization application transaction to be monitored by each node device, so that the chain can be authorized when there is an authorization requirement. The off-chain computing tasks are authorized multiple times to deal with occasions where the legitimacy of the off-chain computing tasks needs to be re-determined, such as the addition of new participating nodes and the update of off-chain computing tasks.

In one embodiment, the authorization application event includes the execution logic of the node device where each participant node is located in the off-chain computing task; the acquisition of the first node device in the off-chain computing task The first execution logic includes: reading the first execution logic of the first node device in the off-chain computing task from the authorization application event.

In the embodiment of this specification, the authorization application event records the execution logic in the off-chain computing task of each node device where all the participant nodes participating in the off-chain computing task are respectively located. Specifically, The authorization application event records the identification information of each participant node and the corresponding execution logic, and each participant node device reads its own corresponding execution logic through the identification information of the blockchain node deployed by itself, such as the first The node device can match the first execution logic corresponding to the identification information of the first blockchain node from the authorization application event according to the identification information of the first blockchain node, thereby reading the first execution logic from the authorization application event. come out.

In another embodiment, obtaining the first execution logic of the first node device in the off-chain computing task includes: initiating an execution logic query transaction to the off-chain computing contract, and monitoring the off-chain computing contract. In response to the execution logic query event generated by the execution logic query transaction, the first execution logic of the first node device in the off-chain computing task is read from the execution logic query event, and the execution logic query event record There is the first execution logic of the first node device in the off-chain computing task or the execution logic of the node device where each participant node is located in the off-chain computing task.

In the embodiment of this specification, the authorization application event does not record any execution logic related to the off-chain computing task. After listening to the authorization application event, the first node device will use it as a trigger method to instruct the first node device to actively Obtain its first execution logic in the off-chain computing task. The first node device can actively initiate an execution logic query transaction to the off-chain computing contract, so that the off-chain computing contract generates an execution logic query event in response to the execution logic query transaction, and sends the execution logic query exchange request maintained by the off-chain computing contract The obtained execution logic is recorded in the execution logic query event for the first node device to monitor and read therefrom to obtain the first execution logic of the first node device in the off-chain computing task. In the embodiment of this specification, the execution logic obtained by the execution logic query exchange request may be the first execution logic of the first node device in the off-chain computing task, or it may be the first execution logic of all participating node devices in the off-chain computing task. Each execution logic.

The execution logic query transaction involved in the embodiment of this specification may be a consensus transaction or a local transaction. When executing a logical query transaction is a consensus transaction, executing a logical query transaction requires consensus on the blockchain network. All blockchain nodes in the blockchain network will execute the transaction and generate corresponding execution logic query events. , so each node device can monitor the execution logical query event; and when the execution logical query transaction is a local transaction, the execution logical query transaction will not be agreed on the blockchain network, that is, only the first node device is deployed The first blockchain node will call the off-chain computing contract maintained by the first blockchain node to execute the execution logic query transaction, and the execution logic query event generated will only be monitored internally by the first node device, and It will not be monitored by other node devices.

In the embodiment of this specification, the off-chain computing contract will verify the identity of the initiator who executes the logic query transaction, so that the initiating node device can only request to obtain its own execution logic in the off-chain computing task, but cannot request to obtain other The execution logic of the node device, for example, the first node device can only initiate a request to obtain the execution logic query transaction of the first execution logic. By setting the execution logic query transaction as a local transaction, and applying the identity verification of the off-chain computing contract involved in the embodiment of this description and the mechanism to limit the acquisition of execution logic requests, each participant node device can only query Its own execution logic in off-chain computing tasks cannot be queried for the execution logic of other node devices other than itself in off-chain computing tasks, so that each participating node device cannot fully understand the overall execution of off-chain computing tasks. Logically, this information isolation method has the effect of reducing security risks.

S104: Approval of the first execution logic to generate the first authorization result corresponding to the off-chain computing task, and initiate the first authorization carrying the first authorization result to the off-chain computing contract through the first blockchain node Transaction, the off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, and when each authorization result corresponding to the off-chain computing task is used to represent the authorization, allow the chain to The off-chain computing contract generates task events related to the off-chain computing task.

In the embodiment of this specification, after acquiring the first execution logic, the first node device can approve the first execution logic by calling the approval system deployed on the first node device to generate a first execution logic for the first execution logic. The authorization result is used as the first authorization result corresponding to the off-chain computing task. When the first node device approves the first execution logic, it can determine whether the first node device supports the execution of the first execution logic based on its predefined data confidentiality policy and resource holdings, that is, when determining the deployment of the first node device The resource engine can satisfy the calling situation of each resource engine involved in the first execution logic, and/or the data privacy policy of the first node device is not consistent with the first node device involved in the first execution logic and/or the When the data interaction between each resource engine and other resource engines deployed by other node devices conflicts, the first authorization result corresponding to the off-chain computing task generated by the first node device is used to represent the pair of the first node device. The off-chain computing task authorization is passed, otherwise the first authorization result is used to indicate that the first node device fails to authorize the off-chain computing task.

After obtaining the first authorization result, the first node device will further initiate a first authorization transaction carrying the first authorization result to the off-chain computing contract through the first blockchain node. In addition, the first node Other participating nodes other than the device will also generate corresponding authorization results respectively, and each initiate an authorization transaction carrying the authorization result corresponding to the off-chain computing task to the off-chain computing contract. The off-chain computing contract responds to each authorized transaction and maintains each authorization result carried by these authorized transactions. When the off-chain computing task maintains the data returned from each participant node device where all the participant nodes corresponding to the off-chain computing task are located, If each authorization result corresponding to the off-chain computing task is used to represent that the off-chain computing task is authorized, the status of the off-chain computing task will be updated to authorized, allowing off-chain execution Computing tasks, which is reflected at the contract level by allowing the off-chain computing contract to generate task events related to the off-chain computing tasks. Specifically: when the status of the off-chain computing tasks is unauthorized, even if The off-chain computing contract is called by the exchange corresponding to the off-chain computing task, and the off-chain computing contract will not respond to the transaction to generate any task events related to the off-chain computing task; and the status of the off-chain computing task is If authorized, if the off-chain computing contract is called by the exchange corresponding to the off-chain computing task, the off-chain computing contract will respond to the transaction normally to generate task events related to the off-chain computing task, thereby passing the event listening mechanism Guide each participant's node equipment to perform off-chain computing tasks.

In the embodiment of this specification, each participant node device only approves the corresponding part of the execution logic in the off-chain computing tasks that it participates in, without paying attention to the execution logic of other node devices, realizing a method for involving multiple nodes. The distributed approval authorization for off-chain computing tasks that devices jointly participate in executes, on the one hand, reduces the approval burden on each participating node device, and on the other hand, it can also achieve information isolation. Since off-chain computing tasks can only be executed after being approved and authorized, this allows each participant's node device to follow the requirements of the relevant task events when the off-chain computing contract generates task events related to the off-chain computing tasks. Directly execute relevant task logic without repeatedly verifying whether the local data privacy policy or resource holdings support the execution of relevant task logic.

S106: Monitor the first task event generated by the off-chain computing contract. The first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the first blockchain node belongs to the collaborative computing task corresponding In the case of a computing provider node, the off-chain computing engine deployed by the first node device is called to execute the collaborative computing task. The off-chain computing engine is used to: obtain the collaboration during the process of executing the collaborative computing task. The proxy access engine deployed on the second node device where the data provider node corresponding to the computing task is located accesses the data read from the second node device.

In the embodiment of this specification, the off-chain computing contract is an on-chain carrier used to carry off-chain computing tasks. The off-chain computing contract defines several sub-tasks included in the off-chain computing tasks, which are used to describe an off-chain computing task. The data flow direction and the computing collaboration process of each node device. Since the off-chain computing contract is deployed on the blockchain network, the participant nodes of the off-chain computing tasks defined by the off-chain computing contract are limited to not exceeding the scope of each blockchain node in the blockchain network. Obviously, multiple off-chain computing contracts can be deployed in the same blockchain network, and the number and performance of the participant nodes involved in different off-chain computing contracts can be flexibly configured, which makes it possible to rely on the same blockchain The network can realize the deployment of off-chain computing tasks with different task types, task requirements and task scales.

In order to explain how the off-chain computing contract guides the implementation of its defined off-chain computing tasks, the following will briefly introduce the implementation logic of off-chain computing tasks through the operation process of a typical off-chain computing contract. Users can generate the code of the off-chain computing contract through the visual contract orchestration system and deploy the off-chain computing contract in the blockchain network, so that the off-chain computing contract defines a type of workflow for off-chain computing tasks, which is embodied as Several subtasks with execution-dependent order. After the off-chain computing contract is successfully deployed, users who have the authority to call the off-chain computing contract can create and start an off-chain computing task by initiating a task creation transaction to the off-chain computing contract. The off-chain computing contract will receive After the task creation transaction, a task instance of the off-chain computing task belonging to the initiating user will be created accordingly. The task instance maintains the task completion status of the off-chain computing task, which is specifically reflected in the status of each sub-task under the off-chain computing task. Task completion status. After the off-chain computing contract responds to the task creation transaction and generates the corresponding task instance, it will further trigger the execution of the first sub-task corresponding to the instance, which is reflected in the off-chain computing contract as generating a participant node containing the first sub-task. event, each blockchain node in the blockchain network can listen to this event, and the node devices of those blockchain nodes that determine that they belong to the participant nodes of the first subtask will further call the node device matching the first subtask. A subtask's off-chain computing resources and/or off-chain storage resources are used to execute the first subtask off-chain. Finally, after the execution is completed, the node device where the participant node is located will further calculate the contract to the off-chain. Initiate a result return transaction carrying the execution result of the first subtask, so that the off-chain computing contract updates the task completion status of the corresponding task instance. For example, when the execution result of the first subtask is successful, the off-chain computing contract The task completion status of the first subtask in the corresponding task instance will be marked as completed, thereby triggering the execution of the next batch of subtasks according to the dependency order of each subtask included in the predefined off-chain computing task, and then generating the next batch of subtasks. The participant nodes of a batch of subtasks describe information events for each blockchain node in the blockchain network to monitor. The subsequent process is similar to the aforementioned process of processing the first subtask. As a result, an "off-chain computing contract updates the task completion status → the off-chain computing contract generates sub-task events → the blockchain node listens to the sub-task events and the designated node device executes the sub-task → the node device reports to The result of the sub-task initiated by the off-chain computing contract is returned to the transaction → the off-chain computing contract updates the task completion status" cycle, until the task completion status of all sub-tasks in the task instance in the off-chain computing contract is completed, the determination of the The off-chain computing task corresponding to the task instance has been executed.

It is not difficult to find that the tasks performed by the off-chain computing contract during the execution of the off-chain computing task only include scheduling tasks such as creating task instances, receiving sub-task results, sub-task scheduling and sub-task delivery. In fact, there are no Really execute the actual tasks defined and required by off-chain computing tasks, such as data calculation, data transfer and data storage, and these tasks that consume a large amount of resources are scheduled to be executed off-chain corresponding to each node device, thereby through event monitoring The mechanism and the transaction callback mechanism realize a distributed computing based on the blockchain, so that the off-chain computing tasks are anchored by the off-chain computing contracts on the blockchain, fully ensuring that the entire task execution process is traceable. Utilizing off-chain resources simultaneously enables reliable information interaction and collaborative computing between different node devices relying on the blockchain. In addition, since off-chain computing tasks are defined in the form of contracts and the design of off-chain computing tasks is not affected by on-chain Resource constraints mean that different off-chain computing contracts can be designed to meet different actual needs, and on-chain collaboration methods can be expanded through off-chain resources.

In the embodiment of this specification, the off-chain computing contract maintains a task completion status corresponding to the off-chain computing task. The task completion status is used to describe the completion status of each sub-task included in the off-chain computing task. The blockchain events related to the off-chain computing task include task events corresponding to each sub-task; when the collaborative computing task belongs to the sub-task of the off-chain computing task, the first task is monitored The event includes: monitoring the first task event generated by the off-chain computing contract for the collaborative computing task when the task completion status satisfies the execution conditions corresponding to the collaborative computing task.

In the embodiment of this specification, the off-chain computing task is represented as a corresponding task instance on the off-chain computing contract, and its task completion status is maintained in the corresponding task instance of the off-chain computing contract. Specifically, the task instance maintains various The completion status of the subtask. In the embodiment of this specification, the blockchain events related to the off-chain computing task include task events corresponding to each sub-task and the collaborative computing task belongs to a sub-task of the off-chain computing task. Since the off-chain computing task The execution dependency sequence of each sub-task included in the computing task has been pre-defined, which means that the execution conditions of each sub-task including the collaborative computing task have also been determined, so the off-chain computing contract can be based on the off-chain computing task. The completion status of each sub-task is used to further determine the collaborative computing task that needs to be executed next, thereby initiating a task event for the collaborative computing task. Further, it also includes: when the collaborative computing task is completed, initiating a result return transaction containing the execution result corresponding to the collaborative computing task to the off-chain computing contract through the first blockchain node to update the off-chain The task completion status corresponding to the off-chain computing tasks maintained by the computing contract. As mentioned above, when the first node device executes a subtask by calling resources and completes the execution, it will update the task completion status of the off-chain computing task maintained by the off-chain computing contract by initiating a result return transaction, thereby making the off-chain The computing contract can further determine the next subtask that should be executed based on the execution dependency sequence of each subtask in the off-chain computing task, and generate a task event for the next subtask. In the embodiment of this specification, the entity that monitors the task events generated by the off-chain computing contract and initiates the result return transaction to the off-chain computing contract is specifically the scheduling engine deployed on the first node device.

As mentioned above, the task completion status is updated by the off-chain computing contract in response to the transaction corresponding to the off-chain computing task, wherein the transaction corresponding to the off-chain computing task includes the transaction corresponding to the off-chain computing task. task creation transaction, or a result return transaction initiated by any node device after completing the execution of any of the subtasks. In the embodiment of this specification, the off-chain computing contract maintains the task completion status corresponding to one or more off-chain computing tasks. Normally, an off-chain computing contract only defines one type of off-chain computing task, but multiple task instances corresponding to the off-chain computing task can be created, and each task instance will record the completion of the task corresponding to the task instance. state. Therefore, the creation of multiple task instances maintained on the off-chain computing contract can be triggered by different users by initiating task creation contracts to the off-chain computing contract, or the creation can be triggered by the same user by initiating task creation contracts multiple times. , but these task instances all have the same execution logic, that is, the task types of each task maintained by the off-chain computing contract are the same.

The type of proxy access engine involved in the embodiment of this specification may be a computing engine or a data engine. Among them, the computing engine, also known as the off-chain computing engine, refers to the service or subsystem that provides off-chain computing capabilities for node devices. A computing engine can often undertake one or more types of computing tasks, which is reflected in the Support the computing requirements corresponding to the task; the data engine, also known as the database engine, refers to the core service program used to store, retrieve, process and protect data. The database engine can be used to control access permissions and process transactions quickly, thereby satisfying most of the needs within the enterprise. Requirements for applications that need to process large amounts of data, use a database engine to create a relational database for online transaction processing or online analytical processing of data. This includes creating tables for storing data and database objects for viewing, managing, and securing the data. (such as indexes, views, and stored procedures). Different data engines support different data access methods or accessed data types, which are reflected in the support of data engine requirements corresponding to related subtasks.

In the embodiment of this specification, the first task event for the collaborative computing task generated by the off-chain computing contract and monitored by the first node device records the data provider node and the computing provider corresponding to the collaborative computing task. Description information of the square node. The first task event includes description information of the participating nodes of the collaborative computing task. This description information specifically refers to the identity information of the blockchain node where the node device involved in the execution is located as specified by the collaborative computing task. The participant node corresponding to the collaborative computing task can be determined as the data provider node and/or the computing provider node corresponding to the collaborative computing task according to its corresponding attribute characteristics, where the data provider node corresponding to the collaborative computing task refers to: During the execution of a collaborative computing task involving multiple node devices, a blockchain node in the blockchain network deployed on a node device that needs to provide data to other node devices, the data is used to provide data to other node devices. The off-chain computing engine deployed on the node device is used as the data required to perform the collaborative computing task and/or other subsequent sub-tasks; and the computing provider corresponding to the collaborative computing task refers to: in a network jointly participated by multiple node devices During the execution of the completed collaborative computing task, the blockchain node in the blockchain network deployed on the node device that provides off-chain computing engine resources to perform the actual computing task. It is easy to understand that for any participant node in a collaborative computing task, it can be either a data provider node corresponding to the collaborative computing task, a computing provider node corresponding to the collaborative computing task, or both at the same time. The data provider node and computing provider node corresponding to the collaborative computing task. For example, for a participant node that is both a data provider node and a computing provider node corresponding to a collaborative computing task, the off-chain computing engine on the node device where it is located will execute the collaborative computing task. The local data of the node device and the data on the node device where the data provider node is located will be obtained at the same time for performing the collaborative computing task and/or other subsequent subtasks.

In the embodiment of this specification, the first task event is also recorded with the identification information of the off-chain computing engine participating in executing the collaborative computing task on the first node device where the computing provider node is located, so as to prompt the first node device to perform on-chain When the second node device where the data provider node is located calls the proxy access engine, it should instruct it to send the read data to the off-chain computing engine. In addition, the first task event will also record the task identifiers of off-chain computing tasks and collaborative computing tasks, thereby distinguishing different tasks and subtasks. This is mainly to facilitate any subsequent node device to complete the collaborative computing task and return When the result return transaction is passed, it can be correctly identified as the result of the collaborative computing task in the off-chain computing task, so that the off-chain computing contract can correctly update the completion status of the collaborative computing task in the task instance corresponding to the off-chain computing task through the result return transaction, so as to To deal with the situation where the same task contains multiple subtasks and the same off-chain computing annual contract creates task instances of multiple off-chain computing tasks at the same time. Of course, the collaborative computing task also records the calculations and data transfer operations it needs to perform, and specifies the source of the required data. This information is used to inform each node device of the task type and implementation method of the collaborative computing task, thereby guiding After determining the task type of the collaborative computing task and its implementation method corresponding to the callable resources, the node device executes the collaborative computing task as expected for the collaborative computing task.

In the embodiment of this specification, since the description information of the computing provider node is recorded in the first task event, the first node device can determine that the identification information of the first blockchain node deployed by itself is included in When the description information of the computing provider node recorded in the first task event is determined, the first blockchain node belongs to the computing provider node; and when it is determined that the identification information of the first blockchain node is not included in In the case of the description information of the computing provider node recorded in the first task event, it is determined that the first blockchain node does not belong to the computing provider node.

In the embodiment of this specification, the first node device only calls the off-chain computing engine to execute the collaborative computing task after determining that the first blockchain node belongs to the computing provider node corresponding to the collaborative computing task. Otherwise, if the first node device does not belong to the computing provider node corresponding to the collaborative computing task, the first node device will not call the off-chain computing engine to execute the collaborative computing task. At the same time, the first task event also records the identification information and/or communication address of the proxy access engine. The first node device writes the identification information and/or communication address of the proxy access engine into the call request for calling the off-chain computing engine. , and sends the call request to the off-chain computing engine to call the off-chain computing engine. The off-chain computing engine thus learns the identification information of the data provider node corresponding to the collaborative computing task and the second node device used to provide data. The identification information and/or communication address of the deployed proxy access engine, so that it can know that it needs to obtain the data on the second node device from the proxy access engine.

In the embodiment of this specification, the proxy access engine and the off-chain computing engine can only execute one subtask/collaborative computing task at the same time. Therefore, the proxy access engine can only perform the collaborative computing task while executing the collaborative computing task. Only within the time period, it has the permission to provide the specific range of data specified by the collaborative computing task, and other off-chain computing engines can only provide data to the agent during the period when they are jointly executing the same collaborative computing task with the agent access engine. The access engine requests specific data, but cannot obtain data from the proxy access engine at any time, nor can it obtain any data from the proxy access engine. This implements an access time limit and access scope limit for data based on collaborative computing tasks.

In the embodiment of this specification, after listening to the authorization application event generated by the off-chain computing contract, the node device where each participant node corresponding to the off-chain computing task is located will separately review the execution logic of each off-chain computing task. Generate authorization results for off-chain computing tasks, and initiate authorization transactions carrying respective authorization results to the off-chain computing contract to complete the authorization of off-chain computing tasks. After completing the authorization of off-chain computing tasks, the off-chain computing contract Only then will it be allowed to generate task events related to off-chain computing tasks, thereby guiding each node device to perform collaborative computing tasks related to off-chain computing tasks through the event listening mechanism, so that the second node device where the data provider node is located can access the engine through the proxy The data read from the second node device is provided to the first node device where the computing provider node is located, thereby limiting data interaction between node devices to the execution of authorized off-chain computing tasks. On the one hand, The scope and timing of data acquisition by data demanders are limited to the execution logic of authorized off-chain computing tasks, reducing security risks; on the other hand, the same off-chain computing engine can participate in different execution logics in different off-chain computing tasks. , which means that the data access rights of the same off-chain computing engine in different off-chain computing tasks can be designed differently, so the functional independence of the same off-chain computing engine in different collaborative computing tasks can be achieved.

In the embodiment of this specification, the off-chain computing engine will specify the task logic of the collaborative computing task that it needs to perform when called by the first node, which includes that the off-chain computing task needs to be deployed to the corresponding second node device. The process of obtaining data by the proxy access engine. Therefore, the off-chain computing engine can obtain the data read by the proxy access engine from the second node device through at least the following two strategies during the execution of the collaborative computing task.

In one embodiment, the off-chain computing engine will not actively request data from the proxy access engine during the execution of collaborative computing tasks, but will wait for the proxy access engine to actively push data to the off-chain computing engine. In this case, during the process of the proxy access engine executing the collaborative computing task in response to the call from the second node device, the data specified by the collaborative computing task can be read from the second node device according to the requirements of the collaborative computing task, and sent to The off-chain computing engine under the first node device specified by the collaborative computing task actively pushes the data, so that the off-chain computing engine obtains the data. Since this embodiment adopts a mechanism in which the proxy access engine actively pushes data during the execution of collaborative computing tasks, the proxy access engine, as the data holder and authorizer, generates the first task event based on the trusted off-chain computing contract. In order to know the relevant data acquisition requirements of the off-chain computing engine deployed on the first node device, and have the ability to actively provide data, this makes the agent computing engine do not need to perform repeated authentication when transmitting data to the outside, but directly follows the collaborative computing task Safe data interaction can be achieved by executing collaborative computing tasks according to the requirements. On the one hand, the time for transmitting data to the outside is limited to the period of executing the collaborative computing task. On the other hand, the scope of externally transmitted data by the agent computing engine is limited by the collaborative computing task. limits.

In another embodiment, the off-chain computing engine will actively send a data access request to the proxy access engine to obtain the data on the second node device during the execution of the collaborative computing task. However, this requires the proxy access engine to verify the data access request. Whether it complies with regulations and whether it is for necessary data interaction in collaborative computing tasks, and only when the proxy access engine determines that the data access request received complies with the execution logic of the collaborative computing task, responds to the data access request and transmits data outwards Only when it is a normal part of the process of executing collaborative computing tasks will it respond to data access requests and provide data to the off-chain computing engine.

Optionally, the off-chain computing engine is also configured to: in the process of executing the collaborative computing task, send a data access request and an authorization credential corresponding to the data access request to the proxy access engine; the proxy The access engine is configured to: receive the data access request and the authorization credential during the execution of the collaborative computing task, and determine that the authorization credential is used to indicate that the data access request is for the collaborative computing task. In the case of , the data read from the second node device is sent to the off-chain computing engine.

In the embodiment of this specification, if the off-chain computing engine needs to obtain data in the second node device during the execution of the collaborative computing task, it will send a data access request to the proxy access engine deployed on the second node device. The data requested by the data access request is within the scope of the required data defined by the collaborative computing task. At the same time, in order to convince the proxy access engine that the data access request is issued for the execution of the collaborative computing task, the off-chain computing engine will also The authorization credentials corresponding to the data access request are synchronously sent to the proxy access engine to prove that the data access request is issued based on the process of executing the collaborative computing task. After the first task event is monitored by the second node device, it will also trigger the second node device to call the locally deployed proxy access engine to perform the collaborative computing task. During the process of executing the collaborative computing task, the proxy access engine will The requirements of the computing task provide specific data on the second node device to the off-chain computing engine in the first node device. Since this embodiment adopts a request-response passive data push mechanism, the proxy access engine performs collaborative computing. During the task, the off-chain computing engine specified by the collaborative computing task will be opened to access the data specified by the collaborative computing task on the second node device. After receiving the data access request and authorization credentials sent by the off-chain computing engine, the proxy access engine verifies the authorization credentials. If it is determined that the data access request is for the collaborative computing task, it is the data access request. is issued during the execution of the collaborative computing task, then the proxy access engine will respond to the data access request, and within the range of available data defined by the collaborative computing task, the data access request specified by the The data is read from the second node device and returned to the off-chain computing engine. If the authorization credential corresponding to the data access request is not received or the received authorization credential cannot characterize the data access request for If the collaborative computing task is performed, the proxy access engine will not respond to the data access request and provide local data to the off-chain computing engine. The embodiment of this specification verifies the authorization credentials, so that under the passive push mechanism, the proxy access engine can effectively distinguish whether the received data access request is legal, and then reject the response except for the purpose of performing the collaborative computing task. The data access request of the off-chain computing engine realizes secure data interaction.

Optionally, the first task event records the identification information of the collaborative computing task, and the authorization voucher includes the identification information. The proxy access engine is used to, when the authorization voucher includes the identification information, The authorization credentials are determined to indicate that the data access request is for the collaborative computing task. In the embodiment of this specification, since the first task event can be monitored by the first node device and the second node device at the same time, the identification information of the collaborative computing task can be carried in the first task event, so that the first Both the node device and the second node device have obtained the identification information of the collaborative computing task. At the same time, the identification information of different collaborative computing tasks is different from each other. Therefore, the identification information can be used to determine the target between the off-chain computing engine and the proxy access engine. Consensus information on the collaborative computing task. The proxy access engine determines that the authorization credential is used to indicate that the data access request is directed to the collaborative computing task by determining that the authorization credential contains the identification information.

Optionally, the first task event records the task public key and task private key ciphertext corresponding to the collaborative computing task, wherein the task private key ciphertext is obtained by using the public key pair corresponding to the off-chain computing engine. The task private key corresponding to the collaborative computing task is encrypted; the authorization certificate includes the first digital signature obtained by using the task private key to sign the data access request, and the task private key is calculated by the off-chain The engine uses the private key corresponding to the off-chain computing engine to decrypt the task private key ciphertext; the proxy access engine is used to use the task public key recorded in the first task event to decrypt the first task public key. If the digital signature verification is successful, it is determined that the authorization certificate is used to indicate that the data access request is directed to the collaborative computing task. In the embodiment of this specification, when the off-chain computing contract generates the first task event corresponding to the collaborative computing task, it will synchronously generate a public-private key pair for the collaborative computing task, which is called the task of the collaborative computing task. Public key and task private key, where the task public key is directly recorded in the first task event and is learned by each node device through the event listening mechanism, while the task private key is cross-domain through the needs involved in the collaborative computing task. The public key corresponding to the off-chain computing engine that obtains the data is encrypted and recorded in the first task event, that is, it is known to each node device in the form of task private key ciphertext. However, due to the above mentioned in the first node device The off-chain computing engine owns the private key corresponding to the off-chain computing engine used to decrypt the task private key ciphertext. Therefore, after the first node device reads the task private key ciphertext in the first task event, , will be put into the call request for calling the off-chain computing engine, so that the off-chain computing engine can decrypt the task private key through its own private key during the execution of the collaborative computing task. ciphertext to obtain the task private key. The only off-chain computing task that can obtain the task private key signs the data access request through the task private key to obtain the first digital signature as the authorization certificate. After receiving the authorization certificate, the proxy access engine After the first digital signature is obtained, the first digital signature is verified using the task public key read by the first node device in the first task event. If the verification is successful, the authorization certificate is determined. Used to indicate that the data access request is directed to the collaborative computing task. In the embodiment of this specification, since only the off-chain computing engine can obtain the task private key corresponding to the collaborative computing task, once the proxy access engine successfully verifies the first digital signature, it means that the proxy access engine can be convinced that the data access request is Initiated by the off-chain computing engine that owns the private key of the task, the proxy access engine can determine that the data access request is initiated for the collaborative computing task, and the initiator of the data access request must be the Therefore, the proxy access engine does not need to repeatedly verify the identity information of the off-chain computing engine, which speeds up the efficiency of the off-chain computing engine in obtaining cross-domain data in the passive push mechanism.

Optionally, the off-chain computing engine is also configured to: in the process of executing the collaborative computing task, use the private key corresponding to the off-chain computing engine to sign the second number obtained by signing the data access request. The signature is sent to the proxy access engine; the proxy access engine is also configured to: use the public key corresponding to the off-chain computing engine to verify the received second digital signature during the execution of the collaborative computing task. If the signature verification is successful and it is determined that the off-chain computing engine has access rights to the first node device, it is determined that the authorization certificate is valid. In the embodiment of this specification, the off-chain computing engine also needs to prove the validity of its identity to the proxy access engine through a second digital signature. After the proxy access engine passes the verification of the second digital signature, it can confirm that the data access request comes from The off-chain computing engine, so that in the case where the collaborative computing task includes the logic of "providing the off-chain computing engine with the data requested by the data access request", and/or the proxy access engine is based on a pre- If the maintained identity permission-based data access monitoring system determines that "providing the data requested by the data access request to the off-chain computing engine" is allowed, it will confirm that the authorization certificate is valid and further The authorization credentials are verified. The embodiment of this specification combines the traditional identity-based data access permission supply strategy to bring better security to cross-domain data interaction between different node devices.

Figure 2 is a flow chart of another data processing method provided by an exemplary embodiment. This method is applied to a second node device deployed with a second blockchain node. The blockchain network to which the second blockchain node belongs is deployed with an off-chain computing contract. The off-chain computing contract maintains a corresponding off-chain computing task. The execution logic of the node device where each participant node is located in the off-chain computing task; the method includes S202 to S206.

S202: After monitoring the authorization application event generated by the off-chain computing contract and determining that the second blockchain node belongs to the second participant node, obtain the second node device in the off-chain computing task. Execute logic.

S204: Approval of the second execution logic to generate a second authorization result corresponding to the off-chain computing task, and initiate a second authorization carrying the second authorization result to the off-chain computing contract through the second blockchain node. Transaction, the off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, and when each authorization result corresponding to the off-chain computing task is used to represent the authorization, allow the chain to The off-chain computing contract generates task events related to the off-chain computing task.

S206: Monitor the first task event generated by the off-chain computing contract. The first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the second blockchain node belongs to the collaborative computing task corresponding In the case of a data provider node, the proxy access engine deployed on the second node device is called to execute the collaborative computing task, and the proxy access engine is used to: during the process of executing the collaborative computing task, access data from the second node device. The read data is provided to the off-chain computing engine deployed on the first node device where the computing provider node corresponding to the collaborative computing task is located.

When the description information of the data provider node recorded in the first task event includes the identification information of the second blockchain node, it is determined that the second blockchain node belongs to the data provider node. In the embodiment of this specification, the description information of the data provider node corresponding to the collaborative computing task is recorded in the first task event for the collaborative computing task, which means that the second node device can determine the description of the data provider node. If the information contains the identification information of the second blockchain node deployed by itself, it is determined that the second blockchain node to which it is deployed belongs to the data provider node corresponding to the collaborative computing task; and if the data provider node If the description information does not include the identification information of the second blockchain node, the second node device can determine that the second blockchain node deployed by itself does not belong to the data provider node corresponding to the collaborative computing task.

In the embodiment of this specification, the second node device needs to determine that the second blockchain node belongs to the data provider node corresponding to the collaborative computing task before calling the proxy access engine to execute the collaborative computing task; otherwise , if the second node device does not belong to the data provider node corresponding to the collaborative computing task, the second node device will not call the proxy access engine to execute the collaborative computing task. After being called by the second node device, the proxy access engine will learn the identification information of the computing provider node corresponding to the collaborative computing task and the identification information of the off-chain computing engine deployed in the first node device that needs to provide data, thereby indicating The proxy access engine can transmit the data read from the second node device to the corresponding off-chain computing engine.

Figure 3 is a schematic diagram of a node device interaction scenario provided by an exemplary embodiment. As shown in Figure 3, the first node device is deployed with the first blockchain node, the first scheduling engine, the off-chain computing engine and the first data source in the blockchain network, and the second node device is deployed with the blockchain The second blockchain node, the second scheduling engine, the proxy access engine and the second data source in the network.

When the off-chain computing contract generates an authorization application event and the event records the description information of the first blockchain node and the second blockchain node that participate in executing the off-chain computing task, the first scheduling engine will pass the first blockchain The node monitors the authorization application event. Assuming that the authorization application event contains the execution logic of each participating node device in the off-chain computing task, then the first scheduling engine will read from the authorization application event to obtain the participation of the first node device. After executing the first execution logic of the off-chain computing task, and auditing the first execution logic to generate the first authorization result corresponding to the off-chain computing task, initiate an initiative to the off-chain computing contract through the first blockchain node The first authorization transaction carrying the first authorization result; similarly, after listening to the authorization application event, the second scheduling engine can also read from it and obtain the second execution logic of the second node device participating in the execution of off-chain computing tasks. The second execution logic performs auditing to generate a second authorization result corresponding to the off-chain computing task, and initiates a second authorization transaction carrying the second authorization result to the off-chain computing contract through the second blockchain node.

The off-chain computing contract responds to the first authorization transaction and the second authorization transaction, and obtains the first authorization result and the second authorization result carried in it. Assuming that the first authorization result and the second authorization result are both used to represent authorization, then the chain The off-chain computing contract will allow the off-chain computing contract to generate task events related to the off-chain computing task.

After the off-chain computing contract generates the first task event of the collaborative computing task that is one of the sub-tasks of the off-chain computing task, the first task event will be monitored by the first scheduling engine and the second scheduling engine respectively. Assume that the first The task event also records the description information of the data provider node and the computing provider node corresponding to the collaborative computing task, as well as the identification information of the proxy access engine that needs to provide data, the identification information of the off-chain computing engine that needs to obtain the data, The identification information of the data that needs to be provided, where the description information of the data provider node is the identification information of the second blockchain node, and the description information of the calculation provider node is the identification information of the first blockchain node. Therefore, the second scheduling engine can determine that the second node device needs to provide data to the off-chain computing engine in the first node device, so the second scheduling engine will call the proxy access engine to perform the collaborative computing task and obtain it from the second data source. The data is actively transmitted to the off-chain computing engine in the first node device. On the other hand, the first scheduling engine can determine that the off-chain computing engine specified in the first task event deployed in the first node device needs to obtain the data of the second node device, so the first scheduling engine will call the specified off-chain computing engine Execute collaborative computing tasks, for example, the designated off-chain computing engine is a trusted computing engine running in a feasible execution environment, which needs to obtain data from the second node device to complete the relevant trusted computing operations defined in the collaborative computing task, At this time, the trusted computing engine will obtain relevant data sent by the proxy access engine through the network connection with the proxy access engine deployed on the second node device, thereby further performing trusted computing operations to support continued completion of collaborative computing tasks.

Figure 4 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to Figure 4. At the hardware level, the device includes a processor 402, an internal bus 404, a network interface 406, a memory 408 and a non-volatile memory 410. Of course, it may also include hardware required for other functions. One or more embodiments of this specification can be implemented based on software. For example, the processor 402 reads the corresponding computer program from the non-volatile memory 410 into the memory 408 and then runs it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each A logic unit can also be a hardware or logic device.

As shown in Figure 5, Figure 5 is a block diagram of a data processing device provided in this specification according to an exemplary embodiment. The device can be applied in the equipment shown in Figure 4 to implement the technical solution of this specification; so The device is applied to a first node device deployed with a first blockchain node. The blockchain network to which the first blockchain node belongs is deployed with an off-chain computing contract. The off-chain computing contract maintains a corresponding off-chain computing task. The execution logic of the node equipment where each participant node is located in the off-chain computing task; the device includes a first execution logic acquisition unit 501, a first authorized transaction initiation unit 502 and a data acquisition unit 503.

The first execution logic acquisition unit 501 is used to acquire the first node device's information on the first node device when it monitors the authorization application event generated by the off-chain computing contract and determines that the first blockchain node belongs to the first participant node. The first execution logic in off-chain computing tasks.

The first authorized transaction initiating unit 502 is used to approve the first execution logic to generate the first authorization result corresponding to the off-chain computing task, and initiate a transaction carrying the first authorization result to the off-chain computing contract through the first blockchain node. The first authorization transaction of the first authorization result, the off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, each authorization result corresponding to the off-chain computing task is used to represent authorization Under certain circumstances, the off-chain computing contract is allowed to generate task events related to the off-chain computing task.

The data acquisition unit 503 is configured to monitor the first task event generated by the off-chain computing contract. The first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the first blockchain node belongs to the In the case of the computing provider node corresponding to the collaborative computing task, the off-chain computing engine deployed by the first node device is called to execute the collaborative computing task, and the off-chain computing engine is used to: in the process of executing the collaborative computing task , obtain the data read from the second node device by the proxy access engine deployed on the second node device where the data provider node corresponding to the collaborative computing task is located.

Optionally, the authorization application event includes the execution logic of the node device where each participant node is located in the off-chain computing task; the first execution logic acquisition unit 501 is specifically used to: obtain the authorization from the In the application event, the first execution logic of the first node device in the off-chain computing task is read.

Optionally, the first execution logic includes: the calling status of each resource engine deployed on the first node device and/or the data interaction status between each resource engine and other resource engines deployed on other node devices.

Optionally, the first execution logic acquisition unit 501 is specifically configured to: initiate an execution logic query transaction to the off-chain computing contract, and monitor the execution logic query generated by the off-chain computing contract in response to the execution logic query transaction. event, the first execution logic of the first node device in the off-chain computing task is read from the execution logic query event, and the execution logic query event records that the first node device is in the off-chain computing task The first execution logic or the execution logic of the node device where each participant node is located in the off-chain computing task.

Optionally, the off-chain computing contract is used to trigger the generation of the authorization application event during the initialization phase of successful deployment or in response to an authorization application transaction.

Optionally, the off-chain computing contract maintains a task completion status corresponding to the off-chain computing task. The task completion status is used to describe the completion status of each sub-task included in the off-chain computing task. The chain Blockchain events related to the off-chain computing task include task events corresponding to each sub-task; when the collaborative computing task belongs to a sub-task of the off-chain computing task, the first execution logic acquisition unit 501 specifically Used to: monitor the first task event generated by the off-chain computing contract for the collaborative computing task when the task completion status satisfies the execution condition corresponding to the collaborative computing task.

Optionally, the task completion status is updated by the off-chain computing contract in response to a transaction corresponding to the off-chain computing task, where the transaction corresponding to the off-chain computing task includes the transaction corresponding to the off-chain computing task. A task creation transaction, or a result return transaction initiated by any node device after completing the execution of any of the subtasks.

Optionally, description information of the data provider node and the computing provider node is recorded in the first task event.

Optionally, the off-chain computing engine is also configured to: in the process of executing the collaborative computing task, send a data access request and an authorization credential corresponding to the data access request to the proxy access engine; the proxy The access engine is configured to: receive the data access request and the authorization credential during the execution of the collaborative computing task, and determine that the authorization credential is used to indicate that the data access request is for the collaborative computing task. In the case of , the data read from the second node device is sent to the off-chain computing engine.

Optionally, the first task event records the identification information of the collaborative computing task, and the authorization voucher includes the identification information. The proxy access engine is used to, when the authorization voucher includes the identification information, The authorization credentials are determined to indicate that the data access request is for the collaborative computing task.

Optionally, the first task event records the task public key and task private key ciphertext corresponding to the collaborative computing task, wherein the task private key ciphertext is obtained by using the public key pair corresponding to the off-chain computing engine. The task private key corresponding to the collaborative computing task is encrypted; the authorization certificate includes the first digital signature obtained by using the task private key to sign the data access request, and the task private key is calculated by the off-chain The engine uses the private key corresponding to the off-chain computing engine to decrypt the task private key ciphertext; the proxy access engine is used to use the task public key recorded in the first task event to decrypt the first task public key. If the digital signature verification is successful, it is determined that the authorization certificate is used to indicate that the data access request is directed to the collaborative computing task.

Optionally, the off-chain computing engine is also configured to: in the process of executing the collaborative computing task, use the private key corresponding to the off-chain computing engine to sign the second number obtained by signing the data access request. The signature is sent to the proxy access engine; the proxy access engine is also configured to: use the public key corresponding to the off-chain computing engine to verify the received second digital signature during the execution of the collaborative computing task. If the signature verification is successful and it is determined that the off-chain computing engine has access rights to the first node device, it is determined that the authorization certificate is valid.

As shown in Figure 6, Figure 6 is a block diagram of a data processing device provided in this specification according to an exemplary embodiment. This device can be applied to the equipment shown in Figure 4 to implement the technical solution of this specification; so The device is applied to a second node device deployed with a second blockchain node. The blockchain network to which the second blockchain node belongs is deployed with an off-chain computing contract. The off-chain computing contract maintains a corresponding off-chain computing task. The execution logic of the node device where each participant node is located in the off-chain computing task; the device includes a second execution logic acquisition unit 601, a second authorized transaction initiation unit 602 and a data providing unit 603.

The second execution logic acquisition unit 601 is configured to acquire the second node device's information on the second node device when it monitors the authorization application event generated by the off-chain computing contract and determines that the second blockchain node belongs to the second participant node. The second execution logic in off-chain computing tasks.

The second authorized transaction initiating unit 602 is used to approve the second execution logic to generate the second authorization result corresponding to the off-chain computing task, and initiate an authorization carrying the transaction information to the off-chain computing contract through the second blockchain node. For the second authorization transaction of the second authorization result, the off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, each authorization result corresponding to the off-chain computing task is used to represent authorization. Under certain circumstances, the off-chain computing contract is allowed to generate task events related to the off-chain computing task.

The data providing unit 603 is configured to monitor the first task event generated by the off-chain computing contract. The first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the second blockchain node belongs to the In the case of the data provider node corresponding to the collaborative computing task, the proxy access engine deployed on the second node device is called to execute the collaborative computing task. The proxy access engine is used to: during the process of executing the collaborative computing task, The data read from the second node device is provided to an off-chain computing engine deployed on the first node device where the computing provider node corresponding to the collaborative computing task is located.

In the 1990s, improvements in a technology could be clearly distinguished as hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method processes). However, with the development of technology, many improvements in today's method processes can be regarded as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement of a method flow cannot be implemented using hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic functions are determined by the user programming the device. Designers can program themselves to "integrate" a digital system on a PLD, instead of asking chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing, and before compilation The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL), and HDL is not just one kind, but there are many, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used The two are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that by simply logically programming the method flow using the above-mentioned hardware description languages and programming it into the integrated circuit, the hardware circuit that implements the logical method flow can be easily obtained.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, For Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, this disclosure does not exclude that with the development of computer technology in the future, the computer that implements the functions of the above embodiments may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, or a personal digital assistant. , media player, navigation device, email device, game console, tablet, wearable device, or a combination of any of these devices.

Although one or more embodiments of this specification provide method operation steps as described in the embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-inventive means. The sequence of steps listed in the embodiment is only one way of executing the sequence of many steps, and does not represent the only execution sequence. When the actual device or terminal product is executed, it may be executed sequentially or in parallel according to the methods shown in the embodiments or figures (for example, a parallel processor or a multi-thread processing environment, or even a distributed data processing environment). The terms "comprises," "comprises" or any other variation thereof are intended to cover a non-exclusive inclusion such that a process, method, product or apparatus including a list of elements includes not only those elements but also others not expressly listed elements, or also elements inherent to the process, method, product or equipment. Without further limitation, it does not exclude the presence of additional identical or equivalent elements in a process, method, product or apparatus including the stated elements. For example, if the words "first" and "second" are used to express names, they do not indicate any specific order.

For the convenience of description, when describing the above device, the functions are divided into various modules and described separately. Of course, when implementing one or more of this specification, the functions of each module can be implemented in the same or multiple software and/or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. . The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

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

Memory may include non-permanent storage in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may 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), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape, magnetic tape storage, graphene storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transient computer-readable media (transitory media), such as modulated data signals and carrier waves.

It should be understood by those skilled in the art that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, one or more embodiments of the present description may employ a computer program implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. Product form.

One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment. In the description of this specification, reference to the terms "one embodiment," "some embodiments," "an example," "specific examples," or "some examples" or the like means that specific features are described in connection with the embodiment or example. , structures, materials or features are included in at least one embodiment or example of this specification. In this specification, the schematic expressions of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine different embodiments or examples and features of different embodiments or examples described in this specification unless they are inconsistent with each other.

The above descriptions are only examples of one or more embodiments of this specification, and are not intended to limit one or more embodiments of this specification. To those skilled in the art, various modifications and changes may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of the claims.

Claims (17)

1. A data processing method, applied to a first node device deployed with a first blockchain node. The blockchain network to which the first blockchain node belongs is deployed with an off-chain computing contract, and the off-chain computing contract maintains a chain The execution logic of the node device where each participant node corresponding to the off-chain computing task is located in the off-chain computing task; the method includes:

   After monitoring the authorization application event generated by the off-chain computing contract and determining that the first blockchain node belongs to the first participant node, obtain the first execution logic of the first node device in the off-chain computing task ;

   Approving the first execution logic to generate the first authorization result corresponding to the off-chain computing task, and initiating the first authorization transaction carrying the first authorization result to the off-chain computing contract through the first blockchain node, The off-chain computing contract is used to: respond to the authorization transactions initiated by each participant node, and allow the off-chain calculation when each authorization result corresponding to the off-chain computing task is used to represent the authorization. The contract generates task events related to the off-chain computing tasks;

   Monitor the first task event generated by the off-chain computing contract, and the first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the first blockchain node belongs to the computing provider corresponding to the collaborative computing task In the case of a square node, the off-chain computing engine deployed by the first node device is called to execute the collaborative computing task. The off-chain computing engine is used to: obtain the collaborative computing task during the process of executing the collaborative computing task. The proxy access engine deployed on the second node device where the corresponding data provider node is located accesses the data read from the second node device.
2. The method according to claim 1, the authorization application event includes the execution logic of the node device where each participant node is located in the off-chain computing task; the obtaining of the off-chain computing task of the first node device The first execution logic in the computing task includes:

   The first execution logic of the first node device in the off-chain computing task is read from the authorization application event.
3. According to the method of claim 1, the first execution logic includes: the calling status of each resource engine deployed on the first node device and/or the data between each resource engine and other resource engines deployed on other node devices. interaction situation.
4. According to the method of claim 1, said obtaining the first execution logic of the first node device in the off-chain computing task includes:

   Initiate an execution logic query transaction to the off-chain computing contract, monitor the execution logic query event generated by the off-chain computing contract in response to the execution logic query transaction, and read the execution logic query event of the first node device from the execution logic query event. The first execution logic in the off-chain computing task, the execution logic query event records the first execution logic of the first node device in the off-chain computing task or the node device where each participant node is located. Execution logic in the off-chain computing tasks.
5. According to the method of claim 1, the off-chain computing contract is used to trigger the generation of the authorization application event during the initialization phase of successful deployment or in response to an authorization application transaction.
6. According to the method of claim 1, the off-chain computing contract maintains a task completion status corresponding to the off-chain computing task, and the task completion status is used to describe the completion of each sub-task included in the off-chain computing task. status, the blockchain events related to the off-chain computing task include task events corresponding to each sub-task; in the case that the collaborative computing task belongs to the sub-task of the off-chain computing task, the monitoring of the A task event includes:

   Monitor the first task event generated by the off-chain computing contract for the collaborative computing task when the task completion status satisfies the execution conditions corresponding to the collaborative computing task.
7. According to the method of claim 6, the task completion status is updated by the off-chain computing contract in response to a transaction corresponding to the off-chain computing task, wherein the transaction corresponding to the off-chain computing task includes the off-chain computing task. The task creation transaction corresponding to the next computing task, or the result return transaction initiated by any node device after completing the execution of any of the subtasks.
8. According to the method of claim 1, description information of the data provider node and the computing provider node is recorded in the first task event.
9. According to the method of claim 1, the off-chain computing engine is further configured to: in the process of executing the collaborative computing task, send a data access request and an authorization certificate corresponding to the data access request to the proxy access engine;

   The proxy access engine is configured to: receive the data access request and the authorization credential during the execution of the collaborative computing task, and determine that the authorization credential is used to indicate that the data access request is for the In the case of collaborative computing tasks, the data read from the second node device is sent to the off-chain computing engine.
10. The method according to claim 9, the first task event is recorded with identification information of the collaborative computing task, the authorization voucher includes the identification information, and the proxy access engine is configured to include the identification information in the authorization voucher. In the case of information, it is determined that the authorization credentials are used to indicate that the data access request is for the collaborative computing task.
11. According to the method of claim 9, the first task event records the task public key and task private key ciphertext corresponding to the collaborative computing task, wherein the task private key ciphertext corresponds to the off-chain computing engine by using the off-chain computing engine. The public key is obtained by encrypting the task private key corresponding to the collaborative computing task;

    The authorization certificate includes a first digital signature obtained by signing the data access request using the task private key, which is generated by the off-chain computing engine using the corresponding private key pair of the off-chain computing engine. The task private key ciphertext is decrypted and obtained;

    The proxy access engine is configured to determine that the authorization certificate is used to indicate that the data access request is for the first digital signature when the first digital signature is successfully verified using the task public key recorded in the first task event. The collaborative computing task.
12. According to the method of claim 9, the off-chain computing engine is further configured to: use the private key corresponding to the off-chain computing engine to sign the data access request during the execution of the collaborative computing task. The obtained second digital signature is sent to the proxy access engine;

    The proxy access engine is also configured to: use the public key corresponding to the off-chain computing engine to verify the received second digital signature during the execution of the collaborative computing task. When the signature verification is successful and the signature is determined, When the off-chain computing engine has access rights to the first node device, it is determined that the authorization certificate is valid.
13. A data processing method applied to a second node device deployed with a second blockchain node. The blockchain network to which the second blockchain node belongs is deployed with an off-chain computing contract, and the off-chain computing contract maintains a chain. The execution logic of the node device where each participant node corresponding to the off-chain computing task is located in the off-chain computing task; the method includes:

    After monitoring the authorization application event generated by the off-chain computing contract and determining that the second blockchain node belongs to the second participant node, obtain the second execution logic of the second node device in the off-chain computing task ;

    Approving the second execution logic to generate the second authorization result corresponding to the off-chain computing task, and initiating a second authorization transaction carrying the second authorization result to the off-chain computing contract through the second blockchain node, The off-chain computing contract is used to: respond to the authorization transactions initiated by each participant node, and allow the off-chain calculation when each authorization result corresponding to the off-chain computing task is used to represent the authorization. The contract generates task events related to the off-chain computing tasks;

    Monitor the first task event generated by the off-chain computing contract, and the first task event corresponds to the collaborative computing task related to the off-chain computing task; provide data corresponding to the collaborative computing task after determining that the second blockchain node belongs to In the case of a square node, call the proxy access engine deployed on the second node device to execute the collaborative computing task. The proxy access engine is used to: during the process of executing the collaborative computing task, read from the second node device. The obtained data is provided to the off-chain computing engine deployed on the first node device where the computing provider node corresponding to the collaborative computing task is located.
14. A data processing device applied to a first node device where a first blockchain node is deployed. The blockchain network to which the first blockchain node belongs is deployed with an off-chain computing contract. The off-chain computing contract maintains a chain The execution logic of the node device where each participant node corresponding to the off-chain computing task is located in the off-chain computing task; the device includes:

    The first execution logic acquisition unit is used to acquire the first node device in the chain when it monitors the authorization application event generated by the off-chain computing contract and determines that the first blockchain node belongs to the first participant node. The first execution logic in the next computing task;

    The first authorized transaction initiating unit is used to approve the first execution logic to generate the first authorization result corresponding to the off-chain computing task, and initiate a transaction carrying the first authorization result to the off-chain computing contract through the first blockchain node. The first authorization transaction of an authorization result, the off-chain computing contract is used to: in response to the authorization transaction initiated by each participant node, each authorization result corresponding to the off-chain computing task is used to represent the authorization pass In this case, allow the off-chain computing contract to generate task events related to the off-chain computing task;

    A data acquisition unit configured to monitor the first task event generated by the off-chain computing contract, where the first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the first blockchain node belongs to the collaboration In the case of the computing provider node corresponding to the computing task, the off-chain computing engine deployed by the first node device is called to execute the collaborative computing task. The off-chain computing engine is used to: in the process of executing the collaborative computing task, Obtain the data read from the second node device by the proxy access engine deployed on the second node device where the data provider node corresponding to the collaborative computing task is located.
15. A data processing device is applied to a second node device deployed with a second blockchain node. The blockchain network to which the second blockchain node belongs is deployed with an off-chain computing contract. The off-chain computing contract maintains an off-chain computing contract. The execution logic of the node device where each participant node corresponding to the computing task is located in the off-chain computing task; the device includes:

    The second execution logic acquisition unit is used to acquire the information of the second node device on the chain when it monitors the authorization application event generated by the off-chain computing contract and determines that the second blockchain node belongs to the second participant node. The second execution logic in the lower calculation task;

    The second authorized transaction initiating unit is used to approve the second execution logic to generate the second authorization result corresponding to the off-chain computing task, and initiate a transaction carrying the third authorization result to the off-chain computing contract through the second blockchain node. A second authorization transaction with two authorization results. The off-chain computing contract is used to: in response to the authorization transactions initiated by each participant node, each authorization result corresponding to the off-chain computing task is used to represent the authorization pass. In this case, allow the off-chain computing contract to generate task events related to the off-chain computing task;

    A data providing unit configured to monitor the first task event generated by the off-chain computing contract, where the first task event corresponds to the collaborative computing task related to the off-chain computing task; after determining that the second blockchain node belongs to the collaboration In the case of the data provider node corresponding to the computing task, the proxy access engine deployed on the second node device is called to execute the collaborative computing task. The proxy access engine is used to: in the process of executing the collaborative computing task, from The data read by the second node device is provided to the off-chain computing engine deployed by the first node device where the computing provider node corresponding to the collaborative computing task is located.
16. An electronic device including:

    processor;

    Memory used to store instructions executable by the processor;

    Wherein, the processor implements the method according to any one of claims 1-13 by running the executable instructions.
17. A computer-readable storage medium having computer instructions stored thereon, which when executed by a processor, implements the steps of the method according to any one of claims 1-13.

Images