Resource processing method and device, equipment and medium

Abstract

The invention provides a resource processing method and device, equipment and a medium. The method comprises the steps of outputting a first interface in response to a selection operation for a first account address, generating a first resource transfer transaction in response to a resource transfer operation for a target resource, sending the first resource transfer transaction to a block chain node through a resource server, receiving cross-level transfer information, and transmitting the cross-level transfer information to the block chain node. Displaying a second interface in response to an address confirmation operation for a second account address in the cross-level transfer information, generating a second resource transfer transaction in response to a resource transfer operation for supplementary resources, sending the second resource transfer transaction to the block chain node through the resource server, receiving resource update information, and sending the resource update information to the block chain node. And when determining that the resource quota of the updated first-level resource reaches the resource quota of the target resource based on the resource updating information, sending the first resource transfer transaction to the block chain node through the resource server. According to the invention, the flexibility and success rate of resource transfer can be improved.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular, to a resource processing method, apparatus, device, and medium. Background Art

[0002] Currently, a business object (e.g., enterprise A) can initiate a resource transfer transaction to a blockchain node (such as a transfer transaction for the business resources of enterprise A). The blockchain node can transfer the to-be-transferred resources indicated by the resource transfer transaction from the account address of enterprise A on the blockchain to a specified account address (such as the account address of enterprise B on the blockchain) to achieve the resource transfer of enterprise-level business resources.

[0003] However, the inventors found in practice that all the business resources of enterprise A on the chain are stored in the account address of enterprise A. Once enterprise A initiates a resource transfer transaction and the resource value of the to-be-transferred resources indicated by the resource transfer transaction exceeds the resource value of the business resources stored in the account address of enterprise A, the blockchain node cannot execute the resource transfer transaction, which directly leads to the failure of the resource transfer, thereby reducing the flexibility and success rate of the resource transfer. Summary of the Invention

[0004] Embodiments of this application provide a resource processing method, apparatus, device, and medium, which can improve the flexibility and success rate of resource transfer.

[0005] On the one hand, embodiments of this application provide a resource processing method, which is executed by a resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store the first-level resources of the business object; the second account address is used to store the second-level resources of the business object; the address level of the first account address is lower than that of the second account address; the method includes:

[0006] On the address display interface of the resource client, display the first account address and the second account address, and in response to the selection operation of the business object for the first account address, output a first interface corresponding to the first account address;

[0007] In response to the resource transfer operation of the target resource on the first interface by the business object, generate a first resource transfer transaction, and send the first resource transfer transaction to the blockchain node through the resource server corresponding to the resource client, so that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resource, generate cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer the business resources in the second account address across levels to the first account address;

[0008] Receive cross - level transfer information, and in response to the address confirmation operation of the business object for the second account address in the cross - level transfer information, display the second interface corresponding to the second account address;

[0009] In response to the resource transfer operation of the business object for the supplementary resources on the second interface, generate a second resource transfer transaction, and send the second resource transfer transaction to the blockchain node through the resource server, so that when the blockchain node transfers the supplementary resources in the second - level resources from the second account address to the first account address and updates the first - level resources based on the supplementary resources, a resource update information is generated; the supplementary resources are determined based on the resource difference between the first - level resources and the target resources;

[0010] Receive the resource update information. When it is determined based on the resource update information that the resource amount of the updated first - level resources reaches the resource amount of the target resources, send the first resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the target resources from the first account address to the target account address indicated by the first resource transfer transaction.

[0011] On the other hand, an embodiment of the present application provides a resource processing method, which is executed by the resource server corresponding to the resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store the first - level resources of the business object; the second account address is used to store the second - level resources of the business object; the address level of the first account address is lower than the address level of the second account address; the method includes:

[0012] When receiving the first resource transfer transaction sent by the resource client, send the first resource transfer transaction to the blockchain node, so that when the blockchain node detects that the resource amount of the first - level resources is less than the resource amount of the target resources indicated by the first resource transfer transaction, generate cross - level transfer information; the cross - level transfer information is used to instruct the business object to transfer the business resources in the second account address across levels to the first account address; the first resource transfer transaction is generated by the resource client in response to the resource transfer operation of the business object for the target resources on the first interface of the first account address; the first interface is output on the address display interface of the resource client when the first account address and the second account address are displayed and in response to the selection operation of the business object for the first account address;

[0013] When receiving the cross - level transfer information, send the cross - level transfer information to the resource client, so that the resource client, in response to the address confirmation operation of the business object for the second account address in the cross - level transfer information, displays the second interface corresponding to the second account address, and in response to the resource transfer operation of the business object for the supplementary resources on the second interface, generates a second resource transfer transaction;

[0014] When receiving a second resource transfer transaction, send the second resource transfer transaction to the blockchain node, so that when the blockchain node transfers the supplementary resources in the second-level resources from the second account address to the first account address and updates the first-level resources based on the supplementary resources, a resource update information is generated; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources;

[0015] When receiving the resource update information, send the resource update information to the resource client, so that when the resource client determines that the resource amount of the updated first-level resources reaches the resource amount of the target resources based on the resource update information, send the first resource transfer transaction to the resource server;

[0016] When receiving the first resource transfer transaction, send the first resource transfer transaction to the blockchain node, so that the blockchain node transfers the target resources from the first account address to the target account address indicated by the first resource transfer transaction.

[0017] On the one hand, an embodiment of the present application provides a resource processing device, and the device runs on the resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store the first-level resources of the business object; the second account address is used to store the second-level resources of the business object; the address level of the first account address is lower than the address level of the second account address; the device includes:

[0018] An interface output module, configured to display the first account address and the second account address on the address display interface of the resource client, and output a first interface corresponding to the first account address in response to a selection operation of the business object for the first account address;

[0019] A first transaction processing module, configured to generate a first resource transfer transaction in response to a resource transfer operation of the business object for the target resources on the first interface, and send the first resource transfer transaction to the blockchain node through the resource server corresponding to the resource client, so that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resources, generate a cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer the business resources in the second account address across levels to the first account address;

[0020] The interface output module is further configured to receive the cross-level transfer information, and display a second interface corresponding to the second account address in response to an address confirmation operation of the business object for the second account address in the cross-level transfer information;

[0021] The second transaction processing module is used to generate a second resource transfer transaction in response to a resource transfer operation of a business object for supplementary resources on a second interface, and send the second resource transfer transaction to a blockchain node through a resource server, so that when the blockchain node transfers the supplementary resources in the second-level resources from a second account address to a first account address and updates the first-level resources based on the supplementary resources, a resource update information is generated; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources;

[0022] The first transaction processing module is further used to receive the resource update information, and when it is determined based on the resource update information that the resource amount of the updated first-level resources reaches the resource amount of the target resources, send the first resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the target resources from the first account address to the target account address indicated by the first resource transfer transaction.

[0023] On the other hand, an embodiment of the present application provides a resource processing device, which runs on a resource server corresponding to a resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store the first-level resources of the business object; the second account address is used to store the second-level resources of the business object; the address level of the first account address is lower than the address level of the second account address; the device includes:

[0024] The first transaction sending module is used to send the first resource transfer transaction to the blockchain node when receiving the first resource transfer transaction sent by the resource client, so that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resources indicated by the first resource transfer transaction, a cross-level transfer information is generated; the cross-level transfer information is used to instruct the business object to transfer the business resources in the second account address across levels to the first account address; the first resource transfer transaction is generated by the resource client in response to a resource transfer operation of the business object for the target resources on a first interface of the first account address; the first interface is output on the address display interface of the resource client when the first account address and the second account address are displayed and in response to a selection operation of the business object for the first account address;

[0025] The information sending module is used to send the cross-level transfer information to the resource client when receiving the cross-level transfer information, so that when the resource client responds to an address confirmation operation of the business object for the second account address in the cross-level transfer information, display a second interface corresponding to the second account address, and in response to a resource transfer operation of the business object for the supplementary resources on the second interface, generate a second resource transfer transaction;

[0026] The second transaction sending module is configured to, when receiving a second resource transfer transaction, send the second resource transfer transaction to a blockchain node, so that the blockchain node generates resource update information when transferring supplementary resources in the second-level resources from a second account address to a first account address and updating the first-level resources based on the supplementary resources; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources.

[0027] The information sending module is further configured to, when receiving the resource update information, send the resource update information to a resource client, so that the resource client sends a first resource transfer transaction to a resource server when determining that the resource amount of the updated first-level resources reaches the resource amount of the target resources based on the resource update information.

[0028] The first transaction sending module is further configured to, when receiving the first resource transfer transaction, send the first resource transfer transaction to a blockchain node, so that the blockchain node transfers the target resources from the first account address to the target account address indicated by the first resource transfer transaction.

[0029] On the one hand, an embodiment of the present application provides a computer device, including a memory and a processor. The memory is connected to the processor. The memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method provided in the above aspect of the embodiment of the present application.

[0030] On the one hand, an embodiment of the present application provides a computer-readable storage medium. A computer program is stored in the computer-readable storage medium. The computer program is suitable for being loaded and executed by a processor so that a computer device with a processor executes the method provided in the above aspect of the embodiment of the present application.

[0031] According to one aspect of the present application, a computer program product is provided. The computer program product includes a computer program, and the computer program is executed by a processor to implement the method provided in the above aspect of the embodiment of the present application.

[0032] In the embodiments of the present application, partial business resources of a business object can be stored by multiple account addresses respectively. For example, the first-level resources are stored by the first account address, and the second-level resources are stored by the second account address, and the address level of the first account address is lower than that of the second account address. In this way, when the resource client generates a first resource transfer transaction through a resource transfer operation of the target resource on the first interface corresponding to the first account address, the first resource transfer transaction can be sent to the blockchain node through the resource server. When the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resource, it can generate cross-level transfer information to instruct the business object to transfer a certain amount of business resources from the second account address to the first account address. At this time, in response to the address confirmation operation of the business object for the second account address in the cross-level transfer information, the second interface corresponding to the second account address can be displayed. In this way, when the resource client generates a second resource transfer transaction through a resource transfer operation of supplementary resources on the second interface corresponding to the second account address, the second resource transfer transaction can be sent to the blockchain node through the resource server. The blockchain node can transfer the supplementary resources in the second-level resources from the second account address to the first account address, and generate resource update information when updating the first-level resources based on the supplementary resources, that is, supplement the first-level resources in the first account address with the second-level resources in the second account address. When the resource client determines that the resource amount of the updated first-level resources reaches the resource amount of the target resource (that is, the first resource transfer transaction can be executed through the updated first-level resources), the first resource transfer transaction can be sent to the blockchain node through the resource server. The blockchain node can transfer the target resource from the first account address to the target account address indicated by the first resource transfer transaction to implement the resource transfer of the business object. Therefore, by storing business resources in multiple levels, when the business resources at the lower level are insufficient, a certain amount of business resources can be transferred from the higher-level business resources to the lower level, so that the resource transfer transaction at the lower level can be successfully executed, thereby improving the flexibility and success rate of resource transfer. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0034] Figure 1 It is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0035] Figure 2 It is a schematic diagram of the process of a resource transfer provided by an embodiment of the present applicationFigure 1 ;

[0036] Figure 3 is a schematic diagram of a resource transfer process provided by an embodiment of the present application Figure 2 ;

[0037] Figure 4 is a schematic diagram of a resource transfer process provided by an embodiment of the present application Figure 3 ;

[0038] Figure 5 is a schematic flow diagram of a resource processing method provided by an embodiment of the present application;

[0039] Figure 6 is a schematic diagram of a process for generating cross - level transfer information provided by an embodiment of the present application Figure 1 ;

[0040] Figure 7 is a schematic diagram of a process for generating cross - level transfer information provided by an embodiment of the present application Figure 2 ;

[0041] Figure 8 is a schematic diagram of a process for generating cross - level transfer information provided by an embodiment of the present application Figure 3 ;

[0042] Figure 9 is a schematic diagram of a resource processing framework provided by an embodiment of the present application;

[0043] Figure 10 is a schematic diagram of a resource processing scenario provided by an embodiment of the present application;

[0044] Figure 11 is a schematic flow diagram of a resource processing method provided by an embodiment of the present application Figure 2 ;

[0045] Figure 12 is a schematic diagram of a resource transfer process provided by an embodiment of the present application Figure 1 ;

[0046] Figure 13 is a schematic diagram of a resource transfer process provided by an embodiment of the present application Figure 2 ;

[0047] Figure 14 is a schematic diagram of an interaction process of resource transfer provided by an embodiment of the present application Figure 1 ;

[0048] Figure 15 is a schematic diagram of an interaction process of resource transfer provided by an embodiment of the present application Figure 2 ;

[0049] Figure 16It is a schematic diagram of an interaction process for resource transfer provided by an embodiment of the present application Figure 3 ;

[0050] Figure 17 It is a schematic structural diagram of a resource processing device provided by an embodiment of the present application Figure 1 ;

[0051] Figure 18 It is a schematic structural diagram of a resource processing device provided by an embodiment of the present application Figure 2 ;

[0052] Figure 19 It is a schematic structural diagram of a computer device provided by an embodiment of the present application. Detailed implementation manners

[0053] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0054] Please refer to Figure 1 , Figure 1 which is a schematic diagram of a network architecture provided by an embodiment of the present application. As Figure 1 shown, the network architecture can be applied to a blockchain system, and the blockchain system can be a distributed system formed by connecting multiple nodes in a network communication manner. Among them, the blockchain system can include but is not limited to the blockchain system corresponding to a consortium chain.

[0055] Among them, it can be understood that blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithms. It is mainly used to sort data in chronological order, encrypt it into a ledger, making it impossible to be tampered with or forged, and at the same time, data verification, storage, and update can be carried out. Blockchain is essentially a decentralized database. Each node in this database stores an identical blockchain. The blockchain network divides nodes into core nodes and light nodes. Among them, core nodes can be responsible for the consensus of the entire blockchain network. That is to say, the core nodes here can be consensus nodes in the blockchain network. It should be understood that when any node (for example, a light node) in the blockchain network receives transaction data (which can also be simply referred to as a transaction) sent by a client, it can pass the transaction in the form of a relay among the light nodes in the blockchain network until the consensus node (i.e., the main core node in the blockchain network) used for packing in this blockchain network receives the transaction. Then, the transaction can be further added to the transaction pool of this main core node, so that subsequently, the consensus node (i.e., the main core node) used for packing can pack this transaction and other transactions in the transaction pool into a block, and then the block obtained by packing (i.e., the target block) can be broadcast to other consensus nodes (i.e., the slave core nodes in the blockchain network) in this blockchain network, so that other consensus nodes can perform block consensus on the broadcast target block. Thus, when consensus is reached among these consensus nodes, the target block carrying this transaction can be written into the local ledger (for example, written into the transaction cache in the node's memory), so that subsequently, the target block carrying this transaction can be written into the blockchain database corresponding to the target blockchain in this blockchain network (which can also be simply referred to as the database). Among them, the target blockchain here can be understood as the longest chain constructed by these consensus nodes according to the consensus mechanism.

[0056] Among them, it can be understood that a smart contract can be included in the blockchain system. The smart contract can be understood as a piece of code that can be understood and executed among nodes (including consensus nodes) of a blockchain in the blockchain system, and can execute any logic and obtain results. A user can initiate a transaction addition request for a certain transaction to any node in the blockchain network through a resource client (also known as a resource management client). Subsequently, the node (for example, the above-mentioned slave core node or light node) in the blockchain network can send the transaction carried in the transaction addition request to the above-mentioned main core node, so that the main core node can run the smart contract in the node to execute the transaction requested by the user and chain the transaction to the blockchain.

[0057] Among them, it should be understood that one or more smart contracts can be included in the blockchain system. These smart contracts can be distinguished by contract call addresses, contract identification numbers (Identity document, ID), or contract names. In the transaction addition request initiated by the resource client, the contract call address, contract identification number, or contract name of the smart contract can also be carried to specify the smart contract that needs to run. If the smart contract specified by the resource client is a contract that needs to read data (i.e., a data reading contract), then each consensus node can, when executing a transaction, call the data reading contract to quickly access the local ledger (for example, each consensus node can quickly access the multi-level block cache constructed in the node memory through the blockchain structure. Among them, the multi-level block cache is obtained by arranging the block caches of each block according to the indexing method of the block hash values of each block cached in the node memory of each consensus node; a block cache can be used to store the transaction read cache and transaction write cache of each transaction in a block). Finally, each consensus node will mutually verify whether the transaction execution results for this transaction are consistent (that is, conduct consensus). If they are consistent, it can be determined that this transaction is a legal transaction. Furthermore, the transaction execution result of this legal transaction can be stored in the transaction write cache of its respective local ledger, and the transaction execution result of the above transaction can be returned to the resource client.

[0058] It should be understood that, as Figure 1 shown, the network architecture can include a core node (i.e., consensus node) cluster, a server cluster, and a user terminal cluster. Among them, the core node cluster can include one or more core nodes. Here, the multiple core nodes can specifically include Figure 1 the node 10a, node 10b, node 10c, and node 10d shown as Figure 1 shown. As Figure 1 shown, node 10a, node 10b, and node 10d can be respectively network-connected to node 10c to form Figure 1 the consensus network 100a shown as Figure 1 shown. It can be understood that in this consensus network 100a, node 10a, node 10b, and node 10d can all perform data interaction through the network connection with node 10c. In addition, the server cluster can include one or more servers (such as the background server or light node corresponding to the resource client). For ease of understanding, here, taking one server (such as the background server corresponding to the resource client, which can be called the resource server) as an example, this resource server is Figure 1 the server 4000a shown as Figure 1 shown. This server 4000a can perform data interaction through the network connection with Figure 1 shown. The user terminal cluster shown asFigure 1 The user terminals 3000a, 3000b, 3000c, ..., 3000n shown. As Figure 1 shown, the user terminals 3000a, 3000b, 3000c, ..., 3000n can be respectively network-connected to the server 4000a in the server cluster, so as to be able to perform data interaction through the network connection with the server 4000a. For example, the user terminal 3000n can send a resource transfer transaction to the server 4000a, and the server 4000a forwards the resource transfer transaction to the blockchain node. At this time, the data interaction between the user terminal 3000n and the blockchain node needs to transmit data through the server 4000a. That is to say, the user terminal 3000n needs to transfer business resources through the server 4000a. Therefore, the resource server can also be understood as a server on the resource management platform (resource hosting platform) for managing the transfer of on-chain business resources of users.

[0059] Among them, in the embodiments of the present application, each core node (for example, node 10a, node 10b, node 10c, node 10d) and light node in the consensus network 100a can be collectively referred to as blockchain nodes, and these blockchain nodes can all be used to receive transaction addition requests (such as transaction addition requests corresponding to resource transfer transactions) sent by user terminals running resource clients. It should be understood that each of these core nodes can be used to maintain the same blockchain (for example, Figure 1 the blockchain 10e shown can be the target blockchain in the above blockchain network). A peer-to-peer network can be formed between any two core nodes in the consensus network 100a, and the peer-to-peer network can adopt the peer-to-peer protocol. Among them, the peer-to-peer protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP). Among them, it can be understood that in a distributed system, any device such as a server, terminal, etc. can join and become a blockchain node. Among them, each blockchain node can include a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0060] Among them, it can be understood that the embodiments of the present application can bind a blockchain node to any role (for example, any entity object such as any individual user, any enterprise, any institution, etc.) accessing the blockchain network, so as to collectively refer to the blockchain network composed of these blockchain nodes as a consortium blockchain network. So, as Figure 1The nodes 10a, 10b, 10c, and 10d shown can respectively have a one-to-one correspondence with the corresponding roles (i.e., entity objects in the corresponding business scenarios) that need to access this consortium blockchain network. The business scenarios here can include transfer scenarios, electronic bill scenarios, social scenarios, credit purchase scenarios, credit scenarios, etc. At this time, the target business in the corresponding business scenario can specifically include transfer business, electronic bill business, social business, credit purchase business, credit business, etc. Here, the specific businesses in the corresponding business scenarios will not be listed one by one.

[0061] Among them, it can be understood that since each entity object can correspond to a blockchain node, therefore, in the embodiments of this application, the entity object can be taken as the above-mentioned enterprise user (i.e., the aforementioned enterprise) as an example. At this time, the blockchain nodes associated with each enterprise user can be the same blockchain node (for example, the core nodes in the core node cluster shown above can perform data interaction with the user terminals corresponding to multiple enterprise users). For example, in the blockchain data system, the transfer business (resource transfer business) corresponding to each enterprise can be collectively referred to as a transaction business. Among them, enterprise A can Figure 1 perform data interaction with the node 10a shown through Figure 1 the user terminal 3000a shown to complete the corresponding transaction; and so on, enterprise B can Figure 1 perform data interaction with the node 10a shown through Figure 1 the user terminal 3000b shown to complete the corresponding transaction; enterprise C can Figure 1 perform data interaction with the node 10a shown through Figure 1 the user terminal 3000c shown to complete the corresponding transaction. Figure 1 perform data interaction with the node 10a shown to complete the corresponding transaction.

[0062] Optionally, it can be understood that in the embodiments of this application, the entity objects (such as enterprise A, enterprise B,..., enterprise C) that send transaction addition requests for the above-mentioned transfer business can be collectively referred to as requesting users (business objects). It should be understood that in the embodiments of this application, the above-mentioned light nodes can receive the transaction addition requests sent by the requesting users (such as enterprise A, enterprise B,..., enterprise C), and the above-mentioned core nodes can also receive the transaction addition requests sent by the requesting users (such as enterprise A, enterprise B,..., enterprise C) to achieve enterprise-level business resource transfer. Here, the node types of the blockchain nodes that receive the transaction addition requests will not be limited.

[0063] Optionally, in the consensus network 100a, since the above node 10c can synchronize data with other blockchain nodes to which it has a network connection (which can also be referred to as a session connection), that is, the above node 10c can synchronize corresponding business data information from other blockchain nodes (such as the business data information here can include but is not limited to the transactions in the above transaction addition requests and the blocks in the block synchronization requests), at this time, the core nodes associated with each enterprise user can be different blockchain nodes. For example, the invoicing enterprise A can also pass through Figure 1 the user terminal 3000a shown in Figure 1 to interact with the node 10c shown in Figure 1 ; the invoicing enterprise B can also pass through Figure 1 the user terminal 3000b shown in Figure 1 to interact with the node 10b shown in Figure 1 ; the invoicing enterprise C can also pass through Figure 1 the user terminal 3000c shown in Figure 1 to interact with the server 4000a shown in . It should be understood that by randomly allocating the transaction addition requests sent by different user terminals to the blockchain nodes in the above blockchain system, the network load in the blockchain network can be effectively balanced, thereby improving the processing efficiency of the business data corresponding to the corresponding business.

[0064] It can be understood that when a blockchain node receives a transaction addition request sent by a requesting user corresponding to a certain resource client, it can forward the transaction addition request initiated by the requesting user to the above main core node to verify the legality of the transaction addition request initiated by the first user through the above main core node. In this way, the main core node can add the transaction requested by the requesting user to the transaction pool, so that the transaction data associated with the transaction can be packaged into a block subsequently, so that it can be consensus with other consensus nodes (i.e., the above slave core nodes) subsequently, and thus after the consensus is passed, the block carrying the transaction data can be temporarily stored in the above local ledger, so that the block carrying the transaction data can be written into the above blockchain database (which can also be simply referred to as the database) subsequently.

[0065] Among them, in the technical solution of this application, when a business object initiates a first resource transfer transaction through a resource client, it can first send it to a resource server, and the resource server sends the first resource transfer transaction to a blockchain node. When the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resources, it determines that the first-level resources are insufficient to execute the first resource transfer transaction, and then generates cross-level transfer information. When the resource client receives the cross-level transfer information, it can initiate a second resource transfer transaction and send the second resource transfer transaction to the resource server. The resource server sends the second resource transfer transaction to the blockchain node, and the blockchain node transfers the supplementary resources in the second-level resources to the first account address to supplement the first-level resources. At this time, when the resource client determines that the business resources in the first account address are sufficient to execute the first resource transfer transaction, it resends the first resource transfer transaction to the resource server, and the resource server sends the first resource transfer transaction to the blockchain node. At this time, the blockchain node can successfully execute the first resource transfer transaction, thus realizing the resource transfer of the first-level resources.

[0066] Among them, it can be understood that a business object refers to an object used to initiate a resource transfer transaction, such as a certain enterprise, or a certain user, etc.

[0067] Among them, the resource client can be used to sign or approve business transactions to be uploaded to the chain, and can also be used to manage digital resources on the chain (such as the transfer of digital resources on the chain, etc. The digital resources on the chain can be enterprise assets). For example, the resource client can use the private key information corresponding to the business object to sign the business transaction to be uploaded to the chain. The resource client can be used to implement the resource management business function and realize the communication connection with the decentralized application client based on this resource management business function. The resource client is a tool used to manage and store user digital resources. For example, digital resources (also known as digital assets) can be transferred to other accounts based on the resource client, and digital resources transferred from other accounts can be received based on the resource client. The resource client can be a hardware device or a software program deployed in a terminal device. It can be understood that the resource client has a corresponding resource management contract on the blockchain, and this resource management contract can be used to execute relevant services requested by the resource client, such as resource transfer services, etc.

[0068] It can be understood that the resource client can store the private key of the user's account on the blockchain (i.e., the object key, or the user key). The user's identity on the blockchain is identified by the public key, and the user's assets are managed by the private key. For example, when initiating transactions such as resource transfer, the private key in the resource client is required to sign the business transaction. The blockchain node can verify the signature information through the public key of the user who signed the business transaction, that is, signature verification processing. Only when the signature verification processing is successful, it indicates that the business transaction is correct and the initiator of the business transaction is correct. At this time, the blockchain node that verifies correctly will execute the transaction, and the forged signature will be rejected by the blockchain node and a failure will be prompted.

[0069] It can be understood that in the embodiments of the present application, the resource client stores the private key through the hardware device of the business object or the local trusted execution environment, preventing the leakage of the private key and ensuring the correctness and reliability of the user identity information for transaction operations through the private key.

[0070] It can be seen that in the embodiments of the present application, the business resources of the business object are stored by using the account addresses at different address levels. When the business resources in the account address at the lower level are insufficient, a certain amount of business resources can be transferred from the account address at the higher level to the account address at the lower level to supplement the business resources in the account address at the lower level, ensuring the successful execution of the resource transfer transaction for the account address at the lower level, improving the flexibility and success rate of resource transfer. At the same time, the business resources of the business object are separately stored in account addresses at different levels, and there can be a certain approval mechanism for the resource transfer transactions corresponding to the account addresses at different levels, preventing the random transfer of resources between different account addresses, and improving the resource security of the business object.

[0071] It can be understood that the computer device involved in the embodiments of the present application can be a server or a terminal device. Among them, the server can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The terminal can include, but is not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, etc. The embodiments of the present application can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, intelligent transportation, assisted driving, etc.

[0072] It can be understood that Figure 1It is only an exemplary representation of the possible network architectures of the technical solution of the present application, and does not limit the specific architecture of the technical solution of the present application, that is, the technical solution of the present application can also provide other forms of network architectures.

[0073] For ease of understanding, further, please refer to Figures 2 - 4 , Figures 2 - 4 is a schematic diagram of a resource transfer process provided by an embodiment of the present application. In this scenario, a resource transfer mechanism is proposed, which can improve the flexibility and success rate of resource transfer. Among them, as Figure 2 , the account addresses of the business object on the blockchain include a first account address and a second account address. The address level of the first account address is lower than that of the second account address. The first account address is used to store the first-level resources of the business object; the second account address is used to store the second-level resources of the business object.

[0074] Therefore, the process of resource transfer can be as follows: The resource client in the terminal device 20a can display the first account address and the second account address on the address display interface (interface 1), and in response to the selection operation of the business object (a1) for the first account address, output the first interface (interface 2) corresponding to the first account address. The first interface includes the resource transfer-out address, that is, the first account address. The business object can fill in the resource transfer-in address of the transferred target resource, such as the target account address, and can fill in the resource amount of the target resource to be transferred, such as X1, on the first interface; the business object can initiate a first resource transfer transaction (TX1) for transferring the target resource in the first-level resources on the first interface and send (S21) the first resource transfer transaction to the resource server 20b, and the resource server sends (S22) the first resource transfer transaction to the blockchain node 20c; when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resource, it generates cross-level transfer information and returns (S23) the cross-level transfer information to the resource server, and the resource server returns (S24) the cross-level transfer information to the resource client.

[0075] At this time, as Figure 3, when the resource client receives the cross - level transfer information, it displays a cross - level confirmation interface (Interface 3) based on the cross - level transfer information. This cross - level confirmation interface is used to indicate whether the business object transfers the business resources in the second account address to the first account address, and can, in response to the address confirmation operation (such as triggering a confirmation control) of the business object for the second account address in the cross - level resource transfer confirmation interface, display the second interface (Interface 4) corresponding to the second account address. The first interface includes the resource transfer - out address, that is, the first account address, and includes the resource transfer - in address, that is, the second account address, and can fill in the resource amount of the supplementary resources to be transferred, such as X2. The business object can initiate a second resource transfer transaction (TX2) for transferring the supplementary resources in the second - level resources (which can be determined based on the resource difference between the first - level resources and the target resources) on the second interface, and send (S25) the second resource transfer transaction to the resource server 20b. The resource server 20b sends (S26) the second resource transfer transaction to the blockchain node 20c; the blockchain node 20c transfers the supplementary resources in the second - level resources from the second account address to the first account address (it can be understood that at this time, the resource amount of the second - level resources is greater than or equal to the resource amount of the supplementary resources), and when updating the first - level resources based on the supplementary resources to obtain the updated first - level resources, generates a resource update information. This resource update information is used to indicate the resource amount of the updated first - level resources. The blockchain node can return (S27) the resource update information to the resource server, and the resource server returns (S28) it to the resource client.

[0076] At this time, such as Figure 4 , when the resource client receives the resource update information, and determines that the resource amount of the updated first - level resources reaches the resource amount of the target resources based on the resource update information, it can resend (S29) the first resource transfer transaction to the resource server. The resource server 20b sends (S210) the second resource transfer transaction to the blockchain node 20c; the blockchain node 20c can transfer the target resources in the updated first - level resources from the first account address to the target account address indicated by the first resource transfer transaction, so as to realize the resource transfer of the business resources in the first account address.

[0077] It should be noted that when the resource client in the embodiment of the present application obtains the identity information of the corresponding business object or the blockchain node obtains the account address of the business object, etc., it can display a prompt interface or a pop - up window on the corresponding client. The prompt interface or the pop - up window is used to prompt the business object that the identity information and other data are currently being collected. Only after obtaining the confirmation operation of the business object on this prompt interface or pop - up window (such as the business object confirms the authorization through the resource client), start to execute the relevant steps of data acquisition, otherwise end.

[0078] In addition, it can be understood that in the specific implementation manners of the present application, data such as account addresses and private key information related to business objects such as users, enterprises, and institutions may be involved. When the above embodiments of the present application are applied to specific products or technologies, permissions or consents from business objects such as users, enterprises, and institutions need to be obtained, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards in relevant regions.

[0079] It can be understood that the above scenarios are only examples and do not constitute limitations on the application scenarios of the technical solutions provided by the embodiments of the present application. The technical solutions of the present application can also be applied to other scenarios. For example, as known to those of ordinary skill in the art, with the evolution of system architectures and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0080] Further, please refer to Figure 5 , Figure 5 which is a schematic flowchart of a resource processing method provided by an embodiment of the present application. As Figure 5 shown, the method can be executed by the computer device mentioned above. The computer device can be a terminal device configured with a resource client. For example, the terminal device can be the terminal device 3000a as Figure 1 shown above. The method can specifically include the following steps S101 - step S105:

[0081] S101. On the address display interface of the resource client, display a first account address and a second account address, and in response to a selection operation of a business object for the first account address, output a first interface corresponding to the first account address.

[0082] Among them, the account addresses in the resource client can include a first account address and a second account address. The first account address is used to store the first - level resources of the business object. The second account address is used to store the second - level resources of the business object. The address level of the first account address is lower than the address level of the second account address.

[0083] Optionally, the account addresses in the resource client can further include a third account address, and the third account address is used to store the third - level resources of the business object. The address level of the second account address is lower than the address level of the third account address.

[0084] That is to say, the business resources of a business object can include first-level resources, second-level resources, and third-level resources, and the business resources of the business object are separately stored by account addresses at different levels. For example, if the business object is a bank, the first account address can be used to store the funds in the bank's first-level vault, the second account address can be used to store the funds in the bank's second-level vault, and the third account address can be used to store the resources in the bank's third-level vault, and so on. At this time, a small amount of the business resources of the business object can be stored in the account address with a lower address level, and a large amount of the business resources of the business object can be stored in the account address with a higher address level to ensure the security of the business resources. It can be understood that the address level can refer to the importance level of the business resources. The higher the address level of the account address, the more business resources are stored, the more important the stored business resources are, and the lower the transaction frequency of the resource transfer transaction to be executed.

[0085] It can be understood that the account address of the business object can include account addresses at at least two address levels for separately storing the business resources of the business object. The number of account addresses of the business object is not limited here. When the account address of the business object includes account addresses at two address levels or three address levels, the processes and logics to be executed are the same.

[0086] It can be understood that when a business object initiates a resource transfer transaction (TX1) for business resources in an account address (account address A), and the resource amount of the business resources in the account address A is less than the amount of resources to be transferred indicated by the resource transfer transaction, a resource transfer transaction (TX2) for business resources in the next higher-level account address (account address B) corresponding to the account address A is initiated to transfer the business resources in the account address B to the account address A, so that TX1 can be successfully executed. That is to say, when transferring resources within the account address of a business object (i.e., internal resource transfer for the business object): the business resources in an account address at one address level can only be transferred to an adjacent-level account address (such as the account address at the previous lower address level). For example, when the resource amount of the business resources in the first account address is insufficient, the second-level resources in the second account address can be transferred to the first account address. Another example is that when the resource amount of the business resources in the second account address is insufficient, the third-level resources in the third account address can be transferred to the second account address to facilitate the business resource management of the business object. Another example is that when the resource amount of the business resources in the first account address is greater than a certain threshold, a part of the first-level resources in the first account address can be transferred to the second account address. Another example is that when the resource amount of the business resources in the second account address is greater than a certain threshold, a part of the second-level resources in the second account address can be transferred to the third account address to ensure the security of the business resources of the business object. It can be understood that for resource transfer outside the account address of a business object (i.e., external resource transfer for the business object, that is, the business object transfers its own business resources to other business objects), resource transfer can be carried out according to the resource transfer strategy corresponding to the account address where the resource transfer is carried out.

[0087] Among them, it can be understood that the account addresses at different address levels can be distinguished according to the real-time requirements of business resource transactions. For business resources with the highest real-time requirements for transactions (such as for scenarios with the highest transaction frequencies), that is, business resources that require rapid resource transfer, they can be stored as first-level resources in the first account address with the lowest address level. It can be understood that for business resources that require rapid transactions, the importance is the lowest (such as a small amount of business resources stored in the first account address for daily resource transfer, for example, 20% of the business resources of a business object can be stored in the first account address), and they can be directly sent by the resource server to the blockchain node. For business resources with relatively high real-time requirements for transactions (such as for scenarios with relatively high transaction frequencies), that is, relatively important business resources (such as a large amount of business resources stored in the second account address, for example, 20% of the business resources of a business object can be stored in the first account address), they can be stored as second-level resources in the second account address with a higher address level. It can be understood that at this time, the resource server can adopt a resource transfer strategy corresponding to the second account address to approve the second resource transfer transaction for the second account address, and only after the transaction approval is passed can the second resource transfer transaction be sent to the blockchain node to ensure the security of the resource transfer of the second-level resources.

[0088] Similarly, for business resources with the lowest real-time requirements for transactions (such as for scenarios with relatively low transaction frequencies), that is, particularly important business resources, they can be stored as third-level resources in the third account address with the highest address level. It can be understood that at this time, the resource server can adopt a resource transfer strategy corresponding to the third account address to approve the third resource transfer transaction for the third account address, and only after the transaction approval is passed can the third resource transfer transaction be sent to the blockchain node to ensure the security of the resource transfer of the third-level resources.

[0089] It can be understood that by storing business resources in account addresses at different address levels, and having corresponding resource transfer strategies for account addresses at different address levels, it can ensure the security and reliability of the resource transfer transactions received by the blockchain node, and ensure that it is not easy to transfer business resources between account addresses at different address levels. In this way, even if the business resources in one account address are illegally transferred, the business resources of other account addresses cannot be illegally transferred, avoiding a large loss of the business resources of the business object.

[0090] Among them, the resource client can display the first account address and the second account address on the address display interface. The selection operation for the first account address is used to output and display the first interface corresponding to the first account address. The business object can initiate a resource transfer transaction on the first interface to transfer the business resources in the first account address. Similarly, the selection operation for the second account address is used to output and display the second interface corresponding to the second account address. The business object can initiate a resource transfer transaction on the second interface to transfer the business resources in the second account address.

[0091] It can be understood that when the business object needs to transfer the first-level resources in the first account address, it triggers the selection operation for the first account address on the address display interface. At this time, the business object can fill in the resource amount of the target resources to be transferred and the target account address for transferring the target resources on the first interface, and then can generate the first resource transfer transaction for the first account address. It can be understood that the target resources refer to the business resources to be transferred out from the first-level resources of the first account address, and the resource amount of the target resources is the amount of resources to be transferred indicated by the first resource transfer transaction.

[0092] For example, the address display interface and the first interface can refer to the above Figure 2 example. Among them, the first account address and the second account address are displayed on the first display interface. Optionally, it can also include the third account address. By triggering the selection operation for the first account address, the first interface corresponding to the first account address is displayed. The resource transfer-out address in the first interface is the first account address. The first interface can include a first configuration area for the resource amount of the target resources (i.e., the transfer-out amount of the first-level resources) and a second configuration area for the resource transfer-in address. The second configuration area can be used to configure the account address for transferring the target resources indicated by the first resource transfer transaction, such as the target account address. Therefore, the resource client can generate the first resource transfer transaction based on the resource amount of the target resources configured in the first configuration area and the target transfer-in address configured in the second configuration area in response to the transaction confirmation operation of the business object for the first interface (for example, there is a confirmation control displayed on the first interface, and the business object can initiate the first resource transfer transaction by touching the confirmation control).

[0093] It can be understood that on the first interface output in response to the selection operation of the first account address on the address display interface, the business object can configure the resource transfer-in address, and the resources transferred at this time can be called target resources, and the amount of the target resources is configured by the business object.

[0094] Similarly, on the second interface output in response to the selection operation of the second account address on the address display interface, the business object can configure the resource transfer-in address, and the resources transferred at this time can be referred to as target resources, and the amount of the target resources is configured by the business object.

[0095] It can be understood that since the first resource transfer transaction is generated in the first interface, the first resource transfer transaction can also include a transaction type associated with the first interface, such as the first transaction type, which can indicate that the first resource transfer transaction is a transaction for transferring the first-level resources in the first account address.

[0096] S102. In response to the resource transfer operation of the business object for the target resources on the first interface, generate a first resource transfer transaction, and send the first resource transfer transaction to the blockchain node through the resource server corresponding to the resource client.

[0097] Among them, it can be understood that in response to the determination operation of the business object on the above-mentioned first interface, a first resource transfer transaction can be generated based on the resource transfer-out address of the business object on the first interface, the resource amount of the target resources configured by the business object, and the resource transfer-in address (target account address), and the first resource transfer transaction is sent to the resource server, and the resource server forwards the first resource transfer transaction to the blockchain node.

[0098] Among them, when the blockchain node executes the first resource transfer transaction, it will obtain the resource amount of the first-level resources. If the resource amount of the first-level resources is less than the resource amount of the target resources, the target resources in the first-level resources will be transferred from the first account address to the target account address. It can be understood that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resources, it means that the transaction cannot be executed. At this time, the blockchain node can generate cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer the business resources in the second account address across levels to the first account address.

[0099] Among them, for the resource client to send the first resource transfer transaction to the blockchain node through the resource server, it can be that the first private key in the resource client is used to sign the first resource transfer transaction to obtain the first signed resource transfer transaction; the first signed resource transfer transaction is sent to the resource server, so that the resource server packs the first signed resource transfer transaction with the data-packing private key to obtain the first packed resource transfer transaction, and the first packed resource transfer transaction is sent to the blockchain node. The first packed resource transfer transaction is used to instruct the blockchain node to determine the first signed resource transfer transaction through the public key corresponding to the data-packing private key. The first signed resource transfer transaction is used to instruct the blockchain node to determine the first resource transfer transaction through the public key corresponding to the first private key, thereby realizing the fast transaction of the first resource transaction. That is, the blockchain node performs transaction signature verification through the public key corresponding to the data-packing private key to obtain the first signed resource transfer transaction, and performs transaction signature verification through the public key corresponding to the first private key to obtain the first resource transfer transaction.

[0100] Among them, it can be understood that as the server in the resource hosting platform, the resource server can have a platform packing key. When the resource server obtains the first signed resource transfer transaction, after verifying the transaction legality of the first signed resource transfer transaction, it can send the first resource transfer transaction according to the resource processing policy associated with the first account address. For example, the first signed resource transfer transaction is packed with data (that is, the first signed resource transfer transaction is signed) to obtain the transaction packing information, and the transaction packing information is written into the first signed resource transfer transaction to obtain the first packed resource transfer transaction, so as to ensure that the packed resource transfer transaction received by the blockchain node comes from the resource server.

[0101] It can be understood that when receiving the resource transfer transaction, the resource server can determine the associated resource processing policy according to the resource transfer address in the resource transfer transaction (such as the first account address, or the second account address, or the third account address), or it can also be determined according to the transaction type in the resource transfer transaction (such as the first transaction type, or the second transaction type, or the third transaction type). For example, the first transaction type is associated with the resource processing policy for the first account address, the second transaction type is associated with the resource processing policy for the second account address, and the third transaction type is associated with the resource processing policy for the third account address.

[0102] It can be understood that when the resource server packs the first signed resource transfer transaction with data, it obtains the resource quota of the first-level resources from the blockchain. When it is determined that the resource quota of the first level is less than the resource quota of the target resources, cross-level transfer information is generated and sent to the resource client.

[0103] Among them, in order to determine the transaction security of the first-level resources, when the resource server obtains the first signed resource transfer transaction, it can obtain the historical transaction times for the first account address (such as the transaction times of the first resource transfer transaction initiated by the resource client on the same day). When the historical transaction times are less than the transaction times threshold, it packages the data of the first signed resource transfer transaction; when the historical transaction times are equal to the transaction times threshold, it does not package the data of the first signed resource transfer transaction and returns a prompt message prohibiting the initiation of the first resource transfer transaction to the resource client.

[0104] Optionally, it can also be that when the resource client displays the first interface and responds to the resource transfer operation of the business object for the target resource on the first interface, it obtains the resource quota of the first-level resources from the blockchain through the resource server. When it determines that the resource quota of the first level is less than the resource quota of the target resource, it generates cross-level transfer information to initiate the second resource transfer transaction; when it determines that the resource quota of the first level is greater than or equal to the resource quota of the target resource, it generates the first resource transfer transaction and sends the first resource transfer transaction to the blockchain node through the resource server corresponding to the resource client to achieve the resource transfer of the first-level resources.

[0105] It can be understood that the cross-level transfer information can be used to instruct the business object to transfer the business resources in the second account address across levels to the first account address, and to indicate the resource difference between the first-level resources and the target resources, that is, the minimum amount required for supplementary resources.

[0106] For example, as Figures 6 - 8 shown, Figures 6 - 8 is a schematic diagram of a process for generating cross-level transfer information provided by an embodiment of the present application; among them, as Figure 6, the resource client in the terminal device 20 can generate a first resource transfer transaction TX1 in response to a resource transfer operation of a service object a1 for a target resource on a first interface, sign the first resource transfer transaction with a first private key in the resource client to obtain a first signed resource transfer transaction TX1', and send (S61) the first signed resource transfer transaction TX1' to the resource server 20b. The resource server packs the first signed resource transfer transaction with a data-packing private key to obtain a first packed resource transfer transaction TX1". The resource server sends (S62) the first packed resource transfer transaction to the blockchain node 20c. The blockchain node determines the first signed resource transfer transaction through the public key corresponding to the data-packing private key and determines the first resource transfer transaction through the public key corresponding to the first private key. At this time, the blockchain node obtains a first account address and a resource quota of the target resource from the first resource transfer transaction, obtains a resource quota of a first-level resource based on the first account address, and detects whether the resource quota of the first-level resource is greater than the resource quota X1 of the target resource. When it is detected that the resource quota of the first-level resource is less than the resource quota X1 of the target resource, a cross-level transfer information can be generated based on the resource difference between the first-level resource and the target resource, and the cross-level transfer information is returned (S63) to the resource server, and the resource server returns (S64) the cross-level transfer information to the resource client.

[0107] Among them, as Figure 7 , the resource client in the terminal device can generate a first resource transfer transaction TX1 in response to a resource transfer operation of a service object for a target resource on a first interface, sign the first resource transfer transaction with a first private key in the resource client to obtain a first signed resource transfer transaction TX1', and send (S71) the first signed resource transfer transaction TX1' to the resource server. The resource server sends (S72) a first resource quota query request (quota query request) for the first-level resource of the first account address to the blockchain node based on the first account address in the first signed resource transfer transaction TX1'. The blockchain node returns (S73) the resource quota of the first-level resource based on the first resource quota query request. The resource server obtains the resource quota X1 of the target resource from the first signed resource transfer transaction TX1' and detects whether the resource quota of the first-level resource is greater than the resource quota X1 of the target resource. When it is detected that the resource quota of the first-level resource is less than the resource quota of the target resource, a cross-level transfer information is generated based on the resource difference between the first-level resource and the target resource, and the cross-level transfer information is returned (S74) to the resource client. Correspondingly, when it is detected that the resource quota of the first-level resource is greater than or equal to the resource quota of the target resource, the first signed resource transfer transaction is packed with a data-packing private key to obtain a first packed resource transfer transaction TX1".

[0108] Among them, as Figure 8 , the resource client in the terminal device can, in response to a resource transfer operation of a service object for a target resource on a first interface, generate a first resource quota query request (quota query request) for the first-level resources of a first account address, and send (S81) the first resource quota query request to a resource server. The resource server sends (S82) the first resource quota query request to a blockchain node. The blockchain node returns (S83) the resource quota of the first-level resources based on the first resource quota query request. The resource server returns (S84) the resource quota of the first-level resources to the resource client. The resource client detects whether the resource quota of the first-level resources is greater than the resource quota X1 of the target resource, and when it detects that the resource quota of the first-level resources is less than the resource quota X1 of the target resource, generates cross-level transfer information based on the resource difference between the first-level resources and the target resource. Correspondingly, when it detects that the resource quota of the first-level resources is greater than or equal to the resource quota of the target resource, generates a first resource transfer transaction TX1, and performs a transaction signature on the first resource transfer transaction with a first private key in the resource client to obtain a first signed resource transfer transaction TX1'.

[0109] S103. Receive the cross-level transfer information, and in response to an address confirmation operation of the service object for a second account address in the cross-level transfer information, display a second interface corresponding to the second account address.

[0110] Among them, it can be understood that the resource client can display a cross-level confirmation interface based on the cross-level transfer information. This cross-level confirmation interface (such as as shown above Figure 2 ) is used to indicate whether the service object transfers the service resources in the second account address to the first account address. For example, a prompt message indicating that the resource quota of the first-level resources in the first account address is insufficient and the resource difference between the first-level resources and the target resource can also be displayed on the cross-level confirmation interface. The service object can display a second interface corresponding to the second account address by touching a confirmation control on the cross-level confirmation interface (i.e., the address confirmation operation for the second account address in the cross-level transfer information). At this time, the resource transfer-in address (the first account address) and the resource transfer-out address (the second account address) are automatically filled in on the second interface, and a configuration area for displaying the resource quota of the supplementary resources corresponding to the target resource (i.e., the transfer-out quota for the second-level resources) is also displayed. Therefore, the resource client can, in response to a transaction confirmation operation of the service object for the second interface (if there is a confirmation control displayed on the second interface, the service object can initiate a second resource transfer transaction by touching the confirmation control), generate a second resource transfer transaction based on the resource quota of the supplementary resources configured in the second configuration area.

[0111] It can be understood that since the second resource transfer transaction is generated in the second interface, the second resource transfer transaction may also include a transaction type associated with the second interface, such as the second transaction type, which may indicate that the second resource transfer transaction is for transferring the second-level resources in the second account address.

[0112] It can be understood that when a business object needs to transfer the first-level resources in the first account address and the second interface is displayed through cross-level transfer information, the business object only needs to fill in the resource amount of the supplementary resources to be transferred on the second interface, and then a second resource transfer transaction for the second account address can be generated. It can be understood that the second-level resources transferred by the second resource transfer transaction at this time are supplementary resources, that is, the supplementary resources refer to the business resources transferred from the second-level resources when the amount is insufficient when transferring business resources from the first-level resources of the first account address. When the second interface is output in response to the selection operation of the second account address on the address display interface, the second-level resources transferred by the second resource transfer transaction generated at this time can also be referred to as target resources.

[0113] S104. In response to the resource transfer operation of the supplementary resources on the second interface by the business object, generate a second resource transfer transaction, and send the second resource transfer transaction to the blockchain node through the resource server.

[0114] Among them, it can be understood that in response to the confirmation operation of the business object on the above-mentioned second interface, a second resource transfer transaction can be generated based on the resource transfer address and resource transfer-in address of the business object on the second interface, and the resource amount of the supplementary resources configured by the business object, and the second resource transfer transaction is sent to the resource server, and the resource server forwards the second resource transfer transaction to the blockchain node.

[0115] It can be understood that the resource client can send the second resource transfer transaction to the resource server, so that when the resource server determines that the first account address is the account address with resource transfer permission associated with the second account address, the second resource transfer transaction is sent to the blockchain node. That is, it is determined whether the first account address is in the address whitelist associated with the second account address.

[0116] Among them, the second-level resources transferred by the second resource transfer transaction are relatively important business resources, so they can go through the transaction approval mechanism. Therefore, the resource client can send the second resource transfer transaction to the resource server, and the resource server can perform transaction approval on the second resource transfer transaction for the second account address by using the resource transfer policy corresponding to the second account address. For example, when the resource server determines that the first account address is the account address associated with the second account address and having the resource transfer permission, it can notify the first approval client corresponding to the first approval object associated with the second account address, and authorize the first approval device of the first approval object to perform transaction approval on the second resource transfer transaction through the second private key in the first approval device, obtaining the first transaction approval information. And when it is determined through the first transaction approval information that the transaction approval result of the second resource transfer transaction is transaction approval passed, it generates the first transaction signature notification information for the second resource transfer transaction. The first approval device is the first hardware device of the first approval object. The first approval client is the resource client of the first approval object.

[0117] At this time, when the resource client receives the first transaction signature notification information, it can authorize the first hardware device of the business object to perform transaction signature on the second resource transfer transaction through the second private key in the first hardware device, obtaining the transaction signature information corresponding to the second resource transfer transaction.

[0118] That is to say, for the resource transfer transaction that transfers the business resources (target resources or supplementary resources for the second-level resources) in the second account address, only after the transaction approval, the resource client will perform transaction signature on the resource transfer transaction. Moreover, both the transaction approval and the transaction signature use the second private key stored in the first hardware device to prevent the loss of the private key and the illegal transfer of resources. And the third resource transfer transaction can adopt a multi-signature algorithm.

[0119] Optionally, when the resource client performs transaction signature on the first resource transfer transaction, it can also use the second private key in the first hardware device of the business object for transaction signature. It can be understood that the transaction approval process is that the first approval object performs transaction signature on the second resource transfer transaction through the second private key in the first approval device, and takes the obtained signature information as the first transaction approval information.

[0120] It is understandable that relevant business personnel can pre-set multiple transaction approval tasks associated with the second account address, and the resource server can send them to the first approval object in multiple transaction approval tasks in turn to approve the second resource transfer transaction. For example, when the first transaction approval information obtained after the first approval object in a transaction approval task approves the transaction reaches a specified threshold, the transaction approval result of the transaction approval task is determined to be transaction approval passed, and the second resource transfer transaction is sent to the first approval object in the next transaction approval task for transaction approval, until the transaction approval results of all transaction approval tasks are transaction approval passed, and the transaction approval result of the second resource transfer transaction is determined to be transaction approval passed. It is understandable that the first transaction approval information is used to indicate that the approval result of the first approval object is approval passed. Optionally, the obtained first transaction approval information can be written into the second resource transfer transaction for chaining, so that the transaction approval process of the second resource transfer transaction can be open, transparent and traceable.

[0121] At this time, the resource client can send the transaction signature information to the resource server. When the resource server determines the second signature resource transfer transaction based on the transaction signature information (i.e., writes the transaction signature information into the second resource transfer transaction), it packages the second signature resource transfer transaction with the data packaging private key to obtain the second packaged resource transfer transaction, and sends the second packaged resource transfer transaction to the blockchain node. At this time, the blockchain node can obtain the second resource transfer transaction based on the second packaged resource transfer transaction. That is, the second packaged resource transfer transaction is used to instruct the blockchain node to determine the second signature resource transfer transaction through the public key corresponding to the data packaging private key. The second signature resource transfer transaction is used to instruct the blockchain node to determine the second resource transfer transaction through the public key corresponding to the transaction signature information.

[0122] Among them, taking the resource client of the business object authorizing the first hardware device to perform transaction signing as an example, the resource server is used to send a challenge value to be verified for the first hardware device of the business object to the resource client (for example, the challenge value to be verified can be sent together when sending the first transaction signing notification information, or the resource client can send a challenge value acquisition request to the resource server when receiving the first transaction signing notification information (similarly, the first approval client can perform transaction approval on the second resource transfer based on the first transaction approval notification information sent by the resource server), and the resource server sends the challenge value to be verified based on the challenge value acquisition request). The resource client uses the second private key in the first hardware device to perform data signing on the challenge value to be verified (for example, the object terminal accesses the first hardware device, and notifies the first hardware device to perform data signing on the challenge value to be verified through the hardware authentication client in the resource client), and obtains the challenge value signature information; the challenge value signature information is returned to the resource server, so that when the resource server performs data signature verification on the challenge value signature information through the public key corresponding to the second private key in the first hardware device and obtains the challenge value to be matched, it performs data comparison on the challenge value to be matched and the challenge value to be verified to obtain a data comparison result; when the data comparison result indicates that the challenge value to be matched and the challenge value to be verified are the same, it is determined that the object authentication of the business object is successful; the second resource transfer transaction is signed through the second private key in the first hardware device to obtain the transaction signature information. It can be understood that the process of the first approval client performing transaction approval through the first approval device is the same as the process of the resource approval client performing transaction signing through the first hardware device.

[0123] Among them, the blockchain node can generate a resource update information when transferring the supplementary resource in the second-level resource from the second account address to the first account address and updating the first-level resource based on the supplementary resource; the supplementary resource is determined based on the resource difference between the first-level resource and the target resource. The resource update information is used to indicate the resource quota of the updated first-level resource. It can be understood that the supplementary resource can be equal to the resource difference between the first-level resource and the target resource, or can be greater than the resource difference between the first-level resource and the target resource.

[0124] It can be understood that the blockchain node transfers the supplementary resource in the second-level resource from the second account address to the first account address when determining that the resource quota of the second-level resource is greater than or equal to the resource quota of the supplementary resource. Correspondingly, when determining that the resource quota of the second-level resource is less than the resource quota of the supplementary resource, business resources can be further transferred from the third account address to the second account address so that the second resource transfer transaction can be successfully executed.

[0125] It can be understood that the blockchain node is used to compare the resource amount of the second-level resource and the resource amount of the supplementary resource when obtaining the second resource transfer transaction, and generate reference cross-level transfer information when detecting that the resource amount of the second-level resource is less than the resource amount of the supplementary resource; the reference cross-level transfer information is used to instruct the business object to transfer the business resources in the third account address across levels to the second account address.

[0126] Therefore, the resource client can receive the reference cross-level transfer information, and in response to the address confirmation operation of the business object for the third account address in the reference cross-level transfer information, display the third interface corresponding to the third account address (for the specific description of the third interface, refer to the relevant description of the second interface above. The third interface automatically fills in the second account address as the resource transfer-in address and the third account address as the resource transfer-out address, and the business object configures the resource amount of the reference supplementary resource); in response to the resource transfer operation of the business object for the reference supplementary resource (for the specific description of the reference supplementary resource, refer to the relevant description of the supplementary resource above) on the third interface, generate a third resource transfer transaction, and send the third resource transfer transaction to the blockchain node through the resource server, so that when the blockchain node transfers the reference supplementary resource in the third-level resource from the third account address to the second account address and updates the second-level resource based on the reference supplementary resource, generate reference resource update information; the reference supplementary resource is determined based on the resource difference between the second-level resource and the supplementary resource; receive the reference resource update information, and when it is determined based on the reference resource update information that the resource amount of the updated second-level resource reaches the resource amount of the supplementary resource, resend the second resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the supplementary resource (it can be understood that at this time, it is the supplementary resource in the updated second-level resource) from the second account address to the first account address.

[0127] That is to say, the resource client can resend the second resource transfer transaction when receiving the reference resource update information. It can be understood that when the resource server receives the resent second resource transfer transaction, if it has obtained the second signed resource transfer transaction (or the second packaged resource transfer transaction) before, it directly packs the data of the previously obtained second signed resource transfer transaction (or directly resends the previously obtained second packaged resource transfer transaction to the blockchain node).

[0128] It can be understood that for the specific description of the reference cross-level transfer information, refer to the relevant description of the cross-level transfer information above. For example, it can also be that when the resource server packs the data of the second signed resource transfer transaction, it obtains the resource amount of the second-level resource from the blockchain, and generates reference cross-level transfer information for the resource client when determining that the resource amount of the second level is less than the resource amount of the target resource.

[0129] Optionally, it can also be that when the resource client displays the second interface and responds to the resource transfer operation of the service object for the supplementary resources on the second interface, it obtains the resource quota of the second-level resources from the blockchain through the resource server. When it is determined that the resource quota of the second level is less than the resource quota of the supplementary resources, a reference cross-level transfer information is generated to initiate a third resource transfer transaction; when it is determined that the resource quota of the second level is greater than or equal to the resource quota of the supplementary resources, a second resource transfer transaction is generated, and the second resource transfer transaction is sent to the blockchain node through the resource server corresponding to the resource client to achieve the resource transfer of the second-level resources.

[0130] It can be understood that the reference cross-level transfer information can be used to instruct the service object to transfer the service resources in the third account address across levels to the second account address, and to indicate the resource difference between the second-level resources and the supplementary resources, that is, the minimum quota required for the reference supplementary resources.

[0131] It can be understood that since the third resource transfer transaction is generated in the third interface, the third resource transfer transaction can also include a transaction type associated with the third interface, such as a third transaction type, which can indicate that the third resource transfer transaction is a transaction for transferring the third-level resources in the third account address.

[0132] It can be understood that when the service object needs to transfer the third-level resources in the third account address and the third interface is displayed through the reference cross-level transfer information, at this time, the service object only needs to fill in the resource quota of the supplementary resources to be transferred on the third interface, and then a third resource transfer transaction for the third account address can be generated. It can be understood that the third-level resources transferred by the third resource transfer transaction at this time are reference supplementary resources, that is, the reference supplementary resources refer to the service resources transferred from the third-level resources when the quota is insufficient when transferring service resources from the second-level resources of the second account address. When the third interface is output in response to the selection operation of the third account address on the address display interface, the third-level resources transferred by the third resource transfer transaction generated at this time can also be referred to as target resources.

[0133] It can be understood that the resource client can send the third resource transfer transaction to the resource server so that when the resource server determines that the second account address is the account address with resource transfer permission associated with the third account address, the third resource transfer transaction is sent to the blockchain node. That is to say, it is determined whether the second account address is in the address whitelist associated with the third account address.

[0134] Among them, sending the third resource transfer transaction to the blockchain node by the resource server may be as follows: The resource client sends the third resource transfer transaction to the resource server. When the resource server determines that the second account address is the account address associated with the third account address and having the resource transfer permission, it notifies the second approval client of the second approval object associated with the third account address. When it is determined that the local trusted execution environment of the second approval device of the second approval object belongs to a secure execution environment, the third resource transfer transaction is approved for the transaction by the third private key determined by the local trusted execution environment of the second approval device, and the first transaction signature shard for the third resource transfer transaction is obtained. And when it is determined that the number of shards of the first transaction signature shard reaches the shard number threshold, it is determined that the transaction approval result of the third resource transfer transaction is transaction approval passed, and the second transaction signature notification information for the third resource transfer transaction is generated.

[0135] At this time, when the resource client receives the second transaction signature notification information and determines that the local trusted execution environment of the second hardware device of the business object belongs to a secure execution environment, the third resource transfer transaction is signed for the transaction by the third private key determined by the local trusted execution environment of the second hardware device, and the second transaction signature shard for the third resource transfer transaction is obtained.

[0136] Therefore, the resource client can send the second transaction signature shard to the resource server. When the resource server determines the third signed resource transfer transaction based on the first transaction signature shard and the second transaction signature shard, the third signed resource transfer transaction is data-packaged by the data-packaging private key to obtain the third packaged resource transfer transaction, and the third packaged resource transfer transaction is sent to the blockchain node. The blockchain node can determine the third resource transfer transaction through the third packaged resource transfer transaction, that is, the third packaged resource transfer transaction is used to instruct the blockchain node to determine the third signed resource transfer transaction through the public key corresponding to the data-packaging private key; the third signed resource transfer transaction is used to instruct the blockchain node to determine the third resource transfer transaction through the public keys corresponding to the first transaction signature shard and the second transaction signature shard.

[0137] Among them, the second approval client is the resource client of the second approval object. The second approval device is the second hardware device of the second approval object.

[0138] It can be understood that, similar to the second resource transfer transaction, for a resource transfer transaction that transfers business resources in the third account address (target resources or reference supplementary resources for third-level resources), it can be that after the transaction is approved, the resource client will perform a transaction signature on the resource transfer transaction. For example, both the transaction approval and the transaction signature can be executed by the local trusted execution environment in the second hardware device to prevent the loss of the private key and the illegal transfer of resources. And the third resource transfer transaction can use a threshold signature algorithm.

[0139] Optionally, when the resource client performs a transaction signature on the first resource transfer transaction, it can also be executed by the local trusted execution environment in the second hardware device of the business object. It can be understood that the transaction approval process is that the second approval object performs a transaction signature on the third resource transfer transaction through the local trusted execution environment in the second approval device, and uses the obtained signature information as the first transaction signature shard.

[0140] It can be understood that relevant business personnel can pre-set multiple second approval objects associated with the third account address, and these multiple second approval objects perform transaction approvals on the third resource transfer transaction. It can be understood that since the address level of the third account address is higher than that of the second account address, the approval level of the second approval object is higher than that of the first approval object. For example, the third resource transfer transaction can be distributed to multiple second approval objects, and the multiple second approval objects perform transaction approvals on the third resource transfer transaction. When the number of shards of the obtained first transaction signature shard reaches the shard number threshold, it is determined that the transaction approval is passed.

[0141] Among them, the resource server can perform an aggregated signature process on the first transaction signature shard and the second transaction signature shard to obtain aggregated signature information, write the aggregated signature information into the third resource transfer transaction to obtain the third signed resource transfer transaction. Subsequently, the blockchain node can perform signature verification on the aggregated signature information through the public keys corresponding to the first transaction signature shard and the second transaction signature shard (i.e., the aggregated signature information) to obtain the third resource transfer transaction. That is to say, the third private key can be a private key shard obtained by sharding a complete private key, and is determined by the local trusted execution environment in each second hardware device respectively.

[0142] Among them, it can be understood that the first hardware device and the second hardware device of the business object can be the same device or different devices. Optionally, the second hardware device can be an offline device for cold storage of third-level resources or the terminal device where the resource client is located. Among them, the first hardware device can be a hardware UKEY. A hardware UKEY is an encryption device, also known as a USB Key. It is a secure hardware encryption device that can store important information such as encryption keys and digital certificates. Among them, a transaction signature key (second private key) for signing transactions can be stored in the hardware UKEY. After authentication through the digital certificate stored in the hardware UKEY, the resource transfer transaction to be signed can be signed with the transaction signature key in the hardware UKEY to complete the approval or signature of the resource transfer transaction. It can be understood that when the business object needs to perform transaction signature through the resource client, the resource client will prompt the business object to insert the hardware UKEY for verification of the hardware UKEY. For example, the resource server will generate a challenge value and let the hardware UKEY sign it using the second private key it holds, so that the signature result of the challenge value can be sent to the resource server. When the resource server queries the public key corresponding to the second private key of the business object, it performs signature verification through the queried public key. When the signature verification passes, it can determine that the business object is a legitimate user holding the hardware UKEY, and then allow the second private key in the hardware UKEY to sign the second resource transfer transaction.

[0143] Taking the example that the resource client of the business object performs transaction signing through the local trusted execution environment in the second hardware device, the resource client can send the second transaction signature notification information to the second hardware device (such as by scanning a code or Bluetooth transmission), so that the second hardware device performs transaction signing on the third resource transfer based on the second transaction signature notification information (similarly, the second approval device can perform transaction approval on the third resource transfer based on the second transaction approval notification information sent by the resource server), and generate a remote authentication request for the local trusted execution environment. When the resource client obtains the remote authentication request generated by the local trusted execution environment of the second hardware device (such as by scanning a code or Bluetooth transmission), it sends the remote authentication request to the resource server (it can also be directly sent by the second hardware device. It can be understood that the second hardware device can be temporarily online here); the remote authentication request is used to represent the remote public key and remote authentication report of the identity information of the local trusted execution environment of the second hardware device; the remote authentication request is used to instruct the resource server to perform remote authentication on the local trusted execution environment of the second hardware device based on the remote public key and remote authentication report, and when the remote authentication is successful, generate a remote authentication success report associated with the local trusted execution environment of the second hardware device; when receiving the remote authentication success report, return the remote authentication success report to the second hardware device (such as by scanning a code or Bluetooth transmission, or it can also be directly returned by the resource server to the second hardware device). At this time, the second hardware device can determine that the local trusted execution environment of the second hardware device belongs to a secure execution environment based on the remote authentication success report, and obtain the third private key determined by the local trusted execution environment of the second hardware device based on the remote authentication success report. At this time, the resource client can perform transaction signing on the third resource transfer transaction through the third private key determined by the local trusted execution environment of the second hardware device to obtain the second transaction signature shard for the third resource transfer transaction.

[0144] For example, that is, the local trusted execution environment of the second hardware device stores the remote private key corresponding to the remote public key. The remote authentication success report includes the encrypted private key shard encrypted by the resource server with the remote public key for the private key shard. The local trusted execution environment of the second hardware device can decrypt the encrypted private key shard with the remote private key to obtain the decrypted private key shard, and use this private key shard as the third private key to perform transaction signing on the third resource transfer transaction. The second hardware device can return the second transaction signature shard to the resource client (such as by scanning a code).

[0145] Among them, the local trusted execution environment (TEE) is a hardware-based secure computing solution. A secure area is constructed in the processor of the second hardware device through software and hardware methods to ensure the confidentiality and integrity of the programs and data loaded therein. The TEE divides the system's hardware resources and software resources into two execution environments - the trusted part and the untrusted part (ordinary part). These two environments are isolated, and the untrusted part cannot access the storage and memory of the trusted part. The local trusted execution environment (TEE) stores the remote public key and remote private key for remote authentication. The private key determined by the remote public key and remote private key is the third private key used to sign the third resource transfer transaction, and the third private key can be a shard of the private key.

[0146] S105. Receive the resource update information. When it is determined based on the resource update information that the resource quota of the updated first-level resource reaches the resource quota of the target resource, send the first resource transfer transaction to the blockchain node through the resource server.

[0147] It can be understood that at this time, after the blockchain node generates and executes the second resource transfer transaction, it returns the resource update information based on the updated first-level resource. After receiving the resource update information, the resource client, in response to the transaction resending operation of the business object for the resource update information, resends the first resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction. It can be understood that when the resource server receives the resent first resource transfer transaction, if it has obtained the first signed resource transfer transaction (or the first packaged resource transfer transaction) previously, it directly packs the data of the previously obtained first signed resource transfer transaction (or directly resends the previously obtained first packaged resource transfer transaction to the blockchain node).

[0148] For example, as Figure 9 shown, Figure 9 is a schematic diagram of a resource processing framework provided by an embodiment of the present application; among them, the technical solution of the present application proposes that the business resources of the business object can be stored by account addresses at multiple levels. For example, the first account address stores the first-level resources for high-frequency resource transfer transactions. The resource processing strategy associated with the first account address can be that the first private key in the resource client signs the first resource transfer transaction to obtain the first signed resource transfer transaction, and the resource server packs the data of the first signed resource transfer transaction with the data-packing private key to obtain the first packaged resource transfer transaction, and sends the first packaged resource transfer transaction to the blockchain node. It can be understood that the resource server can also not pack the data of the first signed resource transfer transaction and send the first signed resource transfer transaction to the blockchain node.

[0149] Among them, the second account address stores second-level resources for medium-frequency resource transfer transactions. The resource processing strategy associated with the second account address can be that the resource client sends a second resource transfer transaction to the resource server. The resource server notifies a first approval object to authorize a first approval device (such as a hardware UKEY) of the first approval object to conduct transaction approval. After the transaction approval is passed, it notifies the business object to authorize a first hardware device of the business object to conduct transaction signing, obtaining a second signed resource transfer transaction (i.e., multi-signature). The resource server uses a data-packing private key to pack the second signed resource transfer transaction, obtaining a second packed resource transfer transaction, and sends the second packed resource transfer transaction to the blockchain node. It can be understood that the resource server can also not pack the second signed resource transfer transaction and send the second signed resource transfer transaction to the blockchain node.

[0150] Among them, the third account address stores third-level resources for low-frequency resource transfer transactions. The resource processing strategy associated with the third account address can be that the resource client sends a third resource transfer transaction to the resource server. The resource server notifies a second approval object to authorize a local trusted execution environment (TEE, Trusted Execution Environment) in a second approval device of the second approval object to conduct transaction approval, obtaining a first transaction signature shard. After the transaction approval is passed, it notifies the business object to authorize a local trusted execution environment in a second hardware device of the business object to conduct transaction signing, obtaining a second transaction signature shard, to determine a third signed resource transfer transaction (threshold signature) based on the first transaction signature shard and the second transaction signature shard. The resource server uses a data-packing private key to pack the third signed resource transfer transaction, obtaining a third packed resource transfer transaction, and sends the third packed resource transfer transaction to the blockchain node. It can be understood that the resource server can also not pack the third signed resource transfer transaction and send the third signed resource transfer transaction to the blockchain node.

[0151] For another example, as Figure 10 shown, Figure 10 is a schematic diagram of a resource processing scenario provided by an embodiment of the present application. Among them, part of the business resources of the business object are stored as first-level resources in the first account address, part of the business resources are stored as second-level resources in the second account address, and part of the business resources are stored as third-level resources in the third account address. Resource transfer transactions for target resources in the first account address, resource transfer transactions for target resources in the second account address, and resource transfer transactions for target resources in the third account address can be initiated respectively.

[0152] At this time, when initiating a resource transfer transaction for the target resource of the first account address, if the resource quota of the first-level resources in the first account address is insufficient, a second resource transfer transaction for the supplementary resources of the second account address can be initiated to transfer the supplementary resources in the second account address to the first account address. It can be understood that when initiating the second resource transfer transaction, it is necessary to ensure that the resource transfer-in address indicated by the second resource transfer transaction (such as the first account address) is the whitelist address corresponding to the second account address (that is, the account address with resource transfer permission). In addition, when officially initiating the second resource transfer transaction, a test resource transfer transaction can be initiated first, such as initiating a small-scale second resource transfer transaction. After determining that the account address is correct, the official second resource transfer transaction can be initiated.

[0153] Correspondingly, when initiating a resource transfer transaction for the target resource (or supplementary resources) of the second account address, if the resource quota of the second-level resources in the second account address is insufficient, a third resource transfer transaction for the reference supplementary resources of the third account address can be initiated to transfer the supplementary resources in the third account address to the second account address. It can be understood that when initiating the third resource transfer transaction, it is necessary that the resource transfer-in address indicated by the third resource transfer transaction (such as the second account address) is the whitelist address corresponding to the third account address (that is, the account address with resource transfer permission). In addition, when officially initiating the third resource transfer transaction, a test resource transfer transaction can be initiated first, such as initiating a small-scale third resource transfer transaction. After determining that the account address is correct, the official third resource transfer transaction can be initiated.

[0154] It can be understood that when there is a fourth account address for the business object's account address and the address level of the fourth account address is higher than that of the third account address, if the resource quota of the third-level resources in the third account address is insufficient, a resource transfer transaction for the business resources of the fourth account address can be initiated to transfer the supplementary resources in the fourth account address to the third account address.

[0155] It can be understood that when the business object is an enterprise, the security management of enterprise-level business resources is realized. The resource server can serve as a hosting platform for enterprise-level business resources, with specific scenario requirements such as multi-person collaboration, approval workflow, and retrievability, and provides different levels of account addresses according to different scenario requirements. For example, the resource client can include a first account address (hot account address layer), a second account address (warm account address layer), and a third account address (cold account address layer). The first account address is for resource transfer scenarios with high real-time requirements and high frequency, the second account address is for resource transfer scenarios with medium real-time requirements and medium frequency, and the third account address is for resource transfer scenarios with low real-time requirements and low frequency. Through the three different levels of account addresses, the resource management of the enterprise in different scenarios can be adapted, the flexibility, success rate, and adaptability of resource transfer can be improved, and enterprise resources can circulate among the three account addresses. For example, enterprise resources can be transferred from the third account address to the second account address or from the second account address to the first account address, improving the flexibility and security of resource management, and realizing the security management of resources and the trusteeship of enterprise assets through hierarchical management and circulation.

[0156] In the embodiments of the present application, partial business resources of a business object can be stored by multiple account addresses respectively. For example, the first-level resources are stored by the first account address, and the second-level resources are stored by the second account address, and the address level of the first account address is lower than that of the second account address. In this way, when the resource client generates a first resource transfer transaction through a resource transfer operation of the target resource on the first interface corresponding to the first account address, the first resource transfer transaction can be sent to the blockchain node through the resource server. When the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resource, it can generate cross-level transfer information to instruct the business object to transfer a certain amount of business resources from the second account address to the first account address. At this time, in response to the address confirmation operation of the business object for the second account address in the cross-level transfer information, the second interface corresponding to the second account address can be displayed. In this way, when the resource client generates a second resource transfer transaction through a resource transfer operation of supplementing resources on the second interface corresponding to the second account address, the second resource transfer transaction can be sent to the blockchain node through the resource server. The blockchain node can transfer the supplementary resources in the second-level resources from the second account address to the first account address, and generate resource update information when updating the first-level resources based on the supplementary resources, that is, supplement the first-level resources in the first account address with the second-level resources in the second account address. When the resource client determines that the resource amount of the updated first-level resources reaches the resource amount of the target resource (that is, the first resource transfer transaction can be executed through the updated first-level resources), the first resource transfer transaction can be sent to the blockchain node through the resource server. The blockchain node can transfer the target resource from the first account address to the target account address indicated by the first resource transfer transaction to achieve the resource transfer of the business object. Therefore, by storing business resources in multiple levels, when the business resources at the lower level are insufficient, a certain amount of business resources can be transferred from the business resources at the higher level to the lower level, so that the resource transfer transaction at the lower level can be successfully executed, thereby improving the flexibility and success rate of resource transfer. At the same time, by storing business resources through multiple levels of account addresses, it can be ensured that even if the first-level resources are illegally transferred, all the business resources of the business object will not be lost, ensuring the resource security of the business object.

[0157] Further, please refer to Figure 11 , Figure 11 which is a schematic flowchart of a resource processing method provided by an embodiment of the present application. As Figure 11 shown, the method can be executed by the computer device mentioned above. The computer device can be a resource server. For example, the resource server can be the above Figure 1Any server in the server cluster shown, such as server 4000c. The method may specifically include the following steps S201 - step S205:

[0158] S201. When receiving a first resource transfer transaction sent by a resource client, send the first resource transfer transaction to a blockchain node.

[0159] Among them, the blockchain node may obtain the resource quota of the first - level resources based on the first account address in the first resource transfer transaction, and generate cross - level transfer information when detecting that the resource quota of the first - level resources is less than the resource quota of the target resources indicated by the first resource transfer transaction. The cross - level transfer information is used to instruct a business object to transfer business resources in a second account address across levels to the first account address.

[0160] Among them, the first resource transfer transaction is generated by the resource client in response to a resource transfer operation of a target resource on a first interface of a first account address; the first interface is an address display interface of the resource client, which displays the first account address and the second account address, and is output when responding to a selection operation of the business object on the first account address.

[0161] Among them, the resource client stores a first private key, and the first private key in the resource client is used to perform a transaction signature on the first resource transfer transaction to obtain a first signed resource transfer transaction. Therefore, the resource client sends the first resource transfer transaction in the form of the first signed resource transfer transaction. At this time, when the resource server receives the first signed resource transfer transaction corresponding to the first resource transfer transaction sent by the resource client, it can perform data packaging on the first signed resource transfer transaction through a data - packaging private key to obtain a first packaged resource transfer transaction; and send the first packaged resource transfer transaction to the blockchain node. Or, the resource server may obtain the historical transaction times for the first account address (such as the transaction times of the first resource transfer transaction initiated by the resource client on the same day), and perform data packaging on the first signed resource transfer transaction when the historical transaction times are less than the transaction times threshold; when the historical transaction times are equal to the transaction times threshold, do not perform data packaging on the first signed resource transfer transaction, and return a prompt message prohibiting the initiation of the first resource transfer transaction to the resource client. Optionally, the resource server may also directly send the first packaged resource transfer transaction without performing data packaging.

[0162] Optionally, it may also be that the resource server queries the resource quota of the first - level resources from the blockchain node when receiving the first signed resource transfer transaction, and generates and returns cross - level transfer information to the resource client when detecting that the resource quota of the first - level resources is less than the resource quota of the target resources indicated by the first resource transfer transaction.

[0163] Optionally, it can also be that the resource client queries the resource quota of the first-level resources from the blockchain node through the resource server, and when it detects that the resource quota of the first-level resources is less than the resource quota of the target resources indicated by the first resource transfer transaction, it generates cross-level transfer information.

[0164] S202. When receiving the cross-level transfer information, send the cross-level transfer information to the resource client.

[0165] Among them, when the resource client responds to the address confirmation operation of the business object for the second account address in the cross-level transfer information, it displays the second interface corresponding to the second account address, and in response to the resource transfer operation of the supplementary resources on the second interface by the business object, it generates a second resource transfer transaction.

[0166] S203. When receiving the second resource transfer transaction, send the second resource transfer transaction to the blockchain node.

[0167] Among them, when the resource server receives the second resource transfer transaction sent by the resource client, it can obtain the first resource transfer account address associated with the second account address; the first resource transfer account address includes N account addresses with resource transfer permissions associated with the second account address; N is a positive integer; among the N account addresses, search for the account address that matches the first account address, and when the account address that matches the first account address is found, determine the first account address as the account address with resource transfer permissions associated with the second account address, and notify the first approval client corresponding to the first approval object associated with the second account address to authorize the first approval device of the first approval object to perform transaction approval on the second resource transfer transaction through the second private key in the first approval device, and obtain the first transaction approval information.

[0168] At this time, when the resource server determines that the transaction approval result of the second resource transfer transaction is transaction approval passed through the first transaction approval information, it generates a first transaction signature notification information for the second resource transfer transaction and sends the first transaction signature notification information to the resource client. The resource client authorizes the first hardware device of the business object to perform transaction signature on the second resource transfer transaction through the second private key in the first hardware device to obtain the transaction signature information corresponding to the second resource transfer transaction. Among them, the process of performing transaction signature through the first hardware device can refer to the relevant description of the above embodiment and will not be elaborated here.

[0169] It can be understood that when the resource server receives the transaction signature information, it determines the second-signature resource transfer transaction based on the transaction signature information, and data-packs the second-signature resource transfer transaction with the data-packing private key to obtain the second data-packed resource transfer transaction, and sends the second data-packed resource transfer transaction to the blockchain node. Among them, the second data-packed resource transfer transaction is used to instruct the blockchain node to determine the second-signature resource transfer transaction through the public key corresponding to the data-packing private key; the second-signature resource transfer transaction is used to instruct the blockchain node to determine the second resource transfer transaction through the public key corresponding to the transaction signature information.

[0170] Among them, the first resource transfer account address associated with the second account address can be stored on the blockchain. Therefore, the resource server can generate an account address query request for the second account address, send the account address query request to the blockchain node, so that the blockchain node queries the first resource transfer account address associated with the second account address on the blockchain, and the resource server can receive the first resource transfer account address associated with the second account address returned by the blockchain node. That is to say, the business resources in the second account address can only be transferred to the first resource transfer account address associated with the second account address.

[0171] It can be understood that when a business object uploads the first resource transfer account address associated with the second account address to the blockchain, it also needs to approve the account address to be uploaded. For example, the business object initiates a transfer address upload transaction for the second account address through a resource client. The transfer address upload transaction includes the first account address to be uploaded. When the resource server receives the transfer address upload transaction, it notifies the first approval client, authorizing the first approval device to approve the transfer address upload transaction through the second private key in the first approval device, obtaining the upload transaction approval information. When it is determined through the upload transaction approval information that the transaction approval result of the transfer address upload transaction is transaction approval passed, a upload transaction signature notification information for the transfer address upload transaction is generated, and the upload transaction signature notification information is sent to the resource client. The resource client can authorize the first hardware device to sign the transfer address upload transaction through the second private key in the first hardware device, obtaining the upload transaction signature information corresponding to the transfer address upload transaction. When the resource server receives the upload transaction signature information, it determines the signature address transfer upload transaction based on the upload transaction signature information, and packs the signature address transfer upload transaction through the data packaging private key, obtaining the packed address transfer upload transaction, and sends the packed address transfer upload transaction to the blockchain node. The blockchain node can add the first account address to the first resource transfer account address associated with the second account address based on the transfer address upload transaction when obtaining the transfer address upload transaction through the packed address transfer upload transaction, that is, upload the first account address. At this time, the first account address can be used as the account address with resource transfer permission associated with the second account address.

[0172] Among them, when the blockchain node obtains the second resource transfer transaction, it can transfer the supplementary resources in the second-level resources from the second account address to the first account address, and update the first-level resources based on the supplementary resources, generating resource update information; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources.

[0173] For example, as Figure 12 shown, Figure 12It is a schematic diagram of a resource transfer process provided by an embodiment of the present application. Among them, business object a1 sends (S31) a second resource transfer transaction to the resource server through the resource client, and the resource server conducts transaction approval on the second resource transfer transaction based on the resource processing policy corresponding to the second account address. If the first approval objects corresponding to the second account address include approval objects b11 - b13, approval objects b11 - b12 are the first approval objects in transaction approval task 1, and approval object b13 is the first approval object in transaction approval task 2. These two transaction approval tasks have an approval order. When the transaction approval result of transaction approval task 1 is transaction approval passed, it notifies transaction approval task 2 to conduct transaction approval. Therefore, resource server 20b can generate the first transaction approval notification information for the second resource transfer transaction and send (S32) the first transaction approval notification information to approval objects b11 and b12 associated with transaction approval task 1. At this time, the transaction approval interface in the first approval clients corresponding to approval objects b11 and b12 displays the second resource transfer transaction to be approved, and approval controls (such as "agree" control, "reject" control) for the second resource transfer transaction to be approved are displayed on the transaction approval interface. Approval objects b11 and b12 touch the "agree" control in the approval control to implement the operation of agreeing to the transaction approval for the second resource transfer transaction. At this time, the first approval client corresponding to approval object b11 conducts transaction approval on the second resource transfer transaction through the first approval device of approval object b11, obtains the transaction approval information 1 of approval object b11 for the second resource transfer transaction, and returns (S33) it to the resource server; similarly, the first approval client corresponding to approval object b12 conducts transaction approval on the second resource transfer transaction through the first approval device of approval object b12, obtains the transaction approval information 2 of approval object b12 for the second resource transfer transaction, and returns (S34) it to the resource server; when the resource server determines that the transaction approval result of transaction approval task 1 is transaction approval passed through transaction approval information 1 and transaction approval information 2, it sends (S35) the first transaction approval notification information to approval object b13 associated with transaction approval task 2. At this time, the transaction approval interface in the first approval client corresponding to approval object b13 displays the second resource transfer transaction to be approved, and approval controls for the second resource transfer transaction are displayed on the transaction approval interface. Approval object b13 touches the approval control to implement the operation of agreeing to the transaction approval for the second resource transfer transaction. At this time, the first approval client corresponding to approval object b13 conducts transaction approval on the second resource transfer transaction through the first approval device of approval object b13, obtains the transaction approval information 3 of approval object b13 for the second resource transfer transaction, and returns (S36) it to the resource server.It can be understood that when the resource server determines that the transaction approval result of the transaction approval task 2 is transaction approval passed through the transaction approval information 3, that is, the transaction approval results of the transaction approval tasks 1-2 are all transaction approval passed, it determines that the transaction approval result of the second resource transfer transaction is transaction approval passed, and can notify the business object to perform a transaction signature on the second resource transfer transaction through the second private key in the first hardware device of the business object to obtain transaction signature information. Subsequently, when the resource server obtains the second packaged resource transfer transaction based on the transaction signature information, it can send (S37) it to the blockchain node 20c, and the blockchain node calls the smart contract to determine the second resource transfer transaction corresponding to the second packaged resource transfer transaction, that is, verify (S38) whether the signature information of multiple parties (such as the first approval object, the business object, and the resource server) in the second packaged resource transfer transaction is correct, and execute the second resource transfer transaction.

[0174] Optionally, the account address in the resource client further includes a third account address; the third account address is used to store the third-level resources of the business object; the address level of the second account address is lower than the address level of the third account address. When the blockchain node obtains the second resource transfer transaction, it will compare the resource amount of the second-level resources with the resource amount of the supplementary resources, and when it detects that the resource amount of the second-level resources is less than the resource amount of the supplementary resources, it generates reference cross-level transfer information. The reference cross-level transfer information is used to instruct the business object to transfer the business resources in the third account address across levels to the second account address.

[0175] Among them, when the resource server receives the reference cross-level transfer information, it returns the reference cross-level transfer information to the resource client. The resource client can display the third interface corresponding to the third account address in response to the address confirmation operation of the business object for the third account address in the reference cross-level transfer information, and generate a third resource transfer transaction in response to the resource transfer operation of the reference supplementary resources on the third interface. That is to say, when the second resource transfer transaction cannot be executed and the resource amount of the second-level resources is insufficient, it can further instruct the business object to initiate a third resource transfer transaction.

[0176] Therefore, when the resource server receives the third resource transfer transaction, it sends the third resource transfer transaction to the blockchain node. When the blockchain node transfers the reference supplementary resources in the third-level resources from the third account address to the second account address and updates the second-level resources based on the reference supplementary resources, it generates reference resource update information; the reference supplementary resources are determined based on the resource difference between the second-level resources and the supplementary resources. The reference supplementary resources are configured by the business object and can be equal to or greater than the resource difference between the second-level resources and the supplementary resources.

[0177] At this time, the resource server can receive the reference resource update information and return the reference resource update information to the resource client. When the resource client determines that the resource quota of the updated second-level resource reaches the resource quota of the supplementary resource based on the reference resource update information, it resends the second resource transfer transaction. When the resource server receives the second resource transfer transaction, it sends the second resource transfer transaction to the blockchain node. The blockchain node transfers the supplementary resource in the second-level resource (i.e., the updated second-level resource) from the second account address to the first account address.

[0178] Among them, when the resource server receives the third resource transfer transaction, it can obtain the second resource transfer account address associated with the third account address; the second resource transfer account address includes M account addresses with resource transfer permissions associated with the third account address; M is a positive integer; among the M account addresses, search for the account address that matches the second account address, and when the account address that matches the second account address is found, notify the second approval client corresponding to the second approval object associated with the third account address. When it is determined that the local trusted execution environment of the second approval device of the second approval object belongs to a secure execution environment, the third resource transfer transaction is transaction-approved through the third private key determined by the local trusted execution environment of the second approval device to obtain the first transaction signature shard for the third resource transfer transaction.

[0179] Among them, the specific description of the second resource transfer account address can refer to the relevant description of the first resource transfer account address. Among them, the specific method of transaction signature / approval through the local trusted execution environment can refer to the relevant description of the above embodiments and will not be elaborated here.

[0180] At this time, when the resource server determines that the number of shards of the first transaction signature shard reaches the shard number threshold, it generates the second transaction signature notification information for the third resource transfer transaction and sends the second transaction signature notification information to the resource client. When the resource client determines that the local trusted execution environment of the second hardware device of the business object belongs to a secure execution environment, the third resource transfer transaction is transaction-signed through the third private key determined by the local trusted execution environment of the second hardware device to obtain the second transaction signature shard for the third resource transfer transaction.

[0181] Among them, when the resource server receives the second transaction signature shard and determines the third signature resource transfer transaction based on the first transaction signature shard and the second transaction signature shard, it packs the third signature resource transfer transaction through the data-packing private key to obtain the third packed resource transfer transaction, and sends the third packed resource transfer transaction to the blockchain node. It can be understood that the third packed resource transfer transaction is used to instruct the blockchain node to determine the third signature resource transfer transaction through the public key corresponding to the data-packing private key; the third signature resource transfer transaction is used to instruct the blockchain node to determine the third resource transfer transaction through the public keys corresponding to the first transaction signature shard and the second transaction signature shard.

[0182] For example, as Figure 13 shown, Figure 13It is a schematic diagram of a resource transfer process provided by an embodiment of the present application; among them, the service object a1 sends (S41) a third resource transfer transaction to the resource server through the resource client, and the resource server conducts transaction approval on the third resource transfer transaction based on the resource processing policy corresponding to the third account address. If the second approval objects corresponding to the third account address include approval objects c11 - c13, the resource server 20b can generate second transaction approval notification information for the third resource transfer transaction and send (S42) the second transaction approval notification information to the approval objects c11 - c13 respectively. At this time, the transaction approval interfaces in the second approval clients corresponding to the approval objects c11 - c13 display the third resource transfer transaction to be approved, and approval controls (such as "approve" control, "reject" control) for the third resource transfer transaction to be approved are displayed on the transaction approval interfaces. The approval objects c11 - c13 touch the "approve" control in the approval controls to implement the operation of approving the third resource transfer transaction. At this time, the second approval client corresponding to the approval object c11 conducts transaction approval on the third resource transfer transaction through the local trusted execution environment (TEE) in the second approval device of the approval object c11, obtains the transaction signature shard 1 of the approval object c11 for the third resource transfer transaction, and returns (S43) it to the resource server; similarly, the second approval client corresponding to the approval object c12 conducts transaction approval on the third resource transfer transaction through the local trusted execution environment in the second approval device of the approval object c12, obtains the transaction signature shard 2 of the approval object c12 for the third resource transfer transaction, and returns (S44) it to the resource server; when the resource server determines that the number of shards of the transaction signature shard 1 and the transaction signature shard 2 reaches the shard number threshold, it generates second transaction signature notification information for the third resource transfer transaction, determines that the transaction approval result of the second resource transfer transaction is transaction approval passed, and notifies the service object to conduct transaction signature on the second resource transfer transaction through the local trusted execution environment in the second hardware device of the service object, obtaining the transaction signature shard 3. Subsequently, when the resource server obtains the third packaged resource transfer transaction based on the transaction signature shards 1 - 3, it can send (S45) it to the blockchain node 20c, and the blockchain node calls the smart contract to determine the third resource transfer transaction corresponding to the third packaged resource transfer transaction, that is, to verify (S46) whether the signature information of multiple parties in the third packaged resource transfer transaction (such as the aggregated signature information determined by the second approval object and the service object and the signature information determined by the resource server) is correct, and execute the third resource transfer transaction.

[0183] S204. When receiving the resource update information, send the resource update information to the resource client.

[0184] Among them, when the resource client determines that the resource quota of the updated first-level resource reaches the resource quota of the target resource based on the resource update information, it sends the first resource transfer transaction to the resource server. That is, the first resource transfer transaction is resent.

[0185] S205. When receiving the first resource transfer transaction, send the first resource transfer transaction to the blockchain node.

[0186] Among them, the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction. Therefore, when the resource quota of the first-level resource in the first account address is insufficient, supplementary resources can be applied to the second account address and transferred to the first account address. Similarly, when the resource quota of the second-level resource in the second account address is insufficient, reference supplementary resources can be applied to the third account address and transferred to the second account address. This can improve the flexibility and success rate of resource transfer of business resources and their liquidity among account addresses at different address levels.

[0187] For example, as Figures 14 - 16 shown, Figures 14 - 16 is a schematic diagram of an interaction process of resource transfer provided by an embodiment of the present application; among them, as Figure 14: S301. The resource client generates a first resource transfer transaction TX1 in response to a resource transfer operation of a business object for a target resource on a first interface, and performs a transaction signature on the first resource transfer transaction with a first private key in the resource client to obtain a first signed resource transfer transaction TX1'. S302. The resource client sends the first signed resource transfer transaction to the resource server. S303. The resource server performs data packaging on the first signed resource transfer transaction with a data packaging private key to obtain a first packaged resource transfer transaction TX1". S304. The resource server sends the first packaged resource transfer transaction to the blockchain node. S305. When the blockchain node detects that the resource amount Xa of the first-level resource is less than the resource amount Xb of the target resource, it generates cross-level transfer information. S306. The blockchain node returns the cross-level transfer information to the resource server. S307. The resource server returns the cross-level transfer information to the resource client. S308. The resource client receives the cross-level transfer information and, in response to an address confirmation operation of the business object for a second account address in the cross-level transfer information, displays a second interface corresponding to the second account address. S309. The resource client generates a second resource transfer transaction TX2 in response to a resource transfer operation of the business object for supplementary resources on the second interface. S310. The resource client sends the second resource transfer transaction to the resource server. S311. When the resource server obtains a second packaged resource transfer transaction TX2" corresponding to the second resource transfer transaction, it sends the second packaged resource transfer transaction to the blockchain node. S312. When the blockchain node detects that the resource amount Xc of the second-level resource is less than the resource amount Xd of the supplementary resources, it generates reference cross-level transfer information. S313. The blockchain node returns the reference cross-level transfer information to the resource server. S314. The resource server returns the reference cross-level transfer information to the resource client. S315. The resource client receives the reference cross-level transfer information and, in response to an address confirmation operation of the business object for a third account address in the reference cross-level transfer information, displays a third interface corresponding to the third account address. S316. The resource client generates a third resource transfer transaction TX3 in response to a resource transfer operation of the business object for reference supplementary resources on the third interface. S317. The resource client sends the third resource transfer transaction to the resource server. S318. When the resource server obtains a third packaged resource transfer transaction TX3" corresponding to the third resource transfer transaction, it sends the second packaged resource transfer transaction to the blockchain node. S319. When the blockchain node transfers the reference supplementary resources in the third-level resource from the third account address to the second account address and updates the second-level resource based on the reference supplementary resources, it generates reference resource update information. S320. The blockchain node returns the reference resource update information to the resource server. S321. The resource server returns the reference resource update information to the resource client.S322. When the resource amount of the updated second-level resources determined by the resource client based on the reference resource update information reaches the resource amount of the supplementary resources, the resource client resends the second resource transfer transaction to the resource server; S323. The resource server resends the second packaged resource transfer transaction to the blockchain node; S324. The blockchain node transfers the supplementary resources in the (updated) second-level resources from the second account address to the first account address, and generates resource update information when updating the first-level resources based on the supplementary resources; S325. The blockchain node returns the resource update information to the resource server; S326. The resource server returns the resource update information to the resource client; S327. When the resource amount of the updated first-level resources determined by the resource client based on the resource update information reaches the resource amount of the target resources, the resource client resends the first signed resource transfer transaction corresponding to the first resource transfer transaction to the resource server; S328. The resource server sends the first packaged resource transfer transaction to the blockchain node; S329. The blockchain node transfers the target resources in the (updated) first-level resources from the first account address to the target account address indicated by the first resource transfer transaction.

[0188] Among them, as Figure 15 , the above Figure 14The step S311 in it can specifically be: S401. The resource server obtains a first resource transfer account address associated with the second account address; S402. The resource server searches among the N account addresses for an account address that matches the first account address, and when an account address that matches the first account address is found (determining that the first account address is the account address with resource transfer authority associated with the second account address), it obtains a first approval object associated with the second account address; for example, the first approval object includes approval object a and approval object b, and approval object a is the first approval object for transaction approval task 1, and approval object b is the second approval object for transaction approval task 2; S403. The resource server generates a first transaction approval notification message for the second resource transfer transaction; S404. The resource server sends the first transaction approval notification message to the first approval client a corresponding to approval object a; S405. In response to the transaction approval consent operation of approval object a for the second resource transfer transaction, the first approval client a conducts transaction approval on the second resource transfer transaction through the first approval device a of approval object a, and obtains transaction approval information a of approval object a for the second resource transfer transaction; S406. The first approval client a returns the transaction approval information a to the resource server; S407. When the resource server determines through the transaction approval information a that the transaction approval result of transaction approval task 1 is transaction approval passed, it sends the first transaction approval notification message to the first approval client b corresponding to approval object b; S408. In response to the transaction approval consent operation of approval object b for the second resource transfer transaction, the first approval client b conducts transaction approval on the second resource transfer transaction through the first approval device b of approval object b, and obtains transaction approval information b of approval object b for the second resource transfer transaction; S409. The first approval client b returns the transaction approval information b to the resource server; S410. When the resource server determines through the transaction approval information b that the transaction approval result of transaction approval task 2 is transaction approval passed, that is, the transaction approval results of both transaction approval task 1 and transaction approval task 2 are transaction approval passed, it determines that the transaction approval result of the second resource transfer transaction is transaction approval passed, and generates a first transaction signature notification message for the second resource transfer transaction; S411. The resource server sends the first transaction signature notification message to the resource client; S412. The resource client conducts transaction signature on the second resource transfer transaction through the first hardware device of the business object, and obtains the transaction signature information of the business object for the resource transfer transaction; S413. The resource client returns the transaction signature information; S414. The resource server determines the second signed resource transfer transaction corresponding to the second resource transfer transaction through the transaction signature information (and transaction approval information a - b); S415. Data-pack the second signed resource transfer transaction through the data-packing private key to obtain the second data-packed resource transfer transaction.

[0189] Among them, such asFigure 16 , the step S318 in the above Figure 14 can specifically be: S501. The resource server obtains a second resource transfer account address associated with the third account address; S502. The resource server searches among the M account addresses for an account address that matches the second account address, and when an account address that matches the second account address is found (determining that the second account address is the account address with resource transfer authority associated with the third account address), obtains a second approval object associated with the third account address; for example, the second approval object includes approval object c and approval object d; S503. The resource server generates a second transaction approval notification message for the third resource transfer transaction; S504. The resource server sends the second transaction approval notification message to the second approval client c corresponding to approval object c; S505. The resource server sends the second transaction approval notification message to the second approval client d corresponding to approval object d; S506. In response to the transaction approval consent operation of approval object c for the third resource transfer transaction, the second approval client c conducts transaction approval on the third resource transfer transaction through the local trusted execution environment in the second approval device c of approval object c, and obtains a transaction signature shard c for the third resource transfer transaction by approval object c; S507. The second approval client c returns the transaction signature shard c to the resource server; S508. In response to the transaction approval consent operation of approval object d for the third resource transfer transaction, the second approval client d conducts transaction approval on the third resource transfer transaction through the local trusted execution environment in the second approval device d of approval object d, and obtains a transaction signature shard d for the third resource transfer transaction by approval object d; S509. The second approval client d returns the transaction signature shard d to the resource server; S510. When the resource server determines that the number of shards of the transaction signature shard c and the transaction signature shard d reaches the shard number threshold, it generates a second transaction signature notification message for the third resource transfer transaction; S511. The resource server sends the second transaction signature notification message to the resource client; S512. The resource client conducts transaction signature on the third resource transfer transaction through the local trusted execution environment in the second hardware device of the business object, and obtains a transaction signature shard X for the third resource transfer transaction; S513. The resource client returns the transaction signature information'; S514. The resource server determines the third signed resource transfer transaction corresponding to the third resource transfer transaction through the transaction signature shard X and the transaction signature information c-d; S515. Data-pack the third signed resource transfer transaction with the data-packing private key to obtain the third data-packed resource transfer transaction.

[0190] In the embodiments of the present application, partial service resources of a service object can be stored by multiple account addresses respectively. For example, the first-level resources are stored by the first account address, and the second-level resources are stored by the second account address, and the address level of the first account address is lower than that of the second account address. When the resource client generates a first resource transfer transaction through a resource transfer operation of the target resource on the first interface corresponding to the first account address, the first resource transfer transaction can be sent to the blockchain node through the resource server. When the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resource, it can generate cross-level transfer information to instruct the service object to transfer a certain amount of service resources from the second account address to the first account address. At this time, in response to the address confirmation operation of the service object for the second account address in the cross-level transfer information, the second interface corresponding to the second account address can be displayed. When the resource client generates a second resource transfer transaction through a resource transfer operation of supplementary resources on the second interface corresponding to the second account address, the second resource transfer transaction can be sent to the blockchain node through the resource server. The blockchain node can transfer the supplementary resources in the second-level resources from the second account address to the first account address, and when updating the first-level resources based on the supplementary resources, generate resource update information, that is, supplement the first-level resources in the first account address with the second-level resources in the second account address. When the resource client determines that the resource amount of the updated first-level resources reaches the resource amount of the target resource (that is, the first resource transfer transaction can be executed through the updated first-level resources), the first resource transfer transaction can be sent to the blockchain node through the resource server. The blockchain node can transfer the target resource from the first account address to the target account address indicated by the first resource transfer transaction to implement the resource transfer of the service object. Therefore, by storing service resources in multiple levels, when the service resources at the lower level are insufficient, a certain amount of service resources can be transferred from the service resources at the higher level to the lower level, so that the resource transfer transaction at the lower level can be successfully executed, thereby improving the flexibility and success rate of resource transfer. At the same time, by storing service resources through multiple levels of account addresses, it can be ensured that even if the first-level resources are illegally transferred, all the service resources of the service object will not be lost, ensuring the resource security of the service object.

[0191] Further, please refer to Figure 17 , Figure 17 which is a schematic structural diagram of a resource processing device provided by an embodiment of the present application. As Figure 17As shown in the figure, the resource processing device 1 can be applied to a computer device. It should be understood that the resource processing device 1 can be a computer program (including program code) running in the computer device. For example, the resource processing device 1 can be an application software. It can be understood that the resource processing device 1 can be used to execute the corresponding steps in the method provided in the embodiments of the present application. As Figure 17 shown in the figure, the resource processing device 1 may include: an interface output module 11, a first transaction processing module 12, a second transaction processing module 13, and a third transaction processing module 14; where:

[0192] The interface output module 11 is configured to display a first account address and a second account address on the address display interface of the resource client, and output a first interface corresponding to the first account address in response to a selection operation of the service object for the first account address;

[0193] The first transaction processing module 12 is configured to generate a first resource transfer transaction in response to a resource transfer operation of the service object for the target resource on the first interface, and send the first resource transfer transaction to the blockchain node through the resource server corresponding to the resource client, so that when the blockchain node detects that the resource amount of the first-level resource is less than the resource amount of the target resource, a cross-level transfer information is generated; the cross-level transfer information is used to instruct the service object to transfer the service resources in the second account address across levels to the first account address;

[0194] The interface output module 11 is further configured to receive the cross-level transfer information, and display a second interface corresponding to the second account address in response to an address confirmation operation of the service object for the second account address in the cross-level transfer information;

[0195] The second transaction processing module 13 is configured to generate a second resource transfer transaction in response to a resource transfer operation of the service object for the supplementary resource on the second interface, and send the second resource transfer transaction to the blockchain node through the resource server, so that when the blockchain node transfers the supplementary resource in the second-level resource from the second account address to the first account address and updates the first-level resource based on the supplementary resource, a resource update information is generated; the supplementary resource is determined based on the resource difference between the first-level resource and the target resource;

[0196] The first transaction processing module 12 is further configured to receive the resource update information, and when it is determined based on the resource update information that the resource amount of the updated first-level resource reaches the resource amount of the target resource, send the first resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction.

[0197] Among them, the first transaction processing module 12 includes:

[0198] The first transaction signature unit 121 is used to perform a transaction signature on the first resource transfer transaction through the first private key in the resource client, obtaining the first signed resource transfer transaction;

[0199] The first signed transaction sending unit 122 is used to send the first signed resource transfer transaction to the resource server, so that the resource server performs data packaging on the first signed resource transfer transaction through the data packaging private key, obtaining the first packaged resource transfer transaction, and sending the first packaged resource transfer transaction to the blockchain node; the first packaged resource transfer transaction is used to instruct the blockchain node to determine the first signed resource transfer transaction through the public key corresponding to the data packaging private key; the first signed resource transfer transaction is used to instruct the blockchain node to determine the first resource transfer transaction through the public key corresponding to the first private key.

[0200] Among them, the second transaction processing module 13 includes:

[0201] The second transaction sending unit 131 is used to send the second resource transfer transaction to the resource server, so that when the resource server determines that the first account address is the account address associated with the second account address and having the resource transfer permission, it notifies the first approval client corresponding to the first approval object associated with the second account address, authorizing the first approval device of the first approval object to perform a transaction approval on the second resource transfer transaction through the second private key in the first approval device, obtaining the first transaction approval information, and when determining that the transaction approval result of the second resource transfer transaction is transaction approval passed based on the first transaction approval information, generating the first transaction signature notification information for the second resource transfer transaction;

[0202] The second transaction signature unit 132 is used to, when receiving the first transaction signature notification information, authorize the first hardware device of the service object to perform a transaction signature on the second resource transfer transaction through the second private key in the first hardware device, obtaining the transaction signature information corresponding to the second resource transfer transaction;

[0203] The second signed transaction sending unit 133 is used to send the transaction signature information to the resource server, so that when the resource server determines the second signed resource transfer transaction based on the transaction signature information, it performs data packaging on the second signed resource transfer transaction through the data packaging private key, obtaining the second packaged resource transfer transaction, and sending the second packaged resource transfer transaction to the blockchain node; the second packaged resource transfer transaction is used to instruct the blockchain node to determine the second signed resource transfer transaction through the public key corresponding to the data packaging private key; the second signed resource transfer transaction is used to instruct the blockchain node to determine the second resource transfer transaction through the public key corresponding to the transaction signature information.

[0204] Among them, the resource server is used to send a to-be-verified challenge value for the first hardware device of the service object to the resource client;

[0205] The second transaction signature unit 132 includes:

[0206] A data signature subunit 1321, configured to perform data signature on the challenge value to be verified by using a second private key in the first hardware device, so as to obtain challenge value signature information;

[0207] The data signature subunit 1321 is further configured to return the challenge value signature information to the resource server, so that when the resource server performs data signature verification on the challenge value signature information by using a public key corresponding to the second private key in the first hardware device and obtains a challenge value to be matched, the resource server performs data comparison on the challenge value to be matched and the challenge value to be verified, so as to obtain a data comparison result;

[0208] A data comparison subunit 1322, configured to determine that the object authentication of the business object is successful when the data comparison result indicates that the challenge value to be matched is the same as the challenge value to be verified;

[0209] A second transaction signature subunit 1323, configured to perform transaction signature on the second resource transfer transaction by using a second private key in the first hardware device, so as to obtain transaction signature information.

[0210] Wherein, the account address in the resource client further includes a third account address; the third account address is used to store the third-level resources of the business object; the address level of the second account address is lower than the address level of the third account address; the blockchain node is configured to compare the resource amount of the second-level resources and the resource amount of the supplementary resources when obtaining the second resource transfer transaction, and generate reference cross-level transfer information when detecting that the resource amount of the second-level resources is less than the resource amount of the supplementary resources; the reference cross-level transfer information is used to instruct the business object to perform cross-level transfer of the business resources in the third account address to the second account address;

[0211] The third transaction processing module 14 of the resource processing device 1 further includes:

[0212] A third transaction processing module 14, configured to receive the reference cross-level transfer information, and display a third interface corresponding to the third account address in response to an address confirmation operation of the business object for the third account address in the reference cross-level transfer information;

[0213] The third transaction processing module 14 is further configured to, in response to a resource transfer operation of a business object for a reference supplementary resource on the third interface, generate a third resource transfer transaction, and send the third resource transfer transaction to a blockchain node through a resource server, so that when the blockchain node transfers the reference supplementary resource in the third-level resource from a third account address to a second account address and updates the second-level resource based on the reference supplementary resource, a reference resource update information is generated; the reference supplementary resource is determined based on a resource difference between the second-level resource and a supplementary resource;

[0214] The third transaction processing module 14 is further configured to receive the reference resource update information, and when it is determined based on the reference resource update information that the resource amount of the updated second-level resource reaches the resource amount of the supplementary resource, notify the second transaction processing module 13 to resend the second resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the supplementary resource from the second account address to the first account address.

[0215] Wherein, the third transaction processing module 14 includes:

[0216] A third transaction sending unit 141, configured to send the third resource transfer transaction to the resource server, so that when the resource server determines that the second account address is an account address associated with the third account address and having resource transfer authority, notify a second approval client of a second approval object associated with the third account address, and when it is determined that the local trusted execution environment of the second approval device of the second approval object belongs to a secure execution environment, perform transaction approval on the third resource transfer transaction through a third private key determined by the local trusted execution environment of the second approval device, obtain a first transaction signature shard for the third resource transfer transaction, and when it is determined that the number of shards of the first transaction signature shard reaches a shard number threshold, determine that the transaction approval result of the third resource transfer transaction is transaction approval passed, and generate a second transaction signature notification information for the third resource transfer transaction;

[0217] A third transaction signature unit 142, configured to, when receiving the second transaction signature notification information and when it is determined that the local trusted execution environment of the second hardware device of the business object belongs to a secure execution environment, perform transaction signature on the third resource transfer transaction through a third private key determined by the local trusted execution environment of the second hardware device, to obtain a second transaction signature shard for the third resource transfer transaction;

[0218] The signature shard sending unit 143 is configured to send the second transaction signature shard to the resource server, so that when the resource server determines the third signature resource transfer transaction based on the first transaction signature shard and the second transaction signature shard, the resource server packs the third signature resource transfer transaction through the data packaging private key to obtain the third packed resource transfer transaction, and sends the third packed resource transfer transaction to the blockchain node; the third packed resource transfer transaction is used to instruct the blockchain node to determine the third signature resource transfer transaction through the public key corresponding to the data packaging private key; the third signature resource transfer transaction is used to instruct the blockchain node to determine the third resource transfer transaction through the public keys corresponding to the first transaction signature shard and the second transaction signature shard.

[0219] Among them, the third transaction signature unit 142 includes:

[0220] The authentication request sending subunit 1421 is configured to send the remote authentication request to the resource server when the remote authentication request generated by the local trusted execution environment of the second hardware device is obtained; the remote authentication request is used to represent the remote public key and the remote authentication report of the identity information of the local trusted execution environment of the second hardware device; the remote authentication request is used to instruct the resource server to perform remote authentication on the local trusted execution environment of the second hardware device based on the remote public key and the remote authentication report, and when the remote authentication is successful, generate a remote authentication success report associated with the local trusted execution environment of the second hardware device;

[0221] The authentication report returning subunit 1422 is configured to return the remote authentication success report to the second hardware device when the remote authentication success report is received, so that the second hardware device determines that the local trusted execution environment of the second hardware device belongs to the secure execution environment based on the remote authentication success report, and obtains the third private key determined by the local trusted execution environment of the second hardware device based on the remote authentication success report;

[0222] The trusted environment signature subunit 1423 is configured to perform transaction signature on the third resource transfer transaction through the third private key determined by the local trusted execution environment of the second hardware device to obtain the second transaction signature shard for the third resource transfer transaction.

[0223] Among them, for the specific implementation manners of the interface output module 11, the first transaction processing module 12, the second transaction processing module 13, and the third transaction processing module 14, reference may be made to the relevant descriptions in the foregoing embodiments, and details will not be elaborated herein. It should be understood that the description of the beneficial effects obtained by using the same method will not be elaborated either.

[0224] Further, please refer to Figure 18 , Figure 18 which is a schematic structural diagram of a resource processing device provided in an embodiment of the present application. As Figure 18As shown, the resource processing device 2 can be applied to a computer device. It should be understood that the resource processing device 2 can be a computer program (including program code) running on the computer device. For example, the resource processing device 2 can be an application software. It can be understood that the resource processing device 2 can be used to execute the corresponding steps in the method provided in the embodiments of the present application. As Figure 18 shown, the resource processing device 2 may include: a first transaction sending module 21, an information sending module 22, a second transaction sending module 23, and a third transaction sending module 24; where:

[0225] The first transaction sending module 21 is configured to, when receiving a first resource transfer transaction sent by a resource client, send the first resource transfer transaction to a blockchain node, so that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resources indicated by the first resource transfer transaction, generate cross-level transfer information; the cross-level transfer information is used to instruct a business object to transfer business resources in a second account address across levels to a first account address; the first resource transfer transaction is generated by the resource client in response to a resource transfer operation of the target resources on a first interface of the first account address; the first interface is an address display interface of the resource client that displays the first account address and the second account address and outputs in response to a selection operation of the business object on the first account address;

[0226] The information sending module 22 is configured to, when receiving the cross-level transfer information, send the cross-level transfer information to the resource client, so that when the resource client responds to an address confirmation operation on the second account address in the cross-level transfer information, display a second interface corresponding to the second account address, and in response to a resource transfer operation of supplementary resources on the second interface, generate a second resource transfer transaction;

[0227] The second transaction sending module 23 is configured to, when receiving the second resource transfer transaction, send the second resource transfer transaction to the blockchain node, so that when the blockchain node transfers the supplementary resources in the second-level resources from the second account address to the first account address and updates the first-level resources based on the supplementary resources, generate resource update information; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources;

[0228] The information sending module 22 is further configured to, when receiving the resource update information, send the resource update information to the resource client, so that when the resource client determines that the resource amount of the updated first-level resources reaches the resource amount of the target resources based on the resource update information, send the first resource transfer transaction to the resource server;

[0229] The first transaction sending module 21 is further configured to, when receiving a first resource transfer transaction, send the first resource transfer transaction to a blockchain node, so that the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction.

[0230] Wherein, the resource client stores a first private key, and the first private key in the resource client is used to perform a transaction signature on the first resource transfer transaction to obtain a first signed resource transfer transaction;

[0231] The first transaction sending module 21 is specifically configured to:

[0232] When receiving the first signed resource transfer transaction corresponding to the first resource transfer transaction sent by the resource client, perform data packaging on the first signed resource transfer transaction through a data packaging private key to obtain a first packaged resource transfer transaction;

[0233] Send the first packaged resource transfer transaction to the blockchain node; the first packaged resource transfer transaction is used to instruct the blockchain node to determine the first signed resource transfer transaction through the public key corresponding to the data packaging private key; the first signed resource transfer transaction is used to instruct the blockchain node to determine the first resource transfer transaction through the public key corresponding to the first private key.

[0234] Wherein, the second transaction sending module 23 includes:

[0235] A first address obtaining unit 231, configured to obtain a first resource transfer account address associated with a second account address; the first resource transfer account address includes N account addresses with resource transfer permissions associated with the second account address; N is a positive integer;

[0236] A second transaction approval notification unit 232, configured to, among the N account addresses, find an account address matching the first account address, and when finding an account address matching the first account address, notify a first approval client corresponding to a first approval object associated with the second account address to authorize a first approval device of the first approval object to perform a transaction approval on a second resource transfer transaction through a second private key in the first approval device to obtain a first transaction approval information;

[0237] A first signature information processing unit 233, configured to generate a first transaction signature notification information for the second resource transfer transaction when determining that the transaction approval result of the second resource transfer transaction is transaction approval passed through the first transaction approval information;

[0238] The first signature information processing unit 233 is further configured to send the first transaction signature notification information to the resource client, so that the resource client authorizes the first hardware device of the business object to perform a transaction signature on the second resource transfer transaction through the second private key in the first hardware device, and obtain the transaction signature information corresponding to the second resource transfer transaction;

[0239] The second transaction packaging unit 234 is configured to, when receiving the transaction signature information, determine the second signed resource transfer transaction based on the transaction signature information, and perform data packaging on the second signed resource transfer transaction through the data packaging private key to obtain the second packaged resource transfer transaction;

[0240] The second transaction packaging unit 234 is further configured to send the second packaged resource transfer transaction to the blockchain node; the second packaged resource transfer transaction is used to instruct the blockchain node to determine the second signed resource transfer transaction through the public key corresponding to the data packaging private key; the second signed resource transfer transaction is used to instruct the blockchain node to determine the second resource transfer transaction through the public key corresponding to the transaction signature information.

[0241] Wherein, the first address acquisition unit 231 includes:

[0242] The address query subunit 2311 is configured to generate an account address query request for the second account address;

[0243] The address query subunit 2311 is further configured to send the account address query request to the blockchain node, so that the blockchain node queries the first resource transfer account address associated with the second account address on the blockchain;

[0244] The address query subunit 2311 is further configured to receive the first resource transfer account address associated with the second account address returned by the blockchain node.

[0245] Wherein, the first address acquisition unit 231 further includes:

[0246] The address on-chain subunit 2312 is configured to receive a transfer address on-chain transaction for the second account address initiated by the business object through the resource client; the transfer address on-chain transaction includes the first account address;

[0247] The address on-chain approval subunit 2313 is configured to notify the first approval client to authorize the first approval device to perform a transaction approval on the transfer address on-chain transaction through the second private key in the first approval device, and obtain the on-chain transaction approval information;

[0248] The address on-chain approval subunit 2313 is further configured to generate an on-chain transaction signature notification information for the transfer address on-chain transaction when it is determined through the on-chain transaction approval information that the transaction approval result of the transfer address on-chain transaction is transaction approval passed;

[0249] The address on-chain sub-unit 2312 is further configured to send the on-chain transaction signature notification information to the resource client, so that the resource client authorizes the first hardware device to perform a transaction signature on the transfer address on-chain transaction through the second private key in the first hardware device, obtaining the on-chain transaction signature information corresponding to the transfer address on-chain transaction;

[0250] The address on-chain sub-unit 2312 is further configured to, when receiving the on-chain transaction signature information, determine the signature address transfer on-chain transaction based on the on-chain transaction signature information, and perform data packaging on the signature address transfer on-chain transaction through the data packaging private key, obtaining the packaged address transfer on-chain transaction;

[0251] The address on-chain sub-unit 2312 is further configured to send the packaged address transfer on-chain transaction to the blockchain node, so that when the blockchain node obtains the transfer address on-chain transaction through the packaged address transfer on-chain transaction, the first account address is added to the first resource transfer account address associated with the second account address based on the transfer address on-chain transaction.

[0252] Wherein, the account address in the resource client further includes a third account address; the third account address is used to store the third-level resources of the business object; the address level of the second account address is lower than the address level of the third account address; the blockchain node is configured to, when obtaining the second resource transfer transaction, compare the resource amount of the second-level resources and the resource amount of the supplementary resources, and when detecting that the resource amount of the second-level resources is less than the resource amount of the supplementary resources, generate a reference cross-level transfer information; the reference cross-level transfer information is used to instruct the business object to perform a cross-level transfer of the business resources in the third account address to the second account address;

[0253] The resource processing device 2 further includes:

[0254] The third transaction sending module 24 is configured to, when receiving the reference cross-level transfer information, return the reference cross-level transfer information to the resource client, so that the resource client, in response to the address confirmation operation of the business object for the third account address in the reference cross-level transfer information, displays the third interface corresponding to the third account address, and in response to the resource transfer operation of the reference supplementary resources on the third interface by the business object, generates a third resource transfer transaction;

[0255] The third transaction sending module 24 is further configured to, when receiving the third resource transfer transaction, send the third resource transfer transaction to the blockchain node, so that when the blockchain node transfers the reference supplementary resources in the third-level resources from the third account address to the second account address and updates the second-level resources based on the reference supplementary resources, generate a reference resource update information; the reference supplementary resources are determined based on the resource difference between the second-level resources and the supplementary resources;

[0256] The third transaction sending module 24 is further configured to receive reference resource update information and return the reference resource update information to the resource client, so that when the resource client determines that the resource amount of the updated second-level resource reaches the resource amount of the supplementary resource based on the reference resource update information, it resends the second resource transfer transaction;

[0257] The third transaction sending module 24 is further configured to, when receiving the second resource transfer transaction, send the second resource transfer transaction to the blockchain node, so that the blockchain node transfers the supplementary resource from the second account address to the first account address.

[0258] Wherein, the third transaction sending module 24 includes:

[0259] The second address acquisition unit 241 is configured to acquire a second resource transfer account address associated with the third account address; the second resource transfer account address includes M account addresses with resource transfer permissions associated with the third account address; M is a positive integer;

[0260] The third transaction approval notification unit 242 is configured to search for an account address matching the second account address among the M account addresses, and when an account address matching the second account address is found, notify the second approval client corresponding to the second approval object associated with the third account address. When it is determined that the local trusted execution environment of the second approval device of the second approval object belongs to a secure execution environment, the third resource transfer transaction is approved for transaction by the third private key determined by the local trusted execution environment of the second approval device, and a first transaction signature shard for the third resource transfer transaction is obtained;

[0261] The second signature information processing unit 243 is configured to generate a second transaction signature notification information for the third resource transfer transaction when it is determined that the number of shards of the first transaction signature shard reaches the shard number threshold;

[0262] The second signature information processing unit 243 is further configured to send the second transaction signature notification information to the resource client, so that when the resource client determines that the local trusted execution environment of the second hardware device of the business object belongs to a secure execution environment, the third resource transfer transaction is signed for transaction by the third private key determined by the local trusted execution environment of the second hardware device, and a second transaction signature shard for the third resource transfer transaction is obtained;

[0263] The third transaction packaging unit 244 is configured to, when receiving the second transaction signature shard, determine the third signature resource transfer transaction based on the first transaction signature shard and the second transaction signature shard, perform data packaging on the third signature resource transfer transaction through the data packaging private key to obtain the third packaged resource transfer transaction, and send the third packaged resource transfer transaction to the blockchain node; the third packaged resource transfer transaction is used to instruct the blockchain node to determine the third signature resource transfer transaction through the public key corresponding to the data packaging private key; the third signature resource transfer transaction is used to instruct the blockchain node to determine the third resource transfer transaction through the public keys corresponding to the first transaction signature shard and the second transaction signature shard.

[0264] Among them, for the specific implementation manners of the first transaction sending module 21, the information sending module 22, the second transaction sending module 23, and the third transaction sending module 24, reference may be made to the relevant descriptions in the foregoing embodiments, and details will not be elaborated herein. It should be understood that the beneficial effects obtained by using the same method will not be elaborated either.

[0265] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other relevant parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of the overall module or unit that includes the functions of the module or unit.

[0266] Further, please refer to Figure 19 , Figure 19 which is a schematic structural diagram of a computer device provided by an embodiment of the present application. As Figure 19 shown, the computer device 1900 can be a service terminal or a server, and no limitation is imposed here. For the sake of understanding, the present application takes the computer device as a server as an example. The computer device 1900 may include: a processor 1901, a network interface 1904, and a memory 1905. In addition, the computer device 1900 may further include: a user interface 1903, and at least one communication bus 1902. Among them, the communication bus 1902 is used to realize the connection and communication between these components. Among them, the user interface 1903 may further include a standard wired interface and a wireless interface. The network interface 1904 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1905 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. The memory 1905 may optionally be at least one storage device located far from the foregoing processor 1901. AsFigure 19 As shown in Figure 19 , the memory 1905, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0267] Among them, the network interface 1904 in the computer device 1900 can also provide network data interaction functions. In Figure 19 the computer device 1900 shown in Figure 19 , the network interface 1904 can provide network data interaction functions; while the user interface 1903 is mainly used to provide an input interface for users; and the processor 1901 can be used to call the device control application program stored in the memory 1905 to execute the above Figure 5 and Figure 11 descriptions of the resource processing method in the corresponding embodiments, and can also execute the descriptions of the resource processing device 1 in the corresponding embodiments mentioned above Figure 17 and Figure 18 the descriptions of the resource processing device 2 in the corresponding embodiments, which will not be elaborated here. In addition, the descriptions of the beneficial effects of adopting the same method will not be elaborated either.

[0268] In addition, it should be noted here that: The embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores the computer programs executed by the resource processing device 1 and the resource processing device 2 mentioned above, and the computer programs include computer instructions. When the processor executes the computer instructions, it can execute the descriptions of the resource processing method in the corresponding embodiments mentioned above Figure 5 and Figure 11 Therefore, it will not be elaborated here. In addition, the descriptions of the beneficial effects of adopting the same method will not be elaborated either. For the technical details not disclosed in the embodiments of the computer-readable storage medium involved in the present application, please refer to the descriptions of the method embodiments of the present application. As an example, the computer instructions can be deployed to be executed on a computing device, or on multiple computing devices located at one place, or on multiple computing devices distributed at multiple places and interconnected through a communication network. The multiple computing devices distributed at multiple places and interconnected through a communication network can form a blockchain system.

[0269] In addition, it should be noted that: The embodiments of the present application also provide a computer program product or a computer program. The computer program product or the computer program may include computer instructions, and the computer instructions can be stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor can execute the computer instructions, so that the computer device executes the above Figure 5 and Figure 11The description of the resource processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated. For the technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0270] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, some steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0271] The steps in the method embodiments of this application can be adjusted, combined, and deleted according to actual needs.

[0272] The modules in the device embodiments of this application can be combined, divided, and deleted according to actual needs.

[0273] Those of ordinary skill in the art can understand that all or part of the processes in the above method embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above method embodiments. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.

[0274] The above-disclosed are only the preferred embodiments of this application. Of course, the scope of rights of this application cannot be limited thereby. Therefore, equivalent changes made according to the claims of this application still fall within the scope covered by this application.

Claims

1. A resource processing method, characterized in that, The method is executed by a resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store first-level resources of a business object; the second account address is used to store second-level resources of the business object; the address level of the first account address is lower than that of the second account address; the method includes: On the address display interface of the resource client, display the first account address and the second account address, and in response to a selection operation of the business object for the first account address, output a first interface corresponding to the first account address; In response to a resource transfer operation of the business object for a target resource on the first interface, generate a first resource transfer transaction, and send the first resource transfer transaction to a blockchain node through a resource server corresponding to the resource client, so that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resource, generate cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer business resources in the second account address to the first account address across levels; Receive the cross-level transfer information, and in response to an address confirmation operation of the business object for the second account address in the cross-level transfer information, display a second interface corresponding to the second account address; In response to a resource transfer operation of the business object for supplementary resources on the second interface, generate a second resource transfer transaction, and send the second resource transfer transaction to the blockchain node through the resource server, so that when the blockchain node transfers supplementary resources in the second-level resources from the second account address to the first account address and updates the first-level resources based on the supplementary resources, generate resource update information; the supplementary resources are determined based on the resource difference between the first-level resources and the target resource; Receive the resource update information, and when it is determined based on the resource update information that the resource amount of the updated first-level resources reaches the resource amount of the target resource, send the first resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction.

2. The method according to claim 1, wherein The sending the first resource transfer transaction to the blockchain node through the resource server corresponding to the resource client includes: Sign the first resource transfer transaction with a first private key in the resource client to obtain a first signed resource transfer transaction; Send the first signature resource transfer transaction to the resource server, so that the resource server packs the first signature resource transfer transaction through the data packaging private key to obtain a first packed resource transfer transaction, and sends the first packed resource transfer transaction to the blockchain node; the first packed resource transfer transaction is used to instruct the blockchain node to determine the first signature resource transfer transaction through the public key corresponding to the data packaging private key; the first signature resource transfer transaction is used to instruct the blockchain node to determine the first resource transfer transaction through the public key corresponding to the first private key.

3. The method according to claim 1, wherein The step of sending the second resource transfer transaction to the blockchain node by the resource server includes: Send the second resource transfer transaction to the resource server, so that when the resource server determines that the first account address is the account address associated with the second account address and having the resource transfer authority, it notifies the first approval client corresponding to the first approval object associated with the second account address, authorizes the first approval device of the first approval object to approve the second resource transfer transaction through the second private key in the first approval device to obtain first transaction approval information, and when determining that the transaction approval result of the second resource transfer transaction is transaction approval passed through the first transaction approval information, generate first transaction signature notification information for the second resource transfer transaction; When receiving the first transaction signature notification information, authorize the first hardware device of the business object to sign the second resource transfer transaction through the second private key in the first hardware device to obtain transaction signature information corresponding to the second resource transfer transaction; Send the transaction signature information to the resource server, so that when the resource server determines the second signature resource transfer transaction based on the transaction signature information, it packs the second signature resource transfer transaction through the data packaging private key to obtain a second packed resource transfer transaction, and sends the second packed resource transfer transaction to the blockchain node; the second packed resource transfer transaction is used to instruct the blockchain node to determine the second signature resource transfer transaction through the public key corresponding to the data packaging private key; the second signature resource transfer transaction is used to instruct the blockchain node to determine the second resource transfer transaction through the public key corresponding to the transaction signature information.

4. The method according to claim 3, wherein The resource server is used to send a challenge value to be verified for the first hardware device of the business object to the resource client; The step of authorizing the first hardware device of the business object to sign the second resource transfer transaction through the second private key in the first hardware device to obtain transaction signature information corresponding to the second resource transfer transaction includes: Sign the challenge value to be verified through the second private key in the first hardware device to obtain challenge value signature information; Return the challenge value signature information to the resource server, so that when the resource server performs data signature verification on the challenge value signature information using the public key corresponding to the second private key in the first hardware device to obtain the challenge value to be matched, compare the challenge value to be matched with the challenge value to be verified to obtain a data comparison result; When the data comparison result indicates that the challenge value to be matched is the same as the challenge value to be verified, determine that the object authentication of the business object is successful; Perform a transaction signature on the second resource transfer transaction using the second private key in the first hardware device to obtain the transaction signature information.

5. The method according to claim 1, characterized in that, The account address in the resource client further includes a third account address; the third account address is used to store the third-level resources of the business object; the address level of the second account address is lower than the address level of the third account address; the blockchain node is used to compare the resource amount of the second-level resources with the resource amount of the supplementary resources when obtaining the second resource transfer transaction, and generate reference cross-level transfer information when detecting that the resource amount of the second-level resources is less than the resource amount of the supplementary resources; The reference cross-level transfer information is used to instruct the business object to transfer the business resources in the third account address across levels to the second account address; The method further includes: Receive the reference cross-level transfer information, and in response to the address confirmation operation of the business object for the third account address in the reference cross-level transfer information, display the third interface corresponding to the third account address; In response to the resource transfer operation of the reference supplementary resources on the third interface by the business object, generate a third resource transfer transaction, and send the third resource transfer transaction to the blockchain node through the resource server, so that when the blockchain node transfers the reference supplementary resources in the third-level resources from the third account address to the second account address and updates the second-level resources based on the reference supplementary resources, generate reference resource update information; the reference supplementary resources are determined based on the resource difference between the second-level resources and the supplementary resources; Receive the reference resource update information, and when it is determined based on the reference resource update information that the resource amount of the updated second-level resources reaches the resource amount of the supplementary resources, resend the second resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the supplementary resources from the second account address to the first account address.

6. The method according to claim 5, wherein The sending the third resource transfer transaction to the blockchain node through the resource server includes: Send the third resource transfer transaction to the resource server, so that when the resource server determines that the second account address is the account address associated with the third account address and has the resource transfer permission, it notifies the second approval client of the second approval object associated with the third account address. When it is determined that the local trusted execution environment of the second approval device of the second approval object belongs to the secure execution environment, the third resource transfer transaction is approved for the transaction by the third private key determined by the local trusted execution environment of the second approval device, and the first transaction signature shard for the third resource transfer transaction is obtained. And when it is determined that the number of shards of the first transaction signature shard reaches the shard number threshold, it is determined that the transaction approval result of the third resource transfer transaction is transaction approval passed, and the second transaction signature notification information for the third resource transfer transaction is generated; When receiving the second transaction signature notification information and when it is determined that the local trusted execution environment of the second hardware device of the business object belongs to the secure execution environment, the third resource transfer transaction is signed for the transaction by the third private key determined by the local trusted execution environment of the second hardware device, and the second transaction signature shard for the third resource transfer transaction is obtained; Send the second transaction signature shard to the resource server, so that when the resource server determines the third signed resource transfer transaction based on the first transaction signature shard and the second transaction signature shard, it packs the third signed resource transfer transaction by the data packing private key to obtain the third packed resource transfer transaction, and sends the third packed resource transfer transaction to the blockchain node; the third packed resource transfer transaction is used to instruct the blockchain node to determine the third signed resource transfer transaction through the public key corresponding to the data packing private key; the third signed resource transfer transaction is used to instruct the blockchain node to determine the third resource transfer transaction through the public keys corresponding to the first transaction signature shard and the second transaction signature shard.

7. The method according to claim 6, wherein The step of, when it is determined that the local trusted execution environment of the second hardware device of the business object belongs to the secure execution environment, signing the third resource transfer transaction by the third private key determined by the local trusted execution environment of the second hardware device to obtain the second transaction signature shard for the third resource transfer transaction, includes: When obtaining the remote authentication request generated by the local trusted execution environment of the second hardware device, send the remote authentication request to the resource server; the remote authentication request is used to represent the remote public key and the remote authentication report of the identity information of the local trusted execution environment of the second hardware device; the remote authentication request is used to instruct the resource server to perform remote authentication on the local trusted execution environment of the second hardware device based on the remote public key and the remote authentication report, and when the remote authentication is successful, generate a remote authentication success report associated with the local trusted execution environment of the second hardware device; Upon receiving the remote authentication success report, return the remote authentication success report to the second hardware device, so that the second hardware device determines that the local trusted execution environment of the second hardware device belongs to the secure execution environment based on the remote authentication success report, and obtains a third private key determined by the local trusted execution environment of the second hardware device based on the remote authentication success report; Perform transaction signing on the third resource transfer transaction with the third private key determined by the local trusted execution environment of the second hardware device to obtain a second transaction signature shard for the third resource transfer transaction.

8. A resource processing method, characterized in that The method is executed by a resource server corresponding to a resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store first-level resources of a business object; The second account address is used to store second-level resources of the business object; The address level of the first account address is lower than the address level of the second account address; the method includes: Upon receiving the first resource transfer transaction sent by the resource client, send the first resource transfer transaction to a blockchain node, so that when the blockchain node detects that the resource amount of the first-level resources is less than the resource amount of the target resources indicated by the first resource transfer transaction, generate cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer business resources in the second account address across levels to the first account address; the first resource transfer transaction is generated by the resource client in response to a resource transfer operation of the target resources on a first interface of the first account address of the business object; the first interface is output on the address display interface of the resource client when the first account address and the second account address are displayed and in response to a selection operation of the business object on the first account address; Upon receiving the cross-level transfer information, send the cross-level transfer information to the resource client, so that when the resource client responds to an address confirmation operation of the business object on the second account address in the cross-level transfer information, display a second interface corresponding to the second account address, and in response to a resource transfer operation of the supplementary resources on the second interface by the business object, generate a second resource transfer transaction; Upon receiving the second resource transfer transaction, send the second resource transfer transaction to the blockchain node, so that when the blockchain node transfers supplementary resources in the second-level resources from the second account address to the first account address and updates the first-level resources based on the supplementary resources, generate resource update information; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources; Upon receiving the resource update information, send the resource update information to the resource client, so that when the resource client determines that the resource quota of the updated first-level resource reaches the resource quota of the target resource based on the resource update information, the first resource transfer transaction is sent to the resource server; Upon receiving the first resource transfer transaction, send the first resource transfer transaction to the blockchain node, so that the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction.

9. The method according to claim 8, wherein The resource client stores a first private key; the first private key in the resource client is used to perform a transaction signature on the first resource transfer transaction to obtain a first signed resource transfer transaction; The step of sending the second resource transfer transaction to the blockchain node upon receiving it includes: Upon receiving the first signed resource transfer transaction corresponding to the first resource transfer transaction sent by the resource client, perform data packaging on the first signed resource transfer transaction through the data packaging private key to obtain a first packaged resource transfer transaction; Send the first packaged resource transfer transaction to the blockchain node; the first packaged resource transfer transaction is used to instruct the blockchain node to determine the first signed resource transfer transaction through the public key corresponding to the data packaging private key; the first signed resource transfer transaction is used to instruct the blockchain node to determine the first resource transfer transaction through the public key corresponding to the first private key.

10. The method according to claim 8, wherein The step of sending the first resource transfer transaction to the blockchain node includes: Obtain a first resource transfer account address associated with the second account address; the first resource transfer account address includes N account addresses with resource transfer permissions associated with the second account address; N is a positive integer; Among the N account addresses, search for an account address that matches the first account address, and when an account address that matches the first account address is found, notify the first approval client corresponding to the first approval object associated with the second account address to authorize the first approval device of the first approval object to perform a transaction approval on the second resource transfer transaction through the second private key in the first approval device to obtain a first transaction approval information; When it is determined through the first transaction approval information that the transaction approval result of the second resource transfer transaction is transaction approval passed, generate a first transaction signature notification information for the second resource transfer transaction; Send the first transaction signature notification information to the resource client, so that the resource client authorizes the first hardware device of the business object to perform a transaction signature on the second resource transfer transaction through the second private key in the first hardware device to obtain the transaction signature information corresponding to the second resource transfer transaction; When receiving the transaction signature information, determine a second-signature resource transfer transaction based on the transaction signature information, and perform data packaging on the second-signature resource transfer transaction by using a data-packaging private key to obtain a second-packaged resource transfer transaction; Send the second-packaged resource transfer transaction to the blockchain node; the second-packaged resource transfer transaction is used to instruct the blockchain node to determine the second-signature resource transfer transaction by using the public key corresponding to the data-packaging private key; the second-signature resource transfer transaction is used to instruct the blockchain node to determine the second resource transfer transaction by using the public key corresponding to the transaction signature information.

11. The method according to claim 10, wherein The obtaining of the first resource transfer account address associated with the second account address includes: Generate an account address query request for the second account address; Send the account address query request to the blockchain node, so that the blockchain node queries, on the blockchain, the first resource transfer account address associated with the second account address; Receive the first resource transfer account address associated with the second account address returned by the blockchain node.

12. The method according to claim 10, wherein The method further includes: Receive a transfer address on-chain transaction for the second account address initiated by the service object through the resource client; the transfer address on-chain transaction includes the first account address; Notify the first approval client to authorize the first approval device to perform transaction approval on the transfer address on-chain transaction by using a second private key in the first approval device to obtain on-chain transaction approval information; When determining, through the on-chain transaction approval information, that the transaction approval result of the transfer address on-chain transaction is transaction approval passed, generate on-chain transaction signature notification information for the transfer address on-chain transaction; Send the on-chain transaction signature notification information to the resource client, so that the resource client authorizes the first hardware device to perform transaction signature on the transfer address on-chain transaction by using a second private key in the first hardware device to obtain on-chain transaction signature information corresponding to the transfer address on-chain transaction; When receiving the on-chain transaction signature information, determine a signature address transfer on-chain transaction based on the on-chain transaction signature information, and perform data packaging on the signature address transfer on-chain transaction by using the data-packaging private key to obtain a packaged address transfer on-chain transaction; Send the packaged address transfer on-chain transaction to the blockchain node, so that when the blockchain node obtains the transfer address on-chain transaction through the packaged address transfer on-chain transaction, add the first account address to the first resource transfer account address associated with the second account address based on the transfer address on-chain transaction.

13. The method according to claim 8, wherein The account address in the resource client further includes a third account address; the third account address is used to store the third-level resources of the service object; the address level of the second account address is lower than that of the third account address; the blockchain node is used to compare the resource amount of the second-level resources and the resource amount of the supplementary resources when obtaining the second resource transfer transaction, and generate reference cross-level transfer information when detecting that the resource amount of the second-level resources is less than the resource amount of the supplementary resources; The reference cross-level transfer information is used to instruct the service object to transfer the service resources in the third account address to the second account address across levels; The method further includes: When receiving the reference cross-level transfer information, returning the reference cross-level transfer information to the resource client, so that the resource client displays the third interface corresponding to the third account address in response to the address confirmation operation of the service object for the third account address in the reference cross-level transfer information, and generates a third resource transfer transaction in response to the resource transfer operation of the reference supplementary resources on the third interface; When receiving the third resource transfer transaction, sending the third resource transfer transaction to the blockchain node, so that the blockchain node generates reference resource update information when transferring the reference supplementary resources in the third-level resources from the third account address to the second account address and updating the second-level resources based on the reference supplementary resources; the reference supplementary resources are determined based on the resource difference between the second-level resources and the supplementary resources; Receiving the reference resource update information and returning the reference resource update information to the resource client, so that the resource client resends the second resource transfer transaction when determining that the resource amount of the updated second-level resources reaches the resource amount of the supplementary resources based on the reference resource update information; When receiving the second resource transfer transaction, sending the second resource transfer transaction to the blockchain node, so that the blockchain node transfers the supplementary resources from the second account address to the first account address.

14. The method according to claim 13, characterized in that, The sending the third resource transfer transaction to the blockchain node includes: Obtaining a second resource transfer account address associated with the third account address; the second resource transfer account address includes M account addresses with resource transfer permissions associated with the third account address; M is a positive integer; Among the M account addresses, search for the account address that matches the second account address, and when the account address that matches the second account address is found, notify the second approval client corresponding to the second approval object associated with the third account address. When it is determined that the local trusted execution environment of the second approval device of the second approval object belongs to a secure execution environment, approve the third resource transfer transaction through the third private key determined by the local trusted execution environment of the second approval device, and obtain the first transaction signature shard for the third resource transfer transaction; When it is determined that the number of shards of the first transaction signature shard reaches the shard number threshold, generate the second transaction signature notification information for the third resource transfer transaction; Send the second transaction signature notification information to the resource client, so that when the resource client determines that the local trusted execution environment of the second hardware device of the business object belongs to the secure execution environment, sign the third resource transfer transaction through the third private key determined by the local trusted execution environment of the second hardware device, and obtain the second transaction signature shard for the third resource transfer transaction; When receiving the second transaction signature shard, when determining the third signed resource transfer transaction based on the first transaction signature shard and the second transaction signature shard, pack the third signed resource transfer transaction through the data packing private key to obtain the third packed resource transfer transaction, and send the third packed resource transfer transaction to the blockchain node; the third packed resource transfer transaction is used to instruct the blockchain node to determine the third signed resource transfer transaction through the public key corresponding to the data packing private key; the third signed resource transfer transaction is used to instruct the blockchain node to determine the third resource transfer transaction through the public keys corresponding to the first transaction signature shard and the second transaction signature shard.

15. A resource processing device, characterized in that, The device runs on the resource client; the account addresses in the resource client include the first account address and the second account address; the first account address is used to store the first-level resources of the business object; The second account address is used to store the second-level resources of the business object; The address level of the first account address is lower than the address level of the second account address; The device includes: An interface output module, configured to display the first account address and the second account address on the address display interface of the resource client, and output the first interface corresponding to the first account address in response to the selection operation of the business object for the first account address; The first transaction processing module is configured to generate a first resource transfer transaction in response to a resource transfer operation of the business object for a target resource on the first interface, and send the first resource transfer transaction to a blockchain node through a resource server corresponding to the resource client, so that when the blockchain node detects that the resource amount of the first-level resource is less than the resource amount of the target resource, it generates cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer business resources in the second account address across levels to the first account address; The interface output module is further configured to receive the cross-level transfer information, and display a second interface corresponding to the second account address in response to an address confirmation operation of the business object for the second account address in the cross-level transfer information; The second transaction processing module is configured to generate a second resource transfer transaction in response to a resource transfer operation of the business object for supplementary resources on the second interface, and send the second resource transfer transaction to the blockchain node through the resource server, so that when the blockchain node transfers the supplementary resources in the second-level resources from the second account address to the first account address and updates the first-level resources based on the supplementary resources, it generates resource update information; the supplementary resources are determined based on the resource difference between the first-level resources and the target resources; The first transaction processing module is further configured to receive the resource update information, and when it is determined based on the resource update information that the resource amount of the updated first-level resources reaches the resource amount of the target resources, send the first resource transfer transaction to the blockchain node through the resource server, so that the blockchain node transfers the target resources from the first account address to the target account address indicated by the first resource transfer transaction.

16. A resource processing device, characterized in that, The device runs on a resource server corresponding to the resource client; the account addresses in the resource client include a first account address and a second account address; the first account address is used to store the first-level resources of the business object; The second account address is used to store the second-level resources of the business object; The address level of the first account address is lower than the address level of the second account address; the device includes: The first transaction sending module is configured to, when receiving the first resource transfer transaction sent by the resource client, send the first resource transfer transaction to the blockchain node, so that when the blockchain node detects that the resource amount of the first-level resource is less than the resource amount of the target resource indicated by the first resource transfer transaction, generate cross-level transfer information; the cross-level transfer information is used to instruct the business object to transfer the business resources in the second account address across levels to the first account address; the first resource transfer transaction is generated by the resource client in response to a resource transfer operation of the target resource on the first interface of the first account address by the business object; the first interface is output on the address display interface of the resource client when the first account address and the second account address are displayed and in response to a selection operation of the first account address by the business object. The information sending module is configured to, when receiving the cross-level transfer information, send the cross-level transfer information to the resource client, so that when the resource client responds to an address confirmation operation of the second account address in the cross-level transfer information by the business object, display a second interface corresponding to the second account address, and in response to a resource transfer operation of supplementary resources on the second interface by the business object, generate a second resource transfer transaction. The second transaction sending module is configured to, when receiving the second resource transfer transaction, send the second resource transfer transaction to the blockchain node, so that when the blockchain node transfers the supplementary resources in the second-level resource from the second account address to the first account address and updates the first-level resource based on the supplementary resources, generate resource update information; the supplementary resources are determined based on the resource difference between the first-level resource and the target resource. The information sending module is further configured to, when receiving the resource update information, send the resource update information to the resource client, so that when the resource client determines that the resource amount of the updated first-level resource reaches the resource amount of the target resource based on the resource update information, send the first resource transfer transaction to the resource server. The first transaction sending module is further configured to, when receiving the first resource transfer transaction, send the first resource transfer transaction to the blockchain node, so that the blockchain node transfers the target resource from the first account address to the target account address indicated by the first resource transfer transaction.

17. A computer device, characterized in that, It includes a memory and a processor. The memory is connected to the processor. The memory is used to store a computer program, and the processor is used to call the computer program to enable the computer device to execute the method according to any one of claims 1-14.

18. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, and the computer program is suitable for being loaded and executed by the processor to enable the computer device with the processor to execute the method according to any one of claims 1-14.

19. A computer program product, characterized in that, Comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-14.

Images