CN110543788A - Data storage method, data storage device, computer-readable storage medium and computer equipment - Google Patents
Data storage method, data storage device, computer-readable storage medium and computer equipment Download PDFInfo
- Publication number
- CN110543788A CN110543788A CN201910859251.8A CN201910859251A CN110543788A CN 110543788 A CN110543788 A CN 110543788A CN 201910859251 A CN201910859251 A CN 201910859251A CN 110543788 A CN110543788 A CN 110543788A
- Authority
- CN
- China
- Prior art keywords
- transaction
- block
- node
- state
- data
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 66
- 238000013500 data storage Methods 0.000 title claims abstract description 62
- 238000012790 confirmation Methods 0.000 claims abstract description 73
- 238000012795 verification Methods 0.000 claims abstract description 51
- 238000012544 monitoring process Methods 0.000 claims abstract description 25
- 238000012545 processing Methods 0.000 claims description 74
- 238000004590 computer program Methods 0.000 claims description 11
- 230000002159 abnormal effect Effects 0.000 claims description 9
- 238000004140 cleaning Methods 0.000 claims description 5
- 238000012937 correction Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 14
- 230000001360 synchronised effect Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 10
- 230000005856 abnormality Effects 0.000 description 8
- 239000003795 chemical substances by application Substances 0.000 description 8
- 238000007726 management method Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000004422 calculation algorithm Methods 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000005201 scrubbing Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003862 health status Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012954 risk control Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2219—Large Object storage; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Finance (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a data storage method, a device, a computer readable storage medium and a computer device, wherein the method comprises the following steps: acquiring service data; the service data comprises a service identifier and transaction state information; monitoring business data and updating transaction state information; sending the service data to the full-scale nodes according to the service identification, so that the full-scale nodes generate the corresponding current blocks from the service data and perform consensus verification; receiving the verified blocks distributed by the full-volume nodes, and writing the verified blocks into the corresponding transaction table; updating the block writing state of the transaction table, and determining a transaction confirmation label by using the updated transaction state information and the block writing state; and deleting the service data in the cache when the block writing state and the transaction confirmation tag are both successfully written into the disk. The scheme provided by the application can effectively store the transaction state of the service request and can effectively ensure the accuracy and effectiveness of the transaction state.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data storage method and apparatus, a computer-readable storage medium, and a computer device.
Background
With the rapid development of computer technology, the block chain technology is gradually widely applied. The uniqueness of distributed storage of the blockchain is that each node of the blockchain stores complete data according to a blockchain structure. Currently, in a blockchain, a lightweight node corresponding to a consensus node is generally used to confirm a blockchain transaction, that is, payment can be verified without running a complete node, and only the block headers of all data blocks need to be saved. The lightweight node is connected with the full-scale node, and by inquiring the corresponding transaction from the blockchain network, the blockchain network can confirm that the transaction is approved and how many confirmations of the network are obtained.
However, when the node confirms the transaction, the related transaction is usually obtained by using a filter, and the transaction can be confirmed only after being packed into a block, and the transaction needs to be confirmed depending on the height of the block. For the transaction which is not packed into the block temporarily, the block and the transaction state may not be synchronous, and the situation of repeated payment is easy to occur, so that the validity of the transaction state and the transaction security cannot be guaranteed.
disclosure of Invention
Based on this, it is necessary to provide a data storage method, an apparatus, a computer-readable storage medium, and a computer device for solving the technical problem that the validity of the transaction state and the transaction security cannot be guaranteed due to the failure to accurately and effectively judge the transaction state.
A method of data storage, comprising:
Acquiring service data; the service data comprises a service identifier and transaction state information;
Monitoring the business data and updating the transaction state information;
Sending the service data to a full-scale node according to the service identification, and enabling the full-scale node to generate the service data into a corresponding current block and carry out consensus verification;
receiving the verified blocks distributed by the full-volume nodes, and writing the verified blocks into a corresponding transaction table;
Updating the block writing state of the transaction table, and determining a transaction confirmation label by using the updated transaction state information and the block writing state;
And deleting the service data in the cache when the block writing state and the transaction confirmation label are both successfully written into the disk.
a data storage device, characterized in that the device comprises:
The data acquisition module is used for acquiring service data; the service data comprises a service identifier and transaction state information;
the data monitoring module is used for monitoring the business data and updating the transaction state information;
The data sending module is used for sending the service data to a full-scale node according to the service identifier, so that the full-scale node generates the service data into a corresponding current block and performs consensus verification;
The data storage module is used for receiving the verified blocks distributed by the full-scale nodes and writing the verified blocks into a corresponding transaction table; updating the block writing state of the transaction table, and determining a transaction confirmation label by using the updated transaction state information and the block writing state;
and the cache cleaning module is used for deleting the service data in the cache when the block writing state and the transaction confirmation tag are both successfully written into the disk.
a computer-readable storage medium, in which a computer program is stored which, when executed by a processor, causes the processor to carry out the steps of the above-mentioned data storage method.
a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the data storage method described above.
According to the data storage method, the data storage device, the computer readable storage medium and the computer equipment, after the business data in the cache is obtained, the business data is monitored in real time, the transaction state information is updated, meanwhile, the business data is sent to the full nodes corresponding to the target block chain according to the business identification, the full nodes generate the current blocks of the business data, and the consensus verification is carried out on the current blocks. And receiving the verified blocks distributed by the full-volume nodes, writing the verified blocks into the corresponding transaction table so as to store the received verified blocks in real time, and updating the block writing state of the transaction table. The processing state in the process of processing the business data is continuously monitored, the transaction state information is updated in real time, whether the transaction state corresponding to the business data is successful or not can be respectively confirmed by using the updated transaction state information and the block writing state of the transaction table, a transaction confirmation label corresponding to the verified block is generated, when the block writing state and the transaction confirmation label are both successfully written into the disk, the transaction state is indicated to be successful, the received verified block is successfully stored, at the moment, the relevant business data in the cache can be deleted, and the cache occupation is reduced. By respectively storing the transaction state information and the received verified block in real time and respectively confirming the transaction state according to the transaction state information and the block writing state, whether the edge node receives the verified block or not can be judged according to the transaction state information locally stored by the edge node, so that the current transaction state can be effectively ensured to be accurate and effective, the condition of repeated payment caused by uncertain transaction state can be effectively prevented, and the transaction safety is effectively improved.
Drawings
FIG. 1 is a diagram of an exemplary data storage system;
FIG. 2 is a block diagram of a blockchain business system in accordance with an embodiment;
FIG. 3 is a schematic flow chart diagram illustrating a data storage method in one embodiment;
FIG. 4 is a schematic flow chart diagram illustrating the step of monitoring the status of a transaction in one embodiment;
FIG. 5 is a flow chart illustrating a data storage method according to an exemplary embodiment;
FIG. 6 is a timing diagram of a data storage method in one embodiment;
FIG. 7 is a block diagram of a data storage device in one embodiment;
FIG. 8 is a block diagram of a data storage device in another embodiment;
FIG. 9 is a block diagram of a data storage device in another embodiment;
FIG. 10 is a block diagram showing a configuration of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
FIG. 1 is a diagram of an application environment of a data storage method in one embodiment. Referring to fig. 1, the data storage method is applied to a data storage system, wherein the data storage system may be a blockchain business system based on a blockchain technology. The data storage system includes a terminal 110 and a blockchain business system 120, the blockchain business system 120 being a computer node deployed in a blockchain network. The terminal 110 and the blockchain service system 120 communicate over a network. The terminal 110 may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The blockchain business system 120 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.
In one embodiment, referring to fig. 2, the blockchain business system 120 includes multiple levels of nodes: edge node 1202, proxy node 1204, consensus node 1206. Each consensus node can also be deployed with a corresponding accounting node. The nodes in the entire blockchain service system can be represented as blockchain nodes, and each node can be provided as a server. The edge node 1202 may be a computer node deployed by an authority in a first hierarchy, and the first hierarchy may be an application service layer in the blockchain service system, such as a computer node deployed by each service provider. The edge node 1202 may be the node closest to the user terminal side connected to the service participant terminal 110 and the respective blockchain nodes. The agent node 1204 may be a second tier of an authority-deployed computer node, and the second tier may be a platform product service tier in a blockchain business system, such as a provincial-deployed computer node. The consensus nodes 1206 may be computer nodes of a third tier of respective authority deployments, and the third tier may be a blockchain underlying platform in a blockchain business system, such as computer nodes of national and provincial organizations deployments. Each edge node 1202, proxy node 1204, and consensus node 1206 has a corresponding service area. Each edge node 1202 is directly connected to the proxy nodes 1204 within its serving area through the network, or indirectly connected to the proxy nodes 1204 within the corresponding serving area through other edge nodes 1202. The edge node 1202 may be configured to receive a service request initiated by a service participant terminal, and distribute a request packet to a corresponding node in the blockchain service system according to a service attribute.
The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a 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 consensus on the valid request is completed, 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 service information to a shared account (network communication) completely and consistently after encryption, and performs recording and storage; 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.
as shown in FIG. 3, in one embodiment, a method of data storage is provided. This embodiment is mainly illustrated by applying the method to the edge node 1202 in the blockchain 120 in fig. 2. Referring to fig. 3, the data storage method specifically includes the following steps:
step 302, acquiring service data; the service data includes service identification and transaction state information.
In a service system based on a block chain, a plurality of block chains may be deployed in advance according to service types, each block chain has a corresponding service type, and the same service type may also correspond to a plurality of block chains. Each blockchain may have a corresponding blockchain identification. The terminal can install corresponding service application for the terminal to initiate service request of corresponding service type. The service system based on the block chain comprises a plurality of nodes, and each node can correspondingly process the received service data. A blockchain node may be a deployed server that establishes connections with multiple blockchains and with multiple terminals. In this embodiment, the data storage method is applied to a data storage system, and the data storage system may be a service system based on a block chain. The business system can be a public chain system, a private chain system or a alliance chain system.
the edge node is a computer node with lower safety and reliability in the blockchain system compared with a full-volume node of a core, and the edge node can be a light-weight node relative to the full-volume node, can provide functions of transaction and query, but does not have full-volume transaction information. The full-volume node is a computer node used for storing full-volume data files and has high safety and reliability.
A quantum node refers to a computer node in a blockchain system that is critical to ensuring data reliability. The full-scale nodes can be reliable nodes in the blockchain system, and the full-scale nodes can comprise agent nodes, consensus nodes, accounting nodes and the like. The full-quantity nodes are used as core nodes in the blockchain system, and have higher requirements on the hardware performance of the computer and the network environment. In the embodiment, in a federation chain scenario, in order to ensure the requirements of security and performance, only a few authority members may deploy reliable nodes. For example, in the above electronic invoice scenario, only the national tax administration may deploy reliable nodes; in the above copyright evidence scenario, only the national copyright center may deploy reliable nodes. The computer nodes deployed by the authority have higher capability of preventing malicious attack intrusion, and can ensure smaller probability of computer performance failure, so that the computer nodes can be regarded as full-scale nodes.
The service data may be in various forms, for example, a service request initiated by a terminal to a certain service, a confirmation request of a user to a certain service, a data read-write operation of a user for a certain service, and the like. For example, in a transaction scenario, the business data may be transaction data, such as an electronic invoice or the like. The service data includes a service identifier and transaction state information, and the transaction state information may be initial transaction state information of the service data, for example, the initial transaction state information may be a pending state.
For example, when the service data is sent by the terminal based on the service request, the terminal may be installed with a service application corresponding to the service system, and the user may initiate a corresponding service request through the service application on the terminal. And the edge node receives the service request waiting sent by the terminal, and stores the service data carried by the service request into a cache. The service request carries a corresponding service identifier, and the edge node firstly performs signature verification and authority verification on the service request.
specifically, the service data further includes signature information, and after receiving the service request, the edge node acquires pre-stored key information corresponding to the user identifier, and verifies the signature information of the service data by using the key information. Specifically, the edge node may analyze the corresponding signature by using the user public key to obtain digest information, calculate the digest information of the data packet according to a preset algorithm, match the two digest information, and determine that the signature verification passes if the matching is successful. After the signature verification is passed, the edge node may further obtain a corresponding blockchain identifier according to the service identifier carried in the service request, where there may be a plurality of blockchains corresponding to the service type. And the edge node respectively performs hash calculation according to the service type and the service identifier and the plurality of block chains to obtain a corresponding hash result set, and when a target block chain identifier corresponding to the service data exists in the hash result set, the edge node indicates that the target block chain has access authority.
When both the signature verification and the authority verification of the service request pass, performing step 304; if any one of the signature verification and the authority verification fails, the service request verification is determined to fail, which indicates that the service request has malicious attack or the service data has a risk of malicious tampering, and the edge node can intercept the service request and the service data.
The edge node can also directly acquire service data in the cache, and the service data in the cache can be the service data stored in the cache after receiving the service data sent by the terminal; and the service data can be acquired from other service platforms and stored in the cache.
Step 304, monitoring the service data and updating the transaction state information.
the transaction state information may indicate a real-time transaction state of the service request, and when the transaction is in different stages and periods, the corresponding transaction state information is different, for example, the transaction state includes various state information such as pending, in-process, in-consensus, and successful transaction, and includes detailed transaction information.
And when the edge node sends the service data corresponding to the service request to the full-amount node corresponding to the target block chain identifier, monitoring the transaction state of the service data of the service request. Specifically, when the service data is not sent to the full-scale node, the transaction state of the service data may be directly identified, for example, the transaction state of the current service data may be undistributed, unprocessed, and pending state information. And the edge node monitors the processing state of the service data in real time and updates the transaction state information in real time according to the processing state.
and step 306, sending the service data to the full-scale nodes according to the service identification, so that the full-scale nodes generate the corresponding current blocks from the service data and perform consensus verification.
Wherein the light-weight nodes are edge nodes connected with the full-scale nodes. The full-scale node may be deployed in plurality. For example, in the electronic invoice scenario, full-volume nodes may be respectively deployed in several data centers distributed nationwide by the national tax administration. The multiple full-quantity nodes are connected pairwise through a network. Each full-scale node is connected with a plurality of edge nodes nearby through a network. When a plurality of full-scale nodes are deployed, the edge node may preferentially send the service data to the full-scale node with the closest position. The full-scale nodes receiving the service data broadcast the corresponding blocks to other full-scale nodes, and each full-scale node distributes the blocks to the edge nodes according to the mode.
The block is a data packet carrying transaction data on a blockchain network, and is a container data structure marked with a time stamp and a hash value of the previous block, and the block verifies and confirms the transaction in the block through a consensus mechanism of the network. The block includes a block head and a block body. The block header records the time stamp of the previous sequential block and the time stamp of the current data block. The block also includes a block height, which is the number of blocks linked in the main chain, i.e., the number of blocks connected in the block chain. The block height may be a block identifier, and the block identifier may include a plurality of identifiers, such as a hash value of a block header, and may also include a block height, where each block has an explicit and fixed block height. The block book is a carrier for recording data to be stored and certified generated in a period of time, and records information of a plurality of data blocks. The plurality of data blocks are connected in series in the block book in the order of generation time.
And after determining the corresponding target block chain identification from the plurality of block chains according to the service identification, the edge node sends the service data corresponding to the service request to the full-scale node corresponding to the target block chain identification, so that the full-scale node generates the corresponding current block from the service data, and the consensus node in the full-scale node performs consensus verification on the generated current block. And after the consensus verification is passed, the full-scale node writes the current block into the corresponding block account book, broadcasts the current block to other accounting nodes of the target block chain, and synchronously distributes the current block to the light-weight nodes so that the light-weight nodes perform backup storage on the current block.
In one embodiment, after the edge node obtains the service data, the corresponding target test chain identifier is determined from the plurality of block chains according to the service identifier, and then the corresponding current block is generated according to the service data. Specifically, the edge node may obtain block header information of a previous block associated with the current block in the target mode chain, generate the current block according to the block header information of the previous block, and write the service data into the current block. When the current block is generated, the characteristic value of the current block can be generated according to the block header information of the previous block, and specifically, multiple hash algorithms can be adopted for parallel calculation, so that the characteristic value of the current block is obtained. And the edge node further generates a current block of the service data according to the information such as the block characteristic value, the service data, the signature information, the block header characteristic value of the previous block, the time stamp and the like. And after the edge node generates the current block corresponding to the service data, distributing the current block to a plurality of full-scale nodes corresponding to the target block chain identification. And after the consensus node in the full amount of nodes obtains the current block, performing consensus verification on the current block. And after the consensus verification is passed, broadcasting the current block in the target block chain and writing the current block into a block account book.
After the edge node distributes the service data to the full-scale nodes, the processing state of the full-scale nodes to the service data can be acquired in real time. For example, when the full-scale node generates a corresponding current block according to the service data, the edge node may acquire, from the full-scale node, transaction state information that the service data is in block generation; when the full-scale node performs consensus on the current block, the edge node can acquire the transaction state information of the service data in the consensus from the full-scale node; after the full-scale node passes the current block consensus verification and is written into the block ledger of the consensus node, the service request is shown to be successful in transaction, and the edge node can acquire the transaction state information that the service data is successful in transaction from the full-scale node.
The edge node generates corresponding transaction state information according to the transaction state acquired in real time, for example, the transaction state of the transaction state information may also be modified according to the current state acquired in real time. And the edge node caches the transaction state information in real time.
Step 308, receiving the verified blocks distributed by the full-scale nodes, and writing the verified blocks into the corresponding transaction table; and updating the block writing state of the transaction table, and determining the transaction confirmation tag by using the updated transaction state information and the block writing state.
the target block chain also comprises a corresponding transaction table, each node in the target block chain stores the corresponding transaction table, and the transaction table is used for storing transaction record data consisting of transaction input and transaction output.
And after the total node passes the current block consensus verification, the total node writes the current block into a corresponding block account book, broadcasts the current block to other accounting nodes of the target block chain, and then synchronously distributes the current block to a plurality of light weight nodes. And the edge node receives the current block distributed by the full-scale node in real time. Wherein, the block comprises a block head and a block body. The full-scale nodes can distribute the verified blocks to the edge nodes through the proxy nodes, and the proxy nodes can only forward the block head parts of the verified blocks to the edge nodes when distributing the verified blocks to the edge nodes. And when the edge node receives the block head of the verified block distributed by the proxy node, storing the block head of the verified block. Specifically, the edge node acquires a transaction table corresponding to the target block chain identifier, and writes transaction data of the verified block into a transaction, so as to store the verified block.
Wherein the generation of transaction state information by the edge node and the receipt of the verified block distributed by the quorum node may be asynchronous. And the edge node respectively stores the generated transaction state information and the received verified block in real time.
and after the edge node writes the verified transaction data of the block into the transaction table, updating the block writing state in the corresponding transaction table. When the verified block is to be stored, the transaction data corresponding to the block is written into the transaction table, the writing completion indicates that the current block is successfully stored, and the block writing state of the transaction table is block writing success.
After the edge node respectively stores the generated transaction state information and the received verified block in real time, whether the transaction state of the service data is successful or not can be determined according to the transaction state information and the block writing state of the transaction table. Specifically, when the state in the transaction state information is that the transaction is successful, it is determined that the transaction state of the service data is successful, and a corresponding transaction confirmation tag is generated and stored. And when the block writing state of the transaction table is that the block writing is successful, adding a transaction confirmation label with successful transaction to the service request. That is, as long as the edge node receives transaction state information of successful transaction arbitrarily, or detects that the block writing state of the transaction table is block writing success, that is, the transaction is successful at this time, the edge node generates and stores a transaction confirmation tag. The edge node may store both the transaction confirmation tag and the transaction table in a local disk.
In step 310, when both the block write status and the transaction confirmation tag are successfully written into the disk, the service data in the cache is deleted.
The cache of the edge node stores service data and related cache information generated in the process of processing the service data, and the cache information may include transaction state information for monitoring the transaction state of the service data, processing information for the service data, and other data. And the edge node stores the generated transaction confirmation label and the obtained verified block into a local disk, and after the transaction confirmation label and the verified block are both stored into the disk, the block writing state and the transaction confirmation label are both successfully written into the disk.
And when the block writing state and the transaction confirmation tag are both successfully written, the transaction state of the service data is indicated as successful transaction. The edge node may delete the relevant service data in the cache.
Because the block chain is a factor of a P2P (Peer-To-Peer) propagation mode and common node storage, two possibilities exist for the transaction state in the cache of the edge node, if the transaction state information acquired by the edge node is successfully returned first, i.e. the transaction is successfully confirmed according To the transaction state information, the transaction state in the cache is changed into a successful state and a transaction confirmation label is generated, and at the moment, the cache information in the cache can be deleted only when the verified block is synchronized To the edge node transaction; in another case, the verified block is synchronized to the edge node first, the transaction state is changed into a block write-in success state, the transaction success can be confirmed according to the block write-in state of the transaction table, and a transaction confirmation tag is generated, and at this time, the cache information is deleted from the cache until the transaction state information of the transaction response success is acquired.
The edge node can effectively and timely acquire the transaction state of the service data by updating the transaction state information of the service data in real time. The generated transaction state information and the received verified block are respectively stored in real time, and whether the transaction of the service data is successful or not is respectively confirmed according to the transaction state information and the block writing state. Therefore, whether the edge node receives the verified block distributed by the full node or not can judge the transaction state of the service data according to the transaction state information stored locally, so that the current transaction state can be effectively ensured to be accurate and effective, and the condition of repeated payment caused by uncertain transaction states can be effectively prevented. When the block writing state and the transaction confirmation label are both successfully written, the transaction state can be completely ensured to be a successful state and the block is successfully stored, and the transaction state information in the edge node cache can be deleted at the moment, so that the resource occupation of the edge node is reduced.
In this embodiment, after the edge node acquires the service data in the cache, the service data is monitored in real time, the transaction state information is updated, and meanwhile, the service data is sent to the full-scale nodes corresponding to the target block chain according to the service identifier, so that the full-scale nodes generate the current block of the service data, and perform consensus verification on the current block. And receiving the verified blocks distributed by the full-volume nodes, writing the verified blocks into the corresponding transaction table so as to store the received verified blocks in real time, and updating the block writing state of the transaction table. The processing state in the process of processing the business data is continuously monitored, the transaction state information is updated in real time, whether the transaction state corresponding to the business data is successful or not can be respectively confirmed by using the updated transaction state information and the block writing state of the transaction table, a transaction confirmation label corresponding to the verified block is generated, when the block writing state and the transaction confirmation label are both successfully written into the disk, the transaction state is indicated to be successful, the received verified block is successfully stored, at the moment, the business data in the cache can be deleted, and the cache occupation is reduced. By respectively storing the transaction state information and the received verified block in real time and respectively confirming the transaction state according to the transaction state information and the block writing state, whether the edge node receives the verified block or not can be judged according to the transaction state information locally stored by the edge node, so that the current transaction state can be effectively ensured to be accurate and effective, the condition of repeated payment caused by uncertain transaction state can be effectively prevented, and the transaction safety is effectively improved.
in one embodiment, the verified block includes a block header, the quantum node includes a consensus node, an accounting node, and a proxy node, the quantum node is configured to return a processing state and generate the current block, the consensus node is configured to perform consensus verification on the current block, the consensus node, the accounting node, and the proxy node are all configured to write the verified block into a block account, and the proxy node is configured to synchronously distribute the block header of the verified block to the edge node.
The block chain business system can comprise a light weight node and a full volume node, the light weight node can comprise an edge node, the full volume node comprises a consensus node, an accounting node and a proxy node, and the light weight node and the full volume node can be respectively deployed in a plurality. For example, in the electronic invoice scenario, a consensus node and a billing node may be respectively deployed in several data centers distributed nationwide by the national tax administration, an agency node may be respectively deployed in each provincial tax administration nationwide, and an edge node may be deployed in each municipal tax administration nationwide and a service provider. A facilitator refers to an entity that has the authority to issue electronic invoices. The light-weight nodes are connected with the full-quantity nodes through a network, and all the nodes between the full-quantity nodes are connected pairwise through the network.
The edge node refers to a computer node with lower security and reliability in the blockchain system compared with a full-scale node of the core, and the edge node may be a lightweight node compared with the full-scale node. The edge node may be a lightweight node (rightweight nodes), for example, the edge node may be an SPV (simple Payment Verification) node, and the SPV node is a lightweight node relative to a consensus node, and may provide functions of transaction and query, but does not have full transaction information, that is, the SPV node does not need to store data of the whole block chain, and only stores partial data related to itself that needs to be verified, so that storage resources may be saved. SPV nodes may be nodes that support the use of Bloom filters (Bloom filters) to quickly retrieve and return relevant data. In order to simplify payment verification, an SPV node is deployed in a block chain service system and is responsible for judging whether the transaction is authenticated by the node consensus of the block chain and confirming for many times, and the transaction can be verified without backing up all data.
the full-volume node is a computer node used for storing a full-volume data file, has high safety and reliability, and can be a reliable node in a block chain system. The SPV nodes can pull the block headers of the related blocks to the proxy nodes, and the block headers can be synchronized among the SPV nodes.
Specifically, the full-scale node may return a processing state in a process of processing the service data to the lightweight node in real time, and any one of the full-scale nodes may generate a corresponding current block according to the service data. After the total node generates the current block, the consensus node in the total node performs consensus verification on the generated current block, after the gear consensus verification passes, the verified block is broadcasted in a target block chain and written into a block account book, after the accounting node and the proxy node receive the broadcasted verified block, the verified block is written into the block account book, and the proxy node synchronously distributes the block head part of the verified block to the edge node. Because the edge node is a lightweight node relative to the full number of nodes, the data of the whole block chain does not need to be stored, only partial data of the block head of the verified block can be stored, the storage resource can be effectively saved, and the validity of the transaction data is ensured.
in one embodiment, as shown in fig. 4, monitoring the service data and updating the transaction status information specifically includes the following steps:
Step 402, tracing the node flow of the service data.
And step 404, detecting the processing state of the full node on the service data, and updating the transaction state information according to the processing state.
Step 406, when it is detected that the consensus node in the full amount of nodes performs consensus on the current block of the service data, generating a transaction confirmation label corresponding to the verified block.
the edge nodes and the full-scale nodes are connected through a network, and the node flow direction can indicate to which node the service data flows and which node the service data is currently located. After receiving the service data sent by the edge node, the full-scale node can feed back the processing state of the service data to the edge node in real time.
and after receiving the service request and determining the corresponding target block chain identification according to the service identification in the service request, the edge node distributes the service data to the full nodes corresponding to the target block chain, and the edge node tracks the node flow direction of the service data in real time according to the service identification. The edge node can route the transaction request corresponding to the service data to the consensus node through the proxy node, so that the consensus node generates a corresponding current block for the service data, and performs consensus verification on the current block.
Specifically, when the edge node receives the service request, it may generate the transaction state information of the service data and add a corresponding timestamp, and store the generated transaction state information in a local cache of the edge node. Meanwhile, the edge node tracks the node flow direction corresponding to the service data of the service request in real time. The edge node can forward the service data to the common node through the agent node in the full-scale nodes, and after the agent node acquires the service data, the edge node can feed back the processing state information of the received service data to the edge node according to the data transmission path. When the consensus node receives the service data forwarded by the proxy node, the received processing state can be fed back to the edge node through the forwarding path, and when the consensus node generates a corresponding block from the service data and performs consensus verification on the current block, the processing state in consensus is fed back to the edge node. And when the consensus node passes the consensus verification of the current block, feeding back a processing state of consensus completion or successful transaction to the edge node.
The edge node can detect the processing state of the corresponding node to the service data in real time according to the feedback condition of each node in the full-quantity nodes to the service data. After the edge node acquires the processing state fed back by the proxy node or the consensus node each time, the processing state acquired in real time is updated to the transaction state information, for example, the processing state acquired in real time can be newly added to the transaction state information according to the current timestamp, so that the transaction state of the service data can be effectively recorded in the local cache of the edge node in real time.
when the consensus node is detected to complete the consensus of the current block of the service data, the trade state corresponding to the service data is shown to be successful, the edge node updates the successful trade state into the trade state information, and a trade confirmation label corresponding to the verified block is generated. The transaction confirmation tag may be stored in a database of the disk of the edge node. And the edge node receives the current block forwarded by the proxy node and stores the current block, and deletes the transaction state information in the cache of the edge node when the write-in state of the block and the transaction confirmation tag are both successfully written in, wherein the transaction confirmation tag is not deleted when the transaction state information in the cache is deleted by the edge node.
In this embodiment, the edge node tracks the node flow direction of the service data, detects the processing state of the corresponding node on the service data in real time, and updates the transaction state information according to the processing state, so that the transaction state corresponding to the service request can be effectively cached at the edge node, and whether the edge node receives the verified block distributed by the full number of nodes or not, the transaction state of the service data can be judged according to the transaction state information locally stored by the edge node, so that the validity of the current transaction state can be effectively ensured.
In one embodiment, receiving verified blocks distributed by the full-scale nodes, and writing the verified blocks into the corresponding transaction table includes: receiving verified block headers distributed by the full-scale nodes; acquiring a transaction table corresponding to the block, and writing transaction data of the block head into the transaction table; and when the transaction data of the block header is detected to be written into the transaction table, updating the block writing state of the transaction table into a writing success state.
the edge nodes and the full-scale nodes are connected through a network, wherein the edge nodes can be directly connected with the agent nodes in the full-scale nodes, and all the nodes between the full-scale nodes are connected pairwise through the network. The current tile includes a tile header and a tile body. The transaction table is used for storing transaction record data consisting of transaction input and transaction output. For example, the data structure of the UTXO (Unspent Transaction Output) model, which is a part of the Transaction input and Output, may be used to store specific Transaction data, and which may be the most basic component of a Transaction.
After the edge node sends the full-scale nodes corresponding to the target block chain according to the service identification, the consensus node in the full-scale nodes generates a corresponding current block according to the service data, and performs consensus verification on the current block. After the verification is passed, the common identification node writes the verified blocks into the block account book and broadcasts the blocks in the target block chain, so that each node in the target block chain respectively writes the received verified blocks into the respective block account book. And after the proxy node in the target block chain receives the verified block, extracting the block head part of the verified block, and synchronously distributing the block head part of the verified block to a plurality of edge nodes.
And the edge node acquires the block head of the verified block distributed by the connected proxy node in real time and stores the block head. Specifically, when the edge node stores the verified block, the transaction table corresponding to the target block chain identifier is obtained according to the verified block, and the transaction table is used for storing specific transaction data. The edge node stores the acquired block header, that is, the edge node writes the acquired transaction data of the block header into the transaction table, so as to update the current block into the corresponding transaction table. Wherein the transaction table is stored in a disk of the edge node. The edge node can also detect the block writing state of the transaction table in real time, and when the transaction data of the block head is detected to be written into the transaction table, the verified block is successfully written into the disk. At this time, the edge node updates the block writing state of the transaction table to a block writing success state.
in the embodiment, the transaction state can be timely and effectively determined by detecting the block writing state of the transaction table, so that the accuracy and consistency of the current transaction state can be effectively ensured. When the edge node stores the verified block corresponding to the service data, only the block head part of the block needs to be stored, and when the data verification, the query and other processing are realized, the data storage cost can be reduced, and meanwhile, the consistency and the effectiveness of the transaction data are ensured.
In one embodiment, the method further comprises: if a processing state of successful transaction returned by the full-volume node is received, updating transaction state information according to the processing state, and generating a transaction confirmation label corresponding to the verified block; when receiving the verified blocks distributed by the full-volume nodes, writing the verified blocks into the corresponding transaction table and updating the block writing state; and deleting the service data in the cache when the block writing state and the transaction confirmation tag are both successfully written into the disk.
When the consensus node in the full-amount node passes the current block consensus verification corresponding to the generated service data, the transaction state corresponding to the service request is a successful transaction processing state. The transaction confirmation tag may represent an identifier that the transaction status corresponding to the service request has been successful.
After the edge node acquires the service request, the edge node starts to monitor the processing state of the service request in real time. And the edge nodes simultaneously transmit the service data to the full-scale nodes corresponding to the target block chain according to the service identification, so that the full-scale nodes generate current blocks of the service data, the current blocks are subjected to consensus verification, and after the verification is passed, the full-scale nodes synchronously distribute the verified blocks to a plurality of edge nodes. After the consensus node passes the consensus verification of the current block, the processing state of successful transaction is returned to the edge node through the proxy node.
At this point, the processing state of the edge node to receive the transaction success and the time of the receiving agent node to distribute the verified tile may not be synchronized. The edge node monitors the processing state of the service request and waits for receiving the block after the distribution verification of the connected proxy node.
Specifically, if the edge node receives the processing state of successful transaction returned by the full-volume node first, the transaction state information is updated according to the processing state, the transaction state information at this time already indicates that the transaction is successful, and the edge node generates a transaction confirmation tag corresponding to the verified block and stores the transaction confirmation tag. At this time, if the terminal initiates a transaction query request of the service request to the edge node, confirmation information of successful transaction can be returned to the terminal.
If the terminal initiates a transaction query request of the service request to the edge node during the period that the edge node does not receive the processing state of successful transaction nor the block after the distribution verification of the connected node, the edge node returns corresponding current transaction state information to the terminal according to the current transaction state information stored in the cache.
And when the edge node subsequently receives the verified block distributed by the connected proxy node, storing the verified block. Specifically, the edge node updates the block writing state in the corresponding transaction table according to the verified block. That is, when the verified block is stored, the transaction data corresponding to the verified block is written in the transaction table, for example, a block header can be written. And the write completion indicates that the block is successfully stored, and the transaction table and the write state in the block write updating process are updated to be in a write success state. And when the block writing state is that the block writing is successful and the transaction confirmation tag is generated, indicating that both the block writing state and the transaction confirmation tag are successfully written into the disk, and deleting the service data in the cache by the edge node.
in this embodiment, the received processing state and the verified block distributed by the connected node are stored in real time, so that the transaction state corresponding to the service request can be effectively cached and determined at the edge node, and the transaction state of the service data can be judged according to the transaction state information locally stored at the edge node no matter whether the edge node receives the verified block. Therefore, the accuracy and the effectiveness of the current transaction state can be effectively ensured, the situation of repeated payment caused by uncertain transaction states can be effectively prevented, and the security of the transaction is effectively guaranteed.
In one embodiment, the method further comprises: if the verified blocks distributed by the full amount nodes are received first, writing the verified blocks into the corresponding transaction table and updating the block writing state to generate transaction confirmation labels corresponding to the verified blocks; when a processing state of successful transaction returned by the full-volume node is received, updating transaction state information according to the processing state; and deleting the service data in the cache when the block writing state, the transaction confirmation tag and the transaction success state are all successfully written into the disk.
after the edge node acquires the service request, the edge node starts to monitor the processing state of the service request in real time. And the edge nodes simultaneously transmit the service data to the full-scale nodes corresponding to the target block chain according to the service identification, so that the full-scale nodes generate current blocks of the service data, the current blocks are subjected to consensus verification, and after the verification is passed, the full-scale nodes synchronously distribute the verified blocks to a plurality of edge nodes. The edge node monitors the processing state of the service request in real time and waits for receiving the verified blocks distributed by the connected proxy nodes.
the time for the edge node to receive the processing status of the transaction success and the verified block distributed by the receiving agent node may not be synchronized. Specifically, if the edge node receives the verified block distributed by the connected node first, it indicates that the service request at this time has been successfully transacted. And the edge node writes the verified block into the corresponding transaction table and updates the block writing state for storage, and the writing completion indicates that the block is successfully stored, and updates the writing state in the transaction table and the block writing update into the writing success state. And the edge node generates a transaction confirmation label corresponding to the verified block and stores the transaction confirmation label. If the terminal initiates a transaction query request of the service request to the edge node at this time, confirmation information of successful transaction can be returned to the terminal.
If the terminal initiates a transaction query request of the service request to the edge node during the period that the edge node does not receive the verified block distributed by the connected node or the processing state of successful transaction, the edge node returns corresponding current transaction state information to the terminal according to the current transaction state information stored in the cache.
and when the edge node subsequently receives the transaction successful processing state returned by the full-volume node, updating the transaction state information according to the processing state, and determining the current transaction state information as the transaction successful state. The edge node can also store the state identifier corresponding to the transaction success state. And when the block writing state is that the block writing is successful and the transaction confirmation tag is generated, indicating that both the block writing state and the transaction confirmation tag are successfully written into the disk, and deleting the service data in the cache by the edge node.
The received processing state and the current block distributed by the connected node are respectively stored in real time, so that the transaction state corresponding to the service request can be effectively cached and determined at the edge node, and the transaction state of the service request can be judged according to the transaction state information locally stored at the edge node no matter whether the edge node receives the current block or not. Therefore, the accuracy and the effectiveness of the current transaction state can be effectively ensured, the condition of repeated payment caused by uncertain transaction state can be effectively prevented, and the security of transaction is effectively guaranteed.
In one embodiment, the method further comprises: receiving the verified blocks distributed by the full-volume nodes, and writing the blocks into the corresponding transaction table; establishing connection with the full-scale nodes according to a preset time frequency; synchronizing the verified blocks from the connected full-scale nodes; and checking the stored blocks according to the blocks obtained by synchronization.
The connected node of the edge node refers to a computer node connected with the edge node through a network. There may be one or more connected nodes of the edge node. The connected nodes may be full-scale nodes or other edge nodes, and may also be proxy nodes in the full-scale nodes. When the connected node comprises a proxy node, it means that the edge node and the proxy node are directly connected through the network, that is, a connection channel exists between the edge node and the proxy node. The agent node stores a block account book corresponding to the target block chain and a complete block.
After the edge nodes acquire the service data, the service data are sent to the full-scale nodes corresponding to the target block chain according to the service identification, so that the full-scale nodes generate current blocks of the service data and perform consensus verification on the current blocks, and after the verification is passed, the full-scale nodes synchronously distribute the verified blocks to a plurality of edge nodes. The edge node also monitors the processing state of the service data in real time and updates the transaction state information in real time according to the processing state. And after receiving the verified block, the edge node stores the block in real time and updates the block writing state.
After the edge node receives and stores the verified block forwarded by the connected node, the edge node can further establish connection with the full-scale nodes according to the preset time frequency. Specifically, the time frequency for establishing a connection channel with the full-scale node is preset for each edge node. The edge node determines whether a connection channel exists between the edge node and the starting node according to a preset time frequency. If not, the edge node sends a connection request to the full-scale node so as to establish a connection channel with the full-scale node.
after the edge node establishes the connection channel with the full-scale node, the edge node may further send a data synchronization request to the full-scale node, so as to synchronize the corresponding blocks from the full-scale node. The data synchronization request carries the node identification of the edge node. A node identification is information that can uniquely identify a computer node, such as an IP address. And the full-amount node acquires the block related to the corresponding edge node according to the node identifier and synchronizes the block to the corresponding edge node.
The blocks synchronized from the full-scale nodes can be regarded as accurate and reliable on the high confidence level, and the edge nodes can also obtain the related blocks generated in the current correction period from the full-scale nodes. The edge nodes compare the corresponding verified blocks synchronized from the full-scale nodes, and check whether the block heights of the blocks acquired from the full-scale nodes or other edge nodes are consistent, whether the time stamps contained in the block heads of the blocks are consistent, and the like. If the block height of each block and the time stamp included in the block header are consistent, the checking result is that the data is normal, and the block corresponding to the service data stored in the edge node can be considered to be not maliciously tampered, so that the method is safe and reliable. When the block height of the block or the time stamps contained in the block head are inconsistent, the checking result is a data exception, which indicates that the block stored by the edge node is at risk of being tampered maliciously. The reliability of the blocks stored in the edge nodes can be effectively improved by checking the blocks stored in the edge nodes according to the blocks pulled from the data source.
In one example, the method further comprises: when the correction result is data abnormity, deleting the transaction data of the abnormal block in the transaction table; and rewriting the transaction data of the blocks synchronously obtained from the full-scale nodes into the transaction table.
The block ledger in the edge node records information of a plurality of blocks related to the edge node, and the block ledger may be a transaction table stored in the edge node. And when the check result is data abnormity, the risk that the edge node is maliciously tampered is shown. The edge node stops pulling the current block from the full-scale node or other edge nodes, deletes the transaction data recorded in the block book of the edge node, wherein the block book is local and has abnormal blocks, and pulls the corresponding verified block from the full-scale node again when a connection channel between the edge node and the full-scale node is established, so that the verified block corresponding to the local abnormal block is synchronized from the full-scale node. And the edge node rewrites the transaction data of the synchronously obtained block into the transaction table based on the block synchronized from the full node, thereby rewriting and updating the abnormal block. The block stored in the edge node is periodically checked, and block account book data is timely rewritten and updated when the check is abnormal, so that the reliability of the block stored on the edge node is improved.
In one implementation, when the data abnormality is found in the calibration result, an abnormality alarm is generated based on the block with the data abnormality, and the abnormality alarm is sent to the monitoring terminal. Monitoring personnel can access the corresponding edge nodes through the monitoring terminal, clear all blocks in the edge nodes, and rewrite the transaction data of the synchronously obtained blocks into a transaction table so as to rebuild the corresponding block accounts book, thereby recovering abnormal data.
in one implementation, when the result of the correction is data abnormality, the edge node may replace the stored block with data abnormality based on the block synchronously obtained from the reliable node, so as to periodically update and correct the block ledger. In other words, when data abnormality is found, only a block in which abnormality exists may be deleted.
in one embodiment, the method further comprises: receiving a transaction query request sent by a terminal, wherein the transaction query request carries a transaction identifier; inquiring the corresponding transaction state and the block writing state in the transaction table according to the transaction identifier; and returning query result information to the terminal according to the transaction state and the block writing state.
The terminal can be installed with a service application corresponding to the service system, and the user can initiate a corresponding service request through the service application on the terminal. After the terminal initiates a service request in a corresponding service application, an edge node in the block chain service system can directly obtain the service request which is appointed to be sent, and further process the service request.
The service request carries service data and a transaction identifier, and the service data may further include a corresponding service identifier. The transaction identifier is used for representing information of the unique identifier corresponding to the service request.
After the edge node acquires the service request, the service data is sent to the full-scale nodes corresponding to the target block chain according to the service identification, so that the full-scale nodes generate the current blocks of the service data and perform consensus verification on the current blocks, and after the verification is passed, the full-scale nodes synchronously distribute the verified blocks to a plurality of edge nodes. The edge node also monitors the processing state of the service data in real time and updates the transaction state information in real time according to the processing state. And after receiving the verified block, the edge node stores the block in real time and updates the block writing state. When the block writing state and the transaction confirmation tag are both successfully written, the transaction state is successful and the current block is successfully stored, and at the moment, the transaction state information in the cache can be deleted, so that the cache occupation is reduced.
After the terminal sends the service request to the edge node, the transaction state of the service request can be inquired in real time. The transaction state may be a processing state of the service data in the service request. The edge node monitors the processing state of the service request and waits to receive the current block distributed by the connected proxy node. The edge nodes respectively cache the received processing states in real time and store the verified blocks distributed by the connected nodes. Therefore, when the terminal sends a transaction query request to the edge node, the corresponding transaction state and the block writing state in the transaction table are queried according to the transaction identifier; and generating corresponding query result information according to the transaction state and the block writing state, and returning the query result information to the terminal.
Specifically, when the block writing state is not written, transaction state information in the cache is acquired, query result information is generated according to the transaction state information, and the query result information is returned to the terminal. The transaction state information may include a transaction confirmation label of successful transaction, and the edge node generates query result information according to the transaction confirmation label and returns the query result information to the terminal. And when the block writing state is writing success, generating query result information according to the block writing state and the transaction confirmation label, and returning the query result information to the terminal. The received processing state and the verified block distributed by the connected node are respectively stored in real time, so that the transaction state corresponding to the service request can be effectively cached and determined at the edge node, the terminal can effectively inquire the transaction state of the service request according to the transaction state information locally stored at the edge node whether the edge node receives the verified block or not, the accuracy and the validity of the currently inquired transaction state information can be effectively ensured, the condition that the user pays repeatedly due to uncertain transaction state can be effectively prevented, and the transaction safety is effectively guaranteed.
in one embodiment, returning query result information to the terminal according to the transaction status and the block writing status comprises: when the block writing state is not written, acquiring transaction state information in a cache; and generating query result information according to the transaction state information, and returning the query result information to the terminal.
After the terminal initiates a service request in the corresponding service application, it can also initiate a transaction query request of the service request to the edge node in real time. After receiving a transaction query request sent by a terminal, the edge node acquires transaction state information and block write state information stored in a local cache of the edge node according to the transaction identifier.
Specifically, when the block writing status in the edge node is unwritten, it indicates that the verified block corresponding to the service request has not been successfully stored, and at this time, the transaction status of the service request cannot be determined according to the block writing status of the block. The edge node caches transaction state information in the cache, wherein the transaction state information comprises various state information such as pending, in-process, in-consensus, successful transaction and the like. The edge node acquires the current transaction state information in the cache, and the current transaction state information may be the transaction state information closest to the query time of the transaction query request or the latest updated transaction state in the transaction state information. And the edge node further generates transaction query result information according to the current transaction state information and returns the transaction query result information to the terminal. Therefore, the transaction state corresponding to the service request can be effectively cached and determined at the edge node, and the terminal can effectively inquire the transaction state of the service request according to the transaction state information locally stored at the edge node no matter whether the edge node receives the current block, so that the accuracy and the effectiveness of the transaction state information are effectively guaranteed.
In one embodiment, returning query result information to the terminal according to the transaction status and the block writing status comprises: when the block writing state is writing success, generating query result information according to the block writing state and the transaction confirmation label; and returning the query result information to the terminal.
After receiving a transaction query request sent by a terminal, the edge node acquires transaction state information and block write state information stored in a local cache of the edge node according to the transaction identifier. When the block writing state is writing success, the current block corresponding to the service request and storage success are indicated, and the transaction state is a transaction success state. At this time, the transaction confirmation tag is stored in the repository, and the edge node can directly generate query result information according to the block writing state and/or the transaction confirmation tag and return the query result information to the terminal.
In this embodiment, by respectively storing the received processing state and the current block distributed by the connected node in real time, the transaction state corresponding to the service request can be effectively cached and determined at the edge node, so that the transaction state of the service request can be judged according to the transaction state information locally stored at the edge node. Therefore, the accuracy and the effectiveness of the current transaction state inquired by the user can be effectively ensured, and the condition of repeated payment caused by uncertain transaction state can be effectively prevented.
In one embodiment, fig. 5 is a flow chart illustrating a data storage method in an embodiment. As shown in fig. 5, the data storage method specifically includes the following steps:
Step 502, acquiring service data; the service data includes service identification and transaction state information.
Step 504, monitoring the service data and tracking the node flow direction of the service data; and detecting the processing state of the full node on the service data, and updating the transaction state information according to the processing state.
step 506, the service data is sent to the full-scale node according to the service identifier, so that the full-scale node generates the corresponding current block from the service data and performs consensus verification.
Step 508, receiving the verified block header distributed by the full node, acquiring a transaction table corresponding to the block, and writing the transaction data of the block header into the transaction table; and updating the block writing state of the transaction table, and determining the transaction confirmation tag by using the updated transaction state information and the block writing state.
Step 510, when the block writing state and the transaction confirmation tag are both successfully written into the disk, deleting the service data in the cache.
step 512, receiving a transaction query request sent by the terminal, where the transaction query request carries a transaction identifier.
step 514, the corresponding transaction status and the block writing status in the transaction table are queried according to the transaction identifier.
and 516, generating query result information according to the transaction state and the block writing state, and returning the query result information to the terminal.
In a specific embodiment, referring to FIG. 6, FIG. 6 is a timing diagram of a data storage method in one embodiment. As shown in fig. 6, after obtaining the service request, the edge node stores service data carried in the service request into a local cache, where the service data includes a service identifier and transaction state information. And the edge node monitors the service data in real time and updates the transaction state information. The edge node can also send the service data to the full nodes of the corresponding target block chain according to the service identification; and enabling the full-scale node to generate a current block of the service data, carrying out consensus verification on the current block, and after the verification is passed, synchronously distributing the verified block to the multiple lightweight nodes by the full-scale node. The full-scale nodes comprise a consensus node, an accounting node and a proxy node. And the edge node updates the transaction state information in real time according to the processing state of the full node on the service data, and stores the transaction state information in real time. And after the edge node receives the verified blocks distributed by the nodes connected with the full amount of nodes, the verified blocks are stored in real time, and the block writing state is updated. The edge node can respectively confirm the transaction state of the service data according to the transaction state information and the block writing state, when the block writing state and the transaction confirmation tag are successfully written, the transaction state is indicated to be successful and the verified block is successfully stored, and at the moment, the edge node can delete the transaction state information in the cache.
fig. 3-5 are flow diagrams illustrating a data storage method according to an embodiment. It should be understood that although the various steps in the flow charts of fig. 3-5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 3-5 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 7, a data storage apparatus 700 is provided, the apparatus comprising a data acquisition module 702, a data monitoring module 704, a data transmission module 706, a data storage module 708, and a cache scrubbing module 710, wherein:
a data acquisition module 702, configured to acquire service data; the service data comprises a service identifier and transaction state information;
A data monitoring module 704, configured to monitor service data and update transaction status information;
The data sending module 706 is configured to send the service data to the full-scale node according to the service identifier, so that the full-scale node generates the service data into a corresponding current block and performs consensus verification;
The data storage module 708 is configured to receive the verified blocks distributed by the full-scale nodes, and write the verified blocks into the corresponding transaction table; updating the block writing state of the transaction table, and determining a transaction confirmation label by using the updated transaction state information and the block writing state;
And the cache cleaning module 710 is configured to delete the service data in the cache when both the block write status and the transaction confirmation tag are successfully written into the disk.
in one embodiment, the current block comprises a block header, the full-scale node comprises a consensus node, an accounting node and a proxy node, the full-scale node is used for returning a processing state and generating the current block, the consensus node is used for performing consensus verification on the current block, the consensus node, the accounting node and the proxy node can write the current block into a block account, and the proxy node is used for synchronously distributing the block header to the edge node.
In one embodiment, the data monitoring module 704 is further configured to track node flow of traffic data; detecting the processing state of the full-scale node on the service data, and updating transaction state information according to the processing state; and when the consensus node in the full amount of nodes is detected to complete the consensus of the current block, generating a transaction confirmation label corresponding to the verified block.
In one embodiment, the data storage module 708 is further configured to receive the verified block header distributed by the full-scale node, obtain a transaction table corresponding to the block, and write transaction data of the block header into the transaction table; and when the transaction data of the block header is detected to be written into the transaction table, updating the block writing state of the transaction table into a writing success state.
In one embodiment, the data storage module 708 is further configured to, if a processing state of successful transaction returned by the full-volume node is received first, update transaction state information according to the processing state, and generate a transaction confirmation tag corresponding to the verified block; when a verified block distributed by the full node is received, writing the verified block into a corresponding transaction table and updating a block writing state; the buffer cleaning module 710 is further configured to delete the service data in the buffer when both the block write status and the transaction confirmation tag are successfully written to the disk.
In one embodiment, the data storage module 708 is further configured to, if the verified block distributed by the full node is received first, write the verified block into the corresponding transaction table and update the block writing state, so as to generate a transaction confirmation tag corresponding to the verified block; when a processing state of successful transaction returned by the full-volume node is received, updating transaction state information according to the processing state; the cache cleaning module 710 is further configured to delete the service data in the cache when the block writing status, the transaction confirmation tag, and the transaction success status are all successfully written into the disk.
In one embodiment, as shown in fig. 8, the data storage device 700 further includes a data checking module 712, configured to receive the verified blocks distributed by the full-scale nodes, and write the blocks into the corresponding transaction table; establishing connection with the full-scale nodes according to a preset time frequency; synchronizing the verified blocks from the connected full-scale nodes; and checking the stored blocks according to the blocks obtained by synchronization.
In one embodiment, the data checking module 712 is further configured to delete the transaction data of the abnormal block in the transaction table when the checking result is data abnormal; and rewriting the transaction data of the blocks synchronously obtained from the full-scale nodes into the transaction table.
In one embodiment, as shown in fig. 9, the data storage device 700 further includes a transaction query module 714, configured to receive a transaction query request sent by the terminal, where the transaction query request carries a transaction identifier; inquiring the corresponding transaction state and the block writing state in the transaction table according to the transaction identifier; and generating query result information according to the transaction state and the block writing state, and returning the query result information to the terminal.
In one embodiment, the transaction query module 714 is further configured to obtain transaction status information in the cache when the block write status is not written; and generating query result information according to the transaction state information, and returning the query result information to the terminal.
in one embodiment, the transaction query module 714 is further configured to generate query result information according to the block writing status and the transaction confirmation tag when the block writing status is writing success; and returning the query result information to the terminal.
FIG. 10 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the server 120 of the edge node in the block chain service system in fig. 1. As shown in fig. 10, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement the data storage method. The internal memory may also have stored therein a computer program that, when executed by the processor, causes the processor to perform a data storage method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, the data storage device provided herein may be implemented in the form of a computer program that is executable on a computer apparatus as shown in fig. 10. The memory of the computer device may store various program modules constituting the data storage apparatus, such as a data acquisition module 702, a data monitoring module 704, a data transmission module 706, a data storage module 708, and a cache flush module 710 shown in fig. 7. The computer program constituted by the respective program modules causes the processor to execute the steps in the data storage method of the respective embodiments of the present application described in the present specification.
For example, the computer apparatus shown in fig. 10 may execute step 302 through the data acquisition module 702 in the data storage device shown in fig. 7. The computer device may perform step 304 via data monitoring module 704. The computer device may perform step 306 via data transmission module 706. The computer device may perform step 308 via data storage module 708. The computer device may perform step 310 via the cache scrubbing module 710.
in one embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the data storage method described above. The steps of the data storage method herein may be steps in the data storage methods of the various embodiments described above.
In one embodiment, a computer-readable storage medium is provided, in which a computer program is stored, which, when executed by a processor, causes the processor to carry out the steps of the above-mentioned data storage method. The steps of the data storage method herein may be steps in the data storage methods of the various embodiments described above.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (14)
1. a method of data storage, comprising:
Acquiring service data; the service data comprises a service identifier and transaction state information;
Monitoring the business data and updating the transaction state information;
Sending the service data to a full-scale node according to the service identification, and enabling the full-scale node to generate the service data into a corresponding current block and carry out consensus verification;
receiving the verified blocks distributed by the full-volume nodes, and writing the verified blocks into a corresponding transaction table; updating the block writing state of the transaction table, and determining a transaction confirmation label by using the updated transaction state information and the block writing state;
and deleting the service data in the cache when the block writing state and the transaction confirmation label are both successfully written into the disk.
2. The method of claim 1, wherein the verified block comprises a block header, wherein the quorum nodes comprise a consensus node, an accounting node, and a proxy node, wherein the quorum nodes are configured to return processing status and generate a current block, wherein the consensus node is configured to perform consensus verification on the current block, wherein the consensus node, the accounting node, and the proxy node are all configured to write a verified block into a block book, and wherein the proxy node is configured to synchronously distribute the block header of the verified block to an edge node.
3. The method of claim 2, wherein the traffic data is monitored and updating the transaction state information comprises:
Tracking the node flow direction of the service data;
detecting the processing state of the full-scale node on the service data, and updating the transaction state information according to the processing state;
And when the consensus node in the full-amount nodes is detected to complete the consensus of the current block, generating a transaction confirmation label corresponding to the verified block.
4. The method of claim 1, wherein receiving verified blocks distributed by the quorum nodes, and writing the verified blocks into corresponding transaction tables comprises:
Receiving the verified block header distributed by the full-scale node;
acquiring a transaction table corresponding to the verified block, and writing the transaction data of the block head into the transaction table;
And when the transaction data of the block header is detected to be written into the transaction table, updating the block writing state of the transaction table into a writing success state.
5. The method of claim 1, further comprising:
If a processing state of successful transaction returned by the full-volume node is received, updating the transaction state information according to the processing state, and generating a transaction confirmation label corresponding to the verified block;
When receiving the verified blocks distributed by the full-volume nodes, writing the verified blocks into a corresponding transaction table and updating the block writing state;
And deleting the service data in the cache when the block writing state and the transaction confirmation label are both successfully written into the disk.
6. The method of claim 1, further comprising:
if a verified block distributed by a full amount of nodes is received, writing the verified block into a corresponding transaction table and updating a block writing state to generate a transaction confirmation label corresponding to the verified block;
When a processing state of successful transaction returned by the full-volume node is received, updating the transaction state information according to the processing state;
and deleting the service data in the cache when the block writing state, the transaction confirmation tag and the transaction success state are all successfully written into the disk.
7. The method of claim 1, further comprising:
Receiving the verified blocks distributed by the full-volume nodes, and writing the blocks into corresponding transaction tables;
establishing connection with the full-scale nodes according to a preset time frequency;
Synchronizing the verified blocks from the connected full-scale nodes;
and checking the stored blocks according to the blocks obtained by synchronization.
8. The method of claim 7, further comprising:
When the correction result is data abnormity, deleting the transaction data of the abnormal block in the transaction table;
and rewriting the transaction data of the blocks synchronously obtained from the full-scale nodes into the transaction table.
9. the method according to any one of claims 1 to 8, further comprising:
Receiving a transaction query request sent by a terminal, wherein the transaction query request carries a transaction identifier;
Inquiring a corresponding transaction state and a block writing state in a transaction table according to the transaction identifier;
And generating query result information according to the transaction state and the block writing state, and returning the query result information to the terminal.
10. the method of claim 9, wherein the returning query result information to the terminal according to the transaction status and the block writing status comprises:
when the block writing state is not written, acquiring transaction state information in the cache;
And generating inquiry result information according to the transaction state information, and returning the inquiry result information to the terminal.
11. The method of claim 9, wherein the returning query result information to the terminal according to the transaction status and the block writing status comprises:
When the block writing state is writing success, generating query result information according to the block writing state and the transaction confirmation label;
And returning the query result information to the terminal.
12. A data storage device, characterized in that the device comprises:
The data acquisition module is used for acquiring service data; the service data comprises a service identifier and transaction state information;
The data monitoring module is used for monitoring the business data and updating the transaction state information;
the data sending module is used for sending the service data to a full-scale node according to the service identifier, so that the full-scale node generates the service data into a corresponding current block and performs consensus verification;
The data storage module is used for receiving the verified blocks distributed by the full-scale nodes and writing the verified blocks into a corresponding transaction table; updating the block writing state of the transaction table, and determining a transaction confirmation label by using the updated transaction state information and the block writing state;
And the cache cleaning module is used for deleting the service data in the cache when the block writing state and the transaction confirmation tag are both successfully written into the disk.
13. A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 11.
14. a computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910859251.8A CN110543788B (en) | 2019-09-11 | 2019-09-11 | Data storage method, apparatus, computer readable storage medium and computer device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910859251.8A CN110543788B (en) | 2019-09-11 | 2019-09-11 | Data storage method, apparatus, computer readable storage medium and computer device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110543788A true CN110543788A (en) | 2019-12-06 |
| CN110543788B CN110543788B (en) | 2024-05-03 |
Family
ID=68713410
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910859251.8A Active CN110543788B (en) | 2019-09-11 | 2019-09-11 | Data storage method, apparatus, computer readable storage medium and computer device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110543788B (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111159303A (en) * | 2020-01-07 | 2020-05-15 | 杭州宇链科技有限公司 | Method for reducing block chain data storage cost |
| CN111241061A (en) * | 2020-01-09 | 2020-06-05 | 平安科技（深圳）有限公司 | Writing method of state database, data processing device and storage medium |
| CN111415161A (en) * | 2020-04-27 | 2020-07-14 | 财付通支付科技有限公司 | Block chain-based data verification method and device and computer-readable storage medium |
| CN111507717A (en) * | 2020-04-20 | 2020-08-07 | 腾讯科技（深圳）有限公司 | Data processing method, device, block node and computer readable storage medium |
| CN111611321A (en) * | 2020-06-29 | 2020-09-01 | 上海优扬新媒信息技术有限公司 | Data storage method and device and block chain system |
| CN111630549A (en) * | 2020-04-22 | 2020-09-04 | 支付宝(杭州)信息技术有限公司 | Managing transaction requests in ledger system |
| CN111917859A (en) * | 2020-07-28 | 2020-11-10 | 腾讯科技（深圳）有限公司 | Data transmission method and device, computer equipment and storage medium |
| CN112396423A (en) * | 2021-01-20 | 2021-02-23 | 腾讯科技（深圳）有限公司 | Transaction data processing method, device, equipment and storage medium |
| CN112748881A (en) * | 2021-01-15 | 2021-05-04 | 长城超云(北京)科技有限公司 | Storage fault tolerance method and cluster system for virtualization scene |
| CN112883107A (en) * | 2020-12-31 | 2021-06-01 | 杭州趣链科技有限公司 | Asynchronous execution method, system and related equipment for transactions in block chain |
| CN112988412A (en) * | 2021-02-07 | 2021-06-18 | 中国联合网络通信集团有限公司 | Edge caching method, base station and system based on block chain network |
| CN113034146A (en) * | 2021-05-25 | 2021-06-25 | 杭州云链趣链数字科技有限公司 | Block chain-based communication method, system, electronic device and storage medium |
| CN113852662A (en) * | 2021-08-06 | 2021-12-28 | 华数云科技有限公司 | Edge cloud distributed storage framework and method based on alliance chain |
| WO2021259127A1 (en) * | 2020-06-24 | 2021-12-30 | 支付宝(杭州)信息技术有限公司 | Pressure testing method, apparatus and system for blockchain network |
| WO2021259125A1 (en) * | 2020-06-24 | 2021-12-30 | 支付宝(杭州)信息技术有限公司 | Data cleaning method and apparatus for blockchain network |
| CN114049213A (en) * | 2021-11-15 | 2022-02-15 | 深圳前海鸿泰源兴科技发展有限公司 | Informatization financial data analysis system and analysis method |
| US11455631B2 (en) | 2020-04-22 | 2022-09-27 | Alipay (Hangzhou) Information Technology Co., Ltd. | Managing transaction requests in ledger systems |
| CN115271733A (en) * | 2022-09-28 | 2022-11-01 | 深圳市迪博企业风险管理技术有限公司 | Privacy-protecting block chain transaction data anomaly detection method and equipment |
| CN116684425A (en) * | 2023-07-28 | 2023-09-01 | 腾讯科技（深圳）有限公司 | Block chain data processing method, system, device and computer equipment |
| CN116956332A (en) * | 2023-09-20 | 2023-10-27 | 深圳市智慧城市科技发展集团有限公司 | BIM data processing method, BIM data processing equipment and computer readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109191124A (en) * | 2018-08-16 | 2019-01-11 | 北京京东尚科信息技术有限公司 | Block chain network, dispositions method and storage medium |
| CN109214823A (en) * | 2018-08-27 | 2019-01-15 | 北京京东金融科技控股有限公司 | Transaction verification method, device, storage medium and electronic equipment based on block chain |
-
2019
- 2019-09-11 CN CN201910859251.8A patent/CN110543788B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109191124A (en) * | 2018-08-16 | 2019-01-11 | 北京京东尚科信息技术有限公司 | Block chain network, dispositions method and storage medium |
| CN109214823A (en) * | 2018-08-27 | 2019-01-15 | 北京京东金融科技控股有限公司 | Transaction verification method, device, storage medium and electronic equipment based on block chain |
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111159303A (en) * | 2020-01-07 | 2020-05-15 | 杭州宇链科技有限公司 | Method for reducing block chain data storage cost |
| CN111241061A (en) * | 2020-01-09 | 2020-06-05 | 平安科技（深圳）有限公司 | Writing method of state database, data processing device and storage medium |
| CN111241061B (en) * | 2020-01-09 | 2023-04-07 | 平安科技（深圳）有限公司 | Writing method of state database, data processing device and storage medium |
| CN111507717A (en) * | 2020-04-20 | 2020-08-07 | 腾讯科技（深圳）有限公司 | Data processing method, device, block node and computer readable storage medium |
| CN111507717B (en) * | 2020-04-20 | 2022-08-12 | 腾讯科技（深圳）有限公司 | Data processing method, device, block node and computer readable storage medium |
| US11455297B2 (en) | 2020-04-22 | 2022-09-27 | Alipay (Hangzhou) Information Technology Co., Ltd. | Managing transaction requests in ledger systems |
| CN111630549A (en) * | 2020-04-22 | 2020-09-04 | 支付宝(杭州)信息技术有限公司 | Managing transaction requests in ledger system |
| US11455631B2 (en) | 2020-04-22 | 2022-09-27 | Alipay (Hangzhou) Information Technology Co., Ltd. | Managing transaction requests in ledger systems |
| CN111415161B (en) * | 2020-04-27 | 2024-03-19 | 财付通支付科技有限公司 | Block chain-based data verification method and device and computer readable storage medium |
| CN111415161A (en) * | 2020-04-27 | 2020-07-14 | 财付通支付科技有限公司 | Block chain-based data verification method and device and computer-readable storage medium |
| WO2021259125A1 (en) * | 2020-06-24 | 2021-12-30 | 支付宝(杭州)信息技术有限公司 | Data cleaning method and apparatus for blockchain network |
| WO2021259127A1 (en) * | 2020-06-24 | 2021-12-30 | 支付宝(杭州)信息技术有限公司 | Pressure testing method, apparatus and system for blockchain network |
| CN111611321B (en) * | 2020-06-29 | 2023-07-25 | 度小满科技(北京)有限公司 | Data storage method, device and blockchain system |
| CN111611321A (en) * | 2020-06-29 | 2020-09-01 | 上海优扬新媒信息技术有限公司 | Data storage method and device and block chain system |
| CN111917859B (en) * | 2020-07-28 | 2022-08-12 | 腾讯科技（深圳）有限公司 | Data transmission method and device, computer equipment and storage medium |
| CN111917859A (en) * | 2020-07-28 | 2020-11-10 | 腾讯科技（深圳）有限公司 | Data transmission method and device, computer equipment and storage medium |
| CN112883107A (en) * | 2020-12-31 | 2021-06-01 | 杭州趣链科技有限公司 | Asynchronous execution method, system and related equipment for transactions in block chain |
| CN112883107B (en) * | 2020-12-31 | 2022-05-17 | 杭州趣链科技有限公司 | Asynchronous execution method, system and related equipment for transactions in block chain |
| CN112748881B (en) * | 2021-01-15 | 2024-02-20 | 长城超云(北京)科技有限公司 | Storage fault-tolerant method and cluster system oriented to virtualization scene |
| CN112748881A (en) * | 2021-01-15 | 2021-05-04 | 长城超云(北京)科技有限公司 | Storage fault tolerance method and cluster system for virtualization scene |
| CN112396423B (en) * | 2021-01-20 | 2021-04-13 | 腾讯科技（深圳）有限公司 | Transaction data processing method, device, equipment and storage medium |
| CN112396423A (en) * | 2021-01-20 | 2021-02-23 | 腾讯科技（深圳）有限公司 | Transaction data processing method, device, equipment and storage medium |
| CN112988412B (en) * | 2021-02-07 | 2023-06-27 | 中国联合网络通信集团有限公司 | Edge caching method, base station and system based on block chain network |
| CN112988412A (en) * | 2021-02-07 | 2021-06-18 | 中国联合网络通信集团有限公司 | Edge caching method, base station and system based on block chain network |
| CN113034146A (en) * | 2021-05-25 | 2021-06-25 | 杭州云链趣链数字科技有限公司 | Block chain-based communication method, system, electronic device and storage medium |
| CN113852662A (en) * | 2021-08-06 | 2021-12-28 | 华数云科技有限公司 | Edge cloud distributed storage framework and method based on alliance chain |
| CN113852662B (en) * | 2021-08-06 | 2023-09-26 | 华数云科技有限公司 | Edge cloud distributed storage system and method based on alliance chain |
| CN114049213A (en) * | 2021-11-15 | 2022-02-15 | 深圳前海鸿泰源兴科技发展有限公司 | Informatization financial data analysis system and analysis method |
| CN115271733A (en) * | 2022-09-28 | 2022-11-01 | 深圳市迪博企业风险管理技术有限公司 | Privacy-protecting block chain transaction data anomaly detection method and equipment |
| CN116684425A (en) * | 2023-07-28 | 2023-09-01 | 腾讯科技（深圳）有限公司 | Block chain data processing method, system, device and computer equipment |
| CN116684425B (en) * | 2023-07-28 | 2023-10-27 | 腾讯科技（深圳）有限公司 | Block chain data processing method, system, device and computer equipment |
| CN116956332A (en) * | 2023-09-20 | 2023-10-27 | 深圳市智慧城市科技发展集团有限公司 | BIM data processing method, BIM data processing equipment and computer readable storage medium |
| CN116956332B (en) * | 2023-09-20 | 2024-01-05 | 深圳市智慧城市科技发展集团有限公司 | BIM data processing method, BIM data processing equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110543788B (en) | 2024-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110543788B (en) | Data storage method, apparatus, computer readable storage medium and computer device | |
| CN110633323B (en) | Service data storage method, device, storage medium and computer equipment | |
| CN109002732B (en) | Data evidence storage method, equipment and system and data evidence obtaining method | |
| CN110572450B (en) | Data synchronization method and device, computer readable storage medium and computer equipment | |
| CN108961030B (en) | Data processing method, apparatus, system, medium, and device for electronic ticket | |
| CN109242467B (en) | Block chain-based networking method and device, computer equipment and storage medium | |
| JP7330596B2 (en) | BLOCKCHAIN DATA ARCHIVING METHOD, BLOCKCHAIN DATA ARCHIVING DEVICE, ELECTRONIC DEVICE, AND COMPUTER PROGRAM | |
| JP7199775B2 (en) | Data processing method, data processing device, node device, and computer program based on smart contract | |
| CN109255084B (en) | Electronic bill query method, device, storage medium and computer equipment | |
| CN110597837B (en) | Service data processing method, device, storage medium and computer equipment | |
| CN110784495B (en) | Block chain-based discovery and configuration information management method for big data cluster system | |
| CN110602116B (en) | Block chain based data verification method, device and computer readable storage medium | |
| CN110602095B (en) | Data distribution and storage method and device based on block chain network | |
| CN110597541B (en) | Interface updating processing method, device, equipment and storage medium based on block chain | |
| CN110597883A (en) | Vehicle rental data processing method and device based on block chain and storage medium | |
| CN112087497B (en) | Data synchronization method and device, electronic equipment and readable storage medium | |
| JP2020190874A (en) | Document management system | |
| CN112448946A (en) | Log auditing method and device based on block chain | |
| CN111506661B (en) | Content access management method, device and storage medium | |
| CN111932326B (en) | Data processing method based on block chain network and related equipment | |
| CN114531260A (en) | Information processing method based on alliance chain system and related equipment | |
| CN112163917A (en) | Bill processing method, device, medium and electronic equipment based on block chain | |
| CN112822279B (en) | Monitoring method and device based on intelligent sensing and trusted storage | |
| CN110598446B (en) | Block chain-based test method, device, storage medium and computer equipment | |
| CN110598446A (en) | Block chain based test method and device, storage medium and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |