WO2024060401A1

WO2024060401A1 - Distributed blockchain baas system based on gossip communication

Info

Publication number: WO2024060401A1
Application number: PCT/CN2022/134585
Authority: WO
Inventors: 吴家彬; 汪昌帅; 贺伟
Original assignee: 天翼电子商务有限公司
Priority date: 2022-09-20
Filing date: 2022-11-28
Publication date: 2024-03-28
Also published as: CN115695440A

Abstract

Disclosed in the present invention is a distributed blockchain BaaS system based on gossip communication. The system comprises: gossip message communication, group resource isolation, BaaS blockchain resource privatization management, and cross-BaaS node blockchain node invitation for networking. Specifically, regarding gossip message communication of BaaS nodes, message interactions between the BaaS nodes are implemented by introducing a gossip communication protocol; and when a large number of BaaS nodes need data synchronization, a common P2P mode is not suitable, and it is required that the BaaS nodes maintain two connection pools, i.e., incoming and outgoing, so that the number of local links of the BaaS nodes is increased by a multiple number of 2N. According to the present solution, communication and data synchronization between the BaaS nodes are implemented by using the gossip protocol; and according to the characteristics of gossip, the BAAS node does not need to be in P2P connection with all BaaS in a cluster, and only needs to be connected to one subset. Moreover, the consistency of blockchain resource data in the cluster is realized by means of gossip, and a message packet which can be processed by a specified node is transmitted by means of gossip, so that cross-BaaS node blockchain nodes are invited for networking.

Description

A distributed blockchain BaaS system based on gossip communication

Technical field

The invention relates to the technical field of blockchain and distributed applications, and in particular to a distributed blockchain BaaS system based on gossip communication.

Background technique

The vast majority of current BaaS platform architectures are usually single-point deployments, which are deployed and maintained by an organization and provide access to the BaaS platform. Platform users operate the blockchain system by importing their local physical machine resources or renting resources provided by the BaaS platform.

technical problem

Under some projects, there will be multiple peer organizations. These organizations may all require the deployment of BaaS platforms to manage their local blockchain resources, but BaaS nodes cannot communicate with each other. When nodes are networked, the resources of other BaaS must be managed. This will cause multiple BaaS to manage one resource at the same time, reducing the security and manageability of the resource.

Technical solutions

The technical problem to be solved by this invention is to overcome the defects of the existing technology, provide a distributed blockchain BaaS system based on gossip communication, realize the communication function between BaaS platform nodes through the gossip protocol, and solve the problem of cross-platform invitation blocks It solves the problem of inaccessible resources during chain networking, and improves the management capabilities of private blockchain resources between BaaS platforms through the group mechanism and local blockchain resource permission management, solving the problem of inability to interact with data between multiple BaaS platforms. .

The present invention provides the following technical solutions:

The present invention provides a distributed blockchain BaaS system based on gossip communication. This system includes: gossip message communication, group resource isolation, BaaS blockchain resource privatization management, and cross-BaaS invitation blockchain node networking; specifically As follows:

1. BaaS node gossip message communication:

The message interaction between BaaS nodes is realized by introducing gossip communication protocol; when there are a large number of BaaS nodes that need data synchronization, the ordinary P2P model is not suitable. It requires the BaaS node to maintain two connection pools, incoming and outgoing, resulting in the local BaaS node The number of links increases by a multiple of 2n;

The gossip protocol allows the BaaS node to connect to some nodes in the cluster. After the BaaS node adds and updates the blockchain resource data, the bottom layer automatically makes the changed data into a gossip message package and propagates it to all other connected nodes. With the Rumer-Mongering feature of gossip, the BaaS cluster can always maintain data consistency;

When a new BaaS node joins the cluster, through the Anti-entropy feature of gossip, the new BaaS node will request all data blockchain resource data under the current cluster from the connected node, and quickly synchronize to the latest status;

The gossip protocol itself has a network fault tolerance mechanism. Its multi-node message redundant transmission feature ensures that when the network between two nodes is unreachable, other nodes will also try to send the same message.

2. Invite blockchain nodes to network across BaaS nodes:

When conducting cross-BaaS node invitation networking, the BaaS node sends invitation information that can only be received by the designated node and spreads it through the gossip protocol. When the non-target node receives the message, it will compare whether the designated node in the message is itself. , if it is not the local node, it will not be processed, and only the message will be disseminated; after the target node receives the message, if it agrees, it will return the acceptance message and the blockchain node certificate file through the gossip message package, otherwise it will return a rejection message carrying the reason for rejection;

3. Group resource isolation:

Group allows BaaS nodes to form a private network and spread blockchain resources that are only public in the group. BaaS nodes not in the group cannot obtain resource information within the group. Partial sharing of BaaS blockchain resources can be achieved through the group. and isolation;

BaaS nodes can enter the group name in the management interface to create a group. After successful creation, the unique group_identifier in the entire network will be returned. Other BaaS nodes need to provide the group name and group_identifier to the internal nodes of the group to join the group. After joining the group, the BaaS nodes will automatically Synchronize the blockchain resource information within the group; group_identifier is calculated by the following formula:

group_identifier=hex(sha256(group_name+timestamp))

If the BaaS node does not need to access the private group, the node can join the global group. The global group is the global default group and any BaaS node can join. The BaaS node only needs to connect to the public seed node;

4. BaaS blockchain resource privatization management:

All blockchain resources managed by BaaS nodes do not need to be made public. When creating blockchain resources, BaaS can choose whether to make them public or to optimize local management. Private resource management can be divided into the following three situations:

(1) Agent resources exposed in global: Almost all BaaS nodes can be synchronized, but resource owners can still choose to hide them privately when creating blockchain resources;

(2) Agent resources disclosed in a private group: Only members within the group can view them. Resource owners can still choose to hide them privately when creating blockchain resources.

(3) Completely privatize locally managed agent resources: other BaaS nodes are not visible.

beneficial effects

Compared with the prior art, the beneficial effects of the present invention are as follows:

(1) Nodes in distributed applications usually use P2P for full-node connections, which causes nodes to maintain too many connection instances; this solution uses the gossip protocol to replace full-node connections without losing system decentralization. Nodes only need to maintain a small number of connections to achieve data consistency within the cluster;

(2) This solution uses the gossip protocol to achieve communication and data synchronization between BaaS nodes. Relying on the characteristics of the gossip protocol, after updating the local blockchain resources, the BaaS node only needs to pass the new data to a small number of nodes through the gossip message package. In the end, except for the offline node, other nodes in the message package can complete the data. Synchronize. The new BaaS node owner needs to know an existing BaaS node to join the cluster and quickly synchronize data to the latest status;

(3) Invite blockchain node networking across BaaS nodes through the gossip protocol. BaaS uses gossip to deliver the message package processed by the designated node, and only relays the message package through the nodes in the cluster. This approach can eliminate the need to create new TCP connections between BaaS nodes;

(4) This solution also implements a group resource isolation mechanism, allowing the formation of sub-clusters between BaaS nodes to achieve resource data isolation between BaaS clusters. Applicable to the current BaaS cluster, when multiple BaaS nodes form a private blockchain network, they can use groups to make BaaS nodes unrelated to this blockchain network unknown. This solution also allows BaaS nodes to selectively expose or hide blockchain resources to improve the security of local blockchain resources.

Description of the drawings

The drawings are used to provide a further understanding of the present invention and constitute a part of the specification. They are used to explain the present invention together with the embodiments of the present invention and do not constitute a limitation of the present invention. In the attached picture:

Figure 1 is one of the schematic diagrams of the embodiment of the present invention;

Figure 2 is a second schematic diagram of the embodiment of the present invention;

Figure 3 is a third schematic diagram of the embodiment of the present invention;

Figure 4 is a schematic diagram of the present invention's dissemination of local blockchain resource information based on gossip;

Figure 5 is a schematic diagram of a BaaS node joining a private group according to the present invention;

Figure 6 is a schematic diagram of the cross-BaaS platform invitation blockchain node networking according to the present invention.

Embodiments of the invention

The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described here are only used to illustrate and explain the present invention, and are not intended to limit the present invention. The same reference numerals in the drawings all refer to the same components.

实施例1Example 1

As shown in Figures 1-6, the present invention provides a distributed blockchain BaaS system based on gossip communication. This system includes: gossip message communication, group resource isolation, BaaS blockchain resource privatization management, and cross-BaaS invitation blocks. Link node networking; details are as follows:

1. BaaS node gossip message communication:

The gossip protocol itself comes with a network fault-tolerance mechanism, and its multi-node message redundant sending feature ensures that if the network between two nodes is unreachable, other nodes will also try to send the same message;

2. Invite blockchain nodes to network across BaaS nodes:

When conducting cross-BaaS node invitation networking, the BaaS node sends invitation information that can only be received by the designated node and spreads it through the gossip protocol. When the non-target node receives the message, it will compare whether the designated node in the message is itself. , if it is not the local node, it will not be processed, and only the message will be disseminated; after the target node receives the message, if it agrees, it will return the acceptance message and the blockchain node certificate file through the gossip message package, otherwise it will return a rejection message carrying the reason for rejection. As shown in Figure 1;

3. Group resource isolation:

Groups allow BaaS nodes to form a private network and spread blockchain resources that are only public in the group. BaaS nodes outside the group cannot obtain resource information within the group. Through groups, local sharing and isolation of BaaS blockchain resources can be achieved;

group_identifier=hex(sha256(group_name+timestamp))

If the BaaS node does not need to access the private group, the node can join the global group. The global group is the global default group and any BaaS node can join. The BaaS node only needs to connect to the public seed node, as shown in Figure 2 shown;

4. BaaS blockchain resource privatization management:

All blockchain resources managed by BaaS nodes do not need to be made public. When creating blockchain resources, BaaS can choose whether to make them public or to optimize local management. Private resource management can be divided into the following three situations, as shown in Figure 3. :

(2) Agent resources disclosed in private groups: only internal members of the group can view them, and resource owners can still choose to hide them privately when creating blockchain resources;

Furthermore, BaaS platforms are deployed in multiple companies, and the networks between BaaS nodes can be interoperable. One BaaS node creates a group, and other BaaS nodes join the group, create blockchain nodes and networks, install smart contracts, and invite blockchain across platforms. Node networking, the blockchain data information saved between BaaS nodes remains consistent.

The invention has the following characteristics:

1. This solution uses the gossip protocol to achieve communication and data synchronization between BaaS nodes. Relying on the characteristics of gossip, BaaS nodes do not need to have P2P connections with all BaaS in the cluster, but only need to connect to a subset. At the same time, the blockchain resource data consistency within the cluster is achieved through gossip, and the message package that can be processed by the designated node is transmitted through gossip, so as to invite blockchain nodes to network across BaaS nodes.

This solution also implements a group resource isolation mechanism, allowing sub-clusters to be formed between BaaS nodes to achieve resource data isolation between BaaS clusters. Applicable to the current BaaS cluster, when multiple BaaS nodes form a private blockchain network, they can use groups to make BaaS nodes unrelated to this blockchain network unknown. This solution also allows BaaS nodes to selectively expose or hide blockchain resources to improve the security of local blockchain resources.

Finally, it should be noted that the above are only preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, for those skilled in the art, it is still The technical solutions described in the foregoing embodiments may be modified, or some of the technical features may be equivalently replaced. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims

A distributed blockchain BaaS system based on gossip communication, which is characterized in that the system includes: gossip message communication, group resource isolation, BaaS blockchain resource privatization management, and cross-BaaS invitation blockchain node networking; The details are as follows:

1. BaaS node gossip message communication:

The message interaction between BaaS nodes is realized by introducing gossip communication protocol; when there are a large number of BaaS nodes that need data synchronization, the ordinary P2P model is not suitable. It requires the BaaS node to maintain two connection pools, incoming and outgoing, resulting in the local BaaS node The number of links increases by a multiple of 2n;

The gossip protocol allows the BaaS node to connect to some nodes in the cluster. After the BaaS node adds and updates the blockchain resource data, the bottom layer automatically makes the changed data into a gossip message package and propagates it to all other connected nodes. With the Rumer-Mongering feature of gossip, the BaaS cluster can always maintain data consistency;

When a new BaaS node joins the cluster, through the Anti-entropy feature of gossip, the new BaaS node will request all data blockchain resource data under the current cluster from the connected node, and quickly synchronize to the latest status;

The gossip protocol itself comes with a network fault-tolerance mechanism, and its multi-node message redundant sending feature ensures that if the network between two nodes is unreachable, other nodes will also try to send the same message;

2. Invite blockchain nodes to network across BaaS nodes:

When inviting a network across BaaS nodes, the BaaS node sends an invitation message that can only be received by the designated node and propagates it through the gossip protocol. When the non-target node receives the message, it will compare whether the designated node in the message is itself. If it is not the current node, it will not process it and only propagate the message. After the target node receives the message, if it agrees, it will return the acceptance message and blockchain node certificate file through the gossip message package, otherwise it will return a rejection message with the rejection reason.

3. Group resource isolation:

Group allows BaaS nodes to form a private network and spread blockchain resources that are only public in the group. BaaS nodes not in the group cannot obtain resource information within the group. Partial sharing of BaaS blockchain resources can be achieved through the group. and isolation;

BaaS nodes can enter the group name in the management interface to create a group. After successful creation, the unique group_identifier in the entire network will be returned. Other BaaS nodes need to provide the group name and group_identifier to the internal nodes of the group to join the group. After joining the group, the BaaS nodes will automatically Synchronize the blockchain resource information within the group; group_identifier is calculated by the following formula:

group_identifier=hex(sha256(group_name+timestamp))

If the BaaS node does not need to access the private group, the node can join the global group. The global group is the global default group and any BaaS node can join. The BaaS node only needs to connect to the public seed node;

4. BaaS blockchain resource privatization management:

All blockchain resources managed by BaaS nodes do not need to be made public. When creating blockchain resources, BaaS can choose whether to make them public or to optimize local management. Private resource management can be divided into the following three situations:

(1) Agent resources exposed in global: Almost all BaaS nodes can be synchronized, but resource owners can still choose to hide them privately when creating blockchain resources;

(2) Agent resources disclosed in private groups: only internal members of the group can view them, and resource owners can still choose to hide them privately when creating blockchain resources;

(3) Completely privatize locally managed agent resources: other BaaS nodes are not visible.