WO2024021627A1

WO2024021627A1 - Consortium blockchain management method and related system

Info

Publication number: WO2024021627A1
Application number: PCT/CN2023/081538
Authority: WO
Inventors: 张子怡; 王磊; 骆挺; 俞岳
Original assignee: 华为云计算技术有限公司
Priority date: 2022-07-28
Filing date: 2023-03-15
Publication date: 2024-02-01
Also published as: CN117527558A

Abstract

The present application provides a consortium blockchain management method, comprising: receiving a consortium policy of a consortium blockchain configured by a first user, the consortium blockchain comprising first organization nodes created by the first user from a physical resource set of the first user; when the consortium policy supports an application for joining the consortium blockchain, and in response to a consortium blockchain joining application of a second user, processing the consortium blockchain joining application according to the consortium policy; and on the basis of a processing result for the consortium blockchain joining application, joining second organization nodes of the second user in the consortium blockchain. By configuring the consortium policy that supports the application for joining the consortium blockchain, the method achieves equal and autonomous consortium construction, and can satisfy the requirements of services. Moreover, the self-defined consortium contract policy is a distributed contract policy, so that a consortium law and regulation can be achieved to restrain behaviors of all consortium members.

Description

An alliance chain management method and related systems

This application claims priority to the Chinese patent application submitted to the State Intellectual Property Office of China on July 28, 2022, with application number 202210899350.0 and the invention title "A management method and related system for alliance chains", the entire content of which is incorporated by reference. incorporated in this application.

Technical field

This application relates to the field of blockchain technology, and in particular to a management method, system, computing device cluster, computer-readable storage medium and computer program product of a consortium chain.

Background technique

Blockchain refers to a distributed database technology in which multiple nodes in a peer-to-peer network jointly maintain a continuously growing, chained list ledger constructed of ordered data blocks through a consensus mechanism designed based on cryptography technology. . This technology allows any number of nodes participating in the system to calculate and record all information exchange data in the system for a period of time into a data block through cryptographic algorithms, and generate the fingerprint of the data block for chain ) next data block and verification, all participating nodes in the system jointly determine whether the recorded data block is true.

Blockchain networks can be divided into public chains, private chains or consortium chains. Among them, the public chain is an unrestricted blockchain network. Any user can join the public chain at any time and can view the ledger and participate in its consensus process. Private and consortium chains are permissioned blockchain networks. Among them, joining a private chain usually requires the permission of a centralized administrator, while a consortium chain is usually jointly managed by multiple organizations or institutions.

The number of nodes in the alliance chain is limited, it is easier to reach consensus, and it is jointly managed by multiple organizations or institutions. It has strong controllability, so it is widely used in many fields. At present, the invitation system (also called the alliance leader system) is usually used to build alliance chains. Taking the construction of an alliance chain by multiple tenants in a cloud environment as an example, the alliance leader sends invitation information to each participant who wants to join the alliance. The participants decide whether to join the alliance. If they agree to join the alliance, they send the consent information to the management of the alliance chain. System, the management system of the alliance chain sends incremental blocks recording incremental transactions to the consensus node. Participants obtain the channel configuration to join from the consensus node and drive the local node to join the corresponding channel of the alliance chain.

However, this method leaves the inviting party to decide who joins the alliance. It is not an equal way to build an alliance that supports autonomy, and it is difficult to meet business needs.

Contents of the invention

This application provides a management method for an alliance chain. This method realizes the construction of an equal and autonomous alliance by configuring an alliance strategy that supports applications to join the alliance chain, and can meet business needs. This application also provides a consortium chain management system, a computing device cluster, a computer-readable storage medium, and a computer program product corresponding to this method.

In the first aspect, this application provides a management method for the alliance chain. This method can be executed by the management system of the alliance chain. For ease of description, it may also be referred to as the management system for short below. The management system may be a software system that may be deployed in a cluster of computing devices. The computing device cluster executes the program code of the software system to execute the alliance chain management method in the embodiment of the present application. In some embodiments, the management system may also be a hardware system with a consortium chain management function. When the hardware system is running, it executes the consortium chain management method in the embodiment of the present application. For example, the Department of Management The system can be a computing device cluster with alliance chain management functions.

Specifically, the management system may receive the alliance policy of the alliance chain configured by the first user. Among them, the alliance chain includes the first organization node created by the first user from the first user's physical resource set. When the alliance policy supports the application to join the above alliance chain, the management system can respond to the second user's application to join the alliance chain, process the application to join the alliance chain according to the alliance policy, and based on the processing result of the application to join the alliance chain, add the second user's application to join the alliance chain. The second organizational node joins the alliance chain.

In this method, the first user who creates the alliance (i.e., the alliance leader) can enable the second user (for example, a cloud tenant) by configuring an alliance strategy that supports application to join, such as democracy, alliance committee system, or a customized alliance contract strategy. Or users under the cloud) can actively initiate an application to join the alliance chain without passively accepting the alliance leader's invitation. This can achieve equal and autonomous alliance construction and meet business needs.

In some possible implementations, the management system can receive the democracy system or alliance committee system selected by the first user, or receive the alliance contract strategy uploaded by the first user. In this method, the alliance strategy configured by the first user can be a single strategy or a mixed strategy, so as to achieve a coexistence model based on application invitations and build an equal, self-organizing alliance chain system.

In some possible implementations, the alliance contract strategy can be written in a contract language, where the alliance contract strategy defines incentive mechanisms for different types of members in the alliance chain. This method defines an incentive mechanism in the alliance contract strategy to encourage members in the alliance chain to share data and participate in security verification work in the alliance chain, thereby making transactions in the alliance chain more smooth and orderly.

In some possible implementations, when the processing result indicates that the second user is allowed to join the alliance chain, the management system can configure alliance information for the second organization node created by the second user, and the alliance information includes the communication address of the second organization node, Then the management system updates the chain code of the alliance chain at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.

This method is aimed at the situation where the user has already created the organization node. By configuring the alliance information, the organization node is directly added to the alliance chain, thereby completing the user's initiative to join the alliance chain and realizing the construction of an equal and autonomous alliance.

In some possible implementations, when the processing result indicates that the second user is allowed to join the alliance chain, the management system can create a second organization node from the second user's physical resource set, and then the management system can configure the second organization node Alliance information, the alliance information includes the communication address of the second organization node, and the chain code of the alliance chain is updated at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.

This method is aimed at the situation where the user has not created an organization node. First, create an organization node, and then add the organization node to the alliance chain by configuring alliance information, thereby completing the user's initiative to join the alliance chain and achieving an equal and autonomous alliance construction.

In some possible implementations, when it is detected that the code of the alliance chain in the second organization node is updated, the management system can synchronize the updated chain code to the first organization node. In this method, when an organization node in the alliance chain is updated, it will be updated synchronously to other organization nodes, thereby ensuring the consistency of chain codes on different organization nodes.

In some possible implementations, the management system can trigger a vote for the second user to join the alliance chain according to the alliance strategy and obtain the voting results. This method uses the voting results of the organizational nodes in the alliance chain to decide whether to allow the second user to join the chain, thereby achieving the construction of an equal and autonomous alliance.

In some possible implementations, the management system may include decentralized autonomous organization components and alliance components. Among them, the decentralized autonomous organization component serves as the orchestration controller for the construction and management of the autonomous organization alliance, and the collaboration and orchestration alliance participates in The parties implement specific alliance strategies to ensure that the inviting party's business is continuously served and smoothly connected to the network; the alliance component serves as the executor of the dynamic management of alliance members, accepts the instructions of the decentralized autonomous organization component, and performs dynamic organization joining management.

The management system can send a voting request to the alliance component through the decentralized autonomous organization component, and perform voting through the alliance component in combination with the voting ratio or voting waiting time defined in the alliance strategy. Then, the management system can aggregate through the decentralized autonomous organization component. Alliance component voting results.

This method determines the voting ratio or voting waiting time according to the alliance strategy, and votes according to the above voting ratio or voting waiting time defined by the alliance strategy, thereby deciding whether to allow the second user to join the chain. Compared with the indiscriminate voting method, this method It is more suitable for actual application scenarios and has higher usability.

In some possible implementations, the first user and the second user may be on-cloud tenants or off-cloud users. In other words, this method supports cloud tenants or off-cloud users to dynamically join the alliance chain, and can adapt to different scenarios and meet different business needs.

In some possible implementations, the physical resource set of the tenant on the cloud may include a cluster of the tenant on the cloud, and the cluster may include a virtual private cloud cluster or a private cloud cluster in the public cloud. This method supports the creation of organizational nodes in the cluster of cloud tenants, so that cloud tenants can use this to build alliance chains or join alliance chains.

In some possible implementations, the management system can also audit the decisions or behaviors of organizational nodes in the alliance chain based on updates to the chain code. Specifically, the management system can initiate an audit of the decisions or behaviors of organizational nodes in the alliance chain when the alliance chain is abnormal, for example, when data maintained by different organizational nodes is inconsistent. Among them, the management system can determine whether the voting and other behaviors of the organizational nodes in the alliance chain or the decisions based on the voting results comply with relevant regulations or agreements based on the update records of the chain codes deployed in each organizational node. In this way, every decision of the alliance chain can be audited, and the behavior of alliance construction can be traced, ensuring security.

In some possible implementations, when the alliance strategy of the alliance chain configured by the first user is the alliance contract strategy, the management system can also present the alliance contract strategy to the second user so that the second user can view the content of the alliance contract strategy. And based on the content of the alliance contract strategy, decide whether to apply to join the alliance chain.

In some possible implementations, the management system can also receive a contract update request triggered by the first user. The contract update request is used to update the alliance contract strategy, for example, to update the voting proportion and voting waiting time in the alliance contract strategy. Management The system updates the alliance contract strategy based on the contract update request. Among them, the management system can deliver the updated alliance contract strategy to each organizational node of the alliance chain, thereby updating the alliance contract strategy.

In some possible implementations, the management system can also trigger a vote on updating the alliance contract strategy in response to a contract update request and obtain the voting results. When the voting results indicate that the alliance contract strategy is allowed to be updated, the management system will issue the updated alliance contract strategy to each organizational node of the alliance chain, thereby updating the alliance contract strategy. In this way, alliance autonomy can be achieved.

In the second aspect, this application provides an alliance chain management system. The system includes:

An orchestration control module, configured to receive an alliance policy of an alliance chain configured by the first user, where the alliance chain includes a first organization node created by the first user from the physical resource set of the first user;

The orchestration control module is also configured to, when the alliance policy supports an application to join the alliance chain, in response to the second user's application to join the alliance chain, process the application to join the alliance chain according to the alliance policy;

An execution module, configured to add the second organization node of the second user to the alliance chain based on the processing result of the alliance chain joining application.

In some possible implementations, the orchestration control module is specifically used to:

Receive the first user's choice of democracy or federation committee; or,

Receive the alliance contract strategy uploaded by the first user.

In some possible implementations, the alliance contract strategy is written in a contract language, and the alliance contract strategy defines incentive mechanisms for different types of members in the alliance chain.

In some possible implementations, the execution module is specifically used to:

When the processing result indicates that the second user is allowed to join the alliance chain, configure alliance information for the second organization node created by the second user, and the alliance information includes the communication address of the second organization node;

The chain code of the alliance chain is updated at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.

In some possible implementations, the execution module is specifically used to:

When the processing result indicates that the second user is allowed to join the alliance chain, create a second organization node from the physical resource set of the second user;

Configure alliance information for the second organization node, where the alliance information includes the communication address of the second organization node;

In some possible implementations, the execution module is specifically used to:

When it is detected that the chain code of the alliance chain in the second organization node is updated, the updated chain code is synchronized to the first organization node.

Trigger a vote for the second user to join the alliance chain according to the alliance policy, and obtain the voting result.

Send a voting request to the execution module;

The execution module is specifically used for:

Perform voting in conjunction with the voting ratio or voting waiting time defined in the alliance policy;

The orchestration control module is specifically used for:

Summarize the voting results of the execution modules.

In some possible implementations, the first user and the second user are on-cloud tenants or off-cloud users.

In some possible implementations, the physical resource set of the cloud tenant includes a cluster of the cloud tenant, and the cluster includes a virtual private cloud cluster or a private cloud cluster in a public cloud.

In a third aspect, this application provides a computing device cluster. The cluster of computing devices includes at least one computing device including at least one processor and at least one memory. The at least one processor and the at least one memory communicate with each other. The at least one processor is configured to execute instructions stored in the at least one memory, so that the computing device or the computing device cluster executes the management method of the consortium chain as described in the first aspect or any implementation of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium in which instructions are stored, and the instructions instruct a computing device or a cluster of computing devices to execute the above-mentioned first aspect or any one of the first aspects. The management method of the alliance chain described in the implementation method.

In a fifth aspect, the present application provides a computer program product containing instructions that, when run on a computing device or a cluster of computing devices, causes the computer or cluster of computing devices to execute the above-mentioned first aspect or any implementation of the first aspect. The management method of the alliance chain described in the method.

Based on the implementation methods provided in the above aspects, this application can also be further combined to provide more implementation methods.

Description of drawings

In order to explain the technical methods of the embodiments of the present application more clearly, the drawings required to be used in the embodiments will be briefly introduced below.

Figure 1 is a schematic structural diagram of an alliance chain provided by an embodiment of the present application;

Figure 2 is a schematic structural diagram of an alliance chain provided by an embodiment of the present application;

Figure 3 is an architectural diagram of a consortium chain management system provided by an embodiment of the present application;

Figure 4 is a flow chart of a consortium chain management method provided by an embodiment of the present application;

Figure 5 is a schematic diagram of an application scenario of a consortium chain management method provided by an embodiment of the present application;

Figure 6 is a schematic diagram of an application scenario of a consortium chain management method provided by an embodiment of the present application;

Figure 7 is a schematic structural diagram of a computing device provided by an embodiment of the present application;

Figure 8 is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application;

Figure 9 is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application;

Figure 10 is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application.

Detailed ways

The terms "first" and "second" in the embodiments of this application are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of these features.

First, some technical terms involved in the embodiments of this application are introduced.

Blockchain network, also referred to as blockchain, refers to a peer-to-peer (P2P) network built using blockchain technology. In a blockchain network, multiple nodes jointly maintain a continuously growing, chained list ledger constructed of ordered data blocks.

Blockchains can be divided into public blockchain, private blockchain or consortium blockchain according to the degree of openness of read and write permissions. The public chain is a public blockchain, and read and write permissions are open to all nodes; the private chain is a private blockchain, and read and write permissions are open to a certain node; the alliance chain is an alliance blockchain, and read and write permissions are open to all nodes. Nodes joining the alliance (members within the alliance) are open.

The number of nodes in the alliance chain is relatively small and it is easier to reach consensus. Therefore, the alliance chain has faster transaction speed and stronger controllability. Members within the alliance can achieve value exchange by maintaining distributed ledgers (such as distributed chain list ledgers). Based on this, the alliance chain can be widely used in the financial industry and other industries such as energy, insurance, and the Internet of Things. It is especially suitable for business scenarios that focus on privacy protection, transaction speed, and internal supervision in the above industries.

The alliance chain can also be combined with cloud computing to provide users with corresponding cloud services. Cloud computing is a computing model that provides dynamically scalable virtualized resources as services over a network. in, The platform that provides cloud computing is called a cloud platform. The cloud platform can provide blockchain services (Blockchain-As-A-Service, BaaS) for building blockchains such as alliance chains. Among them, BaaS can be a public cloud service, and the cloud platform can provide BaaS to public cloud tenants so that tenants can build alliance chains based on BaaS.

The related technology usually uses an invitation system to build a consortium chain. Taking multiple tenants of a cloud platform to build an alliance chain as an example, a tenant can create an alliance, and the tenant who creates the alliance can also be called the alliance leader. The alliance leader sends invitation information to various participants who want to join the alliance, such as other parties on the cloud platform. tenant. Participants decide whether to join the alliance. If they agree to join the alliance, they will send the consent information to the management system of the alliance chain. The management system of the alliance chain sends incremental blocks recording incremental transactions to the consensus node. Participants obtain the channel configuration to join from the consensus node and drive the local node to join the corresponding channel of the alliance chain. However, this method leaves the inviting party to decide who joins the alliance. It is not an equal way to build an alliance that supports autonomy, and it is difficult to meet business needs.

In view of this, embodiments of the present application provide a management method for a consortium chain. This method is applied to the management system of the alliance chain. For convenience of description, it may also be referred to as the management system for short in the embodiment of this application. The management system may be a software system that may be deployed in a cluster of computing devices. The computing device cluster executes the program code of the software system to execute the alliance chain management method in the embodiment of the present application. In some embodiments, the management system may also be a hardware system with a consortium chain management function. When the hardware system is running, it executes the consortium chain management method in the embodiment of the present application. For example, the management system can be a computing device cluster with alliance chain management functions.

In this method, the first user who creates the alliance (i.e., the alliance leader) can enable the second user (for example, a cloud tenant) by configuring an alliance strategy that supports application to join, such as democracy, alliance committee system, or a customized alliance contract strategy. Or users under the cloud) can actively initiate an application to join the alliance chain without passively accepting the alliance leader's invitation. This can achieve equal and autonomous alliance construction and meet business needs. Moreover, the customized alliance contract strategy is a distributed contract strategy, which can achieve a kind of alliance laws and regulations to constrain the behavior of all alliance members.

It should also be noted that the alliance strategy configured by the first user may be a single strategy, such as democracy, alliance committee system, etc. The alliance strategy configured by the first user may also be a mixed strategy, for example, a mixed strategy of alliance leadership and democracy. By configuring the alliance strategy as the above hybrid strategy, the first user can realize the coexistence model based on application invitations and build an equal, self-organizing alliance chain system.

Furthermore, this method supports cloud tenants or off-cloud users to dynamically join the alliance chain, which can adapt to different scenarios and meet different business needs.

Referring to the schematic structural diagram of the alliance chain shown in Figure 1, the management system supports the interconnection between different virtual private clouds (Virtual private clouds, VPC) in the public cloud. As shown in Figure 1, the public cloud includes tenant A and tenant B, where , Tenant A uses VPC01, and tenant B uses VPC02. Node 02 in VPC01 and node 03 in VPC02 are interconnected through connection 102, so that multiple tenants in the public cloud can build a consortium chain. The management system also supports interconnection between public cloud and private cloud. For example, the private cloud includes tenant C, and tenant C uses node 05 in the private cloud. Node 01 in VPC01 of the public cloud can be interconnected with node 05 in the private cloud through connection 104. In this way, public cloud tenants and private cloud tenants can build an alliance chain.

The management system also supports cross-cloud interconnection. Among them, cross-cloud interconnection includes interconnection between public clouds and third-party clouds (specifically, clouds provided by third-party cloud service providers), private clouds, and third-party cloud interconnections. As shown in Figure 1, user A of the third-party cloud can read and write to node 06 in the third-party cloud. Node 04 in VPC02 of the public cloud can be interconnected with node 06 in the third-party cloud through connection 106, so that tenants of the public cloud and users of the third-party cloud can build an alliance chain. Node 05 in the private cloud can be interconnected with node 06 in the third-party cloud through the connection 108, so that the tenants of the private cloud and the users of the third-party cloud can build an alliance chain.

The management system also supports the interconnection between the cloud platform and edge nodes. An edge node refers to a network node with fewer intermediate links between it and the final access user. It can be a computer room or a physical device. Compared with directly accessing the origin site in the cloud platform, users have better response capabilities and connection speeds when accessing edge nodes.

Among them, the interconnection between the cloud platform and edge nodes can include the interconnection between public cloud and edge nodes, the interconnection between private cloud and edge nodes, and the interconnection between third-party cloud and edge nodes. As shown in Figure 1, User B has read and write permissions to Node 07 in the edge node. Node 04 in VPC02 of the public cloud can be interconnected with Node 07 in the edge node through connection 110. In this way, tenants of the public cloud can communicate with each other. Users of edge nodes build alliance chains. Similarly, node 05 in the private cloud can be interconnected with node 07 in the edge node through the connection 112, so that the tenants of the private cloud and the users of the edge node can build an alliance chain. The node 06 in the third-party cloud can be interconnected with the node 07 in the edge node through the connection 114, so that users of the third-party cloud and users of the edge node can build an alliance chain.

Each user or tenant can be regarded as a participant in an alliance and participates in a certain alliance chain as an organization. For the convenience of description, the following examples use multiple tenants in the public cloud to build a consortium chain. For specific implementations of building consortium chains for other types of tenants or users, please refer to the relevant descriptions of building consortium chains for multiple tenants in the public cloud.

Referring to the schematic diagram of a consortium chain constructed by multi-tenants shown in Figure 2, each tenant has a cluster, which may be a VPC cluster, and the cluster includes nodes used to build the consortium chain. Among them, each cluster can apply for an elastic Internet protocol address (EIP) to communicate with nodes in other clusters.

Each tenant can be regarded as a participant in an alliance and participates in a certain alliance chain as an organization. For example, tenant A can be regarded as a participant in an alliance and participates in alliance chain A as organization A. Tenant A can also be regarded as a participant in another alliance, participating in alliance chain B as organization A. That is to say, a tenant has one or more nodes, and these nodes can be used together with nodes of different tenants to build multiple alliance chains to achieve different business requirements. For example, a node of tenant A can build alliance chain A with a node of tenant B and a node of tenant C through alliance policy A, and another node of tenant A can build an alliance chain A with another node of tenant B through alliance policy C. Alliance chain C. It should be noted that different alliance chains can be constructed using the same or different alliance strategies. For example, alliance strategy A can be democracy, and alliance strategy C can be alliance contract strategy. Among them, data in different alliance chains are isolated from each other. Data in the same alliance chain is not isolated, that is, messages sent by nodes in the same alliance chain can be accepted by each other, but nodes not in the alliance chain cannot accept messages sent in the alliance chain. For example, nodes in the tenant A cluster that participate in alliance chain C cannot accept messages sent in alliance chain A.

In this embodiment, a tenant (such as tenant A) can serve as the initiator of a blockchain network, allowing it to dynamically invite other tenants to join the alliance chain built based on this blockchain network. Among them, the chain code embedded in the blockchain network defines general alliance strategies, such as the alliance leader system, democracy system, and alliance committee system. Furthermore, the chain code also defines the incentive system of the alliance chain to be built. This incentive system refers to the incentive mechanism for the operation of the alliance chain. For example, the incentive system can include: a participant in the alliance chain shares data and gives the participant a certain amount of allocable resources to motivate. The above-mentioned tenant can also publish information about the alliance created by the tenant and allow other tenants (or users) to apply to join within the permission network. The invited party can join the alliance chain after receiving the invitation. The applicant can query the alliance strategy of the alliance initiator (i.e. the alliance leader) and initiate an application to join the alliance chain to join the alliance chain. The above-mentioned nodes used to build the alliance chain are also called blockchain nodes. This method supports the invitation application coexistence mode, which can realize the safe autonomy of blockchain nodes between different tenants.

It should be noted that each tenant not only has a blockchain node, but also has components for managing the federation. The above-mentioned components for managing the alliance may also be called alliance components and proxy components. In this embodiment, the alliance component can interact with the blockchain node to obtain or write alliance information. For example, the alliance component is used to obtain alliance information and then publish the alliance information, or the alliance component is used to update the alliance information in the chain code. Among them, the tenant's cluster can include one or more blockchain nodes, and the alliance component can uniformly manage one or more blockchain nodes.

The structure of the alliance chain has been introduced above. Next, the system structure of the management system for building the alliance chain according to the embodiment of the present application will be introduced with reference to the accompanying drawings.

Referring to the system architecture diagram of the management system shown in FIG. 3 , the management system 300 includes an orchestration control module 302 and an execution module 304 . Wherein, the orchestration control module 302 is used to receive the alliance policy of the alliance chain configured by the first user. The alliance chain includes the first organization node created by the first user from the first user's physical resource set. When the alliance policy supports the application to join The alliance chain, in response to the second user's alliance chain joining application, processes the alliance chain joining application according to the alliance policy. The execution module 304 is configured to add the second organization node of the second user to the alliance chain based on the processing result of the alliance chain joining application.

Among them, the orchestration control module 302 and the execution module 304 can be developed using a componentized model. Based on this, the orchestration control module 303 can be a decentralized autonomous organization (Decentralized Autonomous Organization, DAO) component, and the execution module 304 can be the above-mentioned alliance component.

The main function of the DAO component is to serve tenants and serve as an orchestration controller for the construction and management of autonomous organization alliances. It coordinates and orchestrates alliance participants to execute specific alliance policies, ensuring that the inviting party's business is continuously served and smoothly connected to the network.

As the executor of dynamic management of alliance members, the alliance component accepts instructions from the DAO component and performs dynamic organization joining management. At the same time, the alliance component can directly interact with the nodes in the alliance chain. Therefore, the operations triggered by the DAO component when executing a specific alliance strategy, such as voting operations, can be returned by the alliance component to the DAO component.

It should be noted that various parts of the management system 300 can be deployed in a distributed manner on the cloud platform. For example, DAO components can be deployed in the management cluster of the cloud platform, and alliance components can be deployed in each tenant cluster of the cloud platform. In other possible implementations of the embodiments of this application, the DAO component can also be deployed in each tenant cluster of the cloud platform. Since Figure 2 illustrates the construction of a consortium chain with multi-tenants, in other scenarios of building a consortium chain, various parts of the management system 300 such as DAO components and consortium components of different organizations can also be deployed in other environments, such as at the edge. nodes, this embodiment does not limit this.

In order to make the technical solution of the present application clearer and easier to understand, the management method of the alliance chain in the embodiment of the present application will be introduced below with reference to the accompanying drawings.

Refer to the flow chart of the alliance chain management method shown in Figure 4. The method includes:

S402: The management system 300 receives the alliance policy of the alliance chain configured by the first user.

The first user can be an on-cloud tenant or an off-cloud user (also called an offline user). The first user can serve as the alliance initiator and initiate the operation of creating the alliance chain. When creating the alliance chain, the first user can create a first organization node from the first user's physical resource set, and the alliance chain includes the first organization node. The physical resource set of the cloud tenant includes the cluster of the cloud tenant. The cluster is a virtual private cloud or private cloud cluster in the public cloud. The user's physical resource set under the cloud includes edge nodes.

The alliance strategy may include one or more of the general alliance-leader system, democracy system, and alliance committee system. Alliance strategies can also include customized alliance contract strategies. Among them, the alliance contract strategy can be written through contract language. In some embodiments, the contract language may include one or more of Solidity or Vyper.

In the leader system, the leader determines the members of the alliance. Specifically, the alliance leader can invite other users (on-cloud tenants or off-cloud users) to join the alliance chain. When the user agrees, the user can become an internal member of the alliance. Democracy allows users (on-cloud tenants or off-cloud users) to apply to join the alliance chain, and users who have joined (internal members of the alliance) vote whether to agree to the application for users to join. A consensus can be reached when the majority of already-joined users agree. The Alliance Committee supports voting to elect committee members who make decisions. Committee members vote to agree whether the applicant should join. Other members can initiate the election of Alliance Committee members.

The alliance contract strategy is a strategy that stipulates the conditions for users to join the alliance chain based on the contract. For example, the alliance contract strategy can stipulate the conditions for users to join the alliance chain through the contract code. Voting weights are set for different types of internal members of the alliance. Based on this weight, the voting results of whether the user joins the alliance can be determined. When the voting results meet the set conditions , the user is allowed to join the alliance chain, otherwise the user is refused to join the alliance chain.

In some possible implementations, the alliance contract strategy can also define incentive mechanisms for different types of members in the alliance chain. This incentive mechanism refers to the incentive mechanism for the operation of the alliance chain. For example, the incentive mechanism can include: members within the alliance share data and are given 5 shares of allocable resources as incentives; members within the alliance invite new users to join the alliance chain and are given 10 shares of allocable resources as incentives. It should be noted that the allocable resources may be virtual resources, such as points.

S404: When the alliance policy supports the application to join the alliance chain, the management system 300 responds to the second user's application to join the alliance chain and processes the application to join the alliance chain according to the alliance policy.

The alliance strategy that supports the application to join the alliance chain can include democracy, alliance committee system, or a hybrid strategy that combines at least one of democracy and alliance committee system. In some embodiments, the alliance strategy supporting application to join the alliance chain may also include a customized alliance contract strategy.

When the alliance strategy configured by the first user is a contract strategy such as democracy, alliance committee system, or alliance contract strategy that supports application to join the alliance chain, the management system 300 can present the information of the alliance chain to the second user. The information of the alliance chain may include one or more of the business information and communication address of the alliance chain. The second user can initiate an application to join the alliance chain based on the information of the alliance chain. Correspondingly, the management system 300 may respond to the second user's application for joining the alliance chain and process the application for joining the alliance chain according to the alliance policy.

In some possible implementations, the management system 300 can trigger a vote for the second user to join the alliance chain according to the alliance policy, and obtain the voting results. Among them, according to different alliance policies, the management system 300 can send voting requests to different internal members of the alliance. For example, when the alliance policy is a democratic strategy, the management system 300 may send a voting request to each internal member of the alliance. For another example, when the alliance strategy is an alliance committee system, the management system 300 can first determine the members of the alliance committee, for example, by voting, and then report the members to the alliance committee. Committee members send voting requests. Members who receive the voting request can vote and the voting results are returned. The management system 300 can summarize the received voting results to obtain the final voting results.

During specific implementation, the management system 300 can send a voting request to the alliance component through the DAO component, and then use the alliance component to perform voting in combination with the voting ratio or voting waiting time defined in the alliance policy, and then summarize the voting results of the alliance component through the DAO component. .

S406: The management system 300 adds the second organization node of the second user to the alliance chain based on the processing result of the alliance chain joining application.

In the embodiment of this application, when the second user applies to join the alliance chain, the following situations may include:

One situation is that the second user has created a second organization node to be added to the alliance chain. Based on this, when the processing result indicates that the second user is allowed to join the alliance chain, the management system 300 can configure alliance information for the second organization node created by the second user, where the alliance information includes the third communication addresses of the two organization nodes, and then update the chain code of the alliance chain at the first organization node and the second organization node according to the alliance information. The updated chain code includes the communication address of the second organization node.

Another situation is that the second user has not created a second organizational node to join the alliance chain. Based on this, when the processing result indicates that the second user is allowed to join the alliance chain, the management system 300 can obtain the information from the third organization node. The physical resources of the two users are pooled to create a second organization node, and alliance information is configured for the second organization node. The alliance information includes the communication address of the second organization node. Then the management system 300 configures the alliance information in the second organization node based on the alliance information. The first organization node and the second organization node update the chain code of the alliance chain. The updated chain code includes the communication address of the second organization node.

Wherein, when the first organization node and the second organization node update the chain code of the alliance chain, the management system 300 can update the chain code of the alliance chain in the second organization node. The chain code of the alliance chain is updated, and the updated chain code is synchronized to the first organization node.

In order to make the technical solution of this application clearer and easier to understand, the management method of the alliance chain in the embodiment of this application is introduced below in combination with different application scenarios.

Referring to the schematic diagram of an application scenario of the alliance chain management method shown in Figure 5, the method includes the following steps:

Step 1: Tenant A creates the alliance chain, initializes the internal chain code of the alliance chain to support synchronization of alliance information, and then configures the alliance strategy of the alliance chain in the DAO component.

Specifically, tenant A can first create a first organization node from tenant A's cluster, and create an alliance chain based on the first organization node. The alliance chain includes the above-mentioned first organization node. After tenant A creates the alliance chain, it can initialize the internal chain code of the alliance chain to support synchronization of alliance information.

Among them, the DAO component can provide the following alliance strategies: alliance leader system, democracy system and alliance committee system for users to choose and configure. Different alliance strategies support different ways of building alliances. In the alliance leader system, the alliance leader determines the alliance members. The master can invite other users to join the alliance. When other users agree, other users can become members of the alliance. Democracy allows users to apply to join, and members within the alliance vote whether to agree to apply for users to join. A consensus can be reached if a majority of the members within the alliance agree. The Alliance Committee supports voting to elect Alliance Committee members who make decisions. The Alliance Committee members vote to decide whether to apply for users to join. Other members can initiate the election of Alliance Committee members. It should be noted that voting can also determine one or more of the block generation speed, block size limit, voting proportion required for confirmation, voting waiting time for each round of voting, the list of consensus nodes and the permissions of each node.

Step 2: Tenant B views the information of the alliance chain created by tenant A.

Tenant B already has the created organization node. Tenant B can decide whether to join by calling the alliance interface of tenant A to view the alliance chain's alliance policy and other alliance information.

Step 3: Tenant B and tenant C initiate an application to join the alliance chain.

When tenant B decides to join the alliance chain created by tenant A, he can apply for joining the alliance chain by packaging tenant B's existing node information, including the number of tenant B's organizational nodes, name, encryption algorithm, storage model and user public key, into the alliance chain. Then the alliance chain joining application (which may also be referred to as a link joining application for short) is sent to the management system 300 .

Tenant C is the tenant invited by tenant A. When tenant C decides to join the alliance chain created by tenant A, tenant C can package the public key of tenant C and the number and name of the organization nodes to be applied for into the alliance chain joining application, and then send the alliance chain joining application to the management system 300 .

Step 4: The management system 300 receives the application to join the alliance chain and initiates a vote on whether tenant B and tenant C join the alliance chain. Then, the management system 300 delivers the alliance chain audit results to the tenant A cluster, delivers the public key of the applicant, the number of joining nodes, and the name, and authorizes the temporary token. Then proceed to step 5.

Step 5: Tenant B and tenant C obtain the alliance chain application approval information.

The alliance chain application approval information includes the review results of the alliance chain joining application. Tenant B and tenant C can query tenant A for their application results.

Step 6: The management system 300 configures alliance information, temporary tokens, and communication addresses for existing organization nodes. The management system 300 creates organization nodes based on the audit results and issues the communication addresses of existing alliances.

Specifically, for the tenant B cluster that already has organization nodes, the DAO component of the management system 300 can configure alliance information, temporary tokens, and communication addresses for the existing organization nodes. For the tenant C cluster that has not yet created an organization node, the DAO component can pull up The alliance blockchain network issues communication public keys, communication addresses, and temporary tokens to existing alliance parties.

Step 7: The organization node of tenant B, the organization node of tenant C, and the organization node of tenant A form an alliance chain.

The alliance component of tenant A monitors the alliance interface. After receiving the request, it verifies the signature, temporary token, node number name and organization public key information. After passing the verification, the organization CA is added to the chain configuration, and its communication address, link status and Node information is written to the chain through the alliance chain code interface.

After the chain works normally, the alliance components of tenant B and tenant C initiate a link based on the communication address of a member of the alliance, perform the link operation, and receive the task ID. After the query task is completed, the alliance member information is queried from the alliance chain code interface. and communication information to update the current alliance member status for other components.

Refer to the schematic diagram of another application scenario of the alliance chain management method shown in Figure 6. The method includes the following steps:

Step 1: Tenant A creates the alliance chain, initializes the internal chain code of the alliance chain to support synchronization of alliance information, and then uploads the customized alliance contract strategy in the DAO component.

Tenant B already has the organization and nodes he created. Tenant B can call the alliance interface of tenant A to view the alliance strategy of the alliance chain, such as custom contract content, to decide whether to join.

In this embodiment, the DAO component supports alliance building parties to provide customized alliance contract strategies, such as defining a hybrid alliance building system, and defining an open contract to construct different incentive and attraction strategies under a specific alliance to attract different types of alliances. members gathered. When applying to join, tenants can view the alliance contract based on the code is law strategy, clarify the current alliance strategy, and whether they support voting modification systems and other treaties. After joining, the alliance contract is deployed within the organization through the alliance component and the alliance members reach an agreement. Subsequent synchronization of member information, voting and result acquisition can also be completed through the alliance contract.

Based on the above description, the management method of the alliance chain provided by the embodiment of this application supports sending a link application to the DAO component. The DAO component cooperates with the alliance component to achieve chain communication and dynamically achieve an equal and autonomous alliance chain. This can support the future metaverse. Web3.0, open alliance chain, digital asset chain and other chain networks with high requirements on fairness are in demand.

Furthermore, this method also supports writing alliance strategies based on DAO component customization and custom contracts, and supports DAO components to issue alliance contracts to the alliance component side for deployment, and synchronize alliance contracts to other DAO components to support querying during alliance construction. Alliance code business specifications and interfaces. This enables auditing and tracing of alliance operations and actions between multiple members.

Based on the alliance chain management method provided by the embodiment of the present application, the embodiment of the present application also provides an alliance chain management system 300 as mentioned above. The management system 300 of the alliance chain will be introduced below with reference to the accompanying drawings.

Referring to the schematic structural diagram of the alliance chain management system 300 shown in Figure 3, the system 300 includes:

The orchestration control module 302 is configured to receive the alliance policy of the alliance chain configured by the first user. The alliance chain includes the first organization node created by the first user from the first user's physical resource set;

The orchestration control module 302 is also used to process the application to join the alliance chain according to the alliance policy in response to the second user's application to join the alliance chain when the alliance policy supports it;

The execution module 304 is configured to add the second organization node of the second user to the alliance chain based on the processing result of the alliance chain joining application.

The above-mentioned orchestration control module 302 and execution module 304 can be implemented through hardware modules or through software modules.

When implemented in software, orchestration control module 302 and execution module 304 may be applications or application modules running on a computing device or cluster of computing devices.

When implemented by hardware, the orchestration control module 302 may also utilize an application-specific integrated circuit (application-specific integrated circuit). integrated circuit, ASIC), or programmable logic device (PLD), etc. The above-mentioned PLD can be implemented by a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof. Similarly, the execution module 304 may include at least one computing device, or a device implemented using ASIC or PLD.

In some possible implementations, the orchestration control module 302 is specifically used to:

Receive the first user's choice of democracy or federation committee; or,

Receive the alliance contract strategy uploaded by the first user.

In some possible implementations, the execution module 304 is specifically used to:

When the processing result indicates that the second user is allowed to join the alliance chain, create a second organization node from the second user's physical resource set;

Configuring alliance information for the second organization node, where the alliance information includes the communication address of the second organization node;

Trigger the vote for the second user to join the alliance chain according to the alliance strategy, and obtain the voting results.

Send a voting request to the execution module 304;

The execution module 304 is specifically used to:

Perform voting in conjunction with the voting ratio or voting waiting time defined in the alliance strategy;

The arrangement control module 302 is specifically used to:

Summarize the voting results of the execution modules.

In some possible implementations, the physical resource set of the cloud tenant includes a cluster of the cloud tenant, and the cluster includes a virtual private cloud cluster or a private cloud cluster in the public cloud.

The present application also provides a computing device 700. As shown in Figure 7, computing device 700 includes: bus 702, processor 704, memory 706, and communication interface 708. The processor 704, the memory 706 and the communication interface 708 communicate through the bus 702. Computing device 700 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 700.

The bus 702 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one line is used in Figure 7, but it does not mean that there is only one bus or one type of bus. Bus 702 may include a path that carries information between various components of computing device 700 (eg, memory 706, processor 704, communications interface 708).

The processor 704 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (micro processor, MP) or a digital signal processor (digital signal processor, DSP). any one or more of them.

Memory 706 may include volatile memory, such as random access memory (RAM). The processor 704 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid state drive (SSD). drive, SSD). The memory 706 stores executable program code, and the processor 704 executes the executable program code to implement the aforementioned alliance chain management method. Specifically, the memory 706 stores instructions for the alliance chain management system 300 to execute the alliance chain management method.

The communication interface 708 uses transceiver modules such as, but not limited to, network interface cards and transceivers to implement communication between the computing device 700 and other devices or communication networks.

An embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device may be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

As shown in FIG. 8 , the computing device cluster includes at least one computing device 700 . The memory 706 of one or more computing devices 700 in the computing device cluster may store instructions for the same consortium chain management system 300 to execute the consortium chain management method.

In some possible implementations, one or more computing devices 700 in the computing device cluster may also be used to execute part of the instructions of the alliance chain management system 300 for executing the alliance chain management method. In other words, a combination of one or more computing devices 700 may jointly execute the instructions of the alliance chain management system for executing the alliance chain management method.

It should be noted that the memory 706 in different computing devices 700 in the computing device cluster can store different instructions for executing part of the functions of the alliance chain management system.

Figure 9 shows a possible implementation. As shown in Figure 9, two computing devices 700A and 700B are connected through a communication interface 708. Stored on memory in computing device 700A are instructions for performing the functions of orchestration control module 302 . The memory in the computing device 700B stores instructions for performing the functions of the execution module 304 described above. In other words, the memories 706 of the computing devices 700A and 700B jointly store instructions used by the management system of the consortium chain to execute the management method of the consortium chain.

The connection method between the computing device clusters shown in Figure 9 may be based on the fact that the management method of the alliance chain provided by this application needs to receive the configured alliance policy and add the second organization node to the alliance chain. Therefore, it is considered that the orchestration control module 302 The functions implemented are executed by the computing device 700A, and the functions implemented by the execution module 304 are executed by the computing device 700B.

It should be understood that the functions of computing device 700A shown in FIG. 9 may also be performed by multiple computing devices 700. Likewise, the functions of computing device 700B may also be performed by multiple computing devices 700 .

In some possible implementations, one or more computing devices in a cluster of computing devices may be connected through a network. Wherein, the network may be a wide area network or a local area network, etc. Figure 10 shows a possible implementation. As shown in Figure 10, two computing devices 700C and 700D are connected through a network. Specifically, the connection to the network is made through a communication interface in each computing device. In this type of possible implementation, instructions for performing the functions of the orchestration control module 302 are stored in the memory 706 of the computing device 700C. At the same time, instructions for executing the functions of the execution module 304 are stored in the memory 606 of the computing device 600D.

The connection method between the computing device clusters shown in Figure 10 can be: Considering that the management method of the alliance chain provided by this application needs to receive the configured alliance policy and add the second organization node to the alliance chain, it is considered to implement the orchestration control module 302 The functions implemented by the execution module 304 are executed by the computing device 700C, and the functions implemented by the execution module 304 are executed by the computing device 700D. It should be understood that the functions of computing device 700C shown in FIG. 10 may also be performed by multiple computing devices 700. Likewise, the functions of computing device 700D may also be performed by multiple computing devices 700 .

An embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium may be any available medium that a computing device can store or a data storage device such as a data center that contains one or more available media. The available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state drive), etc. The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned management system applied to the alliance chain for executing the management method of the alliance chain.

An embodiment of the present application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions capable of running on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, at least one computing device is caused to execute the above-mentioned management method of the alliance chain.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that it can still be used Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent substitutions are made to some of the technical features; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the protection scope of the technical solutions of the various embodiments of the present invention.

Claims

A management method of an alliance chain, characterized in that it is applied to a management system of an alliance chain, and the method includes:

Receive the alliance policy of the alliance chain configured by the first user, the alliance chain including the first organization node created by the first user from the physical resource set of the first user;

When the alliance policy supports an application to join the alliance chain, in response to the second user's application to join the alliance chain, process the application to join the alliance chain according to the alliance policy;

Based on the processing result of the alliance chain joining application, the second organization node of the second user is added to the alliance chain.
The method according to claim 1, characterized in that said receiving the alliance policy of the alliance chain configured by the first user includes:

Receive the first user's choice of democracy or federation committee; or,

Receive the alliance contract strategy uploaded by the first user.
The method according to claim 2, characterized in that the alliance contract strategy is written in a contract language, and the alliance contract strategy defines incentive mechanisms for different types of members in the alliance chain.
The method according to any one of claims 1 to 3, characterized in that, based on the processing result of the application for joining the alliance chain, adding the second organization node of the second user to the alliance chain includes: :

When the processing result indicates that the second user is allowed to join the alliance chain, configure alliance information for the second organization node created by the second user, and the alliance information includes the communication address of the second organization node;

The chain code of the alliance chain is updated at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.
The method according to any one of claims 1 to 3, characterized in that, based on the processing result of the application for joining the alliance chain, adding the second organization node of the second user to the alliance chain includes: :

When the processing result indicates that the second user is allowed to join the alliance chain, create a second organization node from the physical resource set of the second user;

Configure alliance information for the second organization node, where the alliance information includes the communication address of the second organization node;

The chain code of the alliance chain is updated at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.
The method according to claim 4 or 5, characterized in that, updating the chain code of the alliance chain at the first organization node and the second organization node according to the alliance information includes:

When it is detected that the chain code of the alliance chain in the second organization node is updated, the updated chain code is synchronized to the first organization node.
The method according to any one of claims 1 to 6, characterized in that processing the alliance chain joining application according to the alliance policy includes:

Trigger a vote for the second user to join the alliance chain according to the alliance policy, and obtain the voting result.
The method according to claim 7, characterized in that the management system includes a decentralized autonomous organization component and an alliance component, and the voting for the second user to join the alliance chain is triggered according to the alliance policy, Get voting results, including:

Send a voting request to the alliance component through the decentralized autonomous organization component;

Through the alliance component, voting is performed in combination with the voting ratio or voting waiting time defined in the alliance strategy;

The voting results of the alliance components are aggregated through the decentralized autonomous organization component.
The method according to any one of claims 1 to 8, characterized in that the first user and the second user are on-cloud tenants or off-cloud users.
The method of claim 9, wherein the physical resource set of the cloud tenant includes a cluster of the cloud tenant, and the cluster includes a virtual private cloud cluster or a private cloud cluster in a public cloud.
An alliance chain management system, characterized in that the system includes:

An orchestration control module, configured to receive an alliance policy of an alliance chain configured by the first user, where the alliance chain includes a first organization node created by the first user from the physical resource set of the first user;

The orchestration control module is also configured to, when the alliance policy supports an application to join the alliance chain, in response to the second user's application to join the alliance chain, process the application to join the alliance chain according to the alliance policy;

An execution module, configured to add the second organization node of the second user to the alliance chain based on the processing result of the alliance chain joining application.
The system according to claim 11, characterized in that the orchestration control module is specifically used to:

Receive the first user's choice of democracy or federation committee; or,

Receive the alliance contract strategy uploaded by the first user.
The system according to claim 12, wherein the alliance contract strategy is written in a contract language, and the alliance contract strategy defines incentive mechanisms for different types of members in the alliance chain.
The system according to any one of claims 11 to 13, characterized in that the execution module is specifically used to:

When the processing result indicates that the second user is allowed to join the alliance chain, configure alliance information for the second organization node created by the second user, and the alliance information includes the communication address of the second organization node;

The chain code of the alliance chain is updated at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.
The system according to any one of claims 11 to 13, characterized in that the execution module is specifically used to:

When the processing result indicates that the second user is allowed to join the alliance chain, create a second organization node from the physical resource set of the second user;

Configure alliance information for the second organization node, where the alliance information includes the communication address of the second organization node;

The chain code of the alliance chain is updated at the first organization node and the second organization node according to the alliance information, and the chain code includes the communication address of the second organization node.
The system according to claim 14 or 15, characterized in that the execution module is specifically used to:

When it is detected that the chain code of the alliance chain in the second organization node is updated, the updated chain code is synchronized to the first organization node.
The system according to any one of claims 11 to 16, characterized in that the orchestration control module is specifically used for:

Trigger a vote for the second user to join the alliance chain according to the alliance policy, and obtain the voting result.
The system according to claim 17, characterized in that the orchestration control module is specifically used to:

Send a voting request to the execution module;

The execution module is specifically used for:

Perform voting in conjunction with the voting ratio or voting waiting time defined in the alliance strategy;

The orchestration control module is specifically used for:

Summarize the voting results of the execution modules.
The system according to any one of claims 11 to 18, characterized in that the first user and the second user are on-cloud tenants or off-cloud users.
The system according to claim 19, wherein the physical resource set of the cloud tenant includes a cluster of the cloud tenant, and the cluster includes a virtual private cloud cluster or a private cloud cluster in a public cloud.
A computing device cluster, characterized in that the computing device cluster includes at least one computing device, the at least one computing device includes at least one processor and at least one memory, and the at least one memory stores computer-readable Instructions; the at least one processor executes the computer-readable instructions to cause the cluster of computing devices to perform the method of any one of claims 1 to 10.
A computer-readable storage medium, characterized by comprising computer-readable instructions; the computer-readable instructions are used to implement the method described in any one of claims 1 to 10.
A computer program product, characterized by comprising computer readable instructions; the computer readable instructions are used to implement the method described in any one of claims 1 to 10.