WO2021159606A1 - 基于区块链的组织节点上链方法和系统 - Google Patents

基于区块链的组织节点上链方法和系统 Download PDF

Info

Publication number
WO2021159606A1
WO2021159606A1 PCT/CN2020/086646 CN2020086646W WO2021159606A1 WO 2021159606 A1 WO2021159606 A1 WO 2021159606A1 CN 2020086646 W CN2020086646 W CN 2020086646W WO 2021159606 A1 WO2021159606 A1 WO 2021159606A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
organization
alliance
gateway
channel
Prior art date
Application number
PCT/CN2020/086646
Other languages
English (en)
French (fr)
Inventor
王强
Original Assignee
深圳壹账通智能科技有限公司
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 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2021159606A1 publication Critical patent/WO2021159606A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles

Definitions

  • This application relates to the field of computer technology, and in particular to a blockchain-based method and system for organizing node on-chain.
  • the alliance chain is a commonly used blockchain.
  • Consortium chain refers to a blockchain in which several organizational nodes participate in the management.
  • configuration information such as certificate information and secret keys when applying to join the alliance chain.
  • the inventor realizes that in the traditional method, after each organization node is created, the configuration information is uniformly stored in the back control platform, and the organization node after joining the alliance directly applies to join the alliance chain based on the configuration information stored in the back control platform .
  • the traditional method is very centralized management, the user's more secret information is unified in the back control platform, which will lead to poor security.
  • the present application discloses a blockchain-based method for organizing nodes on the chain, and the method includes:
  • the alliance master node on the alliance chain obtains the alliance request of the organization node to join the alliance;
  • the leader node invokes the configuration information interface of the first gateway node through the leader gateway node of the gateway layer; the first gateway node is the gateway node corresponding to the organization node;
  • the organization node obtains the configuration information of the organization node locally, and sends the configuration information to the leader gateway node through the configuration information interface, so as to return the configuration information to the leader node through the leader gateway node;
  • the leader node adds the configuration information to the system channel configuration file on the alliance chain to add the organization node to the alliance chain.
  • the present application discloses a blockchain-based system for organizing node on-chain, and the system includes:
  • the alliance master node the organization node to be joined in the alliance, the alliance master gateway node, and the first gateway node; the alliance master node is located on the alliance chain;
  • the alliance master node is used to obtain the alliance request of the organization node to be admitted into the alliance;
  • the alliance master node is further configured to call the configuration information interface of the first gateway node through the alliance master gateway node of the gateway layer in response to the alliance request;
  • the first gateway node is the gateway node corresponding to the organization node;
  • the organization node is configured to obtain configuration information of the organization node locally, and send the configuration information to the leader gateway node through the configuration information interface, so as to return the configuration information to the leader node through the leader gateway node;
  • the leader node is also used to add the configuration information to the system channel configuration file on the alliance chain, so as to add the organization node to the alliance chain.
  • the present application discloses a computer device including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, wherein the processor implements the computer program when the computer program is executed.
  • the above-mentioned method for blockchain-based organization node on-chain wherein the method at least includes: the alliance master node on the alliance chain obtains an alliance request of the organization node to join the alliance; the alliance leader node responds to the alliance Request, call the configuration information interface of the first gateway node through the leader gateway node of the gateway layer; the first gateway node is the gateway node corresponding to the organization node; the organization node obtains the configuration information of the organization node locally, And send the configuration information to the leader gateway node through the configuration information interface to return the configuration information to the leader node through the leader gateway node; the leader node adds the configuration information to the alliance In the system channel configuration file on the chain to add the organization node to the alliance chain.
  • the present application discloses a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to execute the aforementioned region-based A blockchain organization node uploading method, wherein the method at least includes: the alliance master node on the alliance chain obtains an alliance request of the organization node to join the alliance; the alliance master node responds to the alliance request through the gateway layer
  • the leader gateway node calls the configuration information interface of the first gateway node; the first gateway node is the gateway node corresponding to the organization node; the organization node obtains the configuration information of the organization node locally, and uses the configuration
  • the information interface sends the configuration information to the leader gateway node to return the configuration information to the leader node through the leader gateway node; the leader node adds the configuration information to the system channel on the alliance chain In the configuration file to add the organization node to the alliance chain.
  • the configuration information of the organization node is equivalent to being stored locally in the organization node.
  • the interface is called to obtain the configuration information stored locally in the organization node, so that the organization node can be added to the alliance chain. Since the configuration information is stored locally in the organization node, compared with the centralized management of the traditional method, the security is improved.
  • Fig. 1 is an application scenario diagram of a blockchain-based method for organizing a node on-chain in an embodiment
  • FIG. 2 is a schematic flowchart of a method for organizing a node on-chain based on a blockchain in an embodiment
  • FIG. 3 is a schematic diagram of the principle of a blockchain-based method for organizing a node on-chain in an embodiment
  • FIG. 4 is a block diagram of a blockchain-based organization node on-chain system in an embodiment
  • FIG. 5 is a block diagram of a blockchain-based organization node on-chain system in another embodiment
  • Figure 6 is a block diagram of a computer device in one embodiment.
  • the blockchain-based method for organizing nodes on the chain provided in this application can be applied to the application environment as shown in FIG. 1.
  • the application scenario includes the leader node 110, the new organization node 120 to be joined in the alliance, the leader gateway node 130, and the first gateway node 140 corresponding to the organization node 120 at the gateway layer.
  • the leader gateway node 130 and the first gateway node 140 are both located at the gateway layer.
  • the leader node 110 is an organization node in the leader position on the alliance chain. That is, the leader node 110 has all the permissions of the system and is used to realize the management of the entire alliance chain.
  • the leader node 110 and the organization node 120 may communicate through an interface provided between the leader gateway node 130 and the first gateway node 140.
  • the alliance master node 110 on the alliance chain obtains the alliance request of the organization node 120 to be admitted into the alliance.
  • the leader node 110 invokes the configuration information interface of the first gateway node 140 through the leader gateway node 130 at the gateway layer; the first gateway node 140 is the gateway node corresponding to the organization node 120.
  • the organization node 120 obtains the configuration information of the organization node 120 locally, and sends the configuration information to the leader gateway node 130 through the configuration information interface of the first gateway node 140, so as to return the configuration information to the leader node 110 through the leader gateway node 130. information.
  • the leader node 110 adds the configuration information to the system channel configuration file on the alliance chain to add the organization node 120 to the alliance chain.
  • a blockchain-based method for organizing nodes on-chain is provided, and the method specifically includes the following steps:
  • S202 The alliance master node on the alliance chain obtains an alliance request of an organization node to be admitted into the alliance.
  • the consortium chain refers to a blockchain in which several organizational nodes participate in the management.
  • the leader node of the alliance is an organization node in a global management position on the alliance chain. That is, the leader node has all the permissions of the system and is used to realize the management of the entire alliance chain.
  • the organization node to be joined in the alliance is the organization node to be added to the alliance chain.
  • a request to join the alliance is a request to join the alliance chain.
  • the organization node that has joined the alliance can actively send an alliance request to the alliance master node, or after receiving the invitation of the alliance chain, send the alliance request to the alliance master node through other devices.
  • the method further includes: the leader node of the alliance sends an invitation to join the alliance to the management terminal corresponding to the organization node; the invitation to join the alliance includes the alliance link and the organization verification code.
  • step S202 includes: when the alliance accession link is triggered, the management terminal displays the alliance application interface; the management terminal obtains the entered organization verification code through the alliance application interface, and when the alliance access trigger operation is detected, Send an alliance request for the organization node to the alliance master node; the alliance request includes the organization verification code; the alliance master node responds to the alliance request after verifying the organization verification code.
  • the invitation to join the alliance is used to invite the organization node to join the alliance chain.
  • the membership invitation may be membership invitation email. It is understandable that the invitation to join the alliance can also be in the form of short messages or instant messaging messages. It is understandable that alliance chain information may also be included in the invitation to join the alliance.
  • the joining link is the link address used to jump to the joining application interface.
  • the organization verification code is the verification code used by the organization node to apply for joining the alliance chain. It can be understood that the organization verification code is used to indicate that the organization node to be joined has the authority to join the alliance chain, and therefore, has the authority to call the alliance master gateway node to execute the process of joining the alliance chain.
  • the alliance master node may send an invitation email to the management terminal corresponding to the organization node.
  • the administrator using the management terminal can trigger the joining link by clicking or long-pressing, etc., to jump to the joining application interface provided by the back-end control platform (ie, back-end control platform).
  • the administrator can enter the organization verification code in the alliance application interface and perform the alliance trigger operation.
  • the management terminal detects the alliance trigger operation, it sends the alliance master node an alliance request for the organization node.
  • the organization verification code is included in the membership request.
  • the organization node to be joined can more conveniently initiate the request for joining the alliance, and the distribution of the organization verification code can be
  • the subsequent invocation of the configuration information interface provides a basis for authentication and improves security.
  • the administrator when the administrator has not created a blockchain organization on the back-control platform, he can create a new blockchain organization node on the login interface of the back-control platform, that is, the organization node to join the alliance, and then initiate the Organization node's membership request.
  • the leader node of the alliance invokes the configuration information interface of the first gateway node through the leader gateway node of the gateway layer; the first gateway node is the gateway node corresponding to the organization node.
  • the leader gateway node is the gateway node corresponding to the leader node at the gateway layer. It can be understood that the leader gateway node and the first gateway node respectively provide the leader node and the organization node with interfaces for docking with other organization nodes.
  • the configuration information interface is an interface used to obtain the configuration information of the organization node that is to join the alliance.
  • the leader administrator can click to agree.
  • the leader node of the alliance can then trigger the leader gateway node of the gateway layer to call the configuration information interface provided by the first gateway node.
  • the first gateway node After detecting that the configuration information interface is called, the first gateway node notifies the calling request to the organization node that is to join the alliance.
  • the leader node of the alliance may send the organization verification code to the first gateway node for storage through the leader gateway node of the alliance. It can be understood that the first gateway node may store the organization verification code in the configuration file.
  • step S204 includes: invoking the configuration information interface of the first gateway node through the leader gateway node of the gateway layer, and using the input organization verification code as the interface input parameter; the first gateway node will serve as the interface input parameter The organization verification code is compared with the locally stored organization verification code, and when the comparison is consistent, the leader gateway node successfully invokes the configuration information interface of the first gateway node.
  • the leader node invokes the configuration information interface of the first gateway node through the leader gateway node, it can use the organization verification code entered when initiating the alliance request as the interface input parameter, and the first gateway node can verify the locally stored organization The code is compared with the organization verification code entered as the interface parameter for consistency. When the comparison is consistent, the leader gateway node can successfully call the configuration information interface of the first gateway node. When the comparison is inconsistent, the leader gateway node of the alliance fails to call the configuration information interface of the first gateway node.
  • the configuration information interface of the first gateway node is called, the organization verification code is verified and authenticated, which can improve security.
  • leader gateway node of the leader can locate the configuration information interface of the first gateway node according to the address of the configuration information interface of the first gateway node, and call it.
  • the leader node of the alliance may also assign a unique communication encryption salt value to the organization node that is to join the alliance, and the leader gateway node of the alliance may send the encrypted salt value of the communication to the first gateway node, and the first gateway node may send The encrypted salt value of the communication is also stored.
  • the communication encryption salt value is used to encrypt and sign the data transmitted by the first gateway node.
  • Table 1 is an example of organization verification code and communication encryption salt value.
  • the organization node obtains the configuration information of the organization node locally, and sends the configuration information to the leader gateway node through the configuration information interface, so as to return the configuration information to the leader node through the leader gateway node.
  • the configuration information of the organization node is pre-stored in the local configuration file of the organization node. It should be noted that the local area of the organization node and the local area of the first gateway node are not at the same location.
  • the configuration information of the organization node includes certificate information and organization information. It can be understood that the configuration information of the organization node also includes other configuration information, such as secret keys and other information.
  • the configuration file (configtx.yaml) of the organization node is the basic file used to create the organization node. It can be understood that the organization node is created based on these configuration files. After the organization node is created, the configuration file of the organization node is stored locally on the organization node.
  • the calling request will be notified to the organization node that is to join the alliance.
  • the organization node obtains the configuration information of the organization node from the locally stored configuration file, and sends the configuration information to the leader gateway node through the configuration information interface, so as to return the configuration information of the organization node to the leader node through the leader gateway node.
  • the organization node may obtain organization information and certificate information of the organization node from a locally stored configuration file, and then generate configuration information of the organization node according to the organization information and certificate information.
  • the organization node to be joined in the alliance may obtain the communication encryption salt value from the first gateway node to add salt to the generated configuration information and sign it. Then, the organization node to be joined into the alliance can connect to the interface provided by the alliance master gateway node through the configuration information interface of the first gateway node of the gateway layer, and return the salted and signed configuration information to the alliance master node.
  • the leader node of the alliance adds the configuration information to the system channel configuration file on the alliance chain to add the organization node to the alliance chain.
  • the leader node of the alliance can decrypt the obtained configuration information after the salted signature according to the correspondingly assigned communication encryption salt value for the organization node to be joined to obtain the organization information and the organization node of the organization node to be joined.
  • Configuration information such as certificate information.
  • the leader node of the alliance can add the decrypted configuration information to the system channel configuration file and sign it, so that the organization node to be joined into the alliance can be added to the alliance chain.
  • the signature is based on the characteristics of the blockchain.
  • you want to change the information in the system channel configuration file you must sign, indicating that it is not tampered with by an illegal user.
  • the leader node of the alliance may parse the configuration file in the compiled format in the system channel configuration file, and convert the format into a character string. Further, the leader node of the alliance may add the configuration information of the organization node to be joined into the character string, and reverse-transform the added character string into a format existing in the system channel configuration file. Further, the information is signed, and based on this signature, the configuration information of the organization node to be joined into the alliance is updated to the system channel configuration file on the alliance chain.
  • the configuration information converted into the protobuffer format is updated to the system channel configuration file on the alliance chain, so as to realize the update of the configuration information of the organization node to be joined to the system channel configuration file on the alliance chain.
  • Fig. 3 is a schematic diagram of the principle of a blockchain-based method for organizing a node on-chain in an embodiment.
  • the leader node of the alliance sends an invitation to join the alliance, generates the content of the invitation, the link to join the alliance, and the organization verification code, and then sends the invitation email to the organization administrator using the management terminal by email.
  • the organization administrator clicks on the joining link, registers or logs in to the post-control platform to jump to the joining application page.
  • the leader node of the alliance may dock and call the configuration information interface provided by the first gateway node through the interface of the leader gateway node to obtain configuration information from the local configuration file of the organization node to be joined in the alliance. After obtaining the configuration information, the leader node of the alliance can add the configuration information to the system channel configuration file on the alliance chain to add the organization node to the alliance chain.
  • the configuration information of the organization node is equivalent to being stored locally in the organization node.
  • the alliance master node receives the alliance request of the organization node to join the alliance, it is called through the gateway layer interface.
  • the gateway layer interface To obtain the configuration information stored locally in the organization node, so as to add the organization node to the alliance chain. Since the configuration information is stored locally in the organization node, compared with the centralized management of the traditional method, the security is improved.
  • obtaining the configuration information of the organization node through the gateway layer can quickly add a new organization node to the alliance chain.
  • the organization node after joining the alliance also needs to join an existing channel or create a channel by itself.
  • channels are used to implement data communication and interactive processing between organizational nodes on the alliance chain. Interaction can be realized between organization nodes in the same channel, but interaction between organization nodes in different channels cannot be realized.
  • the method further includes: after the organization node after joining the alliance chain receives the channel joining request for the target channel, forwarding the channel joining request to the target organization node that created the target channel; In response to the channel joining request, the target organization node invokes the interface of the leader gateway node according to the second gateway node corresponding to the target organization node, so as to obtain the organization by calling the configuration information interface by the leader gateway node Configuration information of the node; the target organization node adds the configuration information of the organization node to the application channel configuration file to add the organization node to the target channel.
  • the target channel is an existing channel that is requested to join.
  • the target organization node is the organization node that creates the target channel.
  • Channel join request used to request to join the channel.
  • the second gateway node is the gateway node corresponding to the target organization node at the gateway layer. It can be understood that the target organization node can exchange data with other organization nodes through the interface provided by the second gateway node.
  • the management terminal can send a channel joining request for the target channel to the organization node after joining the alliance.
  • the organization node can forward the channel joining request to the target organization node that created the target channel.
  • the target organization node may present the channel joining request to the administrator of the target organization node through the corresponding management terminal.
  • the administrator of the target organization node can click to agree or refuse to join.
  • the target organization node receives the instruction to agree to join, it can call the interface of the leader gateway node by calling the corresponding second gateway node, and call the configuration information interface of the first gateway node through the leader gateway node to obtain the organization that has joined the alliance.
  • the configuration information of the node is not limited to negotiate the network.
  • the organization node after joining the alliance can automatically generate an interface authentication verification code and store it in the first gateway node as a basis for subsequent interface authentication.
  • the channel joining request will also carry the generated interface authentication verification code and the address of the first gateway node.
  • the target organization node after the target organization node receives the instruction to agree to join, it can find the first gateway node according to the address of the first gateway node carried in the channel joining request, and perform authentication according to the interface authentication verification code to request Invoke the configuration information interface provided by the first gateway node.
  • the first gateway node can perform authentication processing on the interface authentication verification code carried when the request is invoked according to the stored interface authentication verification code. After the authentication is passed, the configuration information interface of the first gateway node can be successfully invoked.
  • the target organization node after obtaining the configuration information of the organization node after joining the alliance, adds the configuration information of the organization node after joining the alliance to the application channel configuration file, and signs the changes to the application channel configuration file. Add the organization node to the target channel.
  • the target organization node when an organization node applies to join a target channel, the target organization node can uniformly call the interface at the gateway layer through the leader gateway node to obtain the configuration information of the organization node, without the need for docking between the organization nodes, which improves safety.
  • the unified docking of the alliance master gateway node greatly reduces the complexity compared with the docking between nodes of different organizations, thus improving efficiency and reducing resource consumption.
  • the organization node after joining the alliance may also create a channel by itself. It can be understood that the organization node after joining the alliance is the organization node to be joined before joining the alliance chain.
  • the method further includes: when the organization node receives the channel creation request including the organization identifier of the channel member organization node, calling the channel profile interface of the alliance master gateway node through the first gateway node to pass the channel configuration file interface of the leader gateway node.
  • the league master gateway node locates the member gateway node corresponding to each channel member organization node according to each of the organization identifiers, and obtains the configuration information of each channel member organization node by calling the configuration information interface of each member gateway node; the league master gateway The node returns the configuration information of each channel member organization node to the organization node by calling the channel creation interface of the first gateway node; the organization node creates a channel according to the configuration information of each channel member organization node .
  • the channel creation request is used to request the creation of a channel.
  • the channel member organization node is an organization node that is a member of the channel to be created.
  • Organization ID used to uniquely identify the organization node.
  • the member gateway node is the gateway node corresponding to the channel member organization node at the gateway layer. It can be understood that the channel member organization node can exchange data with other organization nodes through the interface provided by the member gateway node.
  • the channel profile interface is an interface used to obtain a configuration file for creating a channel, that is, equivalent to an interface used to obtain configuration information of a channel member organization node that creates a channel.
  • each member gateway node is used to provide configuration information of the corresponding channel member organization node.
  • the channel creation interface is an interface used to create a channel.
  • the administrator of the organization node after joining the alliance enters or selects the channel member organization node through the management terminal to perform the channel creation operation.
  • the management terminal can obtain the organization ID of the channel member organization node, and generate the channel member organization node including the channel member organization node.
  • the channel creation request of the organization ID is sent to the organization node.
  • the organization node after joining the alliance receives the channel creation request, it calls the channel configuration file interface of the alliance master gateway node through the first gateway node to locate the corresponding channel member organization node through the alliance master gateway node according to each organization identifier
  • the member gateway node of each member gateway node and obtain the configuration information of each channel member organization node by calling the configuration information interface of each member gateway node.
  • the alliance master gateway node returns the configuration information of each channel member organization node to the organization node after joining the alliance by calling the channel creation interface of the first gateway node; the organization node after joining the alliance is based on the Each channel member organizes node configuration information and creates a channel.
  • the configuration information of each channel member organization node is obtained uniformly through the leader gateway node at the gateway layer, which improves security and improves processing efficiency. In turn, the efficiency of channel creation is improved.
  • the method further includes: the organization node after joining the alliance obtains alliance chain role information from the alliance chain, and determines the role of the organization node according to the alliance chain role information; when the role of the organization node When it is the coordinator of the alliance chain, the step of calling the channel profile interface of the alliance master gateway node through the first gateway node is executed.
  • the role information of the alliance chain is the role and corresponding authority of each organization node recorded on the alliance chain.
  • the leader node of the alliance can control the permissions based on role granularity for the behavior of each organization node on the alliance chain.
  • Roles can include three roles: leader, consortium chain coordinator, and consortium chain participant.
  • the leader is the super administrator.
  • the core organizer of the alliance he can call all the services of the organization's gateway nodes and its own gateway interface services.
  • Consortium chain coordinator a relatively large organization node, an organization node with credibility, mainly as a channel manager, and can be directly designated by the leader.
  • the alliance chain coordinator in the authority control of the role, when the alliance chain coordinator is creating the alliance chain, it can be the channel manager and can directly call the channel creation related interface service of the alliance master gateway node.
  • an organization node after joining the alliance creates a channel, it can locate the fields corresponding to the role information of the alliance chain from the alliance chain, and obtain the role information of the alliance chain from the alliance chain according to these fields. Further, the organization node after joining the alliance can search for the role corresponding to the organization node after joining the alliance from the role information of the alliance chain according to its own organization name.
  • the organization node after joining the alliance can analyze whether there is the configuration information of the channel member organization node to be added in the local configuration file. If so, create a channel configuration file directly. If not, the configuration information of the channel member organization node exists, call the interface of the alliance master gateway node to obtain the channel configuration file, that is, execute the step of calling the channel configuration file interface of the alliance master gateway node through the first gateway node. It can be understood that in other embodiments, the organization node after joining the alliance may directly call the interface of the alliance master gateway node to obtain the channel configuration file.
  • the organization node after joining the alliance can also obtain the communication encryption salt value from the first gateway node before calling the interface of the alliance master gateway node, and according to the communication encryption salt value, the name of the channel to be created and the channel include The organization ID of the channel member organization node is encrypted, and the encrypted signature result is obtained. Then, according to the organization verification code of the organization node after joining the alliance, the name of the channel to be created and the encrypted signature result as input parameters (ie, the interface input parameters), the interface of the alliance master gateway node is called to request the channel configuration file.
  • the leader gateway node After the leader gateway node receives the call request, it can parse the organization verification code from the input parameters, verify whether a legal organization exists (ie, perform identity verification), and find out the corresponding communication encryption salt value.
  • the encrypted signature included in the input parameters is subjected to signature verification to prevent the input parameters from being tampered with (that is, to perform parameter tamper-proof verification).
  • signature verification After the identity verification and the parameter tamper-proof verification are passed, related services are called to generate a channel configuration file and return to the first gateway node, and the first gateway node creates a channel based on the obtained channel configuration file.
  • the channel configuration file includes the name of the channel to be created, the name of the channel to be created, the organization information of the channel member organization node contained in the channel, and the corresponding certificate information.
  • the management and control of the role authority dimension is taken into consideration, and the role of the organization node is determined from the alliance chain. Different roles perform different processing when creating channels, which improves security.
  • the method further includes: when the role of the organization node is a consortium chain participant, obtaining the gateway node service address corresponding to each organization identifier returned by the leader gateway node; the organization node passes The first gateway node accesses each of the gateway node service addresses to locate each member gateway node, and calls the channel creation authorization interface provided by each member gateway node to request each channel member organization node to authorize the channel creation request; each The channel member organization node sends an authorization notification to the leader gateway node through each member gateway node; the leader gateway node generates a channel creation token after receiving authorization notifications sent by all member gateway nodes, and sends the channel creation token to The first gateway node; the channel creation token is used to signify that the organization node has channel creation authority; the first gateway node executes the call to the leader through the first gateway node according to the channel creation token The steps of the gateway node's channel profile interface.
  • the gateway node service address is used to locate the corresponding gateway node of each organization node at the gateway layer. It can be understood that the gateway node service address corresponding to the organization identifier of each channel member organization node is used to locate the member gateway node corresponding to each channel member organization node.
  • the channel creation authorization interface is an interface used to authorize the creation of a channel.
  • the channel creation token is a credential that can create a channel and is used to signify that the organization node has the channel creation authority, that is, it means that all channel member organization nodes agree to the organization node after joining the alliance to create the channel.
  • the leader gateway node when the role of the organization node after joining the alliance is a participant of the alliance chain, it will forward the channel creation request to the leader gateway node. After receiving the channel creation request, the leader gateway node can return the channels included in the requested channel. The organization ID of the member organization node, and the service address of the gateway node corresponding to each organization ID is obtained. The leader gateway node of the alliance may return the obtained gateway node service address to the organization node after joining the alliance.
  • the organization node accesses each of the gateway node service addresses through the first gateway node to locate each member gateway node, and calls the channel creation authorization interface provided by each member gateway node to request each channel member organization node to The channel creation request is authorized.
  • the administrator corresponding to each channel member organization node can perform an authorization operation, and each channel member organization node can send an authorization notification to the leader gateway node through the corresponding member gateway node.
  • Each league master gateway node can count the authorization notifications returned by each member gateway node. When the league master gateway node receives authorization notifications sent by all member gateway nodes, it generates a channel creation token, and sends the channel creation token to the The first gateway node.
  • the channel creation token is used to signify that the organization node has channel creation authority.
  • the first gateway node may create a token according to the channel, and execute the step of invoking the channel profile interface of the leader gateway node through the first gateway node, so as to locate each channel through the leader gateway node according to the organization identifiers.
  • the member gateway node corresponding to the member organization node obtains the configuration information of each channel member organization node by calling the configuration information interface of each member gateway node.
  • the leader gateway node of the leader returns the configuration information of each channel member organization node to the organization node by calling the channel creation interface of the first gateway node.
  • the organization node after joining the alliance can create a channel according to the configuration information of each channel member organization node.
  • the organization node after joining the alliance can use the communication encryption salt value to perform the organization verification code, the channel name to be created, and the organization identification (such as the organization name) of the channel member organization node before calling the alliance master gateway node. Encrypted signature to get the encrypted signature result.
  • the organization node can use the organization verification code, the name of the channel to be created, and the organization ID of the channel member organization node as input parameters, and send a channel creation request to the alliance master gateway node.
  • Each league master gateway node can splice the organization verification code, the name of the channel to be created, and the organization ID of the channel member organization node, and encrypt the spliced string to generate the channel ID to be created, and combine the channel ID to be created, And the gateway node service address corresponding to the organization identifier of the channel member organization node is returned to the first gateway node.
  • the service address of the gateway node of the organization node org2 http://xxx.xx.xx/baasorg/orderer/orggateway/list/.
  • the organization node accesses each of the gateway node service addresses through the first gateway node to locate each member gateway node, and uses the channel identifier to be created, the organization verification code, the channel name to be created, and the encrypted signature result as input parameters, and calls
  • the channel creation authorization interface provided by each member gateway node requests each channel member organization node to authorize the channel creation request.
  • Each member gateway node can initiate a verification request to the alliance master gateway node to verify whether the organization verification code exists and whether the encrypted signature result is true and valid. After the above verifications are passed, it will trigger the generation to the management terminal corresponding to the channel member organization node Workflow to allow administrators to review authorization.
  • each channel member organization node sends an authorization notification to the alliance master gateway node through the member gateway node.
  • the leader gateway node can record the authorization notification, and generate a channel creation token after receiving the authorization notification sent by all member gateway nodes.
  • each channel member organization node is requested to authorize the channel creation request, and the leader gateway node uniformly records the authorization notification.
  • the leader gateway node allocates a channel creation token for the organization node, and then creates a token based on the channel, and uses the channel configuration file interface of the leader gateway node to create the channel, which improves security.
  • a blockchain-based organization node on-chain system 400 is provided.
  • the system includes: an alliance master node 402, an organization node to be joined 404, an alliance master gateway node 406, and a first gateway node 408 ;
  • the alliance master node 402 is located on the alliance chain;
  • the alliance master node 402 is used to obtain the alliance request of the organization node 404 to be admitted into the alliance.
  • the leader node 402 is also used to call the configuration information interface of the first gateway node 408 through the leader gateway node 406 of the gateway layer in response to the request to join the alliance; the first gateway node 408 is used by the organization node 404 Corresponding gateway node.
  • the organization node 404 is used to obtain the configuration information of the organization node 404 locally, and send the configuration information to the leader gateway node 406 through the configuration information interface, so as to return to the leader node 402 through the leader gateway node 406.
  • the configuration information is used to obtain the configuration information of the organization node 404 locally, and send the configuration information to the leader gateway node 406 through the configuration information interface, so as to return to the leader node 402 through the leader gateway node 406.
  • the configuration information is used to obtain the configuration information of the organization node 404 locally, and send the configuration information to the leader gateway node 406 through the configuration information interface, so as to return to the leader node 402 through the leader gateway node 406.
  • the leader node 402 is also used to add the configuration information to the system channel configuration file on the alliance chain, so as to add the organization node 404 to the alliance chain.
  • system 400 further includes: a management terminal 405;
  • the alliance master node 402 is also used to send an alliance invitation to the management terminal 405 corresponding to the organization node 404; the alliance invitation includes an alliance link and an organization verification code.
  • the management terminal 405 When the union membership link is triggered, the management terminal 405 is used to display the union membership application interface; obtain the input organization verification code through the union membership application interface, and when the union membership trigger operation is detected, send to the union
  • the alliance master node 402 sends an alliance request for the organization node 404; the alliance request includes the input organization verification code.
  • the leader node 402 is also used to send the organization verification code to the first gateway node 408 through the leader gateway node 406 for storage; call the first gateway node through the leader gateway node 406 of the gateway layer
  • the configuration information interface of 408, and the input organization verification code is used as the interface input parameter.
  • the first gateway node 408 is also used to compare the organization verification code entered as an interface parameter with the locally stored organization verification code. When the comparison is consistent, the leader gateway node 406 successfully invokes the first gateway. The configuration information interface of the node 408.
  • the system 400 further includes a management terminal 405, a target organization node 410, and a second gateway node 412;
  • the organization node 404 is further configured to, after receiving the channel joining request for the target channel, forward the channel joining request to the target organization node 410 that created the target channel.
  • the target organization node 410 is configured to, in response to the channel joining request, call the interface of the leader gateway node 406 according to the second gateway node 412 corresponding to the target organization node 410, so as to call the leader gateway node 406 through the leader
  • the configuration information interface obtains the configuration information of the organization node 404.
  • the target organization node 410 is also used to add the configuration information of the organization node 404 to an application channel configuration file, so as to add the organization node 404 to the target channel.
  • the organization node 404 is further configured to, when receiving a channel creation request that includes the organization identifier of the channel member organization node, call the channel profile interface of the leader gateway node 406 through the first gateway node 408 to pass all the channels.
  • the alliance master gateway node 406 locates the member gateway node corresponding to each channel member organization node according to each of the organization identifiers, and obtains the configuration information of each channel member organization node by calling the configuration information interface of each member gateway node.
  • the leader gateway node 406 is further configured to return the configuration information of each channel member organization node to the organization node 404 by calling the channel creation interface of the first gateway node 408.
  • the organization node 404 is also used to create a channel according to the configuration information of each channel member organization node.
  • the organization node 404 is also used to obtain alliance chain role information from the alliance chain, and determine the role of the organization node 404 according to the alliance chain role information; when the role of the organization node 404 is In the case of the alliance chain coordinator, the step of calling the channel profile interface of the alliance master gateway node 406 through the first gateway node 408 is executed.
  • the organization node 404 is also used to obtain the gateway node service address corresponding to each organization identifier returned by the leader gateway node 406 when the role of the organization node 404 is a consortium chain participant;
  • the organization node 404 accesses the service address of each gateway node through the first gateway node 408 to locate each member gateway node, and calls the channel creation authorization interface provided by each member gateway node to request each channel member organization node to The channel creation request is authorized.
  • Each channel member organization node sends an authorization notification to the leader gateway node 406 through each member gateway node; the leader gateway node 406 generates a channel creation token after receiving the authorization notifications sent by all member gateway nodes, and sends the channel creation command
  • the card is sent to the first gateway node 408; the channel creation token is used to indicate that the organization node 404 has channel creation authority.
  • the first gateway node 408 creates a token according to the channel, and executes the step of calling the channel profile interface of the leader gateway node 406 through the first gateway node 408.
  • a computer device is provided.
  • the computer device may be any of the leader node 110 in FIG. 1, the new organization node 120 to be joined, the leader gateway node 130, and the first gateway node 140 in FIG. A device.
  • the internal structure diagram can be shown in Figure 6.
  • the computer equipment includes a processor, a memory, and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide calculation and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium stores an operating system and a computer program.
  • the internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection.
  • the computer program is executed by the processor to realize a blockchain-based method for organizing nodes on the chain, wherein the method includes: the alliance master node on the alliance chain obtains an alliance request of the organization node to join the alliance; In response to the alliance request, the leader node invokes the configuration information interface of the first gateway node through the leader gateway node of the gateway layer; the first gateway node is the gateway node corresponding to the organization node; the organization node obtains it locally The configuration information of the organization node, and send the configuration information to the leader gateway node through the configuration information interface, so as to return the configuration information to the leader node through the leader gateway node; the leader node sends the configuration information to the leader node The configuration information is added to the system channel configuration file on the alliance chain to add the organization node to the alliance chain.
  • FIG. 6 is only a block diagram of part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied.
  • the specific computer device may Including more or fewer parts than shown in the figure, or combining some parts, or having a different arrangement of parts.
  • a computer device including a memory and a processor, the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the blockchain-based method for organizing node on-chain .
  • the steps of the blockchain-based method for organizing a node on-chain may be the steps in the blockchain-based method for organizing a node on-chain in each of the above embodiments. It should be noted that the blockchain-based method for organizing node uploading in each of the above embodiments can be completed by multiple computer devices in cooperation.
  • a computer-readable storage medium is provided.
  • the computer-readable storage medium may be non-volatile or volatile.
  • the computer-readable storage medium stores a computer program. When executed by the processor, the processor is caused to execute the steps of the blockchain-based method for organizing node on-chain.
  • the steps of the blockchain-based method for organizing a node on the chain may be the steps in the blockchain-based method for organizing a node on the chain in each of the above embodiments, wherein the method includes: the leader node on the alliance chain obtains the waiting node The alliance request of the organization node that has joined the alliance; the alliance master node calls the configuration information interface of the first gateway node through the alliance master gateway node of the gateway layer in response to the alliance request; the first gateway node is the organization node Corresponding gateway node; the organization node obtains the configuration information of the organization node locally, and sends the configuration information to the leader gateway node through the configuration information interface, so as to return to the leader node through the leader gateway node The configuration information; the alliance master node adds the configuration information to the system channel configuration file on the alliance chain to add the organization node to the alliance chain.
  • Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请涉及一种基于区块链的组织节点上链方法和系统，该方法包括：联盟链上的盟主节点获取待入盟的组织节点的入盟请求；所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过盟主网关节点向盟主节点返回所述配置信息；所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。采用本方法能够提高安全性。

Description

基于区块链的组织节点上链方法和系统
本申请要求于2020年2月11日提交中国专利局、申请号为202010087063.0，发明名称为“基于区块链的组织节点上链方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种基于区块链的组织节点上链方法和系统。
背景技术
随着区块链技术的飞速发展，区块链的类型越来越多。联盟链即为一种常用的区块链。联盟链是指有若干个组织节点共同参与管理的区块链。随着业务的发展，后续还会有新的组织节点需要加入联盟链，新的组织节点在申请加入联盟链时，需要提供证书信息和秘钥等配置信息。
发明人意识到，在传统方法中，各组织节点创建后，配置信息都是统一存放在后控平台中，入盟后的组织节点根据该后控平台中存放的配置信息，直接申请加入联盟链。显然，传统方法很中心化管理，用户比较秘密的信息都统一放在后控平台中，会导致安全性比较差。
发明内容
基于此，有必要针对上述技术问题，提供一种能够提高安全性的基于区块链的组织节点上链方法和系统。
第一方面，本申请公开一种基于区块链的组织节点上链方法，所述方法包括：
联盟链上的盟主节点获取待入盟的组织节点的入盟请求；
所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；
所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过盟主网关节点向盟主节点返回所述配置信息；
所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
第二方面，本申请公开一种基于区块链的组织节点上链系统，所述系统包括：
盟主节点、待入盟的组织节点、盟主网关节点、以及第一网关节点；所述盟主节点位于联盟链上；
所述盟主节点，用于获取待入盟的所述组织节点的入盟请求；
所述盟主节点还用于响应于所述入盟请求，通过网关层的所述盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；
所述组织节点，用于从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过盟主网关节点向盟主节点返回所述配置信息；
所述盟主节点还用于将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
第三方面，本申请公开一种计算机设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现上述一种基于区块链的组织节点上链方法，其中，所述方法至少包括：联盟链上的盟主节点获取待入盟的组织节点的入盟请求；所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加 入所述联盟链。
第四方面，本申请公开一种计算机可读存储介质，其中，所述计算机可读存储介质存储有计算机程序，所述计算机程序当被处理器执行时使所述处理器执行上述一种基于区块链的组织节点上链方法，其中，所述方法至少包括：联盟链上的盟主节点获取待入盟的组织节点的入盟请求；所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
上述基于区块链的组织节点上链方法和系统中，组织节点的配置信息相当于存储在组织节点的本地，盟主节点在接收到待入盟的组织节点的入盟请求后，通过网关层的接口调用，来获取存储在组织节点本地的配置信息，从而将该组织节点加入联盟链。由于配置信息存储在组织节点的本地，相较于传统方法的集中化管理而言，提高了安全性。
附图说明
图1为一个实施例中基于区块链的组织节点上链方法的应用场景图；
图2为一个实施例中基于区块链的组织节点上链方法的流程示意图；
图3为一个实施例中基于区块链的组织节点上链方法的原理示意图；
图4为一个实施例中基于区块链的组织节点上链系统的框图；
图5为另一个实施例中基于区块链的组织节点上链系统的框图；
图6为一个实施例中计算机设备的框图。
具体实施方式
本申请提供的基于区块链的组织节点上链方法，可以应用于如图1所示的应用环境中。该应用场景中包括盟主节点110、待入盟的新的组织节点120、盟主网关节点130、以及组织节点120在网关层对应的第一网关节点140。其中，盟主网关节点130和第一网关节点140皆位于网关层。盟主节点110是联盟链上处于盟主地位的组织节点。即，盟主节点110具有系统的所有权限，用于实现对整个联盟链的管理。盟主节点110和组织节点120可以通过盟主网关节点130和第一网关节点140之间提供的接口，进行通信。
联盟链上的盟主节点110获取待入盟的组织节点120的入盟请求。盟主节点110响应于所述入盟请求，通过网关层的盟主网关节点130调用第一网关节点140的配置信息接口；第一网关节点140，是所述组织节点120所对应的网关节点。组织节点120从本地获取该组织节点120的配置信息，并通过第一网关节点140的配置信息接口发送所述配置信息至盟主网关节点130，以通过盟主网关节点130向盟主节点110返回所述配置信息。盟主节点110将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点120加入所述联盟链。
在一个实施例中，如图2所示，提供了一种基于区块链的组织节点上链方法，该方法具体包括以下步骤：
S202，联盟链上的盟主节点获取待入盟的组织节点的入盟请求。
其中，联盟链是指有若干个组织节点共同参与管理的区块链。盟主节点是联盟链上处于全局管理地位的组织节点。即，盟主节点具有系统的所有权限，用于实现对整个联盟链的管理。
待入盟的组织节点，是待加入该联盟链的组织节点。入盟请求，是加入联盟链的请求。
可以理解，代入盟的组织节点可以主动地向盟主节点发送入盟请求，也可以在接收联盟链的邀请后，通过其他设备向盟主节点发送入盟请求。
在一个实施例中，该方法还包括：盟主节点向组织节点所对应的管理终端发送入盟邀请； 入盟邀请中包括入盟链接和组织验证码。本实施例中，步骤S202包括：当入盟链接被触发时，管理终端则展示入盟申请界面；管理终端通过入盟申请界面获取输入的组织验证码，并在检测到入盟触发操作时，向盟主节点发送针对组织节点的入盟请求；入盟请求中包括组织验证码；盟主节点在验证组织验证码后，响应于入盟请求。
其中，入盟邀请，用于邀请组织节点加入联盟链。在一个实施例中，入盟邀请可以是入盟邀请邮件。可以理解，入盟邀请还可以是短信或即时通信消息等形式。可以理解，入盟邀请中还可以包括联盟链信息。
入盟链接，是用于跳转到入盟申请界面的链接地址。
组织验证码，是组织节点用于申请加入联盟链的验证码。可以理解，组织验证码，用于表明待入盟的组织节点具有加入联盟链的权限，因而，具有调用盟主网关节点的权限，以执行加入联盟链的处理。
具体地，盟主节点可以向组织节点所对应的管理终端发送入盟邀请邮件。使用管理终端的管理员可以通过点击或长按等方式触发入盟链接，以跳转至由后控平台(即后台控制平台)所提供的入盟申请界面。管理员可以在入盟申请界面中输入组织验证码，并进行入盟触发操作，管理终端在检测到入盟触发操作时，向所述盟主节点发送针对所述组织节点的入盟请求。入盟请求中包括组织验证码。
可以理解，通过发送入盟邀请，以向待入盟的组织节点分配组织验证码和入盟链接，能够让待入盟的组织节点更加便捷地发起入盟请求，而且，分配组织验证码能够为后续的配置信息接口的调用，提供鉴权依据，提高了安全性。
在一个实施例中，当管理员尚未在后控平台创建区块链组织，则可以在后控平台的登录界面新建区块链的组织节点，即为待入盟的组织节点，然后再发起该组织节点的入盟请求。
S204，盟主节点响应于入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是组织节点所对应的网关节点。
其中，盟主网关节点，是盟主节点在网关层对应的网关节点。可以理解，盟主网关节点和第一网关节点，分别为盟主节点和组织节点提供与其他组织节点对接的接口。
配置信息接口，是用于获取待入盟的组织节点的配置信息的接口。
具体地，盟主节点在接收到入盟请求后，盟主管理员可以点击同意。盟主节点之后可以触发网关层的盟主网关节点，调用第一网关节点提供的配置信息接口。第一网关节点在检测到配置信息接口被调用后，会将该调用请求通知到待入盟的组织节点。
在一个实施例中，盟主节点可以通过盟主网关节点，将所述组织验证码发送至所述第一网关节点进行存储。可以理解，第一网关节点可以将组织验证码存储至配置文件中。本实施例中，步骤S204包括：通过网关层的盟主网关节点调用第一网关节点的配置信息接口，并将输入的组织验证码作为接口入参；所述第一网关节点将作为接口入参的组织验证码与本地存储的组织验证码进行比对，当比对一致时，则所述盟主网关节点成功调用所述第一网关节点的配置信息接口。
具体地，盟主节点在通过盟主网关节点调用第一网关节点的配置信息接口时，可以将发起入盟请求时输入的组织验证码作为接口入参，第一网关节点则可以将本地存储的组织验证码与作为接口入参的组织验证码进行一致性比对。当比对一致时，则盟主网关节点可以成功调用所述第一网关节点的配置信息接口。当比对不一致时，则盟主网关节点对第一网关节点的配置信息接口的调用失败。
可以理解，在调用第一网关节点的配置信息接口时，对组织验证码进行验证鉴权，能够提高安全性。
可以理解，盟主网关节点可以按照第一网关节点的配置信息接口的地址，定位第一网关节点的配置信息接口，并对其进行调用。
在一个实施例中，第一网关节点的配置信息接口的地址可以为网址格式，比如，可以为：http://localhost:7788/baasorg/getconfig？appsecret＝xxx。
在其他实施例中，盟主节点还可以为待入盟的组织节点分配一个唯一的通信加密盐值，通过盟主网关节点可以将该通信加密盐值发送至第一网关节点，第一网关节点可以将该通信加密盐值一并保存。其中，通信加密盐值，用于对第一网关节点向外传输的数据进行加密签名。表一即为对组织验证码和通信加密盐值进行举例说明。
组织节点名称 组织验证码 通信加密盐值
org1 org1Key xxkyj
org2 org2Key 8uiey
(表一)
S206，组织节点从本地获取组织节点的配置信息，并通过配置信息接口发送配置信息至盟主网关节点，以通过盟主网关节点向盟主节点返回配置信息。
可以理解，组织节点的配置信息预先存储在组织节点本地的配置文件中。需要说明的是，组织节点的本地和第一网关节点的本地不是同一位置。
在一个实施例中，组织节点的配置信息包括证书信息以及组织信息。可以理解，组织节点的配置信息还包括其他配置信息，比如，秘钥等信息。
组织节点的配置文件(configtx.yaml)，是用于创建组织节点的基本文件。可以理解，组织节点就是基于这些配置文件创建的，在创建组织节点之后，并将该组织节点的配置文件存储在该组织节点的本地。
具体地，在第一网关节点的配置信息接口被调用时，会将该调用请求通知到待入盟的组织节点。组织节点从本地存储的配置文件中，获取组织节点的配置信息，并通过配置信息接口发送配置信息至盟主网关节点，以通过盟主网关节点向盟主节点返回该组织节点的配置信息。
在一个实施例中，组织节点可以从本地存储的配置文件中，获取该组织节点的组织信息和证书信息，进而根据组织信息和证书信息生成该组织节点的配置信息。
在一个实施例中，待入盟的组织节点可以从第一网关节点中获取通信加密盐值对生成的配置信息进行加盐后签名。然后，待入盟的组织节点可以通过网关层的第一网关节点的配置信息接口，对接盟主网关节点提供的接口，将加盐签名后的配置信息返回至盟主节点。
S208，盟主节点将配置信息，加入到联盟链上的系统通道配置文件中，以将组织节点加入联盟链。
具体地，盟主节点，可以按照为待入盟的组织节点对应分配的通信加密盐值，针对所获取的加盐签名后的配置信息进行解密，得到包括该待入盟的组织节点的组织信息和证书信息等配置信息。进一步地，盟主节点可以将解密后的配置信息加入到系统通道配置文件中，并签名，从而实现将待入盟的组织节点加入联盟链。
可以理解，签名，是基于区块链的特性，在要更改系统通道配置文件中的信息时，要签名，说明不是非法用户篡改的。
在一个实施例中，盟主节点可以解析系统通道配置文件中的编译格式的配置文件，将其进行格式转换，转换为字符串。进一步地，盟主节点可以将待入盟的组织节点的配置信息加入该字符串中，并将添加后的字符串进行逆转换，转换成在系统通道配置文件中存在的格式。进一步地，对这些信息进行签名，基于这个签名，将待入盟的组织节点的配置信息更新至联盟链上的系统通道配置文件。
为了便于理解，现举例说明，假设系统通道配置文件中存在的格式为protobuffer格式，那么，将通过如下步骤，将待入盟的组织节点的配置信息更新至联盟链上的系统通道配置文件：
1)获取protobuffer格式的系统通道配置文件；
2)解析protobuffer格式的配置文件为json串；
3)将待入盟的组织节点的配置信息加入至该json串中，并转换成protobuffer格式；
4)管理员加上签名确认；
5)基于这个签名，将转换成protobuffer格式的配置信息更新至联盟链上的系统通道配置文件，从而实现将待入盟的组织节点的配置信息更新至联盟链上的系统通道配置文件。
图3为一个实施例中基于区块链的组织节点上链方法的原理示意图。参照图3，盟主节点发出入盟邀请，生成邀请内容、入盟链接和组织验证码，进而通过邮件的方式发送邀请邮件至使用管理终端的组织管理员。组织管理员点击入盟链接，注册或登录后控平台，以跳转至入盟申请页面。如果没有新的待入盟的组织节点，则选择创建组织，如果有，则从已有组织节点中选择待入盟的组织节点，然后基于待入盟的组织节点的组织名称和证书信息等配置信息，向盟主节点发起入盟工作流，并将该配置信息存储至待入盟的组织节点的本地配置文件中。盟主节点对该组织节点的信息进行审核，当批注加入后，通知组织管理员，收到消息通知。进一步地，盟主节点可以通过盟主网关节点的接口，对接调用第一网关节点所提供的配置信息接口，以从待入盟的组织节点的本地配置文件中获取配置信息。当获取到配置信息后，盟主节点可以将配置信息加入到联盟链上的系统通道配置文件中，以将该组织节点加入联盟链。
上述基于区块链的组织节点上链方法，组织节点的配置信息相当于存储在组织节点的本地，盟主节点在接收到待入盟的组织节点的入盟请求后，通过网关层的接口调用，来获取存储在组织节点本地的配置信息，从而将该组织节点加入联盟链。由于配置信息存储在组织节点的本地，相较于传统方法的集中化管理而言，提高了安全性。此外，通过网关层来获取组织节点的配置信息，能够快速地将新的组织节点加入到联盟链上。
在一个实施例中，入盟后的该组织节点还需要加入已有通道或自身创建通道。可以理解，通道，用于实现联盟链上的组织节点之间的数据通信和交互处理。同一通道中的组织节点之间可以实现交互，不同通道中的组织节点之间无法实现交互。
在一个实施例中，该方法还包括：在加入联盟链后的所述组织节点接收到针对目标通道的通道加入请求后，转发所述通道加入请求至创建所述目标通道的目标组织节点；所述目标组织节点响应于所述通道加入请求，根据所述目标组织节点对应的第二网关节点调用所述盟主网关节点的接口，以通过所述盟主网关节点调用所述配置信息接口获取所述组织节点的配置信息；所述目标组织节点将所述组织节点的配置信息加入应用通道配置文件中，以将所述组织节点加入所述目标通道中。
其中，目标通道，是请求加入的已有通道。目标组织节点，是创建该目标通道的组织节点。通道加入请求，用于请求加入通道。第二网关节点，是目标组织节点在网关层对应的网关节点。可以理解，目标组织节点可以通过第二网关节点提供的接口，与其他组织节点之间进行数据交互。
具体地，当管理员通过管理终端，从已有通道列表中选中需要加入的目标通道时，管理终端可以向入盟后的该组织节点发送针对目标通道的通道加入请求。入盟后的该组织节点可以将通道加入请求转发至创建该目标通道的目标组织节点。目标组织节点可以将该通道加入请求通过对应的管理终端呈现给该目标组织节点的管理员。该目标组织节点的管理员则可以点击同意或拒绝加入。当目标组织节点在接收到同意加入的指令后，可以通过调用相应的第二网关节点调用盟主网关节点的接口，通过盟主网关节点调用第一网关节点的配置信息接口，从而获取入盟的该组织节点的配置信息。
在一个实施例中，接收到针对目标通道的通道加入请求后，入盟后的该组织节点可以自动生成接口鉴权验证码，并存储至第一网关节点，以作为后续接口鉴权依据。通道加入请求中也会携带该生成的接口鉴权验证码和第一网关节点的地址。
这样一来，目标组织节点在接收到同意加入的指令后，可以根据通道加入请求中携带的第一网关节点的地址查找到第一网关节点，并根据接口鉴权验证码进行鉴权，以请求调用该 第一网关节点提供的配置信息接口。第一网关节点可以根据存储的接口鉴权验证码，对请求调用时携带的接口鉴权验证码进行鉴权处理，当鉴权通过后，则可以成功调用第一网关节点的配置信息接口。
进一步地，当获取到入盟后的该组织节点的配置信息后，目标组织节点将入盟后的该组织节点的配置信息加入应用通道配置文件中，并签名进行应用通道配置文件的变更，以将该组织节点加入目标通道中。
上述实施例中，在组织节点申请加入目标通道时，目标组织节点可以通过盟主网关节点统一在网关层进行接口调用，以获取组织节点的配置信息，而不需要组织节点之间进行对接，提高了安全性。此外，统一对接盟主网关节点，相较于不同组织节点之间的对接而言，大大降低了复杂性，所以，提高了效率，而且，降低了资源的消耗。
在一个实施例中，入盟后的组织节点也可以自行创建通道。可以理解，入盟后的组织节点，在未加入联盟链之前，即为待入盟的组织节点。
在一个实施例中，该方法还包括：当所述组织节点接收包括通道成员组织节点的组织标识的通道创建请求时，则通过第一网关节点调用盟主网关节点的通道配置文件接口，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息；盟主网关节点通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点；所述组织节点根据所述各通道成员组织节点的配置信息，创建通道。
其中，通道创建请求，用于请求创建通道。通道成员组织节点，是作为待创建的通道中的成员的组织节点。组织标识，用于唯一标识组织节点。成员网关节点，是通道成员组织节点在网关层对应的网关节点。可以理解，通道成员组织节点可以通过成员网关节点提供的接口，与其他组织节点之间进行数据交互。通道配置文件接口，是用于获取创建通道的配置文件的接口，即，相当于，用于获取创建通道的通道成员组织节点的配置信息的接口。
可以理解，各成员网关节点的配置信息接口，用于提供相应通道成员组织节点的配置信息。通道创建接口，是用于创建通道的接口。
具体地，入盟后的该组织节点的管理员，通过管理终端输入或选择通道成员组织节点，以进行通道创建操作，管理终端可以获取通道成员组织节点的组织标识，并生成包括通道成员组织节点的组织标识的通道创建请求发送至该组织节点。入盟后的该组织节点接收到通道创建请求时，则通过第一网关节点调用盟主网关节点的通道配置文件接口，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息。进一步地，盟主网关节点通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至入盟后的该组织节点；入盟后的该组织节点根据所述各通道成员组织节点的配置信息，创建通道。
上述实施例中，在创建通道时，在网关层统一通过盟主网关节点来获取各通道成员组织节点的配置信息，提高了安全性，且提高了处理效率。进而提高了通道创建效率。
在一个实施例中，该方法还包括：入盟后的该组织节点从联盟链上获取联盟链角色信息，并根据所述联盟链角色信息确定所述组织节点的角色；当该组织节点的角色为联盟链协调者时，则执行通过第一网关节点调用盟主网关节点的通道配置文件接口的步骤。
可以理解，当入盟后的该组织节点自行创建通道时，则需要结合联盟链上的角色信息来进行相应的通道创建处理。
其中，联盟链角色信息，即为在联盟链上记录的各组织节点的角色及相应的权限。
可以理解，盟主节点可以针对联盟链上的各组织节点的行为进行基于角色粒度的权限的控制。角色可以包括盟主、联盟链协调者和联盟链参与者三种角色。
其中，盟主，即为超级管理员，作为联盟核心组织者，可以调用所有组织网关节点的服 务以及自身网关接口服务。
联盟链协调者：比较大的组织节点，有公信力的组织节点，主要作为通道管理者，可由盟主直接指定。本实施例中，在对角色的权限控制中，联盟链协调者在进行联盟链创建的时候，即可以为通道管理者，可直接调用盟主网关节点的通道创建相关接口服务。
联盟链参与者：即为普通组织节点，较小的组织节点。本实施例中，在对角色的权限控制中，联盟链参与者不能直接调用接口创建服务；需要取得其他通道成员组织节点的同意，以及身份认证，相当于协商沟通后，才能调用盟主网关节点通道创建接口服务，创建通道。
可以理解，盟主每次会将这些权限管理的数据更新至联盟链上：
为了便于理解，现举例说明，盟主上链的数据结构如下json串表示：
Figure PCTCN2020086646-appb-000001
因此，入盟后的组织节点在创建通道时，可以从联盟链上定位联盟链角色信息所对应的字段，根据这些字段从联盟链上获取联盟链角色信息。进一步地，入盟后的组织节点可以根据自身的组织名称，从联盟链角色信息中查找该入盟后的组织节点所对应的角色。
在一个实施例中，当查询到自己属于的角色为联盟链协调者时，入盟后的该组织节点则可以解析本地的配置文件里是否有要加入的通道成员组织节点的配置信息的存在。如果有则直接创建通道配置文件。如果没有，通道成员组织节点的配置信息的存在，则调用盟主网关节点的接口，获取通道配置文件，即，执行通过第一网关节点调用盟主网关节点的通道配置文件接口的步骤。可以理解，在其他实施例中，入盟后的组织节点也可以直接调用盟主网关节点的接口，以获取通道配置文件。
在一个实施例中，入盟后的组织节点在调用盟主网关节点的接口之前，还可以从第一网关节点中获取通信加密盐值，根据该通信加密盐值对拟创建的通道名称和通道包括的通道成员组织节点的组织标识进行加密，得到加密签名结果。然后根据入盟后的组织节点的组织验证码、要创建的拟创建的通道名称和加密签名结果作为输入参数(即，接口入参)，调用盟主网关节点的接口，以请求获取通道配置文件。盟主网关节点接收到调用请求后，可以从输入参数中解析出组织验证码，并校验是否是合法的组织存在(即进行身份校验)，以及找出其所对应的通信加密盐值，对输入参数中包括的加密签名进行签名校验，以防止输入参数被篡改(即，进行参数防篡改校验)。身份校验以及参数防篡改校验都通过后，将调用相关的服务，生成通道配置文件返回给第一网关节点，第一网关节点根据得到的通道配置文件，创建通道。
在一个实施例中，通道配置文件包括拟创建的通道名称拟创建的拟创建的通道名称称称、通道所包含通道成员组织节点的组织信息及相应的证书信息等。
上述实施例中，考虑了角色权限维度的管控，从联盟链上确定组织节点的角色，不同的角色在创建通道时，执行不同的处理，提高了安全性。
在一个实施例中，该方法还包括：当所述组织节点的角色为联盟链参与者时，则获取所述盟主网关节点返回的与各组织标识对应的网关节点服务地址；所述组织节点通过第一网关节点访问各所述网关节点服务地址，以定位各成员网关节点，并调用各成员网关节点提供的通道创建授权接口，以请求各通道成员组织节点对所述通道创建请求进行授权；各通道成员组织节点通过各成员网关节点发送授权通知至盟主网关节点；所述盟主网关节点在接收全部成员网关节点发送的授权通知后，生成通道创建令牌，并将所述通道创建令牌发送至所述第一网关节点；所述通道创建令牌，用于表征所述组织节点具有通道创建权限；所述第一网关 节点根据所述通道创建令牌，执行所述通过第一网关节点调用盟主网关节点的通道配置文件接口的步骤。
其中，网关节点服务地址，用于定位各组织节点在网关层对应的网关节点。可以理解，各通道成员组织节点的组织标识所对应的网关节点服务地址，用于定位各通道成员组织节点所对应的成员网关节点。通道创建授权接口，是用于授权创建通道的接口。通道创建令牌，是能够创建通道的凭证，用于表征所述组织节点具有通道创建权限，即，表示所有通道成员组织节点皆同意该入盟后的组织节点创建通道。
可以理解，联盟链上的普通参与者在创建通道时，需要与待创建通道中包括的所有通道成员组织节点进行通讯，在都确认授权之后，才能创建通道。
具体地，当入盟后的组织节点的角色为联盟链参与者时，会向盟主网关节点转发通道创建请求，盟主网关节点在接收到通道创建请求后，可以返回请求创建的通道所包括的通道成员组织节点的组织标识，并获取各组织标识对应的网关节点服务地址。盟主网关节点可以将获取的网关节点服务地址返回至入盟后的该组织节点。
进一步地，该组织节点通过第一网关节点访问各所述网关节点服务地址，以定位各成员网关节点，并调用各成员网关节点提供的通道创建授权接口，以请求各通道成员组织节点对所述通道创建请求进行授权。各通道成员组织节点对应的管理员可以进行确认授权操作，各通道成员组织节点则可以通过相应的各成员网关节点发送授权通知至盟主网关节点。各盟主网关节点，可以统计各成员网关节点返回的授权通知，当盟主网关节点在接收全部成员网关节点发送的授权通知后，生成通道创建令牌，并将所述通道创建令牌发送至所述第一网关节点。所述通道创建令牌，用于表征所述组织节点具有通道创建权限。第一网关节点则可以根据所述通道创建令牌，执行所述通过第一网关节点调用盟主网关节点的通道配置文件接口的步骤，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息。
进一步地，盟主网关节点通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点。该入盟后的组织节点则可以根据所述各通道成员组织节点的配置信息，创建通道。
在一个实施例中，入盟后的组织节点在调用盟主网关节点之前，可以使用通信加密盐值对组织验证码、拟创建的通道名称、以及通道成员组织节点的组织标识(比如组织名称)进行加密签名，得到加密签名结果。入盟后的组织节点可以将组织验证码、拟创建的通道名称以及通道成员组织节点的组织标识作为入参，向盟主网关节点发送通道创建请求。各盟主网关节点可以将组织验证码、拟创建的通道名称、通道成员组织节点的组织标识进行拼接，并对拼接后的字符串进行加密生成拟创建的通道标识，并将拟创建的通道标识、以及通道成员组织节点的组织标识对应的网关节点服务地址返回至第一网关节点。
为了便于理解网关节点服务地址，现举例说明。比如，组织节点org2的网关节点服务地址：http://xxx.xx.xx/baasorg/orderer/orggateway/list/。
该组织节点通过第一网关节点访问各所述网关节点服务地址，以定位各成员网关节点，并将拟创建的通道标识、组织验证码、拟创建的通道名称和加密签名结果作为入参，调用各成员网关节点提供的通道创建授权接口，以请求各通道成员组织节点对所述通道创建请求进行授权。各成员网关节点则可以向盟主网关节点发起验证请求，以验证组织验证码是否存在、以及验证加密签名结果是否真实有效，当上述验证皆通过后，则向通道成员组织节点对应的管理终端触发生成工作流，以让管理员审核是否授权。当同意授权后，则各通道成员组织节点再通过成员网关节点向盟主网关节点发送授权通知。盟主网关节点则可以记录授权通知，在接收全部成员网关节点发送的授权通知后，生成通道创建令牌。
上述实施例中，当组织节点的角色为联盟链参与者时，则通过网关层，请求各通道成员组织节点对通道创建请求进行授权，并由盟主网关节点统一记录授权通知，当全部授权后， 由盟主网关节点为该组织节点分配通道创建令牌，进而基于该通道创建令牌，用盟主网关节点的通道配置文件接口以创建通道，提高了安全性。
如图4所示，提供了一种基于区块链的组织节点上链系统400，所述系统包括：盟主节点402、待入盟的组织节点404、盟主网关节点406、以及第一网关节点408；所述盟主节点402位于联盟链上；
所述盟主节点402，用于获取待入盟的所述组织节点404的入盟请求。
所述盟主节点402还用于响应于所述入盟请求，通过网关层的所述盟主网关节点406调用第一网关节点408的配置信息接口；第一网关节点408，是所述组织节点404所对应的网关节点。
所述组织节点404，用于从本地获取所述组织节点404的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点406，以通过盟主网关节点406向盟主节点402返回所述配置信息。
所述盟主节点402还用于将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点404加入所述联盟链。
在一个实施例中，所述系统400还包括：管理终端405；
盟主节点402还用于向所述组织节点404所对应的管理终端405发送入盟邀请；所述入盟邀请中包括入盟链接和组织验证码。
当所述入盟链接被触发时，所述管理终端405用于展示入盟申请界面；通过所述入盟申请界面获取输入的组织验证码，并在检测到入盟触发操作时，向所述盟主节点402发送针对所述组织节点404的入盟请求；所述入盟请求中包括输入的组织验证码。
在一个实施例中，所述盟主节点402还用于通过盟主网关节点406将所述组织验证码发送至所述第一网关节点408进行存储；通过网关层的盟主网关节点406调用第一网关节点408的配置信息接口，并将输入的组织验证码作为接口入参。
所述第一网关节点408还用于将作为接口入参的组织验证码与本地存储的组织验证码进行比对，当比对一致时，则所述盟主网关节点406成功调用所述第一网关节点408的配置信息接口。
如图5所示，在一个实施例中，该系统400还包括管理终端405、目标组织节点410、以及第二网关节点412；
所述组织节点404还用于在接收到针对目标通道的通道加入请求后，转发所述通道加入请求至创建所述目标通道的目标组织节点410。
所述目标组织节点410，用于响应于所述通道加入请求，根据所述目标组织节点410对应的第二网关节点412调用所述盟主网关节点406的接口，以通过所述盟主网关节点406调用所述配置信息接口获取所述组织节点404的配置信息。
所述目标组织节点410还用于将所述组织节点404的配置信息加入应用通道配置文件中，以将所述组织节点404加入所述目标通道中。
在一个实施例中，所述组织节点404还用于当接收包括通道成员组织节点的组织标识的通道创建请求时，通过第一网关节点408调用盟主网关节点406的通道配置文件接口，以通过所述盟主网关节点406根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息。
所述盟主网关节点406还用于通过调用所述第一网关节点408的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点404。
所述组织节点404还用于根据所述各通道成员组织节点的配置信息，创建通道。
在一个实施例中，所述组织节点404还用于从联盟链上获取联盟链角色信息，并根据所述联盟链角色信息确定所述组织节点404的角色；当所述组织节点404的角色为联盟链协调者时，则执行通过第一网关节点408调用盟主网关节点406的通道配置文件接口的步骤。
在一个实施例中，所述组织节点404还用于当所述组织节点404的角色为联盟链参与者时，则获取所述盟主网关节点406返回的与各组织标识对应的网关节点服务地址；所述组织节点404通过第一网关节点408访问各所述网关节点服务地址，以定位各成员网关节点，并调用各成员网关节点提供的通道创建授权接口，以请求各通道成员组织节点对所述通道创建请求进行授权。
各通道成员组织节点通过各成员网关节点发送授权通知至盟主网关节点406；所述盟主网关节点406在接收全部成员网关节点发送的授权通知后，生成通道创建令牌，并将所述通道创建令牌发送至所述第一网关节点408；所述通道创建令牌，用于表征所述组织节点404具有通道创建权限。
所述第一网关节点408根据所述通道创建令牌，执行所述通过第一网关节点408调用盟主网关节点406的通道配置文件接口的步骤。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是图1中的盟主节点110、待入盟的新的组织节点120、盟主网关节点130、以及第一网关节点140中的任意一种设备。其内部结构图可以如图6所示。该计算机设备包括通过系统总线连接的处理器、存储器和网络接口。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机程序。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机程序被处理器执行时以实现一种基于区块链的组织节点上链方法，其中，所述方法包括：联盟链上的盟主节点获取待入盟的组织节点的入盟请求；所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
本领域技术人员可以理解，图6中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，提供了一种计算机设备，包括存储器和处理器，存储器存储有计算机程序，计算机程序被处理器执行时，使得处理器执行上述基于区块链的组织节点上链方法的步骤。此处基于区块链的组织节点上链方法的步骤可以是上述各个实施例的基于区块链的组织节点上链方法中的步骤。需要说明的是，上述各个实施例的基于区块链的组织节点上链方法可以由多个计算机设备协同完成。
在一个实施例中，提供了一种计算机可读存储介质，所述计算机可读存储介质可以是非易失性，也可以是易失性，所述计算机可读存储介质存储有计算机程序，计算机程序被处理器执行时，使得处理器执行上述基于区块链的组织节点上链方法的步骤。此处基于区块链的组织节点上链方法的步骤可以是上述各个实施例的基于区块链的组织节点上链方法中的步骤，其中，所述方法包括：联盟链上的盟主节点获取待入盟的组织节点的入盟请求；所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一非易失性计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法的实施例的流程。其中，本申请所 提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种基于区块链的组织节点上链方法，其中，所述方法包括：
    联盟链上的盟主节点获取待入盟的组织节点的入盟请求；
    所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；
    所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；
    所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    盟主节点向所述组织节点所对应的管理终端发送入盟邀请；所述入盟邀请中包括入盟链接和组织验证码；
    所述联盟链上的盟主节点获取待入盟的组织节点的入盟请求包括：
    当所述入盟链接被触发时，所述管理终端则展示入盟申请界面；
    所述管理终端通过所述入盟申请界面获取输入的组织验证码，并在检测到入盟触发操作时，向所述盟主节点发送针对所述组织节点的入盟请求；所述入盟请求中包括输入的组织验证码。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    所述盟主节点通过盟主网关节点将所述组织验证码发送至所述第一网关节点进行存储；
    所述通过网关层的盟主网关节点调用第一网关节点的配置信息接口包括：
    通过网关层的盟主网关节点调用第一网关节点的配置信息接口，并将输入的组织验证码作为接口入参；
    所述第一网关节点将作为接口入参的组织验证码与本地存储的组织验证码进行比对，当比对一致时，则所述盟主网关节点成功调用所述第一网关节点的配置信息接口。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    在加入联盟链后的所述组织节点接收到针对目标通道的通道加入请求后，转发所述通道加入请求至创建所述目标通道的目标组织节点；
    所述目标组织节点响应于所述通道加入请求，根据所述目标组织节点对应的第二网关节点调用所述盟主网关节点的接口，以通过所述盟主网关节点调用所述配置信息接口获取所述组织节点的配置信息；
    所述目标组织节点将所述组织节点的配置信息加入应用通道配置文件中，以将所述组织节点加入所述目标通道中。
  5. 根据权利要求1至4任一项所述的方法，其中，所述方法还包括：
    当所述组织节点接收包括通道成员组织节点的组织标识的通道创建请求时，则通过第一网关节点调用盟主网关节点的通道配置文件接口，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息；
    盟主网关节点通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点；
    所述组织节点根据所述各通道成员组织节点的配置信息，创建通道。
  6. 根据权利要求5所述的方法，其中，所述方法还包括：
    所述组织节点从联盟链上获取联盟链角色信息，并根据所述联盟链角色信息确定所述组织节点的角色；
    当所述组织节点的角色为联盟链协调者时，则执行通过第一网关节点调用盟主网关节点的通道配置文件接口的步骤。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    当所述组织节点的角色为联盟链参与者时，则获取所述盟主网关节点返回的与各组织标 识对应的网关节点服务地址；
    所述组织节点通过第一网关节点访问各所述网关节点服务地址，以定位各成员网关节点，并调用各成员网关节点提供的通道创建授权接口，以请求各通道成员组织节点对所述通道创建请求进行授权；
    各通道成员组织节点通过各成员网关节点发送授权通知至盟主网关节点；
    所述盟主网关节点在接收全部成员网关节点发送的授权通知后，生成通道创建令牌，并将所述通道创建令牌发送至所述第一网关节点；所述通道创建令牌，用于表征所述组织节点具有通道创建权限；
    所述第一网关节点根据所述通道创建令牌，执行所述通过第一网关节点调用盟主网关节点的通道配置文件接口的步骤。
  8. 一种基于区块链的组织节点上链系统，所述系统包括：
    盟主节点、待入盟的组织节点、盟主网关节点、以及第一网关节点；所述盟主节点位于联盟链上；
    所述盟主节点，用于获取待入盟的所述组织节点的入盟请求；
    所述盟主节点还用于响应于所述入盟请求，通过网关层的所述盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；
    所述组织节点，用于从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过盟主网关节点向盟主节点返回所述配置信息；
    所述盟主节点还用于将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
  9. 根据权利要求8所述的系统，其中，所述系统还包括目标组织节点；
    所述组织节点还用于在接收到针对目标通道的通道加入请求后，转发所述通道加入请求至创建所述目标通道的目标组织节点；
    所述目标组织节点，用于响应于所述通道加入请求，根据所述目标组织节点对应的第二网关节点调用所述盟主网关节点的接口，以通过所述盟主网关节点调用所述配置信息接口获取所述组织节点的配置信息；
    所述目标组织节点还用于将所述组织节点的配置信息加入应用通道配置文件中，以将所述组织节点加入所述目标通道中。
  10. 根据权利要求8所述的系统，其中，所述组织节点还用于当接收包括通道成员组织节点的组织标识的通道创建请求时，通过第一网关节点调用盟主网关节点的通道配置文件接口，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息；
    所述盟主网关节点还用于通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点；
    所述组织节点还用于根据所述各通道成员组织节点的配置信息，创建通道。
  11. 一种计算机设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现一种基于区块链的组织节点上链方法，其中，所述方法包括：
    联盟链上的盟主节点获取待入盟的组织节点的入盟请求；
    所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；
    所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；
    所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
  12. 根据权利要求11所述的计算机设备，其中，所述基于区块链的组织节点上链方法还包括：
    盟主节点向所述组织节点所对应的管理终端发送入盟邀请；所述入盟邀请中包括入盟链接和组织验证码；
    所述联盟链上的盟主节点获取待入盟的组织节点的入盟请求包括：
    当所述入盟链接被触发时，所述管理终端则展示入盟申请界面；
    所述管理终端通过所述入盟申请界面获取输入的组织验证码，并在检测到入盟触发操作时，向所述盟主节点发送针对所述组织节点的入盟请求；所述入盟请求中包括输入的组织验证码。
  13. 根据权利要求12所述的计算机设备，其中，所述基于区块链的组织节点上链方法还包括：
    所述盟主节点通过盟主网关节点将所述组织验证码发送至所述第一网关节点进行存储；
    所述通过网关层的盟主网关节点调用第一网关节点的配置信息接口包括：
    通过网关层的盟主网关节点调用第一网关节点的配置信息接口，并将输入的组织验证码作为接口入参；
    所述第一网关节点将作为接口入参的组织验证码与本地存储的组织验证码进行比对，当比对一致时，则所述盟主网关节点成功调用所述第一网关节点的配置信息接口。
  14. 根据权利要求11所述的计算机设备，其中，所述基于区块链的组织节点上链方法还包括：
    在加入联盟链后的所述组织节点接收到针对目标通道的通道加入请求后，转发所述通道加入请求至创建所述目标通道的目标组织节点；
    所述目标组织节点响应于所述通道加入请求，根据所述目标组织节点对应的第二网关节点调用所述盟主网关节点的接口，以通过所述盟主网关节点调用所述配置信息接口获取所述组织节点的配置信息；
    所述目标组织节点将所述组织节点的配置信息加入应用通道配置文件中，以将所述组织节点加入所述目标通道中。
  15. 根据权利要求11至14任一项所述的计算机设备，其中，所述基于区块链的组织节点上链方法还包括：
    当所述组织节点接收包括通道成员组织节点的组织标识的通道创建请求时，则通过第一网关节点调用盟主网关节点的通道配置文件接口，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息；
    盟主网关节点通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点；
    所述组织节点根据所述各通道成员组织节点的配置信息，创建通道。
  16. 一种计算机可读存储介质，其中，所述计算机可读存储介质存储有计算机程序，所述计算机程序当被处理器执行时使所述处理器执行一种基于区块链的组织节点上链方法，其中，所述方法包括：
    联盟链上的盟主节点获取待入盟的组织节点的入盟请求；
    所述盟主节点响应于所述入盟请求，通过网关层的盟主网关节点调用第一网关节点的配置信息接口；第一网关节点，是所述组织节点所对应的网关节点；
    所述组织节点从本地获取所述组织节点的配置信息，并通过所述配置信息接口发送所述配置信息至盟主网关节点，以通过所述盟主网关节点向所述盟主节点返回所述配置信息；
    所述盟主节点将所述配置信息，加入到所述联盟链上的系统通道配置文件中，以将所述组织节点加入所述联盟链。
  17. 根据权利要求16所述的计算机可读存储介质，其中，所述基于区块链的组织节点上 链方法还包括：
    盟主节点向所述组织节点所对应的管理终端发送入盟邀请；所述入盟邀请中包括入盟链接和组织验证码；
    所述联盟链上的盟主节点获取待入盟的组织节点的入盟请求包括：
    当所述入盟链接被触发时，所述管理终端则展示入盟申请界面；
    所述管理终端通过所述入盟申请界面获取输入的组织验证码，并在检测到入盟触发操作时，向所述盟主节点发送针对所述组织节点的入盟请求；所述入盟请求中包括输入的组织验证码。
  18. 根据权利要求17所述的计算机可读存储介质，其中，所述基于区块链的组织节点上链方法还包括：
    所述盟主节点通过盟主网关节点将所述组织验证码发送至所述第一网关节点进行存储；
    所述通过网关层的盟主网关节点调用第一网关节点的配置信息接口包括：
    通过网关层的盟主网关节点调用第一网关节点的配置信息接口，并将输入的组织验证码作为接口入参；
    所述第一网关节点将作为接口入参的组织验证码与本地存储的组织验证码进行比对，当比对一致时，则所述盟主网关节点成功调用所述第一网关节点的配置信息接口。
  19. 根据权利要求17所述的计算机可读存储介质，其中，所述基于区块链的组织节点上链方法还包括：
    在加入联盟链后的所述组织节点接收到针对目标通道的通道加入请求后，转发所述通道加入请求至创建所述目标通道的目标组织节点；
    所述目标组织节点响应于所述通道加入请求，根据所述目标组织节点对应的第二网关节点调用所述盟主网关节点的接口，以通过所述盟主网关节点调用所述配置信息接口获取所述组织节点的配置信息；
    所述目标组织节点将所述组织节点的配置信息加入应用通道配置文件中，以将所述组织节点加入所述目标通道中。
  20. 根据权利要求16至19任一项所述的计算机可读存储介质，其中，所述基于区块链的组织节点上链方法还包括：
    当所述组织节点接收包括通道成员组织节点的组织标识的通道创建请求时，则通过第一网关节点调用盟主网关节点的通道配置文件接口，以通过所述盟主网关节点根据各所述组织标识定位各通道成员组织节点对应的成员网关节点，并通过调用各所述成员网关节点的配置信息接口，获取各所述通道成员组织节点的配置信息；
    盟主网关节点通过调用所述第一网关节点的通道创建接口，将各所述通道成员组织节点的配置信息返回至所述组织节点；
    所述组织节点根据所述各通道成员组织节点的配置信息，创建通道。
PCT/CN2020/086646 2020-02-11 2020-04-24 基于区块链的组织节点上链方法和系统 WO2021159606A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010087063.0 2020-02-11
CN202010087063.0A CN111294356B (zh) 2020-02-11 2020-02-11 基于区块链的组织节点上链方法和系统

Publications (1)

Publication Number Publication Date
WO2021159606A1 true WO2021159606A1 (zh) 2021-08-19

Family

ID=71026831

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/086646 WO2021159606A1 (zh) 2020-02-11 2020-04-24 基于区块链的组织节点上链方法和系统

Country Status (2)

Country Link
CN (1) CN111294356B (zh)
WO (1) WO2021159606A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113825174A (zh) * 2021-09-29 2021-12-21 南阳师范学院 一种动态联盟的移动传感器网络数据处理任务协同方法
CN114362957A (zh) * 2021-12-24 2022-04-15 杭州溪塔科技有限公司 使用邀请码的联盟链共建方法和系统
CN116523171A (zh) * 2023-07-03 2023-08-01 成都智慧企业发展研究院有限公司 一种基于全生命周期管理的数据资产管理方法及系统
WO2024021627A1 (zh) * 2022-07-28 2024-02-01 华为云计算技术有限公司 一种联盟链的管理方法及相关系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112380219B (zh) * 2020-11-18 2021-10-08 南威软件股份有限公司 一种定义区块链上链数据业务规约及应用业务规约的方法
CN113542033B (zh) * 2021-07-21 2024-02-27 杭州云象网络技术有限公司 联盟链基础设施与管理平台多对多映射方法与系统
CN115632800B (zh) * 2022-12-22 2023-05-05 广东省电信规划设计院有限公司 基于区块链共识的物联网源端数据存储方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108965469A (zh) * 2018-08-16 2018-12-07 北京京东尚科信息技术有限公司 区块链网络成员动态管理方法、装置、设备及存储介质
CN109391661A (zh) * 2017-08-10 2019-02-26 普天信息技术有限公司 物联网终端的区块链组网方法和系统
CN110278256A (zh) * 2019-06-13 2019-09-24 思力科（深圳）电子科技有限公司 区块链节点接入上链方法、相关设备及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019072281A2 (en) * 2018-11-27 2019-04-18 Alibaba Group Holding Limited ASYMMETRICAL KEY MANAGEMENT IN CONSORTIUM BLOCK CHAIN NETWORKS
CN109815657B (zh) * 2018-12-14 2022-10-28 深圳壹账通智能科技有限公司 基于联盟链的身份认证方法、装置、计算机可读存储介质及终端设备
CN110008263A (zh) * 2019-02-20 2019-07-12 顺丰科技有限公司 Hyperledger fabric集群模式下的动态组织扩展方法和系统
CN109978546A (zh) * 2019-04-08 2019-07-05 北京邮电大学 一种联盟区块链架构及其分级存储和交易穿孔方法
CN110599181B (zh) * 2019-09-26 2021-05-11 腾讯科技（深圳）有限公司 基于区块链的数据处理方法、装置和设备及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391661A (zh) * 2017-08-10 2019-02-26 普天信息技术有限公司 物联网终端的区块链组网方法和系统
CN108965469A (zh) * 2018-08-16 2018-12-07 北京京东尚科信息技术有限公司 区块链网络成员动态管理方法、装置、设备及存储介质
CN110278256A (zh) * 2019-06-13 2019-09-24 思力科（深圳）电子科技有限公司 区块链节点接入上链方法、相关设备及系统

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113825174A (zh) * 2021-09-29 2021-12-21 南阳师范学院 一种动态联盟的移动传感器网络数据处理任务协同方法
CN113825174B (zh) * 2021-09-29 2024-02-20 南阳师范学院 一种动态联盟的移动传感器网络数据处理任务协同方法
CN114362957A (zh) * 2021-12-24 2022-04-15 杭州溪塔科技有限公司 使用邀请码的联盟链共建方法和系统
CN114362957B (zh) * 2021-12-24 2023-05-16 杭州溪塔科技有限公司 使用邀请码的联盟链共建方法和系统
WO2024021627A1 (zh) * 2022-07-28 2024-02-01 华为云计算技术有限公司 一种联盟链的管理方法及相关系统
CN116523171A (zh) * 2023-07-03 2023-08-01 成都智慧企业发展研究院有限公司 一种基于全生命周期管理的数据资产管理方法及系统
CN116523171B (zh) * 2023-07-03 2023-08-29 成都智慧企业发展研究院有限公司 一种基于全生命周期管理的数据资产管理方法及系统

Also Published As

Publication number Publication date
CN111294356A (zh) 2020-06-16
CN111294356B (zh) 2022-09-06

Similar Documents

Publication Publication Date Title
WO2021159606A1 (zh) 基于区块链的组织节点上链方法和系统
US10498543B2 (en) Systems and methods for encryption key management
US10915552B2 (en) Delegating credentials with a blockchain member service
US10469460B2 (en) Data sharing in a blockchain-enabled trust domain
US8752152B2 (en) Federated authentication for mailbox replication
US11791990B2 (en) Apparatus and method for managing personal information
US20100299738A1 (en) Claims-based authorization at an identity provider
US10659453B2 (en) Dual channel identity authentication
US10148637B2 (en) Secure authentication to provide mobile access to shared network resources
US20200058091A1 (en) Address management system
US11874905B2 (en) Establishing access sessions
US11870782B2 (en) Management of hosted channel membership in a communication platform
US11695543B2 (en) Blockchain network control system and methods
CN111651794A (zh) 基于联盟链的电子数据管理方法、装置和存储介质
CN111431793B (zh) 会话管理方法、装置、计算机设备和存储介质
CN110990883A (zh) 数据访问方法、装置、计算机可读存储介质和计算机设备
CN114239046A (zh) 数据共享方法
CN116932617A (zh) 跨平台的数据处理方法、装置、设备和介质
WO2016165443A1 (zh) 一种保护机器类通信设备的方法、网络实体及mtc设备
US11741216B1 (en) Credential revocation leveraging private keys on keystores read by provisioned devices
TWI829215B (zh) 可檢核取用訊標的移轉歷史以驗證取用訊標有效性的去中心化資料授權控管系統
CN113946815B (zh) 用于联邦学习和隐私计算的授权方法
US20230055660A1 (en) Secure data management
TWI829221B (zh) 可允許資料請求者裝置查核區塊鏈子系統中的資料授權政策正確性的去中心化資料授權控管系統
US20220019652A1 (en) Flexible credential supported software service provisioning

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20918347

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/12/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20918347

Country of ref document: EP

Kind code of ref document: A1