CN115776501A - Block chain system architecture, management method, electronic equipment and readable storage medium - Google Patents

Abstract

The application is applicable to the technical field of block chains, and provides a block chain system architecture, a management method, an electronic device and a readable storage medium, wherein the system architecture comprises the following components: the system comprises a block chain management system, a data management system, a main chain group and a sub chain group; the block chain management system is used for managing the creation and deployment of the main chain group and the sub chain group; the data management system is used for acquiring the block data of the sub-chain group, analyzing the block data and feeding back an analysis result to the block management system; the main chain group is used for accessing the sub chain group and synchronizing the transaction information of the sub chain group; the sub-chain group is used for processing the transaction information and providing the block data to the data management system. Through the embodiment of the application, the construction of large block chain infrastructures can be supported, the data analysis difficulty is reduced, the performance of the block chain overall architecture is improved, the flexibility of the block chain construction is higher, and the overall chain group of the block chain can be comprehensively supervised.

Description

Block chain system architecture, management method, electronic equipment and readable storage medium

Technical Field

The present application relates to a blockchain system architecture, a management method, an electronic device and a readable storage medium.

Background

The block chain is used as an infrastructure, and may be divided into a small private chain, a medium multi-mechanism alliance chain, a large public chain architecture, and the like according to the application range of the block chain, where the public chain architecture is not suitable for expansion and management of the block chain architecture in a higher-order application scenario.

At present, the blockchain architecture mainly comprises a single-chain architecture or a master-slave chain architecture, and because the blockchain of the single-chain architecture is limited by the performance of the blockchain, the data analysis difficulty in the master-slave chain architecture is high, so that the blockchain infrastructure construction of a large application scene cannot be supported.

Disclosure of Invention

The present application aims to provide a blockchain system architecture, a management method, an electronic device, and a readable storage medium, which can solve the problem that a blockchain of a single-chain architecture is limited by the performance of the blockchain, and data analysis difficulty in a master-slave chain architecture is high, so that building of a blockchain infrastructure of a large application scenario cannot be supported.

In a first aspect, an embodiment of the present application provides a block chain system architecture, where the system architecture includes: block chain management system, data management system, main chain group and sub chain group:

the block chain management system is used for managing the creation and deployment of the main chain group and the sub-chain group;

the data management system is used for acquiring the block data of the sub-chain group, analyzing the block data and feeding back an analysis result to the block management system;

the main chain group is used for accessing the sub chain group and synchronizing the transaction information of the sub chain group;

the sub-chain group is used for processing the transaction information and providing the block data to the data management system.

In one possible implementation manner of the first aspect, the blockchain management system includes a main chain management unit;

the main chain management unit is used for managing a creation period, a built-in contract and a naming space of the main chain in the main chain group;

the main chain management unit is further used for analyzing the analysis result fed back by the data management system and displaying the topological structure of the sub chain and the transaction information;

the main chain group is used for dividing partitions corresponding to the name space in the main chain, and the partitions correspond to the transaction information of the sub chains in the sub chain group;

the main chain group is further used for deploying the built-in contracts corresponding to the partitions according to the namespaces, and the built-in contracts comprise registration management contracts of the sub-chains and service synchronization contracts of the sub-chains;

the main chain management unit is further configured to perform visual management on the main chain group based on the creation information and the deployment information of the main chain group.

In a possible implementation manner of the first aspect, the system architecture further includes a front gateway, and the blockchain management system further includes a sub-chain management unit;

the sub-chain management unit is further used for sending a registered sub-chain transaction to the main chain group through the front gateway;

the preposed gateway is used for forwarding the registered sub-chain transaction to the main chain group and forwarding the transaction result to the sub-chain management unit after receiving the transaction result fed back by the main chain group;

the sub-chain management unit is further configured to receive the transaction result forwarded by the front gateway, where the transaction result is used to indicate that the sub-chain registration is successful.

In a possible implementation manner of the first aspect, the sub-chain management unit is further configured to obtain a contract address of the built-in contract, a gateway address of the pre-gateway, a space name of the namespace, and an access password joining the main chain group;

the sub-chain management unit is further configured to send the registered sub-chain transaction to the contract address corresponding to the space name in the main chain group based on the gateway address and the access password.

In a possible implementation manner of the first aspect, the data management system is further configured to obtain and analyze the chunk data corresponding to the transaction information in the sub-link group based on the transaction information of the sub-link group, perform structural processing on the analyzed chunk data, and feed back the analysis result after the structural processing to the chunk chain management system;

the main chain management unit is further used for performing visual management on the sub-chain group based on the analysis result after the structural processing.

In a second aspect, an embodiment of the present application provides a method for managing a blockchain, where the method is applied to a blockchain system architecture, and the method includes:

the sub-chain group accesses the main chain group and synchronizes transaction information to the main chain group; providing block data corresponding to the transaction information to a data management system;

the main chain group receives the access of the sub chain group and acquires the transaction information synchronized by the sub chain group;

the data management system acquires the block data of the sub-chain group, analyzes the block data and feeds back an analysis result to the block chain management system;

the block chain management system respectively deploys and manages the main chain group and the sub chain group based on the creation information of the main chain and the sub chain, and visually manages the sub chain group based on the received analysis result.

In a third aspect, an embodiment of the present application provides a method for managing a blockchain, where the method is applied to a blockchain management system, and the method includes:

creating and deploying a main chain group and a sub chain group;

receiving an analysis result fed back by a data management system, wherein the analysis result is obtained by analyzing block data sent by the sub-chain group by the data management system, and the block data is data corresponding to the transaction information of the sub-chain group;

and visually managing the sub-chain groups based on the analysis result.

In a fourth aspect, an embodiment of the present application provides a block chain management method, which is applied to a data management system, and the method includes:

acquiring block data of a sub-chain group, wherein the block data is data corresponding to transaction information of the sub-chain group;

analyzing the block data to obtain an analysis result;

and sending the analysis result to a blockchain management system, wherein the analysis result is used for indicating the blockchain management system to visually manage the sub-chain group.

In a fifth aspect, an embodiment of the present application provides a block chain management apparatus, including:

the transmission unit is used for enabling the sub-chain group to access the main chain group and synchronizing transaction information to the main chain group; providing block data corresponding to the transaction information to a data management system;

the synchronization unit is used for receiving the access of the sub-chain group by the main chain group and acquiring the transaction information synchronized by the sub-chain group;

the processing unit is used for the data management system to obtain the block data of the sub-chain group, analyze the block data and feed back an analysis result to the block chain management system;

and the management unit is used for the block chain management system to respectively carry out deployment management on the main chain group and the sub-chain group based on the creation information of the main chain and the sub-chain, and carry out visual management on the sub-chain group based on the received analysis result.

In a sixth aspect, an embodiment of the present application provides a block chain management apparatus, where the apparatus includes:

the creating and deploying unit is used for creating and deploying the main chain group and the sub chain group;

the receiving unit is used for receiving an analysis result fed back by the data management system, wherein the analysis result is obtained by analyzing block data sent by the sub-chain group by the data management system, and the block data is data corresponding to the transaction information of the sub-chain group;

and the visualized management unit is used for performing visualized management on the sub-chain group based on the analysis result.

In a seventh aspect, an embodiment of the present application provides a block chain management device, which is applied to a data management system, and includes:

the acquisition unit is used for acquiring block data of the sub-chain group, wherein the block data is data corresponding to the transaction information of the sub-chain group;

the analysis unit is used for analyzing the block data to obtain an analysis result;

and the transmission unit is used for sending the analysis result to a blockchain management system, and the analysis result is used for indicating the blockchain management system to visually manage the sub-chain groups.

In an eighth aspect, an embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the method of the third aspect or the fourth aspect is implemented.

In a ninth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, and the computer program implements the method of the third aspect or the fourth aspect when executed by a processor.

In a tenth aspect, embodiments of the present application provide a computer program product, which, when run on an electronic device, causes the electronic device to perform the method of any one of the third or fourth aspects.

It is to be understood that, the beneficial effects of the second to tenth aspects can be referred to the relevant description of the first aspect, and are not described herein again.

Compared with the prior art, the application has the beneficial effects that: the block chain system architecture comprises a block chain management system, a data management system, a main chain group and a sub chain group, wherein the block chain system architecture is provided by the embodiment of the application; the block chain management system is used for managing the creation and deployment of the main chain group and the sub chain group; the data management system is used for acquiring the block data of the sub-chain group, analyzing the block data and feeding back an analysis result to the block management system; the main chain group is used for creating a main chain, accessing the sub chain group and synchronizing the transaction information of the sub chain group; the sub-chain group is used for creating a sub-chain, processing the transaction information and providing the block data to the data management system; the method has the advantages that the construction of large blockchain infrastructures can be supported, the data analysis difficulty is reduced, the performance of the blockchain overall architecture is improved, the flexibility of blockchain construction is high, and the overall chain group of blockchains can be comprehensively supervised; has strong usability and practicability.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a schematic diagram of a block chain system architecture according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a namespace provided by an embodiment of the application;

fig. 3 is a schematic flow chart of a BDMS listening block according to an embodiment of the present application;

FIG. 4 is an external flow diagram illustrating module interactions of the system architecture provided by embodiments of the present application;

FIG. 5 is a schematic diagram of an internal flow of system interaction provided by an embodiment of the present application;

fig. 6 is a flowchart illustrating a block chain management method according to an embodiment of the present application;

fig. 7 is a flowchart illustrating a block chain management method according to an embodiment of the present application;

fig. 8 is a flowchart illustrating a block chain management method according to an embodiment of the present application;

fig. 9 is a schematic diagram of a blockchain management apparatus according to an embodiment of the present application;

fig. 10 is a schematic diagram of a blockchain management apparatus according to an embodiment of the present application;

fig. 11 is a schematic diagram of a blockchain management apparatus according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items and includes such combinations.

As used in the specification of this application and the appended claims, the term "if" may be interpreted contextually as "when 8230that is," or "once" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted depending on the context to mean "upon determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Furthermore, in the description of the present specification and claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for indicating or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather mean "one or more, but not all embodiments" unless otherwise expressly specified. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

The block chain is an infrastructure, and can be divided into a small private chain, a medium multi-organization alliance chain, a large public chain architecture, etc. according to the application range, where the public chain architecture is not suitable for city-level, provincial-level, or even national-level block chain construction, for example, a city chain, i.e. a city-level block chain infrastructure, is generally constructed by provinces, autonomous regions, direct cities, or prefectures, and provides a unified block chain service for multiple levels of administrative units in administrative divisions. In order to meet the general trend and requirements of the intensive construction, a novel infrastructure needs to be provided, in an application level, a main chain can be built by a government supervision department, a sub-chain structure, supervision, sub-chain business data and the like on the main chain are maintained, and the basic services of digital identity management, chain crossing and the like are guaranteed. A service sub-chain constructed by a specific industry needs to be registered on a main chain, and specific applications such as supply tracing, digital commodity transaction and the like in the industry are provided.

The current block chain architecture mainly has the following disadvantages: first, large blockchain traffic cannot be supported: the traditional single chain architecture is limited by the performance of the blockchain itself and cannot support the actual city-level construction of such large blockchain infrastructure. Secondly, the data analysis difficulty is high, and the redundancy is excessive to cause performance reduction: the current multi-chain model is mainly a master-slave architecture, wherein a main chain is responsible for data verification and storage, and a slave chain is responsible for specific business operation. Each slave chain belongs to different namespaces and corresponds to a set of business account book. At present, the main chain can store 'master-slave' structure information and also comprises all service data of slave chains, and the slave chains can store all the service data, so that the current 'master-slave' architecture has complex data redundancy, can not be subdivided according to services, has extremely high data complexity and increases greatly the analysis difficulty; with the increase of the number of the slave chains, the consensus ability of the main chain is reduced, so that the business progress of the slave chains is influenced by the performance of the main chain, and finally the performance of the whole chain group is reduced. Third, heterogeneous chain access is not supported: the current "master-slave" architecture can only support the slave chain to adopt different consensus mechanisms, but cannot support the slave chain to adopt other block chain bottom layers, for example, taking hyperchain as an example, the slave chain can support solo or rbft and other consensus of hyperchain, but does not support the slave chain to adopt fabric or bcos and other block chain technologies. Fourth, the flexibility is not sufficient: the existing slave chain is not supported to be dynamically expanded by the current master-slave architecture, if the existing running service chain is expected to become the slave chain, the slave chain cannot be accessed to the main chain, the slave chain must be built from zero, and the flexibility is insufficient. Fifth, no supervision is available: the main chain cannot acquire key actions such as registration, node addition and deletion, logout and the like of the slave chain and information such as the number and structural change of the slave chain, and the main chain cannot control and sense the overall appearance of the whole chain group. Meanwhile, in an actual scene, the main chain needs to monitor the transaction of the sub-chain, so that illegal transactions are avoided. The main chain in the current 'master-slave' architecture can only check the authenticity of data and cannot monitor sensitive words existing in transaction contents.

In view of the foregoing drawbacks, the present application provides a blockchain system architecture including a blockchain management system, a data management system, a main chain group and a sub-chain group; the block chain management system is used for managing the creation and deployment of the main chain group and the sub chain group; the data management system is used for acquiring the block data of the sub-chain group, analyzing the block data and feeding back an analysis result to the block management system; the main chain group is used for creating a main chain, accessing the sub-chain group and synchronizing the transaction information of the sub-chain group; and the sub-chain group is used for creating a sub-chain, processing the transaction information and providing block data to the data management system. Unified identity identification, sub-chain registration and different service management are provided through a built-in contract of a main chain, and further basic capabilities of main chain supervision and inter-chain intercommunication of the sub-chains are achieved. Has the following advantages: firstly, the construction of large block chain infrastructure similar to city level can be supported, the main chain supervises the whole appearance and the sub chain operation service, and the upper limit of the single chain performance under the city level scene is broken through. Secondly, the service is clear: the sub-chains report the service data according to the service logic respectively according to the name space of the main chain, so that the main chain is prevented from being bundled and storing the data, and the splitting and isolation of the service logic and the physical account book are realized. The block data can be analyzed through the data management system BDMS, so that business data can be visually displayed on the BaaS. Thirdly, flexible access of heterogeneous chains: different heterogeneous chains can be registered to the main chain through a built-in sub-chain registration management contract and a front gateway, and the main chain analyzes data in transactions through a BDMS (browser/server management system) to obtain specific information of the sub-chains, so that management is performed. Even if the sub-chain is in operation, the main chain can be accessed without interruption, and the operation of the service of the sub-chain is not influenced. Fourthly, overall supervision of the main chain: the actions of registering, adding and deleting nodes, canceling and the like of the sub-chains are packaged into a transaction and reported to the main chain, and the main chain can sense the overall appearance of the whole chain group through analyzing the transaction. Meanwhile, whether sensitive transactions exist in the sub-chain or not can be known through monitoring the transactions. Fifth, the architecture is flexible: the method comprises the steps that a main chain is separately deployed, the sub-chains are added to or withdrawn from a main chain system as required, the sub-chains in operation can be added to the main chain system at any time, and if the sub-chain service is supposed to be separated from the main chain system to operate independently, the sub-chain cancellation request is sent only under the condition that the sub-chains operate without stopping, and the existing operation service of the sub-chains is not influenced; the addition of the backbone is also the same as described above. The block chain system architecture has strong usability and practicability.

The following describes the configuration of the blockchain system architecture and the interaction mode among the system modules by using specific embodiments.

Referring to fig. 1, fig. 1 is a schematic diagram illustrating an embodiment of a block chain system architecture 100 according to the present application. As shown in fig. 1, the system architecture 100 includes: a blockchain management system 110, a data management system 120, a main chain group 130, and a sub-chain group 140.

The blockchain management system 110 is configured to manage creation and deployment of the main chain group 130 and the sub-chain group 140.

In some embodiments, the blockchain management system 110 is called BaaS (blockchain as a Service platform), and supports management of creation and deployment of the main chain group 130 and the sub-chain group 140. A main chain group 130 may include a plurality of main chains, a sub chain group 140 may include a plurality of sub chains, the number of the main chains and the number of the sub chains may be N and M, respectively, and N and M are positive integers, respectively. One sub-chain group 140 may be connected to one main chain of one main chain group 130, and the main chain and the sub-chains may be homogeneous chains or heterogeneous chains, respectively.

The data management system 120 is configured to obtain the block data of the sub-chain group 140, analyze the block data, and feed back an analysis result to the block chain management system 110.

In some embodiments, the data Management System 120 is also called a BDMS (Block data Management System), and when the Block data in the sub-chain group 140 is transmitted to the BDMS, the BDMS parses the Block data and then feeds back the parsing result to the Block chain Management System 110. The data management system 120 provides a block pull resolution capability, processes block transaction black box data, which is encrypted data, and can protect the security of the transaction by encrypting the data.

The main chain group 130 is configured to receive access of the sub chain group 140 and synchronize transaction information of the sub chain group 140.

In some embodiments, the main chain group 130 is generally built by a project leader or a supervisor, supports access to homogeneous or heterogeneous sub-block chains, has public capabilities of built-in sub-chain registration management, unified digital identity management, cross-chain management, and the like, and provides basic services of built-in sub-chain registration management, unified digital identity management, cross-chain management, and the like for the accessed sub-chains. After accessing the sub-chain group 140, the main chain group 130 synchronizes the transaction information of the sub-chain group 140.

The sub-chain group 140 is used for processing the transaction information and providing the block data to the data management system 120.

In some embodiments, the sub-chain group 140 may include a plurality of sub-chains, and the number of the sub-chains is self-deployed according to the actual needs of the user. The child chain may be newly created or may be a child chain that is running. The sub-chains mainly carry actual block chain services, interface with real service application systems, and can use common basic services provided by the main chain, such as digital identity management, cross-chain services, registration management and the like of the main chain. The sub-chain group 140 provides the data management system 120 with the block data corresponding to the transaction information after processing the transaction information generated in the actual blockchain service of the sub-chain.

Through the embodiment, based on the chain-spanning structure of the main chain and the sub chain, the infrastructure construction of a large block chain similar to a city level can be supported, the main chain supervises the whole appearance, the sub chain runs the service, and the upper limit of the performance of the single chain under the city level scene is broken through.

The components of the blockchain system architecture 100 are described in detail below with respect to fig. 1.

As shown in fig. 1, the blockchain management system 110 includes a main chain BaaS (main chain management unit) 112 and a child chain BaaS (child chain management unit) 114. A backbone BaaS112 comprising backbone management 1122 and child chain management 1124; the backbone management 1122 is used for management of the backbone, including creation cycle management, built-in contract management, namespace management, and front gateway management of the backbone; it can also be used to visually manage the creation cycle, built-in contracts, namespaces, and front gateways of the backbones in the backbone group 130; wherein, the creation period of the main chain is the life period of the main chain, namely the time from creation to logout of the main chain. The sub-chain management 1124 is configured to manage the sub-chains, including analyzing the analysis result fed back by the data management system 120 and displaying the topology structure and the transaction information of the sub-chains in a visual manner, and may even push the sub-chains to a subscription service, so as to implement sensitive data alarm supervision and audit event pushing.

The BaaS114 of the sub-chain may specifically include functions of creating the sub-chain, obtaining access information, applying for registration, receiving a transaction result, and the like, and is used to manage creation of the sub-chain; the BaaS114 of the child chain is further configured to send a register child chain transaction to the main chain group 130 through the front gateway; and receiving a transaction result forwarded by the front gateway, wherein the transaction result is used for indicating that the sub-chain is successfully registered. Meanwhile, the BaaS114 of the child chain is further configured to obtain information such as a contract address of a built-in contract, a gateway address of a pre-gateway, a space name of a namespace, and an access password added to the backbone group 130; the register subchain transaction may thus be sent to the contract address in the backbone group 130 corresponding to the namespace name based on the gateway address and the access password.

As shown in fig. 1, the main chain group 130 includes N main chains, the main chain 1 is connected to the sub-chain group 140, and the main chain 1 may include four namespaces (name spaces), which may be a first namespace name space1, a second namespace name space2, a third namespace name space3, and a fourth namespace name space4, respectively.

Illustratively, the name space1 includes a sub-chain structure state and a built-in sub-chain registration contract, the name space2 includes a sub-chain 1 service and a built-in sub-chain service synchronization contract, the name space3 includes a sub-chain 2 service and a built-in sub-chain service synchronization contract, and the name space4 includes a sub-chain 3 service and a built-in sub-chain service synchronization contract. The name space1 receives sub-chain structure state data transmitted by a pre-gateway in the sub-chain group 140, and the name space2, the name space3 and the name space4 respectively receive service data transmitted by the pre-gateway in the sub-chain group 140, such as the heterogeneous sub-chain 1, the heterogeneous sub-chain 2 and the heterogeneous sub-chain 3. The master link group 130 transmits the block data corresponding to the transaction information transmitted by the slave link group 140 through the front gateway to the latest block monitoring module in the BDMS. The backbone group 130 is directly managed by the backbone management 1122 in the BaaS112 of the backbone. The backbone group 130 receives the transaction information forwarded by the BaaS114 of the child chain through the front gateway.

It should be noted that, the number and the type of the namespaces on any one main chain in the main chain group may be expanded or set based on the actual application scenario, and are not limited to the above example, each main chain may further include more namespaces, and each namespace may correspond to one service sub-chain in one sub-chain group. Therefore, the extension of the main chain can be realized based on the main chain group, the extension of the sub-chain group can be realized based on the name space of each main chain, meanwhile, the sub-chain can report service data according to the service logic respectively according to the name space of the main chain, the main chain is prevented from being stacked and storing the data, and the splitting and the isolation of the service logic and the physical account book are realized.

Exemplarily, the transaction information corresponding to the sub-chain group may include service data, sub-chain structure data, and sub-chain state data, where the service data is data generated by the sub-chain when the sub-chain undertakes a specific service, the sub-chain structure data is data generated by analyzing a specific structure of the sub-chain, and the sub-chain state data is data generated by the sub-chain in operation events such as registration, cancellation, node addition, node deletion, and the like.

In some embodiments, the main chain group 130 is further configured to partition a partition in the main chain corresponding to the namespace, the partition corresponding to the transaction information of the child chains in the child chain group 140.

In some embodiments, the main chain may implement a partition protection mechanism for transactions in the blockchain network by a namespace method, and a user performs transaction partitioning according to the namespace, thereby achieving the effect of privacy protection in the physical layer by means of independence and isolation between partitions.

For example, as shown in a schematic structural diagram of a namespace (name space) shown in fig. 2, names of the namespace are configured by a user according to specific services, any 4 nodes may form a new name space, each name space is isolated from another, and maintains its own account book data, which is transaction data generated in an actual transaction process when the user records on the account book, each name space may deploy a contract with a specific subject, which is a specific service subject, and different account books correspond to contracts with different subjects. In fig. 2, nodes 1, 2, 5 and 6 form name space1, nodes 3, 4, 7 and 8 form name space2, and nodes 2, 3, 6 and 7 form name space3.

The number of nodes forming the naming space is not specifically limited, and the nodes in the main chain can be divided according to the actual service processing needs of the sub-chains to form the corresponding naming space.

Through the embodiment, the account book data of different namespaces are isolated, so that excessive data aggregation is avoided, and service splitting and service data analysis are facilitated; the sub-chains report the service data according to the service logic respectively according to the name space of the main chain, so that the main chain is prevented from being bundled and storing the data, and the splitting and isolation of the service logic and the physical account book are realized.

In some embodiments, the main chain group 130 is further configured to deploy built-in contracts corresponding to the partitions according to the namespaces, and the built-in contracts may include built-in child chain registration management contracts of the main chain, built-in child chain service synchronization contracts of the main chain, and the like.

In some embodiments, after multiple namespaces are created, corresponding built-in contracts can be deployed within different namespaces according to the business rules supported.

Exemplarily, a namespace is created, and a sub-chain registration management contract is built in the namespace and is mainly used for managing operation events of the sub-chain; the operation events of the child chain mainly comprise registration, logout, node addition, node deletion and the like. The main chain can analyze the complete picture of the main sub-chain group through the transaction of the name space; or a namespace is created, and a sub-chain service anchoring contract is built in, also called a built-in sub-chain service synchronization contract; the sub-chain service synchronization contract can be used for synchronizing block head data of the sub-chain service and also synchronizing block data; to ensure the performance of the whole chain group, only the block header data of the sub-chain service may be synchronized.

As shown in fig. 1, the sub-chain group 140 may include M heterogeneous sub-chains, where heterogeneous means that the sub-chains have different underlying logical architectures from the main chain, and the M sub-chains may also be homogeneous, that is, the sub-chains have the same underlying logical architecture as the main chain, and each sub-chain may be homogeneous or heterogeneous, which is not limited herein. A name space1 is respectively arranged inside the heterogeneous sub-chain 1, the heterogeneous sub-chain 2 and the heterogeneous sub-chain 3, and specific services are placed in the name space 1; the external parts of the system are respectively connected with a front gateway, and the sub-chain structure state data and the service data are respectively transmitted to corresponding name spaces in the main chain 1 in the main chain group 130 through the front gateways. The sub-chain group 140 is directly managed by the BaaS114 of the sub-chain, and the sub-chain in the sub-chain group 140 is created by the BaaS114 of the sub-chain. The sub-link group 140 is used for processing the transaction information and providing the block data to the data management system 120.

In some embodiments, first, the child chain needs to be registered to the main chain, i.e. the child chain is registered: the subchain can send a registration request to a built-in contract (subchain registration management contract) address of a specific namespace of the main chain through the front-end gateway, after a transaction is successful, the subchain is registered successfully, and operation events of subsequent subchains are all sent to the main chain through the front-end gateway, such as the subchain is cancelled, nodes are added and deleted; secondly, the sub-chain needs to synchronize transaction information to the main chain, namely service synchronization: the method mainly relates to a built-in sub-chain service synchronization contract of a main chain, and block header data of specific services of a sub-chain can synchronize self service data on the main chain through a front gateway.

It should be noted that block header data of specific services of a sub-chain may synchronize its own service data on the main chain through the pre-gateway, a built-in sub-chain service synchronization contract may not only synchronize service data, but also solve the problem of the heterogeneous main chain and sub-chain, and unifies logic by using a contract to remove differences brought by different bottom layers, thereby achieving the purpose of unification, and a sub-chain only needs to send a transaction of service data encapsulation to a contract address of a specific namespace according to a specific structure.

The sub-chain processes the service data, the self structure data and the state data generated during the operation of the actual service, and then provides the data to the data management system 120, but the sub-chain does not directly provide the data to the data management system 120, but provides the data through the main chain group 130.

According to the embodiment, different heterogeneous chains can be registered to the main chain through the built-in sub-chain registration management contract and the front gateway, the main chain analyzes data in transactions through the BDMS, and specific information of the sub-chains is obtained, so that management is performed, even if the sub-chains are in operation, the sub-chains can be accessed to the main chain without interruption, and the operation of services of the sub-chains is not influenced.

As shown in fig. 1, the blockchain system architecture 100 further includes front-facing gateways, each of which is connected to a corresponding heterogeneous child chain and main chain group 130.

In some embodiments, the number of head gateways is determined by the number of sub-chains, and there are several head gateways corresponding to how many sub-chains are. The front gateway, also called an internet connector or a protocol converter, is a transaction forwarding middleware, and if a server is compared as a room, the gateway is equivalent to a door and is mainly used for transmitting data of a client to the server and enabling the server to process the data.

The key flow of the data management system (BDMS) 120 listening block is described in detail below with respect to fig. 1 and 3.

As shown in fig. 1, the BDMS includes a latest block monitoring module and a block information parsing module, where the latest block monitoring module is used to pull block data corresponding to a namespace on a main chain in the main chain group 130; the parsing block information module is configured to parse and monitor block data pulled by the latest block module, and then transmit the parsed data to the main chain management 1122 in the BaaS112 of the main chain. The analysis block information is mainly used for analyzing specific contract data in actual transaction through an analysis model, the specific contract data comprises subchain registration management contract data and subchain service synchronization contract data, after the data analysis is completed, the data is processed according to a defined data processing rule, finally the processed data is pushed to a main chain management 1122 in the main chain BaaS112, and a data analysis service is developed through the main chain management 1122 in the main chain BaaS 112.

As shown in fig. 3, the key flow of the BDMS listening block is: step one, BDMS obtains the height of the latest block; secondly, returning the main chain or the sub-chain to the current block height max; thirdly, the BDMS pulls the block; fourthly, returning the main chain or the sub chain to the block; fifthly, the BDMS monitors the latest block; sixthly, pulling block information according to the latest block height; seventhly, returning block information by the main chain or the sub chain; eighth, the BDMS parses the block and updates the local block height. The above process is summarized as follows: after the main chain is accessed into the BDMS, the block on the chain is pulled from the 0 th block until the latest block on the chain is consistent with the block height of local processing, then the BDMS starts block monitoring logic, when block data is generated on the chain, the BDMS monitors the information, firstly starts block pulling service, then analyzes the block data, updates the local block height, then starts the next round of monitoring, and the steps are repeated in a circulating way.

The chunk height is an identifier of the chunk, and the chunk has two identifiers, one is the hash value of the chunk header, and the other is the chunk height. The hash value of the block header is a number obtained by performing a double hash calculation on the block header by the SHA256 algorithm. A chunk hash value may uniquely and unambiguously "identify" a chunk, and any node may independently obtain the chunk hash value by simply hashing the chunk header. The block height refers to the position of the block in the block chain and is not a unique "identifier". While a single block will always have a definite, fixed block height, the opposite is not true, and a block height does not always identify a single block. Two or more blocks may have the same block height, competing for the same position in the block chain.

Through the embodiment, whether sensitive transactions exist in the sub-chain can be known through monitoring the transactions, and if the sensitive information is monitored, the sub-chain can be processed in time.

The following describes the interaction flow between the modules of the blockchain system architecture in detail with reference to fig. 4.

First, a backbone is created: a main chain is created through BaaS of the main chain, a preset built-in contract, such as a subchain registration management contract, is automatically deployed after the creation is successful, and a front gateway needs to be deployed in order that a subchain can be communicated with the main chain for registration.

Secondly, the sub-chain acquires access information: the sub-chain needs to acquire the related information of the main chain to create the front gateway, including: contract address of built-in contract, gateway address of front gateway, space name of name space and access password added into main chain.

Thirdly, the sub-chain is automatically registered: if the sub-chain is newly created and successfully registered on the main chain, the sub-chain runs specific services and generates on-chain transactions after successful registration; if a child chain is running and needs to join the master-child chain system, the operational events of the child chain need to be registered with the master chain. The external flow of the BaaS automatic registration of the child chain is as follows: firstly, a sub-chain is created, after the sub-chain is successfully created, a registration event is automatically triggered, a transaction is automatically initiated to a main chain, and the transaction is sent to a contract address in a specific name space on the main chain through a front gateway; secondly, acquiring related information of the main chain creation front gateway, comprising the following steps: the contract address of the built-in contract, the gateway address of the front gateway, the space name of the namespace and the Access password added into the main chain group 130, wherein the obtained contract address of the built-in contract is mainly the contract address of the registration management contract of the sub-chain, the obtained name of the namespace is determined by specific transaction, the obtained Access password added into the main chain group 130 is Access Key (AK) for authentication, the Access password is very critical for the sub-chain to Access the main chain, and if the Access password is not obtained, the sub-chain cannot Access the main chain even if the contract address of the built-in contract, the gateway address of the front gateway and the space name of the namespace are obtained; thirdly, applying for registering the main chain to form a sub-chain; fourthly, the transaction information is forwarded to a main chain through a front gateway; fifthly, registering the operation event of the sub-chain by the main chain, wherein the operation event of the sub-chain is used as an upper transaction chain; sixthly, feeding back a calling result through a front gateway; step seven, receiving the result of successful application registration; and step eight, sending information of successful creation to the child chain.

The internal flow of sub-chain auto-registration is shown in fig. 5 (the dotted arrow represents the logical data flow, and the solid arrow represents the actual call relationship): first, the backbone is deployed: the BaaS of the subchain sends a deployment command to the chain drive through the core service, and the chain drive is called to deploy the subchain and the nodes; secondly, reporting a registration event: after confirming that the deployment of the child chain and the node is successful, the core service of the BaaS of the child chain converts the deployment event into registration information, packages the registration information into a transaction, and forwards the transaction to the main chain through the front gateway, wherein the specific process comprises the following steps: the method comprises the steps that a chain driver of a BaaS of a subchain reports states of deployed chains and nodes to a core service of a BaaS of the subchain, a state reporting process in the core service reports the states of the chains and the nodes to a state interceptor in the core service, the state interceptor judges whether to intercept state reporting, if the subchain does not need to be registered on a main chain any more, the state interceptor intercepts the state reporting, if the subchain still needs to be registered on the main chain, the state interceptor does not intercept the state reporting, then the state interceptor reports the state to an event process in the core service, the event process reports the state to a front gateway driver of the BaaS of the subchain, the front gateway driver calls a contract built in the main chain, the front gateway of the BaaS of the main chain authenticates and forwards the authentication, the authentication mainly uses AK (Access), if the authentication is successful, the Key front gateway calls a contract built in the BaaS of the subchain, and the contract built in the main chain management contract registered in the BaaS, and the main chain management contract of the subchain are connected with the main chain management main chain.

And finally, managing the main sub-chain: firstly, acquiring the topology of the main sub-chain group structure: after the operation event of the sub-chain is used as a transaction uplink, the BDMS pulls the block according to the preset time to analyze the transaction information of the block, and meanwhile, the analyzed block data corresponding to the transaction information is structurally processed according to the set service analysis rule. The BDMS has no limitation on the state of the sub-chain when pulling the sub-chain, and can pull the sub-chain regardless of whether the sub-chain is in a state of registering, deregistering, or adding and deleting nodes, or in a state of service running or stopping, for example: the pulling can be performed when the sub-chain applies for registration to the main chain and when the sub-chain runs a specific service. And the BaaS of the main chain visually manages the main chain group and the sub chain group according to the analysis result after the structuralization processing of the set business analysis rule. Secondly, reporting and supervising sub-chain service data: the BDMS can directly monitor the block data of the subchain, the data is analyzed after being pulled, and if sensitive information exists, the warning information is reported to the BaaS of the main chain; and logic reported by the registration event can be multiplexed, service data of the sub-chains are packaged into an transaction and sent to the main chain, and the main chain is analyzed through the BDMS. Can be respectively applied according to actual scenes, and has high flexibility.

By the embodiment, the construction of large block chain infrastructures similar to city level can be supported, the main chain supervises the whole appearance and the sub chain operation service, and the upper limit of the single chain performance in the city level scene is broken through; different heterogeneous chains can be registered to a main chain through a built-in sub-chain registration management contract and a front gateway, the main chain analyzes data in transactions through a BDMS (distributed data management System), and specific information of the sub-chains is obtained, so that management is performed, even if the sub-chains are in operation, the sub-chains can be accessed to the main chain without interruption, the operation of the services of the sub-chains is not influenced, and flexible access of the heterogeneous chains can be realized; the main chain is separately deployed, the sub-chains are added or withdrawn from the main chain system as required, the sub-chain in operation can be added into the main chain system at any time, if the sub-chain service is supposed to be separated from the main chain system to operate independently, the sub-chain only needs to send a sub-chain logout request under the condition of not stopping operation, the existing operation service of the sub-chain is not influenced, and the operation of adding the main chain is the same as the operation. Meanwhile, the actions of registering, adding and deleting nodes, canceling and the like of the sub-chains are packaged into a transaction and reported to the main chain, and the main chain can sense the overall appearance of the whole chain group through analyzing the transaction; therefore, the main chain can comprehensively supervise the sub-chain.

The specific process of block data structuring and visual management of the main sub-chain group will be described in detail below with reference to fig. 5.

The specific process of the block data structuring processing is as follows: the BDMS acquires and analyzes block data corresponding to the transaction information in the sub-chain group based on the transaction information of the sub-chain group, performs structural processing on the analyzed block data, and feeds back an analysis result after the structural processing to a block chain management system.

For example, as shown in fig. 5, the BDMS acquires the block data of the sub-chain group, analyzes the block data, and feeds back the analysis result to the BaaS of the main chain in a specific process: firstly, acquiring block data corresponding to transaction information in a child chain group transmitted by BaaS of a child chain; secondly, analyzing the acquired block data according to an analysis model; thirdly, performing structural processing on the analyzed block data according to a set service analysis rule, wherein the data subjected to the structural processing comprises sub-chain structure topology, sub-chain service data and the like; and finally, transmitting the processed block data to a core service in the BaaS of the main chain.

The specific process of the visual management of the main sub-chain group comprises the following steps: the BaaS of the main chain performs visual management on the sub-chain group based on the analysis result after the structural processing; and the BaaS of the main chain also performs visual management on the main chain group based on the creation information and the deployment information of the main chain group.

In some embodiments, the BaaS of the backbone includes a "core service" that includes the specific business logic, and a database db. The core service and the database db visually manage the creation information and the deployment information of the main chain group and the specific structure of the sub-chain group based on the analysis result after the structural processing.

Illustratively, as shown in fig. 5, the BaaS of the main chain transmits the block data corresponding to the transaction information structured according to the set business analysis rule to the "core service" of the BaaS of the main chain, and the "core service" integrates the block data according to the visualization requirement and the specific "business logic" and stores the integrated block data into the "database db". When a user needs to check the architecture of the whole main sub-chain group, the core service of the BaaS of the main chain can directly pull the block data from the database db to be presented to the user.

By the embodiment, the block data can be analyzed through the BDMS, so that service data can be visually displayed on the BaaS of the main chain; whether sensitive transactions exist in the sub-chain or not can be known by monitoring the transactions.

The role of the head-end gateway is described in detail below with respect to fig. 4.

The front gateway is used for forwarding the registered sub-chain transaction to the main chain and forwarding the transaction result to the BaaS of the sub-chain after receiving the transaction result fed back by the main chain.

In some embodiments, the front-end gateway forwards a transaction which is applied for registration as a child chain through the BaaS of the child chain to a contract address in a specific namespace on a main chain in the main chain, and forwards the transaction result to the BaaS of the child chain after receiving a transaction result which is fed back by the main chain and calls a built-in child chain registration management contract of the main chain. And the operation events of the subsequent sub-chains are all sent to the main chain through the front gateway, such as the sub-chain logout, the node addition, the node deletion and the like.

For example, as shown in fig. 1 and fig. 4, the front end gateway forwards a transaction of registering a child chain through the BaaS114 of the child chain to a contract address in a specific namespace name space1 on the main chain in the main chain group 130, and forwards the transaction result to the BaaS114 of the child chain after receiving a transaction result of calling a built-in child chain registration management contract of the main chain fed back by the main chain group 130; the pre-positioned gateway forwards a transaction of logging out the sub-chain through the BaaS114 of the sub-chain to a contract address in a specific name space1 on a main chain in the main chain group 130, and forwards the transaction result to the BaaS114 of the sub-chain after receiving a transaction result of calling a built-in sub-chain registration management contract of the main chain fed back by the main chain group 130; the pre-positioned gateway forwards the transaction of the node added by the BaaS114 of the sub-chain to a contract address in a specific name space1 on a main chain in the main chain group 130, and forwards the transaction result to the BaaS114 of the sub-chain after receiving the transaction result of a built-in sub-chain registration management contract calling the main chain fed back by the main chain group 130; the pre-positioned gateway forwards the transaction of deleting the node through the BaaS114 of the sub-chain to a contract address in a specific namespace name space1 on a main chain in the main chain group 130, and forwards the transaction result to the BaaS114 of the sub-chain after receiving the transaction result of calling the built-in sub-chain registration management contract of the main chain fed back by the main chain group 130.

According to the embodiment, the main chains and the sub chains are separately deployed, the sub chains are added or withdrawn from the main chain system structure as required, the sub chains which are already running can be added into the main chain system at any time, and if the sub chain service is separated from the main chain system to run alone, the main sub chain only needs to send a request for logging off the sub chains without shutdown, so that the sub chains are not influenced to practice the existing running service.

Fig. 6 is a flowchart illustrating a method for managing a blockchain according to an embodiment of the present application, corresponding to the blockchain system architecture 100 described in the foregoing embodiment. The method for managing the block chain is applied to the block chain system architecture 100, and comprises the following steps:

s801, a sub-chain group accesses a main chain group and synchronizes transaction information to the main chain group; and providing the block data corresponding to the transaction information to a data management system.

The step is realized by an entity terminal corresponding to a node in any one subchain in the subchain group.

S802, the main chain group receives the access of the sub chain group and obtains the transaction information synchronized with the sub chain group.

The step is realized by an entity terminal corresponding to a node in any main chain in the main chain group.

And S803, the data management system acquires the block data of the sub-chain group, analyzes the block data, and feeds back an analysis result to the block chain management system.

The step is realized by an entity terminal corresponding to the data management system.

S804, the block chain management system deploys and manages the main chain group and the sub chain group respectively based on the creation information of the main chain and the sub chain, and visually manages the sub chain group based on the received analysis result.

The step is realized by the entity terminal corresponding to the block chain management system.

The specific process of the method provided in this embodiment is described above, and is not described herein again.

The beneficial effects of the method provided in this embodiment can be referred to the related description in the embodiment of the block chain system architecture 100, and are not repeated herein.

Fig. 7 is a flowchart illustrating a method for managing a blockchain according to an embodiment of the present application, corresponding to the system 102 for managing a blockchain according to the above embodiment. The method for managing a block chain is applied to a block chain management system 110, and the method comprises the following steps:

and S901, establishing and deploying the main chain group and the sub chain group.

And S902, receiving an analysis result fed back by the data management system, wherein the analysis result is obtained by analyzing the block data sent by the sub-chain group by the data management system, and the block data is data corresponding to the transaction information of the sub-chain group.

And S903, performing visual management on the sub-chain group based on the analysis result.

The specific process of the method provided in this embodiment is described above, and is not described herein again.

The beneficial effects of the method provided in this embodiment can be referred to the related description in the above embodiment of the block chain management system 110, and are not described herein again.

Fig. 8 shows a flowchart of a block chain management method provided in an embodiment of the present application, corresponding to the data management system 120 in the foregoing embodiment. The block chain management method is applied to the data management system 120, and the method includes:

s101, acquiring block data of the sub-chain group, wherein the block data is data corresponding to the transaction information of the sub-chain group.

S102, analyzing the block data to obtain an analysis result.

S103, sending the analysis result to a blockchain management system, wherein the analysis result is used for indicating the blockchain management system to visually manage the sub-chain group.

The terminal for implementing the method can be a separately deployed terminal, or an integrated module deployed on the BAAS side of the main chain, or a unit of an entity terminal deployed on any node in the main chain.

The specific process of the method provided in this embodiment is described above, and is not described herein again.

The beneficial effects of the method provided by this embodiment can be referred to the related description in the above embodiment of the data management system 120, and are not described herein again.

The block chain system architecture and the block chain management method provided by the embodiment of the application have the following advantages: first, a large blockchain infrastructure can be supported: the provided scheme of the main chain architecture can support the infrastructure construction of a large block chain similar to a city level, the main chain supervises the whole appearance, the sub chain operation service and breaks through the upper limit of the single chain performance in the city level scene; second, the service is clear: the sub-chain reports the service data according to the service logic respectively according to the name space of the main chain, the main chain is prevented from being bundled and storing the data, the service logic and the physical account book are separated and isolated, and the block data can be analyzed through the BDMS, so that the service data can be visually displayed on the BaaS; thirdly, the heterogeneous chain is flexibly accessed: different heterogeneous chains can be registered to a main chain through a built-in sub-chain registration management contract and a front gateway, the main chain analyzes data in transactions through a BDMS (distributed data management system), and specific information of the sub-chains is obtained, so that management is performed, even if the sub-chains are in operation, the sub-chains can be accessed to the main chain without interruption, and the operation of the services of the sub-chains is not influenced; fourthly, overall supervision of the main chain: actions such as registration, node addition and deletion, logout and the like of the sub-chains are packaged into transactions and reported to the main chain, the main chain can sense the overall view of the whole chain group through analyzing the transactions, and meanwhile, whether sensitive transactions exist in the sub-chains or not can be known through monitoring the transactions; fifth, the architecture is flexible: the main chain is separately deployed, the sub-chains are added or withdrawn from the main chain system as required, the sub-chain in operation can be added into the main chain system at any time, if the sub-chain service is supposed to be separated from the main chain system to operate independently, the sub-chain only needs to send a sub-chain logout request under the condition of not stopping operation, the existing operation service of the sub-chain is not influenced, and the operation of adding the main chain is the same as the operation.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Fig. 9 shows a block diagram of a blockchain management device provided in the embodiment of the present application, where for convenience of description, only the parts related to the embodiment of the present application are shown.

Referring to fig. 9, the apparatus includes:

the transmission unit 111 is used for enabling the sub-chain group to access the main chain group and synchronizing transaction information to the main chain group; providing block data corresponding to the transaction information to a data management system;

a synchronization unit 112, configured to receive, by a main chain group, access of the sub-chain group, and acquire the transaction information synchronized by the sub-chain group;

a processing unit 113, configured to acquire the block data of the sub-chain group, analyze the block data, and feed back an analysis result to a block chain management system;

and the management unit 114 is configured to, by the block chain management system, perform deployment management on the main chain group and the sub-chain group based on the creation information of the main chain and the sub-chain, respectively, and perform visual management on the sub-chain group based on the received analysis result.

Fig. 10 shows a block diagram of a blockchain management device provided in the embodiment of the present application, where for convenience of description, only the parts related to the embodiment of the present application are shown.

Referring to fig. 10, the apparatus includes:

a creating and deploying unit 121, configured to create and deploy a main chain group and a sub-chain group;

a receiving unit 122, configured to receive an analysis result fed back by the data management system, where the analysis result is obtained by analyzing, by the data management system, block data sent by the sub-chain group, and the block data is data corresponding to transaction information of the sub-chain group;

and a visualization management unit 123, configured to perform visualization management on the sub-chain group based on the analysis result.

Fig. 11 shows a block diagram of a blockchain management device according to an embodiment of the present application, which corresponds to the blockchain management method according to the foregoing embodiment, and only shows portions related to the embodiment of the present application for convenience of description.

Referring to fig. 11, the apparatus includes:

an obtaining unit 131, configured to obtain block data of a sub-chain group, where the block data is data corresponding to transaction information of the sub-chain group;

an analyzing unit 132, configured to analyze the block data to obtain an analysis result;

a transmitting unit 133, configured to send the analysis result to a blockchain management system, where the analysis result is used to instruct the blockchain management system to perform visual management on the sub-chain group.

Fig. 12 is a schematic structural diagram of an electronic device 14 according to an embodiment of the present application. As shown in fig. 12, the electronic device 14 of this embodiment includes: at least one processor 141 (only one is shown in fig. 12), a memory 143, and a computer program 142 stored in the memory 143 and executable on the at least one processor 141, the processor 141 implementing the steps in the method embodiments applied to the blockchain management system and the data management system when executing the computer program 142.

The electronic device 14 may be a desktop computer, a notebook, a palm computer, a mobile phone, or other computing devices. The electronic device 14 may include, but is not limited to, a processor 141 and a memory 143. Those skilled in the art will appreciate that fig. 12 is merely an example of the electronic device 14 and does not constitute a limitation of the electronic device 14, and may include more or less components than those shown, or combine certain components, or different components, such as may also include input-output devices, network access devices, etc.

The Processor 141 may be a Central Processing Unit (CPU), and the Processor 141 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 143 may be an internal storage unit of the electronic device 14 in some embodiments, such as a hard disk or a memory of the electronic device 14. The memory 143 may also be an external storage device of the electronic device 14 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital Card (SD), a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 14. Further, the memory 143 may also include both an internal storage unit of the electronic device 14 and an external storage device. The memory 143 is used for storing an operating system, an application program, a Boot Loader (Boot Loader), data, and other programs, such as program codes of the computer programs. The memory 143 may also be used to temporarily store data that has been output or is to be output.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, when the present application implements all or part of the flow in the method of the foregoing embodiments, the above steps in the method embodiments applied to the blockchain management system and the data management system may be implemented by a computer program, which may be stored in a computer readable storage medium and executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable storage medium may include at least: any entity or device capable of carrying computer program code to a blockchain device/electronic apparatus, a recording medium, a computer Memory, a Read-Only Memory (ROM), a Random Access Memory (RAM), an electrical carrier wave signal, a telecommunication signal, and a software distribution medium, such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable storage media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and proprietary practices.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. The above-described apparatus/network device embodiments are merely illustrative, and the division of the modules or units is only one logical function division, and other division manners may be available in actual implementation, for example, multiple units or components may be combined or may be integrated into another system, and some features may be omitted from being executed. In addition, the shown or discussed indirect coupling, direct coupling or communication connection between each other may be through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, and do not limit the same. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: modifications and substitutions of the technical features described in the embodiments can be made, and the modifications and substitutions do not depart from the spirit and scope of the technical features of the embodiments and should be included in the scope of the present application.

Claims (10)

1. A block chain system architecture, comprising: the system comprises a block chain management system, a data management system, a main chain group and a sub chain group;

the block chain management system is used for managing the creation and deployment of the main chain group and the sub-chain group;

the data management system is used for acquiring the block data of the sub-chain group, analyzing the block data and feeding back an analysis result to the block management system;

the main chain group is used for accessing the sub chain group and synchronizing the transaction information of the sub chain group;

the sub-chain group is used for processing the transaction information and providing the block data to the data management system.

2. The system architecture of claim 1, wherein the blockchain management system includes a backbone management unit;

the main chain management unit is used for managing a creation period, a built-in contract and a naming space of the main chain in the main chain group;

the main chain management unit is further used for analyzing the analysis result fed back by the data management system and displaying the topological structure of the sub chain and the transaction information;

the main chain group is used for dividing partitions corresponding to the name space in the main chain, and the partitions correspond to the transaction information of the sub chains in the sub chain group;

the main chain group is further used for deploying the built-in contracts corresponding to the partitions according to the namespaces, and the built-in contracts comprise registration management contracts of the sub-chains and service synchronization contracts of the sub-chains;

the main chain management unit is further configured to perform visual management on the main chain group based on the creation information and the deployment information of the main chain group.

3. The system architecture of claim 2, wherein the system architecture further comprises a head-end gateway, the blockchain management system further comprising a child chain management unit;

the sub-chain management unit is used for sending a registered sub-chain transaction to the main chain group through the front gateway;

the preposed gateway is used for forwarding the registered sub-chain transaction to the main chain group and forwarding the transaction result to the sub-chain management unit after receiving the transaction result fed back by the main chain group;

the sub-chain management unit is further configured to receive the transaction result forwarded by the head-end gateway, where the transaction result is used to indicate that the sub-chain is successfully registered.

4. The system architecture of claim 3,

the sub-chain management unit is further configured to obtain a contract address of the built-in contract, a gateway address of the pre-gateway, a space name of the namespace, and an access password joining the main chain group;

the sub-chain management unit is further configured to send the registered sub-chain transaction to the contract address corresponding to the space name in the main chain group based on the gateway address and the access password.

5. The system architecture of claim 2,

the data management system is further configured to acquire and analyze block data corresponding to the transaction information in the sub-chain group based on the transaction information of the sub-chain group, perform structured processing on the analyzed block data, and feed back the analysis result after structured processing to the block chain management system;

the main chain management unit is further configured to perform visual management on the sub-chain group based on the analysis result after the structural processing.

6. A method for managing a blockchain, applied to a blockchain system architecture, the method comprising:

the sub-chain group accesses the main chain group and synchronizes transaction information to the main chain group; providing block data corresponding to the transaction information to a data management system;

the main chain group receives the access of the sub chain group and acquires the transaction information synchronized by the sub chain group;

the data management system acquires the block data of the sub-chain group, analyzes the block data and feeds back an analysis result to the block chain management system;

the block chain management system respectively deploys and manages the main chain group and the sub chain group based on the creation information of the main chain and the sub chain, and visually manages the sub chain group based on the received analysis result.

7. A method for managing a block chain is applied to a block chain management system, and the method comprises the following steps:

establishing and deploying a main chain group and a sub chain group;

receiving an analysis result fed back by a data management system, wherein the analysis result is obtained by analyzing block data sent by the sub-chain group by the data management system, and the block data is data corresponding to the transaction information of the sub-chain group;

and visually managing the sub-chain groups based on the analysis result.

8. A block chain management method is applied to a data management system, and the method comprises the following steps:

acquiring block data of a sub-chain group, wherein the block data is data corresponding to transaction information of the sub-chain group;

analyzing the block data to obtain an analysis result;

and sending the analysis result to a blockchain management system, wherein the analysis result is used for indicating the blockchain management system to perform visual management on the sub-chain group.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any of claims 7 or 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 7 or 8.

Images