WO2019184775A1 - Procédé et dispositif de stockage de données de gestion et support d'informations - Google Patents

Procédé et dispositif de stockage de données de gestion et support d'informations Download PDF

Info

Publication number
WO2019184775A1
WO2019184775A1 PCT/CN2019/078825 CN2019078825W WO2019184775A1 WO 2019184775 A1 WO2019184775 A1 WO 2019184775A1 CN 2019078825 W CN2019078825 W CN 2019078825W WO 2019184775 A1 WO2019184775 A1 WO 2019184775A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
management data
area unit
data
block
Prior art date
Application number
PCT/CN2019/078825
Other languages
English (en)
Chinese (zh)
Inventor
胡艺馨
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019184775A1 publication Critical patent/WO2019184775A1/fr

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
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1042—Peer-to-peer [P2P] networks using topology management mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • 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/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • 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/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
    • 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
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/82—Solving problems relating to consistency
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Definitions

  • the present application relates to the field of information processing technologies, and in particular, to a storage method, device, and storage medium for managing data.
  • a distributed cloud data center usually includes a plurality of regional units distributed in a plurality of regions, each regional unit corresponding to one region, and each regional unit is used to manage data in the local domain.
  • each area unit shares a set of management data including information necessary for the operation of the area unit, such as identity authentication data and system configuration parameters. Since each regional unit shares a set of management data, how to store management data to achieve global sharing of the management data becomes more and more important.
  • a global region is set in a certain regional unit of the plurality of regional units, and management data is stored in the global region at initialization, and the like.
  • the area unit can acquire the management data by accessing the area unit to implement global sharing of management data. Then, when the management data needs to be updated, the management data stored in the global area is updated, and other area units can also obtain the updated management data by accessing the area unit.
  • the present application provides a storage method, device, and storage medium for managing data.
  • the technical solution is as follows:
  • a storage method for managing data is provided, which is applied to a distributed cloud data center, where the distributed cloud data center includes a plurality of regional units, and the method includes:
  • the first management database node acquires the updated management data, and stores the updated management data in a management data link of the first area unit, where the first management database node has the first area unit of the plurality of area units Management database node;
  • the first management database node instructs the second management database node to store the updated management data in a management data link of the second area unit, where the second area unit is other than the first area unit Any of the area units, the second area unit having the second management database node, and the management data links of the different area units of the plurality of area units are used for mutual disaster recovery backup.
  • the distributed cloud data center includes a plurality of area units, and when the first management database node in the first area unit acquires the updated management data, after the update is stored in the management data link of the first area unit Management data, and instructing the second management database node to store the updated management data in the management data link of the second area unit. Therefore, in the present application, when the first management database node stores the updated management data, the management database node of the other regional unit will also store the updated management data to implement the management database node of each regional unit. Management data is stored and the stored management data is consistent.
  • management data is stored in each area unit, so that each of the area units can acquire management data from its own management data chain, which improves the efficiency of the area unit to obtain management data.
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • the management data chain of each area unit includes a plurality of first blocks, each of the plurality of first blocks includes one management data, and the management data chain of each area unit is a tree structure, the plurality of first blocks are respectively nodes in the first tree structure;
  • the first management database node stores the updated management data in the management data link of the first area unit, including:
  • the first management database node generates a new first block, and the new first block includes the updated management data
  • the first management database node adds the new first block as the last first block in the first trust path
  • the first management database node instructs the second management database node to store the updated management data in the management data link of the second area unit, including:
  • the first management database node instructs the second management database node to add the new first block as the last first block in the second trust path.
  • the management data chain in each area unit is a tree structure composed of a plurality of blocks, each node in the tree structure is a block, and each block includes a management. Data so that subsequent management data can be obtained from the block.
  • the first trust path has the most node in the management data link of the first area unit
  • the second trust path has the most management data chain of the second area unit where the second management database node is located. node.
  • the trust path in the management data chain of the regional unit is the path with the most nodes in the management data chain. That is, each regional unit determines the path having the most nodes in its management data chain as the trust path.
  • each area unit further includes a change audit data chain, and the change audit data chain of each area unit includes a plurality of second blocks, and the plurality of second blocks are interconnected to form a first branch having at least one branch a two-tree structure, wherein the plurality of second blocks are nodes in the second tree structure;
  • the first management database node adds the new first block as the last first block in the first trust path, including:
  • the trust path in the management data chain needs to be redefined.
  • each of the above regional units will have its own management data link.
  • the method in which the path with the most nodes is determined to be the trusted path is not applicable to the scenario. Therefore, in the present application, a change audit data chain can be provided for each area unit, and the block in the change audit data chain is used to indicate the trust path in the management data link.
  • the method further includes:
  • the first management database node receives the management data read request, determines the first trust path according to the third trust path, and reads the updated management data in the last first block in the first trust path.
  • the management database node of each area unit further includes a change audit data link
  • the third trust path in the audit data chain is first determined to determine the number in the management data chain.
  • each first block has a timestamp, and a timestamp of each first block is used to indicate a time corresponding to the management data thereon;
  • the method also includes:
  • the first management database node generates a new second block according to the first block found, and adds the new second block as the last second block in the third trust path, the new The second block is configured to reset the first trust path according to the first block that is found.
  • each regional unit further includes a change audit data link
  • the block in the change audit data chain is used to indicate the trust path in the management data link, when the management data needs to be restored to the historical designated time When managing data, simply add a new second block to the change audit data chain.
  • a storage device for managing data which is applied to a first management database node in a distributed cloud data center, where the distributed cloud data center includes a plurality of regional units, where the first management database node is The management database node of the first area unit among the area units has a function of realizing the storage method behavior of the management data in the first aspect described above.
  • the storage device for managing data includes at least one module for implementing the storage method of the management data provided by the above first aspect.
  • a third aspect provides a storage device for managing data, where the storage device includes a processor and a memory for storing a storage device supporting the management data to execute the management data provided by the first aspect.
  • the processor is configured to execute a program stored in the memory.
  • the operating device of the storage device can also include a communication bus for establishing a connection between the processor and the memory.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method of storing management data described in the first aspect above.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of storing management data as described in the first aspect above.
  • the distributed cloud data center includes a plurality of area units, and when the first management database node in the first area unit acquires the updated management data, after the update is stored in the management data link of the first area unit Management data, and instructing the second management database node to store the updated management data in the management data link of the second area unit. Therefore, in the present application, when the first management database node stores the updated management data, the management database node of the other regional unit will also store the updated management data to implement the management database node of each regional unit. Management data is stored and the stored management data is consistent.
  • management data is stored in each area unit, so that each of the area units can acquire management data from its own management data chain, which improves the efficiency of the area unit to obtain management data.
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • 1A is a schematic structural diagram of a blockchain according to an embodiment of the present application.
  • FIG. 1B is a schematic diagram of a P2P network provided by an embodiment of the present application.
  • 2A is a schematic diagram of a distributed cloud data center provided by an embodiment of the present application.
  • 2B is a schematic diagram of another distributed cloud data center provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a method for storing management data provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of another storage method for managing data according to an embodiment of the present application.
  • FIG. 6 is a flowchart of another storage method for managing data according to an embodiment of the present application.
  • FIG. 7 is a flowchart of another storage method for managing data according to an embodiment of the present application.
  • FIG. 8 is a block diagram of a storage device for managing data according to an embodiment of the present application.
  • the present invention provides a distributed management database for a distributed cloud data center.
  • the distributed management database includes a plurality of management database nodes for storing management data of the distributed cloud data center.
  • Each regional unit of the distributed cloud data center has a management database node for storing the management data of the distributed cloud data center to the management data link corresponding to the management database node.
  • Each management data node corresponds to one management data link, and the management data stored in each management data link is disaster recovery.
  • the first management database node obtains the updated management data and stores it in the corresponding management data link, and then instructs the management database nodes of the remaining area units to store the updated management data, and each management data.
  • the updated management data of the chain storage is used for mutual disaster recovery backup.
  • each management database node contains a management data chain.
  • the management data chain is implemented by blockchain technology.
  • a blockchain is a distributed database formed by a peer-to-peer (P2P) network.
  • the network includes multiple nodes. Any two nodes are connected to each other. Each node maintains a growing number of nodes. And a chain of blocks arranged in order. Each block contains a timestamp and is connected to a block before it.
  • the blockchain itself has the property of preventing data from being modified, that is, once the data is recorded in the block, it cannot be returned for modification.
  • P2P networks and distributed timestamp servers a blockchain database can be managed automatically.
  • a blockchain is like an open, distributed general ledger that records transaction information efficiently, securely, and permanently.
  • a blockchain includes a plurality of blocks, and the plurality of blocks form a tree structure having at least one branch, each of which forms a tree structure.
  • the blocks are each a node in the tree structure.
  • the trust path of the blockchain (the path formed by the block identified by the grid box) has the largest number of nodes, starting from the first block (the block identified by the white box) and always connecting to the latest block, the others exist in The path formed by the block outside the trust path (the block identified by the diagonal stripe box) is an invalid path.
  • a block is a data structure that records transactions, consisting of a block body and a block header.
  • the block body is responsible for recording all transaction information for a period of time.
  • the block header includes: version number, parent block hash value, Merkle root, time stamp, difficulty value, random number.
  • the Merkle root is a value calculated by the hash value of all the transactions in the block body, which is used to check whether a transaction exists in the block.
  • the timestamp is used to record the generation time of the block.
  • the difficulty value indicates the difficulty target of the block workload proof.
  • the parent block hash value is used to implement the connection between the blocks, and the random number is used to implement the mining mechanism.
  • FIG. 1B is a schematic diagram of a P2P network provided by an embodiment of the present application, where multiple nodes are included in the network. If the current resource transfer between node A and node B, at this point, each node in the network can be accounted for by the following steps, that is, each node writes the transaction to itself. In the blockchain.
  • Node A uses the private key to sign a digital signature on the last transaction information of the resource to be transferred and the public key of Node B, and attach the signature to the end of the resource to be transferred to obtain a transaction order.
  • Node A broadcasts the transaction slip in the network.
  • Each node in the network acquires the right to generate a block according to the transaction order through the mining mechanism, that is, each node verifies the validity of the transaction ticket when the transaction order is detected, and the verification is effective. After that, start solving math problems.
  • the process of solving the problem is: finding a value such that the hash value of the previous block and the hash value calculated by the specified algorithm of the currently received transaction order satisfy the preset condition.
  • the block is generated according to the solution and the transaction order, and the generated block is broadcasted in the network.
  • FIG. 1B only six nodes are taken as an example, and FIG. 1B does not constitute a limitation on the number of nodes included in the P2P network provided by the embodiment of the present application.
  • FIG. 2A is a schematic diagram of a distributed cloud data center storing management data according to an embodiment of the present invention.
  • the distributed cloud data center includes multiple area units, and each area unit includes a management system and a service.
  • System and management database nodes, the management database nodes of each regional unit include management data links, and the management data chain is implemented by blockchain technology.
  • the service system and the management system of the distributed cloud data platform generate management data according to the needs of the service or read the management data through the management database node, and are used for services or functions such as virtual machine reconstruction and disaster recovery.
  • FIG. 2A only two area units are taken as an example, and FIG. 2A does not constitute a limitation on the number of area units in the distributed cloud data center provided by the embodiment of the present invention.
  • the management database node may further include a database access layer for providing an access interface to the management system or the business system access management database node. That is, the management system of each area unit is connected to its own management database node through the database access layer to realize the writing and reading of management data through the interaction of the management system and the management database node. That is, the database access layer of each area unit is used to provide access to the management database node, and the internal details of the management database node are shielded to realize that the data in the access management database node is transparent to the business system.
  • the management system of each regional unit is respectively connected with its own database access layer and business system, and the database access layer of each regional unit is connected with its own management data link, and the management data links of each regional unit are Connected through the first P2P network.
  • each regional unit provides an operation and operation operation portal for the user to perform operation and maintenance management, such as resource application, issuance, metering and accounting, resource statistics, alarm monitoring, system security deployment, and maintenance upgrade.
  • operation and maintenance management such as resource application, issuance, metering and accounting, resource statistics, alarm monitoring, system security deployment, and maintenance upgrade.
  • the management system may need to obtain management data, and the management system will access the database through the database. Obtain management data from the management data chain.
  • each regional unit is connected with its own business system for resource scheduling, metering and monitoring, and providing support for business activities.
  • the business system may also need to acquire management data, and the business system will send a data acquisition request to the management system to enable The management system obtains management data from the management data link through the database access layer, and returns the acquired management data to the business system.
  • the management data chain of each area unit includes a plurality of first blocks, and the plurality of first blocks are connected to each other to form a first tree structure having at least one branch, and the plurality of first blocks are respectively
  • the nodes in the first shape structure, each of the first blocks is used to store management data updated at the corresponding time stamp. That is, the management database node of each area unit is used to store management data, and the management data is stored by managing the management data chain in the database node.
  • the management database node of each area unit further includes a database cache, and the database access layer of each area unit is also respectively connected to its own database cache.
  • the database cache is used to cache the latest management data.
  • each regional unit in the distributed cloud data center further includes a disaster recovery management system, and the disaster recovery management system of each regional unit is respectively connected to its own management system and service system, and each The disaster recovery management systems of the regional units are connected through a network.
  • the disaster recovery management system of each regional unit is responsible for disaster recovery management of its own business system. Therefore, the functions of the disaster recovery management system mainly include:
  • the disaster recovery management system needs to interact with the management system to obtain management information, mainly information of the service virtual machine, such as specifications, mirroring, volume information, and information about the tenant organization ownership;
  • the service disaster recovery management system also needs to interact with the peer service disaster recovery management system to cooperate.
  • the function of the disaster recovery management system provided by the embodiment of the present application is specifically described by taking the disaster recovery switchover and the disaster recovery switchback as an example.
  • the disaster recovery handover request is used to instruct the first area unit to process the service of the third regional unit that fails.
  • the first area unit is any area unit in the cloud data center.
  • the disaster recovery management system of the first area unit receives the disaster recovery switching request
  • the disaster recovery switching request is forwarded to the management system of the first area unit
  • the management system of the first area unit is managed from the first area unit.
  • the management data of the first regional unit is processed by the management system of the first regional unit to reconstruct the service virtual machine for processing the service of the third regional unit.
  • the disaster recovery switching request is triggered by the administrator through a preset operation, that is, after the third regional unit fails, the management personnel can implement disaster recovery switching through the disaster recovery management system of the first regional unit to implement The traffic of the third regional unit is processed by the first regional unit.
  • the management system of the first area unit processes the acquired management data to rebuild the service virtual machine.
  • the management system of the first area unit sends the acquired management data to the disaster recovery management system of the first area unit.
  • the disaster management system of the first area unit processes the received management data, and sends the processed management data to the service system of the first area unit, where the service system of the first area unit is based on the first area unit
  • the disaster recovery management system processes the management data to reconstruct the business virtual machine.
  • the service system of the first area unit After the disaster recovery management system of the first area unit receives the disaster recovery switching request, the service system of the first area unit finally performs the reconstruction of the service virtual machine according to the received management data to process the third area unit. Business.
  • the disaster recovery switchback request is sent to the management system of the first regional unit, and the disaster recovery switchback request is used for Instructing the first area unit to reprocess the service
  • the management system of the first area unit acquires management data from the management database node of the first area unit, and the management system of the first area unit processes the acquired management data to reconstruct the service virtual machine For processing the services of the first area unit.
  • the disaster recovery switchback request is triggered by the administrator through a preset operation, that is, after the failure of the first regional unit, the management personnel can implement the disaster recovery and backoff through the disaster recovery management system of the first regional unit. So that the first area unit can resume processing the service.
  • the management system of the first area unit processes the acquired management data to rebuild the service virtual machine, which has been described in detail in the process of disaster recovery switching, and will not be further described herein.
  • the implementation of the management system of the first area unit to obtain the management data from the management database node of the first area unit has also been described in detail in the above-mentioned disaster recovery switching, and will not be explained here.
  • the nodes in the network have the tree structure of the blockchain after confirming the effective block.
  • the path of the most node is used as the trust path, and the valid block is added at the end of the trust path.
  • the trust path containing the most nodes in the blockchain can also be called the longest chain in the blockchain, which is not limited by the present invention. Therefore, in the distributed cloud data center shown in FIG. 2A above, management data is acquired from the end block of the trust path of the management data link each time the management data needs to be acquired from the management data link. That is, in the distributed cloud data center shown in FIG. 2A, the management data link determines the path containing the most nodes as the trust path by default, that is, the longest chain is determined as the trust chain.
  • the regional unit may need to restore the management data to the management data at a certain historical moment at a certain time, that is, the regional unit needs to modify its own management data chain according to the actual situation. Therefore, in the embodiment of the present application, the blockchain of the related art is modified so that it can no longer trust only the path containing the most nodes, but can flexibly specify the path of the trust to meet the distributed cloud data center. Demand. At this time, since the management data link no longer only trusts the path containing the most nodes, when the management data link needs to acquire management data, it needs to inform which data path of the management data chain is the trust path. Specifically, in the embodiment of the present application, the trust path in the management data chain is indicated by setting a change audit data chain in the management database node.
  • FIG. 2B is a schematic diagram of another distributed cloud data center storing management data according to an embodiment of the present application.
  • the distributed cloud data center includes multiple area units, and each area unit includes a management system.
  • the business system and management database nodes, and the management database nodes of each regional unit include a management data link and a change audit data link.
  • FIG. 2B only two area units are taken as an example, and FIG. 2B does not constitute a limitation on the number of area units in the distributed cloud data center provided by the embodiment of the present application.
  • the management database node of the distributed cloud data center shown in FIG. 2B also includes a database access layer.
  • the function of the database access layer is the same as that of the database access layer in the distributed cloud data center shown in FIG. 2A, and will not be elaborated in detail.
  • the management system of each regional unit is connected with its own database access layer and business system, and the database access layer of each regional unit is connected with its own management data link and change audit data link, and the management data link of each regional unit.
  • the first P2P network is connected to each other, and the change audit data links of the respective area units are connected through the second P2P network.
  • the change audit data chain of each area unit includes a plurality of second blocks, and the plurality of second blocks are interconnected to form a second tree structure having at least one branch, and the plurality of second blocks are respectively Is the node in the second tree structure.
  • Each of the first block and each of the second blocks has a corresponding timestamp, and each of the second blocks is used to indicate that the end block of the trust path in the data chain is managed at the corresponding timestamp.
  • management system, the business system, and the management data link in the distributed cloud data center shown in FIG. 2B have the same functions as the management system, the business system, and the management data link in the distributed cloud data center shown in FIG. 2A. This is not elaborated.
  • the distributed cloud data center may further include a database cache and a disaster recovery management system, and the connection relationship between the database cache and the disaster recovery management system in the distributed cloud data center shown in FIG. 2B
  • the functions and functions are the same as those of the database cache and disaster recovery management system in the distributed cloud data center shown in FIG. 2A, and will not be elaborated here.
  • the infrastructure and software system of the distributed cloud data center are usually divided into administrative domains.
  • business domain The service domain is composed of computing, network, and storage resources in a pooled manner by the service system of each regional unit, and provides service services for end users, such as cloud host services, physical machine services, storage services, and network services.
  • the management domain is composed of the management system and management data of each regional unit, and supports the normal development of cloud data center operations and operation and maintenance activities, including service opening and metering, identity authentication of users' use resources, and security guarantees.
  • the first block and the second block are the names used in the embodiments of the present application according to the functions of the related modules. In actual applications, other names may be used according to the functions of the related modules, and the embodiments of the present application are not specifically limited herein.
  • FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application.
  • the area unit in FIG. 2A or FIG. 2B can be implemented by the computer device shown in FIG.
  • the computer device includes at least one processor 301, a communication bus 302, a memory 303, and at least one communication interface 304.
  • the processor 301 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated systems for controlling the execution of the program of the present application. Circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 302 can include a path for communicating information between the components described above.
  • the memory 303 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed, but is not limited to this.
  • Memory 303 may be present independently and coupled to processor 301 via communication bus 302. The memory 303 can also be integrated with the processor 301.
  • the communication interface 304 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • processor 301 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG.
  • a computer device can include multiple processors, such as processor 301 and processor 305 shown in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the computer device may further include an output device 306 and an input device 307.
  • Output device 306 is in communication with processor 301 and can display information in a variety of ways.
  • the output device 306 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
  • Input device 307 is in communication with processor 301 and can receive user input in a variety of ways.
  • input device 307 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device described above may be a general purpose computer device or a special purpose computer device.
  • the computer device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device.
  • PDA personal digital assistant
  • the embodiments of the present application do not limit the type of computer equipment.
  • the memory 303 is used to store program code for executing the solution of the present application, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute the program code 308 stored in the memory 303.
  • One or more software modules may be included in program code 308.
  • the area unit shown in FIG. 2A or 2B can determine data for developing an application by the processor 301 and one or more of the program codes 308 in the memory 303.
  • FIG. 4 is a flowchart of a method for storing management data according to an embodiment of the present application. The method is applied to the distributed cloud data center of FIG. 2A. As shown in FIG. 4, the method includes the following steps:
  • Step 401 The first management database node acquires the updated management data, and stores the updated management data in the management data link of the first area unit, where the first management database node is the first area unit of the plurality of area units. Have a management database node.
  • the first area unit is any one of the plurality of area units, and the management data link in the area unit is used to store management data, so when the first management database node of the first area unit receives the management data,
  • the updated management data can be stored in its own management data chain.
  • each of the plurality of first blocks includes one management data
  • the management data chain of each area unit is a tree structure
  • the plurality of first blocks are respectively nodes in the first tree structure, and therefore, the first management database node can store the updated management data in the management data link of the first area unit.
  • the first management database node generates a new first block, the new first block includes the updated management data, and the first management database node adds the new first block as the first trust path.
  • the last first block, the first trust path having the most nodes in the management data chain of the first area unit.
  • the default trust path in the management data link is the path containing the most nodes in the distributed cloud data center shown in FIG. 2A
  • the generated first block may be added to the end of the path with the most nodes in its own management data chain.
  • the first management database node of the first area unit obtains the updated management data by: when the management data link of the first area unit acquires the transaction order carrying the management data through the mining mechanism, the transaction order is carried
  • the management data is determined as the updated management data
  • the transaction data is generated by the management data link of the second area unit according to the updated management data and broadcasted in the first P2P network, and the second area unit is the first area unit. Any area unit other than .
  • the transaction ticket broadcasted by the management data link of the second area unit is a transaction ticket after being signed by the private key. Therefore, when the first unit area unit receives the transaction order, the public key verification signature is also required. Validity to determine the validity of the transaction, and after determining that the transaction is valid, perform the step of generating a first block based on the transaction.
  • the management data chain of the second regional unit when the management database node of each regional unit further includes a database cache, the management data chain of the second regional unit generates a transaction order according to the updated management data:
  • the management system of the second area unit receives multiple configuration requests triggered by the user through a preset operation, and the management system of the second area unit acquires for any one configuration request.
  • the configuration information carried by the configuration request is sent to the service system of the second area unit, and the service system of the second area unit performs the relevant configuration according to the configuration information, and when the implementation is completed, the second area unit is implemented.
  • the management system responds to the configuration result, and the management system of the second area unit writes the configuration information corresponding to the configuration result to the database cache through the database access layer of the second area unit according to the configuration result.
  • the management system of the second area unit When the management system of the second area unit receives the configuration result for all configuration requests, displaying the received configuration result, when receiving the acceptance pass information for the configuration result triggered by the preset operation, determining that the configuration is completed, and Obtaining all configuration information cached in the database cache of the second area unit by the database access layer of the second area unit, and packaging all the acquired configuration information to obtain the management data after the update, and then according to the management data after the update Generate a transaction order and sign the transaction with a private key.
  • the first block in the management data chain is divided according to the granularity of the delivery behavior, and the delivery behavior includes any behavior of updating the management data, for example, the expansion and management of the management data. Data upgrades or modifications to management data.
  • the preset operation may be a click operation, a selection operation, or a voice operation.
  • the management database node of each area unit further includes a database cache
  • the management database node of the first area unit adds the generated first block to the end of the trust path of the management data link of the own area
  • the obtained management data is cached in the database cache.
  • the management data link of the first area unit sends the acquired management data to the database access layer of the first area unit, and the database access layer of the first area unit writes the management data to the database cache of the first area unit.
  • the first first block in the management data chain of the first area unit is obtained according to the factory configuration data set by the publisher of the distributed cloud data center. That is, in the initialization state, the management data chain of the first area unit generates the first first block based on the management data at the time of initialization.
  • the management data at the time of initialization is the factory configuration data set by the publisher of the distributed cloud data center.
  • Step 402 The first management database node instructs the second management database node to store the updated management data in a management data link of the second area unit, where the second area unit is other than the first area unit among the plurality of area units. Any of the area units, the second area unit has a second management database node, and the management data links of the different area units of the plurality of area units are used for mutual disaster recovery backup.
  • the first management database node instructs the second management database node to store the updated management data in the management data link of the second area unit, that is, the first management database node instructs the second management database node to The first block is added as the last first block in the second trust path.
  • the first management database node implements step 402 by broadcasting: the first management database node of the first area unit broadcasts the generated new first block in the first P2P network, so that the first area unit is The management database node of each of the area units adds the generated new first block to the end of the path of the management node of the management node having the most nodes, wherein the first P2P network is connected to the plurality of area units A network of management data links for each regional unit.
  • each area unit of the distributed cloud data center shares a set of management data, it is necessary to ensure the consistency of data stored in the management data link in each area unit. Therefore, after the management database node of the first area unit generates the new first block, the generated new first block needs to be transmitted in the first P2P network, so that other area units will generate the new one.
  • the first block joins the end of the path with the most nodes of its own management data chain to achieve the purpose of updating the management data chain of other area units.
  • the distributed cloud data center includes a plurality of area units.
  • the management data link in the first area unit stores the The updated management data, and instructing the second management database node to store the updated management data in the management data link of the second area unit. Therefore, in the present application, when the first management database node stores the updated management data, the management database node of the other regional unit will also store the updated management data to implement the management database node of each regional unit. Management data is stored and the stored management data is consistent.
  • management data is stored in each area unit, so that each of the area units can acquire management data from its own management data chain, which improves the efficiency of the area unit to obtain management data.
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • FIG. 5 is a flowchart of another method for storing management data provided in an embodiment of the present application, which is applied to the distributed cloud data center shown in FIG. 2A, and the storage data storage method shown in FIG. 5 is used in FIG.
  • the storage method of the management data shown is further explained. Specifically, as shown in FIG. 5, the method includes the following steps:
  • Step 501 The first management database node acquires the updated management data, and stores the updated management data in the management data link of the first area unit, where the first management database node is the first area unit of the plurality of area units. Have a management database node.
  • the implementation of the step 501 is basically the same as the implementation of the step 401 in the embodiment shown in FIG. 4, and will not be described in detail again.
  • Step 502 The first management database node instructs the second management database node to store the updated management data in the management data link of the second area unit, where the second area unit is other than the first area unit of the plurality of area units. Any of the area units, the second area unit has a second management database node, and the management data links of the different area units of the plurality of area units are used for mutual disaster recovery backup.
  • step 502 is basically the same as the implementation of step 402 in the embodiment shown in FIG. 4, and will not be elaborated in the same time.
  • the above steps 501 to 502 are used to explain the process of generating the management data chain of a certain area unit of the distributed cloud data center shown in FIG. 2A.
  • the following step 503 is used to explain how to read management data from the management data link of a regional unit of the distributed cloud data center.
  • Step 503 The first management database node of the first area unit receives the management data read request, and reads the management data in the block at the end of the trust path of the management data link of the own.
  • Step 503 can be implemented by the following steps 5031 to 5033:
  • Step 5031 When the service system of the first area unit receives the management data read request, forward the management data read request to the management system of the first area unit.
  • the management data read request is triggered by the user.
  • the distributed cloud data center shown in FIG. 2A or FIG. 2B knows that the service system of each regional unit is not connected to the management database node, but is each The management system of the area unit is connected to the management database node. Therefore, when the service system of the first area unit receives the management data read request, the management data read request needs to be forwarded to the management system of the first area unit.
  • Step 5032 The management system of the first area unit acquires management data from the first management database node of the first area unit.
  • step 5032 is: when the management system of the first area unit receives the management data read request, the management system of the first area unit sends a management data request message to the database access layer of the first area unit, The database access layer of the first area unit receives the management data request message, and determines the management data according to the management data link of the first area unit, and the database access layer of the first area unit transmits the determined management data to the management system of the first area unit.
  • the management database node of each area unit when the management database node of each area unit further includes a database cache, the management database node of the first area unit reads the management data in the generated first block of the end of the trust path of the management data link of the first area unit.
  • the management database node of the first area unit determines whether the management data is stored in its own database cache, and if so, the first management database node of the first area unit obtains the management data from its own database cache, and if not, the first The first management database node of a zone unit performs the step of reading the management data in the first block generated at the end of the path of the management node of the own management data chain.
  • the database access layer of the first area unit may first determine whether the management data is stored in the database cache of the first area unit, and if so, from the first area.
  • the management data is obtained in the database cache of the unit; if not, the step of determining the management data according to the management data link of the first area unit and the change audit data chain is performed.
  • the management system of the first area unit acquires management data through the database access layer of the first area unit, and the database access layer of the first area unit determines the database cache before acquiring the management data from the management data link. Whether the management data is stored to improve the efficiency of obtaining the management data. If the database access layer of the first area unit does not obtain the management data from the database cache of the first area unit, the management data is obtained from the management data link.
  • the implementation manner of determining the management data by the database access layer of the first area unit according to the management data link of the first area unit may be: the database access layer of the first area unit forwards the management data to the management data link of the first area unit. Requesting, when the management data link of the first area unit receives the management data read request, the management data link of the first area unit searches for the first block of the end of the path with the most nodes, and the first block from the search The management data is acquired in the block, and the management data link of the first area unit sends the acquired management data to the database access layer of the first area unit.
  • Step 5033 The management system of the first area unit sends the acquired management data to the service system of the first area unit.
  • the management system of the first area unit When the management system of the first area unit receives the management data sent by the database access layer of the first area unit, the management system of the first area unit sends the received management data to the service system of the first area unit to complete the reading. The process of managing data.
  • step 503 is used to explain how to read the management data from the cloud distributed data center shown in FIG. 2A.
  • the regional unit may be caused.
  • the following step 504 is used to explain how to recover the management data link of the area unit.
  • Step 504 After the first regional unit fails to cause a problem in its management data link, the first management database node of the first regional unit receives the data recovery request, and rejoins its management data link to the first P2P network, and The block information is reloaded in the first P2P network, and a data recovery confirmation message is returned.
  • step 504 can be implemented by the following steps:
  • the data recovery request is sent to the database access layer of the first area unit, and the data recovery request is used to indicate the reloading
  • the data link is managed, and the database access layer of the first area unit receives the data recovery request and sends a network join request to the management data link of the first area unit.
  • the data recovery request is triggered by the administrator by a preset operation, that is, after the first area unit fails, when the manager needs to restore the first area unit, the data recovery request may be triggered by a preset operation.
  • the management data link of the first area unit may not be in the first P2P network when the first area unit fails, the management data link of the first area unit is first added to the first area through the network join request.
  • the P2P network to recover the block data in the management data link of the first area unit.
  • the management data link of the first area unit receives the network join request, rejoins the first P2P network, and reloads the block information from the first P2P network, and after obtaining each of its own blocks, the first area unit
  • the database access layer sends a first network join confirmation message.
  • the management data link of the first area unit receives the network join request, and the method of rejoining the first P2P network is: the management data link of the first area unit broadcasts a network join request in the first P2P network, and the network join request Carrying the identity information of the first area unit, when the other area units in the first P2P network receive the network join request, verify the identity information of the first area unit, and broadcast the verification result to determine whether to allow the first The zone unit joins the first P2P network.
  • the implementation manner of reloading the block information from the first P2P network by the first area unit may be: the management data link of the first area unit sends a management data link acquisition request to the management data link of any other area unit in the first P2P network.
  • the management data link of the other area unit receives the management data link acquisition request, the block in the chain of the first area unit is sent to the management data link of the first area unit, so that the management data link of the first area unit can obtain each Block.
  • the database access layer of the first area unit receives the first network join confirmation message and transmits a data recovery confirmation message to the management system of the first area unit.
  • the database access layer of the first area unit When the database access layer of the first area unit receives the first network join confirmation message sent by the management data link of the first area unit, determining that the data of the management data link of the current first area unit is restored, therefore, the first area unit
  • the database access layer may send a data recovery confirmation message to the management system of the first regional unit.
  • each regional unit further includes a database cache
  • the stored management data in the database cache of the first regional unit may have expired, and therefore, when the first region When the data in the management data link of the unit is restored, the latest management data can be re-stored in the database cache of the first area unit.
  • the database access layer of the first area unit determines whether management data is stored in the database cache of the first area unit, and if not, determines management data according to the management data link of the first area unit, and writes the determined management data. Enter the database cache of the first zone unit.
  • the database access layer of the first area unit has been explained in detail in step 504 according to the management data link of the first area unit and the determination management data, and the description will not be repeated here.
  • the distributed cloud data center includes a plurality of area units.
  • the management data link in the first area unit stores the The updated management data, and instructing the second management database node to store the updated management data in the management data link of the second area unit. Therefore, in the present application, when the first management database node stores the updated management data, the management database node of the other regional unit will also store the updated management data to implement the management database node of each regional unit. Management data is stored and the stored management data is consistent.
  • management data is stored in each area unit, so that each of the area units can acquire management data from its own management data chain, which improves the efficiency of the area unit to obtain management data.
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • FIG. 6 is a flowchart of another method for storing management data according to an embodiment of the present disclosure. The method is applied to the distributed cloud data center of FIG. 2B. As shown in FIG. 6, the method includes the following steps:
  • Step 601 The first management database node of the first area unit acquires the updated management data, and generates a new first block according to the updated management data, where the first area unit is any one of the plurality of area units. unit.
  • the new first block is generated according to the updated management data, that is, the generated new first block includes the updated management data.
  • the implementation manner of obtaining the updated management data by the first management database node and the implementation manner of generating the new first block have been explained in detail in the steps in the embodiment of FIG. 4, and will not be further explained herein.
  • Step 602 The first management database node of the first area unit stores the generated first block.
  • the trust path of the management data link is no longer the default path with the most nodes, but the specified trust path. Therefore, when the first management database node of the first area unit generates the first block, After that, the current first trust path needs to be determined by changing the audit data chain, and the first block is added to the end of the first trust path in its own management data chain.
  • step 602 the first management database node determines the first trust path according to the third trust path in the change audit data chain of the first area unit, and the change audit data of the third trust path in the first area unit There are the most nodes in the chain and the new first block is added as the last first block in the first trust path.
  • the information of the current trust path in the data chain of the audit management chain is changed, and the credibility of the information of the audit chain itself is still determined by the method of trusting only the path with the most nodes. And the operation of writing the trust path is completed internally by the system, thereby effectively ensuring the credibility of the trust path information. That is, the third trust path has the most nodes in the change audit data chain of the first area unit.
  • the trust path information in the management data chain is recorded by changing the blocks in the audit data chain. Therefore, before the management data link of the first area unit adds the generated first block to the end of its own trust path, the management data link of the first area unit determines the first area unit through the database access layer of the first area unit Change the end block of the path with the most nodes in the audit data chain, and determine its own trust path according to the end block of the path with the most nodes in the audit data link of the first area unit.
  • the first management database node may determine that the first trust path is implemented according to the third trust path in the change audit data link of the first area unit, that the management data link of the first area unit may be to the first area unit.
  • the database access layer sends a trust path read request, and when the database access layer of the first area unit receives the trust path read request, the trust path read request is sent to the change audit data chain of the first area unit.
  • the change audit data link of the first area unit receives the trust path read request, the second block of the end of the path with the most nodes is determined from the second block at the end of the path with the most nodes.
  • the database access layer of the first area unit transmits the received identifier of the first block to the management data chain of the first area unit.
  • the management data link of the first area unit receives the identifier of the first block, the identifier of the end block is searched from the data link of the first area as the path of the identifier of the first block, and the found path is determined as The first trust path.
  • the management database node of each area unit further includes a database cache
  • the management database node of the first area unit adds the generated first block to the end of the first trust path of the management data link of the own area
  • the received management data can also be cached in the database cache.
  • the management data link of the first area unit transmits the received management data to the database access layer of the first area unit, and the database access layer of the first area unit writes the management data to the database cache of the first area unit.
  • the first first block in the management data chain of the first area unit is obtained according to the factory configuration data set by the publisher of the distributed cloud data center. That is, in the initialization state, the management data chain of the first area unit generates the first first block based on the management data at the time of initialization. And the management data link of the first area unit sends a second update request to the change audit data link of the first area unit by using the database access layer of the first area unit, and the change audit data link of the first area unit receives the second update request, and A first second block is generated, and the first second block is used to indicate that the end block of the trust path in the management data chain of the first area unit is the first first block.
  • the management data at the time of initialization is the factory configuration data set by the publisher of the distributed cloud data center.
  • the management data chain may generate a first update request and implement an update to the change audit data chain by the following step 603 according to the first update request.
  • Step 603 The first management database node of the first area unit sends a first update request to its own change audit data link, and adds a second block at the end of the path with the most nodes in the change audit data link of its own.
  • the second block is used to indicate that the end block of the trust path in the management data chain of the first area unit is the generated first block.
  • the implementation of the step 603 may be: the management data link of the first area unit sends a first update request to the database access layer of the first area unit, where the first update request carries the first block generated in step 601. logo.
  • the first update request is sent to the change audit data chain of the first area unit.
  • the change audit data link of the first area unit receives the first update request, and adds a second block in the path that has the most node, and the currently added second block is used to indicate the management data of the current first area unit.
  • the end block of the trust path in the chain is the first block generated.
  • the first update request carries the identifier of the first block generated in step 601
  • the change audit data link of the first area unit receives the first update request, according to the first area carried in the first update request
  • the identifier of the block generates a second block
  • the generated second block is added to the end of the path having the most nodes, and the generated second block stores the identifier of the first block generated in step 601.
  • Step 604 The first management database node of the first area unit broadcasts the generated first block in the first P2P network, so that the management database node of each area unit except the first area unit will generate The first block is added to the end of the trust path of its own management data link, and the management database node of each area unit other than the first area unit adds a second in the path with the most nodes in the change audit data link. Block.
  • each area unit of the distributed cloud data center shares a set of management data, it is necessary to ensure the consistency of the management data link in each area unit and the data stored in the change audit data link. Therefore, after the management data link of the first area unit generates the first block, the generated first block needs to be transmitted in the first P2P network, so that the other area units update their management data link according to step 604. Change the audit data chain.
  • the change audit data link of the other area unit adds the second block in the path with the most nodes and the change audit data link of the first area adds the second in the path with the most nodes of the own area.
  • the implementation of the blocks is basically the same and will not be elaborated here.
  • the distributed cloud data center includes a plurality of regional units, and the management database nodes of each regional unit include a management data link and a change audit data link.
  • the first area unit obtains the updated management data, generates a first block according to the updated management data, and determines a first trust path of the management data chain according to the change audit data chain, and then according to the first trust path.
  • the first block is stored in the management data chain.
  • the management database node of the first area unit broadcasts the generated first block in the first P2P network, so that the management database node of each area unit other than the first area unit will generate the first block Join the end of the trust path of your own management data link.
  • management data is stored in each area unit, so that each of the area units can obtain management data from its own management data chain, thereby improving the efficiency of obtaining the management data by the area unit. .
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • FIG. 7 is a flowchart of another method for storing management data according to an embodiment of the present application, which is applied to the distributed cloud data center shown in FIG. 2B, and the method for storing management data shown in FIG. 7 is used for FIG. 6
  • the method of storing management data is further illustrated. Specifically, as shown in FIG. 6, the method includes the following steps:
  • Step 701 The first management database node of the first area unit acquires the updated management data, and generates a first block according to the updated management data, where the first area unit is any one of the plurality of area units.
  • step 701 is basically the same as the implementation manner of step 601 in the embodiment shown in FIG. 6, and will not be elaborated in the same time.
  • Step 702 The first management database node of the first area unit stores the generated first block.
  • step 702 is basically the same as the implementation of step 602 in the embodiment shown in FIG. 6, and will not be described in detail again.
  • Step 703 The first management database node of the first area unit sends a first update request to its own change audit data link, and adds a second block to the end of the path with the most nodes of its own change audit data link.
  • the second block is used to indicate that the end block of the trust path in the management data chain of the first area unit is the generated first block.
  • step 703 is basically the same as the implementation manner of step 603 in the embodiment shown in FIG. 6, and will not be elaborated in the same time.
  • Step 704 The first management database node of the first area unit broadcasts the generated first block in the first P2P network, so that the management database node of each area unit except the first area unit will generate The first block is added to the end of the trust path of its own management data link, and the management database node of each area unit other than the first area unit is added to the path with the most nodes in the change audit data chain. Second block.
  • step 704 is basically the same as the implementation of step 604 in the embodiment shown in FIG. 6, and will not be elaborated in the second.
  • the above steps 701 to 704 are used to explain how to determine the management data link and change audit data chain of each area unit, that is, to explain the management data chain and change audit data link write management to each area unit.
  • the process of data The following is a description of the management data link of the regional unit and the application of the change audit data link.
  • the application of the management data link and the change audit data link for the regional unit include the following two aspects:
  • step 705 is used to explain how to read the management data from the management data link of the regional unit and the change audit data chain
  • steps 706 and 707 are used to explain how to manage the data link and change according to the regional unit.
  • the audit data link performs management data recovery.
  • Step 705 Acquire management data when the first management database node of the first area unit receives the management data read request.
  • the first management database node of the first area unit receives the management data read request, and determines the end block of the path with the most nodes in the change audit data chain of the first area unit, and the first area of the first area unit
  • the management database node determines the trusted road hole in the management data chain according to the end block of the path with the most nodes in the audit data chain of the change, and the first management database node of the first area unit has its own management data link.
  • the first block at the end of the path of the most node reads the management data. That is, the first management database node determines the first trust path according to the third trust path, and reads the management data in the last first block in the first trust path.
  • the foregoing process may be implemented by the following steps 7051 to 7053:
  • Step 7051 When the service system of the first area unit receives the management data read request, forward the management data read request to the management system of the first area unit.
  • the management data read request is triggered by the user, and the distributed cloud data center shown in FIG. 2B knows that the service system of each regional unit is not connected to the management database node, but by each regional unit.
  • the management system is connected to the management database node. Therefore, when the service system of the first area unit receives the management data read request, the management data read request needs to be forwarded to the management system of the first area unit.
  • Step 7052 The management system of the first area unit acquires management data from the management database node of the first area unit.
  • step 7052 is: when the management system of the first area unit receives the management data read request, the management system of the first area unit sends the management data read to the database access layer of the first area unit. Requesting, the database access layer of the first area unit receives the management data read request, and determines management data according to the management data link of the first area unit and the change audit data chain, and the database access layer of the first area unit is directed to the first area unit The management system sends the determined management data.
  • each regional unit further includes a database cache
  • the database access layer of the first regional unit determines the management data according to the management data link of the first regional unit and the change audit data chain
  • the management system of the first area unit acquires management data through the database access layer of the first area unit, and the database access layer of the first area unit obtains management data from the management data link and the change audit data chain.
  • the management data is stored in the database cache to improve the efficiency of obtaining the management data. If the database access layer of the first area unit does not obtain the management data from the database cache of the first area unit, then the management data link is Obtain management data in the change audit data chain.
  • the implementation manner of determining the management data by the database access layer of the first area unit according to the management data link of the first area unit and the change audit data link may be: changing the audit data of the database access layer of the first area unit to the first area unit.
  • the chain sends a trust path read request
  • the change audit data link of the first area unit receives the trust path read request, and searches for the end second block of the path with the most nodes
  • the change audit data chain of the first area unit is based on Finding the second block, determining an identifier of the first block at the end of the trust path of the management data link of the first area unit, and transmitting the identifier of the first block at the end of the trust path to the first area unit a database access layer
  • the database access layer of the first area unit sends the identifier of the first block at the end of the trust path to the management data link of the first area unit
  • the management data link of the first area unit is based on the end of the trust path
  • the identifier of a block finds the
  • the database access layer of the first area unit first determines the trust path in the management data of the first area unit through the change audit data chain of the first area unit, and then obtains the management from the management data link according to the determined trust chain. Data to ensure the credibility of the acquired management data.
  • Step 7053 The management system of the first area unit sends the acquired management data to the service system of the first area unit.
  • the management system of the first area unit When the management system of the first area unit receives the management data sent by the database access layer of the first area unit, the management system of the first area unit sends the received management data to the service system of the first area unit to complete the reading. The process of managing data.
  • Step 706 After the first regional unit fails to cause a problem in its management data link, when the first management database node of the first regional unit receives the first type of data recovery request, the first management database node of the first regional unit Perform data recovery.
  • the first management database node of the first regional unit receives the first type of data recovery request, and rejoins its own management data link to the first P2P network. Reloading the block information from the first P2P network, and rejoining the change audit data link of the first P2P network to the second P2P network, reloading the block information from the second P2P network, and the first management database node of the first area unit Returns a data recovery confirmation message.
  • the database access layer of the first area unit receives the first type of data recovery request, and respectively manages the data link to the first area unit and changes the audit data link. Send a network join request.
  • the first type of data recovery request is triggered by a preset operation by the administrator, that is, after the first area unit fails, when the manager needs to restore the first area unit, the first operation may be triggered by a preset operation.
  • Class data recovery request is triggered by a preset operation by the administrator, that is, after the first area unit fails, when the manager needs to restore the first area unit, the first operation may be triggered by a preset operation.
  • the first regional unit may be added to the first P2P network and the second P2P network.
  • the management data link and the change audit data link of a regional unit are rejoined to the first P2P network and the second P2P network to restore the management data link of the first area unit and change the block data in the audit data chain.
  • the management data link of the first area unit receives the network join request, rejoins the first P2P network, and reloads the block information from the first P2P network, and after obtaining each of its own blocks, the first area unit
  • the database access layer sends a first network join confirmation message
  • the change audit data link of the first area unit receives the network join request, rejoins the second P2P network, and reloads the block information from the second P2P network, and obtains each of its own
  • the block sends a second network join confirmation message to the database access layer of the first area unit.
  • the management data link of the first area unit receives the network join request, and the method of rejoining the first P2P network is: the management data link of the first area unit broadcasts a network join request in the first P2P network, and the network join request Carrying the identity information of the first area unit, when the other area units in the first P2P network receive the network join request, verify the identity information of the first area unit, and broadcast the verification result to determine whether to allow the first The zone unit joins the first P2P network.
  • the implementation manner of reloading the block information from the first P2P network by the first area unit may be: the management data link of the first area unit sends a management data link acquisition request to the management data link of any other area unit in the first P2P network.
  • the management data link of the other area unit receives the management data link acquisition request, the block in the chain of the first area unit is sent to the management data link of the first area unit, so that the management data link of the first area unit can obtain each Block.
  • the manner in which the first area unit reloads the block information from the second P2P network may be: the change audit data link of the first area unit sends the change audit data to the change audit data link of any other area unit in the second P2P network.
  • the chain acquisition request when the change audit data link of the other area unit receives the change audit data link acquisition request, sends the block in the chain of the first area unit to the change audit data chain of the first area unit, so that the first area unit Each block can be obtained by changing the audit data chain.
  • the database access layer of the first area unit receives the first network join confirmation message and the second network join confirmation message, and sends a data recovery confirmation message to the management system of the first area unit.
  • the database access layer of the first area unit When the database access layer of the first area unit receives the first network join confirmation message sent by the management data link of the first area unit and the second network join confirmation message sent by the change audit data link of the first area unit, determining the current The management data link of the first area unit and the data in the change audit data chain are restored. Therefore, the database access layer of the first area unit can transmit a data recovery confirmation message to the management system of the first area unit.
  • each regional unit further includes a database cache
  • the stored management data in the database cache of the first regional unit may have expired, and therefore, when the first region
  • the latest management data can be re-stored in the database cache of the first area unit.
  • the database access layer of the first area unit determines whether management data is stored in the database cache of the first area unit, and if not, determines management data according to the management data link of the first area unit and the change audit data link, and The determined management data is written into the database cache of the first area unit.
  • the database access layer of the first area unit determines the management data according to the management data link of the first area unit and the change audit data link. The detailed description is in step 705, and the description is not repeated here.
  • the process of restoring the management data link and the change audit data link in the management database node in the first area is referred to as the first type of data recovery.
  • the first type of data recovery may be applied to the disaster recovery and back-cutting process, or may be applied to a scenario where the device or system corresponding to the area unit fails and the locally stored management data is damaged.
  • the following step 707 is used to introduce the second type of data recovery provided by the embodiment of the present application, and the second type of data recovery is applied to a logic error scenario.
  • the logical error scenario refers to a scenario in which the management data is configured to an incorrect value according to a normal configuration process due to an intentional or unintentional error.
  • the configuration process since the configuration process is normal, the current valid data of all the regional units is configured. Wrong data.
  • Step 707 When the first management database node of the first area unit receives the second type data recovery request, the first management database node of the first area unit performs data recovery, and the second type of data recovery request is used to indicate that the time is to be specified.
  • the management data is determined to be valid management data.
  • the implementation manner of the data recovery by the management database node of the first area unit may be: the first management database node acquires the specified time carried in the data recovery request, and the first management database node is in the first area unit according to the specified time Querying, in the data link, a first block whose query timestamp matches the specified time, the first management database node generates a new second block according to the first block found, and adds the new second block And being the last second block in the third trust path, the new second block is configured to reset the first trust path according to the first block that is found.
  • the management system of the first area unit receives the second type of data recovery request
  • the second type of data recovery request is sent to the database access layer of the first area unit, and the database access layer of the first area unit is according to the specified time
  • querying from the management data link of the first area unit, the first block whose timestamp matches the specified time, and the database access layer of the first area unit changes the audit data to the first area unit according to the first block that is found.
  • the chain sends a trust path reset request
  • the change audit data link of the first area unit receives the trust path reset request, and adds a second block at the end of the path with the most nodes, and the currently added second block
  • the end block for indicating the trust path of the current management data link is the first block of the search
  • the change audit data chain of the first area unit sends a trust path reset confirmation message to the database access layer of the first area unit, first
  • the database access layer of the regional unit receives the trust chain reset confirmation message and sends data recovery to the management system of the first regional unit Confirmation message.
  • the database access layer of the first area unit queries the first block that matches the timestamp and the specified time from the management data link of the first area unit according to the specified time: the database access layer direction of the first area unit
  • the management data link of the first area unit sends a block query request, and the block query request carries the specified time.
  • the management data link of the first area unit receives the block query request, according to the specified time from the chain of the own And searching for the first block whose timestamp matches the specified time, and sending the identifier of the found first block to the database access layer of the first area unit.
  • the database access layer of the first area unit carries the identifier of the first block that is found to the trust path reset request sent by the change audit data link of the first area unit, so that the change of the first area unit is audited.
  • the data chain stores the identity of the first block into the newly added second block.
  • the change audit data link of the first regional unit adds one at the end of its own path with the most nodes.
  • the change audit data link of the first area unit broadcasts the currently added second block in the second P2P network, so that each area unit except the first area unit will be newly added.
  • the second block is added to the end of the path with the most nodes of its own change audit data chain to enable reconfiguration of valid data for all area units.
  • the management database node of each area unit further includes a database cache
  • the second type of data recovery when the second type of data recovery is performed, it indicates that the data stored in the current database cache is also erroneous data, and therefore, the database access layer of the first area unit
  • the management data in the first block found Before sending the data recovery confirmation message to the management system of the first area unit, the management data in the first block found may also be determined, and the determined management data is written into the database cache of the first area unit, so that the first The management data in the database cache of the zone unit is updated.
  • the distributed cloud data center includes a plurality of regional units, and the management database nodes of each regional unit include a management data link and a change audit data link.
  • the first area unit obtains the updated management data, generates a first block according to the updated management data, and determines a first trust path of the management data chain according to the change audit data chain, and then according to the first trust path.
  • the first block is stored in the management data chain.
  • the management database node of the first area unit broadcasts the generated first block in the first P2P network, so that the management database node of each area unit other than the first area unit will generate the first block Join the end of the trust path of your own management data link.
  • management data is stored in each area unit, so that each of the area units can obtain management data from its own management data chain, thereby improving the efficiency of obtaining the management data by the area unit. .
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • an embodiment of the present application provides a storage device 800 for managing data, which is applied to a first management database node in a distributed cloud data center, where the first management database node is a first region of multiple regional units.
  • the management database node of the unit, the distributed cloud data center includes a plurality of area units.
  • the device includes a first storage module 801 and a second storage module 802:
  • the first storage module 801 is configured to perform step 401 in the embodiment of FIG. 4 or step 501 in the embodiment of FIG. 5;
  • the first storage module 802 is configured to perform step 402 in the embodiment of FIG. 4 or step 502 in the embodiment of FIG. 5;
  • the management data chain of each area unit includes a plurality of first blocks, each of the plurality of first blocks includes one management data, and the management data chain of each area unit is a tree structure, the plurality of first blocks are respectively nodes in the first tree structure;
  • the first storage module 801 includes:
  • a generating unit configured to generate a new first block, where the new first block includes the updated management data
  • Adding a unit configured to add the new first block as the last first block in the first trust path
  • the second storage module includes:
  • an indicating unit configured to instruct the second management database node to add the new first block as the last first block in the second trust path.
  • the first trust path has the most node in the management data link of the first area unit
  • the second trust path has the most management data chain of the second area unit where the second management database node is located. node.
  • each area unit further includes a change audit data chain, and the change audit data chain of each area unit includes a plurality of second blocks, and the plurality of second blocks are interconnected to form a first branch having at least one branch a two-tree structure, wherein the plurality of second blocks are nodes in the second tree structure;
  • the first storage module 801 further includes:
  • a determining unit configured to determine the first trust path according to the third trust path in the change audit data chain of the first area unit, where the third trust path has the most nodes in the change audit data chain of the first area unit.
  • the device further includes:
  • a first receiving module configured to receive a management data read request, determine the first trust path according to the third trust path, and read the updated management data in a last block of the first trust path .
  • each first block has a timestamp, and a timestamp of each first block is used to indicate a time corresponding to the management data thereon;
  • the device 800 also includes:
  • a second receiving module configured to receive a data recovery request, to obtain a specified time carried in the data recovery request, where the data recovery request is used to indicate that the management data at the specified time is determined as valid management data
  • a querying module configured to query, in the management data link of the first area unit, a first block whose timestamp matches the specified time according to the specified time;
  • a generating module configured to generate a new second block according to the first block found, and add the new second block as the last second block in the third trust path, the new The second block is configured to reset the first trust path according to the first block that is found.
  • the distributed cloud data center includes a plurality of area units.
  • the management data link in the first area unit stores the The updated management data, and instructing the second management database node to store the updated management data in the management data link of the second area unit. Therefore, in the present application, when the first management database node stores the updated management data, the management database node of the other regional unit will also store the updated management data to implement the management database node of each regional unit. Management data is stored and the stored management data is consistent.
  • management data is stored in each area unit, so that each of the area units can acquire management data from its own management data chain, which improves the efficiency of the area unit to obtain management data.
  • management data is stored in the management data link of each area unit, there is no possibility that other area units cannot obtain management data.
  • the storage device for managing data provided by the foregoing embodiment is only illustrated by the division of the foregoing functional modules. In actual applications, the functions may be assigned differently according to needs.
  • the function module is completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the storage device for managing data and the method for storing management data provided by the foregoing embodiments are in the same concept, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital versatile disc (DVD)
  • DVD digital versatile disc
  • SSD solid state disk
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention porte sur un procédé et sur un dispositif de stockage de données de gestion ainsi que sur un support d'informations. Le procédé comprend les étapes consistant : lorsqu'un premier nœud de base de données de gestion dans une première unité de région acquiert des données de gestion mises à jour, à stocker les données de gestion mises à jour dans une chaîne de données de gestion de la première unité de région et à donner l'instruction à un second nœud de base de données de gestion de stocker les données de gestion mises à jour dans une chaîne de données de gestion d'une seconde unité de région. Lorsqu'un premier nœud de base de données de gestion stocke des données de gestion mises à jour, les nœuds de base de données de gestion dans les autres unités de région stockent également les données de gestion mises à jour de sorte que le nœud de base de données de gestion dans chaque unité de région stocke les données de gestion et que les données de gestion stockées sont cohérentes, que chaque unité de région peut acquérir les données de gestion à partir de sa propre chaîne de données de gestion et que l'efficacité d'acquisition des données de gestion par les unités de région peut être améliorée.
PCT/CN2019/078825 2018-03-30 2019-03-20 Procédé et dispositif de stockage de données de gestion et support d'informations WO2019184775A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810292279.3 2018-03-30
CN201810292279.3A CN108616574B (zh) 2018-03-30 2018-03-30 管理数据的存储方法、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2019184775A1 true WO2019184775A1 (fr) 2019-10-03

Family

ID=63659550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/078825 WO2019184775A1 (fr) 2018-03-30 2019-03-20 Procédé et dispositif de stockage de données de gestion et support d'informations

Country Status (2)

Country Link
CN (1) CN108616574B (fr)
WO (1) WO2019184775A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111061735A (zh) * 2019-12-13 2020-04-24 上海优扬新媒信息技术有限公司 一种基于单链区块链的扩容方法及装置
CN112256667A (zh) * 2020-09-16 2021-01-22 珠海市新德汇信息技术有限公司 多生物特征归一方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108616574B (zh) * 2018-03-30 2020-06-16 华为技术有限公司 管理数据的存储方法、设备及存储介质
CN109634679B (zh) * 2018-10-16 2023-04-11 平安科技（深圳）有限公司 区块链配置更新方法、装置、设备及存储介质
CN109600433B (zh) * 2018-12-06 2022-03-29 北京磁云数字科技有限公司 一种系统内数据汇总方法及装置
CN110287170B (zh) * 2019-06-28 2021-05-11 杭州复杂美科技有限公司 数据库升级方法、状态数据调用方法、设备和存储介质
CN112099990A (zh) * 2020-08-31 2020-12-18 新华三信息技术有限公司 一种容灾备份方法、装置、设备及机器可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017109140A1 (fr) * 2015-12-22 2017-06-29 Bigchaindb Gmbh Système de base de données orienté vers les actifs, inviolable et décentralisé et procédé d'enregistrement d'une transaction
CN107657438A (zh) * 2017-09-18 2018-02-02 联动优势科技有限公司 一种区块链生成方法、数据验证方法、节点及系统
CN107846282A (zh) * 2017-11-03 2018-03-27 法信公证云（厦门）科技有限公司 一种基于区块链技术的电子数据分布式保管方法及系统
CN108616574A (zh) * 2018-03-30 2018-10-02 华为技术有限公司 管理数据的存储方法、设备及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9967334B2 (en) * 2015-03-02 2018-05-08 Dell Products Lp Computing device configuration and management using a secure decentralized transaction ledger
US9774578B1 (en) * 2016-05-23 2017-09-26 Accenture Global Solutions Limited Distributed key secret for rewritable blockchain
CN107104816A (zh) * 2017-03-07 2017-08-29 阿里巴巴集团控股有限公司 一种信息变更监控方法和装置
CN107276762B (zh) * 2017-05-08 2019-08-30 飞天诚信科技股份有限公司 一种多协议区块链的工作方法及装置
CN107273759B (zh) * 2017-05-08 2020-07-14 上海点融信息科技有限责任公司 用于保护区块链数据的方法、设备以及计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017109140A1 (fr) * 2015-12-22 2017-06-29 Bigchaindb Gmbh Système de base de données orienté vers les actifs, inviolable et décentralisé et procédé d'enregistrement d'une transaction
CN107657438A (zh) * 2017-09-18 2018-02-02 联动优势科技有限公司 一种区块链生成方法、数据验证方法、节点及系统
CN107846282A (zh) * 2017-11-03 2018-03-27 法信公证云（厦门）科技有限公司 一种基于区块链技术的电子数据分布式保管方法及系统
CN108616574A (zh) * 2018-03-30 2018-10-02 华为技术有限公司 管理数据的存储方法、设备及存储介质

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111061735A (zh) * 2019-12-13 2020-04-24 上海优扬新媒信息技术有限公司 一种基于单链区块链的扩容方法及装置
CN111061735B (zh) * 2019-12-13 2023-07-25 度小满科技(北京)有限公司 一种基于单链区块链的扩容方法及装置
CN112256667A (zh) * 2020-09-16 2021-01-22 珠海市新德汇信息技术有限公司 多生物特征归一方法
CN112256667B (zh) * 2020-09-16 2024-03-22 珠海市新德汇信息技术有限公司 多生物特征归一方法

Also Published As

Publication number Publication date
CN108616574B (zh) 2020-06-16
CN108616574A (zh) 2018-10-02

Similar Documents

Publication Publication Date Title
WO2019184775A1 (fr) Procédé et dispositif de stockage de données de gestion et support d'informations
CN110915166B (zh) 区块链
US20220108285A1 (en) Methods and Systems for Object Validated Blockchain Accounts
EP3776208B1 (fr) Autocorrection d'exécution pour registres de chaîne de blocs
US11615195B2 (en) Systems and methods for providing multi-node resiliency for blockchain peers
US11733991B2 (en) Data processing method based on intelligent contract, device, and storage medium
US11055703B2 (en) Smart contract lifecycle management
CN111213340B (zh) 选择用于密码功能的证明委托并使其安全
US10819701B2 (en) Autonomous secrets management for a managed service identity
CN112840617B (zh) 用于管理区块链资源的方法和计算节点，计算机可读介质
US20190172026A1 (en) Cross blockchain secure transactions
US10691790B2 (en) Autonomous secrets management for a temporary shared access signature service
WO2022121538A1 (fr) Procédé et système de synchronisation de données basés sur une chaîne de blocs, et dispositif associé
US11689616B2 (en) Optimization of delivery of blocks
WO2018176265A1 (fr) Procédé d'accès destiné à un système de stockage distribué, dispositif et système associés
JP6617253B1 (ja) 文書管理システム
US20200084041A1 (en) Automated Blockchain Protocol Update
CN112101942A (zh) 基于区块链的交易请求处理方法、系统、装置及设备
US20220311757A1 (en) Cross-regional replication of keys
JPWO2008056496A1 (ja) 情報の管理方法及び情報処理装置
US20220382637A1 (en) Snapshotting hardware security modules and disk metadata stores
US11601262B2 (en) Distributed key management system
US20220035769A1 (en) Peer-to-peer global namespace for storage system metadata federations
Len et al. OPTIKS: An Optimized Key Transparency System
US10922024B1 (en) Self-protection against serialization incompatibilities

Legal Events

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

Ref document number: 19777959

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 19777959

Country of ref document: EP

Kind code of ref document: A1