CN110597919B

CN110597919B - Block chain-based data management method, device, equipment and storage medium

Info

Publication number: CN110597919B
Application number: CN201910910864.XA
Authority: CN
Inventors: 崔冉
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-09-25
Filing date: 2019-09-25
Publication date: 2023-09-01
Anticipated expiration: 2039-09-25
Also published as: CN110597919A

Abstract

The application discloses a data management method based on a block chain, and belongs to the technical field of computers. The method is performed by a server, the method comprising: acquiring a resource transfer record of a first account in a block chain; and generating a resource transfer check list according to the resource transfer record of the first account in the blockchain, sending the resource transfer check list to the target user, receiving the check result of the target user on the resource transfer check list, and storing the check result into the blockchain. According to the application, the resource transfer record of the first account is stored in the blockchain through the use of the blockchain, the resource transfer check list is generated through the transfer record in the blockchain, and the data check result of the target user is stored in the blockchain, so that the data of the target user can be shared at each node on the blockchain, and the transparency and the credibility of the data of the target user are improved.

Description

Block chain-based data management method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a data management method, apparatus, device and storage medium based on a blockchain.

Background

With the development of the computer field, in daily life, various data are often required to be stored and recorded. For example, transaction records of each bank account are stored in a banking system, and information of each policy is stored in a security system.

Wherein, the related data generated for the reconciliation process of the enterprise in the banking system is stored in the respective servers of the enterprise and the bank. In addition, at present, the reconciliation process of the enterprise still adopts a manual reconciliation mode, that is, when the enterprise needs to reconcile its own bank account, the bank performs the reconciliation processing (such as checking information therein, stamping enterprise official seal, stamping financial seal, etc.) on the paper bill generated by the bank according to the transaction record stored by the enterprise, and then returns the paper bill to the bank, and the bank stores the paper bill again.

The transaction records generated by the bank account number of the enterprise are independently stored in the enterprise server and the bank server, the data stored by the enterprise and the data stored by the bank are not communicated, and the problems of opaque finance of both parties, low credibility of the data and the like exist.

Disclosure of Invention

The embodiment of the application provides a data management method, device and equipment based on a blockchain and a storage medium, which can improve the transparency between data stored by an enterprise and data stored by a bank and increase the credibility of the data. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides a blockchain-based data management method, the method being performed by a server, the method including:

acquiring a resource transfer record of a first account in a block chain;

generating a resource transfer check list according to the resource transfer record of the first account, wherein the resource transfer check list comprises the resource transfer record of the first account;

the resource transfer check list is sent to a target user, wherein the target user is the user to which the first account belongs;

and receiving a checking result of the target user on the resource transfer checking table, and storing the checking result into the blockchain.

In another aspect, an embodiment of the present application provides a blockchain-based data management device, where the device is used in a server, and the device includes:

the transfer record acquisition module is used for acquiring a resource transfer record of the first account in the blockchain;

The check list generation module is used for generating a resource transfer check list according to the resource transfer records of the first account in the blockchain, wherein the resource transfer check list comprises the resource transfer records of the first account;

the check list sending module is used for sending the resource transfer check list to a target user, wherein the target user is the user to which the first account belongs;

and the checking result storage module is used for receiving the checking result of the target user on the resource transfer checking table and storing the checking result into the blockchain.

Optionally, the transfer record obtaining module is configured to obtain, from the blockchain, the resource transfer record in a first period of time when or after a preset time node arrives, where the first period of time is any period of time before the preset time node;

the check list generation module is used for generating the resource transfer check list in the first time period according to the resource transfer record in the first time period.

Optionally, the apparatus further includes:

the record storage module is used for storing a first resource transfer record into the blockchain through an intelligent contract when the first resource transfer record is generated for the first account, wherein the first resource transfer record is generated when the first account is subjected to resource transfer at any time.

Optionally, the apparatus further includes:

a first address storage module for storing a first record address on the blockchain, the first record address being an address of the first resource transfer record stored in the blockchain;

and the relation establishing module is used for establishing a binding relation between the first record address and the first resource transfer record and storing the binding relation on the blockchain.

Optionally, the apparatus further includes:

the second address storage module is used for locally storing the first record address;

and the record inquiring module is used for inquiring the first resource transfer record according to the first record address when inquiring the first resource transfer record.

Optionally, the apparatus further includes:

and the data storage module is used for storing the resource transfer quantity, the resource residual quantity and the resource hash value of the resource transfer check table into the blockchain.

Optionally, the first account is a bank account.

In yet another aspect, embodiments of the present application further provide a computer device, where the computer device includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored, where the at least one instruction, the at least one program, the set of codes, or the set of instructions are loaded and executed by the processor to implement a blockchain-based data management method as described above.

In yet another aspect, embodiments of the present application further provide a computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement a blockchain-based data management method as described above.

The technical scheme provided by the embodiment of the application has the beneficial effects that at least:

the method comprises the steps of obtaining a resource transfer record of a first account in a block chain through a server; and generating a resource transfer check list according to the resource transfer record of the first account in the blockchain, sending the resource transfer check list to the target user, receiving the check result of the target user on the resource transfer check list, and storing the check result into the blockchain. According to the application, the resource transfer record of the first account is stored in the blockchain through the use of the blockchain, the resource transfer check list is generated through the transfer record in the blockchain, and the data check result of the target user is stored in the blockchain, so that the data of the target user can be shared at each node on the blockchain, and the transparency and the credibility of the data of the target user are improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a data sharing system according to an exemplary embodiment of the present application;

FIG. 2 is a block chain architecture diagram according to an exemplary embodiment of the present application;

FIG. 3 is a schematic diagram of a new block generation process provided by an exemplary embodiment of the present application;

FIG. 4 is a method flow diagram of a blockchain-based data management method in accordance with an exemplary embodiment of the present application;

FIG. 5 is a method flow diagram of a blockchain-based data management method in accordance with an exemplary embodiment of the present application;

FIG. 6 is a schematic diagram of a resource transfer check table according to an exemplary embodiment of the present application;

FIG. 7 is an interface diagram of a terminal verification interface according to an exemplary embodiment of the present application;

FIG. 8 is a method flow diagram of a blockchain-based data management method provided by an exemplary embodiment of the present application;

FIG. 9 is a schematic illustration of the architecture of a system frame related to FIG. 8 in accordance with an exemplary embodiment of the present application;

FIG. 10 is a block diagram illustrating a block chain based data management device according to an exemplary embodiment of the present application;

fig. 11 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

The scheme provided by the application can be used for downloading or running the application program in the real scene of using the terminal in the daily life of people. For ease of understanding, some terms and application scenarios will be briefly described below.

1) The blockchain comprises a series of blocks (blocks) which are connected with each other according to the generated sequence time, the new blocks are not removed once being added into the blockchain, and record data submitted by nodes in the blockchain system are recorded in the blocks.

2) Intelligent contracts, computerized agreements, which may execute terms of a contract, implemented by code deployed on a shared ledger for execution when certain conditions are met, for completing automated transactions based on actual business demand codes, such as querying the physical distribution status of goods purchased by a buyer, transferring electronic money of the buyer to the merchant's address after the buyer signs for goods; of course, the smart contract is not limited to executing the contract for the transaction, and may execute a contract that processes the received information.

3) A federated chain, also known as a community blockchain (Consortium Blockchains), refers to a blockchain whose consensus process is controlled by preselected nodes. In a federated chain, all or part of the functions are only opened for node members within the chain, and each blockchain node in the federated chain can customize read-write permissions, query permissions, etc. based on needs.

4) The shared account book is used for providing functions of operations such as storage, inquiry and modification of account data, sending record data of the operations on the account data to other nodes in the blockchain system, and after the other nodes verify that the account data is valid, storing the record data into the temporary block as a response for acknowledging that the account data is valid, and can also send acknowledgement to the node initiating the operations.

Referring to fig. 1, a schematic diagram of a data sharing system according to an exemplary embodiment of the application is shown. As shown in fig. 1, a data sharing system gateway 101 and a plurality of nodes 102 are included in a sharing system 100. The data sharing system 100 is a system for sharing data between nodes, the data sharing system gateway 101 may be used for performing functions such as request conversion and address information verification, and the plurality of nodes 102 may be enterprise servers and financial institution servers in the data sharing system. Alternatively, the server serving as each node may be a server, or several servers, or a virtualization platform, or a cloud computing service center, etc.

Optionally, the data sharing system gateway 101 is configured to receive a service processing request, where the service processing request is generated according to a table structure provided by the data sharing system, and the service processing request may carry a service data record of a user; the data sharing system gateway can extract the service data of the user from the service processing request, generate a service data recording request of the data sharing system, wherein the service data recording request carries the service data of the user, and send the service data recording request to at least one node in the data sharing system; any one of the plurality of nodes is configured to provide a data service, such as a service of writing a shared ledger or an account information query, based on the received business data record request.

The plurality of nodes 101 may be individual servers in a data sharing system. Each node 101 may receive input information while operating normally and maintain shared data within the data sharing system based on the received input information. In order to ensure the information intercommunication in the data sharing system, information connection can exist between each node in the data sharing system, and the nodes can transmit information through the information connection. For example, when any node in the data sharing system receives input information, other nodes in the data sharing system acquire the input information according to a consensus algorithm, and store the input information as data in the shared data, so that the data stored on all nodes in the data sharing system are consistent.

Each node in the data sharing system has a node identifier corresponding to the node identifier, and each node in the data sharing system can store the node identifiers of other nodes in the data sharing system, so that the generated block can be broadcast to other nodes in the data sharing system according to the node identifiers of other nodes. Each node can maintain a node identification list shown in the following table, and the node names and the node identifications are correspondingly stored in the node identification list. The node identifier may be an IP (Internet Protocol, protocol of interconnection between networks) address, and any other information that can be used to identify the node, and the IP address is only illustrated in table 1.

Node name	Node identification
		Node 1	117.114.151.174
Node 2	117.116.189.145
		…	…
Node N	119.123.789.258

TABLE 1

Each node in the data sharing system stores one and the same blockchain. Referring to fig. 2, which is a schematic diagram of a block chain according to an exemplary embodiment of the present application, as shown in fig. 2, each block 202 is included in a block chain 201, and as can be seen from fig. 2, the block chain 201 may be composed of a plurality of blocks 201, an originating block includes a block header and a block body, the block header stores an input information feature value, a version number, a timestamp and a difficulty value, and the block body stores input information; the next block of the starting block takes the starting block as a father block, the next block also comprises a block head and a block main body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the father block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain are associated with the block data stored in the father block, and the safety of the input information in the block is ensured.

When each block in the blockchain is generated, please refer to fig. 3, which is a schematic diagram illustrating a new block generation process provided by an exemplary embodiment of the present application, when a node where the blockchain is located receives input information, the node verifies the input information, stores the input information into a memory pool after the verification is completed, and updates a hash tree for recording the input information; then, updating the update time stamp to the time of receiving the input information, trying different random numbers, and calculating the characteristic value for a plurality of times, so that the calculated characteristic value can meet the following formula:

SHA256(SHA256(virsion+pre_hash+merkle_root+ntime+nbits+x))<TARGET

Wherein SHA256 is a eigenvalue algorithm used to calculate eigenvalues; version (version number) is version information of the related block protocol in the block chain; the prev_hash is the block header characteristic value of the parent block of the current block; the merkle_root is a characteristic value of input information; ntime is the update time of the update timestamp; the nbits is the current difficulty, is a fixed value in a period of time, and is determined again after exceeding a fixed period of time; x is a random number; TARGET is a eigenvalue threshold that can be determined from nbits.

Thus, when the random number meeting the formula is calculated, the information can be correspondingly stored to generate the block head and the block main body, and the current block is obtained. And then, the node where the blockchain is located sends the newly generated blocks to other nodes in the data sharing system where the newly generated blocks are located according to the node identification of other nodes in the data sharing system, the other nodes verify the newly generated blocks, and the newly generated blocks are added into the blockchain stored in the newly generated blocks after the verification is completed.

The embodiment of the application provides a data management method based on a block chain, which can be applied to the data sharing system shown in the figure 1, so that the problems of data intercommunication of various servers, reliability of data storage and the like are solved. Referring to fig. 4, a flowchart of a method for managing blockchain-based data according to an exemplary embodiment of the present application is shown, and the method may be applied to the data sharing system shown in fig. 1 and executed by each node (server) running in the system. As shown in FIG. 4, the blockchain-based data management method may include the following steps.

Step 401, obtaining a resource transfer record of a first account in a blockchain.

The resource transfer record may be a resource transfer record of a first account stored in the blockchain by each node in the blockchain.

Step 402, generating a resource transfer check list according to the resource transfer record of the first account in the blockchain, wherein the resource transfer check list comprises the resource transfer record of the first account.

The server serving as a node in the blockchain can store the resource transfer record of the first account in a uplink manner, and when the resource transfer check list needs to be generated, the server in the blockchain can acquire the stored resource transfer record from the blockchain, so that the resource transfer check list is generated according to the acquired resource transfer record. The resource transfer check list may be a resource transfer check list with a fixed format, which is pre-agreed between the server manufacturer and the owner of the first account. For example, the server serving as a node in the blockchain is a bank server, the owner of the first account is a certain enterprise, the bank and the enterprise can previously specify the format of a resource transfer check table, and the bank server can acquire the resource transfer record stored on the blockchain to generate a corresponding resource transfer check table.

Step 403, sending a resource transfer check list to the target user, where the target user is the user to which the first account belongs.

Optionally, the server serving as a node in the blockchain may send the generated resource transfer check table to the target user, where the target user may be an enterprise user or a personal user. Correspondingly, the server can send the generated resource transfer check list to the terminal of the reconciliation staff in the enterprise user, and the terminal of the reconciliation staff can display the interface of the resource transfer check list, so that the reconciliation staff operates in the interface to complete the check of the resource transfer check list.

Step 404, receiving the checking result of the target user on the resource transfer checking table, and storing the checking result into the blockchain.

Optionally, after the target user checks the received resource transfer check table, the generated check result may be returned to the corresponding server, and after the server receives the check result, the check result may be stored in a uplink manner, so that transparency of storing the check result may be achieved.

In summary, the method includes the steps of obtaining a resource transfer record of a first account in a blockchain through a server, generating a resource transfer check list according to the resource transfer record of the first account in the blockchain, sending the resource transfer check list to a target user, receiving a check result of the target user on the resource transfer check list, and storing the check result in the blockchain. According to the application, the resource transfer record of the first account is stored in the blockchain through the use of the blockchain, the resource transfer check list is generated through the transfer record in the blockchain, and the data check result of the target user is stored in the blockchain, so that the data of the target user can be shared at each node on the blockchain, and the transparency and the credibility of the data of the target user are improved.

In one possible implementation, before the generating the resource transfer check table, the blockchain may store the resource transfer record related to the first account generated by the server of the first account in a uplink manner, so as to describe the embodiment shown in fig. 4. Referring to fig. 5, a flowchart of a method for managing blockchain-based data according to an exemplary embodiment of the present application is shown, and the method may be applied to the data sharing system shown in fig. 1 and executed by each node (server) running in the system. As shown in FIG. 5, the blockchain-based data management method may include the following steps.

In step 501, when a first resource transfer record is generated for a first account, the first resource transfer record is stored into a blockchain through a smart contract.

The first resource transfer record is generated when the first account is subjected to resource transfer at any time. Optionally, when the first account number performs resource transfer, the server that generates and stores the first resource transfer record of the first account number is used as one of the nodes of the blockchain, and the first resource transfer record may be stored into the blockchain through an intelligent contract, and the first resource transfer record is stored on the blockchain. Alternatively, the server may uplink the first resource transfer record in a desensitized uplink manner.

Optionally, when the first account is a bank account, the money transfer record generated by the bank server stores the money in a uplink manner when the bank account performs a money transfer. Wherein, for the bank server, if itself is one of the nodes of the blockchain, the bank server can uplink the funds transfer record generated this time through the smart contract. When the first resource transfer record is a funds transfer record of a bank account, the data of the bank server for uplink may include funds information and transaction information of the bank account.

In one possible implementation, the blockchain according To the embodiments of the present application is a federation chain composed of different server nodes, and each node performs data synchronization based on a point-To-point (P2P) network characteristic of the blockchain. Alternatively, the first resource transfer record generated by the current server may also be stored in each node in the blockchain by performing a bypass link by other nodes. For example, the bank a may store its own first resource transfer record in a ul through the server of the bank B.

Step 502, a first record address is stored on a blockchain, the first record address being an address where a first resource transfer record is stored in the blockchain.

After the server uplinks the first resource transfer record to the blockchain, the blockchain can correspond to the content of the current uplink, the timestamp and other information to generate a corresponding first record address, the blockchain can return the uplink address to the current uplink server, and the server can store the first record address in the uplink through the intelligent contract again, so that each node in the blockchain can know the storage condition of the first resource transfer record.

The server may also store the first record address locally, i.e., the server may store the first record address returned by the blockchain locally, and upon querying the first resource transfer record, the server may query the first resource transfer record based on the first record address.

Step 503, establishing a binding relationship between the first record address and the first resource transfer record, and storing the binding relationship on the blockchain.

Optionally, after obtaining the first record address returned by the blockchain, the server may also establish a binding relationship between the local pair of first record addresses and the first resource transfer record, so as to facilitate subsequent calls. Referring to table 2, a table of correspondence between blockchain addresses and resource transfer records according to an embodiment of the present application is shown.

Block chain address	Resource transfer records
		Block chain Address one	Resource transfer record one
Block chain address two	Resource transfer record two
		Block chain address three	Resource transfer record three
……	……

TABLE 2

As shown in table 2, the corresponding relationship between each blockchain address and each resource transfer record is included, the server may store the corresponding relationship between the blockchain address and the resource transfer record locally in the form of table 2, and store the corresponding relationship in uplink through an intelligent contract, so that each node of the blockchain may also obtain the corresponding relationship.

At step 504, a resource transfer record in a first time period is obtained from the blockchain at or after the arrival of a predetermined time node.

Wherein the first time period is any time period before the preset time node.

Alternatively, the preset time node and the first period may be pre-stored in the server, for example, a fixed period value, etc. Every other period (preset time node), the server can acquire the resource transfer record in the first time period from the blockchain. For example, the preset time node is the end of the month of each month, the first time period is one month before the time node, i.e., every month, the server may obtain the resource transfer record stored in this month from the blockchain.

Alternatively, the server may obtain the resource transfer records stored in the current month from the blockchain, by downloading, from the blockchain, the corresponding resource transfer records from the blockchain through each blockchain address according to the locally stored blockchain address. In one possible implementation manner, the server may also obtain the resource transfer record stored in the month from the table 2 stored in the server, which is not limited in this embodiment of the present application. For example, when the first account is a bank account and the server is a bank server, the bank server may obtain each funds transfer record in the month of the bank account according to the blockchain address of each funds transfer record of the transaction stored in the month.

And step 505, generating a resource transfer check table in the first time period according to the resource transfer record in the first time period.

The server may generate a resource transfer check table in the first time period according to the resource transfer record in the first time period acquired from the blockchain. For example, according to the first time period being one month, the server may generate a resource transfer check table of one month from each resource transfer record in the month obtained from the blockchain. Taking the first account as a bank account and the server as a bank server as an example, the bank server obtains a fund transfer record in a month of the bank account and generates a resource transfer check list (also referred to as a statement) in the month of the bank account.

Referring to fig. 6, a schematic diagram of a resource transfer check table according to an exemplary embodiment of the present application is shown. As shown in fig. 6, each funds transfer record 601, balance information 602, funds transfer time 603 for the month of the first account number is included. The server may generate a resource transfer check table of the first account in a month as shown in fig. 6 according to each resource transfer record of the first account in the month obtained from the blockchain.

Optionally, the server may further store the generated resource transfer check table in a uplink manner, where the method includes storing the resource transfer number, the resource remaining number and the resource hash value of the resource transfer check table in the blockchain. If the resource transfer check table shown in fig. 6 is used, the data stored in the server uplink may have the funds transfer details, balances, hash values of the data, etc. contained in fig. 6. That is, the server stores the generated resource transfer check table in a uplink manner, so that the resource transfer check table can also exist in the blockchain, and transparency of the resource transfer check table is realized. Alternatively, the calculation manner of the resource hash value may refer to the related description in fig. 3 of the merchant, which is not described herein.

Optionally, the blockchain may also return the storage address of the resource transfer check table to the server, where the server may store the storage address of the resource transfer check table in the server similar to the above-mentioned address storage of the resource transfer record, and details of execution may refer to the above-mentioned storage of the address of the resource transfer record by the server, which is not described herein. It should be noted that fig. 6 is only an example, and the resource transfer check table in practical application may also include other information, and accordingly, the server may also store other information in a uplink manner.

Step 506, sending a resource transfer check list to the target user, wherein the target user is the user to which the first account belongs.

Optionally, the target user may set up the requirement information for acquiring the resource transfer check list in the server in advance, and the server may determine the target user to which the first account belongs according to the requirement information, and send the generated resource transfer check list to the target user. Optionally, when the target user is an enterprise user and the first account is a bank account of the enterprise user, the server sends the generated resource transfer check list to a terminal of a staff checking the enterprise user, and the terminal of the staff can display an interface of the resource transfer check list, so that the staff operates in the interface to finish checking the resource transfer check list.

Optionally, the server of the first account may further send a prompt message to the enterprise user, where the prompt message may indicate that the server has sent the resource transfer check table to the enterprise user, so as to remind the enterprise user to check. For example, the bank may send a short message, a communication message, etc. to the enterprise user, or a staff member of the bank may notify the enterprise user by telephone, thereby notifying the enterprise user that the resource transfer check list has been sent by the enterprise user. Optionally, the staff of the bank can store the prompt message in a uplink manner through the bank server, so that transparency of the flow data is achieved.

Optionally, the server may also send the target user a storage address of the prokaryotic table. That is, the server may also send the storage address of the stored resource transfer check table on the blockchain to the target client, for example, the prompt message sent by the server to the target user includes the storage address of the resource transfer check table generated at the time on the blockchain, the target user may query the resource transfer check table through the address, check the resource transfer check table, formulate a corresponding check result and return the check result and the storage address to the server together.

And 507, receiving a checking result of the target user on the resource transfer checking table, and storing the checking result into the blockchain.

After receiving the resource transfer check list, the target user can check the resource transfer check list. Referring to fig. 7, an interface diagram of a terminal verification interface according to an exemplary embodiment of the present application is shown. As shown in fig. 7, a resource transfer check table 701, a check control 702, a submit control 703, and a remark input box 704 are included in the terminal interface 700. The target user may view the resource transfer check table 701, select the check control 702, input relevant information (such as no error, which of the tables has error, etc.) in the remark input box 704, and finally click the submit control 703, so as to return the check result to the server sending the resource transfer check table, and complete the check. After receiving the verification result, the server may also store the verification result in a uplink manner, and optionally, the uplink manner may refer to the related content, which is not described herein.

Alternatively, corresponding to an alternative implementation of step 506, the server may also receive the verification result including the storage address, and store the received verification result in a uplink manner.

In a possible implementation manner, taking the first account as a bank account and the target user as an enterprise user as an example, please refer to fig. 8, which illustrates a method flowchart of a blockchain-based data management method according to an exemplary embodiment of the present application. As shown in FIG. 8, the blockchain-based data management method may include the following steps.

In step 801, a payment transaction occurs for an enterprise.

In daily life, enterprises can make online banking payment, loan exchange and other modes, so that payment transactions occur on own bank account numbers, and the enterprises can store corresponding transaction information, such as the amount of the payment transactions, the flow information of the transactions and the like, at the time of sending.

At step 802, the bank server generates a transaction record.

The bank server can generate a transaction record for the bank account corresponding to the amount actually transferred out or transferred in by the bank account of the enterprise, wherein the transaction record can contain transaction running water and fund running water information.

In step 803, the bank server stores the transaction record in a chain.

Wherein the bank server may bypass the transaction records by invoking an intelligent contract. Optionally, the uplink data may include serial numbers, service numbers, transaction amounts, etc. of the transaction.

At step 804, the blockchain stores the transaction record.

In step 805, the blockchain returns the address of the transaction record to the bank server.

That is, the blockchain returns an on-chain address of the posted transaction record through which the bank server can query the stored transaction record.

In step 806, the bank server establishes a binding relationship for the address and corresponding transaction record.

That is, the bank server can bind the address returned by the blockchain with the previous transaction record, thereby facilitating later tracing.

In step 807, the bank server generates statement of account on a periodic basis.

The bank server may collect monthly, quarterly, semi-annual and annual statement according to the period, and the specific period may be determined between the enterprise and the bank, which is not limited in the present application.

In step 808, the bank server stores the statement in the uplink.

The bank server can store the transaction amount of the statement, the balance, the hash value of the data and the like in a uplink mode.

In step 809, the bank server sends the statement to the corporation.

At step 810, the bank server sends notification information to the corporation.

Alternatively, the bank side may notify the enterprise operator to check out by sending notification information. Alternatively, the notification information may be notified to the enterprise by a short message, a telephone, or the like.

In step 811, the enterprise checks out.

The staff of the enterprise performs online checking. The staff of the enterprise can check the transaction record of the enterprise to the bank account number with the statement sent by the bank server, and compile a bank deposit balance adjustment table to finish checking.

At step 812, the enterprise returns the reconciliation result to the bank server.

The enterprise returns the check result to the bank server.

Step 813, the bank server stores the reconciliation result in a uplink manner.

Alternatively, the bank server may store the reconciliation result on the blockchain through the smart contract.

In addition, the application establishes a public transparent trust mechanism based on the characteristics of block chain decentralization, distributed storage, non-falsification and the like, optimizes the reconciliation process of banks and enterprises, reduces the labor and time costs of the banks and the enterprises, improves the timeliness and accuracy of reconciliation, and prevents the risk of serial investigation between the banks and the enterprises. The method lays a good foundation for digitizing and credible enterprise assets, and can finally solve the problems of difficult financing and expensive financing of middle and small enterprises.

Referring to fig. 9, a schematic structural diagram of a system frame according to an exemplary embodiment of the present application is shown in fig. 8. As shown in fig. 9, a user module 901, a banking module 902, an intelligent contract 903, and a blockchain 904 are included.

The user module 901 may be configured to store a transaction record and the like when a payment transaction occurs in a bank account of an enterprise, and the user module 901 may be further configured to receive a statement sent by the bank service module 902, perform reconciliation processing, and return a reconciliation result to the bank service module 902.

The bank service module 902 may include an enterprise recording module 902a and an enterprise reconciliation module 902b, where the enterprise recording module 902a may record a transaction record when a payment transaction occurs with a bank account of an enterprise, and send an uplink storage request for the transaction record to the intelligent contract 903; the enterprise reconciliation module 902b may generate a statement, send the generated statement to the user module 901, receive the reconciliation result returned by the user module 901, and send a request for uplink storage of the reconciliation result to the intelligent contract 903.

The smart contracts 903 may include a billing contract 903a and a reconciliation contract 903b, the banking service module 902 may invoke the billing contract 903a to store the transaction record in a chain, and the banking service module 902 may invoke the reconciliation contract 903b to store the reconciliation result in a chain. The banking module 902 may also store interaction data (such as notification information) needed in the reconciliation process in a chain through the smart contract 903.

Blockchain 904 may be used to store the smart contract 903 invoked by banking module 902 and return a storage address or the like to banking module 902.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Fig. 10 is a block diagram illustrating a block chain based data management apparatus according to an exemplary embodiment of the present application. The blockchain-based data management device may be used in the server shown in fig. 1 to perform all or part of the steps of the methods shown in the corresponding embodiments of fig. 4, 5, or 8. The blockchain-based data management device may include the following modules:

a transfer record obtaining module 1001, configured to obtain a resource transfer record of a first account in a blockchain;

the check list generation module 1002 is configured to generate a resource transfer check list according to a resource transfer record of the first account in the blockchain, where the resource transfer check list includes the resource transfer record of the first account;

a check list sending module 1003, configured to send the resource transfer check list to a target user, where the target user is a user to whom the first account belongs;

And the checking result storage module 1004 is configured to receive a checking result of the target user on the resource transfer checking table, and store the checking result into the blockchain.

Optionally, the transfer record obtaining module 1001 is configured to obtain, from the blockchain, the resource transfer record in a first period of time when or after a preset time node arrives, where the first period of time is any period of time before the preset time node;

the check table generating module 1001 is configured to generate the resource transfer check table in the first period according to the resource transfer record in the first period.

Optionally, the apparatus further includes:

Optionally, the first account is a bank account.

It should be noted that: in the device provided in the above embodiment, when the steps are executed, only the division of the functional modules is used for illustration, in practical application, the functional allocation may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the apparatus provided in the above embodiment and the method embodiment of the block chain-based data management method are the same conception, and detailed implementation processes of the apparatus are referred to in the method embodiment, and are not repeated herein.

Fig. 11 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application. The computer apparatus 1100 includes a central processing unit (Central Processing Unit, CPU) 1101, a system memory 1104 including a random access memory (random access memory, RAM) 1102 and a Read Only Memory (ROM) 1103, and a system bus 1105 connecting the system memory 1104 and the central processing unit 1101. The computer device 1100 also includes a basic input/output system (Input output system, I/O system) 1106, which helps to transfer information between the various devices within the computer, and a mass storage device 1107 for storing an operating system 1112, application programs 1113, and other program modules 1114.

The basic input/output system 1106 includes a display 1108 for displaying information and an input device 1109, such as a mouse, keyboard, etc., for a user to input information. Wherein the display 1108 and the input device 1109 are both coupled to the central processing unit 1101 through an input-output controller 1110 coupled to the system bus 1105. The basic input/output system 1106 may also include an input/output controller 1110 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, the input output controller 1110 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 1107 is connected to the central processing unit 1101 through a mass storage controller (not shown) connected to the system bus 1105. The mass storage device 1107 and its associated computer-readable media provide non-volatile storage for the computer device 1100. That is, the mass storage device 1107 may include a computer-readable medium (not shown) such as a hard disk or CD-ROM drive.

The computer readable medium may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other solid state Memory technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc, high density digital video disc) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage medium is not limited to the one described above. The system memory 1104 and mass storage device 1107 described above may be collectively referred to as memory.

The computer device 1100 may connect to the internet or other network device through a network interface unit 1111 connected to the system bus 1105.

The memory further includes one or more programs stored in the memory, and the central processor 1101 implements all or part of the steps of the method provided by the above embodiments of the present application by executing the one or more programs.

In one exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as a memory, including a computer program (instructions) executable by a processor of a computer device to perform all or part of the steps of the methods shown in the various embodiments of the application. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method of blockchain-based data management, the method performed by a server, the method comprising:

generating a first resource transfer record of a first account in response to resource transfer of a target user through the first account, wherein the target user is a user to which the first account belongs, and the first resource transfer record is generated when the first account is subjected to resource transfer at any time;

storing the first resource transfer record into the blockchain;

receiving a first record address corresponding to the first resource transfer record returned by the blockchain, wherein the first record address is an address of the first resource transfer record stored in the blockchain;

storing a correspondence between the first record address and the first resource transfer record locally; when the first resource transfer record is inquired, inquiring the first resource transfer record according to the first record address;

When or after a preset time node arrives, acquiring a resource transfer record of the first account in a first time period from the blockchain, wherein the first time period is any time period before the preset time node;

generating a resource transfer check table in the first time period according to the resource transfer record in the first time period, wherein the resource transfer check table comprises the resource transfer record in the first time period;

storing the resource transfer check table into the blockchain;

sending the resource transfer check list to the target user, and sending a prompt message to the target user, wherein the prompt message is used for indicating that the server has sent the resource transfer check list to the target user so as to remind the target user to check the resource transfer check list;

storing the hint message into the blockchain;

2. The method according to claim 1, wherein the method further comprises:

storing a first record address corresponding to the first resource transfer record on the blockchain;

And establishing a corresponding relation between the first record address and the first resource transfer record, and storing the corresponding relation on the blockchain.

3. The method of claim 1, wherein storing the resource transfer check table into the blockchain comprises:

and storing the resource transfer quantity, the resource residual quantity and the resource hash value of the resource transfer check table into the blockchain.

4. A method according to any one of claims 1 to 3, wherein the first account number is a bank account number.

5. A blockchain-based data management device for use in a server, the device comprising:

the record storage module is used for responding to the resource transfer of a target user through a first account, generating a first resource transfer record of the first account, wherein the target user is the user to which the first account belongs, and the first resource transfer record is generated when the first account is subjected to resource transfer at any time; storing the first resource transfer record into the blockchain;

the address storage module is used for receiving a first record address corresponding to the first resource transfer record returned by the blockchain, wherein the first record address is an address of the first resource transfer record stored in the blockchain; storing a correspondence between the first record address and the first resource transfer record locally; when the first resource transfer record is inquired, inquiring the first resource transfer record according to the first record address;

The transfer record acquisition module is used for acquiring a resource transfer record of the first account in a first time period from the blockchain when or after a preset time node arrives, wherein the first time period is any time period before the preset time node;

the check list generation module is used for generating a resource transfer check list in the first time period according to the resource transfer record in the first time period, wherein the resource transfer check list comprises the resource transfer record in the first time period;

the data storage module is used for storing the resource transfer check table into the blockchain;

the check list sending module is used for sending the resource transfer check list to the target user and sending a prompt message to the target user, wherein the prompt message is used for indicating that the server has sent the resource transfer check list to the target user so as to remind the target user to check the resource transfer check list;

the data storage module is further used for storing the prompt message into the blockchain;

6. A computer device comprising a processor and a memory, wherein the memory has stored therein at least one program that is loaded and executed by the processor to implement the blockchain-based data management method of any of claims 1 to 4.

7. A computer readable storage medium having stored therein at least one program loaded and executed by a processor to implement the blockchain-based data management method of any of claims 1 to 4.