Blockchain-based resource credential processing method, device and computer equipment

Abstract

The application relates to a blockchain-based resource certificate processing method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: obtaining a resource certificate processing request carrying resource certificate business data; generating a verifiable certificate conforming to a distributed digital identity identifier standard according to the resource certificate business data; performing operation authentication on an operation requested by the resource certificate processing request based on the verifiable certificate; when the operation authentication result indicates that the operation is verified, processing a target resource certificate corresponding to the resource certificate processing request to obtain update data; and calling an intelligent contract in a blockchain to update resource certificate attribute information describing the target resource certificate and conforming to the distributed digital identity identifier standard in the intelligent contract through the update data. The method can improve the expansibility of resource certificate processing for different application scenarios and realize cross-application scenario processing.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a blockchain-based resource credential processing method, apparatus, computer equipment, storage medium, and computer program product. Background Technology

[0002] With the development of computer technology, digital transformation has gradually become a very popular topic, involving various industries such as high-tech, retail, finance, manufacturing, and energy. Digital transformation can include various aspects such as information digitization, process digitization, and business digitization. For digital resources, by processing their resource credentials, efficient transfer and management of digital resources can be achieved, realizing business digitization.

[0003] However, current processing of resource credentials for digital resources is often designed for specific business scenarios, limiting the scalability of application scenarios. Summary of the Invention

[0004] Therefore, it is necessary to provide a blockchain-based resource credential processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the scalability of resource credential processing for different application scenarios and enable cross-application scenario processing, addressing the aforementioned technical problems.

[0005] Firstly, this application provides a blockchain-based method for processing resource credentials. The method includes:

[0006] Obtain a resource certificate processing request carrying business data related to resource certificates;

[0007] When the resource credential business data passes the business data verification, a verifiable credential conforming to the distributed digital identity identifier standard is generated based on the resource credential business data.

[0008] Based on verifiable credentials, the operation requested by the resource credential processing request is authenticated to obtain the operation authentication result.

[0009] When the operation authentication result indicates that the operation verification is successful, the target resource certificate for the resource certificate processing request is processed according to the resource certificate business data to obtain the updated data;

[0010] The system invokes a smart contract in the blockchain to update the attribute information of the resource credential that describes the target resource credential and conforms to the distributed digital identity identifier standard by updating the data.

[0011] Secondly, this application also provides a blockchain-based resource certificate processing device. The device includes:

[0012] The request acquisition module is used to acquire resource credential processing requests that carry resource credential business data.

[0013] The verifiable credential generation module is used to generate verifiable credentials that conform to the distributed digital identity identifier standard based on the resource credential business data when the business data verification is passed.

[0014] The operation authentication processing module is used to perform operation authentication on the operation requested by the resource credential processing request based on verifiable credentials, and obtain the operation authentication result.

[0015] The update data acquisition module is used to process the target resource credential of the resource credential processing request to obtain updated data when the operation authentication result indicates that the operation verification is successful, based on the resource credential business data.

[0016] The attribute information update module is used to call the smart contract in the blockchain and update the attribute information of the resource certificate that describes the target resource certificate and conforms to the distributed digital identity identifier standard by updating the data.

[0017] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0018] Obtain a resource certificate processing request carrying business data related to resource certificates;

[0019] When the resource credential business data passes the business data verification, a verifiable credential conforming to the distributed digital identity identifier standard is generated based on the resource credential business data.

[0020] Based on verifiable credentials, the operation requested by the resource credential processing request is authenticated to obtain the operation authentication result.

[0021] When the operation authentication result indicates that the operation verification is successful, the target resource certificate for the resource certificate processing request is processed according to the resource certificate business data to obtain the updated data;

[0022] The system invokes a smart contract in the blockchain to update the attribute information of the resource credential that describes the target resource credential and conforms to the distributed digital identity identifier standard by updating the data.

[0023] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0024] Obtain a resource certificate processing request carrying business data related to resource certificates;

[0025] When the resource credential business data passes the business data verification, a verifiable credential conforming to the distributed digital identity identifier standard is generated based on the resource credential business data.

[0026] Based on verifiable credentials, the operation requested by the resource credential processing request is authenticated to obtain the operation authentication result.

[0027] When the operation authentication result indicates that the operation verification is successful, the target resource certificate for the resource certificate processing request is processed according to the resource certificate business data to obtain the updated data;

[0028] The system invokes a smart contract in the blockchain to update the attribute information of the resource credential that describes the target resource credential and conforms to the distributed digital identity identifier standard by updating the data.

[0029] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0030] Obtain a resource certificate processing request carrying business data related to resource certificates;

[0031] When the resource credential business data passes the business data verification, a verifiable credential conforming to the distributed digital identity identifier standard is generated based on the resource credential business data.

[0032] Based on verifiable credentials, the operation requested by the resource credential processing request is authenticated to obtain the operation authentication result.

[0033] When the operation authentication result indicates that the operation verification is successful, the target resource certificate for the resource certificate processing request is processed according to the resource certificate business data to obtain the updated data;

[0034] The system invokes a smart contract in the blockchain to update the attribute information of the resource credential that describes the target resource credential and conforms to the distributed digital identity identifier standard by updating the data.

[0035] The aforementioned blockchain-based resource credential processing method, apparatus, computer equipment, storage medium, and computer program product, when the resource credential business data in the resource credential processing request passes business data verification, generates a verifiable credential conforming to the distributed digital identity identifier standard based on the resource credential business data. Based on the verifiable credential, the operation requested in the resource credential processing request is authenticated. When the operation authentication result indicates that the operation verification is successful, the target resource credential targeted by the resource credential processing request is processed according to the resource credential business data to obtain updated data. A smart contract in the blockchain is then invoked to update the resource credential attribute information describing the target resource credential and conforming to the distributed digital identity identifier standard in the smart contract. During the resource credential processing, the generated verifiable credential conforming to the distributed digital identity identifier standard is used to authenticate the operation requested in the resource credential processing request, and the resource credential attribute information conforming to the distributed digital identity identifier standard is updated. This achieves standardized processing of resource credentials, improves the scalability of resource credential processing for different application scenarios, and enables cross-application scenario processing of resource credentials. Attached Figure Description

[0036] Figure 1 This is an application environment diagram of a blockchain-based resource credential processing method in one embodiment;

[0037] Figure 2 This is a flowchart illustrating a blockchain-based resource credential processing method in one embodiment.

[0038] Figure 3 This is a schematic diagram of the resource freezing process in one embodiment;

[0039] Figure 4 This is a schematic diagram illustrating the flow of debt instruments within a company in one embodiment;

[0040] Figure 5 This is a flowchart illustrating the process of splitting a debt instrument into multiple orders in one embodiment.

[0041] Figure 6 This is a flowchart illustrating the process of splitting a debt instrument in another embodiment;

[0042] Figure 7 This is a structural block diagram of a resource credential processing system in one embodiment;

[0043] Figure 8 This is a block diagram of the resource credential processing system in another embodiment;

[0044] Figure 9 This is a schematic diagram of the protocol design in a resource credential processing method in one embodiment;

[0045] Figure 10 This is a block diagram of the resource credential processing system in another embodiment;

[0046] Figure 11 This is a sequence diagram of the debt instrument issuance process in one embodiment;

[0047] Figure 12 This is a sequence diagram of the debt instrument splitting process in one embodiment;

[0048] Figure 13 This is a sequence diagram of the settlement process for debt instruments in one embodiment;

[0049] Figure 14 This is a structural block diagram of a blockchain-based resource credential processing device in one embodiment;

[0050] Figure 15 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0052] The blockchain-based resource credential processing method provided in this application can be applied to, for example... Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network, and server 104 communicates with blockchain node 106 via a network. Blockchain node 106 can be implemented using computer devices such as servers or terminals. The data storage system can store the data that the corresponding server needs to process. The data storage system can be integrated on the corresponding server, or it can be placed on the cloud or other servers. When resource credential processing is required, the user can send a resource credential processing request to the server 104 through the terminal 102. Upon receiving the resource credential processing request, the server 104 verifies the business data of the resource credential carried in the request. If the business data of the resource credential passes the verification, the server 104 generates a verifiable credential that conforms to the distributed digital identity identifier standard based on the business data of the resource credential. The server 104 then performs operation authentication on the operation requested by the resource credential processing request based on the verifiable credential. If the operation authentication result indicates that the operation verification is successful, the server 104 processes the target resource credential targeted by the resource credential processing request based on the business data of the resource credential, obtains updated data, and calls the smart contract in the blockchain to update the resource credential attribute information that describes the target resource credential and conforms to the distributed digital identity identifier standard in the smart contract through the updated data, thereby obtaining the resource credential processing result of the resource credential processing request. The server 104 can then return the resource credential processing result to the terminal 102.

[0053] In some embodiments, blockchain-based resource credential processing can be implemented by terminal 102 alone, or by terminal 102 and server 104 working together. Terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0054] In one embodiment, such as Figure 2 As shown, a blockchain-based resource credential processing method is provided. This method is executed by a computer device, specifically by a terminal or server alone, or by both a terminal and a server. In this embodiment, the method is applied to... Figure 1 Taking the server in the example, the following steps are included:

[0055] Step 202: Obtain the resource certificate processing request carrying the resource certificate business data.

[0056] Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information exchanged across a batch of networks, used to verify the validity of the information (anti-counterfeiting) and to generate the next block. A blockchain can include an underlying platform, a platform product service layer, and an application service layer.

[0057] The underlying blockchain platform can include modules for user management, basic services, smart contracts, and operational monitoring. The user management module is responsible for managing the identity information of all blockchain participants, including maintaining public and private key generation (account management), key management, and maintaining the correspondence between user identities and blockchain addresses (access management). Under authorization, it also monitors and audits the exchange of certain real identities and provides risk control rule configuration (risk control audit). The basic service module is deployed on all blockchain node devices to verify the validity of business requests. After consensus is reached on valid requests, they are recorded in storage. For a new business request, the basic service first performs interface adaptation parsing and authentication (interface adaptation), and then encrypts the business information using a consensus algorithm (consensus management). The blockchain process involves several layers of data transmission and processing. The first layer, after encryption, transmits the encrypted data consistently and completely to the shared ledger (network communication) and stores it. The second layer, the smart contract module, is responsible for contract registration, issuance, triggering, and execution. Developers can define contract logic using a programming language and publish it to the blockchain (contract registration). Based on the contract terms, the module invokes keys or other events to trigger execution, completing the contract logic. It also provides functions for contract upgrades and cancellations. The third layer, the operation monitoring module, is primarily responsible for deployment, configuration modification, contract settings, cloud adaptation, and real-time visualization of the product's operational status during product release. This includes alerts, network status monitoring, and node device health monitoring. The platform's product service layer provides basic capabilities and implementation frameworks for typical applications. Developers can leverage these capabilities and add business characteristics to implement business logic on the blockchain. The fourth layer provides blockchain-based application services to business stakeholders.

[0058] Resources refer to items whose ownership can be acquired through the internet, and can include at least one of virtual or physical items. Virtual items can be digital objects, specifically including but not limited to account values, funds, stocks, bonds, virtual avatar products, digital collectibles, virtual recharge cards, or game equipment. Digital resources are digitized resources, specifically including digital assets and digital claims. Resource certificates are credentials for digital resources. Through resource certificates, ownership of corresponding digital resources can be declared. By processing resource certificates, such as issuing, splitting, or terminating orders, the allocation, splitting, and transfer of digital resources can be achieved. For example, if a resource is an electronic claim, then the resource certificate can be an electronic claim certificate; if a resource is a digital collectible, then the resource certificate can be a digital collectible certificate.

[0059] A resource credential processing request is a request message used to process resource credentials. The resource credential business data carried in the request refers to the business data involved in the resource credential processing, which may include user account identity data, resource credential information, and other data. The resource credential business data carried in the request can differ depending on the type of request—that is, the request to perform different processing steps. For example, when creating a resource credential, the resource credential business data may include the user account information for creating the resource credential and the amount of resources in the resource credential to be created; while when terminating a resource credential, the resource credential business data may include the user account information holding the resource credential, as well as the resource credential to be terminated. Resource credential processing requests can be sent by the user to the server through a terminal, and the server will perform the corresponding resource credential processing based on the request.

[0060] Specifically, users can send resource credential processing requests to the server through their terminals. These requests carry resource credential business data, which may include, but are not limited to, user account information and data related to resource credentials. The server can then process the resource credentials based on this data.

[0061] Step 204: When the resource credential business data passes the business data verification, a verifiable credential conforming to the distributed digital identity identifier standard is generated based on the resource credential business data.

[0062] Business data verification refers to the verification of resource credential business data in resource credential processing requests to ensure the reliability of the resource credential business data. The specific verification items and methods correspond to the specific business data within the resource credential business data, enabling targeted verification processing. For example, resource credential business data may include user account information and resource credential information; therefore, business data verification may include verification of both account information and resource credential information. Smart contracts can be pre-deployed in the blockchain and may include logic for generating entity identifiers and corresponding verifiable credentials. Entity identifiers represent entities and are obtained through abstraction; a specific entity identifier can be a string. Verifiable credentials describe the entity's attribute information, including the issuer, validity period, and the attributes being verified.

[0063] Decentralized IDs (DIDs), combined with blockchain technology, enable users to truly own and control their personal data and assets, achieving decentralized sharing capabilities across departments, industries, and regions. Specifically, DIDs, implemented on blockchain, prevent identity data from being controlled by a single centralized authority, thus achieving decentralization; based on a distributed public key infrastructure, DIDs ensure that each user's identity is controlled by its owner, not a trusted third party, allowing individuals to manage their own identities autonomously; and since identity-related data is anchored to the blockchain, the authentication process does not rely on the application providing the identity.

[0064] Based on the DID standard, entities can be abstracted to obtain the corresponding entity identifier, i.e., the DID identifier. An entity's DID digital identity can consist of three parts: the DID identifier, the DID document, and verifiable credentials (VC). Each DID identifier must have a unique DID document, but can have a variable number of verifiable credentials. The entity's digital identity is represented by the DID identifier, which should possess the characteristics of application-specific uniqueness and cross-application self-discovery. The DID identifier conforms to the W3C (World Wide Web Consortium) specification and mainly includes a fixed prefix, a partition identifier, and a unique number identifier. The DID document describes the characteristics of the entity's digital identity and has a one-to-one correspondence with the DID identifier. The DID document can record account public keys, account status, authorized management accounts, and provides extensible fields for users to flexibly configure according to business scenarios. Verification of transactions related to digital identity services will be based on the public key in the DID document. The DID document and the DID identifier form a key-value pair, describing the public key, authentication protocol, and service endpoint necessary to guide the entity with the identifier to conduct cryptographically verifiable interactions. A DID document describes the DID subject identifier, public key, verification protocol, and server endpoint necessary for password verification interactions with the identified object. Verifiable credentials describe the real-world identity attributes of an entity corresponding to a digital identity, recording information such as the issuer, validity period, and the attributes being proven.

[0065] Specifically, the server can perform business data verification on the resource credential business data to confirm its validity and reliability. For example, the server can obtain verification data, specifically from the blockchain, and use this data to verify the resource credential business data. Alternatively, the server can also verify the resource credential business data through smart contracts within the blockchain. Once the business data verification confirms the resource credential business data is reliable and secure, the server can invoke a pre-deployed smart contract in the blockchain to generate a verifiable credential conforming to the Distributed Digital Identity Token (DID) standard based on the resource credential business data. In practice, a smart contract can be pre-deployed in the blockchain. The contract execution logic stipulated in the smart contract can include processing DID identification, DID document generation, and VC generation based on the DID standard. The server can invoke this smart contract to generate a verifiable credential using the resource credential business data, and this verifiable credential conforms to the DID standard. The verifiable credential generated from the resource credential business data can be used to authenticate the operations requested by the resource credential processing request, ensuring the reliability of the requested operations. In practical applications, servers can also directly generate verifiable credentials based on resource credential business data according to the Distributed Digital Identity Identifier standard, without relying on smart contracts.

[0066] Step 206: Based on verifiable credentials, perform operation authentication on the operation requested by the resource credential processing request to obtain the operation authentication result.

[0067] The resource credential processing request refers to the operation requested in the request, which may include various types of processing such as resource credential creation, resource credential splitting, or resource credential closing (i.e., terminating the resource credential). Operation authentication verifies the operation requested in the resource credential processing request to ensure that the processing of the resource credential has been confirmed by the resource credential holder. The operation authentication result indicates whether the operation requested in the resource credential processing request has been authorized and confirmed by the user.

[0068] Specifically, the server can use the generated verifiable credentials to authenticate the operations requested by the resource credential processing request. This can be achieved by issuing the verifiable credentials to the resource credential holder (e.g., the requester who issued the resource credential processing request), who can then sign the credentials to obtain the authentication result. Alternatively, the holder can use their private key to sign the credentials and return the signed credentials to the server. The server then verifies the signed credentials, thereby authenticating the operations requested by the resource credential processing request.

[0069] Step 208: When the operation authentication result indicates that the operation verification is successful, the target resource certificate for the resource certificate processing request is processed according to the resource certificate business data to obtain updated data.

[0070] The target resource credential refers to the resource credential that the resource credential processing request needs to target. For example, when the resource credential processing request is a splitting request, the target resource credential may include the parent resource credential that needs to be split, as well as the sub-resource credentials obtained after splitting the parent resource credential. Similarly, when the resource credential processing request is a billing request, the target resource credential may include the resource credential that needs to be created. Updated data refers to the processing result data obtained after processing the target resource credential according to the resource credential business data. Updating the data allows for updating the attribute information of the target resource credential, thereby realizing the processing of the target resource credential.

[0071] Specifically, the operation authentication result indicates that the operation verification is successful, signifying that the operation requested by the resource credential processing request has been authorized and confirmed by the user. The server can then respond to the resource credential processing request and perform resource credential processing. Specifically, the server can determine the target resource credential for the resource credential processing request and perform corresponding operations on the target resource credential based on the resource credential business data. These operations may include resource allocation when creating an order, resource splitting when splitting an order, and resource termination when closing an order, resulting in updated data for the target resource credential. For example, for resource allocation processing for a target resource credential, the updated data may include various data such as the resource quantity, validity period, and holder identity information of the target resource credential.

[0072] Step 210: Invoke the smart contract in the blockchain and update the attribute information of the resource certificate that describes the target resource certificate and conforms to the distributed digital identity identifier standard by updating the data.

[0073] Resource credential attribute information describes the target resource credential. In the Distributed Digital Identity Identifier standard, resource credential attribute information can be stored in a DID document, which corresponds to the DID identifier of the target resource credential. Resource credential attribute information may include various descriptive information such as the credential status, credential resource quantity, frozen resource quantity, and holder identity information of the target resource credential.

[0074] Specifically, the smart contract in the blockchain pre-defines the DID document data read / write logic based on the Distributed Digital Identity Token (DID) standard. The server can update the DID document associated with the DID identifier of the target resource credential by calling the smart contract, thereby updating the resource credential attribute information of the target resource credential. The server can call the smart contract in the blockchain to determine the resource credential attribute information in the smart contract that describes the target resource credential and conforms to the Distributed Digital Identity Token (DID) standard. For example, the server can determine the DID identifier of the target resource credential and determine the corresponding DID document based on the DID identifier. The DID document stores the resource credential attribute information of the target resource credential. The server can call the smart contract to update the DID document in the smart contract by updating the data, thereby updating the resource credential attribute information of the target resource credential and obtaining the processing result for the target resource credential. The server can then feed back the processing result for the target resource credential to the terminal, thus completing the processing of the target resource credential.

[0075] In a specific application, the resource credential can be a stock certificate. Users can send resource credential processing requests to the server via a terminal, specifically order splitting requests. These requests carry resource credential business data, including user account information and stock certificate attribute information. The server can perform business data verification on the resource credential business data, including identity verification and stock certificate verification. When the business data verification passes, the server generates a verifiable credential conforming to the Distributed Digital Identity Token (DVI) standard based on the resource credential business data. The smart contract specifies processing logic based on the DVI standard, and based on this logic, it can generate a verifiable credential conforming to the DVI standard. The server then authenticates the operation requested by the resource credential processing request based on the verifiable credential. Specifically, the server can send the verifiable credential to the requesting end, where the user signs the verifiable credential. The server then verifies the signed verifiable credential, thereby authenticating the operation requested by the resource credential processing request.

[0076] Once the operation verification is successful, the server can process the target resource certificate for the resource certificate processing request based on the resource certificate business data. Specifically, it performs order splitting of stock certificates to obtain updated data corresponding to the target resource certificate, i.e., the target stock certificate. The server can invoke a smart contract in the blockchain to update the resource certificate attribute information of the target stock certificate in the smart contract through update data. The smart contract can pre-store stock certificate information, specifically including a stock certificate DID identifier and a stock certificate DID document built based on the Distributed Digital Identity Authentication Standard (DISA). The stock certificate DID identifier identifies the stock certificate, while the stock certificate DID document records the stock certificate's attribute information. On the other hand, the smart contract can also pre-store user account information, specifically including a user account DID identifier and a user account DID document built based on the DISA. The user account DID identifier identifies the user account, while the user account DID document records the user account's attribute information. The server can perform business data verification on the resource certificate business data using the attribute information in the stock certificate DID document and the user account DID document within the smart contract. In practice, the resource certificate processing request may include the stock certificate DID identifier of the target stock certificate. The server can call the smart contract to update the stock certificate DID document associated with the stock certificate DID identifier in the smart contract, thereby updating the resource certificate attribute information. The server can then return the processing result of the order splitting for the target stock certificate to the terminal.

[0077] In the aforementioned blockchain-based resource credential processing method, when the resource credential business data in the resource credential processing request passes business data verification, a verifiable credential conforming to the Distributed Digital Identity Token (DVI) standard is generated based on the resource credential business data. Operation authentication is performed on the operation requested by the resource credential processing request based on the verifiable credential. When the operation authentication result indicates that the operation verification is successful, the target resource credential targeted by the resource credential processing request is processed according to the resource credential business data to obtain updated data. A smart contract in the blockchain is then invoked to update the resource credential attribute information describing the target resource credential and conforming to the DVI standard through the updated data. During the resource credential processing, the generated verifiable credential conforming to the DVI standard is used to authenticate the operation requested by the resource credential processing request, and the resource credential attribute information conforming to the DVI standard is updated. This achieves standardized processing of resource credentials, improving the scalability of resource credential processing for different application scenarios and enabling cross-application scenario processing of resource credentials.

[0078] In one embodiment, the resource credential processing request includes an invoice request; generating a verifiable credential conforming to the Distributed Digital Identity Identifier (DDI) standard based on resource credential business data includes: determining resource credential invoicing data for the target resource credential targeted by the invoice request from the resource credential business data; generating a resource credential identifier for the target resource credential and an attribute document associated with the resource credential identifier based on the resource credential invoicing data according to the DDI standard; and generating a verifiable credential based on the resource credential identifier, attribute document, and resource credential business data according to the DDI standard.

[0079] In this context, an invoice request refers to a request message used to request the creation or generation of resource credentials. Resource credential processing requests include invoice requests, indicating that a user needs to issue a resource credential, and the target resource credential is the entity for which the user needs to issue the resource credential. Resource credential invoicing data is processing data related to issuing the target resource credential. This data can be used to abstract the target resource credential entity, such as generating a resource credential identifier and attribute document based on the Distributed Digital Identity Identifier (DID) standard. The resource credential identifier and attribute document are associated and generated according to the DID standard; that is, the resource credential identifier can be a DID identifier in the DID standard, and the attribute document can be a DID document associated with the DID identifier in the DID standard. The DID identifier is used to identify the corresponding abstract entity, i.e., the target resource credential; while the DID document is used to store the attribute information of the target resource credential.

[0080] Specifically, resource credential processing requests include invoice requests, meaning the terminal needs to generate resource credentials. The server extracts the resource credential invoicing data for the target resource credential from the resource credential business data. This data includes information such as the target resource credential's resource limit, validity period, and holder identity. The resource credential invoicing data allows for accurate definition of the target resource credential, enabling invoicing processing. The server generates a resource credential identifier and attribute document using the resource credential invoicing data according to the Distributed Digital Identity Identifier (DID) standard. This can be achieved by calling a pre-deployed smart contract in the blockchain. The resource credential identifier identifies the target resource credential, while the attribute document corresponds to it and records various attribute information, allowing for accurate representation of the target resource credential. Smart contracts can pre-define processing logic based on the Distributed Digital Identity Authentication Standard (DDI), thereby enabling the generation of resource credential identifiers, attribute documents, and verifiable credentials based on the DDI standard.

[0081] After obtaining the resource credential identifier of the target resource credential and the attribute document associated with the resource credential identifier, the server generates a verifiable credential based on the resource credential identifier, attribute document, and resource credential business data, according to the Distributed Digital Identity Identifier standard. The verifiable credential can be used to authenticate the invoicing operation requested in the invoicing request, ensuring that the invoicing operation is authorized by the user and thus ensuring the reliability of the invoicing operation.

[0082] In this embodiment, for an invoice request, the server generates a resource credential identifier and attribute document according to the Distributed Digital Identity Identifier (DDI) standard, and further generates a verifiable credential according to the DDI standard. Based on the DDI standard, the target resource credential can be processed in a standardized manner, so that the resource credential has the good protocol readability, scalability and universality of the DDI standard. This can improve the scalability of resource credential processing for different application scenarios, thereby enabling cross-application scenario processing of resource credentials.

[0083] In one embodiment, a verifiable credential is generated based on the resource credential identifier, attribute document, and resource credential business data in accordance with the Distributed Digital Identity Identifier standard. This includes: determining invoice verification data for the invoice request from the resource credential business data; and generating a verifiable credential based on the resource credential identifier, attribute document, and invoice verification data in accordance with the Distributed Digital Identity Identifier standard.

[0084] Among them, the order verification data is the data that needs to be verified in order processing for the order request. The data type and data range of the order verification data can be set according to actual needs, such as including but not limited to various types of data such as resource voucher quota, validity period, and scope of use.

[0085] Specifically, not all data in the resource credential business data may be required for verification during invoicing. The server can filter the resource credential business data to obtain invoicing verification data specific to the invoicing request. This invoicing verification data describes the invoicing operation requested, requiring user confirmation to ensure the reliability of the invoicing operation. Based on the resource credential identifier, attribute document, and invoicing verification data, the server can process the data according to the Distributed Digital Identity Token (DID) standard to generate a verifiable credential for the invoicing request.

[0086] In this embodiment, the server obtains the invoice verification data that needs to be verified from the resource credential business data, and generates a verifiable credential based on the resource credential identifier, attribute document and invoice verification data in accordance with the distributed digital identity identifier standard. This enables the server to obtain a verifiable credential that can accurately and effectively authenticate the invoice operation requested by the invoice request.

[0087] In one embodiment, processing the target resource certificate for the resource certificate processing request based on resource certificate business data to obtain updated data includes: performing resource allocation processing on the target resource certificate based on resource certificate business data to obtain invoice update data for the target resource certificate.

[0088] The target resource certificate is the resource certificate requested in the invoice request. Resource allocation processing is performed on the target resource certificate to obtain the resource amount required in the invoice request. Invoice update data is data related to the invoice operation generated during the resource allocation processing of the target resource certificate. Invoice update data can include attribute information related to the invoice operation, such as resource allocation amount, validity period, effective period, and application scope. The specific data type and scope of the invoice update data can be set according to actual needs.

[0089] Specifically, the server can perform resource allocation processing on the target resource credential based on the resource credential business data. For example, it can allocate resources of a corresponding amount to the target resource credential according to the requested invoice amount in the resource credential business data, thus obtaining the invoice update data for the target resource credential. The invoice update data can be used to describe the invoice operation on the target resource credential, and may specifically include data generated or updated during the invoice operation.

[0090] Furthermore, the smart contract in the blockchain is invoked to update the resource certificate attribute information in the smart contract that describes the target resource certificate and conforms to the distributed digital identity identifier standard by updating the data. This includes: invoking the smart contract in the blockchain to update the attribute document in the smart contract by issuing an order to update the data; wherein the attribute document conforms to the distributed digital identity identifier standard and includes resource certificate attribute information describing the target resource certificate.

[0091] The attribute document conforms to the Distributed Digital Identity Identifier standard, specifically the DID document in the Distributed Digital Identity Identifier standard, which is used to record the resource credential attribute information of the target resource credential.

[0092] Specifically, the server can invoke a smart contract in the blockchain to update the attribute document within the smart contract using order update data. The smart contract can determine the resource attribute information of the target resource certificate based on its resource certificate identifier, specifically by determining the DID document, which stores the resource certificate attribute information. The server can then update the attribute document of the target resource certificate with the order update data, thereby updating the resource certificate attribute information of the target resource certificate and processing the order for that target resource certificate.

[0093] In this embodiment, for an order request, the server performs resource allocation processing on the target resource credential based on the resource credential business data. Then, by calling a smart contract in the blockchain, it updates the attribute document of the target resource credential in the smart contract based on the order update data obtained from the resource allocation processing. This achieves the update processing of the resource credential attribute information and realizes the order processing for the target resource credential. By using an attribute document conforming to the Distributed Digital Identity Identifier (DDI) standard to record the resource credential attribute information, the resource credential possesses the good protocol readability, extensibility, and universality of the DDI standard. This improves the scalability of resource credential processing for different application scenarios, thereby enabling cross-application scenario processing of resource credentials.

[0094] In one embodiment, the resource credential processing request includes a splitting request; the target resource credential for the splitting request includes a parent resource credential and sub-resource credentials formed by splitting the parent resource credential; generating a verifiable credential conforming to the Distributed Digital Identity Identifier (DDI) standard based on the resource credential business data includes: determining the resource credential splitting data of the parent resource credential from the resource credential business data; generating a sub-resource credential identifier and an attribute document associated with the sub-resource credential identifier based on the resource credential splitting data according to the DDI standard; and generating a verifiable credential based on the sub-resource credential identifier, attribute document, and resource credential business data according to the DDI standard.

[0095] A splitting request is a message used to request the splitting of a resource credential. Resource credential processing requests include splitting requests, indicating that the user needs to split a resource credential. The target resource credential may include the parent resource credential to be split, and the child resource credentials obtained after splitting the parent resource credential. Resource credential splitting data is processing data related to splitting the target resource credential. Using resource credential splitting data, the target resource credential entity can be abstracted, such as generating resource credential identifiers and attribute documents based on the Distributed Digital Identity Identifier standard.

[0096] Specifically, resource certificate processing requests include splitting requests, meaning the end user needs to split resource certificates. The server extracts the splitting data for the parent resource certificate from the resource certificate business data. This extraction process includes information such as the split resource amount, validity period, and holder identity of the parent resource certificate. Using this splitting data, the splitting process for the parent resource certificate can be accurately defined, enabling the splitting of the parent resource certificate. The server then uses this splitting data to generate a sub-resource certificate identifier and attribute document according to the Distributed Digital Identity Identifier (DID) standard. This can be achieved by calling a pre-deployed smart contract in the blockchain. The sub-resource certificate identifier identifies the sub-resource certificate, and the attribute document corresponds to it, recording various attribute information of the sub-resource certificate. This allows for an accurate representation of the sub-resource certificate. After obtaining the sub-resource credential identifier and the associated attribute document of the sub-resource credential, the server generates a verifiable credential based on the sub-resource credential identifier, attribute document, and resource credential business data, according to the Distributed Digital Identity Identifier standard. In specific applications, the resource credential business data may carry the parent resource credential identifier of the parent resource credential. The server can generate a verifiable credential based on the sub-resource credential identifier, the associated attribute document of the sub-resource credential identifier, the parent resource credential identifier, the associated attribute document of the parent resource credential identifier, and the resource credential business data. The verifiable credential can be used to authenticate the order splitting operation requested in the order splitting request, ensuring that the order splitting operation is authorized by the user and ensuring the reliability of the order splitting operation.

[0097] In this embodiment, for a splitting request, the server generates a sub-resource credential identifier and attribute document for the sub-resource credential formed by splitting the parent resource credential, according to the Distributed Digital Identity Identifier (DDI) standard. Furthermore, it generates a verifiable credential according to the DDI standard. Based on the DDI standard, the target resource credential can be processed in a standardized manner, enabling the resource credential to possess the good protocol readability, extensibility, and universality of the DDI standard. This improves the scalability of resource credential processing for different application scenarios, thereby enabling cross-application scenario processing of resource credentials.

[0098] In one embodiment, a verifiable credential is generated based on the sub-resource credential identifier, attribute document, and resource credential business data in accordance with the Distributed Digital Identity Identifier standard, including: determining the splitting verification data for the splitting request from the resource credential business data; and generating the verifiable credential based on the sub-resource credential identifier, attribute document, and splitting verification data in accordance with the Distributed Digital Identity Identifier standard.

[0099] Among them, the split order verification data is the data that needs to be verified in response to the split order request. The data type and data range of the split order verification data can be set according to actual needs, such as including but not limited to various types of data such as resource voucher split amount, validity period, and scope of use.

[0100] Specifically, not all data in the resource credential business data may be required for verification during order splitting. The server can filter the resource credential business data to obtain splitting verification data specific to the splitting request. This splitting verification data describes the splitting operation requested in the splitting request, requiring user confirmation to ensure its reliability. The server can process the data according to the Distributed Digital Identity Identifier standard based on the sub-resource credential identifier, the associated attribute document, and the splitting verification data to generate a verifiable credential for the splitting request. In specific applications, the server can also determine the parent resource credential identifier from the resource credential business data, further obtain the associated attribute document, and generate a verifiable credential based on the sub-resource credential identifier, the associated attribute document, the parent resource credential identifier, the associated attribute document, and the splitting verification data.

[0101] In this embodiment, the server obtains the split verification data that needs to be verified from the resource credential business data. According to the distributed digital identity identifier standard, it generates a verifiable credential based on the sub-resource credential identifier, the attribute document associated with the sub-resource credential identifier, and the split verification data. This enables the server to obtain a verifiable credential that can accurately and effectively authenticate the split operation requested by the split request.

[0102] In one embodiment, processing the target resource certificate for the resource certificate processing request based on resource certificate business data to obtain updated data includes: performing resource splitting processing on the parent resource certificate and the sub-resource certificate based on the resource certificate business data to obtain split update data associated with the parent resource certificate and the sub-resource certificate.

[0103] The target resource certificate includes a parent resource certificate and child resource certificates. The parent resource certificate is the resource certificate that the splitting request needs to split, and the child resource certificate is the resource certificate obtained after splitting the parent and child resource certificates. By performing resource splitting processing on the parent and child resource certificates, parent and child resource certificates that meet the resource quota in the splitting request are obtained. The splitting update data is data related to the splitting operation generated during the resource splitting processing of the target resource certificate. The splitting update data can include attribute information of the target resource certificate related to the splitting operation, and the specific data type and scope of the splitting update data can be set according to actual needs.

[0104] Specifically, the server can perform resource splitting on the target resource certificate based on the resource certificate business data. This splitting can be done on both the parent and child resource certificates. For example, according to the requested split amount in the resource certificate business data, the server can deduct the resource quota from the parent resource certificate and increase the resource quota from the child resource certificate, resulting in split update data. This split update data can describe the splitting operation and may include data generated or updated during the splitting process.

[0105] Furthermore, the smart contract in the blockchain is invoked to update the resource certificate attribute information that describes the target resource certificate and conforms to the distributed digital identity identifier standard by updating data. This includes: invoking the smart contract in the blockchain to update the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier in the smart contract by splitting the data; wherein the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier conform to the distributed digital identity identifier standard; the attribute document associated with the parent resource certificate identifier includes resource certificate attribute information describing the parent resource certificate, and the attribute document associated with the child resource certificate identifier includes resource certificate attribute information describing the child resource certificate.

[0106] The attribute document conforms to the Distributed Digital Identity Identifier standard, specifically the DID document in the Distributed Digital Identity Identifier standard, which is used to record the resource credential attribute information of the resource credential.

[0107] Specifically, the server can invoke a smart contract in the blockchain to update the attribute documents within the smart contract using split update data. This includes the attribute documents associated with the parent resource certificate identifier and the attribute documents associated with the child resource certificate identifier. By invoking the smart contract in the blockchain, the server can update the attribute documents associated with the parent and child resource certificate identifiers respectively, thereby achieving the update processing of the resource certificate attribute information of the target resource certificate and realizing the split processing of the target resource certificate.

[0108] In this embodiment, for order splitting requests, the server performs resource splitting processing on the parent resource certificate and child resource certificates based on resource certificate business data. Then, by calling a smart contract in the blockchain, based on the order splitting update data obtained from resource allocation processing, it updates the attribute documents associated with the parent resource certificate identifier and the attribute documents associated with the child resource certificate identifier in the smart contract, thereby updating the resource certificate attribute information of the target resource certificate and realizing the order splitting processing of the target resource certificate. Utilizing attribute documents conforming to the Distributed Digital Identity Identifier (DDI) standard to record the resource certificate attribute information of the target resource certificate gives the resource certificate the good protocol readability, extensibility, and universality of the DDI standard, improving the scalability of resource certificate processing for different application scenarios, thus enabling cross-application scenario processing of resource certificates.

[0109] In one embodiment, such as Figure 3 As shown, the blockchain-based resource certificate processing method also includes resource freezing processing, specifically including:

[0110] Step 302: When the operation authentication result indicates that the operation verification is successful, the smart contract in the blockchain is invoked to split and freeze the parent resource certificate.

[0111] Specifically, resource splitting and freezing refers to freezing the resources in the parent resource certificate that are to be split, to ensure that the resource splitting process can be completed subsequently. For example, if the amount of resources to be split in the parent resource certificate is 100, then the resources of 100 in the parent resource certificate need to be frozen to ensure that there are at least 100 resources in the parent resource certificate that can complete the order splitting process.

[0112] Specifically, once the operation authentication result indicates that the operation verification is successful, the server can call the smart contract to freeze the resources in the parent resource certificate that need to be split. Specifically, the server can call the smart contract to update the attribute document of the parent resource certificate in the smart contract, thereby realizing the freezing of the split resources of the parent resource certificate.

[0113] Step 304: Invoke the smart contract to generate a verifiable credential for the holder of the sub-resource credential based on the sub-resource credential identifier and resource credential business data, in accordance with the distributed digital identity identifier standard.

[0114] Among them, the holder-verifiable certificate refers to the certificate that can be verified by the holder account of the sub-resource certificate. Through the holder-verifiable certificate, the holder of the sub-resource certificate can authenticate the splitting operation of the splitting request.

[0115] Specifically, the server invokes a smart contract to generate a holder-verifiable credential for the sub-resource credential based on the sub-resource credential identifier and resource credential business data, in accordance with the Distributed Digital Identity Token standard. The holder-verifiable credential is generated in the same way as the verifiable credential, but based on different data generated by the smart contract.

[0116] Step 306: Send the holder's verifiable credential to the holder of the sub-resource credential; the holder's verifiable credential is used to instruct the holder to confirm the split order based on the holder's verifiable credential, and return the split order confirmation result.

[0117] In this context, "holder" refers to the user who holds the sub-resource certificate. When splitting the parent resource certificate, multiple sub-resource certificates can be obtained. These sub-resource certificates can be assigned to different users, and the assigned user becomes the holder of the corresponding sub-resource certificate. The splitting of the parent resource certificate requires confirmation from both the holder of the parent resource certificate and the holders of the sub-resource certificates to ensure the splitting operation takes effect.

[0118] Specifically, the server can determine the holder of the sub-resource credential, and more specifically, the user account holding the sub-resource credential. The server then sends a verifiable credential to the holder, and more specifically, to the user account's terminal, instructing the user account to perform order splitting confirmation based on the verifiable credential and return the order splitting confirmation result. In practical applications, the holder of the sub-resource credential can sign the verifiable credential to achieve order splitting confirmation, and return the signed verifiable credential as the order splitting confirmation result.

[0119] Step 308: When the order splitting confirmation result indicates acceptance of the order splitting, the freeze on the splitting resources of the parent resource certificate is lifted, and the process is executed to process the target resource certificate for the resource certificate processing request based on the resource certificate business data to obtain updated data.

[0120] Specifically, unfreezing the split resource refers to releasing the frozen resource amount in the parent resource certificate, thereby enabling order splitting processing for the parent resource certificate. Specifically, the server receives the order splitting confirmation result from the holder. When the confirmation result indicates that the holder accepts the order splitting, the server can unfreeze the split resource of the parent resource certificate and proceed with the steps of processing the target resource certificate for the resource certificate processing request based on the resource certificate business data to obtain updated data, thus enabling order splitting processing of the parent resource certificate.

[0121] In this embodiment, for a split request, the parent resource certificate is split and frozen, and the holder of the sub-resource certificate is confirmed to split the order through the holder's verifiable certificate. When the holder of the sub-resource certificate confirms acceptance of the split, the server releases the split resource freeze of the parent resource certificate and performs split processing on the parent resource certificate. This ensures that the split processing is authorized by the holder of the sub-resource certificate, thereby improving the reliability of the split operation.

[0122] In one embodiment, the resource credential processing request includes at least one of an order creation request or an order splitting request; the blockchain-based resource credential processing method further includes: generating a resource credential token for the target resource credential targeted by the resource credential processing request; establishing a binding relationship between the resource credential token and the resource credential identifier of the target resource credential; the resource credential identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; and calling the smart contract to update the binding relationship in the resource credential attribute information.

[0123] Resource credential tokens are used to identify resource credentials. These tokens are generated by smart contracts deployed on the server, based on the resource credential business data in resource credential processing requests. This establishes a binding relationship between the resource credential token and the resource credential identifier on the server, further improving the applicability of resource credentials for different application scenarios. Both resource credential tokens and resource credential identifiers are generated based on different smart contracts and can be used to identify resource credentials.

[0124] Specifically, for order creation or order splitting requests, new resource credentials need to be generated. Processing an order creation request requires generating the target resource credential, while processing an order splitting request requires generating sub-resource credentials obtained by splitting the parent resource credential. The server can generate resource credential tokens for the target resource credential targeted by the resource credential processing request. This can be done through a deployed credential smart contract, following a token generation algorithm. In order creation, the server generates the resource credential token for the target resource credential to be issued; in order splitting, the server generates the resource credential token for the split sub-resource credential. The server binds the resource credential token to the resource credential identifier of the target resource credential, establishing a binding relationship between them. The resource credential identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard. Both the resource credential identifier and the resource credential token can identify the target resource credential, thereby further improving its security. The server calls the smart contract to update the binding relationship into the resource credential attribute information. Specifically, the server can update the binding relationship into the attribute document of the target resource credential, such as updating it into the DID document, thereby recording the binding relationship between the resource credential token and the resource credential identifier through the DID document.

[0125] In this embodiment, the resource credential token that identifies the target resource credential is bound to the resource credential identifier, and the binding relationship is updated in the resource credential attribute information of the target resource credential. Thus, the resource credential attribute information can be obtained based on the resource credential token or the resource credential identifier, which can enhance the expression of the target resource credential and improve the scalability of resource credential processing for different application scenarios, thereby enabling cross-application scenario processing of resource credentials.

[0126] In one embodiment, the resource credential processing request includes a settlement request; generating a verifiable credential conforming to the Distributed Digital Identity Identifier standard based on the resource credential business data includes: determining, from the resource credential business data, the resource credential identifier of the target resource credential for which the settlement request is directed, and the settlement verification data for the settlement request; and generating a verifiable credential based on the resource credential identifier and the settlement verification data in accordance with the Distributed Digital Identity Identifier standard.

[0127] The settlement request refers to a request message used to request the termination of a resource credential. Resource credential processing requests include settlement requests, indicating that the user needs to terminate a resource credential; the target resource credential is the entity for which the user needs to terminate. Settlement verification data is the data that needs to be verified for the settlement operation in response to the settlement request, and may include the amount of resource to be terminated, the quantity to be terminated, and the effective time of termination. The resource credential identifier is used to identify the target resource credential; the resource credential identifier can be generated by calling a smart contract and conforms to the distributed digital identity identifier standard.

[0128] Specifically, resource credential processing requests include settlement requests, whereby the end user needs to terminate resource credentials. The server extracts the resource credential identifier of the target resource credential for the settlement request, as well as the settlement verification data for the settlement request, from the resource credential business data. Based on the resource credential identifier and settlement verification data, the server processes the data according to the Distributed Digital Identity Token (DDI) standard to generate a verifiable credential. Specifically, the server can call a smart contract to generate the verifiable credential. The smart contract can pre-define the processing logic based on the DDI standard, thereby generating the resource credential identifier, attribute document, and verifiable credential. The verifiable credential can be used to authenticate the settlement operation requested in the settlement request, ensuring that the settlement operation is authorized by the user and ensuring the reliability of the settlement operation.

[0129] In this embodiment, for a checkout request, the server generates a verifiable credential according to the Distributed Digital Identity Identifier standard, based on the resource credential identifier of the target resource credential and the checkout verification data for the checkout request. Based on the Distributed Digital Identity Identifier standard, the target resource credential can be processed in a standardized manner, giving the resource credential the good protocol readability, extensibility and universality of the Distributed Digital Identity Identifier standard. This can improve the scalability of resource credential processing for different application scenarios, thereby enabling cross-application scenario processing of resource credentials.

[0130] In one embodiment, processing the target resource certificate for the resource certificate processing request based on resource certificate business data to obtain updated data includes: performing resource certificate termination processing on the target resource certificate based on the resource certificate business data to obtain the settlement update data of the target resource certificate.

[0131] Resource certificate termination processing refers to the termination of target resource certificates that require termination, thereby enabling the closing operation of the target resource certificate. This can be achieved by updating the target resource certificate to an invalid state or updating its resource quota to 0. Closing update data is data generated during the resource certificate termination processing of the target resource certificate and related to the closing operation. This data can include attribute information related to the closing operation, such as the resource termination quota, effective period, and application scope. The specific data type and scope of the closing update data can be set according to actual needs.

[0132] Specifically, the server can perform resource certificate termination processing on the target resource certificate based on the resource certificate business data. For example, it can terminate the corresponding amount of resources for the target resource certificate according to the termination amount requested in the resource certificate business data, and obtain the settlement update data of the target resource certificate. The settlement update data can be used to describe the settlement operation on the target resource certificate, and can specifically include data generated or updated during the settlement operation.

[0133] Furthermore, the smart contract in the blockchain is invoked to update the resource certificate attribute information that describes the target resource certificate and conforms to the distributed digital identity identifier standard by updating the data. This includes: invoking the smart contract in the blockchain to update the attribute document associated with the resource certificate identifier in the smart contract by updating the data through the settlement statement; wherein, the attribute document conforms to the distributed digital identity identifier standard and includes resource certificate attribute information describing the target resource certificate.

[0134] The attribute document conforms to the Distributed Digital Identity Identifier standard and includes resource certificate attribute information describing the target resource certificate. Specifically, the server can invoke a smart contract in the blockchain to update the attribute document in the smart contract using settlement update data. The smart contract can determine the resource certificate attribute information of the target resource certificate based on its resource certificate identifier, specifically by determining the DID document, which stores the resource certificate attribute information. The server can then update the attribute document of the target resource certificate with settlement update data, thereby updating the resource certificate attribute information of the target resource certificate and completing the settlement process for the target resource certificate.

[0135] In this embodiment, for a settlement request, the server performs resource certificate termination processing on the target resource certificate based on the resource certificate business data. Then, by calling a smart contract in the blockchain, and based on the settlement update data obtained from resource allocation processing, it updates the attribute document of the target resource certificate in the smart contract, thereby achieving the update processing of the resource certificate attribute information and realizing the settlement processing of the target resource certificate. By using attribute documents conforming to the Distributed Digital Identity Identifier (DDI) standard to record the resource certificate attribute information of the target resource certificate, the resource certificate possesses the good protocol readability, extensibility, and universality of the DDI standard. This improves the scalability of resource certificate processing for different application scenarios, thus enabling cross-application scenario processing of resource certificates.

[0136] In one embodiment, the resource credential processing request includes a settlement request; the blockchain-based resource credential processing method further includes: determining the resource credential token of the target resource credential for which the resource credential processing request is directed; releasing the binding relationship between the resource credential token and the resource credential identifier of the target resource credential; the resource credential identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; and calling the smart contract to update the information of the release of the binding relationship into the resource credential attribute information.

[0137] Resource credential tokens are used to identify resource credentials. These tokens are generated by smart contracts deployed on the server, based on the resource credential business data in resource credential processing requests. This establishes a binding relationship between the resource credential token and the resource credential identifier on the server, further improving the applicability of resource credentials for different application scenarios. Both resource credential tokens and resource credential identifiers are generated based on different smart contracts and can be used to identify resource credentials.

[0138] Specifically, for a settlement request, the server can determine the resource credential token used to identify the target resource credential. The server will then unbind the resource credential token from the resource credential identifier of the target resource credential, thereby unbinding the resource credential token from the resource credential identifier. The unbinding information will then be updated in the resource credential attribute information by calling a smart contract.

[0139] In this embodiment, when the target resource credential is settled, the binding relationship between the resource credential token and the resource credential identifier is removed, and the information on the removal of the binding relationship is updated in the resource credential attribute information of the target resource credential. This allows for timely removal of the binding relationship between the resource credential token and the resource credential identifier, ensuring the security of the resource credential identifier.

[0140] In one embodiment, based on a verifiable credential, operation authentication is performed on the operation requested by the resource credential processing request to obtain an operation authentication result, including: sending the verifiable credential to the request triggering end that issued the resource credential processing request; the verifiable credential is used to instruct the requesting account of the request triggering end to sign the verifiable credential and return the signed verifiable credential; and performing business data verification and signature verification on the signed verifiable credential to obtain the operation authentication result.

[0141] In this context, the request triggering end refers to the terminal that issues the resource credential processing request, and the requesting account is the user account that performs resource credential processing through the request. The signature can be implemented by the requesting account using the private key it carries.

[0142] Specifically, the server can send verifiable credentials to the request triggering end that issued the resource credential processing request, instructing the requesting account on the triggering end to sign the verifiable credentials and return the signed verifiable credentials. The server can then perform business data verification and signature verification on the verifiable credentials signed by the requesting account to obtain the operation authentication result. In practical applications, the signed verifiable credentials can be obtained by the requesting account through a signing operation using its private key, and the server can perform signature verification using the corresponding public key of the requesting account, thereby achieving signature verification processing.

[0143] In this embodiment, the server sends verifiable credentials to the request triggering end for signature by the requesting account. The server then performs business data verification and signature verification on the signed verifiable credentials, thereby authenticating the operation requested by the resource credential processing request. This ensures that the operation requested by the resource credential processing request has been authorized and confirmed by the user, thus improving the security of resource credential processing.

[0144] In one embodiment, performing business data verification and signature verification on the signed verifiable credential to obtain an operation authentication result includes: performing business data verification on the resource credential business data carried in the signed verifiable credential to obtain a business data verification result; determining the account identifier of the requesting account; the account identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; performing signature verification on the signed verifiable credential using the account attribute information associated with the account identifier in the smart contract to obtain a signature verification result; and obtaining the operation authentication result based on the business data verification result and the signature verification result.

[0145] Business data verification refers to the verification of resource credential business data in resource credential processing requests to ensure the reliability of the resource credential business data. Business data verification can include identity information verification and credential data verification. The account identifier is generated by calling a smart contract and conforms to the Distributed Digital Identity Identifier standard; that is, the account identifier can specifically be an account DID identifier. Account attribute information is used to describe the requesting account, and may include various attribute information such as account information, authorized limit information, social credit code, and public key. The account attribute information can be recorded in the DID document.

[0146] Specifically, the server can determine the resource credential business data from the signed verifiable credential and perform business data verification on it, including identity information verification and credential data verification, to obtain a business data verification result. The server can determine the account identifier of the requesting account, which can specifically be a DID identifier conforming to the Distributed Digital Identity Identifier standard. The server uses the account attribute information associated with the account identifier in the smart contract to perform signature verification on the signed verifiable credential, obtaining a signature verification result. In a specific implementation, the server can determine the account attribute information of the requesting account from the smart contract based on the account identifier, and use the public key in the account attribute information to perform signature verification on the signed verifiable credential, obtaining a signature verification result. The server combines the business data verification result and the signature verification result to obtain the operation authentication result. Specifically, if both the business data verification result and the signature verification result pass verification, the operation authentication result can be considered as successful operation verification.

[0147] In this embodiment, the server performs business data verification on the resource credential business data carried in the signed verifiable credential, and uses the account attribute information associated with the account identifier of the requesting account in the smart contract to perform signature verification on the signed verifiable credential. The operation authentication result is obtained by combining the business data verification result and the signature verification result, which can realize the effective authentication of the operation requested by the resource credential processing request, ensure that the operation requested by the resource credential processing request has been authorized and confirmed by the user, and improve the security of resource credential processing.

[0148] In one embodiment, the blockchain-based resource credential processing method further includes: determining account identity data and resource credential data from resource credential business data; verifying the account identity data and resource credential data respectively to obtain the business data verification result of the resource credential business data.

[0149] Account identity data refers to the data related to the identity of the requesting account that issued the resource credential processing request; that is, the account identity data describes the user corresponding to the requesting account. Resource credential data is the data required for resource credential processing, which may include various data such as resource credential processing limit, validity period, and holder identity binding.

[0150] Specifically, the server extracts account identity data and resource credential data from the resource credential business data. Data extraction can be performed based on specific fields to obtain account identity data and resource credential data. The server then verifies both the account identity data and resource credential data. For example, it can verify the account identity data by obtaining identity verification data, and verify the resource credential data by obtaining resource credential verification data, thus obtaining the business data verification result for the resource credential business data.

[0151] In this embodiment, the server verifies the account identity data and resource credential data in the resource credential business data respectively, which can ensure the reliability of the resource credential business data.

[0152] In one embodiment, the account identity data and resource credential data are verified separately to obtain the business data verification result of the resource credential business data. This includes: determining the account identifier to be verified associated with the account identity data; the account identifier to be verified is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; and verifying the account identity data and resource credential data separately using the account attribute information associated with the account identifier to be verified in the smart contract to obtain the business data verification result.

[0153] The account identifier to be verified is used to identify the account associated with the account identity data, and the account to be verified is associated with the user. The account identifier to be verified is generated by calling a smart contract and conforms to the Distributed Digital Identity Identifier standard, that is, the account identifier to be verified can specifically be an account DID identifier. The account attribute information is used to describe the account to be verified, and may include various attribute information such as account information, authorized limit information, social credit code, public key, etc. The account attribute information can be recorded in a DID document that conforms to the Distributed Digital Identity Identifier standard.

[0154] Specifically, the server can associate account identity data with the account to be verified and determine the account identifier to identify the account to be verified. The account identifier can be a DID identifier that conforms to the Digital Identity Identifier standard. The server verifies the account identity data and resource credential data through the account attribute information associated with the account identifier in the smart contract, and obtains the business data verification result. In specific implementations, the account attribute information may include the user's identity information and the authorization information of the resource credential associated with the account to be verified. The verification of account identity data and resource credential data can be achieved through the account attribute information.

[0155] In this embodiment, the server uses the account attribute information associated with the account identifier to be verified in the smart contract to verify the account identity data and resource credential data, which can ensure the reliability of the resource credential business data.

[0156] This application also provides an application scenario in which the aforementioned blockchain-based resource certificate processing method is applied, wherein the resource certificate is an electronic debt certificate. Specifically, the application of the blockchain-based resource certificate processing method in this scenario is as follows:

[0157] In the supply chain finance industry, the digital transformation of financial credit between core enterprises and suppliers is typically achieved through the multi-level splitting and circulation of electronic debt certificates. Traditional electronic debt certificates, implemented through centralized services, are susceptible to security risks such as data tampering and service attacks, significantly challenging their authority and credibility. Blockchain, with its decentralized and tamper-proof security features, can largely solve the trust issues among participating entities by using blockchain as an information exchange infrastructure for electronic debt certificates. However, current blockchain-based solutions for electronic debt certificates are usually based on private protocols for specific business scenarios, lacking ecosystem openness and incurring high implementation costs.

[0158] Based on this, this embodiment proposes a blockchain-based resource certificate processing method that can be applied to electronic debt certificates. Using distributed digital identity identifiers (DIDs) as the application infrastructure, it realizes the entire lifecycle of electronic debt certificate circulation and can serve as a general implementation for blockchain electronic debt certificate services. A distributed digital identity identifier (DID) is a new type of identifier composed of strings. Digital identity is represented by the identity identifier and its associated attribute declarations. The specification of distributed identity includes two parts: the distributed digital identity identifier and the verifiable digital identity certificate. Blockchain electronic debt certificate services based on the DID protocol have high protocol readability and data expression capabilities, and possess interoperability with the DID protocol. They also have significant advantages in traceability and supervision, and can be used as a standardized technical prototype applied to debt certificate scenarios in different supply chain finance industries.

[0159] Specifically, in the application scenarios of electronic debt instruments, such as Figure 4 As shown, a core enterprise can obtain a certain amount of financing credit from a funding party, such as a bank, thus acquiring a certain debt credit line. Due to business needs, the core enterprise can issue debt instruments to its primary suppliers, with the amount within the core enterprise's financing credit line. Suppliers can then use these instruments to obtain financing from funding parties. For example, a certain amount of debt instruments can be issued to primary supplier A and primary supplier B respectively. Primary suppliers, due to business needs, can issue debt instruments to secondary suppliers, with the amount within the primary supplier's existing financing credit line. The credit line will deduct the corresponding amount from the amount of the instruments held by the secondary supplier, allowing the secondary supplier to obtain financing from funding parties. For instance, primary supplier B can issue debt instruments to secondary suppliers A and B respectively, thereby transferring the debt instruments. The operator or regulator can monitor the flow of debt instruments according to business needs and may intervene, such as terminating certain instruments.

[0160] The core process of debt instruments is the transfer process. In the field of supply chain finance, the transfer process is usually achieved through order splitting, which generally has two modes. For example... Figure 5 As shown, in splitting pattern A, the parent debt instrument (or higher-level debt instrument) has its amount deducted and transferred to the newly created sub-debt instruments. Specifically, for the parent debt instrument with an amount of X, the remaining amount after splitting is XY, the amount of the split sub-debt instruments is YZ, and the amount of the sub-sub-debt instruments after splitting the sub-debt instruments is Z. In splitting pattern B, the parent debt instrument terminates, and its amount is split into two newly created sub-debt instruments. For example... Figure 6 As shown, the amount of the parent debt instrument is X. After splitting, the parent debt instrument terminates, while the amount of sub-debt instrument 1 is XY and the amount of sub-debt instrument 2 is Y. Sub-debt instrument 2 is further split, and sub-debt instrument 2 terminates, resulting in sub-sub-debt instrument 1 with an amount of X and sub-sub-debt instrument 2 with an amount of YZ.

[0161] Taking splitting mode A as an example, this embodiment proposes a blockchain-based resource certificate processing method. The splitting process of the debt certificate implemented based on blockchain can be completed in a smart contract. The smart contract stores the credit amount of the parent debt certificate and deducts the amount of the parent debt certificate during splitting, with the corresponding amount transferred to the new sub-debt certificate. Figure 7 As shown, the supply chain platform provides a user interface to realize the circulation and processing of debt instruments through smart contracts for debt instruments deployed in the blockchain network. Figure 8As shown, the certificate server, through the debt certificate application module, provides the supply chain platform with interfaces for certificate circulation, data query, operation, and supervision. The debt certificate application module can read and write the status data of the debt certificate contract, thereby achieving data updates. The debt certificate contract implements the contract interface for the entire lifecycle of the debt certificate circulation. The supply chain platform or debt certificate holders complete the certificate circulation operation by calling the debt certificate smart contract or the debt certificate application. Typically, blockchain networks are asymmetric technologies, such as account systems implemented using public / private keys or certificates. When users or certificate holders directly access the blockchain network to call smart contracts, they need to sign the data with their private key. However, when users call smart contracts through the supply chain platform, to solve the credibility issue, the data needs to be signed by the user. The specific signing rules can be customized by the user, and the supply chain platform uploads the data to the blockchain through a proxy model.

[0162] Traditional blockchain-based debt certificate solutions lack a protocol layer, resulting in a lack of universality and scalability. Furthermore, the use of blockchain's native account system by users, enterprises, regulators, and operators lacks a unified identity system, leading to weak user identification and management capabilities and hindering regulatory oversight and data traceability. Additionally, the use of private protocols for user identity, signature formats, and certificate representation results in a lack of interoperability and hinders data exchange across contracts and chains, as well as certificate identification and verification across different business scenarios. Moreover, because the information representation of debt certificates and user accounts is customized by the supply chain finance platform, the data representation lacks comprehensive coordination, often resulting in insufficient data representation for users and certificates and weak information transmission capabilities. The blockchain-based resource certificate processing method provided in this embodiment does not require the definition of a private protocol. It uses the DID protocol itself to realize the user identity and certificate circulation of debt certificates, as well as data expression. It not only has protocol interoperability, which facilitates implementation in cross-contract and cross-chain scenarios, and the interoperability of certificates in different businesses, but also achieves the standardization and universality of the debt certificate blockchain solution. Moreover, by realizing identity management and object-oriented management of certificate data through the DID protocol, it has higher reliability, security, and traceability, and can expand regulatory functions according to business scenarios, making it more suitable for consortium blockchain scenarios.

[0163] Specifically, the blockchain-based resource credential processing method provided in this embodiment, such as... Figure 9As shown, in terms of protocols, the debt certificate service is carried on top of the DID protocol. Through the interoperability of the DID protocol layer, data exchange can be achieved between different lower-level blockchain networks and different upper-level debt certificate services. For example, for debt certificate application A on blockchain network A and debt certificate application B on blockchain network B, application A and application B can exchange certificate data. Their respective DID protocol layers can also communicate via DID and VC, thereby enabling cross-chain data exchange between blockchain network A and blockchain network B.

[0164] Furthermore, the implementation of debt instruments based on DID primarily involves entity DID abstraction and VC operation authentication in the protocol design. For entity DID abstraction, all participating entities and objects in the debt instrument business process are abstracted into DID identifiers, including identity entities such as the core enterprise, suppliers, operators, and funding parties, and the debt instrument entity, i.e., each debt instrument is represented by a unique DID identifier. According to the DID protocol specification, the DID identifier serves as a digital symbol for the entity. The DID identifier is used to parse the DID document containing the public attributes of each entity, detailing the entity's attribute data such as the core enterprise's name and the amount of the debt instrument. For VC operation authentication, during the debt instrument circulation process, such as issuance and transfer, operation authentication is required for the instrument holder. This authentication is achieved through the issuance and verification of VCs according to the DID specification. The VC's claim statement contains parameter data for the transfer of the debt certificate. Since the VC is signed by the certificate holder's private key, the validity of the VC's signature can be verified by the public key published on the holder's DID document. Only user operations that have been verified by the VC can trigger the transfer of the debt certificate's status, ensuring the credibility and security of the certificate holder.

[0165] The design of the DID identifier for a debt instrument can be in the following format:

[0166] did:tdid:cm772g1:0x86575ef232476a772b90c608279c68a1faea2bd8

[0167] In this structure, tdid is the DID platform provider's custom registration on W3C, and cm772g1 is the chain ID, used for routing access across different blockchain networks. For example, in consortium blockchain scenarios, it can be used in conjunction with a Blockchain as a Service (BaaS) platform; this ID can be assigned by the BaaS. The final part is a unique identifier assigned by the DID platform, which can specifically be a public key converted address identifier. In accordance with the DID protocol specification, the key attribute information in the DID document of a debt certificate is not limited to the definitions in Table 1 below.

[0168] Table 1

[0169]

[0170] In a specific implementation, a portion of the field content extracted from the debt certificate DID document can be shown as follows:

[0171] {……

[0172] "tokenID":"l", / / Token ID of the certificate

[0173] "created":"2022-o8-01T13:45:29+000o", / / Creation time

[0174] "frozenAmount":"100", / / Frozen amount

[0175] "bil1Amount":"12345600", / / Total amount of the voucher

[0176] "controller":

[0177] "did:tdid:cm772gl:0x89cbe77e0b5465d86b2fbd2d55fc618d452ffb3b", / / Holder's ID

[0178] ...}

[0179] Furthermore, in the implementation of DID-based electronic debt instruments, such as Figure 10 As shown, the electronic debt instrument circulation system includes a DID platform and a certificate server, both implemented based on a blockchain network. The certificate server includes a debt instrument application module and a debt instrument contract module; the DID platform includes a DID application service module and a DID smart contract module. In the application of electronic debt instruments, users can access the debt instrument application module through the supply chain platform to generate DIDs and VCs, triggering certificate circulation and VC input operations. The debt instrument application module can call the DID application service module through the DID application layer interface. The DID application service module can perform DID status data read and write operations on the DID smart contract module. The debt instrument application module can also read and write certificate status data on the debt instrument contract module, and the debt instrument contract module can also read DID status data on the DID smart contract module.

[0180] Specifically, the Distributed Identity Platform (DID) is a standard infrastructure platform consisting of a DID application service module and a DID smart contract module, but it is not limited to pure contract implementation. The DID application service module provides API (Application Programming Interface) level application interfaces, including registering and querying the DID identifiers and DID documents of entities participating in debt instruments, generating the original authentication VC text and VC signature verification for the debt instrument process, etc. The DID smart contract module stores the DID's state data, including the DID identifier and bound public key information such as the core enterprise's public key, and associated entity attribute information such as the amount of the debt instrument.

[0181] The certificate server consists of a debt certificate application service module and a debt certificate smart contract module. It implements service components for common debt certificate scenarios, but is not limited to pure contract implementations. The debt certificate application service module provides the upper-layer supply chain platform with user identity registration and role management in debt certificate scenarios (achieved by calling the DID service interface) and standard interfaces for the entire lifecycle of debt certificate circulation, such as order opening, order splitting, and termination. In scenarios requiring operational and regulatory needs, the debt certificate application can provide relevant regulatory interfaces to offer management and operation functions for debt certificates. However, operators and regulators also need to register their identities on the DID platform and be certified as authoritative institutions, publicly disclosing their regulatory identity DID identifier. The debt certificate contract module stores the binding relationship between the certificate DID identifier and the user identity identifier. It verifies the user identity and key data of the debt certificate, such as the certificate amount, by reading the DID document of the DID contract. During the circulation of debt certificates, it modifies the certificate amount and other related data information in the certificate's DID document. In scenarios requiring higher credibility, the debt certificate contract can implement verification by the VC (Voucher Authentication Center). Only after successful verification can the debt certificate status be transferred.

[0182] Furthermore, such as Figure 11As shown, for the processing of debt instrument issuance, the core enterprise can trigger the issuance through the supply chain platform. The document service module in the document server verifies the identity and document data. After successful verification, it generates DID data for the parent debt instrument based on the DID platform. This includes the DID identifier of the parent debt instrument and the associated DID document. The DID document stores the metadata of the parent debt instrument, specifically describing its attribute information. The metadata includes key information about the debt instrument, such as its status (in progress, closed, etc.), amount, frozen amount, and token ID assigned by the document contract. The token ID is used to bind to the document DID identifier. The document service module generates a verifiable issuance document, i.e., generates the original document (VC) of the issuance document, and sends it to the supply chain platform for user signature confirmation to trigger the issuance process. The document contract module in the document server performs identity verification, amount check, and document signature verification. After successful verification, a document token is generated, which can be bound to the document identifier, specifically the DID identifier. The voucher contract module can update voucher metadata and token identifiers based on the DID platform and return the order results to the supply chain platform.

[0183] Furthermore, such as Figure 12 As shown, for the processing of splitting debt instruments, users can trigger the splitting through the supply chain platform, i.e., triggering the transfer of instruments. The instrument service module in the instrument server verifies the identity and instrument data. After successful verification, it generates DID data for the split sub-debt instruments based on the DID platform, including the DID identifier of the sub-debt instrument and the associated DID document. The DID document stores the metadata of the sub-debt instrument, specifically describing its attribute information. The instrument service module generates a splitting verifiable voucher, i.e., generates the original splitting voucher VC, and sends it to the supply chain platform for user signature confirmation to trigger the splitting process. Since the splitting requires recipient confirmation to take effect, the splitting amount is frozen before confirmation. If there is a new splitting request, the frozen amount cannot be used for splitting, but the remaining amount can still be split in parallel. The instrument contract module in the instrument server performs identity verification, amount checking, and instrument signature verification. After successful verification, the splitting amount is frozen, and a receiving confirmation verifiable voucher is returned to the supply chain platform for confirmation and signature by the sub-debt instrument holder, and a receiving confirmation result is returned. If the confirmation result indicates acceptance of the split, the voucher service module checks the metadata of the sub-debt certificate based on the DID platform, generates a voucher token, and then binds the voucher token to the voucher identifier, specifically the DID identifier. The voucher contract module can update the voucher metadata and token identifier based on the DID platform and return the splitting result to the supply chain platform.

[0184] Furthermore, such as Figure 13As shown, for the processing of debt instrument settlement, users can trigger settlement through the supply chain platform. The voucher service module in the voucher server verifies identity and voucher data. After successful verification, the voucher service module generates a verifiable settlement voucher, i.e., generates the original settlement voucher VC, and sends the verifiable settlement voucher to the supply chain platform for user signature confirmation to trigger settlement processing. The voucher contract module in the voucher server performs identity verification, amount check, and voucher signature verification. After successful verification, the voucher token and voucher identifier are unbound, specifically the DID identifier. The voucher contract module can update the voucher status based on the DID platform and return the settlement result to the supply chain platform.

[0185] This embodiment provides a blockchain-based resource certificate processing method that, by combining with a DID distributed identity platform, achieves a standardized solution for blockchain-based electronic debt certificates. This gives debt certificates and user identities the excellent readability and expressive power of DID protocols, along with good scalability, universality, and ease of engineering implementation. The resource certificate processing method is implemented based on the W3C DID specification, exhibiting significant advantages in protocol interoperability and interoperability. It not only provides application-layer protocol support for cross-contract and application-level cross-chain scenarios but can also be extended to data exchange and rights confirmation scenarios for debt certificates in different business areas. Furthermore, the debt certificate circulation operation authentication provided in this embodiment includes a user-signed VC stub, facilitating users to present proof of rights and regulatory operations. Simultaneously, through the parent certificate identifier in the debt certificate DID document, the certificate has a hierarchical upward verification function, improving the reliability, credibility, and authority of certificate verification. This hierarchical backtracking verification mode is beneficial for compliance management with consortium blockchain characteristics, such as regulatory auditing and backtracking management.

[0186] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0187] Based on the same inventive concept, this application also provides a blockchain-based resource certificate processing device for implementing the blockchain-based resource certificate processing method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more embodiments of the blockchain-based resource certificate processing device provided below can be found in the limitations of the blockchain-based resource certificate processing method described above, and will not be repeated here.

[0188] In one embodiment, such as Figure 14 As shown, a blockchain-based resource credential processing device 1400 is provided, including: a request acquisition module 1402, a verifiable credential generation module 1404, an operation authentication processing module 1406, an update data acquisition module 1408, and an attribute information update module 1410, wherein:

[0189] The request acquisition module 1402 is used to acquire resource certificate processing requests carrying resource certificate business data.

[0190] The verifiable credential generation module 1404 is used to generate verifiable credentials that conform to the distributed digital identity identifier standard based on the resource credential business data when the resource credential business data passes the business data verification.

[0191] The operation authentication processing module 1406 is used to perform operation authentication on the operation requested by the resource certificate processing request based on verifiable credentials, and obtain the operation authentication result.

[0192] The update data acquisition module 1408 is used to process the target resource certificate for the resource certificate processing request and obtain the update data when the operation authentication result indicates that the operation verification is successful, based on the resource certificate business data.

[0193] The attribute information update module 1410 is used to call the smart contract in the blockchain to update the attribute information of the resource certificate that describes the target resource certificate and conforms to the distributed digital identity identifier standard by updating the data.

[0194] In one embodiment, the resource credential processing request includes an invoice request; the verifiable credential generation module 1404 is further configured to determine the resource credential invoicing data of the target resource credential targeted by the invoice request from the resource credential business data; generate a resource credential identifier of the target resource credential and an attribute document associated with the resource credential identifier based on the resource credential invoicing data according to the Distributed Digital Identity Identifier standard; and generate a verifiable credential based on the resource credential identifier, the attribute document, and the resource credential business data according to the Distributed Digital Identity Identifier standard.

[0195] In one embodiment, the verifiable credential generation module 1404 is further configured to determine the invoice verification data for the invoice request from the resource credential business data; and generate a verifiable credential based on the resource credential identifier, attribute document and invoice verification data in accordance with the distributed digital identity identifier standard.

[0196] In one embodiment, the update data acquisition module 1408 is further configured to perform resource allocation processing on the target resource certificate based on the resource certificate business data to obtain the order update data of the target resource certificate; the attribute information update module 1410 is further configured to call the smart contract in the blockchain to update the attribute document in the smart contract through the order update data; wherein, the attribute document conforms to the distributed digital identity identifier standard, and the attribute document includes resource certificate attribute information describing the target resource certificate.

[0197] In one embodiment, the resource credential processing request includes a splitting request; the target resource credential for the splitting request includes a parent resource credential and a sub-resource credential formed by splitting the parent resource credential; the verifiable credential generation module 1404 is further configured to determine the resource credential splitting data of the parent resource credential from the resource credential business data; generate a sub-resource credential identifier of the sub-resource credential and an attribute document associated with the sub-resource credential identifier based on the resource credential splitting data according to the Distributed Digital Identity Identifier standard; and generate a verifiable credential based on the sub-resource credential identifier, the attribute document, and the resource credential business data according to the Distributed Digital Identity Identifier standard.

[0198] In one embodiment, the verifiable credential generation module 1404 is further configured to determine the splitting verification data for the splitting request from the resource credential business data; and generate a verifiable credential based on the sub-resource credential identifier, attribute document, and splitting verification data in accordance with the distributed digital identity identifier standard.

[0199] In one embodiment, the update data acquisition module 1408 is further configured to perform resource splitting processing on the parent resource certificate and the child resource certificate based on the resource certificate business data, to obtain the split update data associated with the parent resource certificate and the child resource certificate; the attribute information update module 1410 is further configured to call the smart contract in the blockchain, and update the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier in the smart contract respectively through the split update data; wherein, the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier conform to the distributed digital identity identifier standard; the attribute document associated with the parent resource certificate identifier includes resource certificate attribute information describing the parent resource certificate, and the attribute document associated with the child resource certificate identifier includes resource certificate attribute information describing the child resource certificate.

[0200] In one embodiment, a resource freezing module is further included, which is used to call a smart contract in the blockchain to freeze the parent resource certificate when the operation authentication result indicates that the operation verification is successful; call the smart contract to generate a holder-verifiable certificate for the sub-resource certificate based on the sub-resource certificate identifier and resource certificate business data according to the distributed digital identity identifier standard; send the holder-verifiable certificate to the holder of the sub-resource certificate; the holder-verifiable certificate is used to instruct the holder to confirm the split order based on the holder-verifiable certificate, and return the split order confirmation result; when the split order confirmation result indicates acceptance of the split order, the resource freezing of the parent resource certificate is lifted, and the step of processing the target resource certificate targeted by the resource certificate processing request according to the resource certificate business data to obtain updated data is executed.

[0201] In one embodiment, the resource credential processing request includes at least one of an order creation request or an order splitting request; it also includes a credential token binding module for generating a resource credential token for the target resource credential targeted by the resource credential processing request; establishing a binding relationship between the resource credential token and the resource credential identifier of the target resource credential; the resource credential identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; and the smart contract is called to update the binding relationship to the resource credential attribute information.

[0202] In one embodiment, the resource credential processing request includes a settlement request; the verifiable credential generation module 1404 is further configured to determine, from the resource credential business data, the resource credential identifier of the target resource credential for which the settlement request is directed, and the settlement verification data for the settlement request; and generate a verifiable credential based on the resource credential identifier and the settlement verification data in accordance with the Distributed Digital Identity Identifier standard.

[0203] In one embodiment, the update data acquisition module 1408 is further configured to perform resource certificate termination processing on the target resource certificate based on the resource certificate business data, and obtain the settlement update data of the target resource certificate; the attribute information update module 1410 is further configured to call the smart contract in the blockchain, and update the attribute document associated with the resource certificate identifier in the smart contract through the settlement update data; wherein, the attribute document conforms to the distributed digital identity identifier standard, and the attribute document includes resource certificate attribute information describing the target resource certificate.

[0204] In one embodiment, the resource credential processing request includes a settlement request; it also includes a token unbinding module, used to determine the resource credential token of the target resource credential for which the resource credential processing request is directed; to unbind the binding relationship between the resource credential token and the resource credential identifier of the target resource credential; the resource credential identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; and to call the smart contract to update the unbinding information in the resource credential attribute information.

[0205] In one embodiment, the operation authentication processing module 1406 is further configured to send a verifiable credential to the request triggering end that issued the resource credential processing request; the verifiable credential is used to instruct the requesting account of the request triggering end to sign the verifiable credential and return the signed verifiable credential; and to perform business data verification and signature verification on the signed verifiable credential to obtain the operation authentication result.

[0206] In one embodiment, the operation authentication processing module 1406 is further configured to perform business data verification on the resource certificate business data carried in the signed verifiable credential to obtain a business data verification result; determine the account identifier of the requesting account; the account identifier is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; perform signature verification on the signed verifiable credential using the account attribute information associated with the account identifier in the smart contract to obtain a signature verification result; and obtain the operation authentication result based on the business data verification result and the signature verification result.

[0207] In one embodiment, the system further includes a business data verification module, which is used to determine account identity data and resource credential data from resource credential business data; and to verify the account identity data and resource credential data respectively to obtain the business data verification result of the resource credential business data.

[0208] In one embodiment, the business data verification module is further used to determine the account identifier to be verified associated with the account identity data; the account identifier to be verified is generated by calling a smart contract and conforms to the distributed digital identity identifier standard; the account identity data and resource credential data are verified respectively through the account attribute information associated with the account identifier to be verified in the smart contract to obtain the business data verification result.

[0209] Each module in the aforementioned blockchain-based resource certificate processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can invoke and execute the corresponding operations of each module.

[0210] In one embodiment, a computer device is provided, which may be a server or a terminal, and its internal structure diagram may be as follows: Figure 14As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores smart contract data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network. When executed by the processor, the computer program implements a blockchain-based resource credential processing method.

[0211] Those skilled in the art will understand that Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0212] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0213] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0214] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0215] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0216] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0217] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0218] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A resource certificate processing method based on blockchain, characterized in that, The method includes: Obtain a resource certificate processing request carrying business data related to resource certificates; When the resource credential business data passes the business data verification, a verifiable credential conforming to the distributed digital identity identifier standard is generated based on the resource credential business data. Based on the verifiable credential, the operation requested by the resource credential processing request is authenticated to obtain the operation authentication result, including: sending the verifiable credential to the requesting party that issued the resource credential processing request, and having the requesting party sign the verifiable credential to obtain the operation authentication result. When the operation authentication result indicates that the operation verification is successful, the target resource certificate targeted by the resource certificate processing request is processed according to the resource certificate business data to obtain updated data, including: performing resource splitting processing on the parent resource certificate and the child resource certificate according to the resource certificate business data to obtain split update data associated with the parent resource certificate and the child resource certificate, wherein the parent resource certificate is the resource certificate that the split request needs to split, the resource certificate processing request includes the split request, and the child resource certificate is the resource certificate obtained by splitting the parent resource certificate; Invoking a smart contract in the blockchain to update the resource certificate attribute information describing the target resource certificate and conforming to the distributed digital identity identifier standard through the update data includes: invoking a smart contract in the blockchain to update the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier in the smart contract through the split update data; wherein the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier conform to the distributed digital identity identifier standard; the attribute document associated with the parent resource certificate identifier includes resource certificate attribute information describing the parent resource certificate, and the attribute document associated with the child resource certificate identifier includes resource certificate attribute information describing the child resource certificate.

2. The method according to claim 1, characterized in that, The resource credential processing request includes an invoice request; the step of generating a verifiable credential conforming to the distributed digital identity identifier standard based on the resource credential business data includes: From the resource certificate business data, determine the resource certificate ordering data of the target resource certificate for which the ordering request is directed; According to the Distributed Digital Identity Identifier standard, based on the resource credential invoicing data, a resource credential identifier for the target resource credential and an attribute document associated with the resource credential identifier are generated. According to the distributed digital identity identifier standard, a verifiable credential is generated based on the resource credential identifier, the attribute document, and the resource credential business data.

3. The method according to claim 2, characterized in that, The step of generating a verifiable credential based on the resource credential identifier, the attribute document, and the resource credential business data, according to the distributed digital identity identifier standard, includes: Determine the order verification data for the order request from the resource certificate business data; According to the distributed digital identity identifier standard, a verifiable credential is generated based on the resource credential identifier, the attribute document, and the invoice verification data.

4. The method according to claim 2, characterized in that, The step of processing the target resource credential for the resource credential processing request based on the resource credential business data to obtain updated data includes: Based on the resource certificate business data, resource allocation processing is performed on the target resource certificate to obtain the order update data of the target resource certificate; The invocation of a smart contract in the blockchain, through the update data, updates the attribute information of the resource credential describing the target resource credential and conforming to the distributed digital identity identifier standard, including: The smart contract in the blockchain is invoked to update the attribute document in the smart contract through the order update data; The attribute document conforms to the distributed digital identity identifier standard, and the attribute document includes resource credential attribute information describing the target resource credential.

5. The method according to claim 1, characterized in that, The resource certificate processing request includes a splitting request; the target resource certificate for the splitting request includes a parent resource certificate and a sub-resource certificate formed by splitting the parent resource certificate. The step of generating a verifiable credential conforming to the distributed digital identity identifier standard based on the resource credential business data includes: From the resource certificate business data, determine the resource certificate splitting data of the parent resource certificate; According to the Distributed Digital Identity Identifier standard, based on the resource credential splitting data, a sub-resource credential identifier and an attribute document associated with the sub-resource credential identifier are generated for the sub-resource credential. According to the distributed digital identity identifier standard, a verifiable credential is generated based on the sub-resource credential identifier, the attribute document, and the resource credential business data.

6. The method according to claim 5, characterized in that, The step of generating a verifiable credential according to the distributed digital identity identifier standard, based on the sub-resource credential identifier, the attribute document, and the resource credential business data, includes: Determine the split verification data for the split request from the resource certificate business data; According to the distributed digital identity identifier standard, a verifiable credential is generated based on the sub-resource credential identifier, the attribute document, and the split verification data.

7. The method according to claim 5, characterized in that, The method further includes: When the operation authentication result indicates that the operation verification is successful, the smart contract in the blockchain is invoked to split and freeze the parent resource certificate; The smart contract is invoked to generate a verifiable credential for the holder of the sub-resource credential, based on the sub-resource credential identifier and the resource credential business data, according to the distributed digital identity identifier standard. Send the holder's verifiable credential to the holder of the sub-resource credential; the holder's verifiable credential is used to instruct the holder to perform order split confirmation based on the holder's verifiable credential, and return the order split confirmation result; When the order split confirmation result indicates acceptance of the order split, the freeze on the split resource of the parent resource certificate is lifted, and the step of processing the target resource certificate of the resource certificate processing request based on the resource certificate business data to obtain updated data is executed.

8. The method according to claim 1, characterized in that, The resource certificate processing request includes at least one of an order creation request or an order splitting request; the method further includes: Generate a resource credential token for the target resource credential targeted by the resource credential processing request; Establish a binding relationship between the resource credential token and the resource credential identifier of the target resource credential; the resource credential identifier is generated by calling the smart contract and conforms to the distributed digital identity identifier standard; The smart contract is invoked to update the binding relationship in the resource credential attribute information.

9. The method according to claim 1, characterized in that, The resource credential processing request includes a settlement request; the step of generating a verifiable credential conforming to the distributed digital identity identifier standard based on the resource credential business data includes: From the resource credential business data, determine the resource credential identifier of the target resource credential for the settlement request, and the settlement verification data for the settlement request; According to the distributed digital identity identifier standard, a verifiable credential is generated based on the resource credential identifier and the settlement verification data.

10. The method according to claim 9, characterized in that, The step of processing the target resource credential for the resource credential processing request based on the resource credential business data to obtain updated data includes: Based on the resource certificate business data, resource certificate termination processing is performed on the target resource certificate to obtain the settlement update data of the target resource certificate; The invocation of a smart contract in the blockchain, through the update data, updates the attribute information of the resource credential describing the target resource credential and conforming to the distributed digital identity identifier standard, including: The smart contract in the blockchain is invoked to update the attribute document associated with the resource certificate identifier in the smart contract through the settlement update data; The attribute document conforms to the distributed digital identity identifier standard, and the attribute document includes resource credential attribute information describing the target resource credential.

11. The method according to claim 1, characterized in that, The resource credential processing request includes a settlement request; the method further includes: The resource credential token of the target resource credential for which the resource credential processing request is directed is determined; The binding relationship between the resource credential token and the resource credential identifier of the target resource credential is released; the resource credential identifier is generated by calling the smart contract and conforms to the distributed digital identity identifier standard; The smart contract is invoked to update the information on the removal of the binding relationship into the resource credential attribute information.

12. The method according to claim 1, characterized in that, The step of performing operation authentication on the operation requested by the resource credential processing request based on the verifiable credential, and obtaining the operation authentication result, includes: The verifiable credential is sent to the request triggering end that issued the resource credential processing request; the verifiable credential is used to instruct the request account of the request triggering end to sign the verifiable credential and return the signed verifiable credential. The signed verifiable credential is subjected to business data verification and signature verification to obtain the operation authentication result.

13. The method according to claim 12, characterized in that, The step of performing business data verification and signature verification on the signed verifiable credential to obtain the operation authentication result includes: The business data of the resource certificate carried in the signed verifiable certificate is verified to obtain the business data verification result. The account identifier of the requesting account is determined; the account identifier is generated by calling the smart contract and conforms to the distributed digital identity identifier standard; The signature verification result is obtained by using the account attribute information associated with the account identifier in the smart contract to verify the signature of the verifiable credential. Based on the business data verification result and the signature verification result, the operation authentication result is obtained.

14. The method according to any one of claims 1 to 13, characterized in that, The method further includes: Determine account identity data and resource credential data from the resource credential business data; The account identity data and the resource credential data are verified separately to obtain the business data verification result of the resource credential business data.

15. The method according to claim 14, characterized in that, The step of verifying the account identity data and the resource credential data respectively to obtain the business data verification result of the resource credential business data includes: Determine the account identifier to be verified associated with the account identity data; the account identifier to be verified is generated by calling the smart contract and conforms to the distributed digital identity identifier standard; By using the account attribute information associated with the account identifier to be verified in the smart contract, the account identity data and the resource credential data are verified respectively to obtain the business data verification result.

16. A resource certificate processing device based on blockchain, characterized in that, The device includes: The request acquisition module is used to acquire resource credential processing requests that carry resource credential business data. The verifiable credential generation module is used to generate a verifiable credential that conforms to the distributed digital identity identifier standard based on the resource credential business data when the resource credential business data passes the business data verification. The operation authentication processing module is used to perform operation authentication on the operation requested by the resource credential processing request based on the verifiable credential and obtain the operation authentication result. The module includes: sending the verifiable credential to the requesting party that issued the resource credential processing request, and having the requesting party sign the verifiable credential to obtain the operation authentication result. The update data acquisition module is used to process the target resource certificate targeted by the resource certificate processing request to obtain update data when the operation authentication result indicates that the operation verification is successful, based on the resource certificate business data. This includes: performing resource splitting processing on the parent resource certificate and the child resource certificate based on the resource certificate business data to obtain split update data associated with the parent resource certificate and the child resource certificate. The parent resource certificate is the resource certificate that the split request needs to split, the resource certificate processing request includes the split request, and the child resource certificate is the resource certificate obtained by splitting the parent resource certificate. The attribute information update module is used to invoke a smart contract in the blockchain to update the attribute information of the resource certificate that describes the target resource certificate and conforms to the distributed digital identity identifier standard through the update data. This includes: invoking the smart contract in the blockchain and updating the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier in the smart contract through the split update data; wherein the attribute document associated with the parent resource certificate identifier and the attribute document associated with the child resource certificate identifier conform to the distributed digital identity identifier standard; the attribute document associated with the parent resource certificate identifier includes resource certificate attribute information describing the parent resource certificate, and the attribute document associated with the child resource certificate identifier includes resource certificate attribute information describing the child resource certificate.

17. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 15.

18. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

Images