CN114493871A - Data processing method, data processing device, computer equipment and storage medium - Google Patents

Data processing method, data processing device, computer equipment and storage medium Download PDF

Info

Publication number
CN114493871A
CN114493871A CN202210073251.7A CN202210073251A CN114493871A CN 114493871 A CN114493871 A CN 114493871A CN 202210073251 A CN202210073251 A CN 202210073251A CN 114493871 A CN114493871 A CN 114493871A
Authority
CN
China
Prior art keywords
data storage
resource data
container
encrypted resource
storage container
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210073251.7A
Other languages
Chinese (zh)
Inventor
刘伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202210073251.7A priority Critical patent/CN114493871A/en
Publication of CN114493871A publication Critical patent/CN114493871A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

The embodiment of the application discloses a data processing method, a data processing device, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring a transaction request, wherein the transaction request comprises a container address of a second encrypted resource data storage container; determining a target first sub encrypted resource data storage container matched with 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; and executing the business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container. By adopting the method and the device, fine-grained control can be performed on the transaction process.

Description

Data processing method, data processing device, computer equipment and storage medium
The present application is a divisional application of a chinese patent application with application number 2020109433174, entitled "data processing method, apparatus, computer device, and storage medium" filed by the chinese patent office on 09/2020, and the entire contents of the present application are incorporated by reference in the present application.
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data processing method and apparatus, a computer device, and a storage medium.
Background
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 by using the encrypted resource data storage container is to sign the resource data transfer transaction data by using the private key, the resource data transfer transaction data is broadcasted to the whole network, and the transfer of the encrypted resource data is completed on a distributed account book.
The existing encrypted resource data storage containers and objects are in a one-to-one relationship, each object corresponds to one encrypted resource data storage container, that is, all encrypted resource data of the objects are stored in one storage container, so that when the objects trade, fine-grained control is difficult to be performed on a trading process in a specific scene.
Disclosure of Invention
The embodiment of the application provides a data processing method, a data processing device, computer equipment and a storage medium, which can control a transaction process in a fine granularity mode.
An aspect of the present embodiment provides a data processing method, which is applied to a first client, where the first client registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers that belong to the first encrypted resource data storage container, and the method includes:
obtaining a transaction request, wherein the transaction request comprises 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 under a first encrypted resource data storage container;
and executing business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
An aspect of the present embodiment provides a data processing apparatus, where the data processing apparatus registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers under the first encrypted resource data storage container, and the apparatus includes:
an obtaining module, configured to obtain a transaction request, where the transaction request includes a container address of a second encrypted resource data storage container;
the searching module is used for determining a target first sub-encrypted resource data storage container matched with 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;
and the first transaction module is used for executing business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
An aspect of the embodiments of the present application provides a computer device, including a memory and a processor, where the memory stores a computer program, and when the computer program is executed by the processor, the processor is caused to execute the method in the foregoing embodiments.
An aspect of the embodiments of the present application provides a computer storage medium, in which a computer program is stored, where the computer program includes program instructions, and when the program instructions are executed by a processor, the method in the foregoing embodiments is performed.
An aspect of the embodiments of the present application provides a computer program product or a computer program, where the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium, and when the computer instructions are executed by a processor of a computer device, the computer instructions perform the methods in the embodiments described above.
In the application, each object can register one encrypted resource data storage container, and can also register a plurality of sub encrypted resource data storage containers below the encrypted resource data storage container, and when a transaction request is received, the corresponding sub encrypted resource data storage containers can be used for performing transaction. By refining the type 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, so that the loss can be reduced even if the encrypted resource data are leaked.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic diagram of a block chain network according to an embodiment of the present application;
2 a-2 f are schematic diagrams of a data processing scenario provided by an embodiment of the present application;
fig. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application;
FIG. 4 is a schematic flow chart illustrating a process for determining a target first sub-encrypted resource data storage container according to an embodiment of the present application;
FIG. 5 is a schematic diagram of creating an encrypted resource data storage container according to an embodiment of the present application;
FIG. 6 is a schematic diagram of creating an encrypted resource data storage container according to an embodiment of the present application;
fig. 7 is a schematic flowchart of a data processing method according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained without inventive work based on the embodiments in this application belong to the protection scope of this application.
The Block chain (Block chain) is a novel application mode of computer technologies such as distributed data storage, point-To-point transmission (P2P, Peer To Peer), a consensus mechanism, an encryption algorithm and the like. The blockchain is essentially a decentralized database, which is a string of data blocks associated using cryptography, each data block containing one or more transaction messages for verifying the validity (anti-counterfeiting) of the message and generating the next block.
Referring to fig. 1, which is a schematic diagram of a blockchain network provided in the embodiment of the present disclosure, a node 1, a node 2, a node 3, and a node 4 may be combined into a blockchain network, each node may store one same blockchain, the 4 nodes may also be referred to as blockchain nodes, and each node may include a hardware layer, an intermediate layer, an operating system layer, and an application layer. It will be appreciated that a node may comprise a computer device.
The node may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, Network service, cloud communication, middleware service, domain name service, security service, CDN (Content Delivery Network), big data, and the like. The node may also be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The nodes may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.
The application scenario of the data processing method related by the application is as follows: the encrypted resource data storage container software of the object is registered with a first encrypted resource data storage container and a plurality of first sub encrypted resource data storage containers under the first encrypted resource data storage container. When the encrypted resource data storage container software acquires a transaction request containing a container address of a second encrypted resource data storage container, a target first sub-encrypted resource data storage container matched with the container address of the second encrypted resource data storage container is determined from the plurality of first sub-encrypted resource data storage containers, and the subsequent encrypted resource data storage container software executes business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
Please refer to fig. 2 a-2 f, which are schematic diagrams illustrating a data processing scenario according to an embodiment of the present application. The wallet software in the terminal device 10a in fig. 2a registers a main electronic wallet, as shown in page 10b, whose wallet address is abcde (the wallet address of each wallet is unique, that is, the wallet address has uniqueness and exclusivity), where the wallet address can be regarded as an account, and the wallet address needs to be known for transferring resource data in or out; the remaining resource data amount of the main electronic wallet is 100.
The main electronic purse belongs to a plurality of sub-electronic purses. As shown in page 10c in fig. 2b, the main electronic wallet is subordinate to 2 sub-electronic wallets, namely sub-wallet 1 and sub-wallet 2, wherein the balance of sub-wallet 1 is 40, the address of sub-wallet 1 is qwerty, and it is further defined that the transaction address of sub-wallet 1 is qazws, i.e. sub-wallet 1 can only transact with electronic wallet with wallet address qazws. In other words, the object, when creating the sub-wallet 1, has defined that the sub-wallet 1 can only communicate resource data with a certain specific e-wallet(s). Of course, the object can modify the transaction address of the sub-wallet 1 at any time, i.e. the object can limit which wallet or wallets the sub-wallet 1 can only transact with according to the situation of the object.
The balance of the sub-wallet 2 is 10, the address of the sub-wallet 2 is rfvtg, and it is further defined that the transaction address of the sub-wallet 2 is plmok, i.e. the sub-wallet 2 can only transact with an electronic wallet with wallet address plmok. In other words, the object, when creating the sub-wallet 2, has defined that the sub-wallet 2 can only communicate resource data with a certain specific e-wallet(s). Of course, the object can modify the transaction address of the sub-wallet 2 at any time, i.e. the object can limit which wallet or wallets the sub-wallet 2 can only transact with according to the situation of the object.
If the object clicks the button "start transfer" in the page 10b, the object can select a wallet for transferring the current resource data from the main wallet, the sub-wallet 1 and the sub-wallet 2, and input the wallet address and the transfer resource amount for transferring the resource data to the electronic wallet, so that the resource data can be transferred from the selected electronic wallet to the resource data for transferring to the electronic wallet.
As shown in fig. 2c, the terminal device 10a receives a transaction request 10d sent by wallet software in the terminal device 10c, where the transaction request 10d includes a transfer-in address "plmok" and a transfer amount "5", and in colloquial, the transaction request 10d is to request the terminal device 10a to transfer resource data with a resource amount of 5 into an electronic wallet with an address of plmok.
The terminal device 10a determines the sub-wallet having the transaction address plmok from among the sub-wallets 1 and 2, since the transaction address of the sub-wallet 2 is the same as the transfer-in address in the transaction request 10 d. Thus, the terminal device 10a can determine that the transaction request 10d is responded to by the sub-wallet 2.
As shown in fig. 2d, the terminal device 10a generates transaction data 10e from the transaction request 10d and the wallet address of the sub-wallet 2, wherein the transaction data 10e includes a roll-out address: rfvtg, transfer-in address: plmok, and amount of resource transfer: 5, it is known that the roll-out address is the wallet address of the sub-wallet 2, and it is colloquially understood that the transaction data 10e means that resource data of 5 in number is transferred from the wallet of "rfvtg" address to the wallet of "plok" address.
The resource data to be transferred is resource data on the blockchain, and the electronic wallets corresponding to the inbound address "plock" in the main wallet, the sub-wallets 1 and 2 and the transaction request 10d are all electronic wallets for managing blockchain resource data, 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 inbound address "plock" in the transaction request 10d are all transaction addresses on the blockchain.
As shown in fig. 2d, the terminal device 10a sends the generated transaction data 10e to a blockchain network, wherein the blockchain network includes 3 nodes, and the 3 nodes are: node 1, node 2 and node 3, it is assumed that these 3 nodes are all common nodes of the blockchain network. All of these 3 nodes will store a block chain, and it can be seen from fig. 2d that the current block chain includes 3 blocks.
The node in the blockchain network first determines whether the wallet balance of the sub-wallet 2 is greater than 5, verifies whether the signature of the transaction data 10e is correct, and so on, and if the wallet balance of the sub-wallet 2 is greater than 5, verifies that the signature of the transaction data 10e is correct. As shown in fig. 2e, a node in the block chain network stores the transaction data 10e into a block, calculates a merkel root of the transaction data 10e, obtains a hash value of the last block (i.e. the 3 rd block) of the current block chain (where the hash value of the block is the hash value of the block header) and a current timestamp, stores the merkel 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 a block 10f, and adds a newly generated block 10f into the block chain, where the transaction data 10e stored onto the block chain represents that resource data of 5 number is transferred from an electronic wallet of address "rfvtg" to an electronic wallet of address "plmok" to achieve the effect of resource data transfer.
As shown in fig. 2f, after a node in the blockchain network adds a newly generated block 10f to the blockchain, the blockchain includes 4 blocks, the last block is the newly generated block 10f, and transaction data 10e is stored in the block 10 f.
At this point, the transfer of the resource data of the number 5 from the sub-wallet 2 to the electronic wallet addressed to "plmok" is completed. It can be known that the object can refine the type of the electronic wallet according to the self requirement, so that the object can control the transaction process more carefully, and the object can store the resource data in different electronic wallets, thereby reducing the loss even if the encrypted resource data is leaked.
Wherein, a transaction request (transaction request 10d in the above-described embodiment) is obtained, a target first sub encrypted resource data storage container (sub-wallet 2 in the above-described embodiment) is determined from among a plurality of first sub encrypted resource data storage containers (sub-wallets 1 and 2 in the above-described embodiments) under the first encrypted resource data storage container (main wallet in the above-described embodiment), and a specific procedure of performing a business operation corresponding to the transaction request (resource data transfer in the above-described embodiment) may be referred to the following embodiments corresponding to fig. 3 to 7.
Referring to fig. 3, fig. 3 is a flowchart illustrating a data processing method according to an embodiment of the present application, where the data processing method may be applied to a first client (e.g., wallet software in terminal device 10a in the corresponding embodiment of fig. 2a to fig. 2 f), and an encrypted resource data storage container (referred to as a first encrypted resource data storage container, e.g., a main wallet in the corresponding embodiment of fig. 2a to fig. 2 f) and a plurality of sub encrypted resource data storage containers (both referred to as first sub encrypted resource data storage containers, e.g., sub-wallet 1 and sub-wallet 2 in the corresponding embodiment of fig. 2a to fig. 2 f) under the first encrypted resource data storage container are registered in the first client.
The first client may be wallet software, and the wallet software is used to store a wallet address and a private key, the wallet address may be similar to a bank card number, and the private key may be similar to a bank card password, in other words, the wallet software is a storage medium for the wallet address and the private key.
The encrypted resource data storage container may refer to a wallet, which is a wallet address + private key, and thus the container address refers to a wallet address.
The data processing method comprises the following steps:
step S101, a transaction request is obtained, wherein the transaction request comprises a container address of a second encryption resource data storage container.
The first client receives the two-dimensional code image sent by the second client (e.g. the wallet software in the terminal device 10c in the corresponding embodiment of fig. 2 a-2 f), and the first client identifies the two-dimensional code image to obtain the original transaction request and the digital signature of the original transaction request. The first client performs signature verification on the original transaction request, and if the verification is passed, the original transaction request is used as a transaction request (e.g., the transaction request 10d in the corresponding embodiment of fig. 2 a-2 f).
The specific process of signature verification on the original transaction request may be: the first client calculates a data fingerprint of the original transaction request by using an encryption algorithm (the encryption algorithm may specifically be an MD5 algorithm, an SHA1 algorithm, an SHA256 algorithm, an HMAC algorithm, etc.), where the data fingerprint is a string of ciphertext that can identify the original transaction request and does not conflict with data fingerprints of other data. Generally, the length of a data fingerprint is fixed, and the data fingerprint is usually represented by a short string of random letters and numbers. And the first client decrypts the digital signature of the original transaction request by adopting the public key of the second client to obtain the signature abstract. Comparing whether the signature abstract is the same as the data fingerprint of the original transaction request, if so, indicating that the signature verification of the first client to the original transaction request is passed; otherwise, if the signature digest is different from the data fingerprint of the original transaction request, it indicates that the signature verification of the first client to the original transaction request is not passed.
The transaction request includes a container address of the 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 of fig. 2a to 2 f) and a transfer resource amount (such as the transfer amount 5 in the transaction request 10d in the corresponding embodiment of fig. 2a to 2 f). It is colloquially understood that a transaction request is a request to transfer an amount of resource data equal to the amount of transferred resource from an encrypted resource data storage container in a first client to a second encrypted resource data storage container.
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.
Specifically, the first client obtains a plurality of first sub-encrypted resource data storage containers (e.g., the sub-wallets 1 and 2 in the corresponding embodiments of fig. 2a to 2f described above) under the first encrypted resource data storage container, where each first sub-encrypted resource data storage container not only includes a container address and a private key, but also includes a transaction container address of a storage container to be transacted. That is, when each first sub-encrypted resource data storage container is created, it has been defined that the first sub-encrypted resource data storage container can only transact with one (or more) storage container to be transacted (the storage container to be transacted is also an encrypted resource data storage container), but cannot transact with other encrypted resource data storage containers.
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 (e.g., the sub-wallet 2 in the corresponding embodiment of fig. 2 a-2 f).
For example, there are 3 first sub-encrypted resource data storage containers, which are 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, respectively, and 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, 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 then the target transaction container address is: 456, the first sub-encrypted resource data storage container 2 is thus the target first sub-encrypted resource data storage container.
Wherein, 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 being created, the object determines the transaction counterpart of the encrypted resource data storage container (i.e. determines the transaction container address of the transaction storage container), and may set transaction rules (for example, specify a certain encrypted resource data to perform transaction, the upper limit and the lower limit of the transaction resource amount, etc.), the container characteristics of the encrypted resource data storage container such as the life cycle, etc., these container characteristics can be modified at any time during the use of the subsequent 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 to the first encrypted resource data storage container at any time (namely, the balance in the sub-wallet can be transferred to the main wallet at any time). For example, the first sub encrypted resource data storage container belonging to the active container type may be exclusively used for paying a water charge or electricity fee, etc.
The first sub-encrypted resource data storage container of the passive container type is created by an object, a merchant and a wallet software provider at the same time, that is, when the first sub-encrypted resource data storage container belonging to the passive container type is created, a transaction object (that is, a merchant, that is, 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, and furthermore, transaction rules (for example, specifying a certain encrypted resource data for transaction, an upper limit and a lower limit of the transaction resource amount, a preferential policy, etc.), container characteristics of the encrypted resource data storage container such as a life cycle, etc. may be set, but these container characteristics, the object can not be modified unilaterally, and if the object is modified, the object, the merchant and the wallet software provider need to approve three parties to modify the container characteristics. It can be known that each first sub-encrypted resource data storage container corresponds to a merchant, the number of the initial encrypted resource data of the first sub-encrypted resource data and the transaction rules, life cycles, and the like in the container characteristics are determined by negotiation between the object and the merchant, and the object can transfer the encrypted resource data to 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 to the first encrypted resource data storage container at will, and an agreement is reached by the object, the merchant and the wallet software provider, or after the object proves to the wallet software provider that the merchant cannot normally perform and the object agrees, the encrypted resource data in the first sub-encrypted resource data storage container belonging to the passive container type can be transferred to the first encrypted resource data storage container.
Step S103, executing a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
Specifically, the container address of each of the 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 transaction addresses on a block chain (such as the block chain in the corresponding embodiments of fig. 2 a-2 f).
The first client obtains a 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 may be determined by the first client by traversing historical transactional data in all blocks on the blockchain.
The specific process of the first client obtaining the remaining resource amount of the target first sub-encrypted resource data storage container may be as follows: the first client traverses all blocks in the block chain to find out the block related to the target first sub-encrypted resource data storage container. And reading historical transaction data in the search processing block, and calculating the residual resource amount of the target first sub-encrypted resource data storage container according to the read historical transaction data. For example, if the blocks found on the blockchain associated with the target first sub-encrypted resource data storage container are block 1 and block 2, and the specific content of the historical transaction data in block 1 is: transferring 10 encrypted resource data into the target first sub encrypted resource data storage container from the encrypted resource data storage container with the container address a, transferring 20 encrypted resource data into the target first sub encrypted resource data storage container from the encrypted resource data storage container with the container address b, so that the remaining resource amount of the target first sub encrypted resource data storage container is: 10+ 20-30.
After the first client acquires 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 corresponding embodiment of fig. 2 a-2 f) 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. And the container address of the target first sub encrypted resource data storage container in the first transaction data is a roll-in address, and the container address of the second encrypted resource data storage container is a roll-out address.
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 may generate transaction data (referred to as second transaction data) including a container address of the target first sub-encrypted resource data storage container, a container address of the first encrypted resource data storage container, and the transfer resource amount, where the container address of the target first sub-encrypted resource data storage container is a roll-in address, and the container address of the first encrypted resource data storage container is a roll-out address. The first client stores the second transaction data to the blockchain, where the second transaction data stored on the blockchain represents a transfer of resource data (which may specifically be encrypted resource data) equivalent to the amount of the transfer resource 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 transferring the resource data to the target first sub-encrypted resource data storage container, at this time, 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, so that the first client may generate 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.
The first transaction data stored on the blockchain represents a transfer of an amount of resource data (which may specifically be encrypted resource data) equivalent to the amount of transferred resource 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.
The process of storing the first transaction data into the blockchain by the first client is substantially the same as the process of storing the second transaction data into the blockchain by the first client, and the following specifically describes how to store the first transaction data onto the blockchain by taking the first transaction data as an example:
the first client sends the first transaction data to a consensus node set of the blockchain, wherein the consensus node set comprises a plurality of consensus nodes. An accounting node is selected from a plurality of common identification nodes based on a preset common identification mechanism of a block chain, the accounting node packs first transaction data into blocks, the accounting node broadcasts the blocks to all block chain nodes, and all block chain nodes store the blocks to a locally maintained block chain, so that all the block chain nodes achieve common identification and store the first transaction data to the block chain, namely, the resource data equal to the transferred resource amount is transferred to a container address of a second encrypted resource data storage container.
The following description is made in detail based on the PBFT (Practical Byzantine Fault Tolerance) consensus mechanism to store the first transaction data onto the blockchain: the multiple consensus nodes in the consensus node set can be divided into 1 main node and N backup nodes (N is an integer greater than 0), that is, the number of the consensus nodes is N +1, where the N +1 consensus nodes are alternately used as the main nodes, the remaining consensus nodes are all backup nodes, and the main node is an accounting node. The main node packs the first transaction data into a block, the block is sent to each backup node, each backup node performs transaction verification on the first transaction data in the block, and verification content of the transaction verification can specifically be whether the block is correct or not, whether a container address of a target first sub encrypted resource data storage container and a container address of a target second encrypted resource data storage container are both transaction addresses on a block chain or not, and the like. If the backup node passes the transaction verification of the cross-link transaction data in the block, the backup node signs the first transaction data by using the private key of the backup node to obtain the unit consensus signature. The backup node packages the unit consensus signature into a transaction confirmation message, and sends the transaction confirmation message to the main node and other backup nodes to indicate that the backup node considers the first transaction data as valid transaction data; if the transaction verification of the first transaction data in the block by the backup node is not passed, the backup node will not sign or send any message. It is assumed that the master node and each backup node receive transaction confirmation messages sent by M backup nodes (M is a positive integer not greater than N, and the reason why M is smaller than N is that a malicious consensus node or a faulty consensus node may exist in the M backup nodes), that is, the number of transaction confirmation messages is equal to M. If M is larger than the preset number threshold, the main node adds the block to the block chain maintained locally, and each backup node also adds the block to the block chain maintained locally, so that the first transaction data is stored in the block chain, and the effect of transferring the resource data from the container address of the target first sub encrypted data storage container to the container address of the second encrypted resource data storage container is achieved. Otherwise, if M is not greater than the preset number threshold, a notification message of the resource transfer failure may be output, and the notification message may be sent to the first client.
As can be seen from the above, in the present application, each object may not only register one encrypted resource data storage container, but also register a plurality of sub encrypted resource data storage containers below the encrypted resource data storage container, and when a transaction request is received, a transaction may be performed using the corresponding sub encrypted resource data storage container. By thinning the type 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, so that the loss can be reduced even if the encrypted resource data is leaked.
Please refer to fig. 4, which is a schematic flowchart illustrating a process of determining a target first sub-encrypted resource data storage container according to an embodiment of the present application, where determining the target first sub-encrypted resource data storage container includes the following steps S201 to S203, and steps S201 to S203 are an embodiment of step S102 in the corresponding embodiment of fig. 3:
step S201, obtaining a plurality of first sub-encrypted resource data storage containers, where each first sub-encrypted resource data storage container includes a transaction container address of a storage container to be transacted.
Specifically, the first client acquires a plurality of original encrypted resource data storage containers, each original encrypted resource data storage container includes a transaction container address of a container to be transacted, and each original encrypted resource data storage container is a child container of the first encrypted resource data storage container. And the first client traverses the transaction container addresses of all the original encrypted resource data storage containers, and if the transaction container addresses of the plurality of original encrypted resource data storage containers have the transaction container addresses identical to the container address of the second encrypted resource data storage container, the plurality of encrypted resource data storage containers are all used as first sub-encrypted resource data storage containers.
And if the transaction container address identical to the container address of the second encrypted resource data storage container does not exist in the transaction container addresses of the plurality of original encrypted resource data storage containers, the first client displays a container creation reminding message, wherein the container creation reminding message comprises an agreement creation control.
The object may click on the consent-creation control, the first client generates a trigger message (referred to as a first trigger message) for the consent-creation control, and the first client determines a container type of the encrypted resource data storage container to be created according to the transaction request (the container type includes an active container type or a passive container type). If the container type of the encrypted resource data storage container to be created is an active container type, the first client generates a container creation request, and the container creation request includes a container address of the second encrypted resource data storage container. The first client sends a container creation request to a background server (the background server may be a server where a wallet software provider is located), so that the background server performs request verification on the container creation request, and creates a new encrypted resource data storage container according to a container address of the second encrypted resource data storage container by the background server after the request verification is passed, wherein the container type of the created encrypted resource data storage container is an active container type, and a transaction container address of the created encrypted resource data storage container is a container address of the second encrypted resource data storage container. And the background server takes the created encrypted resource data storage container as a child container of the first encrypted resource data storage container.
If the container type of the encrypted resource data storage container to be created is a passive container type, the first client receives a container creation request sent by the second client, and the container creation request includes a container address of the second encrypted resource data storage container. The first client sends a container creation request to a background server (the background server may be a server where a wallet software provider is located), so that the background server performs request verification on the container creation request, and creates a new encrypted resource data storage container according to a container address of the second encrypted resource data storage container by the background server after the request verification is passed, wherein the container type of the created encrypted resource data storage container is a passive container type, and a 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 background server takes the created encrypted resource data storage container as a child container of the first encrypted resource data storage container.
After the new encrypted resource data storage container is created, the first client uses the newly created encrypted resource data storage container and the plurality of original encrypted resource data storage containers as first sub-encrypted resource data storage containers.
Referring to fig. 5, fig. 5 is a schematic diagram of creating an encrypted resource data storage container according to an embodiment of the present application, and when an object clicks an agreement creation control, a wallet type of a wallet to be created is determined according to a wallet type in a transaction request (the wallet type may correspond to a container type of the encrypted resource data storage container in the present application). If the wallet to be created is an active wallet (the active wallet may correspond to an encrypted resource data storage container belonging to an active container type in the present application), generating an active wallet creation request by using an object wallet APP (the object wallet APP may correspond to a first client in the present application), where the active wallet creation request includes wallet characteristics (for example, a wallet address that can transact with the wallet, a life cycle of the wallet, transaction rules of the wallet, and the like), and sending the request to a wallet backend server. The wallet background server authenticates the active wallet creation request and verifies wallet characteristics. And after the verification is passed, the wallet background server creates a proactive wallet under the main wallet of the object, wherein the created proactive money is a sub-wallet of the main wallet. The wallet background server sends a notification message to the object wallet APP that the creation was successful.
Referring to fig. 6, fig. 6 is a schematic diagram of creating an encrypted resource data storage container according to an embodiment of the present application, and when an object clicks an agreement creation control, a wallet type of a wallet to be created is determined according to a wallet type in a transaction request (the wallet type may correspond to a container type of the encrypted resource data storage container in the present application). If the wallet to be created is a passive wallet (the passive wallet may correspond to an encrypted resource data storage container belonging to a passive container type in the present application), the wallet APP sends a first trigger message indicating that the object triggers an agreement to create a control to a merchant wallet APP (the merchant wallet APP may correspond to a second client in the present application), the merchant wallet APP generates a passive wallet creation request after receiving the first trigger message, the passive wallet creation request includes wallet characteristics (e.g., a wallet address that can transact with the wallet, a life cycle of the wallet, transaction rules of the wallet, etc.), the merchant wallet APP sends the passive wallet creation request to the object wallet APP, the object checks the passive wallet creation request to see whether the check is in accordance with an expectation, and if the check is that the object can click a button "ok", the object wallet sends the passive wallet creation request to a wallet background server, the wallet background server authenticates the passive wallet creation request and verifies wallet characteristics. And when the verification is passed, the wallet background server creates a passive wallet under the main wallet of the object, wherein the created active wallet is a sub-wallet of the main wallet. And 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.
Optionally, the container creation reminder message further includes a modification container control, the object can click on 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 a plurality of first sub-encryption resource data storage containers with container types being active container types from the plurality of first sub-encryption resource data storage containers according to the third trigger message, the object can select a first sub-encryption resource data storage container (called as an auxiliary first sub-encryption resource data storage container) with a transaction container address to be modified from the selected plurality of first sub-encryption resource data storage containers, and the transaction container address of the auxiliary first sub-encryption resource data storage container is modified into a container address of the second encryption resource data storage container. And the first client takes 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.
For example, there are 3 original encrypted resource data storage containers, which are 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, respectively, and 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 a modified container control in the container creation reminding 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, so that the first client can modify the transaction container address of the original encrypted resource data storage container 1 from "123" to "234", and certainly, the transaction container addresses of the original encrypted resource data storage container 2 and the original encrypted resource data storage container 3 are not changed, and 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 with the modified transaction container addresses are all used as the first sub-encrypted resource data storage container.
Step S202, 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.
It can be known that, in the plurality of first sub encrypted resource data storage containers, the transaction container address of one first sub encrypted resource data storage container must be the same as the container address of the second encrypted resource data storage container. The first client determines a transaction container address (referred to as a target transaction container address) that is the same as the container address of the second encrypted resource data storage container from among the transaction container addresses of the plurality of first sub-encrypted resource data storage containers.
Step S203, using 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.
Specifically, the first client uses a first sub-encrypted resource data storage container corresponding to the target transaction container address as a target first sub-encrypted resource data storage container.
Optionally, the container creation alert message further includes a disapproval creation control, the object may click on the disapproval creation control, and the first client generates a trigger message (referred to as a second trigger message) for the disapproval creation control. And the first client transfers the resource data (which can be encrypted) with the same amount of resource transferred 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.
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 transaction addresses on the block chain, and a specific process of transferring resource data (which can transfer encrypted 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 is as follows: the first client generates third transaction data, wherein the third transaction data comprises: the container address of the first encrypted resource data storage container is a roll-out address, and the container address of the second encrypted resource data storage container is a roll-in address. The first client stores the generated third transaction data into the blockchain, wherein a process of storing the third transaction data into the blockchain is the same as the process of storing the first transaction data into the blockchain, and the third transaction data is only replaced by the first transaction data as the processing object, which is not described herein again.
In colloquial, if the object refuses to create a new encrypted resource data storage container or modifies the transaction container address of the original encrypted resource data storage container, the encrypted resource data corresponding to the transaction request is paid by the master wallet.
According to the method, the sub-encryption resource data storage container can be created in real time, and management of the sub-encryption resource data storage container by an object can be facilitated; furthermore, when the matched sub-encryption resource data storage container is not stored in the original sub-encryption resource storage container and the object does not agree with the creation of a new sub-encryption resource data storage container, transaction payment is carried out by the main encryption resource data storage container, so that the success rate of transaction can be ensured, and the transaction failure can be prevented.
Referring to fig. 7, fig. 7 is a schematic flowchart of a data processing method according to an embodiment of the present application, where the data processing method includes the following steps:
in step S301, the receiver wallet APP sends transaction information to the sender wallet APP.
Specifically, the receiving-side wallet APP may correspond to a second client in the application, the sending-side wallet APP may correspond to a first client in the application, the transaction information may correspond to a transaction request in the application, the transaction information includes a wallet address of the receiving-side wallet APP, a receiving resource amount, and a wallet type, and the wallet type is used for determining a wallet type when the sending side needs to create a new wallet subsequently. The receiving side wallet APP can convert the transaction request into the two-dimensional code image, and the two-dimensional code image is sent to the sending side wallet APP.
And step S302, matching the sender wallet APP in the custom wallet list, and determining the matched custom wallet.
Specifically, the wallet APP of the sender identifies the two-dimensional code image to obtain transaction information. And the sender wallet APP searches the custom wallet matched with the wallet address of the receiver wallet APP in the custom wallet list according to the wallet address of the receiver wallet APP in the transaction information. The user-defined wallet may correspond to the first sub-encrypted resource data storage container in the application.
If the wallet address of the sender wallet APP is found in the custom wallet list to be matched with the wallet address of the receiver wallet APP, executing step S303, namely finding out that the custom wallet is the wallet to be paid; if the sending-side wallet APP does not find a wallet address matching the receiving-side wallet APP in the custom wallet list, step S304 is executed.
And step S303, the sender wallet APP generates an order according to the transaction information.
Step S304, inquiring whether the object creates a new custom wallet, and if the object chooses to approve creating the custom wallet, executing step S305; if the object selection does not agree to create the custom wallet, go to step S306.
Step S305, the sending-side wallet APP creates a custom wallet according to the wallet type in the transaction information, where the created custom wallet may be an active wallet or a passive wallet.
The specific process of creating the active wallet may refer to the description of the embodiment corresponding to fig. 5, and the specific process of creating the passive wallet may refer to the description of the embodiment corresponding to fig. 6.
Step S306, the subject is asked whether the subject agrees to pay using the master wallet.
The primary wallet may correspond to the first encrypted resource data storage container in the present application. If the subject agrees to pay using the master wallet, go to step S303, i.e., the master wallet is the wallet to be paid; if the subject does not agree to pay using the primary wallet, step S310 is performed.
In step S307, the sender wallet APP checks whether the order complies with the transaction rules of the wallet to be paid. If yes, go to step S308, otherwise go to step S310.
At step S308, the sender wallet APP makes payment using the wallet to be paid.
It will be appreciated that the purse to be paid is either a found custom purse, a newly created custom purse, or a master purse.
In step S309, a transaction success notification message is generated.
In step S310, a transaction failure notification message is generated.
Further, please refer to fig. 8, which is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application. As shown in fig. 8, the data processing apparatus 1 may be the first client in the embodiment corresponding to fig. 3 to fig. 7, specifically, the data processing apparatus 1 may 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 device 1 may be configured to perform corresponding steps in the method provided by the embodiment of the present application.
The data processing apparatus 1 is registered with a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers under the first encrypted resource data storage container, and the data processing apparatus 1 may include: an acquisition module 11, a search module 12 and a first transaction module 13.
An obtaining module 11, configured to obtain a transaction request, where the transaction request includes a container address of a second encrypted resource data storage container;
the searching module 12 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 a plurality of first sub encrypted resource data storage containers belonging to a first encrypted resource data storage container;
and a first transaction module 13, configured to execute a business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
In one embodiment, the obtaining module 11 is specifically configured to:
receiving a two-dimensional code image sent by a second client;
and identifying the two-dimension code image to obtain an original transaction request, performing signature verification on the original transaction request, and taking the original transaction request as the transaction request if the signature verification is passed.
The specific functional implementation manners of the obtaining module 11, the searching module 12 and the first transaction module 13 may refer to steps S101 to S103 in the embodiment corresponding to fig. 3.
Referring to fig. 8, the lookup module 12 may include: an acquisition unit 121 and a lookup unit 122.
An obtaining unit 121, configured to obtain a plurality of first sub-encrypted resource data storage containers, where each first sub-encrypted resource data storage container includes a transaction container address of a storage container to be transacted;
the searching unit 122 is configured to determine, from transaction container addresses of multiple first sub-encrypted resource data storage containers, a target transaction container address that is the same as the container address of the second encrypted resource data storage container, and use a first sub-encrypted resource data storage container corresponding to the target transaction container address as the target first sub-encrypted resource data storage container.
In one embodiment, the obtaining unit 121 may include: an acquisition subunit 1211 and a first determination subunit 1212.
An obtaining sub-unit 1211, configured to obtain a plurality of original encrypted resource data storage containers, each original encrypted resource data storage container including a transaction container address of a storage container to be transacted, each original encrypted resource data storage container being a sub-container of the first encrypted resource data storage container;
the acquiring subunit 1211 is further configured to traverse transaction container addresses of the plurality of original encrypted resource data storage containers;
a first determining subunit 1212, configured to, if a transaction container address that is the same as the container address of the second encrypted resource data storage container exists in the transaction container addresses of the multiple original encrypted resource data storage containers, use the multiple original encrypted resource data storage containers as the multiple first sub encrypted resource data storage containers.
In one embodiment, the obtaining unit 121 may include: an acquisition subunit 1211 and a first determination subunit 1212; the method can also comprise the following steps: a display sub-unit 1213 and a create sub-unit 1214.
A display subunit 1213, configured to display a container creation prompting message 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 multiple original encrypted resource data storage containers, where the container creation prompting message includes an agreement creation control;
a creating subunit 1214, configured to create, if a first trigger message for the creation approval control is received, an encrypted resource data storage container according to the first trigger message, where a transaction container address of the created encrypted resource data storage container is a container address of the second encrypted resource data storage container, and the created encrypted resource data storage container is a child container of the first encrypted resource data storage container;
the display subunit 1213 is further configured to use 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.
In an embodiment, the creating sub-unit 1214, when being configured to create the encrypted resource data storage container according to the first trigger message, is specifically configured to:
acquiring a container creation request according to the first trigger message, wherein the container creation request comprises a container address of the second encrypted resource data storage container;
and sending the container creation request to a background server, enabling the background server to perform request verification on the container creation request, creating an encrypted resource data storage container by the background server according to the container address of the second encrypted resource data storage container after the request verification is passed, and taking the created encrypted resource data storage container as a sub-container of the first encrypted resource data storage container.
In one embodiment, the container creation reminder message further includes a disapproval creation control, the transaction request further includes an amount of transfer resources;
the data processing apparatus 1 may include: the system comprises an acquisition module 11, a search module 12 and a first transaction module 13; the method can also comprise the following steps: a second transaction module 14.
A second transaction module 14, configured to, if a second trigger message for the creation of the control block that is not agreed to is received, transfer, according to the second trigger message, resource data that is equal to the transferred 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.
The specific functional implementation manners of the obtaining unit 121, the searching unit 122, the obtaining sub-unit 1211, the first determining sub-unit 1212, the displaying sub-unit 1213, the creating sub-unit 1214, and the second transaction module 14 may refer to steps S201 to S203 in the embodiment corresponding to fig. 4.
Referring to fig. 9, 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 transaction addresses on the blockchain, and the transaction request further includes a transfer resource amount;
the first transaction module 13 may include: a generating unit 131 and a storing unit 132.
A generating unit 131, configured to generate first transaction data according to the transaction request, where the first transaction data includes a container address of the target first sub encrypted resource data storage container, a container address of the second encrypted resource data storage container, and the transfer resource amount;
a storage unit 132, configured to store the first transaction data to the blockchain, where the first transaction data stored to the blockchain represents a transfer of data equivalent to the transfer resource amount 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.
In one embodiment, the generating unit 131 may include: a first generation subunit 1311.
A first generating subunit 1311, 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.
In one embodiment, the container address of the first encrypted resource data storage container is a transaction address on the blockchain;
the generation unit 131 may include a first generation sub-unit 1311; the method can also comprise the following steps: a second generation subunit 1312.
A second generating subunit 1312, configured to generate second transaction data if the remaining resource amount is smaller than the transfer resource amount, where the second transaction data includes 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, store the second transaction data to the block chain, and the second transaction data stored to the block chain represents 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 second generating subunit 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.
For specific functional implementation manners of the generating unit 131, the storing unit 132, the first generating sub-unit 1311, and the second generating sub-unit 1312, reference may be made to step S103 in the above embodiment corresponding to fig. 3.
Further, please refer to fig. 9, which is a schematic structural diagram of a computer device according to an embodiment of the present application. The terminal device where the first client is located in the above embodiments corresponding to fig. 3 to fig. 7 may be the computer device 1000. As shown in fig. 9, the computer apparatus 1000 may include: an object interface 1002, a processor 1004, an encoder 1006, and a memory 1008. Signal receiver 1016 is used to receive or transmit data via cellular interface 1010, WIFI interface 1012. The encoder 1006 encodes the received data into a computer-processed data format. The memory 1008 has stored therein a computer program by which the processor 1004 is arranged to perform the steps of any of the method embodiments described above. The memory 1008 may include volatile memory (e.g., dynamic random access memory DRAM) and may also include non-volatile memory (e.g., one time programmable read only memory OTPROM). In some instances, the memory 1008 can further include memory located remotely from the processor 1004, which can be connected to the computer device 1000 via a network. The object interface 1002 may include: a keyboard 1018, and a display 1020.
In the computer device 1000 shown in fig. 9, the computer device 1000 is registered with a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers under the first encrypted resource data storage container, and the processor 1004 may be configured to call the memory 1008 to store a computer program to implement:
obtaining a transaction request, wherein the transaction request comprises 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 under a first encrypted resource data storage container;
and executing business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
In one embodiment, the processor 1004, when executing the step of determining a target first sub encrypted resource data storage container matching the container address of the second encrypted resource data storage container from among a plurality of first sub encrypted resource data storage containers that are under the first encrypted resource data storage container, specifically performs the following steps:
acquiring a plurality of first sub-encrypted resource data storage containers, wherein each first sub-encrypted resource data storage container comprises a transaction container address of a storage container to be transacted;
determining a target transaction container address from the transaction container addresses of a plurality of first sub-encrypted resource data storage containers that is the same as the container address of the second encrypted resource data storage container;
and taking a first sub-encryption resource data storage container corresponding to the target transaction container address as the target first sub-encryption resource data storage container.
In one embodiment, the processor 1004, when executing the step of obtaining the plurality of first sub-encrypted resource data storage containers, specifically performs the following steps:
acquiring a plurality of original encrypted resource data storage containers, wherein each original encrypted resource data storage container comprises a transaction container address of a storage container to be transacted, and each original encrypted resource data storage container is a sub-container of a first encrypted resource data storage container;
traversing transaction container addresses of the plurality of original encrypted resource data storage containers;
and if the transaction container address identical to the container address of the second encrypted resource data storage container exists 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.
In one embodiment, the processor 1004 further performs the following steps:
if the transaction container address identical to the container address of the second encrypted resource data storage container does not exist in the transaction container addresses of the plurality of original encrypted resource data storage containers, displaying a container creation reminding message, wherein the container creation reminding message comprises an agreement creation control;
if a first trigger message aiming at the control which is allowed to be created is received, creating an encrypted resource data storage container according to the first trigger message, wherein 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;
and taking 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.
In an embodiment, when the processor 1004 executes creating the encrypted resource data storage container according to the first trigger message, specifically, the following steps are executed:
acquiring a container creation request according to the first trigger message, wherein the container creation request comprises a container address of the second encrypted resource data storage container;
and sending the container creation request to a background server, enabling the background server to perform request verification on the container creation request, creating an encrypted resource data storage container by the background server according to the container address of the second encrypted resource data storage container after the request verification is passed, and taking the created encrypted resource data storage container as a sub-container of the first encrypted resource data storage container.
In one embodiment, the container creation reminder message further includes a disapproval creation control, the transaction request further includes an amount of transfer resources;
the processor 1004 also performs the following steps:
and if a second trigger message aiming at the control which is not approved to be created is received, transferring the resource data with the same amount as the transferred 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.
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 transaction addresses on a blockchain, the transaction request further comprising a transfer resource amount;
when executing the business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container, the processor 1004 specifically executes the following steps:
generating first transaction data according to the transaction request, wherein the first transaction data comprises a container address of the target first sub encrypted resource data storage container, a container address of the second encrypted resource data storage container and the transfer resource amount;
storing the first transaction data to the blockchain, the first transaction data stored to the blockchain representing a transfer of data equivalent to the amount of transfer resources 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.
In one embodiment, when the processor 1004 executes the generation of the first transaction data according to the transaction request, the following steps are specifically executed:
acquiring the residual resource amount of the target first sub-encrypted resource data storage container;
and if the residual 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.
In one embodiment, the container address of the first encrypted resource data storage container is a transaction address on the blockchain;
the processor 1004 also performs the following steps:
if the residual resource amount is less than the transfer resource amount, generating second transaction data, wherein the second transaction data comprises 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;
storing the second transaction data to the blockchain, the second transaction data stored to the blockchain representing a transfer of resource data 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 equal to the amount of transfer resource;
and 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.
In one embodiment, the processor 1004, when executing the get transaction request, specifically performs the following steps:
receiving a two-dimensional code image sent by a second client;
and identifying the two-dimension code image to obtain an original transaction request, performing signature verification on the original transaction request, and taking the original transaction request as the transaction request if the signature verification is passed.
It should be understood that the computer device 1000 described in this embodiment of the present application may perform the description of the data processing method in the embodiment corresponding to fig. 3 to fig. 7, and may also perform the description of the data processing apparatus 1 in the embodiment corresponding to fig. 8, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.
Further, here, it is to be noted that: an embodiment of the present application further provides a computer storage medium, and the computer storage medium stores the aforementioned computer program executed by the data processing apparatus 1, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the data processing method in the embodiment corresponding to fig. 3 to 7 can be performed, so that details are not repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in the embodiments of the computer storage medium referred to in the present application, reference is made to the description of the embodiments of the method of the present application. By way of example, program instructions may be deployed to be executed on one computer device or on multiple computer devices at one site or distributed across multiple sites and interconnected by a communication network, and the multiple computer devices distributed across the multiple sites and interconnected by the communication network may be combined into a blockchain network.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and executes the computer instruction, so that the computer device can perform the method in the embodiment corresponding to fig. 3 to fig. 7, and therefore, the detailed description thereof will not be repeated here.
All or part of the processes in the methods of the embodiments may be implemented by a computer program that can be stored in a computer-readable storage medium and that, when executed, can include the processes of the embodiments of the methods. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.

Claims (13)

1. A data processing method, applied to a first client, where the first client registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers under the first encrypted resource data storage container, and the method includes:
obtaining a transaction request, wherein the transaction request comprises 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 under a first encrypted resource data storage container;
and executing business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
2. The method of claim 1, wherein determining a target first sub-encrypted resource data storage container from a plurality of first sub-encrypted resource data storage containers that are under a first encrypted resource data storage container that matches a container address of the second encrypted resource data storage container comprises:
acquiring a plurality of first sub-encrypted resource data storage containers, wherein each first sub-encrypted resource data storage container comprises a transaction container address of a storage container to be transacted;
determining a target transaction container address from the transaction container addresses of the plurality of first sub-encrypted resource data storage containers that is the same as the container address of the second encrypted resource data storage container;
and taking a first sub-encryption resource data storage container corresponding to the target transaction container address as the target first sub-encryption resource data storage container.
3. The method of claim 2, wherein obtaining the plurality of first sub-encrypted resource data storage containers comprises:
acquiring a plurality of original encrypted resource data storage containers, wherein each original encrypted resource data storage container comprises a transaction container address of a storage container to be transacted, and each original encrypted resource data storage container is a sub-container of a first encrypted resource data storage container;
traversing transaction container addresses of the plurality of original encrypted resource data storage containers;
and if the transaction container address identical to the container address of the second encrypted resource data storage container exists 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, further comprising:
if the transaction container address identical to the container address of the second encrypted resource data storage container does not exist in the transaction container addresses of the plurality of original encrypted resource data storage containers, displaying a container creation reminding message, wherein the container creation reminding message comprises an agreement creation control;
if a first trigger message aiming at the control which is allowed to be created is received, creating an encrypted resource data storage container according to the first trigger message, wherein 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;
and taking 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.
5. The method of claim 4, wherein the creating an encrypted resource data storage container from the first trigger message comprises:
acquiring a container creation request according to the first trigger message, wherein the container creation request comprises a container address of the second encrypted resource data storage container;
and sending the container creation request to a background server, enabling the background server to perform request verification on the container creation request, creating an encrypted resource data storage container by the background server according to the container address of the second encrypted resource data storage container after the request verification is passed, and taking the created encrypted resource data storage container as a sub-container of the first encrypted resource data storage container.
6. The method of claim 4, wherein the container creation reminder message further comprises not agreeing to create a control, wherein the transaction request further comprises an amount of resources to transfer;
the method further comprises the following steps:
and if a second trigger message aiming at the control which is not approved to be created is received, transferring the resource data with the same amount as the transferred 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.
7. The method of claim 1, wherein 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 transaction addresses on a blockchain, the transaction request further comprising an amount of transfer resources;
the executing the business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container comprises:
generating first transaction data according to the transaction request, wherein the first transaction data comprises a container address of the target first sub encrypted resource data storage container, a container address of the second encrypted resource data storage container and the transfer resource amount;
storing the first transaction data to the blockchain, the first transaction data stored to the blockchain representing a transfer of data equivalent to the amount of transfer resources 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.
8. The method of claim 7, wherein generating first transaction data from the transaction request comprises:
acquiring the residual resource amount of the target first sub-encrypted resource data storage container;
and if the residual 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.
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 the following steps:
if the residual resource amount is less than the transfer resource amount, generating second transaction data, wherein the second transaction data comprises 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;
storing the second transaction data to the blockchain, the second transaction data stored to the blockchain representing a transfer of resource data 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 equal to the amount of transfer resource;
and 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.
10. The method of claim 1, wherein obtaining the transaction request comprises:
receiving a two-dimensional code image sent by a second client;
and identifying the two-dimension code image to obtain an original transaction request, performing signature verification on the original transaction request, and taking the original transaction request as the transaction request if the signature verification is passed.
11. A data processing apparatus, wherein the data processing apparatus registers a first encrypted resource data storage container and a plurality of first sub-encrypted resource data storage containers under the first encrypted resource data storage container, the apparatus comprising:
an obtaining module, configured to obtain a transaction request, where the transaction request includes a container address of a second encrypted resource data storage container;
the searching module is used for determining a target first sub-encrypted resource data storage container matched with 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;
and the first transaction module is used for executing business operation corresponding to the transaction request based on the target first sub-encrypted resource data storage container.
12. A computer arrangement comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to carry out the steps of the method of any of claims 1-10.
13. A computer storage medium, characterized in that the computer storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method of any one of claims 1-10.
CN202210073251.7A 2020-09-09 2020-09-09 Data processing method, data processing device, computer equipment and storage medium Pending CN114493871A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210073251.7A CN114493871A (en) 2020-09-09 2020-09-09 Data processing method, data processing device, computer equipment and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210073251.7A CN114493871A (en) 2020-09-09 2020-09-09 Data processing method, data processing device, computer equipment and storage medium
CN202010943317.4 2020-09-09

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN202010943317.4 Division 2020-09-09 2020-09-09

Publications (1)

Publication Number Publication Date
CN114493871A true CN114493871A (en) 2022-05-13

Family

ID=81534711

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210073251.7A Pending CN114493871A (en) 2020-09-09 2020-09-09 Data processing method, data processing device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114493871A (en)

Similar Documents

Publication Publication Date Title
US20210150521A1 (en) Blockchain-based privacy transaction and blockchain-based privacy transaction application methods and apparatuses
CN109756582B (en) Information recording method, device, node and storage medium in block chain network
US11451400B2 (en) Blockchain transaction method and apparatus
US20160342977A1 (en) Device, method and system for virtual asset transactions
CN111681003A (en) Resource cross-chain transfer method and device, computer equipment and storage medium
CN110839029B (en) Micro-service registration method and device
CN113874897A (en) Computer-implemented system and method for effecting transfers over blockchain networks
CN110336779B (en) Block chain construction method and device and electronic equipment
CN111047321A (en) Service processing method and device, electronic equipment and storage medium
CN111597567B (en) Data processing method, data processing device, node equipment and storage medium
CN112367164B (en) Service request processing method and device, computer equipment and storage medium
CN104301293A (en) Data processing method, device and system
CN111178840A (en) Service processing method, device, system, electronic equipment and storage medium
CN113850575A (en) Resource processing method and device
CN110910109B (en) Electronic resource transfer method and device based on block chain
CN115705601A (en) Data processing method and device, computer equipment and storage medium
US20230237476A1 (en) Electronic wallet, server for executing the same, and method for atomic exchange of blockchain tokens using the server
WO2022095426A1 (en) Blockchain-based joint account creation method, system, device, and storage medium
CN114493871A (en) Data processing method, data processing device, computer equipment and storage medium
CN110535664B (en) Data processing method and device based on block chain, server and storage medium
CN110098928B (en) Key generation method and device for collaborative signature
CN114418769A (en) Block chain transaction charging method and device and readable storage medium
CN111340479A (en) Service processing method and device
CN115860745B (en) Secret payment-free signing method, gateway equipment and storage medium
CN116743377B (en) Data processing method, device, equipment and storage medium based on blockchain key

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination