CN111241115A - Data synchronization method, device, equipment and storage medium - Google Patents

Data synchronization method, device, equipment and storage medium Download PDF

Info

Publication number
CN111241115A
CN111241115A CN202010015144.XA CN202010015144A CN111241115A CN 111241115 A CN111241115 A CN 111241115A CN 202010015144 A CN202010015144 A CN 202010015144A CN 111241115 A CN111241115 A CN 111241115A
Authority
CN
China
Prior art keywords
data
target
synchronized
node device
determining
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010015144.XA
Other languages
Chinese (zh)
Other versions
CN111241115B (en
Inventor
刘攀
李茂材
王宗友
蓝虎
孔利
周开班
时一防
杨常青
张劲松
朱耿良
刘区城
黄焕坤
崔嘉辉
廖志勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202010015144.XA priority Critical patent/CN111241115B/en
Publication of CN111241115A publication Critical patent/CN111241115A/en
Application granted granted Critical
Publication of CN111241115B publication Critical patent/CN111241115B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/2365Ensuring data consistency and integrity
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

The application discloses a data synchronization method, a data synchronization device, data synchronization equipment and a storage medium, and belongs to the technical field of block chains. The method comprises the steps of determining target data from all synchronized data, wherein the synchronized data are data synchronized by node equipment to target node equipment, the target node equipment and the node equipment have an incidence relation, determining at least one piece of data to be synchronized from unsynchronized data based on the target data and a target value, wherein the target value is used for indicating the data volume of the data to be synchronized obtained in one data synchronization process, and sending the at least one piece of data to be synchronized to the target node equipment. The node devices synchronize data in batch in a point-to-point mode, the data do not need to be broadcasted to each node device in the block chain network, and network resource occupation in the data synchronization process can be reduced.

Description

Data synchronization method, device, equipment and storage medium
Technical Field
The present application relates to the field of block chain technologies, and in particular, to a data synchronization method, apparatus, device, and storage medium.
Background
In the block chain technology, data synchronization is usually performed in a broadcast manner, that is, after one node device passes verification on acquired data, the data is added into a local memory pool, and the data is respectively sent to other node devices in a block chain network, so as to complete data broadcast.
However, in the above data synchronization method, a large amount of broadcasted data is copied and transmitted in the blockchain network, which occupies a large amount of network bandwidth, resulting in network performance degradation and affecting normal operation of other services in the network.
Disclosure of Invention
The embodiment of the application provides a data synchronization method, a data synchronization device, data synchronization equipment and a storage medium, and network resources occupied in the data synchronization process can be saved. The technical scheme is as follows:
in one aspect, a data synchronization method is provided, and the method includes:
determining target data from each synchronized data, wherein the synchronized data is data synchronized by the node equipment to the target node equipment, and the target node equipment and the node equipment have an association relationship;
determining at least one piece of data to be synchronized from unsynchronized data based on the target data and a target numerical value, wherein the target numerical value is used for indicating the data volume of the data to be synchronized acquired in one data synchronization process;
and sending the at least one piece of data to be synchronized to the target node equipment.
In one aspect, a data synchronization apparatus is provided, the apparatus including:
a target data determining module, configured to determine target data from each synchronized data, where the synchronized data is data synchronized by the node device to a target node device, and the target node device and the node device have an association relationship;
a data to be synchronized determining module, configured to determine at least one data to be synchronized from unsynchronized data based on the target data and a target value, where the target value is used to indicate a data amount of the data to be synchronized obtained in a data synchronization process;
and the sending module is used for sending the at least one piece of data to be synchronized to the target node equipment.
In one possible implementation, the apparatus further includes:
and the storage module is used for storing the any data and the data identifier of the any data into a data list of the transaction pool based on the numerical value of the data identifier of the any data.
In one aspect, a computer device is provided that includes one or more processors and one or more memories having at least one program code stored therein, the at least one program code being loaded and executed by the one or more processors to implement the operations performed by the data synchronization method.
In one aspect, a computer-readable storage medium having at least one program code stored therein is provided, the at least one program code being loaded and executed by a processor to implement the operations performed by the data synchronization method.
According to the technical scheme provided by the embodiment of the application, target data is determined from all synchronized data, the synchronized data is data synchronized by the node equipment to target node equipment, the target node equipment and the node equipment have an incidence relation, at least one piece of data to be synchronized is determined from unsynchronized data based on the target data and a target value, the target value is used for indicating the data volume of the data to be synchronized obtained in one data synchronization process, and the at least one piece of data to be synchronized is sent to the target node equipment. The node devices synchronize data in batch in a point-to-point mode, the data do not need to be broadcasted to each node device in the block chain network, and network resource occupation in the data synchronization process can be reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a block chain system 100 according to an embodiment of the present disclosure;
fig. 2 is a functional architecture diagram of a node device according to an embodiment of the present application;
fig. 3 is a flowchart of a data synchronization method provided in an embodiment of the present application;
fig. 4 is a schematic diagram of a method for determining data to be synchronized according to an embodiment of the present application;
FIG. 5 is a diagram illustrating a data synchronization process provided by an embodiment of the present application;
FIG. 6 is a diagram illustrating a data list provided by an embodiment of the present application;
fig. 7 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Hereinafter, terms related to the present application are explained.
Blockchain (blockchain): the method is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. The blockchain is essentially a decentralized database, which is a string of data blocks associated by using cryptography, each data block contains information of a batch of network transactions, and the information is used for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.
The block chain underlying platform can comprise processing modules such as user management, basic service, intelligent contract and operation monitoring. The user management module is responsible for identity information management of all blockchain participants, and comprises public and private key generation maintenance (account management), key management, user real identity and blockchain address corresponding relation maintenance (authority management) and the like, and under the authorization condition, the user management module supervises and audits the transaction condition of certain real identities and provides rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node equipment and used for verifying the validity of the service request, recording the service request to storage after the effective request is identified in a consensus, and for a new service request, the basic service firstly performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts service information (consensus management) through a consensus algorithm, transmits the encrypted service information to a shared account (network communication) completely and consistently, and records and stores the encrypted service information; the intelligent contract module is responsible for registering and issuing contracts, triggering the contracts and executing the contracts, developers can define contract logics through a certain programming language, issue the contract logics to a block chain (contract registration), call keys or other event triggering and executing according to the logics of contract clauses, complete the contract logics and simultaneously provide the function of upgrading and canceling the contracts; the operation monitoring module is mainly responsible for deployment, configuration modification, contract setting, cloud adaptation in the product release process and visual output of real-time states in product operation, such as: alarm, monitoring network conditions, monitoring node equipment health status, and the like.
The platform product service layer provides basic capability and an implementation framework of typical application, and developers can complete block chain implementation of business logic based on the basic capability and the characteristics of the superposed business. The application service layer provides the application service based on the block chain scheme for the business participants to use.
The present embodiment provides a blockchain system 100 implemented based on blockchain technology, and a system architecture of the blockchain system is described below.
Fig. 1 is a schematic diagram of a blockchain system 100 according to an embodiment of the present disclosure, referring to fig. 1, the blockchain system 100 may include a plurality of node devices 101, and the blockchain system 100 may further include at least one client.
Node device 101 may be any form of computing device in a network, such as a server, a host, a user terminal, etc. The node apparatus 101 and the node apparatus 101 can share data therebetween. Among them, the node devices 101 may establish a P2P network based on a Peer-To-Peer (P2P) protocol. The P2P Protocol is an application layer Protocol that runs on top of the Transmission Control Protocol (TCP) Protocol.
Each node apparatus 101 may receive input information during normal operation, and maintain shared data in the blockchain system based on the received input information. In order to ensure information intercommunication in the blockchain system, information connection can exist between each node device in the blockchain system, and information transmission can be carried out between the node devices through the information connection. For example, when any node device in the blockchain system receives input information, other node devices in the blockchain system may also acquire the input information and store the input information as data in shared data, so that the data stored on all node devices in the blockchain system are consistent.
In the following, a functional architecture of the node apparatus 101 is described.
Referring to fig. 2, fig. 2 is a functional architecture diagram of a node device according to an embodiment of the present application, where a node device 101 may be functionally divided into a hardware layer, an intermediate layer, an operating system layer, and an application layer, and the specific functions involved may be as follows:
1) routing, a basic function that the node device has for supporting communication between the node devices.
The node device may have the following functions in addition to the routing function:
2) the application is used for being deployed in a block chain, realizing specific services according to actual service requirements, recording data related to the realization functions to form recording data, carrying a digital signature in the recording data to represent a source of task data, and sending the recording data to other node equipment in the block chain system for the other node equipment to add the recording data to a temporary block when the source and integrity of the recording data are verified successfully.
For example, the services implemented by the application include:
2.1) wallet, for providing the function of transaction of electronic money, including initiating transaction (i.e. sending the transaction record of current transaction to other node devices in the blockchain system, after the other node devices are successfully verified, writing the record data of transaction into the temporary blocks of the blockchain as the response of affirming that the transaction is valid; of course, the wallet also supports the querying of the electronic money remaining in the electronic money address.
And 2.2) the shared account book is used for providing functions of operations such as storage, query and modification of account data, sending the recorded data of the operations on the account data to other node equipment in the block chain system, writing the recorded data into a temporary block as a response for acknowledging that the account data is valid after the other node equipment verifies that the operation is valid, and sending confirmation to the node equipment initiating the operation.
2.3) Intelligent contracts, computerized agreements, which can enforce the terms of a contract, implemented by codes deployed on a shared ledger for execution when certain conditions are met, for completing automated transactions according to actual business requirement codes, such as querying the logistics status of goods purchased by a buyer, transferring the buyer's electronic money to the merchant's address after the buyer signs for the goods; of course, smart contracts are not limited to executing contracts for trading, but may also execute contracts that process received information.
3) And the Block chain comprises a series of blocks (blocks) which are mutually connected according to the generated chronological order, new blocks cannot be removed once being added into the Block chain, and the blocks record the record data submitted by the node equipment in the Block chain system.
It is understood that the method provided by the embodiments of the present application may be executed by a node device, where the node device is a computer device, including but not limited to a server or a terminal.
Fig. 3 is a flowchart of a data synchronization method provided in an embodiment of the present application, and the method is described in the embodiment of the present application by taking an example in which the method is applied to a node device in a block chain system. Referring to fig. 3, the method may specifically include the following steps:
301. the node device marks the input data.
The node device may be any node device in the blockchain system, and the node device may be a terminal, a server, and the like, which is not limited in this embodiment of the present application. The input data may be data created by the node device, or may also be data sent by other node devices or a user terminal, which is not specifically limited in this embodiment of the present application.
Each node device in the blockchain system may maintain a transaction pool, where the transaction pool may be used to store data that has been generated but is not yet stored in the blockchain, and the transaction pool may be a memory pool, and the like, which is not limited in this embodiment of the present application. In an embodiment of the present application, the transaction pool may be maintained with a global data identifier (orderIndex), and the node device may tag the input data based on the global data identifier. In one possible implementation, the node device may obtain a global data identifier from a transaction pool in response to a data tagging instruction of any data, the transaction pool may be configured to store the any data, and the node device may use the global data identifier as a data identifier (transactionIndex) of the any data. Wherein a data identity may be used to uniquely indicate a data, in a possible implementation, the global data identity may be in the form of a number, and the global data number may be monotonically increasing. For example, the data marking instruction may be triggered each time a piece of data is added to the transaction pool, the node device may mark the data by using the global data identifier, that is, add a data identifier to the data, and after the data marking is completed, add one to the number of the global data identifier.
It should be noted that, in the embodiment of the present application, a triggering manner of the data marking instruction and a specific representation form of the global data identifier are not limited.
In a possible implementation manner, a data list may be maintained in the transaction pool of the node device, and the data list may use the data identifier of each data as a key and each data as a content. The node device may store the arbitrary data and the data identifier of the arbitrary data in a data list of the transaction pool based on a numerical size of the data identifier of the arbitrary data. That is, each data in the data list is stored according to the sequence of the data identification, which is convenient for data searching and reading in the subsequent data synchronization process. Of course, the data in the data list may also be stored in other orders, which is not limited in this embodiment of the application.
302. The node device determines target data from the respective synchronized data.
The synchronized data is data synchronized by the node device to a target node device, and the target node device and the node device have an association relationship. For example, one node device may only send data to other node devices having an association relationship with itself, and then the other node devices propagate the data based on the association relationship between the nodes to synchronize the data to each node device in the blockchain system, thereby achieving a data broadcasting effect, avoiding a large amount of same data from being copied and transmitted in the blockchain system, and reducing occupation of network resources in the blockchain system.
In a possible implementation manner, node identifiers of node devices having an association relationship with the node devices may be stored in the node devices to record the association relationship between the node devices, where one node identifier may be used to uniquely indicate one node device. Of course, the blockchain system may also include a data management node device, where the data management node device may store an association relationship between the node devices, and before performing data synchronization, each node device may query the node device having an association relationship with itself through the data management node device, and then perform a data sending step. The embodiment of the present application does not limit the recording method of the association relationship. In the embodiment of the present application, a description will be given taking as an example that node identifiers of respective node apparatuses having an association relationship with the node apparatuses are stored in the node apparatuses.
In a possible implementation manner, an association relationship may be established between two node devices in the blockchain system by sending target information, where the target information may be set by a developer, and this is not limited in this embodiment of the present application. Of course, the association relationship between two node devices may also be established in other ways, which is not limited in this embodiment of the present application. In a possible implementation manner, the association relationship may be an adjacency relationship or the like, and the embodiment of the present application does not specifically limit what kind of association relationship exists between two nodes.
It should be noted that the node device may have an association relationship with at least one other node device in the blockchain system, and the embodiment of the present application is described only by taking a target node device having an association relationship with the node device as an example.
In a possible implementation manner, the node device may traverse a synchronization data list according to a target period, where the synchronization data list is used to record latest synchronization data in each data synchronization process, and the node device may use the latest synchronization data corresponding to a data synchronization process closest to the current time as the target data based on the synchronization data list. The target period may be set by a developer, and is not limited in this embodiment of the application. In a possible implementation manner, the synchronization data list may be in the form of a hash table, a node identifier of the target node device may be used as a key of the hash table, the node device may obtain a data identifier of the latest synchronization data in each data synchronization process, and a storage location of the data identifier in the data list is used as the content of the hash table, and the node device may record the latest synchronization data in each data synchronization process through the hash table. When the data identifier is represented as a data number, the node device obtains the data identifier of the latest synchronization data in each data synchronization process, that is, obtains the data identifier with the largest value in each data synchronization process. In a possible implementation manner, each item of data in the hash table may carry a timestamp, where the timestamp may be used to indicate a start time of each data synchronization process, and the node device may determine, based on the timestamp corresponding to each data synchronization process, a data synchronization process that is closest to a current time, so as to determine the target data. Of course, the node device may also determine the target data in other ways, which is not limited in this embodiment of the application.
It should be noted that the hash table is only one representation form of the synchronization data list, and the embodiment of the present application does not limit the specific form of the synchronization data list.
In the embodiment of the application, the synchronous data list only records the latest synchronous data in each data synchronization process, so that the node device can conveniently query the current data synchronization condition of the target node device, and the query efficiency is improved.
303. The node device determines at least one piece of data to be synchronized from unsynchronized data based on the target data and the target value.
The target value is used for indicating the data volume of the data to be synchronized acquired in the primary data synchronization process, and the specific value can be set by a developer. In this embodiment of the present application, the target values corresponding to each data synchronization process may be the same or different, and the target values corresponding to each node device may be the same or different, which is not limited in this embodiment of the present application.
In one possible implementation, the node device may determine at least one data from the data list based on the target data and the target value, and perform a subsequent data synchronization step. In this embodiment of the application, the node device may perform screening and deduplication on the at least one piece of data, and further determine data to be synchronized. In a possible implementation manner, the step 303 may specifically include the following steps:
step one, the node equipment determines at least one candidate data from the unsynchronized data based on the target data and the target value.
In a possible implementation manner, the node device may determine a first storage location of the target data in a data list, where the data list stores at least one synchronized data and at least one unsynchronized data, and the node device may determine at least one second storage location in the data list based on the first storage location and the target value, and obtain data stored in the at least one second storage location as the at least one candidate data. Fig. 4 is a schematic diagram of a method for determining data to be synchronized according to an embodiment of the present application, referring to fig. 4, when the data synchronization list 401 is represented as a hash table, the node device may determine, based on the hash table, a storage location of the data identifier of the target data in the data list as the first storage location 402, taking the target value as 3 as an example, the node device may determine, from a next location 403 of the first storage location 402, 3 second storage locations, and read data corresponding to the 3 second storage locations, that is, data in an area 404, as the candidate data.
And step two, the node equipment compares the at least one candidate data with the data synchronization record of the target node equipment, and performs data deduplication on the at least one candidate data.
In one possible implementation manner, a data synchronization record may be maintained in the transaction pool of the node device, and the data synchronization record is used for recording data synchronized by each data synchronization process and a node identifier of the data receiving node device. In a possible implementation manner, one node device may correspond to one data synchronization record, and taking the data synchronization record corresponding to the target node device as an example, the data synchronization record may store a node identifier of the target node device, and the node device and the target node device may synchronize data identifiers of data with each other. Of course, other information, such as the start and stop time of each data synchronization process, may also be stored in the data synchronization record, and the specific content of the data synchronization record is not limited in the embodiments of the present application.
In a possible implementation manner, the node device may compare the data identifier of each candidate data with each data identifier in the data synchronization record corresponding to the target node device, and perform data deduplication based on a comparison result, that is, remove the synchronized data in the candidate data.
And step three, the node equipment determines the at least one candidate data after the duplication removal as the at least one data to be synchronized.
It should be noted that, the above description of the manner of acquiring the data to be synchronized is only an exemplary description, and the embodiment of the present application does not limit which manner is specifically adopted to acquire the data to be synchronized.
304. The node device sends the at least one piece of data to be synchronized to the target node device.
In one possible implementation, the node device may package the at least one piece of data to be synchronized into a message, and send the message to the target node device based on the node identifier of the target node device. Of course, the node device may also package the at least one piece of data to be synchronized into another data format, and perform the step of sending the data, which is not limited in this embodiment of the present application.
According to the technical scheme provided by the embodiment of the application, target data is determined from all synchronized data, the synchronized data is data synchronized by the node equipment to target node equipment, the target node equipment and the node equipment have an incidence relation, at least one piece of data to be synchronized is determined from unsynchronized data based on the target data and a target value, the target value is used for indicating the data volume of the data to be synchronized obtained in one data synchronization process, and the at least one piece of data to be synchronized is sent to the target node equipment. The node devices synchronize data in batch in a point-to-point mode, the data do not need to be broadcasted to each node device in the block chain network, and network resource occupation in the data synchronization process can be reduced.
Fig. 5 is a schematic diagram of a data synchronization process provided by an embodiment of the present application, referring to fig. 5, the node device may traverse a data synchronization list, i.e., the hash table 501, reads the location information 502 corresponding to the data identification of the latest synchronization data transmitted to the target node device, reads m data from the location 504 of the data list 503 based on the location information 502, i.e., the data in area 505, where m is a positive integer, the specific value of which may be set by a developer, the node device may query whether there is already synchronized data in the m data based on the data synchronization record 506 corresponding to the target node device, if so, the m data are filtered out, the filtered data are packaged into a message 507, and the message is sent to the target node device based on the node identification of the target node device. In the data synchronization process, data can be synchronized in batches aiming at different node devices, the efficiency of data synchronization in a transaction pool is improved, network resources are effectively utilized, and the probability of network storms is reduced.
In the embodiments of the present application, after the node device completes data synchronization, the synchronized data list and the data synchronization record may be updated.
In a possible implementation manner, the node device may store the latest synchronization data in the data synchronization process into the synchronization data list. Taking the synchronized data list as a hash table as an example, referring to fig. 6, fig. 6 is a schematic diagram of a data list provided in an embodiment of the present application, when data synchronized in the current data synchronization process is data 601, data 602, and data 603 in the data list, the node device may use data corresponding to a data identifier with a largest value, that is, data 603, as latest synchronized data in the current data synchronization process, and write a storage location corresponding to the data identifier of the data 603 into the hash table.
In one possible implementation, the node device may update the data synchronization record of the target node device based on the node identification of the target node device and the at least one data to be synchronized. That is, the node device may write information such as a data identifier of the data synchronized in the data synchronization process into the data synchronization record corresponding to the target node device.
Of course, when the node device receives data synchronized by other node devices, the data synchronization record may also be updated. Taking receiving the data synchronized by the target node device as an example, in a possible implementation manner, the node device may write information such as a data identifier of the received data into a data synchronization record corresponding to the target node device.
All the above optional technical solutions may be combined arbitrarily to form optional embodiments of the present application, and are not described herein again.
Fig. 7 is a schematic structural diagram of a data synchronization apparatus provided in an embodiment of the present application, where the data synchronization apparatus may be a computer program (including program code) running in a computer device, for example, the data synchronization apparatus is an application software; the apparatus may be used to perform the corresponding steps in the methods provided by the embodiments of the present application. Referring to fig. 7, the apparatus includes:
a target data determining module 701, configured to determine target data from each synchronized data, where the synchronized data is data synchronized by the node device to a target node device, and the target node device and the node device have an association relationship;
a to-be-synchronized data determining module 702, configured to determine, based on the target data and a target value, at least one to-be-synchronized data from unsynchronized data, where the target value is used to indicate a data amount of the to-be-synchronized data obtained in a data synchronization process;
a sending module 703, configured to send the at least one piece of data to be synchronized to the target node device.
In one possible implementation, the target data determination module 701 is configured to:
traversing a synchronous data list according to a target period, wherein the synchronous data list is used for recording the latest synchronous data in each data synchronization process;
and based on the synchronous data list, taking the latest synchronous data corresponding to the data synchronous process closest to the current time as the target data.
In one possible implementation, the to-be-synchronized data determining module 702 is configured to:
determining at least one candidate data from the unsynchronized data based on the target data and the target value;
comparing the at least one candidate data with a data synchronization record of the target node device, and performing data deduplication on the at least one candidate data, wherein the data synchronization record is used for recording data synchronized in each data synchronization process and node identification of a data receiving node device;
and determining the at least one candidate data after the duplication removal as the at least one data to be synchronized.
In one possible implementation, the to-be-synchronized data determining module 702 is configured to:
determining a first storage position of the target data in a data list, wherein the data list stores at least one synchronized data and at least one unsynchronized data;
determining at least one second storage location in the data list based on the first storage location and the target value;
and acquiring the data stored in the at least one second storage position as the at least one candidate data.
In one possible implementation, the apparatus further includes:
and the updating module is used for updating the data synchronization record of the target node equipment based on the node identification of the target node equipment and the at least one piece of data to be synchronized.
In one possible implementation, the apparatus further includes:
the identification acquisition module is used for responding to a data marking instruction of any data and acquiring a global data identification from a transaction pool, and the transaction pool is used for storing the any data;
and the identification determining module is used for taking the global data identification as the data identification of any data.
In one possible implementation, the apparatus further includes:
and the storage module is used for storing the any data and the data identifier of the any data into a data list of the transaction pool based on the numerical value of the data identifier of the any data.
The apparatus provided in the embodiment of the present application determines, from each synchronized data, target data, where the synchronized data is data synchronized by the node device to a target node device, and the target node device and the node device have an association relationship, and determines, based on the target data and a target value, at least one to-be-synchronized data from unsynchronized data, where the target value is used to indicate a data amount of the to-be-synchronized data obtained in a data synchronization process, and sends the at least one to-be-synchronized data to the target node device. The node devices synchronize data in batch in a point-to-point mode, the data do not need to be broadcasted to each node device in the block chain network, and network resource occupation in the data synchronization process can be reduced.
It should be noted that: in the data synchronization device provided in the above embodiment, only the division of the above functional modules is used for illustration when data is synchronized, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above described functions. In addition, the data synchronization device and the data synchronization method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.
The node device provided in the foregoing technical solution may be implemented as a terminal or a server, for example, fig. 8 is a schematic structural diagram of a terminal provided in this embodiment of the present application. The terminal 800 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. The terminal 800 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.
In general, the terminal 800 includes: one or more processors 801 and one or more memories 802.
The processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 801 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 801 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 801 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 801 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 802 may include one or more computer-readable storage media, which may be non-transitory. Memory 802 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 802 is used to store at least one program code for execution by the processor 801 to implement the data synchronization methods provided by the method embodiments herein.
In some embodiments, the terminal 800 may further include: a peripheral interface 803 and at least one peripheral. The processor 801, memory 802 and peripheral interface 803 may be connected by bus or signal lines. Various peripheral devices may be connected to peripheral interface 803 by a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 804, a display screen 805, a camera assembly 806, an audio circuit 807, a positioning assembly 808, and a power supply 809.
The peripheral interface 803 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 801 and the memory 802. In some embodiments, the processor 801, memory 802, and peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 801, the memory 802, and the peripheral interface 803 may be implemented on separate chips or circuit boards, which are not limited by this embodiment.
The Radio Frequency circuit 804 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 804 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 804 converts an electrical signal into an electromagnetic signal to be transmitted, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 804 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 804 may further include NFC (Near Field Communication) related circuits, which are not limited in this application.
The display screen 805 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 805 is a touch display, the display 805 also has the ability to capture touch signals on or above the surface of the display 805. The touch signal may be input to the processor 801 as a control signal for processing. At this point, the display 805 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 805 may be one, providing the front panel of the terminal 800; in other embodiments, the display 805 may be at least two, respectively disposed on different surfaces of the terminal 800 or in a folded design; in some embodiments, display 805 may be a flexible display disposed on a curved surface or a folded surface of terminal 800. Even further, the display 805 may be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The Display 805 can be made of LCD (liquid crystal Display), OLED (Organic Light-Emitting Diode), and the like.
The camera assembly 806 is used to capture images or video. Optionally, camera assembly 806 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 806 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuit 807 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 801 for processing or inputting the electric signals to the radio frequency circuit 804 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 800. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 801 or the radio frequency circuit 804 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 807 may also include a headphone jack.
The positioning component 808 is used to locate the current geographic position of the terminal 800 for navigation or LBS (location based Service). The positioning component 808 may be a positioning component based on the GPS (global positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.
Power supply 809 is used to provide power to various components in terminal 800. The power supply 809 can be ac, dc, disposable or rechargeable. When the power source 809 comprises a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, terminal 800 also includes one or more sensors 810. The one or more sensors 810 include, but are not limited to: acceleration sensor 811, gyro sensor 812, pressure sensor 813, fingerprint sensor 814, optical sensor 815 and proximity sensor 816.
The acceleration sensor 811 may detect the magnitude of acceleration in three coordinate axes of the coordinate system established with the terminal 800. For example, the acceleration sensor 811 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 801 may control the display 805 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 811. The acceleration sensor 811 may also be used for acquisition of motion data of a game or a user.
The gyro sensor 812 may detect a body direction and a rotation angle of the terminal 800, and the gyro sensor 812 may cooperate with the acceleration sensor 811 to acquire a 3D motion of the user with respect to the terminal 800. From the data collected by the gyro sensor 812, the processor 801 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
Pressure sensors 813 may be disposed on the side frames of terminal 800 and/or underneath display 805. When the pressure sensor 813 is disposed on the side frame of the terminal 800, the holding signal of the user to the terminal 800 can be detected, and the processor 801 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 813. When the pressure sensor 813 is disposed at a lower layer of the display screen 805, the processor 801 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 805. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 814 is used for collecting a fingerprint of the user, and the processor 801 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 814, or the fingerprint sensor 814 identifies the identity of the user according to the collected fingerprint. Upon identifying that the user's identity is a trusted identity, the processor 801 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying for and changing settings, etc. Fingerprint sensor 814 may be disposed on the front, back, or side of terminal 800. When a physical button or a vendor Logo is provided on the terminal 800, the fingerprint sensor 814 may be integrated with the physical button or the vendor Logo.
The optical sensor 815 is used to collect the ambient light intensity. In one embodiment, processor 801 may control the display brightness of display 805 based on the ambient light intensity collected by optical sensor 815. Specifically, when the ambient light intensity is high, the display brightness of the display screen 805 is increased; when the ambient light intensity is low, the display brightness of the display 805 is reduced. In another embodiment, the processor 801 may also dynamically adjust the shooting parameters of the camera assembly 806 based on the ambient light intensity collected by the optical sensor 815.
A proximity sensor 816, also known as a distance sensor, is typically provided on the front panel of the terminal 800. The proximity sensor 816 is used to collect the distance between the user and the front surface of the terminal 800. In one embodiment, when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 gradually decreases, the processor 801 controls the display 805 to switch from the bright screen state to the dark screen state; when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 becomes gradually larger, the display 805 is controlled by the processor 801 to switch from the breath-screen state to the bright-screen state.
Those skilled in the art will appreciate that the configuration shown in fig. 8 is not intended to be limiting of terminal 800 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.
Fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application, where the server 900 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 901 and one or more memories 902, where the one or more memories 902 store at least one program code, and the at least one program code is loaded and executed by the one or more processors 901 to implement the methods provided by the foregoing method embodiments. Certainly, the server 900 may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the server 900 may also include other components for implementing device functions, which are not described herein again.
In an exemplary embodiment, a computer readable storage medium, such as a memory including at least one program code, which is executable by a processor to perform the data synchronization method in the above embodiments, is also provided. For example, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or implemented by at least one program code associated with hardware, where the program code is stored in a computer readable storage medium, such as a read only memory, a magnetic or optical disk, etc.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (15)

1. A data synchronization method is applied to a node device in a block chain system, and the method comprises the following steps:
determining target data from each synchronized data, wherein the synchronized data are data synchronized by the node equipment to the target node equipment, and the target node equipment and the node equipment have an association relationship;
determining at least one piece of data to be synchronized from unsynchronized data based on the target data and a target numerical value, wherein the target numerical value is used for indicating the data volume of the data to be synchronized obtained in one data synchronization process;
and sending the at least one piece of data to be synchronized to the target node equipment.
2. The method of claim 1, wherein determining the target data from the respective synchronized data comprises:
traversing a synchronous data list according to a target period, wherein the synchronous data list is used for recording the latest synchronous data in each data synchronization process;
and based on the synchronous data list, taking the latest synchronous data corresponding to the data synchronous process closest to the current time as the target data.
3. The method of claim 1, wherein determining at least one data to be synchronized from unsynchronized data based on the target data and a target value comprises:
determining at least one candidate data from the unsynchronized data based on the target data and the target value;
comparing the at least one candidate data with a data synchronization record of the target node device, and performing data deduplication on the at least one candidate data, wherein the data synchronization record is used for recording data synchronized in each data synchronization process and node identification of a data receiving node device;
determining the at least one candidate data after the de-duplication as the at least one data to be synchronized.
4. The method of claim 3, wherein determining at least one candidate data from the unsynchronized data based on the target data and the target value comprises:
determining a first storage location of the target data in a data list, wherein the data list stores at least one synchronized data and at least one unsynchronized data;
determining at least one second storage location in the data list based on the first storage location and the target value;
and acquiring the data stored in the at least one second storage position as the at least one candidate data.
5. The method of claim 3, wherein after the sending the at least one data to be synchronized to the target node device, the method further comprises:
and updating the data synchronization record of the target node equipment based on the node identification of the target node equipment and the at least one piece of data to be synchronized.
6. The method of claim 1, wherein prior to determining the target data from the synchronized data, the method further comprises:
responding to a data marking instruction of any data, and acquiring a global data identifier from a transaction pool, wherein the transaction pool is used for storing the any data;
and taking the global data identification as the data identification of any data.
7. The method of claim 6, wherein after the global data identifier is used as the data identifier of the any data, the method further comprises:
and storing the any data and the data identifier of the any data into a data list of the transaction pool based on the numerical value of the data identifier of the any data.
8. A data synchronization apparatus, applied to a node device in a blockchain system, the apparatus comprising:
a target data determination module, configured to determine target data from each synchronized data, where the synchronized data is data synchronized by the node device to a target node device, and the target node device and the node device have an association relationship;
a to-be-synchronized data determining module, configured to determine at least one to-be-synchronized data from unsynchronized data based on the target data and a target value, where the target value is used to indicate a data amount of the to-be-synchronized data obtained in a data synchronization process;
a sending module, configured to send the at least one piece of data to be synchronized to the target node device.
9. The apparatus of claim 8, wherein the target data determination module is configured to:
traversing a synchronous data list according to a target period, wherein the synchronous data list is used for recording the latest synchronous data in each data synchronization process;
and based on the synchronous data list, taking the latest synchronous data corresponding to the data synchronous process closest to the current time as the target data.
10. The apparatus of claim 8, wherein the means for determining data to be synchronized is configured to:
determining at least one candidate data from the unsynchronized data based on the target data and the target value;
comparing the at least one candidate data with a data synchronization record of the target node device, and performing data deduplication on the at least one candidate data, wherein the data synchronization record is used for recording data synchronized in each data synchronization process and node identification of a data receiving node device;
determining the at least one candidate data after the de-duplication as the at least one data to be synchronized.
11. The apparatus of claim 10, wherein the data to be synchronized determining module is configured to:
determining a first storage location of the target data in a data list, wherein the data list stores at least one synchronized data and at least one unsynchronized data;
determining at least one second storage location in the data list based on the first storage location and the target value;
and acquiring the data stored in the at least one second storage position as the at least one candidate data.
12. The apparatus of claim 10, further comprising:
and the updating module is used for updating the data synchronization record of the target node equipment based on the node identification of the target node equipment and the at least one piece of data to be synchronized.
13. The apparatus of claim 8, further comprising:
the identification acquisition module is used for responding to a data marking instruction of any data and acquiring a global data identification from a transaction pool, wherein the transaction pool is used for storing the any data;
and the identification determining module is used for taking the global data identification as the data identification of any data.
14. A computer device comprising one or more processors and one or more memories having at least one program code stored therein, the at least one program code loaded and executed by the one or more processors to perform operations performed by the data synchronization method of any one of claims 1 to 7.
15. A computer-readable storage medium having stored therein at least one program code, the at least one program code being loaded into and executed by a processor to perform operations performed by the data synchronization method of any one of claims 1 to 7.
CN202010015144.XA 2020-01-07 2020-01-07 Data synchronization method, device, equipment and storage medium Active CN111241115B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010015144.XA CN111241115B (en) 2020-01-07 2020-01-07 Data synchronization method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010015144.XA CN111241115B (en) 2020-01-07 2020-01-07 Data synchronization method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111241115A true CN111241115A (en) 2020-06-05
CN111241115B CN111241115B (en) 2022-02-22

Family

ID=70873009

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010015144.XA Active CN111241115B (en) 2020-01-07 2020-01-07 Data synchronization method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111241115B (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112231414A (en) * 2020-12-14 2021-01-15 腾讯科技(深圳)有限公司 Data synchronization method and device of block chain system, readable medium and electronic equipment
CN112291356A (en) * 2020-11-02 2021-01-29 大连理工大学 Self-verification variable name distributed storage method based on CNFS protocol
CN113282660A (en) * 2021-05-24 2021-08-20 挂号网(杭州)科技有限公司 Method and system for synchronizing data in cluster, electronic device and storage medium
CN114900538A (en) * 2022-03-28 2022-08-12 青岛海尔科技有限公司 Control method and device of intelligent mirror, storage medium and electronic device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554135A (en) * 2015-12-23 2016-05-04 北京奇虎科技有限公司 Method and device for synchronizing meta information among digital nodes
CN109634970A (en) * 2018-10-19 2019-04-16 平安科技(深圳)有限公司 Table method of data synchronization, equipment, storage medium and device
US20190146979A1 (en) * 2017-04-12 2019-05-16 Vijay Madisetti Method and System for Tuning Blockchain Scalability for Fast and Low-Cost Payment and Transaction Processing
CN110365768A (en) * 2019-07-15 2019-10-22 腾讯科技(深圳)有限公司 Method of data synchronization, device, medium, the electronic equipment of distributed system
CN110543448A (en) * 2019-07-22 2019-12-06 深圳壹账通智能科技有限公司 data synchronization method, device, equipment and computer readable storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554135A (en) * 2015-12-23 2016-05-04 北京奇虎科技有限公司 Method and device for synchronizing meta information among digital nodes
US20190146979A1 (en) * 2017-04-12 2019-05-16 Vijay Madisetti Method and System for Tuning Blockchain Scalability for Fast and Low-Cost Payment and Transaction Processing
CN109634970A (en) * 2018-10-19 2019-04-16 平安科技(深圳)有限公司 Table method of data synchronization, equipment, storage medium and device
CN110365768A (en) * 2019-07-15 2019-10-22 腾讯科技(深圳)有限公司 Method of data synchronization, device, medium, the electronic equipment of distributed system
CN110543448A (en) * 2019-07-22 2019-12-06 深圳壹账通智能科技有限公司 data synchronization method, device, equipment and computer readable storage medium

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112291356A (en) * 2020-11-02 2021-01-29 大连理工大学 Self-verification variable name distributed storage method based on CNFS protocol
CN112291356B (en) * 2020-11-02 2022-01-04 大连理工大学 Self-verification variable name distributed storage method based on CNFS protocol
CN112231414A (en) * 2020-12-14 2021-01-15 腾讯科技(深圳)有限公司 Data synchronization method and device of block chain system, readable medium and electronic equipment
CN112231414B (en) * 2020-12-14 2022-02-25 腾讯科技(深圳)有限公司 Data synchronization method and device of block chain system, readable medium and electronic equipment
CN113282660A (en) * 2021-05-24 2021-08-20 挂号网(杭州)科技有限公司 Method and system for synchronizing data in cluster, electronic device and storage medium
CN113282660B (en) * 2021-05-24 2023-05-23 挂号网(杭州)科技有限公司 Method and system for synchronizing data in cluster, electronic equipment and storage medium
CN114900538A (en) * 2022-03-28 2022-08-12 青岛海尔科技有限公司 Control method and device of intelligent mirror, storage medium and electronic device
CN114900538B (en) * 2022-03-28 2024-01-26 青岛海尔科技有限公司 Control method and device of intelligent mirror, storage medium and electronic device

Also Published As

Publication number Publication date
CN111241115B (en) 2022-02-22

Similar Documents

Publication Publication Date Title
CN111339086B (en) Block processing method, and data query method and device based on block chain
CN111245745B (en) Message sending method, device, node equipment and storage medium
CN111241115B (en) Data synchronization method, device, equipment and storage medium
CN110674022B (en) Behavior data acquisition method and device and storage medium
CN111340482B (en) Conflict detection method, device, node equipment and storage medium
CN108805560B (en) Numerical value integration method and device, electronic equipment and computer readable storage medium
CN110689460A (en) Traffic accident data processing method, device, equipment and medium based on block chain
CN110602206A (en) Data sharing method and device based on block chain and storage medium
CN110569220B (en) Game resource file display method and device, terminal and storage medium
CN111414598B (en) Monitoring method, device and equipment based on block chain and storage medium
CN110555780B (en) Insurance data processing method, device and equipment based on block chain and storage medium
CN110597924B (en) Block chain-based user identification processing method, device, equipment and storage medium
CN110598879A (en) Garbage recycling method, device and equipment based on block chain and storage medium
CN110826103A (en) Block chain-based document authority processing method, device, equipment and storage medium
CN111667371B (en) Resource aggregation method, system, device and storage medium based on block chain
CN111339181A (en) Block storage method, block storage device, node equipment and storage medium
CN110769050B (en) Data processing method, data processing system, computer device, and storage medium
CN110677262A (en) Block chain-based information notarization method, device and system
CN112084157A (en) File recovery method and device, computer equipment and storage medium
CN111881423A (en) Method, device and system for limiting function use authorization
CN110597840A (en) Partner relationship establishing method, device, equipment and storage medium based on block chain
CN112995587B (en) Electronic equipment monitoring method, system, computer equipment and storage medium
CN110971692B (en) Method and device for opening service and computer storage medium
CN111191254A (en) Access verification method and device, computer equipment and storage medium
CN112749583A (en) Face image grouping method and device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40024836

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant