Data processing method and device, computer device, and storage medium

By registering multiple sub-encrypted resource data storage containers under the encrypted resource data storage container, the problem of difficulty in fine-grained control of the transaction process in the existing technology is solved, and detailed control of the transaction process and reduction of losses are achieved.

CN114493871BActive Publication Date: 2025-11-07TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202210073251.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-09
Publication Date
2025-11-07
Estimated Expiration
2040-09-09

AI Technical Summary

Technical Problem

Existing encrypted resource data storage containers have a one-to-one relationship, making it difficult to perform fine-grained control over transaction processes in specific scenarios.

Method used

Register multiple sub-encrypted resource data storage containers under the encrypted resource data storage container, and execute the business operation of the transaction request by determining the target sub-encrypted resource data storage container.

Benefits of technology

It enables fine-grained control over the transaction process, reducing losses in the event of data breaches involving encrypted resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114493871B_ABST
    Figure CN114493871B_ABST
Patent Text Reader

Abstract

Embodiments of the present application disclose a data processing method and device, computer equipment and a storage medium. The method comprises: obtaining a transaction request, the transaction request comprising a container address of a second encrypted resource data storage container; determining a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container from a plurality of first sub-encrypted resource data storage containers subordinate to a first encrypted resource data storage container; and performing a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container. The present application can be used to control the transaction process in a fine-grained manner.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the Chinese patent application No. 2020109433174, filed on September 9, 2020, entitled "Data processing method and device, computer device and storage medium", the whole content of which is incorporated into the present application by application. TECHNICAL FIELD

[0002] The present application relates to the technical field of computer, in particular to a data processing method and device, computer device and storage medium. BACKGROUND

[0003] The encrypted resource data storage container refers to a storage container address and a private key. The underlying principle of transferring the encrypted resource data using the encrypted resource data storage container is to sign the resource data transfer transaction data with the private key, and broadcast the resource data transfer transaction data to the whole network, so as to complete the transfer of the encrypted resource data on the distributed ledger.

[0004] The existing encrypted resource data storage container and object are in a one-to-one relationship, and each object corresponds to an encrypted resource data storage container. That is, all encrypted resource data of the object is stored in one storage container, which makes it difficult to control the transaction process in a specific scenario in detail when the object performs a transaction. SUMMARY

[0005] The embodiments of the present application provide a data processing method and device, computer device and storage medium, which can control the transaction process in detail.

[0006] The embodiments of the present application provide a data processing method, applied to a first client, wherein the first client registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container. The method comprises:

[0007] Obtaining a transaction request, wherein the transaction request comprises a container address of a second encrypted resource data storage container;

[0008] Determining a target first sub-encrypted resource data storage container from the plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container, which matches the container address of the second encrypted resource data storage container;

[0009] Performing a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.

[0010] The embodiment of the present application provides a data processing device, the data processing device registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers belonging to the first encrypted resource data storage container, and the device comprises:

[0011] An acquisition module is configured to acquire a transaction request, wherein the transaction request comprises a container address of a second encrypted resource data storage container;

[0012] A searching module is configured to determine a target first sub-encrypted resource data storage container matched with the container address of the second encrypted resource data storage container from the plurality of first sub-encrypted resource data storage containers belonging to the first encrypted resource data storage container;

[0013] A first transaction module is configured to perform a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.

[0014] The embodiment of the present application provides a computer device, which comprises a memory and a processor, the memory stores a computer program, and the computer program is executed by the processor to enable the processor to execute the method in each of the above embodiments.

[0015] The embodiment of the present application provides a computer storage medium, which stores a computer program, and the computer program comprises program instructions, and the program instructions are executed by a processor to execute the method in each of the above embodiments.

[0016] The embodiment of the present application provides a computer program product or a computer program, which comprises computer instructions, the computer instructions are stored in a computer readable storage medium, and the computer instructions are executed by a processor of a computer device to execute the method in each of the above embodiments.

[0017] Each object in the present application can not only register an encrypted resource data storage container, but also register a plurality of sub-encrypted resource data storage containers under the encrypted resource data container, when a transaction request is received, the corresponding sub-encrypted resource data storage container can be used for transaction. Through the type refinement of the encrypted resource data storage container, the object can control the transaction process more carefully, and the object can store the encrypted resource data in different sub-encrypted resource data storage containers, even if the encrypted resource data is leaked, the loss can be reduced. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced. Obviously, the accompanying drawings in the following description only represent some embodiments of the present application, and other drawings can also be obtained without creative labor.

[0019] Figure 1 is a schematic diagram of a blockchain network provided by an embodiment of the present application;

[0020] Figures 2a-2f is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0021] Figure 3 is a flowchart of a data processing method provided by an embodiment of the present application;

[0022] Figure 4 is a flowchart of determining a target first sub-encrypted resource data storage container provided by an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of creating an encrypted resource data storage container provided by an embodiment of the present application;

[0024] Figure 6 is a schematic diagram of creating an encrypted resource data storage container provided by an embodiment of the present application;

[0025] Figure 7 is a flowchart of a data processing method provided by an embodiment of the present application;

[0026] Figure 8 is a structural schematic diagram of a data processing apparatus provided by an embodiment of the present application;

[0027] Figure 9 is a structural schematic diagram of a computer device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0028] The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments only represent some embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained without creative labor belong to the scope of protection of the present application.

[0029] Blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer (P2P), consensus mechanism, and encryption algorithm. Blockchain is essentially a decentralized database and a series of data blocks associated using a cryptographic method, each data block containing one or more transaction information for verifying the validity (anti-fake) of the information and generating the next block.

[0030] Please refer to Figure 1 which is a schematic diagram of a blockchain network provided by an embodiment of the present application. Node 1, node 2, node 3, and node 4 can be combined into a blockchain network, each node can store the same blockchain, and the above four nodes can also be referred to as blockchain nodes. Each node can include a hardware layer, an intermediate layer, an operating system layer, and an application layer. It can be understood that the node can include a computer device.

[0031] The above node can be a standalone physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data. The node can also be a smartphone, tablet computer, notebook computer, desktop computer, smart speaker, smart watch, etc., but is not limited thereto. The nodes can be directly or indirectly connected through wired or wireless communication, which is not limited in the present application.

[0032] The application scenario of the data processing method disclosed in the present application is that a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container are registered in an object's encrypted resource data storage container software. When the encrypted resource data storage container software obtains a transaction request containing a container address of a second encrypted resource data storage container, a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container is determined from the plurality of first sub-encrypted resource data storage containers. Subsequently, the encrypted resource data storage container software performs a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.

[0033] Please refer to Figures 2a-2f which is a schematic diagram of a data processing scenario provided by an embodiment of the present application. Figure 2aThe terminal device 10a in the page 10b registers a main electronic wallet in the wallet software in the terminal device 10a, and the wallet address of the main electronic wallet is abcde (the wallet address of each wallet is unique, that is, the wallet address has uniqueness and exclusivity), wherein the wallet address can be regarded as an account, and the transfer-in or transfer-out of resource data needs to know the wallet address; the remaining resource data amount of the main electronic wallet is 100.

[0034] The main electronic wallet has multiple sub-electronic wallets. As shown in the page 10c in the terminal device 10a, Figure 2b The main electronic wallet has two sub-electronic wallets, namely sub-wallet 1 and sub-wallet 2, wherein the balance of the sub-wallet 1 is 40, the address of the sub-wallet 1 is qwert, and the transaction address of the sub-wallet 1 is qazws, that is, the sub-wallet 1 can only conduct transactions with the electronic wallet with the wallet address of qazws. In other words, the object has limited the sub-wallet 1 to only conduct transactions with a certain (or multiple) specific electronic wallet when creating the sub-wallet 1. Of course, the object can modify the transaction address of the sub-wallet 1 at any time, that is, the object can limit the sub-wallet 1 to only conduct transactions with which wallet at any time according to the situation of the object.

[0035] The balance of the sub-wallet 2 is 10, the address of the sub-wallet 2 is rfvtg, and the transaction address of the sub-wallet 2 is plmok, that is, the sub-wallet 2 can only conduct transactions with the electronic wallet with the wallet address of plmok. In other words, the object has limited the sub-wallet 2 to only conduct transactions with a certain (or multiple) specific electronic wallet when creating the sub-wallet 2. Of course, the object can modify the transaction address of the sub-wallet 2 at any time, that is, the object can limit the sub-wallet 2 to only conduct transactions with which wallet at any time according to the situation of the object.

[0036] If the object clicks the button “start transfer” in the page 10b, the object can select the wallet for the current resource data transfer from the main wallet, the sub-wallet 1 and the sub-wallet 2, and input the wallet address of the resource data transfer-in electronic wallet and the transfer resource amount, so as to transfer the resource data from the selected electronic wallet to the resource data transfer-in electronic wallet.

[0037] As shown in the page 10c in the terminal device 10a, Figure 2c The terminal device 10a receives the transaction request 10d sent by the wallet software in the terminal device 10c, wherein the transaction request 10d includes the transfer-in address “plmok” and the transfer amount “5”, in simple terms, the transaction request 10d is a request for the terminal device 10a to transfer the resource data with the resource amount of 5 to the electronic wallet with the address of plmok.

[0038] The terminal device 10a determines the sub-wallet of the transaction address plmok from the sub-wallet 1 and the sub-wallet 2, because the transaction address of the sub-wallet 2 is the same as the transfer-in address in the transaction request 10d. Therefore, the terminal device 10a can determine that the sub-wallet 2 responds to the transaction request 10d.

[0039] As shown in Figure 2d The terminal device 10a generates the transaction data 10e according to the transaction request 10d and the wallet address of the sub-wallet 2, where the transaction data 10e includes the transfer-out address: rfvtg, the transfer-in address: plmok, and the resource transfer amount: 5. It can be known that the transfer-out address is the wallet address of the sub-wallet 2, and the meaning of the transaction data 10e is to transfer the resource data with the amount of 5 from the electronic wallet with the address "rfvtg" to the electronic wallet with the address "plmok".

[0040] The resource data to be transferred is resource data on the blockchain, and the electronic wallet corresponding to the main wallet, the sub-wallet 1, the sub-wallet 2, and the transfer-in address "plmok" in the transaction request 10d are all electronic wallets for managing the resource data on the blockchain, that is, the wallet address of the main wallet, the wallet address of the sub-wallet 1, the wallet address of the sub-wallet 2, and the wallet address of the electronic wallet corresponding to the transfer-in address "plmok" in the transaction request 10d are all transaction addresses on the blockchain.

[0041] As shown in Figure 2d The terminal device 10a sends the generated transaction data 10e to the blockchain network, where the blockchain network includes three nodes, which are node 1, node 2, and node 3. It is assumed that the three nodes are consensus nodes of the blockchain network. The three nodes will all store the blockchain, and Figure 2d It can be seen that the current blockchain includes three blocks.

[0042] The nodes in the blockchain network first determine whether the wallet balance of the sub-wallet 2 is greater than 5, verify whether the signature of the transaction data 10e is correct, and the like. If it is determined that the wallet balance of the sub-wallet 2 is greater than 5, and it is verified that the signature of the transaction data 10e is correct, the nodes in the blockchain network will add the transaction data 10e to the blockchain. Figure 2eAs shown, the node in the blockchain network stores the transaction data 10e into the block body, calculates the Merkle root of the transaction data 10e, obtains the hash value of the last block (i.e., the third block) of the current blockchain (wherein the hash value of the block = the hash value of the block header), and the current timestamp, stores the Merkle root, the hash value of the last block and the current timestamp into the block header, combines the block header and the block body storing the transaction data 10e into the block 10f, and adds the newly generated block 10f to the blockchain, where the transaction data 10e stored on the blockchain indicates that the resource data in the amount of 5 is transferred from the electronic wallet with the address "rfvtg" to the electronic wallet with the address "plmok", so as to achieve the effect of resource data transfer.

[0043] As shown in Figure 2f , after the node in the blockchain network adds the newly generated block 10f to the blockchain, the blockchain includes 4 blocks, and the last block is the newly generated block 10f, and the transaction data 10e is stored in the block 10f.

[0044] At this point, the resource data in the amount of 5 is transferred from the sub-wallet 2 to the electronic wallet with the address "plmok". It can be known that the object can refine the type of the electronic wallet according to its own needs, so that the object can control the transaction process more carefully, and the object can store the resource data in different electronic wallets, so as to reduce the loss even if the encrypted resource data is leaked.

[0045] Wherein, the specific process of obtaining the transaction request (such as the transaction request 10d in the above embodiment), determining the target first sub-encrypted resource data storage container (such as the sub-wallet 2 in the above embodiment) from the plurality of first sub-encrypted resource data storage containers (such as the sub-wallet 1 and the sub-wallet 2 in the above embodiment) under the first encrypted resource data storage container (such as the main wallet in the above embodiment), and performing the business operation (such as the resource data transfer in the above embodiment) corresponding to the transaction request can be referred to the following Figures 3-7 corresponding embodiment.

[0046] Please refer to Figure 3 , Figure 3 is a flowchart of a data processing method provided by the embodiment of the present application. The data processing method can be applied to the wallet software in the first client (such as the terminal device 10a in the above Figures 2a-2f corresponding embodiment), and an encrypted resource data storage container (referred to as a first encrypted resource data storage container, such as the main wallet in the above Figures 2a-2f corresponding embodiment) and a plurality of sub-encrypted resource data storage containers (all referred to as first sub-encrypted resource data storage containers, such as the sub-wallet 1 and the sub-wallet 2 in the aboveFigures 2a-2f Sub-wallet 1 and sub-wallet 2 in the corresponding embodiments.

[0047] The first client can refer to a wallet software, which is used to store a wallet address and a private key. The wallet address can be compared to a bank card number, and the private key can be compared to a bank card password. In other words, the wallet software is a storage medium of the wallet address and the private key.

[0048] The encrypted resource data storage container can refer to a wallet, and the wallet = wallet address + private key. Therefore, the container address refers to the wallet address.

[0049] The data processing method includes the following steps:

[0050] In step S101, a transaction request is obtained, and the transaction request includes a container address of a second encrypted resource data storage container.

[0051] The first client receives a two-dimensional code image sent by the second client (such as the wallet software in the terminal device 10c in the corresponding embodiment described above), and the first client identifies the two-dimensional code image to obtain an original transaction request and a digital signature of the original transaction request. The first client performs signature verification on the original transaction request. If the verification is passed, the original transaction request is taken as a transaction request (such as the transaction request 10d in the corresponding embodiment described above). Figures 2a-2f Figures 2a-2f The first client receives a two-dimensional code image sent by the second client (such as the wallet software in the terminal device 10c in the corresponding embodiment described above), and the first client identifies the two-dimensional code image to obtain an original transaction request and a digital signature of the original transaction request. The first client performs signature verification on the original transaction request. If the verification is passed, the original transaction request is taken as a transaction request (such as the transaction request 10d in the corresponding embodiment described above).

[0052] The specific process of performing signature verification on the original transaction request can be that the first client calculates a data fingerprint of the original transaction request by using an encryption algorithm (the encryption algorithm can be MD5 algorithm, SHA1 algorithm, SHA256 algorithm, and HMAC algorithm, etc.). The data fingerprint is a string of ciphertext that can identify the original transaction request and does not conflict with the data fingerprints of other data. Generally, the length of the data fingerprint is fixed, and the data fingerprint is usually represented by a short string of random letters and numbers. The first client decrypts the digital signature of the original transaction request by using the public key of the second client to obtain a signature digest. The signature digest and the data fingerprint of the original transaction request are compared. If they are the same, it means that the signature verification of the first client on the original transaction request is passed. Otherwise, if the signature digest and the data fingerprint of the original transaction request are different, it means that the signature verification of the first client on the original transaction request is not passed.

[0053] The transaction request includes a container address of an encrypted resource data storage container (referred to as a container address of a second encrypted resource data storage container, such as the transfer-in address "plmok" in the transaction request 10d in the corresponding embodiment described above) and a resource transfer amount (such as the resource transfer amount in the transaction request 10d in the corresponding embodiment described above). Figures 2a-2f Figures 2a-2f ​​The transfer amount 5) in the transaction request 10d in the corresponding embodiment. The transaction request is to request to transfer the resource data equivalent to the transfer resource amount from the first encrypted resource data storage container to the second encrypted resource data storage container.

[0054] Step S102, determining a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container from a plurality of first sub-encrypted resource data storage containers under the first encrypted resource data storage container.

[0055] Specifically, the first client acquires a plurality of first sub-encrypted resource data storage containers (such as the sub-wallet 1 and the sub-wallet 2 in the above Figures 2a-2f corresponding embodiment) under the first encrypted resource data storage container. Each first sub-encrypted resource data storage container contains not only the container address and the private key, but also the transaction container address of the to-be-transacted storage container. That is, when each first sub-encrypted resource data storage container is created, it is already limited that the first sub-encrypted resource data storage container can only transact with a certain (or multiple) to-be-transacted storage container (which is also an encrypted resource data storage container), and cannot transact with other encrypted resource data storage containers.

[0056] The first client determines a transaction container address (referred to as a target transaction container address) identical to the container address of the second encrypted resource data storage container from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers, and takes the first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container (such as the sub-wallet 2 in the above Figures 2a-2f corresponding embodiment).

[0057] For example, there are three first sub-encrypted resource data storage containers, namely the first sub-encrypted resource data storage container 1, the first sub-encrypted resource data storage container 2, and the first sub-encrypted resource data storage container 3. The transaction container address of the first sub-encrypted resource data storage container 1 is 123, the transaction container address of the first sub-encrypted resource data storage container 2 is 456, and the transaction container address of the first sub-encrypted resource data storage container 3 is 789. If the container address of the second encrypted resource data storage container is 456, the target transaction container address is 456, and thus the first sub-encrypted resource data storage container 2 is the target first sub-encrypted resource data storage container.

[0058] The container type of the first sub-encrypted resource data storage container can be subdivided into an active container type and a passive container type. The first sub-encrypted resource data storage container of the active container type refers to that, when created, the transaction counterparty of the encrypted resource data storage container is determined by the object (i.e., the transaction container address of the transaction storage container is determined), and in addition, the container characteristics of the encrypted resource data storage container such as transaction rules (for example, a certain type of encrypted resource data is specified for transaction, upper and lower limits of transaction resource quantity, and the like), life cycle, and the like can be set. These container characteristics can be modified at any time in the subsequent use process of the encrypted resource data storage container, and the encrypted resource data in the first sub-encrypted resource data storage container belonging to the active container type can be transferred into the first encrypted resource data storage container at any time (i.e., the balance in the sub-wallet can be transferred into the main wallet at any time). For example, the first sub-encrypted resource data storage container belonging to the active container type can be used to pay for water and electricity charges.

[0059] The first sub-encrypted resource data storage container of the passive container type refers to that, when created, the transaction object (i.e., the merchant, i.e., the transaction container address of the transaction storage container is the container address of the encrypted resource data storage container of the merchant) is determined by the object, the merchant, and the wallet software provider at the same time, and in addition, the container characteristics of the encrypted resource data storage container such as transaction rules (for example, a certain type of encrypted resource data is specified for transaction, upper and lower limits of transaction resource quantity, and the like), life cycle, and the like can be set. However, the object cannot unilaterally modify these container characteristics, and if the object wants to modify the container characteristics, the consent of the object, the merchant, and the wallet software provider is required. It can be known that each first sub-encrypted resource data storage container corresponds to a merchant, and the initial encrypted resource data quantity of the first sub-encrypted resource data and the transaction rules, life cycle, and the like in the container characteristics are determined by negotiation between the object and the merchant. The object can transfer the encrypted resource data into the first sub-encrypted resource data storage container through the first encrypted resource data storage container at any time in the subsequent use process. It should be noted that the encrypted resource data in the first sub-encrypted resource data storage container belonging to the passive container type cannot be transferred into the first encrypted resource data storage container at will, and the encrypted resource data in the first sub-encrypted resource data storage container belonging to the passive container type can be transferred into the first encrypted resource data storage container only after the object, the merchant, and the wallet software provider reach an agreement or the object proves to the wallet software provider that the merchant cannot normally perform the agreement with the object.

[0060] In step S103, a business operation corresponding to the transaction request is performed based on the target first sub-encrypted resource data storage container.

[0061] Specifically, the container address of each first sub-encrypted resource data storage container, the container address of the first encrypted resource data storage container, and the container address of the second encrypted resource data storage container are all transaction addresses on a blockchain (such as the blockchain in the above Figures 2a-2f corresponding embodiments).

[0062] The first client obtains the remaining resource amount of the target first sub-encrypted resource data storage container on the blockchain, where the remaining resource amount of the first sub-encrypted resource data storage container can be determined by the first client by traversing the historical transaction data in all blocks on the blockchain.

[0063] The specific process of the first client obtaining the remaining resource amount of the target first sub-encrypted resource data storage container can be that the first client traverses all blocks on the blockchain to find blocks related to the target first sub-encrypted resource data storage container. In the processed blocks, the historical transaction data is read, and the remaining resource amount of the target first sub-encrypted resource data storage container is calculated according to the read historical transaction data. For example, if the blocks related to the target first sub-encrypted resource data storage container found on the blockchain are block 1 and block 2, and the specific content of the historical transaction data in block 1 is that the encrypted resource data storage container with container address a transfers 10 encrypted resource data to the target first sub-encrypted resource data storage container, and the encrypted resource data storage container with container address b transfers 20 encrypted resource data to the target first sub-encrypted resource data storage container, therefore the remaining resource amount of the target first sub-encrypted resource data storage container is 10+20=30.

[0064] After the first client obtains the remaining resource amount of the target first sub-encrypted resource data storage container, if the remaining resource amount of the target first sub-encrypted resource data storage container is greater than or equal to the transfer resource amount in the transaction request, the first client generates transaction data (referred to as first transaction data, such as the transaction data 10e) in the above Figure 4 corresponding embodiments) containing the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount. In the first transaction data, the container address of the target first sub-encrypted resource data storage container is the transfer-in address, and the container address of the second encrypted resource data storage container is the transfer-out address.

[0065] If the remaining resource amount of the target first sub-encrypted resource data storage container is less than the transfer resource amount in the transaction request, the first client can generate transaction data (referred to as second transaction data) containing the container address of the target first sub-encrypted resource data storage container, the container address of the first encrypted resource data storage container, and the transfer resource amount, wherein the container address of the target first sub-encrypted resource data storage container is the transfer-in address, and the container address of the first encrypted resource data storage container is the transfer-out address. The first client stores the second transaction data to the blockchain, and the second transaction data stored on the blockchain indicates that the resource data (which can be specifically encrypted resource data) equal to the transfer resource amount is transferred from the container address of the first encrypted resource data storage container to the container address of the target first sub-encrypted resource data storage container. After the resource data is transferred into the target first sub-encrypted resource data storage container, the remaining resource amount of the target first sub-encrypted resource data storage container is not less than the transfer resource amount in the transaction request, and therefore, the first client can generate first transaction data containing the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount.

[0066] The first transaction data stored on the blockchain indicates that the resource data (which can be specifically encrypted resource data) equal to the transfer resource amount is transferred from the container address of the target first sub-encrypted resource data storage container to the container address of the second encrypted resource data storage container.

[0067] The process of storing the first transaction data to the blockchain by the first client is basically the same as the process of storing the second transaction data to the blockchain by the first client, and the following will be specifically described by taking the first transaction data as an example.

[0068] The first client sends the first transaction data to a consensus node set of the blockchain, and the consensus node set includes a plurality of consensus nodes. Based on a preset consensus mechanism of the blockchain, a ledger node is selected from the plurality of consensus nodes, the ledger node packs the first transaction data into a block, the ledger node broadcasts the block to all blockchain nodes, and all blockchain nodes store the block to the blockchain maintained locally. In this way, all blockchain nodes reach a consensus, and the first transaction data is stored to the blockchain, that is, the resource data equal to the transfer resource amount is transferred into the container address of the second encrypted resource data storage container.

[0069] The first transaction data is stored on the blockchain based on the PBFT (Practical Byzantine Fault Tolerance) consensus mechanism. The plurality of consensus nodes in the consensus node set can be divided into 1 master node and N backup nodes (N is an integer greater than 0), that is, the number of consensus nodes is N+1, wherein the N+1 consensus nodes take turns as master nodes, and the remaining consensus nodes are backup nodes. The master node is the accounting node. The master node packs the first transaction data into a block and sends the block to each backup node. Each backup node verifies the first transaction data in the block. The verification content of the transaction verification can be specifically verifying whether the block is correct, verifying whether the container address of the target first encrypted resource data storage container and the container address of the second encrypted resource data storage container are both transaction addresses on the blockchain, and the like. If the backup node passes the transaction verification of the cross-chain transaction data in the block, the backup node signs the first transaction data with its own node private key to obtain a unit consensus signature. The backup node encapsulates the unit consensus signature into a transaction confirmation message and sends the transaction confirmation message to the master node and the remaining backup nodes, indicating that the backup node considers the first transaction data to be valid transaction data. If the backup node fails to verify the first transaction data in the block, the backup node will not sign or send any message. Assuming that the master node and each backup node have received M transaction confirmation messages sent by the backup nodes (M is a positive integer not greater than N, and M is less than N because there may be malicious consensus nodes or faulty consensus nodes among the M backup nodes), that is, the number of transaction confirmation messages is equal to M. If M is greater than a preset number threshold, the master node adds the block to the locally maintained blockchain, and each backup node also adds the block to the locally maintained blockchain. Thus, the first transaction data is stored on the blockchain, achieving the effect of transferring resource data from the container address of the target first encrypted resource data storage container to the container address of the second encrypted resource data storage container. Conversely, if M is not greater than the preset number threshold, a resource transfer failure notification message can be output and sent to the first client.

[0070] As can be seen from the above, each object in the present application can not only register an encrypted resource data storage container, but also register multiple sub-encrypted resource data storage containers under the encrypted resource data storage container. When receiving a transaction request, the corresponding sub-encrypted resource data storage container can be used for transaction. By refining the type of encrypted resource data storage container, the object can control the transaction process more carefully, and the object can store encrypted resource data in different sub-encrypted resource data storage containers, so that even if the encrypted resource data is leaked, the loss can be reduced.

[0071] Please refer toFigure 3 which is a flow diagram for determining a target first sub-encrypted resource data storage container provided by an embodiment of the present application. The determination of the target first sub-encrypted resource data storage container includes steps S201-S203, and steps S201-S203 are Figure 5 One specific embodiment of step S102 in the corresponding embodiment:

[0072] Step S201: Obtain a plurality of first sub-encrypted resource data storage containers, each of which includes a transaction container address of a to-be-traded storage container.

[0073] Specifically, the first client obtains a plurality of original encrypted resource data storage containers, each of which includes a transaction container address of a to-be-traded container, and each of which is a sub-container of a first encrypted resource data storage container. The first client traverses the transaction container addresses of all original encrypted resource data storage containers. If there is a transaction container address that is the same as the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, the plurality of encrypted resource data storage containers are all taken as first sub-encrypted resource data storage containers.

[0074] If there is no transaction container address that is the same as the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, the first client displays a container creation reminder message, which includes an agree-to-create control.

[0075] The object can click the agree-to-create control, and the first client generates a trigger message (referred to as a first trigger message) for the agree-to-create control. The first client determines the container type (the container type includes an active container type or a passive container type) of the encrypted resource data storage container to be created according to the transaction request. If the container type of the encrypted resource data storage container to be created is the active container type, the first client generates a container creation request, which includes the container address of the second encrypted resource data storage container. The first client sends the container creation request to a background server (which can be a server where a wallet software provider is located) to enable the background server to perform request verification on the container creation request, and after the request verification is passed, the background server creates a new encrypted resource data storage container according to the container address of the second encrypted resource data storage container. The container type of the created encrypted resource data storage container is the active container type, the transaction container address of the created encrypted resource data storage container is the container address of the second encrypted resource data storage container, and the created encrypted resource data storage container is a sub-container of the first encrypted resource data storage container.

[0076] If the container type of the to-be-created encrypted resource data storage container is a passive container type, the first client receives a container creation request sent by the second client, the container creation request including a container address of the second encrypted resource data storage container. The first client sends the container creation request to a background server (the background server can be a server where a wallet software provider is located) to enable the background server to perform request verification on the container creation request, and after the request verification passes, the background server creates a new encrypted resource data storage container according to the container address of the second encrypted resource data storage container, the container type of the created encrypted resource data storage container is a passive container type, and the transaction container address of the created encrypted resource data storage container is the container address of the second encrypted resource data storage container. The background server takes the created encrypted resource data storage container as a sub-container of the first encrypted resource data storage container.

[0077] After the new encrypted resource data storage container is created, the first client takes the newly created encrypted resource data storage container and the plurality of original encrypted resource data storage containers as a first sub-encrypted resource data storage container.

[0078] Please refer to Figure 5 , Figure 6 is a schematic diagram of creating an encrypted resource data storage container provided by an embodiment of the present application. When the object clicks the consent creation control, the wallet type of the to-be-created wallet is determined according to the wallet type in the transaction request (the wallet type can correspond to the container type of the encrypted resource data storage container in the present application). If the to-be-created wallet is an active wallet (the active wallet can correspond to the encrypted resource data storage container belonging to the active container type in the present application), the object wallet APP (the object wallet APP can correspond to the first client in the present application) generates an active wallet creation request, the active wallet creation request including wallet features (for example, a wallet address that can be traded with the wallet, a wallet life cycle, a wallet transaction rule, and the like), and sends the request to the wallet background server. The wallet background server authenticates the active wallet creation request and checks the wallet features. When the check passes, the wallet background server creates an active wallet under the main wallet of the object, and the created active wallet is a sub-wallet of the main wallet. The wallet background server sends a notification message of successful creation to the object wallet APP.

[0079] Please refer to Figure 6 , Figure 7is a schematic diagram of creating an encrypted resource data storage container provided by an embodiment of the present application. When the object clicks the consent creation control, the wallet type of the to-be-created wallet is determined according to the wallet type in the transaction request (the wallet type can correspond to the container type of the encrypted resource data storage container in the present application). If the to-be-created wallet is a passive wallet (the passive wallet can correspond to the encrypted resource data storage container belonging to the passive container type in the present application), the wallet APP sends a first trigger message of the object triggering the consent creation control to the merchant wallet APP (the merchant wallet APP can correspond to the second client in the present application). After receiving the first trigger message, the merchant wallet APP generates a passive wallet creation request, which includes wallet features (for example, a wallet address that can be traded with the wallet, a wallet life cycle, a wallet transaction rule, etc.). The merchant wallet APP sends the passive wallet creation request to the object wallet APP. The object verifies the passive wallet creation request, checks whether it meets the expectations, and if the verification is passed, the object can click the button “Determine”. The object wallet APP sends the passive wallet creation request to the wallet background server. The wallet background server authenticates the passive wallet creation request and verifies the wallet features. When the verification is passed, the wallet background server creates a passive wallet under the main wallet of the object. The active wallet created is a sub-wallet of the main wallet. The wallet background server sends a notification message of successful creation to the object wallet APP, and the object wallet APP sends a notification message of successful creation to the merchant wallet APP.

[0080] Optionally, the container creation reminder message further includes a modification container control. The object can click the modification container control, and the first client generates a trigger message (referred to as a third trigger message) for the modification container control. The first client selects, according to the third trigger message, a plurality of first sub-encrypted resource data storage containers whose container types are active container types from the plurality of first sub-encrypted resource data storage containers. The object can select a first sub-encrypted resource data storage container (referred to as an auxiliary first sub-encrypted resource data storage container) to be modified from the selected plurality of first sub-encrypted resource data storage containers, and modify the transaction container address of the auxiliary first sub-encrypted resource data storage container to the container address of the second encrypted resource data storage container. The first client regards the modified auxiliary first sub-encrypted resource data storage container and the unmodified original encrypted resource data storage container as first sub-encrypted resource data storage containers.

[0081] For example, there are three original encrypted resource data storage containers, namely original encrypted resource data storage container 1, original encrypted resource data storage container 2 and original encrypted resource data storage container 3, the transaction container address of the original encrypted resource data storage container 1 is 123, the transaction container address of the original encrypted resource data storage container 2 is 456, the transaction container address of the original encrypted resource data storage container 3 is 789, if the container address of the second encrypted resource data storage container is 234, the object clicks the modify container control in the container creation prompt message, and selects the original encrypted resource data storage container 1 as the auxiliary first sub-encrypted resource data storage container, and the container type of the original encrypted resource data storage container 1 is the active container type, therefore the first client can modify the transaction container address of the original encrypted resource data storage container 1 from 123 to 234, of course the transaction container addresses of the original encrypted resource data storage container 2 and the original encrypted resource data storage container 3 remain unchanged, the original encrypted resource data storage container 1, the original encrypted resource data storage container 2 and the original encrypted resource data storage container 3 after the transaction container address is modified are all taken as the first sub-encrypted resource data storage container.

[0082] Step S202, determining a target transaction container address same as the container address of the second encrypted resource data storage container from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers.

[0083] It can be known that there is certainly a first sub-encrypted resource data storage container whose transaction container address is same as the container address of the second encrypted resource data storage container in the plurality of first sub-encrypted resource data storage containers. The first client determines a transaction container address (called target transaction container address) same as the container address of the second encrypted resource data storage container from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers.

[0084] Step S203, taking the first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container.

[0085] Specifically, the first client takes the first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container.

[0086] Optionally, the container creation prompt message further includes a disagree to create control, the object can click the disagree to create control, and the first client generates a trigger message (called second trigger message) for the disagree to create control. The first client transfers the resource data (may be encrypted resource data) of the same amount of resource quantity in the transaction request from the container address of the first encrypted resource data storage container to the container address of the second encrypted resource data storage container according to the second trigger message.

[0087] The container address of the first encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the container address of each first sub-encrypted resource data storage container are all transaction addresses on the blockchain. The specific process of transferring an amount of resource data (which can be encrypted resource data) equivalent to the amount of resource data to be transferred from the container address of the first encrypted resource data storage container to the container address of the second encrypted resource data storage container is as follows: the first client generates third transaction data, wherein the third transaction data includes the container address of the first encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the amount of resource data to be transferred, and the container address of the first encrypted resource data storage container is the transfer-out address and the container address of the second encrypted resource data storage container is the transfer-in address. The first client stores the generated third transaction data to the blockchain, wherein the process of storing the third transaction data to the blockchain is the same as the process of storing the first transaction data to the blockchain as described above, except that the processing object is changed from the first transaction data to the third transaction data, which will not be described here.

[0088] In simple terms, if the object refuses to create a new encrypted resource data storage container or modify the transaction container address of the original encrypted resource data storage container, the main wallet will pay for the encrypted resource data corresponding to the transaction request.

[0089] As can be seen from the above, the sub-encrypted resource data storage container can be created in real time in the present application, which facilitates the management of the sub-encrypted resource data storage container by the object. Furthermore, when the original sub-encrypted resource data storage container does not store a matching sub-encrypted resource data storage container and the object does not agree to create a new sub-encrypted resource data storage container, the main encrypted resource data storage container will make a transaction payment, which can ensure the success rate of the transaction and prevent transaction failure.

[0090] Please refer to Figure 7 , Figure 5 is a flowchart of a data processing method provided by an embodiment of the present application. The data processing method includes the following steps:

[0091] Step S301, the receiver wallet APP sends transaction information to the sender wallet APP.

[0092] Specifically, the receiving wallet app can correspond to the second client in this application, the sending wallet app can correspond to the first client in this application, and the transaction information can correspond to the transaction request in this application. The transaction information includes the wallet address of the receiving wallet app, the amount of resources received, and the wallet type. This wallet type is used to determine the wallet type when the sending party needs to create a new wallet. The receiving wallet app can convert the transaction request into a QR code image and send the QR code image to the sending wallet app.

[0093] Step S302: The sending wallet app matches the custom wallets in the list of custom wallets and determines the matching custom wallet.

[0094] Specifically, the sending wallet app recognizes the QR code image to obtain transaction information. Based on the receiving wallet app's wallet address in the transaction information, the sending wallet app searches for a custom wallet in the custom wallet list that matches the receiving wallet app's wallet address. This custom wallet can correspond to the first sub-encrypted resource data storage container in this application.

[0095] If the sending wallet app finds a custom wallet in the custom wallet list that matches the wallet address of the receiving wallet app, then step S303 is executed, meaning the found custom wallet is the wallet to be paid; if the sending wallet app does not find a custom wallet in the custom wallet list that matches the wallet address of the receiving wallet app, then step S304 is executed.

[0096] Step S303: The sending wallet APP generates an order based on the transaction information.

[0097] Step S304: Ask the object whether to create a new custom wallet. If the object agrees to create a custom wallet, proceed to step S305; if the object disagrees to create a custom wallet, proceed to step S306.

[0098] In step S305, the sending wallet app creates a custom wallet based on the wallet type in the transaction information. The created custom wallet can be an active wallet or a passive wallet.

[0099] The specific process for creating an active wallet can be found above. Figure 6 The specific process of creating a passive wallet, corresponding to the description in the embodiments, can be found above. Figure 8 Description of the corresponding embodiments.

[0100] Step S306: Ask the recipient if they agree to use the main wallet for payment.

[0101] The main wallet can correspond to the first encrypted resource data storage container in the application. If the object agrees to pay by the main wallet, step S303 is executed, that is, the main wallet is the to-be-paid wallet; if the object does not agree to pay by the main wallet, step S310 is executed.

[0102] In step S307, the sender wallet APP checks whether the order meets the transaction rules of the to-be-paid wallet. If yes, step S308 is executed; if no, step S310 is executed.

[0103] In step S308, the sender wallet APP uses the to-be-paid wallet to make payment.

[0104] It can be known that the to-be-paid wallet is either a custom wallet found, or a custom wallet newly created, or the main wallet.

[0105] In step S309, a transaction success notification message is generated.

[0106] In step S310, a transaction failure notification message is generated.

[0107] Further, please refer to Figure 8 which is a structural schematic diagram of a data processing apparatus provided in the application. As Figures 3-7 shown, the data processing apparatus 1 can be the first client in the above Figure 3 corresponding embodiment. Specifically, the data processing apparatus 1 can be a computer program (including program code) running in a computer device, for example, the data processing apparatus 1 is an application software; the data processing apparatus 1 can be used to execute corresponding steps in the method provided in the application.

[0108] The data processing apparatus 1 registers the first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container. The data processing apparatus 1 can include an acquisition module 11, a search module 12, and a first transaction module 13.

[0109] The acquisition module 11 is configured to acquire a transaction request, wherein the transaction request includes a container address of a second encrypted resource data storage container;

[0110] The search module 12 is configured to determine a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container from the plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container;

[0111] The first transaction module 13 is configured to execute a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.

[0112] In an embodiment, the obtaining module 11 is specifically configured to:

[0113] receive the two-dimensional code image sent by the second client;

[0114] identify the two-dimensional code image to obtain an original transaction request, perform signature verification on the original transaction request, and if the signature verification is passed, take the original transaction request as the transaction request.

[0115] The specific function implementation manners of the obtaining module 11, the searching module 12 and the first transaction module 13 can be referred to the above Figure 8 steps S101-S103 in the corresponding embodiments.

[0116] Please refer to Figure 4 , the searching module 12 can include an obtaining unit 121 and a searching unit 122.

[0117] The obtaining unit 121 is configured to obtain a plurality of first sub-encrypted resource data storage containers, each of which includes a transaction container address of a to-be-transacted storage container;

[0118] The searching unit 122 is configured to determine a target transaction container address same as the container address of the second encrypted resource data storage container from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers, and take the first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container.

[0119] In an embodiment, the obtaining unit 121 can include an obtaining sub-unit 1211 and a first determining sub-unit 1212.

[0120] The obtaining sub-unit 1211 is configured to obtain a plurality of original encrypted resource data storage containers, each of which includes a transaction container address of a to-be-transacted storage container, and each of which is a sub-container of a first encrypted resource data storage container;

[0121] The obtaining sub-unit 1211 is further configured to traverse the transaction container addresses of the plurality of original encrypted resource data storage containers;

[0122] The first determining sub-unit 1212 is configured to, if there is a transaction container address same as the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, take the plurality of original encrypted resource data storage containers as the plurality of first sub-encrypted resource data storage containers.

[0123] In an embodiment, the obtaining unit 121 can include an obtaining subunit 1211 and a first determining subunit 1212; and can further include a display subunit 1213 and a creating subunit 1214.

[0124] The display subunit 1213 is configured to display a container creation reminding message if there is no transaction container address same as the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, the container creation reminding message including an agree-to-create control;

[0125] The creating subunit 1214 is configured to create an encrypted resource data storage container according to a first trigger message for the agree-to-create control if the first trigger message is received, the transaction container address of the created encrypted resource data storage container being the container address of the second encrypted resource data storage container, and the created encrypted resource data storage container being a sub-container of the first encrypted resource data storage container.

[0126] The display subunit 1213 is further configured to take the created encrypted resource data storage container and the plurality of original encrypted resource data storage containers as the plurality of first sub-encrypted resource data storage containers.

[0127] In an embodiment, the creating subunit 1214, when used to create an encrypted resource data storage container according to the first trigger message, is specifically configured to:

[0128] obtain a container creation request according to the first trigger message, the container creation request including the container address of the second encrypted resource data storage container;

[0129] send the container creation request to a background server, so that the background server performs request verification on the container creation request, and after the request verification passes, the background server creates an encrypted resource data storage container according to the container address of the second encrypted resource data storage container, and takes the created encrypted resource data storage container as a sub-container of the first encrypted resource data storage container.

[0130] In an embodiment, the container creation reminding message further includes a disagree-to-create control, and the transaction request further includes a resource amount to be transferred.

[0131] The data processing apparatus 1 can include an obtaining module 11, a searching module 12, and a first transaction module 13; and can further include a second transaction module 14.

[0132] The second transaction module 14 is configured to, if a second trigger message for the disagree creation control is received, transfer the resource data equivalent to the transfer resource amount from the container address of the first encrypted resource data storage container to the container address of the second encrypted resource data storage container according to the second trigger message.

[0133] The specific function implementation manners of the obtaining unit 121, the searching unit 122, the obtaining subunit 1211, the first determining subunit 1212, the displaying subunit 1213, the creating subunit 1214, and the second transaction module 14 can be referred to the above Figure 9 The steps S201-S203 in the corresponding embodiment.

[0134] Please attend Figure 3 The container address of each first sub-encrypted resource data storage container and the container address of the second encrypted resource data storage container are both transaction addresses on the block chain, and the transaction request further includes a transfer resource amount.

[0135] The first transaction module 13 can include a generating unit 131 and a storage unit 132.

[0136] The generating unit 131 is configured to generate first transaction data according to the transaction request, the first transaction data including the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount.

[0137] The storage unit 132 is configured to store the first transaction data to the block chain, and the first transaction data stored to the block chain indicates that the data data equivalent to the transfer resource amount is transferred from the container address of the target first sub-encrypted resource data storage container to the container address of the second encrypted resource data storage container.

[0138] In one embodiment, the generating unit 131 can include a first generating subunit 1311.

[0139] The first generating subunit 1311 is configured to obtain a remaining resource amount of the target first sub-encrypted resource data storage container, and if the remaining resource amount is not less than the transfer resource amount, generate the first transaction data according to the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount.

[0140] In one embodiment, the container address of the first encrypted resource data storage container is a transaction address on the block chain.

[0141] The generating unit 131 can include a first generating sub-unit 1311, and further include a second generating sub-unit 1312.

[0142] The second generating sub-unit 1312 is configured to generate second transaction data if the remaining resource amount is less than the transfer resource amount, the second transaction data including a container address of the first encrypted resource data storage container, a container address of the target first sub-encrypted resource data storage container, and the transfer resource amount, and store the second transaction data to the blockchain, the second transaction data stored to the blockchain indicating that resource data equivalent to the transfer resource amount is transferred from the container address of the first encrypted resource data storage container to the container address of the target first sub-encrypted resource data storage container.

[0143] The second generating sub-unit 1312 is further configured to generate the first transaction data according to the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount.

[0144] The specific function implementation manners of the generating unit 131, the storing unit 132, the first generating sub-unit 1311, and the second generating sub-unit 1312 can refer to the above Figure 9 The step S103 in the corresponding embodiment.

[0145] Further, please refer to Figures 3-7 is a structural schematic diagram of a computer device provided by the embodiment of the present application. The above Figure 9 The terminal device where the first client in the corresponding embodiment is located can be a computer device 1000. As shown in Figure 9 The computer device 1000 can include an object interface 1002, a processor 1004, an encoder 1006, and a memory 1008. A signal receiver 1016 is configured to receive or send data via a cellular interface 1010, a WIFI interface 1012,..., or an NFC interface 1014. The encoder 1006 encodes the received data into a data format for computer processing. The memory 1008 stores a computer program, and the processor 1004 is configured to execute the steps in any of the above method embodiments by the computer program. The memory 1008 can include a volatile memory (for example, a dynamic random access memory DRAM), and can also include a non-volatile memory (for example, a one-time programmable read-only memory OTPROM). In some examples, the memory 1008 can further include a memory remotely arranged relative to the processor 1004, and these remote memories can be connected to the computer device 1000 through a network. The object interface 1002 can include a keyboard 1018 and a display 1020.

[0146] InFigures 3-7 In the computer device 1000 shown, the computer device 1000 registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers belonging to the first encrypted resource data storage container, and the processor 1004 can be configured to invoke the computer program stored in the memory 1008 to implement:

[0147] obtain a transaction request, the transaction request including a container address of a second encrypted resource data storage container;

[0148] determine, from the plurality of first sub-encrypted resource data storage containers belonging to the first encrypted resource data storage container, a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container;

[0149] perform a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.

[0150] In one embodiment, when performing the step of determining, from the plurality of first sub-encrypted resource data storage containers belonging to the first encrypted resource data storage container, a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container, the processor 1004 specifically performs the following steps:

[0151] obtain a plurality of first sub-encrypted resource data storage containers, each including a transaction container address of a to-be-transacted storage container;

[0152] determine, from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers, a target transaction container address identical to the container address of the second encrypted resource data storage container;

[0153] take the first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container.

[0154] In one embodiment, when performing the step of obtaining a plurality of first sub-encrypted resource data storage containers, the processor 1004 specifically performs the following steps:

[0155] obtain a plurality of original encrypted resource data storage containers, each including a transaction container address of a to-be-transacted storage container, and each being a sub-container of the first encrypted resource data storage container;

[0156] traverse the transaction container addresses of the plurality of original encrypted resource data storage containers;

[0157] If there is a transaction container address same as the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, the plurality of original encrypted resource data storage containers are taken as the plurality of first sub-encrypted resource data storage containers.

[0158] In one embodiment, the processor 1004 further performs the following steps:

[0159] If there is no transaction container address same as the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, a container creation reminder message is displayed, the container creation reminder message comprising an agree-to-create control;

[0160] If a first trigger message for the agree-to-create control is received, an encrypted resource data storage container is created according to the first trigger message, the transaction container address of the created encrypted resource data storage container being the container address of the second encrypted resource data storage container, the created encrypted resource data storage container being a sub-container of the first encrypted resource data storage container;

[0161] The created encrypted resource data storage container and the plurality of original encrypted resource data storage containers are taken as the plurality of first sub-encrypted resource data storage containers.

[0162] In one embodiment, the processor 1004, in creating the encrypted resource data storage container according to the first trigger message, specifically performs the following steps:

[0163] According to the first trigger message, a container creation request is obtained, the container creation request comprising the container address of the second encrypted resource data storage container;

[0164] The container creation request is sent to a background server, so that the background server performs request verification on the container creation request, and after the request verification passes, the background server creates an encrypted resource data storage container according to the container address of the second encrypted resource data storage container, and takes the created encrypted resource data storage container as a sub-container of the first encrypted resource data storage container.

[0165] In one embodiment, the container creation reminder message further comprises a disagree-to-create control, and the transaction request further comprises a resource amount to be transferred.

[0166] The processor 1004 further performs the following steps:

[0167] If a second trigger message for the disagree-to-create control is received, then according to the second trigger message, resource data in the amount of the transfer resource amount is transferred from the container address of the first encrypted resource data storage container to the container address of the second encrypted resource data storage container.

[0168] In one embodiment, the container address of each first sub-encrypted resource data storage container and the container address of the second encrypted resource data storage container are both transaction addresses on the blockchain, and the transaction request further includes a transfer resource amount.

[0169] The processor 1004, in performing the business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container, specifically performs the following steps:

[0170] generating first transaction data according to the transaction request, the first transaction data including the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount;

[0171] storing the first transaction data to the blockchain, the first transaction data stored to the blockchain indicating that data in the amount of the transfer resource amount is transferred from the container address of the target first sub-encrypted resource data storage container to the container address of the second encrypted resource data storage container.

[0172] In one embodiment, the processor 1004, in generating the first transaction data according to the transaction request, specifically performs the following steps:

[0173] obtaining a remaining resource amount of the target first sub-encrypted resource data storage container;

[0174] if the remaining resource amount is not less than the transfer resource amount, generating the first transaction data according to the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount.

[0175] In one embodiment, the container address of the first encrypted resource data storage container is a transaction address on the blockchain.

[0176] The processor 1004 further performs the following steps:

[0177] if the remaining resource amount is less than the transfer resource amount, generating second transaction data, the second transaction data including the container address of the first encrypted resource data storage container, the container address of the target first sub-encrypted resource data storage container, and the transfer resource amount;

[0178] The second transaction data is stored in the blockchain. The second transaction data stored in the blockchain represents the transfer of resource data of equal amount from the container address of the first encrypted resource data storage container to the container address of the target first sub-encrypted resource data storage container.

[0179] The first transaction data is generated based on the container address of the first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the amount of resources to be transferred.

[0180] In one embodiment, when the processor 1004 executes a transaction retrieval request, it specifically performs the following steps:

[0181] Receive a QR code image sent by the second client;

[0182] The QR code image is identified to obtain the original transaction request. The original transaction request is then verified by signature. If the signature verification is successful, the original transaction request is used as the transaction request.

[0183] It should be understood that the computer device 1000 described in the embodiments of this application can execute the foregoing text. Figure 8 The description of the data processing method in the corresponding embodiments can also be performed as described above. Figures 3-7 The description of the data processing device 1 in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated here.

[0184] Furthermore, it should be noted that this application embodiment also provides a computer storage medium, which stores a computer program executed by the aforementioned data processing device 1. The computer program includes program instructions, and when the processor executes the program instructions, it can execute the aforementioned... Figures 3 to 7 The description of the data processing method in the corresponding embodiments is already provided and will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer storage medium involved in this application, please refer to the description of the method embodiments of this application. As an example, program instructions can be deployed and executed on a single computer device, or on multiple computer devices located in one location, or on multiple computer devices distributed across multiple locations and interconnected via a communication network. Multiple computer devices distributed across multiple locations and interconnected via a communication network can be combined to form a blockchain network.

[0185] According to an aspect of the present application, a computer program product or computer program is provided, which includes computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device can perform the above ​ The method in the corresponding embodiment will not be described here again.

[0186] All or part of the processes in the above-mentioned embodiment methods can be completed by a computer program instructing related hardware. The above-mentioned program can be stored in a computer readable storage medium, and when the program is executed, the program can include the processes of the above-mentioned embodiment methods. The above-mentioned storage medium can be a magnetic disc, an optical disc, a read-only memory (ROM), a random access memory (RAM), or the like.

[0187] The above only describes preferred embodiments of the present application, and of course cannot limit the scope of the rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope of the present application.

Claims

1. A data processing method, characterized by, The method is applied to a first client, the first client registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container, and the method comprises the following steps: Obtaining a transaction request, the transaction request comprising a container address of a second encrypted resource data storage container; Determining a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container from a plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container; Performing a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container; Wherein, the container type of the first sub-encrypted resource data storage container comprises an active container type and a passive container type, the container characteristics of the first sub-encrypted resource data storage container belonging to the active container type allow dynamic modification, and the encrypted resource data in the first sub-encrypted resource data storage container belonging to the active container type allows dynamic transfer to the first encrypted resource data storage container; the container characteristics of the first sub-encrypted resource data storage container belonging to the passive container type are allowed to be modified only when the transaction parties reach an agreement, and the encrypted resource data of the first sub-encrypted resource data storage container belonging to the passive container type is allowed to be transferred to the first encrypted resource data storage container only when the transaction parties reach an agreement.

2. The method of claim 1, wherein, The method comprises the following steps: Obtaining a plurality of first sub-encrypted resource data storage containers, each first sub-encrypted resource data storage container comprising a transaction container address of a to-be-transacted storage container; Determining a target transaction container address identical to the container address of the second encrypted resource data storage container from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers; Taking the first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container.

3. The method of claim 2, wherein, The method comprises the following steps: Obtaining a plurality of original encrypted resource data storage containers, each original encrypted resource data storage container comprising a transaction container address of a to-be-transacted storage container, and each original encrypted resource data storage container being a sub-container of the first encrypted resource data storage container; Traversing the transaction container addresses of the plurality of original encrypted resource data storage containers; If there is a transaction container address identical to the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, taking the plurality of original encrypted resource data storage containers as the plurality of first sub-encrypted resource data storage containers.

4. The method of claim 3, wherein, Further comprising: if there is no transaction container address identical to the container address of the second encrypted resource data storage container in the transaction container addresses of the plurality of original encrypted resource data storage containers, a container creation reminder message is displayed, the container creation reminder message comprising an agreement creation control; if a first trigger message for the agreement creation control is received, an encrypted resource data storage container is created according to the first trigger message, the transaction container address of the created encrypted resource data storage container being the container address of the second encrypted resource data storage container, and the created encrypted resource data storage container being a first child container of the first encrypted resource data storage container; the created encrypted resource data storage container and the plurality of original encrypted resource data storage containers are taken as a plurality of first child encrypted resource data storage containers.

5. The method of claim 4, wherein, The method further comprises: the container creation request comprises the container address of the second encrypted resource data storage container; the container creation request is sent to a background server, so that the background server performs request verification on the container creation request, and after the request verification is passed, the background server creates an encrypted resource data storage container according to the container address of the second encrypted resource data storage container, and takes the created encrypted resource data storage container as a child container of the first encrypted resource data storage container.

6. The method of claim 4, wherein, The container creation reminder message further comprises a disagreement creation control, and the transaction request further comprises a transfer resource amount. The method further comprises: if a second trigger message for the disagreement creation control is received, an amount of resource data equal to the transfer resource amount is transferred from the container address of the first encrypted resource data storage container to the container address of the second encrypted resource data storage container according to the second trigger message.

7. The method of claim 1, wherein, The container address of each first child encrypted resource data storage container and the container address of the second encrypted resource data storage container are both transaction addresses on a block chain, and the transaction request further comprises a transfer resource amount. The method further comprises: the first transaction data comprises the container address of the target first child encrypted resource data storage container, the container address of the second encrypted resource data storage container, and the transfer resource amount; the first transaction data is stored on the block chain, and the first transaction data stored on the block chain indicates that an amount of data equal to the transfer resource amount is transferred from the container address of the target first child encrypted resource data storage container to the container address of the second encrypted resource data storage container.

8. The method of claim 7, wherein, The method further comprises: the target first child encrypted resource data storage container is obtained; the remaining resource amount of the target first child encrypted resource data storage container is obtained; If the remaining resource amount is not less than the transfer resource amount, the first transaction data is generated according to the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container and the transfer resource amount.

9. The method of claim 8, wherein, The container address of the first encrypted resource data storage container is a transaction address on the blockchain; The method further comprises: If the remaining resource amount is less than the transfer resource amount, second transaction data is generated, the second transaction data comprising the container address of the first encrypted resource data storage container, the container address of the target first sub-encrypted resource data storage container and the transfer resource amount; The second transaction data is stored to the blockchain, and the second transaction data stored to the blockchain indicates that resource data equal to the transfer resource amount is transferred from the container address of the first encrypted resource data storage container to the container address of the target first sub-encrypted resource data storage container. The first transaction data is generated according to the container address of the target first sub-encrypted resource data storage container, the container address of the second encrypted resource data storage container and the transfer resource amount.

10. The method of claim 1, wherein, The transaction request comprises: Receiving a two-dimensional code image sent by a second client; Identifying the two-dimensional code image to obtain an original transaction request, performing signature verification on the original transaction request, and if the signature verification is passed, taking the original transaction request as the transaction request.

11. A data processing apparatus, characterized by The data processing apparatus registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container, and the apparatus comprises: An acquisition module configured to acquire a transaction request, the transaction request comprising a container address of a second encrypted resource data storage container; A search module configured to determine, from the plurality of first sub-encrypted resource data storage containers subordinate to the first encrypted resource data storage container, a target first sub-encrypted resource data storage container matching the container address of the second encrypted resource data storage container; A first transaction module configured to perform a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container. The container type of the first sub-encrypted resource data storage container comprises an active container type and a passive container type, the container characteristics of the first sub-encrypted resource data storage container of the active container type allow dynamic modification, and the encrypted resource data in the first sub-encrypted resource data storage container of the active container type is allowed to be dynamically transferred to the first encrypted resource data storage container; the container characteristics of the first sub-encrypted resource data storage container of the passive container type are allowed to be modified only when a plurality of transaction parties reach an agreement, and the encrypted resource data of the first sub-encrypted resource data storage container of the passive container type is allowed to be transferred to the first encrypted resource data storage container only when a plurality of transaction parties reach an agreement.

12. A computer device, comprising: The memory stores a computer program, and the computer program is executed by the processor to make the processor execute the steps of the method in any one of claims 1-10.

13. A computer storage medium, characterized in that The computer storage medium stores a computer program, and the computer program comprises program instructions. When the program instructions are executed by a processor, the method in any one of claims 1-10 is executed.

14. A computer program product, characterised in that, The computer program product comprises computer instructions stored in a computer readable storage medium. A processor of a computer device reads and executes the computer instructions from the computer readable storage medium, so that the computer device executes the method in any one of claims 1-10.

Citation Information

Patent Citations

  • Selecting and securing proof delgates for cryptographic functions

    CN111213340A

  • Dynamic blockchain system and method for providing efficient and secure distributed data access, data storage and data transport

    US20190386817A1

  • Method and system for linkage of blockchain private keys

    US20200273025A1