WO2021208762A1

WO2021208762A1 - Data storage and query

Info

Publication number: WO2021208762A1
Application number: PCT/CN2021/085224
Authority: WO
Inventors: 李睿
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2020-04-13
Filing date: 2021-04-02
Publication date: 2021-10-21
Also published as: CN111538757A; CN111538757B

Abstract

Provided in the embodiments of the present description are a data storage method and apparatus, a data query method and apparatus, a server, and a medium. The storage method comprises: first detecting the type of transaction data; and if the data is first-type transaction data, it being necessary to first determine a target storage node, that matches the transaction data, in a blockchain, then store the transaction data in a private ledger of the target storage node, and then store digest information, generated by encrypting the transaction data, in other storage nodes in the blockchain to ensure the authenticity of the stored data while ensuring the privacy of storage of the first-type transaction data; and if the data is second-type transaction data, storing the transaction data in a public ledger of any storage node in the blockchain. The unified and automatic storage of the first-type transaction data and the second-type transaction data is realized.

Description

Data storage and query

Technical field

The present invention relates to the field of computer technology, in particular to a data storage method, query method, device, server and storage medium.

Background technique

Related party transactions are a relatively common transaction mode in the management of group companies, and they have developed into a very important factor affecting the financial status and operating results of listed companies. Due to its particularity, on the one hand, supervision and disclosure requirements to prove the authenticity of transaction data, on the other hand, there is a high degree of privacy for important transaction data in the management process, which also puts forward high requirements on the storage of transaction data.

Summary of the invention

The embodiments of this specification provide a data storage method, query method, device, server, and storage medium.

In the first aspect, the embodiments of this specification provide a transaction data storage method for storing transaction data in a blockchain, and each storage node of the blockchain is configured with a private ledger and a public ledger. The method includes: detecting the type of transaction data; if the type of the transaction data is the first type of transaction data, determining a target storage node in the blockchain that matches the transaction data, and storing the transaction data To the private ledger of the target storage node, and store the summary information generated by encrypting the transaction data in the public ledger of other storage nodes in the blockchain; if the type of the transaction data is a second type of transaction Data, the transaction data is stored in the public ledger of each storage node in the blockchain.

In the second aspect, the embodiment of this specification provides a transaction data query method for querying transaction data stored in a blockchain, and each storage node of the blockchain is configured with a private ledger and a public ledger. The method includes: obtaining a transaction query request initiated by a user, and determining the type of target transaction data according to the transaction query request; if the type of the target transaction data is the first type of transaction data, downloading from the blockchain Determine the target storage node storing the target transaction data in the private ledger, and send the transaction query request to the target storage node, so that the target storage node stores the private ledger in the private ledger based on the transaction query request The target transaction data is fed back to the user; if the type of the target transaction data is the second type of transaction data, the transaction query request is sent to any storage node in the blockchain, so that the storage node According to the transaction query request, the target transaction data stored in the public ledger is fed back to the user.

In a third aspect, the embodiments of this specification provide a transaction data storage device for storing transaction data in a blockchain, and each storage node of the blockchain is configured with a private ledger and a public ledger. The device includes: a detection module, used to detect the type of transaction data; a first storage module, used to determine if the type of the transaction data is the first type of transaction data, determine the transaction data in the blockchain The matched target storage node stores the transaction data in the private ledger of the target storage node, and stores the summary information generated by encrypting the transaction data in the public ledger of other storage nodes in the blockchain; The second storage module is configured to store the transaction data in the public ledger of each storage node in the blockchain if the type of the transaction data is the second type of transaction data.

In a fourth aspect, the embodiment of this specification provides a transaction data query device for querying transaction data stored in a blockchain, and each storage node of the blockchain is configured with a private ledger and a public ledger. The device includes: a determining module, configured to obtain a transaction query request initiated by a user, and determine the type of target transaction data according to the transaction query request; a first query module, configured to determine if the type of the target transaction data is the first For transaction data of one type, the target storage node storing the target transaction data in the private ledger is determined from the blockchain, and the transaction query request is sent to the target storage node, so that the target storage The node feeds back the target transaction data stored in the private ledger to the user based on the transaction query request; the second query module is configured to query the transaction if the type of the target transaction data is the second type of transaction data The request is sent to any storage node in the blockchain, so that the storage node feeds back the target transaction data stored in the public ledger to the user according to the transaction query request.

In a fifth aspect, an embodiment of the present specification provides a server, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor executes the above-mentioned first or second aspect. Method steps.

In a sixth aspect, the embodiments of the present specification provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the method described in the first aspect or the second aspect are realized.

The transaction data storage method provided in the embodiment of this specification first detects the type of transaction data. If it is the first type of transaction data, it is necessary to first determine the target storage node in the blockchain that matches the transaction data, and then store the transaction data In the private ledger of the target storage node, the summary information generated by encrypting the transaction data is stored in other storage nodes in the blockchain to ensure the authenticity of the stored data while ensuring the privacy of the first type of transaction data storage If it is the second type of transaction data, the transaction data is stored in the public ledger of any storage node in the blockchain, which realizes the unified and automatic storage of the first type of transaction data and the second type of transaction data. In addition, this solution is highly scalable, and can flexibly classify transaction data according to needs, and configure the target storage node matching the first type of transaction data, so as to facilitate the storage of various transaction data generated by newly-added services .

Correspondingly, the transaction data query method provided by the embodiment of this specification first determines the type of target transaction data through the acquired transaction query request; if it is the first type of transaction data, first determine from the blockchain that the private ledger is stored The target storage node of the target transaction data forwards the transaction query request to the target storage node to obtain the target transaction data stored in its private ledger; if the target transaction data is the second type of transaction data, the transaction query request is forwarded to the district Any storage node in the block chain obtains the target transaction data stored in its public ledger. In this way, configuring the query process for the target transaction data type can meet the user's query requirements for various transaction data. While ensuring the privacy of the first type of transaction data storage, it realizes the unified query of the first type of transaction data and the second type of transaction data. , It is convenient for users to operate.

Description of the drawings

By reading the detailed description of the preferred embodiments below, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only used for the purpose of illustrating the preferred embodiments, and are not considered as a limitation to the present invention. Also, throughout the drawings, the same reference symbols are used to denote the same components. In the attached picture:

Figure 1 is a schematic diagram of an operating environment suitable for the embodiments of this specification;

2 is a flowchart of a method for storing transaction data according to the first aspect of the embodiments of this specification;

3 is a schematic diagram of transaction data storage provided by the first aspect of the embodiments of this specification;

4 is a flowchart of a method for querying transaction data provided by the second aspect of the embodiments of this specification;

5 is a block diagram of a transaction data storage device provided by the third aspect of the embodiments of this specification;

6 is a block diagram of a transaction data query device provided by the fourth aspect of the embodiments of this specification;

Fig. 7 is a schematic diagram of a server provided by the fifth aspect of the embodiment of this specification.

Detailed ways

FIG. 1 is a schematic diagram of an operating environment suitable for the data storage method provided by the embodiment of this specification. As shown in FIG. 1, the server 300 is in communication connection with one or more storage nodes in the blockchain 100 (the connection of the three storage nodes shown in FIG. 1 is only for illustration) for data communication or interaction.

Wherein, the server 300 may be a business server, that is, a server where a business system is located, providing transaction services for users, and may receive transaction requests initiated by users through the client, process the transaction requests, and generate transaction data.

The blockchain 100 includes a plurality of storage nodes (only the storage nodes 101 to 106 shown in FIG. 1), and these storage nodes can be connected to each other through a network 200 for data communication or interaction. These storage nodes may be personal computers (Personal Computers, PCs), notebook computers, tablet computers, smart phones, wearable devices, and other devices with network functions and data storage functions. It should be noted that the number of storage nodes in FIG. 1 is only for illustration, and does not limit the specific number of storage nodes included in the blockchain 100. In actual application scenarios, more storage nodes can be included and new storage nodes can be added one after another.

In addition, in the embodiment of this specification, each storage node of the blockchain is configured with a private ledger and a public ledger. Among them, the private ledger is a ledger with access permissions, that is, except for the storage node itself, other storage nodes in the blockchain cannot arbitrarily obtain transaction data from the storage node's private ledger. Correspondingly, the public ledger is a ledger without access rights, which is a ledger open to any storage node in the blockchain, and any other storage node can obtain transaction data from the public ledger of the storage node.

The transaction data storage method provided in the embodiments of this specification can be applied to the business server in the above system. On the one hand, through the structural design of private and public ledgers in the storage nodes, the public information shared between nodes is used to ensure the authenticity of transactions that cannot be tampered with. At the same time, the private ledger is used to share only the summary information generated by encrypting the transaction data between non-target storage nodes to ensure the privacy of the stored transaction data of the first type; on the other hand, the transaction data type is uniformly identified, and then the different types are automatically entered The on-chain storage process realizes the unified and automatic storage of the first type of transaction data and the second type of transaction data, which has stronger applicability and scalability, and can flexibly classify transaction data according to needs, as well as the second type of transaction data. One type of transaction data matching target storage node is configured to facilitate the storage of various transaction data generated by newly-added services.

Further, the embodiment of this specification also provides a transaction data query method, which can also be applied to the business server in the above-mentioned system for querying private ledgers and public ledgers stored in each storage node of the blockchain through the above-mentioned storage method. By configuring the query process for the target transaction data type, it can meet the user's query requirements for various transaction data. While ensuring the privacy of the first type of transaction data storage, it can realize the first type of transaction data and the second type of transaction. The unified query of data is convenient for users to operate.

In order to better understand the above technical solutions, the technical solutions of the embodiments of this specification are described in detail below through the drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are of the technical solutions of the embodiments of this specification. The detailed description is not a limitation on the technical solution of this specification. The embodiments of this specification and the technical features in the embodiments can be combined with each other if there is no conflict. In the embodiments of this specification, the term "plurality" means "two or more", that is, two or more than two are included.

In the first aspect, the embodiments of this specification provide a transaction data storage method for storing transaction data in a blockchain, and each storage node of the blockchain is configured with a private ledger and a public ledger. As shown in Figure 2, the method includes the following steps S201 to S203.

Step S201: Detect the type of transaction data.

Among them, the transaction data to be detected is the transaction data that needs to be stored. When the business system in the business server detects that a transaction occurs, for example, when the transaction is created or the transaction is completed, the transaction data generated based on the transaction request triggered by the user can be obtained. The content of the specific transaction data is determined according to the business type of the actual application scenario.

In the embodiment of this specification, the transaction data may be related transaction data. Among them, related party transactions refer to any behavior or transaction that transfers resources, labor services, or obligations between related parties, regardless of whether the price is charged or not. According to the type of transaction, common related transactions fall into the following categories: purchase or sale of goods, equity investment, provision or acceptance of labor services, provision of funds, research and development transfer, key management compensation, etc. Of course, in other embodiments of this specification, it may also be other types of transaction data, which is not limited here.

Specifically, the types of transaction data may include the first type of transaction data and the second type of transaction data. Among them, the first type of transaction data is important and private transaction data that needs to be stored confidentially, and the second type of transaction data is transaction data that can be made public.

As an implementation manner, the above process of detecting the type of transaction data may include: extracting business feature information from the transaction data; judging whether the business feature information of the transaction data meets preset private storage conditions, and if so, determining the type of transaction data It is the first type of transaction data. If not, the type of the transaction data is determined to be the second type of transaction data. Among them, the preset private storage condition is a condition for performing privacy detection on transaction data.

Among them, the service feature information and the preset private storage conditions can be set according to the needs of actual application scenarios. For example, the business characteristic information may include, but is not limited to, one or more of the business type to which the transaction belongs, the transaction amount, the transaction object, and the contract attribute of the transaction. Among them, the business type and contract attributes can be specifically determined according to actual application scenarios. For example, the type of business can include acquiring fee business, profit sharing business, and interest discount business, etc. The contract attributes of the transaction may include the nature of the contract, such as a major transaction or ordinary transaction, the source of the contract, such as from the first contracting platform or the second contracting platform, and the pricing strategy, such as related party pricing or ordinary transaction pricing.

For example, in an application scenario, a related transaction occurs between the first business platform and the second business platform. At this time, the business characteristic information includes the transaction amount, pricing strategy, and business type. Judging whether the business characteristic information of the transaction data meets the preset private storage conditions can be based on the size of the transaction amount. If the transaction amount exceeds 100 million, it is determined that the transaction data meets the preset private storage conditions, otherwise it does not; or, it may be According to the pricing strategy, if the related party preferential rate, it is determined that the transaction data meets the preset private storage condition, otherwise it does not meet; or, it can be a combination of multiple conditions. If the transaction amount exceeds 100 million and the related party If the preferential rate is applied, it is determined that the transaction data meets the preset private storage conditions, and vice versa.

In the specific implementation process, transaction data can be flexibly divided into types according to needs. In this way, for each transaction data generated by a newly-added service, the storage method provided in the embodiment of this specification can also be applied without spending a lot of resources to reconfigure the newly-added transaction data. The on-chain storage process of transaction data generated by the business is highly scalable.

Step S202: If the type of transaction data is the first type of transaction data, determine the target storage node in the blockchain that matches the transaction data, store the transaction data in the private ledger of the target storage node, and encrypt the transaction data to generate The summary information of is stored in the public ledger of other storage nodes in the blockchain.

Step S203: If the type of the transaction data is the second type of transaction data, store the transaction data in the public ledger of each storage node in the blockchain.

It is understandable that the private ledgers of each storage node are set with strict permissions. Access to the private ledgers and access to the transaction data stored in the private ledgers require permission detection. Any storage node in the blockchain has no right to access other storage. The private ledger of the node, in contrast, the public ledger in any storage node in the blockchain is open and transparent to other storage nodes in the blockchain, and each storage node in the blockchain can access the public ledger mutually.

For the first type of transaction data, in order to ensure the privacy of the stored first type of transaction data, the transaction data of this type needs to be stored in the private ledger of the storage node matching the transaction data in the blockchain. Prior to this, it is necessary to determine the target storage node matching the transaction data from the storage nodes of the blockchain, specifically determining the target storage node from the storage nodes that are in communication with the business server in the blockchain. In the embodiment of this specification, the target storage node of the first type of transaction data may be one or multiple. In the specific implementation process, the target storage node matching the first type of transaction data can be flexibly configured according to needs, which is also convenient to realize the storage of various types of transaction data generated by new services, so that the storage provided by the embodiment of this specification Method specific and strong scalability.

As an implementation manner, the foregoing process of determining the target storage node in the blockchain that matches the transaction data may include: obtaining business attribute information of the transaction data; business attribute information according to the transaction data, and The preset mapping relationship between the storage node and the business attribute information determines the target storage node that matches the transaction data.

The business server is pre-configured with a mapping relationship between business attribute information and storage nodes in the blockchain. The business attribute information is determined according to actual application scenarios, and may include, but is not limited to, one or more combinations of business type, transaction amount, and contract type, for example. Among them, the transaction contract type can be determined according to actual application scenarios, for example, it can include, but is not limited to: equity investment contracts, financing contracts, and transaction contracts. Of course, in addition to the above information, the business attribute information may also include other information, such as transaction level, transaction object, and so on. The transaction level refers to the confidentiality level pre-configured for all transactions. The transaction object is the counterparty of the transaction, such as a bank or a network platform.

For example, in an application scenario, the business attribute information can include the size of the transaction amount. In this case, the range can be divided according to the amount. If the transaction amount is less than 1 million, it is stored in nodes A, B, and C; the transaction amount is 1 million- 100 million is stored in nodes D, E, and F; if the transaction amount exceeds 100 million, it is stored in nodes G and H.

In an optional embodiment, the mapping relationship between the service attribute information and the storage node in the blockchain that is communicatively connected with the service server may be pre-configured. For example, if the service server is in communication connection with 10 storage nodes in the blockchain, the mapping relationship between the service attribute information and the 10 storage nodes can be pre-configured and stored, and then, according to the mapping relationship, from the 10 storage nodes The storage node determines the target storage node of the current transaction data.

Of course, in other embodiments of this specification, the mapping relationship between service attribute information and all storage nodes in the blockchain can also be pre-configured and stored. In this way, in some application scenarios, if the target storage node can also include Storage nodes other than the storage node connected in communication with the server are transferred from the storage node in communication connection with the business server to the private ledger of the target storage node for storage.

In addition, for the second type of transaction data, since the second type of transaction data does not need to be stored confidentially, any storage node in the blockchain that is communicatively connected with the business server can be used as the target storage node. The transaction data is sent to the storage node and stored in the local public ledger, and the storage node broadcasts the transaction data to the rest of the storage nodes in the blockchain, so that other storage nodes store the transaction data in their respective public In the ledger, the shared storage of the second type of transaction data in all storage nodes of the blockchain is realized. Since each block in the blockchain stores the digest value of this block and the digest value of the adjacent block, once the transaction data is tampered with, the digest value will not match the data recorded in the public ledger, which can effectively Ensure the authenticity of transaction data.

In an optional embodiment, after determining the type of transaction data, the service server may mark the type label of the transaction data. The type tag is used to uniquely identify the type of the transaction data, that is, to indicate whether the transaction data is the first type of transaction data or the second type of transaction data. Furthermore, after determining the target storage node, the service server can send the transaction data carrying the type label to the target storage node, thereby facilitating the storage node to determine the transaction data type to be stored, and perform the corresponding storage process according to the transaction data type.

At this time, after the target storage node receives the transaction data, it can determine whether the transaction data is the first type of transaction data or the second type of transaction data according to the type label carried by the transaction data. If it is the first type of transaction data, store the transaction data in the local private ledger, encrypt the transaction data, and broadcast the encrypted summary information to other storage nodes in the blockchain except the target storage node , Enabling these storage nodes to store the encrypted digest value of the transaction data in their respective public ledgers. Among them, there may be multiple ways to encrypt the transaction data. For example, a hash function may be used to encrypt the transaction data, and the output value may be used as the summary information generated by encrypting the transaction data. If it is the second type of transaction data, store the transaction data in the local public ledger, and broadcast the transaction data to the rest of the storage nodes in the blockchain except the target storage node, thereby sharing the transaction data to the rest of the storage In the public ledger of the node.

For example, as shown in Figure 3, in a certain application scenario, there are transaction data TX1, TX2, and TX3. After the detection in step 201, the transaction data TX1 is the second type of transaction data, and the transaction data TX2 and TX3 are the second type of transaction data. One type of transaction data. Storage nodes A, B, and C are all nodes in the blockchain, and they are all configured with public ledgers and private ledgers. Wherein, storage nodes A and C are both target storage nodes that match the transaction data TX2, then the transaction data TX2 is stored in the private ledger of the storage nodes A and C, and the digest (Tx2) generated by encrypting the transaction data TX2 is broadcast To be stored in the public ledger of other storage nodes in the blockchain. Storage nodes B and C are both target storage nodes that match the transaction data TX3, then the transaction data TX3 is stored in the private ledger of the storage nodes B and C, and the digest (Tx3) generated by encrypting the transaction data TX3 is broadcast to the district It is stored in the public ledger of other storage nodes in the block chain. The transaction data TX1 is stored in the public ledger of each storage node in the blockchain.

In other words, the first type of transaction data is only visible on the private ledger of the target storage node, but the digest (Tx2) and digest (Tx3) in the figure above will be distributed and stored in all nodes. On the public ledger. Relying on the summary value alone, it is impossible to reverse the specific transaction data, and since the summary value is recorded at each node, if the private ledger data is tampered with, the summary value will not match. Therefore, the privacy requirements of data storage can be met while ensuring the authenticity of the data.

In the second aspect, the embodiments of this specification provide a transaction data query method for querying transaction data stored in the blockchain, specifically for querying transaction data stored in accordance with the transaction data storage method provided by any embodiment of the first aspect. Transaction data. Among them, each storage node of the blockchain is configured with private ledgers and public ledgers. As shown in Fig. 4, the method includes the following steps S401 to S403.

Step S401: Obtain a transaction query request initiated by the user, and determine the type of target transaction data according to the transaction query request.

For example, the user can input or select the query conditions of the target transaction data to be queried through the transaction query interface set in the client corresponding to the business server, and after triggering the transaction query, generate a transaction query based on the query conditions entered by the user ask. For example, the query conditions may include, but are not limited to, one or more combinations of index items such as transaction object, transaction amount, and transaction time.

As an implementation manner, the foregoing process of determining the type of target transaction data according to the transaction query request may include: obtaining the business characteristic information of the target transaction data according to the transaction query request; judging whether the business characteristic information meets the preset private storage condition, if so , The type of the target transaction data is determined as the first type of transaction data, if not, the type of the target transaction data is determined as the second type of transaction data, wherein the preset private storage condition is used to privately store the target transaction data The conditions for sex testing.

For example, after receiving the transaction query request, the business server can parse the transaction query request to obtain the business characteristic information of the target transaction data. For example, the transaction query request may include the business characteristic information of the target transaction data to be queried, and in this case, the business characteristic information of the target transaction data may be extracted from the transaction query request.

It should be noted that the specific content of the service feature information and the type judgment process after the service feature information is obtained are similar to the foregoing storage method embodiment. For details, please refer to the corresponding description in the foregoing method embodiment provided in the first aspect. Go into details again.

As another embodiment, the transaction query request may include the query conditions entered by the user. After the business server parses the query conditions of the target transaction data from the transaction query request, it can match the requirements in the preset transaction database according to the query conditions. For the target transaction data to be queried, the transaction database records the key information of the transaction data generated by the business server, where the key information may include the type of the transaction data. In this way, the type of target transaction data to be queried can be found in the transaction database according to the query conditions.

Step S402: If the type of the target transaction data is the first type of transaction data, the target storage node storing the target transaction data in the private ledger is determined from the blockchain, and the transaction query request is sent to the target storage node, so that the target The storage node feeds back the target transaction data stored in the private ledger to the user based on the transaction query request.

It should be noted that the target transaction data to be queried is stored according to the transaction data storage method provided in the first aspect above. If it is determined according to the above step S401 that the target transaction data is the first type of transaction data, then the target transaction data is stored in the private ledger of the target storage node matching the target transaction data in the blockchain, and other storage nodes in the blockchain Only the summary information generated by encrypting the target transaction data is stored in the public ledger. Therefore, it is necessary to determine the target storage node of the target transaction data first, and obtain the target transaction data from the private ledger of the target storage node.

As an implementation manner, the process of determining the target storage node storing the target transaction data in the private ledger from the blockchain may include: obtaining the business attribute information of the target transaction data according to the transaction query request; according to the business attribute information, and the zone The preset mapping relationship between storage nodes and business attribute information in the block chain determines the target storage node that stores the target transaction data in the private ledger.

For example, by analyzing the transaction query request, the business attribute information of the target transaction data can be obtained. For example, the transaction query request may contain the business attribute information of the target transaction data to be queried. In this case, the business attribute information of the target transaction data can be extracted from the transaction query request.

It should be noted that the specific content of the business attribute information and the process of determining the target storage node after the business attribute information is obtained are similar to the foregoing storage method embodiment. For details, reference may be made to the corresponding description in the method embodiment provided in the first aspect. I won't repeat them here.

As another embodiment, the transaction query request may include the query conditions entered by the user. After the business server parses the query conditions of the target transaction data from the transaction query request, it can match the requirements in the preset transaction database according to the query conditions. For the queried target transaction data, the transaction database records the key information of the transaction data generated by the business server, where the key information may include the target storage node that matches the transaction data determined in the storage process. In this way, the target storage node that stores the target transaction data in the private ledger can be found in the transaction database according to the query conditions.

After the target storage node is determined, the transaction query request can be sent to the target storage node. The target storage node can then feed back the target transaction data stored in the private ledger to the user based on the transaction query request. It should be noted that there can be one or more target storage nodes determined. If there are multiple target storage nodes, the transaction query request can be sent to each target storage node, and each target storage node returns its private ledger. Target transaction data stored in.

In order to ensure the privacy of the transaction data stored in the private ledger of the storage node, in an optional embodiment, if the target transaction data to be queried is the first type of transaction data, the business server needs to first before forwarding the transaction query request Perform permission verification on the user to determine whether the user has the permission to query the target transaction data, if so, forward the transaction query request to the target storage node, if not, end the local query and return an error message. For example, a whitelist or a pre-appointed key can be configured in the business server for the private ledger of each storage node. If the user is in the whitelist or the user provides the pre-appointed key, it is determined that the user passes Permission Validation.

In an optional embodiment, the storage node may also set access permissions for the private ledger. If the target transaction data is the first type of transaction data, the business server needs to carry the permission information when forwarding the transaction query request to the target storage node After the storage node receives the transaction query request, when it determines that the target transaction data to be queried is the data stored in the private ledger according to the transaction query request, it needs to verify the authority information carried in the transaction query request. If the verification is passed, then query according to the transaction Request to find the target transaction data from the private ledger and feed it back to the user. If the verification fails, the transaction query request will not be responded to and the query will be ended. Wherein, the permission information can be pre-configured according to actual application scenarios, for example, it can be a pre-appointed key. This helps avoid leakage of transaction data in the private ledger, and further ensures the privacy of the transaction data stored in the private ledger.

Step S403: If the type of the target transaction data is the second type of transaction data, the transaction query request is sent to any storage node in the blockchain, so that the storage node stores the target transaction data in the public ledger according to the transaction query request. Feedback to users.

Since the second type of transaction data is the transaction data shared by all storage nodes in the blockchain, it can be obtained from the public ledger of any storage node in the blockchain. Therefore, after determining that the target transaction data is the second type of transaction data, the business server can forward the transaction query request to any storage node in the blockchain, specifically, it can be forwarded to the storage node in the blockchain that is in communication with the business server Any storage node in.

When the storage node receives the transaction query request and determines that the target transaction data to be queried is transaction data stored in the public ledger according to the transaction query request, it will feed back the target transaction data stored in the public ledger to the user according to the transaction query request.

Further, in order to ensure that the transaction data queried by the user is true and reliable, in an optional embodiment, in the above step S402 and step S403, the storage node may first report the target transaction data before feeding back the target transaction data to the user. Perform tamper-proof verification, which can specifically verify that the encrypted digest value of the locally stored target transaction data is consistent with the digest value stored in other storage nodes. If they are consistent, it means that the locally stored target transaction data is true and reliable, and it will be stored locally. The target transaction data is fed back to the user. If it is inconsistent, it means that the locally stored target transaction data may have been tampered with, the query fails, and an error message is returned.

The transaction data query method provided by the embodiments of this specification can meet the user's query requirements for various transaction data, realize the unified query of the first type of transaction data and the second type of transaction data, facilitate user operations, and can not only ensure the transactions found The authenticity of the data can ensure the privacy of the transaction data in the private ledger, and at the same time facilitate the query of the transaction data in the private ledger.

In the third aspect, the embodiment of this specification provides a transaction data storage device, which can be run in a business server for storing transaction data in a blockchain, and each storage node of the blockchain is configured with Private ledgers and public ledgers. Please refer to FIG. 5, the storage device 50 includes: a detection module 51 for detecting the type of transaction data; a first storage module 52 for determining the area if the type of the transaction data is the first type of transaction data The target storage node matching the transaction data in the block chain stores the transaction data in the private ledger of the target storage node, and stores the summary information generated by encrypting the transaction data in the block chain In the public ledger of other storage nodes; the second storage module 53 is used to store the transaction data in the public account of each storage node in the blockchain if the type of the transaction data is the second type of transaction data In the ledger.

In an optional embodiment, the aforementioned detection module 51 includes: an extraction sub-module 511, configured to extract business characteristic information in the transaction data; and a judging sub-module 512, configured to determine whether the business characteristic information meets the requirements Set private storage conditions, if yes, determine the type of the transaction data as the first type of transaction data, if not, determine the type of the transaction data as the second type of transaction data, wherein the preset private storage The condition is the condition used to check the privacy of the transaction data.

In an optional embodiment, the above-mentioned first storage module 52 is configured to: obtain the business attribute information of the transaction data; The mapping relationship determines the target storage node that matches the transaction data.

Regarding the above device, the specific functions of each module have been described in detail in the method embodiments provided in the first aspect of the embodiments of this specification, and will not be elaborated here. For the specific implementation process, please refer to the method provided in the first aspect. Examples.

In the fourth aspect, the embodiment of this specification provides a transaction data query device, which can run in a business server for querying transaction data stored in a blockchain, and each storage node of the blockchain is configured with Private ledgers and public ledgers. Please refer to FIG. 6, the query device 60 includes:

The determining module 61 is configured to obtain a transaction query request initiated by the user and determine the type of target transaction data according to the transaction query request; the first query module 62 is configured to determine if the type of the target transaction data is the first type of transaction Data, the target storage node storing the target transaction data in the private ledger is determined from the blockchain, and the transaction query request is sent to the target storage node, so that the target storage node is based on the The transaction query request feeds back the target transaction data stored in the private ledger to the user; the second query module 63 is configured to send the transaction query request if the type of the target transaction data is the second type of transaction data To any storage node in the blockchain, so that the storage node feeds back the target transaction data stored in the public ledger to the user according to the transaction query request.

In an optional embodiment, the above-mentioned determining module 61 includes: an obtaining sub-module 611, configured to obtain business characteristic information of the target transaction data according to the transaction query request; and a judging sub-module 612, configured to determine the business Whether the characteristic information meets the preset private storage condition, if so, the type of the target transaction data is determined as the first type of transaction data, if not, the type of the target transaction data is determined as the second type of transaction data, wherein , The preset private storage condition is a condition for performing privacy detection on the target transaction data.

In an optional embodiment, the above-mentioned first query module 62 is configured to: obtain the business attribute information of the target transaction data according to the transaction query request; according to the business attribute information, and the storage nodes in the blockchain and The preset mapping relationship of the business attribute information determines the target storage node where the target transaction data is stored in the private ledger.

Regarding the above device, the specific functions of each module have been described in detail in the method embodiment provided in the second aspect of the embodiments of this specification, and will not be elaborated here. For the specific implementation process, please refer to the method provided in the above second aspect. Examples.

In the fifth aspect, based on the same inventive concept as the previous embodiment, the embodiment of this specification also provides a server, as shown in FIG. When executing the program, the processor 702 implements the steps of any embodiment of the transaction data storage method provided in the first aspect or any implementation of the transaction data query method provided in the second aspect Example steps.

Wherein, in FIG. 7, the bus architecture (represented by a bus 700), the bus 700 may include any number of interconnected buses and bridges, and the bus 700 will include one or more processors represented by the processor 702 and a memory 704 represented by The various circuits of the memory are linked together. The bus 700 may also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein. The bus interface 705 provides an interface between the bus 700 and the receiver 701 and transmitter 703. The receiver 701 and the transmitter 703 may be the same element, that is, a transceiver, which provides a unit for communicating with various other devices on the transmission medium. The processor 702 is responsible for managing the bus 700 and general processing, and the memory 704 may be used to store data used by the processor 702 when performing operations.

It is understandable that the structure shown in FIG. 7 is only for illustration, and the server provided in the embodiment of this specification may also include more or less components than those shown in FIG. 7 or have a different configuration from that shown in FIG. 7. Each component shown in FIG. 7 can be implemented by hardware, software, or a combination thereof.

In the sixth aspect, based on the same inventive concept as the previous embodiment, the embodiment of this specification also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the first aspect described above is realized. The steps of any embodiment of the transaction data storage method provided or the steps of any embodiment of the transaction data query method provided in the second aspect are provided.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than in the embodiments and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown in order to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

This specification is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present invention.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. In this way, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

A method for storing transaction data is used to store transaction data in a block chain, each storage node of the block chain is configured with a private ledger and a public ledger, and the method includes:

Detect the type of transaction data;

If the type of the transaction data is the first type of transaction data, determine the target storage node in the blockchain that matches the transaction data, and store the transaction data in the private ledger of the target storage node, And storing the summary information generated by encrypting the transaction data in the public ledger of other storage nodes in the blockchain;

If the type of the transaction data is the second type of transaction data, the transaction data is stored in the public ledger of each storage node in the blockchain.
The method according to claim 1, wherein said detecting the type of transaction data comprises:

Extract business feature information from the transaction data;

Determine whether the business feature information meets the preset private storage conditions, if yes, determine the type of the transaction data as the first type of transaction data, if not, determine the type of the transaction data as the second type of transaction data , Wherein, the preset private storage condition is a condition for performing privacy detection on transaction data.
The method according to claim 1, wherein the determining a target storage node in the blockchain that matches the transaction data includes:

Obtaining business attribute information of the transaction data;

According to the business attribute information and the preset mapping relationship between the storage node and the business attribute information in the blockchain, a target storage node that matches the transaction data is determined.
A transaction data query method for querying transaction data stored in a block chain, each storage node of the block chain is configured with a private ledger and a public ledger, and the method includes:

Obtain the transaction query request initiated by the user, and determine the type of target transaction data according to the transaction query request;

If the type of the target transaction data is the first type of transaction data, the target storage node storing the target transaction data in the private ledger is determined from the blockchain, and the transaction query request is sent to the A target storage node, so that the target storage node feeds back the target transaction data stored in the private ledger to the user based on the transaction query request;

If the type of the target transaction data is the second type of transaction data, the transaction query request is sent to any storage node in the blockchain, so that the storage node stores the public ledger in the public ledger according to the transaction query request. The stored target transaction data is fed back to the user.
The method according to claim 4, wherein the determining the type of target transaction data according to the transaction query request comprises:

Obtain the business characteristic information of the target transaction data according to the transaction query request;

Determine whether the business feature information meets the preset private storage conditions, if yes, determine the type of the target transaction data as the first type of transaction data, if not, determine the type of the target transaction data as the second type Transaction data, wherein the preset private storage condition is a condition for performing privacy detection on the target transaction data.
The method according to claim 4, wherein the determining from the blockchain the target storage node storing the target transaction data in the private ledger comprises:

Obtain the business attribute information of the target transaction data according to the transaction query request;

According to the business attribute information and the preset mapping relationship between the storage node and the business attribute information in the blockchain, the target storage node storing the target transaction data in the private ledger is determined.
A transaction data storage device for storing transaction data in a block chain, each storage node of the block chain is configured with a private ledger and a public ledger, and the device includes:

Detection module, used to detect the type of transaction data;

The first storage module is configured to, if the type of the transaction data is the first type of transaction data, determine a target storage node in the blockchain that matches the transaction data, and store the transaction data in the target In the private ledger of the storage node, and storing the summary information generated by encrypting the transaction data in the public ledger of other storage nodes in the blockchain;

The second storage module is configured to store the transaction data in the public ledger of each storage node in the blockchain if the type of the transaction data is the second type of transaction data.
The device according to claim 7, wherein the detection module comprises:

The extraction sub-module is used to extract business feature information in the transaction data;

The judging sub-module is used to judge whether the business feature information meets the preset private storage conditions, if so, the type of the transaction data is determined as the first type of transaction data, if not, the type of the transaction data is determined It is the second type of transaction data, where the preset private storage condition is a condition for performing privacy detection on the transaction data.
According to the device according to claim 7, the first storage module is used for:

Obtaining business attribute information of the transaction data;

According to the business attribute information and the preset mapping relationship between the storage node and the business attribute information in the blockchain, a target storage node that matches the transaction data is determined.
A transaction data query device for querying transaction data stored in a block chain, each storage node of the block chain is configured with a private account book and a public account book, and the device includes:

The determining module is used to obtain the transaction query request initiated by the user, and determine the type of target transaction data according to the transaction query request;

The first query module is configured to, if the type of the target transaction data is the first type of transaction data, determine from the blockchain the target storage node storing the target transaction data in the private ledger, and compare the Sending a transaction query request to the target storage node, so that the target storage node feeds back the target transaction data stored in the private ledger to the user based on the transaction query request;

The second query module is configured to send the transaction query request to any storage node in the blockchain if the type of the target transaction data is the second type of transaction data, so that the storage node will The transaction query request feeds back the target transaction data stored in the public ledger to the user.
The device according to claim 10, the determining module comprises:

The obtaining sub-module is used to obtain the business characteristic information of the target transaction data according to the transaction query request;

The judging sub-module is used to judge whether the business feature information meets the preset private storage conditions, if so, the type of the target transaction data is determined as the first type of transaction data, if not, the target transaction data is determined to be the first type of transaction data. The type is determined as the second type of transaction data, wherein the preset private storage condition is a condition for performing privacy detection on the target transaction data.
According to the device of claim 10, the first query module is configured to:

Obtain the business attribute information of the target transaction data according to the transaction query request;

According to the business attribute information and the preset mapping relationship between the storage node and the business attribute information in the blockchain, the target storage node storing the target transaction data in the private ledger is determined.
A server includes a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the processor implements the steps of the method according to any one of claims 1 to 6 when the processor executes the program.
A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in any one of claims 1-6.