WO2024021785A1 - 一种数字实体的处理方法、装置、设备、介质及程序产品 - Google Patents

一种数字实体的处理方法、装置、设备、介质及程序产品 Download PDF

Info

Publication number
WO2024021785A1
WO2024021785A1 PCT/CN2023/094699 CN2023094699W WO2024021785A1 WO 2024021785 A1 WO2024021785 A1 WO 2024021785A1 CN 2023094699 W CN2023094699 W CN 2023094699W WO 2024021785 A1 WO2024021785 A1 WO 2024021785A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
digital
target object
target
data
Prior art date
Application number
PCT/CN2023/094699
Other languages
English (en)
French (fr)
Inventor
曾锦辉
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2024021785A1 publication Critical patent/WO2024021785A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products

Definitions

  • This application relates to the field of computer technology, and in particular to digital entity processing technology.
  • Digital entities are digital entities that are uniquely identified based on blockchain technology. Compared with actual entities, digital entities have the advantages of being easy to carry, disseminate, and permanently preserve.
  • Embodiments of the present application provide a digital entity processing method, device, equipment, medium and program product, which can improve the security of digital entities and the traceability of related operations.
  • embodiments of the present application provide a digital entity processing method, which is executed by an electronic device.
  • the method includes:
  • the digital identification of the target object is obtained, and the operation request carries the operation information of the target operation requested by the target object to be performed on the digital entity;
  • the entity operation voucher is used to indicate that the target operation is requested to be performed on the digital entity, and is used to indicate that the requester of the target operation is the target object;
  • the statement data is obtained.
  • the statement data is obtained by performing signature processing on the entity operation voucher using the first signature data of the target object;
  • a digital entity processing device which includes:
  • the acquisition unit is used to acquire the digital identification of the target object when acquiring an operation request initiated by the target object for the digital entity.
  • the operation request carries the operation information of the target operation requested by the target object to be performed on the digital entity;
  • a processing unit configured to generate an entity operation voucher based on the digital identification and operation information of the target object; the entity operation voucher is used to indicate that the target operation is requested to be performed on the digital entity, and is used to indicate that the requester of the target operation is the target object;
  • the processing unit is also configured to obtain statement data if the target object confirms that the target operation is performed on the digital entity.
  • the statement data is obtained by performing signature processing on the entity operation voucher using the first signature data of the target object;
  • the processing unit is also used to perform target operations on digital entities based on declaration data.
  • this application provides an electronic device, which includes:
  • a computer-readable storage medium stores a computer program.
  • the computer program is executed by a processor, the above-mentioned digital entity processing method is implemented.
  • the present application provides a computer-readable storage medium that stores a computer-readable storage medium.
  • the computer program is adapted to be loaded by the processor and execute the above-mentioned processing method of digital entities.
  • the present application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned processing method for digital entities.
  • the entity operation voucher when receiving an operation request initiated by the target object for a digital entity, can be generated according to the digital identification of the target object and the operation information carried in the operation request, and the entity operation voucher indicates that the request is for the digital entity.
  • the target operation is executed, and the requester of the target operation is the target object; by generating the entity operation voucher of the digital entity, the target object can obtain the entity operation voucher, thereby intuitively informing the target object of the information related to the digital entity through the entity operation voucher, and optimizing Representation and readability of digital entities.
  • the target object confirms that the target operation is performed on the digital entity, that is, the declaration data (that is, the entity operation certificate after signature processing) is obtained, and the signature verification of the declaration data is successful, the target operation is performed on the digital entity.
  • the embodiment of the present application uses the digital identification of the target object throughout the operation process of the digital entity, and generates the entity operation voucher and declaration data based on the digital identification of the target object. In this way, during the process of performing the target operation on the digital entity, the operation process for the digital entity is intuitively and reliably recorded.
  • the related operations performed by the digital entity and the execution objects of the related operations thereby ensuring the security of the digital entity and the traceability of the related operations.
  • Figure 1a is a schematic structural diagram of a blockchain provided by an exemplary embodiment of the present application.
  • Figure 1b is a schematic structural diagram of a data sharing system provided by an exemplary embodiment of the present application.
  • Figure 2a is a schematic architectural diagram of a digital entity processing system provided by an exemplary embodiment of the present application
  • Figure 2b is a schematic structural diagram of a blockchain application protocol model provided by an exemplary embodiment of the present application.
  • Figure 2c is a schematic diagram of the protocol mapping relationship between an NFT smart contract and a DID smart contract provided by an exemplary embodiment of the present application;
  • Figure 2d is a schematic diagram of an NFT protocol design based on the DID protocol provided by an exemplary embodiment of the present application
  • Figure 3 is a schematic flowchart of a digital entity processing method provided by an exemplary embodiment of the present application.
  • Figure 4 is a schematic diagram of outputting entity operation credentials provided by an exemplary embodiment of the present application.
  • Figure 5 is a schematic flowchart of another digital entity processing method provided by an exemplary embodiment of the present application.
  • Figure 6 is a schematic flow chart of casting digital entities provided by an exemplary embodiment of the present application.
  • Figure 7 is a schematic flowchart of yet another digital entity processing method provided by an exemplary embodiment of the present application.
  • Figure 8 is a schematic flowchart of transferring a digital entity provided by an exemplary embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a digital entity processing device provided by an exemplary embodiment of the present application.
  • Figure 10 is a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application.
  • the embodiment of this application provides a method for processing digital entities.
  • the processing method mainly involves blockchain technology, specifically involving typical applications in blockchain technology, including: distributed identity (Decentralized Identity, DID) and non-homogeneous Non-Fungible Token (NFT).
  • DID distributed Identity
  • NFT non-homogeneous Non-Fungible Token
  • Blockchain is the basis of blockchain technology; the so-called blockchain is a new application model of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm.
  • Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information ( Anti-counterfeiting) and generate the next block.
  • the schematic structural diagram of a blockchain can be seen in Figure 1a. As shown in Figure 1a, the blockchain is composed of multiple blocks.
  • the first block of the blockchain is called the genesis block (which can be referred to as the genesis block for short). block), the genesis block includes a block header and a block body.
  • the block header stores the input information characteristic value, version number, timestamp and difficulty value.
  • the block body stores the input information; the next area of the genesis block
  • the block has the genesis block as its sub-block, which can also be understood as the genesis block being the parent block of the next block.
  • the next block also includes a block header and a block body, and the block header stores the parent block. block header characteristic value, input information characteristic value of the current block, version number, timestamp and difficulty value, and so on, so that the block data stored in each block in the blockchain is the same as that in the parent block
  • the stored block data is associated, ensuring the security of the information entered in the block.
  • the blockchain can be maintained by the blockchain nodes included in the blockchain network; among them, the blockchain network can be understood as a data sharing system, which refers to the data sharing between blockchain nodes and blockchain nodes.
  • System an exemplary structure of the data sharing system can be seen in Figure 1b; as shown in Figure 1b, the data sharing system can include multiple blockchain nodes 101, and each blockchain node 101 can be connected to the area.
  • the server in the blockchain network can also be a terminal connected to the blockchain network (such as a client running in the terminal).
  • 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 in the blockchain network can store other blockchains in the blockchain network.
  • the node identification of node 101 so that the generated block can be subsequently broadcast to other blockchain nodes 101 in the data sharing system based on the node identification of other blockchain nodes 101, so as to achieve distributed storage of blocks in the blockchain network.
  • the data contained ensures that the data cannot be tampered with, cannot be copied, and is permanently saved.
  • Smart contracts can refer to: digital protocols that deploy the protocol specifications required for business execution on the blockchain network in the form of code; specifically, smart contracts are deployed on blockchain nodes in the blockchain network, thereby through the Blockchain nodes are used to run smart contracts to implement the business corresponding to the smart contract.
  • the business corresponding to the smart contract is transaction, that is, the smart contract is a contract used for transactions.
  • the smart contract includes: querying the logistics status of the goods purchased by the consumer, and after the consumer signs for the goods, the consumer's electronic resources (such as in Resources used for commodity transactions on the Internet) are transferred to the merchant's address; then, after the consumer has signed for the goods, the smart contract (specifically, the code that runs the smart contract) can be run to transfer the consumer's electronic resources (such as in Resources for commodity transactions on the Internet) are transferred to the merchant's address.
  • the smart contract specifically, the code that runs the smart contract
  • the smart contract can be run to transfer the consumer's electronic resources (such as in Resources for commodity transactions on the Internet) are transferred to the merchant's address.
  • the above is just an exemplary smart contract application provided by the embodiment of the present application.
  • the blockchain maintained by the blockchain network is mainly divided into three major types, including: public chain (Public Block Chains), alliance chain (Consortium Block Chains) and private chain (Private) Block Chains).
  • the public chain refers to: any node in the blockchain network (such as the blockchain node corresponding to a single object or a collective object) can send transaction data, and the transaction data can be effectively confirmed, and any node can participate in the consensus Process blockchain.
  • a consortium chain may refer to a blockchain in which some nodes in the blockchain network can participate in the block consensus process, while other nodes do not have access to the consensus process; for example, a blockchain network containing a consortium chain can specify multiple pre-selected Blockchain nodes are accounting nodes (such as blockchain nodes with consensus authority). Each block on the alliance chain is jointly decided by all accounting nodes (that is, pre-selected blockchain nodes participate in the consensus process). In addition to the accounting nodes, other connected blockchain nodes in the blockchain network can participate in transactions, but do not participate in the consensus process.
  • a private chain refers to a blockchain in which one blockchain node in the blockchain network has exclusive write permissions (such as uploading the blockchain to the blockchain after consensus).
  • Digital entities can include Non-Fungible Token (NFT), which is a set of digital asset protocols based on blockchain technology; specifically, the entity is digitized and placed on the blockchain, making the entity Digitization has become a unique, indivisible and rare digital entity; for ease of explanation, the abbreviation NFT will be used to represent digital entities.
  • NFT Non-Fungible Token
  • the physical forms that can be cast into digital entities may include but are not limited to: digital images (or digital pictures), audio and video, 3D (3-dimension, three-dimensional) models, electronic tickets, digital souvenirs and other forms; the embodiments of this application are The physical form cast into a digital entity is not limited. Digital entities are stored on the blockchain and cannot be tampered with or copied, making digital entities have unique value compared to physical entities.
  • digital certificates corresponding to digital entities can be stored on the blockchain, so that as long as the blockchain exists, the digital entities can be stored permanently without being tampered with or copied.
  • digital entities exist in the blockchain in digital form, making them easy for owners to carry and spread.
  • interactive operations can be performed on digital entities in the blockchain network, including but not limited to: the casting of digital entities and the transfer of digital entities.
  • casting of digital entities refers to the use of blockchain technology to digitally encrypt digital entities, and the digital entities will have a digital certificate (or serial number, blockchain number, etc.) that uniquely identifies their identity.
  • Digital certificates can be used as proof of the holder's right to own a digital entity; the digital certificate corresponding to the digital entity is then stored on the blockchain to realize the process of uploading the digital entity to the chain.
  • the so-called transfer of digital entities refers to the process of transferring a digital entity from the current holder to another object. After the transfer, the other object has the operating authority of the digital entity.
  • the target object transfers the digital entity to the reference object (such as another object different from the target object), which essentially transfers the operating permissions to the digital entity. (such as sales, display, etc.) are transferred to the reference object. After the transfer, the reference object has the operating authority to operate the digital entity.
  • smart contracts deploy protocol specifications on the blockchain network in the form of code, which allows the target object to access the blockchain network through decentralized applications (Decentralized Application, DApp) (such as NFT wallets).
  • NFT smart contracts realize target operations such as the casting or transfer of digital entities (or digital assets).
  • NFT smart contracts follow 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 to achieve interoperability for NFT (such as NFT casting, issuance, and trading) wait).
  • digital assets are locked in the corresponding account in the form of tokens on the blockchain.
  • the token is associated with the metadata of the NFT asset.
  • the metadata metadata contains relevant information describing the content of the NFT, including but not limited to: storage location. Or historical data, etc.
  • DID Distributed Identity
  • the infrastructure of distributed digital identity can be deployed in a distributed environment (such as a blockchain network) instead of being deployed in a centralized environment controlled by a single organization or alliance organization. It can realize that the identity is truly autonomous.
  • the identity here It refers to the identity of a person, organization or object; in other words, objects (or entities) with distributed digital identities are not limited to people or animals with life activities, but can also be other objects without life activities, etc.
  • DIDs Distributed Digital Identifiers
  • strings a string of data composed of characters, such as ahd21db23XX. They are used to represent the digital identity of a target object and can be globally unique without the need for a registration agency. sex.
  • An object can often have multiple digital identities. Each digital identity is assigned a unique DID value and an asymmetric key associated with it (that is, different public and private keys); there is no association between different digital identities. information, thus effectively avoiding the aggregation of the owner’s identity information.
  • Verifiable credentials VCs are declaration documents formed by the credential issuer endorsing the attributes of an entity (such as a target object); a verifiable credential can be issued by an identity owner (such as an individual or organization) itself, or it can be issued by other credentials Sent by people.
  • a digital identity is issued by a certificate issuer. Specifically, it can be issued by an identity endorser (certificate issuer) who endorses and signs the identity owner's attribute information based on the identity owner's request. It is worth noting that depending on the identity owner and the voucher generation scenario, the attribute information of the identity owner is different, and the verifiable credentials generated based on the attribute information are also different.
  • the identity endorsement is the node used by the school
  • the verifiable voucher is generated by the school's endorsement of the student's attribute information (such as age information, major information, grade information, and school information, etc.) Students’ academic certificates.
  • DID digital identity expression uses DID protocol to express and describe NFT and related participants, so that blockchain digital assets have the two-layer technical protocol attributes of DID and NFT.
  • This solution combines the DID protocol specification and the NFT protocol specification, and can realize all technical capabilities of NFT based on the DID protocol specification, including casting, publishing and transfer functions. It is a new type of NFT implementation solution.
  • the general principle of this solution may include: when the target object has a need to perform a target operation (such as casting or transfer) on the digital entity, the target object can initiate an operation request for the digital entity; in response to the operation request, obtain the digital identification of the target object , this digital ID is used to uniquely identify the identity of the target object, such as identity ID, number or nickname, etc. Then, the entity operation voucher can be generated based on the digital identification of the target object and the operation information of the target operation carried in the operation request. The entity operation voucher is used to indicate the target operation that the target object wants to perform on the digital entity.
  • a target operation such as casting or transfer
  • the target object confirms that the target operation indicated by the entity operation certificate is performed on the digital entity
  • the statement data signed with the first signature data (such as a private key) of the target object can be obtained, and the second signature of the target object can be obtained.
  • the data such as public key
  • the target operation is performed on the digital entity to realize the function of performing operations on the digital entity.
  • the embodiments of this application introduce the DID protocol into the traditional NFT operation implementation process, and can combine the advantages of the DID protocol and the NFT protocol, so that the digital entity processing solution provided by the embodiments of this application has the following advantages: : 1 Because distributed digital identity identifiers and verifiable credentials have the advantages of international standards, strong expression capabilities, readability and security, NFT and related participants (such as NFT itself, NFT issuers) can be expressed and described through the DID protocol , NFT holders and other entities), it can make the description of NFT richer and more complete, have better technical scalability, and optimize the expression and readability of NFT. 2 Implementing NFT through DID realizes the interconnection and upper and lower support of the two-layer protocol.
  • NFT can also complete protocol interoperability through the DID layer protocol, resulting in better protocol compatibility and interoperability.
  • Operational portability using DID's routing and cross-chain capabilities to enable NFT to support more protocol capabilities, improves the interoperability, portability and scenario expansion capabilities of the digital asset layer, making it easier to implement more scenarios.
  • 3The verifiable certificates under the DID protocol also have the ability of third-party signature and verification, which means that the NFT implementation solution based on DID has better supervision capabilities. For example, the casting and transfer certificates of DID can be signed by third-party authorities.
  • the signature verification is completed, which is not possible based on the single-layer NFT protocol implementation; through the high readability and traceability of distributed digital identity identifiers DIDs, more supervision functions can be applied to NFT, making this application implementable. For example, it can adapt to NFT scenarios with regulatory requirements, such as NFT implementation scenarios based on alliance chains.
  • the digital entity The processing system includes a terminal device 201 and a server 202.
  • the embodiment of the present application does not limit the number and type of the terminal device 201 and the server 202, which will be described here.
  • the electronic equipment involved in the digital entity processing system is described below, where:
  • the terminal device 201 may refer to a device on which distributed applications (ie, the aforementioned decentralized application DApp) are deployed.
  • the terminal device 201 can be a blockchain node device belonging to the blockchain network, or it can also be a device that is independent of the blockchain network but uses the blockchain in the blockchain network to provide trusted data for the DApp.
  • the terminal device 201 may include but is not limited to: smart phones (such as Android phones, iOS phones, etc.), tablet computers, portable personal computers, mobile Internet devices (Mobile Internet Devices, MID for short), smart TVs, vehicle-mounted devices, and head-mounted devices. wait.
  • the distributed application program of the digital entity deployed in the terminal device 201 is an application client that supports the target object to send operation requests regarding the digital entity.
  • the embodiment of the present application does not limit the running mode of the distributed application; for example, the distributed application is a client deployed on the terminal device 201 through an installation package; for another example, the distributed application can be run in the form of an online application.
  • distributed applications can run in the form of small programs among other applications deployed on the terminal device.
  • the so-called public and private keys can include: public key (publickey for short) and private key (privatekey for short); the public key and the private key are a pair of keys. If the encryption party uses the private key of the target object to encrypt the data , then the decryptor can only obtain the decrypted data by decrypting the encrypted data with 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 after generating the public and private keys of the target object, save the public and private keys for the target object.
  • the digital identification here refers to the distributed digital identity identifiers (DIDs) described above, and no distinction will be made about this. That is to say, the distributed application deployed in the terminal device can also receive the digital identification of the target object and implement the function of saving the received digital identification.
  • DIDs distributed digital identity identifiers
  • the entity operation credentials here may refer to the aforementioned verifiable credentials VCs, which will not be described differently.
  • the verifiable credentials VCs are different depending on the operation the target wants to perform on the digital entity. For example: In a scenario where the target object wants to cast a digital entity, the so-called casting of a digital entity can be simply understood as: the process of generating a digital entity and putting the digital entity on the chain. The verifiable certificate generated at this time is used to indicate: the digital entity is requested. Perform a casting operation, which is a request to cast a digital entity.
  • the so-called transfer of digital entities can be simply understood as: transferring the operation permission of the digital entity from one object to another object.
  • the verifiable certificate generated at this time is used to indicate: The digital entity is requested to perform a transfer operation, that is, the digital entity is requested to be transferred.
  • the server 202 may refer to a device with the function of realizing interactive operations corresponding to digital entities (such as casting or transfer operations); the server 202 is a blockchain node device belonging to the blockchain network.
  • the server 202 is deployed with a DID-based NFT protocol model innovatively proposed by the embodiment of the present application.
  • the DID-based NFT protocol model can also be called a blockchain application protocol model; the server can specifically use the blockchain application protocol.
  • the model implements interactive operations corresponding to digital entities.
  • the blockchain application protocol model includes: NFT protocol layer, DID protocol layer and blockchain network from top to bottom.
  • Each protocol layer can include the corresponding application layer and smart contract.
  • the NFT protocol layer includes the NFT application layer and the NFT smart contract.
  • the DID protocol layer includes the DID application layer and the DID smart contract.
  • the application layer and smart contract functions in the protocol layer are introduced.
  • the NFT protocol layer includes the NFT application layer and NFT smart contract.
  • the functions of the NFT application layer and NFT smart contract are briefly introduced below. in:
  • the NFT application layer can be used to process operation requests sent by terminal devices.
  • the operation request may include an entity digital identity registration request.
  • the NFT application layer may uniformly process the entity DID identity registration request on the NFT application end side (such as the NFT wallet in the terminal device), specifically in response to the DID identity registration request.
  • the DID protocol layer such as calling the DID application layer or DID smart contract
  • the generation and registration of the digital identifier (or digital ID for short) of the target object is completed.
  • the registered digital identification is also bound to the public key of the target object, so that the public key bound to the digital identification and the asymmetric encryption technology can be used to verify whether the operator of the NFT application is the target object of the corresponding digital identification. , to achieve identity verification of the target object and improve the security of data processing.
  • the NFT application layer After the NFT application layer registers and obtains the digital ID of the target object, it can also assign the digital ID of the target object to the terminal device (i.e., NFT application), so that the target object can pass the NFT application (i.e., the aforementioned DApp) based on the digital ID. ) initiates an operation request related to a digital entity (also known as an NFT operation request), allowing the NFT application layer to process NFT operation requests such as casting and transfer sent by the NFT application end. For example, in the NFT casting scenario, NFT should The user layer can directly generate the DID identifier corresponding to the token (i.e.
  • the DID application layer in order to facilitate the distinction between the DID identifier of the target object and the DID identifier of the digital entity, the DID identifier of the digital entity is symbol is called an entity identifier
  • the NFT application layer can indirectly generate the DID identifier corresponding to the token in the DID smart contract through the NFT smart contract.
  • 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 the NFT smart contract to check the target Whether the object has the operation permission to operate the digital entity, such as detecting whether the target object has the transfer permission to transfer the digital entity, or detecting whether the target object has the casting permission to cast the digital entity.
  • 2NFT smart contracts are used to process and manage data related to digital entities.
  • the NFT smart contract stores the binding relationship between the digital identification of the target object and the entity identification of the digital entity, which is used to anchor the object ownership of the digital entity.
  • there is a binding relationship (or called a binding mapping relationship) between the entity identification of digital entity A and the digital identification of target object a. This binding relationship anchors the holding object of digital entity A as target object a. Then according to the binding relationship, the holder of digital entity A is determined to be the target object a.
  • the NFT smart contract can directly call the DID smart contract to generate the DID identifier of the digital entity, and directly call the DID smart contract to verify the verifiable credentials VCs, and execute the execution on the digital entity after the verification of the verifiable credentials VCs is successful.
  • the corresponding target operation can modify the binding relationship between the digital ID of the target object and the entity ID of the digital entity to complete the transfer of the digital entity.
  • the DID protocol layer includes the DID application layer and DID smart contract.
  • the functions of the DID application layer and DID smart contract are briefly introduced below. in:
  • the DID application layer can be used to process operation requests sent by the NFT application layer located above it in the protocol model (such as operation requests such as creating digital identities or verifying credentials), and is used to connect downward to the DID smart contract in the protocol model to read and write DID status data.
  • the DID application layer serves as an intermediate layer.
  • the business logic that needs to be processed in the DID smart contract can be used as a service entrance, the DID application layer can enter the DID smart contract.
  • the DID status data includes but is not limited to: data contained in the DID document of the target object, and data contained in the DID document of the digital entity.
  • the DID document of the target object can be obtained by parsing the digital identification of the target object by the DID smart contract.
  • the DID document of the digital entity can be obtained by parsing the entity identification of the digital entity by the DID smart contract.
  • 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 any entity.
  • 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 and other information).
  • the document data contained in the DID document of the digital entity may include information related to the digital entity, including but not limited to: attribute information of the digital entity (such as the morphological information of the digital entity, casting Metadata such as time and other information) and digital content (such as element information contained in digital entities) are used to express all or part of the information of NFT entities (i.e. digital entities).
  • 2DID smart contracts can be used to process and manage DID-related data.
  • the DID smart contract stores all state data of DID, including DID documents of target objects and digital entities, specifically the document data contained in the DID document.
  • the DID status data in the DID smart contract can be read and written through the DID application layer and NFT smart contract.
  • the DID smart contract also contains a contract interface for verifying verifiable certificates. By calling this contract interface, the DID smart contract can verify whether the signed verifiable certificate is signed by the corresponding DID entity (such as a target object signed with a private key).
  • the protocol mapping relationship between the NFT smart contract and the DID smart contract provided by the embodiment of this application can be seen in Figure 2c.
  • the digital identification of the target object (DID identification of the target object) is stored in the NFT smart contract.
  • the entity identification of the digital entity (NFT token DID identification); and, the binding mapping relationship between the digital identification of the target object and the entity identification of the digital entity is also stored in the NFT smart contract, and the binding mapping relationship can be determined through the binding mapping relationship
  • the holder of the digital entity is the target object.
  • the DID smart contract stores the DID document of the target object.
  • the DID document of the target object is obtained by parsing the digital ID of the target object.
  • the DID smart contract also stores the DID document of the digital entity.
  • the DID document of the digital entity is obtained by parsing the entity identification of the digital entity. It can be understood as the entity identification of the digital entity and the relationship between the digital entity and the digital entity. There is a binding relationship between DID documents.
  • the DID document of the digital entity in the DID smart contract also includes a controller field.
  • the controller field can identify the target object to which the digital entity belongs. Specifically, the controller field is assigned a target object. Digital identification indicates that the owner of the digital entity is the target object, that is, the target object has the operation permission to interact with the digital entity.
  • the DID protocol and the NFT protocol In order to realize the two protocols to jointly complete the processing of digital entities, it is necessary to design the DID protocol and the NFT protocol.
  • the purpose is to determine the mapping relationship (or correspondence relationship) between the fields on both sides of the DID protocol and the NFT protocol. For example, in the protocol Certain field assignments, etc., enable the content of the other party's agreement to be identified based on a certain field in either party's agreement. For example, after obtaining a DID document, it can be determined based on the fields in the DID document that the DID document is an entity document of a digital entity.
  • the object side supports the generation of the first signature data and the second signature data of the target object by the object side (that is, the terminal device side used by the target object).
  • the object side generates public and private keys based on asymmetric cryptography algorithms, and the first signature data is public key, and the second signature data is 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 the digital identification of the target object in accordance with the DID specification and register it on the blockchain.
  • DID identity identifiers correspond to DID documents (i.e., the aforementioned entity documents) for description and expression Digital entity content in the NFT protocol standard.
  • the service field (such as service field) in the DID document corresponding to the digital entity as the entity identifier of the digital entity, so that the metadata of the digital entity can be accessed through the entity identifier, that is, the digital entity can be accessed through this field.
  • Metadata access For example, if the digital entity is a digital image, then the service field in the DID document corresponding to the digital entity can be assigned the resource identifier (Uniform Resource Identifier, URI) of the digital entity to access the metadata of the digital entity through the URI of the digital entity.
  • URI Uniform Resource Identifier
  • the metadata of digital entities can be stored in the gateway of the digital entity issuance platform, and the metadata stored in the gateway of the digital entity issuance platform can be accessed through the digital identity of the digital entity;
  • the metadata metadata contains the attribute information of the digital entity NFT.
  • this attribute information can be stored in various storage services such as decentralized storage or object storage in JSON form;
  • the metadata metadata also stores the access path to the NFT's visual presentation file (such as digital image).
  • the interaction that the target object wants to perform on the digital entity includes the operation of transferring the digital entity, then in the scenario where the holder of the digital entity (such as the target object) transfers the digital entity, it can be issued for the holder of the digital entity.
  • the verifiable voucher (or entity transfer voucher) sets the transfer validity period, then in the claim of the entity operation voucher
  • the statement needs to include the digital ID of the reference object of the digital entity to be received and the entity ID of the digital entity; and the entity transfer certificate needs to be signed by the target object (i.e. the holder).
  • the claim statement can also contain other customized transfer conditions 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.
  • the DID protocol layer can Shield the differences of the underlying blockchain network, and the NFT protocol layer is built on top of the DID protocol layer, that is, the NFT protocol layer can call the lower DID protocol layer, so that NFT assets can be based on the Decentralized Identifier (DIDs) of the DID protocol. and the Verifiable Credentials (VCs) protocol to achieve interoperability between different smart contracts or different blockchain networks.
  • DIDs Decentralized Identifier
  • VCs Verifiable Credentials
  • it provides standard blockchain identity layer protocol support for the NFT protocol, enhancing the account and asset security and autonomous control capabilities of the NFT implementation solution with the alliance chain as the bottom layer.
  • the embodiments of this application also support the integration of application layer functions into smart contracts, so that the NFT protocol layer and DID protocol layer in the blockchain application protocol model can only include smart contracts without additional application layer.
  • the digital entity processing system involved in the embodiment of the present application may also include only the server.
  • distributed applications can be deployed in the server; The embodiments of this application do not limit the type and quantity of devices included in the digital entity processing system.
  • the embodiments of this application are applied to specific entities or technologies, such as when obtaining the digital identification of a target object, the permission or consent of the target object is required at this time; and the collection, use and processing of relevant data need to comply with relevant countries and regions. Relevant laws, regulations and standards. For example, interoperability for digital entities needs to comply with relevant laws, regulations and standards of relevant countries and regions.
  • FIG 3 shows a schematic flowchart of a digital entity processing method provided by an exemplary embodiment of the present application; the digital entity processing method can be executed by an electronic device, for example, by a server in the system shown in Figure 2a,
  • the processing method may include but is not limited to steps S301-S304:
  • the target object when the target object has the need to perform a target operation on the digital entity, the target object initiates an operation request through the electronic device it holds, and the operation request carries the operation information of the target operation it requests to perform on the digital entity.
  • Operation information is information used to describe a target operation requested to be performed on a digital entity; then, in response to the operation request, the digital identity of the target object can be obtained.
  • the operation information of the target operation is different depending on the target operation.
  • target operations for digital entities may include but are not limited to: casting operations or transfer operations; when the target operation is a casting operation, the operation information of the target operation at least includes: the entity casting information required to cast the digital entity (such as the digital entity contains (element information of various elements), the digital identification of the owner of the minted digital entity,...; when the target operation is a transfer operation, the operation information of the target operation at least includes: the digital identification of the reference object of the digital entity to be received, the digital entity The digital identification of the holder before being transferred,....
  • the terminal device held by the target object and the execution subject server of the embodiment of the present application may be the same electronic device or different electronic devices.
  • the electronic device that generates the operation request may be A terminal device or server, specifically an electronic device with the function of calling a third-party organization to generate verifiable credentials.
  • the terminal device and the server are different electronic devices, and the target object can perform an initiating operation in the terminal device held by it, so that the terminal device can generate an operation request based on the detected initiating operation; and, after the server calls the third party On the premise that the institution generates entity operation credentials, the terminal device sends the operation request to the server, so that the server performs the operation of obtaining the digital identification of the target object in response to the operation request.
  • the terminal device has the ability to call a third-party organization to generate entity operation credentials. Then, after generating an operation request, the terminal device can directly respond to the operation request and perform the operation of generating entity operation credentials without sending the operation request to the server.
  • the terminal device and the server are the same electronic device, and the target object can perform an initiating operation on the digital entity in the server, so that the server can generate a corresponding operation request based on the detected initiating operation, and execute the acquisition of the target in response to the operation request.
  • the electronic device used to generate the operation request is not limited to whether it is a terminal device or a server.
  • the specific implementation process of the target object performing the initiated operation is also different.
  • the target operation that the target object wants to perform on the digital entity is a casting operation
  • the initiating operation performed by the target object through the electronic device may include: inputting the casting operation on the display screen (or simply referred to as a display, display screen, etc.) provided by the electronic device. Entity casting information required for digital entities.
  • the initiating operation performed by the target object through the electronic device may include: inputting the entity identification of the digital entity to be transferred in the display screen provided by the electronic device, and Information such as the digital identification of the reference object to be received.
  • the implementation process of obtaining the digital identification of the target object in response to the operation request may include: obtaining the digital identification of the target object from the storage space, or generating the target object. digital identity and register the digital identity on the blockchain.
  • the digital ID of the target object if the digital ID of the target object has been generated before receiving the operation request performed by the target object on the digital entity, then when the operation request is received, the digital ID of the target object can be obtained directly from the storage space. Specifically, The digital ID of the target object is obtained from the list used to store digital IDs in the storage space.
  • the digital identification of the storage space may be stored in the storage space after the DID smart contract generates the digital identification; or the digital identification of the storage space may also be the digital identification of the target object registered in the block by other blockchain nodes. When on-chain, it is distributed and stored in the storage space. On the contrary, if the digital ID of the target object is not generated and registered before receiving the operation request performed by the target object on the digital entity, the digital ID of the target object can be generated and registered based on the operation request to obtain the target object's digital ID. Digital ID.
  • the digital identifier of the target object may be an identifier that is generated based on the object information of the target object and can uniquely determine the target object.
  • the object information of the target object may include but is not limited to: attribute information of the target object (such as nickname, ID number, etc.) Or the public key of the target object, etc.
  • the process of generating the digital identification of the target object may include: first obtaining the object information of the target object, and then converting the object information into the digital identification of the target object. For example, assuming that the object information of the target object includes the public key of the target object, the public key can be transcoded into a digital ID according to the DID specification, and the generated digital ID can be registered on the blockchain to obtain the digital ID of the target object. logo.
  • the process of generating the digital ID of the target object is different, among which:
  • the generation process of the digital ID of the target object may include: the requirement that the target object has a registered ID.
  • the target object can initiate an identity registration request, and the identity registration request carries the object information of the target object; further, in response to the identity registration request, the object information can be converted into a digital identity of the target object.
  • the generation process of the digital identification of the target object may include: after receiving the operation request, and When it is detected that there is no digital identification of the target object, an information acquisition request is returned (such as returning an information acquisition request to the terminal device held by the target object). This information acquisition request is used to request to obtain the object information of the target object; receive the response to the information acquisition Request the returned object information of the target object, and convert the object information into a digital ID of the target object.
  • S302 Generate entity operation credentials based on the digital identification and operation information of the target object.
  • S303 If the target object confirms that the target operation is performed on the digital entity, obtain statement data.
  • the statement data is obtained by performing signature processing on the entity operation voucher using the first signature data of the target object.
  • the entity operation voucher can be generated based on the digital identification of the target object and the operation information of the target operation.
  • An entity operation certificate is similar to a digital certificate, used to indicate a request to perform a target operation on a digital entity, and also used to indicate that the requester of the target operation is the target object. It can be used as record data for the target object to initiate an operation request for the digital entity. .
  • the entity operation voucher can be generated by the terminal device held by the target object.
  • the terminal device can generate the entity operation voucher based on the operation information of the target operation requested by the operation request and the digital identification of the target object, and send it to Entity operation credentials are sent to the server.
  • the entity operation credential can also be generated by the server. In this case, when the server obtains the operation request, it can generate the entity operation credential based on the obtained digital ID of the target object and the operation information of the target operation.
  • the embodiments of the present application do not limit the electronic device that generates entity operation credentials; for example, when a distributed application is deployed on a server, the target object can directly perform operations on the server. In this case, there is no need to Contains terminal devices so that entity operation credentials are generated by the server.
  • the subsequent introduction will take the generation of entity operation credentials by a terminal device deployed with a distributed application program (DAPP) as an example.
  • DAPP distributed application program
  • the target object can obtain the entity operation voucher.
  • the server returns the entity operation voucher to the terminal device held by the target object, so that the target object obtains the entity operation voucher through the terminal device, or the terminal device generates and outputs the entity operation voucher. Credentials so that the target object can view the entity operation credentials. After the target object obtains the entity operation voucher, it can view the information contained in the entity operation voucher. If the target object confirms that the target operation indicated by the entity operation voucher is performed on the digital entity, then the first signature data of the target object can be used to authenticate the entity.
  • the operation voucher is signed, for example, the first signature data is used to digitally sign the entity operation voucher to generate statement data; the first signature data of the target object here can be the private key of the target object.
  • the target operation is performed on the digital entity based on the signed declaration data of the target object.
  • the first signature data of the target object is used to sign the entity operation certificate, which means that the target is performed on the digital entity based on the permission of the target object. Operational, able to ensure the security of operating digital entities.
  • the target object can use the self-sustained first signature data (such as a private key) to authenticate the entity through the distributed application.
  • the operation credential is signed and processed to generate statement data; and the statement data is sent to the server so that the server can perform target operations on the digital entity based on the statement data.
  • the target object can directly use the self-sustained first signature data to perform signature processing on the entity operation voucher to generate statement data.
  • the target object can also authorize the terminal device, so that the terminal device is authorized to obtain the first signature data of the target object, and uses the first signature data to sign the entity operation voucher to generate statement data.
  • the server can use any of the following methods: Get claim data:
  • the terminal device and the server are different electronic devices.
  • the server can send the entity operation voucher to the terminal device held by the target object, and then the terminal device returns the statement data obtained by the target object using the first signature data to sign the entity operation voucher.
  • the entity operation voucher can be sent to the target object, specifically to the terminal device held by the target object; so that the terminal The device displays the physical operation credentials on the display screen, as shown in Figure 4.
  • the target object can visually view the information contained in the physical operation voucher on the display screen, and when confirming that the target operation indicated by the physical operation voucher is performed on the digital entity, the target object directly or the target object authorizes the terminal device to use the target object's
  • the first signature data performs signature processing on the entity operation voucher to obtain statement data; then, the terminal device returns the statement data obtained through signature processing to the server. This allows the server to receive claim data directly from the terminal device.
  • the server can also generate an authorization request based on the entity operation credential.
  • the authorization request carries the entity operation credential.
  • the authorization request is used to request the target object authorization server to sign the entity operation credential and send the authorization request to the terminal device.
  • the terminal device responds to the received authorization request and outputs the entity operation voucher; if the target object confirms that the information contained in the entity operation voucher is correct and agrees to the authorization server for signature processing, the terminal device returns confirmation information, which indicates the target
  • the object authorization server uses the first signature data to sign the entity operation voucher. In this way, the server can obtain the first signature data of the target object based on the confirmation information, and perform signature processing on the entity operation voucher based on the first signature data to obtain the statement data.
  • the terminal device and the server are the same electronic device, that is, a distributed application is deployed in the server; in this implementation, the server can display the entity operation voucher on the display screen. If the target object adopts the first signature The data signs the entity operation voucher, and then in response to the target object using the first signature data to perform a signing operation on the entity operation voucher, a signed entity operation voucher is obtained, and the signed entity operation voucher is used as declaration data.
  • the process of signing the entity operation voucher using the first signature data of the target object may be performed directly by the target object, or may be performed by the target object authorization server.
  • the target object can use the first signature data to sign the entity operation voucher to obtain the statement data. That is, the server responds to the target object by using the target object's first signature data and performs a signature operation on the entity operation voucher to obtain the signature.
  • the signed entity operation certificate is used as the statement data.
  • the server can also receive the authorization operation of the target object for the entity operation voucher, obtain the first signature data of the target object, and the server performs signature processing on the entity operation voucher according to the first signature data of the target object, and obtains the signed Entity operation credential, the signed entity operation credential is used as claim data.
  • the target object can obtain the entity operation voucher used to instruct the execution of the target operation on the digital entity.
  • the DID protocol can be used to express and describe the digital entity, optimizing the expression and readability of the digital entity. This enables the target object to clearly understand the target operation to be performed on the digital entity based on the entity operation credentials, thereby improving the experience of the target object.
  • more application functions can be applied to digital entities, enriching the implementation scenarios of digital entities.
  • the declaration data is obtained by signing the entity operation certificate using the first signature data of the target object (such as the private key of the target object).
  • the server After the server obtains the declaration data, it needs to first perform the signature on the declaration data.
  • Signature verification processing when the signature verification of the statement data is successful, it means that the identity verification of the entity that wants to perform the target operation is successful, and the target operation can be started on the digital entity.
  • the implementation process of performing target operations on digital entities based on declaration data may include: first, since the digital identification (ie, DID identifier) of the target object is bound to the second signature data of the target object (such as the target object's public key), then the second signature data of the target object can be obtained based on the digital identification of the target object. Then, the second signature data of the target object is used to perform signature verification processing on the declaration data, and the signature verification result is obtained.
  • the digital identification ie, DID identifier
  • the second signature data of the target object is used to perform signature verification processing on the declaration data, and the signature verification result is obtained.
  • the signature verification result is a signature verification success, that is, the signature verification result indicates that the identity verification of the operator on the terminal device side is successful, the target operation is performed on the digital entity; conversely, when the signature verification result is a signature verification failure, Indicates that if the identity authentication of the operator on the terminal device side fails, the target operation will not be performed on the digital entity.
  • the embodiment of the present application adopts Asymmetric encryption technology is used to verify whether the operator of the terminal device is the target object corresponding to the digital identification recorded in the entity operation voucher, and to realize the verification of the identity of the operator on the terminal device side, thereby achieving the target operation on the digital entity.
  • Previous transaction permission verification improves the security and traceability of digital entities and can be applied to application scenarios that require review, such as alliance chain scenarios.
  • the entity operation voucher when receiving an operation request initiated by the target object for the digital entity, can be generated according to the digital identification of the target object and the operation information carried in the operation request.
  • the entity operation voucher indicates that the request is executed for the digital entity.
  • the target operation and the requester of the target operation are the target object; by generating the entity operation voucher of the digital entity, the target object can be intuitively informed of the information related to the digital entity, and the expression and readability of the digital entity can be optimized.
  • the target object confirms that the target operation is performed on the digital entity, that is, the declaration data (that is, the entity operation after signature processing) is obtained, and the signature verification of the declaration data is successful, the target operation is performed on the digital entity.
  • the embodiment of the present application uses the digital identification of the target object throughout the operation process of the digital entity, and generates the entity operation voucher and declaration data based on the digital identification of the target object.
  • the operation process for the digital entity is intuitively and reliably recorded.
  • the related operations performed by the digital entity and the execution objects of the related operations thereby improving the security of the digital entity and the traceability of the related operations, thereby efficiently and safely achieving the target operations for the digital entity.
  • the digital entity processing system involved in the embodiment of the present application may include a terminal device and a server, and a distributed application (DAPP or NFT APP) is deployed in the terminal device, or the digital entity processing system may It only includes servers, and distributed applications are deployed in the servers; in the following, a digital entity processing system including terminal devices and servers will be used as an example to focus on the specific implementation process of performing target operations on digital entities. It is not difficult to understand that the types of target operations performed on digital entities are relatively rich. The following is an example of the target operation of casting a digital entity and the target operation of transferring a digital entity in conjunction with the attached figure. The specific implementation process of the operation is introduced.
  • FIG 5 shows an exemplary flow chart of a digital entity processing method provided by the embodiment of the present application when the target operation is the operation of casting a digital entity; the digital entity processing method can be implemented by the system shown in Figure 2a
  • the terminal device and the server are jointly executed.
  • the processing method may include but is not limited to steps S501-S509:
  • S501 The terminal device sends an identity registration request to the server.
  • S502 The server responds to the identity registration request, generates and registers the digital identity of the target object.
  • S503 The server sends the digital identification of the target object to the terminal device.
  • the target object can generate an identity registration request through the terminal device, specifically through a distributed application deployed in the terminal device. Then, the terminal device sends the identity registration request to the server, and the NFT application layer in the blockchain application protocol model deployed in the server receives the identity registration request. Then, the NFT application layer calls the DID application layer, and then the DID application layer calls the DID smart contract to respond to the identification registration request to generate the digital identification of the target object, and register the digital identification of the target object on the blockchain.
  • the terminal device generates an entity operation voucher, performs signature processing on the entity operation voucher based on the first signature data, and generates statement data.
  • the entity operation voucher generated by the terminal device may be called an entity casting voucher.
  • the terminal device can generate an operation request in response to the need to cast a digital entity.
  • the operation request is used to request the casting of a digital entity; that is, the target operation for the digital entity is The operation of casting a digital entity.
  • the operation information of the target operation at least includes: the entity casting information required to cast the digital entity. If the digital entity is a digital image, then the entity casting information required to cast the digital image may include various elements that make up the digital image. Element information (such as element address or element layer, etc.).
  • the terminal device generates an entity casting voucher based on the digital identification of the target object and the operation information of the target operation.
  • the entity casting certificate is signed based on the first signature data of the target object to generate statement data.
  • the terminal device can send the operation request to the server, and the server responds to the request.
  • the operation request generates an entity casting voucher, and the specific implementation process of generating the entity casting voucher by the server is not limited here.
  • the terminal device generates a casting request based on the entity operation credential, and sends the casting request to the server.
  • the casting request carries the signed entity operation credential (ie, statement data).
  • S506 The server responds to the casting request and performs signature verification on the declaration data.
  • steps S505-S506 when the server obtains the casting request, it also obtains the declaration data carried in the casting request. Then the server can perform signature verification on the declaration data based on the digital identification of the target object, specifically the digital identification of the target object.
  • the public key of the target object is bound, so that the server can obtain the public key of the target object, verify the signature of the statement data based on the public key of the target object, and obtain the signature verification result.
  • S508 The server binds the entity ID of the digital entity and the digital ID of the target object.
  • steps S507-S508 when the signature verification of the statement data based on the second signature data of the target object is successful, it means that the identity verification of the entity on the terminal device side is successful, that is, the entity on the terminal device side uses the first signature data to cast the entity. If the certificate is digitally signed by the target object, the target operation can be performed on the digital entity.
  • the specific process can include: first, casting the digital entity according to the entity casting information required to cast the digital entity,
  • the digital entity is a digital image
  • the entity casting information required to cast the digital entity is element images belonging to different layer levels
  • the individual element images are superimposed in order from high to low (or from low to high) in the layer level.
  • Digital images can be cast.
  • the server can then create an entity identification for the minted digital entity based on the DID smart contract in the deployed blockchain application protocol model. This entity identification is the DID identification of the digital entity NFT, which is used to uniquely identify the digital entity.
  • the entity identification of the digital entity and the digital identification of the target object can be bound, so that there is a mapping and binding relationship between the entity identification of the digital entity and the digital identification of the target object.
  • This mapping and binding relationship can be stored in the block.
  • the owner of the digital entity can be determined as the target object through the mapping binding relationship, that is, the target object is the only one with the right The object of the operation permission of this digital entity to perform operations.
  • the specific implementation process of binding the digital entity and the target object may include: establishing a first mapping binding relationship based on the digital identification of the target object and the entity identification of the digital entity.
  • the first mapping binding relationship may refer to the above-mentioned The mentioned mapping and binding relationship, the first mapping and binding relationship is used to indicate the holder of the digital entity as the target object; then, the first mapping and binding relationship is stored in the smart contract corresponding to the digital entity, that is, NFT In smart contracts, with Realize the binding of digital entities and target objects.
  • S509 The server returns the casting result for the digital entity to the terminal device.
  • the server can return the casting result for the digital entity to the terminal device.
  • the casting result for the digital entity can include: the cast digital entity (such as a digital image) and the digital entity on-chain result (such as successful on-chain). and other information; the embodiments of this application do not limit the specific content contained in the casting results.
  • the entity operation voucher when receiving an operation request initiated by the target object for a digital entity, can be generated according to the digital identification of the target object and the operation information carried in the operation request, and the entity operation voucher indicates that the request is for the digital entity.
  • the target operation is executed, and the requester of the target operation is the target object; by generating the entity operation voucher of the digital entity, the target object can be intuitively informed of the information related to the digital entity, and the expression and readability of the digital entity can be optimized.
  • the target object confirms that the target operation is performed on the digital entity, that is, the declaration data (that is, the entity operation after signature processing) is obtained, and the signature verification of the declaration data is successful, the target operation is performed on the digital entity.
  • the embodiment of the present application uses the digital identification of the target object throughout the operation process of the digital entity, and generates the entity operation voucher and declaration data based on the digital identification of the target object.
  • the operation process for the digital entity is intuitively and reliably recorded.
  • the related operations performed by the digital entity and the execution objects of the related operations can thereby improve the security of the digital entity and the traceability of the related operations, thereby efficiently and safely achieving target operations on the digital entity, such as the operation of casting a digital entity.
  • Figure 7 shows an exemplary flow chart of a digital entity processing method provided by the embodiment of the present application when the target operation is the operation of transferring a digital entity; the digital entity processing method can be performed by the system shown in Figure 2a
  • the terminal device and the server are jointly executed.
  • the processing method may include but is not limited to steps S701-S706:
  • the terminal device generates an entity operation voucher, performs signature processing on the entity operation voucher according to the first signature data, and generates statement data.
  • the entity operation voucher generated by the terminal device may be called an entity transfer voucher.
  • the terminal device can generate an operation request in response to the need to transfer the digital entity.
  • the operation request is used to request the transfer of the digital entity from the target object to the reference object.
  • the target operation for the digital entity is an operation to transfer the digital entity
  • the operation information of the target operation at least includes: the digital identification of the reference object , and the entity identification of the digital entity to be transferred.
  • the terminal device in response to the operation request, the terminal device generates an entity transfer voucher based on the digital identification of the target object and the operation information of the target operation.
  • the entity transfer voucher is signed based on the first signature data of the target object to generate statement data.
  • the terminal device can send the operation request to the server, and the server responds to the The operation request calls a third-party agency to generate an entity transfer voucher; the specific implementation process of generating the entity transfer voucher by the server is not limited here.
  • the terminal device generates a transfer request based on the entity transfer voucher and sends the transfer request to the server.
  • the transfer request carries the signed entity transfer voucher (ie, statement data).
  • S703 The server responds to the transfer request and performs signature verification on the declaration data.
  • steps S702-S703 when the server obtains the transfer request, it also obtains the declaration data carried in the transfer request, and the server can perform signature verification on the declaration data based on the digital identification of the target object, specifically the digital identification of the target object.
  • the public key of the target object is bound, so that the server can obtain the public key of the target object, verify the signature of the statement data based on the public key of the target object, and obtain the signature verification result.
  • S705 The server modifies the mapping binding relationship between the entity ID of the digital entity and the digital ID of the target object.
  • steps S704-S705 when the signature verification of the statement data based on the second signature data of the target object is successful, it means that the identity verification of the entity on the terminal device side is successful, that is, the entity on the terminal device side uses the first signature data to transfer the entity.
  • the certificate is digitally signed by the target object, the target operation can be performed on the digital entity.
  • the specific implementation process of performing the target operation on the digital entity, and the target operation is the operation of transferring the digital entity can be shown in Figure 8.
  • the specific process can include:
  • the entity identifier of the digital entity is parsed.
  • the entity identifier of the digital entity is created when the digital entity is cast.
  • the entity document corresponding to the digital entity (that is, the DID document) is obtained; among them, the entity document stores the metadata of the digital entity.
  • metadata metadata includes the storage location describing the content of the digital entity (such as appearance attribute description files, pictures, etc.).
  • the entity document also includes the controller field, which records the digital identification of the target object and represents the digital entity.
  • the owner is the target object corresponding to the numerical identification recorded in the controller field.
  • the operating authority for the digital entity is transferred from the target object to the reference object, including:
  • the NFT smart contract in the blockchain application protocol model deployed by the server stores a first mapping binding relationship.
  • This first mapping binding relationship combines the entity identification of the digital entity with the digital identification of the target object.
  • the first mapping binding relationship can be modified into the second mapping binding relationship in the smart contract corresponding to the digital entity (i.e., NFT smart contract); where the first mapping binding relationship indicates the persistence of the digital entity.
  • the owner is the target object
  • the second mapping binding relationship indicates that the holder of the digital entity is the reference object.
  • the transfer operation of the digital entity can be realized, and the operation permission for the digital entity can be transferred from the target object to the reference object.
  • the holder of a digital entity transfers a digital entity
  • the holder needs to issue an entity transfer certificate of the digital entity for verification of the change of the holder of the digital entity.
  • the embodiment of the present application also Supports setting the transfer validity period for entity transfer vouchers, that is, the entity operation voucher (or signed declaration data) is time-sensitive. Only within the transfer validity period can the entity transfer voucher be verified and subsequently transferred.
  • the transfer validity period can be set for the generated statement data.
  • the transfer validity period can be preset or customized by the target object. .
  • the server after the server obtains the declaration data, it can first obtain the generation time of the declaration data.
  • the generation time refers to the time when the entity operation certificate of the digital entity is signed and processed to generate the declaration data. Then, determine the target duration between the generation time of the declaration data and the current time.
  • the current time refers to the moment when the declaration data is verified; that is, starting from the moment when the declaration data is generated until the server verifies the declaration data. Until the time when the signature is processed, this period of time is regarded as the target time.
  • the target duration is compared with the transfer validity duration; if the target duration is less than or equal to the transfer validity duration, it means that the entity transfer voucher is in a valid state, and the step of executing the target operation on the digital entity based on the declaration data can be triggered; otherwise, if The target duration is greater than the transfer validity duration, which means that the physical transfer voucher is no longer in a valid state, but in an invalid state, and it is determined that the transfer of the digital entity failed.
  • the server can perform the signature verification process on the statement data.
  • the server performs signature verification on the declaration data at 12:00 on December 15, and determines that the target time between the generation time of the declaration data and the current time is 72 hours, which is greater than the transfer validity period of 24 hours, then the server The signature verification process on the declaration data cannot be performed, and the transfer of the digital entity is determined to have failed.
  • the transfer validity period for the entity operation voucher the Entity operation credentials have a valid operation range, which can improve the security of entity operation credentials to a certain extent.
  • S706 The server returns the transfer result for the digital entity to the terminal device.
  • the server may return the transfer result for the digital entity to the terminal device, where the transfer result for the digital entity may include information such as successful transfer or failed transfer; the embodiments of this application do not make any specific content contained in the transfer result. limited.
  • the terminal device can generate an operation request in response to the need to transfer the digital entity.
  • the operation request is used to request to adjust the holder of the digital entity from the target object to Reference object, the target object is different from the reference object; that is, the target operation on the digital entity is the operation of transferring the digital entity, and the operation information of the target operation at least includes: the digital identification of the reference object, and the entity identification of the digital entity to be transferred.
  • the terminal device in response to the operation request, the terminal device generates an entity transfer voucher based on the digital identification of the target object and the operation information of the target operation.
  • the entity transfer voucher is signed based on the first signature data of the target object to generate statement data.
  • DID protocol blockchain identity layer protocol
  • Figure 9 is a schematic structural diagram of a digital entity processing device provided by an embodiment of the present application.
  • the processing device can be provided in an electronic device (such as a server) provided by an embodiment of the present application; in some embodiments , the processing device may be a computer program (including program code) running in the electronic device, and the processing device may be used to execute corresponding steps in the method embodiments shown in FIG. 3, FIG. 5 or FIG. 7.
  • the processing device may include the following units:
  • the obtaining unit 901 is configured to obtain the digital identification of the target object when obtaining an operation request initiated by the target object for the digital entity.
  • the operation request carries the operation information of the target operation requested by the target object to be performed on the digital entity;
  • the processing unit 902 is configured to generate an entity operation voucher based on the digital identification and operation information of the target object; the entity operation voucher is used to indicate a request to perform the target operation on the digital entity, and is used to indicate that the requester of the target operation is the target object;
  • the processing unit 902 is also configured to obtain statement data if the target object confirms that the target operation is performed on the digital entity.
  • the statement data is obtained by performing signature processing on the entity operation voucher using the first signature data of the target object;
  • the processing unit 902 is also used to perform target operations on the digital entity based on the declaration data.
  • the digital identification of the target object is bound to the second signature data of the target object, and the processing unit 902 is used to perform the target operation on the digital entity based on the declaration data, specifically for:
  • the target operation is performed on the digital entity.
  • the operation request is used to request to cast a digital entity
  • the target operation includes an operation of casting a digital entity
  • the operation information of the target operation includes: entity casting information required to cast the digital entity
  • processing unit 902 When the processing unit 902 is used to perform target operations on digital entities, it is specifically used to:
  • the digital entity is obtained by casting
  • the processing unit 902 is used to compare the entity identification of the digital entity and the digital identification of the target object. When performing binding processing, it is specifically used for:
  • the first mapping binding relationship is used to indicate that the holder of the digital entity is the target object;
  • the operation request is used to request to transfer the digital entity from the target object to the reference object.
  • the reference object is different from the target object.
  • the target operation includes an operation of transferring the digital entity.
  • the operation information of the target operation at least includes: the reference object.
  • processing unit 902 When the processing unit 902 is used to perform target operations on digital entities, it is specifically used to:
  • the entity document includes a controller field, and the controller field records the digital identification of the target object;
  • the smart contract corresponding to the digital entity modify the first mapping binding relationship to the second mapping binding relationship; wherein, the first mapping binding relationship indicates that the holder of the digital entity is the target object, and the second mapping binding relationship indicates that the holder of the digital entity is the target object, and the second mapping binding relationship indicates that the holder of the digital entity is the target object.
  • a certain relationship indicates that the holder of the digital entity is the reference object.
  • processing unit 902 when the processing unit 902 is used to obtain the entity document corresponding to the digital entity, it is specifically used to:
  • the entity identifier of the digital entity is parsed to obtain the entity document corresponding to the digital entity; the entity document stores the metadata of the digital entity.
  • the processing unit 902 is also used to:
  • the generation time is the moment when the entity operation voucher of the digital entity is signed and processed to generate the declaration data;
  • the current time is the moment when the declaration data is verified
  • the step of performing the target operation on the digital entity based on the declaration data is triggered.
  • the processing unit 902 is configured to obtain, if the target object confirms that the target operation is performed on the digital entity, the first signature data of the target object and the statement data obtained by performing signature processing on the entity operation voucher. :
  • the processing unit 902 is configured to obtain, if the target object confirms that the target operation is performed on the digital entity, the first signature data of the target object and the statement data obtained by performing signature processing on the entity operation voucher. :
  • the processing unit 902 is configured to respond to the target object's signature operation for the entity operation voucher and when obtaining the signed entity operation voucher, is specifically used to:
  • the signed entity operation voucher is obtained;
  • the generation process of the digital identification of the target object includes:
  • the object information includes the public key of the target object.
  • each unit in the processing device shown in Figure 9 can be separately or entirely combined into one or several additional units, or some of the units can be further divided into It is composed of multiple functionally smaller units, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application.
  • the above units are divided based on logical functions.
  • the function of one unit can also be realized by multiple units, or the functions of multiple units can be realized by one unit.
  • the processing device may also include other units.
  • these functions may also be implemented with the assistance of other units, and may be implemented by multiple units in cooperation.
  • the method can be implemented on a general computing device such as a computer including a central processing unit (CPU), a random access storage medium (RAM), a read-only storage medium (ROM), and other processing elements and storage elements.
  • a computer program (including program code) capable of executing the steps involved in the corresponding methods shown in Figure 3, Figure 5 and Figure 7, to construct the processing device shown in Figure 9, and to implement the embodiments of the present application
  • the processing method of digital entities can be recorded on, for example, a computer-readable recording medium, loaded into the above-mentioned computing device through the computer-readable recording medium, and run therein.
  • the entity operation voucher when receiving an operation request initiated by the target object for the digital entity, can be generated according to the digital identification of the target object and the operation information carried in the operation request, and the entity operation voucher indicates that the request is executed for the digital entity.
  • the target operation and the requester of the target operation are the target object; by generating the entity operation voucher of the digital entity, the target object can be intuitively informed of the information related to the digital entity, and the expression and readability of the digital entity can be optimized.
  • the target object confirms that the target operation is performed on the digital entity, that is, the declaration data (that is, the entity operation after signature processing) is obtained, and the signature verification of the declaration data is successful, the target operation is performed on the digital entity.
  • the embodiment of the present application uses the digital identification of the target object throughout the operation process of the digital entity, and generates the entity operation voucher and declaration data based on the digital identification of the target object.
  • the operation process for the digital entity is intuitively and reliably recorded.
  • the related operations performed by the digital entity and the execution objects of the related operations thereby improving the security and traceability of the digital entity, and thereby efficiently achieving the target operations for the digital entity.
  • Figure 10 shows a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application.
  • the electronic device includes a processor 1001, a communication interface 1002, and a computer-readable storage medium 1003.
  • the processor 1001, the communication interface 1002 and the computer-readable storage medium 1003 can be connected through 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.
  • the computer-readable storage medium 1003 is used to store a computer program.
  • the computer program includes 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 core and control core of the electronic device. It is suitable for implementing one or more instructions, specifically suitable for loading and executing one or more instructions to achieve Corresponding method flow or corresponding function.
  • Embodiments of the present application also provide a computer-readable storage medium (Memory).
  • the computer-readable storage medium is a memory device in an electronic device and is used to store programs and data. It can be understood that the computer-readable storage medium here may include a built-in storage medium in the electronic device, and of course may also include an extended storage medium supported by the electronic device.
  • the computer-readable storage medium provides storage space that stores the processing system of the electronic device. Furthermore, one or more instructions suitable for being loaded and executed by the processor 1001 are also stored in the storage space. These instructions may be one or more computer programs (including program codes).
  • the storage medium may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory; optionally, it may also be at least one computer-readable storage medium located far away from the aforementioned processor.
  • one or more instructions are stored in the computer-readable storage medium; the processor 1001 loads and executes one or more instructions stored in the computer-readable storage medium to implement the above digital entity processing method.
  • the processor 1001 loads and executes one or more instructions stored in the computer-readable storage medium to implement the above digital entity processing method.
  • one or more instructions in the computer-readable storage medium are loaded by the processor 1001 and execute the steps involved in the corresponding methods as shown in Figure 3, Figure 5 and Figure 7
  • Embodiments of the present application also provide a computer program product or computer program.
  • the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the above-mentioned processing method for digital entities.
  • a computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • Computer instructions may be stored in or transmitted over a computer-readable storage medium.
  • Computer instructions may be sent from one website, computer, server, or data center to another website, via wired (e.g., coaxial cable, fiber optic, digital line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. computer, server or data center for transmission.
  • Computer-readable storage media can be any available media that can be accessed by the computer, or data processing equipment such as servers and data centers integrated with one or more available media. Available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.

Abstract

本申请实施例提供了一种数字实体的处理方法、装置、设备、介质及程序产品，其中的方法包括：在获取到目标对象针对数字实体发起的操作请求时，获取目标对象的数字标识；基于目标对象的数字标识和操作信息生成实体操作凭证；若目标对象确认对数字实体执行目标操作，则获取声明数据，该声明数据是采用目标对象的第一签名数据，对实体操作凭证执行签名处理得到的；基于声明数据对数字实体执行目标操作。采用本申请实施例能够提高数字实体的安全性和相关操作的可追溯性。

Description

一种数字实体的处理方法、装置、设备、介质及程序产品
本申请要求于2022年07月29日提交中国专利局、申请号为2022109138257、申请名称为“一种数字产品的处理方法、装置、设备、介质及程序产品”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及数字实体的处理技术。
背景技术
数字实体是基于区块链技术进行唯一标识的数字化实体；相比于实际的实体而言，数字实体具有便于携带、传播以及永久保存等优势。
目前，支持针对数字实体执行铸造、发布或转移等操作，以实现数字实体的铸造和流通。然而，目前针对数字实体执行操作时，并未考虑数字实体的安全性和操作的可追溯性等问题，相关操作者可以直接针对数字实体执行相应操作(如转移数字实体)，而后台并未设置任何相关的操作记录机制。可见，如何提高安全性和可追溯性，成为当前亟待解决的问题。
发明内容
本申请实施例提供一种数字实体的处理方法、装置、设备、介质及程序产品，能够提高数字实体的安全性和相关操作的可追溯性。
一方面，本申请实施例提供了一种数字实体的处理方法，由电子设备执行，该方法包括：
在获取到目标对象针对数字实体发起的操作请求时，获取目标对象的数字标识，操作请求中携带目标对象请求针对数字实体执行的目标操作的操作信息；
基于目标对象的数字标识和操作信息生成实体操作凭证；实体操作凭证用于指示请求针对数字实体执行的目标操作，且用于指示目标操作的请求者为目标对象；
若目标对象确认对数字实体执行所述目标操作，则获取声明数据，该声明数据是采用目标对象的第一签名数据对实体操作凭证执行签名处理得到的；
基于声明数据，对数字实体执行目标操作。
另一方面，本申请实施例提供了一种数字实体的处理装置，该装置包括：
获取单元，用于在获取到目标对象针对数字实体发起的操作请求时，获取目标对象的数字标识，操作请求中携带目标对象请求针对数字实体执行的目标操作的操作信息；
处理单元，用于基于目标对象的数字标识和操作信息生成实体操作凭证；实体操作凭证用于指示请求针对数字实体被执行目标操作，且用于指示目标操作的请求者为目标对象；
处理单元，还用于若目标对象确认对数字实体执行所述目标操作，则获取声明数据，该声明数据是采用目标对象的第一签名数据，对实体操作凭证执行签名处理得到的；
处理单元，还用于基于声明数据，对数字实体执行目标操作。
另一方面，本申请提供了一种电子设备，该设备包括：
处理器，用于加载并执行计算机程序；
计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，该计算机程序被处理器执行时，实现上述数字实体的处理方法。
另一方面，本申请提供了一种计算机可读存储介质，计算机可读存储介质存储有计算 机程序，该计算机程序适于由处理器加载并执行上述数字实体的处理方法。
另一方面，本申请提供了一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述数字实体的处理方法。
本申请实施例中，在接收到目标对象针对数字实体发起的操作请求时，可根据目标对象的数字标识和操作请求携带的操作信息生成实体操作凭证，且该实体操作凭证指示了请求针对数字实体执行目标操作，以及目标操作的请求者为目标对象；通过生成数字实体的实体操作凭证，使得目标对象能够获取到实体操作凭证，从而通过实体操作凭证直观地告知目标对象数字实体有关的信息，优化数字实体的表达和可读性。并且，只有在目标对象确认对数字实体执行目标操作时，即获取到声明数据(即签名处理后的实体操作凭证)，且对声明数据验签成功的情况下，才对数字实体执行目标操作。本申请实施例将目标对象的数字标识贯穿对于数字实体的操作过程，基于目标对象的数字标识生成实体操作凭证和声明数据，如此，在对数字实体执行目标操作的过程中，直观可靠地记录针对该数字实体执行的相关操作以及相关操作的执行对象，从而确保数字实体的安全性和相关操作的可追溯性。
附图说明
图1a是本申请一个示例性实施例提供的一种区块链的结构示意图；
图1b是本申请一个示例性实施例提供的一种数据共享系统的结构示意图；
图2a是本申请一个示例性实施例提供的一种数字实体的处理系统的架构示意图；
图2b是本申请一个示例性实施例提供的一种区块链应用协议模型的结构示意图；
图2c是本申请一个示例性实施例提供的一种NFT智能合约和DID智能合约之间的协议映射关系的示意图；
图2d是本申请一个示例性实施例提供的一种基于DID协议的NFT协议设计的示意图；
图3是本申请一个示例性实施例提供的一种数字实体的处理方法的流程示意图；
图4是本申请一个示例性实施例提供的一种输出实体操作凭证的示意图；
图5是本申请一个示例性实施例提供的另一种数字实体的处理方法的流程示意图；
图6是本申请一个示例性实施例提供的一种铸造数字实体的流程示意图；
图7是本申请一个示例性实施例提供的又一种数字实体的处理方法的流程示意图；
图8是本申请一个示例性实施例提供的一种转移数字实体的流程示意图；
图9是本申请一个示例性实施例提供的一种数字实体的处理装置的结构示意图；
图10是本申请一个示例性实施例提供的一种电子设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例提供了一种数字实体的处理方法，该处理方法主要涉及区块链技术，具体涉及区块链技术中的典型应用，包括：分布式身份(Decentralized Identity，DID)以及非同质化通证(Non-Fungible Token，NFT)。
下面对本申请实施例涉及的技术术语和概念进行简要说明，其中：
1)区块链(Blockchain)，是区块链技术的基础；所谓区块链是分布式数据存储、点对点传输、共识机制、加密算法等计算机技术的新型应用模式。区块链本质上是一个去中心化的数据库，是一串使用密码学方法相关联产生的数据块，每一个数据块中包含一批次网络交易的信息，用于验证其信息的有效性(防伪)和生成下一个区块。一种区块链的结构示意图可参见图1a，如图1a所示，区块链由多个区块组成，区块链的第一个区块称为创世区块(可简称为创世块)，创世块中包括区块头和区块体，区块头中存储有输入信息特征值、版本号、时间戳和难度值，区块体中存储有输入信息；创世块的下一区块以创世块为子区块，也可以理解为创世块为该下一区块的父区块，下一区块中同样包括区块头和区块体，区块头中存储有父区块的区块头特征值、当前区块的输入信息特征值、版本号、时间戳和难度值，并以此类推，使得区块链中每个区块中存储的区块数据均与父区块中存储的区块数据存在关联，保证了区块中输入信息的安全性。
区块链可由区块链网络所包含的区块链节点维护；其中，区块链网络可以理解为一个数据共享系统，是指用于实现区块链节点与区块链节点之间数据共享的系统，该数据共享系统的一种示例性结构可参见图1b；如图1b所示，数据共享系统中可包括多个区块链节点101，各个区块链节点101可以为接入至该区块链网络中的服务器，也可以为接入至该区块链网络中的终端(如终端中运行的客户端)，这里对区块链节点101的具体形式不做限定。对于区块链网络中的每个区块链节点101，均具有与其对应的节点标识，而且区块链网络中的每个区块链节点101均可以存储有区块链网络中其它区块链节点101的节点标识，以便后续根据其它区块链节点101的节点标识，将生成的区块广播至数据共享系统中的其它区块链节点101，以实现在区块链网络分布式存储区块所包含的数据，确保数据的不可篡改性、不可复制性以及永久保存。
需要特别说明的是，①基于区块链网络实现某种业务时，必须要遵守智能合约。智能合约可以是指：将执行业务所需的协议规范以代码形式部署于区块链网络上的数字化协议；具体是将智能合约部署于区块链网络中的区块链节点上，从而通过区块链节点来运行智能合约，以实现智能合约对应的业务。例如，智能合约对应的业务为交易，即智能合约是用于交易的合约，如智能合约包括：查询消费者所购买商品的物流状态，在消费者签收货物后将消费者的电子资源(如在互联网中用于商品交易的资源)转移到商户的地址；那么，在消费者已签收货物后，就可以运行该智能合约(具体是运行该智能合约的代码)将消费者的电子资源(如在互联网中用于商品交易的资源)转移到商户的地址。当然，上述只是本申请实施例给出一种示例性的智能合约的应用。
②根据区块链网络的对外开放程度不同，区块链网络维护的区块链主要分为三大类型，包括：公有链(Public Block Chains)、联盟链(Consortium Block Chains)和私有链(Private Block Chains)。其中，公有链可是指：区块链网络中的任何节点(如单个对象或集体对象对应的区块链节点)均可以发送交易数据，且交易数据能获得有效确认的、任何节点都能参与共识过程的区块链。联盟链可是指：区块链网络中的部分节点可以参与区块共识过程，而其他节点不具有访问共识过程的区块链；例如，包含联盟链的区块链网络内部可指定多个预选的区块链节点为记账节点(如具有共识权限的区块链节点)，联盟链上的每个区块均由所有记账节点共同决定(即预选的区块链节点参与共识过程)，区块链网络中除记账节点以外的其他接入的区块链节点可以参与交易，但不过问共识过程。私有链可是指：区块链网络中的一个区块链节点独享写入权限(如对区块共识后上链)的区块链。
2)数字实体可以包括非同质化通证(Non-Fungible Token，NFT)，是一套基于区块链技术的数字资产协议；具体是将实体数字化后放到区块链上，使得该实体数字化成为独一无二、不可分割以及稀有的数字化实体；为便于阐述，后续以缩写NFT代表数字实体。 其中，能够铸造成数字实体的实体形态可包括但不限于：数字图像(或数字图片)、音视频、3D(3-dimension，三维)模型、电子票证以及数字纪念品等形式；本申请实施例对被铸造成数字实体的实体形态不作限定。数字实体存储于区块链上，具有不可篡改、不可复制等特性，使得数字实体相较于实物实体而言，具有其独特的价值。例如，数字实体对应的数字凭证可存储至区块链上，这样只要区块链一直存在，数字实体就可以永久保存，不被篡改和复制。再如，数字实体以数字化形式存在于区块链中，便于拥有者携带和传播。
在实际应用中，可在区块链网络中针对数字实体执行交互操作(或称为目标操作)，包括但不限于：数字实体的铸造以及数字实体的转移等。所谓数字实体的铸造是指：使用区块链技术对数字实体进行数字手段加密处理，数字实体就拥有了一张唯一标识身份的数字凭证(或称为序列号、区块链编号等)，该数字凭证可作为持有者拥有数字实体的权利证明；再将数字实体对应的数字凭证存储至区块链上，以实现数字实体的上链的过程。所谓数字实体的转移是指：将数字实体从当前持有者转移至另一个对象的过程，转移后另一个对象具有该数字实体的操作权限。例如，数字实体的当前持有者为目标对象(如任一对象)，那么目标对象将数字实体转移至参考对象(如与目标对象不同的另一对象)，实质是将对数字实体的操作权限(如售卖、展示等操作)转移给参考对象，转移后，参考对象具有对该数字实体进行操作的操作权限。
正如前述所描述的，智能合约将协议规范以代码形式部署于区块链网络上，这使得目标对象可通过去中心化应用(DecentralizedApplication，DApp)(如NFT钱包)来访问区块链网络上的NFT智能合约，实现对数字实体(或称为数字资产)的铸造或转移等目标操作。具体地，NFT智能合约遵循NFT智能合约接口协议标准(如ERC721或ERC1155)，以便于第三方服务(如NFT交易所)调用NFT标准接口，实现针对NFT的互操作(如NFT铸造、发行、买卖等)。并且，数字资产在区块链上以token的形式锁定在对应的账户下，token关联了NFT资产的元数据metadata，元数据metadata中包含了描述NFT内容的相关信息，包括但不限于：存储位置或历史数据等。
3)分布式身份(Decentralized Identity，DID)，或称为分布式数字身份，
本质上是一套基于区块链技术的数字身份标识和凭证签名验签协议，包含了分布式身份标识符DIDs和可验证的凭证(Verifiable Credentials，VCs)两大核心组件。分布式数字身份的基础设施可部署于分布式环境(如区块链网络)中，而不是部署于单一组织或联盟组织控制的中心化环境，能够实现身份真正地具有自主权，此处的身份可是指人、组织或物品的身份；换句话说，拥有分布式数字身份的对象(或称为实体)不限于具有生命活动的人或动物，还可以是不具有生命活动的其他物品等。
其中，分布式数字身份标识符(DIDs)是由字符串(字符组成的一串数据，如ahd21db23XX)组成的标识符，用来代表一个目标对象的数字身份，不需要注册机构就可以实现全球唯一性。一个对象往往可以拥有多个数字身份，每个数字身份被分配唯一的DID值，以及与之关联的非对称密钥(即不相同的公钥和私钥)；不同的数字身份之间没有关联信息，从而有效地避免了所有者身份信息的归集。可验证凭证VCs是由凭证发行者对实体(如目标对象)的属性背书形成的声明文件；可验证凭证可以是一个身份所有者(如个人或组织)自己发出的，也可以是由其他凭证发行人发出的。例如，数字身份是由凭证发行人发布的，具体可以是由身份背书方(凭证发行方)根据身份所有人请求，对身份所有者的属性信息进行背书签署发布的。值得注意的是，根据身份所有者不同以及凭证生成场景不同，身份所有者的属性信息并不相同，进而基于属性信息生成的可验证凭证也不相同。例如，在学历认证场景中，身份背书方可是学校所使用的节点，可验证凭证可是学校对学生的属性信息(如年龄信息、专业信息、成绩信息及院校信息等)进行背书生成 学生的如学历证书。
基于上述对区块链网络、数字实体以及分布式数字身份的相关介绍，本申请实施例提出一种数字实体的处理方案。该方案支持将NFT本身、NFT发行者(即铸造NFT的对象)、NFT持有者(即具有对数字实体的操作权限的对象，该对象与NFT发行者可相同或不同)等对象的身份通过DID数字身份表达，以DID协议表达和描述NFT及相关参与方，使区块链数字资产具备DID和NFT两层技术协议属性。本方案结合了DID协议规范和NFT协议规范，能够基于DID协议规范实现NFT的所有技术能力，包括铸造、发布和转移等功能，是一种新型的NFT实现方案。
本方案的大致原理可包括：在目标对象具有对数字实体执行目标操作(如铸造或转移)的需求时，目标对象可发起针对数字实体的操作请求；响应该操作请求，获取目标对象的数字标识，该数字标识用于唯一标识目标对象的身份，如身份ID、编号或昵称等。然后，可以基于目标对象的数字标识和操作请求携带的目标操作的操作信息，生成实体操作凭证，该实体操作凭证用于指示目标对象想要针对数字实体执行的目标操作。在目标对象确认对数字实体执行实体操作凭证所指示的目标操作的情况下，可获取采用目标对象的第一签名数据(如私钥)签名得到的声明数据，并在采用目标对象的第二签名数据(如公钥)对声明数据验签成功的情况下，对数字实体执行目标操作，以实现针对数字实体执行操作的功能。
综上所述，本申请实施例在传统的NFT操作实现过程中引入DID协议，能够结合DID协议和NFT协议的优势，使得本申请实施例提供的数字实体的处理方案具有包括但不限于如下优势：①由于分布式数字身份标识符和可验证凭证具有国际标准、强大表达能力、可读性和安全性等优势，使得通过DID协议表达和描述NFT及相关参与方(如NFT本身、NFT发行者、NFT持有者等实体)的身份时，能够让NFT的描述更加丰富和完整，并有较好的技术扩展性，优化了NFT的表达和可读性。②通过DID实现NFT，实现了两层协议的互联互通和上下支撑，这样NFT除了遵循本身的协议规范外，还可以通过DID层的协议来完成协议互操作，有更好的协议兼容性和互操作可移植能力，利用DID的路由和跨链能力使NFT支持更多的协议能力，提高了数字资产层的互操作性、可移植性和场景扩展能力，便于更多的场景落地。③DID协议下的可验证凭证还具备第三方签名和验签的能力，这意味着基于DID实现的NFT实现方案具备更好的监管能力，如DID的铸造和转移凭证可以通过第三方权威机构来签名验签完成，这是基于单层NFT协议实现所不具备的；而通过分布式数字身份标识符DIDs较高的可读性和回溯性，可以对NFT施加更多的监管功能，使得本申请实施例能够适应具有监管要求的NFT场景，如基于联盟链的NFT落地场景。
为便于更好地理解本申请实施例提出的数字实体的处理方法，下面结合图2a给出一种示例性的该方法可应用的数字实体的处理系统；如图2a所示，该数字实体的处理系统包括终端设备201和服务器202，本申请实施例对终端设备201和服务器202的数量和类型不做限定，在此说明。下面对该数字实体的处理系统所涉及的电子设备进行说明，其中：
(1)终端设备201可是指：部署有分布式应用程序(即前述提及的去中心化应用DApp)的设备。该终端设备201可以是属于区块链网络的区块链节点设备，或者，还可以是独立于区块链网络、但由区块链网络中的区块链为DApp提供可信数据的设备。该终端设备201可包括但不限于：智能手机(如Android手机、iOS手机等)、平板电脑、便携式个人计算机、移动互联网设备(Mobile Internet Devices，简称MID)、智能电视、车载设备、头戴设备等。
其中，终端设备201中部署的数字实体的分布式应用程序，是支持目标对象发送关于数字实体的操作请求的应用客户端。本申请实施例对分布式应用程序的运行方式不作限定；例如，分布式应用程序是通过安装包部署在终端设备201上的客户端；再如，分布式应用程序可以以在线应用的形式运行于终端设备上；又如，分布式应用程序可以以小程序的形式运行于终端设备中部署的其他应用程序之中。
通过终端设备中部署的分布式应用程序可实现但不限于如下功能：
①生成和保存目标对象的公私钥。所谓公私钥可包括：公开密钥(publickey简称公钥)和私有密钥(privatekey简称私钥)；公钥与私钥是一对密钥，如果加密方采用目标对象的私钥对数据进行加密，那么解密方只有用目标对象的私钥对应的公钥对加密后的数据进行解密，才能得到解密后的数据。换句话说，分布式应用程序具有为目标对象生成公私钥的能力，并在生成目标对象的公私钥后，为目标对象保存公私钥。
②接收并保存目标对象的数字标识，此处的数字标识即是指前述描述的分布式数字身份标识符(DIDs)，对此不作区分描述。也就是说，终端设备中部署的分布式应用程序还能够接收目标对象的数字标识，并实现对接收到的数字标识的保存功能。
③生成并保存目标对象的实体操作凭证，此处的实体操作凭证可是指前述提及的可验证凭证VCs，对此不作区分描述。根据目标对象想要对数字实体执行的操作的不同，该可验证凭证VCs并不相同。例如：在目标对象想要铸造数字实体的场景中，所谓铸造数字实体可简单理解为：生成数字实体并将数字实体上链的过程，此时生成的可验证凭证用于指示：数字实体被请求执行铸造操作，即请求铸造数字实体。再如：在目标对象想要转移数字实体的场景中，所谓转移数字实体可简单理解为：将数字实体的操作权限从一个对象转移至另一个对象，此时生成的可验证凭证用于指示：数字实体被请求执行转移操作，即请求转移数字实体。
(2)服务器202可是指：具有实现数字实体对应的交互操作(如铸造或转移等操作)的功能的设备；该服务器202是属于区块链网络的区块链节点设备。服务器202中部署有本申请实施例创新性提出的一种基于DID的NFT协议模型，该基于DID的NFT协议模型还可以称为区块链应用协议模型；服务器具体可以通过该区块链应用协议模型实现数字实体对应的交互操作。参见图2b，该区块链应用协议模型自上而下分别包括：NFT协议层、DID协议层以及区块链网络。各个协议层中可包括相应的应用层和智能合约，如NFT协议层中包括NFT应用层和NFT智能合约，同理，DID协议层中包括DID应用层和DID智能合约；下面结合图2b分别对协议层中的应用层和智能合约的功能进行介绍。
NFT协议层包括NFT应用层和NFT智能合约，下面分别对NFT应用层和NFT智能合约的功能进行简单介绍。其中：
①NFT应用层可用于处理终端设备发送的操作请求。例如，操作请求可包括实体数字标识注册请求，此情况下，NFT应用层可以统一处理NFT应用端侧(如终端设备中的NFT钱包)的实体DID标识注册请求，具体是响应于DID标识注册请求通过调用DID协议层，如调用DID应用层或DID智能合约，完成目标对象的数字标识符(或简称为数字标识)的生成和注册。另外，注册得到的数字标识还绑定目标对象的公钥，这样也可通过数字标识绑定的公钥，以及通过非对称加密技术可以验证NFT应用端的操作人是否是对应的数字标识的目标对象，以实现对目标对象的身份校验，提高数据处理的安全性。
NFT应用层在注册得到目标对象的数字标识后，还可以将目标对象的数字标识分配至终端设备(即NFT应用端)，这样目标对象可基于数字标识通过NFT应用端(即前述提及的DApp)发起与数字实体相关的操作请求(或称为NFT操作请求)，使得NFT应用层处理NFT应用端发送的铸造和转移等NFT操作请求。例如，在NFT铸造场景，NFT应 用层可通过调用DID应用层直接在DID智能合约中生成token(即数字实体)对应的DID标识符(为便于区分目标对象的DID标识符和数字实体的DID标识符，将数字实体的DID标识符称为实体标识)，或者，NFT应用层可通过NFT智能合约间接在DID智能合约中生成token对应的DID标识符。再如，在NFT转移场景，NFT应用层可通过调用DID应用层直接验证目标对象对应的可验证凭证VCs，或者NFT应用层可通过NFT智能合约间接验证目标对象对应的可验证凭证VCs，检查目标对象是否具有对数字实体进行操作的操作权限，如检测目标对象是否具有转移数字实体的转移权限，或者，检测目标对象是否具有铸造数字实体的铸造权限。
②NFT智能合约用于处理和管理与数字实体相关的数据。例如，NFT智能合约中存储有目标对象的数字标识和数字实体的实体标识之间的绑定关系，用于锚定数字实体的对象归属。例如，数字实体A的实体标识与目标对象a的数字标识之间具有绑定关系(或称为绑定映射关系)，该绑定关系锚定了数字实体A的持有对象为目标对象a，则根据该绑定关系确定数字实体A的持有者为目标对象a。为了提高智能合约的公信力，NFT智能合约可以直接调用DID智能合约生成数字实体的DID标识符，以及直接调用DID智能合约验证可验证凭证VCs，并在可验证凭证VCs验证成功后，对数字实体执行相应的目标操作，如可修改目标对象的数字标识和数字实体的实体标识之间的绑定关系，以完成数字实体的转移。
与NFT协议层类似的，DID协议层包括DID应用层和DID智能合约，下面分别对DID应用层和DID智能合约的功能进行简单介绍。其中：
①DID应用层可用于处理协议模型中位于其上的NFT应用层发送的操作请求(如创建数字标识或验证凭证等操作请求)，以及，用于在协议模型中向下对接DID智能合约读写DID状态数据。也就是说，DID应用层作为一个中间层，只要需在DID智能合约中处理的业务逻辑均可以通过DID应用层作为服务入口，进入DID智能合约。
其中，DID状态数据包括但不限于：目标对象的DID文档所包含数据，以及数字实体的DID文档所包含数据。目标对象的DID文档可以由DID智能合约对目标对象的数字标识进行解析得到，同理，数字实体的DID文档可以由DID智能合约对数字实体的实体标识进行解析得到的。换句话说，每个DID标识对应各自的DID文档，任一实体的DID文档用于描述和表达该任一实体的内容。例如：该任一实体为目标对象，那么目标对象的DID文档所包含的文档数据可包括与目标对象相关的信息，包括但不限于：目标对象的公钥以及属性信息(如年龄、昵称、性别或注册时间等信息)。再如：该任一实体为数字实体，那么数字实体的DID文档所包含的文档数据可包括与数字实体相关的信息，包括但不限于：数字实体的属性信息(如数字实体的形态信息、铸造时间等信息)和数字内容(如数字实体所包含的元素信息)等元数据metadata，用于表达NFT实体(即数字实体)的全部或部分信息。
②DID智能合约可用于处理和管理与DID相关的数据。例如，DID智能合约中存储有DID的所有状态数据，包括目标对象和数字实体的DID文档，具体是DID文档所包含的文档数据。在涉及数字实体的不同应用场景(如铸造数字实体的场景，或转移数字实体的场景)中，均可以通过DID应用层和NFT智能合约读写DID智能合约中的DID状态数据。另外，DID智能合约还包含验证可验证凭证的合约接口，DID智能合约通过调用该合约接口，可实现验证被签名的可验证凭证是否由对应DID实体(如采用私钥签名的目标对象)签发。
本申请实施例提供的NFT智能合约和DID智能合约之间的协议映射关系，可以参见图2c。如图2c所示，NFT智能合约中存储有目标对象的数字标识(目标对象的DID标识) 以及数字实体的实体标识(NFT token DID标识)；并且，在NFT智能合约中还存储有目标对象的数字标识和数字实体的实体标识之间的绑定映射关系，通过该绑定映射关系可以确定数字实体的持有者为目标对象。DID智能合约中存储有目标对象的DID文档，该目标对象的DID文档是通过对目标对象的数字标识进行解析得到的，可以理解为目标对象的对象标识与目标对象的DID文档之间的具有绑定关系；同理，DID智能合约中还存储有数字实体的DID文档，该数字实体的DID文档是通过对数字实体的实体标识进行解析得到的，可以理解为数字实体的实体标识与数字实体的DID文档之间的具有绑定关系。进一步的，在DID智能合约中的数字实体的DID文档中还包括controller控制者字段，该controller控制者字段可标识出数字实体所归属的目标对象，具体是对该controller控制者字段赋值目标对象的数字标识，表示数字实体的归属者为目标对象，即目标对象具有对数字实体进行交互操作的操作权限。
为实现两种协议共同完成数字实体的处理方法，需对DID协议和NFT协议进行设计，目的在于确定DID协议和NFT协议两边的字段的映射关系(或称为对应关系)，如为协议中的某些字段赋值等，使得基于任一方协议中的某个字段能够识别出另一方协议内容。例如，获取到一个DID文档后，可根据DID文档中的字段确定该DID文档是一个数字实体的实体文档。
本申请实施例提供的基于DID协议的NFT协议设计的示意图可参见图2d，下面结合图2d对本申请实施例给出的几种示例性的协议设计进行简单介绍，并不会对本申请实施例产生限定。其中，基于DID的NFT协议设计中可定义但不限于如下规范：
①支持由对象侧(即目标对象所使用的终端设备侧)产生目标对象的第一签名数据和第二签名数据，如对象侧产生基于非对称密码学算法的公私钥，第一签名数据为公钥，第二签名数据为私钥。还支持应用协议模型(即前述提及的区块链应用协议模型)将目标对象的公钥按照DID规范转码为目标对象的数字标识，并注册到区块链上。
②支持对铸造得到的数字实体创建实体标识，即被铸造产生的数字实体本身也同样具备DID身份标识，且该DID身份标识对应有DID文档(即前述提及的实体文档)用于描述和表达NFT协议标准中的数字实体内容。
③支持将数字实体对应的DID文档中的服务字段(如service字段)赋值为数字实体的实体标识，以便通过该实体标识能够访问到数字实体的元数据metadata，即通过该字段实现对数字实体的元数据metadata的访问。例如，数字实体为数字图像，那么可以为数字实体对应的DID文档中的service字段赋值数字实体的资源标识符(Uniform Resource Identifier，URI)，以实现通过该数字实体的URI访问数字实体的元数据metadata。
其中，数字实体的元数据metadata可以保存在数字实体发行平台网关中，通过数字实体的数字标识可以访问数字实体发行平台网关中存储的元数据metadata；元数据metadata中包含了数字实体NFT的属性信息，该属性信息可以以JSON形式保存在去中心化存储或对象存储等各类存储服务中；元数据metadata中还保存了NFT的视觉呈现文件(如数字图像)的访问路径。
④支持将数字实体对应的DID文档中的控制者字段(controller)绑定目标对象的数字标识，以表示数字实体的实体标识和目标对象的数字标识之间的绑定关系，即数字实体的归属者为目标对象。且DID文档的状态数据(即DID文档所包含数据)可以持久化在区块链上，确保数据的不可篡改。
⑤若目标对象想要针对数字实体执行的交互互操作包括转移数字实体的操作，那么在数字实体的持有者(如目标对象)转移数字实体的场景中，可以为数字实体的持有者签发的可验证凭证(或称为实体转移凭证)设置转移有效时长，那么在实体操作凭证的claim 声明中需要包含待接收数字实体的参考对象的数字标识以及数字实体的实体标识；并且，实体转移凭证需由目标对象(即持有者)签名。当然，根据业务需求claim声明中还可以包含其他自定义所需的转移条件，具体在claim声明中配置的信息可以根据应用场景灵活配置和扩展，在此不作限定。
需要说明的是，通过上述对区块链应用协议模型的相关介绍可知，在不同区块链网络(如图2b所示的区块链网络A和区块链网络B)上通过DID协议层可屏蔽底层区块链网络的差异性，而NFT协议层在DID协议层之上构建，即NFT协议层可调用下层的DID协议层，这样NFT资产可以基于DID协议的身份标识符Decentralized Identifier(DIDs)和可验证凭证Verifiable Credentials(VCs)协议实现不同智能合约或不同区块链网络之间的互操作性。并且，为NFT协议提供标准的区块链身份层协议支撑，增强以联盟链为底层的NFT实现方案的账户和资产安全性和自主控制能力。
还需说明的是，本申请实施例还支持将应用层的功能集成至智能合约中，这样区块链应用协议模型中的NFT协议层和DID协议层中可以只包括智能合约，而不包含额外的应用层。另外，本申请实施例涉及的数字实体的处理系统除包括终端设备201和服务器202以外，数字实体的处理系统还可以只包括服务器，此种实现方式下，分布式应用程序可以部署于服务器中；本申请实施例对数字实体的处理系统所包含的设备的种类和数量不作限定。另外，本申请实施例运用到具体实体或技术中时，如获取目标对象的数字标识时，此时需要获得目标对象的许可或者同意；且相关数据的收集、使用和处理需要遵守相关国家和地区的相关法律法规和标准，如针对数字实体执行的互操作需要遵循相关国家和地区的相关法律法规和标准。
基于上述描述的数字实体的处理方案，本申请实施例提出更为详细的数字实体的处理方法，下面将结合附图对本申请实施例提出的处理方法进行详细介绍。
图3示出了本申请一个示例性实施例提供的一种数字实体的处理方法的流程示意图；该数字实体的处理方法可以由电子设备执行，例如由图2a所示系统中的服务器来执行，该处理方法可包括但不限于步骤S301-S304：
S301：在获取到目标对象针对数字实体发起的操作请求时，获取目标对象的数字标识。
具体实现中，在目标对象具有针对数字实体执行目标操作的需求时，目标对象通过其持有的电子设备发起操作请求，该操作请求中携带其请求针对数字实体执行的目标操作的操作信息，该操作信息是用于描述请求针对数字实体执行的目标操作的信息；然后，响应于该操作请求可获取目标对象的数字标识。其中，根据目标操作不同，目标操作的操作信息并不相同。如针对数字实体的目标操作可包括但不限于：铸造操作或转移操作等；目标操作为铸造操作时，目标操作的操作信息至少包括：铸造数字实体所需的实体铸造信息(如数字实体所包含的各种元素的元素信息)、铸造的数字实体的归属者的数字标识、…；目标操作为转移操作时，目标操作的操作信息至少包括：待接收数字实体的参考对象的数字标识、数字实体被转移前的持有者的数字标识、…。
由前述描述可知，目标对象持有的终端设备与本申请实施例的执行主体服务器可以是同一电子设备或不同电子设备，那么根据本申请实施例涉及的系统不同，生成操作请求的电子设备可以为终端设备或服务器，具体可是具有调用第三方机构生成可验证凭证的功能的电子设备。可选的，终端设备与服务器为不同电子设备，目标对象可在其持有的终端设备中执行发起操作，这样终端设备可以根据检测到的发起操作生成操作请求；并且，在由服务器调用第三方机构生成实体操作凭证的前提下，由终端设备将该操作请求发送至服务器，以使服务器响应于该操作请求执行获取目标对象的数字标识的操作。当然，如果终端 设备具有调用第三方机构生成实体操作凭证的能力，那么终端设备在生成操作请求后，可直接响应操作请求执行生成实体操作凭证的操作，而无需将操作请求发送至服务器。可选的，终端设备与服务器为同一电子设备，目标对象可在服务器中执行针对数字实体的发起操作，这样服务器可根据检测到的发起操作生成相应的操作请求，并响应于操作请求执行获取目标对象的数字标识的操作。本申请实施例用于生成操作请求的电子设备具体为终端设备还是为服务器不作限定。
可以理解的是，根据目标对象欲对数字实体执行的目标操作的不同，目标对象执行发起操作的具体实施过程也不相同。例如，目标对象想要针对数字实体执行的目标操作为铸造操作，则目标对象通过电子设备执行的发起操作可包括：在电子设备提供的显示屏幕(或简称为显示器、显示屏等)中输入铸造数字实体所需的实体铸造信息。再如，目标对象想要针对数字实体执行的目标操作为转移操作，则目标对象通过电子设备执行的发起操作可包括：在电子设备提供的显示屏幕中输入待转移的数字实体的实体标识，以及待接收的参考对象的数字标识等信息。上述只是本申请实施例给出的两种发起操作的示例性过程，在目标操作为其他操作的情况下，目标对象执行的发起操作还可以发生适应性变化，本申请实施例对此不作限定。
进一步的，在接收到目标对象针对数字实体发起的操作请求后，响应于该操作请求获取目标对象的数字标识的实现过程可包括：从存储空间中获取目标对象的数字标识，或者，生成目标对象的数字标识，并将数字标识注册到区块链上。换句话说，若在接收到目标对象针对数字实体执行的操作请求之前，目标对象的数字标识已生成，则在接收到该操作请求时，可以直接从存储空间中获取目标对象的数字标识，具体是从存储空间中用于存储数字标识的列表中获取目标对象的数字标识。其中，存储空间的数字标识可能是DID智能合约在生成数字标识后，存储至存储空间中的；或者，存储空间的数字标识还可能是其他区块链节点将目标对象的数字标识注册到区块链上时，分布式存储至存储空间中的。反之，若在接收到目标对象针对数字实体执行的操作请求之前，未生成和注册目标对象的数字标识，则可以基于该操作请求先生成和注册目标对象的数字标识，以实现获取到目标对象的数字标识。
其中，目标对象的数字标识可以是根据目标对象的对象信息生成的、能够唯一确定目标对象的标识，目标对象的对象信息可包括但不限于：目标对象的属性信息(如昵称、ID号码等)或目标对象的公钥等。具体地，目标对象的数字标识的生成过程可包括：先获取目标对象的对象信息，然后，将对象信息转换为目标对象的数字标识。举例来说，假设目标对象的对象信息包括目标对象的公钥，则可以将公钥按照DID规范转码为数字标识，并将生成的数字标识注册到区块链上，以获取目标对象的数字标识。
根据目标对象的数字标识的生成时机的不同(如是在接收到操作请求之前或之后生成的)，生成目标对象的数字标识的流程有所差异，其中：
在一种实现方式中，假设目标对象的数字标识是在接收到目标对象针对数字实体发起的操作请求之前生成的，那么目标对象的数字标识的生成过程可包括：在目标对象具有注册标识的需求时，目标对象可发起标识注册请求，该标识注册请求中携带目标对象的对象信息；进而，可响应于该标识注册请求，将对象信息转换为目标对象的数字标识。然后，在区块链上注册目标对象的数字标识，使得区块链网络中的各个区块链节点能够同步到目标对象的数字标识，实现对目标对象的数字标识的分布式存储；这样后续区块链网络中的任一区块链节点在具有获取目标对象的数字标识的需求时，均可以直接从区块链上同步。这种预先在区块链上注册目标对象的数字标识的方式，在一定程度上能够提高后续针对数字实体执行相关操作的速度和效率。
在另一种实现方式中，假设目标对象的数字标识是在接收到目标对象针对数字实体发起的操作请求之后生成的，那么目标对象的数字标识的生成过程可包括：在接收到操作请求，且检测到不存在目标对象的数字标识时，返回信息获取请求(如向目标对象持有的终端设备返回信息获取请求)，该信息获取请求用于请求获取目标对象的对象信息；接收响应该信息获取请求返回的目标对象的对象信息，并将对象信息转换为目标对象的数字标识。
应当理解的是，上述只是给出的两种示例性的生成目标对象的数字标识的过程；在实际应用中目标对象的数字标识的生成过程可能发生变化，本申请实施例对此不做任何限定。
S302：基于目标对象的数字标识和操作信息生成实体操作凭证。
S303：若目标对象确认对数字实体执行目标操作，则获取声明数据，该声明数据是采用所述目标对象的第一签名数据对所述实体操作凭证执行签名处理得到的。
步骤S302-S303中，根据目标对象针对数字实体发起的操作请求，确定目标对象想要针对数字实体执行的目标操作后，可基于目标对象的数字标识和目标操作的操作信息生成实体操作凭证，该实体操作凭证类似于一张数字证书，用于指示请求针对数字实体执行目标操作，且还用于指示目标操作的请求者为目标对象，其可以作为对于目标对象针对数字实体发起操作请求的记录数据。其中，实体操作凭证可以是由目标对象持有的终端设备生成的，此情况下，终端设备可以基于操作请求所请求的目标操作的操作信息和目标对象的数字标识，生成实体操作凭证，并将实体操作凭证发送至服务器。或者，实体操作凭证还可以是由服务器生成的，此情况下，服务器在获取到操作请求时，可基于获取到的目标对象的数字标识和目标操作的操作信息生成实体操作凭证。
应当注意的是，本申请实施例对生成实体操作凭证的电子设备不作限制；例如，在分布式应用程序部署于服务器的情况下，目标对象可以直接对服务器执行操作，此时在处理系统中无需包含终端设备，这样实体操作凭证由服务器生成。为便于阐述，后续以部署有分布式应用程序(DAPP)的终端设备生成实体操作凭证为例进行介绍。
进一步的，目标对象可获取到实体操作凭证，如服务器将实体操作凭证返回至目标对象所持有的终端设备，这样目标对象通过终端设备获取到实体操作凭证，或者，终端设备生成并输出实体操作凭证，以便于目标对象查看实体操作凭证。目标对象获取到实体操作凭证后，可对实体操作凭证所包含的信息进行查看，若目标对象确认对数字实体执行实体操作凭证所指示的目标操作，那么可采用目标对象的第一签名数据对实体操作凭证进行签名处理，如采用第一签名数据对实体操作凭证进行数字签名，生成声明数据；此处的目标对象的第一签名数据可是目标对象的私钥。最后，基于目标对象签名后的声明数据对数字实体执行目标操作，具体参见步骤S304所示的具体实施过程。上述实现过程中，只有目标对象在确认对数字实体执行目标操作的情况下，才采用目标对象的第一签名数据对实体操作凭证进行签名处理，表示是基于目标对象的许可才针对数字实体执行目标操作的，能够确保操作数字实体的安全性。
需要说明的是，在实体操作凭证由部署有分布式应用程序(DApp)的终端设备生成的情况下，目标对象可通过分布式应用程序，采用自持的第一签名数据(如私钥)对实体操作凭证进行签名处理生成声明数据；并将声明数据发送至服务器，以便于服务器基于声明数据对数字实体进行目标操作。可选的，目标对象可直接采用自持的第一签名数据，对实体操作凭证进行签名处理生成声明数据。可选的，目标对象还可以授权终端设备，以便于终端设备授权获取目标对象的第一签名数据，并采用第一签名数据对实体操作凭证进行签名处理生成声明数据。
在实体操作凭证由服务器生成的情况下，如服务器部署有分布式应用程序，根据服务器与目标对象持有的终端设备是相同或不同的电子设备，服务器可以采用如下任一种方式 获取声明数据：
在一种实现方式中，终端设备与服务器是不同的电子设备。可选的，服务器可将实体操作凭证发送至目标对象所持有的终端设备，再由终端设备返回目标对象采用第一签名数据对实体操作凭证签名处理得到的声明数据。具体实现中，在服务器基于目标对象的数字标识和目标操作的操作信息生成实体操作凭证后，可将实体操作凭证发送至目标对象，具体是发送至目标对象所持有的终端设备；以使终端设备在显示屏幕上显示实体操作凭证，如图4所示。目标对象可在显示屏幕中直观地查看实体操作凭证所包含的信息，并在确认对数字实体执行实体操作凭证所指示的目标操作时，由目标对象直接或者目标对象授权终端设备，采用目标对象的第一签名数据对实体操作凭证进行签名处理得到声明数据；然后，终端设备再将签名处理得到的声明数据返回至服务器。这样服务器可直接从终端设备处接收声明数据。
可选的，服务器还可以基于实体操作凭证生成授权请求，该授权请求中携带实体操作凭证，授权请求用于请求目标对象授权服务器对实体操作凭证进行签名处理，并将授权请求发送至终端设备。终端设备响应于接收到的授权请求，输出实体操作凭证；若目标对象确认实体操作凭证所包含的信息是正确的，且同意授权服务器进行签名处理，则终端设备返回确认信息，该确认信息指示目标对象授权服务器采用第一签名数据对实体操作凭证进行签名处理。这样服务器可以根据该确认信息获取到目标对象的第一签名数据，并根据第一签名数据对实体操作凭证进行签名处理，得到声明数据。
在另一种实现方式中，终端设备与服务器是同一电子设备，即服务器中部署有分布式应用程序；此实现方式下，服务器可以在显示屏幕上显示实体操作凭证，若目标对象采用第一签名数据对实体操作凭证进行签名，则响应于目标对象采用第一签名数据针对实体操作凭证的签名操作，得到签名后的实体操作凭证，将该签名后的实体操作凭证作为声明数据。
与前述描述的，采用目标对象的第一签名数据对实体操作凭证进行签名处理的过程，可以是由目标对象直接执行的，也可以是由目标对象授权服务器执行的。可选的，目标对象可以采用第一签名数据对实体操作凭证进行签名处理得到声明数据，即服务器响应于目标对象采用目标对象的第一签名数据，对实体操作凭证执行的签名操作，可以得到签名后的实体操作凭证，该签名后的实体操作凭证作为声明数据。可选的，服务器还可以接收目标对象针对实体操作凭证的授权操作，获取目标对象的第一签名数据，并由服务器根据目标对象的第一签名数据对实体操作凭证执行签名处理，得到签名后的实体操作凭证，该签名后的实体操作凭证作为声明数据。
通过上述实现过程，目标对象可获取到用于指示针对数字实体执行目标操作的实体操作凭证，通过实体操作凭证的形式实现采用DID协议表达和描述数字实体，优化数字实体的表达和可读性，使得目标对象基于实体操作凭证明确了解所要针对数字实体执行的目标操作，提升目标对象的体验。并且，通过DID协议的支撑，可以对数字实体施加更多的应用功能，丰富数字实体的落地场景。
S304：基于声明数据，对数字实体执行目标操作。
由前述描述可知，声明数据是采用目标对象的第一签名数据(如目标对象的私钥)对实体操作凭证进行签名处理得到的，那么服务器在获取到声明数据后，还需先对声明数据进行验签处理；当对声明数据验签成功时，表示对想要执行目标操作的实体的身份验签成功，可开始对数字实体执行目标操作。
具体实现中，基于声明数据对数字实体执行目标操作的实施过程可包括：首先，由于目标对象的数字标识(即DID标识符)绑定有目标对象的第二签名数据(如目标对象的 公钥)，那么可以基于目标对象的数字标识，获取到目标对象的第二签名数据。然后，采用目标对象的第二签名数据来对声明数据进行验签处理，得到验签结果。最后，在验签结果为验签成功时，即验签结果表示对在终端设备侧的操作者的身份验证成功，则对数字实体执行目标操作；反之，在验签结果为验签失败时，表示对在终端设备侧的操作者的身份验证失败，则不对数字实体执行目标操作。
上述实现过程中，在目标对象的第一签名数据为目标对象的私钥，目标对象的第二签名数据为目标对象的公钥，且公钥与私钥不同的情况下，本申请实施例通过非对称加密技术，来验证终端设备的操作者是否是实体操作凭证中记录的数字标识所对应的目标对象，实现对终端设备侧的操作者的身份的验证，从而实现在对数字实体进行目标操作之前的交易许可验证，提高数字实体的安全性和可追溯性，能够适用于对审查有需求的应用场景，如联盟链场景。
本申请实施例中，在接收到目标对象针对数字实体发起的操作请求时，可根据目标对象的数字标识和操作请求携带的操作信息生成实体操作凭证，该实体操作凭证指示了请求针对数字实体执行目标操作，以及目标操作的请求者为目标对象；通过生成数字实体的实体操作凭证，能够直观地告知目标对象数字实体有关的信息，优化数字实体的表达和可读性。并且，只有在目标对象确认对数字实体执行目标操作时，即获取到声明数据(即签名处理后的实体操作)，且对声明数据验签成功的情况下，才对数字实体执行目标操作。本申请实施例将目标对象的数字标识贯穿对于数字实体的操作过程，基于目标对象的数字标识生成实体操作凭证和声明数据，如此，在对数字实体执行目标操作的过程中，直观可靠地记录针对该数字实体执行的相关操作以及相关操作的执行对象，从而提高数字实体的安全性和相关操作的可追溯性，进而高效安全地实现针对数字实体的目标操作。
正如前述所描述的，本申请实施例涉及的数字实体的处理系统中可包括终端设备和服务器，终端设备中部署有分布式应用程序(DAPP或NFT APP)，或者，数字实体的处理系统中可只包括服务器，服务器中部署分布式应用程序；后续以数字实体的处理系统中包括终端设备和服务器为例，重点对针对数字实体执行目标操作的具体实施过程进行阐述。不难理解的是，针对数字实体执行的目标操作的操作类型是比较丰富的，下面结合附图分别对目标操作为铸造数字实体的操作，以及目标操作为转移数字实体的操作为例，对目标操作的具体实施过程进行介绍。
如图5示出了本申请实施例提供的一种示例性的，目标操作为铸造数字实体的操作时，数字实体的处理方法的流程示意图；该数字实体的处理方法可以由图2a所示系统中的终端设备和服务器共同执行，该处理方法可包括但不限于步骤S501-S509：
S501：终端设备将标识注册请求发送至服务器。
S502：服务器响应标识注册请求，生成并注册目标对象的数字标识。
S503：服务器将目标对象的数字标识发送至终端设备。
步骤S501-S503中，在目标对象具有生成和注册数字标识的需求时，目标对象可通过终端设备产生标识注册请求，具体是通过终端设备中部署的分布式应用程序产生标识注册请求。然后，由终端设备将标识注册请求发送至服务器，由服务器中部署的区块链应用协议模型中的NFT应用层接收该标识注册请求。继而，由NFT应用层调用DID应用层，再由DID应用层调用DID智能合约响应标识注册请求生成目标对象的数字标识，并将目标对象的数字标识注册至区块链上。
需要说明的是，服务器响应于标识注册请求生成和注册目标对象的数字标识的具体实施过程，可参加图3所示实施例中步骤S301所示的具体实施过程的相关描述，在此不作 赘述。
S504：终端设备生成实体操作凭证，并根据第一签名数据对实体操作凭证进行签名处理，生成声明数据。
在针对数字实体执行的目标操作为铸造数字实体的操作的场景下，终端设备生成的实体操作凭证可称为实体铸造凭证。
具体实现中，若目标对象具有铸造数字实体的需求，那么终端设备响应于该铸造数字实体的需求可生成操作请求，此时该操作请求用于请求铸造数字实体；即针对数字实体的目标操作为铸造数字实体的操作，目标操作的操作信息至少包括：铸造数字实体所需的实体铸造信息，如数字实体为数字图像，那么铸造该数字图像所需的实体铸造信息可包括组成数字图像的各个元素的元素信息(如元素地址或元素图层等)。然后，终端设备响应于操作请求，基于目标对象的数字标识和目标操作的操作信息生成实体铸造凭证。最后，基于目标对象的第一签名数据对实体铸造凭证进行签名处理，生成声明数据。
正如前述图3所示实施例中描述的，若实体铸造凭证是由服务器生成的，如服务器调用第三方权威机构来生成实体铸造凭证，那么终端设备可以将操作请求发送至服务器，由服务器响应该操作请求生成实体铸造凭证，在此对由服务器生成实体铸造凭证的具体实施过程不作限定。
S505：终端设备基于实体操作凭证生成铸造请求，并将铸造请求发送至服务器，该铸造请求中携带签名后的实体操作凭证(即声明数据)。
S506：服务器响应铸造请求，对声明数据进行验签处理。
步骤S505-S506中，服务器在获取到铸造请求时，一并获取到铸造请求所携带的声明数据，则服务器可以基于目标对象的数字标识对声明数据进行验签处理，具体是目标对象的数字标识绑定有目标对象的公钥，这样服务器可以获取到目标对象的公钥，并基于目标对象的公钥对声明数据进行验签，得到验签结果。
S507：若验签成功，服务器创建数字实体的实体标识。
S508：服务器绑定数字实体的实体标识和目标对象的数字标识。
步骤S507-S508中，在基于目标对象的第二签名数据对声明数据验签成功时，表示对终端设备侧的实体的身份验证成功，即终端设备侧的实体为采用第一签名数据对实体铸造凭证进行数字签名的目标对象，那么可以执行针对数字实体的目标操作。
其中，对数字实体执行目标操作，目标操作为铸造数字实体的操作的具体实施过程可如图6所示，具体流程可包括：首先，根据铸造数字实体所需的实体铸造信息，铸造数字实体，例如，数字实体为数字图像，铸造数字实体所需的实体铸造信息为属于不同图层级别的元素图像，那么将各个元素图像按照图层级别从高至低(或从低至高)的顺序叠加，可铸造得到数字图像。然后，服务器可基于其部署的区块链应用协议模型中的DID智能合约，为铸造的数字实体创建实体标识，该实体标识即为数字实体NFT的DID标识，用于唯一标识数字实体。最后，可对数字实体的实体标识和目标对象的数字标识进行绑定处理，使得数字实体的实体标识和目标对象的数字标识之间具有映射绑定关系，该映射绑定关系可存储于区块链应用协议模型中的NFT协议层中，具体是存储于NFT协议层中的NFT智能合约中；这样通过该映射绑定关系可确定数字实体的归属者为目标对象，即目标对象是唯一具有对该数字实体进行操作的操作权限的对象。
其中，对数字实体和目标对象进行绑定处理的具体实施过程可包括：根据目标对象的数字标识和数字实体的实体标识，建立第一映射绑定关系，该第一映射绑定关系可是指上述提及的映射绑定关系，该第一映射绑定关系用于指示数字实体的持有者为目标对象；然后，将该第一映射绑定关系存储至数字实体对应的智能合约中，即NFT智能合约中，以 实现对数字实体和目标对象的绑定。
S509：服务器将针对数字实体的铸造结果返回至终端设备。
具体实现中，服务器可以将针对数字实体的铸造结果返回至终端设备，此处的针对数字实体的铸造结果可包括：铸造的数字实体(如数字图像)以及数字实体上链结果(如上链成功)等信息；本申请实施例对铸造结果所包含的具体内容不作限定。
本申请实施例中，在接收到目标对象针对数字实体发起的操作请求时，可根据目标对象的数字标识和操作请求携带的操作信息生成实体操作凭证，且该实体操作凭证指示了请求针对数字实体执行目标操作，以及目标操作的请求者为目标对象；通过生成数字实体的实体操作凭证，能够直观地告知目标对象数字实体有关的信息，优化数字实体的表达和可读性。并且，只有在目标对象确认对数字实体执行目标操作时，即获取到声明数据(即签名处理后的实体操作)，且对声明数据验签成功的情况下，才对数字实体执行目标操作。本申请实施例将目标对象的数字标识贯穿对于数字实体的操作过程，基于目标对象的数字标识生成实体操作凭证和声明数据，如此，在对数字实体执行目标操作的过程中，直观可靠地记录针对该数字实体执行的相关操作以及相关操作的执行对象，从而能够提高数字实体的安全性和相关操作的可追溯性，进而高效安全地实现针对数字实体的目标操作，如铸造数字实体的操作。
图7示出了本申请实施例提供的一种示例性的，目标操作为转移数字实体的操作时，数字实体的处理方法的流程示意图；该数字实体的处理方法可以由图2a所示系统中的终端设备和服务器共同执行，该处理方法可包括但不限于步骤S701-S706：
S701：终端设备生成实体操作凭证，并根据第一签名数据对实体操作凭证进行签名处理，生成声明数据。
在针对数字实体执行的目标操作为转移数字实体的操作的场景下，终端设备生成的实体操作凭证可称为实体转移凭证。
具体实现中，若目标对象具有转移数字实体的需求，那么终端设备响应于转移数字实体需求可生成操作请求，此时该操作请求用于请求将数字实体从目标对象转移至参考对象，换句话说，将数字实体的持有者从目标对象调整为参考对象，目标对象与参考对象不同；即针对数字实体的目标操作为转移数字实体的操作，目标操作的操作信息至少包括：参考对象的数字标识，以及待转移的数字实体的实体标识。然后，终端设备响应于操作请求，基于目标对象的数字标识和目标操作的操作信息生成实体转移凭证。最后，基于目标对象的第一签名数据对实体转移凭证进行签名处理，生成声明数据。
正如前述图3所示实施例中描述的，若实体转移凭证是由服务器生成的，如服务器调用第三方权威机构来生成实体转移凭证，那么终端设备可以将操作请求发送至服务器，由服务器响应该操作请求调用第三方机构生成实体转移凭证；在此对由服务器生成实体转移凭证的具体实施过程不作限定。
S702：终端设备基于实体转移凭证生成转移请求，并将转移请求发送至服务器，该转移请求中携带签名后的实体转移凭证(即声明数据)。
S703：服务器响应转移请求，对声明数据进行验签处理。
步骤S702-S703中，服务器在获取到转移请求时，一并获取到转移请求所携带的声明数据，则服务器可以基于目标对象的数字标识对声明数据进行验签处理，具体是目标对象的数字标识绑定有目标对象的公钥，这样服务器可以获取到目标对象的公钥，并基于目标对象的公钥对声明数据进行验签，得到验签结果。
S704：若验签成功，服务器修改数字实体的实体文档中的目标对象的数字标识。
S705：服务器修改数字实体的实体标识和目标对象的数字标识之间的映射绑定关系。
步骤S704-S705中，在基于目标对象的第二签名数据对声明数据验签成功时，表示对终端设备侧的实体的身份验证成功，即终端设备侧的实体为采用第一签名数据对实体转移凭证进行数字签名的目标对象，那么可以执行针对数字实体的目标操作。其中，对数字实体执行目标操作，目标操作为转移数字实体的操作的具体实施过程可如图8所示，具体流程可包括：
首先，对数字实体的实体标识进行解析，数字实体的实体标识是在铸造数字实体时创建的，获取到数字实体对应的实体文档(即DID文档)；其中，实体文档存储有数字实体的元数据metadata，元数据metadata中包括描述数字实体内容的存储位置(如外观属性描述文件、图片等)，实体文档中还包括controller控制者字段，该控制者字段记录了目标对象的数字标识，表示数字实体的归属者为控制者字段记录的数字标识对应的目标对象。
然后，执行如下两种操作，不限定两种操作的执行先后顺序，以实现将数字实体从目标对象转移至参考对象，具体是将对数字实体的操作权限从目标对象转移至参考对象，包括：
①在实体文档中，将控制者字段记录的目标对象的数字标识，修改为待接收数字实体的参考对象的数字标识。②如前述描述可知，服务器所部署的区块链应用协议模型中的NFT智能合约中存储有第一映射绑定关系，该第一映射绑定关系将数字实体的实体标识与目标对象的数字标识进行绑定，那么可以在数字实体对应的智能合约(即NFT智能合约)中，将第一映射绑定关系修改为第二映射绑定关系；其中，第一映射绑定关系指示数字实体的持有者为目标对象，第二映射绑定关系指示数字实体的持有者为参考对象。
通过上述过程，可实现对数字实体的转移操作，能够将针对数字实体的操作权限从目标对象转移至参考对象。
另外，由前述描述可知，在数字实体的持有者转移数字实体的场景中，需要持有者签发数字实体的实体转移凭证，以用于数字实体的持有者变更验证，本申请实施例还支持为实体转移凭证设置转移有效时长，即实体操作凭证(或签名后的声明数据)具有时效性，只有在转移有效时长内，才能执行对实体转移凭证进行验签以及后续的转移的操作。具体实现中，在采用目标对象的第一签名数据对实体转移凭证进行数字签名时，可以为生成的声明数据设置转移有效时长，该转移有效时长可以是预先设定的或由目标对象自定义的。这样服务器在获取到声明数据后，可先获取声明数据的生成时间，该生成时间是指对数字实体的实体操作凭证进行签名处理生成该声明数据的时刻。然后，确定声明数据的生成时间与当前时间之间的目标时长，该当前时间是指对声明数据验签处理的时刻；也就是说，以生成声明数据的时刻开始，直到服务器对声明数据进行验签处理的时刻为止，将这段时长作为目标时长。最后，将目标时长与转移有效时长进行比较；若目标时长小于或等于转移有效时长，表示实体转移凭证处于有效状态，此时可触发执行基于声明数据对数字实体执行目标操作的步骤；反之，若目标时长大于转移有效时长，表示实体转移凭证不再处于有效状态，而是处于无效状态，确定对数字实体的转移失败。
举例来说，在数字实体的转移场景中，若在12月12日12:00点生成声明数据，且该声明数据对应的转移有效时长为24小时，那么当服务器在12月12日19:00时，对声明数据进行验签处理，则确定声明数据的生成时间和当前时间之间的目标时长为7小时，小于转移有效时长24小时，那么服务器可以执行对声明数据的验签处理。反之，若服务器在12月15日12:00时，对声明数据进行验签处理，则确定声明数据的生成时间和当前时间之间的目标时长为72小时，大于转移有效时长24小时，那么服务器不能执行对声明数据的验签处理，确定对数字实体转移失败。通过为实体操作凭证设置转移有效时长，使得 实体操作凭证具有有效操作范围，在一定程度上能够提升实体操作凭证的安全性。
S706：服务器将针对数字实体的转移结果返回至终端设备。
具体实现中，服务器可以将针对数字实体的转移结果返回至终端设备，此处的针对数字实体的转移结果可包括转移成功或转移失败等信息；本申请实施例对转移结果所包含的具体内容不作限定。
本申请实施例中，若目标对象具有转移数字实体的需求，那么终端设备响应于转移数字实体需求可生成操作请求，此时该操作请求用于请求将数字实体的持有者从目标对象调整为参考对象，目标对象与参考对象不同；即针对数字实体的目标操作为转移数字实体的操作，目标操作的操作信息至少包括：参考对象的数字标识，以及待转移的数字实体的实体标识。然后，终端设备响应于操作请求，基于目标对象的数字标识和目标操作的操作信息生成实体转移凭证。最后，基于目标对象的第一签名数据对实体转移凭证进行签名处理，生成声明数据。进一步的，在转移数字实体的过程中，为NFT协议层提供区块链身份层协议(即DID协议)的支撑，不仅提高对数字实体的自主控制能力，而且能够增强数字实体转移的安全性，为跨链(即不同区块链)或跨合约(如不同智能合约)下的实体流通提供协议支持。
上述详细阐述了本申请实施例的方法，为了便于更好地实施本申请实施例的上述方案，相应地，下面提供了本申请实施例的装置。
请参见图9，图9是本申请实施例提供的一种数字实体的处理装置的结构示意图，该处理装置可以设置于本申请实施例提供的电子设备(如服务器)中；在一些实施例中，该处理装置可以是运行于电子设备中的一个计算机程序(包括程序代码)，该处理装置可以用于执行图3、图5或图7所示的方法实施例中的相应步骤。请参见图9，该处理装置可以包括如下单元：
获取单元901，用于在获取到目标对象针对数字实体发起的操作请求时，获取目标对象的数字标识，操作请求中携带目标对象请求针对数字实体执行的目标操作的操作信息；
处理单元902，用于基于目标对象的数字标识和操作信息生成实体操作凭证；实体操作凭证用于指示请求针对数字实体执行目标操作，且用于指示目标操作的请求者为目标对象；
处理单元902，还用于若目标对象确认对数字实体执行所述目标操作，则获取声明数据，该声明数据是采用目标对象的第一签名数据，对实体操作凭证执行签名处理得到的；
处理单元902，还用于基于声明数据，对数字实体执行目标操作。
在一种实现方式中，目标对象的数字标识绑定有目标对象的第二签名数据，处理单元902用于基于声明数据，对数字实体执行目标操作时，具体用于：
根据目标对象的数字标识，获取目标对象的第二签名数据；
采用目标对象的第二签名数据，对声明数据进行验签处理；
若声明数据验签成功，则对数字实体执行目标操作。
在一种实现方式中，操作请求用于请求铸造数字实体，目标操作包括铸造数字实体的操作，目标操作的操作信息包括：铸造数字实体所需的实体铸造信息；
处理单元902用于对数字实体执行目标操作时，具体用于：
根据铸造数字实体所需的实体铸造信息，铸造得到数字实体；
为铸造得到的数字实体创建实体标识；
对数字实体的实体标识和目标对象的数字标识进行绑定处理。
在一种实现方式中，处理单元902用于对数字实体的实体标识和目标对象的数字标识 进行绑定处理时，具体用于：
根据目标对象的数字标识和数字实体的实体标识，建立第一映射绑定关系，所第一映射绑定关系用于指示数字实体的持有者为目标对象；
将第一映射绑定关系存储至数字实体对应的智能合约中。
在一种实现方式中，操作请求用于请求将所述数字实体从目标对象转移至参考对象，参考对象与目标对象不同目标操作包括转移数字实体的操作，目标操作的操作信息至少包括：参考对象的数字标识，以及数字实体的实体标识；
处理单元902用于对数字实体执行目标操作时，具体用于：
获取数字实体对应的实体文档；实体文档中包括控制者字段，控制者字段记录有目标对象的数字标识；
在实体文档中，将控制者字段记录的目标对象的数字标识，修改为参考对象的数字标识；
以及，在数字实体对应的智能合约中，将第一映射绑定关系修改为第二映射绑定关系；其中，第一映射绑定关系指示数字实体的持有者为目标对象，第二映射绑定关系指示数字实体的持有者为参考对象。
在一种实现方式中，处理单元902用于获取数字实体对应的实体文档时，具体用于：
对数字实体的实体标识进行解析，得到数字实体对应的实体文档；实体文档存储有数字实体的元数据。
在一种实现方式中，声明数据具有转移有效时长；处理单元902，还用于：
获取声明数据的生成时间，生成时间是对数字实体的实体操作凭证进行签名处理生成声明数据的时刻；
确定声明数据的生成时间与当前时间之间的目标时长，当前时间是对声明数据进行验签处理的时刻；
若目标时长小于或等于转移有效时长，则触发执行基于声明数据，对数字实体执行目标操作的步骤。
在一种实现方式中，处理单元902用于若目标对象确认对数字实体执行目标操作，则获取采用目标对象的第一签名数据，对实体操作凭证执行签名处理得到的声明数据时，具体用于：
将实体操作凭证发送至目标对象，以使目标对象在确认对数字实体执行目标操作时，采用目标对象的第一签名数据对实体操作凭证进行签名处理得到声明数据；
接收目标对象返回的声明数据。
在一种实现方式中，处理单元902用于若目标对象确认对数字实体执行目标操作，则获取采用目标对象的第一签名数据，对实体操作凭证执行签名处理得到的声明数据时，具体用于：
在显示屏幕上显示实体操作凭证；
响应于目标对象针对实体操作凭证的签名操作，得到签名后的实体操作凭证；
将签名后的实体操作凭证作为声明数据。
在一种实现方式中，处理单元902用于响应于目标对象针对实体操作凭证的签名操作，得到签名后的实体操作凭证时，具体用于：
响应于目标对象采用目标对象的第一签名数据对实体操作凭证执行的签名操作，得到签名后的实体操作凭证；
或者，接收目标对象针对实体操作凭证的授权操作，获取目标对象的第一签名数据，并采用目标对象的第一签名数据对实体操作凭证执行签名处理，得到签名后的实体操作凭 证。
在一种实现方式中，目标对象的数字标识的生成过程包括：
获取目标对象的对象信息；
将对象信息转换为目标对象的数字标识；
其中，对象信息包括目标对象的公钥。
根据本申请的一个实施例，图9所示的处理装置中的各个单元可以分别或全部合并为一个或若干个另外的单元来构成，或者其中的某个(些)单元还可以再拆分为功能上更小的多个单元来构成，这可以实现同样的操作，而不影响本申请的实施例的技术效果的实现。上述单元是基于逻辑功能划分的，在实际应用中，一个单元的功能也可以由多个单元来实现，或者多个单元的功能由一个单元实现。在本申请的其它实施例中，该处理装置也可以包括其它单元，在实际应用中，这些功能也可以由其它单元协助实现，并且可以由多个单元协作实现。根据本申请的另一个实施例，可以通过在包括中央处理单元(CPU)、随机存取存储介质(RAM)、只读存储介质(ROM)等处理元件和存储元件的例如计算机的通用计算设备上运行能够执行如图3、图5及图7所示的相应方法所涉及的各步骤的计算机程序(包括程序代码)，来构造如图9中所示的处理装置，以及来实现本申请实施例的数字实体的处理方法。计算机程序可以记载于例如计算机可读记录介质上，并通过计算机可读记录介质装载于上述计算设备中，并在其中运行。
本申请实施例中，在接收到目标对象针对数字实体发起的操作请求时，可根据目标对象的数字标识和操作请求携带的操作信息生成实体操作凭证，且该实体操作凭证指示请求针对数字实体执行目标操作，以及目标操作的请求者为目标对象；通过生成数字实体的实体操作凭证，能够直观地告知目标对象数字实体有关的信息，优化数字实体的表达和可读性。并且，只有在目标对象确认对数字实体执行目标操作时，即获取到声明数据(即签名处理后的实体操作)，且对声明数据验签成功的情况下，才对数字实体执行目标操作。本申请实施例将目标对象的数字标识贯穿对于数字实体的操作过程，基于目标对象的数字标识生成实体操作凭证和声明数据，如此，在对数字实体执行目标操作的过程中，直观可靠地记录针对该数字实体执行的相关操作以及相关操作的执行对象，从而提高数字实体的安全性和可追溯性，进而高效地实现针对数字实体的目标操作。
图10示出了本申请一个示例性实施例提供的电子设备的结构示意图。请参见图10，该电子设备包括处理器1001、通信接口1002以及计算机可读存储介质1003。其中，处理器1001、通信接口1002以及计算机可读存储介质1003可通过总线或者其它方式连接。其中，通信接口1002用于接收和发送数据。计算机可读存储介质1003可以存储在电子设备的存储器中，计算机可读存储介质1003用于存储计算机程序，计算机程序包括程序指令，处理器1001用于执行计算机可读存储介质1003存储的程序指令。处理器1001(或称CPU(Central Processing Unit，中央处理器))是电子设备的计算核心以及控制核心，其适于实现一条或多条指令，具体适于加载并执行一条或多条指令从而实现相应方法流程或相应功能。
本申请实施例还提供了一种计算机可读存储介质(Memory)，计算机可读存储介质是电子设备中的记忆设备，用于存放程序和数据。可以理解的是，此处的计算机可读存储介质既可以包括电子设备中的内置存储介质，当然也可以包括电子设备所支持的扩展存储介质。计算机可读存储介质提供存储空间，该存储空间存储了电子设备的处理系统。并且，在该存储空间中还存放了适于被处理器1001加载并执行的一条或多条的指令，这些指令可以是一个或多个的计算机程序(包括程序代码)。需要说明的是，此处的计算机可读存 储介质可以是高速RAM存储器，也可以是非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器；可选的，还可以是至少一个位于远离前述处理器的计算机可读存储介质。
在一个实施例中，该计算机可读存储介质中存储有一条或多条指令；由处理器1001加载并执行计算机可读存储介质中存放的一条或多条指令，以实现上述数字实体的处理方法实施例中的相应步骤；具体实现中，计算机可读存储介质中的一条或多条指令由处理器1001加载并执行如图3、图5及图7所示的相应方法所涉及的各步骤
本申请实施例还提供一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。电子设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该电子设备执行上述数字实体的处理方法。
本领域普通技术对象可以意识到，结合本申请中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术对象可以对每个特定的应用，使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程设备。计算机指令可以存储在计算机可读存储介质中，或者通过计算机可读存储介质进行传输。计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如，同轴电缆、光纤、数字线(DSL))或无线(例如，红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据处理设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术对象在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (15)

  1. 一种数字实体的处理方法，由电子设备执行，包括：
    在获取到目标对象针对数字实体发起的操作请求时，获取所述目标对象的数字标识，所述操作请求中携带所述目标对象请求针对所述数字实体执行的目标操作的操作信息；
    基于所述目标对象的数字标识和所述操作信息生成实体操作凭证；所述实体操作凭证用于指示请求针对所述数字实体执行所述目标操作，且用于指示所述目标操作的请求者为所述目标对象；
    若所述目标对象确认对所述数字实体执行所述目标操作，则获取声明数据，所述声明数据是采用所述目标对象的第一签名数据对所述实体操作凭证执行签名处理得到的；
    基于所述声明数据，对所述数字实体执行所述目标操作。
  2. 如权利要求1所述的方法，所述目标对象的数字标识绑定有所述目标对象的第二签名数据，所述基于所述声明数据，对所述数字实体执行所述目标操作，包括：
    根据所述目标对象的数字标识，获取所述目标对象的第二签名数据；
    采用所述目标对象的第二签名数据，对所述声明数据进行验签处理；
    若所述声明数据验签成功，则对所述数字实体执行所述目标操作。
  3. 如权利要求1或2所述的方法，所述操作请求用于请求铸造所述数字实体，所述目标操作包括铸造所述数字实体的操作，所述目标操作的操作信息包括：铸造所述数字实体所需的实体铸造信息；
    所述对所述数字实体执行所述目标操作，包括：
    根据所述铸造所述数字实体所需的实体铸造信息，铸造得到所述数字实体；
    为铸造得到的所述数字实体创建实体标识；
    对所述数字实体的实体标识和所述目标对象的数字标识进行绑定处理。
  4. 如权利要求3所述的方法，所述对数字实体的实体标识和目标对象的数字标识进行绑定处理，包括：
    根据所述目标对象的数字标识和所述数字实体的实体标识，建立第一映射绑定关系，所述第一映射绑定关系用于指示所述数字实体的持有者为所述目标对象；
    将所述第一映射绑定关系存储至所述数字实体对应的智能合约中。
  5. 如权利要求1至4任一项所述的方法，所述操作请求用于请求将所述数字实体从所述目标对象转移至参考对象，所述参考对象与所述目标对象不同；所述目标操作包括转移所述数字实体的操作，所述目标操作的操作信息至少包括：所述参考对象的数字标识，以及所述数字实体的实体标识；
    所述对所述数字实体执行所述目标操作，包括：
    获取所述数字实体对应的实体文档；所述实体文档中包括控制者字段，所述控制者字段记录有所述目标对象的数字标识；
    在所述实体文档中，将所述控制者字段记录的所述目标对象的数字标识修改为所述参考对象的数字标识；
    以及，在所述数字实体对应的智能合约中，将第一映射绑定关系修改为第二映射绑定关系；其中，所述第一映射绑定关系指示所述数字实体的持有者为所述目标对象，所述第二映射绑定关系指示所述数字实体的持有者为所述参考对象。
  6. 如权利要求5所述的方法，所述获取所述数字实体对应的实体文档，包括：
    对所述数字实体的实体标识进行解析，得到所述数字实体对应的实体文档；所述实体文档存储有所述数字实体的元数据。
  7. 如权利要求5所述的方法，所述声明数据具有转移有效时长；所述基于所述声明 数据，对所述数字实体执行所述目标操作之前，还包括：
    获取所述声明数据的生成时间，所述生成时间是对所述实体操作凭证进行签名处理生成所述声明数据的时刻；
    确定所述声明数据的生成时间与当前时间之间的目标时长，所述当前时间是对所述声明数据进行验签处理的时刻；
    若所述目标时长小于或等于所述转移有效时长，则触发执行所述基于所述声明数据，对所述数字实体执行所述目标操作的步骤。
  8. 如权利要求1至7任一项所述的方法，所述若所述目标对象确认对所述数字实体执行所述目标操作，则获取声明数据，包括：
    将所述实体操作凭证发送至所述目标对象，以使所述目标对象在确认对所述数字实体执行所述目标操作时，采用所述目标对象的第一签名数据对所述实体操作凭证进行签名处理得到所述声明数据；
    接收所述目标对象返回的所述声明数据。
  9. 如权利要求1至7任一项所述的方法，所述若所述目标对象确认对所述数字实体执行所述目标操作，则获取声明数据，包括：
    在显示屏幕上显示所述实体操作凭证；
    响应于所述目标对象针对所述实体操作凭证的签名操作，得到签名后的实体操作凭证；
    将所述签名后的实体操作凭证作为所述声明数据。
  10. 如权利要求9所述的方法，所述响应于所述目标对象针对所述实体操作凭证的签名操作，得到签名后的实体操作凭证，包括：
    响应于所述目标对象采用所述目标对象的第一签名数据对所述实体操作凭证执行的签名操作，得到所述签名后的实体操作凭证；
    或者，接收所述目标对象针对所述实体操作凭证的授权操作，获取所述目标对象的第一签名数据，并采用所述目标对象的第一签名数据对所述实体操作凭证执行签名处理，得到所述签名后的实体操作凭证。
  11. 如权利要求1至10任一项所述的方法，所述目标对象的数字标识的生成过程包括：
    获取目标对象的对象信息；
    将所述对象信息转换为所述目标对象的数字标识；
    其中，所述对象信息包括所述目标对象的公钥。
  12. 一种数字实体的处理装置，其特征在于，包括：
    获取单元，用于在获取到目标对象针对数字实体发起的操作请求时，获取所述目标对象的数字标识，所述操作请求中携带所述目标对象请求针对所述数字实体执行的目标操作的操作信息；
    处理单元，用于基于所述目标对象的数字标识和所述操作信息生成实体操作凭证；所述实体操作凭证用于指示请求针对所述数字实体执行目标操作，且用于指示所述目标操作的请求者为所述目标对象；
    所述处理单元，还用于若所述目标对象确认对所述数字实体执行所述目标操作，则获取声明数据，所述声明数据是采用所述目标对象的第一签名数据对所述实体操作凭证执行签名处理得到的；
    所述处理单元，还用于基于所述声明数据对所述数字实体执行所述目标操作。
  13. 一种电子设备，包括：
    处理器，适于执行计算机程序；
    计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，所述计算机程序被所述处理器执行时，实现如权利要求1-11任一项所述的数字实体的处理方法。
  14. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机应用程序，所述计算机应用程序被执行时，实现如权利要求1-11任一项所述的数字实体的处理方法。
  15. 一种计算机程序产品，所述计算机程序产品包括计算机指令，所述计算机指令被处理器执行时实现如权利要求1-11任一项所述的数字实体的处理方法。
PCT/CN2023/094699 2022-07-29 2023-05-17 一种数字实体的处理方法、装置、设备、介质及程序产品 WO2024021785A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210913825.7A CN117521154A (zh) 2022-07-29 2022-07-29 一种数字产品的处理方法、装置、设备、介质及程序产品
CN202210913825.7 2022-07-29

Publications (1)

Publication Number Publication Date
WO2024021785A1 true WO2024021785A1 (zh) 2024-02-01

Family

ID=89705276

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/094699 WO2024021785A1 (zh) 2022-07-29 2023-05-17 一种数字实体的处理方法、装置、设备、介质及程序产品

Country Status (2)

Country Link
CN (1) CN117521154A (zh)
WO (1) WO2024021785A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107480964A (zh) * 2017-07-24 2017-12-15 湖南搜云网络科技股份有限公司 数字资产的定向转让方法、中央服务器及存储介质
CN112651052A (zh) * 2020-12-24 2021-04-13 江苏通付盾科技有限公司 一种基于区块链技术的数据确权方法及系统
US20210318996A1 (en) * 2020-09-15 2021-10-14 Alipay (Hangzhou) Information Technology Co., Ltd. Methods, apparatuses, and devices for transferring data assets based on blockchain
CN113743921A (zh) * 2021-09-09 2021-12-03 网易（杭州）网络有限公司 数字资产的处理方法、装置、设备及存储介质
CN114298710A (zh) * 2021-11-26 2022-04-08 浙江毫微米科技有限公司 基于区块链的资产确权方法、装置、系统及存储介质
CN114444134A (zh) * 2022-01-27 2022-05-06 支付宝(杭州)信息技术有限公司 一种数据使用授权方法、系统及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107480964A (zh) * 2017-07-24 2017-12-15 湖南搜云网络科技股份有限公司 数字资产的定向转让方法、中央服务器及存储介质
US20210318996A1 (en) * 2020-09-15 2021-10-14 Alipay (Hangzhou) Information Technology Co., Ltd. Methods, apparatuses, and devices for transferring data assets based on blockchain
CN112651052A (zh) * 2020-12-24 2021-04-13 江苏通付盾科技有限公司 一种基于区块链技术的数据确权方法及系统
CN113743921A (zh) * 2021-09-09 2021-12-03 网易（杭州）网络有限公司 数字资产的处理方法、装置、设备及存储介质
CN114298710A (zh) * 2021-11-26 2022-04-08 浙江毫微米科技有限公司 基于区块链的资产确权方法、装置、系统及存储介质
CN114444134A (zh) * 2022-01-27 2022-05-06 支付宝(杭州)信息技术有限公司 一种数据使用授权方法、系统及装置

Also Published As

Publication number Publication date
CN117521154A (zh) 2024-02-06

Similar Documents

Publication Publication Date Title
JP7436568B2 (ja) ブロックチェーンにより実現される方法及びシステム
US20200228321A1 (en) Verifying an identity based on multiple distributed data sources using a blockchain to safeguard the identity
EP3847565B1 (en) Methods and devices for managing user identity authentication data
JP6873270B2 (ja) ブロックチェーンにおけるスマートコントラクトに基づくトランザクション活動の取扱注意データを保護するための方法及びデバイス
US20220255737A1 (en) Methods and systems for recovering data using dynamic passwords
US20210224938A1 (en) System and method for electronically providing legal instrument
US20230179405A1 (en) Trustworthy data exchange using distributed databases
US20210287770A1 (en) Electronic patient credentials
TWI444029B (zh) 控制數位身分表徵之分配及使用
US11017122B2 (en) Method and server for authenticating and verifying file
CN117150581A (zh) 安全身份和档案管理系统
US9100171B1 (en) Computer-implemented forum for enabling secure exchange of information
US20220303258A1 (en) Computer-implemented system and method
JP2009527984A (ja) 秘密鍵とのアカウントリンク
CA3051066A1 (en) Dynamic implementation and management of hash-based consent and permissioning protocols
CN111292174A (zh) 一种纳税信息处理方法、装置及计算机可读存储介质
CN110674531B (zh) 基于区块链的居住信息管理方法、装置、服务器及介质
WO2023207086A1 (zh) 一种基于区块链的用户数据流转方法、装置及设备
US11038685B1 (en) Correcting blockchain transactions with cryptocurrency type mistakes
JP7462903B2 (ja) 利用者端末、認証者端末、登録者端末、管理システムおよびプログラム
KR20210106532A (ko) 블록체인을 통해 행해지는 전송의 성능을 제어하거나 강제하기 위한 컴퓨터-구현된 시스템 및 방법
WO2024021785A1 (zh) 一种数字实体的处理方法、装置、设备、介质及程序产品
CN116975810A (zh) 身份验证方法、装置、电子设备及计算机可读存储介质
EP3883204B1 (en) System and method for secure generation, exchange and management of a user identity data using a blockchain
KR20220076486A (ko) 블록체인 트랜잭션들을 위한 콜-백 메커니즘들

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23845000

Country of ref document: EP

Kind code of ref document: A1