# US 12,003,653 B2 · Method for managing consortium chain data structure network, management node, and non-transitory computer-readable recording medium > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,653 B2 - Document ID: US12003653B2 - Status: Granted - Kind: B2 - Application number: 17/348,946 - Filed: 2021-06-16 - Published: 2021-12-23 - Granted: 2024-06-04 - Earliest claimed: 2020-06-19 - Assignees: Ricoh Company, Ltd. - Applicants: Xiaojing Fan; Wei Wang; Jinting Hou - Inventors: Xiaojing Fan; Wei Wang; Jinting Hou - Web page: https://patentgrep.com/patent/US12003653B2 ## CPC - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3265: {using certificate chains, trees or paths; Hierarchical trust model} - H04L 9/3247: {involving digital signatures} - H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)} - H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)} - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method for managing a consortium chain data structure network, a management node, and a non-transitory computer-readable recording medium are provided. The consortium chain data structure network includes a first network that maintains a first chain data structure for recording management data, and a second network that maintains a second chain data structure for recording user data. A management node for management consensus of the consortium chain data structure network only accesses the first network. In the method, the management node receives a management request message sent by a requesting node, verifies the management request message, and processes the management request message in response to successful verification on the management request message. A data block in the first chain data structure is generated based on a result of the processing. ## Claims ### Claim 1 A method for managing a consortium chain data structure network, the consortium chain data structure network including a first network that maintains a first chain data structure for recording management data of the consortium chain data structure network, and a second network that maintains a second chain data structure for recording user data, the method comprising: receiving, by the management node, a management request message sent by a requesting node; verifying, by the management node, the management request message; and processing, by the management node, the management request message in response to successful verification on the management request message, wherein a data block in the first chain data structure is generated based on a result of the processing, and wherein a management node for management consensus of the consortium chain data structure network only accesses the management data of the consortium chain data structure network without accessing the user data. ### Claim 2 (depends on 1) The method for managing a consortium chain data structure network as claimed in claim 1, wherein the management node issues a node digital certificate to the requesting node in advance, and wherein verifying the management request message includes verifying, using the node digital certificate, a digital signature included in the management request message. ### Claim 3 (depends on 2) The method for managing a consortium chain data structure network as claimed in claim 2, wherein the management request message is a first network creation request message, and the first network creation request message includes a node list, and wherein processing the management request message includes generating a genesis data block of the first chain data structure based on the first network creation request message; and synchronizing the genesis data block of the first chain data structure to one or more nodes included in the node list. ### Claim 4 (depends on 3) The method for managing a consortium chain data structure network as claimed in claim 3, wherein the genesis data block includes an updated node list, and the updated node list is obtained by adding the management node to the node list included in the first network creation request message. ### Claim 5 (depends on 2) The method for managing a consortium chain data structure network as claimed in claim 2, wherein the management request message is a first network change request message, and wherein processing the management request message includes generating a first network change transaction based on the first network change request message, and broadcasting the first network change transaction in the first network; and collecting one or more feedback messages on the first network change transaction from one or more member nodes in the first network, and determining, based on the feedback messages, whether to change a member node in the first network. ### Claim 6 (depends on 5) The method for managing a consortium chain data structure network as claimed in claim 5, wherein determining whether to change the member node in the first network includes using the received feedback messages as input of a first smart contract, and wherein a data block including the first network change transaction is generated in the first chain data structure using the first smart contract, in response to determining to change the member node in the first network. ### Claim 7 (depends on 2) The method for managing a consortium chain data structure network as claimed in claim 2, wherein the management request message is a second network creation request message or a second network change request message, wherein if the management request messaue is the second network creation request message, processing the management request message includes generating a second network creation transaction based on the second network creation request message, and broadcasting the second network creation transaction in the first network; and collecting one or more feedback messages on the second network creation transaction from one or more member nodes in the first network, and determining, based on the feedback messages, whether to create a second network, and wherein if the management request message is the second network change request message, processing the management request message includes generating a second network change transaction based on the second network change request message, and broadcasting the second network change transaction in the first network; and collecting one or more feedback messages on the second network change transaction from one or more member nodes in the first network, and determining, based on the feedback messages, whether to change a member node in the second network. ### Claim 8 (depends on 7) The method for managing a consortium chain data structure network as claimed in claim 7, wherein the management node locally maintains a first network member list based on the data block in the first chain data structure, and wherein verifying the management request message further includes verifying, using the first network member list, an identity of the requesting node that sent the second network change request message. ### Claim 9 (depends on 8) The method for managing a consortium chain data structure network as claimed in claim 8, the method further comprising: using the received feedback messages as input of a second smart contract, wherein if the management request message is the second network creation request message, a data block including the second network creation transaction is generated in the first chain data structure using the second smart contract, in response to determining to create the second network, and wherein if the management request message is the second network change request message, a data block including the second network change transaction is generated in the first chain data structure using the second smart contract, in response to determining to change the member node in the second network. ### Claim 10 (depends on 9) The method for managing a consortium chain data structure network as claimed in claim 9, wherein if the management request message is the second network creation request message, the requesting node generates a genesis data block of a created second chain data structure, using the data block including the second network creation transaction that is generated in the first chain data structure. ### Claim 11 (depends on 1) The method for managing a consortium chain data structure network as claimed in claim 1, wherein a member node that accesses both the first network and the second network updates a first network member list and a second network member list that are locally maintained, and updates a second network member list maintained by a member node of the same organization that only accesses the second network, using the data block in the first chain data structure. ### Claim 12 A management node for management consensus of a consortium chain data structure network, the consortium chain data structure network including a first network that maintains a first chain data structure for recording management data of the consortium chain data structure network, and a second network that maintains a second chain data structure for recording user data, the management node comprising: a memory storing computer-executable instructions; and one or more processors configured to execute the computer-executable instructions such that the one or more processors are configured to receive a management request message sent by a requesting node; verify the management request message; and process the management request message in response to successful verification on the management request message, wherein a data block in the first chain data structure is generated based on a result of the processing, and wherein the management node only accesses the management data of the consortium chain data structure network without accessing the user data. ### Claim 13 (depends on 12) The management node as claimed in claim 12, wherein the management node issues a node digital certificate to the requesting node in advance, and wherein the one or more processors are configured to verify, using the node digital certificate, a digital signature included in the management request message. ### Claim 14 (depends on 13) The management node as claimed in claim 13, wherein the management request message is a first network creation request message, and the first network creation request message includes a node list, and wherein the one or more processors are configured to generate a genesis data block of the first chain data structure based on the first network creation request message; and synchronize the genesis data block of the first chain data structure to one or more nodes included in the node list. ### Claim 15 (depends on 14) The management node as claimed in claim 14, wherein the genesis data block includes an updated node list, and the updated node list is obtained by adding the management node to the node list included in the first network creation request message. ### Claim 16 (depends on 13) The management node as claimed in claim 13, wherein the management request message is a first network change request message, and wherein the one or more processors are configured to generate a first network change transaction based on the first network change request message, and broadcast the first network change transaction in the first network; and collect one or more feedback messages on the first network change transaction from one or more member nodes in the first network, and determine, based on the feedback messages, whether to change a member node in the first network. ### Claim 17 (depends on 16) The management node as claimed in claim 16, wherein the one or more processors are configured to use the received feedback messages as input of a first smart contract, and wherein a data block including the first network change transaction is generated in the first chain data structure using the first smart contract, in response to determining to change the member node in the first network. ### Claim 18 (depends on 13) The management node as claimed in claim 13, wherein the management request message is a second network creation request message or a second network change request message, wherein if the management request message is the second network creation request message, the one or more processors are configured to generate a second network creation transaction based on the second network creation request messaue, and broadcast the second network creation transaction in the first network; and collect one or more feedback messages on the second network creation transaction from one or more member nodes in the first network, and determine, based on the feedback messages, whether to create a second network, and wherein if the management request message is the second network change request message, the one or more processors are configured to generate a second network change transaction based on the second network change request message, and broadcast the second network change transaction in the first network; and collect one or more feedback messages on the second network change transaction from one or more member nodes in the first network, and determine, based on the feedback messages, whether to change a member node in the second network. ### Claim 19 (depends on 18) The management node as claimed in claim 18, wherein the management node locally maintains a first network member list based on the data block in the first chain data structure, and wherein the one or more processors are further configured to verify, using the first network member list, an identity of the requesting node that sent the second network change request message. ### Claim 20 A non-transitory computer-readable recording medium having computer-executable instructions for execution by one or more processors, wherein, the computer-executable instructions, when executed, cause the one or more processors to carry out a method for managing a consortium chain data structure network, the consortium chain data structure network including a first network that maintains a first chain data structure for recording management data of the consortium chain data structure network, and a second network that maintains a second chain data structure for recording user data, the method comprising: receiving, by the management node, a management request message sent by a requesting node; verifying, by the management node, the management request message; and processing, by the management node, the management request message in response to successful verification on the management request message, wherein a data block in the first chain data structure is generated based on a result of the processing, and wherein a management node for management consensus of the consortium chain data structure network only accesses the management data of the consortium chain data structure network without accessing the user data.