Decentralized identifier-based delegation system and method

The distributed identifier-based delegation system using blockchain technology addresses security and control issues in centralized identity systems by verifying agents and delegators, ensuring secure and accurate identity delegation for legal entities, enhancing security and scalability.

WO2024242405A1PCT designated stage expired Publication Date: 2024-11-28K4-SECURITY CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006674
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-05-16
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

Centralized digital identity systems lack security and control over personal information, leading to potential leaks and inaccuracies in identity verification, especially in corporate and non-human entity contexts, where representative authentication is unverified and public certificate obligations have been abolished.

Method used

A distributed identifier-based delegation system utilizing blockchain technology for self-sovereign identity, which verifies the identity of agents and delegators, issues delegation-type credentials, and performs batch verification for efficient signature validation, ensuring secure and accurate delegation of actions by legal entities like corporations and foundations.

Benefits of technology

This system provides secure, scalable, and efficient identity delegation, ensuring accurate verification and control over personal information, addressing the limitations of centralized models and enabling secure delegation of actions by legal entities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006674_28112024_PF_FP_ABST
    Figure KR2024006674_28112024_PF_FP_ABST
Patent Text Reader

Abstract

The present invention relates to a blockchain-based delegation system and, more specifically, to a decentralized identifier-based delegation system and method capable of performing delegation for a legal entity to perform an action, by applying a blockchain-based decentralized identifier technology that guarantees self-sovereign identity. According to an embodiment of the present invention, a specific action of a legal entity may be delegated to a deputy for a specific period of time on the basis of a decentralized identifier.
Need to check novelty before this filing date? Find Prior Art

Description

Delegation system and method based on distributed identifiers

[0001] The present invention relates to a blockchain-based delegation system, and more particularly, to a distributed identifier-based delegation system and method that can delegate the performance of acts of a legal entity by applying a blockchain-based distributed identifier technology that guarantees self-sovereign identity.

[0002] Digital IDs (DIDs), such as IDs, resident registration numbers, email addresses, addresses, and joint certificates, are used to verify identity online. However, with the advancement of Internet technology, these digital IDs have become increasingly convenient and efficient, while the importance of storage and management technologies for security is also growing. Consequently, digital ID management technologies are also evolving and changing. Initially, with the emergence of numerous websites, the need for repeated user registration procedures for each site led to issues such as the inconvenience of having to register multiple times and the inconvenient management of account information across multiple sites. To address these issues, a centralized model for single sign-on (SSO) was proposed, enabling access to multiple sites with a single login. Furthermore, the centralized model suffers from a lack of scalability, particularly in ID utilization, due to the centralized management of all user information. To address this, the federated model was developed. While both models offer simplified registration and authentication procedures from the user's perspective, they present distinct limitations: they lack security and control over personal information. In other words, digital IDs have security limitations. These limitations force users to provide personal information unrelated to the service, which in turn leads to numerous data leaks. In 2016, Alan Christopher first proposed the Self-Sovereign Identity (SSI) model, which empowers users, the subjects of their personal information, to directly control their data.Based on this, active research is currently underway on decentralized identifiers (DIDs) utilizing distributed ledger technologies (DLTs) such as blockchain. In particular, blockchain-based decentralized identifier (DID) technology is being designed and researched under the leadership of the Decentralized Identity Foundation (DIF), and the technology was recently approved as a web standard by the World Wide Web Consortium (W3C) on July 10, 2022.

[0003] Meanwhile, the public certificate, which was a representative digital authentication technology, had its related obligations removed by the revision of the Electronic Signature Act in December 2020. As a result, it is currently used under the name "joint certificate." However, despite the abolition of this obligation, there is still no realistic way to strongly replace it in some services, so joint certificates are still used in numerous fields such as tax inquiries by the National Tax Service and online banking. Joint certificates have a public key infrastructure (PKI) and are a type of digital ID created by adding the owner's information to the public key required for verification.

[0004] However, the joint certificate system is structurally a centralized model that presupposes a central trust authority (TTP: Trust-Third Party) that securely distributes keys. This presents distinct limitations in efficiency and security. Furthermore, when implementing digital identity-based delegation, which is frequently used in real-world environments, if a representative of a corporation receiving a corporate certificate performs a specific action, the representative's identity is not authenticated. Furthermore, the absence of representative information within the certificate renders accurate identification of the representative impossible. This presents a vulnerability in that it is impossible to verify that the person submitting the corporate certificate is the true representative. In other words, even if a malicious third party obtains the joint certificate file and valid password through social engineering or other attacks, there is no way to verify the authenticity of the proxy. This presents a significant problem, making accurate identification of the proxy impossible. Therefore, in order to complement the fundamental centralized model and the problems in the actual use of joint certificates, a blockchain-based decentralized identifier (DID) technology that can realize self-sovereign identity is essential, and a new delegation model based on a decentralized identifier (DID) that can clearly verify each other and resolve the problems of the aforementioned joint certificates is needed.

[0005] In addition, according to the W3C DID Core v1.0 specification, which is the current decentralized identifier (DID) standard model, there are no restrictions on the issuance target of a decentralized identifier (DID). However, when the owner (Holder) of a decentralized identifier submits a verifiable presentation (VP), a signing action regarding the owner is required, and unless this signing action is performed through an automatic algorithm, the issuance target (owner object) of the decentralized identifier must be a person. In such a restricted environment, it is somewhat unsuitable to apply the current decentralized identifier (DID) model to non-human objects such as corporations, and this requires a DID-based delegation technology for a series of objects such as corporations and foundations.

[0006] The present invention can solve a security problem that occurs when performing digital identity-based delegation of legal entities such as corporations, foundations, schools, and government agencies because information on the delegated agent does not exist in the certificate.

[0007] The present invention provides a distributed identifier-based delegation system and method that delegates authority for a specific action for a specific period of time when an action of a legal entity such as a corporation, foundation, school, or government agency is required, so that the delegated agent can perform the action on behalf of the legal entity.

[0008] The technical problems to be solved by the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0009] According to one aspect of the present invention, a distributed identifier-based delegation system is provided.

[0010] A distributed identifier-based delegation system according to one embodiment of the present invention includes an issuing unit that verifies the identity information of a delegate and a delegator and issues a delegated credential for delegation;

[0011] It may include a verification unit that performs verification by looking up metadata of a distributed identifier and a storage unit that stores metadata of the distributed identifier.

[0012] According to another aspect of the present invention, a distributed identifier-based delegation method and a computer processor executing the same are provided.

[0013] A distributed identifier-based delegation method according to one embodiment of the present invention may include a step of receiving a delegation request from a delegate, a step of issuing a delegated credential, a step of requesting verification for performing a delegation action, a step of verifying that the delegation action is authorized, and a step of causing the delegate to perform the delegation action.

[0014] According to one embodiment of the present invention, a specific action of a legal object can be delegated to a proxy for a specific period of time based on a distributed identifier.

[0015] According to one embodiment of the present invention, detailed verification of a delegated agent can be performed by applying a blockchain-based distributed identifier technology that guarantees self-sovereign identity.

[0016] In addition, according to one embodiment of the present invention, by applying batch verification for multi-signatures, signature verification in cases where multiple participants exist, such as delegation of legal objects, can be performed more efficiently than in existing models.

[0017] According to one embodiment of the present invention, signatures of multiple participants with different signing times and signature verification times are safely encrypted into a single signature, thereby enabling signature verification of a legal object containing the signatures of multiple participants in real time.

[0018] The effects of the present invention are not limited to the above-described effects, and should be understood to include all effects that can be inferred from the composition of the invention described in the description or claims of the present invention.

[0019] Figure 1 is a drawing for explaining the W3C DID v1.0 standard model.

[0020] FIGS. 2 and 3 are drawings for explaining a distributed identifier-based delegation system according to one embodiment of the present invention.

[0021] FIG. 4 is a diagram schematically illustrating a distributed identifier-based delegation method according to one embodiment of the present invention.

[0022] FIGS. 5 to 7 are exemplary drawings of a distributed identifier-based delegation method according to one embodiment of the present invention.

[0023] Figures 8 to 10 are examples of scenarios of a distributed identifier-based delegation system according to one embodiment of the present invention.

[0024] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention. In describing the present invention, detailed descriptions of related known technologies will be omitted if they are determined to unnecessarily obscure the gist of the present invention. Furthermore, the use of the singular forms "a," "an," and "the" in this specification and claims should generally be construed to mean "one or more," unless otherwise specified.

[0025] Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the attached drawings. In describing with reference to the attached drawings, identical or corresponding components are assigned the same drawing numbers, and redundant descriptions thereof will be omitted.

[0026] Figure 1 is a diagram illustrating the W3C DID v1.0 standard model.

[0027] Referring to Figure 1, the decentralized identifier (DID) standard model defined in W3C DID v1.0 consists of an issuer that issues a decentralized identifier (DID) and a verifiable credential (VC), a holder who is issued a decentralized identifier (DID) and a credential (VC) from an issuer that can guarantee the identity of the owner and who owns the DID and the credential (VC), and a verifier that verifies the submitted credentials (VC) to determine whether to provide a service. At this time, metadata for the issued decentralized identifier is stored in a verifiable data registry and searched for verification.

[0028] According to the current W3C DID core v1.0 specification, there are no restrictions on who can issue a decentralized identifier (DID). However, when an owner selects a credential and submits a verifiable presentation (VP), a signing action is required to prove that the presentation is theirs. Unless the signing action is performed through an automated algorithm, the issuance target of a DID must be a person. In this restricted environment, entities granted personality, such as corporations recognized by law as entities with legal capacity, require a proxy to perform certain actions, such as signing.

[0029] FIG. 2 and FIG. 3 are drawings for explaining a distributed identifier-based delegation system according to one embodiment of the present invention.

[0030] Referring to FIG. 2, a distributed identifier-based delegation system (10) can have a delegate (Deputy) delegated with a specific action perform an action when an action by a legal object is required.

[0031] A distributed identifier-based delegation system (10) delegates authority over some actions of a legal entity for a specific period of time, allowing a deputy to perform actions on behalf of the legal entity. The legal entity may include a corporation, foundation, school, government department, organization, etc.

[0032] A delegate is a person who receives a delegation and requires proof of delegation to perform the delegated actions authorized by the principal.

[0033] The Delegator is the object of delegation, and shares delegation information, such as the Delegator's distributed identifier, with the Deputy in advance.

[0034] A Delegator represents a legal entity that receives a corporate ID based on delegated credentials (Delegated VC). Depending on the nature of the legal entity, there may be more than one Delegator.

[0035] The Deputy obtains a delegated credential (Delegated VC) for the purpose of generating a corporate ID, uses it to prove delegation, and requests verification of a delegated credential-based presentation (VP included Delegated VC) to perform delegated actions.

[0036] The distributed identifier-based delegation system (10) issues a delegated credential (Delegated VC) to the delegate for generating a corporate ID for delegation proof, and verifies the delegated credential-based presentation (VP included Delegated VC) submitted by the delegate when a delegation action occurs to determine whether to provide a service.

[0037] The distributed identifier-based delegation system (10) verifies the verifiable presentation (VP) of the delegate, verifies the distributed identifier (DID) of the delegate, and then issues a delegated credential (Delegated VC).

[0038] In order to perform a delegated act, a delegate must create a presentation based on the delegated credential (VP included Delegated VC) and have proof of delegation verified.

[0039] A distributed identifier-based delegation system (10) uses a distributed identifier integrated resolver (DID Resolver) to search for and verify distributed identifier information stored in a verifiable data registry.

[0040] Referring to FIG. 3, a distributed identifier-based delegation system (10) may include a delegator (20), a representative (30), an issuing unit (100), a verification unit (200), an integrated analysis unit (300), and a storage unit (400).

[0041] The issuing unit (100) includes the role of an issuer in the existing distributed identifier standard model, verifies information on the agent and delegator, and issues a delegated credential (Delegated VC) for delegation.

[0042] The issuing unit (100) may be excluded from the delegation target, and the prerequisite before issuing the delegated credential (Delegated VC) is that both the delegator (20) and the delegate (30) must have been issued a key pair, a distributed identifier, and a distributed identifier document (DID Document). In addition, the corporation must have designated a delegate in advance through an internal committee, etc., to create a corporate ID. Assuming that these prerequisites are satisfied, the distributed identifier-based delegation system (10) performs the issuance and verification of the delegated credential (Delegated VC), and the presentation based on the delegated credential (VP included Delegated VC).

[0043] When the issuing unit (100) receives a request for issuing a delegated credential (Delegated VC), it requests the delegate (30) to submit a verifiable presentation (VP), and upon completion of the submission, requests verification from the verification unit (200). The delegate's (30) verifiable presentation (VP) includes a verifiable credential (VC) containing information about the legal relationship with the delegate (20).

[0044] Additionally, the issuing unit (100) requests the verification unit (200) to verify the validity of the delegate distributed identifier (DID) to confirm the delegate (20).

[0045] The issuing unit (100) can issue a delegated credential (Delegated VC) when all verifications are completed.

[0046] The issuing unit (100) issues a delegated credential (Delegated VC) including the issuance date, expiration date, distributed identifiers of the delegate and the delegator, and details about the delegation (field, authorized delegation actions, etc.). The issuing unit (100) can include the signature values ​​of the issuer, delegator, and delegate in the delegated credential (Delegated VC) to prove that it was issued with the consent of the delegator and the delegate. In cases where there are joint names or multiple delegates, the issuing unit (100) can include the signature values ​​of all participants in the delegated VC and issue it.

[0047] The issuing unit (100) can issue and manage a delegated credential (Delegated VC) to prove the delegation of the delegate (30) receiving the delegation. At this time, the issuing unit (100) creates the delegated credential (Delegated VC) by hiding the information of the delegate (30) to be included in the delegated credential (Delegated VC) so as to ensure cryptographic anonymity. For example, the issuing unit (100) can set a validity period for the delegated credential (Delegated VC) and specify the delegation period for the start and end of the delegation so that the delegated credential can be used only during a specific period. In addition, the issuing unit (100) issues a delegated credential (Delegated VC) that can verify the validity of the proof value, authenticate all delegated participants, prevent repudiation, and check for data falsification through the proof of the delegated credential (Delegated VC).

[0048] When a delegate (30) submits a presentation based on delegated credentials (VP ​​included Delegated VC) to perform a delegated act, the delegate (30) can select information from the delegated credential (Delegated VC). Furthermore, the delegate (30) generates a verifiable presentation (VP) based on the delegated credential (Delegated VC) to enable validation of the proof value, authentication of the delegate, non-repudiation, and detection of data falsification through the proof of the delegated credential (Delegated VC).

[0049] The agent (30) must submit a verifiable presentation (VP) of the agent to issue a delegated credential (Delegated VC), and to use the service for delegated acts, must submit a delegated credential-based presentation (VP included Delegated VC) to the verification department (200).

[0050] The verification unit (200) verifies the legal relationship between the principal (20) and the principal (30) based on the principal's verifiable presentation (VP). Once verification is complete, the verification unit (200) notifies the issuing unit (100) of the results. The issuing unit (100) can issue a delegated credential (Delegated VC) if the legal relationship between the principal (20) and the principal (30) is proven.

[0051] In addition, the verification unit (200) verifies and provides evidence of the delegation period and authorized delegation acts of the delegator (20) and the agent (30) through a delegated credential (Delegated VC) that includes information on the legal relationship with the delegator (20). The verification unit (200) verifies and provides evidence of the legal relationship related to delegation between the delegator (20) and the agent (30) through a delegated credential (Delegated VC) that includes information on the legal relationship with the delegator (20) in a delegated credential-based presentation (VP included Delegated VC).

[0052] The verification unit (200) checks the specifications or format of the delegated credential-based presentation (VP included Delegated VC) to determine whether the delegated credential (Delegated VC) is included.

[0053] The verification unit (200) verifies the decentralized identifier (DID) for the delegate (30) and the delegator (20). The verification unit (200) verifies the validity of the decentralized identifier (DID) of the delegate (20) and the delegate (30). The verification unit (200) searches for and verifies a decentralized identifier document (DID Document) stored in a storage unit (400) linked to one or more blockchains through the integrated interpretation unit (300).

[0054] The verification unit (200) verifies the validity of the proof of a verifiable presentation (VP). More specifically, the verification unit (200) retrieves the distributed identifier document (DID Document) of the submitter (agent) stored in the storage unit (400) through the integrated interpretation unit (300) to verify the verifiable presentation. The verification unit (200) verifies the verifiable presentation (VP) using the public key contained in the retrieved distributed identifier document (DID Document) and determines its validity.

[0055] If a verifiable presentation (VP) is valid, the verification unit (200) verifies the verifiable credential (VC) included in the verifiable presentation (VP). The verification unit (200) checks whether the verifiable credential (VC) included in the verifiable presentation (VP) has expired. For example, the verification unit (200) can verify a delegated credential (Delegated VC) included in a delegated credential-based presentation (VP included Delegated VC) and check whether it has expired.

[0056] The verification unit (200) verifies the validity of the signature values ​​for all delegated participants (delegators and representatives). At this time, the verification unit (200) can apply batch verification, which efficiently verifies multiple signature values ​​for the same message. Specifically, through batch verification, the verification unit (200) can efficiently verify the signature values ​​N times, which would otherwise be performed for all N delegated participants, through a single verification.

[0057] The verification unit (200) receives a delegated credential-based presentation (VP included Delegated VC) to perform proof of delegation, and performs verification by retrieving metadata of the corresponding decentralized identifier (DID) from the storage unit (400) via the integrated interpretation unit (300). Through this, the decentralized identifier-based delegation system (10) can determine whether to provide a service.

[0058] The integrated interpretation unit (300) can manage access information for blockchains by managing one or more distributed identifier integrated resolvers (DID Resolvers) in multiple layers. The integrated interpretation unit (300) can access one or more blockchains or heterogeneous blockchains.

[0059] The storage unit (400) is a verifiable data registry (VDR) that stores metadata for decentralized identifiers (DIDs). For example, the storage unit (400) may utilize a blockchain that stores a distributed ledger for a decentralized identifier environment capable of self-sovereign identity verification. The storage unit (400) supports one or more or heterogeneous blockchain environments using the integrated analysis unit (300).

[0060] FIG. 4 is a schematic diagram illustrating a distributed identifier-based delegation method according to one embodiment of the present invention. Each process described below is performed by each functional unit of the distributed identifier-based delegation system. However, for the sake of a concise and clear explanation of the present invention, the entities of each step will be collectively referred to as the distributed identifier-based delegation system.

[0061] Referring to FIG. 4, the decentralized identifier-based delegation system (10) receives a request for delegation, including information about the delegate (30) and the delegator (20), at step S410. For example, the decentralized identifier-based delegation system (10) may submit the delegate's verifiable presentation (Deputy's VP) and the delegator's decentralized identifier (Delegator's DID) together.

[0062] At step S420, the distributed identifier-based delegation system (10) issues a delegated credential (Delegated VC). For example, the distributed identifier-based delegation system (10) verifies the validity of the delegate's verifiable presentation (Deputy's VP) and the delegate's distributed identifier (Delegator's DID) and then issues a delegated credential (Delegated VC). The distributed identifier-based delegation system (10) retrieves the delegate's or delegate's distributed identifier document (DIDDOCU) stored in the storage (400) through the integrated analysis unit (300) and uses it for validity verification.

[0063] At step S430, the distributed identifier-based delegation system (10) is requested to verify the performance of the delegated act by the agent (30).

[0064] At step S440, the distributed identifier-based delegation system (10) generates a delegated credential-based presentation (VP included Delegated VC) that can be verified using the delegate's signature value. For example, the delegated credential-based presentation (VP included Delegated VC) includes the delegation period of the delegate (20) and the delegate (30), the authorized delegation actions, etc., through the delegated credential (Delegated VC) that includes information about the legal relationship between the delegate (20) and the delegate (30).

[0065] At step S450, the decentralized identifier-based delegation system (10) verifies that the requested delegation action is authorized. For example, the decentralized identifier-based delegation system (10) verifies and proves the legal relationship between the delegator (20) and the agent (30) regarding delegation through a delegated credential (Delegated VC) that includes information about the legal relationship with the delegator (20) in a delegated credential-based presentation (VP included Delegated VC). The decentralized identifier-based delegation system (10) can verify the validity of all delegation participants using the decentralized identifier document (DIDDOCU) of the agent, delegator, and issuer.

[0066] At step S460, the distributed identifier-based delegation system (10) allows the agent (30) to perform the delegation action when all verifications are completed.

[0067] FIGS. 5 to 7 are exemplary drawings of a distributed identifier-based delegation method according to one embodiment of the present invention.

[0068] The example in Fig. 5 is a detailed process for issuing a delegated credential (Delegated VC) by a distributed identifier-based delegation system (10).

[0069] Referring to FIG. 5, a distributed identifier-based delegation system (10) can issue delegated credentials (Delegated VC). More specifically, the issuing unit (200) can issue delegated credentials (Delegated VC) at the request of a delegate (30).

[0070] At step S4200, the agent (30) requests the issuing unit (100) to issue a delegated credential. At this time, the agent (30) must submit information that can verify the delegator and the delegated agent. For example, the agent's verifiable presentation (VP) and the delegator's decentralized identifier (DID) must be submitted for agent identity verification. The submitted agent's verifiable presentation (VP) includes personal information that satisfies legal requirements and personal information that can prove the legal relationship with the agent.

[0071] At step S4210, the issuing unit (100) requests verification of the received verifiable presentation (Deputy's VP) from the verification unit (200) to confirm the delegate (30).

[0072] To explain in detail, in step S4211, the verification unit (200) interprets the Deputy's distributed identifier (Deputy's DID) through the integrated interpretation unit (300) to verify the Deputy's verifiable presentation (Deputy's VP).

[0073] In steps S4212 to S4214, the verification unit (200) searches for the distributed identifier document (Deputy's DIDDOCU) of the submitter (delegate) stored in the storage unit (400).

[0074] In step S4216, the verification unit (200) determines validity by performing verification of the verifiable presentation (Deputy's VP) of the delegate using the public key included in the retrieved distributed identifier document (Deputy's DIDDOCU).

[0075] In step S4217, the verification unit (200) transmits the verification result to the issuer (100).

[0076] In step S4220, the issuing unit (100) performs validation through the Delegator's distributed identifier (DID).

[0077] In step S4221, the issuing unit (100) interprets the Delegator's distributed identifier (DID) through the integrated interpretation unit (300).

[0078] In steps S4222 to S4224, the verification unit (200) searches for the Delegator's distributed identifier document (Delegator's DIDDOCU) stored in the storage unit (400).

[0079] At step S4226, the verification unit (200) determines validity through the Delegator's distributed identifier (DID).

[0080] If the verification result is valid, the issuing unit (100) can issue a delegated credential (Delegated VC) based on the presentation internal information and the delegation information in step S4230. For example, the delegated credential (Delegated VC) may include not only the issuance period and expiration period, but also the distributed identifiers of the delegate and the delegator, time information indicating the start and end of the delegation period, and detailed information about the delegation (field, delegation act, etc.). The detailed information about the delegation is composed of information that meets the legal requirements of a general power of attorney. In addition, as with the existing distributed identifier model, the authority to issue the credential (VC) belongs to the issuer, and the issuance of the delegated credential (Delegated VC) includes all important proof elements that the delegate who delegated and the delegate who received the delegation proceeded together. Therefore, the distributed identifier-based delegation system (10) may include the signature values ​​of the issuer, the delegator, and the delegate to prove the delegated credential (Delegated VC). Additionally, the distributed identifier-based delegation system (10) can be configured with the total number of participants involved in delegation and the corresponding signature value for cases where there are joint names or multiple delegators.

[0081] In the case of issuing delegated credentials in a decentralized identifier-based delegation system (10), the issuer can create the credentials while hiding the delegate's information to be included in the credentials so as to ensure cryptographic anonymity. In addition, the decentralized identifier-based delegation system (10) can set a validity period for the credential (VC) and specify the delegation period for the start and end of the delegation so that it can be used only during a specific period. In addition, the decentralized identifier-based delegation system (10) can verify the validity of the proof value, authentication of all delegation participants, non-repudiation, and data tampering through proof of the delegated credential (Delegated VC).

[0082] In step S4240, the issuing unit (100) transfers the issued delegated credential (Delegated VC) to the agent (30).

[0083] The example in Fig. 6 is a detailed process for a distributed identifier-based delegation system (10) to issue a delegated credential-based presentation (VP included Delegated VC).

[0084] Referring to FIG. 6, at step S4400, the agent (30) is issued a delegated credential-based presentation (VP included Delegated VC).

[0085] To explain in detail, in step S4410, the agent (30) selects one or more delegated credentials (Delegated VC) including the issued delegated credentials (Delegated VC).

[0086] At step S4420, the proxy (30) uses the proxy's (30) signature in the proof of the delegated credential-based presentation (VP included Delegated VC). Since the presentation issuing authority lies with the submitter (proxy), the proof of the delegated credential-based presentation (VP included Delegated VC) consists of the proxy's (30) signature value.

[0087] When a delegated credential-based presentation (VP included Delegated VC) is issued in a distributed identifier-based delegation system (10), the delegate (30) can selectively hide information. The distributed identifier-based delegation system (10) can verify the validity of the proof value, authentication of the delegate (30), non-repudiation, and data tampering through the proof of the delegated credential-based presentation (VP included Delegated VC) in the same way as the proof of the delegated credential (Delegated VC).

[0088] When verifying a delegated credential-based presentation (VP included Delegated VC) in a distributed identifier-based delegation system (10), the verification unit (200) can perform validity verification without obtaining any personal information about the delegate's information.

[0089] The example in Fig. 7 is a detailed process for verifying a delegated credential-based presentation (VP included Delegated VC) by a distributed identifier-based delegation system (10).

[0090] The verification unit (200) checks the specifications of the delegated credential-based presentation (VP included Delegated VC) and determines whether a delegated credential (Delegated VC) is included.

[0091] And, the verification unit (200) searches for the distributed identifier document (Deputy's DIDDOCU) of the submitter (delegate) through the integrated interpretation unit (300) to verify the delegated credential-based presentation (VP included Delegated VC).

[0092] The distributed identifier-based delegation system (10) can perform verification of a delegated credential-based presentation (VP included Delegated VC) through a public key included in a retrieved document (Deputy's DIDDOCU) and determine its validity.

[0093] Referring to FIG. 7, a distributed identifier-based delegation system (10) can verify a delegated credential-based presentation (VP included Delegated VC).

[0094] At step S4510, the agent (30) submits a delegated credential-based presentation (VP included Delegated VC) to the verification unit (200) for delegation proof.

[0095] The verification unit (200) performs a thorough verification of the delegated credential-based presentation (VP included Delegated VC). Specifically, the verification unit (200) verifies the distributed identifiers (DIDs) of the delegate, delegator, and issuer, and uses the distributed identifier document (DIDDOCU) to verify the validity of all delegated participants and the delegated credential-based presentation (VP included Delegated VC).

[0096] First, in step S4511, the verification unit (200) interprets the Deputy's distributed identifier (DID) through the integrated interpretation unit (300).

[0097] At step S4512, the integrated analysis unit (300) requests the distributed identifier document (Deputy's DIDDOCU) of the submitter (delegate) stored in the storage unit (400).

[0098] In step S4513, the storage unit (400) searches for and retrieves the distributed identifier document (Deputy's DIDDOCU) of the submitter (delegate).

[0099] In steps S4514 and S4515, the verification unit (200) searches for the distributed identifier document (Deputy's DIDDOCU) through the integrated interpretation unit (300).

[0100] At step S4516, the verification unit (200) verifies the delegated credential-based presentation (VP included Delegated VC) using the public key of the distributed identifier document (Deputy's DIDDOCU).

[0101] If it is invalid, it means that the presentation based on the delegated credential of the agent (30) is not a VP included Delegated VC or has been tampered with.

[0102] In step S4521, the verification unit (200) interprets the Delegator's distributed identifier (DID) through the integrated interpretation unit (300).

[0103] At step S4522, the integrated analysis unit (300) requests the Delegator's distributed identifier (DID) stored in the storage unit (400).

[0104] In step S4523, the storage unit (400) searches for and retrieves the Delegator's distributed identifier document (Delegator's DIDDOCU).

[0105] In steps S4524 and S4525, the verification unit (200) searches for the Delegator's distributed identifier document (Delegator's DIDDOCU) through the integrated interpretation unit (300).

[0106] At step S4526, the verification unit (200) checks the validity of the delegated credential-based presentation (VP included Delegated VC) using the public key of the delegater's distributed identifier document (Delegator's DIDDOCU).

[0107] In step S4531, the verification unit (200) interprets the issuer's distributed identifier (Issuer's DID) through the integrated interpretation unit (300).

[0108] At step S4532, the integrated interpretation unit (300) requests the issuer's distributed identifier (Issuer's DID) stored in the storage unit (400).

[0109] In step S4533, the storage unit (400) searches for and retrieves the issuer's distributed identifier document (Issuer's DIDDOCU).

[0110] In steps S4534 and S4525, the verification unit (200) searches for the issuer's distributed identifier document (Issuer's DIDDOCU) through the integrated interpretation unit (300).

[0111] At step S4536, the verification unit (200) checks the validity of the delegated credential-based presentation (VP included Delegated VC) using the public key of the issuer's distributed identifier document (Issuer's DIDDOCU).

[0112] If all validation checks in the preceding steps are passed, the verification unit (200) verifies the delegated credential (Delegated VC) in step S4537. In the case of the delegated credential (Delegated VC), the distributed identifier-based delegation system (10) must verify the validity of the signature value for all participants. Batch verification is applied to efficiently verify multiple signature values ​​for the same message. Through batch verification, the distributed identifier-based delegation system (10) can efficiently verify the signature value N times that must be performed for all N participants through a single verification.

[0113] At step S4540, the verification unit (200) transmits the verification result of the delegated credential (Delegated VC) to the agent (30).

[0114] FIG. 8 is an example of a delegated credential issuance scenario for generating a corporate ID in a distributed identifier-based delegation system according to an embodiment of the present invention.

[0115] Referring to FIG. 8, the distributed identifier-based delegation system (10) 1. receives a request for issuing a delegated credential (Delegated VC), 2. verifies the verifiable presentation (Deputy's VP) of the delegate, 3. verifies the validity of the delegate's distributed identifier (Delegator's DID), and then 4. issues a delegated credential (Delegated VC).

[0116] 1. Delegated Credential Issuance Request Scenario

[0117] 1-1. The agent (30) requests the issuing department (100) to issue a delegated credential (Delegated VC) to create a corporate ID.

[0118] 1-2. The issuing department (100) requests the delegate (30) to submit the delegate's decentralized identifier (Delegator's DID) to verify the delegate.

[0119] 1-3. The delegate (30) submits the delegate's decentralized identifier (DID) to the issuing department (100).

[0120] 1-4. In order to issue a delegated credential (Delegated VC) to create a corporate ID for a delegate (30), the identity of the delegate (30) must be verified, so the issuing department (100) requests the delegate (30) to submit a verifiable presentation (Deputy's VP).

[0121] 1-5. The agent (30) submits his / her verifiable presentation (Deputy's VP) to the verification unit (200). At this time, the verification unit (200) verifies the identity of the issuer and the agent through the verifiable credential (VC) that contains information about the legal relationship with the principal (corporation) in the agent's verifiable presentation (Deputy's VP).

[0122] 2. Verification Scenario for Deputy's Verifiable Presentation (VP)

[0123] 2-1. The issuing department (100) requests the verification department (200) to verify the deputy's verifiable presentation (VP).

[0124] 2-2. The verification unit (200) verifies the Deputy's distributed identifier (DID) through the integrated interpretation unit (300).

[0125] 2-3. The integrated interpretation unit (300) requests the deputy's distributed identifier document (Deputy's DIDDOCU) from the storage unit (400).

[0126] 2-4. The storage unit (400) searches for the Deputy's distributed identifier document (Deputy's DIDDOCU).

[0127] 2-5. The storage unit (400) returns the searched delegate's distributed identifier document (Deputy's DIDDOCU) to the integrated interpretation unit (300).

[0128] 2-6. The integrated interpretation unit (300) returns the Deputy's distributed identifier document (Deputy's DIDDOCU) to the verification unit (200).

[0129] 2-7. The verification unit (200) verifies the verifiable presentation (Deputy's VP) of the agent using the agent's distributed identifier document (Deputy's DIDDOCU). This verifies the identity of the agent (30). For example, the verifiable presentation (VP) contains a verifiable credential (VC) that includes information about the legal relationship with the corporation, such as a series of employee numbers or proof of employment. The verification unit (200) verifies the legal relationship between the principal (corporation) and the agent (30) using this verifiable credential (VC).

[0130] 2-8. The verification unit (200) transmits the verification result of the deputy's verifiable presentation (Deputy's VP) to the issuing unit (100).

[0131] 3. Delegator's Decentralized Identifier (DID) Validation Scenario

[0132] 3-1. The issuing unit (100) requests verification of the Delegator's distributed identifier (DID) from the verification unit (200).

[0133] 3-2. The verification unit (200) verifies the Delegator's distributed identifier (DID) through the integrated interpretation unit (300).

[0134] 3-3. The integrated interpretation unit (300) requests the delegator's distributed identifier document (Delegator's DIDDOCU) from the storage unit (400).

[0135] 3-4. The storage unit (400) searches for the Delegator's distributed identifier document (Delegator's DIDDOCU).

[0136] 3-5. The storage unit (400) returns the searched delegate's distributed identifier document (Delegator's DIDDOCU) to the integrated interpretation unit (300).

[0137] 3-6. The integrated interpretation unit (300) returns the delegator's distributed identifier document (Delegator's DIDDOCU) to the verification unit (200).

[0138] 3-7. The verification unit (200) transmits the verification result of the Delegator's decentralized identifier (DID) to the issuing unit (100).

[0139] 4. Delegated Credential Issuance Scenario

[0140] 4-1. Based on the verification procedures of 1, 2, and 3 above, the issuing department (100) issues a delegated credential (Delegated VC) for corporate ID.

[0141] 4-2. The issuing department (100) transmits the delegated credential (Delegated VC) for the issued corporate ID to the agent (30).

[0142] The issued delegated credential (Delegated VC) specifically defines the delegation information. For example, the "Type" of the "CredentialSubject" can be defined as "CorporateCredential," and the "CredentialSubject" can define the information of the delegator (20) and the delegate (30), the delegation period, the validity period of the corresponding credential (VC), etc. After defining all related properties, signing is performed, and the signature value is defined in the "Proof" property. Since the delegated credential (Delegated VC) is a method based on delegation consisting of the delegator (corporation, 20) and the delegate (30), recording that the delegator (corporation, 20) and the delegate (30) performed the transaction together is one of the important elements. Therefore, the signature value of a delegated credential (Delegated VC) can be composed as {sig1: "Issuer's signature", sig2: "Delegate's signature", sig3: "Delegate's signature"}. In this case, there can be one or more delegates, and the signature value must include the signatures of all delegates.

[0143] FIG. 9 is an example of a delegated credential issuance scenario for joint name-based corporate ID generation in a distributed identifier-based delegation system according to an embodiment of the present invention.

[0144] If a corporation is under a single name, a single agent (30) may possess the authority to delegate, but if a corporation is under a joint name, there may be more than one agent (30). If there are N agents (30), a representative agent is set among the N agents, and it is assumed that the representative agent has been issued an ID for creating a joint name corporation ID.

[0145] Referring to FIG. 9, the distributed identifier-based delegation system (10) 1. receives a request for issuing a jointly-named delegated credential, 2. verifies the verifiable presentation (Deputy's VP) of all delegates, 3. verifies the validity of the delegate's distributed identifier (Delegator's DID), and then 4. issues a jointly-named delegated credential (Delegated VC).

[0146] When issuing a jointly-named delegated credential, since there is more than one proxy, the verification unit (200) must verify the verifiable presentation (Deputy's VP) of all N proxies. The verification unit (200) verifies the identity of all proxies.

[0147] In addition, when there are N delegates, the distributed identifier-based delegation system (10) can specify the "Type" of the "CredentialSubject" of the joint delegated credential (Delegated VC) as "Join1tTenancyCorporateCredential". In addition, the signature value of the joint delegated credential (Delegated VC) can be configured as {sig1: "Issuer's signature", sig2: "Delegate's signature", sig3: "Delegate 1's signature", ···, sig(N+2): "Delegate N's signature"}. The signature value of the joint delegated credential (Delegated VC) must include the signatures of all delegates. At this time, the group of N delegates receives the signatures of other delegates under the leadership of the representative delegate, and then specifies them in the "Proof" attribute to generate the final joint delegated credential (Delegated VC).

[0148] FIG. 10 is an example of a delegated credential-based presentation issuance and verification scenario of a distributed identifier-based delegation system according to an embodiment of the present invention.

[0149] Referring to FIG. 10, the distributed identifier-based delegation system (10) includes the steps of 1. issuing a delegated credential-based presentation (VP included Delegated VC), 2. verifying a delegated credential-based presentation (VP included Delegated VC), and 3. verifying a delegated credential (Delegated VC).

[0150] 1. Presentation issuance scenario based on delegated credentials

[0151] 1-1. Check the specifications of the delegated credential (Delegated VC).

[0152] 1-2. Add the delegated credential to the "VerifiableCredential" property in the delegated credential-based presentation.

[0153] 1-3. Enter the delegate signature value in the "Proof" property in the delegated credential-based presentation.

[0154] 2. Delegated Credential-Based Presentation (VP Included Delegated VC) Verification Scenario

[0155] 2-1. Submit a presentation based on delegated credentials (VP ​​included Delegated VC) to the Verification Department (200).

[0156] 2-2. The verification unit (200) verifies the specifications for the delegated credential-based presentation (VP included Delegated VC).

[0157] 2-3. The verification unit (200) checks the validity of the distributed identifier document (DIDDOCU) for the distributed identifier (DID) of the agent (30) and verifies the agent signature of the delegated credential-based presentation (VP included Delegated VC).

[0158] 3. Delegated Credential Verification Scenario

[0159] 3-1. The verification unit (200) checks the validity of the distributed identifier (DID) of the issuing unit (100) specified in the delegated credential by looking up the distributed identifier document (DIDDOCU) and extracting the issuer's public key.

[0160] 3-2. The verification unit (200) checks the validity of the distributed identifier document (DIDDOCU) for the distributed identifier (DID) of the delegator (20) specified in the delegated credential, and extracts the public key of the delegator.

[0161] 3-3. The verification unit (200) checks the validity of the distributed identifier document (DIDDOCU) for the distributed identifier (DID) of one or more delegates (30) specified in the delegated credential, and extracts the delegate's public key.

[0162] 3-4. The verification unit (200) performs batch verification (once) using the extracted public key. Specifically, it verifies the specifications of the delegated credential (Delegated VC), the issuance and expiration periods, and the validity of the delegation period.

[0163] The above-described distributed identifier-based delegation system and method may include one or more processors, memories, user interface input devices, user interface output devices, and storage that communicate with each other via a bus. In addition, the distributed identifier-based delegation system and method may further include a network interface connected to a network. The processor may be a central processing unit or a semiconductor device that executes programs or processing instructions stored in the memory or storage. The memory and storage may be a storage medium including at least one of a volatile medium, a non-volatile medium, a removable medium, a non-removable medium, a communication medium, or an information transmission medium. The memory may include a ROM or a RAM. For example, the present invention may receive a user's request and information through a user interface input device and store them in a storage medium, process the request through one or more processors, and then store necessary data in the storage medium. The processing result of the request may be shared through a user interface output device.

[0164] The above-described distributed identifier-based delegation method can be implemented as computer-readable code on a computer-readable medium. The computer-readable storage medium can be, for example, a removable storage medium (CD, DVD, Blu-ray disc, USB storage device, removable hard disk) or a fixed storage medium (ROM, RAM, computer-attached hard disk). The computer program recorded on the computer-readable storage medium can be transmitted to another computing device via a network such as the Internet and installed on the other computing device, thereby allowing it to be used on the other computing device.

[0165] Although all components constituting the embodiments of the present invention have been described as being combined or operating in combination as one, the present invention is not necessarily limited to such embodiments. That is, within the scope of the present invention, all of the components may be selectively combined and operated one or more times.

[0166] Although operations are illustrated in the drawings in a specific order, this should not be construed as requiring that the operations be executed in the specific order illustrated, or in any sequential order, or that all illustrated operations must be executed to achieve the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various components in the embodiments described above should not be construed as requiring such separation, and it should be understood that the described program components and systems can generally be integrated together into a single software product or packaged into multiple software products.

[0167] The present invention has been described above, focusing on specific embodiments thereof. Those skilled in the art will appreciate that the present invention can be implemented in modified forms without departing from its essential characteristics. Therefore, the disclosed embodiments should be considered illustrative rather than limiting. The scope of the present invention is set forth in the claims, not the foregoing description, and all differences within the scope equivalent thereto should be construed as being encompassed by the present invention.

[0168] The mode for carrying out the invention has been described together with the best mode for carrying out the invention above.

[0169] The present invention has industrial applicability because it addresses security issues that arise when performing digital identity-based delegation for legal entities such as corporations, foundations, schools, and government agencies due to the absence of information about the delegated agent in the certificate. Furthermore, the present invention allows multiple delegates to be designated in cases of jointly owned entities, and the delegation is performed through identity verification of all delegates, making it highly applicable to industrial use.

Claims

1. In a distributed identifier-based delegation system, An issuing unit that verifies the identity of the agent and the delegate and issues a delegated credential for the delegated authority; A verification unit that performs verification by looking up metadata of a distributed identifier; and A distributed identifier-based delegation system including a storage unit that stores metadata of the distributed identifier.

2. In paragraph 1, The above issuing department A decentralized identifier-based delegation system that issues delegated credentials for legal entities.

3. In paragraph 1, The above verification department A decentralized identifier-based delegation system that verifies delegated credential-based presentations (VPs) submitted by agents to perform delegated actions.

4. In paragraph 1 The above delegated credentials are A decentralized identifier-based delegation system that includes at least one of the following: an issuance period, an expiration period, decentralized identifiers of the delegate and the delegator, time information indicating the start and end of the delegation period, a delegation field, and a delegation action.

5. In paragraph 1, The above delegated credentials are A distributed identifier-based delegation system including information on one or more delegates when the delegates are joint holders.

6. In the delegation method performed by the distributed identifier-based delegation system, Steps to receive a request for delegation from an agent; Steps for issuing delegated credentials; A step in which verification is requested for the performance of a delegated act; A step of verifying that the above delegated act is permitted; and A distributed identifier-based delegation method comprising a step of causing a delegate to perform a delegated act.

7. In paragraph 6 The steps for receiving a request for delegation from the above agent are A decentralized identifier-based delegation method that utilizes the verifiable presentation of the delegate and the decentralized identifier of the delegator.

8. In paragraph 6, The steps for receiving a request for delegation from the above agent are A decentralized identifier-based delegation method for requesting delegation to legal objects.

9. In paragraph 6, The above delegated credentials are A distributed identifier-based delegation method including information on one or more delegates when the delegates are joint holders.

10. In paragraph 6 The above delegated credentials are A delegation method based on a distributed identifier that includes at least one of the following: an issuance period, an expiration period, a distributed identifier of the delegate and the delegator, time information indicating the start and end of the delegation period, a delegation field, and a delegation action.

11. A computer program recorded on a computer-readable recording medium that executes the distributed identifier-based delegation method of Article 6.

Citation Information

Patent Citations

  • Artificial disc for spinal disease

    KR1020240150167A

  • Method for obtaining one-time authentication information for authentication based on blockchain

    KR102044749B1

  • Low power greenhouse system with double layered plate for water membrane

    KR102388899B1

  • Data authorization based on decentralized identifiers

    US20210256505A1

  • Information processing device, authentication system, authentication method, and recording medium for recording computer program

    WO2017033442A1