CN113132430A - Alliance chain system management method, device, equipment and computer storage medium - Google Patents

Alliance chain system management method, device, equipment and computer storage medium Download PDF

Info

Publication number
CN113132430A
CN113132430A CN201911411172.7A CN201911411172A CN113132430A CN 113132430 A CN113132430 A CN 113132430A CN 201911411172 A CN201911411172 A CN 201911411172A CN 113132430 A CN113132430 A CN 113132430A
Authority
CN
China
Prior art keywords
node
accounting
chain system
nodes
consensus
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.)
Pending
Application number
CN201911411172.7A
Other languages
Chinese (zh)
Inventor
王敏行
唐睿
张翔
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Chengdu ICT Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Chengdu ICT Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Chengdu ICT Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to CN201911411172.7A priority Critical patent/CN113132430A/en
Publication of CN113132430A publication Critical patent/CN113132430A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • H04L41/042Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols 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]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Abstract

The invention provides a union chain system management method, a device, equipment and a computer storage medium. The alliance chain system management method comprises the following steps: setting node marks, namely setting the node marks for nodes newly accessed to a alliance chain system, wherein the node marks comprise common node marks for indicating that the nodes are common nodes and consensus node marks for indicating that the nodes are consensus nodes; and a billing management step, when the ordinary node participates in billing, the ordinary node is enabled to provide a workload certification; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data. According to the management method of the alliance chain system, the billing time of the alliance chain system can be reduced, and the requirement on the computing capacity of a hardware system of a billing node is lowered.

Description

Alliance chain system management method, device, equipment and computer storage medium
Technical Field
The invention relates to the technical field of block chains and edge computing, in particular to a union chain system management method based on an edge server unit.
Background
Generally, a block chain is a large account book formed by connecting data blocks packed with information in sequence by using a chain, and is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. Here, Peer-to-Peer (P2P, Peer-to-Peer) is a Peer-to-Peer network, also called Peer-to-Peer technology, where a user of any Peer-to-Peer network has functions of both a node and a server, and any node cannot directly find other nodes and must rely on its user group to perform information exchange. The consensus mechanism is a system for maintaining the operation sequence and fairness of the system, and rewards and punishments are made, and the consensus mechanism proves who is the fastest-booked person or the malicious person in some way. Workload certification is one of the consensus mechanisms, generally requiring some time-consuming and complex operations by the user, and the answers can be quickly verified by the server, taking the time, equipment and energy consumed as warranty costs to ensure that services and resources are used by the real needs.
The general block chain is a decentralized database in nature, and is a series of data blocks which are generated by using a cryptographic method to correlate with each other as the underlying technology of virtual currency such as bitcoin, and each data block contains information of a batch of bitcoin network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate the next block. Here, taking the first generation blockchain technology as an example, the three methods of decentralization, reward mechanism and consensus mechanism are combined together to achieve the goal of blockchain technology.
The existing mainstream block chain system adopts a public chain form, that is, any node directly enters the system without providing audit verification, and each node strives for the verification by providing an effective workload verification as the authority of verifying the block. Typically, the generation of each tile is guaranteed to take around 10 minutes, depending on the current computational power level of the system. Strict calculation audit obviously improves the capability of preventing the system from being attacked and also provides guarantee for the safe storage and distribution of data. However, because of the existence of the mechanism, the system can also generate huge data volume while solving the trust problem, and on the other hand, due to the existence of the workload proving time length and the serial working mechanism of the block chain, the time length required by one-time distributed storage is certainly longer than the sum of the verification time of all the participating nodes. The time consumption is usually too long compared to the actual business storage requirements.
To provide adequate proof of computing power and to minimize the length of proof time, computer systems are often upgraded in computing power. I.e. using computationally efficient mining machines for block generation. On one hand, the powerful calculation power proves that calculation power resources are usually excessive in daily use scenes, and the resource waste is obvious; on the other hand, the excessive investment cost of the strong computing power is huge, and the maintenance cost for the general contract system is also obviously increased. Therefore, the existing blockchain system is difficult to be accepted by users at the level of contract storage trust in a market environment.
That is, a general blockchain system authenticates nodes through a POS (Proof of authority) mechanism, under which the system makes all nodes participate in accounting, and accounting burden is heavy. On the other hand, if the workload proving time is shortened to provide a sufficient calculation power proof, the problem that the calculation power resources are usually excessive at ordinary times and the cost is huge if the calculation power of the computer system is upgraded.
Disclosure of Invention
The embodiment of the invention provides a management method, a device, equipment and a computer storage medium for a coalition chain system, which can take contract accounting of a commercialized coalition chain as an application scene and provide the management method for the coalition chain system with small system accounting load and proper cost.
In one aspect, an embodiment of the present invention provides an alliance chain system management method, where the method includes: setting node marks, namely setting the node marks for nodes newly accessed to a alliance chain system, wherein the node marks comprise common node marks for indicating that the nodes are common nodes and consensus node marks for indicating that the nodes are consensus nodes; and a billing management step, when the ordinary node participates in billing, the ordinary node is enabled to provide a workload certification; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data.
On the other hand, an embodiment of the present invention provides an alliance chain system management apparatus, including: a node flag setting unit that sets a node flag for a node newly accessed to the alliance chain system, the node flag including a common node flag indicating that the node is a common node and an consensus node flag indicating that the node is a consensus node; the accounting management unit enables the common node to provide workload certification when the common node participates in accounting; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data.
In another aspect, an embodiment of the present invention provides an alliance chain system management device, where the device includes: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the federation chain system management method described above.
In still another aspect, an embodiment of the present invention provides a computer storage medium, where computer program instructions are stored, and when the computer program instructions are executed by a processor, the method for managing a federation chain system as described above is implemented.
According to the alliance chain system management method, device and equipment and the computer storage medium, the total workload generated by forming the alliance chain can be reduced by using the consensus node to account the generated blocks. In addition, the method and the device can realize the matching of the suitability, the calculation power and the large probability application scene, and the maintenance cost meets the scene cost requirement.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart illustrating a federation chain system management method according to one embodiment of the present invention;
FIG. 2 is a flowchart illustrating a federation chain system management method according to another embodiment of the present invention;
FIG. 3 is a schematic diagram of the connection relationships between nodes;
FIG. 4 is a flow diagram of the generation of a federation chain in accordance with the federation chain system management method of the present invention;
FIG. 5 is a schematic structural diagram of a federation chain system management device according to another embodiment of the present invention;
FIG. 6 is a block diagram of a federation chain system provided by yet another embodiment of the present invention;
fig. 7 is a schematic structural diagram of a federation chain system management device according to another embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
In order to solve the problem of the prior art, embodiments of the present invention provide a method, an apparatus, a device, and a computer storage medium for managing an alliance chain system. First, a federation chain system management method provided by the embodiment of the present invention is described below.
Fig. 1 is a flowchart illustrating a federation chain system management method according to an embodiment of the present invention. The federation chain system management method shown in FIG. 1 includes: a node flag setting step S101 of setting a node flag to a node newly accessed to the alliance chain system, where the node flag includes a common node flag indicating that the node is a common node and a consensus node flag indicating that the node is a consensus node; a billing management step S102, when the ordinary node participates in billing, the ordinary node provides workload certification; when the consensus node participates in accounting, the consensus node is enabled not to provide workload proofs and directly stores data.
According to the management method of the alliance chain system, the calculation load of the alliance chain system in contract billing can be reduced, and the workload proving time is saved.
Fig. 2 shows a flowchart of a federation chain system management method provided by another embodiment of the present invention.
Firstly, a node access management step S201 is included, which is to perform auditing on a node requesting to access a federation chain system, and access a node passing the auditing, where the node includes an enterprise-level owned server system accessed in a mobile edge manner or an edge server under a 5G system.
The alliance chain system related to the embodiment of the invention is different from the full-open of a public chain and the full-closed of a private chain, and is designed into a semi-open block chain which can be conditionally accessed to an external node. The access node of the system adopts a strict admission condition setting mode, for example, an Edge server under an enterprise-level self-owned server system or a 5G system is accessed in a form of MEC (Mobile Edge Computing) generally.
The node access of the alliance chain system related to the embodiment of the invention is different from the node access of the general block chain system as follows. Usually, the blockchain system can be completed by the node applying for access accessing to the node. In the alliance chain system, an access request of a node end is not accepted any more, but a special access interface is arranged at a background end of the alliance chain system, and the interface designates a specific operator to access by presetting user authority. Meanwhile, an access auditing mechanism is added, and an operator with auditing authority receives data uploaded by a specific accessor, wherein the data at least comprises content for reflecting the trust risk bearing capacity of the applied node, and the data is classified into a special storage logic unit. The operator port of the auditing authority is provided with a template editing unit, the auditing operator can set a data template and specify necessary data independently, and the data template can be issued only after being approved by at least one non-self auditing operator in the issuing process.
Therefore, through the node access control in the management method of the alliance chain system, the trust guarantee capability of the node accessed to the alliance chain system is obviously improved, and the trust risk of the system is obviously reduced. In addition, a large space is provided for adjusting the calculation power proving rule designed for guaranteeing the credibility of the system, and the requirement on the calculation capacity of the hardware system is obviously reduced. The accessed node has higher trust guarantee capability, and the potential possibility of losing credit is effectively controlled.
Next, in step S202, a node flag setting step of setting a node flag for a node accessed to the federation chain system. The node flag includes a common node flag indicating that the node is a common node and a consensus node flag indicating that the node is a consensus node. This step is the same as step S101 shown in fig. 1.
Here, in the node flag setting step, since the initial access node has not been subjected to the computation test and the computation capability of the node is unclear, the newly accessed node is defaulted to be a normal node, and the normal node flag is set.
Optionally, before the node flag setting step, a node calculation capability testing step may be further included, where a test is performed on the accessed node, and the calculation capability level of the node is calculated according to the calculation amount of the node and the calculation time required for completing the calculation amount, that is, the calculation capability of the node is obtained. And judging whether the calculated force level reaches a preset threshold value. Setting the accessed node as a consensus node when the computation power level is greater than or equal to the threshold; and if the computing power level is less than the threshold value, setting the accessed node as a normal node. But this node effort test step is not necessary for the node access procedure.
In addition, optionally, in the process of the initial participation of the node in the accounting, the calculation process of the node is monitored, and the calculation capability level of the node is calculated according to the calculation amount and the calculation time of the node. That is, in the initial accounting participation process of the node, if the node is not monitored to calculate the computational power level or is monitored to calculate the computational power level but does not reach the set threshold value, the node can only be set as a normal node.
Here, as a common node, when receiving a block data packet of an accounting request, the node needs to actually run a calculation process until the calculation is completed and provides a calculation power demonstration to the system, and then can be used as a node for accounting at this time to store and record data. I.e. the ordinary node needs to provide proof of the workload in the accounting. And as the consensus node, the node does not need to complete the calculation process and directly store the consensus node when receiving the block data packet of the current accounting request in the accounting process, namely the consensus node does not need to provide workload certification in the accounting process. Details regarding the participation of the general node and the accounting node in accounting are described later.
FIG. 3 illustrates an identification diagram of relationships between nodes in accordance with an embodiment of the present invention.
The dotted circle shows a private chain, for example, an enterprise-level self-owned server system accessed in the form of MEC, or an edge server under a 5G system, in which 1-3 edge computing node (MEC) devices can be configured as nodes of a federation chain system, each node is composed of a separate set of MEC devices, and the set of MEC devices possesses a control system, a gateway module, and the capability of performing a large amount of complex operations and storing information. However, in the process of generating the same federation chain, more than two nodes in the same private chain cannot participate in the accounting process at the same time. The solid circles show common nodes and the dashed circles show consensus nodes. In the alliance chain system, a mesh connection system formed by several hundreds or even thousands of nodes may be formed according to the number of nodes. In the alliance chain system, mutual trust between nodes is much lower than that in a private chain, and in order to realize a credible contract transfer process formed between the nodes with the lower mutual trust, the alliance chain system needs to provide a certain workload proof. The case where the federation chain system includes the private chains and nodes shown in fig. 3 will be described as an example. For the common nodes, taking node 1 and node 2 as an example, nodes 1 and 2 belong to the same private chain, so node 1 and node 2 cannot participate in the generation of the same federation chain, and there is no connection relationship between the two nodes in the generation of the federation chain, but node 1 may be interconnected with all nodes except node 2 to participate in the generation of the federation chain, and node 2 may be interconnected with all nodes except node 1 to participate in the generation of the federation chain. The node 3 and the node 4 are consensus nodes, the two consensus nodes cannot participate in generation of the same federation chain because of belonging to the same private chain, the two nodes do not have a connection relation in generation of the federation chain, but the node 3 may be interconnected with all nodes except the node 4 to participate in generation of the federation chain, and the node 4 may be interconnected with all nodes except the node 3 to participate in generation of the federation chain. Although the other nodes 5 to 10 are not drawn out of the connection relationship, the nodes 5 to 10 are the same as the nodes 1 and 2, and are not described in detail here.
Next, returning to fig. 2, in step S203, a node management step is included, and whether to update the node flag of the node is determined based on the accounting data of the node in a fixed time and a preset threshold. After the node mark is set, the well-represented common node needs to be awarded to promote the well-represented common node to be a consensus node, meanwhile, the consensus node also needs to be supervised, and the consensus node is degraded to be the common node under the condition that a preset condition is not met. Therefore, the effective management of the nodes of the alliance chain system can be maintained, and the reliability of the alliance chain system is guaranteed.
Optionally, in the node management step, for a common node, the hardware configuration and the load state of the node are monitored and recorded in real time at a fixed frequency. For example, the monitoring node monitors data for accounting in a fixed time, and obtains accounting amount and accuracy. For example, monitoring accounting data of a common node in a period of 30 days, acquiring accounting quantity and accuracy, if the accounting quantity of the common node is 50 and is greater than a preset threshold value 40, and the common node has no error in accounting, changing the mark of the common node into a consensus node, wherein the node does not need to provide workload certification in the process of next accounting.
Optionally, in the node management step, the node management method may also monitor accounting data of the common node, obtain an accounting rate and an accuracy rate of the node, and change the node flag of the common node to a consensus node when the accounting rate of the node exceeds a preset threshold in a fixed period and there is no error.
For the node management of the common node, the node which randomly participates in the accounting has a high probability of being trusted on the premise that a large amount of workload is carried out in a time period without any error is fully considered. That is, it is a very small probability event that such a node will make a statement of an error at the next stage if a large amount of work has not been made in the last period of time. Therefore, in the management method of the alliance chain system, on the premise that the possibility of the extremely-small-probability event is extremely low, the extremely-small-probability event is trusted not to occur, the extremely-small-probability event is allowed to participate in accounting, a system with an account book placed at the node is considered to be safe, and the accounting accuracy of the node is fully trusted. The block chain system in the form of a common public chain generates a large amount of workload in the aspect of workload certification, the workload certification in the block chain is realized by calculating a hash value, each point generally needs to provide about ten minutes of workload, and the workload must be performed by a mining machine. Here, the HASH value is a cryptographic algorithm that can encrypt only and cannot decrypt, compresses a message to obtain a message digest (HASH value), and is a fingerprint for protecting metadata. Taking one point as an example, it is often necessary for the mining machine to continue the calculations and provide ten minutes of calculation power. Therefore, compared with the block chain in the form of a public chain, the semi-open alliance chain system changes the mode that the existing block chain system must participate in accounting on the premise of providing workload certification, and saves accounting time. Therefore, the calculation amount of the node self-mining machine can be reduced, the calculation force of the node is released, the load of the node is reduced, and the calculation load of the whole system can be reduced.
Likewise, optionally, supervision is also needed for the consensus node, for example, accounting data performed by the consensus node in a 30-day period is monitored, an accounting number is obtained, and if the accounting number of the consensus node is lower than a preset threshold 40, the consensus node is changed to a normal node.
In addition, optionally, for the consensus node, the consensus node may also be restored to the common node after the consensus node completes the accounting once, so that iteration of the consensus node in the federation block system can be maintained, and an increase of the consensus nodes is avoided.
Optionally, in the node management step, a node classification step may be further included. For example, a first set and a second set are set, common nodes are divided into the first set according to the node marks, and common nodes are divided into the second set. In the random selection of the accounting nodes, a plurality of nodes are randomly selected from a first set containing common nodes and a second set containing common nodes to participate in accounting, wherein 3-8 nodes are preferably selected, and the number of the selected nodes in each set is ensured to be not 0. And selecting the nodes according to the total number of the nodes participating in the accounting, the minimum number of the nodes participating in the accounting in the first set and the minimum number of the nodes participating in the accounting in the second set according to the application requirements of different industries. Therefore, effective saving of computational resources or obvious improvement of safety can be achieved, and selection of nodes from the set is facilitated when the alliance chain is generated. As described above, referring to fig. 3, in the process of creating the same federation chain, either node 3 or node 4 is necessarily included.
In step S204 of fig. 2, a billing management step is included, when the generic node participates in billing, the generic node is caused to provide a workload certification; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data.
The coalition chain system management method reduces the workload generated by coalition chain formation and ensures the reliability of the system. In addition, according to the union link system management method provided by the embodiment of the invention, the accounting time is saved. Therefore, the calculation amount of the node self-mining machine can be reduced, the calculation force of the node is released, the load of the node is reduced, and the calculation load of the whole system can be reduced.
While the federation chain management method of the present invention has been described above, for further understanding of the present invention, an example of generating a federation chain using the federation chain management method described above is described below.
FIG. 4 illustrates a flow diagram for federation chain generation. First, in step S401, contract behavior is generated between terminal a and terminal Z, and the accounting flow is started. And B, the information is decrypted by the public key provided by the A and then is compared with the encrypted hash value provided by the A, and if the information is identical, the information is confirmed to be sent by the A and is not tampered.
In step S402, a node selection step. The selection of the node is made randomly, but it contains at least one consensus node and one ordinary node. For example, 6 nodes are randomly selected from a first set containing common nodes and a second set containing common nodes to participate in accounting, and the contract original text information sent by the A is transmitted to the nodes participating in accounting in the form of encrypted character string generation data blocks.
In step S403, n-1 is set, taking the total number of nodes n-6 as an example. In step S404, it is determined whether the node is a consensus node according to the node flag. If the determination is yes, the process proceeds to step S405, and the node does not need to provide workload certification, that is, does not need to perform calculation on the received block data, but directly performs redundancy processing on the data and then stores the data. That is, the step of calculating the random number is skipped to directly record the necessary information of other blocks except the random number. Then, the process proceeds to step S407. In step S404, if the determination is no, the process proceeds to step S406, and since the node is a normal node, the node executes a calculation process and stores data if a workload certification is provided. That is, when receiving information provided by a predecessor data block after forwarding, a node calculates a random number that makes the hash value satisfy a specific condition, and records information such as the random number and a contract number after finding the random number to generate a new data block. Then, the process proceeds to step S407.
In step S407, it is determined whether or not n is 0? And if n is equal to 0, storing the data, finishing the accounting work of all the nodes and finishing the generation of the alliance chain. And in the case that n is not equal to 0, the process proceeds to step S403, and the data is forwarded to the next node, and the accounting processing of the next node is started, and the process is repeated until accounting of all nodes is completed.
The above description is directed to a federation chain system management method according to an embodiment of the present invention. According to the union link system management method, the safety of the system can be ensured by setting a strict node access management rule. In addition, according to the management method of the alliance chain system, by setting the rule that the consensus node participates in the accounting, the accounting time can be saved, meanwhile, the calculation amount of an ore machine of the node is reduced, the calculation power of the node is released, the load of the node is reduced, and the calculation load of the whole system can be reduced. In addition, according to the management method of the alliance chain system, the node is managed to update the rule of the node mark, an effective excitation system can be formed, common nodes are excited to participate in more effective calculation to become consensus nodes, and a virtuous circle is formed.
Fig. 5 is a block diagram illustrating a federation chain system management apparatus according to an embodiment of the present invention. The federation chain system management apparatus 500 shown in fig. 5 includes: a node flag setting unit 501, configured to set a node flag to a node newly accessed to the federation chain system, where the node flag includes a common node flag indicating that the node is a common node and a consensus node flag indicating that the node is a consensus node; a billing management unit 502, when the ordinary node participates in billing, causing the ordinary node to provide a workload certification; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data.
FIG. 6 illustrates a block diagram of a federation chain system provided by yet another embodiment of the present invention. The alliance chain system comprises an alliance chain system management device and nodes. As an example, the federation chain system shown in fig. 6 includes: the node access management unit 601 is configured to perform auditing on a node requesting to access the alliance chain system, and access a node that passes the auditing; a node flag setting unit 602, configured to set a consensus flag for a node accessed to the alliance chain system, where the consensus flag indicates that the node is a consensus node or a common node; a normal node 603; a consensus node 604; a node management unit 605, which determines whether to update the node flag of the node based on the accounting data of the node in a fixed time and a preset threshold; and a billing management unit 606 for making the common node provide the workload certification when the common node participates in billing; when the consensus node participates in accounting, the consensus node is enabled not to provide workload proofs and directly stores data. Node access management section 601, node flag setting section 602, node management section 605, and accounting management section 606 constitute a federation chain system management apparatus.
The operation method of each unit of the alliance chain system management device is the same as the description of the alliance chain system management method, and the description is omitted here.
Fig. 7 is a schematic diagram illustrating a hardware structure of a federation chain system management device according to an embodiment of the present invention.
The alliance chain system management device may comprise a processor 701 and a memory 702 storing computer program instructions.
Specifically, the processor 701 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured as one or more Integrated circuits implementing an embodiment of the present invention.
Memory 702 may include a mass storage for data or instructions. By way of example, and not limitation, memory 702 may include a Hard Disk Drive (HDD), a floppy Disk Drive, flash memory, an optical Disk, a magneto-optical Disk, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 702 may include removable or non-removable (or fixed) media, where appropriate. The memory 702 may be internal or external to the integrated gateway disaster recovery device, where appropriate. In a particular embodiment, the memory 702 is non-volatile solid-state memory. In a particular embodiment, the memory 702 includes Read Only Memory (ROM). Where appropriate, the ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory or a combination of two or more of these.
The processor 701 implements any of the federation chain system management methods in the embodiments described above by reading and executing computer program instructions stored in the memory 702.
In one example, the alliance chain system management device may also include a communication interface 703 and a bus 710. As shown in fig. 7, the processor 701, the memory 702, and the communication interface 703 are connected by a bus 710 to complete mutual communication.
The communication interface 703 is mainly used for implementing communication between modules, apparatuses, units and/or devices in the embodiment of the present invention.
Bus 710 comprises hardware, software, or both to couple the components of the system management device together in a federation chain. By way of example, and not limitation, a bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hypertransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus or a combination of two or more of these. Bus 710 may include one or more buses, where appropriate. Although specific buses have been described and shown in the embodiments of the invention, any suitable buses or interconnects are contemplated by the invention.
The federation chain system management device may execute the federation chain system management method in the embodiment of the present invention, so as to implement the federation chain system management method and apparatus described in conjunction with fig. 1, fig. 2, fig. 5, and fig. 6.
In addition, in combination with the federation chain system management method in the foregoing embodiment, an embodiment of the present invention may be implemented by providing a computer storage medium. The computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement any of the federation chain system management methods of the embodiments described above.
It is to be understood that the invention is not limited to the specific arrangements and instrumentality described above and shown in the drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions or change the order between the steps after comprehending the spirit of the present invention.
The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.
It should also be noted that the exemplary embodiments mentioned in this patent describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.
As described above, only the specific embodiments of the present invention are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present invention, and these modifications or substitutions should be covered within the scope of the present invention.

Claims (12)

1. A union chain system management method is characterized by comprising the following steps:
setting node marks, namely setting the node marks for nodes newly accessed to a alliance chain system, wherein the node marks comprise common node marks for indicating that the nodes are common nodes and consensus node marks for indicating that the nodes are consensus nodes; and
accounting management step, when the ordinary node participates accounting, the ordinary node provides workload certification; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data.
2. The federation chain system management method of claim 1,
the method also comprises a node computing power testing step, which tests the computing power level of the node aiming at the newly accessed node,
at the node flag setting step, the node flag is set based on whether the computation power level reaches a predetermined value.
3. The federation chain system management method of claim 1,
the method also comprises a node management step, which is used for judging whether to update the node mark of the node based on the accounting data of the node in a fixed time and a preset threshold value.
4. The federation chain system management method of claim 3,
in the node management step, the accounting number and the accuracy of the common node in a fixed period are obtained based on the accounting data, and when the accounting number and the accuracy of the common node are higher than a preset threshold value, the node mark of the common node is changed into a consensus node mark.
5. The federation chain system management method of claim 3,
in the node management step, the accounting rate and the accuracy of the common node in a fixed period are obtained based on the accounting data, and when the accounting rate and the accuracy of the common node are higher than a preset threshold value, the node mark of the common node is changed into a consensus node mark.
6. The federation chain system management method of any one of claims 3 to 5,
in the node management step, after the consensus node completes accounting, the consensus node flag of the consensus node is changed into a common node flag.
7. The federation chain system management method of any one of claims 3 to 5,
in the node management step, the accounting number of the consensus node in a fixed period is obtained based on the accounting data, and when the accounting number of the consensus node is lower than a preset threshold value, the node mark of the consensus node is changed into a common node mark.
8. The federation chain system management method of claim 1,
and a step of assigning accounting nodes, in which a predetermined number of nodes accessed to the alliance chain system are randomly assigned to participate in accounting in one accounting process, wherein the predetermined number of nodes comprise at least one common node and at least one consensus node.
9. The federation chain system management method of claim 1,
and the node access management step is also included, namely auditing the nodes which request to access the alliance chain system, and accessing the nodes which pass the auditing, wherein the nodes comprise enterprise-level self-owned server systems accessed in a mobile edge computing mode or edge servers under 5G systems.
10. An alliance chain system management apparatus, comprising:
a node flag setting unit that sets a node flag for a node newly accessed to the alliance chain system, the node flag including a common node flag indicating that the node is a common node and an consensus node flag indicating that the node is a consensus node; and
the accounting management unit enables the common node to provide workload certification when the common node participates in accounting; and when the consensus node participates in accounting, the consensus node is enabled not to provide the workload certification and directly stores the data.
11. An alliance chain system management device, wherein the device comprises: a processor and a memory storing computer program instructions;
the computer program instructions, when executed by the processor, implement a federation chain system management method as recited in any one of claims 1-9.
12. A computer storage medium having computer program instructions stored thereon that, when executed by a processor, implement a federation chain system management method as recited in any one of claims 1-9.
CN201911411172.7A 2019-12-31 2019-12-31 Alliance chain system management method, device, equipment and computer storage medium Pending CN113132430A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911411172.7A CN113132430A (en) 2019-12-31 2019-12-31 Alliance chain system management method, device, equipment and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911411172.7A CN113132430A (en) 2019-12-31 2019-12-31 Alliance chain system management method, device, equipment and computer storage medium

Publications (1)

Publication Number Publication Date
CN113132430A true CN113132430A (en) 2021-07-16

Family

ID=76770140

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911411172.7A Pending CN113132430A (en) 2019-12-31 2019-12-31 Alliance chain system management method, device, equipment and computer storage medium

Country Status (1)

Country Link
CN (1) CN113132430A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110222529A (en) * 2019-05-21 2019-09-10 平安普惠企业管理有限公司 Assets management method, electronic equipment and computer storage medium based on alliance's chain
CN110473106A (en) * 2019-08-21 2019-11-19 腾讯科技(深圳)有限公司 A kind of method and relevant apparatus of trading processing
CN110519246A (en) * 2019-08-15 2019-11-29 安徽师范大学 Based on the degree of belief calculation method for trusting block chain link point

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110222529A (en) * 2019-05-21 2019-09-10 平安普惠企业管理有限公司 Assets management method, electronic equipment and computer storage medium based on alliance's chain
CN110519246A (en) * 2019-08-15 2019-11-29 安徽师范大学 Based on the degree of belief calculation method for trusting block chain link point
CN110473106A (en) * 2019-08-21 2019-11-19 腾讯科技(深圳)有限公司 A kind of method and relevant apparatus of trading processing

Similar Documents

Publication Publication Date Title
CN110046996B (en) Data processing method and device
KR102002509B1 (en) Privite blockchain system including notarizing center and notarial method thereof
KR101937220B1 (en) Method for generating and verifying a digital signature or message authentication code based on a block chain that does not require key management
CN112288434B (en) Privacy transaction method, device, zero knowledge proof system and privacy transaction architecture model
US11251975B1 (en) Block chain based trusted security infrastructure
CN109995712B (en) Data encryption and decryption method, device, equipment and medium
CN113940032A (en) Method and apparatus for recording work history and certifying reputation in blockchain networks
CN113256297B (en) Data processing method, device and equipment based on block chain and readable storage medium
CN110661779B (en) Block chain network-based electronic certificate management method, system, device and medium
CN112527912A (en) Data processing method and device based on block chain network and computer equipment
US11477184B2 (en) Conducting secure interactions utilizing reliability information
CN111934870B (en) Method, apparatus, device and medium for updating root certificate in block chain network
US11757884B2 (en) Method and system for controlling the release of a resource
CN114503146A (en) Method and apparatus for registration and authentication of miner identity in a blockchain network
CN112235301B (en) Access right verification method and device and electronic equipment
CN114731279A (en) Method and apparatus for automatic digital certificate verification
CN114978635A (en) Cross-domain authentication method and device, and user registration method and device
CN110839002A (en) Cloud account opening, authentication and access method and device
CN113132430A (en) Alliance chain system management method, device, equipment and computer storage medium
CN112751675B (en) Information monitoring method, system, equipment and storage medium based on block chain
CN113055178B (en) Block chain system, and method, system, device and medium for transmitting numerical information
CN114154996A (en) Cross-block-chain data transfer method and system, storage medium and terminal
CN113868713A (en) Data verification method and device, electronic equipment and storage medium
US20220067727A1 (en) Method for operating a distributed database system, distributed database system, and industrial automation system
CN112688775A (en) Management method and device of alliance chain intelligent contract, electronic equipment and medium

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20210716

RJ01 Rejection of invention patent application after publication