Data processing method and device based on block chain, equipment and medium

Abstract

The invention provides a data processing method and device based on a block chain, equipment and a medium, and the method comprises the steps: obtaining a receiving transaction, writing the receiving transaction into a digital collection contract, and calling the digital collection contract to generate a generation request for generating a digital collection when an authentication contract is called to authenticate first object identification information successfully; when a digital collection is generated based on the generation request, deploying an account contract on the block chain, configuring an account management relationship between the account contract and the first object identification information, and storing the digital collection in the account contract; and an account management transaction is received, when the account contract is called to execute the account authorization transaction, the second business object is configured as an account sharing role for the account contract through the role management contract, and an account sharing management relationship between the account contract and the second object identification information of the second business object is configured based on the account sharing role. According to the invention, the association degree of account management can be improved through an on-chain account authorization mode.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a blockchain-based data processing method, apparatus, device, and medium. Background Art

[0002] Due to the decentralized and tamper-proof nature of blockchain technology, it can digitize off-chain assets on the blockchain. For example, a user (e.g., User U) can use a smart contract to issue an off-chain asset as a unique digital asset (e.g., Asset A) on the blockchain. In this case, only User U owns, operates, and manages Asset A.

[0003] In practice, the inventors have discovered that when business scenarios are complex, simply having a single user (e.g., User U) operate and manage Asset A cannot meet the actual needs of such complex business scenarios. Therefore, how to authorize multiple users to jointly manage the on-chain account, thereby meeting the needs of actual business scenarios, has become an urgent problem to be solved. Summary of the Invention

[0004] The embodiments of the present application provide a blockchain-based data processing method, apparatus, device, and medium, which can improve the relevance of account management through on-chain account authorization.

[0005] On one hand, an embodiment of the present application provides a data processing method based on a blockchain. An authentication contract and a digital collection contract associated with the authentication contract are deployed on the blockchain. The method is executed by a consensus node. The authentication contract and the digital collection contract are running on the consensus node. The method includes:

[0006] Obtaining a claim transaction sent by the first resource client for claiming the digital collection;

[0007] Writing the claim transaction into the digital collection contract used to generate the digital collection, calling the authentication contract through the digital collection contract, performing information authentication on the first object identification information of the first business object in the claim transaction, and when the information authentication is successful, calling the digital collection contract to generate a generation request for generating the digital collection;

[0008] When generating a digital collectible based on the generation request, deploying an account contract associated with the digital collectible on the blockchain, configuring an account management relationship between the account contract and the first object identification information, and storing the digital collectible in the account contract; the account management relationship is used to indicate that the first business object has account management authority over the digital collectible in the account contract;

[0009] Receiving an account management transaction sent by the first resource client; the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share account management authority for the account contract;

[0010] When calling the account contract to execute the account authorization transaction, the role management contract associated with the account contract is called, and the second business object is configured as an account sharing role for the account contract through the role management contract. Based on the account sharing role, the account sharing management relationship between the account contract and the second object identification information of the second business object is configured, and the account sharing management relationship is used as the first transaction execution result of the account authorization transaction; the first transaction execution result is used to indicate that the first business object has authorized the second business object to share the account management authority for the account contract.

[0011] In one aspect, an embodiment of the present application provides a data processing device based on a blockchain. An authentication contract and a digital collection contract associated with the authentication contract are deployed on the blockchain. The device runs on a consensus node. The consensus node runs the authentication contract and the digital collection contract. The device includes:

[0012] A first acquisition module is used to acquire a redemption transaction sent by a first resource client for redeeming a digital collection;

[0013] a request generation module, configured to write a claim transaction into a digital collection contract used to generate a digital collection, invoke an authentication contract through the digital collection contract, perform information authentication on the first object identification information of the first business object in the claim transaction, and upon successful information authentication, invoke the digital collection contract to generate a generation request for generating the digital collection;

[0014] A contract deployment module, configured to deploy an account contract associated with the digital artifact on the blockchain when generating the digital artifact based on the generation request, configure an account management relationship between the account contract and the first object identification information, and store the digital artifact in the account contract; the account management relationship is used to indicate that the first business object has account management authority over the digital artifact in the account contract;

[0015] A first receiving module is configured to receive an account management transaction sent by a first resource client; the account management transaction includes an account authorization transaction for instructing a first business object to authorize a second business object to share account management authority for an account contract;

[0016] The role configuration module is used to call the role management contract associated with the account contract when calling the account contract to execute the account authorization transaction, configure the second business object as an account sharing role for the account contract through the role management contract, configure the account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and use the account sharing management relationship as the first transaction execution result of the account authorization transaction; the first transaction execution result is used to indicate that the first business object has authorized the second business object to share the account management authority for the account contract.

[0017] In one aspect, an embodiment of the present application provides a data processing device based on a blockchain. An authentication contract and a digital collection contract associated with the authentication contract are deployed on the blockchain. The device runs on a first resource client and includes:

[0018] A first transaction sending module, configured to send a claim transaction for claiming a digital collection to a consensus node;

[0019] The second transaction sending module is used to send an account management transaction to the consensus node; the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; the account contract is deployed on the blockchain when the consensus node generates a digital collection based on a generation request; the generation request is generated when the consensus node calls the authentication contract through the digital collection contract to authenticate the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, it calls the digital collection contract to generate.

[0020] In one aspect, an embodiment of the present application provides a computer device, including a memory and a processor, wherein 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.

[0021] On one hand, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. 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.

[0022] According to one aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method provided in the above aspect.

[0023] In an embodiment of the present application, the consensus node can obtain the claim transaction sent by the first resource client; further, the consensus node can write the claim transaction into the digital collection contract, call the authentication contract through the digital collection contract, perform information authentication on the first object identification information of the first business object in the claim transaction, and when the information authentication is successful, call the digital collection contract to generate a generation request for generating the digital collection; further, when the consensus node generates the digital collection based on the generation request, it can deploy an account contract associated with the digital collection on the blockchain, configure the account management relationship between the account contract and the first object identification information, and store the digital collection in the account contract; it should be understood that the account management relationship is used to indicate that the first business object has account management authority over the digital collection in the account contract. This means that by deploying the account contract and storing the digital collection in the account contract, the digital collection has an independent account that can store business assets. In addition, the consensus node can receive the account management transaction sent by the first resource client; it should be understood that the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; further, the consensus node can call the role management contract associated with the account contract when calling the account contract to execute the account authorization transaction, and configure the second business object as an account sharing role for the account contract through the role management contract, and configure the account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and use the account sharing management relationship as the first transaction execution result of the account authorization transaction; it should be understood that the first transaction execution result is used to characterize that the first business object has authorized the second business object to share the account management authority for the account contract. This means that by configuring the second business object as an account sharing role for the account contract, the second business object has the account management authority for the account contract, so that multiple business objects can manage the account contract. It can be seen that the embodiment of the present application can improve the correlation of account management through on-chain account authorization. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0025] Figure 1 This is a schematic diagram of the structure of a blockchain network architecture provided by an embodiment of the present application;

[0026] Figure 2This is a schematic diagram of a data interaction scenario provided by an embodiment of the present application;

[0027] Figure 3 This is a schematic diagram of a protocol standard involving digital assets in a blockchain provided by an embodiment of the present application;

[0028] Figure 4 This is a flowchart of a blockchain-based data processing method provided in an embodiment of the present application;

[0029] Figure 5 This is a schematic diagram of information authentication for a business object provided by an embodiment of the present application;

[0030] Figure 6 This is a schematic diagram of a consensus node obtaining and adding registration address information provided by an embodiment of the present application;

[0031] Figure 7 This is a schematic diagram of another consensus node obtaining and adding registration address information provided by an embodiment of the present application;

[0032] Figure 8 This is a schematic diagram of obtaining a target authentication information list provided by an embodiment of the present application;

[0033] Figure 9 This is a schematic diagram of configuring an account sharing role for a second business object provided by an embodiment of the present application;

[0034] Figure 10 This is a flowchart of configuring an asset operation management relationship for a second business object provided by an embodiment of the present application;

[0035] Figure 11 This is a schematic diagram of a scenario for configuring an asset operation management relationship for a second business object provided by an embodiment of the present application;

[0036] Figure 12 This is a flowchart of another blockchain-based data processing method provided in an embodiment of the present application;

[0037] Figure 13 This is an interactive diagram of a blockchain-based data processing method provided in an embodiment of the present application;

[0038] Figure 14 This is a schematic diagram of the structure of a blockchain-based data processing device provided in an embodiment of the present application;

[0039] Figure 15 This is a structural diagram of another blockchain-based data processing device provided in an embodiment of the present application;

[0040] Figure 16This is a schematic diagram of the structure of a computer device provided in an embodiment of the present application;

[0041] Figure 17 It is a structural diagram of a data processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0043] See Figure 1 , Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application. The network architecture may include a terminal device cluster and a blockchain network. Figure 1 As shown, the terminal device cluster here can be as follows Figure 1 The terminal device cluster A10 shown in the figure, the blockchain network here can be as follows Figure 1 The consensus network A11 is shown.

[0044] Among them, it is understandable that Figure 1 The terminal device cluster A10 shown may include one or more terminal devices, and the number of terminal devices in the terminal device cluster A10 is not limited here. Figure 1 As shown, the multiple terminal devices may specifically include terminal device 10a, terminal device 10b, ..., terminal device 10n, etc. The terminal devices in terminal device cluster A10 (for example, terminal device 10a) may include: smart phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices (for example, smart watches, smart bracelets, etc.), smart voice interaction devices, smart home appliances (for example, smart TVs, etc.), and in-vehicle devices, etc.

[0045] It should be understood that Figure 1A resource client, also called a resource management client, can be run in any terminal device in the terminal device cluster A10 shown (for example, terminal device 10a). A resource client can be a tool for managing digital collections, and can be used to send transactions initiated by business objects (for example, a transaction to collect digital collections) to the consensus node in the above-mentioned consensus network A11, so that the consensus node can complete the operation indicated by the collection transaction. It should be understood that the resource client can be a hardware device or a software program. It is understandable that one or more resource clients can be run in a terminal device, and there is no limit on the number of resource clients running in a terminal device. It is understandable that the same business object can correspond to one or more resource clients, and multiple resource clients corresponding to the same business object can run on the same terminal device or on different terminal devices, and there is no limit here.

[0046] It should be understood that Figure 1 In the consensus network A11 shown, multiple consensus nodes are deployed, and there is no limit on the number of consensus nodes. Figure 1 As shown, the multiple consensus nodes may specifically include consensus node 11a, consensus node 11b, consensus node 11c, ..., consensus node 11n. In addition, as Figure 1 As shown, for multiple consensus nodes running in the consensus network A11, the blockchain they jointly maintain is specifically Figure 1 Blockchain 12e is shown.

[0047] It can be understood that the method provided in the embodiment of the present application can be executed by a computer device, including but not limited to a terminal or a server. The consensus node 11a, consensus node 11b, consensus node 11c, ..., consensus node 11n in the embodiment of the present application can be a computer device. The above-mentioned server can be an independent physical server or a server cluster or distributed system composed of multiple physical servers. It can also be 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, and big data and artificial intelligence platforms. Figure 1 As shown, consensus node 11a, consensus node 11b, consensus node 11c, ..., consensus node 11n can respectively establish network connections with consensus network A11.

[0048] like Figure 1As shown, a terminal device in the terminal device cluster A10 (e.g., terminal device 10a) can establish a network connection with consensus nodes such as consensus node 11a, consensus node 11b, and consensus node 11c, so that when the terminal device in the terminal device cluster A10 is connected to the consensus network A11, data can be exchanged with the consensus nodes in the consensus network A11. For example, terminal device 10a can serve as a business terminal, and the business object can send a data query request to the blockchain network through the business terminal. The consensus node in the blockchain network can then determine the request result based on the data query request and return the request result to the corresponding business terminal.

[0049] It should be understood that the blockchain involved in the embodiments of the present application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm. It is mainly used to organize data in chronological order and encrypt it into a ledger to make it tamper-proof and forged, and to verify, store, and update data. The blockchain is essentially a decentralized database, a string of data blocks generated using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of the information (anti-counterfeiting) and generate the next block. The blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer. The blockchain includes a series of blocks that are connected to each other in the order of their generation. The blocks record the block data packaged and submitted by the blockchain nodes in the blockchain system. The blockchain underlying platform can include processing modules such as object management, basic services, smart contracts, and operation management. Among them, the object management module is responsible for the identity information management of all blockchain participants, including maintaining public and private key generation (account management), key management, and maintaining the corresponding relationship between the user's real identity and blockchain address (authority management), etc., and under authorization, it supervises and audits the transactions of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and records the valid requests to the storage after reaching consensus. For a new business request, the basic service first adapts the interface to parse and authenticate the request (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management). The smart contract module is responsible for contract registration, issuance, triggering, and execution. Developers can define contract logic in a programming language and publish it to the blockchain (contract registration). Based on the contract terms, they can trigger execution by invoking keys or other events to complete the contract logic. It also provides contract upgrade and cancellation capabilities. The operations management module is primarily responsible for product deployment, configuration modifications, contract settings, cloud adaptation, and real-time visualization of product status during operation, such as alarms, network management, and node device health. The platform's product service layer provides the basic capabilities and implementation framework for typical applications. Developers can build on these capabilities and overlay business features to complete the blockchain implementation of business logic. The application service layer provides blockchain-based application services for business participants.

[0050] It is understood that one or more smart contracts (also referred to as contracts) can be deployed on the blockchain (e.g., blockchain 12e) of the consensus network (e.g., consensus network A11). In a blockchain system, a smart contract can be understood as a code that can be understood and executed by each blockchain node (e.g., consensus node), capable of executing arbitrary logic and producing results. A smart contract is a computer protocol that digitally facilitates, verifies, or enforces the negotiation or performance of a contract. It is a piece of code written on the blockchain. Once an event triggers the terms of the contract, the code automatically executes, that is, it executes when the conditions are met, without the need for human intervention. Smart contracts can be used to automate the execution of agreements, ensuring that all participants can immediately determine the outcome without the involvement of any intermediaries or wasted time. For example, an entity (e.g., a user requesting a transaction) can invoke a smart contract deployed on the blockchain by initiating a transaction request through a client on their terminal.

[0051] It should be understood that these smart contracts can be distinguished by contract identifiers (such as identification numbers (ID) or names, and can also include contract addresses or contract function names (also known as contract method names)), and the transaction service request initiated by the client can also carry the identification number or name of the smart contract to specify the smart contract that the blockchain needs to run. In an embodiment of the present application, the smart contract deployed on the blockchain can include an authentication contract. The authentication contract can be a contract used for real-name authentication, for example, a contract for real-name authentication of the real-name authentication information for the business object sent by the resource management client.

[0052] It is understandable that in order to enable digital collections to have an independent account for storing assets (for example, a digital collection account), and in order to better manage the permissions and assets corresponding to the digital collection account and meet the diversification of business scenarios, the embodiment of the present application provides a novel account authorization method, which configures a corresponding account for the smart contract (for example, an account contract), stores the digital collection in the account contract, and enables the digital collection to have an independent account for storing assets. In addition, the account sharing role for the account contract is configured using a smart contract (for example, a role management contract), so that multiple business objects can manage and operate the business assets in the account contract, thereby enriching the business scenario. Among them, the digital collections in the embodiment of the present application can be used to represent unique and irreplaceable items, including but not limited to game resources (such as props, equipment, skins, etc. in electronic games), digital artworks, such as digital music / video collections, and various virtual assets (such as virtual real estate, virtual creative goods, virtual identities, etc.). Digital collections are created based on blockchain technology. Each digital collection can have its own unique identifier (such as the ID of the digital collection, which can be generated through the generation rules specified in the blockchain protocol standard) and metadata. These metadata may include ownership, author, creation time and other details. Therefore, each digital collection is unique and cannot be replaced or exchanged.

[0053] Among them, to facilitate subsequent understanding and explanation, the embodiment of the present application may collectively refer to entity objects (such as individual users, corporate users, institutions, etc.) that send business transactions to consensus nodes in the consensus network as business objects. Furthermore, in the asset management scenario, for ease of distinction, the business object that initiates the account management transaction (for example, user 1) may be referred to as the first business object, and correspondingly, the business object that initiates an asset operation request to the account contract (for example, user 2) may be referred to as the second business object. It can be understood that the embodiment of the present application may refer to the terminal device associated with the first business object as the first terminal, and the resource client installed on the first terminal for initiating business transactions as the first resource client, and the background server corresponding to the first resource client as the resource service terminal. Similarly, the terminal device associated with the second business object may be referred to as the second terminal, and the resource client installed on the second terminal for initiating asset operation requests may be referred to as the second resource client.

[0054] Next, see Figure 2 , Figure 2 This is a schematic diagram of a data interaction scenario provided by an embodiment of the present application. Figure 2 As shown, the terminal device 20a can be the above Figure 1For any terminal device in the terminal device cluster in the corresponding embodiment (such as the above-mentioned terminal device 10a, terminal device 10b, etc.), it can be understood that the business object a1 can correspond to the above-mentioned first business object, and a resource client is running on the terminal device 20a. For ease of understanding, the embodiment of the present application can refer to the resource client corresponding to the first business object (for example, business object a1) as the first resource client. In addition, the consensus node 20b can be the above-mentioned Figure 1 Any consensus node in the consensus network in the corresponding embodiment (such as the above consensus node 11a, consensus node 11b, etc.), the blockchain 20e here can correspond to the above Figure 1 Blockchain 12e is shown.

[0055] It is understandable that a smart contract is deployed on the blockchain 20e, which includes a digital collection contract 200a and a certification contract 200b. Figure 2 As shown, the digital collection contract 200a and authentication contract 200b are run on consensus node 20b. Specifically, the digital collection contract 200a can be used to generate digital collections, and the authentication contract 200b can be used to authenticate the business object that initiates a transaction request to consensus node 20b.

[0056] like Figure 2 As shown, business object a1 (i.e., the first business object) can send transaction TX1 to consensus node 20b through the first resource client (step S21). Among them, the transaction parameters in the transaction TX1 carry identification information associated with business object a1. This identification information can be used to verify the information of business object a1. For example, the identification information is the registration address information of business object a1, the contract address of the contract called by transaction TX1, and so on. Among them, for ease of understanding, the embodiment of the present application refers to the identification information associated with business object a1 (i.e., the first business object) as the first object identification information. Further, consensus node 20b authenticates the first object identification information 21a through authentication contract 200b (step S22). For example, consensus node 20b can call authentication contract 200b, and search for information that matches the first object identification information 21a in the authentication information list stored in authentication contract 200b. If information that matches the first object identification information 21a is found in the authentication information list, the authentication is successful.

[0057] Furthermore, the consensus node 20b can obtain (i.e., generate) a generation request 22a (step S23) through the digital collection contract 200a. It is understandable that the generation request 22a is used to generate a digital collection. Furthermore, the consensus node 20b generates the digital collection 22b based on the generation request 22a. Specifically, the consensus node 20b can generate the digital collection 22b based on the generation request 22a through the digital collection contract 200a. It is understandable that the request parameters of the generation request 22a include parameters for indicating the generation of a specific type of digital collection. For example, if the request parameters of the generation request 22a include parameters for indicating the generation of an electronic invoice, then the digital collection generated at this time is an electronic invoice; for another example, if the request parameters of the generation request 22a include parameters for indicating the generation of a game skin, then the digital collection generated at this time is a game skin.

[0058] Furthermore, when consensus node 20b generates a digital collectible based on generation request 22a, it deploys account contract 200c on the blockchain (e.g., blockchain 20e) (step S24). It should be understood that the digital collectibles here can be the aforementioned electronic receipts, game skins, and so on. Furthermore, account contract 200c is deployed in real time. When a new digital collectible is generated, a new account contract is deployed in real time, i.e., one account contract corresponds to one digital collectible. Furthermore, consensus node 20b configures an account management relationship between account contract 200c and first object identification information 21a, and stores digital collectible 22b in account contract 200c (step S25). This account management relationship indicates that business object a1 (i.e., the first business object) has account management authority over digital collectible 22b in account contract 200c. For example, business object a1 can initiate an asset transfer operation on the business assets in digital collectible 22b.

[0059] In addition, business object a1 (i.e., the first business object) can send transaction TX2 to consensus node 20b through the first resource client (step S26). Consensus node 20b receives transaction TX2 and calls account contract 200c to execute transaction TX2 (step S27), wherein transaction TX2 here is used to instruct business object a1 to authorize the second business object (for example, business object A) to share account management permissions for account contract 200c. Consensus node 20b configures the account sharing role by calling the role management contract associated with account contract 200c (step S28). Specifically, the role management contract here is deployed at the same time as the account contract 200c and can be regarded as part of the account contract 200c. In the embodiment of the present application, in order to facilitate distinction and understanding, the role management contract and the account contract 200c are processed separately. In addition, the above-mentioned account sharing role refers to the role that operates on the account contract 200c, and the specific operation here is determined by the first business object. Furthermore, consensus node 20b configures an account sharing management relationship between account contract 200c and second object identification information 21b (step S29). It should be understood that second object identification information 21b may specifically include, but is not limited to, the registered address information of the second business object. Furthermore, the account sharing management relationship includes, but is not limited to, business object a1 (i.e., the first business object) sharing the second business object's account management permissions for account contract 200c. Account management permissions may include, but are not limited to, the second business object being able to further authorize permissions in account contract 200c, such as the second business object authorizing a third business object to transfer business assets in account contract 200c. Furthermore, consensus node 20b obtains a transaction execution result based on the aforementioned account sharing roles and account sharing management relationship (step S30).

[0060] It should be noted that before collecting the relevant data of a business object (such as the first business object mentioned above) (for example, the registration information of the first business object) and during the process of collecting the relevant data of the business object, this application can display a prompt interface, pop-up window or output a voice prompt message. The prompt interface, pop-up window or voice prompt message is used to remind the user that its relevant data is currently being collected, so that this application only starts to execute the relevant steps of obtaining the user's relevant data after obtaining the user's confirmation operation on the prompt interface or pop-up window. Otherwise (that is, when the user's confirmation operation on the prompt interface or pop-up window is not obtained), the relevant steps of obtaining the user's relevant data are terminated, that is, the user's relevant data is not obtained. In other words, all user data collected by this application are collected with the user's consent and authorization, and the collection, use and processing of relevant user data need to comply with the relevant laws, regulations and standards of the relevant region.

[0061] It is understood that the above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0062] In the embodiments of this application, it mainly involves digital collections on the blockchain (or unique digital assets), and therefore involves the digital collection protocols used on the blockchain (for example, the ERC721 protocol standard and the ERC1155 protocol standard), which are also called digital collection contracts in the embodiments of this application.

[0063] See Figure 3 , Figure 3 This is a schematic diagram of a protocol standard involving digital assets in a blockchain provided by an embodiment of the present application. Figure 3 As shown, digital assets 301 may include first-type digital assets 302 and second-type digital assets 303. First-type digital assets 302 are non-unique digital assets that are divisible, computable, and fungible, and can be managed based on a preset first protocol standard. Second-type digital assets 303 are unique digital assets that are indivisible, non-fungible, and verifiable.

[0064] In addition, depending on whether the second type of digital assets are computable, they can be further divided into non-computable second type digital assets 304 and computable second type digital assets 305. Non-computable second type digital assets 304 can be managed based on a preset second protocol standard, and computable second type digital assets 305 can be managed based on a preset third protocol standard. The difference between the third protocol standard and the second protocol standard is that non-computable second type digital assets managed based on the second protocol standard can only exist in one copy on a blockchain, while computable second type digital assets managed based on the third protocol standard can exist in multiple copies on a blockchain at the same time. The digital asset transaction method provided in the embodiments of the present application can be applied to different protocol standards in various application scenarios.

[0065] Among them, the above-mentioned first protocol standard refers to the ERC20 standard, the second protocol standard refers to the ERC721 protocol standard, and the third protocol standard refers to the ERC1155 standard.

[0066] Next, we will introduce the main interfaces involved in the ERC-721 protocol standard and the ERC-1155 protocol standard respectively:

[0067] (1) Main interfaces of the ERC-721 protocol standard:

[0068] ERC721: Main contract interface; for example, in the embodiment of the present application, when generating a digital collection, the main contract interface can be called to generate the digital collection (for example, the above Figure 2 In the corresponding embodiment, a digital collection 22b) is generated.

[0069] ERC721Enumerable: Enumeration data query interface, mainly used to count all digital collections in the contract, and to which account each digital collection belongs; for example, in the embodiment of the present application, the consensus node can query and traverse the generated digital collections (for example, the above example) by calling the enumeration data query interface. Figure 2 The digital collection shown is 22b).

[0070] ERC721Receiver: callback implementation interface, mainly used to verify the recipient's contract address to avoid "dead accounts"; for example, in an embodiment of the present application, assuming that the first business object wants to transfer the business assets in the account contract to the second business object, it is necessary to call the callback implementation interface to verify the recipient's contract address (that is, the address of the second business object). Only when the verification is successful can the asset transfer be successfully performed.

[0071] ERC721MetaData: Main contract metadata interface (name, symbol, tokenURI); "name" is used to return the name of the digital artifact, "symbol" is used to return the identifier of the digital artifact, and "tokenURI" is used to return the metadata URI associated with the given digital artifact. In this embodiment of the present application, the first business object can obtain the name, identifier, and associated metadata URI of the generated digital artifact (e.g., the aforementioned digital artifact 22b) through this main contract metadata interface.

[0072] ERC721Pausable: Contract suspension interface; for example, in the embodiment of the present application, when generating digital collections (for example, the above Figure 2 When the digital collection 22b is displayed, the generation of the digital collection can be stopped by calling the contract pause interface.

[0073] ERC721Burnable: Warrant destruction interface; the warrant here may refer to a digital collection (for example, the above-mentioned digital collection 22b). In the embodiment of the present application, the generated digital collection can be destroyed by calling the warrant destruction interface, that is, the digital collection is permanently deleted under the corresponding account address.

[0074] ERC721URIStorage: tokenURI storage interface refers to the interface for storing the metadata URI associated with the digital collection. However, in the embodiment of the present application, the metadata URI associated with the digital collection is stored in the account contract deployed in real time (for example, the above Figure 2 Account contract 220c).

[0075] ERC721PresetMinterPauserAutoId: The contract owner authorizes the Minter (maker) and Pauser (pauser) interfaces; in this embodiment of the application, "Minter (maker)" refers to the first business object, that is, the role responsible for generating digital collections; "Pauser (pauser)" refers to the role that has the right to suspend asset transfers.

[0076] ERC721Holder: The default implementation interface of ERC721Receiver, used to receive any digital collection.

[0077] (2) Main interfaces of the ERC-1155 protocol standard:

[0078] ERC1155: Main contract interface; for example, in the embodiment of the present application, when generating digital collections, the main contract interface can be called to generate digital collections (for example, the above Figure 2 In the corresponding embodiment, digital collectibles are generated 22b). Unlike the above-mentioned ERC721, one off-chain digital asset can be issued as multiple digital collectibles on the chain.

[0079] ERC1155MetadataURI: A primary contract metadata URI (Uniform Resource Identifier, URI) interface; used to retrieve metadata URIs associated with digital artifacts. In this embodiment, the first business object can retrieve metadata URIs for multiple generated digital artifacts (e.g., digital artifact 22b ) using this primary contract metadata URI interface.

[0080] ERC1155Receiver: Receiver callback implementation interface, used to verify the receiving account address to avoid "dead accounts"; similar to the above-mentioned ERC72 Receiver 1, for example, in an embodiment of the present application, assuming that the first business object wants to transfer the business assets in the account contract to the second business object, it is necessary to call the callback implementation interface to verify the recipient's contract address (that is, the address of the second business object). Only when the verification is successful can the asset transfer be successfully performed.

[0081] ERC1155Pausable: Contract Pause Interface; similar to ERC721 Pausable, for example, in the embodiment of this application, when generating digital collections (for example, the above Figure 2 When the digital collection 22b is displayed, the generation of the digital collection can be stopped by calling the contract pause interface.

[0082] ERC1155Burnable: Warrant destruction interface; the warrant here may refer to a digital collection (for example, the above-mentioned digital collection 22b). In the embodiment of the present application, the generated digital collection can be destroyed by calling the warrant destruction interface, that is, the digital collection is permanently deleted under the corresponding account address.

[0083] ERC1155Supply: The total supply data statistics interface for each digital collection; each digital collection generated under the ERC1155 protocol standard is unique, and this interface can count the total number of digital collections; for example, in the embodiment of this application, the generated digital collections (for example, the above Figure 2 The number of digital artifacts 22b) shown.

[0084] ERC1155PresetMinterPauserAutoId: The contract owner authorizes the Minter (maker) and Pauser (pauser) interfaces; in this embodiment of the application, "Minter (maker)" refers to the first business object, that is, the role responsible for generating digital collections; "Pauser (pauser)" refers to the role that has the right to suspend asset transfers.

[0085] Further, see Figure 4 , Figure 4 This is a flowchart of a data processing method based on blockchain provided by an embodiment of the present application. Figure 1 In the corresponding embodiment, any consensus node (for example, consensus node 11a) in the consensus network A11 executes the method, which may specifically include the following steps S101 to S105.

[0086] Step S101: obtaining a claim transaction sent by a first resource client for claiming a digital collection;

[0087] The first resource client is a resource client corresponding to the first business object, and the first business object may be an individual, an enterprise, an organization, and the like.

[0088] It can be understood that the collection transaction carries transaction parameters, which may include the transaction source address of the transaction, that is, the address of the business object sending the transaction (that is, the first business object), and may also include the destination address of the transaction, that is, the contract address of the smart contract to be called. Some additional parameters of the transaction may include data that needs to be passed when calling the smart contract, such as the specific call processing method required when calling the smart contract, other parameters required to be passed in when calling the smart contract, etc., which are not limited here.

[0089] Step S102: Write the claim transaction into the digital collection contract used to generate the digital collection. The digital collection contract calls the authentication contract to authenticate the first object identification information of the first business object in the claim transaction. When the authentication succeeds, the digital collection contract is called to generate a generation request for generating the digital collection.

[0090] Among them, the digital collection contract may include a variety of contract methods, which can be used to complete the operations indicated by the transaction sent by the first business object (for example, the above-mentioned collection transaction). For example, the contract method can be used to call other smart contract methods, such as a contract method for calling an authentication contract. It can be understood that the above-mentioned authentication contract specifically refers to a contract that can authenticate the information of the business object that initiates the transaction (for example, the above-mentioned business object a1). Generally speaking, the authentication contract stores the address information of multiple business objects. By querying whether there is address information that matches the business object a1 in the address information stored in the authentication contract, it can be determined whether the business object a1 is a legitimate business object, and then decide whether to execute the relevant transaction.

[0091] It is understood that the above-mentioned first object identification information refers to information associated with the identity information of the first business object. For example, it can be the relevant information submitted by the first business object during the information registration process before logging into the first resource client. For example, the registration process can include the phone number information, fingerprint information, facial information, ID card information, name information, etc. submitted by the first business object. The first object identification information can also include the registration address information generated by the backend service terminal corresponding to the first resource client when the first business object successfully registers. It is understood that when the first business object accesses the service through the first resource client, it will carry the access address information. At this time, the access address information is the registration address information of the first business object.

[0092] Specifically, the digital collection contract includes a first contract method and a second contract method; the first contract method refers to a first contract calling method for calling an authentication contract, and the second contract method refers to a request generation method for generating a request; the first object identification information includes the access address information used by the first business object when accessing the first resource client; then the first object identification information of the first business object is authenticated, and when the authentication is successful, a generation request is obtained (i.e., generated), which may include the following steps: the consensus node may obtain the first contract calling method from the digital collection contract, and call the authentication contract through the first contract calling method, thereby obtaining a target authentication information list maintained by the authentication contract; further, the consensus node may perform information authentication on the first object identification information of the first business object in the collection transaction based on the registered address information in the target authentication information list, thereby obtaining an information authentication result; it can be understood that when the information authentication result indicates that there is registered address information matching the access address information in the registered address information of at least one address registration object, the consensus node may generate an information authentication success result indicating that the information authentication is successful; thereby, the digital collection contract acquisition request generation method may be called based on the information authentication success result, and a generation request for generating a digital collection may be obtained through the request generation method.

[0093] The request generation method refers to the method for generating the digital collection. The access address information refers to the address information used by the first business object when logging into the first resource client and accessing the relevant data resources in the first resource client.

[0094] It can be understood that the target authentication information list refers to a list that stores the address information of the address registration object after registration on the corresponding resource client and information authentication. The target authentication information list stores the registration address information of at least one registration object, for example, the registration address information obtained when the above-mentioned first business object is registered on the first resource client.

[0095] In addition, it can be understood that information authentication is performed on the first object identification information of the first business object in the collection transaction to obtain an information authentication result, which can specifically include: the consensus node searches for address information that matches the access address information in the registered address information in the target authentication information list; if address information that matches the access address information is found in the registered address information, the search success result that matches the access address information is used as the information authentication result; if address information that matches the access address information is not found in the registered address information, the search failure result that does not match the access address information is used as the information authentication result.

[0096] It is understandable that if no address information matching the access address information is found, it is determined that the first business object information authentication has failed, and the consensus node will terminate subsequent operations.

[0097] See Figure 5 , Figure 5 This is a schematic diagram of information authentication for a business object provided by an embodiment of the present application. Figure 5 As shown, the terminal device 50a can correspond to the above Figure 2 In the corresponding embodiment, the terminal device 20a has a business object corresponding to the terminal device 50a, which is the business object a1, i.e. the first business object. In addition, a resource client, i.e. the first resource client, is running on the terminal device 50a. The consensus node 50b may correspond to the above Figure 2 The consensus node 20b in the corresponding embodiment.

[0098] like Figure 5 As shown, business object a1 (i.e., the first business object) sends transaction TX3 to the consensus node through the first resource client, wherein the transaction TX3 may correspond to the above-mentioned claim transaction. It should be understood that the transaction parameters in transaction TX3 include identification information associated with business object a1, i.e., the above-mentioned first object identification information, and the first object identification information includes the access address information x used by business object a1 when accessing the first resource client through terminal device 50a. Consensus node 50b obtains authentication information list 500a, i.e., the above-mentioned target authentication information list, by calling the authentication contract. As Figure 5 As shown, the authentication information list 500a (i.e., the target authentication information list) includes registration address information b1, registration address information b2, registration address information b3, registration address information b4, ..., registration address information bn, etc. It is understandable that the above-mentioned registration address information b1, registration address information b2, ..., registration address information bn are address information registered when different business objects log in to the corresponding resource client.

[0099] Furthermore, the consensus node 50b erases the passport access address information x in the authentication information list 500a, such as Figure 5 As shown, if the registration address information b2 is found to match the access address information x, then the consensus node 50b can determine that the business object a1 is a legal object, that is, the business object a1 information authentication is successful.

[0100] It should be understood that the target authentication information list stored in the above-mentioned authentication contract is obtained by updating the initial authentication information list. Before the consensus node obtains the transaction, the consensus node will also add the object identification information associated with the first business object after real-name authentication to the authentication contract, thereby determining that the first business object is an object that has undergone real-name authentication. Among them, the real-name authentication process is executed by the background service corresponding to the first resource client. For ease of understanding, the embodiment of this application refers to the first resource client as a resource service terminal.

[0101] There are two methods for the consensus node to obtain the identification information of the first business object after real-name authentication by the resource service terminal.

[0102] In an optional embodiment, the consensus node can directly obtain the information authentication transaction sent by the resource service terminal, thereby obtaining the identification information in the real-name authentication transaction. Specifically, the following steps may be included: the consensus node can obtain the information authentication transaction sent by the resource service terminal corresponding to the first resource client; further, the consensus node can obtain the authentication object identification information from the information authentication transaction, and use the first business object as the address registration object corresponding to the authentication object identification information, so that when the address registration object and the authentication object identification information are added to the initial authentication information list maintained by the authentication contract, the initial authentication information list with the added authentication object identification information is determined as the target authentication information list.

[0103] It should be understood that the transaction parameters of the information authentication transaction carry authentication object identification information after information authentication, and the authentication object identification information is obtained after the resource service terminal performs information authentication based on the first object identification information of the first business object; the first object identification information includes the business registration information submitted by the first business object on the registration business interface of the first resource client for information authentication;

[0104] Among them, the registration service interface may include but is not limited to information entry areas for obtaining the first business object's phone number information, fingerprint information, face information, home address information, hobby information, ID card information, name information, etc. Correspondingly, the service registration information at this time may include but is not limited to the first business object's phone number information, fingerprint information, face information, home address information, hobby information, ID card information, name information, etc. The above-mentioned first object identification information may include the first business object's phone number information, fingerprint information, ID card information, name information, etc. After the first business object registers information on the registration service interface, the first resource client will submit the information to the resource service terminal, so that the resource service terminal can authenticate the first object identification information to obtain the authenticated information (i.e., the authentication object identification information).

[0105] The first resource client packages the transaction based on the authentication object information, thereby obtaining an information authentication transaction. It then uses the private key information associated with the first business object to sign the information authentication transaction and sends it to the consensus node. At this point, the real-name authentication transaction carries the first signature information after the transaction is signed. The first signature information carries the public key information corresponding to the private key information. Therefore, when the consensus node receives the information authentication transaction, it can obtain the public key information carried in the information authentication transaction and then verify the signature using this public key information.

[0106] It can be understood that the above-mentioned initial authentication information list is a list without adding the object identification information of the first business object. For example, if the target authentication information list stores registration address information x1 and registration address information x2, and registration address information x2 is the registration address information of the first business object, then the address information stored in the initial target authentication information list only includes registration address information x1.

[0107] For details, see Figure 6 , Figure 6 This is a schematic diagram of a consensus node obtaining and adding registration address information provided by an embodiment of the present application. Figure 6 As shown, the terminal device 60a may correspond to the above Figure 2 In the corresponding embodiment, the terminal device 20a has a business object corresponding to the terminal device 60a, which is the business object a1, i.e., the first business object. In addition, a resource client, i.e., the first resource client, is running on the terminal device 60a. The resource service terminal 60b is the backend terminal of the first resource client. The consensus node 60c can correspond to the above Figure 2 The consensus node 20b in the corresponding embodiment.

[0108] like Figure 6 As shown, the business object a1 can log in to the first resource client through the terminal device 60a, and then register for the business on the registration business interface displayed on the first resource client, that is, enter the business registration information on the registration business interface. The business registration information here may include the relevant information described above (for example, name information, fingerprint information, etc.). After the entry is completed, the business object a1 clicks the submit information control to obtain the business registration information 600a.

[0109] Furthermore, business object a1 sends business registration information 600a to resource service terminal 60b via the first resource client (step S61). Resource service terminal 60b receives business registration information 600a and authenticates it, obtaining identification information 600b (step S62). The identification information 600b herein may correspond to the authentication object identification information described above. Specifically, resource service terminal 60b authenticates the information carried in business registration information 600a (e.g., fingerprint information, name information, etc.), and then configures a registration address for the first business object, obtaining registration address information. The registration address information is packaged as identification information 600b (i.e., authentication object identification information) in a transaction, resulting in transaction TX4. Transaction TX4 herein may be used to authenticate a transaction using the aforementioned information.

[0110] Furthermore, the resource service terminal 60b sends the transaction TX4 (i.e., the information authentication transaction) to the consensus node 60c (step S63). The consensus node 60c receives the transaction TX4, first performs transaction verification on the transaction TX4, and then obtains the identification information 600b in the transaction TX4. Figure 6 As shown, the consensus node 60c obtains the identification information 600b from the transaction TX4 and adds the identification information 600b to the list (step S64).

[0111] In another optional embodiment, the consensus node can obtain a first authentication transaction sent by a resource service terminal corresponding to the first resource client; further, the consensus node can call the authentication contract to execute the first authentication transaction, thereby obtaining authentication event information associated with the first object identification information, so that when the resource service terminal detects the authentication event information, it performs information authentication on the first object identification information contained in the authentication event information, and sends a second authentication transaction to the consensus node; further, the consensus node can receive the second authentication transaction sent by the resource service terminal; and then can obtain the authentication object identification information from the second authentication transaction, use the first business object as the address registration object corresponding to the authentication object identification information, and when adding the address registration object and the authentication address information to the initial authentication information list maintained by the authentication contract, the initial authentication information list with the added authentication object identification information can be determined as the target authentication information list.

[0112] It should be understood that the transaction parameters of the first authentication transaction carry the first object identification information of the first business object; the first object identification information includes the business registration information submitted by the first business object on the registration business interface of the first resource client for information authentication. A detailed description of the registration business interface, business registration information, and first object identification information can be found in the above description and will not be repeated here.

[0113] In addition, the transaction parameters of the second authentication transaction carry the authentication object identification information after information authentication. The authentication object identification information is obtained by the resource service terminal after information authentication based on the first object identification information. Information authentication here refers to authenticating the first object identification information to obtain the authenticated information (i.e., the authentication object identification information).

[0114] Among them, it should be understood that the above-mentioned authentication event information refers to the event information generated when the first authentication transaction has been executed by the consensus node and the first object identification information carried is obtained, and the first business object is bound to the first object identification information, which is used by the resource service terminal for off-chain detection. Once the resource service terminal detects the authentication event information, the resource service terminal knows that the first business object has submitted registration information on the first resource client, and then it will perform information authentication on the first object identification information in the authentication event information, thereby obtaining the authenticated information (that is, the authentication object identification information).

[0115] The resource service terminal packages the transaction based on the authentication object information, thereby obtaining an information authentication transaction. It then uses the private key associated with the first business object to sign the information authentication transaction and sends it to the consensus node. At this point, the second authentication transaction carries the second signature information after the transaction is signed. The second signature information carries the public key information corresponding to the private key information. Therefore, when the consensus node receives the second authentication transaction, it can obtain the public key information carried in the information authentication transaction and then verify the signature using this public key information.

[0116] For details, see Figure 7 , Figure 7 This is another schematic diagram of a consensus node obtaining and adding registration address information provided by an embodiment of the present application. Figure 7 As shown, the terminal device 70a can correspond to the above Figure 2 In the corresponding embodiment, the terminal device 20a has a business object corresponding to the terminal device 70a, which is the business object a1, i.e., the first business object. In addition, a resource client, i.e., the first resource client, is running on the terminal device 70a. The resource service terminal 70b is the backend terminal of the first resource client. The consensus node 70c can correspond to the above Figure 2 The consensus node 20b in the corresponding embodiment.

[0117] like Figure 7As shown, business object a1 can log in to the first resource client through terminal device 70a and register for a service on the registration service interface displayed on the first resource client. Specifically, business object a1 enters the service registration information on the registration service interface. The service registration information here may include the relevant information described above (e.g., name information, fingerprint information, etc.). After completing the entry, business object a1 clicks the submit information control, thereby obtaining service registration information 700a. Further, the first resource client sends service registration information 700a to resource service terminal 70b (step S71). The resource service terminal receives service registration information 700a and then packages the transaction based on the service registration information 700a to obtain transaction TX5. Transaction TX5 can be a transaction based on the first authentication transaction described above.

[0118] Furthermore, business object a1 sends transaction TX5 (i.e., the first authentication transaction) to consensus node 70c via the first resource client, which in turn sends it via the resource service terminal (step S72). Consensus node 70c receives transaction TX5, invokes the authentication contract to execute transaction TX5, and obtains authentication event information (step S73). The authentication event information here can be the business object a1 and business registration information 700b (i.e., the name information, fingerprint information, etc. associated with business object a1).

[0119] Furthermore, after detecting the authentication event, resource service terminal 70b retrieves the service registration information 700a contained in the authentication event and authenticates the service registration information 700a, obtaining identification information 700b (step S74). Specifically, resource service terminal 70b authenticates the information contained in service registration information 700a (e.g., fingerprint information, name information, etc.), configures a registration address for the first service object, and obtains registration address information. The registration address information is packaged as identification information 700b (i.e., authentication object identification information) in a transaction, resulting in transaction TX6. Transaction TX6 can be the second authentication transaction described above.

[0120] Furthermore, resource service terminal 70b sends transaction TX6 (i.e., the second authentication transaction) to consensus node 70c (step S75). Consensus node 70c receives transaction TX6, first performs transaction signature verification on transaction TX6, then obtains identification information 700b in transaction TX6 and adds identification information 600b to the list.

[0121] For further information, see Figure 8 , Figure 8 This is a schematic diagram of obtaining a target authentication information list provided by an embodiment of the present application. Figure 8As shown, the authentication information list 801a is the initial authentication information list mentioned above, and the consensus node adds the identification information 800a. In other words, the consensus node 80c adds the identification information 800a to the authentication information list 801a (i.e., the initial authentication information list), thereby obtaining the authentication information list 801b, i.e., the target authentication information list mentioned above, as shown in FIG. Figure 8 As shown, the authentication information list 801b (ie, the target authentication information list) includes identification information 800a (ie, address registration information). It should be understood that the identification information 800a here may correspond to the above Figure 6 The identification information 600b in the corresponding embodiment, or Figure 7 This corresponds to the identification information 700b in the embodiment.

[0122] Step S103: When generating a digital collectible based on the generation request, deploying an account contract associated with the digital collectible on the blockchain, configuring an account management relationship between the account contract and the first object identification information, and storing the digital collectible in the account contract;

[0123] The first object identification information includes, but is not limited to, the address information of the first business object, which can be referred to as the first account address. Furthermore, it should be understood that since the claim request is sent by the first business object, the holder of the digital collectible generated by the consensus node based on the request is the first business object. In other words, the digital collectible stored in the account contract is specifically stored in the first account address of the account contract.

[0124] As mentioned above, the consensus node configures the account management relationship between the account contract and the first object identification information, which means that at this time the first business object is the contract management object of the account contract, and the first business object can perform any operation on the digital collection in the account contract.

[0125] The account management relationship indicates that the first business object has account management permissions for the digital collectibles in the account contract. Account management permissions may include, but are not limited to, asset transfer permissions, read permissions, change permissions, delegation permissions, and approval permissions. In this embodiment, we will not elaborate on the permissions involved in these account management permissions.

[0126] Asset transfer permission refers to the permission to transfer business assets within an account contract; read permission refers to the permission to view specific data within an account contract, which may include account assets, transaction history, contract status, and other information. In the insurance policy business scenario, read permission can refer to the permission to view the specific content within the insurance policy contract. Change permission refers to the permission to modify the contract status, change permission settings, or perform other operations that may affect the account contract status. Change permission can include the permission to change the content of the insurance policy contract and the permission to change the beneficiary, etc. Delegate permission allows certain permissions to be delegated to other business objects; approval permission refers to the permission to approve operations performed by other business objects on business assets. Only approved operations can be executed. This is only an example explanation of the permissions listed above; other permissions exist and will not be explained in detail here.

[0127] Step S104: receiving an account management transaction sent by the first resource client;

[0128] The account management transaction includes an account authorization transaction that instructs a first business object to authorize a second business object to share account management permissions for an account contract. As mentioned above, an account authorization transaction can refer to the first business object authorizing the second business object to share change permissions within an account contract. Alternatively, it can refer to the first business object authorizing the second business object to share delegation permissions within an account contract. Furthermore, it can refer to the first business object authorizing the second business object to share management permissions for specific business assets (e.g., first-type assets) within an account contract. In this case, the second business object can perform any operations on the first-type asset contract within the account contract.

[0129] Step S105: When calling the account contract to execute the account authorization transaction, the role management contract associated with the account contract is called, and the second business object is configured as an account sharing role for the account contract through the role management contract. Based on the account sharing role, an account sharing management relationship is configured between the account contract and the second object identification information of the second business object, and the account sharing management relationship is used as the first transaction execution result of the account authorization transaction.

[0130] The second business object may be any individual, enterprise, organization, etc. other than the first business object. The role management contract specifically refers to a contract that can configure related roles (eg, account sharing roles) for other business objects (eg, the second business object).

[0131] It should be understood that account-sharing roles refer to the sharing of access rights and roles across multiple business entities for a system, platform, or service. This role model typically allows for better management and allocation of system resources, information, and functionality. In many systems, users are assigned to different roles, each with a specific set of permissions. For example, a system may have roles such as administrator, user, and observer, each with varying levels of system access and operational permissions.

[0132] For example, in an insurance policy business scenario, the rights and roles within an insurance policy may include the policyholder, insurer, insured, and beneficiary. Each policyholder, insurer, insured, and beneficiary has different rights and obligations, which are reflected in the policy contract. For example, the policyholder's rights include canceling the policy, designating and changing the beneficiary, changing the policy contract content, and attaching conditions or time limits to the contract's effectiveness. The policyholder's obligations include, but are not limited to, notification and information. The insurer's rights include, but are not limited to, modifying the policy contract content, requesting compensation on behalf of the insured, and questioning the insured. The insurer's obligations include, but are not limited to, assuming insurance liability, providing explanations and reminders, notifications, and maintaining confidentiality. The insured's rights include, but are not limited to, designating and changing the beneficiary, requesting and collecting insurance assets. The insured's obligations include, but are not limited to, notification and confidentiality obligations. The beneficiary's rights include requesting insurance assets, requesting compensation for insurance assets, collecting insurance assets, and obtaining income rights. The beneficiary's obligations include notification and the provision of relevant supporting documentation. It should be understood that in this insurance policy business scenario, the first business object can be the holder of the insurance policy contract, and different insurance policy responsibilities (for example, rights and obligations) are formulated for different business objects. At this time, the above-mentioned second business object can correspond to any one of the above-mentioned roles of the insured, insurer, insured, and beneficiary, and is specified by the first business object.

[0133] Among them, it should be understood that the above-mentioned account authorization transaction may include an operation authorization transaction for instructing the first business object to authorize the second business object to have a first asset operation permission for the first type of asset in the account contract; then, at this time, the specific steps may include: the consensus node may call the role management contract associated with the account contract through the account contract when calling the account contract to execute the account authorization transaction; further, the consensus node may configure the second business object as an account sharing role for the account contract through the role management contract, and may configure the account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role; in addition, the consensus node may also configure the first asset operation management relationship between the first type of asset and the second object identification information in the account contract based on the account sharing role; and then the consensus node may use the account sharing management relationship and the first asset operation management relationship as the first transaction execution result of the account authorization transaction.

[0134] It should be understood that the first transaction execution result is used to represent that the first business object has authorized the second business object to share the account management authority for the account contract, and that the first business object has authorized the second business object to have the first asset operation authority for the first type of asset in the account contract; the account management authority includes the authority transfer authority used to instruct the second business object to transfer the account management authority.

[0135] The first asset operation management relationship refers to the operational relationship between the second business object and the first type of asset. For example, the second business object can transfer the first type of asset, or register the first type of asset. Similarly, the first asset operation permission can correspond to the aforementioned asset transfer permission for the first type of asset, or the asset registration permission for registering the first type of asset.

[0136] For example, in the aforementioned insurance policy business scenario, the account sharing role of the second business object can refer to any of the aforementioned roles: policyholder, insurer, insured, or beneficiary. For example, if the second business object's account sharing role is the insured, then the account management permissions can include the aforementioned permissions to designate and change beneficiaries, request insurance assets, and claim insurance assets. Furthermore, if the first type of asset is the insurance asset corresponding to the insured (e.g., Asset A), then the asset call permissions can include, but are not limited to, the second business object's permission to claim the insurance asset A or transfer the insurance asset A to other business objects. Detailed examples will not be given here.

[0137] It should be understood that the specific steps for determining the first type of assets may include: calling the account contract through the role management contract, obtaining the asset type classification method, and determining the asset type of the business assets in the account contract based on the asset type classification method; classifying the business assets based on the asset type, and obtaining the first type of assets in the business assets.

[0138] It should be understood that this asset classification method is a method included in the account contract, and that this asset classification method can be used to classify digital assets in the account contract. It should be understood that in different business scenarios, this asset classification method can be based on multiple factors, such as the nature of the asset, its purpose, and its value. For example, if the classification is based on asset type, assuming that the business assets in the digital collection include virtual real estate, game props, game skins, tickets, and merchandise receipts, then virtual real estate can be classified as a first-type asset, game skins and game props can be classified as a second-type asset, and tickets and merchandise receipts can be classified as a third-type asset. For another example, if the classification is based on asset value, assets with large asset amounts (e.g., asset amounts of more than 100) can be classified as first-type assets, and assets with small asset amounts (e.g., asset amounts of less than 100) can be classified as second-type assets.

[0139] For details, see Figure 9 , Figure 9 This is a schematic diagram of configuring an account sharing role for a second business object provided by an embodiment of the present application. Figure 9 As shown, business object a1 may correspond to the first business object, account contract 9a may correspond to the account contract, and account address 900a may be the address of business object a1 (i.e., the first business object) (e.g., the registered address of the first business object). Business assets are stored in account address 900a, where business assets are divided according to the above-mentioned asset type classification method, for example, divided into Figure 9 The first type of assets, the second type of assets and the third business assets shown. In addition, there is an account management relationship between business object a1 and account contract 9a, that is, business object a1 can manage account contract 9a and the business assets in account contract 9a. For example, the specific permissions for the business assets in account contract 9a include: Figure 9 The approval permission, transfer permission, sharing permission, ..., read permission, etc. are shown. This means that business object a1 has the permissions listed above and can perform corresponding operations.

[0140] Furthermore, the consensus node calls the role management contract to configure the account sharing role for the business object a2, where the business object a2 here may correspond to the second business object mentioned above. Figure 9 As shown, at this time, business object a2 (i.e., the second business object) has the same permissions as business object a1 (i.e., the first business object) and can manage the business assets in the account address 900a in the account contract 9a. For example, the specific permissions for the business assets in the account contract 9a include: Figure 9 The approval permission, transfer permission, sharing permission, ..., read permission, etc. are shown. This means that business object a1 has the permissions listed above and can perform corresponding operations.

[0141] Optionally, the account sharing role configured by the first business object for the second business object may also be specifically configured to configure one or more permissions for the second business object for the business assets in the account contract 9a; the second business object may have the above Figure 9 The approval authority shown; or the second business object can have the above Figure 9 Approval permissions and transfer permissions are shown. Furthermore, you can configure an asset operation management relationship between a first-type asset and a second business object, specifically including asset call permissions for the first-type asset. For example, asset call permissions can be permissions to transfer the first-type asset.

[0142] It should be understood that the code for managing the account contract and configuring the role by the first business object may be as follows:

[0143] It mainly involves three code segments: authorization, revocation, and role checking:

[0144] (1)function grantRoleFrom(bytes32_role,address_tokenAddress,uint256_tokenId,address_grantor,address_grantee)external;

[0145] This code is a function code related to the authorization role, and can be specifically applied to the step of calling the role management contract to configure the account sharing role for the second business object. The authorization role code defines five core data fields (e.g., role field, first address field, identification field, second address field, and third address field). The role field can be used to describe the role with a holding relationship with the digital collection represented by 32 bytes (i.e., the above string bytes32_role), the first address field can be used to describe the authorized address of the digital collection (i.e., the above address_tokenAddress), the identification field can be used to describe the identifier of the digital collection represented by 256 bits (i.e., the above uint256_tokenId), the second address field can be used to describe the address of the grantor (i.e., the above address_grantor), and the third address field can be used to describe the address of the authorized person (i.e., the above address_grantee). Through the grantRoleFrom function, the authorizer can authorize the authorized person to hold the role of a digital collection. That is, the authorizer authorizes the authorizer's address as the address holding the digital collection, and the authorized person can then perform related operations and permission management on the digital collection.

[0146] In an embodiment of the present application, the authorizer may be the first business object, the authorizer address is the address of the first business object (i.e., the registered address of the first business object), the authorized person may be the second business object, the authorized person address is the address of the second business object (i.e., the registered address of the second business object), the authorizer (i.e., the first business object) authorizes the authorized person (i.e., the second business object) to have the account sharing role (i.e., the above-mentioned role) of the above-mentioned account contract, and authorizes the second business object to have the account management relationship of the above-mentioned account contract (including the management relationship of the digital collections in the account contract).

[0147] (2)function revokeRoleFrom(bytes32_role,address_tokenAddress,uint256_tokenId,address_revoker,address_grantee)external;

[0148] This code is a function code related to the withdrawal of roles, which can be specifically applied to calling the role management contract to withdraw the account sharing role of the second business object. Among them, the code for withdrawing the role defines five core data fields (for example, the role field, the first address field, the identification field, the fourth address segment, and the third address field). Among them, the role field, the first address field, the identification field, and the third address field can be referred to the description in (1) above, and will not be repeated here. In addition, the fourth address field can be specifically used to describe the address of the revoker (that is, the above-mentioned address_revoker). The function revokeRoleFrom can be used by the revoker to withdraw the role of the authorized person holding the digital collection, that is, the authorizer withdraws the address of the digital collection granted to the authorized person, and then the authorized person will no longer be able to perform related operations and permission management on the digital collection.

[0149] In an embodiment of the present application, the revoker may be the first business object, the revoker address is the address of the first business object (i.e., the registered address of the first business object), the authorized person may be the second business object, the authorized person address is the address of the second business object (i.e., the registered address of the second business object), the authorizer (i.e., the first business object) revokes the account sharing role (i.e., the above-mentioned role) of the above-mentioned account contract to the authorized person (i.e., the second business object), and revokes the account management relationship of the second business object for the above-mentioned account contract (including the management relationship of the digital collection in the account contract).

[0150] (3)function hasRole(bytes32_role,address_tokenAddress,uint256_tokenId,address_grantor,address_grantee)external view returns(bool);

[0151] This code is a function code related to checking roles. Specifically, it can be applied to the following embodiments when the second business object initiates an operation request for the account contract, and the consensus node calls the account contract to query the role and corresponding permissions of the second business object. Among them, the code for checking roles defines five core data fields (for example, the role field, the first address field, the identification field, the second address field, and the third address field). The role field, the first address field, the identification field, the second address field, and the third address field can be referred to in the above (1), and will not be repeated here.

[0152] In an embodiment of the present application, the function hasRole function can be used in subsequent embodiments when the second business object initiates an operation request for the account contract. The consensus node calls the account contract and queries the role and corresponding permissions of the second business object through the function hasRole function to determine whether to execute the operation request initiated by the second business object.

[0153] In addition, it should be understood that the account contract also maintains a permission management relationship list, which is the initial permission management relationship list; the consensus node can call the account contract through the role management contract, store the above-mentioned first transaction execution result to the initial permission management relationship list maintained by the account contract, and can determine the initial permission management relationship list with the first transaction execution result added as the first target permission management relationship list.

[0154] The initial permission management relationship list refers to a list that stores initial business objects and the permissions they possess. This list is typically created during the account contract deployment phase to ensure effective management of access to assets in the account contract. For example, the initial business object can refer to the first business object mentioned above. In this case, the first business object can refer to the administrator of the account contract. An account management relationship exists between the first business object and the account contract. This account management relationship means that the first business object can perform any operation on the account contract and any operation on the digital collections in the account contract. The permissions possessed by the first business object include, but are not limited to, assigning and revoking permissions for the account contract, configuring business objects for the management of business assets in the account contract, and approving specific operations or transactions. For example, a specific operation can be an asset transfer operation initiated by a business object for business assets in the account contract.

[0155] It can be understood that the above-mentioned first target permission management relationship list refers to the list after the initial permission management relationship list is updated. Taking the above-mentioned first business object as an example, in which the first business object configures an account sharing role for the second business object by calling the role management contract, and configures the account contract for the second business object based on the account sharing role and the account sharing management relationship between the second business object and the second business object, the permissions possessed by the second business object at this time can be the permissions possessed by the above-mentioned first business object, the permission to transfer permissions (or permission sharing) for its own permissions, and the permission to independently operate the above-mentioned first type of assets. The independent operations here can include but are not limited to asset transfer operations on first type assets, and the first business object does not need to approve the asset transfer operation, so that some assets in the first type of assets can be successfully transferred. Therefore, it should be understood that the above-mentioned first target permission management relationship list is a list that stores the first business object and the permissions corresponding to the first business object, and the second business object and the permissions corresponding to the second business object.

[0156] It should be understood that after configuring the account sharing role and corresponding permissions for the second business object, the second business object can initiate an operation request (e.g., a first operation request) through its corresponding resource client. The resource client corresponding to the second business object can be referred to as the second resource client, and the operation request is a request for the account contract. The consensus node can then receive the operation request and perform further operations.

[0157] Specifically, the consensus node can obtain a first operation request for the account contract sent by the second resource client; it should be understood that the first operation request is used to instruct the second business object to perform a permission transfer operation on the account management permission of the account contract; further, the consensus node can call the authentication contract through the account contract to perform information authentication on the second object identification information of the second business object carried in the first operation request, and obtain a first information authentication result; it should be understood that when the first information authentication result indicates that the second object identification information authentication is successful, the consensus node can call the account contract to query the account operation permission between the second business object and the account contract, thereby obtaining a first query result; it should be understood that when the first query result indicates that the second business object has the permission to transfer the permission for the account contract, the consensus node can execute the permission transfer operation indicated by the first operation request based on the permission transfer permission, obtain the first operation execution result, and return the first operation execution result to the second resource client.

[0158] The detailed description of the account management authority can be found in the description of the account management authority in the above step S105, which will not be repeated here.

[0159] Furthermore, it should be understood that the aforementioned permission transfer can also be referred to as permission sharing, i.e., sharing the permissions possessed by one (e.g., the second business object) with another business object (e.g., the third business object). For example, if the permission possessed by the second business object is approval permission, after permission sharing, both the second business object and the third business object now possess the same approval permission. It should be understood that the result of executing the first operation at this time means that both the second business object and the third business object possess approval permission.

[0160] For example, if the second business object has the permission to add an approval object, after permission sharing, the second and third business objects now both have the permission to add an approval object. It should be understood that the result of executing the first operation means that both the second and third business objects have the permission to add an approval object.

[0161] For example, if the second business object has the asset transfer permission to transfer the first type of assets in the account contract, after permission sharing, the second and third business objects now both have the asset transfer permission to transfer the first type of assets in the account contract. It should be understood that the result of the first operation in this case means that both the second and third business objects have the asset transfer permission to transfer the first type of assets in the account contract.

[0162] It should be understood that the specific process of authenticating the second object identification information of the second business object can be found in the above Figure 5 The specific process of authenticating the first object identification information in the corresponding embodiment will not be described in detail here.

[0163] In addition, specifically, the first query result can be obtained as follows: the consensus node calls the account contract, queries the account operation authority that the second business object has for the account contract in the first target authority management relationship list maintained by the account contract, and obtains the first query result.

[0164] It should be understood that the first target authority management relationship list can refer to the above description of the first target authority management relationship list, which will not be repeated here.

[0165] Optionally, the account management transaction further includes an asset operation transaction for instructing the first business object to authorize the second business object to perform an asset operation on a second type of asset in the account contract.

[0166] Optional, see Figure 10 , Figure 10 This is a flow chart of configuring asset operation management relationship for a second business object provided by an embodiment of the present application. The method can be performed by a consensus node (for example, Figure 1The consensus node 11a) shown in FIG. The method includes the following steps S201 to S205.

[0167] Step S201: When calling an account contract to execute an asset operation transaction, obtain an asset type classification method, and determine the asset type of the business asset in the account contract based on the asset type classification method;

[0168] Step S202: classifying the business assets into asset types based on the asset types, and obtaining second-type assets in the business assets;

[0169] Step S203: Calling the role management contract through the account contract to configure the second asset operation management relationship between the second type of asset and the second object identification information;

[0170] The second asset operation management relationship can be the same as or different from the first asset operation management relationship. For example, the first asset operation management relationship can refer to the operation relationship between the second business object and the second type of asset. For example, the second business object can transfer the second type of asset, or register the second type of asset. Similarly, the second asset operation permission can correspond to the asset transfer permission for the first type of asset, or can also correspond to the asset registration permission for the first type of asset.

[0171] Step S204: Using the second asset operation management relationship as the second transaction execution result of the asset operation transaction;

[0172] The second transaction execution result is used to indicate that the first business object has authorized the second business object to have the second asset operation permission for the second type of asset;

[0173] Step S205: Call the account contract through the role management contract, store the second transaction execution result in the initial permission management relationship list maintained by the account contract, and determine the initial permission management relationship list with the second transaction execution result added as the second target permission management relationship list.

[0174] It should be understood that the above asset classification method can be found in the above Figure 4 The description of the asset classification method in the corresponding embodiment will not be repeated here.

[0175] See Figure 11 , Figure 11 This is a schematic diagram of a scenario for configuring asset operation management relationship for a second business object provided by an embodiment of the present application. Figure 11As shown, business object a1 may correspond to the first business object, account contract 11a may correspond to the account contract, and account address 1100a may be the address of business object a1 (i.e., the first business object) (e.g., the registered address of the first business object). Business assets are stored in account address 1100a, where business assets are divided according to the above-mentioned asset type classification method, for example, divided into Figure 11 The first type of assets, the second type of assets, and the third business assets are shown.

[0176] Furthermore, the consensus node calls the role management contract to configure the second asset operation management relationship for the business object a2; specifically, it may refer to configuring the asset operation management relationship of the second business object for the second type of assets in the business assets, such as Figure 11 As shown, business object a2 now has asset call permission for the second type of asset. It should be understood that asset call permission may include but is not limited to permission to transfer the second type of asset, permission to register the second type of asset, etc.

[0177] Optionally, the first business object may also call the role management contract to configure an asset operation management relationship for the first type of assets or the third type of assets for the business object a2, which is specifically determined by the first business object.

[0178] In addition, it should be understood that the first business object calls the role contract to configure the second asset operation management relationship for the business object a2, which can be seen in the above code. Figure 9 The code segments related to the authorization roles in the corresponding embodiment will not be described in detail here.

[0179] Furthermore, corresponding to the aforementioned insurance policy business scenario, the account sharing role of the second business object can be a role responsible for managing insurance assets (e.g., asset B). In this case, the second asset operation permissions may include, but are not limited to, the permission for the second business object to claim insurance asset B or transfer insurance asset B to other business objects. A detailed example will not be given here.

[0180] It should be understood that after configuring the second asset operation management relationship for the second type of asset for the second business object, the second business object can initiate an operation request (e.g., a second operation request) through its corresponding resource client. The resource client corresponding to the second business object can be referred to as the second resource client, and the operation request is a request for the second type of asset in the account contract. The consensus node can then receive the operation request and perform further operations.

[0181] Specifically, the consensus node can obtain a second operation request for the account contract sent by the second resource client; wherein, it should be understood that the second operation request is used to instruct the second business object to perform an asset transfer operation for the second type of asset; further, the consensus node can call the authentication contract through the account contract to perform information authentication on the second object identification information of the second business object carried in the second operation request, thereby obtaining a second information authentication result; then, when the second information authentication result indicates that the second object identification information authentication is successful, the consensus node can call the account contract to query the asset operation authority between the second business object and the second type of asset in the account contract, and obtain a second query result; further, when the second query result indicates that the second business object has the second asset operation authority for the second type of asset, the consensus node can execute the asset transfer operation indicated by the second operation request based on the second asset operation authority, obtain a second operation execution result, and can return the second operation execution result to the second resource client.

[0182] The second type of assets may include, but are not limited to, assets with large asset values (i.e., asset values exceeding 100), virtual real estate, virtual game props, etc. Assuming the second type of assets are stored at account address A (e.g., the address of the first business object), the asset transfer operation here is to transfer the second type of assets from account address A to account address B (e.g., the address of the third business object).

[0183] Similarly, it should be understood that the specific process of authenticating the second object identification information of the second business object can be found in the above Figure 5 The specific process of authenticating the first object identification information in the corresponding embodiment will not be described in detail here.

[0184] In addition, specifically, the second query result obtained above can be specifically: the consensus node calls the account contract, and queries the asset operation authority of the second business object for the second type of assets in the account contract in the second target authority management relationship list maintained by the account contract to obtain the second query result.

[0185] It should be understood that the first target authority management relationship list can refer to the above description of the first target authority management relationship list, which will not be repeated here.

[0186] It can be seen from this that in the embodiment of the present application, the consensus node can obtain the collection transaction sent by the first resource client; further, the consensus node can write the collection transaction into the digital collection contract, call the authentication contract through the digital collection contract, and perform information authentication on the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, call the digital collection contract to generate a generation request for generating the digital collection; further, when the consensus node generates the digital collection based on the generation request, it can deploy an account contract associated with the digital collection on the blockchain, configure the account management relationship between the account contract and the first object identification information, and store the digital collection in the account contract; it should be understood that the account management relationship is used to indicate that the first business object has account management authority over the digital collection in the account contract. This means that by deploying the account contract and storing the digital collection in the account contract, the digital collection has an independent account that can store business assets. In addition, the consensus node can receive the account management transaction sent by the first resource client; it should be understood that the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; further, the consensus node can call the role management contract associated with the account contract when calling the account contract to execute the account authorization transaction, configure the second business object as an account sharing role for the account contract through the role management contract, configure the account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and use the account sharing management relationship as the first transaction execution result of the account authorization transaction; it should be understood that the first transaction execution result is used to characterize that the first business object has authorized the second business object to share the account management authority for the account contract. This means that by configuring the second business object as an account sharing role for the account contract, the second business object has the account management authority for the account contract, so that multiple business objects can manage the account contract. It can be seen that the embodiment of the present application can improve the correlation of account management through on-chain account authorization, thereby enabling multiple business objects to effectively manage the permissions and assets corresponding to the account, thereby enriching the business scenarios of digital collections (for example, the above-mentioned insurance policy business scenario).

[0187] See Figure 12 , Figure 12 This is a flow chart of another data processing method based on blockchain provided by the embodiment of the present application. The method can be executed by the first resource client, which can run on the above Figure 1 For any terminal device (eg, terminal device 10a) in the terminal device cluster in the corresponding embodiment, the method may specifically include the following steps S301 to S302.

[0188] Step S301: Sending a claim transaction for claiming the digital collection to the consensus node;

[0189] Among them, the collection transaction carries transaction parameters, which may include the transaction source address of the transaction, that is, the address of the business object sending the transaction (that is, the first business object), and may also include the destination address of the transaction, that is, the contract address of the smart contract to be called. Some additional parameters of the transaction may include the data required to pass when calling the smart contract, such as the specific calling processing method required when calling the above-mentioned digital collection contract, other parameters required to be passed in when calling the digital collection contract, etc., which are not limited here.

[0190] Step S302, sending an account management transaction to the consensus node; wherein, the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; the account contract is deployed on the blockchain when the consensus node generates a digital collection based on a generation request; the generation request is when the consensus node calls the authentication contract through the digital collection contract to authenticate the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, calls the digital collection contract to generate.

[0191] Among them, the detailed description of account management transactions can be found in the above Figure 4 The description of the account management transaction in step S104 in the corresponding embodiment will not be repeated here. Similarly, the detailed description of the account authorization transaction can also be found in the above Figure 4 The description of the account authorization transaction in step S104 in the corresponding embodiment will not be repeated here.

[0192] For further information, see Figure 13 , Figure 13 This is an interactive diagram of a data processing method based on blockchain provided by an embodiment of the present application. Figure 2 The consensus node 20b in the corresponding embodiment, the first resource client running on the terminal device 20a, the resource service terminal corresponding to the first resource client, and the resource service terminal running on the terminal device (for example, Figure 1 The second resource client of the corresponding terminal device 10b) interacts and executes together. The method may specifically include the following steps S401-S415.

[0193] Step S401: The resource service terminal sends a first authentication transaction to the consensus node;

[0194] Step S402: The consensus node calls the authentication contract to execute the first authentication transaction and obtains authentication event information;

[0195] Step S403: when the authentication event information is detected, performing information authentication on the first object identification information;

[0196] Step S404: The resource service terminal sends a second authentication transaction to the consensus node;

[0197] Step S405: The consensus node obtains the authentication object identification information, adds the address registration object and authentication address information to the initial authentication information list maintained by the authentication contract, and obtains the target authentication information list;

[0198] The description of steps S401 to S405 can be found in the above Figure 7 The description of the corresponding embodiments will not be repeated here.

[0199] Step S406: The consensus node writes the claim transaction into the digital collection contract and calls the authentication contract to authenticate the first business object identifier.

[0200] The description of step S406 can be found in the above Figure 5 The process of information authentication in the corresponding embodiment will not be described in detail here.

[0201] Step S407: The first resource client sends a claim transaction to the consensus node;

[0202] Step S408: When the information authentication is successful, the consensus node calls the digital collection contract to generate a generation request for generating the digital collection;

[0203] Step S409: When generating the digital collectible, the consensus node deploys an account contract on the blockchain, configures the account management relationship between the account contract and the first object identification information, and stores the digital collectible in the account contract;

[0204] Step S410: The first resource client sends an account management transaction to the consensus node;

[0205] It should be understood that the description of steps S407 to S410 can refer to the above Figure 4 The description of step S103 - step S104 in the corresponding embodiment will not be repeated here.

[0206] Step S411: When the consensus node calls the account contract to execute the account authorization transaction, it calls the role management contract to configure the account sharing role for the second business object, and configures the account management relationship between the account contract and the second object identification information based on the account sharing role;

[0207] The detailed description of step S411 can be found in the above Figure 10 The description of the corresponding embodiments will not be repeated here.

[0208] Step S412: The second resource client sends an operation request to the consensus node;

[0209] Step S413: The consensus node calls the authentication contract to authenticate the second object identification information;

[0210] Step S414: When the information authentication is successful, the consensus node queries the account operation authority of the second business object, and performs the operation if the second business object has the operation authority;

[0211] Step S415: The consensus node sends the operation execution result to the second resource client.

[0212] It should be understood that the description of steps S412 to S415 can refer to the above Figure 4 or Figure 10 The description of the corresponding embodiment, wherein Figure 4 In , the operation request here may correspond to the first operation request mentioned above. Or, in Figure 10 The operation request here may correspond to the second operation request, which will not be described in detail here.

[0213] It can be seen from this that in the embodiment of the present application, the consensus node can obtain the collection transaction sent by the first resource client; further, the consensus node can write the collection transaction into the digital collection contract, call the authentication contract through the digital collection contract, and perform information authentication on the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, call the digital collection contract to generate a generation request for generating the digital collection; further, when the consensus node generates the digital collection based on the generation request, it can deploy an account contract associated with the digital collection on the blockchain, configure the account management relationship between the account contract and the first object identification information, and store the digital collection in the account contract; it should be understood that the account management relationship is used to indicate that the first business object has account management authority over the digital collection in the account contract. This means that by deploying the account contract and storing the digital collection in the account contract, the digital collection has an independent account that can store business assets. In addition, the consensus node can receive the account management transaction sent by the first resource client; it should be understood that the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; further, the consensus node can call the role management contract associated with the account contract when calling the account contract to execute the account authorization transaction, configure the second business object as an account sharing role for the account contract through the role management contract, configure the account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and use the account sharing management relationship as the first transaction execution result of the account authorization transaction; it should be understood that the first transaction execution result is used to characterize that the first business object has authorized the second business object to share the account management authority for the account contract. This means that by configuring the second business object as an account sharing role for the account contract, the second business object has the account management authority for the account contract, so that multiple business objects can manage the account contract. It can be seen that the embodiment of the present application can improve the correlation of account management through on-chain account authorization, thereby enabling multiple business objects to effectively manage the permissions and assets corresponding to the account, thereby enriching the business scenarios of digital collections (for example, the above-mentioned insurance policy business scenario).

[0214] See Figure 14 , Figure 14 This is a schematic diagram of the structure of a data processing device based on blockchain provided by an embodiment of the present application. Figure 14 As shown, the blockchain-based data processing device 1 can be applied to a consensus node, which can be any consensus node in a consensus network (for example, the consensus network A11). For example, the consensus node can be the consensus node Figure 1The consensus node 11a in the corresponding embodiment. It should be understood that the blockchain-based data processing device 1 can be a computer program (including program code) running in a consensus node (for example, the aforementioned consensus node 11a). For example, the blockchain-based data processing device 1 can be an application software. The blockchain-based data processing device 1 can be used to execute the corresponding steps of the method provided in the embodiment of the present application. Figure 14 As shown, the blockchain-based data processing device 1 may include: a first acquisition module 11, a request generation module 12, a contract deployment module 13, a first receiving module 14 and a role configuration module 15;

[0215] A first acquisition module 11 is used to acquire a redemption transaction sent by a first resource client for redeeming a digital collection;

[0216] The request generation module 12 is configured to write the claim transaction into the digital collection contract used to generate the digital collection, call the authentication contract through the digital collection contract, authenticate the first object identification information of the first business object in the claim transaction, and upon successful authentication, call the digital collection contract to generate a generation request for generating the digital collection;

[0217] A contract deployment module 13 is configured to deploy an account contract associated with the digital artifact on the blockchain when generating the digital artifact based on the generation request, configure an account management relationship between the account contract and the first object identification information, and store the digital artifact in the account contract; the account management relationship is used to indicate that the first business object has account management authority over the digital artifact in the account contract;

[0218] A first receiving module 14 is configured to receive an account management transaction sent by the first resource client; the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract;

[0219] The role configuration module 15 is configured to call the role management contract associated with the account contract when calling the account contract to execute the account authorization transaction, configure the second business object as an account sharing role for the account contract through the role management contract, configure the account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and use the account sharing management relationship as the first transaction execution result of the account authorization transaction; the first transaction execution result is used to indicate that the first business object has authorized the second business object to share the account management authority for the account contract.

[0220] The specific implementation of the first acquisition module 11, the request generation module 12, the contract deployment module 13, the first receiving module 14 and the role configuration module 15 can be found in the above Figure 4The description of steps S101 to S105 in the corresponding embodiment will not be repeated here.

[0221] The digital collection contract includes a first contract method and a second contract method; the first contract method is a first contract invocation method for invoking the authentication contract, and the second contract method is a request generation method for generating a request; the first object identification information includes access address information used by the first business object when accessing the first resource client;

[0222] The request generation module 12 includes: a first acquisition unit 121, an information authentication unit 122, a result generation unit 123, and a request generation unit 124;

[0223] The first acquisition unit 121 is configured to acquire a first contract call method from the digital collection contract, call the authentication contract through the first contract call method, and acquire a target authentication information list maintained by the authentication contract; the target authentication information list includes registered address information of at least one address registration object;

[0224] The information authentication unit 122 is configured to perform information authentication on the first object identification information of the first business object in the claim transaction based on the registration address information in the target authentication information list, and obtain an information authentication result;

[0225] A result generating unit 123 is configured to generate an information authentication success result indicating that the information authentication is successful when the information authentication result indicates that the registered address information of at least one address registration object matches the access address information.

[0226] The request generation unit 124 is used to call the digital collection contract acquisition request generation method based on the successful result of the information authentication, and obtain a generation request for generating the digital collection through the request generation method.

[0227] The specific implementation of the first acquisition unit 121, the information authentication unit 122, the result generation unit 123 and the request generation unit 124 can be found in the above Figure 5 The description in the corresponding embodiment will not be repeated here.

[0228] The information authentication unit 122 includes: an information search subunit, a first information matching subunit, and a second information matching subunit;

[0229] An information search subunit, configured to search for address information matching the access address information in the registered address information in the target authentication information list;

[0230] The first information matching subunit is configured to, if address information matching the access address information is found in the registered address information, use the search success result that matches the access address information as the information authentication result;

[0231] The second information matching subunit is configured to use a search failure result of not finding address information matching the access address information as an information authentication result if no address information matching the access address information is found in the registered address information.

[0232] The specific implementation of the information search subunit, the first information matching subunit and the second information matching subunit can be found in the above Figure 5 The description of the corresponding embodiments will not be repeated here.

[0233] Optionally, the authentication information list maintained in the authentication contract is an initial authentication information list;

[0234] The device 1 further includes: a first transaction acquisition module 16 and a first information adding module 17;

[0235] The first transaction acquisition module 16 is configured to acquire an information authentication transaction sent by a resource service terminal corresponding to the first resource client. The transaction parameters of the information authentication transaction carry authentication object identification information after information authentication. The authentication object identification information is obtained by the resource service terminal after performing information authentication based on the first object identification information of the first business object. The first object identification information includes the business registration information submitted by the first business object on the registration business interface of the first resource client for information authentication.

[0236] The first information adding module 17 is used to obtain authentication object identification information from the information authentication transaction, use the first business object as the address registration object corresponding to the authentication object identification information, and when adding the address registration object and the authentication object identification information to the initial authentication information list maintained by the authentication contract, determine the initial authentication information list with the added authentication object identification information as the target authentication information list.

[0237] The specific implementation of the first transaction acquisition module 16 and the first information adding module 17 can be found in the above Figure 6 The description of the corresponding embodiments will not be repeated here.

[0238] Optionally, the apparatus 1 further comprises: a second transaction acquiring module 18, a first transaction executing module 19, a transaction receiving module 20 and a second information adding module 21;

[0239] The second transaction acquisition module 18 is configured to acquire a first authentication transaction sent by a resource service terminal corresponding to the first resource client; the transaction parameters of the first authentication transaction carry first object identification information of the first business object; the first object identification information includes business registration information submitted by the first business object for information authentication on the registration business interface of the first resource client;

[0240] The first transaction execution module 19 is configured to call the authentication contract to execute the first authentication transaction and obtain authentication event information associated with the first object identification information, so that when the resource service terminal detects the authentication event information, it authenticates the first object identification information contained in the authentication event information and sends the second authentication transaction to the consensus node; the transaction parameters of the second authentication transaction carry the authentication object identification information after information authentication, and the authentication object identification information is obtained after the resource service terminal performs information authentication based on the first object identification information;

[0241] The transaction receiving module 20 is used to receive the second authentication transaction sent by the resource service terminal;

[0242] The second information adding module 21 is used to obtain the authentication object identification information from the second authentication transaction, and use the first business object as the address registration object corresponding to the authentication object identification information. When adding the address registration object and the authentication address information to the initial authentication information list maintained by the authentication contract, the initial authentication information list with the authentication object identification information added is determined as the target authentication information list.

[0243] The specific implementation of the second transaction acquisition module 18, the first transaction execution module 19, the transaction receiving module 20 and the second information adding module 21 can be found in the above Figure 7 The description of the corresponding embodiments will not be repeated here.

[0244] The account authorization transaction includes an operation authorization transaction for instructing the first business object to authorize the second business object to have a first asset operation permission for a first type of asset in the account contract;

[0245] The role configuration module 15 includes: a first contract calling unit 151, a first configuration unit 152, a second configuration unit 153, and an execution result determination unit 154;

[0246] The first contract calling unit 151 is used to call the role management contract associated with the account contract through the account contract when calling the account contract to perform the account authorization transaction;

[0247] A first configuration unit 152 is configured to configure the second business object as an account sharing role for the account contract through the role management contract, and configure an account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role;

[0248] The second configuration unit 153 is configured to configure a first asset operation management relationship between a first type of asset and second object identification information in the account contract based on the account sharing role;

[0249] An execution result determining unit 154 is configured to use the account sharing management relationship and the first asset operation management relationship as a first transaction execution result of the account authorization transaction; the first transaction execution result is configured to indicate that the first business object has authorized the second business object to share the account management authority for the account contract, and that the first business object has authorized the second business object to have the first asset operation authority for the first type of asset in the account contract; and the account management authority includes a permission transfer authority for instructing the second business object to transfer the account management authority.

[0250] The specific implementation of the first contract calling unit 151, the first configuration unit 152, the second configuration unit 153 and the execution result determination unit 154 can be found in the above Figure 4 The description of step S105 in the corresponding embodiment will not be repeated here.

[0251] The account contract includes an asset type classification method for classifying business assets in the account contract into asset types;

[0252] The second configuration unit 153 includes: an asset type determination subunit, a first division subunit, and a first asset configuration subunit;

[0253] The asset type determination subunit is used to call the account contract through the role management contract, obtain the asset type classification method, and determine the asset type of the business assets in the account contract based on the asset type classification method;

[0254] An asset type classification subunit, configured to classify business assets based on asset type, and obtain first type assets from the business assets;

[0255] The first asset configuration subunit is configured to configure a first asset operation management relationship between a first type of asset and second object identification information based on the account sharing role.

[0256] The specific implementation of the asset type determination subunit, the first division subunit and the first asset allocation subunit can be found in the above Figure 10 The description of steps S202 to S205 in the corresponding embodiment will not be repeated here.

[0257] Optionally, the permission management relationship list maintained by the account contract is an initial permission management relationship list;

[0258] The device 1 further includes: a first execution result storage module 22;

[0259] The first execution result storage module 22 is used to call the account contract through the role management contract, store the first transaction execution result in the initial permission management relationship list maintained by the account contract, and determine the initial permission management relationship list added with the first transaction execution result as the first target permission management relationship list.

[0260] The specific implementation of the first execution result storage module 22 can be found in the above Figure 4 The description of steps S101 to S105 in the corresponding embodiment will not be repeated here.

[0261] Optionally, the apparatus 1 further includes: a first request obtaining module 23, a first information authentication module 24, a first authority query module 25, and a first operation execution module 26;

[0262] A first request acquisition module 23 is configured to acquire a first operation request for an account contract sent by a second resource client; the first operation request is configured to instruct the second business object to perform a permission transfer operation for transferring the account management permission of the account contract;

[0263] The first information authentication module 24 is configured to call the authentication contract through the account contract to authenticate the second object identification information of the second business object carried in the first operation request, and obtain a first information authentication result;

[0264] A first permission query module 25 is configured to, when the first information authentication result indicates that the second object identification information authentication is successful, call the account contract to query the account operation permission between the second business object and the account contract, and obtain a first query result;

[0265] The first operation execution module 26 is used to execute the permission transfer operation indicated by the first operation request based on the permission transfer permission when the first query result indicates that the second business object has the permission to transfer the permission for the account contract, obtain the first operation execution result, and return the first operation execution result to the second resource client.

[0266] The specific implementation of the first request acquisition module 23, the first information authentication module 24, the first authority query module 25 and the first operation execution module 26 can be found in the above Figure 11 The description of the corresponding embodiments will not be repeated here.

[0267] The first authority query module 25 includes: a first query unit 251;

[0268] The first query unit 251 is configured to call the account contract and query the account operation authority possessed by the second business object for the account contract in the first target authority management relationship list maintained by the account contract to obtain a first query result.

[0269] The specific implementation of the first query unit 251 can be found in the above Figure 4 The description of steps S101 to S105 in the corresponding embodiment will not be repeated here.

[0270] Optionally, the account management transaction includes an asset operation transaction for instructing the first business object to authorize the second business object to perform an asset operation on a second type of asset in the account contract; the account contract includes an asset type classification method for classifying business assets in the account contract into asset types;

[0271] The apparatus 1 further comprises: an asset type determination module 27, an asset type classification module 28, a management relationship configuration module 29, and an execution result determination module 30;

[0272] The asset type determination module 27 is used to obtain the asset type classification method when calling the account contract to perform an asset operation transaction, and determine the asset type of the business asset in the account contract based on the asset type classification method;

[0273] An asset type classification module 28 is configured to classify business assets based on asset type and obtain second type assets from the business assets;

[0274] A management relationship configuration module 29 is configured to call a role management contract through an account contract to configure a second asset operation management relationship between the second type of asset and the second object identification information;

[0275] The execution result determination module 30 is used to use the second asset operation management relationship as the second transaction execution result of the asset operation transaction; the first transaction execution result is used to indicate that the first business object has authorized the second business object to have the second asset operation permission for the second type of asset.

[0276] The specific implementation of the asset type determination module 27, the asset type classification module 28, the management relationship configuration module 29 and the execution result determination module 30 can be found in the above Figure 10 The description of steps S201 to S205 in the corresponding embodiment will not be repeated here.

[0277] Optionally, the permission management relationship list maintained by the account contract is an initial permission management relationship list;

[0278] The device 1 further includes: a second execution result storage module 31;

[0279] The second execution result storage module 31 is used to call the account contract through the role management contract, store the second transaction execution result in the initial permission management relationship list maintained by the account contract, and determine the initial permission management relationship list with the second transaction execution result added as the second target permission management relationship list.

[0280] The specific implementation of the second execution result storage module 31 can be found in the above Figure 10 The description of steps S201 to S205 in the corresponding embodiment will not be repeated here.

[0281] Optionally, the device 1 further includes: a second request acquisition module 32, a second information authentication module 33, a second authority query module 34 and a second operation execution module 35;

[0282] A second request acquisition module 32 is configured to acquire a second operation request for the account contract sent by the second resource client; the second operation request is configured to instruct the second business object to perform an asset transfer operation for a second type of asset;

[0283] The second information authentication module 33 is configured to call the authentication contract through the account contract to authenticate the second object identification information of the second business object carried in the second operation request, and obtain a second information authentication result;

[0284] A second permission query module 34 is configured to, when the second information authentication result indicates that the second object identification information authentication is successful, call the account contract to query the asset operation permission between the second business object and the second type of asset in the account contract, and obtain a second query result;

[0285] The second operation execution module 35 is used to execute the asset transfer operation indicated by the second operation request based on the second asset operation authority when the second query result indicates that the second business object has the second asset operation authority for the second type of assets, obtain the second operation execution result, and return the second operation execution result to the second resource client.

[0286] The specific implementation of the second request acquisition module 32, the second information authentication module 33, the second authority query module 34 and the second operation execution module 35 can be found in the above Figure 4 The description of the corresponding embodiments will not be repeated here.

[0287] The second authority query module 34 includes: a second query unit 341;

[0288] The second query unit 341 is configured to call the account contract and query the second target permission management relationship list maintained by the account contract for the asset operation permission possessed by the second business object for the second type of asset in the account contract to obtain a second query result.

[0289] The specific implementation of the second query unit 341 can be found in the above Figure 10 The description of steps S201 to S205 in the corresponding embodiment will not be repeated here.

[0290] See Figure 15 , Figure 15 This is a structural diagram of another data processing device based on blockchain provided by the embodiment of this application. Figure 15 As shown, the blockchain-based data processing device 2 can be a computer program (including program code) running on a computer device. For example, the blockchain-based data processing device 2 can be an application software, and the computer device can be a user terminal (for example, the above-mentioned Figure 1 The terminal device 10a shown in FIG. 1 is a block chain-based data processing device 2 that can be used to execute the corresponding steps of the method provided in the embodiment of the present application. Figure 15 As shown, the blockchain-based data processing device 2 may include: a first transaction sending module 201 and a second transaction sending module 202;

[0291] The first transaction sending module 201 is used to send a claim transaction for claiming a digital collection to the consensus node;

[0292] The second transaction sending module 202 is used to send an account management transaction to the consensus node; the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; the account contract is deployed on the blockchain when the consensus node generates a digital collection based on a generation request; the generation request is generated when the consensus node calls the authentication contract through the digital collection contract to authenticate the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, it calls the digital collection contract to generate.

[0293] The specific implementation of the first transaction sending module 201 and the second transaction sending module 202 can be found in the above Figure 12 The description of step S301-step S302 in the corresponding embodiment will not be repeated here.

[0294] Further, see Figure 16 , Figure 16 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. Figure 16As shown, the computer device 1000 may be a user terminal, for example, Figure 1 The terminal device 10a in the corresponding embodiment may also be a server, for example, Figure 1 The server 10d in the corresponding embodiment will not be limited here. For ease of understanding, this application takes the computer device as an example of a user terminal. The computer device 1000 may include: a processor 1001, a network interface 1004 and a memory 1005. In addition, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. Among them, the user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. As Figure 16 As shown, the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application.

[0295] The network interface 1004 in the computer device 1000 can also provide a network communication function, and the optional user interface 1003 can also include a display screen and a keyboard. Figure 16 In the computer device 1000 shown, the network interface 1004 can provide network communication functions; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to execute the above Figure 4 、 Figure 10 、 Figure 12 as well as Figure 13 The description of the data processing method based on blockchain in the corresponding embodiment can also be performed as described above. Figure 14 The description of the data processing device 1 based on blockchain in the corresponding embodiment, as well as the above Figure 15 The description of the blockchain-based data processing device 2 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here.

[0296] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores the computer program executed by the blockchain-based data processing device 1 mentioned above, and the computer program includes computer instructions. When the processor executes the computer instructions, it can execute the above-mentioned Figure 4 、 Figure 10 、 Figure 12 as well as Figure 13 The description of the data processing method based on blockchain in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, computer instructions can be deployed on a computing device for execution, or on multiple computing devices located in one location, or on multiple computing devices distributed in multiple locations and interconnected by a communication network. Multiple computing devices distributed in multiple locations and interconnected by a communication network can constitute a blockchain system.

[0297] In addition, it should be noted that: the embodiment of the present application also provides a computer program product or computer program, which may include computer instructions, which may 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 may execute the computer instructions, so that the computer device performs the above Figure 4 、 Figure 10 、 Figure 12 as well as Figure 13 The description of the blockchain-based data 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 here. For technical details not disclosed in the computer program product or computer program embodiments involved in this application, please refer to the description of the method embodiments of this application.

[0298] For further information, see Figure 17 , Figure 17 Schematic diagram of a data processing system provided in an embodiment of the present application. The data processing system 3 may include a data processing device 1a and a data processing device 2a. The data processing device 1a may be the above-mentioned Figure 14 In the corresponding embodiment, the data processing device 1 based on blockchain can be integrated into the above-mentioned Figure 2 The corresponding embodiment of the consensus node 20b, therefore, will not be described here in detail. Among them, the data processing device 2a can be the above Figure 15In the corresponding embodiment, the data processing device 2 based on blockchain can be integrated into the above-mentioned Figure 2 The first resource client running on the terminal device 20a in the corresponding embodiment will not be described in detail here. In addition, the description of the beneficial effects of adopting the same method will not be described in detail. For technical details not disclosed in the data processing system embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0299] It should be noted that for the aforementioned various method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0300] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0301] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0302] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a 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 part of an overall module or unit that includes the function of the module or unit.

[0303] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0304] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method based on blockchain, characterized in that: The blockchain has an authentication contract and a digital collection contract associated with the authentication contract deployed thereon. The method is executed by a consensus node, on which the authentication contract and the digital collection contract are running. The method includes: Obtaining a claim transaction sent by the first resource client for claiming the digital collection; Writing the claim transaction into the digital collection contract used to generate the digital collection, invoking the authentication contract through the digital collection contract to authenticate the first object identification information of the first business object in the claim transaction, and upon successful authentication, invoking the digital collection contract to generate a generation request for generating the digital collection; When generating the digital collectible based on the generation request, deploying an account contract associated with the digital collectible on the blockchain, configuring an account management relationship between the account contract and the first object identification information, and storing the digital collectible in the account contract; the account management relationship is used to indicate that the first business object has account management authority over the digital collectible in the account contract; receiving an account management transaction sent by the first resource client; the account management transaction comprising an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; When calling the account contract to execute the account authorization transaction, the role management contract associated with the account contract is called, and the second business object is configured as an account sharing role for the account contract through the role management contract. Based on the account sharing role, an account sharing management relationship is configured between the account contract and the second object identification information of the second business object, and the account sharing management relationship is used as a first transaction execution result of the account authorization transaction; the first transaction execution result is used to indicate that the first business object has authorized the second business object to share the account management authority for the account contract.

2. The method according to claim 1, characterized in that The digital collection contract includes a first contract method and a second contract method; the first contract method is a first contract calling method for calling the authentication contract, and the second contract method is a request generation method for generating a request; The first object identification information includes access address information used by the first business object when accessing the first resource client; The step of calling the authentication contract through the digital collection contract to authenticate the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, calling the digital collection contract to generate a generation request for generating the digital collection includes: Obtaining the first contract calling method from the digital collectible contract, calling the authentication contract through the first contract calling method, and obtaining a target authentication information list maintained by the authentication contract; the target authentication information list includes registered address information of at least one address registration object; Based on the registered address information in the target authentication information list, performing information authentication on the first object identification information of the first business object in the claim transaction to obtain an information authentication result; When the information authentication result indicates that the registered address information of the at least one address registration object contains registered address information that matches the access address information, generating an information authentication success result indicating that the information authentication is successful; Based on the successful result of the information authentication, the digital collection contract is called to obtain the request generation method, and a generation request for generating the digital collection is obtained through the request generation method.

3. The method according to claim 2, characterized in that The step of performing information authentication on the first object identification information of the first business object in the collection transaction based on the registered address information in the target authentication information list to obtain an information authentication result includes: Searching for address information matching the access address information in the registered address information in the target authentication information list; If address information matching the access address information is found in the registered address information, the search success result matching the access address information is used as the information authentication result; If no address information matching the access address information is found in the registered address information, a search failure result indicating that no address information matching the access address information is found is used as an information authentication result.

4. The method according to claim 2, characterized in that The authentication information list maintained in the authentication contract is the initial authentication information list; Before obtaining the claiming transaction sent by the first resource client for claiming the digital collectible, the method further includes: Obtaining an information authentication transaction sent by a resource service terminal corresponding to the first resource client; wherein the transaction parameters of the information authentication transaction carry authentication object identification information after information authentication, the authentication object identification information being obtained by the resource service terminal after information authentication based on the first object identification information of the first business object; the first object identification information comprising the service registration information for information authentication submitted by the first business object on a registration service interface of the first resource client; The authentication object identification information is obtained from the information authentication transaction, and the first business object is used as the address registration object corresponding to the authentication object identification information. When the address registration object and the authentication object identification information are added to the initial authentication information list maintained by the authentication contract, the initial authentication information list with the authentication object identification information added thereto is determined as the target authentication information list.

5. The method according to claim 2, characterized in that The authentication information list maintained in the authentication contract is the initial authentication information list; Before obtaining the claiming transaction sent by the first resource client for claiming the digital collectible, the method further includes: Obtaining a first authentication transaction sent by a resource service terminal corresponding to the first resource client; the transaction parameters of the first authentication transaction carry first object identification information of the first business object; the first object identification information includes business registration information submitted by the first business object on a registration business interface of the first resource client for information authentication; The authentication contract is called to execute the first authentication transaction, obtaining authentication event information associated with the first object identification information, so that upon detecting the authentication event information, the resource service terminal performs information authentication on the first object identification information contained in the authentication event information, and sends a second authentication transaction to the consensus node; the transaction parameters of the second authentication transaction carry the authentication object identification information after information authentication, and the authentication object identification information is obtained by the resource service terminal after information authentication based on the first object identification information; receiving the second authentication transaction sent by the resource service terminal; The authentication object identification information is obtained from the second authentication transaction, and the first business object is used as the address registration object corresponding to the authentication object identification information. When the address registration object and the authentication address information are added to the initial authentication information list maintained by the authentication contract, the initial authentication information list with the authentication object identification information added is determined as the target authentication information list.

6. The method according to claim 1, characterized in that The account authorization transaction includes an operation authorization transaction for instructing the first business object to authorize the second business object to have a first asset operation permission for a first type of asset in the account contract; The method further comprises: when calling the account contract to execute the account authorization transaction, calling the role management contract associated with the account contract, configuring the second business object as an account sharing role for the account contract through the role management contract, configuring an account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and using the account sharing management relationship as the first transaction execution result of the account authorization transaction, including: When calling the account contract to execute the account authorization transaction, calling the role management contract associated with the account contract through the account contract; Configuring the second business object as an account sharing role for the account contract through the role management contract, and configuring an account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role; configuring a first asset operation management relationship between the first type of asset in the account contract and the second object identification information based on the account sharing role; The account sharing management relationship and the first asset operation management relationship are used as the first transaction execution result of the account authorization transaction; the first transaction execution result is used to indicate that the first business object has authorized the second business object to share the account management authority for the account contract, and that the first business object has authorized the second business object to have the first asset operation authority for the first type of asset in the account contract; the account management authority includes a permission transfer authority for instructing the second business object to transfer the account management authority.

7. The method according to claim 6, characterized in that The account contract includes an asset type classification method for classifying business assets in the account contract into asset types; The configuring the asset operation management relationship between the first type of asset in the account contract and the second object identification information based on the account sharing role includes: Calling the account contract through the role management contract to obtain the asset type classification method, and determining the asset type of the business asset in the account contract based on the asset type classification method; Classifying the business assets into asset types based on the asset types, and obtaining the first type of assets in the business assets; A first asset operation management relationship between the first type of asset and the second object identification information is configured based on the account sharing role.

8. The method according to claim 6, characterized in that The permission management relationship list maintained by the account contract is the initial permission management relationship list; After taking the account sharing management relationship and the first asset operation management relationship as the first transaction execution result of the account authorization transaction, the method further includes: The account contract is called by the role management contract, the first transaction execution result is stored in the initial permission management relationship list maintained by the account contract, and the initial permission management relationship list to which the first transaction execution result is added is determined as the first target permission management relationship list.

9. The method according to claim 8, characterized in that The method further comprises: Obtaining a first operation request for the account contract sent by the second resource client; the first operation request is used to instruct the second business object to perform a permission transfer operation on the account management permission of the account contract; Calling the authentication contract through the account contract to authenticate the second object identification information of the second business object carried in the first operation request, thereby obtaining a first information authentication result; When the first information authentication result indicates that the second object identification information authentication is successful, calling the account contract to query the account operation authority between the second business object and the account contract to obtain a first query result; When the first query result indicates that the second business object has the permission to transfer the permission for the account contract, the permission transfer operation indicated by the first operation request is performed based on the permission to transfer the permission, a first operation execution result is obtained, and the first operation execution result is returned to the second resource client.

10. The method according to claim 9, characterized in that The calling of the account contract to query the account operation authority between the second business object and the account contract to obtain a first query result includes: The account contract is called, and the account operation authority possessed by the second business object for the account contract is searched in the first target authority management relationship list maintained by the account contract to obtain a first query result.

11. The method according to claim 1, wherein The account management transaction includes an asset operation transaction for instructing the first business object to authorize the second business object to perform an asset operation on a second type of asset in the account contract; the account contract includes an asset type classification method for classifying business assets in the account contract into asset types; The method further comprises: When calling the account contract to execute the asset operation transaction, obtaining the asset type classification method, and determining the asset type of the business asset in the account contract based on the asset type classification method; Classifying the business assets into asset types based on the asset types, and obtaining the second type of assets in the business assets; Calling the role management contract through the account contract to configure a second asset operation management relationship between the second type of asset and the second object identification information; The second asset operation management relationship is used as the second transaction execution result of the asset operation transaction; the second transaction execution result is used to indicate that the first business object has authorized the second business object to have the second asset operation permission for the second type of asset.

12. The method according to claim 11, characterized in that The permission management relationship list maintained by the account contract is the initial permission management relationship list; After taking the second asset operation management relationship as the second transaction execution result of the asset operation transaction, the method further includes: The account contract is called by the role management contract, the second transaction execution result is stored in the initial permission management relationship list maintained by the account contract, and the initial permission management relationship list to which the second transaction execution result is added is determined as the second target permission management relationship list.

13. The method according to claim 12, characterized in that The method further comprises: Obtaining a second operation request for the account contract sent by the second resource client, wherein the second operation request is used to instruct the second business object to perform an asset transfer operation for transferring the second type of asset; Invoking the authentication contract through the account contract to authenticate the second object identification information of the second business object carried in the second operation request, and obtaining a second information authentication result; When the second information authentication result indicates that the second object identification information authentication is successful, calling the account contract to query the asset operation authority between the second business object and the second type of asset in the account contract, and obtaining a second query result; When the second query result indicates that the second business object has the second asset operation authority for the second type of asset, the asset transfer operation indicated by the second operation request is executed based on the second asset operation authority, a second operation execution result is obtained, and the second operation execution result is returned to the second resource client.

14. The method according to claim 13, characterized in that The calling of the account contract to query the asset operation authority between the second business object and the second type of asset, and obtaining a second query result, includes: The account contract is called, and the asset operation permission possessed by the second business object for the second type of asset in the account contract is searched in the second target permission management relationship list maintained by the account contract to obtain a second query result.

15. A data processing method based on blockchain, characterized in that: An authentication contract and a digital collection contract associated with the authentication contract are deployed on the blockchain; The method is executed by a first resource client, and includes: Send a claim transaction to the consensus node to claim the digital collection; An account management transaction is sent to the consensus node; the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; the account contract is deployed on the blockchain when the consensus node generates the digital collection based on the generation request; the generation request is generated when the consensus node calls the authentication contract through the digital collection contract, authenticates the first object identification information of the first business object in the collection transaction, and calls the digital collection contract when the information authentication is successful.

16. A data processing device based on blockchain, characterized in that: The blockchain is deployed with an authentication contract and a digital collection contract associated with the authentication contract. The device is deployed on a consensus node, and the authentication contract and the digital collection contract are running on the consensus node. The device includes: A first acquisition module is used to acquire a redemption transaction sent by a first resource client for redeeming a digital collection; a request generation module, configured to write the claim transaction into a digital collection contract used to generate the digital collection, invoke the authentication contract through the digital collection contract, perform information authentication on the first object identification information of the first business object in the claim transaction, and upon successful information authentication, invoke the digital collection contract to generate a generation request for generating the digital collection; a contract deployment module configured to, when generating the digital collectible based on the generation request, deploy an account contract associated with the digital collectible on the blockchain, configure an account management relationship between the account contract and the first object identification information, and store the digital collectible in the account contract; the account management relationship being used to indicate that the first business object has account management authority over the digital collectible in the account contract; a first receiving module, configured to receive an account management transaction sent by the first resource client; the account management transaction comprising an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; a role configuration module, configured to, when calling the account contract to execute the account authorization transaction, call the role management contract associated with the account contract, configure the second business object as an account sharing role for the account contract through the role management contract, configure an account sharing management relationship between the account contract and the second object identification information of the second business object based on the account sharing role, and use the account sharing management relationship as a first transaction execution result of the account authorization transaction; the first transaction execution result being used to indicate that the first business object has authorized the second business object to share the account management authority for the account contract.

17. A data processing device based on blockchain, characterized in that: An authentication contract and a digital collection contract associated with the authentication contract are deployed on the blockchain; The device is deployed on a first resource client, and includes: A first transaction sending module, configured to send a claim transaction for claiming a digital collection to a consensus node; The second transaction sending module is used to send an account management transaction to the consensus node; the account management transaction includes an account authorization transaction for instructing the first business object to authorize the second business object to share the account management authority for the account contract; the account contract is deployed on the blockchain when the consensus node generates the digital collection based on the generation request; the generation request is generated by the consensus node calling the authentication contract through the digital collection contract to authenticate the first object identification information of the first business object in the collection transaction, and when the information authentication is successful, calling the digital collection contract.

18. A computer device, characterized in that: including memory and 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 according to any one of claims 1 to 15.

19. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 15.

20. A computer program product, characterized in that The method comprises a computer program / instruction, which implements the method according to any one of claims 1 to 15 when executed by a processor.

Images