WO2020181985A1 - 一种区块链中多联盟链的负载均衡方法及装置 - Google Patents
一种区块链中多联盟链的负载均衡方法及装置 Download PDFInfo
- Publication number
- WO2020181985A1 WO2020181985A1 PCT/CN2020/076490 CN2020076490W WO2020181985A1 WO 2020181985 A1 WO2020181985 A1 WO 2020181985A1 CN 2020076490 W CN2020076490 W CN 2020076490W WO 2020181985 A1 WO2020181985 A1 WO 2020181985A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- chain
- routing
- node
- service request
- organization
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
Definitions
- the embodiment of the present invention belongs to the field of financial technology (Fintech), and in particular relates to a method and device for load balancing of multiple alliance chains in a blockchain (Blockchain).
- Blockchain is a distributed shared ledger database.
- Consortium chain is composed of mutually trusting institutional nodes.
- the establishment of connections and data transmission between nodes use safe and reliable methods, such as authentication, IP (Internet Protocol, network The interconnection agreement) whitelist, etc., the blockchain system that external nodes cannot join.
- IP Internet Protocol, network The interconnection agreement
- the existing business requests are relatively large, and the performance and storage of a single chain cannot meet the business needs. Therefore, it is necessary to introduce multi-chain technology.
- the load balancing of multiple alliance chains in the existing blockchain is mainly through the routing configuration files of each access organization , To determine the consortium chain to which the upper chain request is sent, so as to achieve load balancing of multiple consortium chains.
- each organization needs to maintain its own routing configuration file. Once the routing configuration file needs to be modified, each organization needs to modify it synchronously. In this case, inconsistent routing rules may occur, and multiple alliance chains cannot be realized. Load balancing between.
- the embodiment of the present invention provides a method and device for load balancing of multiple alliance chains in a blockchain.
- Multiple agencies jointly maintain contract information of a routing chain to avoid the inconsistency of the routing rules of various agencies, which may lead to the failure to implement multiple alliance chains.
- Load balancing is a method and device for load balancing of multiple alliance chains in a blockchain.
- An embodiment of the present invention provides a load balancing method for multiple alliance chains in a blockchain, including:
- the routing chain is a block chain composed of nodes of institutions in the multi-consortium chain;
- the service request includes a service to be processed;
- the first node is determined according to the alliance chain corresponding to the service request, and the service to be processed is sent to the first node; the first node is the one used to process the service to be processed in the multiple alliance chain node.
- the routing chain is a block chain composed of nodes of institutions in multiple alliance chains, and the contract information of the routing chain is jointly maintained by multiple institutions.
- the alliance chain corresponding to the business request can be determined based on the business request and the contract information of the routing chain, and after the first node is determined, the pending business is sent to the first Nodes, the alliance chain corresponding to the business request determined in this way and the first node can effectively achieve the load balance of the multiple alliance chains, that is, the contract information of a routing chain is maintained by multiple agencies to avoid inconsistencies in the routing rules of each agency. As a result, load balancing of multiple alliance chains cannot be realized.
- the contract information of the routing chain includes routing rules of each organization;
- the service request includes an organization ID, a service ID, and a serial number;
- the determining the alliance chain corresponding to the service request according to the service request and the contract information of the routing chain includes:
- the routing rules of the organization to which the service request belongs are queried, and the alliance chain corresponding to the service request is determined.
- the contract information of the routing chain includes the routing rules of each organization, and the business request includes the organization ID, business ID and serial number. According to the routing rules of each organization, the organization ID of the business request, the business ID and the serial number, it can be Determine the alliance chain corresponding to the business request.
- the contract information of the routing chain includes the routing rules of each organization, that is, each organization jointly maintains a routing configuration file that includes the routing rules of each organization to avoid the occurrence of each organization maintaining its own routing configuration file, causing each organization Inconsistent routing configuration files affect the load balance between multiple chains.
- the contract information of the routing chain includes the nodes of each organization and the nodes of each alliance chain;
- the service request includes the identifier of the organization;
- the determining the first node according to the alliance chain corresponding to the service request includes:
- the contract information of the routing chain includes the nodes of each organization and the nodes of each alliance chain
- the service request includes the organization identifier.
- the alliance chain corresponding to the service request and the node of each alliance chain can be used to determine the alliance corresponding to the service request.
- the set of all nodes in the chain that is, the first set, further determines the node of the organization to which the service request belongs, that is, the second set, based on the organization identifier and the nodes of each organization, and determines the first set based on the nodes that belong to the first set and the second set.
- Node that is, the node used to process the business to be processed.
- the acquiring contract information of the routing chain includes:
- the contract information of the routing chain is the contract information of the blockchain composed of the nodes of the institutions in the multi-consortium chain.
- Optional also includes:
- the modification information of the routing rule is sent to the node of the routing chain, so that the node of the routing chain can modify the contract information of the routing chain according to the modification information of the routing rule.
- the modification information of the routing rule can be obtained, and the modification information of the routing rule can be sent to the node of the routing chain, thereby modifying the contract information of the routing chain.
- each institution can directly obtain the contract information of the routing chain from the routing chain, that is, it can obtain the routing rules of the institution after the modification takes effect, so as to avoid the failure to achieve multiple changes due to the non-synchronization of the routing rules of each institution. Load balancing of the alliance chain.
- an embodiment of the present invention also provides a load balancing device for multiple alliance chains in a blockchain, including:
- the transceiver unit is used to obtain service requests and contract information of a routing chain;
- the routing chain is a block chain composed of nodes of institutions in the multi-consortium chain;
- the service request includes a service to be processed;
- the processing unit is configured to determine the alliance chain corresponding to the service request according to the service request and the contract information of the routing chain; determine the first node according to the alliance chain corresponding to the service request, and send the service to be processed to The first node; the first node is a node used to process the service to be processed in the multiple alliance chain.
- the contract information of the routing chain includes routing rules of each organization;
- the service request includes an organization ID, a service ID, and a serial number;
- the processing unit is specifically used for:
- the routing rules of the organization to which the service request belongs are queried, and the alliance chain corresponding to the service request is determined.
- the contract information of the routing chain includes the nodes of each organization and the nodes of each alliance chain;
- the service request includes the identifier of the organization;
- the processing unit is specifically used for:
- the transceiver unit is specifically configured to:
- the transceiver unit is further configured to:
- the modification information of the routing rule is sent to the node of the routing chain, so that the node of the routing chain can modify the contract information of the routing chain according to the modification information of the routing rule.
- an embodiment of the present invention also provides a computing device, including:
- Memory used to store program instructions
- the processor is configured to call the program instructions stored in the memory, and execute the load balancing method of the multiple alliance chains in the blockchain according to the obtained program.
- an embodiment of the present invention also provides a computer-readable non-volatile storage medium, including computer-readable instructions.
- the computer reads and executes the computer-readable instructions, the computer executes the above-mentioned blockchain Load balancing method for multiple alliance chains.
- an embodiment of the present invention also provides a computer program product, the computer program product includes a computer program stored on a computer-readable non-volatile storage medium, the computer program includes program instructions, when the program When the instruction is executed by the computer, the computer is caused to execute the load balancing method of the multi-consortium chain in the blockchain.
- the service request and the contract information of the routing chain are obtained.
- the routing chain is a block chain composed of nodes of institutions in multiple alliance chains, and the contract information of the routing chain is jointly maintained by multiple institutions.
- the alliance chain corresponding to the business request can be determined based on the business request and the contract information of the routing chain, and after the first node is determined, the pending business is sent to the first node.
- One node, the alliance chain corresponding to the business request determined in this way and the first node can effectively achieve the load balance of the multiple alliance chains, that is, the contract information of a routing chain is jointly maintained by multiple institutions to avoid the inconsistency of the routing rules of each institution , Resulting in the inability to achieve load balancing of multiple alliance chains.
- FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present invention
- FIG. 2 is a schematic flowchart of a load balancing method for multiple alliance chains provided by an embodiment of the present invention
- FIG. 3 is a schematic flowchart of a load balancing method for multiple alliance chains according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart of a load balancing method for multiple alliance chains according to an embodiment of the present invention
- FIG. 5 is a schematic structural diagram of a load balancing device for multiple alliance chains according to an embodiment of the present invention.
- Fig. 6 is a schematic structural diagram of a computing device provided by an embodiment of the present invention.
- the embodiment of the present invention provides a system architecture applicable to a load balancing method for multiple alliance chains in a blockchain.
- the system architecture may include multiple institutions.
- the nodes of each institution in the multiple institutions form an alliance chain and a routing chain.
- the system includes organization A, organization B, and organization C.
- Organization A includes node A1, node A2, node A3, and node A4, and organization B includes node B1, node B2, node B3, and node B4.
- Organization C includes node C1, node C2, and node C3.
- Node A1, node A4, node B1, and node C1 form alliance chain 1
- node A2, node B2, node B4, and node C2 form alliance chain 2
- node A3, node B3, and node C3 form a routing chain.
- the routing chain is a block chain composed of the nodes of the institutions in the multi-consortium chain.
- the contract information of the routing chain includes a routing configuration file, that is, each institution jointly maintains a routing configuration file.
- the routing configuration file includes the routing rules of organization A, the routing rules of organization B, The routing rules of organization C. If an organization receives a business request, it will determine which alliance chain the business request should be sent to according to the contract information of the routing chain, so as to achieve load balancing of multiple alliance chains.
- FIG. 2 exemplarily shows the flow of a load balancing method for multiple alliance chains in a blockchain according to an embodiment of the present invention, and the flow can be executed by the load balancing device of the multiple alliance chains in the blockchain .
- the process specifically includes:
- Step 201 Obtain the service request and the contract information of the routing chain.
- the service request may include any one or a combination of the following parameters: the service to be processed, the organization ID, the service ID, and the serial number.
- the organization ID is the ID of the organization corresponding to the service to be processed in the service request
- the service ID is the service ID of the service to be processed in the service request
- the serial number is the serial number of the service to be processed.
- organization A obtains a service request and the organization corresponding to the service to be processed in the service request is organization A, the organization ID is "Org A”, and the service ID of the service to be processed in the service request is "APPID” A1" and the sequence number is "SeqNo 50", it can be understood that the service request includes "Org A, APPID A1, SeqNo 50".
- the contract information of the routing chain may include any one or a combination of the following parameters: routing rules of each organization, nodes of each organization, and nodes of each alliance chain.
- the routing rules of each organization include the business identification of each organization, the range of serial numbers, and the identity of the alliance chain.
- the nodes of each organization are the nodes included in each organization, and the nodes of each alliance chain are the nodes included in each alliance chain.
- the routing rules of each organization can refer to Table 1
- the nodes of each organization can refer to Table 2
- the nodes of each alliance chain can refer to Table 3. Table 1
- the institution can obtain the contract information of the routing chain from the routing chain, and the institution sends a contract information obtaining request to the node of the routing chain.
- the node of the routing chain feeds back the contract information of the routing chain
- the organization receives the contract information of the routing chain fed back by the nodes of the routing chain.
- Step 202 Determine the alliance chain corresponding to the service request according to the service request and the contract information of the routing chain.
- the contract information of the routing chain may include the routing rules of each organization, and the business request includes the organization ID, business ID, and serial number. Specifically, the organization to which the business request belongs is determined based on the organization ID and the routing rules of each organization. According to the business identification and serial number, the routing rules of the organization to which the business request belongs are queried to determine the alliance chain corresponding to the business request.
- the organization can obtain that the service to be processed is a business request of its own institution, or it can obtain that the service to be processed is not a business request of its own institution, that is, institution A can obtain a service request with the organization identifier "Org A" , You can also get the service request with the organization identifier "Org B”.
- the service request obtained by organization A includes "Org A, APPID A1, SeqNo50”, it can be determined based on “Org A, APPID A1, SeqNo 50” and Table 1 that the alliance chain identifier is Chain1, that is, the service The request corresponds to the alliance chain 1.
- the service request obtained by organization A includes "Org B, APPID B1, SeqNo 50”
- the service request corresponds to Alliance Chain 2.
- Step 203 Determine the first node according to the alliance chain corresponding to the service request, and send the service to be processed to the first node.
- the first node is a node used for processing to-be-processed services in a multi-consortium chain. That is, after the alliance chain corresponding to the service request is determined in step 202, the node that processes the service to be processed needs to be determined from the alliance chain corresponding to the service request, and this node is the first node.
- the contract information of the routing chain includes the nodes of each organization and the nodes of each alliance chain
- the business request includes the organization identification.
- the alliance chain corresponding to the business request and the nodes of each alliance chain determine the alliance chain corresponding to the business request. The first set of nodes; and then determine the second set of nodes of the organization to which the service request belongs based on the organization identifier and the nodes of each organization; finally, determine the first node based on the nodes that belong to the first set and belong to the second set.
- the node of the alliance chain corresponding to the service request can be determined according to Table 3, and the node of the organization corresponding to the service request can be determined according to Table 2.
- the service request corresponding to alliance chain 1 according to "Org A, APPID A1, SeqNo 50" and Table 1
- the first set of nodes of alliance chain 1 is "node A1, node A4, node B1, and node C1 "
- determine that the second set of nodes of organization A is "node A1, node A2, node A3, node A4"
- the nodes that belong to both the first and second sets are "node A1, node A4", according to "node A1, node A4" determines the first node.
- the first node can be randomly determined from the greater than one node, or according to a preset rule OK, there is no limit here.
- the node may include the IP address and listening port corresponding to the node.
- the service to be processed may be sent to the first node according to the IP address and listening port of the first node, so that the first node Process the pending business.
- the contract information of the routing chain can also be modified.
- the routing rules of each organization can be modified. Specifically, the modification information of the routing rules is obtained, and the modification information of the routing rules is sent to the routing chain. So that the nodes of the routing chain modify the contract information of the routing chain according to the modification information of the routing rules. For example, if the routing rules of organization B need to be modified, the consortium chain corresponding to the serial number range of APPID B1 from "100 to 200" is modified to consortium chain 1, then it can be modified directly in organization B and the modification information will be sent The node to the routing chain, as shown in Figure 1, can be sent to node B3, and node B3 modifies the contract information of the routing chain according to the modification information.
- Step 301 the organization obtains the business request
- Step 302 The organization sends a contract information acquisition request to the routing chain node
- Step 303 The routing chain node sends the contract information of the routing chain to the institution;
- Step 304 The organization determines the alliance chain corresponding to the business request according to the business request and the contract information of the routing chain;
- Step 305 The organization determines the first node according to the alliance chain corresponding to the business request
- Step 306 The organization sends the service to be processed to the first node
- Step 307 The first node processes the service to be processed.
- the system can also include a proxy (proxy server), the proxy can be located in the organization, or independent of the organization, the proxy is used by the agency to complete the above area
- a proxy proxy server
- the proxy can be located in the organization, or independent of the organization, the proxy is used by the agency to complete the above area
- the load balancing method of multiple alliance chains in the block chain Specifically, after the organization obtains the business request, it sends the business request to the proxy, and the proxy reads the contract information in the routing chain, and determines the relationship with the The alliance chain corresponding to the business request, the alliance chain corresponding to the business request processes the pending business in the business request, and feeds back the successful result of the business to the proxy, and the proxy responds to the agency with the execution result.
- the routing chain is a block chain composed of nodes of institutions in multiple alliance chains, and the contract information of the routing chain is jointly maintained by multiple institutions.
- the alliance chain corresponding to the business request can be determined based on the business request and the contract information of the routing chain, and after the first node is determined, the pending business is sent to the first Nodes, the alliance chain corresponding to the business request determined in this way and the first node can effectively achieve the load balance of the multiple alliance chains, that is, the contract information of a routing chain is maintained by multiple agencies to avoid inconsistencies in the routing rules of each agency. As a result, load balancing of multiple alliance chains cannot be realized.
- FIG. 5 exemplarily shows the structure of a load balancing device for multiple alliance chains in a blockchain provided by an embodiment of the present invention, which can execute a load balancing method for multiple alliance chains in a blockchain The process.
- the device includes:
- the transceiver unit 501 is configured to obtain service requests and contract information of a routing chain; the routing chain is a block chain composed of nodes of institutions in the multi-consortium chain; the service request includes a service to be processed;
- the processing unit 502 is configured to determine the alliance chain corresponding to the service request according to the service request and the contract information of the routing chain; determine the first node according to the alliance chain corresponding to the service request, and send the service to be processed To the first node; the first node is a node used to process the service to be processed in the multiple alliance chain.
- the contract information of the routing chain includes routing rules of each organization;
- the service request includes an organization ID, a service ID, and a serial number;
- the processing unit 502 is specifically configured to:
- the routing rules of the organization to which the service request belongs are queried, and the alliance chain corresponding to the service request is determined.
- the contract information of the routing chain includes the nodes of each organization and the nodes of each alliance chain;
- the service request includes the identifier of the organization;
- the processing unit 502 is specifically configured to:
- the transceiver unit 501 is specifically configured to:
- the transceiver unit 501 is further configured to:
- the modification information of the routing rule is sent to the node of the routing chain, so that the node of the routing chain can modify the contract information of the routing chain according to the modification information of the routing rule.
- an embodiment of the present invention also provides a computing device, as shown in FIG. 6, including:
- the memory 601 is used to store program instructions
- the processor 602 is configured to call the program instructions stored in the memory, and execute the load balancing method of the multiple alliance chains in the blockchain according to the obtained program.
- embodiments of the present invention also provide a computer-readable non-volatile storage medium, including computer-readable instructions, when the computer reads and executes the computer-readable instructions, the computer executes the above-mentioned blocks.
- Load balancing method of multiple alliance chains in the chain when the computer reads and executes the computer-readable instructions, the computer executes the above-mentioned blocks.
- the embodiments of the present invention also provide a computer program product.
- the computer program product includes a computer program stored on a computer-readable non-volatile storage medium.
- the computer program includes program instructions. When the program instructions are executed by the computer, the computer is caused to execute the load balancing method of the multiple alliance chains in the blockchain.
- These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
- the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
- These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
- the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本发明公开了一种区块链中多联盟链的负载均衡方法及装置,该方法包括,获取业务请求和路由链的合约信息,其中,路由链是由多联盟链中的机构的节点组成的区块链,业务请求包括待处理业务,根据业务请求和路由链的合约信息,确定业务请求对应的联盟链,根据业务请求对应的联盟链确定第一节点,并将待处理业务发送至第一节点,通过多机构共同维护一个路由链的合约信息,避免出现由于各机构的路由规则不一致,导致无法实现多联盟链的负载均衡。
Description
相关申请的交叉引用
本申请要求在2019年03月12日提交中国专利局、申请号为201910184051.7、申请名称为“一种区块链中多联盟链的负载均衡方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本发明实施例属于金融科技(Fintech)领域,尤其涉及一种区块链(Blockchain)中多联盟链的负载均衡方法及装置。
区块链是一种分布式共享账本数据库,联盟链是一种由互相信任的机构节点组成,节点之间建立连接、数据传输均采用安全、可靠的方式,比如认证,IP(Internet Protocol,网络之间互连的协议)白名单等,外部节点无法加入的区块链体系。现有的业务请求量比较大,单链的性能和存储无法满足业务需求,因此需要引入多链技术,现有的区块链中多联盟链的负载均衡主要通过各接入机构的路由配置文件,来确定上链请求发送到哪一条联盟链,以实现多联盟链的负载均衡。
但现有技术中,每个机构需要维护各自的路由配置文件,一旦需要对路由配置文件进行修改时,各机构间需要同步修改,该情况可能会出现路由规则不一致的情况,无法实现多联盟链间的负载均衡。
发明内容
本发明实施例提供一种区块链中多联盟链的负载均衡方法及装置,通过多机构共同维护一个路由链的合约信息,避免出现由于各机构的路由规则不一致,导致无法实现多联盟链的负载均衡。
本发明实施例提供的一种区块链中多联盟链的负载均衡方法,包括:
获取业务请求和路由链的合约信息;所述路由链是由所述多联盟链中的机构的节点组成的区块链;所述业务请求包括待处理业务;
根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链;
根据所述业务请求对应的联盟链确定第一节点,并将所述待处理业务发送至所述第一节点;所述第一节点为所述多联盟链中用于处理所述待处理业务的节点。
上述技术方案中,获取业务请求和路由链的合约信息,其中,路由链是由多联盟链中的机构的节点组成的区块链,路由链的合约信息是由多机构共同维护的,也就避免出现各机构路由配置文件不一致的问题,进一步根据业务请求和路由链的合约信息,即可以确定出业务请求对应的联盟链,并在确定出第一节点后,将待处理业务发送至第一节点,该方式确定出的业务请求对应的联盟链以及第一节点可有效达到多联盟链的负载均衡,即通过多机构共同维护一个路由链的合约信息,避免出现由于各机构的路由规则不一致,导致无法实现多联盟链的负载均衡。
可选的,所述路由链的合约信息包括各机构的路由规则;所述业务请求包括机构标识、业务标识和序列号;
所述根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链,包括:
根据所述机构标识、所述各机构的路由规则,确定所述业务请求所属机构的路由规则;
根据所述业务标识和序列号,查询所述业务请求所属机构的路由规则,确定出所述业务请求对应的联盟链。
上述技术方案中,路由链的合约信息包括各机构的路由规则,业务请求包括机构标识、业务标识和序列号,根据各机构的路由规则、业务请求的机构标识、业务标识和序列号,即可以确定出业务请求对应的联盟链。路由链 的合约信息中包括各机构的路由规则,也就是各机构共同维护一个路由配置文件,该路由配置文件中包括各机构的路由规则,避免出现各机构维护各自的路由配置文件,导致各机构路由配置文件不一致,影响多链间的负载均衡的问题。
可选的,所述路由链的合约信息包括各机构的节点、各联盟链的节点;所述业务请求包括机构标识;
所述根据所述业务请求对应的联盟链确定第一节点,包括:
根据所述业务请求对应的联盟链、所述各联盟链的节点,确定所述业务请求对应的联盟链的节点的第一集合;
根据所述机构标识、所述各机构的节点,确定所述业务请求所属机构的节点的第二集合;
根据属于所述第一集合且属于所述第二集合的节点,确定第一节点。
上述技术方案中,路由链的合约信息包括各机构的节点、各联盟链的节点,业务请求包括机构标识,可以根据业务请求对应的联盟链、各联盟链的节点,确定出业务请求对应的联盟链的所有节点的集合,即第一集合,进一步根据机构标识、各机构的节点,确定业务请求所属机构的节点,即第二集合,根据同属于第一集合和第二集合的节点确定第一节点,也就是用于处理待处理业务的节点。
可选的,所述获取路由链的合约信息,包括:
发送合约信息获取请求至所述路由链的节点;
接收所述路由链的节点反馈的所述路由链的合约信息。
上述技术方案中,多个机构共同维护一个路由链的合约信息,该路由链的合约信息为多联盟链中的机构的节点组成的区块链的合约信息,在需要获取该路由链的合约信息时,可以向路由链的节点发送合约信息获取请求,并接收路由链的反馈,从而获取到该路由链的合约信息。
可选的,还包括:
获取路由规则的修改信息;
将所述路由规则的修改信息发送至所述路由链的节点,以使所述路由链的节点根据所述路由规则的修改信息对所述路由链的合约信息进行修改。
上述技术方案中,当需要修改机构的路由规则时,可以获取该路由规则的修改信息,并将该路由规则的修改信息发送至路由链的节点,从而修改路由链的合约信息。在修改生效后,各机构可以直接从路由链中获取该路由链的合约信息,即可以获取到修改生效后的机构的路由规则,避免出现由于各机构的路由规则修改不同步,导致无法实现多联盟链的负载均衡。
相应的,本发明实施例还提供了一种区块链中多联盟链的负载均衡装置,包括:
收发单元,用于获取业务请求和路由链的合约信息;所述路由链是由所述多联盟链中的机构的节点组成的区块链;所述业务请求包括待处理业务;
处理单元,用于根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链;根据所述业务请求对应的联盟链确定第一节点,并将所述待处理业务发送至所述第一节点;所述第一节点为所述多联盟链中用于处理所述待处理业务的节点。
可选的,所述路由链的合约信息包括各机构的路由规则;所述业务请求包括机构标识、业务标识和序列号;
所述处理单元具体用于:
根据所述机构标识、所述各机构的路由规则,确定所述业务请求所属机构的路由规则;
根据所述业务标识和序列号,查询所述业务请求所属机构的路由规则,确定出所述业务请求对应的联盟链。
可选的,所述路由链的合约信息包括各机构的节点、各联盟链的节点;所述业务请求包括机构标识;
所述处理单元具体用于:
根据所述业务请求对应的联盟链、所述各联盟链的节点,确定所述业务请求对应的联盟链的节点的第一集合;
根据所述机构标识、所述各机构的节点,确定所述业务请求所属机构的节点的第二集合;
根据属于所述第一集合且属于所述第二集合的节点,确定第一节点。
可选的,所述收发单元具体用于:
发送合约信息获取请求至所述路由链的节点;
接收所述路由链的节点反馈的所述路由链的合约信息。
可选的,所述收发单元还用于:
获取路由规则的修改信息;
将所述路由规则的修改信息发送至所述路由链的节点,以使所述路由链的节点根据所述路由规则的修改信息对所述路由链的合约信息进行修改。
相应的,本发明实施例还提供了一种计算设备,包括:
存储器,用于存储程序指令;
处理器,用于调用所述存储器中存储的程序指令,按照获得的程序执行上述区块链中多联盟链的负载均衡方法。
相应的,本发明实施例还提供了一种计算机可读非易失性存储介质,包括计算机可读指令,当计算机读取并执行所述计算机可读指令时,使得计算机执行上述区块链中多联盟链的负载均衡方法。
相应的,本发明实施例还提供了一种计算机程序产品,所述计算机程序产品包括存储在计算机可读非易失性存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行上述区块链中多联盟链的负载均衡方法。
本发明实施例中,获取业务请求和路由链的合约信息,其中,路由链是由多联盟链中的机构的节点组成的区块链,路由链的合约信息是由多机构共同维护的,也就避免出现各机构路由配置文件不一致的问题,进一步根据业务请求和路由链的合约信息,即可以确定出业务请求对应的联盟链,并在确定出第一节点后,将待处理业务发送至第一节点,该方式确定出的业务请求对应的联盟链以及第一节点可有效达到多联盟链的负载均衡,即通过多机构 共同维护一个路由链的合约信息,避免出现由于各机构的路由规则不一致,导致无法实现多联盟链的负载均衡。
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简要介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域的普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种***架构的示意图;
图2为本发明实施例提供的一种多联盟链的负载均衡方法的流程示意图;
图3为本发明实施例提供的一种多联盟链的负载均衡方法的流程示意图;
图4为本发明实施例提供的一种多联盟链的负载均衡方法的流程示意图;
图5为本发明实施例提供的一种多联盟链的负载均衡装置的结构示意图;
图6为本发明实施例提供的一种计算设备的结构示意图。
为了使本发明的目的、技术方案和优点更加清楚,下面将结合附图对本发明作进一步地详细描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本发明保护的范围。
本发明实施例提供区块链中多联盟链的负载均衡方法所适用的***架构,该***架构可以包括多个机构,多个机构中各个机构的节点组成联盟链以及路由链,示例性的,可以如图1所示,该***包括机构A、机构B、机构C,其中,机构A包括节点A1、节点A2、节点A3、节点A4,机构B包括节点B1、节点B2、节点B3、节点B4,机构C包括节点C1、节点C2、节点C3。节点A1、节点A4、节点B1、节点C1组成联盟链1,节点A2、节点B2、节 点B4、节点C2组成联盟链2,节点A3、节点B3、节点C3组成路由链。
本发明实施例中,路由链是由多联盟链中的机构的节点组成的区块链,路由链的合约信息包括一个路由配置文件,即各机构共同维护一个路由配置文件,该路由配置文件中包括各机构的路由规则,如图1,机构A、机构B、机构C确定路由链的合约信息,共同维护一个路由配置文件,该路由配置文件包括机构A的路由规则、机构B的路由规则、机构C的路由规则。若某个机构接收到业务请求之后,会根据路由链的合约信息确定出应该将该业务请求发送至哪一个联盟链中,从而实现多联盟链的负载均衡。
基于上述描述,图2示例性的示出了本发明实施例提供的一种区块链中多联盟链的负载均衡方法的流程,该流程可以由区块链中多联盟链的负载均衡装置执行。如图2所示,该流程具体包括:
步骤201,获取业务请求和路由链的合约信息。
本发明实施例中,业务请求可以包括以下参数中的任一项或组合:待处理业务、机构标识、业务标识和序列号。其中,机构标识即业务请求中待处理业务对应机构的标识,业务标识即该业务请求中待处理业务的业务标识,序列号为该待处理业务的序列号。结合图1,若机构A获取到一个业务请求,该业务请求中待处理业务对应的机构为机构A,则机构标识为“Org A”,该业务请求中的待处理业务的业务标识为“APPID A1”、序列号为“SeqNo 50”,则可以理解为,该业务请求中包括“Org A,APPID A1、SeqNo 50”。
本发明实施例中,路由链的合约信息可以包括以下参数中的任一项或组合:各机构的路由规则、各机构的节点、各联盟链的节点。各机构的路由规则包括各机构的业务标识、序列号的范围和联盟链标识,各机构的节点即各机构包含的节点,各联盟链的节点即各联盟链包含的节点。示例性的,如图1所示的架构中,各机构的路由规则可以参照表1所示,各机构的节点可以参照表2所示,各联盟链的节点可以参照表3所示。 表1
表2
机构 | 机构标识 | 机构的节点 |
机构A | Org A | 节点A1、节点A2、节点A3、节点A4 |
机构B | Org B | 节点B1、节点B2、节点B3、节点B4 |
机构C | Org B | 节点C1、节点C2、节点C3 |
表3
本发明实施例中,机构可以从路由链获取路由链的合约信息,机构发送合约信息获取请求至路由链的节点,路由链的节点接收到该合约信息获取请求后,将路由链的合约信息反馈至机构,机构接收该路由链的节点反馈的路由链的合约信息。
步骤202,根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链。
本发明实施例中,路由链的合约信息可以包括各机构的路由规则,业务请求包括机构标识、业务标识和序列号,具体的,先根据机构标识、各机构的路由规则,确定业务请求所属机构的路由规则,再根据业务标识和序列号,查询业务请求所属机构的路由规则,确定出业务请求对应的联盟链。
本发明实施例中,机构可以获取到待处理业务是本机构的业务请求,也可以获取到待处理业务不是本机构的业务请求,即机构A可以获取到机构标识为“Org A”的业务请求,也可以获取到机构标识为“Org B”的业务请求。
示例性的,若机构A获取到的业务请求包括“Org A,APPID A1、SeqNo50”,则可以根据“Org A,APPID A1、SeqNo 50”和表1确定出联盟链标识为Chain1,即该业务请求对应联盟链1。或者,若机构A获取到的业务请求包括“Org B,APPID B1、SeqNo 50”,则可以根据“Org B,APPID B1、SeqNo50”和表1确定出联盟链标识为Chain2,即该业务请求对应联盟链2。
步骤203,根据所述业务请求对应的联盟链确定第一节点,并将所述待处理业务发送至所述第一节点。
本发明实施例中,第一节点为多联盟链中用于处理待处理业务的节点。 也就是说,在步骤202中确定出业务请求对应的联盟链后,需要从该业务请求对应的联盟链中确定出处理该待处理业务的节点,该节点即为第一节点。
可选的,路由链的合约信息包括各机构的节点、各联盟链的节点,业务请求包括机构标识,先根据业务请求对应的联盟链、各联盟链的节点,确定业务请求对应的联盟链的节点的第一集合;再根据机构标识、各机构的节点,确定业务请求所属机构的节点的第二集合;最后根据属于第一集合且属于所述第二集合的节点,确定第一节点。
解释为,在确定出业务请求对应的联盟链后,可以根据表3确定出业务请求对应的联盟链的节点,根据表2确定出业务请求对应的机构的节点。例如,根据“Org A,APPID A1、SeqNo 50”和表1确定出业务请求对应联盟链1后,确定联盟链1的节点组成的第一集合为“节点A1、节点A4、节点B1、节点C1”,确定机构A的节点组成的第二集合为“节点A1、节点A2、节点A3、节点A4”,同属于第一集合、第二集合的节点为“节点A1、节点A4”,根据“节点A1、节点A4”确定出第一节点,此处可知,属于第一集合且属于第二集合的节点可以为一个或者大于一个,当属于第一集合且属于第二集合的节点为一个,则将该唯一一个节点确定为第一节点,当属于第一集合且属于第二集合的节点为大于一个时,可以从该大于一个的节点中随机确定出第一节点,也可以根据预先设定的规则确定,在此不做限定。
此外,节点可以包括节点所对应的IP地址和监听端口,在确定出第一节点后,可以根据第一节点的IP地址和监听端口,将待处理业务发送至第一节点,以使得第一节点对该待处理业务进行处理。
本发明实施例中,还可以对路由链的合约信息进行修改,进一步的,可以对各机构的路由规则进行修改,具体的,获取路由规则的修改信息,将路由规则的修改信息发送至路由链的节点,以使路由链的节点根据路由规则的修改信息对路由链的合约信息进行修改。例如,需要对机构B的路由规则进行修改,将APPID B1的序列号范围为“100~200”所对应的联盟链修改为联盟链1,则可以直接在机构B中修改,并将修改信息发送至路由链的节点, 如图1,可以发送至节点B3,节点B3根据该修改信息对路由链的合约信息进行修改。
为了更好的解释本发明实施例,下面将在具体的实施场景下描述该多联盟链的负载均衡流程,如图3所示,具体如下:
步骤301,机构获取业务请求;
步骤302,机构发送合约信息获取请求至路由链节点;
步骤303,路由链节点发送路由链的合约信息至机构;
步骤304,机构根据业务请求和路由链的合约信息,确定业务请求对应的联盟链;
步骤305,机构根据业务请求对应的联盟链确定第一节点;
步骤306,机构发送待处理业务至第一节点;
步骤307,第一节点处理待处理业务。
由于本实施例的具体实现方式已在其他实施例中描述,在此不作赘述。
本发明提供的另一个实施例可以如图4所示,其中,该***中还可以包括proxy(代理服务器),该proxy可以位于机构中,也可以独立于机构,proxy用于代理机构完成上述区块链中多联盟链的负载均衡方法,具体的,机构获取到业务请求后,将业务请求发送至proxy,proxy读取路由链中的合约信息,根据合约信息从多联盟链中确定出与该业务请求相对应的联盟链,该业务请求相对应的联盟链处理该业务请求中的待处理业务,并将业务成功的结果反馈至proxy,proxy向机构响应执行结果。
上述技术方案中,获取业务请求和路由链的合约信息,其中,路由链是由多联盟链中的机构的节点组成的区块链,路由链的合约信息是由多机构共同维护的,也就避免出现各机构路由配置文件不一致的问题,进一步根据业务请求和路由链的合约信息,即可以确定出业务请求对应的联盟链,并在确定出第一节点后,将待处理业务发送至第一节点,该方式确定出的业务请求对应的联盟链以及第一节点可有效达到多联盟链的负载均衡,即通过多机构共同维护一个路由链的合约信息,避免出现由于各机构的路由规则不一致, 导致无法实现多联盟链的负载均衡。
基于同一发明构思,图5示例性的示出了本发明实施例提供的一种区块链中多联盟链的负载均衡装置的结构,该装置可以执行区块链中多联盟链的负载均衡方法的流程。
该装置,包括:
收发单元501,用于获取业务请求和路由链的合约信息;所述路由链是由所述多联盟链中的机构的节点组成的区块链;所述业务请求包括待处理业务;
处理单元502,用于根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链;根据所述业务请求对应的联盟链确定第一节点,并将所述待处理业务发送至所述第一节点;所述第一节点为所述多联盟链中用于处理所述待处理业务的节点。
可选的,所述路由链的合约信息包括各机构的路由规则;所述业务请求包括机构标识、业务标识和序列号;
所述处理单元502具体用于:
根据所述机构标识、所述各机构的路由规则,确定所述业务请求所属机构的路由规则;
根据所述业务标识和序列号,查询所述业务请求所属机构的路由规则,确定出所述业务请求对应的联盟链。
可选的,所述路由链的合约信息包括各机构的节点、各联盟链的节点;所述业务请求包括机构标识;
所述处理单元502具体用于:
根据所述业务请求对应的联盟链、所述各联盟链的节点,确定所述业务请求对应的联盟链的节点的第一集合;
根据所述机构标识、所述各机构的节点,确定所述业务请求所属机构的节点的第二集合;
根据属于所述第一集合且属于所述第二集合的节点,确定第一节点。
可选的,所述收发单元501具体用于:
发送合约信息获取请求至所述路由链的节点;
接收所述路由链的节点反馈的所述路由链的合约信息。
可选的,所述收发单元501还用于:
获取路由规则的修改信息;
将所述路由规则的修改信息发送至所述路由链的节点,以使所述路由链的节点根据所述路由规则的修改信息对所述路由链的合约信息进行修改。
基于同一发明构思,本发明实施例还提供了一种计算设备,如图6所示,包括:
存储器601,用于存储程序指令;
处理器602,用于调用所述存储器中存储的程序指令,按照获得的程序执行上述区块链中多联盟链的负载均衡方法。
基于同一发明构思,本发明实施例还提供了一种计算机可读非易失性存储介质,包括计算机可读指令,当计算机读取并执行所述计算机可读指令时,使得计算机执行上述区块链中多联盟链的负载均衡方法。
基于同一发明构思,本发明实施例还提供了一种计算机程序产品,所述计算机程序产品包括存储在计算机可读非易失性存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行上述区块链中多联盟链的负载均衡方法。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设 备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。
Claims (13)
- 一种区块链中多联盟链的负载均衡方法,其特征在于,包括:获取业务请求和路由链的合约信息;所述路由链是由所述多联盟链中的机构的节点组成的区块链;所述业务请求包括待处理业务;根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链;根据所述业务请求对应的联盟链确定第一节点,并将所述待处理业务发送至所述第一节点;所述第一节点为所述多联盟链中用于处理所述待处理业务的节点。
- 如权利要求1所述的方法,其特征在于,所述路由链的合约信息包括各机构的路由规则;所述业务请求包括机构标识、业务标识和序列号;所述根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链,包括:根据所述机构标识、所述各机构的路由规则,确定所述业务请求所属机构的路由规则;根据所述业务标识和序列号,查询所述业务请求所属机构的路由规则,确定出所述业务请求对应的联盟链。
- 如权利要求1所述的方法,其特征在于,所述路由链的合约信息包括各机构的节点、各联盟链的节点;所述业务请求包括机构标识;所述根据所述业务请求对应的联盟链确定第一节点,包括:根据所述业务请求对应的联盟链、所述各联盟链的节点,确定所述业务请求对应的联盟链的节点的第一集合;根据所述机构标识、所述各机构的节点,确定所述业务请求所属机构的节点的第二集合;根据属于所述第一集合且属于所述第二集合的节点,确定第一节点。
- 如权利要求1所述的方法,其特征在于,所述获取路由链的合约信息, 包括:发送合约信息获取请求至所述路由链的节点;接收所述路由链的节点反馈的所述路由链的合约信息。
- 如权利要求1至4任一项所述的方法,其特征在于,还包括:获取路由规则的修改信息;将所述路由规则的修改信息发送至所述路由链的节点,以使所述路由链的节点根据所述路由规则的修改信息对所述路由链的合约信息进行修改。
- 一种区块链中多联盟链的负载均衡装置,其特征在于,包括:收发单元,用于获取业务请求和路由链的合约信息;所述路由链是由所述多联盟链中的机构的节点组成的区块链;所述业务请求包括待处理业务;处理单元,用于根据所述业务请求和路由链的合约信息,确定所述业务请求对应的联盟链;根据所述业务请求对应的联盟链确定第一节点,并将所述待处理业务发送至所述第一节点;所述第一节点为所述多联盟链中用于处理所述待处理业务的节点。
- 如权利要求6所述的装置,其特征在于,所述路由链的合约信息包括各机构的路由规则;所述业务请求包括机构标识、业务标识和序列号;所述处理单元具体用于:根据所述机构标识、所述各机构的路由规则,确定所述业务请求所属机构的路由规则;根据所述业务标识和序列号,查询所述业务请求所属机构的路由规则,确定出所述业务请求对应的联盟链。
- 如权利要求6所述的装置,其特征在于,所述路由链的合约信息包括各机构的节点、各联盟链的节点;所述业务请求包括机构标识;所述处理单元具体用于:根据所述业务请求对应的联盟链、所述各联盟链的节点,确定所述业务请求对应的联盟链的节点的第一集合;根据所述机构标识、所述各机构的节点,确定所述业务请求所属机构的 节点的第二集合;根据属于所述第一集合且属于所述第二集合的节点,确定第一节点。
- 如权利要求6所述的装置,其特征在于,所述收发单元具体用于:发送合约信息获取请求至所述路由链的节点;接收所述路由链的节点反馈的所述路由链的合约信息。
- 如权利要求6至9任一项所述的装置,其特征在于,所述收发单元还用于:获取路由规则的修改信息;将所述路由规则的修改信息发送至所述路由链的节点,以使所述路由链的节点根据所述路由规则的修改信息对所述路由链的合约信息进行修改。
- 一种计算设备,其特征在于,包括:存储器,用于存储程序指令;处理器,用于调用所述存储器中存储的程序指令,按照获得的程序执行权利要求1至5任一项所述的方法。
- 一种计算机可读非易失性存储介质,其特征在于,包括计算机可读指令,当计算机读取并执行所述计算机可读指令时,使得计算机执行如权利要求1至5任一项所述的方法。
- 一种计算机程序产品,其特征在于,所述计算机程序产品包括存储在计算机可读非易失性存储介质上的计算机程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使得计算机执行如权利要求1至5任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910184051.7 | 2019-03-12 | ||
CN201910184051.7A CN110011930B (zh) | 2019-03-12 | 2019-03-12 | 一种区块链中多联盟链的负载均衡方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020181985A1 true WO2020181985A1 (zh) | 2020-09-17 |
Family
ID=67166838
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/076490 WO2020181985A1 (zh) | 2019-03-12 | 2020-02-24 | 一种区块链中多联盟链的负载均衡方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110011930B (zh) |
WO (1) | WO2020181985A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112328605A (zh) * | 2020-11-26 | 2021-02-05 | 安徽继远软件有限公司 | 一种基于区块链的电力现场安全数据管理方法与*** |
CN112612816A (zh) * | 2020-12-01 | 2021-04-06 | 网易(杭州)网络有限公司 | 以太坊联盟链的业务结果查询方法、装置、设备及介质 |
CN113691621A (zh) * | 2021-08-24 | 2021-11-23 | 上海点融信息科技有限责任公司 | 一种区块链数据上链方法 |
CN115334038A (zh) * | 2022-08-20 | 2022-11-11 | 信通院(江西)科技创新研究院有限公司 | 一种基于区块链的appid申请管理方法和*** |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110535697B (zh) * | 2019-08-22 | 2021-05-11 | 杭州趣链科技有限公司 | 一种均衡区块链跨域广播网络负载的方法 |
CN111262959B (zh) * | 2020-01-13 | 2021-05-25 | 平安科技(深圳)有限公司 | 区块链节点访问方法、装置及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170228734A1 (en) * | 2016-02-10 | 2017-08-10 | Bank Of America Corporation | System for secure routing of data to various networks from a process data network |
CN108540536A (zh) * | 2018-03-16 | 2018-09-14 | 深圳前海微众银行股份有限公司 | 基于区块链的网络海量业务处理方法、设备及存储介质 |
CN108696594A (zh) * | 2018-05-27 | 2018-10-23 | 佛山市虚拟现实大数据产业研究院有限公司 | 一种市场监管区块链的大数据传输负载均衡方法及装置 |
CN109325366A (zh) * | 2018-08-22 | 2019-02-12 | 深圳前海微众银行股份有限公司 | 基于联盟链的业务处理方法、设备及计算机可读存储介质 |
CN109347955A (zh) * | 2018-10-19 | 2019-02-15 | 北京奇艺世纪科技有限公司 | 一种区块链网络***以及信息处理方法 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2019111909A (ru) * | 2016-10-03 | 2020-11-06 | Виза Интернэшнл Сервис Ассосиэйшн | Сетевая топология |
CN108323232B (zh) * | 2017-05-16 | 2020-01-24 | 北京大学深圳研究生院 | 一种多层级区块链***之间索引与链拓扑结构的维护方法 |
CN107231299A (zh) * | 2017-06-07 | 2017-10-03 | 众安信息技术服务有限公司 | 一种链路由及实现区块链跨链通信的*** |
CN108600315B (zh) * | 2018-03-22 | 2021-04-06 | 深圳市网心科技有限公司 | 区块链路由处理方法、装置及存储介质 |
CN109447643B (zh) * | 2018-10-31 | 2022-12-20 | ***股份有限公司 | 一种基于区块链的数据共享***及数据共享方法 |
-
2019
- 2019-03-12 CN CN201910184051.7A patent/CN110011930B/zh active Active
-
2020
- 2020-02-24 WO PCT/CN2020/076490 patent/WO2020181985A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170228734A1 (en) * | 2016-02-10 | 2017-08-10 | Bank Of America Corporation | System for secure routing of data to various networks from a process data network |
CN108540536A (zh) * | 2018-03-16 | 2018-09-14 | 深圳前海微众银行股份有限公司 | 基于区块链的网络海量业务处理方法、设备及存储介质 |
CN108696594A (zh) * | 2018-05-27 | 2018-10-23 | 佛山市虚拟现实大数据产业研究院有限公司 | 一种市场监管区块链的大数据传输负载均衡方法及装置 |
CN109325366A (zh) * | 2018-08-22 | 2019-02-12 | 深圳前海微众银行股份有限公司 | 基于联盟链的业务处理方法、设备及计算机可读存储介质 |
CN109347955A (zh) * | 2018-10-19 | 2019-02-15 | 北京奇艺世纪科技有限公司 | 一种区块链网络***以及信息处理方法 |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112328605A (zh) * | 2020-11-26 | 2021-02-05 | 安徽继远软件有限公司 | 一种基于区块链的电力现场安全数据管理方法与*** |
CN112328605B (zh) * | 2020-11-26 | 2024-01-12 | 安徽继远软件有限公司 | 一种基于区块链的电力现场安全数据管理方法与*** |
CN112612816A (zh) * | 2020-12-01 | 2021-04-06 | 网易(杭州)网络有限公司 | 以太坊联盟链的业务结果查询方法、装置、设备及介质 |
CN112612816B (zh) * | 2020-12-01 | 2023-06-30 | 网易(杭州)网络有限公司 | 以太坊联盟链的业务结果查询方法、装置、设备及介质 |
CN113691621A (zh) * | 2021-08-24 | 2021-11-23 | 上海点融信息科技有限责任公司 | 一种区块链数据上链方法 |
CN113691621B (zh) * | 2021-08-24 | 2023-10-13 | 上海点融信息科技有限责任公司 | 一种区块链数据上链方法 |
CN115334038A (zh) * | 2022-08-20 | 2022-11-11 | 信通院(江西)科技创新研究院有限公司 | 一种基于区块链的appid申请管理方法和*** |
CN115334038B (zh) * | 2022-08-20 | 2024-03-26 | 信通院(江西)科技创新研究院有限公司 | 一种基于区块链的appid申请管理方法和*** |
Also Published As
Publication number | Publication date |
---|---|
CN110011930B (zh) | 2022-06-24 |
CN110011930A (zh) | 2019-07-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020181985A1 (zh) | 一种区块链中多联盟链的负载均衡方法及装置 | |
WO2018076759A1 (zh) | 基于区块链的多链管理方法、***、电子装置及存储介质 | |
US11030217B2 (en) | Blockchain implementing cross-chain transactions | |
US10425375B2 (en) | Message sending method, apparatus, and system, and server | |
US11190525B2 (en) | Blockchain system and permission management method thereof | |
CN108540536B (zh) | 基于区块链的网络海量业务处理方法、设备及存储介质 | |
WO2018076760A1 (zh) | 基于区块链的交易事务处理方法、***、电子装置及存储介质 | |
EP3788578A1 (en) | Blockchain implementing cross-chain transactions | |
TW202020785A (zh) | 使用智慧型合約執行多方交易 | |
CN110599095B (zh) | 基于区块链网络的危废处理方法及区块链网络的节点 | |
JP2018147507A5 (zh) | ||
US20170085498A1 (en) | Accessing a cloud-based service using a communication device linked to another communication device via a peer-to-peer ad hoc communication link | |
US20200120039A1 (en) | Systems and methods for controlling access to broker resources | |
US9961125B2 (en) | Messaging API over HTTP protocol to establish context for data exchange | |
TW202027456A (zh) | 聯盟鏈的可信度驗證方法、系統、裝置及設備 | |
US9319449B2 (en) | Method, apparatus, and computer program product for processing data requests | |
WO2022193984A1 (zh) | 跨链进行数据传输的方法、装置、计算机设备、存储介质和计算机程序产品 | |
WO2020253634A1 (zh) | 一种数据处理方法、***及装置 | |
JP6920442B2 (ja) | ブロックチェーンシステムのノード間の通信を確立するための方法及びデバイス | |
US20180234416A1 (en) | Polymorphic configuration management for shared authorization or authentication protocols | |
CN114189525A (zh) | 服务请求方法、装置和电子设备 | |
WO2021068477A1 (zh) | 区块处理方法、装置、计算机设备及存储介质 | |
CN104468594A (zh) | 一种数据请求的方法、装置及*** | |
US20180255042A1 (en) | Hop latency network location identifier | |
WO2021114857A1 (zh) | 接口调用方法、装置、计算机设备和存储介质 |
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: 20769972 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 21/01/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20769972 Country of ref document: EP Kind code of ref document: A1 |