CN110597923B - Block chain resource management method, device and storage medium - Google Patents
Block chain resource management method, device and storage medium Download PDFInfo
- Publication number
- CN110597923B CN110597923B CN201910933790.1A CN201910933790A CN110597923B CN 110597923 B CN110597923 B CN 110597923B CN 201910933790 A CN201910933790 A CN 201910933790A CN 110597923 B CN110597923 B CN 110597923B
- Authority
- CN
- China
- Prior art keywords
- resource
- management
- blockchain
- target
- management 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
- 238000007726 management method Methods 0.000 title abstract description 379
- 238000000034 method Methods 0.000 claims abstract description 34
- 238000004891 communication Methods 0.000 description 16
- 238000012545 processing Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 11
- 230000002093 peripheral effect Effects 0.000 description 10
- 230000001133 acceleration Effects 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 6
- 230000008520 organization Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 239000000919 ceramic Substances 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- GNFTZDOKVXKIBK-UHFFFAOYSA-N 3-(2-methoxyethoxy)benzohydrazide Chemical compound COCCOC1=CC=CC(C(=O)NN)=C1 GNFTZDOKVXKIBK-UHFFFAOYSA-N 0.000 description 1
- FGUUSXIOTUKUDN-IBGZPJMESA-N C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 Chemical compound C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 FGUUSXIOTUKUDN-IBGZPJMESA-N 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000006641 stabilisation Effects 0.000 description 1
- 238000011105 stabilization Methods 0.000 description 1
- 239000010409 thin film Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
- G06F9/5088—Techniques for rebalancing the load in a distributed system involving task migration
Abstract
The application discloses a block chain resource management method, a device and a storage medium, and relates to the technical field of networks. The method can acquire the resource locking information of the target management node of the blockchain, wherein the resource locking information is used for indicating to lock the target resource in the blockchain, and when the target resource is not locked, the resource locking information is sent to other management nodes of the blockchain except the target management node. When the target resource is not locked, the blockchain resource management device can send the resource locking information to other management nodes except the target management node of the blockchain, so that the target resource can be ensured not to be occupied by the other management nodes when occupied by the target management node, and the phenomenon that management operation failure is caused because the atomicity of management operation cannot be ensured when a plurality of management nodes perform management operation on the blockchain based on the target resource at the same time is avoided.
Description
Technical Field
The present disclosure relates to the field of network technologies, and in particular, to a method and apparatus for managing blockchain resources, and a storage medium.
Background
Currently, multiple organizations may deploy nodes to build blockchains for data sharing, which may be referred to as participants of a blockchain, each of which may perform management operations on the blockchain through its management node, e.g., may process join requests of other organizations, and install smart contracts.
In the related art, when a certain participant performs a management operation on a blockchain, other participants may perform the same management operation, that is, multiple participants may occupy the shared resource corresponding to the management operation at the same time, and perform the management operation on the blockchain based on the shared resource. For example, when processing a join request of another organization, there may be multiple participants simultaneously occupying a shared resource corresponding to the initiated vote, and the vote is initiated among the participants of the blockchain based on the shared resource to determine whether to agree to the other organization to join the cross-chain.
However, since the shared resource is generally only available to one participant at a time, the management operations performed by multiple participants on the blockchain based on the same shared resource have mutual exclusivity, and the sequential execution of the management operations cannot be guaranteed, that is, the atomicity of the management operations performed by each participant on the blockchain cannot be guaranteed, so that the management operations performed by the participants on the blockchain fail. Wherein atomicity refers to the property that the management operation has that is not broken.
Disclosure of Invention
The application provides a blockchain resource management method, a device and a storage medium, which can solve the problem of management operation failure of each participant on a blockchain caused by the fact that atomicity of management operation of each participant on the blockchain cannot be guaranteed in the related art. The technical scheme is as follows:
in one aspect, a blockchain resource management method is provided, the method including:
acquiring resource locking information of a target management node of a blockchain, wherein the resource locking information is used for indicating to lock target resources in the blockchain, the blockchain is provided with at least two management nodes, and the target management node is any management node in the at least two management nodes;
determining whether the target resource has been locked;
and when the target resource is not locked, sending the resource locking information to other management nodes of the blockchain except the target management node.
In another aspect, there is provided a blockchain resource management apparatus, the apparatus comprising:
the first acquisition module is used for acquiring resource locking information of a target management node of a blockchain, wherein the resource locking information is used for indicating to lock target resources in the blockchain, and the blockchain is provided with at least two management nodes;
A determining module for determining whether the target resource has been locked;
and the first sending module is used for sending the resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked.
Optionally, each management node of the blockchain includes a management component and an auxiliary component, the device is disposed in the auxiliary component, and the first obtaining module is configured to:
and acquiring the resource locking information sent by the management component in the target management node.
Optionally, the first sending module is configured to:
and when the target resource is not locked, sending the resource locking information to auxiliary components in other management nodes of the blockchain except the target management node.
Optionally, the first obtaining module is further configured to:
acquiring resource unlocking information sent by the management component, wherein the resource unlocking information is used for indicating unlocking of the target resource;
the first sending module is further configured to:
and sending the resource unlocking information to auxiliary components of other management nodes except the target management node of the blockchain.
Optionally, the auxiliary components in each management node of the blockchain form a sub-blockchain, and the first sending module is configured to:
the resource lock information is broadcast in the sub-blockchain when the target resource is not locked.
Optionally, the apparatus further includes:
the second acquisition module is used for acquiring the data to be stored sent by the management component;
the storage module is used for storing the data to be stored into a database of the target management node;
and the second sending module is used for sending the data to be stored to auxiliary components of other management nodes except the target management node of the blockchain.
Optionally, the apparatus further includes:
the receiving module is used for receiving data to be stored sent by auxiliary components of other management nodes except the target management node of the blockchain;
the storage module is used for:
and storing the data to be stored into a database of the target management node.
In yet another aspect, a blockchain resource management apparatus is provided that includes a processor and a memory having at least one instruction, at least one program, code set, or instruction set stored therein, the at least one instruction, at least one program, code set, or instruction set loaded and executed by the processor to implement the blockchain resource management method as described in the above aspects.
In yet another aspect, a storage medium having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein is provided, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded by the processor and performing the blockchain resource management method of the above aspect.
The beneficial effects that this application provided technical scheme brought include at least:
the application provides a method, a device and a storage medium for managing block chain resources, wherein the method can acquire resource locking information of a target management node of a block chain, the resource locking information is used for indicating to lock target resources in the block chain, and when the target resources are not locked, the resource locking information is sent to other management nodes of the block chain except the target management node. When the target resource is not locked, the blockchain resource management device can send the resource locking information to other management nodes except the target management node of the blockchain, so that the target resource can be ensured not to be occupied by the other management nodes when occupied by the target management node, and the phenomenon that management operation failure is caused because the atomicity of management operation cannot be ensured when a plurality of management nodes perform management operation on the blockchain based on the target resource at the same time is avoided.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an implementation environment according to an embodiment of the present application;
FIG. 2 is a flowchart of a blockchain resource management method provided by an embodiment of the present application;
fig. 3 is a schematic structural diagram of a management node according to an embodiment of the present application;
FIG. 4 is a flowchart of another blockchain resource management method provided by embodiments of the present application;
FIG. 5 is a schematic structural view of an auxiliary assembly according to an embodiment of the present application;
FIG. 6 is a schematic diagram of data synchronization between management nodes according to an embodiment of the present disclosure;
FIG. 7 is a flowchart of yet another blockchain resource management method provided by embodiments of the present application;
FIG. 8 is a schematic diagram of a block chain resource management device according to an embodiment of the present disclosure;
FIG. 9 is a schematic diagram of another blockchain resource management device according to the embodiments of the present application;
FIG. 10 is a schematic diagram of a block chain resource management device according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of another blockchain resource management device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Fig. 1 is a schematic structural view of an implementation environment according to an embodiment of the present application. As shown in fig. 1, the implementation environment may include: a pre-established blockchain 10, and at least two management nodes 20 that establish a communication connection with the blockchain 10, e.g., 3 management nodes 20 are shown in fig. 1. Each management node 20 may establish a communication connection with the blockchain 10 by wire or wirelessly. Each management node 20 may perform management operations on the blockchain 10 through the communication connection, such as issuing a smart contract, i.e., each management node 20 has management rights for the blockchain 10.
Where blockchain 10 may include multiple nodes, for example, fig. 1 shows only 6 nodes (node 101 through node 106). The plurality of nodes may establish a communication connection between themselves via a wired network or a wireless network and synchronize data via the communication connection. When any node receives data, the data may be broadcast to all nodes in the entire blockchain 10 (i.e., broadcast the data to the blockchain 10) so that other nodes in the blockchain 10 can receive and store the data. Any two management nodes 20 of the at least two management nodes 20 may also establish a communication connection, either by wire or wirelessly, and may synchronize management operation data for the blockchain 10 based on the communication connection. The management operation data is data obtained by performing management operation on the blockchain.
In the embodiment of the application, each of the at least two management nodes 20 and each of the blockchain 10 may be an electronic device. Alternatively, the electronic device may be a smart phone, tablet, notebook, desktop, dynamic video expert compression standard audio layer 4 (Moving Picture Experts Group Audio Layer Iv, MP 4) player or server, etc.
It should be noted that, among the plurality of nodes included in the blockchain 10, at least two nodes are deployed for different organizations, for example, referring to fig. 1, the 6 nodes may be deployed for three different organizations. Each organization has an internet data center (Internet Data Center, IDC) that may include a plurality of nodes, at least one of which is deployed in a blockchain 10 and at least one of which is a management node 20 of the blockchain 10. Accordingly, the 3 management nodes shown in FIG. 1 are nodes in IDCs of 3 different organizations.
By way of example, referring to FIG. 1, nodes 101 and 102 in blockchain 10 may be nodes deployed for the first organization, i.e., also nodes in IDC 1; nodes 103 and 104 in blockchain 10 may be nodes deployed by the second organization, i.e., also nodes in IDC 2; nodes 105 and 106 in blockchain 10 may be nodes deployed by the third organization, i.e., also nodes in IDC 3.
The embodiment of the application provides a block chain resource management method which can be applied to a block chain resource management device. Referring to fig. 2, the method may include:
step 301, obtaining resource locking information of a target management node of a blockchain.
The resource locking information is used for indicating to lock target resources in the blockchain. The target resource refers to any one of a plurality of shared resources in the blockchain, and the target management node may perform a target management operation on the blockchain based on the target resource. The blockchain has at least two management nodes, and the target management node is any one of the at least two management nodes.
Alternatively, the resource lock information may carry an identification of the target resource.
Step 302, determining whether the target resource has been locked.
In the embodiment of the application, the correspondence relationship between the identifier of the shared resource and the lock flag of the shared resource is recorded in the blockchain resource management device. When the blockchain resource management device acquires the resource locking information of the target management node, whether the target resource is locked or not can be determined according to the identification of the target resource carried in the resource locking information, the identification of the shared resource and the corresponding relation of the locking mark of the shared resource.
Step 303, when the target resource is not locked, sending resource locking information to other management nodes of the blockchain except the target management node.
Alternatively, the blockchain resource management device may send the resource locking information to other management nodes of the blockchain except the target management node based on the consensus algorithm.
In summary, the embodiments of the present application provide a blockchain resource management method, which may obtain resource locking information of a target management node of a blockchain, where the resource locking information is used to indicate to lock a target resource in the blockchain, and send the resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked. When the target resource is not locked, the blockchain resource management device can send the resource locking information to other management nodes except the target management node of the blockchain, so that the target resource can be ensured not to be occupied by the other management nodes when occupied by the target management node, and the phenomenon that management operation failure is caused because the atomicity of management operation cannot be ensured when a plurality of management nodes perform management operation on the blockchain based on the target resource at the same time is avoided.
In the embodiment of the present application, referring to fig. 3, each management node 20 of the blockchain may include a management component 201 and an auxiliary component 202 (may also be referred to as a multiparty administration plug-in), and the blockchain resource management method provided in the embodiment of the present application may be applied to the auxiliary component of the target management node. The following describes a blockchain resource management method as an example of the blockchain resource management method being applied to an auxiliary component of a target management node. Referring to fig. 3, the method may include:
step 401, obtaining resource locking information sent by a management component in a target management node.
The resource locking information is used for indicating to lock target resources in the blockchain. The target resource refers to any one of a plurality of shared resources in the blockchain, and the target management node may perform a target management operation on the blockchain based on the target resource. The blockchain has at least two management nodes, and the target management node is any management node of the blockchain.
Alternatively, the resource lock information may carry an identification of the target resource.
Step 402, determining whether the target resource has been locked.
In this embodiment of the present application, the auxiliary component of each management node records a correspondence between an identifier of the shared resource and a lock flag of the shared resource. When the auxiliary component of the target management node acquires the resource locking information, whether the target resource is locked or not can be determined according to the identification of the target resource carried in the resource locking information, the recorded correspondence between the identification of the shared resource and the locking mark of the shared resource.
If the target resource has been locked, step 403 may be performed. If the target resource is not locked, step 404 may be performed.
Step 403, sending a locking prompt message to a management component in the target management node.
The locking prompt information is used for indicating that the target resource is locked and the target resource cannot be acquired.
Step 404, sending resource lock information to auxiliary components in other management nodes of the blockchain, except the target management node.
In the embodiment of the application, the auxiliary component of the target management node can synchronize the resource locking information to the auxiliary components of other management nodes except the target management node of the blockchain based on the consensus algorithm so as to ensure the consistency of the resource locking information received by each management node of the other management nodes.
Alternatively, the consensus algorithm may comprise: the practical bayer fault tolerance (Practical Byzantine Fault Tolerance, PBFT) algorithm, or RAFT algorithm.
When the auxiliary components of the target management node determine that the target resource is not locked, the auxiliary components of the other management nodes except the auxiliary components of the target management node can send resource locking information to the auxiliary components of the other management nodes so that the auxiliary components of the other management nodes update the recorded identification of the shared resource and the corresponding relation of the locking mark of the shared resource according to the resource locking information, thereby ensuring that the other management nodes cannot repeatedly occupy the target resource, realizing the locking of the target resource, and further ensuring the atomicity of the management operation of the target management node on the block chain based on the target resource, namely ensuring that the management operation of the target management node on the block chain cannot be interrupted.
Fig. 5 is a schematic structural diagram of an auxiliary assembly according to an embodiment of the present application. Referring to fig. 5, the auxiliary component 202 of each management node may include a consensus module 2021, and the auxiliary component 202 of the target management node may synchronize the resource locking information to the consensus module 2021 of the other management node through the consensus module 2021 thereof, so that the other management nodes may acquire the resource locking information. Alternatively, the consensus module may be developed based on RAFT algorithm, for example, the consensus module may be ETCD. Among these, ETCD is a high availability key value storage system, mainly for shared configuration and service discovery.
It should be noted that the auxiliary components in each management node of the blockchain may constitute a sub-blockchain, that is, the auxiliary component in each management node is one node in the sub-blockchain. The target management node may broadcast the resource lock information in the sub-blockchain upon determining that the target resource is not locked so that each node (i.e., auxiliary component) in the sub-blockchain may acquire the resource lock information.
Because the blockchain has the tamper-proof characteristic, and each auxiliary component is a node in the sub-blockchain, the reliability of synchronous resource locking information can be effectively ensured, and after the target management node occupies target resources, the atomicity of target management operation of the target management node on the blockchain based on the target resources is further ensured.
The auxiliary component may determine the locking status of the target resource by executing the steps 401 to 404, and lock the target resource when the target resource is not locked.
In this embodiment of the present application, the management component of the target management node may acquire management operation data (i.e., data to be stored described below) of the blockchain, and after acquiring the management operation data, the target management node may synchronize the management operation data to other management nodes for the other management nodes to perform subsequent management operations.
Because the management components of all the management nodes of the blockchain are mutually independent, the auxiliary components of all the management nodes are communicated, and communication connection is established between the management component of each management node and the auxiliary component, the management component of the target management node can communicate with the management components of other management nodes through the auxiliary component, so that data synchronization is performed. And in order to ensure consistency of Data written into databases of respective management nodes of the blockchain, the management component may write the acquired management operation Data into its database (Data Base, DB) through the auxiliary component. In the process of writing the management operation data into the database through the auxiliary component, if the management operation data can be written into the database, the management operation data can be synchronized to the auxiliary components of other management nodes. If the management operation data cannot be written to the database, the management operation data cannot be synchronized to the auxiliary components of other management nodes.
Step 405, obtaining data to be stored sent by the management component.
When the target management node acquires the data to be stored, the data to be stored can be sent to the auxiliary component, and correspondingly, the auxiliary component can acquire the data to be stored, which is sent by the management component.
The data to be stored may be the management operation data of the management component to the blockchain. For example, the data to be stored may be a smart contract that the management component installs on a node of the blockchain. An intelligent contract is a contract program that is automatically executed according to a specific condition.
Step 406, storing the data to be stored in a database of the target management node.
The auxiliary component may write the data to be stored in the database of the target management node, i.e. store the data to be stored in the database of the target management node.
In an embodiment of the present application, referring to fig. 5, an interface (interface) module 2022 may be included in the auxiliary component of each management node, and the interface module 2022 may provide a service for writing data to be stored into the database for the management component. I.e. the interface module 2022 may be a channel (which may also be referred to as an interface) for writing data between the management component and the database of the management node. Alternatively, the interface module may be a hypertext transfer protocol (Hypertext Transfer Protocol, HTTP) interface module.
For example, referring to fig. 6, after the management component of the target management node obtains the data to be stored, step a may be performed, that is, the data to be stored is sent to the interface module 2022 of the auxiliary component 202. Accordingly, the interface module 2022 may obtain the data to be stored, and may perform step b, i.e. directly write the data to be stored into the database DB of the target management node, even if the data to be stored falls to the ground in the database DB of the target management node 20.
It should be noted that, the database is provided with a task monitor, and the task monitor can monitor whether new data is written in the database (i.e. whether new data exists in the database) in real time. If the task monitor detects that new data is written in the database, prompt information can be sent out to prompt the auxiliary component to synchronize the newly added data to other management nodes. Thus, the consistency of the data written in the database of the target management node and the data written in the databases of other management nodes can be ensured. The newly added data refers to data to be stored written into a database of the management node.
Step 407, transmitting the data to be stored to the auxiliary components of other management nodes of the blockchain except the target management node.
After the auxiliary component of the target management node writes the data to be stored into the database, the data to be stored can be acquired from the database, and the data to be stored can be sent to the auxiliary components of other management nodes except the target management node.
In an embodiment of the present application, referring to fig. 5, the auxiliary component of each management node may further include: a write (writer) module 2023, the writer module 2023 may monitor in real time whether the task monitor of the database of the management node issues a prompt message. If a prompt is sent, the writer module 2023 may determine that there is new data in the database of the target management node (the new data may also be referred to as data to be synchronized at this time), that is, the new data may be read from the database and written into the consensus module 2021 of the auxiliary component. That is, the writer module 2023 may read the data to be stored written into the database and asynchronously write it into the consensus module 2021. The consensus module 2021 may then synchronize the newly added data into auxiliary components of other management nodes based on a consensus algorithm. Correspondingly, other management nodes can acquire the newly added data.
For example, when the writer module 2023 detects that the prompt information exists in the database, as shown in fig. 6, step c may be performed, that is, the newly added data in the database DB is read, and then step d may be performed, that is, the newly added data read is written into the consensus module 2021. The consensus module 2021 may then perform step e, i.e. synchronize the new added data into the auxiliary component 202 of the other management node.
The auxiliary component may implement the data synchronization between the target management node and the other management nodes by performing steps 405 to 407. According to the data synchronization process, the auxiliary component can write the data to be stored in the database into the consensus module after writing the data to be stored into the database of the management node, so that the atomicity of two-step writing operation (namely writing the data to be stored into the database of the management node and writing the data to be stored into the database into the consensus module) is effectively ensured, the data to be stored in the database of the management node is ensured to be written into the consensus module, and then the data to be stored into the databases of other management nodes are synchronized into the databases of other management nodes through the consensus module, and the consistency of the data written into the database of the target management node and the data written into the databases of other management nodes is ensured.
Step 408, obtaining the resource unlocking information sent by the management component.
The resource unlocking information is used for indicating an unlocking target resource.
In this embodiment of the present application, if the management component determines that the management operation based on the target resource is completed, the resource unlocking information may be sent to the auxiliary component, and accordingly, the auxiliary component may acquire the resource unlocking information.
Step 409, sending resource unlocking information to auxiliary components of other management nodes of the blockchain except the target management node.
The auxiliary component may synchronize the resource unlocking information to auxiliary components in other management nodes of the blockchain, except for the target management node, based on a consensus algorithm, to ensure consistency of the resource unlocking information received by each of the other management nodes.
After the auxiliary component of the target management node determines that the management operation based on the target resource is completed, the resource unlocking information can be sent to the auxiliary component, so that the auxiliary components in other management nodes update the recorded corresponding relationship between the identification of the shared resource and the locking mark of the shared resource according to the resource unlocking information, and the other management nodes can acquire the target resource later, namely the unlocking of the target resource is realized.
For example, the auxiliary component may synchronize the resource unlocking information to the consensus module of the other management node through the consensus module thereof, so that the other management node may acquire the resource unlocking information.
It should be noted that, in the embodiment of the present application, a timer may be set in an auxiliary component of each management node, and a resource unlocking period is stored in each auxiliary component. When the auxiliary components of the target management node send the resource locking information to the auxiliary components of other management nodes except the target management node of the blockchain, the timer is started and starts to count, if the auxiliary components do not receive the resource unlocking information sent by the management component in the resource unlocking period, the auxiliary components can generate the resource unlocking information according to the identification of the target resource and send the resource unlocking information to the auxiliary components of the other management nodes, namely, the target resource is forcedly unlocked.
Fig. 7 is a flowchart of yet another blockchain resource management method provided in an embodiment of the present application, where the method may be applied to a blockchain resource management device, where the device may be disposed in an auxiliary component of a target management node, or where the device may be an auxiliary component of the target management node. Referring to fig. 7, the method may include:
step 410, receiving data to be stored sent by auxiliary components of other management nodes except the target management node of the blockchain.
Wherein, the data to be stored refers to: other management nodes manage operation data of the blockchain.
In this embodiment of the present application, the auxiliary component of the other management node may synchronize the data to be stored to the consensus module of the target management node through the consensus module thereof, and correspondingly, the target management node may receive the data to be stored sent by the other management node.
Step 411, the data to be stored is stored in the database of the target management node.
The auxiliary component of the target management node may write the received data to be stored into the database of the target management node, that is, may store the data to be stored into the database of the target management node.
In an embodiment of the present application, referring to fig. 5, the auxiliary component 202 of each management node may further include: a monitor (watch) module 2024. The latch module 2024 may monitor the data change of the consensus module 2021 in real time, that is, monitor whether the data to be stored is received, and write the received data to be stored into the database of the management node in time, so as to achieve synchronization of the data of each management node.
For example, referring to fig. 6, when the latch module 2024 of the target management node detects that the consensus module 2021 receives the data to be stored, step f may be performed, that is, the data to be stored in the consensus module 2021 is read, and then step g may be performed, that is, the read data to be stored is written into the database DB, so that the data written into the database of the target management node is consistent with the data written into the databases of other management nodes.
It should be noted that, in the embodiment of the present application, the identifier of the target management node is stored in the auxiliary component, and the data to be stored received by the auxiliary component carries the identifier of the data receiver. When the auxiliary component receives the data to be stored, whether the data to be stored is relevant to the target management node or not can be judged based on the identification of the data receiver carried by the data to be stored, namely whether the identification identical to the identification of the target management node exists in the identification of the data receiver carried by the data to be stored or not is judged. If the auxiliary component determines that the identifier which is the same as the identifier of the target management node exists in the identifier of the data receiver carried by the data to be stored, the auxiliary component can decrypt the received data to be stored to obtain the control logic of the data to be stored.
It should be further noted that, the sequence of the steps of the blockchain resource management method provided in the embodiments of the present application may be appropriately adjusted, and the steps may also be correspondingly increased or decreased according to the situation. For example, after the target resource is acquired, if the data synchronization operation is not required, the step of performing the data synchronization may not be required, that is, steps 405 to 407 may not be required; in the data synchronization, if the target resource is not required to be locked, the operations of locking and unlocking the resource are not required to be executed, that is, steps 401 to 404, 408 and 409 are not required to be executed. Any method that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered in the scope of protection of the present application, and thus will not be described in detail.
In summary, the embodiments of the present application provide a blockchain resource management method, which may obtain resource locking information of a target management node of a blockchain, where the resource locking information is used to indicate to lock a target resource in the blockchain, and send the resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked. When the target resource is not locked, the blockchain resource management device can send the resource locking information to other management nodes except the target management node of the blockchain, so that the target resource can be ensured not to be occupied by the other management nodes when occupied by the target management node, and the phenomenon that management operation failure is caused because the atomicity of management operation cannot be ensured when a plurality of management nodes perform management operation on the blockchain based on the target resource at the same time is avoided.
It should be noted that, in the embodiment of the present application, the auxiliary component may also be an independent node where the management node establishes a communication connection. The implementation manner of the auxiliary component is not limited, and only the auxiliary component can be ensured to provide the functions of resource locking and data synchronization for the management node.
An embodiment of the present application provides a blockchain resource management device, referring to fig. 8, the device 500 may include:
the first obtaining module 501 is configured to obtain resource locking information of a target management node of a blockchain, where the resource locking information is used to indicate locking a target resource in the blockchain, the blockchain has at least two management nodes, and the target management node is any management node of the at least two management nodes.
A determination module 502 is configured to determine whether the target resource has been locked.
A first sending module 503, configured to send resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked.
In summary, the embodiments of the present application provide a blockchain resource management device, which may obtain resource locking information of a target management node of a blockchain, where the resource locking information is used to indicate to lock a target resource in the blockchain, and send the resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked. When the target resource is not locked, the blockchain resource management device can send the resource locking information to other management nodes except the target management node of the blockchain, so that the target resource can be ensured not to be occupied by the other management nodes when occupied by the target management node, and the phenomenon that management operation failure is caused because the atomicity of management operation cannot be ensured when a plurality of management nodes perform management operation on the blockchain based on the target resource at the same time is avoided.
Optionally, each management node of the blockchain includes a management component and an auxiliary component, and the apparatus may be disposed in the auxiliary component, and the first obtaining module 501 is configured to:
and acquiring the resource locking information sent by the management component in the target management node.
Optionally, the first sending module 502 is configured to:
when the target resource is not locked, resource locking information is sent to auxiliary components in other management nodes of the blockchain than the target management node.
Optionally, the first obtaining module 501 is further configured to:
and acquiring resource unlocking information sent by the management component, wherein the resource unlocking information is used for indicating to unlock the target resource.
The first sending module 502 is further configured to:
and sending resource unlocking information to auxiliary components of other management nodes except the target management node of the blockchain.
Optionally, the auxiliary components in each management node of the blockchain form a sub-blockchain, and the first sending module 501 is configured to:
when the target resource is not locked, the resource lock information is broadcast in the sub-block chain.
Fig. 9 is a schematic structural diagram of another blockchain resource management device according to the embodiment of the present application. Referring to fig. 9, the apparatus 500 further includes:
A second obtaining module 504, configured to obtain the data to be stored sent by the management component.
The storage module 505 is configured to store data to be stored in a database of the target management node.
A second sending module 506, configured to send the data to be stored to auxiliary components of other management nodes of the blockchain except the target management node.
Optionally, the apparatus further comprises:
and the receiving module 507 is used for receiving data to be stored sent by auxiliary components of other management nodes except the target management node of the blockchain.
The storage module 505 is further configured to:
and storing the data to be stored into a database of the target management node.
In summary, the embodiments of the present application provide a blockchain resource management device, which may obtain resource locking information of a target management node of a blockchain, where the resource locking information is used to indicate to lock a target resource in the blockchain, and send the resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked. When the target resource is not locked, the blockchain resource management device can send the resource locking information to other management nodes except the target management node of the blockchain, so that the target resource can be ensured not to be occupied by the other management nodes when occupied by the target management node, and the phenomenon that management operation failure is caused because the atomicity of management operation cannot be ensured when a plurality of management nodes perform management operation on the blockchain based on the target resource at the same time is avoided.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus and each module described above may refer to the corresponding process in the foregoing method embodiment, which is not repeated herein.
Fig. 10 is a schematic structural diagram of another blockchain resource management device according to an embodiment of the present application, and the device 600 may be a server. By way of example, as shown in fig. 10, the apparatus 600 includes a central processing unit (Central Processing Unit, CPU) 601, a system Memory 604 including a random access Memory (Random Access Memor, RAM) 602 and a Read-Only Memory (ROM) 603, and a system bus 605 connecting the system Memory 604 and the central processing unit 601. Apparatus 600 also includes a basic Input/Output (I/O) system 606 that facilitates the transfer of information between various devices within the computer, and a mass storage device 607 for storing an operating system 613, application programs 614, and other program modules 615.
The basic input/output system 606 includes a display 608 for displaying information and an input device 609, such as a mouse, keyboard, etc., for a user to input information. Wherein both the display 608 and the input device 609 are coupled to the central processing unit 601 via an input output controller 610 coupled to the system bus 605. The basic input/output system 606 may also include an input/output controller 610 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, the input/output controller 610 also provides output to a display screen, a printer, or other type of output device.
The mass storage device 607 is connected to the central processing unit 601 through a mass storage controller (not shown) connected to the system bus 605. The mass storage device 607 and its associated computer-readable media provide non-volatile storage for the apparatus 600. That is, the mass storage device 607 may include a computer readable medium (not shown) such as a hard disk or a compact disk-Only (CD-ROM) drive.
Computer readable storage media may include computer storage media and communication media without loss of generality. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes random access Memory (Random Access Memo, RAM), read-Only Memory (ROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), flash Memory or other solid state Memory technology, CD-ROM, digital versatile disks (Digital Video Disc, DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will recognize that computer storage media are not limited to the ones described above. The system memory 604 and mass storage device 607 described above may be collectively referred to as memory.
According to various embodiments of the present application, the apparatus 600 may also operate by a remote computer connected to the network through a network, such as the Internet. I.e., the apparatus 600 may be connected to the network 612 through a network interface unit 611 connected to the system bus 605, or alternatively, the network interface unit 611 may be used to connect to other types of networks or remote computer systems (not shown).
The above memory further includes one or more programs, one or more programs being stored in the memory and configured to be executed by the CPU to implement the methods provided by the embodiments of the present application.
Fig. 11 is a schematic structural diagram of another blockchain resource management device according to an embodiment of the present application. The blockchain resource management device 700 may be: a smart phone, a tablet computer, an MP3 (Moving Picture Experts Group Audio Layer III, dynamic image expert compression standard audio layer 3) player, an MP4 player, a notebook computer or a desktop computer, and the like. The blockchain resource management device 700 may also be referred to by other names of user devices, portable terminals, laptop terminals, desktop terminals, and the like. Alternatively, the blockchain resource management device 700 may be a server.
Generally, the blockchain resource management device 700 includes: a processor 701 and a memory 702.
Processor 701 may include one or more processing cores, such as a 4-core processor, a 12-core processor, and the like. The processor 701 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 701 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ); a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 701 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 701 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.
Memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 702 is used to store at least one instruction for execution by processor 701 to implement the blockchain-based data sharing method provided by embodiments of the present application.
In some embodiments, the blockchain resource management device 700 may further optionally include: a peripheral interface 703 and at least one peripheral. The processor 701, the memory 702, and the peripheral interface 703 may be connected by a bus or signal lines. The individual peripheral devices may be connected to the peripheral device interface 703 via buses, signal lines or a circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 704, touch display 705, camera 706, audio circuitry 707, and power supply 709.
A peripheral interface 703 may be used to connect the I/O related at least one peripheral to the processor 701 and memory 702. In some embodiments, the processor 701, memory 702, and peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.
The Radio Frequency circuit 704 is configured to receive and transmit RF (Radio Frequency) signals, also referred to as electromagnetic signals. The radio frequency circuitry 704 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 704 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 704 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuitry 704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: metropolitan area networks, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or wireless fidelity (Wireless Fidelity, WIFI) networks. In some embodiments, the radio frequency circuitry 704 may also include NFC (Near Field Communication ) related circuitry, which is not limited in this application.
The display screen 705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 705 is a touch display, the display 705 also has the ability to collect touch signals at or above the surface of the display 705. The touch signal may be input to the processor 701 as a control signal for processing. At this time, the display 705 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, the display 705 may be one, disposed on the front panel of the blockchain resource management device 700; in other embodiments, the display 705 may be at least two, each disposed on a different surface of the blockchain resource management device 700 or in a folded design; in still other embodiments, the display 705 may be a flexible display disposed on a curved surface or a folded surface of the blockchain resource management device 700. Even more, the display 705 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The display 705 may be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.
The camera assembly 706 is used to capture images or video. Optionally, the camera assembly 706 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal and the rear camera is disposed on the rear surface of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 706 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.
The audio circuit 707 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and environments, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing, or inputting the electric signals to the radio frequency circuit 704 for voice communication. For purposes of stereo acquisition or noise reduction, a plurality of microphones may be respectively disposed at different portions of the blockchain resource management device 700. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, the audio circuit 707 may also include a headphone jack.
The power supply 709 is used to power the various components in the blockchain resource management device 700. The power supply 709 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 709 includes a rechargeable battery, the rechargeable battery may support wired or wireless charging. Rechargeable batteries may also be used to support fast charge technology.
In some embodiments, the blockchain resource management device 700 also includes one or more sensors 710. The one or more sensors 710 include, but are not limited to: acceleration sensor 711, gyro sensor 712, pressure sensor 713, optical sensor 715, and proximity sensor 716.
The acceleration sensor 711 can detect the magnitudes of accelerations on three coordinate axes of the coordinate system established with the blockchain resource management device 700. For example, the acceleration sensor 711 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 701 may control the touch display screen 705 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal acquired by the acceleration sensor 711. The acceleration sensor 711 may also be used for the acquisition of motion data of a game or a user.
The gyro sensor 712 may detect the body direction and the rotation angle of the blockchain resource management device 700, and the gyro sensor 712 may cooperate with the acceleration sensor 711 to collect the 3D motion of the user on the blockchain resource management device 700. The processor 701 may implement the following functions based on the data collected by the gyro sensor 712: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.
The pressure sensor 713 may be disposed on a side frame of the blockchain resource management device 700 and/or on an underlying layer of the touch display 705. When the pressure sensor 713 is disposed at a side frame of the blockchain resource management device 700, a user's grip signal of the blockchain resource management device 700 may be detected, and the processor 701 performs a left-right hand recognition or a shortcut operation according to the grip signal collected by the pressure sensor 713. When the pressure sensor 713 is disposed at the lower layer of the touch display screen 705, the processor 701 controls the operability control on the UI interface according to the pressure operation of the user on the touch display screen 705. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.
The optical sensor 715 is used to collect the ambient light intensity. In one embodiment, the processor 701 may control the display brightness of the touch display 705 based on the ambient light intensity collected by the optical sensor 715. Specifically, when the intensity of the ambient light is high, the display brightness of the touch display screen 705 is turned up; when the ambient light intensity is low, the display brightness of the touch display screen 705 is turned down. In another embodiment, the processor 701 may also dynamically adjust the shooting parameters of the camera assembly 706 based on the ambient light intensity collected by the optical sensor 715.
The proximity sensor 716, also referred to as a distance sensor, is typically disposed on the front panel of the blockchain resource management device 700. The proximity sensor 716 is used to collect the distance between the user and the front of the blockchain resource management device 700. In one embodiment, when the proximity sensor 716 detects a gradual decrease in the distance between the user and the front face of the blockchain resource management device 700, the processor 701 controls the touch display 705 to switch from the on screen state to the off screen state; when the proximity sensor 716 detects that the distance between the user and the front face of the blockchain resource management device 700 is gradually increasing, the processor 701 controls the touch display 705 to switch from the off-screen state to the on-screen state.
Those skilled in the art will appreciate that the structure shown in fig. 11 is not limiting of the blockchain resource management device 700 and may include more or fewer components than shown, or may combine certain components, or may employ a different arrangement of components.
Also provided in embodiments of the present application is a computer readable storage medium having stored therein at least one instruction, at least one program, code set, or instruction set that is loaded and executed by a processor to implement a blockchain resource management method as shown in any of fig. 2, 4, or 7.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The foregoing description of the exemplary embodiments of the present application is not intended to limit the invention to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, alternatives, and alternatives falling within the spirit and scope of the invention.
Claims (10)
1. A method of blockchain resource management, the method comprising:
acquiring resource locking information of a target management node of a blockchain, wherein the resource locking information is used for indicating to lock target resources in the blockchain, the blockchain is provided with at least two management nodes, and the target management node is any management node in the at least two management nodes;
determining whether the target resource has been locked;
and when the target resource is not locked, sending the resource locking information to other management nodes of the blockchain except the target management node.
2. The method of claim 1, wherein each management node of the blockchain includes a management component and an auxiliary component, the method for the auxiliary component,
the obtaining the resource locking information of the target management node of the blockchain includes:
and acquiring the resource locking information sent by the management component in the target management node.
3. The method of claim 2, wherein the sending the resource lock information to other management nodes of the blockchain than the target management node when the target resource is not locked comprises:
And when the target resource is not locked, sending the resource locking information to auxiliary components in other management nodes of the blockchain except the target management node.
4. The method according to claim 2, wherein the method further comprises:
acquiring resource unlocking information sent by the management component, wherein the resource unlocking information is used for indicating unlocking of the target resource;
and sending the resource unlocking information to auxiliary components of other management nodes except the target management node of the blockchain.
5. The method of claim 2, wherein the auxiliary components in each management node of the blockchain constitute a sub-blockchain,
the sending the resource locking information to other management nodes of the blockchain except the target management node when the target resource is not locked includes:
the resource lock information is broadcast in the sub-blockchain when the target resource is not locked.
6. The method according to claim 2, wherein the method further comprises:
acquiring data to be stored sent by the management component;
storing the data to be stored into a database of the target management node;
And sending the data to be stored to auxiliary components of other management nodes of the blockchain except the target management node.
7. The method according to claim 2, wherein the method further comprises:
receiving data to be stored sent by auxiliary components of other management nodes except the target management node of the blockchain;
and storing the data to be stored into a database of the target management node.
8. A blockchain resource management apparatus comprising means for performing the method of any of claims 1 to 7.
9. A blockchain resource management apparatus, the apparatus comprising a processor and a memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions that are loaded and executed by the processor to implement the method of any of claims 1 to 7.
10. A storage medium having stored therein at least one instruction, at least one program, code set, or instruction set, the at least one instruction, the at least one program, the code set, or instruction set being loaded and executed by a processor to implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910933790.1A CN110597923B (en) | 2019-09-29 | 2019-09-29 | Block chain resource management method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910933790.1A CN110597923B (en) | 2019-09-29 | 2019-09-29 | Block chain resource management method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110597923A CN110597923A (en) | 2019-12-20 |
| CN110597923B true CN110597923B (en) | 2024-02-02 |
Family
ID=68864944
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910933790.1A Active CN110597923B (en) | 2019-09-29 | 2019-09-29 | Block chain resource management method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110597923B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105700939A (en) * | 2016-04-21 | 2016-06-22 | 北京京东尚科信息技术有限公司 | Method and system for multi-thread synchronization in distributed system |
| CN106656600A (en) * | 2016-12-22 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Resource transformation method and device |
| WO2017077616A1 (en) * | 2015-11-05 | 2017-05-11 | 株式会社Ｍｕｒａｋｕｍｏ | Database system, transaction management node, method, and program |
| CN108596768A (en) * | 2018-05-09 | 2018-09-28 | 神州数码融信软件有限公司 | A kind of distributed transaction processing method, apparatus and system |
| CN108647285A (en) * | 2018-05-04 | 2018-10-12 | 北京小米移动软件有限公司 | Renaming method, apparatus and distributed file system in distributed file system |
| CN108829709A (en) * | 2018-05-03 | 2018-11-16 | 广州金山安全管理系统技术有限公司 | Distributed database management method, apparatus, storage medium and processor |
| CN110231979A (en) * | 2019-05-07 | 2019-09-13 | 深圳壹账通智能科技有限公司 | Transaction methods, device, equipment and storage medium based on block chain |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10318487B2 (en) * | 2014-08-20 | 2019-06-11 | International Business Machines Corporation | Sharing resources among remote repositories utilizing a lock file in a shared file system or a node graph in a peer-to-peer system |
-
2019
- 2019-09-29 CN CN201910933790.1A patent/CN110597923B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017077616A1 (en) * | 2015-11-05 | 2017-05-11 | 株式会社Ｍｕｒａｋｕｍｏ | Database system, transaction management node, method, and program |
| CN105700939A (en) * | 2016-04-21 | 2016-06-22 | 北京京东尚科信息技术有限公司 | Method and system for multi-thread synchronization in distributed system |
| CN106656600A (en) * | 2016-12-22 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Resource transformation method and device |
| CN108829709A (en) * | 2018-05-03 | 2018-11-16 | 广州金山安全管理系统技术有限公司 | Distributed database management method, apparatus, storage medium and processor |
| CN108647285A (en) * | 2018-05-04 | 2018-10-12 | 北京小米移动软件有限公司 | Renaming method, apparatus and distributed file system in distributed file system |
| CN108596768A (en) * | 2018-05-09 | 2018-09-28 | 神州数码融信软件有限公司 | A kind of distributed transaction processing method, apparatus and system |
| CN110231979A (en) * | 2019-05-07 | 2019-09-13 | 深圳壹账通智能科技有限公司 | Transaction methods, device, equipment and storage medium based on block chain |
Non-Patent Citations (2)
| Title |
|---|
| 云计算环境下的资源管理研究;邹永贵;万建斌;;数字通信(第04期);全文 * |
| 指纹识别门禁系统在智能小区的研究;李玉丽;;黑龙江科技信息(第34期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110597923A (en) | 2019-12-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108805560B (en) | Numerical value integration method and device, electronic equipment and computer readable storage medium | |
| CN111190748B (en) | Data sharing method, device, equipment and storage medium | |
| CN113204298B (en) | Method and device for displaying release progress, electronic equipment and storage medium | |
| CN110147380B (en) | Data updating method, device, server and storage medium | |
| CN109922356B (en) | Video recommendation method and device and computer-readable storage medium | |
| CN113076051A (en) | Slave control terminal synchronization method, device, terminal and storage medium | |
| CN110677262B (en) | Information notarization method, device and system based on blockchain | |
| CN111510482A (en) | Method and device for determining failed network request and computer storage medium | |
| CN109697113B (en) | Method, device and equipment for requesting retry and readable storage medium | |
| CN111126958A (en) | Schedule creating method, schedule creating device, schedule creating equipment and storage medium | |
| CN110544193A (en) | Donation information distributed storage method and device | |
| CN110597868B (en) | Information query method, device, terminal and storage medium based on block chain | |
| CN110597840B (en) | Partner relationship establishment method, device, equipment and storage medium based on blockchain | |
| CN117215990A (en) | Inter-core communication method and device of multi-core chip and multi-core chip | |
| CN111428080B (en) | Video file storage method, video file search method and video file storage device | |
| CN110597923B (en) | Block chain resource management method, device and storage medium | |
| CN113408989B (en) | Automobile data comparison method and device and computer storage medium | |
| CN114594885A (en) | Application icon management method, device and equipment and computer readable storage medium | |
| CN111918084B (en) | Wheat loading method and device, server and terminal | |
| CN110324791B (en) | Networking method and device, computer equipment and storage medium | |
| CN111190751B (en) | Task processing method and device based on song list, computer equipment and storage medium | |
| CN108519913B (en) | Application program running state management method and device, storage medium and terminal | |
| CN114698409A (en) | Video conference realization method, device, system and storage medium | |
| CN113225573B (en) | Live broadcast connection method, device, terminal, server, medium and product | |
| CN114816187B (en) | Control display method, device, computer 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 |