Data processing method and device, equipment and storage medium
By using the universal parsing container parsing component of the universal identifier management platform, the problem of parsing complexity caused by the differences in DID protocols among different service organizations is solved, and efficient and secure digital identifier parsing is achieved.
Patent Information
- Application Number
- CN202410939377.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-12
- Publication Date
- 2026-01-13
AI Technical Summary
The differences between DID protocols used by different service providers make the resolution process of digital identifiers more complex, requiring the creation of dedicated code modules for each service provider, which increases the workload of business equipment.
By adopting a universal identifier management platform, digital identifier resolution is performed by querying the resolution components in the universal resolution container associated with the target service provider. This reduces the need for business devices to connect to the service provider's resolution components and lowers the resolution complexity.
It reduces the complexity of parsing digital identifiers, improves information security, prevents the unauthorized acquisition of identifier document information, and enhances parsing efficiency and security.
Smart Images

Figure CN121326481A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, device, and storage medium. Background Technology
[0002] As the concept of decentralized digital identity gains attention from users (i.e., business entities), blockchain-based digital identification technology is being widely applied. More and more service providers are implementing their own DID protocols based on the World Wide Web Consortium (W3C) definition and standards for decentralized identifiers (DIDs). These protocols enable the creation and resolution of digital identifiers for users, greatly facilitating the development of application scenarios using decentralized digital identity technology.
[0003] During implementation, it was found that different business objects can choose different service providers to create digital identifiers, and the DID protocols of different service providers differ. Therefore, in the process of parsing the digital identifiers of business objects, a dedicated code module needs to be created for each service provider to interface with the corresponding service provider's parsing component. This process of parsing the digital identifiers through the parsing component introduces inconvenience and results in high complexity for digital identifier parsing. Summary of the Invention
[0004] This application provides a data processing method, apparatus, device, and storage medium that can reduce the complexity of parsing digital identifiers.
[0005] One embodiment of this application provides a data processing method, including:
[0006] The request receiving interface of the general identifier management platform is invoked to receive the parsing request for the digital identifier of the business device; the digital identifier includes the organizational information of the target service organization that generated the digital identifier.
[0007] Based on the above-mentioned organizational information, query the general parsing container associated with the target service organization from the container cluster of the above-mentioned general identifier management platform; the container cluster includes general parsing containers associated with multiple service organizations respectively, the target service organization is any one of the multiple service organizations, and each general parsing container runs the parsing component provided by the corresponding service organization;
[0008] The parsing component running in the general parsing container associated with the aforementioned target service provider parses the digital identifier of the aforementioned business device to obtain the encrypted identifier document corresponding to the digital identifier of the aforementioned business device.
[0009] The encrypted identifier document corresponding to the digital identifier of the aforementioned business device is sent to the aforementioned business device; the aforementioned business device is used to decrypt the aforementioned encrypted identifier document to obtain the identifier document corresponding to the digital identifier of the aforementioned business device.
[0010] One embodiment of this application provides a data processing apparatus, including:
[0011] The receiving module is used to call the request receiving interface of the general identifier management platform to receive the parsing request for the digital identifier of the business device; the digital identifier includes the organizational information of the target service organization that generated the digital identifier;
[0012] The query module is used to query the general parsing container associated with the target service organization from the container cluster of the general identifier management platform based on the above-mentioned organization information. The container cluster includes general parsing containers associated with multiple service organizations respectively. The target service organization is any one of the multiple service organizations. Each general parsing container runs a parsing component provided by the corresponding service organization.
[0013] The processing module is used to parse the digital identifier of the aforementioned business device through the parsing component running in the general parsing container associated with the aforementioned target service provider, and obtain the encrypted identifier document corresponding to the digital identifier of the aforementioned business device.
[0014] The sending module is used to send the encrypted identifier document corresponding to the digital identifier of the aforementioned business device to the aforementioned business device; the aforementioned business device is used to decrypt the encrypted identifier document to obtain the identifier document corresponding to the digital identifier of the aforementioned business device.
[0015] One aspect of this application provides a computer device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of the method described above.
[0016] One embodiment of this application provides a computer storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described method.
[0017] One aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described method.
[0018] This application provides a universal identifier management platform, which includes a container cluster. Within the container cluster are multiple universal parsing containers associated with different service providers. Each universal parsing container runs a parsing component provided by the corresponding service provider. Therefore, when a parsing request for a digital identifier of a business device is received, based on the organization information of the target service provider in the digital identifier, the platform can query the universal parsing container associated with the target service provider from the container cluster. The parsing component running in the found universal parsing container is then used to parse the digital identifier of the business device. This eliminates the need for the business device to implement additional code modules to interface with the service provider's parsing component, reducing the parsing workload and complexity of the digital identifier. The universal identifier management platform can only parse the encrypted identifier document corresponding to the digital identifier, thus preventing the unauthorized acquisition of information in the identifier document and improving the information security of the identifier document. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.
[0020] Figure 1 This is a schematic diagram of the structure of a blockchain data processing system provided in this application;
[0021] Figure 2 This is a schematic diagram of the structure of a data processing system provided in this application;
[0022] Figure 3 This is a flowchart illustrating a data processing method provided in this application;
[0023] Figure 4 This is a flowchart illustrating yet another data processing method provided in this application;
[0024] Figure 5 This is a flowchart illustrating a registration process for a digital identifier provided in this application;
[0025] Figure 6 This is a schematic diagram of the structure of a data processing device provided in this application;
[0026] Figure 7 This is a schematic diagram of the structure of a computer device provided in this application. Detailed Implementation
[0027] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0028] To facilitate understanding, the following brief explanations are provided for some of the terms:
[0029] (1) DID technology is a new type of identifier technology with global uniqueness, high availability and resolvability, and cryptographic verifiability. DID technology is typically associated with cryptographic materials (such as public keys) and server endpoints to establish secure communication channels. The implementation of DID technology relies on the DID protocol; the DID protocol is a digital identity protocol based on decentralized principles, conforming to the W3C DID specification. The DID protocol can include rules and methods for creating, resolving, and using digital identifiers, as well as rules and methods for creating, resolving, and using the corresponding identifier documents. Different service providers use different methods and rules in their DID protocols; therefore, there are differences between DID protocols used by different service providers. For example, the method for creating a digital identifier in the DID protocol of service provider A1 is method F1. Method F1 can perform hexadecimal operations on the public key of the business object to obtain the digital identifier of the business object. The DID protocol of service provider A2 includes method F2 for creating a digital identifier. Method F2 can perform hash value operations on the public key of the business object to obtain the digital identifier of the business object. In this case, method F1 in the DID protocol of service provider A1 is different from method F2 in the DID protocol of service provider A2. There is a difference between the DID protocol of service provider A1 and the DID protocol of service provider A2.
[0030] (2) Digital identifier, which can refer to decentralized identity identifier, can be in the following data format: "did:X: <method-specific-id>Here, "did" can be a fixed prefix in the numeric identifier, meaning that every numeric identifier includes the "did" prefix. When the parsing component receives data, it can determine that the data is a numeric identifier by the presence of the "did" prefix. "X" can be organizational information indicating the service organization that generated the numeric identifier; different service organizations will have different "X" in their generated numeric identifiers. For example, the format of the numeric identifier generated by service organization A3 is as follows: "did:a3did: <method-specific-id>The format of the digital identifier generated by service provider A4 is as follows: "did:a4did: <method-specific-id> ”。" <method-specific-id>"This can be an identifier within a digital identifier, used to determine the identification method for data identifiers. Furthermore, the digital identifiers generated by the same service provider for different business objects may differ. For example, service provider A5 generates the digital identifier did:a1did:1452874edb4863 for business object D1; and does:a1did:875a74ed8b4894 for business object D2. Service provider A5 generates different digital identifiers for business objects D1 and D2 respectively."
[0031] (3) Identification document. The identification document may include specific information about the digital identifier, such as the object public key of the business object corresponding to the digital identifier and the digital identifier encryption suite. The digital identifier encryption suite may include a series of encryption technologies, standards, and methods for generating, parsing, and managing the digital identifier. The specific format of the identification document can be found below:
[0032] {
[0033] "@context":"https: / / w3id.org / did / v1",
[0034] "id":"did:adid:7f8ca8982f6cc6e8ea087bd9457ab8024bd2",
[0035] "version":1,
[0036] "created":"2016-02-08T16:02:20Z",
[0037] "updated":"2016-02-08T16:02:20Z",
[0038] "publickey":[
[0039] {"id":"did:ccp:7f8ca8982f6cc6e8ea087bd9457ab8024bd2#keys-1",
[0040] "type":"secp256k1",
[0041] "publicKeyHex":"02b97c30de767f084ce3080168ee293053ba33b235"},
[0042] {"id":"did:ccp:7f8ca8982f6cc6e8ea087bd9457ab8024bd2#keys-2",
[0043] "type":"secp256k1",
[0044] "publicKeyHex":"e3080168ee293053ba33b235d7116a3263d29f1450936"}],
[0045] "authentication":["did:adid:7f8ca8982f6cc6e8ea087bd9457ab8024bd2#key-1"]
[0046] "recovery":["did:adid:7f8ca8982f6cc6e8ea087bd9457ab8024bd2#key-2"]
[0047] "service":[
[0048] {
[0049] "id":"did:adid:7f8ca8982f6cc6e8ea087bd9457ab8024bd2#resolver",
[0050] "type":"DIDResolve"
[0051] "serviceEndpoint":"https: / / did.aaa.com"
[0052] }
[0053] ],
[0054] "proof":{
[0055] "type":"Secp256k1",
[0056] "creator":"did:ccp:7f8ca8982f6cc6e8ea087bd9457ab8024bd2#keys-1",
[0057] "signatureValue":"ONB13Y7091tzin4w=="}}”。
[0058] Here, "@context" can be used to define the terminology used in the identifier document and its corresponding Uniform Resource Locator (URL). "id" can be used to indicate a numeric identifier. "version" can be used to indicate the version of the identifier document. "created" can be used to indicate the creation time of the identifier document. "updated" can be used to indicate the last modification time of the identifier document. "publickey" can be used to indicate a list of public keys for the object. "type" can be used to indicate the type of the corresponding public key for the object.
[0059] Here, "publicKeyHex" can be used to store the hexadecimal representation of the object's public key. "serviceEndpoint" can be used to specify the network endpoint of the service associated with the digital identifier. "authentication" can be used to indicate which business object owns the private key corresponding to the object's public key. "recovery" can be used to recover the list of object public keys. "service" can be used to indicate the endpoint information that can use the digital identifier. "creator" is used to indicate the digital identifier of the controller or owner of the document.
[0060] (4) Registration and resolution of digital identifiers. Registration of digital identifiers can refer to creating a digital identifier for a business object by calling the resolution component provided by the corresponding service provider. Resolution of digital identifiers can refer to obtaining the identifier document and related resources corresponding to the digital identifier based on the digital identifier of the business object.
[0061] (5) A blockchain is a data structure consisting of several blocks linked together by hash values. Each block comprises transactions generated within a certain period, packaged by computer nodes that have the right to record transactions, and independently verified by each computer node. In essence, a blockchain is a decentralized database, a chain of data blocks linked using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. In this application, the target service organization can use blockchain technology to manage the digital identifiers and encrypted identifier documents of its business objects. Therefore, this application can obtain the encrypted identifier document corresponding to the digital identifier of the business device from the blockchain corresponding to the target service organization based on the parsing component running in the general parsing container associated with the target service organization.
[0062] To facilitate a clearer understanding of this application, we will first introduce... Figure 1 , Figure 1 This is a schematic diagram of the structure of a blockchain data processing system provided in an embodiment of this application. Figure 1 In the example of a target service organization using blockchain network 10 to store digital and encrypted identification documents of business objects, the blockchain data processing system may include blockchain network 10 and server 11.
[0063] It should be noted that server 11 can refer to the backend device that manages the general identifier management platform. The target service organization can store the encrypted identifier document corresponding to the digital identifier in the blockchain of blockchain network 10, and each encrypted identifier document is associated with a corresponding identifier document URL.
[0064] Specifically, server 11 includes a general parsing container associated with the target service provider. Therefore, when server 11 receives a parsing request for a digital identifier from a business device, and the digital identifier includes organizational information of the target service provider that generated the digital identifier, server 11 can use the parsing component running in the general parsing container associated with the target service provider to parse the digital identifier to obtain an identifier document URL. Then, it can search for the encrypted identifier document associated with the parsed identifier document URL in the blockchain corresponding to the target service provider. Specifically, server 11 can send the parsed identifier document URL to a node device, which then searches for the encrypted identifier document associated with the identifier document URL in the blockchain network 10. Server 11 can receive the encrypted identifier document returned by the node device. After receiving the encrypted identifier document, server 11 can send the encrypted identifier document to the business device.
[0065] The blockchain network is an end-to-end decentralized network composed of multiple node devices (also called blockchain nodes). The number of node devices in the blockchain network can be deployed according to actual needs, and this application does not limit the number of node devices; Figure 1 The following example illustrates the blockchain network, which includes four node devices: node device 101, node device 102, node device 103, and node device 104.
[0066] It should be noted that node devices 101, 102, 103, and 104 can be a single physical server, a server cluster or distributed system consisting of at least two physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms.
[0067] It should be noted that server 11 can be a single physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.
[0068] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of a data processing system provided in an embodiment of this application. This data processing system can be used to implement the data processing method in this application. The data processing system may include a universal identifier management platform, which includes a file repository 230, a parsing component registration sub-platform 231, a container cluster 232, and a digital identifier parsing sub-platform 233.
[0069] It should be noted that the file repository 230, the parsing component registration sub-platform 231, the container cluster 232, and the digital identifier parsing sub-platform 233 can be deployed on the same device or on different devices.
[0070] It should be noted that the file repository 230 can be used to store image files corresponding to the parsing components provided by multiple service providers. In this application, the target service provider can be any one of the multiple service providers. For example, taking multiple service providers including service provider 201 and service provider 202 as an example, the device 211 corresponding to service provider 201 can package the parsing components provided by service provider 201 to obtain image file 221, and send image file 221 to the file repository 230. The device 212 corresponding to service provider 202 can package the parsing components provided by service provider 202 to obtain image file 222, and send image file 222 to the file repository 230.
[0071] It should be noted that the parsing component registration sub-platform 231 can be used to provide a request receiving interface for service organizations regarding registration requests for parsing components. For example, the organization device 213 corresponding to service organization 203 can send a registration request for the parsing component to the backend device corresponding to the parsing component registration sub-platform 231 based on the request receiving interface. The backend device corresponding to the parsing component registration sub-platform 231 can call the request receiving interface to receive the registration request for the parsing component from service organization 203.
[0072] It should be noted that container cluster 232 may include multiple general-purpose parsing containers corresponding to different service providers, each of which runs a parsing component provided by the corresponding service provider. When the backend device corresponding to container cluster 232 receives a registration request for the parsing component from service provider 203, the backend device corresponding to container cluster 232 may, based on the registration request, create a general-purpose parsing container associated with service provider 203 in container cluster 232 and run the parsing component of the corresponding service provider in the general-purpose parsing container.
[0073] It should be noted that the digital identifier resolution sub-platform 233 can be used to provide a request receiving interface for resolution requests regarding digital identifiers to business objects. For example, taking business device 240 as the device corresponding to the business object, business device 240 can send resolution requests regarding digital identifiers to the backend device corresponding to the digital identifier resolution sub-platform 233. The backend device corresponding to the digital identifier resolution sub-platform 233 can call the request receiving interface of the digital identifier resolution sub-platform 233 to receive the resolution requests regarding digital identifiers from business device 240.
[0074] Further, please see Figure 3 This is a flowchart illustrating a data processing method provided in an embodiment of this application. Figure 3 As shown, this method can be executed by a computer device, which can refer to... Figure 1 The server in the system. The method may include at least:
[0075] S101. Call the request receiving interface of the general identifier management platform to receive the parsing request for the digital identifier of the business device.
[0076] It should be noted that the computer equipment can refer to the backend equipment used to manage the universal identifier management platform, which may include a file repository, a resolution component registration sub-platform, a container cluster, and a digital identifier resolution sub-platform. The request receiving interface of the universal identifier management platform can refer to the request receiving interface of the digital identifier resolution sub-platform.
[0077] It should be noted that "business equipment" can refer to the equipment corresponding to the business object, or it can refer to the equipment that provides services related to digital identification for the business object. There can be one or more digital identifiers; each digital identifier may include organizational information of the target service organization that generated the digital identifier. Organizational information may include at least one of the following: organization name, organization number, etc.
[0078] In this application, a digital identifier can be an identity information of a business object in a decentralized application (DPA) scenario. When a business object logs into the DPA, its digital identifier needs to be parsed to obtain the corresponding identifier document, thereby verifying the legitimacy of the business object's identity based on the identifier document. In other words, the digital identifier is used to identify the business object's identity, and upon successful verification, the DPA allows users to perform data operations based on the digital identifier. For example, after logging into an asset management application, a business object can perform data operations such as asset transfer and asset inflow. Therefore, when a business device provides a DPA to a business object, and the business object logs into the DPA, the business device needs to verify the legitimacy of the business object's identity. The business device can generate a parsing request based on the business object's digital identifier. The business device can call the request receiving interface of the digital identifier parsing sub-platform, using the parsing request as a parameter, and send the parsing request to the computer device. The computer device can receive the parsing request for the business device's digital identifier through the request receiving interface of the digital identifier parsing sub-platform.
[0079] It should be noted that decentralized applications (DAPIs) can refer to applications built using blockchain technology or other distributed ledger technologies, which do not rely on a single central server or entity, but instead run on multiple nodes distributed across a network. Application scenarios for DAPIs can include asset management related to digital assets, social networking, and gaming.
[0080] S102. Based on the organization information, query the general resolution container associated with the target service organization from the container cluster of the general identifier management platform.
[0081] It should be noted that a container cluster includes multiple general-purpose resolution containers associated with different service providers, each running a resolution component provided by its corresponding service provider. The target service provider can be any one of these multiple service providers. A container cluster can refer to a system that organizes and manages multiple container instances into a single, coordinated unit. Container clusters include managed clusters, self-managed clusters, hybrid cloud clusters, multi-cloud clusters, etc.
[0082] It should be noted that the parsing component can refer to an application or code module; the parsing component can be used to parse digital identifiers, register digital identifiers, modify identifier documents, etc. The parsing component includes the DID protocol of the corresponding service organization. That is to say, the parsing component includes the rules and methods for the corresponding service organization to create, parse, and use digital identifiers, as well as the rules and methods for creating, parsing, and using the identifier documents corresponding to the digital identifiers.
[0083] It should be noted that a general-purpose parsing container can refer to a component with a lightweight, portable, and self-sufficient software runtime environment. Each general-purpose parsing container has two data interfaces. These two data interfaces can be a digital identifier parsing interface for parsing the encrypted identifier document corresponding to the digital identifier of a business object, and a digital identifier management interface for registering the digital identifier of a business object and modifying the identifier document corresponding to the digital identifier of the business object. Modifying the identifier document corresponding to the digital identifier of a business object can be achieved by sending the encrypted file of the modified identifier document to the corresponding institutional equipment of the target service organization.
[0084] It should be noted that the generic resolution container is associated with information such as container ID, service address, and container name within the container cluster, and these information are all unique. That is, different generic resolution containers are associated with different container IDs, service addresses, and container names. The container ID can be generated based on the organization ID, the container name can be generated based on the organization name, and the service address can also be generated based on the organization name.
[0085] In this application, upon receiving a resolution request for a digital identifier of a business device, the organization information of the target service organization that generated the digital identifier is obtained from the digital identifier. The generic resolution container associated with the organization information is then queried from the container cluster of the generic identifier management platform; this container is the generic resolution container associated with the target service organization.
[0086] For example, taking an organization information field that includes the organization name and a general resolution container that includes the service address as an example, the general resolution container associated with the target service organization can include any of the following: 1. A general resolution container in the container cluster whose associated service address includes the organization name of the target service organization; 2. A general resolution container in the container cluster whose information similarity between the associated service address and the organization information of the target service organization is greater than an information similarity threshold. The information similarity threshold can be a default value in the computer equipment or can be manually set. Information similarity can be obtained based on a similarity algorithm, such as cosine similarity or Euclidean distance.
[0087] S103. The parsing component running in the general parsing container associated with the target service provider is used to parse the digital identifier of the business device to obtain the encrypted identifier document corresponding to the digital identifier of the business device.
[0088] It should be noted that the institutional equipment corresponding to the service provider can use blockchain technology to manage the digital identifiers and identifier documents of business objects. Specifically, the institutional equipment corresponding to the service provider can use the public key of the business object to encrypt the identifier document of the business object, obtaining an encrypted identifier document; and store the encrypted identifier document and the digital identifier on the blockchain corresponding to the service provider.
[0089] It should be noted that the encrypted identifier document corresponding to the digital identifier of the business device can be obtained by the target service organization encrypting the identifier document corresponding to the digital identifier of the business object based on the object's public key. The identifier document corresponding to the digital identifier of the business object may include the object's public key, digital identifier encryption suite, etc. The digital identifier encryption suite may include a series of encryption technologies, standards, and methods for generating, parsing, and managing digital identifiers.
[0090] In this application, a computer device can input the digital identifier of a business device into a parsing component running in a general parsing container associated with a target service provider to obtain the URL of an identifier document corresponding to the digital identifier. Then, it can retrieve an encrypted identifier document matching the URL from the storage space corresponding to the target service provider. This eliminates the need to implement additional code modules to interface with the service provider's parsing component, reducing the parsing workload of the business device and lowering the complexity of digital identifier parsing.
[0091] It should be noted that when the institutional equipment corresponding to the target service provider uses blockchain technology to manage the digital identifiers and identifier documents of business objects, the storage space corresponding to the target service provider can refer to the blockchain corresponding to the target service provider, and the blockchain corresponding to the target service provider can be stored in the node equipment within the blockchain network corresponding to the target service provider. When the institutional equipment corresponding to the target service provider uses other distributed ledger technologies to manage the digital identifiers and identifier documents of business objects, the storage space corresponding to the target service provider can be located within the institutional equipment corresponding to the target service provider.
[0092] S104. Send the encrypted identifier document corresponding to the digital identifier of the business device to the business device.
[0093] It should be noted that the business equipment is used to decrypt the encrypted identification document to obtain the identification document corresponding to the digital identification of the business equipment.
[0094] In this application, after obtaining the encrypted identifier document corresponding to the digital identifier of the business device, the computer device can send the encrypted identifier document to the business device. The business device can decrypt the encrypted identifier file based on the private key of the business object to obtain the identifier document corresponding to the digital identifier of the business device. The business device can verify the identity and legitimacy of the business object based on the identifier document, thus preventing the information in the identifier document from being illegally obtained and improving the information security of the identifier document. Furthermore, if an encrypted identifier document matching the digital identifier cannot be obtained from the blockchain corresponding to the target service institution, a parsing failure message will be generated. The computer device can return the parsing failure message to the business device.
[0095] This application provides a universal identifier management platform, which includes a container cluster. Within the container cluster are multiple universal parsing containers associated with different service providers. Each universal parsing container runs a parsing component provided by the corresponding service provider. Therefore, when a parsing request for a digital identifier of a business device is received, based on the organization information of the target service provider in the digital identifier, the platform can query the universal parsing container associated with the target service provider from the container cluster. The parsing component running in the found universal parsing container is then used to parse the digital identifier of the business device. This eliminates the need for the business device to implement additional code modules to interface with the service provider's parsing component, reducing the parsing workload and complexity of the digital identifier. The universal identifier management platform can only parse the encrypted identifier document corresponding to the digital identifier, thus preventing the unauthorized acquisition of information in the identifier document and improving the information security of the identifier document.
[0096] Further, please see Figure 4 This is a flowchart illustrating another data processing method provided in an embodiment of this application. Figure 4 As shown, this method can be executed by a computer device, which can refer to... Figure 1 The server in the system. The method may include at least:
[0097] S201. Call the request receiving interface of the general identifier management platform to receive the second registration request for the digital identifier of the business object corresponding to the business device.
[0098] It should be noted that the second registration request carries the public key of the aforementioned business object and the organizational information corresponding to the N service providers used to generate the digital identifier. The target service provider is any one of the N service providers; N is an integer greater than 1.
[0099] It should be noted that the request receiving interface of the general identifier management platform can refer to the request receiving interface of the digital identifier resolution sub-platform. The public key and private key of a business object can refer to a set of numbers generated through an encryption algorithm. Business devices can generate the public and private keys of business objects based on asymmetric encryption algorithms. These asymmetric encryption algorithms can include Rivest-Shamir-Aardman encryption, Elgamar encryption, elliptic curve cryptography, etc.
[0100] In this application, the universal identifier management platform can provide a business object with the function of registering digital identifiers for multiple service providers at once. Specifically, the business device can generate a second registration request based on the business object's public key and the organization information corresponding to the N service providers used to generate the digital identifiers. The business device can send the second registration request to the computer device through the request receiving interface of the digital identifier resolution sub-platform. The computer device can receive the second registration request for the digital identifiers of the business object corresponding to the business device through the request receiving interface of the digital identifier resolution sub-platform.
[0101] S202. Based on the organization information of each of the N service organizations, query the general parsing container corresponding to each service organization from the container cluster.
[0102] It should be noted that each generic DNS container in the container cluster has an associated service address. The service address associated with each generic DNS container can be generated based on a service address template and the corresponding service provider's organizational information. The service address template can be the default template in the container cluster or it can be manually set.
[0103] In this application, the computer device can obtain the organization information of the first service provider from the second registration request, add the organization information of the first service provider to the service address template in the container cluster, and obtain the service address associated with the general resolution container corresponding to the first service provider in the container cluster. It then obtains the organization information of the second service provider, adds the organization information of the second service provider to the service address template in the container cluster, and obtains the service address associated with the general resolution container corresponding to the second service provider in the container cluster. This process is repeated sequentially to obtain the service addresses associated with the general resolution containers corresponding to N service providers. Further, based on the service address associated with the general resolution container corresponding to each service provider, the general resolution container corresponding to each service provider is queried from the container cluster.
[0104] S203. Using the parsing components running in the general parsing containers corresponding to the N service providers respectively, generate digital identifiers for the business object corresponding to the N service providers based on the public key of the business object.
[0105] It should be noted that the methods for creating digital identifiers differ within the parsing components running in the general parsing containers corresponding to different service providers. Therefore, the parsing components running in the general parsing containers for each service provider include the method for creating digital identifiers specific to that service provider. These methods may include hashing the object's public key, performing hexadecimal operations on the object's public key, or performing encryption operations on the object's public key, among others.
[0106] In this application, a computer device can send the public key of a business object to a resolution component running in a general resolution container corresponding to the first service provider. Based on the method for creating digital identifiers for the first service provider, the device processes the public key of the business object to generate a digital identifier for the business object corresponding to the first service provider. The device then sends the public key of the business object to a resolution component running in a general resolution container corresponding to the second service provider. Based on the method for creating digital identifiers for the second service provider, the device processes the public key of the business object to generate a digital identifier for the business object corresponding to the second service provider. This process is repeated until digital identifiers for the business object corresponding to N service providers are obtained. Through a general identifier management platform, digital identifiers for multiple service providers can be registered with a single click, improving the convenience and efficiency of using DID services, lowering the barrier to entry for users of the DID protocol, and enhancing the user experience.
[0107] S204. Send the digital identifiers corresponding to the N service providers for the business object to the business device.
[0108] In this application, the computer device can send the digital identifiers corresponding to the N service providers for the business object to the business device.
[0109] like Figure 5 As shown, Figure 5 This is a schematic diagram of a registration process for a digital identifier provided in an embodiment of this application. Taking a second registration request carrying organizational information corresponding to three service providers as an example, the business device 51 sends a second registration request for the digital identifier of the business object corresponding to the business device to the backend device corresponding to the digital identifier resolution sub-platform 52. The backend device corresponding to the digital identifier resolution sub-platform 52 can be used to generate service addresses of the general resolution containers corresponding to the three service providers based on the organizational information corresponding to the three service providers. Based on the service address of the general resolution container corresponding to the first service provider, the general resolution container 531 corresponding to the first service provider is queried from the container cluster 53; based on the service address of the general resolution container corresponding to the second service provider, the general resolution container 532 corresponding to the second service provider is queried from the container cluster 53; based on the service address of the general resolution container corresponding to the third service provider, the general resolution container 533 corresponding to the third service provider is queried from the container cluster 53. The backend device corresponding to the digital identifier resolution sub-platform 52 can send the object public key to the general resolution containers 531, 532, and 533 respectively.
[0110] Furthermore, the parsing component running in the general parsing container 531 can obtain the digital identifier corresponding to the first service provider based on the object's public key; the parsing component running in the general parsing container 532 can obtain the digital identifier corresponding to the second service provider based on the object's public key; and the parsing component running in the general parsing container 533 can obtain the digital identifier corresponding to the third service provider based on the object's public key. The obtained three digital identifiers are then returned to the digital identifier parsing sub-platform 52. The backend device corresponding to the digital identifier parsing sub-platform 52 can then send the obtained three digital identifiers to the business device 51.
[0111] S205. Call the request receiving interface of the general identifier management platform to receive the parsing request for the digital identifier of the business device.
[0112] S206. Based on the organization information, query the general resolution container associated with the target service organization from the container cluster of the general identifier management platform.
[0113] Optionally, obtain the service address template of the general resolution container in the container cluster of the general identifier management platform; add the organization information to the service address template to obtain the service address of the general resolution container associated with the target service organization; and query the general resolution container associated with the target service organization from the container cluster of the general identifier management platform based on the service address.
[0114] In this application, a computer device can obtain a service address template for a generic resolution container from a container cluster, add organization information to the service address template, and generate a service address for a generic resolution container associated with the target service organization. From the container cluster, the generic resolution container whose associated service address matches the generated service address is the generic resolution container associated with the target service organization.
[0115] For example, if the container cluster is a Kubernetes (K8S) cluster, the service address template for the general resolution container in the K8S cluster is "Http: / / www.resolver.xxx", where "xxx" indicates the organization information of the corresponding service provider. When the organization information of the target service provider is the organization name, and the organization name is "abc", the service address of the general resolution container associated with the target service provider can be "Http: / / www.resolver.abc".
[0116] It should be noted that the general resolution container that matches the associated service address with the generated service address can include any of the following: 1. A general resolution container in the container cluster whose associated service address is the same as the generated service address is a general resolution container associated with the target service organization; 2. A general resolution container in the container cluster whose address similarity between the associated service address and the generated service address is greater than the address similarity threshold is a general resolution container associated with the target service organization.
[0117] It should be noted that the address similarity threshold can be a default value in the computer device or it can be set manually. Address similarity can be obtained based on similarity algorithms, such as cosine similarity and Euclidean distance.
[0118] Optionally, a first test message is sent to a general resolution container with a service address in the container cluster of the general identifier management platform; when a first test response message is received from the general resolution container with a service address in response to the first test message, it is determined that the general resolution container with a service address is in a working state; the general resolution container with a service address and in a working state is identified as the general resolution container associated with the target service organization.
[0119] It should be noted that the first test information can be used to test whether the registration status of the general parsing container associated with the target service provider is registered, and whether the general parsing container associated with the target service provider is in a working state. The first test response information can be generated by the general parsing container in a working state after receiving the first test information.
[0120] It should be noted that a general parsing container in working state can return a first test response to the computer device when it receives the first test information; a general parsing container that is not in working state cannot receive the first test information, and therefore the computer device cannot receive the returned first test response information.
[0121] In this application, when a generic resolution container with the service address exists in the container cluster, it indicates whether the registration status of the generic resolution container associated with the target service organization is registered; when no generic resolution container with the service address exists in the container cluster, it indicates whether the registration status of the generic resolution container associated with the target service organization is unregistered. Further, the computer device can send first test information to the service address. Upon receiving the first test information, the generic resolution container with the service address can generate first test response information based on the first test information and send the first test response information to the computer device. When the computer device receives the first test response information returned by the generic resolution container with the service address in response to the first test information, it indicates that the generic resolution container with the service address is in a working state. The computer device can identify a generic resolution container with a service address and in a working state as a generic resolution container associated with the target service organization.
[0122] S207. The parsing component running in the general parsing container associated with the target service provider is used to parse the digital identifier of the business device to obtain the encrypted identifier document corresponding to the digital identifier of the business device.
[0123] Optionally, the request receiving interface of the general identifier management platform is called to receive the first registration request for the parsing component for the target service organization; the first registration request carries the image file and the organization information of the target service organization, and the image file is obtained by packaging the parsing component of the target service organization; based on the image file and the organization information, a general parsing container associated with the target service organization is created in the container cluster, and the parsing component provided by the target service organization is run in the general parsing container.
[0124] It should be noted that the request receiving interface of the universal identifier management platform can refer to the request receiving interface of the parsing component registration sub-platform. The universal identifier management platform also includes interface documentation for the universal parsing container; the image file can be a package of the parsing component implemented based on this interface documentation, obtained from the institutional equipment corresponding to the target service organization. The image file can include the application code, system settings, configuration parameters, etc., of the parsing component. This interface documentation can be used to indicate the interface parameters of the two data interfaces that the parsing component must satisfy. These two data interfaces can refer to the digital identifier parsing interface and the digital identifier management interface present in the universal parsing container mentioned above.
[0125] For example, the interface documentation may include interface parameter C1 "GET / v1 / did / resolve / {did}HTTP / 1.1" and interface parameter C2 "POST / v1 / did / operation HTTP / 1.1". An interface implemented based on interface parameter C1 can be used to parse the encrypted identifier document corresponding to the digital identifier of a business object; an interface implemented based on interface parameter C2 can be used to register the digital identifier of a business object, modify the identifier document corresponding to the digital identifier of a business object, etc.
[0126] In this application, the equipment corresponding to the target service organization can implement the corresponding parsing component based on the interface documentation. The equipment corresponding to the target service organization can package the parsing component to obtain an image file, and generate a first registration request carrying the image file and the organization information of the target service organization; and send the first registration request to the computer equipment. The computer equipment can receive the first registration request based on the request receiving interface of the registration sub-platform of the parsing component. An initial general parsing container is created in the container cluster, and the image file is deployed in the initial general parsing container to obtain a general parsing container associated with the target service organization. Through the general identifier management platform, multiple parsing components corresponding to service organizations related to digital identifiers can be integrated, facilitating cross-platform use of digital identifier registration and parsing services for users.
[0127] Optionally, the image file is stored in the file repository of the general identifier management platform, and the storage address of the image file in the file repository is obtained; based on the organization information, the registration status of the general parsing container associated with the target service organization in the container cluster is determined; when the registration status of the general parsing container associated with the target service organization in the container cluster is unregistered, the storage address and organization information are added to the registration queue; based on the registration queue, the general parsing container associated with the target service organization is created in the container cluster, and the parsing component provided by the target service organization is run in the general parsing container.
[0128] It should be noted that the file repository can include image files corresponding to multiple service providers. The registration status of the general parsing container includes registered and unregistered status. The registration queue includes at least one image file associated with a service provider and the corresponding service provider's organizational information.
[0129] In this application, the computer device can store the received image file in a file repository of a universal identifier management platform, obtain the storage address of the image file in the file repository, and send the storage address to the organizational device corresponding to the target service organization. Based on the organizational information, the computer device can generate a service address for the universal resolution container associated with the target service organization in a container cluster. When a universal resolution container with this service address exists in the container cluster, it indicates that the universal resolution container associated with the target service organization is registered; when no universal resolution container with this service address exists in the container cluster, it indicates that the universal resolution container associated with the target service organization is unregistered. Furthermore, the computer device can store the storage address and the organizational information of the target service organization in a registration queue. The computer device can sequentially obtain the storage address and organizational information from the registration queue. When it obtains the storage address of the image file associated with the target service organization and the organizational information of the target service organization, it creates a universal resolution container associated with the target service organization in the container cluster and deploys the image file associated with the target service organization in the universal resolution container.
[0130] Optionally, the storage address and organization information are obtained sequentially from the registration queue. When the storage address of the image file associated with the target service organization and the organization information of the target service organization are obtained from the queue to be registered, the image file associated with the target service organization is queried from the file repository according to the storage address. According to the organization information, a general parsing container associated with the target service organization is created in the container cluster. According to the image file associated with the target service organization, the parsing component provided by the target service organization is run in the general parsing container.
[0131] In this application, the computer device can sequentially retrieve storage addresses and organization information from the registration queue based on a first-in, first-out (FIFO) principle. When it retrieves the storage address of an image file associated with a target service organization and the organization information of the target service organization from the registration queue, it indicates that the general resolution container corresponding to the target service organization needs to be registered. Therefore, the computer device can query the file repository for image files whose storage addresses match the storage addresses of the image files associated with the target service organization. An initial general resolution container is created in the container cluster, and the organization information of the target service organization is associated with this initial general resolution container to obtain a general resolution container associated with the target service organization. The retrieved image file is deployed in the general resolution container associated with the target service organization, allowing the resolution components provided by the target service organization to run within the general resolution container.
[0132] Optionally, a container creation method is used to create an initial general-purpose resolution container in a container cluster; based on the organization information, a service address associated with the target service organization is generated; the service address associated with the target service organization is associated with the initial general-purpose resolution container to obtain a general-purpose resolution container associated with the target service organization.
[0133] It should be noted that the container creation method described above can refer to using a container orchestration tool to execute container creation commands. A container orchestration tool can be a component in a container cluster used to create new containers (i.e., initial generic resolution containers). Container creation commands can be used to instruct the container orchestration tool to perform the operation of creating new containers.
[0134] In this application, the computer device can create an initial general-purpose resolution container in a container cluster based on a container creation method, and configure the environment parameters of the initial general-purpose resolution container. The computer device can obtain a service address template, add organization information to the service address template to obtain a service address associated with the target service organization, and associate the service address associated with the target service organization with the initial general-purpose resolution container to obtain a general-purpose resolution container associated with the target service organization.
[0135] Optionally, send the second test information to the general parsing container; when the general parsing container returns the second test response information in response to the second test information, determine that the general parsing container is in a working state; and delete the storage address and organization information from the registration queue.
[0136] It should be noted that the second test information can be used to test whether the general parsing container is in a working state. The first test response information can be generated by the general parsing container, which is in a working state, based on the second test information.
[0137] In this application, after a computer device runs the parsing component provided by the target service provider within a universal parsing container associated with the target service provider, based on an image file, it can verify the working status of the parsing component in the universal parsing container. Specifically, the computer device can send second test information to the universal parsing container. When a second test response is received within a preset time period, it indicates that the parsing component running in the universal parsing container is in a working state, meaning that the universal parsing container associated with the target service provider has been successfully registered in the universal identifier management platform. The computer device can then remove the storage address and organization information from the registration queue. The preset time period can be a default value in the computer device or a manually set value.
[0138] Furthermore, the universal identifier management platform also includes a registered queue, which stores the organization information of the service providers corresponding to universal resolution containers that are registered, as well as the storage address of the image files provided by these service providers in the file repository. Before a computer device removes the storage address and organization information from the pending registration queue, it can also add the storage address and organization information to the registered queue. The computer device can also send registration success information about the universal resolution component to the organization device corresponding to the target service provider. When the organization device corresponding to the target service provider receives the registration success information, it indicates that the image file has been successfully deployed and the universal resolution container has been successfully registered. The target service provider can then announce that its digital identifier service has been integrated into the universal identifier management platform. Through the universal identifier management platform, digital identifier services provided by multiple service providers can be used, which helps reduce the complexity of digital identifier resolution.
[0139] S208. Send the encrypted identifier document corresponding to the digital identifier of the business device to the business device.
[0140] This application provides a universal identifier management platform, which includes a container cluster. Within the container cluster are multiple universal parsing containers associated with different service providers. Each universal parsing container runs a parsing component provided by the corresponding service provider. Therefore, when a parsing request for a digital identifier of a business device is received, based on the organization information of the target service provider in the digital identifier, the platform can query the universal parsing container associated with the target service provider from the container cluster. The parsing component running in the found universal parsing container is then used to parse the digital identifier of the business device. This eliminates the need for the business device to implement additional code modules to interface with the service provider's parsing component, reducing the parsing workload and complexity of the digital identifier. The universal identifier management platform can only parse the encrypted identifier document corresponding to the digital identifier, thus preventing the unauthorized acquisition of information in the identifier document and improving the information security of the identifier document.
[0141] Please see Figure 6 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application. Figure 6 As shown, the data processing apparatus may include:
[0142] The receiving module 611 is used to call the request receiving interface of the general identifier management platform to receive the parsing request for the digital identifier of the business device; the digital identifier includes the organizational information of the target service organization that generated the digital identifier.
[0143] The query module 612 is used to query the general parsing container associated with the target service organization from the container cluster of the general identifier management platform based on the above-mentioned organization information; the container cluster includes general parsing containers associated with multiple service organizations respectively, the target service organization is any one of the multiple service organizations, and each general parsing container runs a parsing component provided by the corresponding service organization.
[0144] The processing module 613 is used to parse the digital identifier of the business device through the parsing component running in the general parsing container associated with the target service provider, and obtain the encrypted identifier document corresponding to the digital identifier of the business device.
[0145] The sending module 614 is used to send the encrypted identifier document corresponding to the digital identifier of the above-mentioned service device to the above-mentioned service device; the above-mentioned service device is used to decrypt the encrypted identifier document to obtain the identifier document corresponding to the digital identifier of the above-mentioned service device.
[0146] Optionally, the query module 612 described above can also be used to execute:
[0147] Obtain the service address template of the general resolution container in the container cluster of the aforementioned general identifier management platform;
[0148] Add the above organization information to the above service address template to obtain the service address of the general resolution container associated with the above target service organization;
[0149] Based on the above service address, query the general resolution container associated with the above target service provider from the container cluster of the above general identifier management platform.
[0150] Optionally, the query module 612 described above can also be used to execute:
[0151] Send the first test information to the general resolution container with the above service address in the container cluster of the above general identifier management platform;
[0152] When the first test response information returned by the general parsing container with the above service address in response to the above first test information is received, it is determined that the general parsing container with the above service address is in a working state.
[0153] The aforementioned general-purpose DNS container that has the above-mentioned service address and is in a working state is identified as the general-purpose DNS container associated with the aforementioned target service provider.
[0154] Optionally, the above-mentioned data processing apparatus may further include:
[0155] The receiving module 611 is also used to call the request receiving interface of the general identifier management platform to receive the first registration request for the parsing component of the target service organization; the first registration request carries an image file and the organization information of the target service organization, and the image file is obtained by packaging the parsing component of the target service organization.
[0156] The processing module 613 is further configured to create a general parsing container associated with the target service organization in the container cluster based on the image file and the organization information, and run the parsing component provided by the target service organization in the general parsing container.
[0157] Optionally, the above-mentioned processing module 613 can also be used to perform:
[0158] Store the aforementioned image file in the file repository of the aforementioned general identifier management platform, and obtain the storage address of the aforementioned image file in the aforementioned file repository;
[0159] Based on the above-mentioned organization information, determine the registration status of the general parsing container associated with the above-mentioned target service organization in the above-mentioned container cluster;
[0160] When the registration status of the general parsing container associated with the target service organization in the above container cluster is unregistered, add the above storage address and the above organization information to the registration queue;
[0161] Based on the above-mentioned queue of pending registrations, a general parsing container associated with the above-mentioned target service provider is created in the above-mentioned container cluster, and the parsing component provided by the above-mentioned target service provider is run in the above-mentioned general parsing container.
[0162] Optionally, the above-mentioned processing module 613 can also be used to perform:
[0163] The storage address and organization information are retrieved sequentially from the above queue of pending registrations;
[0164] When the storage address of the image file associated with the target service provider and the organization information of the target service provider are obtained from the above-mentioned queue of pending registrations, the image file associated with the target service provider is queried from the above-mentioned file repository based on the above-mentioned storage address.
[0165] Based on the organization information, create a general parsing container associated with the target service organization in the aforementioned container cluster;
[0166] Based on the image file associated with the aforementioned target service provider, the parsing component provided by the aforementioned target service provider is run in the aforementioned general parsing container.
[0167] Optionally, the above-mentioned processing module 613 can also be used to perform:
[0168] Using the container creation method, an initial general-purpose parsing container is created in the aforementioned container cluster;
[0169] Based on the above organization information, generate a service address associated with the above target service organization;
[0170] The service address associated with the aforementioned target service provider is associated with the aforementioned initial general resolution container to obtain the general resolution container associated with the aforementioned target service provider.
[0171] Optionally, the above-mentioned processing module 613 can also be used to perform:
[0172] Send the second test information to the aforementioned general parsing container;
[0173] When the general parsing container receives the second test response information returned by the general parsing container in response to the second test information, it is determined that the general parsing container is in a working state.
[0174] Remove the aforementioned storage address and organization information from the aforementioned queue of pending registrations.
[0175] Optionally, the above-mentioned data processing device can also be used to perform:
[0176] The receiving module 611 is also used to call the request receiving interface of the general identifier management platform to receive a second registration request for the digital identifier of the business object corresponding to the business device; the second registration request carries the object public key of the business object and the organization information corresponding to the N service organizations used to generate the digital identifier; the target service organization is any one of the N service organizations; N is an integer greater than 1.
[0177] The query module 612 is also used to query the general parsing container corresponding to each of the above-mentioned service institutions from the above-mentioned container cluster based on the institution information of each of the above-mentioned N service institutions.
[0178] Processing module 613 is further configured to generate digital identifiers for the business object corresponding to the N service institutions based on the object public key of the business object, using the parsing components running in the general parsing containers corresponding to the N service institutions respectively.
[0179] The sending module 614 is also used to send the digital identifiers corresponding to the above-mentioned business objects and the above-mentioned N service institutions to the above-mentioned business equipment.
[0180] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.
[0181] This application provides a universal identifier management platform, which includes a container cluster. Within the container cluster are multiple universal parsing containers associated with different service providers. Each universal parsing container runs a parsing component provided by the corresponding service provider. Therefore, when a parsing request for a digital identifier of a business device is received, based on the organization information of the target service provider in the digital identifier, the platform can query the universal parsing container associated with the target service provider from the container cluster. The parsing component running in the found universal parsing container is then used to parse the digital identifier of the business device. This eliminates the need for the business device to implement additional code modules to interface with the service provider's parsing component, reducing the parsing workload and complexity of the digital identifier. The universal identifier management platform can only parse the encrypted identifier document corresponding to the digital identifier, thus preventing the unauthorized acquisition of information in the identifier document and improving the information security of the identifier document.
[0182] Please see Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 7 As shown, the aforementioned computer device 700 can refer to a server or terminal, including: a processor 701, a network interface 704, and a memory 705. Furthermore, the aforementioned computer device 700 may also include: a user interface 703, and at least one communication bus 702. The communication bus 702 is used to implement communication between these components. In some embodiments, the user interface 703 may include a display screen and a keyboard; optionally, the user interface 703 may also include a standard wired interface or a wireless interface. The network interface 704 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 705 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. The memory 705 may also optionally be at least one storage device located remotely from the aforementioned processor 701. Figure 7 As shown, the memory 705, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and computer programs.
[0183] exist Figure 7 In the computer device 700 shown, the network interface 704 provides network communication functionality; the user interface 703 is mainly used to provide an input interface; and the processor 701 can be used to call computer programs stored in the memory 705 to execute:
[0184] The request receiving interface of the general identifier management platform is invoked to receive the parsing request for the digital identifier of the business device; the digital identifier includes the organizational information of the target service organization that generated the digital identifier.
[0185] Based on the above-mentioned organizational information, query the general parsing container associated with the target service organization from the container cluster of the above-mentioned general identifier management platform; the container cluster includes general parsing containers associated with multiple service organizations respectively, the target service organization is any one of the multiple service organizations, and each general parsing container runs the parsing component provided by the corresponding service organization;
[0186] The parsing component running in the general parsing container associated with the aforementioned target service provider parses the digital identifier of the aforementioned business device to obtain the encrypted identifier document corresponding to the digital identifier of the aforementioned business device.
[0187] The encrypted identifier document corresponding to the digital identifier of the aforementioned business device is sent to the aforementioned business device; the aforementioned business device is used to decrypt the aforementioned encrypted identifier document to obtain the identifier document corresponding to the digital identifier of the aforementioned business device.
[0188] Optionally, the processor 701 can be used to call a computer program stored in the memory 705 to perform the above-mentioned querying of the general resolution container associated with the target service organization from the container cluster of the general identifier management platform based on the above-mentioned organization information, including:
[0189] Obtain the service address template of the general resolution container in the container cluster of the aforementioned general identifier management platform;
[0190] Add the above organization information to the above service address template to obtain the service address of the general resolution container associated with the above target service organization;
[0191] Based on the above service address, query the general resolution container associated with the above target service provider from the container cluster of the above general identifier management platform.
[0192] Optionally, processor 701 can be used to call a computer program stored in memory 705 to execute the above-mentioned querying of the general resolution container associated with the target service provider from the container cluster of the general identifier management platform based on the above-mentioned service address, including:
[0193] Send the first test information to the general resolution container with the above service address in the container cluster of the above general identifier management platform;
[0194] When the first test response information returned by the general parsing container with the above service address in response to the above first test information is received, it is determined that the general parsing container with the above service address is in a working state.
[0195] The aforementioned general-purpose DNS container that has the above-mentioned service address and is in a working state is identified as the general-purpose DNS container associated with the aforementioned target service provider.
[0196] Optionally, the processor 701 can be used to invoke a computer program stored in the memory 705 to perform the above method, which further includes:
[0197] The request receiving interface of the aforementioned general identifier management platform is invoked to receive the first registration request for the parsing component of the aforementioned target service organization; the first registration request carries an image file and the organization information of the aforementioned target service organization, and the image file is obtained by packaging the parsing component of the aforementioned target service organization;
[0198] Based on the aforementioned image file and the aforementioned organization information, a general parsing container associated with the aforementioned target service organization is created in the aforementioned container cluster, and the parsing component provided by the aforementioned target service organization is run in the aforementioned general parsing container.
[0199] Optionally, processor 701 can be used to call a computer program stored in memory 705 to execute the creation of a general parsing container associated with the target service organization in the container cluster based on the image file and the organization information, and to run the parsing components provided by the target service organization in the general parsing container, including:
[0200] Store the aforementioned image file in the file repository of the aforementioned general identifier management platform, and obtain the storage address of the aforementioned image file in the aforementioned file repository;
[0201] Based on the above-mentioned organization information, determine the registration status of the general parsing container associated with the above-mentioned target service organization in the above-mentioned container cluster;
[0202] When the registration status of the general parsing container associated with the target service organization in the above container cluster is unregistered, add the above storage address and the above organization information to the registration queue;
[0203] Based on the above-mentioned queue of pending registrations, a general parsing container associated with the above-mentioned target service provider is created in the above-mentioned container cluster, and the parsing component provided by the above-mentioned target service provider is run in the above-mentioned general parsing container.
[0204] Optionally, processor 701 can be used to invoke a computer program stored in memory 705 to execute the creation of a general parsing container associated with the target service provider in the container cluster according to the registration queue, and to run the parsing component provided by the target service provider in the general parsing container, including:
[0205] The storage address and organization information are retrieved sequentially from the above queue of pending registrations;
[0206] When the storage address of the image file associated with the target service provider and the organization information of the target service provider are obtained from the above-mentioned queue of pending registrations, the image file associated with the target service provider is queried from the above-mentioned file repository based on the above-mentioned storage address.
[0207] Based on the organization information, create a general parsing container associated with the target service organization in the aforementioned container cluster;
[0208] Based on the image file associated with the aforementioned target service provider, the parsing component provided by the aforementioned target service provider is run in the aforementioned general parsing container.
[0209] Optionally, processor 701 can be used to invoke a computer program stored in memory 705 to execute the creation of a generic parsing container associated with the target service organization in the container cluster based on the organization information, including:
[0210] Using the container creation method, an initial general-purpose parsing container is created in the aforementioned container cluster;
[0211] Based on the above organization information, generate a service address associated with the above target service organization;
[0212] The service address associated with the aforementioned target service provider is associated with the aforementioned initial general resolution container to obtain the general resolution container associated with the aforementioned target service provider.
[0213] Optionally, the processor 701 can be used to invoke a computer program stored in the memory 705 to perform the above method, which further includes:
[0214] Send the second test information to the aforementioned general parsing container;
[0215] When the general parsing container receives the second test response information returned by the general parsing container in response to the second test information, it is determined that the general parsing container is in a working state.
[0216] Remove the aforementioned storage address and organization information from the aforementioned queue of pending registrations.
[0217] Optionally, the processor 701 can be used to invoke a computer program stored in the memory 705 to perform the above method, which further includes:
[0218] The request receiving interface of the aforementioned general identifier management platform is invoked to receive a second registration request for the digital identifier of the business object corresponding to the aforementioned business device; the second registration request carries the object public key of the aforementioned business object and the organization information corresponding to the N service organizations used to generate the digital identifier; the target service organization is any one of the N service organizations; N is an integer greater than 1;
[0219] Based on the organization information of each of the above N service organizations, query the general parsing container corresponding to each of the above service organizations from the above container cluster;
[0220] The parsing components running in the general parsing containers corresponding to the above N service providers generate digital identifiers for the above business objects for the above N service providers based on the object public key of the above business objects.
[0221] Send the digital identifiers corresponding to the above-mentioned N service institutions for the above-mentioned business objects to the above-mentioned business equipment.
[0222] This application provides a universal identifier management platform, which includes a container cluster. Within the container cluster are multiple universal parsing containers associated with different service providers. Each universal parsing container runs a parsing component provided by the corresponding service provider. Therefore, when a parsing request for a digital identifier of a business device is received, based on the organization information of the target service provider in the digital identifier, the platform can query the universal parsing container associated with the target service provider from the container cluster. The parsing component running in the found universal parsing container is then used to parse the digital identifier of the business device. This eliminates the need for the business device to implement additional code modules to interface with the service provider's parsing component, reducing the parsing workload and complexity of the digital identifier. The universal identifier management platform can only parse the encrypted identifier document corresponding to the digital identifier, thus preventing the unauthorized acquisition of information in the identifier document and improving the information security of the identifier document.
[0223] Furthermore, it should be noted that this application also provides a computer-readable storage medium storing a computer program executed by the aforementioned data processing apparatus. This computer program includes program instructions, which, when executed by the processor, enable the execution of the data processing method described in the corresponding embodiments above. Therefore, further details will not be repeated here. Additionally, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer-readable storage medium involved in this application, please refer to the description of the method embodiments of this application.
[0224] As an example, the above program instructions can be deployed and executed on a computer device, or deployed and executed on at least two computer devices in one location, or executed on at least two computer devices distributed in at least two locations and interconnected by a communication network. At least two computer devices distributed in at least two locations and interconnected by a communication network can form a blockchain network.
[0225] The aforementioned computer-readable storage medium may be a data processing apparatus provided in any of the foregoing embodiments or a central storage unit of the aforementioned computer device, such as a hard disk or central storage of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, smart memory card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium may include both the central storage unit and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.
[0226] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish content in different media, rather than to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.
[0227] In practice, the collection and processing of data in this application should strictly comply with the requirements of relevant laws and regulations, obtain the informed consent or separate consent of the data subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the data subject.
[0228] This application also provides a computer program product, including a computer program. When executed by a processor, the computer program implements the data processing method and decoding method described in the preceding embodiments, and therefore will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer program product involved in this application, please refer to the description of the method embodiments of this application.
[0229] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.
[0230] The methods and related apparatus provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowchart and / or structural diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable network-connected device to create a machine, such that the instructions, which execute via the processor of the computer or other programmable network-connected device, generate instructions for implementing the process. Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable network-connected device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable network-connected device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 A process or multiple processes and / or structures illustrate the steps of the functions specified in one or more boxes.
[0231] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application. < / method-specific-id>
Claims
1. A data processing method, characterized in that, include: Call the request receiving interface of the general identifier management platform to receive the parsing request for the digital identifier of the business device; The digital identifier includes organizational information of the target service provider that generated the digital identifier; Based on the organization information, query the general parsing container associated with the target service organization from the container cluster of the general identifier management platform; the container cluster includes general parsing containers associated with multiple service organizations respectively, the target service organization is any one of the multiple service organizations, and each general parsing container runs a parsing component provided by the corresponding service organization; The parsing component running in the general parsing container associated with the target service provider parses the digital identifier of the business device to obtain the encrypted identifier document corresponding to the digital identifier of the business device. The encrypted identifier document corresponding to the digital identifier of the service device is sent to the service device; the service device is used to decrypt the encrypted identifier document to obtain the identifier document corresponding to the digital identifier of the service device.
2. The method according to claim 1, characterized in that, The step of querying the universal resolution container associated with the target service organization from the container cluster of the universal identifier management platform based on the organization information includes: Obtain the service address template of the general resolution container in the container cluster of the general identifier management platform; Add the organization information to the service address template to obtain the service address of the general resolution container associated with the target service organization; Based on the service address, query the general resolution container associated with the target service provider from the container cluster of the general identifier management platform.
3. The method according to claim 2, characterized in that, The step of querying the universal resolution container associated with the target service provider from the container cluster of the universal identifier management platform based on the service address includes: Send the first test information to the general resolution container with the service address in the container cluster of the general identifier management platform; When the first test response information returned by the general parsing container with the service address in response to the first test information is received, it is determined that the general parsing container with the service address is in a working state. The generic resolution container that has the service address and is in a working state is identified as the generic resolution container associated with the target service provider.
4. The method according to claim 1, characterized in that, The method further includes: The request receiving interface of the general identifier management platform is invoked to receive a first registration request for the parsing component of the target service organization; the first registration request carries an image file and the organization information of the target service organization, wherein the image file is obtained by packaging the parsing component of the target service organization; Based on the image file and the organization information, a general parsing container associated with the target service organization is created in the container cluster, and the parsing component provided by the target service organization is run in the general parsing container.
5. The method according to claim 4, characterized in that, The step of creating a generic parsing container associated with the target service organization in the container cluster based on the image file and the organization information, and running the parsing component provided by the target service organization in the generic parsing container, includes: The image file is stored in the file repository of the general identifier management platform, and the storage address of the image file in the file repository is obtained; Based on the organization information, determine the registration status of the general parsing container associated with the target service organization in the container cluster; When the registration status of the general parsing container associated with the target service organization in the container cluster is unregistered, the storage address and the organization information are added to the registration queue. Based on the queue to be registered, a general parsing container associated with the target service provider is created in the container cluster, and the parsing component provided by the target service provider is run in the general parsing container.
6. The method according to claim 5, characterized in that, The step of creating a general parsing container associated with the target service provider in the container cluster according to the queue to be registered, and running the parsing component provided by the target service provider in the general parsing container, includes: The storage address and organization information are sequentially obtained from the queue of entities to be registered; When the storage address of the image file associated with the target service organization and the organization information of the target service organization are obtained from the queue to be registered, the image file associated with the target service organization is queried from the file repository according to the storage address; Based on the organization information, a generic parsing container associated with the target service organization is created in the container cluster; Based on the image file associated with the target service provider, the parsing component provided by the target service provider is run in the general parsing container.
7. The method according to claim 6, characterized in that, The step of creating a generic parsing container associated with the target service organization in the container cluster based on the organization information includes: Using a container creation method, an initial general-purpose parsing container is created in the container cluster; Based on the organization information, generate a service address associated with the target service organization; The service address associated with the target service provider is associated with the initial general resolution container to obtain a general resolution container associated with the target service provider.
8. The method according to claim 6, characterized in that, The method further includes: Send the second test information to the general parsing container; When the general parsing container receives the second test response information returned by the general parsing container in response to the second test information, it is determined that the general parsing container is in a working state; Remove the storage address and the organization information from the registration queue.
9. The method according to claim 1, characterized in that, The method further includes: The request receiving interface of the general identifier management platform is invoked to receive a second registration request for the digital identifier of the business object corresponding to the business device; the second registration request carries the object public key of the business object and the organization information corresponding to N service organizations used to generate the digital identifier; the target service organization is any one of the N service organizations; N is an integer greater than 1; Based on the organization information of each of the N service organizations, query the general parsing container corresponding to each service organization from the container cluster; The parsing components running in the general parsing containers corresponding to the N service providers generate digital identifiers for the business object corresponding to the N service providers based on the object public key of the business object. The digital identifiers corresponding to the N service providers for the business object are sent to the business device.
10. A data processing apparatus, characterized in that, include: The receiving module is used to call the request receiving interface of the general identifier management platform to receive parsing requests for digital identifiers of business devices; The digital identifier includes organizational information of the target service provider that generated the digital identifier; The query module is used to query the general parsing container associated with the target service organization from the container cluster of the general identifier management platform based on the organization information; the container cluster includes general parsing containers associated with multiple service organizations respectively, the target service organization is any one of the multiple service organizations, and each general parsing container runs a parsing component provided by the corresponding service organization; The processing module is used to parse the digital identifier of the business device through a parsing component running in a general parsing container associated with the target service provider, and obtain an encrypted identifier document corresponding to the digital identifier of the business device; The sending module is used to send the encrypted identifier document corresponding to the digital identifier of the service device to the service device; the service device is used to decrypt the encrypted identifier document to obtain the identifier document corresponding to the digital identifier of the service device.
11. 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 9.
12. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, performs the steps of the method as described in any one of claims 1 to 9.
13. 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 9.