Collaborative task execution method and device, and block chain system
By using gateways and proxy domain names in blockchain nodes, the interaction between computing service components is achieved, and the problems of complexity and security risks of computing service network configuration in blockchain systems are solved, thereby improving system stability and security.
Patent Information
- Application Number
- CN202411215395.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2044-08-30
AI Technical Summary
The network configuration of computing services in the blockchain system is complex and has security risks, and requires centralized management of nodes to affect service stability.
By introducing gateways into blockchain nodes, allocating proxy domain names to register computing service components, the interaction between computing service components is realized, avoiding external exposure of service ports and reducing the dependence of centralized management nodes.
Simplifies port management, improves system security and service stability, and realizes the distributed deployment and operation of computing services.
Smart Images

Figure CN118972394A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of this specification belong to the field of blockchain technology, and in particular, relate to a method and device for executing collaborative tasks, and a blockchain system. Background Art
[0002] Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. In the blockchain system, data blocks are combined into a chain data structure in a sequential manner according to chronological order, and a distributed ledger that cannot be tampered with or forged is guaranteed by cryptography.
[0003] Users can participate in blockchain collaborative computing and other related affairs through blockchain nodes. For example, multiple blockchain nodes corresponding to different users in the blockchain system can deploy computing services to perform multi-party joint computing such as secure multi-party computing (SMPC) or federated learning (FL) based on privacy technologies such as homomorphic encryption and zero-knowledge proof. To this end, related technologies often require complex network configuration of computing services to expose the access ports of computing services to the outside world. For example, it is necessary to configure corresponding IP addresses for each computing service or deploy complex DNS resolution services. This method has high service port management complexity and often requires exposing the access ports of node devices to the Internet, which poses a high security risk. In addition, the above computing services usually need to be registered to a centralized management node for unified scheduling by the node. Therefore, if the management node fails, it will affect the normal operation of the computing service and the service stability is poor. Summary of the invention
[0004] The purpose of the present invention is to provide a method and device for executing collaborative tasks, and a blockchain system.
[0005] According to a first aspect of one or more embodiments of this specification, a method for executing a collaborative task is proposed, which is applied to a first node in a blockchain system, wherein the first node includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway, and the method includes:
[0006] The first target computing service component participating in the online collaborative computing task in the at least one first computing service component submits the task description information of the online collaborative computing task to the first gateway;
[0007] The first gateway determines a second target proxy domain name generated according to the task description information, the second target proxy domain name is used to represent a second target computing service component in the second node and is registered to a second gateway in the second node; and, sends the task description information to the second gateway according to the second target proxy domain name, so that the second gateway forwards the task description information to the second target computing service component;
[0008] The first target computing service component and the second target computing service component jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0009] According to a second aspect of one or more embodiments of the present specification, a collaborative task execution device is provided, which is applied to a first node in a blockchain system, wherein the first node includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway, and the device includes:
[0010] An information submitting unit, configured to enable a first target computing service component participating in the online collaborative computing task among the at least one first computing service component to submit task description information of the online collaborative computing task to the first gateway;
[0011] an information sending unit, configured to enable the first gateway to determine a second target proxy domain name generated according to the task description information, the second target proxy domain name being used to represent a second target computing service component in the second node and being registered to a second gateway in the second node; and, to send the task description information to the second gateway according to the second target proxy domain name, so that the second gateway forwards the task description information to the second target computing service component;
[0012] The collaborative computing unit is used to enable the first target computing service component and the second target computing service component to jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0013] According to a third aspect of one or more embodiments of the present specification, a blockchain system is proposed, wherein a first node in the blockchain system includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway; a second node includes a second gateway and at least one second computing service component, and a second proxy domain name of each second computing service component is registered to the second gateway, wherein:
[0014] The first target computing service component participating in the online collaborative computing task in the at least one first computing service component is used to submit task description information of the online collaborative computing task to the first gateway;
[0015] The first gateway is used to determine a second target proxy domain name generated according to the task description information, the second target proxy domain name is used to represent a second target computing service component in the second node; and, according to the second target proxy domain name, the task description information is sent to the second gateway, so that the second gateway forwards the task description information to the second target computing service component;
[0016] The first target computing service component and the second target computing service component are used to jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0017] According to a fourth aspect of one or more embodiments of this specification, an electronic device is provided, including:
[0018] A processor; a memory for storing processor-executable instructions; wherein the processor implements the method as described in any one of the first aspects by running the executable instructions.
[0019] According to a fifth aspect of one or more embodiments of the present specification, a computer-readable storage medium is provided, on which computer instructions are stored, and when the instructions are executed by a processor, the steps of the method described in any one of the first aspects are implemented.
[0020] According to a sixth aspect of one or more embodiments of this specification, a computer program product is proposed, comprising a computer program and / or instructions, which, when executed by a processor, implement the steps of the method as described in any one of the first aspects.
[0021] In the above embodiment, the first target computing service component participating in the online collaborative task in the first node submits the task description information of the task to the first gateway, and the first gateway sends the information to the second gateway according to the second target proxy domain name, so that the second gateway forwards the information to the second target computing service component, so that the first target computing service component and the second target computing service component jointly participate in the execution of the above online collaborative task according to the workflow. It can be seen that the first and second target computing service components participating in the execution of the online collaborative task use the gateways in their respective nodes to transmit the task description information, and use the information to participate in the online collaborative computing.
[0022] It can be understood that this solution realizes the interaction between computing service components based on the proxy capability of the gateway in the node, that is, assigning a proxy domain name to each computing service component and registering it to the corresponding gateway, and then realizing service addressing and interaction based on the proxy domain name. It can be seen that this solution does not need to expose the service ports of computing service components or even node devices to the outside, which not only avoids complex port management problems, but also has high device / system security. In addition, the different computing service components involved in this solution are deployed in different nodes, and different computing service components only need each other's proxy domain name to interact with the gateway, realizing the distributed deployment and operation of computing services, without the need to set up a centralized management node, which helps to improve service stability. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0024] Figure 1 It is a structural diagram of a blockchain system provided by an exemplary embodiment.
[0025] Figure 2 It is a flowchart of a method for executing a collaborative task provided by an exemplary embodiment.
[0026] Figure 3 It is a flowchart of another method for executing a collaborative task provided by an exemplary embodiment.
[0027] Figure 4 It is a structural schematic diagram of a device provided by an exemplary embodiment.
[0028] Figure 5 It is a block diagram of a collaborative task execution device provided by an exemplary embodiment. DETAILED DESCRIPTION
[0029] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.
[0030] To solve the above problems in the related art, this specification proposes a method for executing collaborative tasks, which enables computing service components in different nodes to interact using the proxy capabilities of the gateway, thereby completing cross-node online collaborative computing. The solution is described in detail below with reference to the accompanying drawings.
[0031] See also Figure 1 , Figure 1 This is a schematic diagram of the structure of a blockchain system provided by an exemplary embodiment. Figure 1 As shown, the blockchain system may include at least one blockchain network, such as net1 and net2; wherein each blockchain network includes multiple blockchain nodes (hereinafter referred to as nodes), such as net1 includes nodes A to E, and net2 includes nodes F to I. In addition, each node in the blockchain system may include multiple functional components, such as a gateway, a computing service component, a business layer, a collaboration engine, etc. Exemplarily, node A in net1 includes a gateway and multiple computing service components (i.e., computing service components a1 to computing service components a3), and node B includes a gateway and a computing service component (i.e., computing service component b1); of course, nodes A and B also include other functional components, which will not be repeated. The "functional component" in any node described in the embodiments of this specification should be understood as a functional module at the logical level, which can be deployed in a container in the form of a microservice (such as deployed under the Kubernetes microservice architecture), and constitute a blockchain node at the logical level through service calls.
[0032] In addition, any node in the blockchain network can also connect to the corresponding tenant (or user, Figure 1 ), such as connecting to the blockchain client used by the tenant. The tenants corresponding to any two nodes may be the same or different. For example, node A is connected to the blockchain client A used by tenant A, node B is connected to the blockchain client B used by tenant B, etc. The above tenants can interact with the corresponding nodes through the blockchain client they use to access the blockchain network.
[0033] Different nodes in the system can interact through their own gateways (wherein, there may be gateways of other nodes as relays on the interaction path between the two). For example, in the case where a blockchain network is a fully connected network, the gateway of any node can directly access the gateway of any other node; in the case of a non-fully connected network, any two gateways can directly access each other or use other gateways as relays to achieve multi-hop access. In addition, the gateways contained in two blockchain nodes belonging to different blockchain networks can interact by borrowing the cross-chain channel between the two networks, and the embodiments of this specification do not limit this.
[0034] Among them, any gateway described in the embodiments of this specification can support one-way connection and two-way communication. After the blockchain node joins the network, its gateway automatically connects with the gateway of the existing node in the network to facilitate subsequent communication between nodes. Various functional components with external data interaction requirements in the same node can share the gateway, that is, use the gateway as a unified external interface to achieve communication. Therefore, for dynamically deployed computing service components, there is no need to open corresponding ports to the Internet / other nodes for each component. In addition, the gateway can also support identity verification capabilities to reduce the risk of port opening, which will not be repeated.
[0035] The embodiment of this specification proposes a blockchain system, in which a first node in the blockchain system includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway; a second node includes a second gateway and at least one second computing service component, and a second proxy domain name of each second computing service component is registered to the second gateway, wherein:
[0036] The first target computing service component participating in the online collaborative computing task in the at least one first computing service component is used to submit task description information of the online collaborative computing task to the first gateway;
[0037] The first gateway is used to determine a second target proxy domain name generated according to the task description information, the second target proxy domain name is used to represent a second target computing service component in the second node; and, according to the second target proxy domain name, the task description information is sent to the second gateway, so that the second gateway forwards the task description information to the second target computing service component;
[0038] The first target computing service component and the second target computing service component are used to jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0039] In one embodiment, the online collaborative task to be executed is initiated by the first node and jointly executed by the first target computing service component in the first node and the second target computing service component in the second node. Of course, it can also be considered that the first node and the second node jointly execute the task.
[0040] The first node described in the embodiment of this specification is used as a task initiator and participant, and the second node is only a task participant. The two are different blockchain nodes in the blockchain system. The two can belong to the same blockchain network, or they can belong to different blockchain networks. Among them, the number of first nodes is one, and the number of second nodes is one or more. Correspondingly, each computing service component in the first node is called a first computing service component, and the one that initiates and participates in the execution of online collaborative tasks is called a first target computing service component, and the number is one; each computing service component in the second node is called a second computing service component, and the one that participates in the execution of online collaborative tasks is called a second target computing service component, and the number is one or more.
[0041] Given that multiple computing service components of the same or different types may be deployed in the same blockchain node, there may be multiple computing service components in any node participating in the execution of online collaborative tasks. In the case where there are multiple computing service components participating in the execution of online collaborative tasks in the first node, these computing service components include other first computing service components in addition to the first target computing service component. At this time, only the first target computing service component can submit the task description information to the first gateway, without the need for the other first computing service components to submit, so as to avoid submitting the same task description information separately, resulting in too many repeated interactive messages in the network.
[0042] In addition, the proxy domain name of each computing service component in any node will be registered on the gateway in the node, such as when the component is deployed, the corresponding proxy domain name is assigned to the component and registered on the corresponding gateway. Among them, the proxy domain name of the first computing service component is called the first proxy domain name, and the proxy domain name of the first target computing service component is called the first target proxy domain name; similarly, the proxy domain name of the second computing service component is called the second proxy domain name, and the proxy domain name of the second target computing service component is called the second target proxy domain name. In this way, after any computing service component is deployed, the node (such as the collaboration engine) will automatically register (or inject) its proxy domain name into the gateway without the need for tenants or managers to manually configure network information. In one embodiment, the relevant description information of any target computing service component can be obtained, and this information can be arranged based on preset rules to generate the proxy domain name of the component. Exemplarily, for any computing service component in any node, the network identifier of the blockchain network where the node is located, the node identifier of the node, and the service component identifier of the component (such as a unique service name, service number, etc.) can be obtained, and then the proxy domain name of the component is generated according to the above identifiers. Figure 1Taking the computing service component a1 deployed in the node A as an example, its proxy domain name can be {net1,A,a1}; similarly, the proxy domain name of the computing service component b1 deployed in the node B can be {net2,B,b1}, which will not be repeated here.
[0043] In addition, in addition to the aforementioned computing service components (i.e., computing components used to provide collaborative computing services to the outside world) that can be used to perform online collaborative tasks, the node may also include ordinary computing components that are only used to perform local tasks. In order to distinguish these two types of components, an online collaborative identifier used to characterize this function, such as "online", can be added to the proxy domain name of the aforementioned computing service component to facilitate subsequent accurate calling of the corresponding type of component. Exemplarily, the proxy domain name of the aforementioned computing service component a1 can be {net1,A,a1,online}, and the proxy domain name of the computing service component b1 can be {net1,B,b1,online}, etc., which will not be repeated here.
[0044] Multi-party data collaboration scenarios are usually divided into two categories. One is multi-party computing and processing for batch data, which is characterized by large scale, large amount of calculation, and low timeliness requirements. It is generally called "offline" computing tasks, such as model training, large-scale data analysis, etc., which are all "offline" tasks. The other type is to directly connect to the platform or system, provide a real-time access interface, and user requests reach the online service according to a certain distribution granularity. It is sensitive to interface timeliness response delays and has a small amount of single calculation data. It is generally called "online" computing tasks. The online collaborative computing tasks described in the embodiments of this specification belong to the above-mentioned online computing tasks; and the offline collaborative computing tasks belong to the above-mentioned offline computing tasks, which are hereby explained.
[0045] See also Figure 2 , Figure 2 FIG. 1 is a flowchart of a method for executing a collaborative task provided by an exemplary embodiment. Figure 2 As shown, the method includes steps 202-206.
[0046] Step 202: A first target computing service component participating in an online collaborative computing task among the at least one first computing service component submits task description information of the online collaborative computing task to a first gateway.
[0047] The first target computing service component participating in executing the task in the first node initiating the online collaborative task needs to first obtain the task description information of the task and submit it to the first gateway in the first node.
[0048] In one embodiment, the first node may also include a first business layer, which is a functional component in the first node for implementing business processing logic. At this time, the first business layer may determine the first target computing service component and provide it with task description information of the online collaborative task. For example, when receiving an online collaborative request, the first business layer may parse the request to obtain the task description information; then, based on the information, determine the first target computing service component that participates in executing the task from at least one first computing service component included in the first node, and send the task description information to the component. In this way, the first business layer can accurately determine the first target computing service component that participates in executing the task from the various computing service components of the first node.
[0049] Among them, the first business layer can connect to the blockchain client corresponding to the first node, and the first business layer can receive the online collaboration request sent by the blockchain client. If the user corresponding to the first node has a need for collaborative computing, the user can initiate the above-mentioned online collaboration request to the first business layer through the blockchain client used by him to trigger the first node to initiate an online collaboration task. Alternatively, based on the transaction execution function possessed by the first node, the first business layer can also monitor the online collaboration request generated by the first node executing the blockchain transaction. For example, the first business layer can monitor the events generated when the first node executes the smart contract called by the exchange through a monitoring mechanism, and identify the above-mentioned online collaboration request therefrom. After receiving the online collaboration request in the above manner, the first business layer can parse the request and extract the task description information of the online collaboration task therefrom.
[0050] Among them, the task description information of the online collaborative task described in the embodiment of this specification may include two types of information: participant information and execution information. Among them, the participant information is used to indicate the various computing service components involved in the execution of the task, for example, it may include node information (such as the node identifier of the node where the computing service component is located, the network identifier of the blockchain network to which the node belongs, etc.), service component identifier (i.e., the name / ID and other identifiers of each target computing service component involved in the execution of the task), and in some embodiments, it may also include service deployment related information (source code, computing model, etc. required for the deployment of the target computing service component). The execution information is used to indicate the specific method / process of each participant participating in the execution of the task, for example, it may include workflow description information (describing the order in which each participant participates in the execution of the task, data interaction process, etc.) and data information (such as the original data and / or its access address required for each participant to execute the task, etc.).
[0051] In one embodiment, the first node may also include a first collaboration engine, which is used to deploy and pull up a computing service component. For example, before receiving the online collaboration request, the first business layer may instruct the first collaboration engine to deploy the at least one first computing service component belonging to the first node, and thereafter, the first collaboration engine may register the first proxy domain names of each first computing service component that has been deployed to the first gateway. In this way, the first collaboration engine can deploy at least one computing service component in advance (before the initiator initiates the online collaboration task) so that it can be called when the task is subsequently executed, which helps to shorten the overall time consumed to execute the task. For another example, after parsing the task description information from the received online collaboration request, the first business layer may instruct the first collaboration engine to deploy the first target computing service component that participates in the execution of the online collaborative computing task according to the service deployment related information therein, and register the proxy domain name of the deployed first target computing service component to the first gateway. Of course, in the case where other first computing service components are included in addition to the first target computing service component in the first node participating in the execution of the task, the first business layer may also instruct the first collaboration engine to deploy the other first computing service components, that is, instruct the engine to deploy the various computing service components that participate in the execution of the task. In this way, the first collaboration engine only temporarily generates the corresponding first computing service component when it needs to perform online collaboration tasks (i.e., when there is a demand for online collaboration), which helps to avoid the situation where the deployed components are not used for a long time, thereby reducing the invalid occupation of resources of the first node and improving its resource utilization to a certain extent. In the above embodiment, each proxy domain name can be generated by the first collaboration engine, or it can be generated by the first business layer and sent to the first collaboration engine (such as included in the corresponding indication message), and the embodiments of this specification do not limit this.
[0052] After obtaining the task description information of the online collaborative task in the aforementioned manner, the first business layer can determine the first target computing service component that participates in executing the task from at least one computing service component of the first node based on the information. For example, when the task description information includes a service component identifier, the first target computing service component can be directly determined based on the identifier. Alternatively, when the task description information includes information such as a network identifier, a node identifier, and a service name, the first proxy domain name of the first target computing service component can also be generated based on the information, and the first target computing service component can be determined based on the domain name.
[0053] In one embodiment, after obtaining the task description information by any of the aforementioned methods, the first business layer or the first collaboration engine can determine the second gateways corresponding to each participant according to the information, and then initiate a collaboration inquiry message to the second collaboration engine in the corresponding second node through the gateway to instruct the second collaboration engine to confirm whether the corresponding second target computing service component participates in the execution of the task; further, after receiving the collaboration confirmation message returned by the other party, it can instruct to execute subsequent steps (such as instructing the first collaboration engine to deploy the first target computing service component, or instructing the first target computing service component to submit the task description information to the first gateway, etc.) to continue to execute the online collaboration task. Otherwise, if no message is received or a corresponding collaboration rejection message is received, it can instruct to terminate the execution of the task.
[0054] As mentioned above, the first business layer can receive an online collaboration request initiated by a blockchain client or monitor an online collaboration request generated by a transaction executed by the first node, and then determine the first target computing service component based on the task description information parsed from the request. In addition, when the first node includes a first transaction execution component, the component can generate task description information of an online collaborative task during the execution of a blockchain transaction, and further determine the first target computing service component based on the information, and then send the task description information to the component; in other words, the first target computing service component can directly receive the task description information generated and sent by the first transaction execution component when executing a blockchain transaction. For example, the first transaction execution component can determine the first target computing service component based on the aforementioned service component identifier and other information, and then send the remaining task description information to the component.
[0055] As mentioned above, the first node may also include a first collaboration engine. Wherein, when the first node and the second node belong to the same blockchain network, the first collaboration engine may deploy a smart contract containing the workflow of the online collaboration task in the network, so that the second node obtains the workflow by executing the smart contract (such as obtaining the workflow by monitoring the events generated by the execution of the contract), and participates in the execution of the online collaboration task according to the workflow. It is understandable that after the second node obtains the workflow, it can determine the second target computing service component that participates in the execution of the online collaboration task from the second computing service component that has been deployed locally, or, in the case where the second target computing service component does not exist locally, the component may also be temporarily deployed locally. In this way, the workflow of the online collaboration task can be synchronized to other participants by deploying a smart contract, which not only ensures that each participant obtains the workflow separately, but also enables the storage of the workflow, which is convenient for tracing the execution process after the online collaboration task is completed.
[0056] As mentioned above, the proxy domain name of the target computing service component that participates in the execution of the online collaborative task may include an online collaborative identifier (such as "online"). In addition to participating in the execution of the online collaborative task, the first target computing service component may also participate in the execution of other types of computing tasks. At this time, the proxy domain name in the message it generates may not include the above-mentioned online collaborative identifier. In view of this, in order to effectively distinguish the messages of different tasks and process them separately, when the second target proxy domain name is generated by the first target computing service component, the first target computing service component can determine whether the domain name contains the aforementioned online collaborative identifier, and when confirming that the identifier is contained, submit the task description information to the first gateway, thereby realizing differentiated processing of different types of messages.
[0057] As the interface of the first node for external data interaction, the functional components in the first node can communicate with the subject outside the node through the first gateway. Therefore, after obtaining the task description information of the above online collaborative task, the first target computing service component can submit the information to the first gateway, so that the first gateway can send it to the corresponding second gateway.
[0058] In step 204, the first gateway determines a second target proxy domain name generated according to the task description information, where the second target proxy domain name is used to represent a second target computing service component in the second node and is registered to a second gateway in the second node; and, sends the task description information to the second gateway according to the second target proxy domain name, so that the second gateway forwards the task description information to the second target computing service component.
[0059] In one embodiment, the first gateway can determine the second target proxy domain name in a variety of ways. For example, after receiving the task description information, the second target proxy domain name can be generated based on the information. For another example, the first gateway can also receive the first target proxy domain name sent by the first target computing service component after it is generated based on the above-mentioned task description information, such as the first target computing service component can submit the domain name together with the task description information to the first gateway. This method can simplify the processing flow of the first gateway and facilitate the first gateway to achieve efficient forwarding of information. Among them, the first target computing service component can send a message containing the task description information to the first gateway (or traffic import). For example, when the blockchain system is deployed in a k8s cluster, traffic import can be completed based on the CoreDns plug-in.
[0060] As mentioned above, the task description information may include the network identifier, node identifier, and service component identifier corresponding to each participant. Therefore, in one embodiment, when the first gateway or the first target computing service component generates the second target proxy domain name according to the task description information, it can first determine from the information the second node identifier other than the first node identifier of the first node, the second network identifier of the blockchain network to which the second node represented by the second node identifier belongs, and the second service identifier of the second target computing service component in the second node, and then generate the second target proxy domain name of the second target computing service component according to the above second node identifier, the second network identifier, and the second service identifier. It can be understood that the task description information contains the above identification information corresponding to each second target computing service component, so the second target proxy domain name of each second target computing service component can be generated respectively in this way. For example, let's assume Figure 1 Node A in the system shown is the first node. If the generated second target proxy domain name includes {net1,B,b1} (or {net1,B,b1,online}, the same below), it means that the second target computing service component is only the computing service component b1 in node B; if the generated second target proxy domain name includes {net1,B,b1} and {net1,C,c2}, it means that the second target computing service component includes component b1 in node B and computing service component c2 in node C; if the generated second target proxy domain name includes {net1,B,b2} and {net2,G,g1}, it means that the second target computing service component includes computing service component b1 in node B and computing service component g2 in node G, which will not be repeated.
[0061] In addition, since the second target proxy domain name is determined in this way to represent the second target computing service component participating in the online collaborative task, a preset online collaboration identifier can be added to a specific position (such as the tail) of the domain name. For example, when {net1, B, b1, online} is generated, the domain name also indicates that the second target computing service component includes the computing service component b1 in node B.
[0062] In one embodiment, the first gateway may maintain a routing table, which may be used to record the mapping relationship between the access addresses of other gateways and the proxy domain name of the computing service component in the node where it is located. For example, after the collaboration engine in any node deploys and registers a new computing service component, the gateway may update the routing table maintained by itself and synchronize the update to the gateways of other nodes in the system, so that other gateways can access the component according to the updated routing table. Based on this, when sending the task description information to the second gateway, if the second target proxy domain name exists in the routing table maintained by itself, the first gateway may determine the access address corresponding to the second target proxy domain name in the routing table as the access address of the second gateway, and send the task description information to the second gateway according to the access address. On the contrary, if the second target proxy domain name does not exist in the routing table maintained by itself, the first gateway may send the second target proxy domain name and the task description information to the corresponding third gateway according to at least one access address recorded in the routing table, so that the third gateway forwards the task description information to the second gateway based on the second target proxy domain name. It can be seen from this that if the routing table of the first gateway records the correspondence between the access address of the second gateway and the proxy domain name of each second computing service component, the access address of the second gateway can be directly found according to the second target proxy domain name, and the task description information can be sent to it according to the address, that is, the first gateway can directly access the second gateway. On the contrary, if the above correspondence is not recorded in the routing table of the first gateway, the first gateway cannot directly access the second gateway. At this time, it is necessary to use at least one third gateway that the first gateway can directly access to realize the forwarding of the task description information (actually the message containing the message) through a multi-hop mechanism until the message reaches the second gateway. In the above way, the proxy domain name can be relied on to ensure that the first gateway accurately transmits the task description information to the second gateway.
[0063] In one embodiment, when the first node includes multiple first computing service components, in addition to the first target computing service component participating in the execution of the online collaborative task, there may be other first computing service components that need to participate in the execution of the task. In this regard, when the task description information indicates that the participants of the online collaborative task also include other first computing service components, the first target computing service component can send the task description information to the other first computing service components, so that the latter can participate in the execution of the online collaborative computing task together with the first target computing service component and the second target computing service component according to the workflow described. It can be understood that because the first target computing service component and the other first computing service components are in the same first node, the task description information can be transmitted between the two without relying on the first gateway, that is, the first target computing service component can directly send the information to each other first computing service component (such as the processes where the two are located can perform inter-process communication), thereby reducing the workload of the first gateway and improving the sharing efficiency of the task description information. Of course, when the above-mentioned task description information is determined by the first business layer or the first collaboration engine, the two can also send the information to the first target computing service component and the other first computing service components respectively. In this case, the first target computing service component does not need to send the message to the other first computing service components.
[0064] Step 206: The first target computing service component and the second target computing service component jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0065] After the task description information of the online collaborative task is transmitted to the second target computing service component in the above manner, the first target computing service component and each second target computing service component can jointly participate in the execution of the task according to the workflow of the task, thereby realizing "online collaboration" between multiple nodes. In the process of any target computing service component participating in the execution of the task, it can process its corresponding task-related data according to the above workflow. For example, it can process the task-related data according to any form of data processing logic such as preset formulas, algorithms, models, rules, etc.
[0066] In the above embodiment, the first target computing service component participating in the online collaborative task in the first node submits the task description information of the task to the first gateway, and the first gateway sends the information to the second gateway according to the second target proxy domain name, so that the second gateway forwards the information to the second target computing service component, so that the first target computing service component and the second target computing service component jointly participate in the execution of the above online collaborative task according to the workflow. It can be seen that the first and second target computing service components participating in the execution of the online collaborative task use the gateways in their respective nodes to transmit the task description information, and use the information to participate in the online collaborative computing.
[0067] It can be understood that this solution realizes the interaction between computing service components based on the proxy capability of the gateway in the node, that is, assigning a proxy domain name to each computing service component and registering it to the corresponding gateway, and then realizing service addressing and interaction based on the proxy domain name. It can be seen that this solution does not need to expose the service ports of computing service components or even node devices to the outside, which not only avoids complex port management problems, but also has high device / system security. In addition, the different computing service components involved in this solution are deployed in different nodes, and different computing service components only need each other's proxy domain name to interact with the gateway, realizing the distributed deployment and operation of computing services, without the need to set up a centralized management node, which helps to improve service stability.
[0068] In one embodiment, the first and second target computing service components may need to exchange data through the aforementioned first gateway and second gateway during the process of jointly participating in the execution of an online collaborative task. For example, the first target computing service component may send the intermediate computing result generated by its own calculation to the first gateway, so that the first gateway forwards the intermediate computing result to the second target computing service component through the second gateway for processing. And / or, the second target computing service component may send the intermediate computing result generated by its own calculation to the first target computing service component through the first gateway and the second gateway, so that the latter can perform corresponding processing on the intermediate computing result. Among them, the specific form of the above-mentioned intermediate computing result and the specific manner in which the first target computing service component or the second target computing service component performs subsequent processing on it, etc., can be determined by the specific content of the aforementioned online collaborative task, the aforementioned workflow, and the processing logic of the target computing service component itself, etc., and the embodiments of this specification do not limit this.
[0069] In addition, as a participant in the online collaborative task, the first target computing service component can calculate and generate a first computing result share, and each second target computing service component can calculate and generate a corresponding second computing result share. In this regard, each second target computing service component can send the second computing result share generated by its own calculation to the first target computing service component through the first gateway and the corresponding second gateway, so that the first target computing service component can generate the execution result of the online collaborative task based on the first computing result share and the received second computing result shares. In this way, the first target computing service component as the initiator (and also a participant) uniformly generates the execution result of the task based on the computing result shares calculated by each participant, so that other participants can only know a limited share of the computing result, but cannot know the complete execution result, which helps to avoid the result from being leaked.
[0070] Of course, when the final settlement result needs to be confirmed by each participating party separately, the first target computing service component can also synchronize the result to each second target computing service component and receive the confirmation result returned by the latter; even, each target computing service component can broadcast its own share of the calculation result to other target computing service components, so that each target computing service component can calculate the execution result separately, and when all or most of the execution results are the same result, the result is determined as the execution result of the online collaborative computing task, which will not be repeated.
[0071] In one embodiment, the first node may also include a first collaboration engine and at least one first computing engine, and the second node may also include a second collaboration engine and at least one second computing engine. Based on this, the first collaboration engine may obtain the task description information of the offline collaborative computing task; and send the task description information to the first target computing engine participating in the offline collaborative computing task determined from the at least one first computing engine according to the information, and submit the task description information to the blockchain account maintained by the blockchain network; accordingly, after obtaining the submitted task description information, the second collaboration engine may determine the second target computing engine participating in the offline collaborative computing task from the at least one second computing engine according to the task description information, and send the task description information to the second target computing engine; further, the first target computing engine and the second target computing engine may jointly participate in executing the offline collaborative computing task according to the workflow described by the task description information, and the corresponding execution results are used to deploy the first target computing service component and the second target computing service component.
[0072] In this way, the first target computing engine and the second target computing engine jointly participate in the execution of offline collaborative computing tasks, generate execution results on the chain through multi-party joint computing, and deploy corresponding computing service components based on the execution results. It can be seen that this scheme uses the execution results as logical data for deploying computing service components. It can be understood that, on the one hand, since the execution result is obtained by multi-party joint computing rather than specified by one party, and the task description information involved in its calculation process is tamper-proof and stored in the blockchain account book, it is possible to effectively control the functions of logical data and corresponding computing service components, thereby reducing the corresponding security risks; on the other hand, the generation of logical data and the deployment of computing service components require the joint participation of multiple nodes (that is, the execution results are obtained by multiple computing engines in multiple nodes participating in the execution of offline collaborative computing tasks, and are used to deploy corresponding computing service components in the blockchain network), realizing the distributed deployment and operation of computing services, without the need to set up centralized management nodes, which helps to improve service stability.
[0073] It can be understood that the execution result of the offline collaborative computing task is used to deploy a computing service component, which can be used to execute an online collaborative computing task to provide the corresponding online computing service to the tenant. The above-mentioned execution results may include multiple types. For example, in the case where the online computing service is an online prediction service, the execution result may be a machine learning model generated by offline training, and the first and second computing service components formed by deploying the model are used to provide the online prediction service; and in the case where the online computing service is an online hidden query service, the execution result may be metadata pre-generated by offline collaborative computing, and the first and second computing service components formed by deploying the model are used to provide the online hidden query service, which will not be repeated. It should be noted that the above-mentioned offline training and offline collaborative computing process is the process in which the first node and the second node cooperate with each other to perform the offline collaborative computing task in the embodiment of this specification; and the provision of the online prediction service and the online hidden query service to the outside is the process in which the first node and the second node cooperate with each other to perform the online collaborative computing task in the embodiment of this specification.
[0074] In addition, when the first target computing service component and the second target computing service component jointly participate in executing the offline collaborative computing task, the two can store relevant data involved in the execution process (such as the hash of the intermediate execution results and the final result, etc.) in the aforementioned blockchain account book, so as to realize the full process traceability of the offline collaborative computing task execution process, thereby ensuring that the ownership of the execution product of the task, the finally deployed computing service component, etc. is clear and the life cycle is clear.
[0075] Of course, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0076] Below Figure 1 As shown in the figure, nodes A and B in net1 are the first node and the second node respectively. Figure 3 The process of the two collaborating to perform online collaborative tasks is introduced. Figure 3 This is a flow chart of another method for executing a collaborative task provided by an exemplary embodiment. Figure 3 As shown, the method includes steps 301-306.
[0077] Step 301: Business layer a initiates a component deployment request for computing service component a1 to collaboration engine a; and business layer b initiates a component deployment request for computing service component b1 to collaboration engine b.
[0078] In one embodiment, tenant A and tenant B may pre-negotiate relevant matters of the online collaborative computing task to be executed through an off-chain method (such as an offline channel or an online platform associated with the blockchain network, etc.) to determine the relevant information of each computing service component in node A and node B that participates in executing the task, and after reaching an agreement, each tenant may initiate an online collaboration request for the offline collaborative computing task to the business layer of the corresponding node through the blockchain client used by itself (such as an online prediction request corresponding to the online prediction service, or an online hidden query request corresponding to the online hidden query service, etc.).
[0079] Taking node a as an example, business layer a can initiate the component deployment request to collaboration engine a when receiving an online collaboration request initiated by tenant A through a blockchain client or an online collaboration request generated by a transaction execution component (not shown) of node A. The component deployment request can include source code, model and other relevant data of the computing service component a1 to be deployed.
[0080] Step 302: Collaboration engine a deploys computing service component a1 and registers its proxy domain name with gateway a; and, collaboration engine b deploys computing service component b1 and registers its proxy domain name with gateway b.
[0081] Still taking node a as an example, after the deployment of computing service component a1 is completed, collaboration engine a can determine its proxy domain name and register the domain name with gateway a. The proxy domain name can be obtained from the component deployment request (generated by business layer a), or can be generated by collaboration engine a according to the network identifier, node identifier, service component identifier and other related data in the request.
[0082] Step 303: Business layer a schedules computing service component a1 to execute the online collaborative task.
[0083] In fact, the business layer a may have learned about the online collaboration task before initiating the component deployment request, or may determine the task after the computing service component a1 is deployed. In any case, after the computing service component a1 is deployed and registered, the business layer a may call the component to execute the online collaboration task. The corresponding call request may carry the task description information of the task, or may be determined by the collaboration engine a and sent to the computing service component a1, or may be sent to the computing service component a1 by the aforementioned transaction execution component, etc.
[0084] Step 304: the computing service component a1 submits the task description information of the online collaborative task to the gateway a.
[0085] Step 305 : Gateway a addresses Gateway b based on the proxy domain name of the computing service component b1 , and sends the task description information to Gateway b.
[0086] Step 306: Gateway b forwards the task description information to computing service component b1.
[0087] In response to the call of business layer a, computing service component a1 can transmit the task description information to computing service component b1 through the first gateway, and interact with the component based on the first gateway and the second gateway until the online collaborative task is completed and the corresponding execution result is obtained.
[0088] At this time, the first XX and / or the second XX can return the execution result to the corresponding tenant, thereby completing the response to the aforementioned online collaboration request. For example, in the case where the online collaboration request is an online prediction request, the execution result can be a prediction result, and the first computing service component can return the prediction result to tenant A; and in the case where the online collaboration request is an online hidden query request, the execution result can be a query result, and the first computing service component can return the query result to tenant A, which will not be repeated.
[0089] Figure 4 is a schematic structural diagram of a device provided by an exemplary embodiment. Figure 4At the hardware level, the device includes a processor 402, an internal bus 404, a network interface 406, a memory 408, and a non-volatile memory 410, and may also include hardware required for other functions. One or more embodiments of this specification may be implemented based on software, such as the processor 402 reading the corresponding computer program from the non-volatile memory 410 into the memory 408 and then running it. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.
[0090] like Figure 5 As shown, Figure 5 is a block diagram of a collaborative task execution device provided by this specification according to an exemplary embodiment. The device can be applied to Figure 4 The device shown in the figure is used to implement the technical solution of this specification. The device is applied to the first node in the blockchain system, the first node includes a first gateway and at least one first computing service component, the first proxy domain name of each first computing service component is registered to the first gateway, and the device includes:
[0091] An information submitting unit 501 is configured to enable a first target computing service component participating in an online collaborative computing task in the at least one first computing service component to submit task description information of the online collaborative computing task to a first gateway;
[0092] The information sending unit 502 is used to enable the first gateway to determine a second target proxy domain name generated according to the task description information, where the second target proxy domain name is used to represent the second target computing service component in the second node and is registered to the second gateway in the second node; and, according to the second target proxy domain name, send the task description information to the second gateway, so that the second gateway forwards the task description information to the second target computing service component;
[0093] The collaborative computing unit 503 is used to enable the first target computing service component and the second target computing service component to jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0094] Optionally, the first node further includes a first service layer, and the device further includes:
[0095] The collaboration request acquisition unit 504 is used to enable the first business layer to parse the online collaboration request to obtain the task description information; and to determine the first target computing service component that participates in executing the online collaborative computing task from the at least one first computing service component according to the task description information, and send the task description information to the first target computing service component.
[0096] Optionally, the first node further includes a first collaboration engine, and the apparatus further includes a deployment instruction unit 505, configured to:
[0097] Before receiving the online collaboration request, the first business layer instructs the first collaboration engine to deploy the at least one first computing service component, and the first collaboration engine registers the first proxy domain name of each deployed first computing service component to the first gateway respectively; or
[0098] The first business layer instructs the first collaboration engine to deploy the first target computing service component according to the service deployment related information in the task description information, and the first collaboration engine registers the proxy domain name of the deployed first target computing service component to the first gateway.
[0099] Optionally, the deployment instruction unit 505 is specifically used to:
[0100] Enable the first business layer to receive an online collaboration request sent by the blockchain client; or,
[0101] The first business layer monitors the online collaboration request generated by the first node executing the blockchain transaction.
[0102] Optionally, the first node further includes a first transaction execution component, and the information submission unit 501 is specifically used to:
[0103] The first target computing service component receives the task description information generated and sent by the first transaction execution component when executing the blockchain transaction.
[0104] Optionally, the first node further includes a first collaboration engine, and the device further includes a contract deployment unit 506, which is used to:
[0105] In the case where the first node and the second node belong to the same blockchain network, the first collaboration submits the workflow described by the task description information to the blockchain ledger maintained by the blockchain network, so that the second node can jointly participate in executing the online collaborative computing task based on the submitted workflow.
[0106] Optionally, the information sending unit 502 is specifically configured to:
[0107] enabling the first gateway to generate a second target proxy domain name according to the task description information; or,
[0108] The first gateway is enabled to receive a second target proxy domain name generated by the first target computing service component according to the task description information.
[0109] Optionally, the information sending unit 502 is specifically configured to:
[0110] The first target computing service component or the first gateway determines from the task description information a second node identifier other than the first node identifier of the first node, a second network identifier of the blockchain network to which the second node represented by the second node identifier belongs, and a second service identifier of the second target computing service component in the second node, and generates a second target proxy domain name of the second target computing service component according to the determined second node identifier, second network identifier, and second service identifier.
[0111] Optionally, when the second target proxy domain name is generated by the first target computing service component, the information sending unit 502 is specifically used to:
[0112] The first target computing service component is enabled to submit task description information of the online collaborative computing task to the first gateway when the second target proxy domain name includes the online collaborative identifier.
[0113] Optionally, the first gateway maintains a routing table, the routing table is used to record the mapping relationship between the access address of other gateways and the proxy domain name of the computing service component in the node where the first gateway is located, and the information sending unit 502 is specifically used to:
[0114] When the first gateway has the second target proxy domain name in the routing table, the first gateway determines the access address corresponding to the second target proxy domain name in the routing table as the access address of the second gateway, and sends the task description information to the second gateway according to the access address;
[0115] When the second target proxy domain name does not exist in the routing table, the first gateway sends the second target proxy domain name and the task description information to the corresponding third gateway according to at least one access address recorded in the routing table, so that the third gateway forwards the task description information to the second gateway based on the second target proxy domain name.
[0116] Optionally, also include:
[0117] The other component information sending unit 507 is used to enable the first target computing service component to send the task description information to other first computing service components when the task description information indicates that the participants of the online collaborative computing task also include other first computing service components in the first node except the first target computing service component, so that the other first computing service components and the first target computing service component and the second target computing service component jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
[0118] Optionally, the collaborative computing unit 503 is used to:
[0119] The first target computing service component sends the intermediate computing result generated by its own calculation to the first gateway, so that the first gateway forwards the intermediate computing result to the second target computing service component through the second gateway for processing; or, the first target computing service component receives the intermediate computing result generated by the second target computing service component and sent through the first gateway and the second gateway, and processes the intermediate computing result; and / or,
[0120] The first target computing service component receives the second computing result shares generated by the respective target second target computing service components and sent through the first gateway and the corresponding second gateway, and generates the execution result of the online collaborative computing task based on the first computing result shares generated by its own calculation and the respective second computing result shares received.
[0121] Based on the same concept as the above method, this specification also provides a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the steps of the method described in any of the above embodiments are implemented.
[0122] Based on the same concept as the above method, this specification also provides a computer program product, including a computer program / instruction, which implements the steps of the method described in any of the above embodiments when executed by a processor.
Claims
1. A method for executing a collaborative task, applied to a first node in a blockchain system, wherein the first node includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway, the method comprising: The first target computing service component participating in the online collaborative computing task in the at least one first computing service component submits the task description information of the online collaborative computing task to the first gateway; The first gateway determines a second target proxy domain name generated according to the task description information, where the second target proxy domain name is used to represent a second target computing service component in the second node and is registered to a second gateway in the second node; and, sending the task description information to a second gateway according to the second target proxy domain name, so that the second gateway forwards the task description information to a second target computing service component; The first target computing service component and the second target computing service component jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
2. The method according to claim 1, wherein the first node further comprises a first service layer, and the method further comprises: The first business layer parses the online collaboration request to obtain the task description information; And, determining a first target computing service component participating in the online collaborative computing task from the at least one first computing service component according to the task description information, and sending the task description information to the first target computing service component.
3. The method according to claim 2, wherein the first node further comprises a first collaboration engine, and the method further comprises: Before receiving the online collaboration request, the first business layer instructs the first collaboration engine to deploy the at least one first computing service component, and the first collaboration engine registers the first proxy domain name of each deployed first computing service component to the first gateway respectively; or The first business layer instructs the first collaboration engine to deploy the first target computing service component according to the service deployment related information in the task description information, and the first collaboration engine registers the proxy domain name of the deployed first target computing service component to the first gateway.
4. According to the method of claim 2, the first business layer obtains the online collaboration request, comprising: The first business layer receives an online collaboration request sent by a blockchain client; or, The first business layer monitors the online collaboration request generated by the first node executing the blockchain transaction.
5. According to the method of claim 1, the first node further comprises a first transaction execution component, and the first target computing service component obtains the task description information, comprising: Receive the task description information generated and sent by the first transaction execution component to execute the blockchain transaction.
6. The method according to claim 1, wherein the first node further comprises a first collaboration engine, and the method further comprises: When the first node and the second node belong to the same blockchain network, the first collaboration engine submits the workflow described by the task description information to the blockchain ledger maintained by the blockchain network, so that the second node can jointly participate in executing the online collaborative computing task based on the submitted workflow.
7. According to the method of claim 1, the first gateway determines the second target proxy domain name generated according to the task description information, comprising: The first gateway generates a second target proxy domain name according to the task description information; or, The first gateway receives a second target proxy domain name generated by the first target computing service component according to the task description information.
8. The method according to claim 7, wherein the first target computing service component or the first gateway generates the second target proxy domain name according to the task description information, comprising: Determine from the task description information a second node identifier other than the first node identifier of the first node, a second network identifier of the blockchain network to which the second node represented by the second node identifier belongs, and a second service identifier of a second target computing service component in the second node, and generate a second target proxy domain name of the second target computing service component based on the determined second node identifier, second network identifier, and second service identifier.
9. The method according to claim 1, in the case where the second target proxy domain name is generated by the first target computing service component, the first target computing service component submits the task description information of the online collaborative computing task to the first gateway, comprising: If the second target proxy domain name includes an online collaboration identifier, the task description information of the online collaborative computing task is submitted to the first gateway.
10. The method according to claim 1, wherein the first gateway maintains a routing table, wherein the routing table is used to record the mapping relationship between the access address of other gateways and the proxy domain name of the computing service component in the node where the first gateway is located, and the first gateway sends the task description information to the second gateway according to the second target proxy domain name, comprising: When the first gateway has the second target proxy domain name in the routing table, the first gateway determines the access address corresponding to the second target proxy domain name in the routing table as the access address of the second gateway, and sends the task description information to the second gateway according to the access address; When the second target proxy domain name does not exist in the routing table, the first gateway sends the second target proxy domain name and the task description information to the corresponding third gateway according to at least one access address recorded in the routing table, so that the third gateway forwards the task description information to the second gateway based on the second target proxy domain name.
11. The method according to claim 1, further comprising: When the task description information indicates that the participants of the online collaborative computing task also include other first computing service components in the first node except the first target computing service component, the first target computing service component sends the task description information to the other first computing service components, so that the other first computing service components and the first target computing service component and the second target computing service component jointly participate in executing the online collaborative computing task according to the workflow described in the task description information.
12. The method according to claim 1, wherein the first target computing service component and the second target computing service component jointly participate in executing the online collaborative computing task according to the workflow described by the task description information, including at least one of the following: The first target computing service component sends the intermediate computing result generated by its own computing to the first gateway, so that the first gateway forwards the intermediate computing result to the second target computing service component through the second gateway for processing; The first target computing service component receives the intermediate computing result generated by the second target computing service component and sent through the first gateway and the second gateway, and processes the intermediate computing result; The first target computing service component receives the second computing result shares generated by the respective target second target computing service components and sent through the first gateway and the corresponding second gateway, and generates the execution result of the online collaborative computing task based on the first computing result shares generated by its own calculation and the respective second computing result shares received.
13. The method according to any one of claims 1 to 12, wherein the first node further comprises a first collaboration engine and at least one first computing engine, the second node further comprises a second collaboration engine and at least one second computing engine, and the method further comprises: The first collaboration engine obtains task description information of the offline collaborative computing task; And, sending the task description information to a first target computing engine participating in the offline collaborative computing task determined from the at least one first computing engine according to the information, and submitting the task description information to a blockchain ledger maintained by the blockchain network, so that after the second collaborative engine obtains the submitted task description information, it determines a second target computing engine participating in the offline collaborative computing task from the at least one second computing engine according to the task description information, and sends the task description information to the second target computing engine; The first target computing engine and the second target computing engine jointly participate in executing the offline collaborative computing task according to the workflow described in the task description information, and the execution result of the offline collaborative computing task is used to deploy the first target computing service component and the second target computing service component.
14. A collaborative task execution device, applied to a first node in a blockchain system, wherein the first node includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway, the device comprising: An information submitting unit, configured to enable a first target computing service component participating in the online collaborative computing task among the at least one first computing service component to submit task description information of the online collaborative computing task to the first gateway; An information sending unit, configured to enable the first gateway to determine a second target proxy domain name generated according to the task description information, wherein the second target proxy domain name is used to represent a second target computing service component in the second node and is registered to a second gateway in the second node; and, sending the task description information to a second gateway according to the second target proxy domain name, so that the second gateway forwards the task description information to a second target computing service component; The collaborative computing unit is used to enable the first target computing service component and the second target computing service component to jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
15. A blockchain system, wherein a first node in the blockchain system includes a first gateway and at least one first computing service component, and a first proxy domain name of each first computing service component is registered to the first gateway; The second node includes a second gateway and at least one second computing service component, and the second proxy domain name of each second computing service component is registered to the second gateway, wherein: The first target computing service component participating in the online collaborative computing task in the at least one first computing service component is used to submit task description information of the online collaborative computing task to the first gateway; The first gateway is used to determine a second target proxy domain name generated according to the task description information, the second target proxy domain name is used to represent a second target computing service component in the second node; and, according to the second target proxy domain name, the task description information is sent to the second gateway, so that the second gateway forwards the task description information to the second target computing service component; The first target computing service component and the second target computing service component are used to jointly participate in executing the online collaborative computing task according to the workflow described by the task description information.
16. An electronic device, comprising: processor; A memory for storing processor-executable instructions; wherein the processor implements the method according to any one of claims 1 to 3 by executing the executable instructions.
17. A computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 13.
18. A computer program product, comprising a computer program and / or instructions, wherein the computer program and / or instructions, when executed by a processor, implement the steps of the method according to any one of claims 1 to 13.
Citation Information
Patent Citations
Cooperative edge calculation method, block chain and cooperative edge calculation system
CN110851531A
Application access method and device in multi-party security computing
CN113312612A
Routing method and system in multi-party security computing
CN113472668A
Data processing method and device
CN114726537A
Communication processing method and device based on block chain
CN115576709A
