A processing method, device, equipment, medium and program product of a digital product

Abstract

Embodiments of the present application provide a digital product processing method, device, equipment, medium and program product, wherein the method comprises: when an operation request performed by a target object on a digital product is obtained, obtaining a digital identifier of the target object; generating a product operation voucher based on the digital identifier of the target object and operation information; if the target object confirms to perform a target operation on the digital product, obtaining declaration data obtained by performing signature processing on the product operation voucher by using first signature data of the target object; and performing the target operation on the digital product based on the declaration data. The embodiments of the present application can improve the security and traceability of the digital product.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for processing digital products, a device for processing digital products, a computer device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] Digital products are digital products that are uniquely identified based on blockchain technology. Compared with physical products, digital products are popular with the public because of their advantages such as portability, dissemination, and permanent storage.

[0003] Currently, operations such as casting, publishing, or transferring digital products are supported to facilitate their creation and circulation. However, existing operations on digital products do not consider issues such as the security and traceability of the digital products and objects; they simply and crudely perform corresponding operations (such as transferring digital products). Therefore, improving security and traceability has become a hot research topic for digital products. Summary of the Invention

[0004] This application provides a method, apparatus, device, medium, and program product for processing digital products, which can improve the security and traceability of digital products.

[0005] On one hand, embodiments of this application provide a method for processing digital products, the method comprising:

[0006] When a target object requests an operation on a digital product, the target object's digital identifier is obtained, and the operation request carries the operation information of the requested target operation.

[0007] A product operation certificate is generated based on the digital identifier and operation information of the target object; the product operation certificate is used to indicate that the digital product is requested to perform the target operation, and to indicate that the requester of the target operation is the target object;

[0008] If the target object confirms to perform the target operation on the digital product, then the first signature data of the target object is obtained, and the declaration data obtained by performing signature processing on the product operation certificate is obtained.

[0009] Perform targeted operations on digital products based on claimed data.

[0010] On the other hand, embodiments of this application provide a processing apparatus for a digital product, the apparatus comprising:

[0011] The acquisition unit is used to acquire the digital identifier of the target object when it acquires an operation request for the target object to perform on the digital product. The operation request carries the operation information of the requested target operation.

[0012] The processing unit is used to generate a product operation certificate based on the digital identifier and operation information of the target object; the product operation certificate is used to indicate that the digital product is requested to perform the target operation, and to indicate that the requester of the target operation is the target object;

[0013] The processing unit is further configured to, if the target object confirms that the target operation is performed on the digital product, obtain the declaration data obtained by performing signature processing on the product operation certificate using the first signature data of the target object;

[0014] The processing unit is also used to perform target operations on digital products based on claim data.

[0015] In one implementation, the digital identifier of the target object is bound to the second signature data of the target object. When the processing unit performs target operations on the digital product based on the declaration data, it specifically performs the following:

[0016] Based on the digital identifier of the target object, obtain the second signature data of the target object;

[0017] The second signature data of the target object is used to verify the signature of the declared data;

[0018] If the data verification is successful, the target operation will be performed on the digital product.

[0019] In one implementation, the operation request is used to request the casting of a digital product, the target operation includes the operation of casting the digital product, and the operation information of the target operation includes: product casting information required for casting the digital product;

[0020] When the processing unit performs target operations on digital products, it is specifically used for:

[0021] Based on the product casting information required for casting digital products, digital products are cast to obtain digital products;

[0022] Create product identifiers for the digital products obtained through casting;

[0023] Bind the product identifier of the digital product to the digital identifier of the target object.

[0024] In one implementation, when the processing unit binds the product identifier of the digital product and the digital identifier of the target object, it specifically performs the following:

[0025] A first mapping and binding relationship is established based on the digital identifier of the target object and the product identifier of the digital product. The first mapping and binding relationship is used to indicate that the holder of the digital product is the target object.

[0026] The first mapping and binding relationship is stored in the smart contract corresponding to the digital product.

[0027] In one implementation, the operation request is used to request the transfer of a digital product from a target object to a reference object, the reference object being different from the target object. The target operation includes the operation of transferring the digital product, and the operation information of the target operation includes at least: the digital identifier of the reference object and the product identifier of the digital product.

[0028] When the processing unit performs target operations on digital products, it is specifically used for:

[0029] Obtain the product document corresponding to the digital product; the product document includes a controller field, which records the digital identifier of the target object;

[0030] In the product documentation, change the numerical identifier of the target object recorded in the controller field to the numerical identifier of the reference object;

[0031] Furthermore, in the smart contract corresponding to the digital product, the first mapping binding relationship is modified to a second mapping binding relationship; wherein, the first mapping binding relationship indicates that the holder of the digital product is the target object, and the second mapping binding relationship indicates that the holder of the digital product is the reference object.

[0032] In one implementation, when the processing unit obtains the product document corresponding to the digital product, it specifically performs the following:

[0033] The product identifier of the digital product is parsed to obtain the corresponding product document; the product document stores the metadata of the digital product.

[0034] In one implementation, the data is declared to have a transfer validity period; the processing unit is further used for:

[0035] The generation time of the declaration data is obtained. The generation time refers to the moment when the product operation certificate of the digital product is signed and the declaration data is generated.

[0036] Determine the target duration between the generation time of the declaration data and the current time, where the current time refers to the moment when the declaration data is verified and signed.

[0037] If the target duration is less than or equal to the transfer validity duration, the step of performing the target operation on the digital product based on the declared data is triggered.

[0038] In one implementation, the processing unit is used to obtain the declaration data obtained by performing signature processing on the product operation credential using the first signature data of the target object if the target object confirms the execution of the target operation on the digital product. Specifically, it is used to:

[0039] The product operation credential is sent to the target object so that when the target object confirms the execution of the target operation on the digital product, it uses the target object's first signature data to sign the product operation credential to obtain the declaration data and returns the declaration data.

[0040] Receive the declaration data returned by the target object.

[0041] In one implementation, the processing unit is used to obtain the declaration data obtained by performing signature processing on the product operation credential using the first signature data of the target object if the target object confirms the execution of the target operation on the digital product. Specifically, it is used to:

[0042] Output product operation credentials on the display screen;

[0043] In response to the target object's signature operation on the product operation credential, the signed product operation credential is obtained;

[0044] The signed product operation certificate is used as the declaration data.

[0045] In one implementation, the processing unit, in response to the target object's signature operation on the product operation credential, obtains the signed product operation credential by specifically:

[0046] In response to the target object adopting the target object's first signature data, a signature operation is performed on the product operation credential to obtain a signed product operation credential;

[0047] Alternatively, receive the authorization operation of the target object for the product operation certificate, obtain the first signature data of the target object, and use the first signature data of the target object to perform signature processing on the product operation certificate to obtain the signed product operation certificate.

[0048] In one implementation, the process of generating the digital identifier of the target object includes:

[0049] Obtain object information of the target object;

[0050] Convert object information into a numerical identifier for the target object;

[0051] The object information includes the public key of the target object.

[0052] On the other hand, this application provides an electronic device, which includes:

[0053] A processor is used to load and execute computer programs;

[0054] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the processing method of the aforementioned digital product.

[0055] On the other hand, this application provides a computer-readable storage medium storing a computer program adapted to be loaded by a processor and executed by the processing method of the aforementioned digital product.

[0056] On the other hand, this application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the processing method of the aforementioned digital product.

[0057] In this embodiment, upon receiving an operation request from a target object to perform on a digital product, a product operation credential can be generated based on the target object's digital identifier and the operation information carried in the operation request. This product operation credential indicates that the digital product is requested to perform a target operation, and that the requester of the target operation is the target object. By generating a product operation credential for the digital product, the target object can obtain the credential and be intuitively informed of relevant information about the digital product, thus optimizing the expression and readability of the digital product. Furthermore, the target operation is only performed on the digital product after the target object confirms the execution of the target operation, i.e., obtains the declaration data (i.e., the signed product operation), and the declaration data is successfully verified, ensuring the security and traceability of the digital product. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0059] Figure 1a This is a schematic diagram of a blockchain structure provided in an exemplary embodiment of this application;

[0060] Figure 1b This is a schematic diagram of the structure of a data sharing system provided in an exemplary embodiment of this application;

[0061] Figure 2a This is a schematic diagram of the architecture of a digital product processing system provided in an exemplary embodiment of this application;

[0062] Figure 2b This is a schematic diagram of the structure of a blockchain application protocol model provided in an exemplary embodiment of this application;

[0063] Figure 2c This is a schematic diagram illustrating the protocol mapping relationship between an NFT smart contract and a DID smart contract, provided in an exemplary embodiment of this application.

[0064] Figure 2d This is a schematic diagram of an NFT protocol design based on the DID protocol provided in an exemplary embodiment of this application;

[0065] Figure 3 This is a flowchart illustrating a digital product processing method provided in an exemplary embodiment of this application;

[0066] Figure 4 This is a schematic diagram illustrating an output product operation certificate provided in an exemplary embodiment of this application;

[0067] Figure 5 This is a flowchart illustrating another digital product processing method provided in an exemplary embodiment of this application;

[0068] Figure 6 This is a schematic diagram of a process for casting digital products provided in an exemplary embodiment of this application;

[0069] Figure 7 This is a flowchart illustrating another digital product processing method provided in an exemplary embodiment of this application;

[0070] Figure 8 This is a schematic diagram of a process for transferring digital products provided in an exemplary embodiment of this application;

[0071] Figure 9 This is a schematic diagram of the structure of a processing apparatus for a digital product provided in an exemplary embodiment of this application;

[0072] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this application. Detailed Implementation

[0073] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0074] This application provides a processing solution for digital products, which mainly involves blockchain technology, specifically typical applications of blockchain technology, including: Decentralized Identity (DID) and Non-Fungible Token (NFT).

[0075] The following is a brief description of the technical terms and concepts involved in the embodiments of this application, wherein:

[0076] 1) Blockchain is the foundation of blockchain technology. Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A schematic diagram of a blockchain structure can be found here. Figure 1a ,like Figure 1a As shown, Blockchain 101 consists of multiple blocks. The first block of the blockchain is called the genesis block (or simply the genesis block). The genesis block includes a block header and a block body. The block header stores the input information feature value, version number, timestamp, and difficulty value, while the block body stores the input information. The next block after the genesis block takes the genesis block as its parent block. The next block also includes a block header and a block body. The block header stores the input information feature value of the current block, the block header feature value of the parent block, the version number, the timestamp, and the difficulty value, and so on. This ensures that the block data stored in each block of the blockchain is related to the block data stored in the parent block, guaranteeing the security of the input information in the blocks.

[0077] A blockchain can be maintained by blockchain nodes contained within a blockchain network; wherein, a blockchain network can be understood as a data sharing system, referring to a system used for data sharing between blockchain nodes, an exemplary structure of which can be found here. Figure 1b ;like Figure 1bAs shown, the data sharing system may include multiple blockchain nodes 101. Each blockchain node 101 can be a server connected to the blockchain network, or a terminal (such as a client running on a terminal) connected to the blockchain network. The specific form of the blockchain node 101 is not limited here. Each blockchain node 101 in the blockchain network has a corresponding node identifier, and each blockchain node 101 can store the node identifiers of other blockchain nodes 101 in the blockchain network. This allows the generated block to be broadcast to other blockchain nodes 101 in the data sharing system based on the node identifiers of other blockchain nodes 101, thereby achieving distributed storage of the data contained in the block within the blockchain network and ensuring the immutability, non-copyability, and permanent preservation of the data.

[0078] It is important to note that ① when implementing a business on a blockchain network, smart contracts must be followed. A smart contract can be a digital protocol that deploys the necessary protocol specifications for executing a business transaction in code form on a blockchain network; specifically, it involves deploying the smart contract on blockchain nodes, which then run the smart contract to realize the corresponding business. For example, if the business corresponding to the smart contract is a transaction, then the smart contract is a contract used for transactions. For instance, the smart contract might include: querying the logistics status of goods purchased by a consumer, and transferring the consumer's electronic resources (such as resources used for transactions on the internet) to the merchant's address after the consumer signs for the goods. After the consumer has signed for the goods, the smart contract (specifically, the code of the smart contract) can be run to transfer the consumer's electronic resources (such as resources used for transactions on the internet) to the merchant's address. Of course, the above is merely an exemplary application of a smart contract provided in this application.

[0079] ② Based on the degree of openness of blockchain networks, blockchains maintained by blockchain networks are mainly divided into three types: public blockchains, consortium blockchains, and private blockchains. A public blockchain refers to a blockchain where any node in the network (such as a blockchain node corresponding to a single object or a group of objects) can send transaction data, and the transaction data can be effectively confirmed; any node can participate in the consensus process. A consortium blockchain refers to a blockchain where some nodes in the network can participate in the block consensus process, while other nodes do not have access to the consensus process. For example, within a blockchain network containing a consortium blockchain, multiple pre-selected blockchain nodes can be designated as accounting nodes (such as blockchain nodes with consensus permissions). Each block on the consortium blockchain is jointly decided by all pre-selected blockchain nodes (i.e., pre-selected blockchain nodes participate in the consensus process). Other blockchain nodes connected to the network besides the pre-selected blockchain nodes can participate in transactions but do not participate in the consensus process. A private blockchain refers to a blockchain in a blockchain network where a single blockchain node has exclusive write permissions (such as uploading blocks after reaching consensus). In other words, a private blockchain has exclusive write permissions within a blockchain network.

[0080] 2) Digital products may include non-fungible tokens (NFTs), a set of digital asset protocols based on blockchain technology. Specifically, products are digitized and placed on the blockchain, making them unique, indivisible, and rare digital products. For ease of explanation, NFT will be used hereafter to represent digital products. The forms of products that can be minted into digital products include, but are not limited to: digital images (or digital pictures), audio and video, 3D (3-dimensional) models, electronic tickets, and digital souvenirs. This application does not limit the form of products minted into digital products. Digital products stored on the blockchain possess characteristics such as immutability and non-copyability, giving them unique value compared to physical products. For example, digital certificates corresponding to digital products can be stored on the blockchain, ensuring the digital product's permanent preservation as long as the blockchain exists, preventing tampering and duplication. Furthermore, the digital form of digital products on the blockchain facilitates their portability and dissemination by the owner.

[0081] In practical applications, interoperability (or target operation) can be performed on digital products within a blockchain network, including but not limited to: the creation and transfer of digital products. The creation of a digital product refers to: using blockchain technology to encrypt the digital product, giving it a unique digital certificate (or serial number, blockchain number, etc.) that serves as proof of ownership. This digital certificate is then stored on the blockchain, thus enabling the digital product to be listed on the chain. The transfer of a digital product refers to the process of transferring a digital product from its current holder to another object, granting that new object the right to operate on the product. For example, if the current holder of the digital product is the target object (such as any object), then when the target object transfers the digital product to a reference object (such as another object different from the target object), it is essentially transferring the right to operate on the digital product (such as selling, displaying, etc.) from the target object to the reference object. After the transfer, the reference object has the right to operate on the digital product.

[0082] As described above, smart contracts deploy protocol specifications in code form on a blockchain network. This allows target objects to access NFT smart contracts on the blockchain network through decentralized applications (DApps) (such as NFT wallets), enabling them to perform target operations such as minting or transferring digital products (or digital assets). Specifically, NFT smart contracts conform to NFT smart contract interface protocol standards (such as ERC721 or ERC1155) to facilitate third-party services (such as NFT exchanges) to call NFT standard interfaces, achieving interoperability for NFTs (such as NFT minting, issuance, and trading). Furthermore, digital assets are locked in the form of tokens under corresponding accounts on the blockchain. These tokens are associated with the NFT asset's metadata, which contains relevant information describing the NFT content, including but not limited to: storage location or historical data.

[0083] 3) Decentralized Identity (DID), also known as distributed digital identity, is essentially a set of digital identity identification and credential signing and verification protocols based on blockchain technology. It comprises two core components: Distributed Identity Identifiers (DIDs) and Verifiable Credentials (VCs). The infrastructure of distributed digital identity can be deployed in a distributed environment (such as a blockchain network), rather than a centralized environment controlled by a single organization or consortium. This enables true autonomy of identity, which can refer to the identity of a person, organization, or item. In other words, objects (or entities) possessing distributed digital identities are not limited to living beings like people or animals; they can also include other inanimate objects.

[0084] Distributed Digital Identity Identifiers (DIDs) are identifiers composed of strings (a string of characters, such as ahd21db23XX) used to represent the digital identity of a target object. They achieve global uniqueness without requiring a registration authority. An object can often possess multiple digital identities, each assigned a unique DID value and associated asymmetric keys (i.e., different public and private keys). Different digital identities are not linked, effectively avoiding the aggregation of owner identity information. Verifiable Credentials (VCs) are declaration documents formed by the credential issuer endorsing the attributes of an entity (such as a target object). Verifiable credentials can be issued by an identity owner (such as an individual or organization) or by other credential issuers. For example, a digital identity can be issued by a credential issuer, specifically by the identity endorser (credential issuer) endorsing and signing the identity owner's attribute information at the identity owner's request. It is worth noting that the attribute information of an identity owner varies depending on the identity owner and the credential generation scenario, and consequently, the verifiable credentials generated based on that attribute information also differ. For example, in the context of academic qualification verification, the identity endorser may refer to the node used by the school, and the verifiable credential may refer to the school's endorsement of the student's attribute information (such as age information, major information, academic information and institution information, etc.) to generate the student's academic certificate.

[0085] Based on the foregoing introduction to blockchain networks, digital products, and distributed digital identities, this application proposes a digital product processing solution. This solution supports expressing the identities of NFTs themselves, NFT issuers (i.e., the objects that mint NFTs), and NFT holders (i.e., objects with operational permissions for digital products; these objects may be the same as or different from the NFT issuer) through DID digital identities. The DID protocol is used to express and describe NFTs and related participants, giving blockchain digital assets both DID and NFT technical protocol attributes. This allows this solution to combine the DID protocol specification and the NFT protocol specification, enabling the implementation of all NFT technical capabilities based on the DID protocol specification, including minting, publishing, and transfer functions, representing a novel NFT implementation solution.

[0086] The general principle of this scheme can be summarized as follows: When a target object has a need to perform a target operation (such as minting or transferring) on ​​a digital product, the target object can initiate an operation request for the digital product. This operation request can then be used to obtain the target object's digital identifier, which uniquely identifies the target object, such as an identity ID, number, or nickname. Then, based on the target object's digital identifier and the operation information of the target operation carried in the operation request, a product operation credential can be generated. This credential can be used to instruct the target object to perform the target operation on the digital product. If the target object confirms the execution of the target operation indicated by the product operation credential, declaration data signed with the target object's first signature data (such as a private key) can be obtained. Upon successful verification of the declaration data using the target object's second signature data (such as a public key), the target operation is executed on the digital product to achieve the desired functionality.

[0087] In summary, the embodiments of this application introduce the DID protocol into the traditional NFT operation process, combining the advantages of both the DID and NFT protocols. This results in the following advantages for the digital product processing solutions provided in this application: ① Due to the advantages of distributed digital identity identifiers and verifiable credentials, such as international standards, strong expressive power, readability, and security, expressing and describing the identity of NFTs and related participants (such as the NFT itself, the NFT issuer, and the NFT holder) through the DID protocol allows for richer and more complete descriptions of NFTs, with better technical scalability, thus optimizing the expression and readability of NFTs. ② Implementing NFTs through DID achieves interconnection and interoperability between the two protocols. In addition to adhering to its own protocol specifications, NFTs can also achieve protocol interoperability through the DID layer protocol, resulting in better protocol compatibility and interoperability portability. Utilizing the routing and cross-chain capabilities of DID enables NFTs to support more protocol capabilities, improving the interoperability, portability, and scenario expansion capabilities of the digital asset layer, facilitating implementation in more scenarios. ③ Verifiable credentials under the DID protocol also have the ability to be signed and verified by third parties. This means that NFT implementation schemes based on DID have better regulatory capabilities. For example, the minting and transfer of DID credentials can be completed by signing and verifying by a third-party authoritative institution, which is not possible with single-layer NFT protocol implementations. Furthermore, through the high readability and traceability of Distributed Digital Identity Identifiers (DIDs), more regulatory functions can be imposed on NFTs, enabling the embodiments of this application to adapt to NFT scenarios with regulatory requirements, such as NFT implementation scenarios based on consortium blockchains.

[0088] To facilitate a better understanding of the digital product processing scheme proposed in the embodiments of this application, the following is combined with... Figure 2a An exemplary processing system for a digital product is provided; such as Figure 2a As shown, the processing system for this digital product includes a terminal device 201 and a server 202. This application embodiment does not limit the number or type of the terminal device 201 and the server 202, but this will not be discussed further. The electronic devices involved in the processing system for this digital product will be described below, wherein:

[0089] (1) Terminal device 201 may refer to a device that has deployed a distributed application (i.e., the aforementioned decentralized application DApp). The terminal device 201 may be a blockchain node device belonging to the blockchain network, or it may be a device independent of the blockchain network, but still having the blockchain in the blockchain network provide trusted data to the DApp. The terminal device 201 may include, but is not limited to: smartphones (such as Android phones, iOS phones, etc.), tablet computers, portable personal computers, mobile internet devices (MIDs), smart TVs, in-vehicle devices, head-mounted devices, etc.

[0090] The distributed application of the digital product deployed in terminal device 201 is an application client used by the target object to send operation requests regarding the digital product. This application embodiment does not limit the operation mode of the distributed application; for example, the distributed application may be a client deployed on terminal device 201 via an installation package; or it may run on the terminal device as an online application; or it may run as a mini-program among other applications deployed on the terminal device.

[0091] The following functions can be achieved through distributed applications deployed on terminal devices, but are not limited to:

[0092] ① Generate and save the public and private keys of the target object. The public and private keys include a public key and a private key. They are a key pair. If the encryptor uses the target object's private key to encrypt data, the decryptor can only obtain the decrypted data by using the public key corresponding to the target object's private key. In other words, the distributed application has the ability to generate public and private keys for the target object and save them after generation.

[0093] ② Receive and save the digital identifier of the target object. Here, the digital identifier refers to the Distributed Digital Identifiers (DIDs) described above, and will not be further distinguished. In other words, the distributed application deployed in the terminal device can also receive the digital identifier of the target object and save the received digital identifier.

[0094] ③ Generate and save the target object's product operation credentials. These credentials may refer to the aforementioned verifiable credentials (VCs), which will not be distinguished further. The verifiable credentials (VCs) will differ depending on the operation the target object wants to perform on the digital product. For example, in a scenario where the target object wants to mint a digital product, minting a digital product can be simply understood as the process of generating a digital product and putting it on the blockchain. The generated verifiable credential in this case indicates that the digital product requests a minting operation, i.e., a request to mint a digital product. As another example, in a scenario where the target object wants to transfer a digital product, transferring minted digital products can be simply understood as the process of transferring the operation rights of the digital product from one object to another. The generated verifiable credential in this case indicates that the digital product requests a transfer operation, i.e., a request to transfer the digital product.

[0095] (2) Server 202 can refer to a device with the function of realizing interoperability (such as minting or transferring) of digital products; server 202 is a blockchain node device in a blockchain network. Server 202 deploys a DID-based NFT protocol model innovatively proposed in this application embodiment, which can also be called a blockchain application protocol model; the server specifically realizes interoperability of digital products through this blockchain application protocol model. See also Figure 2b This blockchain application protocol model, from top to bottom, includes: the NFT protocol layer, the DID protocol layer, and the blockchain network. Each protocol layer can include corresponding application layers and smart contracts. For example, the NFT protocol layer includes an NFT application layer and NFT smart contracts; similarly, the DID protocol layer includes a DID application layer and DID smart contracts. The following section will combine... Figure 2b The functions of applications and smart contracts in the protocol layer are introduced separately.

[0096] The NFT protocol layer comprises the NFT application layer and NFT smart contracts. The functions of the NFT application layer and NFT smart contracts are briefly introduced below. Specifically:

[0097] ① The NFT application layer can be used to process operation requests sent by terminal devices. For example, operation requests may include entity digital identifier registration requests. In this case, the NFT application layer can uniformly process entity DID identifier registration requests from the NFT application side (such as the NFT wallet in the terminal device). Specifically, in response to the DID identifier registration request, it calls the DID protocol layer, such as calling the DID application layer or the DID smart contract, to complete the generation and registration of the target object's digital identifier (or simply digital identifier). In addition, the registered digital identifier is also bound to the target object's public key. Thus, the public key bound to the digital identifier, as well as asymmetric encryption technology, can be used to verify whether the operator on the NFT application side is the target object of the corresponding digital identifier, thereby achieving identity verification of the target object and improving the security of data processing.

[0098] After registering and obtaining the digital identifier of the target object, the NFT application layer can allocate the digital identifier of the target object to the terminal device (i.e., the NFT application client). This allows the target object to initiate operation requests (or NFT operation requests) related to the digital product through the NFT application client (i.e., the aforementioned DApp) based on the digital identifier. The NFT application layer then processes these NFT operation requests, such as minting and transferring. For example, in an NFT minting scenario, the NFT application layer can directly generate the DID identifier corresponding to the token (i.e., the digital product) in the DID smart contract by calling the DID application layer (to easily distinguish the DID identifier of the target object from the DID identifier of the digital product, the DID identifier of the digital product is referred to as the product identifier). Alternatively, the NFT application layer can indirectly generate the DID identifier corresponding to the token in the DID smart contract through the NFT smart contract. For example, in NFT transfer scenarios, the NFT application layer can directly verify the verifiable credentials (VCs) corresponding to the target object by calling the DID application layer, or the NFT application layer can indirectly verify the verifiable credentials (VCs) corresponding to the target object through NFT smart contracts to check whether the target object has the same operation permission to perform the same operation on the digital product, such as checking whether the target object has the transfer permission to transfer the digital product, or checking whether the target object has the minting permission to mint the digital product.

[0099] ② NFT smart contracts are used to process and manage data related to digital products. For example, an NFT smart contract stores the binding relationship between the digital identifier of a target object and the product identifier of a digital product, used to anchor the ownership of the digital product. For instance, if there is a binding relationship (or binding mapping relationship) between the product identifier of digital product A and the digital identifier of target object a, this binding relationship anchors the holder of digital product A as target object a. Therefore, the holder of digital product A is determined to be target object a based on this binding relationship. To enhance the credibility of smart contracts, NFT smart contracts can directly call DID smart contracts to generate the DID identifier of digital products, and directly call DID smart contracts to verify verifiable credentials (VCs). After successful verification of the verifiable credentials (VCs), corresponding target operations can be performed on the digital product, such as modifying the binding relationship between the digital identifier of the target object and the product identifier of the digital product to complete the transfer of the digital product.

[0100] Similar to the NFT protocol layer, the DID protocol layer includes the DID application layer and DID smart contracts. The functions of the DID application layer and DID smart contracts are briefly introduced below. Specifically:

[0101] ① The DID application layer can be used to process operation requests sent by the NFT application layer above it in the protocol model (such as requests to create digital identifiers or verify credentials), and to connect downwards in the protocol model to read and write DID state data to the DID smart contract. In other words, as an intermediate layer, any business logic that needs to be processed in the DID smart contract can enter the DID smart contract through the DID application layer as a service entry point.

[0102] The DID status data includes, but is not limited to, the data contained in the DID document of the target object and the data contained in the DID document of the digital product. The DID document of the target object can be obtained by parsing the digital identifier of the target object through a DID smart contract. Similarly, the DID document of the digital product can be obtained by parsing the product identifier of the digital product through a DID smart contract. In other words, each DID identifier corresponds to its own DID document, and the DID document of any entity is used to describe and express the content of that entity. For example, if the entity is a target object, then the document data contained in the target object's DID document may include information related to the target object, including but not limited to: the target object's public key and attribute information (such as age, nickname, gender, or registration time). As another example, if the entity is a digital product, then the document data contained in the digital product's DID document may include information related to the digital product, including but not limited to: the digital product's attribute information (such as the digital product's form information, minting time, etc.) and metadata such as digital content (such as the element information contained in the digital product), used to express all or part of the information of the NFT entity (i.e., the digital product).

[0103] ② DID smart contracts can be used to process and manage DID-related data. For example, a DID smart contract stores all state data of the DID, including the DID document of the target object and the digital product, specifically the document data contained in the DID document. In different application scenarios involving digital products (such as the minting or transferring of digital products), the DID state data in the DID smart contract can be read and written through the DID application layer and NFT smart contracts. Additionally, DID smart contracts also include a contract interface for verifying verifiable credentials. By calling this interface, the DID smart contract can verify whether the signed verifiable credential was issued by the corresponding DID entity (such as the target object signed with a private key).

[0104] The protocol mapping relationship between the NFT smart contract and the DID smart contract provided in this application embodiment can be found in [reference needed]. Figure 2c .like Figure 2cAs shown, the NFT smart contract stores the digital identifier of the target object (the DID identifier of the target object) and the product identifier of the digital product (the DID identifier of the NFT token). Furthermore, the NFT smart contract also stores the binding mapping relationship between the digital identifier of the target object and the product identifier of the digital product. This binding mapping relationship can identify the holder of the digital product as the target object. The DID smart contract stores the DID document of the target object, which is obtained by parsing the digital identifier of the target object. This can be understood as a binding relationship between the object identifier and the DID document of the target object. Similarly, the DID smart contract stores the DID document of the digital product, which is obtained by parsing the product identifier of the digital product. This can be understood as a binding relationship between the product identifier and the DID document of the digital product. Furthermore, the DID document of a digital product in a DID smart contract also includes a controller field. This controller field can be used to identify the target object to which the digital product belongs. Specifically, the controller field is assigned a digital identifier of the target object, indicating that the target object is the owner of the digital product, that is, the target object has the operation permission to interoperate with the digital product.

[0105] To enable the processing of digital products using both protocols, the DID and NFT protocols need to be designed. The goal is to determine the mapping (or correspondence) between fields in the DID and NFT protocols, such as assigning values ​​to certain fields, so that the content of the other protocol can be identified based on a field in either protocol. For example, after obtaining a DID document, its fields can be used to determine that the DID document is a product document for a digital product.

[0106] The schematic diagram of the NFT protocol design based on the DID protocol provided in this application embodiment can be found in [reference needed]. Figure 2d The following is combined with Figure 2d The following is a brief introduction to several exemplary protocol designs given in the embodiments of this application, which does not limit the embodiments of this application. The following specifications may be defined in the DID-based NFT protocol design, but are not limited to:

[0107] ① It supports the generation of the first and second signature data of the target object by the object side (i.e., the terminal device used by the target object). For example, the object side generates public and private keys based on asymmetric cryptography algorithms, with the first signature data being the public key and the second signature data being the private key. It also supports the application protocol model (i.e., the aforementioned blockchain application protocol model) to transcode the public key of the target object into a digital identifier of the target object according to the DID specification and register it on the blockchain.

[0108] ② Supports the creation of product identifiers for digital products obtained through casting. That is, the digital products generated by casting also have DID identity identifiers, and these DID identity identifiers correspond to DID documents (i.e., the aforementioned product documents) used to describe and express the digital product content in the NFT protocol standard.

[0109] ③ It supports assigning the product identifier of the digital product to the service field (such as the service field) in the DID document corresponding to the digital product, so that the metadata of the digital product can be accessed through the product identifier. That is, the metadata of the digital product can be accessed through this field. For example, if the digital product is a digital image, the service field of the digital product can be assigned the resource identifier (URI) of the digital product to enable access to the metadata of the digital product through the URI of the digital product.

[0110] The metadata of digital products can be stored in the digital product distribution platform gateway. The metadata stored in the digital product distribution platform gateway can be accessed through the digital identifier of the digital product. The metadata contains the attribute information of the digital product NFT, which can be stored in various storage services such as decentralized storage or object storage in JSON format. The metadata also stores the access path of the visual presentation file of the NFT (such as a digital image).

[0111] ④ It supports binding the controller field in the DID document corresponding to a digital product to the digital identifier of the target object, indicating the subordinate relationship between the product identifier of the digital product and the digital identifier of the target object, that is, the owner of the digital product is the target object. Furthermore, the state data of the DID document (i.e., the data contained in the DID document) can be persisted on the blockchain, ensuring the immutability of the data.

[0112] ⑤ If the target object wants to perform interoperability on digital products that includes transferring digital products, then in scenarios where the holder of the digital product (such as the target object) transfers the digital product, a transfer validity period can be set for the verifiable certificate (or product transfer certificate) issued by the holder of the digital product. Therefore, the claim statement for the product transfer certificate needs to include the digital identifier of the reference object to which the digital product will be received and the product identifier of the digital product; furthermore, the product transfer certificate must be signed by the target object (i.e., the holder). Of course, other custom transfer conditions can also be included in the claim statement according to business needs. The specific information configured in the claim statement can be flexibly configured and expanded according to the application scenario, and is not limited here.

[0113] It should be noted that, as can be seen from the above introduction to blockchain application protocol models, different blockchain networks (such as...) Figure 2b The blockchain networks A and B shown can mask the differences between the underlying blockchain networks through the DID protocol layer. The NFT protocol layer is built on top of the DID protocol layer, meaning it can call the underlying DID protocol layer. This allows NFT assets to achieve interoperability between different smart contracts or different blockchain networks based on the Decentralized Identifier (DIDs) and Verifiable Credentials (VCs) protocols of the DID protocol. Furthermore, it provides standard blockchain identity layer protocol support for the NFT protocol, enhancing the account and asset security and self-control capabilities of NFT implementations based on consortium blockchains.

[0114] It should also be noted that this application embodiment also supports integrating application layer functions into smart contracts. Thus, the NFT protocol layer and DID protocol layer in the blockchain application protocol model can include only smart contracts, without additional application layers. Furthermore, in addition to terminal device 201 and server 202, the digital product processing system involved in this application embodiment can also include only a server. In this implementation, distributed applications can be deployed on the server. This application embodiment does not limit the type and number of devices included in the digital product processing system, as stated here. Additionally, when this application embodiment is applied to specific products or technologies, such as obtaining the digital identifier of a target object, permission or consent from the target object is required. Moreover, the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, interoperability performed on digital products must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0115] Based on the digital product processing scheme described above, this application proposes a more detailed digital product processing method. The processing method proposed in this application will be described in detail below with reference to the accompanying drawings.

[0116] Figure 3 This application illustrates a flowchart of a digital product processing method according to an exemplary embodiment; the digital product processing method can be provided by... Figure 2a The server in the system shown executes this process, which may include, but is not limited to, steps S301-S304:

[0117] S301: When a target object receives an operation request for a digital product, obtain the target object's digital identifier.

[0118] In practice, when a target object needs to perform a target operation on a digital product, the target object initiates an operation request through its electronic device. This operation request carries the operation information of the requested target operation. Then, in response to the operation request, the target object's digital identifier can be obtained. The operation information varies depending on the target operation. For example, a target operation on a digital product may include, but is not limited to, casting or transfer operations. When the target operation is casting, the operation information includes at least: product casting information required for casting the digital product (such as element information of the various elements contained in the digital product), the digital identifier of the owner of the cast digital product, etc. When the target operation is transfer, the operation information includes at least: the digital identifier of the reference object to receive the digital product, the digital identifier of the holder of the digital product before it is transferred, etc.

[0119] As described above, the terminal device held by the target object and the execution entity server in this application embodiment can be the same electronic device or different electronic devices. Depending on the system involved in this application embodiment, the electronic device generating the operation request can be either the terminal device or the server. Specifically, it can be an electronic device with the function of calling a third-party organization to generate verifiable credentials to generate the operation request. Optionally, the terminal device and the server are different electronic devices. The target object can initiate an operation on its terminal device, allowing the terminal device to generate an operation request based on the detected initiation operation. Furthermore, provided the server calls a third-party organization to generate a product operation credential, the terminal device sends the operation request to the server, enabling the server to respond to the operation request by performing an operation to obtain the target object's digital identifier. Of course, if the terminal device has the ability to call a third-party organization to generate a product operation credential, the terminal device can directly respond to the operation request by generating the product operation credential after generating the operation request, without needing to send the operation request to the server. Optionally, the terminal device and the server are the same electronic device. The target object can initiate an operation for a digital product on the server, allowing the server to generate a corresponding operation request based on the detected initiation operation and respond to the operation request by performing an operation to obtain the target object's digital identifier. The specific electronic device used to generate the operation request in this application embodiment is not limited to a terminal device or a server, and is not specified here.

[0120] It is understandable that the specific implementation process of the initiation operation performed by the target object varies depending on the target operation that the target object intends to perform on the digital product. For example, if the target operation that the target object wants to perform on the digital product is a casting operation, the initiation operation performed by the target object in the electronic device may include: inputting the product casting information required for casting the digital product into the display screen (or simply display, screen, etc.) provided by the electronic device. As another example, if the target operation that the target object wants to perform on the digital product is a transfer operation, the initiation operation performed by the target object in the electronic device may include: inputting the product identifier of the digital product to be transferred, and the digital identifier of the reference object to be received, etc., into the display screen provided by the electronic device. The above are merely exemplary processes for two initiation operations given in the embodiments of this application. When the target operation is other operations, the initiation operation performed by the target object may also undergo adaptive changes, which are not limited in this embodiment.

[0121] Furthermore, upon receiving an operation request from the target object regarding a digital product, the process of obtaining the target object's digital identifier in response to the operation request may include: retrieving the target object's digital identifier from storage space, or generating the target object's digital identifier and registering it on the blockchain. In other words, if the target object's digital identifier has already been generated before receiving the operation request, it can be directly retrieved from storage space upon receiving the request. Specifically, it can be retrieved from a list of digital identifiers stored in storage space. The digital identifiers in storage space may be stored there after the DID smart contract generates them; or they may be distributed and stored in storage space when other blockchain nodes register the target object's digital identifier on the blockchain. Conversely, if the target object's digital identifier has not been generated or registered before receiving the operation request, it can be generated and registered based on the operation request to obtain the target object's digital identifier.

[0122] The digital identifier of the target object can be generated based on the object information of the target object, which may include, but is not limited to, the target object's attribute information (such as nickname, ID number, etc.) or the target object's public key. Specifically, the process of generating the digital identifier of the target object may include: first obtaining the object information of the target object, and then converting the object information into the target object's digital identifier. For example, assuming that the object information of the target object includes the target object's public key, the public key can be converted into a digital identifier according to the DID specification, and the generated digital identifier can be registered on the blockchain to obtain the target object's digital identifier.

[0123] Depending on whether the target object's digital identifier is generated before or after receiving the operation request, the process for generating the target object's digital identifier differs, including:

[0124] In one implementation, assuming the target object's digital identifier is generated before receiving an operation request from the target object for a digital product, the generation process of the target object's digital identifier may include: when the target object needs to register an identifier, it can initiate an identifier registration request, which carries the target object's object information; upon receiving the identifier registration request from the target object, the object information can be converted into the target object's digital identifier in response to the request. Then, the target object's digital identifier is registered on the blockchain, enabling all blockchain nodes in the blockchain network to synchronize with the target object's digital identifier, achieving distributed storage of the target object's digital identifier; thus, any subsequent blockchain node in the blockchain network that needs to obtain the target object's digital identifier can directly synchronize it from the blockchain. This method of pre-registering the target object's digital identifier on the blockchain can, to some extent, improve the speed and efficiency of subsequent digital product generation.

[0125] In other implementations, assuming that the digital identifier of the target object is generated after receiving an operation request from the target object for the digital product, the generation process of the digital identifier of the target object may include: upon receiving an operation request and detecting that the digital identifier of the target object does not exist, returning an information retrieval request (such as returning an information retrieval request to the terminal device held by the target object), the information retrieval request is used to request the object information of the target object; receiving the object information of the target object returned by the response information retrieval request, and converting the object information into the digital identifier of the target object.

[0126] It should be understood that the above are only two exemplary processes for generating digital identifiers of target objects; the process for generating digital identifiers of target objects may change in actual applications, which is explained here.

[0127] S302: Generate product operation credentials based on the digital identifier and operation information of the target object.

[0128] S303: If the target object confirms that the target operation is performed on the digital product, then the first signature data of the target object is obtained, and the declaration data obtained by performing signature processing on the product operation certificate is obtained.

[0129] In steps S302-S303, after determining the target operation that the target object wants to perform on the digital product based on the operation request from the target object, a product operation credential can be generated based on the target object's digital identifier and the operation information of the target operation. This product operation credential is similar to a digital certificate, used to indicate that the digital product is requested to perform the target operation, and also to indicate that the requester of the target operation is the target object. The product operation credential can be generated by the terminal device held by the target object. In this case, the terminal device can generate the product operation credential based on the operation information of the target operation requested in the operation request and the target object's digital identifier, and send the product operation credential to the server. Alternatively, the product operation credential can also be generated by the server. In this case, when the server receives the operation request, it can generate the product operation credential based on the obtained target object's digital identifier and the operation information of the target operation.

[0130] It should be noted that the embodiments of this application do not limit the electronic device that generates the product operation certificate; for example, when the distributed application is deployed on a server, the target object can directly perform operations on the server, and in this case, the processing system does not need to include a terminal device, so the product operation certificate is generated by the server. For ease of explanation, the following description will take the generation of product operation certificates by a terminal device with a distributed application (DAPP) deployed on it as an example.

[0131] Furthermore, the target object can obtain a product operation credential. For example, the server returns the product operation credential to the terminal device held by the target object, allowing the target object to obtain the credential through the terminal device. Alternatively, the terminal device can generate and output the product operation credential for the target object to view. After obtaining the product operation credential, the target object can view the information contained within it. If the target object confirms to perform the target operation indicated by the product operation credential on the digital product, it can sign the product operation credential using its first signature data. For example, it can digitally sign the product operation credential using its first signature data to generate declaration data; here, the target object's first signature data can refer to the target object's private key. Finally, the target operation is performed on the digital product based on the declaration data signed by the target object, as detailed in step S304. In the above implementation process, the target object's first signature data is used to sign the product operation credential only when the target object confirms to perform the target operation on the digital product. This indicates that the target operation is performed on the digital product based on the target object's permission, ensuring the security of operating the digital product.

[0132] It should be noted that when the product operation credential is generated by a terminal device with a deployed distributed application (DApp), the target object can use the distributed application to sign the product operation credential using its own first signature data (such as a private key) to generate claim data; and then send the claim data to the server so that the server can perform target operations on the digital product based on the claim data. Optionally, the target object can directly use its own first signature data to sign the product operation credential to generate claim data. Optionally, the target object can also authorize the terminal device to obtain the target object's first signature data and use the first signature data to sign the product operation credential to generate claim data.

[0133] When product operation credentials are generated by the server, and if the server is deployed with a distributed application, depending on whether the terminal device held by the server and the target object is the same or a different electronic device, the server can obtain the claim data in any of the following ways:

[0134] In one implementation, the terminal device and the server are different electronic devices. Optionally, the server can send the product operation certificate to the terminal device held by the target object, and then the terminal device returns declaration data after the target object has signed the product operation certificate using the first signature data. Specifically, after the server generates the product operation certificate based on the target object's digital identifier and the operation information of the target operation, it can send the product operation certificate to the target object, specifically to the terminal device held by the target object; so that the terminal device outputs the product operation certificate on its display screen, such as... Figure 4 As shown. The target object can visually view the information contained in the product operation certificate on the display screen. When confirming the execution of the target operation indicated by the product operation certificate on the digital product, the target object, either directly or through an authorized terminal device, uses the target object's first signature data to sign the product operation certificate to obtain declaration data. Then, the terminal device returns the signed declaration data to the server. In this way, the server can directly receive the declaration data from the terminal device.

[0135] Optionally, the server can also generate an authorization request based on the product operation credential. This authorization request carries the product operation credential and is used to request the target object's authorization server to sign the product operation credential. The authorization request is then sent to the terminal device. In response to the received authorization request, the terminal device outputs the product operation credential. If the target object confirms that the information contained in the product operation credential is correct and agrees to the authorization server's signing process, the terminal device returns confirmation information. This confirmation information instructs the target object's authorization server to sign the digital product using the first signature data. Thus, the server can obtain the target object's first signature data based on the confirmation information and sign the product operation credential based on the first signature data to obtain the declaration data.

[0136] In other implementations, the terminal device and the server are the same electronic device, i.e., the server has a distributed application deployed in it. In this implementation, the server can output the product operation certificate on the display screen. If the target object signs the product operation certificate with the first signature data, the signed product operation certificate is obtained in response to the target object's signing operation with the first signature data. The signed product operation certificate is used as the declaration data.

[0137] As described above, the process of signing a digital product using the target object's first signature data can be performed directly by the target object or by the target object's authorization server. Optionally, the target object can use the first signature data to sign a product operation credential to obtain declaration data. That is, in response to the target object's signing operation on the product operation credential using the target object's first signature data, the server can obtain a signed product operation credential, which serves as the declaration data. Optionally, the server can also receive an authorization operation from the target object regarding the product operation credential, obtain the target object's first signature data, and then perform signing processing on the product operation credential based on the target object's first signature data to obtain a signed product operation credential, which serves as the declaration data.

[0138] Through the above implementation process, the target object can obtain product operation credentials to instruct the execution of target operations on the digital product. By using these product operation credentials to express and describe the digital product using the DID protocol, the expression and readability of the digital product are optimized. This allows the target object to clearly understand the target operation to be performed on the digital product based on the product operation credentials, thus improving the target object's experience. Furthermore, with the support of the DID protocol, more application functions can be applied to the digital product, enriching the application scenarios of the digital product.

[0139] S304: Perform target operations on digital products based on claimed data.

[0140] As described above, the declaration data is obtained by signing the product operation certificate using the first signature data of the target object (such as the private key of the target object). After the server obtains the declaration data, it still needs to verify the signature of the declaration data. When the signature of the declaration data is successfully verified, it means that the identity of the entity that wants to perform the target operation has been successfully verified, and the target operation can be performed on the digital product.

[0141] In specific implementation, the process of performing the target operation on a digital product based on the declared data may include: First, since the target object's digital identifier (i.e., DID identifier) ​​is bound to the target object's second signature data (such as the target object's public key), the target object's second signature data can be obtained based on the target object's digital identifier. Then, the target object's second signature data is used to verify the declared data, obtaining the verification result. Finally, if the verification result is successful, it indicates that the identity verification of the operator on the terminal device side is successful, and the target operation is performed on the digital product; conversely, if the verification result is unsuccessful, it indicates that the identity verification of the operator on the terminal device side has failed, and the target operation is not performed on the digital product.

[0142] In the above implementation process, when the first signature data of the target object is the private key of the target object, the second signature data of the target object is the public key of the target object, and the public key is different from the private key, the embodiments of this application use asymmetric encryption technology to verify whether the operator of the terminal device is the target object corresponding to the digital identifier recorded in the product operation certificate, thereby realizing the verification of the identity of the operator on the terminal device side, thereby realizing transaction permission verification before performing target operations on digital products, improving the security and traceability of digital products, and being applicable to application scenarios with review requirements, such as consortium blockchain scenarios.

[0143] In this embodiment, upon receiving an operation request from a target object to perform on a digital product, a product operation credential can be generated based on the target object's digital identifier and the operation information carried in the operation request. This product operation credential indicates that the digital product is requested to perform a target operation, and that the requester of the target operation is the target object. By generating a product operation credential for the digital product, the target object can be intuitively informed of relevant information about the digital product, optimizing the expression and readability of the digital product. Furthermore, the target operation is only performed on the digital product when the target object confirms the execution of the target operation, i.e., obtains the declaration data (i.e., the product operation after signature processing), and the signature verification of the declaration data is successful. This improves the security and traceability of the digital product, thereby efficiently realizing the target operation on the digital product.

[0144] As described above, the digital product processing system involved in this application embodiment may include a terminal device and a server. The terminal device deploys a distributed application (DAPP or NFT APP), or the digital product processing system may only include a server, on which a distributed application is deployed. The following description focuses on the specific implementation process of performing target operations on digital products, using a digital product processing system including both a terminal device and a server as an example. It is easy to understand that the types of target operations performed on digital products are quite diverse. The following description, in conjunction with the accompanying drawings, uses the operation of casting a digital product and the operation of transferring a digital product as examples to introduce the specific implementation process of the target operation.

[0145] like Figure 5 This illustration shows an exemplary flowchart of a digital product processing method provided in an embodiment of this application, where the target operation is casting a digital product; this digital product processing method can be... Figure 2a The terminal devices and server in the system shown work together to execute this processing method, which may include, but is not limited to, steps S501-S509:

[0146] S501: The terminal device sends the identifier registration request to the server.

[0147] S502: The server responds to the identifier registration request, generating and registering the digital identifier of the target object.

[0148] S503: The server assigns the digital identifier of the target object to the terminal device.

[0149] In steps S501-S503, when the target object has a need to generate and register a digital identifier, the target object can generate an identifier registration request through a terminal device, specifically through a distributed application deployed on the terminal device. Then, the terminal device sends the identifier registration request to the server, where the NFT application layer in the blockchain application protocol model deployed on the server receives the identifier registration request. Subsequently, the NFT application layer calls the DID application layer, which in turn calls the DID smart contract to respond to the identifier registration request, generating the target object's digital identifier and registering it on the blockchain.

[0150] It should be noted that the specific implementation process of the server generating and registering the digital identifier of the target object in response to the identifier registration request can be found in [the relevant documentation / information]. Figure 3 The specific implementation process shown in step S301 of the illustrated embodiment will not be repeated here.

[0151] S504: The terminal device generates a product operation certificate and signs the product operation certificate according to the first signature data to generate declaration data.

[0152] In scenarios where the target operation performed on a digital product is the casting of the digital product, the product operation certificate generated by the terminal device can be referred to as the product casting certificate, as explained here.

[0153] In practical implementation, if the target object has a need to cast digital products, the terminal device can generate an operation request in response to this need. This operation request is used to request the casting of the digital product; that is, the target operation for the digital product is the casting of the digital product. The operation information for the target operation includes at least the product casting information required for casting the digital product. For example, if the digital product is a digital image, the product casting information required for casting the digital image may include the element information of each element that makes up the digital image (such as element addresses or element layers). Then, in response to the operation request, the terminal device generates a product casting certificate based on the target object's digital identifier and the operation information of the target operation. Finally, the product casting certificate is signed based on the target object's first signature data to generate declaration data.

[0154] As mentioned above Figure 3 As described in the illustrated embodiment, if the product casting certificate is generated by the server, such as when the server calls a third-party authoritative institution to generate the product casting certificate, the terminal device can send an operation request to the server, and the server will respond to the operation request to generate the product casting certificate. The specific implementation process of the server generating the product casting certificate is not limited here.

[0155] S505: The terminal device generates a casting request based on the product operation certificate and sends the casting request to the server. The casting request carries the signed product operation certificate (i.e., declaration data).

[0156] S506: The server responds to the casting request and verifies the declaration data.

[0157] In steps S505-S506, when the server receives the casting request, it also receives the declaration data carried by the casting request. The server can then perform signature verification on the declaration data based on the digital identifier of the target object. Specifically, the digital identifier of the target object is bound to the public key of the target object. In this way, the server can obtain the public key of the target object and perform signature verification on the declaration data based on the public key of the target object to obtain the signature verification result.

[0158] S507: If the signature verification is successful, the server creates a product identifier for the digital product.

[0159] S508: The server binds the product identifier of the digital product and the digital identifier of the target object.

[0160] In steps S507-S508, when the declaration data is successfully verified based on the second signature data of the target object, it indicates that the identity verification of the entity on the terminal device side is successful. That is, the entity on the terminal device side is the target object that digitally signs the product casting certificate using the first signature data, and then the target operation for the digital product can be executed.

[0161] Among them, the specific implementation process of performing the target operation on the digital product, where the target operation is the casting of the digital product, can be as follows: Figure 6 As shown, the specific process may include: First, based on the product casting information required for casting the digital product, the digital product is cast. For example, if the digital product is a digital image, and the product casting information required for casting the digital product consists of element images belonging to different layer levels, then the various element images are superimposed in order of layer level from high to low (or from low to high) to cast the digital image. Then, the server can create a product identifier for the cast digital product based on the DID smart contract in its deployed blockchain application protocol model. This product identifier is the DID identifier of the digital product NFT, used to uniquely identify the digital product. Finally, the product identifier of the digital product and the digital identifier of the target object can be bound together, creating a mapping relationship between them. This mapping relationship can be stored in the NFT protocol layer of the blockchain application protocol model, specifically in the NFT smart contract within the NFT protocol layer. Through this binding mapping relationship, the owner of the digital product can be determined as the target object, meaning the target object is the only object with the permission to operate on the digital product.

[0162] The specific implementation process of binding digital products and target objects may include: establishing a first mapping binding relationship based on the digital identifier of the target object and the product identifier of the digital product. This first mapping binding relationship may refer to the mapping binding relationship mentioned above, which is used to indicate that the holder of the digital product is the target object; then, storing the first mapping binding relationship in the smart contract corresponding to the digital product, i.e., the NFT smart contract, to realize the binding of the digital product and the target object.

[0163] S509: The server returns the casting results for the digital product to the terminal device.

[0164] In a specific implementation, the server can return the casting results for digital products to the terminal device. The casting results for digital products may include: the cast digital product (such as a digital image) and the results of the digital product being put on the blockchain (such as successful blockchain upload). This application embodiment does not limit the specific content included in the casting results.

[0165] In this embodiment, upon receiving an operation request from a target object to perform on a digital product, a product operation credential can be generated based on the target object's digital identifier and the operation information carried in the operation request. This product operation credential indicates that the digital product is requested to perform a target operation, and that the requester of the target operation is the target object. By generating a product operation credential for the digital product, the target object can be intuitively informed of relevant information about the digital product, optimizing the expression and readability of the digital product. Furthermore, the target operation is only performed on the digital product when the target object confirms the execution of the target operation, i.e., obtains the declaration data (i.e., the product operation after signature processing), and the signature verification of the declaration data is successful. This improves the security and traceability of the digital product, thereby efficiently realizing the target operation on the digital product.

[0166] Figure 7 This illustration shows an exemplary flowchart of a digital product processing method provided by an embodiment of this application, where the target operation is to transfer the operation of a digital product; this digital product processing method can be provided by... Figure 2a The terminal devices and server in the system shown work together to execute this processing method, which may include, but is not limited to, steps S701-S706:

[0167] S701: The terminal device generates a product operation certificate and signs the product operation certificate according to the first signature data to generate declaration data.

[0168] In scenarios where the target operation performed on a digital product is to transfer the digital product, the product operation certificate generated by the terminal device can be called a product transfer certificate, as explained here.

[0169] In practice, if the target object has a need to transfer digital products, the terminal device can generate an operation request in response to this request. This operation request requests the transfer of the digital product from the target object to a reference object; in other words, it changes the holder of the digital product from the target object to the reference object. The target object and the reference object are different. Therefore, the target operation for the digital product is a transfer operation, and the operation information for this target operation includes at least: the digital identifier of the reference object and the product identifier of the digital product to be transferred. Then, in response to the operation request, the terminal device generates a product transfer certificate based on the digital identifier of the target object and the operation information of the target operation. Finally, it signs the product transfer certificate based on the first signature data of the target object, generating declaration data.

[0170] As mentioned above Figure 3As described in the illustrated embodiment, if the product transfer certificate is generated by the server, such as when the server calls a third-party authoritative institution to generate the product transfer certificate, the terminal device can send an operation request to the server, and the server will respond to the operation request by calling the third-party institution to generate the product transfer certificate; the specific implementation process of the server generating the product transfer certificate is not limited here.

[0171] S702: The terminal device generates a transfer request based on the product transfer certificate and sends the transfer request to the server. The transfer request carries the signed product transfer certificate (i.e., declaration data).

[0172] S703: The server responds to the transfer request and performs signature verification on the declared data.

[0173] In steps S702-S703, when the server receives the transfer request, it also receives the declaration data carried by the transfer request. The server can then perform signature verification on the declaration data based on the digital identifier of the target object. Specifically, the digital identifier of the target object is bound to the public key of the target object. In this way, the server can obtain the public key of the target object and perform signature verification on the declaration data based on the public key of the target object to obtain the signature verification result.

[0174] S704: If the signature verification is successful, the server modifies the digital identifier of the target object in the product document of the digital product.

[0175] S705: The server modifies the binding mapping relationship between the product identifier of a digital product and the digital identifier of a target object.

[0176] In steps S704-S705, when the verification of the declaration data based on the second signature data of the target object is successful, it indicates that the identity verification of the entity on the terminal device side is successful. That is, the entity on the terminal device side is the target object that digitally signed the product casting certificate using the first signature data, and then the target operation for the digital product can be executed. The specific implementation process of executing the target operation on the digital product, which is the operation of transferring the digital product, can be as follows: Figure 8 As shown, the specific process may include:

[0177] First, the product identifier of the digital product is parsed. The product identifier of the digital product is created when the digital product is manufactured, and the corresponding product document (i.e., DID document) is obtained. The product document stores the metadata of the digital product. The metadata includes the storage location of the content of the digital product (such as appearance attribute description file, pictures, etc.). The product document also includes a controller field, which records the digital identifier of the target object, indicating that the owner of the digital product is the target object corresponding to the digital identifier recorded in the controller field.

[0178] Then, perform the following two operations, in any order, to transfer the digital product from the target object to the reference object. Specifically, this involves transferring the access permissions for the digital product from the target object to the reference object, including:

[0179] ① In the product documentation, modify the digital identifier of the target object recorded in the controller field to the digital identifier of the reference object to which the digital product is to be received. ② As described above, the NFT smart contract in the blockchain application protocol model deployed on the server stores a first mapping binding relationship, which binds the product identifier of the digital product to the digital identifier of the target object. Therefore, in the smart contract corresponding to the digital product (i.e., the NFT smart contract), the first mapping binding relationship can be modified to a second mapping binding relationship; wherein, the first mapping binding relationship indicates that the holder of the digital product is the target object, and the second mapping binding relationship indicates that the holder of the digital product is the reference object.

[0180] Through the above process, the transfer operation of digital products can be realized, and the operation permissions for digital products can be transferred from the target object to the reference object.

[0181] Furthermore, as described above, in scenarios where the holder of a digital product transfers the digital product, the holder needs to issue a product transfer certificate for verification of the change of holder. This application embodiment also supports setting a transfer validity period for the product transfer certificate, meaning the product operation certificate (or signed declaration data) has a time limit. Only within the transfer validity period can the verification of the product transfer certificate and subsequent transfer operations be performed. Specifically, when digitally signing the product transfer certificate using the target object's first signature data, a transfer validity period can be set for the generated declaration data. This validity period can be pre-set or customized by the target object. After obtaining the declaration data, the server can first obtain the generation time of the declaration data, which refers to the moment when the product operation certificate of the digital product is signed and the declaration data is generated. Then, a target duration between the generation time of the declaration data and the current time is determined; the current time refers to the moment when the declaration data is verified. In other words, the target duration is the period from the moment the declaration data is generated until the moment the server verifies the declaration data. Finally, the target duration is compared with the transfer validity period. If the target duration is less than or equal to the transfer validity period, it means that the product transfer certificate is in a valid state, and the step of performing the target operation on the digital product based on the declared data can be triggered. Conversely, if the target duration is greater than the transfer validity period, it means that the product transfer certificate is not in a valid state, but in an invalid state, and the transfer of the digital product is determined to have failed.

[0182] For example, in a digital product transfer scenario, if declaration data is generated at 12:00 on December 12th, and the corresponding transfer validity period is 24 hours, then when the server verifies the declaration data at 19:00 on December 12th, the target duration between the creation time of the declaration data and the current time is determined to be 7 hours, which is less than the 24-hour transfer validity period. Therefore, the server can perform the verification of the declaration data. Conversely, if the server verifies the declaration data at 12:00 on December 15th, the target duration between the creation time of the declaration data and the current time is determined to be 72 hours, which is greater than the 24-hour transfer validity period. Therefore, the server cannot perform the verification of the declaration data, and the digital product transfer fails. By setting a transfer validity period for product operation credentials, the product operation credentials have a valid operational scope, which can improve the security of the product operation credentials to a certain extent.

[0183] S706: The server returns the transfer results for digital products to the terminal device.

[0184] In a specific implementation, the server can return the transfer result of the digital product to the terminal device. The transfer result of the digital product may include information such as whether the transfer was successful or failed. This application embodiment does not limit the specific content of the transfer result.

[0185] In this embodiment, if the target object has a need to transfer digital products, the terminal device can generate an operation request in response to the need to transfer digital products. This operation request requests that the holder of the digital product be changed from the target object to a reference object. The target object and the reference object are different; that is, the target operation for the digital product is the operation to transfer the digital product. The operation information for the target operation includes at least: the digital identifier of the reference object and the product identifier of the digital product to be transferred. Then, in response to the operation request, the terminal device generates a product transfer certificate based on the digital identifier of the target object and the operation information of the target operation. Finally, the product transfer certificate is signed based on the first signature data of the target object to generate declaration data. Furthermore, during the transfer of digital products, the NFT protocol layer is supported by a blockchain identity layer protocol (i.e., a DID protocol), which not only improves the autonomous control over digital products but also enhances the security of digital product transfer, providing protocol support for product circulation across chains (i.e., different blockchains) or across contracts (such as different smart contracts).

[0186] The methods of the embodiments of this application have been described in detail above. In order to facilitate better implementation of the above solutions of the embodiments of this application, the apparatus of the embodiments of this application is provided below.

[0187] Please see Figure 9, Figure 9 This is a schematic diagram of the structure of a processing device for a digital product provided in an embodiment of this application. This processing device can be disposed in an electronic device (such as a server) provided in this embodiment of the application. In some embodiments, the processing device can be a computer program (including program code) running in the electronic device, and the processing device can be used to execute... Figure 3 , Figure 5 or Figure 7 The corresponding steps in the method embodiments shown. Please refer to... Figure 9 The processing apparatus may include the following units:

[0188] The acquisition unit 901 is used to acquire the digital identifier of the target object when it acquires an operation request for the target object to perform on the digital product, and the operation request carries the operation information of the requested target operation.

[0189] Processing unit 902 is used to generate a product operation certificate based on the digital identifier and operation information of the target object; the product operation certificate is used to indicate that the digital product is requested to perform the target operation, and to indicate that the requester of the target operation is the target object;

[0190] The processing unit 902 is further configured to, if the target object confirms the execution of the target operation on the digital product, obtain the declaration data obtained by performing signature processing on the product operation certificate using the first signature data of the target object;

[0191] The processing unit 902 is also used to perform target operations on digital products based on the claimed data.

[0192] In one implementation, the digital identifier of the target object is bound to the second signature data of the target object. When the processing unit 902 performs a target operation on the digital product based on the claim data, it is specifically used for:

[0193] Based on the digital identifier of the target object, obtain the second signature data of the target object;

[0194] The second signature data of the target object is used to verify the signature of the declared data;

[0195] If the data verification is successful, the target operation will be performed on the digital product.

[0196] In one implementation, the operation request is used to request the casting of a digital product, the target operation includes the operation of casting the digital product, and the operation information of the target operation includes: product casting information required for casting the digital product;

[0197] When processing unit 902 performs target operations on digital products, it is specifically used for:

[0198] Based on the product casting information required for casting digital products, digital products are cast to obtain digital products;

[0199] Create product identifiers for the digital products obtained through casting;

[0200] Bind the product identifier of the digital product to the digital identifier of the target object.

[0201] In one implementation, when processing unit 902 binds the product identifier of a digital product and the digital identifier of a target object, it specifically performs the following:

[0202] A first mapping and binding relationship is established based on the digital identifier of the target object and the product identifier of the digital product. The first mapping and binding relationship is used to indicate that the holder of the digital product is the target object.

[0203] The first mapping and binding relationship is stored in the smart contract corresponding to the digital product.

[0204] In one implementation, the operation request is used to request the transfer of the digital product from the target object to the reference object, the reference object being different from the target object. The target operation includes the operation of transferring the digital product, and the operation information of the target operation includes at least: the digital identifier of the reference object and the product identifier of the digital product.

[0205] When processing unit 902 performs target operations on digital products, it is specifically used for:

[0206] Obtain the product document corresponding to the digital product; the product document includes a controller field, which records the digital identifier of the target object;

[0207] In the product documentation, change the numerical identifier of the target object recorded in the controller field to the numerical identifier of the reference object;

[0208] Furthermore, in the smart contract corresponding to the digital product, the first mapping binding relationship is modified to a second mapping binding relationship; wherein, the first mapping binding relationship indicates that the holder of the digital product is the target object, and the second mapping binding relationship indicates that the holder of the digital product is the reference object.

[0209] In one implementation, when processing unit 902 obtains the product document corresponding to the digital product, it specifically performs the following functions:

[0210] The product identifier of the digital product is parsed to obtain the corresponding product document; the product document stores the metadata of the digital product.

[0211] In one implementation, the data is declared to have a transfer validity period; the processing unit 902 is further configured to:

[0212] The generation time of the declaration data is obtained. The generation time refers to the moment when the product operation certificate of the digital product is signed and the declaration data is generated.

[0213] Determine the target duration between the generation time of the declaration data and the current time, where the current time refers to the moment when the declaration data is verified and signed.

[0214] If the target duration is less than or equal to the transfer validity duration, the step of performing the target operation on the digital product based on the declared data is triggered.

[0215] In one implementation, the processing unit 902 is used to obtain the declaration data obtained by performing signature processing on the product operation credential using the first signature data of the target object if the target object confirms the execution of the target operation on the digital product. Specifically, it is used to:

[0216] The product operation credential is sent to the target object so that when the target object confirms the execution of the target operation on the digital product, it uses the target object's first signature data to sign the product operation credential to obtain the declaration data and returns the declaration data.

[0217] Receive the declaration data returned by the target object.

[0218] In one implementation, the processing unit 902 is used to obtain the declaration data obtained by performing signature processing on the product operation credential using the first signature data of the target object if the target object confirms the execution of the target operation on the digital product. Specifically, it is used to:

[0219] Output product operation credentials on the display screen;

[0220] In response to the target object's signature operation on the product operation credential, the signed product operation credential is obtained;

[0221] The signed product operation certificate is used as the declaration data.

[0222] In one implementation, when processing unit 902 receives the signed product operation certificate in response to a signature operation by the target object, it specifically performs the following:

[0223] In response to the target object adopting the target object's first signature data, a signature operation is performed on the product operation credential to obtain a signed product operation credential;

[0224] Alternatively, receive the authorization operation of the target object for the product operation certificate, obtain the first signature data of the target object, and use the first signature data of the target object to perform signature processing on the product operation certificate to obtain the signed product operation certificate.

[0225] In one implementation, the process of generating the digital identifier of the target object includes:

[0226] Obtain object information of the target object;

[0227] Convert object information into a numerical identifier for the target object;

[0228] The object information includes the public key of the target object.

[0229] According to one embodiment of this application, Figure 9 The processing device shown can be constructed by combining each unit individually or entirely into one or more other units, or one or more of the units can be further divided into multiple functionally smaller units. This can achieve the same operation without affecting the technical effect of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the processing device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by multiple units working together. According to another embodiment of this application, the processing device can be executed by running on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM). Figure 3 , Figure 5 and Figure 7 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 9 The processing apparatus shown herein, and the processing method for implementing the digital product according to the embodiments of this application, are described. A computer program may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and executed therein.

[0230] In this embodiment, upon receiving an operation request from a target object to perform on a digital product, a product operation credential can be generated based on the target object's digital identifier and the operation information carried in the operation request. This product operation credential indicates that the digital product is requested to perform a target operation, and that the requester of the target operation is the target object. By generating a product operation credential for the digital product, the target object can be intuitively informed of relevant information about the digital product, optimizing the expression and readability of the digital product. Furthermore, the target operation is only performed on the digital product when the target object confirms the execution of the target operation, i.e., obtains the declaration data (i.e., the product operation after signature processing), and the signature verification of the declaration data is successful. This improves the security and traceability of the digital product, thereby efficiently realizing the target operation on the digital product.

[0231] Figure 10 A schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this application is shown. Please refer to... Figure 10 The electronic device includes a processor 1001, a communication interface 1002, and a computer-readable storage medium 1003. The processor 1001, communication interface 1002, and computer-readable storage medium 1003 can be connected via a bus or other means. The communication interface 1002 is used to receive and send data. The computer-readable storage medium 1003 can be stored in the memory of the electronic device and is used to store computer programs, including program instructions. The processor 1001 is used to execute the program instructions stored in the computer-readable storage medium 1003. The processor 1001 (or CPU (Central Processing Unit)) is the computing and control core of the electronic device, suitable for implementing one or more instructions, specifically suitable for loading and executing one or more instructions to achieve corresponding method flows or corresponding functions.

[0232] This application embodiment also provides a computer-readable storage medium (Memory), which is a memory device in an electronic device used to store programs and data. It is understood that the computer-readable storage medium here can include both built-in storage media in the electronic device and extended storage media supported by the electronic device. The computer-readable storage medium provides storage space that stores the processing system of the electronic device. Furthermore, the storage space also stores one or more instructions suitable for loading and execution by the processor 1001, which may be one or more computer programs (including program code). It should be noted that the computer-readable storage medium here can be high-speed RAM memory or non-volatile memory, such as at least one disk storage device; optionally, it may also be at least one computer-readable storage medium located remotely from the aforementioned processor.

[0233] In one embodiment, the computer-readable storage medium stores one or more instructions; the processor 1001 loads and executes one or more instructions stored in the computer-readable storage medium to implement the corresponding steps in the above-described embodiment of the digital product processing method; specifically, the one or more instructions in the computer-readable storage medium are loaded by the processor 1001 and executed as follows:

[0234] When a target object requests an operation on a digital product, the target object's digital identifier is obtained, and the operation request carries the operation information of the requested target operation.

[0235] A product operation certificate is generated based on the digital identifier and operation information of the target object; the product operation certificate is used to indicate that the digital product is requested to perform the target operation, and to indicate that the requester of the target operation is the target object;

[0236] If the target object confirms to perform the target operation on the digital product, then the first signature data of the target object is obtained, and the declaration data obtained by performing signature processing on the product operation certificate is obtained.

[0237] Perform targeted operations on digital products based on claimed data.

[0238] In one implementation, the digital identifier of the target object is bound to the second signature data of the target object. When one or more instructions in the computer-readable storage medium are loaded by the processor 1001 and the target operation on the digital product based on the claimed data is performed, the following steps are specifically executed:

[0239] Based on the digital identifier of the target object, obtain the second signature data of the target object;

[0240] The second signature data of the target object is used to verify the signature of the declared data;

[0241] If the data verification is successful, the target operation will be performed on the digital product.

[0242] In one implementation, the operation request is used to request the casting of a digital product, the target operation includes the operation of casting the digital product, and the operation information of the target operation includes: product casting information required for casting the digital product;

[0243] One or more instructions in a computer-readable storage medium are loaded by processor 1001 and, when performing a target operation on a digital product, specifically execute the following steps:

[0244] Based on the product casting information required for casting digital products, digital products are cast to obtain digital products;

[0245] Create product identifiers for the digital products obtained through casting;

[0246] Bind the product identifier of the digital product to the digital identifier of the target object.

[0247] In one implementation, when one or more instructions in the computer-readable storage medium are loaded by the processor 1001 and executed to bind the product identifier of the digital product and the digital identifier of the target object, the following steps are specifically performed:

[0248] A first mapping and binding relationship is established based on the digital identifier of the target object and the product identifier of the digital product. The first mapping and binding relationship is used to indicate that the holder of the digital product is the target object.

[0249] The first mapping and binding relationship is stored in the smart contract corresponding to the digital product.

[0250] In one implementation, the operation request is used to request the transfer of a digital product from a target object to a reference object, which is different from the target object; the target operation includes the operation of transferring the digital product, and the operation information of the target operation includes at least: the digital identifier of the reference object, and the product identifier of the digital product;

[0251] One or more instructions in a computer-readable storage medium are loaded by processor 1001 and, when performing a target operation on a digital product, specifically execute the following steps:

[0252] Obtain the product document corresponding to the digital product; the product document includes a controller field, which records the digital identifier of the target object;

[0253] In the product documentation, change the numerical identifier of the target object recorded in the controller field to the numerical identifier of the reference object;

[0254] Furthermore, in the smart contract corresponding to the digital product, the first mapping binding relationship is modified to a second mapping binding relationship; wherein, the first mapping binding relationship indicates that the holder of the digital product is the target object, and the second mapping binding relationship indicates that the holder of the digital product is the reference object.

[0255] In one implementation, when one or more instructions in the computer-readable storage medium are loaded by the processor 1001 and executed to retrieve the product document corresponding to the digital product, the following steps are specifically performed:

[0256] The product identifier of the digital product is parsed to obtain the corresponding product document; the product document stores the metadata of the digital product.

[0257] In one implementation, data is declared to have a transfer validity period; one or more instructions in a computer-readable storage medium are loaded by processor 1001 and the following steps are also executed:

[0258] The generation time of the declaration data is obtained. The generation time refers to the moment when the product operation certificate of the digital product is signed and the declaration data is generated.

[0259] Determine the target duration between the generation time of the declaration data and the current time, where the current time refers to the moment when the declaration data is verified and signed.

[0260] If the target duration is less than or equal to the transfer validity duration, the step of performing the target operation on the digital product based on the declared data is triggered.

[0261] In one implementation, when one or more instructions in a computer-readable storage medium are loaded and executed by processor 1001, if the target object confirms that the target operation is performed on the digital product, and the first signature data of the target object is obtained, and the declaration data obtained by performing signature processing on the product operation certificate is executed, the following steps are specifically performed:

[0262] The product operation credential is sent to the target object so that when the target object confirms the execution of the target operation on the digital product, it uses the target object's first signature data to sign the product operation credential to obtain the declaration data and returns the declaration data.

[0263] Receive the declaration data returned by the target object.

[0264] In one implementation, when one or more instructions in a computer-readable storage medium are loaded and executed by processor 1001, if the target object confirms that the target operation is performed on the digital product, and the first signature data of the target object is obtained, and the declaration data obtained by performing signature processing on the product operation certificate is executed, the following steps are specifically performed:

[0265] Output product operation credentials on the display screen;

[0266] In response to the target object's signature operation on the product operation credential, the signed product operation credential is obtained;

[0267] The signed product operation certificate is used as the declaration data.

[0268] In one implementation, when one or more instructions in a computer-readable storage medium are loaded by processor 1001 and executed in response to a signature operation of a target object on a product operation credential to obtain a signed product operation credential, the following steps are specifically performed:

[0269] In response to the target object adopting the target object's first signature data, a signature operation is performed on the product operation credential to obtain a signed product operation credential;

[0270] Alternatively, receive the authorization operation of the target object for the product operation certificate, obtain the first signature data of the target object, and use the first signature data of the target object to perform signature processing on the product operation certificate to obtain the signed product operation certificate.

[0271] In one implementation, the process of generating the digital identifier of the target object includes:

[0272] Obtain object information of the target object;

[0273] Convert object information into a numerical identifier for the target object;

[0274] The object information includes the public key of the target object.

[0275] Based on the same inventive concept, the principle and beneficial effects of the electronic device provided in the embodiments of this application in solving the problem are similar to the principle and beneficial effects of the digital product processing method in the embodiments of this application in solving the problem. For the sake of brevity, the principle and beneficial effects of the method implementation can be referred to.

[0276] This application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the processing method of the digital product described above.

[0277] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0278] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data processing device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0279] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this invention should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing digital products, characterized in that, The method is applied to blockchain node devices in a blockchain network, and the method includes: When an operation request is received from a target object for a digital product, the digital identifier of the target object is obtained, and the operation request carries operation information of the requested target operation; the digital identifier of the target object is bound to the second signature data of the target object. A product operation certificate is generated based on the digital identifier of the target object and the operation information; the product operation certificate is used to indicate that the digital product is requested to perform a target operation, and to indicate that the requester of the target operation is the target object; The product operation certificate is sent to the terminal device held by the target object, so that the terminal device outputs the product operation certificate to the target object; If the target object confirms to perform the target operation indicated by the product operation certificate on the digital product based on the product operation certificate output by the terminal device, then the first signature data of the target object is obtained, and the declaration data obtained by performing signature processing on the product operation certificate is obtained. Based on the digital identifier of the target object, obtain the second signature data of the target object; The declaration data is verified using the second signature data of the target object. If the declared data is successfully verified, the target operation is performed on the digital product.

2. The method as described in claim 1, characterized in that, The operation request is used to request the casting of the digital product. The target operation includes the operation of casting the digital product. The operation information of the target operation includes: product casting information required to cast the digital product. Performing the target operation on the digital product includes: The digital product is cast according to the product casting information required for casting the digital product; Create a product identifier for the digital product obtained by casting; The product identifier of the digital product and the digital identifier of the target object are bound together.

3. The method as described in claim 2, characterized in that, The process of binding the product identifier of the digital product and the digital identifier of the target object includes: A first mapping and binding relationship is established based on the digital identifier of the target object and the product identifier of the digital product. The first mapping and binding relationship is used to indicate that the holder of the digital product is the target object. The first mapping binding relationship is stored in the smart contract corresponding to the digital product.

4. The method as described in claim 1, characterized in that, The operation request is used to request the transfer of the digital product from the target object to a reference object, the reference object being different from the target object; the target operation includes the operation of transferring the digital product, and the operation information of the target operation includes at least: the digital identifier of the reference object, and the product identifier of the digital product; Performing the target operation on the digital product includes: Obtain the product document corresponding to the digital product; the product document includes a controller field, which records the digital identifier of the target object; In the product documentation, the numerical identifier of the target object recorded in the controller field is modified to the numerical identifier of the reference object; Furthermore, in the smart contract corresponding to the digital product, the first mapping binding relationship is modified to a second mapping binding relationship; wherein, the first mapping binding relationship indicates that the holder of the digital product is the target object, and the second mapping binding relationship indicates that the holder of the digital product is the reference object.

5. The method as described in claim 4, characterized in that, The step of obtaining the product document corresponding to the digital product includes: The product identifier of the digital product is parsed to obtain the product document corresponding to the digital product; the product document stores the metadata of the digital product.

6. The method as described in claim 4, characterized in that, The declaration data has a transfer validity period; before obtaining the second signature data of the target object based on the digital identifier of the target object, the method further includes: The generation time of the declaration data is obtained, where the generation time refers to the moment when the product operation certificate of the digital product is signed and the declaration data is generated. Determine the target duration between the generation time of the declaration data and the current time, where the current time refers to the moment when the declaration data is verified and signed; If the target duration is less than or equal to the effective duration of the transfer, then the step of performing the target operation on the digital product based on the declared data is triggered.

7. The method as described in claim 1, characterized in that, If the target object confirms the execution of the target operation on the digital product, then the declaration data obtained by performing signature processing on the product operation credential using the first signature data of the target object includes: Output the product operation certificate on the display screen; In response to the target object's signature operation on the product operation credential, the signed product operation credential is obtained; The signed product operation certificate is used as the declaration data.

8. The method as described in claim 7, characterized in that, The step of responding to the target object's signature operation on the product operation credential to obtain the signed product operation credential includes: In response to the target object using the first signature data of the target object, a signature operation is performed on the product operation credential to obtain the signed product operation credential; Alternatively, the system may receive an authorization operation from the target object for the product operation credential, obtain the first signature data of the target object, and use the first signature data of the target object to perform signature processing on the product operation credential to obtain the signed product operation credential.

9. The method as described in claim 1, characterized in that, The process of generating the digital identifier of the target object includes: Obtain object information of the target object; Convert the object information into a digital identifier for the target object; The object information includes the public key of the target object.

10. A processing device for digital products, characterized in that, The processing device is located on a blockchain node device in the blockchain network, and the device includes: The acquisition unit is used to acquire the digital identifier of the target object when an operation request for the target object to be performed on the digital product is received. The operation request carries operation information of the requested target operation. The digital identifier of the target object is bound to the second signature data of the target object. The processing unit is configured to generate a product operation certificate based on the digital identifier of the target object and the operation information; the product operation certificate is used to indicate that the digital product is requested to perform a target operation, and to indicate that the requester of the target operation is the target object; The processing unit is further configured to send the product operation certificate to the terminal device held by the target object, so that the terminal device outputs the product operation certificate to the target object; if the target object confirms to perform the target operation indicated by the product operation certificate on the digital product based on the product operation certificate output by the terminal device, then the unit obtains the declaration data obtained by performing signature processing on the product operation certificate using the first signature data of the target object. The processing unit is further configured to perform the target operation on the digital product based on the declaration data; obtain the second signature data of the target object according to the digital identifier of the target object; perform signature verification processing on the declaration data using the second signature data of the target object; and if the signature verification of the declaration data is successful, perform the target operation on the digital product.

11. An electronic device, characterized in that, include: A processor, adapted to execute computer programs; A computer-readable storage medium storing a computer program, which, when executed by the processor, implements the processing method of a digital product as described in any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer application program, which, when executed, implements the processing method for a digital product as described in any one of claims 1-9.

13. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed by a processor, implement the processing method of the digital product as described in any one of claims 1-9.

Images