CN112671589B

CN112671589B - Method, device, equipment and storage medium for realizing operation of alliance network

Info

Publication number: CN112671589B
Application number: CN202011629817.7A
Authority: CN
Inventors: 荆博
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2020-12-31
Filing date: 2020-12-31
Publication date: 2023-04-18
Anticipated expiration: 2040-12-31
Also published as: CN112671589A

Abstract

The application discloses an operation implementation method, device, equipment and storage medium of an alliance network, relates to the technical field of block chains, and can be used for cloud computing and cloud services. The specific implementation scheme is as follows: when determining that the alliance authority of the alliance owner client of the alliance network is withdrawn, determining a new alliance owner client in the alliance network; the alliance client is used for controlling the operation of the alliance network based on management platform data; and is used for synchronizing the management platform data to a chain management secondary alliance master client with a secondary alliance master authority in the alliance network. Distributed management of the alliance network can be achieved, and a management framework is optimized.

Description

Operation implementation method, device, equipment and storage medium of alliance network

Technical Field

The application relates to the technical field of computers, in particular to the technical field of block chains, which can be used for cloud computing and cloud service, and specifically is used for an operation implementation method, device, equipment and storage medium of an alliance network.

Background

With the development of block chain technology, the application of the alliance network is more and more extensive. A federation network is generally formed by enterprises and is usually maintained by multiple nodes of the same federation, and one federation network may include at least one federation chain, and each federation chain may be in a parallel chain relationship or a sub-chain relationship.

However, the existing alliance network has a problem of inconvenient operation of the alliance network due to more constraints on network operation, and needs to be improved urgently.

Disclosure of Invention

The application provides a method, a device, equipment and a storage medium for realizing operation of an alliance network so as to optimize the management mode of the alliance network.

According to an aspect of the present application, there is provided a method for implementing operation of an alliance network, the method being performed by a chain management client, the method including:

when determining that the alliance authority of the alliance owner client of the alliance network is withdrawn, determining a new alliance owner client in the alliance network;

the alliance client is used for controlling the operation of the alliance network based on management platform data; and is used for synchronizing the management platform data to a chain management secondary alliance owner client with a secondary alliance owner authority in the alliance network.

According to another aspect of the present application, there is provided an apparatus for implementing an operation of an alliance network, the apparatus being configured at a chain management client, the apparatus including:

the authority revocation determining module is used for determining the alliance authority revocation of the alliance client of the alliance network;

the new client determining module is used for determining a new alliance client in the alliance network when the alliance authority of the alliance client of the alliance network is determined to be withdrawn;

According to another aspect of the present application, there is provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method for implementing operations of a federated network as described in any embodiment of the present application.

According to another aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, in which computer instructions are stored, wherein the computer instructions are configured to cause a computer to perform a method for implementing operations of a federated network according to any one of the embodiments of the present application.

According to another aspect of the present disclosure, there is provided a computer program product including a computer program, which when executed by a processor, implements the operation implementation method of the federation network according to any one of the embodiments of the present application.

The technical scheme of the embodiment of the application can realize distributed management of the alliance network and optimize a management framework.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1A is a schematic structural diagram of an alliance network system according to an embodiment of the present application;

fig. 1B is a flowchart of an operation implementation method of an alliance network according to an embodiment of the present application;

fig. 1C is a schematic diagram of identity roles of a chain management client of an organization a in different federation networks, provided according to an embodiment of the present application;

fig. 2 is a flowchart of an operation implementation method of an alliance network according to an embodiment of the present application;

FIG. 3 is a flowchart of an implementation method for operation of an alliance network according to an embodiment of the present application;

FIG. 4 is a flowchart of an implementation method for operation of an alliance network according to an embodiment of the present application;

FIG. 5 is a flowchart of an implementation method for operation of an alliance network according to an embodiment of the present application;

FIG. 6 is a flowchart of an implementation method for operation of an alliance network according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an operation implementation apparatus of an alliance network according to an embodiment of the present application;

fig. 8 is a block diagram of an electronic device for implementing an operation implementation method of a federation network according to an embodiment of the present application.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Before the embodiments of the present application are described, a brief description is given to a federation network to which the embodiments of the present application are applicable. A federation network generally consists of a plurality of enterprises collectively forming a federation network system, each enterprise may provide computing devices and storage devices to carry the operation of a blockchain as blockchain nodes. One or more federation networks may be created to support different services, respectively. As shown in fig. 1A, the alliance network system includes three organizations, each of which is provided with an Internet Data Center (IDC), also called a machine room, and electronic devices and storage devices are deployed in the machine room as block chain nodes. Federation chains can run between block link points.

In the alliance network system, the operations such as creation, maintenance, operation, authority control and the like of the alliance network can be comprehensively managed through a chain management platform. The chain management platform is, for example, a block chain as a Service (BaaS) platform. The BaaS platform may manage the alliance network by installing a client on the electronic device, where the client may be called a chain management client, and is implemented in a software form or implemented in a manner that software is matched with hardware. The chain management client is able to control the devices by interacting with the block chain nodes and other hardware devices.

In the technical solution provided in the embodiment of the present application, multiple enterprises in the alliance network system may allow multiple chain management clients to be installed and run simultaneously, and the chain management clients may have different permissions. The authority can comprise an alliance authority and an auxiliary alliance authority, and optionally, member authorities are further arranged. The chain management client having the alliance authority is called an alliance client, the chain management client having the sub-alliance authority is called a sub-alliance client, and the chain management client having the member authority is called a member client. Different chain management clients typically belong to different organizations, and therefore, the alliance client, the secondary alliance client and the member client may be deployed in machine room devices of different organizations. In the alliance network system, two mechanisms can be selected to participate, and an alliance main client and an auxiliary alliance main client are deployed; preferably, three or more organizations are included, and an alliance client, a sub-alliance client, and a member client are deployed. The number of the alliance main client is one, and the number of the auxiliary alliance main clients is one or more.

In the embodiment of the present application, distributed management of an alliance network is realized by improving the function of a chain management client, and the following is introduced through a detailed embodiment.

Fig. 1B is a flowchart of an operation implementation method of an alliance network according to an embodiment of the present application; the embodiment is suitable for managing a federation network, and the operation implementation method of the federation network is implemented by an operation implementation device of the federation network, wherein the device is configured in a chain management client and can be borne in an electronic device with computing and storing functions, for example, in some electronic device of a machine room deployed by an organization.

The method of this embodiment is specifically executed by a chain management alliance client having alliance authority. As shown in fig. 1B, the method includes:

and S110, controlling the operation of the alliance network based on the management platform data.

The management platform data is data which is used by the BaaS platform for managing the alliance network. Optionally, the management platform data is stored in a machine room device of the mechanism to which the client belongs.

In order to implement management of the alliance network, optionally, the management platform data includes at least one of authentication server (CA) data, platform database data, and data auditing service configuration data.

The operation of controlling the alliance network by the alliance client based on the management platform data comprises the following steps: and authenticating the node identity, deploying an intelligent contract, auditing the uplink data and the like.

In a federation network, generally, a federation owner client needs to be set to uniformly manage the operation of the federation network under the limitation of authority control, technical constraints and the like. For example, the authentication of the CA server requires a unique root certificate for identity authorization. For the operation efficiency of the alliance network, an applicable consensus mechanism is needed to determine the out-of-block node with the function of generating the block in the nodes in a set range. That is, optionally, at least two block chain nodes are deployed in the machine room to which the alliance master client belongs, and are used for assuming a block outputting function. For example, as shown in fig. 1A, when an organization a carries an alliance client, several nodes deployed in an organization a machine room may be controlled to select a deterministic block node, which is beneficial for supporting an efficient consensus mechanism. Nodes in other institutional rooms are used for accounting as accounting nodes, i.e. nodes used for verification of generated blocks.

And S120, synchronizing the management platform data to a chain management auxiliary alliance master client with the auxiliary alliance master authority in the alliance network.

And after the management platform data is synchronized to the auxiliary alliance owner client, the auxiliary alliance owner client controls the operation of the alliance network based on the management platform data when the auxiliary alliance owner client is switched to have alliance authority.

The alliance main client needs to synchronously backup the management platform data to the auxiliary alliance main client. Thus, when the alliance authority is revoked, for example, when the alliance authority is withdrawn, the sub-alliance client can be switched to have the alliance authority, and the function and data of the alliance client are taken over, so that the operation of the alliance network is continuously managed.

The alliance client side can synchronize the management platform data to a chain management auxiliary alliance client side with the auxiliary alliance authority in the alliance network according to a set period or when a synchronization triggering condition is met. The setting period is, for example, one block output period; the synchronization trigger condition may be any timing when synchronization is required, such as when incremental data is generated by generating management platform data.

According to the technical scheme of the embodiment of the application, distributed management of the alliance network is achieved by arranging the alliance client and the auxiliary alliance client. The data synchronization of the management platform is carried out between the alliance main client and the auxiliary alliance main client, so that the alliance network can still continue to operate when the alliance main client exits. According to the technical scheme, management flat right and data flat right can be achieved among a plurality of organizations related to the alliance network, and the auxiliary alliance main client can obtain management platform data so as to perform inquiry and supervision.

In the above technical solution, the operation of controlling the operation of the federation network by the federation owner client based on the management platform data may specifically include the following situations:

first, management based on CA data. That is, controlling the operation of the federation network based on the management platform data includes:

and maintaining the node identity in the alliance network based on authentication server data in the management platform data.

As shown in fig. 1A, a CA server may be deployed in a machine room, where the CA server is configured to perform identity maintenance on nodes participating in a federation network, that is, register, change, or revoke an identity certificate for a node, and provide an identity authentication service for the node in a block chain operation process. The alliance client can control data in the CA server and carry out operations such as authorization on node identities through a root certificate. Of course, each chain management client may use a different root certificate when becoming an alliance master client. Or a mutually approved CA certificate may be used.

And secondly, management based on a BaaS database. That is, controlling the operation of the federation network based on the management platform data includes:

deploying and monitoring at least one of a network configuration, a smart contract configuration, and a chain configuration in the federation network based on platform database data in the management platform data.

As shown in fig. 1A, a BaaS database may be deployed in a machine room, and is used to store platform database data. The platform database is typically used to manage network configuration, intelligent contract configuration, and chain configuration in a federated network. Optionally, the network configuration includes: and the information of the participating nodes in the alliance network, such as node identification, hardware configuration information, software configuration information, dynamic load condition and the like. The intelligent contract configuration comprises: the intelligent contract source code, the version identification and the description information are deployed in the alliance network, and the description information includes intelligent contract deployment time, deployment users, realizable functions and the like. The chain configuration includes: the height of the deployed chain resources and blocks in the alliance network, and the like, the chain resources such as the quantity of electronic money issued in the alliance chain, circulation conditions and the like. A user can perform deployment operations such as addition, deletion, modification and the like on platform database data through the chain management client, and can also perform monitoring operations such as inquiry and the like.

And thirdly, management based on audit service data. That is, controlling the operation of the federation network based on the management platform data includes:

and checking the uplink data in the alliance network based on the data checking service configuration data in the management platform data.

As shown in fig. 1A, the data auditing service configuration data may be configured in the data auditing server for maintaining data auditing services, specifically, in the process of generating a block, the uplink data is pre-audited, and the block can be released after the audit is passed. The data auditing service configuration data includes, for example, data auditing policies and the like.

In the embodiment of the present application, a federation network system formed by several enterprises may carry one or more federation networks, i.e., one or more federation chains. The permissions that each client has in the multiple federation networks may be the same or different, including federation master permissions, secondary federation master permissions, and member permissions. As shown in fig. 1C, the chain management client of the organization a is a member client in the federation network 1, a sub-member client in the federation network 2, and a member client in the federation network 3.

In the embodiment of the present application, the identities of the alliance and the sub-alliance may be determined in various ways, or the identities may be revoked when a condition is satisfied, which is described in detail below.

Determination of alliance identity

The affiliate identity may be determined in a number of ways, such as by user specification, voting, condition-based screening, or algorithm selection.

Specifically, the method in the embodiment of the present application further includes:

acquiring a alliance network establishing request initiated by a user at a local chain management client;

and creating a new alliance network according to the alliance network creating request, and determining an alliance client and a secondary alliance client in all member clients of the new alliance network.

In creating a federated network as described above, each client may be a member client by default. The user specification mode may be specified when the user creates a federation network through the chain management client. For example, the client that initiates the creation request may be the franchisee client by default, and franchisee permission may be given to the franchisee client. Alternatively, it may be specified that a certain member client has an alliance authority based on client information input by the user. Alternatively, the client initiating creation of the federation network may be the alliance client by default, and then the alliance client invites other clients to join the federation network as member clients. Of course, the member client may also choose to join or leave an existing federation network.

For the condition screening method, the franchisee can be screened and determined according to various conditions such as hardware conditions, resource conditions or qualification conditions of the organization to which each client belongs.

For the algorithm selection, the ally-assigned client may be determined by calculation, for example, using a random algorithm or a certain setting algorithm.

(II) determination of Secondary alliance Master identity

The determination of the secondary federation leader client, similar to the federation leader client, may be determined in a variety of ways, such as user specification, voting, screening based on conditions, or algorithm selection. Preferably, the secondary alliance client may be selected and determined in a voting manner among the remaining member clients after the alliance client is determined.

If there are a plurality of sub-franchise clients, the priority may be determined in advance so that the sub-franchise clients can be switched to franchise clients in order of priority. Alternatively, when a handover is necessary, voting may be performed to determine which sub-franchise master client is to be handed over to the franchise master client.

(III) revocation of federated principal identities

Permission revocation of an alliance main client is generally divided into an active situation and a passive situation.

The initiative situation is that the mechanism to which the alliance owner belongs actively quits the alliance network, which is equivalent to abandoning the alliance owner authority. At this time, the affiliate client may notify the sub-affiliate client and the member client of the exit state of the affiliate client so that the sub-affiliate client is switched to be the affiliate client, and may initiate an operation of electing a new sub-affiliate client again.

The passive condition is that the operation of the ally master client is abnormal, such as equipment or network failure. Other clients can recognize the abnormality of the ally owner client, and the ally owner client can be judged to be abnormal based on the consensus mechanism and can not be qualified by the function of the ally owner. When the clients reaching a certain proportion judge that the allied master client is abnormal, the allied master client is determined to cancel the allied master authority and is switched into the auxiliary allied master client for taking over.

(IV) revocation of Secondary alliance Master identity

The permission revocation of the auxiliary alliance main client is similar to the alliance owner and is divided into an active situation and a passive situation.

The initiative situation is that the mechanism of the sub-alliance owner actively quits the alliance network, which is equivalent to abandoning the authority of the sub-alliance owner. At this time, the secondary alliance client may inform the alliance client and the member client of the exit state of the secondary alliance client so as to initiate an operation of electing a new secondary alliance client again.

The passive condition is that the operation of the auxiliary alliance main client side is abnormal, such as equipment or network failure. Other clients can recognize the abnormity of the auxiliary alliance main client, and the abnormity of the auxiliary alliance main client can be judged based on the consensus mechanism and can not be qualified by the auxiliary alliance main client. When the client side reaching a certain proportion judges that the auxiliary alliance main client side is abnormal, the client side and the auxiliary alliance main client side are jointly determined to withdraw the auxiliary alliance authority, and the held auxiliary alliance owner is selected again.

The passive condition may also include the affiliate master client revoking a secondary affiliate master authority of a secondary affiliate master client.

Or, optionally, if the alliance master client determines that the auxiliary alliance master authority of the auxiliary alliance master client is revoked, triggering to select and determine a new auxiliary alliance master client from the member clients of the alliance network; and synchronizing the management platform data to the new auxiliary alliance main client.

Specifically, the alliance master client may separately maintain abnormal monitoring of the secondary alliance master client, for example, whether there is a response after data synchronization or monitoring in a heartbeat packet manner. And when the secondary alliance owner is monitored to be abnormal, informing the user of canceling the secondary alliance owner authority. If the synchronization of the management platform data to the old secondary alliance master client is stopped, the authority of the old secondary alliance master client can be cancelled, so that the old secondary alliance master client does not have the capability of taking over the alliance master client. The affiliate client may notify the member client that a secondary affiliate has been replaced.

In the embodiment of the present application, all enterprises in a federation network can manage the federation network through independent visual clients, including but not limited to: building a alliance network; selecting to join or quit a alliance network; voting to elect allied master and secondary allied master; and configuring a data auditing strategy, carrying out pre-auditing on the uplink data, and outputting blocks after the auditing is passed. Each organization has the right to create a new blockchain network through its BaaS client and then invite other organizations to join the network. Each different blockchain network may have its own member, sub-member, and common member.

On the basis of the technical scheme of the embodiment of the application, the authority of each client can be realized through account login. That is, the method of the embodiment of the present application further includes:

installing a chain management client with a visual interface in the machine room equipment;

and inputting the alliance account information through the visual interface so as to enable the local chain management client to login as the alliance client with alliance authority.

Specifically, the chain management client comprises a visual interface and can perform human-computer interaction. The user is allowed to enter different login accounts in the visual interface, thereby distinguishing different identities of the allied owner, the sub-allied owner and the members.

Optionally, after the information of the alliance owner account is input through the visual interface, the method further comprises the following steps:

and verifying the alliance main account information, judging whether the alliance main account information is matched with the hardware information of the computer room equipment, and if so, confirming that the alliance main account information is verified to be passed.

That is, the account information with different identities needs to be further verified, and whether the account information matches with the hardware information of the logged computer room device, such as information of an IP network segment, a network port, and the like. Of course, the identity authentication of different chain management clients can also be realized by means of an authorization certificate or a key.

Fig. 2 is a flowchart of an operation implementation method of an alliance network provided in the embodiment of the present application, and the embodiment further implements a data display function of a member client based on the foregoing embodiment. The method comprises the following steps:

and S210, controlling the operation of the alliance network based on the management platform data.

And S220, synchronizing the management platform data to a chain management auxiliary alliance master client with the auxiliary alliance master authority in the alliance network.

And the management platform data is used for controlling the operation of the alliance network based on the management platform data when the auxiliary alliance main client is switched to have alliance authority.

And S230, synchronizing the display data of the management platform data to a chain management member client with member authority in the alliance network so that the member client can display the alliance network condition in a visual interface according to the display data.

The management platform data is used for managing the operation of the alliance network, and the display data is used for the member client to know the operation condition of the alliance network. Optionally, the display data includes: at least one of network configuration data, intelligent contract configuration data, and chain configuration data of the federation network. Therefore, the member client can know the conditions of network configuration, intelligent contract configuration and chain configuration.

The member client can display the display data in a visual interface for the user to view. And the search query can be carried out in a targeted manner in response to the query operation of the user.

According to the technical scheme of the embodiment of the application, each mechanism can manage the block chain alliance network added by the mechanism through the BaaS client of the mechanism. Each enterprise may join multiple blockchain alliance networks at the same time and play different roles and assume different responsibilities in different blockchain networks. For example, the A network serves as a member, the B network serves as a subordinate member, and the C network serves as a common member. Each enterprise needs to synchronize data related to the network with other enterprise members of the same alliance network when necessary, and the synchronized data comprises: blockchain network data, i.e., blockbook data; the block chain management platform (BaaS platform) data comprises CA server data, baaS platform database data, data auditing service configuration data and the like.

Fig. 3 is a flowchart of an implementation method for operation of an alliance network according to an embodiment of the present application. The embodiment is executed by a chain management auxiliary alliance client with an auxiliary alliance authority, and the auxiliary alliance client can be borne in equipment of a machine room to which a certain organization belongs, similar to the alliance client. The method comprises the following steps:

s310, acquiring management platform data of the synchronization of the chain management alliance client with alliance authority.

Specifically, the synchronized management platform data may be received from the alliance master client according to a set period or when a synchronization trigger condition is satisfied.

Managing platform data as previously described, may include at least one of authentication server data, platform database books, and data auditing service configuration data.

And S320, when determining that the alliance authority of the alliance client is withdrawn, switching to the alliance client with the alliance authority.

Specifically, the sub-alliance client can take over the identity of the alliance and control the operation of the alliance network based on the previously synchronized management platform data when the alliance authority of the alliance client is withdrawn.

Optionally, determining the alliance authority revocation of the alliance client may include:

receiving a notification of the affiliate client to determine an affiliate authority revocation of the affiliate client; or

Determining an alliance authority revocation of the alliance client based on an consensus mechanism in an alliance network.

For example, when a certain percentage of the member clients determine that the alliance client is abnormal, the alliance authority revocation of the alliance client can be jointly determined. Alternatively, the monitoring relationship may be maintained between the franchise client and the sub franchise client, and for example, the franchise client may transmit a heartbeat packet to the sub franchise client so that the sub franchise client can know the survival state of the franchise client. Management platform data that is synchronized periodically may also serve as a monitoring of the survival status. When the sub-alliance client identifies that the alliance client is abnormal, namely is not in a survival state, the alliance authority of the alliance client can be determined to be withdrawn.

After the sub-alliance client is switched to the alliance client with alliance authority, the method further comprises the following steps: triggering determination of a new secondary federation master client in the federation network. For example, a voting election may be initiated to determine a new secondary affiliate client.

Optionally, the secondary alliance master client also has the capability of creating a new alliance network, that is, the method according to the embodiment of the present application may further include: acquiring a alliance network establishment request initiated by a user at a local chain management client; and creating a new alliance network according to the alliance network creating request, and determining an alliance client and a secondary alliance client in all member clients of the new alliance network.

In the embodiment of the application, the number of the alliance networks is one or more; the authorities of each client in the plurality of alliance networks are the same or different, and the authorities comprise alliance authorities, auxiliary alliance authorities and member authorities.

According to the technical scheme, the method and the device for establishing the distributed block chain network management platform can support the establishment of the distributed block chain network management platform, namely a BaaS platform, and achieve data flat right and a distributed network management architecture. A distributed architecture of alliance network, baaS management and CA management is realized; and the exit of any party member organization (including the exit of the alliance owner) is ensured, and no negative influence is generated on the stable operation of the whole block chain alliance network ecology.

Fig. 4 is a method for implementing operation of an alliance network, provided in this embodiment of the present application, where the method is executed by any chain management client in a chain management platform, such as a BaaS platform. The method comprises the following steps:

and S410, executing operation management of the alliance network, wherein a chain management alliance client with alliance authority is configured in the alliance network.

The link management client may be a client having role authority in the federation network, and may be, for example, a federation owner client, a secondary federation owner client, a member client, or the like. For clients with different authorities, the operation management of the alliance network can be realized under the constraint of different authorities. The alliance client can control the operation of the alliance network based on management platform data; the auxiliary alliance main client can be used as a backup of the alliance main client, receives synchronous data and controls operation of an alliance network when switched to the alliance main client; the member client can participate in the process of the alliance operation management, for example, election voting of alliance main and auxiliary alliance main can be carried out; display data of the management platform data and the like are displayed.

And S420, when determining that the alliance authority of the alliance client of the alliance network is cancelled, determining a new alliance client in the alliance network.

The functions of the alliance owner client and the sub-alliance owner client in the alliance network management process can refer to the introduction of the previous embodiment.

In the embodiment of the application, the revocation mechanism of the ally master client can be determined as required, including consideration on revocation opportunity, revocation mode and the like.

Each chain management client may be an identity of an affiliate, sub-affiliate, or member. When the chain management client is in different identities, the ways of revoking the alliance client authority are different.

Determining an affiliate privilege revocation of an affiliate client of the affiliate network may include, if the local chain management client is a member client or a secondary affiliate client:

determining an alliance authority revocation of an alliance client of the alliance network based on an consensus mechanism; or

Receiving a notification of the affiliate client or secondary affiliate client to determine affiliate authority revocation of the affiliate client.

Specifically, if a certain chain management client is a sub-alliance client or a member client, alliance authority revocation to the alliance client can be actively initiated. This typically occurs when the allied client becomes abnormal or when many organizations believe that the allied organization is no longer competent for the allied. In this case, either the chain management client or the secondary league owner client may initiate consensus votes to elect whether the league owner authority of the current league owner client can be revoked. Or the chain management client can also independently monitor the abnormity of the ally client, count the number of the monitored abnormal chain management clients, and determine to revoke the ally authority of the ally client when the number meets the set threshold condition.

When the secondary league client determines that the league client revokes, then all member clients may be notified of this.

In addition, the ally client may also decide to revoke the own ally authority by itself, and thus notify other member clients to determine the ally authority revocation of the ally client.

(ii) if the local chain management client is an alliance client, determining an alliance authority revocation of the alliance client of the alliance network may comprise:

determining that the local chain management client cancels the allied owner authority according to the user instruction; or

When the abnormity of the block outlet node associated with the local chain management client is monitored, determining that the local chain management client cancels the alliance authority; or

And acquiring a consensus result notice of the alliance network to determine that the local chain management client cancels the alliance owner authority.

Specifically, for the ally-master client, the user can actively withdraw the ally-master authority or automatically determine to withdraw the ally-master authority.

For example, a revocation instruction input by a user can be received through a visual interface, so that the local chain management client is determined to revoke the ally-owned authority. The franchise authority configured by the account can be changed according to the user instruction.

For the case of automatically determining that the alliance authority is revoked, the alliance client may automatically monitor itself for an exception, for example, whether an exception occurs in a machine room device controlled by the alliance client is monitored through a monitoring policy, the exception may include an exception of block generation calculation, an exception of network communication, an exception of a device related to management platform data, and the like, and these exceptions may cause an exception of a block generation node, that is, a block cannot be generated normally. Therefore, it is necessary to revoke the alliance authority so that the sub-alliance client can take over the alliance and maintain the normal operation of the alliance network.

When other chain management clients determine to revoke the alliance authority of the alliance client based on the consensus mechanism, the alliance client can obtain the consensus result notification. This may occur, for example, when a network anomaly itself for the ally hosted client is not discovered.

Fig. 5 is a flowchart of an operation implementation method of an alliance network provided in the embodiment of the present application, where the embodiment optimizes an exit mechanism of an alliance client based on the foregoing embodiment, and the method includes:

and S510, executing operation management of the alliance network.

S520, when the alliance authority of the alliance client of the alliance network is determined to be withdrawn, a new alliance client is determined in the alliance network.

And S530, if the local chain management client is the alliance client, when the alliance authority of the alliance client of the alliance network is determined to be withdrawn, informing the auxiliary alliance client to be switched to the alliance client with the alliance authority.

In the above operation, if the alliance client determines that the alliance authority is revoked, it is preferable to notify the sub-alliance client of switching so as to ensure that the alliance network can smoothly switch alliances and stably operate.

On the basis of the scheme, the step of informing the auxiliary alliance client to switch to the alliance client with the alliance authority optionally comprises the following steps:

stopping synchronization of the management platform data with the secondary alliance master client to inform the secondary alliance master client of switching to an alliance master client having an alliance authority.

Specifically, the notification of the member client to the subordinate member client may be an implicit notification or an explicit notification in a notification message. For example, if the synchronization management platform data is stopped, the sub-alliance master client fails to synchronize the effective management platform data and recognizes an abnormality of the alliance master client, the sub-alliance master client switches to the alliance master client and continues to perform the alliance master role.

By the technical scheme, the switching of the auxiliary alliance main client can be triggered in time when the alliance main client is abnormal, and the smooth and stable operation of an alliance network is ensured.

On the basis of the above technical solution, optionally, if the local chain management client is an alliance client, when determining that the alliance authority of the alliance client of the alliance network is revoked, triggering the determination of a new auxiliary alliance client in the alliance network.

Since the current secondary alliance client has been switched to become an alliance client, a new secondary alliance client needs to be further selected and determined for subsequent switching. Of course, the new sub-alliance client may be initiated and identified by the switched alliance client.

Preferably, the operation of triggering the determination of the new secondary federated master client in the federated network may include:

and initiating a secondary alliance owner vote in the alliance network, and determining a secondary alliance owner client from the member clients according to a voting result.

In the operation implementation method of the alliance network provided by the embodiment of the application, a preferable alliance client screening and determining mechanism is provided, and the exit of the alliance client, the switching of the subsequent alliance client and the determination of a new auxiliary alliance client can be timely triggered under various conditions, so that the stable operation of the alliance network is guaranteed.

Fig. 6 is a flowchart of an operation implementation method of an alliance network according to an embodiment of the present application, and the present embodiment provides a method for determining alliance authority revocation through multi-client cooperation based on the foregoing embodiment, which is suitable for a case where an alliance authority is revoked when a device controlled by an alliance client is abnormal. The method can be executed by any chain management client, and is generally executed by a sub-alliance client or each member client independently. In the method, the operation of determining the revocation of the alliance authority of the alliance client of the alliance network comprises the following steps:

s610, acquiring heartbeat packets broadcast by the alliance main client in the alliance network according to the set heartbeat period.

The alliance main client may broadcast the heartbeat packet in the alliance network according to a certain period, for example, the heartbeat packet is broadcast once every 2 seconds, and specifically, the alliance main client controls a machine room device, for example, a certain block chain node to broadcast the heartbeat packet.

And S620, identifying the survival state of the ally client according to the receiving condition of the heartbeat packet, and generating an ally abnormal affirming message when the survival state is abnormal.

Each chain management client may receive heartbeat packets, e.g., broadcast heartbeat packets, through controlled equipment room devices, e.g., block chain nodes. If the heartbeat packet cannot be normally received, at least communication abnormality between the device of the alliance client and the device of the chain management client is explained, and the device of the alliance client is abnormal and is in a non-survival state. Accordingly, an alliance exception assertion message is generated when the survival status is abnormal. The alliance owner exception assertion message may be signed with a private key of the chain management client to indicate identity.

Optionally, the chain management client may specifically be:

if the heartbeat packet of the alliance client is not received before the heartbeat monitoring countdown is finished, an alliance owner abnormal affirmation message is generated.

And if the heartbeat packet is received before the heartbeat monitoring countdown is finished, indicating that the ally-assigned client side is alive, re-determining the heartbeat monitoring countdown, and entering the next round of monitoring. If the heartbeat packet is not received before the heartbeat monitoring countdown is finished, the alliance client side is not alive, and an alliance abnormal affirmation message is generated.

S630, broadcasting the alliance owner abnormal identification information in the alliance network.

And S640, if the situation that the alliance owner abnormity identification information broadcasted by the chain management client in the alliance network reaches the set quantity condition is determined, the alliance owner client is determined to be abnormal, and the alliance owner permission of the alliance owner client in the alliance network is determined to be withdrawn.

The other chain management clients except the alliance master client can independently receive the heartbeat packet, identify the abnormal survival state and broadcast the alliance master abnormal confirmation message, and can also receive the alliance master abnormal confirmation message broadcast by the other chain management clients. When the alliance owner abnormity identification information in the alliance network reaches the set quantity condition, a certain number of chain management clients all identify alliance owner abnormity, and then the alliance owner authority of the alliance owner client of the alliance network can be determined to be cancelled. The set number condition may be an absolute number or a ratio, for example, two-thirds of the clients deemed abnormal and considered to reach the set number condition.

Optionally, the operation of determining that the alliance owner client is abnormal when determining that the alliance owner abnormal affirmation message broadcasted by the chain management client in the alliance network reaches the set number condition includes:

randomly generating a statistic countdown, and collecting alliance owner abnormal identification information broadcasted in an alliance network before the statistic countdown is finished;

and if the number of the collected alliance owner abnormity identification messages reaches a set number condition, determining that the alliance owner client end is abnormal.

In the above scheme, the chain management client may randomly generate a statistical countdown to collect the exception acknowledgement messages initiated by other clients after broadcasting the owner exception acknowledgement message. The randomly generated statistical countdown ensures that each chain management client does not simultaneously determine the revocation of the allied owner, and the first client determining the revocation of the allied owner authority can inform the auxiliary allied owner client and other member clients. Other clients may verify that the revocation of the assertion is correct. The countdown generating algorithm, the set quantity condition and the multi-party threshold signature mode of the multi-client can be uniformly configured at the client, and all the clients execute the revocation mode respectively, so that consensus can be achieved, and the authority of the alliance owner can be revoked when the alliance owner is abnormal.

The determination of a new alliance master client in the alliance network optionally comprises:

and informing the secondary alliance client to be switched into a new alliance client.

The first chain management client that determines the revocation of the master alliance client may notify the slave alliance client. After the sub-alliance main client is switched to the alliance main client, the sub-alliance main client can send a notification message of the switching to inform all other chain management clients.

According to the technical scheme of the embodiment, each chain management client can independently execute the revocation strategy of the alliance, and a plurality of clients can achieve consensus to control revocation of the alliance authority.

Fig. 7 is a schematic structural diagram of an operation implementation apparatus of an alliance network according to an embodiment of the present application. The device can realize the operation realization method of the alliance network in the embodiment of the application. The apparatus may be configured in a chain management client. The operation implementing apparatus 700 of the alliance network specifically includes:

an authority revocation determination module 710 for determining federation owner authority revocation of a federation owner client of the federation network;

a new client determining module 720, configured to determine a new alliance client in the alliance network when the alliance authority revocation of the alliance owner client of the alliance network is determined;

the alliance main client is used for controlling operation of an alliance network based on management platform data; and is used for synchronizing the management platform data to a chain management secondary alliance master client with a secondary alliance master authority in the alliance network.

The technical scheme of the embodiment of the application provides a quit mechanism of the alliance client, and can trigger quit of the alliance client in time under various conditions, and switching of the alliance client and determination of a new auxiliary alliance client subsequently, so that stable operation of an alliance network is guaranteed.

For example, if the local chain management client is a member client or a secondary alliance master client, the permission revocation determination module 710 is specifically configured to:

determining alliance authority revocation of an alliance client of the alliance network based on an consensus mechanism; or

Receiving a notification of the allied client or the sub-allied client to determine an allied permission revocation of the allied client.

For example, if the local chain management client is an alliance master client, the permission revocation determination module 710 is specifically configured to:

determining that the local chain management client cancels the allied master authority according to the user instruction; or

Exemplarily, the apparatus further includes:

and the notification module is used for notifying the auxiliary alliance client to be switched to the alliance client with alliance authority when the local chain management client is the alliance client and the alliance authority of the alliance client of the alliance network is determined to be withdrawn.

Illustratively, the notification module is specifically configured to:

the synchronization of the management platform data to the sub-alliance master client is stopped to inform the sub-alliance master client of the switching to the alliance master client having the alliance authority.

Illustratively, the new client determination module 720 is further configured to:

and if the local chain management client is the alliance client, triggering to determine a new auxiliary alliance client in the alliance network when the alliance authority of the alliance client of the alliance network is determined to be withdrawn.

Illustratively, the new client determining module 720 is specifically configured to:

Illustratively, the management platform data in this embodiment includes at least one of authentication server data, platform database books, and data auditing service configuration data.

Illustratively, the rights revocation determination module 710 includes:

the system comprises a heartbeat packet acquisition unit, a heartbeat packet transmission unit and a heartbeat packet transmission unit, wherein the heartbeat packet acquisition unit is used for acquiring a heartbeat packet broadcasted by a alliance main client in an alliance network according to a set heartbeat period;

the survival state identification unit is used for identifying the survival state of the alliance main client according to the receiving condition of the heartbeat packet and generating alliance main abnormal identification information when the survival state is abnormal;

a message broadcasting unit for broadcasting the alliance owner abnormal identification message in the alliance network;

and the permission revocation determining unit is used for determining that the alliance client is abnormal and determining alliance permission revocation of the alliance client of the alliance network if determining that the alliance abnormality confirmation message broadcasted by the chain management client in the alliance network reaches the set number condition.

Illustratively, the survival status identification unit is specifically configured to:

if the heartbeat packet of the ally leader client is not received before the heartbeat monitoring countdown is finished, generating an ally leader abnormal affirmation message.

Illustratively, the permission revocation determination unit is specifically configured to:

randomly generating a statistical countdown, and collecting an alliance owner abnormity identification message broadcasted in an alliance network before the statistical countdown is finished;

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

FIG. 8 illustrates a schematic block diagram of an example electronic device 800 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 8, the electronic device 800 includes a computing unit 801 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic apparatus 800 can also be stored. The calculation unit 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

A number of components in the electronic device 800 are connected to the I/O interface 805, including: an input unit 806, such as a keyboard, a mouse, or the like; an output unit 807 such as various types of displays, speakers, and the like; a storage unit 808, such as a magnetic disk, optical disk, or the like; and a communication unit 809 such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows the electronic device 800 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

Computing unit 801 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 801 performs the various methods and processes described above, such as the operational implementation of a federated network. For example, in some embodiments, the operations implementing the method of federation network may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program can be loaded and/or installed onto the electronic device 800 via the ROM 802 and/or the communication unit 809. When loaded into RAM 803 and executed by the computing unit 801, the computer programs may perform one or more of the steps of the above-described operational implementation method of a federated network. Alternatively, in other embodiments, the computing unit 801 may be configured in any other suitable manner (e.g., by way of firmware) to perform the federated network's operational implementation method.

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. An operation implementation method of an alliance network, the method is executed by a chain management client, and the method comprises the following steps:

when determining that the alliance authority of the alliance client of the alliance network is revoked, determining a new alliance client in the alliance network; the alliance network is formed by a plurality of organizations together, a plurality of chain management clients are installed and operated at the same time, and different chain management clients belong to different organizations;

the alliance client is used for controlling the operation of the alliance network based on management platform data; and is used for synchronizing the management platform data to a chain management auxiliary alliance owner client with an auxiliary alliance owner authority in the alliance network; the operation of the alliance network is managed by a chain management platform in a block chain form, the chain management platform is provided with a plurality of chain management clients with different authorities, and the authorities comprise alliance main authorities and auxiliary alliance main authorities.

2. The method of claim 1, wherein determining an alliance authority revocation of an alliance client of the alliance network if the local chain management client is a member client or a secondary alliance client comprises:

3. The method of claim 1, wherein determining an affiliate authority revocation of an affiliate client of the affiliate network if the local chain management client is an affiliate client comprises:

4. The method of claim 1, when determining that an affiliate authority of an affiliate client of the federation network revokes if the local chain management client is an affiliate client, further comprising:

notifying the secondary alliance client to switch to an alliance client with alliance authority.

5. The method of claim 4, wherein notifying the secondary federated owner client to switch to a federated owner client with federated owner privileges comprises:

6. The method of claim 1, if the local chain management client is an alliance client, upon determining an alliance authority revocation of the alliance client of the alliance network, further comprising:

triggering determination of a new secondary federation master client in the federation network.

7. The method of claim 6, wherein triggering determination of a new secondary federated master client in the federated network comprises:

8. The method of claim 1, wherein the management platform data comprises at least one of authentication server data, platform database books, and data auditing service configuration data.

9. The method of claim 1, wherein determining an alliance authority revocation of an alliance client of the alliance network comprises:

acquiring a heartbeat packet broadcast in a alliance network by a alliance main client according to a set heartbeat period;

identifying the survival state of the alliance client according to the receiving condition of the heartbeat packet, and generating alliance abnormity identification information when the survival state is abnormal;

broadcasting the alliance owner abnormal identification message in the alliance network;

if the situation that the alliance owner broadcast by the chain management client in the alliance network is confirmed to be abnormal and the situation that the alliance owner client is abnormal reaches the set number condition is determined, and the alliance owner authority of the alliance owner client in the alliance network is determined to be withdrawn.

10. The method of claim 9, wherein identifying the liveness status of the ally owner client according to the receipt of the heartbeat packet and generating an ally owner anomaly assertion message when the liveness status is anomalous comprises:

11. The method of claim 9, wherein determining that the alliance client broadcast alliance anomaly ok message reaches a set number condition comprises:

12. The method of claim 1 or 9, wherein determining a new federation master client in the federation network comprises:

and informing the auxiliary alliance client to switch into a new alliance client.

13. An apparatus for implementing an operation of a federated network, the apparatus being configured at a chain management client, the apparatus comprising:

an authority revocation determining module for determining alliance authority revocation of alliance client-side of the alliance network; the alliance network is formed by a plurality of organizations together, a plurality of chain management clients are installed and operated at the same time, and different chain management clients belong to different organizations;

14. The apparatus according to claim 13, wherein if the local chain management client is a member client or a secondary alliance master client, the permission revocation determination module is specifically configured to:

15. The apparatus according to claim 13, wherein if the local chain management client is an alliance master client, the permission revocation determination module is specifically configured to:

When the abnormity of the block outlet node associated with the local chain management client is monitored, the local chain management client is determined to cancel the allied master authority; or

16. The apparatus of claim 13, further comprising:

17. The apparatus of claim 16, wherein the notification module is specifically configured to:

18. The apparatus of claim 13, wherein the new client determination module is further configured to:

if the local chain management client is the alliance owner client, when the alliance authority of the alliance owner client of the alliance network is determined to be withdrawn, determining a new auxiliary alliance owner client in the alliance network is triggered.

19. The apparatus of claim 18, wherein the new client determination module is specifically configured to:

20. The apparatus of claim 13, wherein the management platform data comprises at least one of authentication server data, platform database books, and data auditing service configuration data.

21. The apparatus of claim 13, wherein the permission revocation determination module comprises:

the system comprises a heartbeat packet acquisition unit, a heartbeat packet transmission unit and a heartbeat packet transmission unit, wherein the heartbeat packet acquisition unit is used for acquiring heartbeat packets broadcast by a alliance main client side in an alliance network according to a set heartbeat period;

the survival state identification unit is used for identifying the survival state of the ally owner client according to the receiving condition of the heartbeat packet and generating an ally owner abnormity identification message when the survival state is abnormal;

and the permission revocation determining unit is used for determining that the allied client is abnormal and determining that the allied authority of the allied client of the alliance network revokes if determining that the allied authority abnormal identification message broadcasted by the chain management client in the alliance network reaches the set number condition.

22. The apparatus according to claim 21, wherein the survival status identification unit is specifically configured to:

23. The apparatus according to claim 21, wherein the permission revocation determination unit is specifically configured to:

24. The apparatus according to claim 13 or 21, wherein the new client determining module is specifically configured to:

25. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method for operational implementation of a federated network as recited in any one of claims 1-12.

26. A non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform a method for implementing operations of a federated network as described in any one of claims 1-12.