CN113709197B - Alliance block chain organization system and block chain system - Google Patents
Alliance block chain organization system and block chain system Download PDFInfo
- Publication number
- CN113709197B CN113709197B CN202010433356.XA CN202010433356A CN113709197B CN 113709197 B CN113709197 B CN 113709197B CN 202010433356 A CN202010433356 A CN 202010433356A CN 113709197 B CN113709197 B CN 113709197B
- Authority
- CN
- China
- Prior art keywords
- node
- backup
- accounting
- blockchain
- nodes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000008520 organization Effects 0.000 title claims abstract description 122
- 235000013305 food Nutrition 0.000 description 13
- 238000010586 diagram Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 238000000034 method Methods 0.000 description 7
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 201000010099 disease Diseases 0.000 description 1
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 1
- 229940079593 drug Drugs 0.000 description 1
- 239000003814 drug Substances 0.000 description 1
- 230000005284 excitation Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a alliance blockchain organization system and a blockchain system, wherein the alliance blockchain organization system comprises a first accounting node, a first backup node set, a private gateway node and a public gateway node; the first accounting node is connected with the first backup node set through a network; the first set of backup nodes is for synchronizing the ledger from the first accounting node; the private gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring data of the account book from the first accounting node and the first backup node set based on the first authority; the public gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring data of the account book from the first accounting node and the first backup node set based on the second authority, wherein the number of allowed service types in the first authority is smaller than that of allowed service types in the second authority, and the first client is a client outside the alliance blockchain organization system.
Description
Technical Field
The application relates to the technical field of blockchains, in particular to a alliance blockchain organization system and a blockchain system.
Background
Blockchain technology is becoming popular with its characteristics of decentralization, non-falsification, safety, reliability, strong expansibility, etc. The development of the blockchain technology can be summarized as the following stages, from cryptocurrency to intelligent contracts and to future everything interlinks, people in various industries begin to look at the actual application scene of the blockchain. The blockchain technology is taken as a distributed account book, necessarily involves the deployment and expansion of nodes in a distributed system, and is different from a public chain, so that the joining of alliance blockchain members is more complicated and strict. A federated blockchain is a type of blockchain that is targeted only to members of a particular population and to limited third parties. Within the federated blockchain, a plurality of preselected nodes may be designated as the billers, with the generation of each block being determined jointly by all of the preselected nodes.
Currently, known federated blockchain organization systems are not load balanced and are not available in high availability.
Disclosure of Invention
The embodiment of the application provides a alliance blockchain organization system and a blockchain system, which aim to solve the problem of balancing the load of the alliance blockchain organization system and improve the usability.
In a first aspect, the present application provides a federated blockchain organization system, including a first accounting node, a first backup node set, a private gateway node, a public gateway node;
the first accounting node is connected with the first backup node set in a network manner, and the first accounting node is commonly recognized with other alliance blockchain organization systems except the alliance blockchain organization system and stores an account book;
the first set of backup nodes is for synchronizing the ledger from the first accounting node;
the private gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring a service request of a first client and acquiring data of the account book from the first accounting node and the first backup node set based on a first authority;
the public gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring the service request of the first client and acquiring the data of the account book from the first accounting node and the first backup node set based on the second authority,
the number of allowed service types in the first authority is smaller than that of allowed service types in the second authority, and the first client is a client outside the alliance blockchain organization system.
The number of the first accounting nodes is at least two, the number of the first backup node sets is at least two, at least two first accounting nodes are respectively connected with at least two first backup node sets, at least two first accounting nodes are used for participating in consensus with other alliance blockchain organization systems at the same time, and the new blocks after consensus are respectively written into the first backup node sets which are respectively connected.
The first backup node set comprises at least two first primary backup nodes and at least two first secondary backup nodes, the at least two first primary backup nodes are connected with the first billing nodes, the at least two first primary backup nodes are used for synchronizing the account book from the first billing nodes connected with the at least two first primary backup nodes, the first primary backup nodes are connected with the at least one first secondary backup node, and the at least two first secondary backup nodes are used for synchronizing the account book from the first primary backup nodes connected with the at least two first secondary backup nodes.
The at least two first primary backup nodes are connected with each other, so that the at least two first primary backup nodes can synchronize the ledger with each other.
The alliance blockchain organization system comprises a second client, wherein the second client can be connected with any one node in the first accounting node and the first backup node set to acquire data in the account book.
The alliance blockchain organization system further comprises a tracing server, wherein the tracing server is connected with the public gateway node and is used for monitoring communication between the public gateway node and the first client.
In a second aspect, the present application provides a blockchain system including the federated blockchain organization of any of the first aspects.
The blockchain system comprises at least two first alliance blockchain organization systems, wherein the first alliance blockchain organization systems are any one of the alliance blockchain organization systems in the first aspect, the at least two first alliance blockchain organization systems are commonly identified through a first accounting node, and an accounting book is stored.
The blockchain system further comprises a second federation blockchain organization system for supervising the at least two first federation blockchain organization systems, the second federation blockchain organization system comprising a second set of backup nodes for synchronizing the ledger from the first billing node of the first federation blockchain organization system.
The second backup node set comprises at least two second-level backup nodes and at least two second-level backup nodes, the at least two second-level backup nodes are used for synchronizing the account book from the first accounting node of the first alliance blockchain organization system, the second-level backup nodes are connected with at least one second-level backup node, and the at least two second-level backup nodes are connected with the account book from the second-level backup node.
The application provides a alliance blockchain organization system, the connection between an external client of the alliance blockchain organization system and the alliance blockchain organization system is established through a private gateway node and a public gateway node, and by setting different authorities for the private gateway node and the public gateway, a part of service requests with higher service requirements can be accessed into the alliance blockchain organization system through the private gateway node, so that the availability of the alliance blockchain organization system is improved, and meanwhile, the account book of a first accounting node is backed up through a first backup node set, so that the load pressure of the first accounting node can be reduced, and the alliance blockchain organization system is balanced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of one embodiment of a federated blockchain organization provided in embodiments of the present application;
FIG. 2 is a schematic diagram of a first backup node set in an embodiment of a federated blockchain organization system provided in embodiments of the present application;
FIG. 3 is a schematic block diagram of one embodiment of a blockchain system provided in accordance with the embodiments of the present application;
fig. 4 is a schematic structural diagram of a second backup node set in an embodiment of a blockchain system provided in an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
In the description of the present application, it should be understood that the terms "center," "longitudinal," "transverse," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate an orientation or positional relationship based on that shown in the drawings, merely for convenience of description and to simplify the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be configured and operated in a particular orientation, and thus should not be construed as limiting the present application. Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more features. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
In this application, the term "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for purposes of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known structures and processes have not been shown in detail to avoid obscuring the description of the present application with unnecessary detail. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
Some basic concepts involved in the embodiments of the present invention will be first described below:
blockchain: the blockchain is an important concept of bit coin, is essentially a de-intermediated database, is a bottom technology of bit coin, is a series of data blocks generated by associating a cryptography method, each data block contains information of a bit coin network transaction for verifying the validity of the information and generating a next block, generally speaking, the blockchain multi-chain system consists of a data layer, a network layer, a consensus layer, an excitation layer, a contract layer and an application layer, in a narrow sense, the blockchain is a chain type data structure formed by sequentially connecting the data blocks according to time sequence, and is a non-falsifiable and non-falsifiable distributed account book ensured in a cryptography method, in a broad sense, the blockchain technology is a distributed script operation and a calculation basic operation mode which is characterized in that the data is verified and stored by utilizing the block chain type data structure, the information of a distributed node consensus algorithm is generated and updated by utilizing the cryptography method, the data transmission and automatic access are ensured by utilizing the security of the cryptography method, and the intelligent contract code is utilized.
Blockchains can be categorized into public blockchains, private blockchains, federated blockchains. The alliance blockchain is between the public blockchain and the private blockchain, and a plurality of organizations cooperate together to maintain a blockchain, the use of the blockchain must be authorized to be managed, and related information is protected, such as a financial organization.
In summary, a blockchain is a distributed database system that is engaged by nodes, or may also be referred to as a distributed public ledger based on a point-to-point network, characterized as being unalterable, impersonatable, and also understood as an accounting system.
Nodes of the blockchain: the nodes participating in building the blockchain can be execution subjects for random number generation, interaction among the nodes can realize business such as transaction and the like. The node stores the associated block data.
The embodiment of the application provides a alliance blockchain organization system and a blockchain system. The following will describe in detail.
Firstly, a alliance blockchain organization system is provided in the embodiment of the application, and the alliance blockchain organization system comprises a first accounting node, a first backup node set, a private gateway node and a public gateway node; the first accounting node is connected with a first backup node set network, and the first accounting node is commonly recognized with other alliance blockchain organization systems except the alliance blockchain organization system and stores an account book; the first set of backup nodes is for synchronizing the ledger from the first accounting node; the private gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring a service request of the first client and acquiring data of an account book from the first accounting node and the first backup node set based on the first authority; the public gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring a service request of a first client and acquiring data of an account book from the first accounting node and the first backup node set based on the second authority, wherein the number of allowed service types in the first authority is smaller than that of allowed service types in the second authority, and the first client is a client outside the alliance blockchain organization system.
Referring to fig. 1 and 2, fig. 1 is a schematic structural diagram of one embodiment of a federated blockchain organization system provided in embodiments of the present application; FIG. 2 is a schematic diagram of a first backup node set in an embodiment of a federated blockchain organization system provided in embodiments of the present application.
Referring to fig. 1 and 2, in an embodiment of the present application, a federated blockchain organization system 10 includes a first accounting node 12, a first backup node set 11, a private gateway node 14, and a public gateway node 13. The number of nodes in the first set of backup nodes 11 may be one, two or more. The first accounting node 12, the nodes in the first backup node set 11, the private gateway node 14, and the public gateway node 13 may be mobile phones, computers, or other devices capable of connecting to the internet, such as servers. The federated blockchain organization system 10 may correspond to an enterprise or organization, for example, the federated blockchain organization system 10 corresponds to enterprise a.
The node may be a general purpose computer device or a special purpose computer device. In a specific implementation, the node may be a desktop, a portable computer, a network server, a palm computer (Personal Digital Assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, etc., and the embodiment is not limited to the type of the node.
The first accounting node 12 is connected to the first backup node set 11 through a network, and the first accounting node 12 performs consensus with other federated blockchain organization systems other than the federated blockchain organization system 10 and stores an account book. Other federated blockchain organization systems correspond to other enterprises, such as other enterprises associated with enterprise A. The ledger may be a distributed ledger, which is a database that is shared, replicated, and synchronized among the network members. The distributed ledger records transactions, such as exchanges of assets or data, between network participants. Participants in the network restrict and negotiate updates to records in the ledger in accordance with consensus principles. Each record in the distributed ledger has a timestamp and unique cryptographic signature, which makes the ledger an auditable history of all transactions in the network. The ledger is permanently recorded in the node in the form of a file, the file forms blocks, each block stores transaction records generated within a period of time, all the blocks form a linked list, each block contains the hash value of the block, the block generation timestamp, the hash value of the previous block and a transaction set, and the transaction set is a transaction set formed by a group of transactions arranged in time sequence, so that the whole blockchain continuously grows and the data is irreversible.
The first accounting node 12 is configured to agree with other federated blockchain organization systems, and the agreed mechanism may be a POW (Proof of Work) mechanism, a POS (Proof of equity) mechanism, or the like. When a new block is generated, the first accounting node 12 performs consensus with accounting nodes in other alliance blockchain organization systems, and after consensus is achieved, the new block is added to the account book, so that each accounting node has the same account book. Wherein the first accounting node 12 may be designated or may be generated by a node vote in the federated blockchain organization system 10.
The data synchronization means that the palm computer can rapidly realize data synchronization and information sharing with the desktop computer and the notebook computer, so that the data can keep integrity and uniformity. The first set of backup nodes 11 is used to synchronize the ledger from the first accounting node 12. The first backup node set 11 and the first accounting node 12 have the same account book, when a service request is acquired, the first backup node set 11 can share a reading function with the first accounting node 12, so that the first accounting node 12 can use more computing power for consensus and writing in a new block, namely, the first accounting node 12 in the alliance blockchain organization system 10 is used for writing in data, the first backup node set 11 in the alliance blockchain organization system 10 is used for reading data, the reading and writing separation of the alliance blockchain organization system 10 is realized, and the efficiency of the alliance blockchain organization system 10 is improved.
The private gateway node 14 is connected to the first accounting node 12 and the first backup node set 11, respectively, and the private gateway node 14 is configured to obtain a service request of the first client 50, and obtain data of an account book from the first accounting node 12 and the first backup node set 11 based on the first authority. The common gateway node 13 is connected to the first accounting node 12 and the first set of backup nodes 11, respectively. The public gateway node 13 is configured to obtain a service request of the first client 50, and obtain data of an account book from the first accounting node 12 and the first backup node set 11 based on the second authority. The first right is a right for allowing a service request of a first specified service type, for example, the first specified service type includes a financial service type. The second authority is an authority for allowing a service request of a second specified service type, for example, a traceable service type of the second specified service type, a personal service type, etc., and may be set according to the specific situation. And when the service type of the service request of the first client belongs to the allowed service type in the authority, the gateway node acquires the data of the account book from the first accounting node 12 and the first backup node set 11 according to the service request. And the gateway node refuses the service request when the service type of the service request of the first client belongs to the allowed service type in the authority. Wherein the number of allowed service types in the first authority is smaller than the number of allowed service types in the second authority, i.e. the number of services of the first designated service type is smaller than the number of services of the second designated service type, and the first client 50 is a client external to the federated blockchain organization system 10.
The first client 50 is a client external to the federated blockchain organization 10. For example, the first client 50 corresponds to an enterprise or person having business to and from enterprise A. The number of allowed service types in the first right is smaller than the number of allowed service types in the second right. And compared with the public gateway node, each service request accessing the private gateway node can be responded more quickly, the service accessing the account book can be obtained more quickly, the service in the first authority range can be processed preferentially, and the service availability of the alliance blockchain organization system 10 is improved.
The first authority and the second authority can be set according to specific situations. For example, the common gateway node 13 supports generic services such as a traceability service and a customer premise access service. The private gateway node 14 supports services requiring high service requirements, e.g., the private gateway node 14 supports only financial service B, and does not open other services, ensuring high availability of services for the federated blockchain organization system 10.
In this embodiment, the federated blockchain organization system 10 includes a second client 16, where the second client 16 may connect with any one of the first accounting node 12 and the first backup node set 11 to obtain data in the ledger. The second client 16 may directly access any one of the first accounting node 12 and the first backup node set 11, and directly obtain data of the ledger from any one of the first accounting node 12 and the first backup node set 11. Likewise, the second client 16 may be a mobile phone, a computer, or a server. The second client 16 is a client within the federated blockchain organization 10, and the second client 16 may directly access any one of the first accounting node 12 and the first backup node set 11. For example, the second client 16 is a respective department or individual within the enterprise. Specifically, the access authority of the second client 16 may be set, so that the second client 16 may directly access any node in the first accounting node 12 and the first backup node set 11.
In this embodiment, the federated blockchain organization system 10 further includes a tracing server 15, where the tracing server 15 is connected to the public gateway node 13. Tracing, tracing the source, searching the root and source of things. The earliest is the food safety management system established and perfected by European Union in 1997 for coping with the problem of mad cow disease. The set of food safety management system is pushed by government, covers the upstream and downstream of the whole food industry chain of food production bases, food processing enterprises, food terminal sales and the like, and is used for sharing information through special hardware equipment similar to a bank cash dispenser system to serve final consumers. Once the quality of the food is problematic at the consumer end, the online inquiry can be carried out through the traceability code on the food label, all circulation information of the food production enterprises, the food production places, specific farmers and the like can be detected, and the corresponding legal responsibility of the accident party is clarified. The system has quite important significance for food safety and self-restraint in the food industry. The technology is widely applied at present, and the shadow of the tracing technology can be seen in various industries such as medicines, clothes, electronics, fishing boats and the like besides foods.
In a specific embodiment, the number of the first accounting nodes 12 is two, the number of the first backup node sets 11 is two, the two first accounting nodes 12 are respectively connected with the two first backup node sets 11, and the two first accounting nodes 12 are used for participating in the consensus with other alliance blockchain organization systems at the same time, and writing new blocks after the consensus into the respectively connected first backup node sets 11. The two first accounting nodes 12 can be backed up mutually, and when one first accounting node 12 fails, the other first accounting node 12 continues to perform consensus so as to ensure the normal operation of the alliance blockchain organization system 10. In addition, the two first accounting nodes 12 and the two first backup node sets 11 mutually backup account book data, and when one node fails, the access function of the client to the account book can be ensured. In other embodiments, the federated blockchain organization system 10 may include 3 or more first accounting nodes 12, 3 or more first backup node sets 11.3 or more first accounting nodes 12 are each connected to one first set of backup nodes 11, providing further backups.
In the embodiment of the application, the primary backup node is used for monitoring the accounting node so as to synchronize the account book from the accounting node; the secondary backup node is used for monitoring the primary backup node so as to acquire the account book from the primary backup node. The primary backup node is different from the secondary backup node in that the monitored objects are different and the sources of the acquired account book are different. The account book is acquired hierarchically, so that the situation that the account book is acquired from the accounting node by a plurality of backup nodes at the same time, and the load of the accounting node is overlarge can be avoided.
In this embodiment, the first backup node set 11 includes at least two first primary backup nodes 111 and at least two first secondary backup nodes 112, the at least two first primary backup nodes 111 are connected with the first accounting node 12, the at least two first primary backup nodes 111 are used for synchronizing accounts from the first accounting node 12 connected therewith, the first primary backup nodes 111 are connected with the at least one first secondary backup node 112, and the at least two first secondary backup nodes 112 are used for synchronizing accounts from the first primary backup nodes 111 connected therewith. The plurality of first primary backup nodes 111 monitor the first accounting nodes 12 connected with the first primary backup nodes respectively, and when a new block is written in the accounting book of the first accounting node 12 is detected, the accounting book stored on the first accounting node 12 is synchronized; the plurality of first secondary backup nodes 112 monitor the first primary backup nodes 111 connected thereto, respectively, and synchronize the ledgers of the first primary backup nodes 111 when it is detected that new blocks are written in the ledgers of the first primary backup nodes 111. The nodes in the first set of backup nodes 11 and the first accounting node 12 are in a tree hierarchy. The nodes in the first backup node set 11 are divided into two stages, so that the pressure of the first accounting node 12 can be relieved, the first primary backup node 111 can only synchronize data from the first accounting node 12, and the first secondary backup node 112 can only synchronize data from the first primary backup node 111, thereby being convenient for data synchronization and management and control. In other embodiments, the first backup node set 11 may be further divided into 3, 4 or more levels, and when the first backup node set 11 includes backup nodes of 3, 4 or more levels, a node of an uppermost level is connected to the first accounting node 12, and nodes of an upper level are respectively connected to nodes of at least one next level, and nodes of the next level synchronize accounting data from nodes of the upper level connected thereto.
In a particular embodiment, at least two first primary backup nodes 111 are interconnected such that at least two first primary backup nodes 111 may synchronize the ledgers with each other. The backup nodes of the first level are mutually communicated to form a mesh structure, when one of the first primary backup nodes 111 of the same level is disconnected from the first accounting node 12, the accounting book can be acquired through the other first primary backup nodes of the same level and transferred to the backup node of the next level, so that the robustness of the alliance blockchain organization system 10 can be enhanced. In other embodiments, backup nodes of the same level may be interconnected to backup each other.
Compared with the prior art, the application provides the alliance blockchain organization system, the alliance blockchain organization system establishes the connection between the external client side of the alliance blockchain organization system and the alliance blockchain organization system through the private gateway node and the public gateway node, and the service request with higher service requirements can be accessed into the alliance blockchain organization system through the private gateway node by setting different authorities to the private gateway node and the public gateway, so that the availability of the alliance blockchain organization system is improved, and meanwhile, the account book of the first accounting node is backed up through the first backup node set, so that the load pressure of the first accounting node can be reduced, and the alliance blockchain organization system is balanced.
Further, referring to fig. 3 and 4, fig. 3 is a schematic structural diagram of an embodiment of a blockchain system provided in an embodiment of the present application; fig. 4 is a schematic structural diagram of a second backup node set in an embodiment of a blockchain system provided in an embodiment of the present application.
The present application also provides a blockchain system including the federated blockchain organization 10 of any of the above embodiments.
In this embodiment, the blockchain system 100 includes at least two first federated blockchain organization systems 30, the first federated blockchain organization system 30 being the federated blockchain organization system 10 of any of the above embodiments.
In this embodiment, at least two first federation blockchain organization systems 30 are commonly identified by the first accounting node 12 and store an accounting book. The first federated blockchain organization system 30 may pre-designate the first accounting node 12, or nodes inside the first federated blockchain organization system 30 elect the first accounting node 12 by voting, and the first accounting node 12 replaces the entire first federated blockchain organization system 30 to participate in the consensus of the entire blockchain system 100, so as to improve the consensus efficiency.
In this embodiment, the blockchain system 100 further includes a second federation blockchain organization system 20, where the second federation blockchain organization system 20 is configured to supervise at least two first federation blockchain organization systems 30, and the second federation blockchain organization system 20 includes a second backup node set 21, and the second backup node set 21 is configured to synchronize accounts from the first accounting nodes 12 of the first federation blockchain organization systems 30. For example, the plurality of first alliance blockchain organization systems 30 correspond to enterprises that go to and from various businesses, and the second alliance blockchain organization system 20 corresponds to a regulatory agency such as a government agency. The second federation blockchain organization system 20 only performs supervision, so that the client can obtain ledger data from the backup node of the second federation blockchain organization system 20 without participating in consensus, without setting a billing node, and only deploying the backup node. The second federation blockchain organization system 20 does not have accounting nodes, and can reduce the number of accounting nodes of the entire blockchain system 100, thereby improving the consensus efficiency of the entire blockchain system 100 and reducing the load of the entire blockchain system 100.
In this embodiment, the second backup node set 21 includes at least two second-level backup nodes 211 and at least two second-level backup nodes 212, where the at least two second-level backup nodes 212 are used to synchronize the ledgers from the first accounting node 12 of the first federation blockchain organization system 30, the second-level backup nodes 212 are connected with the at least one second-level backup node 212, and the at least two second-level backup nodes 212 synchronize the ledgers from the second-level backup nodes 211 connected therewith.
It should be noted that, the second federation blockchain organization system 20 may be the same as the first federation blockchain organization system 30, where the second federation blockchain organization system 20 includes a public gateway node and a private gateway node, and authority control is performed on access of clients outside the second federation blockchain organization system 20 through the public gateway node and the private gateway node, so as to improve service high availability of the second federation blockchain organization system 20.
The foregoing has described in detail a federated blockchain organization system, a blockchain system, and a method for providing a block chain organization system, wherein specific examples are employed to illustrate the principles and implementations of the present application, and the description of the foregoing examples is only for aiding in the understanding of the methods of the present application and the core ideas thereof; meanwhile, those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, and the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. A alliance block chain organization system is characterized in that,
the alliance blockchain organization system comprises a first accounting node, a first backup node set, a private gateway node and a public gateway node;
the first accounting node is connected with the first backup node set in a network manner, and the first accounting node is commonly recognized with other alliance blockchain organization systems except the alliance blockchain organization system and stores an account book;
the first set of backup nodes is for synchronizing the ledger from the first accounting node;
the private gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring a service request of a first client and acquiring data of the account book from the first accounting node and the first backup node set based on a first authority;
the public gateway node is respectively connected with the first accounting node and the first backup node set, and is used for acquiring the service request of the first client and acquiring the data of the account book from the first accounting node and the first backup node set based on the second authority,
the number of allowed service types in the first authority is smaller than that of allowed service types in the second authority, and the first client is a client outside the alliance blockchain organization system.
2. The federated blockchain organization system of claim 1 wherein the number of first accounting nodes is at least two, the number of first backup node sets is at least two, at least two of the first accounting nodes are respectively connected with at least two of the first backup node sets, at least two of the first accounting nodes are configured to participate in consensus with other federated blockchain organization systems at the same time, and write new blocks after consensus to the respectively connected first backup node sets.
3. The federated blockchain organization system of claim 1 or 2, wherein the first set of backup nodes includes at least two first primary backup nodes and at least two first secondary backup nodes, the at least two first primary backup nodes being connected to the first accounting node, the at least two first primary backup nodes being for synchronizing the accounting from the first accounting node to which they are connected, the first primary backup nodes being connected to at least one of the first secondary backup nodes, the at least two first secondary backup nodes being for synchronizing the accounting from the first primary backup node to which they are connected.
4. The federated blockchain organization of claim 3, wherein the at least two first primary backup nodes are interconnected such that the at least two first primary backup nodes can synchronize the ledgers with each other.
5. The federated blockchain organization system of claim 3, comprising a second client connectable to any one of the first billing node and the first backup node set to obtain data in the ledger.
6. The federated blockchain organization system of claim 1, further comprising a traceability server, the traceability server being connected to the common gateway node.
7. A blockchain system, characterized in that the blockchain system comprises the federated blockchain organization system of any of claims 1-6.
8. The blockchain system of claim 7, wherein the blockchain system includes at least two first federated blockchain organization systems, the first federated blockchain organization system being the federated blockchain organization system of any of claims 1-6, the at least two first federated blockchain organization systems being commonly identified by a first accounting node and storing an accounting book.
9. The blockchain system of claim 8, further comprising a second federation blockchain organization system for policing the at least two first federation blockchain organization systems, the second federation blockchain organization system including a second set of backup nodes for synchronizing the ledger from the first billing node of the first federation blockchain organization system.
10. The blockchain system of claim 9, wherein the second set of backup nodes includes at least two second primary backup nodes for synchronizing the ledger from the first billing node of the first federated blockchain organization system and at least two second secondary backup nodes connected to at least one of the second secondary backup nodes that synchronize the ledger from the second primary backup node connected thereto.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010433356.XA CN113709197B (en) | 2020-05-21 | 2020-05-21 | Alliance block chain organization system and block chain system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010433356.XA CN113709197B (en) | 2020-05-21 | 2020-05-21 | Alliance block chain organization system and block chain system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113709197A CN113709197A (en) | 2021-11-26 |
| CN113709197B true CN113709197B (en) | 2024-02-23 |
Family
ID=78645421
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010433356.XA Active CN113709197B (en) | 2020-05-21 | 2020-05-21 | Alliance block chain organization system and block chain system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113709197B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107147735A (en) * | 2017-05-12 | 2017-09-08 | 北京博晨技术有限公司 | A kind of distributed account book system based on hierarchy |
| CN108492103A (en) * | 2018-02-07 | 2018-09-04 | 北京大学深圳研究生院 | A kind of alliance's block chain common recognition method |
| CN108874918A (en) * | 2018-05-30 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of data processing equipment, database all-in-one machine and its data processing method |
| CN109615510A (en) * | 2018-12-04 | 2019-04-12 | 国网辽宁省电力有限公司大连供电公司 | A kind of supply chain finance based on block chain is multistage to increase letter method |
| CN109831545A (en) * | 2019-01-31 | 2019-05-31 | 中国互联网络信息中心 | A kind of domain name abuse processing method and system based on block chain |
| CN110246005A (en) * | 2019-05-23 | 2019-09-17 | 阿里巴巴集团控股有限公司 | Rent method and device based on block chain |
| CN110363413A (en) * | 2019-06-28 | 2019-10-22 | 深圳市元征科技股份有限公司 | A kind of method and relevant apparatus of voluntary service management |
| CN110417883A (en) * | 2019-07-23 | 2019-11-05 | 杭州云象网络技术有限公司 | A kind of design method of the point to point network structure applied to block chain |
| CN110727737A (en) * | 2019-10-29 | 2020-01-24 | 南京邮电大学 | Intelligent medical data storage method based on multi-level block chain system architecture |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107506258B (en) * | 2016-06-14 | 2021-11-12 | 伊姆西Ip控股有限责任公司 | Method and apparatus for data backup |
| CN107819749A (en) * | 2017-10-26 | 2018-03-20 | 平安科技（深圳）有限公司 | Block catenary system and transaction data processing method based on ether mill |
| CN109299336B (en) * | 2018-09-30 | 2022-07-01 | 腾讯科技（深圳）有限公司 | Data backup method and device, storage medium and computing equipment |
-
2020
- 2020-05-21 CN CN202010433356.XA patent/CN113709197B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107147735A (en) * | 2017-05-12 | 2017-09-08 | 北京博晨技术有限公司 | A kind of distributed account book system based on hierarchy |
| CN108492103A (en) * | 2018-02-07 | 2018-09-04 | 北京大学深圳研究生院 | A kind of alliance's block chain common recognition method |
| CN108874918A (en) * | 2018-05-30 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of data processing equipment, database all-in-one machine and its data processing method |
| CN109615510A (en) * | 2018-12-04 | 2019-04-12 | 国网辽宁省电力有限公司大连供电公司 | A kind of supply chain finance based on block chain is multistage to increase letter method |
| CN109831545A (en) * | 2019-01-31 | 2019-05-31 | 中国互联网络信息中心 | A kind of domain name abuse processing method and system based on block chain |
| CN110246005A (en) * | 2019-05-23 | 2019-09-17 | 阿里巴巴集团控股有限公司 | Rent method and device based on block chain |
| CN110363413A (en) * | 2019-06-28 | 2019-10-22 | 深圳市元征科技股份有限公司 | A kind of method and relevant apparatus of voluntary service management |
| CN110417883A (en) * | 2019-07-23 | 2019-11-05 | 杭州云象网络技术有限公司 | A kind of design method of the point to point network structure applied to block chain |
| CN110727737A (en) * | 2019-10-29 | 2020-01-24 | 南京邮电大学 | Intelligent medical data storage method based on multi-level block chain system architecture |
Non-Patent Citations (2)
| Title |
|---|
| 区块链共识机制研究与分析;刘童桐;;信息通信技术与政策(第07期);全文 * |
| 张大勇.基于区块链政务信息资源共享系统的设计.《电脑知识与技术》.2018,(2018,14(28)),153-160. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113709197A (en) | 2021-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11669811B2 (en) | Blockchain-based digital token utilization | |
| TWI724391B (en) | Node management method and device based on blockchain | |
| EP3635607B1 (en) | Computer-implemented system and method for managing transactions over a blockchain network | |
| Bada et al. | Towards a green blockchain: A review of consensus mechanisms and their energy consumption | |
| WO2021004058A1 (en) | Blockchain-based data processing method and device | |
| CN109063169A (en) | A kind of customer data management system based on block chain | |
| WO2020147568A1 (en) | Block chain-based evidence storage method and device | |
| Selimi et al. | Towards blockchain-enabled wireless mesh networks | |
| WO2020134631A1 (en) | Block chain-based data processing method and apparatus | |
| Kadam | Review of distributed ledgers: The technological advances behind cryptocurrency | |
| CN113568946A (en) | Method, system and apparatus for managing transactions in multiple blockchain networks | |
| CN112287033B (en) | Data synchronization method, equipment and computer readable storage medium | |
| WO2021220062A1 (en) | Blockchain transaction | |
| CN113595734A (en) | Method, system and apparatus for managing transactions in multiple blockchain networks | |
| CN112053271B (en) | Public service platform data evidence management method and system based on block chain | |
| Kumar et al. | Front-End IoT application for the bitcoin based on proof of elapsed time (PoET) | |
| KR102181098B1 (en) | System and method for distributed database using block chain | |
| KR102376783B1 (en) | The blockchain-based transaction history confirmation system | |
| CN113709197B (en) | Alliance block chain organization system and block chain system | |
| Wang | Research on development method of application system based on blockchain | |
| Bu et al. | Cross hyperledger fabric transactions | |
| Kazmi et al. | Is blockchain overrated? | |
| KR102332814B1 (en) | The block chain system including a block chain structure for data self-sovereign identity | |
| Wadhwa | Lightweight modified consensus approach in IoT blockchain | |
| US20240187399A1 (en) | Customized Token Rules Generation System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |