CN113315826B - Block chain management method and device, management service node and storage medium - Google Patents
Block chain management method and device, management service node and storage medium Download PDFInfo
- Publication number
- CN113315826B CN113315826B CN202110568668.6A CN202110568668A CN113315826B CN 113315826 B CN113315826 B CN 113315826B CN 202110568668 A CN202110568668 A CN 202110568668A CN 113315826 B CN113315826 B CN 113315826B
- Authority
- CN
- China
- Prior art keywords
- management service
- service node
- blockchain
- block chain
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A10/00—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE at coastal zones; at river basins
- Y02A10/40—Controlling or monitoring, e.g. of flood or hurricane; Forecasting, e.g. risk assessment or mapping
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a block chain management method, a block chain management device, a management service node and a storage medium, and relates to the technical field of data processing. The method comprises the following steps: receiving a calling request aiming at a first block chain sent by a block chain client; determining whether the first blockchain is within a blockchain partition of the first management service node; and if the first blockchain is in the blockchain partition of the first management service node, executing a calling operation on the first blockchain according to the calling request. And if the first block chain is in the block chain partition of the first management service node and the first block chain is managed by the first management service node, the first block chain is called by the first management service node. The management service node manages the block chains in the corresponding block chain partitions, so that data flood peaks of a single management service node are avoided, and the efficiency of managing the block chains is improved.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method and an apparatus for managing a block chain, a management service node, and a storage medium.
Background
The block chain is a distributed shared account book and a database, and has the characteristics of decentralization, no tampering, trace retaining in the whole process, traceability, collective maintenance, openness and transparency and the like. The adoption of a management service platform is also becoming critical to the management of the blockchain.
In the related art, a management service platform may be deployed with a plurality of management service nodes, where the management service platform needs to manage N block chains, and each management service node needs to manage N block chains.
However, in the related art, each management service node independently manages all block chains, which easily causes data flooding of a single management service node, and reduces the efficiency of managing the block chains.
Disclosure of Invention
The present invention aims to provide a method and an apparatus for managing a block chain, a management service node, and a storage medium, so as to solve the problem that in the related art, each management service node independently manages all block chains, which easily causes data flooding of a single management service node, and reduces the efficiency of managing the block chains.
In order to achieve the above purpose, the embodiment of the present invention adopts the following technical solutions:
in a first aspect, an embodiment of the present invention provides a method for managing a block chain, where the method is applied to a first management service node in a management service platform, and each management service node in the management service platform is used to manage a block chain partition corresponding to each management service node; the method comprises the following steps:
receiving a calling request aiming at a first block chain sent by a block chain client;
determining whether the first blockchain is within a blockchain partition of the first management service node;
and if the first blockchain is in the blockchain partition of the first management service node, executing a calling operation on the first blockchain according to the calling request.
Optionally, each management service node stores therein: a node list for each blockchain, the node list comprising: managing an identifier of a service management node of each block chain;
the determining whether the first blockchain is within a blockchain partition of the first management service node includes:
judging whether the identifier of the first management service node exists in a node list of the first block chain;
if the identifier of the first management service node exists in the node list of the first blockchain, determining that the first blockchain is in a blockchain partition of the first management service node;
if the identifier of the first management service node does not exist in the node list of the first blockchain, determining that the first blockchain is not in the blockchain partition of the first management service node.
Optionally, the method further includes:
if the identifier of the first management service node does not exist in the node list of the first block chain, sending the call request to a second management service node in the node list of the first block chain, so that the second management service node executes a call operation on the first block chain according to the call request.
Optionally, the method further includes:
receiving a calling result returned by the first block chain acquired by the second management service node;
and sending the calling result to the blockchain client.
Optionally, the method further includes:
receiving a newly-added request aiming at a second block chain sent by the block chain client;
judging whether the number of the block chains in the block chain subarea of the first management service node is greater than or equal to the preset number of the block chains corresponding to the first management service node;
and if the number of the blockchains in the blockchain partition of the first management service node is less than the preset number of blockchains, adding the second blockchain into the blockchain partition of the first management service node.
Optionally, before adding the second blockchain to the blockchain partition of the first management service node, the method further includes:
judging whether the number of the management service nodes corresponding to the second block chain is larger than or equal to the preset number of the nodes corresponding to the second block chain;
the adding the second blockchain to the blockchain partition of the first management service node comprises:
and if the number of the management service nodes corresponding to the second blockchain is less than the preset number of nodes, adding the second blockchain into the blockchain partition of the first management service node, and adding the identifier of the first management service node into the management service node corresponding to the second blockchain.
Optionally, the method further includes:
and inquiring and updating stored management information from the fragment configuration database at preset time intervals, wherein the management information comprises: the block chain partition of each management service node and the management information of the management service node corresponding to each block chain.
Optionally, the management information further includes: all management service node information, all managed blockchain information.
Optionally, the method further includes:
adding the second blockchain to the blockchain partition of the first management service node stored in the fragment configuration database;
and adding the identifier of the first management service node to the management service node corresponding to the second block chain stored in the fragment configuration database.
Optionally, the method further includes:
receiving a deletion request aiming at a third block chain sent by the block chain client;
deleting the third blockchain from the blockchain partition of the first management service node;
and deleting the management service node corresponding to the third block chain.
Optionally, the method further includes:
and sending a deletion request of the third block chain to each management service node corresponding to the third block chain, so that each management service node corresponding to the third block chain deletes the third block chain from the corresponding block chain partition.
Optionally, the method further includes:
deleting the third block chain in the block chain partition of the first management service node stored in the fragment configuration database;
and deleting the management service node corresponding to the third block chain stored in the fragment configuration database.
In a second aspect, an embodiment of the present invention provides a device for managing a block chain, where the device is applied to a first management service node in a management service platform, and each management service node in the management service platform is configured to manage a block chain partition corresponding to each management service node; the device comprises:
the receiving module is used for receiving a calling request aiming at a first block chain sent by a block chain client;
a determining module, configured to determine whether the first blockchain is within a blockchain partition of the first management service node;
and the calling module is used for executing calling operation on the first block chain according to the calling request if the first block chain is in the block chain partition of the first management service node.
Optionally, each management service node stores therein: a node list for each blockchain, the node list comprising: managing an identifier of a service management node of each block chain;
the judging module is further configured to judge whether the identifier of the first management service node exists in the node list of the first block chain; if the identifier of the first management service node exists in the node list of the first blockchain, determining that the first blockchain is in a blockchain partition of the first management service node; if the identifier of the first management service node does not exist in the node list of the first blockchain, determining that the first blockchain is not in the blockchain partition of the first management service node.
Optionally, the apparatus further comprises:
a first sending module, configured to send the call request to a second management service node in the node list of the first block chain if the identifier of the first management service node does not exist in the node list of the first block chain, so that the second management service node performs a call operation on the first block chain according to the call request.
Optionally, the apparatus further comprises:
a first receiving module, configured to receive a call result returned by the first blockchain, where the call result is obtained by the second management service node;
and the second sending module is used for sending the calling result to the block chain client.
Optionally, the apparatus further comprises:
a second receiving module, configured to receive a new addition request for a second blockchain sent by the blockchain client;
a first determining module, configured to determine whether the number of blockchains in a blockchain partition of the first management service node is greater than or equal to a preset number of blockchains corresponding to the first management service node;
a first adding module, configured to add the second blockchain to the blockchain partition of the first management service node if the number of blockchains in the blockchain partition of the first management service node is smaller than the preset number of blockchains.
Optionally, the apparatus further comprises:
a second determining module, configured to determine whether the number of management service nodes corresponding to the second blockchain is greater than or equal to a preset number of nodes corresponding to the second blockchain;
the first adding module is further configured to add the second blockchain to the blockchain partition of the first management service node if the number of the management service nodes corresponding to the second blockchain is smaller than the preset number of nodes, and add the identifier of the first management service node to the management service node corresponding to the second blockchain.
Optionally, the apparatus further comprises:
an updating module, configured to query and update stored management information from a segment configuration database at a preset time interval, where the management information includes: the block chain partition of each management service node and the management service node management information corresponding to each block chain.
Optionally, the management information further includes: all management service node information, all managed blockchain information.
Optionally, the apparatus further comprises:
a second adding module, configured to add the second blockchain to the blockchain partition of the first management service node stored in the fragment configuration database; and adding the identifier of the first management service node to the management service node corresponding to the second block chain stored in the fragment configuration database.
Optionally, the apparatus further comprises:
a third receiving module, configured to receive a deletion request for a third blockchain sent by the blockchain client;
a first deleting module, configured to delete the third blockchain from the blockchain partition of the first management service node; and deleting the management service node corresponding to the third block chain.
Optionally, the apparatus further comprises:
a third sending module, configured to send a deletion request of the third block chain to each management service node corresponding to the third block chain, so that each management service node corresponding to the third block chain deletes the third block chain from the corresponding block chain partition.
Optionally, the apparatus further comprises:
a second deleting module, configured to delete the third blockchain in the blockchain partition of the first management service node stored in the fragmentation configuration database; and deleting the management service node corresponding to the third block chain stored in the fragment configuration database.
In a third aspect, an embodiment of the present invention further provides a management service node, including: a memory storing a computer program executable by the processor, and a processor implementing the method for managing a block chain according to any one of the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is read and executed, the management method for a block chain according to any one of the above first aspects is implemented.
The invention has the beneficial effects that: the embodiment of the application provides a block chain management method, which is applied to a first management service node in a management service platform, wherein each management service node in the management service platform is used for managing a block chain partition corresponding to each management service node; the method comprises the following steps: receiving a calling request aiming at a first block chain sent by a block chain client; determining whether the first blockchain is within a blockchain partition of the first management service node; and if the first blockchain is in the blockchain partition of the first management service node, executing a calling operation on the first blockchain according to the calling request. And if the first block chain is in the block chain partition of the first management service node, the first block chain is managed by the first management service node, and the first block chain is called by the first management service node. The block chains in the corresponding block chain partitions are managed by the management service nodes, so that data flood peaks of single management service nodes are avoided, and the efficiency of managing the block chains is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic structural diagram of a block chain management system according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for managing a block chain according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a block chain management method according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a block chain management method according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a block chain management method according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a block chain management method according to an embodiment of the present invention;
fig. 7 is a flowchart illustrating a block chain management method according to an embodiment of the present invention;
fig. 8 is a flowchart illustrating a method for managing a block chain according to an embodiment of the present invention;
fig. 9 is a flowchart illustrating a block chain management method according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a management apparatus for a block chain according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a management service node according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it should be noted that if the terms "upper", "lower", etc. are used for indicating the orientation or positional relationship based on the orientation or positional relationship shown in the drawings or the orientation or positional relationship which is usually arranged when the product of the application is used, the description is only for convenience of describing the application and simplifying the description, but the indication or suggestion that the referred device or element must have a specific orientation, be constructed in a specific orientation and operation, and thus, cannot be understood as the limitation of the application.
Furthermore, the terms "first," "second," and the like in the description and in the claims, as well as in the drawings, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
Fig. 1 is a schematic structural diagram of a management system of a block chain according to an embodiment of the present invention, as shown in fig. 1, the management system of the block chain includes: client device 101, management service platform 102, blockchain set 103.
The client device 101 may communicate with the management service platform 102, and the blockchain client is installed on the client device 101. In addition, multiple blockchains may be included in blockchain set 103, and management service platform 102 communicates with each blockchain in the blockchains.
In some embodiments, the blockchain client may send a call request for a first blockchain to the management service platform 102; the management service platform 102 may receive the call request for the first blockchain, determine whether the first blockchain is in the blockchain partition of the first management service node, and if the first blockchain is in the blockchain partition of the first management service node, perform a call operation on the first blockchain according to the call request.
As shown in fig. 1, the management service platform 102 may have a plurality of management service nodes (a management service node a, a management service node B, and a management service node N), and each management service node may perform communication to implement forwarding of a transaction, where the management service node may implement forwarding of a user transaction and querying of a state of a link node. Block chains after fragmentation (fragment 1, fragment 2, fragment x, where fragment 1 corresponds to block chain a and block chain B, fragment 2 corresponds to block chain C and block chain D, fragment x corresponds to block chain N1 and block chain N2), and block chain fragments corresponding to each management service node are deployed in block chain set 103.
Optionally, the client device 101 may be a terminal or a server, which is not specifically limited in this embodiment of the present application. In addition, the management service platform 102 may be a base platform, and the management service node may be referred to as a base node, a base service node, or a base management service node.
In this embodiment of the application, each management service node has a corresponding blockchain partition, partition management of each management service node on a blockchain is achieved, and when a call request for a first blockchain is received, if the first blockchain is in the blockchain partition of the first management service node, which indicates that the first blockchain is managed by the first management service node, the first blockchain is called by the first management service node. The block chains in the corresponding block chain partitions are managed by the management service nodes, so that data flood peaks of single management service nodes are avoided, and the efficiency of managing the block chains is improved.
The following explains a management method of a block chain provided in the embodiment of the present application, with a first management service node in the management service platform 102 as an execution subject. The first management service node may be any one of the management service platforms, and each management service node in the management service platform 102 is configured to manage a block chain partition corresponding to each management service node.
Fig. 2 is a schematic flowchart of a block chain management method according to an embodiment of the present invention, and as shown in fig. 2, the method may include:
s201, receiving a calling request for a first block chain sent by a block chain client.
The first blockchain may be one blockchain in the set of blockchains.
In some embodiments, a user may perform a call operation for a first blockchain at a blockchain client, the blockchain client may determine a call request in response to the call operation, the blockchain client may send the call request for the first blockchain to a first management service node of a management service platform, and the first management service node of the management service platform may receive the call request.
In this embodiment of the present application, the invoking request may include: a block chain transaction request, a block chain state query request and a block chain contract data query request. The block chain state query request may include: block high query request and block out speed query request.
S202, whether the first blockchain is in the blockchain partition of the first management service node is judged.
Each management service node is provided with a corresponding block chain partition, and the block chains contained in the block chain partition corresponding to each management node are partial block chains in the block chain set.
It should be noted that one blockchain may be in blockchain partitions of different management service nodes, and of course, one blockchain may also be in only one blockchain partition of a management service node, which is not specifically limited in this embodiment of the present application.
In some embodiments, a first management service node of the management service platform may traverse the blockchain identifiers in the blockchain partition of the first management service node and determine whether the identifier of the first blockchain exists in the blockchain identifiers in the blockchain partition of the first management service node.
S203, if the first block chain is in the block chain partition of the first management service node, executing a calling operation on the first block chain according to the calling request.
In this embodiment, if the first blockchain is in the blockchain partition of the first management service node, it is indicated that the first blockchain is managed by the first management service node, and therefore, the first management service node may be adopted to perform a call operation on the first blockchain according to the call request.
In addition, after the first management service node executes the calling operation on the first blockchain according to the calling request, the first blockchain can return a calling result to the first management service node; the first management service node can receive the calling result and send the calling result to the blockchain client; accordingly, the blockchain client may receive the call result.
To sum up, the embodiment of the present application provides a block chain management method, which is applied to a first management service node in a management service platform, where each management service node in the management service platform is used to manage a block chain partition corresponding to each management service node; the method comprises the following steps: receiving a calling request aiming at a first block chain sent by a block chain client; determining whether the first blockchain is within a blockchain partition of the first management service node; and if the first blockchain is in the blockchain partition of the first management service node, executing a calling operation on the first blockchain according to the calling request. And if the first block chain is in the block chain partition of the first management service node, the first block chain is managed by the first management service node, and the first block chain is called by the first management service node. The block chains in the corresponding block chain partitions are managed by the management service nodes, so that data flood peaks of single management service nodes are avoided, and the efficiency of managing the block chains is improved.
Optionally, each management service node stores: a node list for each block chain, the node list comprising: an identification of the service management node that manages each block chain.
Fig. 3 is a flowchart of a method for managing a blockchain according to an embodiment of the present invention, and as shown in fig. 3, the determining whether a first blockchain is in a blockchain partition of a first management service node includes:
s301, judging whether the node list of the first block chain has the identifier of the first management service node.
The first management service node may store a node list of the first block chain. The node list of the first blockchain may include: an identification of a management service node for managing the first blockchain.
In some embodiments, the first management service node may traverse the identifier of the management service node in the node list of the first blockchain, and determine whether the identifier identical to the identifier of the first management service node exists in the node list of the first blockchain.
S302, if the identifier of the first management service node exists in the node list of the first block chain, determining that the first block chain is in the block chain partition of the first management service node.
It should be noted that, if the first blockchain is in the blockchain partition of the first management service node, it indicates that the first blockchain is managed by the first management service node, and therefore, the first management service node may be adopted to call the first blockchain.
S303, if the identifier of the first management service node does not exist in the node list of the first blockchain, determining that the first blockchain is not in the blockchain partition of the first management service node.
It should be noted that, if the first blockchain is not in the blockchain partition of the first management service node, it indicates that the first blockchain is not managed by the first management service node, and therefore, the first blockchain may not be called by the first management service node, and the first blockchain may be called by other management service nodes in the management service platform.
Optionally, the method may further include:
and if the identifier of the first management service node does not exist in the node list of the first block chain, sending a calling request to a second management service node in the node list of the first block chain, so that the second management service node executes calling operation on the first block chain according to the calling request.
Wherein the second management service node in the node list of the first blockchain may be any one of the management service nodes in the node list of the first blockchain.
In some embodiments, the first management service node may send a call request to the second management service node, the second management service node may determine that the first blockchain is within the blockchain partition of the second management service node, and then the second management service node may perform a call operation on the first blockchain according to the call request.
For example, the management service platform may include: 3 management service nodes (BaasSerera, baasServerB, baasServerN), the block chain managed by the management service platform comprises: (ChainA, chainB, chainC, chainD, chainN1, chainN 2). The management service node BaasSerera manages and calls the fragment 1 (ChainA, chainB), the management service node BaasSererb manages and calls the fragment 2 (ChainC, chainD), and the management service node BaasServerC manages and calls the fragment x (ChainN 1, chainN 2).
The first block chain can be ChainA, the calling request can reach any one management service node randomly, and if the calling request is directly sent to the BaasServerA, the ChainA can be directly operated in the BaasServerA; if the calling request is directly sent to the BaasServerB, the BaasServerB also forwards the request to the BaasServerA, so that the BaasServerA carries out calling operation on ChainA and returns a calling result.
In addition, the first block chain may be ChainD, if the call request is directly sent to basservera, basservera also forwards the request to basservera, so that basservera performs a call operation on ChainD and returns a call result, basservera returns the call result to basservera, and basservera returns the result to the block chain client.
Optionally, fig. 4 is a schematic flowchart of a management method for a block chain according to an embodiment of the present invention, and as shown in fig. 4, the method may further include:
s401, receiving a calling result returned by the first block chain acquired by the second management service node;
s402, sending the calling result to the block chain client.
It should be noted that the second management service node may perform a call operation on the first blockchain according to the call request, and the first blockchain may return a call result to the second management service node; the second management service node can receive the calling result and send the calling result to the blockchain client; the call result may be received to the blockchain client.
In some embodiments, the call request for the first blockchain sent by the blockchain client may also carry blockchain client information. After the second management service node obtains the call result returned by the first blockchain, the call result can be directly sent to the blockchain client according to the information of the blockchain client.
In the method for managing a block chain provided in the embodiment of the present application, an implementation process of a program code may be: a user input chain (chain) and a Request (Request); the acquisition chain is managed by which nodes: nodeList = chain2nodelismmap.get (chain); if the node list nodeList contains the current node baasNodeMame, directly calling; if the node list nodeList does not contain the current node baasNodeMame, one of the node list nodeList is randomly acquired to carry out forwarding transaction: forward (nodeName, chain, request).
In addition, after the target node receives the transaction, the target node executes chain calling and returns the result to the original node before forwarding; after receiving the calling result, the original node can return the result to the user. The target node may be a second management service node, and the original node may be the first management service node.
The program code of the above process is implemented as follows:
// user request invocation
public static Response callChainRequest(Chain chain,Request request){
// by which nodes the acquisition chain is managed
List<String>nodeList＝chain2NodeListMap.get(chain)；
If the current node manages this chain, it calls directly
if(nodeList.contains(baasNodeMame)){
return callRequest(request)；
}else{
If the current node does not manage the current chain, the request is forwarded randomly and the result is received
String nodeName＝nodeList.get(0)；
return forward(nodeName，chain，request)；
}
}
Optionally, fig. 5 is a schematic flowchart of a management method for a block chain according to an embodiment of the present invention, and as shown in fig. 5, the method may further include:
s501, a new adding request for a second block chain sent by the block chain client is received.
The second blockchain may be one blockchain in the set of blockchains.
In some embodiments, the user may perform an addition operation for the second blockchain at the blockchain client, the blockchain client may determine an addition request in response to the addition operation, the blockchain client may send the addition request for the second blockchain to the first management service node of the management service platform, and the first management service node of the management service platform may receive the addition request.
S502, judging whether the number of the block chains in the block chain subarea of the first management service node is more than or equal to the preset number of the block chains corresponding to the first management service node.
The memory of the first management service node may store a block chain partition of the first management service node and a preset number of block chains corresponding to the first management service node.
Optionally, the number of the preset block chains corresponding to the first management service node may be the maximum number of the preset block chains manageable by the first management service node. The number of the preset block chains corresponding to the first management service node may be represented as maxNode2ChainCount.
In addition, the first management service node may count the number of blockchains in the blockchain partition of the first management service node, and then perform the process of S502.
S503, if the number of the blockchains in the blockchain partition of the first management service node is less than the preset number of blockchains, adding the second blockchain to the blockchain partition of the first management service node.
It should be noted that, if the number of blockchains in the blockchain partition of the first management service node is less than the preset number of blockchains, which indicates that the number of blockchains managed by the first management service node does not reach the upper limit, the first management service node may manage the second blockchain, and thus, the second blockchain may be added to the blockchain partition of the first management service node.
In the embodiment of the present application, if the number of blockchains in the blockchain partition of the first management service node is greater than or equal to the preset number of blockchains, it indicates that the number of blockchains managed by the first management service node has reached the upper limit, and the first management service node cannot manage the second blockchain.
Optionally, fig. 6 is a schematic flowchart of a management method for a blockchain according to an embodiment of the present invention, and as shown in fig. 6, before the process of adding the second blockchain to the blockchain partition of the first management service node in S503, the method may further include:
s601, determining whether the number of management service nodes corresponding to the second blockchain is greater than or equal to the number of preset nodes corresponding to the second blockchain.
The memory of the first management service node may store a management service node corresponding to the second blockchain and a preset node number corresponding to the second blockchain.
Optionally, the number of the preset nodes corresponding to the second blockchain may be the maximum number of the management service nodes managing the second blockchain. The number of the preset nodes corresponding to the second blockchain may be denoted as maxChain2 nodermanagecount.
The process of adding the second blockchain to the blockchain partition of the first management service node in S503 may include:
s602, if the number of the management service nodes corresponding to the second blockchain is less than the preset number of nodes, adding the second blockchain to the blockchain partition of the first management service node, and adding the identifier of the first management service node to the management service node corresponding to the second blockchain.
The second blockchain may be added to a blockchain list corresponding to the first management service node, and the identifier of the first management service may be added to a node list corresponding to the second blockchain. The second block chain may be managed by the first management service node.
It should be noted that, if the number of the management service nodes corresponding to the second blockchain is greater than or equal to the preset number of nodes, it indicates that the number of the management service nodes managing the second blockchain exceeds the upper limit, and the first management service node cannot manage the second blockchain.
For example, the number of the predetermined blockchains may be 3, and the number of the predetermined nodes may be 2.
In terms of program code implementation, the newonemagechain method may be executed at regular time, so as to add the block chain to the first management service node.
The program code of the above process is implemented as follows:
// current node baas node name
static String baasNodeMame＝"BaasServerA"；
// maximum number of blockchains managed by each bas serving node
static int maxNode2ChainCount＝3；
// how many Bass service nodes can manage each blockchain at most
static int maxChain2NodeManageCount＝2；
Block chain list for/base node management and corresponding block chain list of base node name
public static Map<String,List<Chain>>nodeName2ChainListCMap＝new HashMap<>()；
// which ones of the base nodes of the blockchain is managed by correspond to the list of base nodes
Publicstatic Map<Chain，List<String>>chain2NodeListMap＝new HashMap<>()
//1, adding chains to Current node management
public static void newOneManageChain(Chain chain){
If/chain has been managed by greater than or equal to 2 Bass service nodes then abandon
if(chain2NodeListMap.get(chain).size()>＝maxChain2NodeManageCount){return；
}
Optionally, the method may further include:
and inquiring and updating stored management information from the fragment configuration database at preset time intervals, wherein the management information comprises: the block chain partition of each management service node and the management service node management information corresponding to each block chain.
Optionally, the management information further includes: all management service node information, all managed blockchain information.
The preset time duration may be set according to an actual requirement, for example, the preset time duration may be 30 seconds, or may also be 15 seconds or 20 seconds, which is not specifically limited in the embodiment of the present application. In the implementation of program codes, the method of yncnnodechinmanage can be executed at regular time, and the management information of the service platform cluster can be managed synchronously at regular time.
In this embodiment, the first management service node may update the queried management information to a memory corresponding to the first management service node. The blockchain partition of each management service node may be represented as nodeb name2ChainListCMap, and the information managed by the management service node corresponding to each blockchain may be represented as chain2 nodelilistmap. The first management service node may query whether the blockchain in the blockchain list can be continued to be managed by the continuation first management service node.
It should be noted that, when the first management service node queries and updates the stored management information from the fragmentation configuration database, the logic for adding the second blockchain to the first management service node may be executed.
The program code of the above process is implemented as follows:
// current node baas node name
static String baasNodeMame＝"BaasServerA"；
// maximum number of blockchains managed by each bas serving node
static int maxNode2ChainCount＝3；
// how many Bass service nodes can manage each blockchain at most
static int maxChain2NodeManageCount＝2；
Block chain list for/base node management and corresponding block chain list of base node name
public static Map<String,List<Chain>>nodeName2ChainListCMap＝new HashMap<>()；
// which ones of the base nodes that the blockchain manages correspond to the list of base nodes that the blockchain corresponds to
public static Map<Chain,List<String>>chain2NodeListMap＝newHashMap<>()；
// synchronizing the management information of the baas clusters
public static void syncNodeChainManage(){
// db query management information maintenance of all current nodes
findAllChainManagerInfo()；
In this embodiment, the fragment configuration database may store management information, and each management service node may perform initialization start, configure the number of preset block chains and the number of preset nodes, and configure the fragment configuration database.
For the sharding configuration database, sharding rules may be determined, which may include: the number of the preset block chains of each management service node and the number of the preset nodes corresponding to each block chain. For example, the management service node manages up to 3 blockchains, and each blockchain is managed by up to 2 management service nodes.
For example, a management service platform may manage 3 management service nodes (basservera, basserverb, basservern), and manage N block chains (ChainA, chainB, chainC, chainD). The management service node BaasServerA manages and calls the fragment 1 (ChainA, chainB, chainC), the management service node BaasServerA manages and calls the fragment 2 (ChainA, chainB, chainC), and the management service node BaasServerA manages and calls the fragment x (ChainD).
If 2 block chains ChainE and ChainF are added, the management service node BaasServeN can manage the added chains ChainE and ChainF, and the management service node BaasServeN is changed into the management service node BaasServeN to manage and call the fragment x (ChainD, chainE, chainF).
Optionally, fig. 7 is a schematic flowchart of a management method for a block chain according to an embodiment of the present invention, and as shown in fig. 7, the method may further include:
s701, partitioning the block chain of the first management service node stored in the partition configuration database, and adding a second block chain.
S702, adding the identifier of the first management service node to the management service node corresponding to the second block chain stored in the partition configuration database.
It should be noted that the first management service node may execute S701 to S702 for the fragment configuration database to update the fragment configuration database, so that other management nodes in the management service platform may obtain the latest management information from the fragment configuration database at a preset time interval.
Optionally, fig. 8 is a schematic flowchart of a management method for a block chain according to an embodiment of the present invention, and as shown in fig. 8, the method may further include:
and S801, receiving a deletion request for the third block chain sent by the block chain client.
Wherein the third blockchain may be one blockchain in the set of blockchains.
In some embodiments, a user may perform a delete operation for the third blockchain at the blockchain client, the blockchain client may determine a delete request in response to the delete operation, the blockchain client may send the delete request for the third blockchain to the first management service node of the management service platform, and the first management service node of the management service platform may receive the delete request.
S802, deleting the third block chain from the block chain partition of the first management service node.
Optionally, the first management service node may delete the third blockchain from the blockchain management list corresponding to the first management service node. The block chain management list corresponding to the first management service node may be represented as (nodename 2chainlistcmap.
And S803, deleting the management service node corresponding to the third block chain.
Optionally, the management service node program code corresponding to the third block chain may be represented as List < String > nodeList = chain 2nodelismmap.get (chain), and the process program code of the above S803 may be represented as chain 2nodelismmap.remove (chain).
Optionally, the method may further include:
and sending a deletion request of the third block chain to each management service node corresponding to the third block chain so that each management service node corresponding to the third block chain deletes the third block chain from the corresponding block chain partition.
For example, the management service platform has 3 management service nodes (BaasServerA, baasServerB, baasServerN), and manages N block chains (ChainA, chainB, chainC, chainD). The management service node BaasServerA manages and calls the fragment 1 (ChainA, chainB and ChainC), the management service node BaasServerB manages and calls the fragment 2 (ChainA, chainB and ChainC), and the management service node BaasServereN manages and calls the fragment x (ChainD).
If the block chain A is deleted at this time, the BaasServerA manages and calls the fragment 1 (ChainB, chainC), the BaasServerB manages and calls the fragment 2 (ChainB, chainC), and the BaasServereN manages and calls the fragment x (ChainD).
Optionally, fig. 9 is a schematic flowchart of a management method for a block chain according to an embodiment of the present invention, and as shown in fig. 9, the method may further include:
s901, deleting a third block chain in a block chain partition of the first management service node stored in the fragment configuration database;
and S902, deleting the management service node corresponding to the third block chain stored in the fragment configuration database.
It should be noted that the first management service node may execute S901 to S902 for the fragment configuration database to update the fragment configuration database, so that other management nodes in the management service platform may obtain the latest management information from the fragment configuration database at a preset time interval.
The program code of the above process is implemented as follows:
//2, delete chain management
public static void removeOneManageChain(Chain chain){
// performing blockchain management
nodeName2ChainListCMap.get(baasNodeMame).remove(chain)；
// by which nodes the acquisition chain is managed
List<String>nodeList＝chain2NodeListMap.get(chain)；
nodeList.forEach(s->{
// notify other nodes to also delete the chain
forwardRemoveOneManageChain(chain)；
})；
chain2NodeListMap.remove(chain)；
// update db, update nodeName2ChainListCMap, chain2NodeListMap to database }
To sum up, the embodiment of the present application provides a block chain management method, which is applied to a first management service node in a management service platform, where each management service node in the management service platform is used to manage a block chain partition corresponding to each management service node; the method comprises the following steps: receiving a calling request aiming at a first block chain sent by a block chain client; determining whether the first blockchain is within a blockchain partition of the first management service node; and if the first blockchain is in the blockchain partition of the first management service node, executing a calling operation on the first blockchain according to the calling request. Each management service node is provided with a corresponding block chain partition, partition management of each management service node on the block chain is achieved, and if the first block chain is in the block chain partition of the first management service node, the first block chain is called by the first management service node. The block chains in the corresponding block chain partitions are managed by the management service nodes, so that data flood peaks of single management service nodes are avoided, and the efficiency of managing the block chains is improved.
Moreover, the management service node divides the management block chain, and each management service node only manages a part of the block chain, so that the problem of processing performance of a single management service node is solved. The management of adding the block chain to the management service node and deleting the chain by the management service node can be realized, and the management of the block chain is convenient.
The following describes a management apparatus, a management service platform, a storage medium, and the like for executing a block chain management method provided in the present application, and specific implementation processes and technical effects thereof refer to relevant contents of the block chain management method, which are not described in detail below.
Fig. 10 is a schematic structural diagram of a management apparatus for a block chain according to an embodiment of the present invention, and as shown in fig. 10, the apparatus may include:
the device is applied to a first management service node in a management service platform, and each management service node in the management service platform is used for managing a block chain partition corresponding to each management service node; the device comprises:
a receiving module 1001, configured to receive a call request for a first blockchain sent by a blockchain client;
a determining module 1002, configured to determine whether the first blockchain is in a blockchain partition of the first management service node;
the invoking module 1003 is configured to, if the first blockchain is within the blockchain partition of the first management service node, execute an invoking operation on the first blockchain according to the invoking request.
Optionally, each management service node stores: a node list for each block chain, the node list comprising: managing an identifier of a service management node of each block chain;
the determining module 1002 is further configured to determine whether an identifier of a first management service node exists in a node list of the first block chain; if the identifier of the first management service node exists in the node list of the first block chain, determining that the first block chain is in a block chain partition of the first management service node; and if the identifier of the first management service node does not exist in the node list of the first blockchain, determining that the first blockchain is not in the blockchain partition of the first management service node.
Optionally, the apparatus further comprises:
a first sending module, configured to send a call request to a second management service node in the node list of the first block chain if the identifier of the first management service node does not exist in the node list of the first block chain, so that the second management service node performs a call operation on the first block chain according to the call request.
Optionally, the apparatus further comprises:
the first receiving module is used for receiving a calling result returned by the first block chain acquired by the second management service node;
and the second sending module is used for sending the calling result to the block chain client.
Optionally, the apparatus further comprises:
the second receiving module is used for receiving a newly-added request aiming at a second block chain, which is sent by the block chain client;
the first judging module is used for judging whether the number of the block chains in the block chain subarea of the first management service node is greater than or equal to the preset number of the block chains corresponding to the first management service node;
the first adding module is used for adding the second blockchain into the blockchain partition of the first management service node if the number of the blockchains in the blockchain partition of the first management service node is less than the preset number of the blockchains.
Optionally, the apparatus further comprises:
the second judging module is used for judging whether the number of the management service nodes corresponding to the second block chain is larger than or equal to the preset number of the nodes corresponding to the second block chain;
the first adding module is further configured to add the second blockchain to the blockchain partition of the first management service node if the number of the management service nodes corresponding to the second blockchain is less than the preset number of nodes, and add the identifier of the first management service node to the management service nodes corresponding to the second blockchain.
Optionally, the apparatus further comprises:
the updating module is used for inquiring and updating stored management information from the fragment configuration database at intervals of preset duration, and the management information comprises: the block chain partition of each management service node and the management information of the management service node corresponding to each block chain.
Optionally, the management information further includes: all management service node information, all managed blockchain information.
Optionally, the apparatus further comprises:
the second adding module is used for adding a second block chain to the block chain partition of the first management service node stored in the fragment configuration database; and adding the identifier of the first management service node to the management service node corresponding to the second block chain stored in the fragment configuration database.
Optionally, the apparatus further comprises:
a third receiving module, configured to receive a deletion request for a third blockchain sent by a blockchain client;
a first deleting module, configured to delete the third blockchain from the blockchain partition of the first management service node; and deleting the management service node corresponding to the third block chain.
Optionally, the apparatus further comprises:
a third sending module, configured to send a deletion request of the third block chain to each management service node corresponding to the third block chain, so that each management service node corresponding to the third block chain deletes the third block chain from the corresponding block chain partition.
Optionally, the apparatus further comprises:
the second deleting module is used for deleting a third block chain in the block chain partition of the first management service node stored in the fragment configuration database; and deleting the management service node corresponding to the third block chain stored in the fragment configuration database.
The above-mentioned apparatus is used for executing the method provided by the foregoing embodiment, and the implementation principle and technical effect are similar, which are not described herein again.
These above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Fig. 11 is a schematic structural diagram of a management service node according to an embodiment of the present invention, and as shown in fig. 11, the management service node includes: a processor 1101, a memory 1102.
The memory 1102 is used for storing programs, and the processor 1101 calls the programs stored in the memory 1102 to execute the above-described method embodiments. The specific implementation and technical effects are similar, and are not described herein again.
Optionally, the invention also provides a program product, for example a computer-readable storage medium, comprising a program which, when being executed by a processor, is adapted to carry out the above-mentioned method embodiments.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (13)
1. The block chain management method is applied to a first management service node in a management service platform, wherein each management service node in the management service platform is used for managing a block chain partition corresponding to each management service node; the method comprises the following steps:
receiving a calling request aiming at a first block chain sent by a block chain client;
determining whether the first blockchain is within a blockchain partition of the first management service node;
if the first blockchain is in the blockchain partition of the first management service node, executing a calling operation on the first blockchain according to the calling request;
each management service node stores therein: a node list for each blockchain, the node list comprising: managing an identifier of a service management node of each block chain;
the determining whether the first blockchain is within a blockchain partition of the first management service node includes:
judging whether the identifier of the first management service node exists in a node list of the first block chain;
if the identifier of the first management service node exists in the node list of the first blockchain, determining that the first blockchain is in a blockchain partition of the first management service node;
if the identifier of the first management service node does not exist in the node list of the first blockchain, determining that the first blockchain is not in the blockchain partition of the first management service node;
the method further comprises the following steps:
if the identifier of the first management service node does not exist in the node list of the first block chain, sending the calling request to a second management service node in the node list of the first block chain, so that the second management service node executes calling operation on the first block chain according to the calling request.
2. The method of claim 1, further comprising:
receiving a calling result returned by the first block chain acquired by the second management service node;
and sending the calling result to the blockchain client.
3. The method of claim 1, further comprising:
receiving a newly added request aiming at a second block chain sent by the block chain client;
judging whether the number of the block chains in the block chain subarea of the first management service node is greater than or equal to the preset number of the block chains corresponding to the first management service node;
and if the number of the blockchains in the blockchain partition of the first management service node is less than the preset number of blockchains, adding the second blockchain into the blockchain partition of the first management service node.
4. The method of claim 3, wherein prior to adding the second blockchain to the blockchain partition of the first management service node, the method further comprises:
judging whether the number of the management service nodes corresponding to the second block chain is larger than or equal to the preset number of the nodes corresponding to the second block chain;
the adding the second blockchain to the blockchain partition of the first management service node comprises:
and if the number of the management service nodes corresponding to the second blockchain is less than the preset node number, adding the second blockchain into the blockchain partition of the first management service node, and adding the identifier of the first management service node into the management service node corresponding to the second blockchain.
5. The method of claim 4, further comprising:
and inquiring and updating stored management information from the fragment configuration database at preset time intervals, wherein the management information comprises: the block chain partition of each management service node and the management service node management information corresponding to each block chain.
6. The method of claim 5, wherein the management information further comprises: all management service node information, all managed blockchain information.
7. The method of claim 5, further comprising:
adding the second blockchain to the blockchain partition of the first management service node stored in the fragment configuration database;
and adding the identifier of the first management service node to the management service node corresponding to the second block chain stored in the fragment configuration database.
8. The method of claim 1, further comprising:
receiving a deletion request aiming at a third block chain sent by the block chain client;
deleting the third blockchain from the blockchain partition of the first management service node;
and deleting the management service node corresponding to the third block chain.
9. The method of claim 8, further comprising:
and sending a deletion request of the third block chain to each management service node corresponding to the third block chain, so that each management service node corresponding to the third block chain deletes the third block chain from the corresponding block chain partition.
10. The method of claim 9, further comprising:
deleting the third block chain in the block chain partition of the first management service node stored in the fragment configuration database;
and deleting the management service node corresponding to the third block chain stored in the fragment configuration database.
11. The management device of the block chain is characterized by being applied to a first management service node in a management service platform, wherein each management service node in the management service platform is used for managing a block chain partition corresponding to each management service node; the device comprises:
the receiving module is used for receiving a calling request aiming at a first block chain sent by a block chain client;
a determining module, configured to determine whether the first blockchain is within a blockchain partition of the first management service node;
a calling module, configured to perform a calling operation on the first blockchain according to the calling request if the first blockchain is within the blockchain partition of the first management service node;
each management service node stores therein: a node list for each blockchain, the node list comprising: managing an identifier of a service management node of each block chain;
the judging module is further configured to judge whether the identifier of the first management service node exists in the node list of the first block chain; if the identifier of the first management service node exists in the node list of the first blockchain, determining that the first blockchain is in a blockchain partition of the first management service node; if the identifier of the first management service node does not exist in the node list of the first blockchain, determining that the first blockchain is not in the blockchain partition of the first management service node;
the device further comprises:
a first sending module, configured to send the call request to a second management service node in the node list of the first block chain if the identifier of the first management service node does not exist in the node list of the first block chain, so that the second management service node performs a call operation on the first block chain according to the call request.
12. A management service node, comprising: memory storing a computer program executable by the processor, and a processor implementing the method of managing a block chain according to any one of claims 1 to 10 when executing the computer program.
13. A storage medium, characterized in that it stores thereon a computer program which, when read and executed, implements the management method of a blockchain according to any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110568668.6A CN113315826B (en) | 2021-05-24 | 2021-05-24 | Block chain management method and device, management service node and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110568668.6A CN113315826B (en) | 2021-05-24 | 2021-05-24 | Block chain management method and device, management service node and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113315826A CN113315826A (en) | 2021-08-27 |
| CN113315826B true CN113315826B (en) | 2023-03-24 |
Family
ID=77374420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110568668.6A Active CN113315826B (en) | 2021-05-24 | 2021-05-24 | Block chain management method and device, management service node and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113315826B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756566A (en) * | 2018-12-27 | 2019-05-14 | 重庆小雨点小额贷款有限公司 | Date storage method, relevant device and storage medium based on block chain |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113766035B (en) * | 2017-03-28 | 2023-05-23 | 创新先进技术有限公司 | Service acceptance and consensus method and device |
| CN107886388B (en) * | 2017-09-22 | 2020-11-03 | 杭州云象网络技术有限公司 | Transportation credit and safety service platform for realizing polycentricity based on alliance chain and operation method thereof |
| US11035903B2 (en) * | 2018-12-19 | 2021-06-15 | International Business Machines Corporation | Monitoring of batteries in blockchain networks |
| CN110138586A (en) * | 2019-04-04 | 2019-08-16 | 平安科技（深圳）有限公司 | Block chain node administration method, electronic device, system and readable storage medium storing program for executing |
| CN110545273B (en) * | 2019-08-29 | 2022-05-03 | 广东昭阳信息技术有限公司 | Resource allocation method and system based on block chain application |
-
2021
- 2021-05-24 CN CN202110568668.6A patent/CN113315826B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756566A (en) * | 2018-12-27 | 2019-05-14 | 重庆小雨点小额贷款有限公司 | Date storage method, relevant device and storage medium based on block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113315826A (en) | 2021-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111555963B (en) | Message pushing method and device, electronic equipment and storage medium | |
| CN107104824B (en) | Network topology determination method and device | |
| EP1589691B1 (en) | Method, system and apparatus for managing computer identity | |
| EP2696555B1 (en) | Method and system for identifying storage device | |
| CN110543512B (en) | Information synchronization method, device and system | |
| CN112650812A (en) | Data fragment storage method and device, computer equipment and storage medium | |
| CN111984735A (en) | Data archiving method and device, electronic equipment and storage medium | |
| CN111338689A (en) | File calling method, device and equipment | |
| CN111026765A (en) | Dynamic processing method, equipment, storage medium and device for strictly balanced binary tree | |
| CN110737458A (en) | code updating method and related device | |
| CN113315826B (en) | Block chain management method and device, management service node and storage medium | |
| CN105653556B (en) | Data aging method and device | |
| US20180293317A1 (en) | Prefix matching using distributed tables for storage services compatibility | |
| CN110874365B (en) | Information query method and related equipment thereof | |
| EP3649532B1 (en) | Methods, systems, databases and network nodes of data communication networks for handling data posts | |
| CN113934742B (en) | Data updating method, node information storage method, electronic device and medium | |
| CN115687276A (en) | File processing method and device, electronic equipment and storage medium | |
| CN112162731B (en) | Data expansion method, device, storage medium and electronic device | |
| CN115412552A (en) | Method and system for block chain deployment configuration | |
| CN113626509A (en) | Data access method and device, electronic equipment and readable storage medium | |
| CN113741889A (en) | Method and equipment for intelligently accessing data of heterogeneous database | |
| CN111221847A (en) | Monitoring data storage method and device and computer readable storage medium | |
| CN111953722A (en) | Terminal address book synchronization method and device | |
| CN107770265A (en) | A kind of method of data synchronization, data synchronization unit and mobile terminal | |
| CN113364855A (en) | Block chain information management method, device, service platform, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |