CN114726858A

CN114726858A - Data processing method and device, electronic equipment and storage medium

Info

Publication number: CN114726858A
Application number: CN202210345176.5A
Authority: CN
Inventors: 谢桂鲁; 王毅飞
Original assignee: Ant Blockchain Technology Shanghai Co Ltd
Current assignee: Ant Blockchain Technology Shanghai Co Ltd
Priority date: 2022-03-31
Filing date: 2022-03-31
Publication date: 2022-07-08
Also published as: WO2023185041A1

Abstract

The present specification provides a data processing method, an apparatus, an electronic device, and a storage medium, which are applied to a first node device deployed with a first block chain node, where a block chain network to which the first block chain node belongs is deployed with a down-link computation contract; the method comprises the following steps: monitoring a task event aiming at a cooperative computing task generated by the down-link computing contract; in a case that it is determined that the first block link point belongs to the data provider node corresponding to the collaborative computing task but not to the computing provider node corresponding to the collaborative computing task, invoking a proxy access engine deployed by the first node device to execute the collaborative computing task, where the proxy access engine is configured to: and in the process of executing the cooperative computing task, transmitting the data read from the first node device to a down-link computing engine deployed on a second node device where the computing provider node is located.

Description

Data processing method and device, electronic equipment and storage medium

Technical Field

The embodiment of the specification belongs to the technical field of block chains, and particularly relates to a data processing method and device, an electronic device and a storage medium.

Background

The Blockchain (Blockchain) is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. In the block chain system, data blocks are combined into a chain data structure in a sequential connection mode according to a time sequence, and a distributed account book which is not falsified and forged is guaranteed in a cryptology mode. Because the blockchain has the characteristics of decentralization, information non-tampering, autonomy and the like, the blockchain is also paid more and more attention and is applied by people.

The block chain network can undertake a down-chain computing task defined based on the intelligent contract, and each node device where each block chain link point in the block chain network is respectively located can call a locally deployed down-chain computing engine under the guidance of an event generated by the intelligent contract to realize the down-chain computing task. For a cooperative computing task, that is, a down-link computing task that needs to be completed by multiple node devices in cooperation, there is often a need for data in a certain node device to be read by a down-link computing engine in another external node device, and in a case where a down-link computing engine participating in the cooperative computing task is not deployed on a certain node device, a certain node device cannot achieve data interaction through communication between the down-link computing engines, but needs to directly expose a local data source to the external node device, so that the external node device directly obtains the required data through the data source, and at this time, the local data source corresponding to the certain node device is open to the outside.

Disclosure of Invention

The invention aims to provide a data processing method, a data processing device, electronic equipment and a storage medium.

According to a first aspect of one or more embodiments of the present specification, a data processing method is provided, which is applied to a first node device deployed with a first blockchain node, where a blockchain network to which the first blockchain node belongs is deployed with a down-link computation contract; the method comprises the following steps:

monitoring a task event aiming at a cooperative computing task generated by the down-link computing contract;

in a case that it is determined that the first block link point belongs to the data provider node corresponding to the collaborative computing task but not to the computing provider node corresponding to the collaborative computing task, invoking a proxy access engine deployed by the first node device to execute the collaborative computing task, where the proxy access engine is configured to: and in the process of executing the cooperative computing task, transmitting the data read from the first node device to a down-link computing engine deployed on a second node device where the computing provider node is located.

According to a second aspect of one or more embodiments of the present specification, a data processing method is provided, which is applied to a second node device, where the second node device is deployed with a second blockchain node, and a blockchain network to which the second blockchain node belongs is deployed with a down-chain computation contract; the method comprises the following steps:

in a case where it is determined that the second block link point belongs to a computation provider node of the collaborative computation task, invoking an off-chain computation engine deployed by the second node device to perform the collaborative computation task, the off-chain computation engine being configured to: in the process of executing the collaborative computing task, data read from a first node device by an agent access engine deployed on the first node device where a data provider node of the collaborative computing task is located is acquired, and a first block chain node deployed on the first node device does not belong to the computing provider node.

According to a third aspect of one or more embodiments of the present specification, there is provided a data processing apparatus, which is applied to a first node device in which a first blockchain node is deployed, wherein a blockchain network to which the first blockchain node belongs is deployed with a down-link computation contract; the device comprises:

a first event monitoring unit, configured to monitor a task event for a collaborative computing task generated by the down-link computing contract;

a data providing unit, configured to, in a case that it is determined that the first tile link node belongs to the data provider node corresponding to the collaborative computing task but not to the computing provider node corresponding to the collaborative computing task, invoke a proxy access engine deployed by the first node device to execute the collaborative computing task, where the proxy access engine is configured to: and in the process of executing the cooperative computing task, transmitting the data read from the first node device to a down-link computing engine deployed on a second node device where the computing provider node is located.

According to a fourth aspect of one or more embodiments of the present specification, a data processing apparatus is provided, which is applied to a second node device, where a second blockchain node is deployed in the second node device, and a blockchain network to which the second blockchain node belongs is deployed with a down-chain computation contract; the device comprises:

the second event monitoring unit is used for monitoring task events which are generated by the down-link computation contract and aim at the collaborative computation task;

a data obtaining unit, configured to, in a case that it is determined that the second block link point belongs to a computation provider node of the collaborative computation task, invoke a down-link computation engine deployed by the second node device to execute the collaborative computation task, where the down-link computation engine is configured to: in the process of executing the collaborative computing task, data read from a first node device by an agent access engine deployed on the first node device where a data provider node of the collaborative computing task is located is acquired, and a first block chain node deployed on the first node device does not belong to the computing provider node.

According to a fifth aspect of one or more embodiments herein, there is provided an electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method according to the first aspect or the second aspect by executing the executable instructions.

According to a sixth aspect of one or more embodiments of the present description, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to the first or second aspect.

In the present specification embodiment, by intermediating a proxy access engine deployed on a first node device where a data provider node is located to provide local data to a second node device, reading a data source by the agent access engine in the first node device, and realizing communication between the first node device and the second node device through the agent access engine arranged on the first node device and the down-link computing engine arranged on the second node device, thereby avoiding directly exposing the data source local to the first node device to the second node device, and simultaneously, because the data transmitted between the agent access engine and the down-link computing engine deployed by the second node device only contains the data defined by the cooperative computing task, therefore, the data reading range of the second node equipment can be limited relatively controllably, privacy information is prevented from being exposed, and safety risks are reduced.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and it is obvious for a person skilled in the art to obtain other drawings based on these drawings without inventive labor.

Fig. 1 is a flowchart of a data processing method according to an exemplary embodiment.

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

Fig. 3 is a schematic diagram of a scenario of node device interaction according to an exemplary embodiment.

Fig. 4 is a schematic structural diagram of an apparatus according to an exemplary embodiment.

Fig. 5 is a block diagram of a data processing apparatus according to an example embodiment.

FIG. 6 is a block diagram of another data processing apparatus provided in an exemplary embodiment.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.

Fig. 1 is a flowchart of a data processing method according to an exemplary embodiment. The method is applied to first node equipment with a first block chain node, and a block chain network to which the first block chain node belongs is provided with a down-link calculation contract; the method comprises the following steps:

s102: and monitoring task events generated by the down-link computation contract and aiming at the cooperative computation task.

In this embodiment of the present specification, a down-link computation contract is an on-link bearer for carrying down-link computation tasks, and a number of subtasks included in the down-link computation contract are defined in the down-link computation contract, and are used to describe a data flow direction in a down-link computation task and a computation cooperation process of each node device. Since the calculation contract under the chain is deployed on the blockchain network, the participant nodes of the calculation task under the chain defined by the calculation contract under the chain are limited not to exceed the range of each blockchain node in the blockchain network. Obviously, a plurality of calculation contracts under the chain can be deployed in the same block chain network, and the number and the performance of the participating party nodes involved in different calculation contracts under the chain can be flexibly configured, so that the deployment of the calculation tasks under the chain with different task types, task requirements and task scales can be realized depending on the same block chain network.

To illustrate how a computation contract under a chain directs to perform its defined computation tasks under the chain, the logic for performing the computation tasks under the chain will be briefly described below by the operation of a typical computation contract under the chain. A user may generate code for a calculation contract under a chain and deploy the calculation contract under a chain in a blockchain network through a visualization contract orchestration system such that the calculation contract under a chain defines a workflow of a type of calculation task under a chain, which is embodied as a number of subtasks having an execution dependency order. After the calculation contract under the chain is successfully deployed, a user authorized to call the calculation contract under the chain can create and start a calculation task under the chain by initiating a task creation transaction to the calculation contract under the chain, the calculation contract under the chain can correspondingly create a task instance belonging to the calculation task under the chain of an initiator user after receiving the task creation transaction, and the task instance maintains the task completion state of the calculation task under the chain, which is specifically embodied as the task completion state of each subtask under the calculation task under the chain. After the calculation contract under the chain responds to the task creation transaction and generates a corresponding task instance, a first subtask corresponding to the instance is further triggered to be executed, the calculation contract under the chain is embodied to generate an event containing a participant node of the first subtask, each block chain node in the block chain network can monitor the event, and the node equipment where the block chain link point of the participant node which is judged to belong to the first subtask further calls the chain lower calculation resource and/or the chain lower storage resource which are matched with the first subtask to execute the first subtask under the chain, and finally, the node equipment where the participant node is located can further initiate a result carrying the execution result of the first subtask to the calculation contract under the chain to return the transaction after the execution is completed, so that the calculation contract under the chain updates the task completion state of the corresponding task instance, for example, when the execution result of the first subtask is that the execution is successful, the under-chain computation contract marks the task completion status of the first subtask in the corresponding task instance as completed, so that the execution of the next subtask is triggered according to the predefined dependency order of each subtask included in the under-chain computation task, and then an event including the description information of the participant node of the next subtask is generated for each block link node in the block chain network to monitor, and the subsequent process is similar to the process for processing the first subtask. Therefore, a cycle of 'updating the task completion state of the calculation contract under the chain → generating the subtask event under the calculation contract under the chain → monitoring the subtask event by the block link point and executing the subtask by the appointed node equipment → sending the result of starting the task to the calculation contract under the chain by the node equipment to return the transaction → updating the task completion state of the calculation contract under the chain' is formed, and the calculation task under the chain corresponding to the task example is determined to be executed and completed under the condition that the task completion states of all the subtasks in the task example in the calculation contract under the chain are completed.

It is not difficult to find that the tasks executed in the execution process of the under-chain computing task only include creating task instances, receiving subtask results, subtask scheduling and subtask issuing such scheduling tasks, and actually, actual tasks defined and required to be executed by the under-chain computing task, such as data computing, data transferring and data storing, are not really executed, and the tasks consuming a large amount of resources are scheduled to be executed under the chain corresponding to each node device, so that a distributed computing based on a block chain is realized through an event monitoring mechanism and a transaction return mechanism, the under-chain computing task is anchored by an under-chain computing contract on the block chain, the under-chain resources are fully utilized on the premise of ensuring that the task execution full flow can be tracked, and meanwhile, reliable information interaction and cooperative computing are realized among different node devices by means of the block chain, in addition, since the calculation tasks under the chain are defined in a contract form and the design of the calculation tasks under the chain is not subject to the toggle of the resources on the chain, the method means that the on-chain cooperation mode can be expanded through the resources under the chain by designing different calculation contracts under the chain to meet different actual requirements.

In an embodiment of the present specification, the calculation contract under the chain maintains a task completion state corresponding to a calculation task under the chain, where the task completion state is used to describe a completion state of each subtask included in the calculation task under the chain; when the collaborative computing task belongs to a subtask of the calculation task under the chain, the monitoring a task event generated by the calculation contract under the chain and aiming at the collaborative computing task includes: and monitoring the task event aiming at the collaborative computing task generated by the under-chain computing contract under the condition that the task completion state meets the execution condition corresponding to the collaborative computing task. In this embodiment of the present specification, a calculation task under a chain is represented as a corresponding task instance on a calculation contract under a chain, and the task completion status of the calculation task under a chain is maintained in the corresponding task instance of the calculation contract under a chain, which is specifically represented as the completion status of each subtask maintained in the task instance. In this embodiment of the present specification, the collaborative computing task belongs to one sub-task of the calculation task under the chain, and since the execution dependency order of each sub-task included in the calculation task under the chain is predefined, which means that the execution condition of each sub-task including the collaborative computing task is also determined, the calculation contract under the chain can further determine the collaborative computing task to be executed next according to the completion state of each sub-task included in the calculation task under the chain, so as to initiate a task event for the collaborative computing task. Further, the method also comprises the following steps: and under the condition that the execution of the collaborative computing task is finished, initiating a result return transaction containing an execution result corresponding to the collaborative computing task to the under-chain computing contract through the first block link node so as to update a task completion state corresponding to the under-chain computing task maintained by the under-chain computing contract. As described above, when the first node device executes a subtask by calling a resource and finishes executing the subtask, the task completion status of the calculation task under the chain maintained by the calculation contract under the chain is updated by initiating a result return transaction, so that the calculation contract under the chain can further determine a next subtask to be executed next according to the execution dependency order of each subtask in the calculation task under the chain, and generate a task event for the next subtask. In an embodiment of the present specification, the entity that monitors the task event generated by the calculation contract under the chain and returns the transaction to the result of the calculation contract under the chain is specifically a scheduling engine deployed on the first node device.

As described above, the task completion status is updated by the under-chain computation contract in response to a transaction trigger corresponding to the under-chain computation task, where the transaction corresponding to the under-chain computation task includes a task creation transaction corresponding to the under-chain computation task, or a result return transaction initiated by any node device when any one of the subtasks is completely executed. In an embodiment of the present specification, the calculation contract maintains a task completion status corresponding to each of one or more calculation tasks. In general, a calculation contract under a chain only defines one type of calculation task under the chain, but a plurality of task instances corresponding to the calculation task under the chain can be created, and each task instance records a task completion status corresponding to the task instance. Therefore, the plurality of task instances maintained on the calculation contract under the chain can be created by different users through respectively initiating the task creation contracts to the calculation contract under the chain, or can be created by the same user through initiating the task creation contracts for multiple times, but the task instances all have the same execution logic, namely the task types of the tasks maintained by the calculation contract under the chain are the same.

S104: in a case that it is determined that the first block link point belongs to the data provider node corresponding to the collaborative computing task but not to the computing provider node corresponding to the collaborative computing task, invoking a proxy access engine deployed by the first node device to execute the collaborative computing task, where the proxy access engine is configured to: and in the process of executing the cooperative computing task, transmitting the data read from the first node device to a down-link computing engine deployed on a second node device where the computing provider node is located.

In the embodiment of the present specification, description information of a participant node of a collaborative computing task is recorded in a task event for the collaborative computing task generated by the under-link computing contract monitored by the first node device. The task event comprises description information of the participant node of the collaborative computing task, which means that the collaborative computing task specifies identity information of the blockchain node which needs to be involved in the collaborative computing task. The participant node of the collaborative computing task can be determined as a data provider node and/or a computing provider node corresponding to the collaborative computing task according to the corresponding attribute characteristics, wherein the data provider node corresponding to the collaborative computing task is: in the execution process of a cooperative computing task which is completed by a plurality of node devices jointly, a blockchain node in the blockchain network deployed on a node device which needs to provide data to other node devices, wherein the data is used for providing data for a down-chain computing engine deployed on other node devices as data required for executing the cooperative computing task and/or other subsequent subtasks; and the calculation provider corresponding to the collaborative calculation task is as follows: and providing the blockchain nodes in the blockchain network deployed on the node equipment of which the under-chain computing engine resources execute the actual computing task in the process of executing the cooperative computing task which is completed by the joint participation of a plurality of node equipment. It is easy to understand that any participant node in a collaborative computing task may be a data provider node corresponding to the collaborative computing task, may also be a computing provider node corresponding to the collaborative computing task, and may also be a data provider node and a computing provider node corresponding to the collaborative computing task at the same time. For example, for a data provider node and a participant node of a computation provider node that correspond to a collaborative computation task at the same time, a down-link computation engine on a node device where the data provider node is located will acquire data local to the node device in the process of executing the collaborative computation task, so as to obtain the collaborative computation task and/or other subsequent subtasks.

The type of proxy access engine to which embodiments of the present description relate may be a compute engine or a data engine. The computing engine is also called a down-link computing engine, and refers to a service or subsystem providing down-link computing energy for the node device, and one computing engine can often bear one or more types of computing tasks, which is reflected in the support of computing requirements corresponding to related subtasks; the data engine is also called a database engine and refers to a core service program for storing, retrieving, processing and protecting data, can control access authority and rapidly process transactions by using the database engine so as to meet the requirements of most application programs needing to process a large amount of data in an enterprise, and uses the database engine to create a relational database for online transaction processing or online analysis processing of data, wherein the relational database comprises a table for storing data and database objects (such as indexes, views and storage processes) for viewing, managing and protecting data security, and different data engines support different data access modes or different accessed data types, so that the data engines are supported by corresponding subtasks.

In this embodiment of the present specification, the first node device needs to invoke the proxy access engine to execute the collaborative computing task only when it is determined that the first block link node belongs to the data provider node corresponding to the collaborative computing task but not to the computing provider node corresponding to the collaborative computing task, which means that the first node device invokes the proxy access engine only when the first node device only belongs to the data provider of the collaborative computing task, otherwise, the first node device does not invoke the proxy access engine to execute the collaborative computing task unless the first node device does not belong to the data provider node corresponding to the collaborative computing task or belongs to the computing provider node corresponding to the collaborative computing task. This is because, if the first tile link node belongs to both the data provider node and the computation provider node corresponding to the collaborative computation task, the first node device can directly perform data transmission via the down-link computation engine involved in the computation provider node as an intermediary even if it needs to provide data to other node devices, and the down-link computation engine accesses the local data source, so that the local data source does not need to be exposed to the outside. In an embodiment of the present specification, the entity that invokes the down-link computing engine to execute the collaborative computing task is specifically a scheduling engine deployed on the first node device.

Optionally, when the description information of the data provider node recorded in the task event includes identification information of a first block chain node, determining that the first block chain link point belongs to the data provider node; and determining that the first blockchain node does not belong to the computation provider node when the description information of the computation provider node recorded in the task event does not contain the identification information of the first blockchain node or a chain-down computation engine supporting the execution of the collaborative computation task is not deployed on the first node device.

In this embodiment of the present specification, description information of a participant node of a collaborative computing task recorded in a task event of the collaborative computing task specifically means that description information of a data provider node corresponding to the collaborative computing task is recorded in the task event, which means that a first node device may determine that a first block link point to which the first node device belongs to a data provider node corresponding to the collaborative computing task when it is determined that the description information of the data provider node includes identification information of a first block link node deployed by the first node device; if the description information of the data provider node does not include the identification information of the first block chain node, the first node device may determine that the first block chain node deployed by itself does not belong to the data provider node corresponding to the cooperative computing task.

In an embodiment, description information of a computation provider node corresponding to a collaborative computation task is further recorded in a task event for the collaborative computation task, which means that a first node device may determine that a first block link point to which the first node device belongs to a computation provider node corresponding to the collaborative computation task when it is determined that the description information of the computation provider node includes identification information of a first block link node deployed by the first node device; if the description information of the computation provider node does not include the identification information of the first block chain node, the first node device may determine that the first block chain node deployed by itself does not belong to the computation provider node corresponding to the collaborative computation task. In this embodiment, the task event further records identification information of a down-link computing engine that participates in executing the collaborative computing task on a node device where the computing provider node is located.

In another embodiment, in a case that only description information of a data provider node corresponding to a collaborative computing task is recorded in a task event of the collaborative computing task, but description information of a computing provider node corresponding to the collaborative computing task and identification information of a computing engine under a chain participating in execution of the collaborative computing task are not recorded, at this time, after monitoring the task event, each node device recognizes that description information of a computing provider node corresponding to the collaborative computing task is not recorded in the task event, and then, negotiation of the computing provider node corresponding to the collaborative computing task is triggered. For any node device, it may determine that the node device itself belongs to the computation provider node corresponding to the collaborative computation task when it is determined that the node device itself deploys the under-chain computation engine supporting execution of the collaborative computation task, and therefore, it may be determined that the first block chain node does not belong to the computation provider node when the first node device does not deploy the under-chain computation engine supporting execution of the collaborative computation task.

Further, in the case of receiving a computation providing statement sent by another node device, attributing the tile link nodes deployed on the another node device to the computation provider node, wherein the computation providing statement is broadcast by the another node device to a first node device where the data provider node is located in the case of determining that the another node device is deployed with a down-chain computation engine that supports execution of the collaborative computation task. When any node device in each node device negotiates with a computation provider node, in addition to determining whether the node device belongs to the computation provider node corresponding to the collaborative computation task according to whether the node device itself is deployed with a down-chain computation engine supporting the collaborative computation task, after determining that the node device itself belongs to the computation provider node, the node device broadcasts a computation provision declaration including identification information of the down-chain computation engine supporting the collaborative computation task to other node devices, so that after receiving the computation provision declaration of any node device, the node device belongs to the computation provider node corresponding to the collaborative computation task, and simultaneously learns down-chain computation engines deployed on the other node devices involved in performing actual computation in the collaborative computation task, where the other node devices may be all node devices deployed with block chain nodes in a block chain network, or all node devices deployed with data provider nodes corresponding to the collaborative computing task. Therefore, for a first node device, when it receives a computation providing declaration sent by another node device, it can attribute the tile link node deployed on the another node device to the computation provider node, and at the same time, learn the identification information of the down-link computation engine that is the target of providing data. In this embodiment of the present specification, under the condition that the node device where the participant node is located can not record the description information of the computation provider node corresponding to the collaborative computation task in the task event, the node device can also perform negotiation on the computation provider node to obtain the collaborative computation party node and the corresponding under-link computation engine, thereby further guiding effective execution of the collaborative computation task.

In addition, task identifiers of the calculation tasks and the collaborative calculation tasks under the chain can be recorded in the task event, so that different tasks and subtasks can be distinguished, and the accurate identifier of any subsequent node equipment can be a result of the collaborative calculation tasks in the calculation tasks under the chain when the collaborative calculation tasks are completely executed and returned back to the transaction, so that the calculation contracts under the chain can be returned to the transaction through the result to accurately update the completion state of the collaborative calculation tasks in the task instances of the calculation tasks under the chain, and the condition that the same task comprises a plurality of subtasks and the same calculation annual contract under the chain simultaneously creates the task instances of the calculation tasks under the chain is met. Certainly, the cooperative computing task also records operations such as computation and data transfer required to be executed by the cooperative computing task, and specifies a source of required data, and the information is used for informing each node device of the task type and the implementation manner of the cooperative computing task, so as to guide the node devices to execute the cooperative computing task according to the expectation of the cooperative computing task after determining that the task type and the implementation manner of the cooperative computing task correspond to the callable resources.

Optionally, the invoking the agent access engine deployed by the first node device to execute the cooperative computing task includes: calling the agent access engine pre-deployed by the first node equipment to execute the cooperative computing task; or deploying the agent access engine at the first node device, and calling the agent access engine to execute the cooperative computing task. In this embodiment of the present specification, a first node device may be pre-deployed with a proxy access engine, and in this case, the first node device may directly invoke the pre-deployed proxy access engine to execute a cooperative computing task when determining that it needs to invoke the proxy access engine to execute the cooperative computing task; in another case, the agent access engine is not deployed in advance in the first node device, but at this time, when it is determined that the first node device needs to invoke the agent access engine to execute the cooperative computing task, the agent access engine is temporarily generated and deployed locally, so that the agent access engine is invoked to execute the cooperative computing task after the agent access engine is deployed.

Optionally, the proxy access engine is configured to: in response to the proxy access engine being invoked, transmitting data indicated by the task event read from the first node device to the down-link compute engine; or reading pre-reading data indicated by the task event from a first node device, and transmitting the pre-reading data to the down-link computing engine in response to a data access request sent by the down-link computing engine; or responding to the data access request sent by the calculation engine under the chain, and transmitting the data indicated by the data access request read from the first node device to the calculation engine under the chain. In this specification embodiment, the proxy access engine may provide data to a second node device where the compute provider node is located through at least three types of logic: first, a first node device calls a request of a proxy access engine to carry identification information of a down-link computing engine as a transmission target and a data requirement recorded in a task event, so that the proxy access engine can trigger reading corresponding data from the first node device according to the data requirement contained in the task event and transmitting the data to the down-link computing engine deployed by a second node device when being called to execute a cooperative computing task; secondly, the first node device triggers and reads pre-read data corresponding to the data demand based on a call request of a proxy access engine, wherein the call request carries identification information of a down-link computing engine serving as a transmission target and the data demand recorded in the task event, waits for the data access request from the down-link computing engine deployed by the second node device, and further triggers and transmits the pre-read data to the down-link computing engine after the proxy access engine receives the data access request; and thirdly, the first node device carries identification information of the down-link computing engine as a transmission target in a call request of the proxy access engine, the proxy access engine waits for a data access request from the down-link computing engine deployed by the second node device, and after receiving the data access request, the proxy access engine further triggers and reads data indicated by the data access request and transmits the data to the down-link computing engine. The embodiment of the present specification provides various ways for the proxy access engine to provide data to the down-link computation engine, so as to adapt to actual requirements of different scenarios, for example, compared with the first and second ways, the data provided by the first and second ways are determined by task events generated by a down-link computation contract, so that access right control between different node devices can be achieved by compiling down-link computation tasks, and the data provided by the third way is determined by the down-link computation engine, so that the method can be adapted to more flexible execution of the down-link computation tasks, and meanwhile, the proxy access engine can be used as work for access right control; the second mode and the third mode emphasize that the data transmission is controlled by the under-chain computing engine compared with the first mode, and the under-chain computing task with uncertain data stream transfer process can be matched, because the possibility that the under-chain computing engine does not need to acquire data from the proxy access engine can also occur according to different specific situations in some under-chain computing tasks, the data transmission controlled by the under-chain computing engine can meet the actual needs of the under-chain computing engine, and the safety risk and resource loss possibly caused by unnecessary data transmission are avoided.

Optionally, the proxy access engine is configured to: and encrypting the data read from the first node equipment through a certification storage public key corresponding to the down-link computing engine maintained by the down-link computing contract to obtain encrypted data, and sending the encrypted data to the down-link computing engine. In this embodiment, the public key of each of the down-link computing engines participating in executing the down-link computing task is maintained in the down-link computing contract, and therefore, the public key of the down-link computing engine participating in executing the collaborative computing task disposed on the second node device is also included, the proxy access engine may obtain the public key of the down-link computing engine as a data providing target from the down-link computing contract, and then, as a substitute for the original data, encrypted data obtained by encrypting the original data read from the first node device by the public key of the down-link computing engine, transmit the encrypted data to the down-link computing engine instead of the original data, and the down-link computing engine may decrypt the encrypted data by its own public key to obtain the original data, thereby avoiding directly transmitting plaintext data while ensuring communication validity, and potential safety hazards are reduced.

Further, the certification storing public key corresponding to the calculation engine under the chain maintained by the calculation contract under the chain is triggered and updated by a key update transaction initiated by the second computing device, the key update transaction is initiated by the second computing device under the condition that a key update event generated by the calculation contract under the chain is monitored, and the key update transaction carries the latest public key corresponding to the calculation engine under the chain acquired by the second node device in response to the key update event. In this embodiment, when a certain node device determines that it deploys an offline computation engine with a key to be updated according to a monitored key update event, for example, the key update event records description information of a participant node related to a key update task or identification information of the offline computation engine with the key to be updated, the node device may determine whether it needs to execute the key update task by determining whether a block link point deployed by itself is included in the description information of the participant node or determining whether there is identification information matching the offline computation engine deployed by itself in the key update event. When executing a key updating task, any node device needs to access a locally deployed under-chain computing engine of a key to be updated and obtain a corresponding latest public key, then carries the latest public key in a key updating transaction, and finally initiates the key updating transaction to an under-chain computing contract, so that the under-chain computing contract triggers updating of a certificate storing public key of the under-chain computing engine maintained by the under-chain computing contract, namely, the certificate storing public key of the under-chain computing engine to which the originally maintained key updating transaction in the under-chain computing contract is replaced by the latest public key of the under-chain computing contract carried in the key updating transaction. According to the embodiment of the description, the public key information of the down-link computing engine deployed in the node equipment is maintained in the down-link computing contract through the event monitoring mechanism and the transaction returning mechanism, so that the public keys of all down-link computing engines participating in the down-link computing task can be subjected to up-link certification storage and immediate updating, and authority and effectiveness of all main bodies participating in executing the down-link computing task for obtaining the public keys are ensured.

Further, the under-chain computing contract is used to trigger generation of the rekeying event in the initialization phase of a successful deployment or in response to a rekeying transaction. In an embodiment of the present specification, when a calculation contract is successfully deployed on any node device, the calculation contract triggers execution of an initialization procedure, which includes generating a key update event, so that the calculation contract updates the certified public key of each calculation engine participating in the calculation task in each node device. In addition, any node device can also actively initiate a rekey transaction to the calculation contract under the chain, so that the calculation contract under the chain responds to the rekey transaction to trigger and generate a rekey event to be monitored by each node device, thereby handling the situation that the latest public key of the calculation engine under the chain, which is deployed on some node devices and participates in the calculation task under the chain, changes, and ensuring the consistency of the certified public key on the chain and the actual latest public key of the calculation engine under the chain.

FIG. 2 is a flow chart of another data processing method provided by an exemplary embodiment. The method is applied to second node equipment, wherein second block chain nodes are deployed on the second node equipment, and a block chain network to which the second block chain nodes belong is deployed with a down-chain calculation contract; the method comprises the following steps:

s202: and monitoring task events generated by the under-chain computing contract and aiming at the cooperative computing task.

S204: in a case where it is determined that the second block link point belongs to a computation provider node of the collaborative computation task, invoking an off-chain computation engine deployed by the second node device to perform the collaborative computation task, the off-chain computation engine being configured to: in the process of executing the cooperative computing task, data read from a first node device by a proxy access engine deployed on the first node device where a data provider node of the cooperative computing task is located is acquired, and a first block chain node deployed on the first node device does not belong to the computing provider node.

The embodiment of the present specification is an embodiment of a second node device side corresponding to the foregoing embodiment of the data processing method, where details of the related technology have been described in detail in the foregoing, and are not described herein again. Because the first blockchain node deployed on the first node device does not belong to the computation provider node, that is, the first blockchain node is only used as the data provider node, in order to avoid that the second node device directly reads data from the first node device in the process of executing the collaborative computation task, the proxy access engine deployed in the first node device is used as an intermediary to acquire the data on the first node device, so that the range of reading the data in the first node device by the second node device can be more controllably limited, privacy information is prevented from being leaked, and security risks are reduced.

In this specification embodiment, the task event records description information of the data provider node. The second node device may determine that the second blockchain node belongs to the data provider node when it is determined that the identification information of the second blockchain node deployed by itself is included in the description information of the data provider node recorded in the task event, and may determine that the second blockchain node does not belong to the data provider node when it is determined that the identification information of the second blockchain node is not included in the description information of the data provider node recorded in the task event. Meanwhile, the second node device can also know the node device where the related data provider node participating in the execution of the collaborative computing task is located, so that the node device can inform the down-link computing engine of where to acquire data in the process of executing the collaborative computing task.

Optionally, the method further includes: and determining that a second blockchain link point belongs to the computation provider node when the description information of the computation provider node recorded in the task event includes identification information of a second blockchain node or a second node device deploys a calculation engine under a chain supporting execution of the collaborative computation task. As described above, in an embodiment, the task event directly records the description information of the computation provider node, so that the second node device may determine that the second blockchain node belongs to the computation provider node by determining that the identification information of the second blockchain node is included in the description information of the computation provider node. In another embodiment, if the description information of the computation provider node is not recorded in the task event, the negotiation of the computation provider node corresponding to the collaborative computation task is triggered to be participated, the negotiation is carried out in each node device, each node device judges whether a down-link computing engine supporting the execution of the cooperative computing task is deployed, in this embodiment, the calculation provider node is not assigned in the task event generated by the calculation contract under the chain, but the calculation provider node is selected by the node devices through negotiation, therefore, dynamic resource planning is realized to a certain extent, and the resources of the down-link computing engine on each node device are fully utilized.

Optionally, the method further includes: in the event that it is determined that a second node device is deployed with an in-chain compute engine that supports performing the collaborative compute task, broadcasting the compute offer statement to a first node device at which the data provider node is located to cause the first node device to ascribe a second blockchain link point to the compute provider node. When negotiating the calculation providing node, each node device needs to know whether the block link point deployed by itself belongs to the calculation providing node or not, and also needs to know other calculation providing nodes, so that when any one of the calculation node devices determines that the calculation engine under the chain deployed by itself supports execution of the cooperative calculation task, the calculation providing statement carrying the identification information of the block link point deployed by itself and the identification information of the determined calculation engine under the chain is broadcast to other node devices, so that the other node devices can attribute the block link point carried by the other node devices to the calculation providing node through the calculation providing statement, and determine the chain lower calculation engine carried by the other node devices as needing to participate in the cooperative calculation task.

Optionally, the method further includes: in the event that it is determined that a second chunk link node belongs to both the compute provider node and the data provider node, invoking the down-chain compute engine to perform the collaborative compute task, wherein the down-chain compute engine is configured to: and in the process of executing the cooperative computing task, acquiring local data read from the second node device and data read from the first node device by the agent access engine, wherein a first block chain node deployed on the first node device does not belong to the computing provider node. In this embodiment, if the second node device determines that the second block link point deployed by itself belongs to both the computation provider node and the data provider node, in this case, during the process of performing the cooperative computation task, the down-link computation engine participating in performing the cooperative computation task in the second node device will not only obtain data from other node devices, but also read data local to the second node device for further use in the performance of the cooperative computation task or subsequent subtasks.

Optionally, the downlink computation engine is configured to: and acquiring encrypted data sent by the agent access engine, wherein the encrypted data is obtained by encrypting the data read from the first node equipment by the agent access engine through a certification storage public key corresponding to the down-link computation engine maintained by the down-link computation contract.

Further, the method also comprises the following steps: and under the condition that a key updating event generated by the calculation contract under the chain is monitored, acquiring a latest public key corresponding to the calculation engine under the chain, and initiating a key updating transaction carrying the latest public key to the calculation contract under the chain through a second block chain node so as to update a certificate storing public key corresponding to the calculation engine under the chain maintained by the calculation contract under the chain into the latest public key.

Further, the downchain computation contract is used to trigger generation of the rekeying event during an initialization phase of a successful deployment or in response to a rekeying transaction.

Further, the acquiring a latest public key corresponding to the calculation engine under the chain when the key update event generated by the calculation contract under the chain is monitored includes: under the condition that the key updating event generated in the initialization stage of successful deployment of the calculation contract under the chain is monitored, the latest public keys corresponding to all calculation engines under the chain deployed by the second node equipment are obtained; or, in a case that the key update event generated by the under-chain computing contract in response to the rekeying transaction is monitored and it is determined that the target under-chain computing engine indicated by the key update event is deployed in the first node device, acquiring the latest public key corresponding to the target under-chain computing engine. In this embodiment of the present specification, when a calculation contract under a chain is deployed on any node device, an execution initialization program is triggered, where the execution initialization program includes a process of generating the key update event, where the key update event is used to instruct any node device to obtain the latest public keys of all calculation engines under the chain deployed on any node device, and maintain them in the calculation contract under the chain through a transaction pass-back mechanism, so that the public key of a new calculation engine under the chain, which participates in executing a calculation task under the chain defined by the calculation contract under the chain, is immediately maintained in the calculation contract under the chain, thereby ensuring normal execution of the calculation task under the chain; or, after the calculation contract under the chain receives the rekey transaction, a key update event is also generated to indicate to update the certification public key of the target calculation engine under the chain maintained in the calculation contract under the chain, and at this time, if the second node device recognizes that the target calculation engine under the chain is locally deployed, the second node device responds to the key update event to obtain the latest public key corresponding to the target calculation engine under the chain deployed on the second node device, and updates the latest public key to the calculation contract under the chain through a called transaction feedback mechanism, so that the certification public key in the calculation contract under the chain of the specific calculation engine is updated immediately, and execution errors of the calculation task under the chain caused by the fact that the certification public key of the specific calculation engine under the chain lags behind the latest public key of the calculation engine under the specific chain are avoided.

FIG. 3 is a schematic diagram of a scenario of node device interaction provided by an exemplary embodiment. As shown in fig. 3, a first blockchain node, a first scheduling engine, a proxy access engine, and a first data source in a blockchain network are deployed on a first node device, and a second blockchain node, a second scheduling engine, a down-link computation engine, and a second data source in the blockchain network are deployed on a second node device. After a task event aiming at a collaborative computing task is generated by a calculation contract under a chain, the task event is monitored by a first scheduling engine on first node equipment and a second scheduling engine on second node equipment through a first block chain link node and a second block chain node respectively, and description information of a data provider node and a calculation provider node corresponding to the collaborative computing task and identification information of a calculation engine under the chain needing to provide data are supposed to be recorded in the task event at the same time, wherein the description information of the data provider node is the identification information of the first block chain node, and the description information of the calculation provider node is the identification information of the second block chain node. Therefore, the first scheduling engine may determine that the first node device needs to provide data to the offline computing engine in the second node device, and at the same time, the first node device does not need to provide computing support for the collaborative computing task, so the first scheduling engine may invoke the proxy access engine to execute the collaborative computing task, so as to transmit the data acquired from the first data source to the offline computing engine in the second node device. On the other hand, the second scheduler engine may determine that the specified offline computing engine in the task event deployed in the second node device needs to acquire the data of the first node device, and then the second scheduler engine may invoke the specified offline computing engine to perform the collaborative computing task, for example, the specified offline computing engine is a trusted computing engine running in a feasible execution environment, which needs to acquire data from the first node device to complete the relevant trusted computing operation defined in the collaborative computing task, and at this time, the trusted computing engine may acquire the data read by the agent access engine from the first data source through a network connection with the agent access engine deployed on the first node device, so as to further perform the trusted computing operation to continue to complete the collaborative computing task.

FIG. 4 is a schematic block diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 4, at the hardware level, the apparatus includes a processor 402, an internal bus 404, a network interface 406, a memory 408, and a non-volatile memory 410, but may also include hardware required for other functions. One or more embodiments of the present description may be implemented in software, such as by processor 402 reading corresponding computer programs from non-volatile storage 410 into memory 408 and then executing. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Fig. 5 is a block diagram of a data processing apparatus provided in the present specification according to an exemplary embodiment, and the apparatus may be applied to the device shown in fig. 4 to implement the technical solution of the present specification; the device is applied to first node equipment with a first block chain node, and a block chain network to which the first block chain node belongs is provided with a down-link calculation contract; the device comprises:

a first event monitoring unit 501, configured to monitor a task event generated by the calculation contract for the collaborative calculation task.

A data providing unit 502, configured to, in a case that it is determined that the first chunk link node belongs to the data provider node corresponding to the collaborative computing task but not to the computing provider node corresponding to the collaborative computing task, invoke a proxy access engine deployed by the first node device to execute the collaborative computing task, where the proxy access engine is configured to: and in the process of executing the cooperative computing task, transmitting the data read from the first node device to a down-link computing engine deployed on a second node device where the computing provider node is located.

Optionally, the calculation contract under the chain maintains a task completion state corresponding to the calculation task under the chain, where the task completion state is used to describe a completion state of each subtask included in the calculation task under the chain; in a case that the collaborative computing task belongs to a subtask of the calculation task under the chain, the first event monitoring unit 501 is specifically configured to:

and monitoring the task event aiming at the collaborative computing task generated by the under-chain computing contract under the condition that the task completion state meets the execution condition corresponding to the collaborative computing task.

Optionally, the task completion state is updated by the under-chain computation contract in response to a transaction trigger corresponding to the under-chain computation task, where the transaction corresponding to the under-chain computation task includes a task creation transaction corresponding to the under-chain computation task, or a result initiated by any node device when any one of the subtasks is completely executed returns a transaction.

Optionally, the data providing unit 502 is specifically configured to:

calling the agent access engine pre-deployed by the first node equipment to execute the cooperative computing task; alternatively, the first and second electrodes may be,

and deploying the agent access engine at the first node equipment, and calling the agent access engine to execute the cooperative computing task.

Optionally, the proxy access engine is configured to:

in response to the proxy access engine being invoked, transmitting data indicated by the task event read from the first node device to the down-link compute engine; alternatively, the first and second electrodes may be,

reading pre-read data indicated by the task event from a first node device, and transmitting the pre-read data to the down-link computing engine in response to a data access request sent by the down-link computing engine; alternatively, the first and second electrodes may be,

and responding to the data access request sent by the calculation engine under the chain, and transmitting the data indicated by the data access request read from the first node device to the calculation engine under the chain.

Optionally, the method further includes:

a data provider node determining unit 503, configured to determine that a first blockchain link point belongs to the data provider node when the description information of the data provider node recorded in the task event includes identification information of the first blockchain node.

A first computation provider node determining unit 504, configured to determine that a first blockchain node does not belong to a computation provider node when description information of the computation provider node recorded in the task event does not include identification information of the first blockchain node or a chain-down computation engine supporting execution of the collaborative computation task is not deployed on a first node device.

Optionally, the method further includes:

a calculation providing declaration receiving unit 505, configured to, in a case where a calculation providing declaration sent by another node device is received, assign a tile link node deployed on the another node device to the calculation provider node, where the calculation providing declaration is broadcast by the another node device to a first node device where the data provider node is located in a case where the another node device is determined to be deployed with a chain lower calculation engine that supports execution of the collaborative calculation task.

Optionally, the proxy access engine is configured to:

and encrypting the data read from the first node equipment through a certification storage public key corresponding to the down-link computing engine maintained by the down-link computing contract to obtain encrypted data, and sending the encrypted data to the down-link computing engine.

Optionally, the certificate-stored public key corresponding to the offline calculation engine maintained by the offline calculation contract is triggered and updated by a key update transaction initiated by the second calculation device, where the key update transaction is initiated by the second calculation device under the condition that a key update event generated by the offline calculation contract is monitored, and the key update transaction carries a latest public key corresponding to the offline calculation engine, which is obtained by the second node device in response to the key update event.

Optionally, the chain-down computation contract is used to trigger generation of the rekeying event in an initialization phase of successful deployment or in response to a rekeying transaction.

Fig. 6 is a block diagram of a data processing apparatus provided in the present specification according to an exemplary embodiment, which may be applied to the device shown in fig. 4 to implement the technical solution of the present specification; the device is applied to second node equipment, second block chain nodes are deployed on the second node equipment, and a block chain network to which the second block chain nodes belong is deployed with a down-chain calculation contract; the device comprises:

a second event monitoring unit 601, configured to monitor a task event for a collaborative computing task generated by the down-link computing contract.

A data obtaining unit 602, configured to, in a case that it is determined that the second block link node belongs to a computation provider node of the collaborative computation task, invoke a down-link computation engine deployed by the second node device to execute the collaborative computation task, where the down-link computation engine is configured to: in the process of executing the collaborative computing task, data read from a first node device by an agent access engine deployed on the first node device where a data provider node of the collaborative computing task is located is acquired, and a first block chain node deployed on the first node device does not belong to the computing provider node.

Optionally, the task event records description information of the data provider node.

Optionally, the method further includes:

a second calculation provider node determining unit 603, configured to determine that a second blockchain link point belongs to the calculation provider node when the description information of the calculation provider node recorded in the task event includes identification information of a second blockchain node or a second node device deploys a calculation engine under a chain that supports execution of the collaborative calculation task.

Optionally, the method further includes:

a calculation providing declaration broadcasting unit 604, configured to broadcast the calculation providing declaration to a first node device where the data provider node is located, so that the first node device belongs to the calculation provider node for a second tile link node, in a case where it is determined that the second node device is deployed with an in-chain calculation engine that supports execution of the cooperative calculation task.

Optionally, the method further includes:

a calculation task execution unit 605, configured to, in a case that it is determined that a second chunk link node belongs to both the calculation provider node and the data provider node, invoke the calculation engine to execute the collaborative calculation task, where the calculation engine is configured to: and in the process of executing the cooperative computing task, acquiring local data read from the second node device and data read from the first node device by the agent access engine, wherein the first block chain node deployed on the first node device does not belong to the computing provider node.

Optionally, the method further includes:

a certificate storing public key updating unit 606, configured to, when a key updating event generated by the calculation contract under the chain is monitored, obtain a latest public key corresponding to the calculation engine under the chain, initiate, to the calculation contract under the chain, a key updating transaction carrying the latest public key through a second block chain node, so as to update the certificate storing public key corresponding to the calculation engine under the chain, which is maintained by the calculation contract under the chain, to the latest public key.

Optionally, the certificate storing public key updating unit 606 is specifically configured to:

under the condition that the key updating event generated in the initialization stage of successful deployment of the calculation contract under the chain is monitored, the latest public keys corresponding to all calculation engines under the chain deployed by the second node equipment are obtained; alternatively, the first and second electrodes may be,

and in the case that the key updating event generated by the under-chain computing contract in response to the rekeying transaction is monitored and the first node device is determined to be deployed with a target under-chain computing engine indicated by the key updating event, acquiring the latest public key corresponding to the target under-chain computing engine.

In the 90's of the 20 th century, improvements to a technology could clearly distinguish between improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements to process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

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 (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be regarded as a hardware component and the means for performing the various functions included therein may also be regarded as structures within the hardware component. Or even means for performing the functions may be conceived to be both a software module implementing the method and a structure within a hardware component.

The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. One typical implementation device is a server system. Of course, the present invention does not exclude that with future developments in computer technology, the computer implementing the functionality of the above embodiments may be, for example, a personal computer, a laptop computer, a vehicle mounted human interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device or a combination of any of these devices.

Although one or more embodiments of the present description provide method operational steps as described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive approaches. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of sequences, and does not represent a unique order of performance. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in processes, methods, articles, or apparatus that include the recited elements is not excluded. For example, the use of the terms first, second, etc. are used to denote names, but not to denote any particular order.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, etc. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

One skilled in the art will appreciate 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 combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

One or more embodiments of the present description 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 particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

The above description is merely exemplary of one or more embodiments of the present disclosure and is not intended to limit the scope of one or more embodiments of the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present specification should be included in the scope of the claims.

Claims

1. A data processing method is applied to first node equipment with a first block chain node, and a block chain network to which the first block chain node belongs is provided with a calculating contract under a chain; the method comprises the following steps:

2. The method according to claim 1, wherein the calculation contract maintains a task completion status corresponding to a calculation task under the link, and the task completion status is used for describing a completion status of each subtask included in the calculation task under the link; in a case that the collaborative computing task belongs to a subtask of the calculation task under the chain, the monitoring a task event generated by the calculation contract under the chain and aiming at the collaborative computing task includes:

3. The method according to claim 2, wherein the task completion status is updated by the under-chain computation contract in response to a transaction trigger corresponding to the under-chain computation task, wherein the transaction corresponding to the under-chain computation task includes a task creation transaction corresponding to the under-chain computation task, or a result return transaction initiated by any node device when any of the subtasks is completely executed.

4. The method of claim 1, the invoking a proxy access engine deployed by a first node device to perform the collaborative computing task, comprising:

5. The method of claim 1, the proxy access engine to:

reading pre-reading data indicated by the task event from a first node device, and transmitting the pre-reading data to the down-link computing engine in response to a data access request sent by the down-link computing engine; alternatively, the first and second electrodes may be,

6. The method of claim 1, further comprising:

determining that a first block link point belongs to the data provider node when description information of the data provider node recorded in the task event includes identification information of the first block link node;

and determining that the first blockchain node does not belong to the computation provider node when the description information of the computation provider node recorded in the task event does not contain the identification information of the first blockchain node or a chain-down computation engine supporting the execution of the collaborative computation task is not deployed on the first node device.

7. The method of claim 1, further comprising:

in the event that a computation providing statement sent by another node device is received, attributing the chunk link nodes deployed on the other node device to the computation provider node, wherein the computation providing statement is broadcast by the other node device to a first node device where the data provider node is located in the event that it is determined that the other node device is deployed with an in-chain computation engine that supports execution of the collaborative computation task.

8. The method of claim 1, the proxy access engine to:

9. The method according to claim 8, wherein the certified public key corresponding to the calculation engine under the chain maintained by the calculation contract under the chain is updated by a key update transaction initiated by a second computing device, the key update transaction is initiated by the second computing device when a key update event generated by the calculation contract under the chain is monitored, and the key update transaction carries a latest public key corresponding to the calculation engine under the chain acquired by the second node device in response to the key update event.

10. The method of claim 9, the down-chain computation contract to trigger generation of the rekeying event in an initialization phase of a successful deployment or in response to a rekey transaction.

11. A data processing method is applied to second node equipment, wherein second block chain nodes are deployed on the second node equipment, and a block chain network to which the second block chain nodes belong is deployed with a down-link calculation contract; the method comprises the following steps:

in a case that it is determined that the second block link point belongs to a computation provider node of the collaborative computation task, invoking an off-chain computation engine deployed by the second node device to perform the collaborative computation task, the off-chain computation engine being configured to: in the process of executing the collaborative computing task, data read from a first node device by an agent access engine deployed on the first node device where a data provider node of the collaborative computing task is located is acquired, and a first block chain node deployed on the first node device does not belong to the computing provider node.

12. The method of claim 11, wherein the task event has recorded therein descriptive information of the data provider node.

13. The method of claim 11, further comprising:

and determining that a second blockchain link point belongs to the computation provider node when the description information of the computation provider node recorded in the task event includes identification information of a second blockchain node or a second node device deploys a calculation engine under a chain supporting execution of the collaborative computation task.

14. The method of claim 11, further comprising:

in the event that it is determined that a second node device is deployed with an in-chain compute engine that supports performing the collaborative compute task, broadcasting the compute offer statement to a first node device at which the data provider node is located to cause the first node device to ascribe a second blockchain link point to the compute provider node.

15. The method of claim 11, further comprising:

in the event that it is determined that a second chunk link node belongs to both the compute provider node and the data provider node, invoking the down-chain compute engine to perform the collaborative compute task, wherein the down-chain compute engine is configured to: and in the process of executing the cooperative computing task, acquiring local data read from the second node device and data read from the first node device by the agent access engine, wherein the first block chain node deployed on the first node device does not belong to the computing provider node.

16. The method of claim 11, the down-link compute engine to: and acquiring encrypted data sent by the agent access engine, wherein the encrypted data is obtained by encrypting the data read from the first node equipment by the agent access engine through a certification storage public key corresponding to the down-link computation engine maintained by the down-link computation contract.

17. The method of claim 16, further comprising:

and under the condition that a key updating event generated by the calculation contract under the chain is monitored, acquiring a latest public key corresponding to the calculation engine under the chain, and initiating a key updating transaction carrying the latest public key to the calculation contract under the chain through a second block chain node so as to update a certificate storing public key corresponding to the calculation engine under the chain maintained by the calculation contract under the chain into the latest public key.

18. The method of claim 17, the down-chain computation contract is used to trigger generation of the rekeying event in an initialization phase of deployment success or in response to a rekey transaction.

19. The method of claim 18, wherein obtaining the latest public key corresponding to the calculation engine under the condition of monitoring the key update event generated by the calculation contract under the chain comprises:

20. A data processing device is applied to first node equipment with a first block chain node, and a block chain network to which the first block chain node belongs is provided with a calculation contract under a chain; the device comprises:

21. A data processing device is applied to second node equipment, wherein second block chain nodes are deployed on the second node equipment, and a block chain network to which the second block chain nodes belong is deployed with a down-link calculation contract; the device comprises:

22. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 1-19 by executing the executable instructions.

23. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 19.