Device and method

The apparatus and method enhance the reliability verification of VC issuers by using issuer identity verification information to confirm their existence and trustworthiness within a DID/VC platform, addressing the lack of clarity in existing methods.

WO2026239431A1PCT designated stage Publication Date: 2026-11-19NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/017160
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-12
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing methods for verifying the reliability of a Verifiable Credential (VC) issuer on a DID/VC platform lack clarity and require a different approach beyond chaining certifications by higher authorities.

Method used

An apparatus and method that includes an issuing unit to provide first verification information based on issuer identity verification and a verification unit to collate this information with second information from a verifier, confirming the issuer's existence and reliability through a decentralized identifier (DID) platform.

Benefits of technology

This approach enables reliable verification of the issuer, enhancing trustworthiness by preventing tampering and impersonation, thus ensuring the integrity of the verification process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025017160_19112026_PF_FP_ABST
    Figure JP2025017160_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure provides technology whereby the credibility of an issuer of verifiable credentials (VC) can be verified. A third party device 10 according to one aspect of the present disclosure comprises: an issuing unit 12 that, on the basis of identity confirmation information of an issuer of a decentralized identifier (DID) / VC, issues first information related to verification of a device of the issuer; and a comparing unit 13 that acquires second information relating to verification from a device of a verifier of the DID / VC, and compares the first information relating to verification with the second information relating to verification.
Need to check novelty before this filing date? Find Prior Art

Description

Apparatus and Method

[0001] The present invention relates to an apparatus and a method.

[0002] On a DID / VC (Decentralized Identifier / Verifiable Credentials) platform, verification of a VC is possible using the electronic signature of an issuer. However, a method for verifying the reliability of the issuer has not been clarified.

[0003] Patent Document 1 discloses a technique for verifying the reliability of a VC issuing authority by using a VC issued by a higher authority above the issuing authority. The technique described in Patent Document 1 chains the certifications of VC issuing authorities.

[0004] Japanese Unexamined Patent Application Publication No. 2025-004321

[0005] There is a demand for verifying the reliability of a VC issuer using a method different from that of Patent Document 1.

[0006] An objective of the present disclosure is to provide a technique capable of verifying the reliability of a VC issuer.

[0007] An apparatus according to one aspect of the present disclosure includes an issuing unit that issues first information related to verification to an issuer's apparatus based on issuer identity verification information in DID / VC, and a verification unit that acquires second information related to verification from a verifier's apparatus in DID / VC and collates the first information related to verification with the second information related to verification.

[0008] In the apparatus according to one aspect of the present disclosure, the first information related to verification backed by the issuer's identity verification information is issued to the issuer's apparatus. In DID / VC, information is passed from the issuer's apparatus to the verifier's apparatus via the VC. Then, the issued first information related to verification is collated with the second information related to verification acquired from the verifier's apparatus. The collation can confirm that the issuer exists and is reliable. As a result, the reliability of the VC issuer can be verified.

[0009] According to the present disclosure, it is possible to provide a technique capable of verifying the reliability of an issuer.

[0010] Figure 1 is a schematic diagram showing an example of the overall configuration of the verification system. Figure 2 is a diagram showing an example of the first information related to identity verification and verification. Figure 3 is a sequence diagram showing an example of the operation of the verification system. Figure 4 is a sequence diagram showing another example of the operation of the verification system. Figure 5 is a diagram showing an example of the hardware configuration of the verification system.

[0011] Embodiments of this disclosure will be described with reference to the attached drawings. Where possible, the same parts will be denoted by the same reference numerals, and redundant descriptions will be omitted.

[0012] Figure 1 shows an example of the overall configuration of Verification System 1. Verification System 1 is applied to a DID / VC platform. In this disclosure, DID is an identifier that enables a particular entity to have self-sovereignty. The type of VC is not limited. For example, VC may be data that proves educational background, work history, or identity.

[0013] Verification system 1 comprises VDR2 (Verifiable Data Registry), issuer device 3, holder device 4, verifier device 5, and third-party device 10 (device). VDR2, issuer device 3, holder device 4, verifier device 5, and third-party device 10 are communicated to a network.

[0014] VDR2 functions as a registry in DID / VC. VDR2 may be configured, for example, by a blockchain. VDR2 manages the DID documents of a particular entity. A DID document contains the DID and public key of a particular entity.

[0015] Issuer device 3 is the issuer device in DID / VC. Issuer device 3 issues VC to holder device 4. The issuer may be a natural person or a legal entity. For example, the issuer may be a company, an educational institution, or a public institution. Issuer device 3 may be, for example, a server device.

[0016] The issuer device 3 manages the issuer's DID, the issuer's public key, and the issuer's private key. The issuer device 3 registers the issuer's DID document 21 with VDR2. The issuer's DID document 21 includes the issuer's DID and the issuer's public key.

[0017] Holder device 4 is the Holder's device in DID / VC. Holder device 4 holds the VC issued by issuer device 3. Holder device 4 presents (transmits) the VC to verifier device 5. The holder may be a natural person. Holder device 4 may be, for example, a personal computer, smartphone, tablet terminal, or wearable device terminal.

[0018] The holder device 4 manages the holder's DID, VC, the holder's public key, and the holder's private key. The holder device 4 registers the holder's DID document 22 with VDR2. The holder's DID document 22 includes the holder's DID and the holder's public key.

[0019] Verifier device 5 is the verifier device in DID / VC. Verifier device 5 verifies the VC presented by holder device 4. The verifier may be a natural person or a legal entity. For example, the verifier may be a company, educational institution, or public institution. Verifier device 5 may be, for example, a server device.

[0020] Third-party device 10 is a device that verifies the authenticity of the issuer. Third-party device 10 may be independent of the DID / VC platform. Third-party device 10 verifies the presence of the issuer on the DID / VC platform. The third party may be a company or organization, an educational institution or a public institution. The third party may provide services that require verification of the issuer's identity. For example, the third party may provide communication services with the issuer as the subscriber. Third-party device 10 may be, for example, a server device. Third-party device 10 may manage the third party's public key and the third party's private key.

[0021] The third-party device 10, in response to a request from the issuer device 3, issues verification information to the issuer device 3. The verification information is information that uniquely identifies the issuer. The third-party device 10 stores the verification information as the reference data (first data) for verification.

[0022] Issuer device 3 issues a VC containing verification information to holder device 4. The VC may include a contact for inquiries regarding verification information. The contact for inquiries regarding verification information may be, for example, the global FQDN (Fully Qualified Domain Name) of third-party device 10. Holder device 4 presents the VC to verifier device 5. Verifier device 5 extracts verification information from the VC. Verifier device 5 presents the verification information to third-party device 10 as comparison data (second data) for verification.

[0023] The third-party device 10 verifies whether an issuer exists by comparing the issued verification information (first data) with the acquired verification information (second data). The third-party device 10 transmits the verification result to the issuer device 3.

[0024] The third-party device 10 includes a storage unit 11, an issuing unit 12, and a verification unit 13 as functional elements.

[0025] The memory unit 11 is a non-temporary storage device that stores various types of information used in the verification system 1. For example, the memory unit 11 stores the issuer's identity verification information. The identity verification information may be a driver's license or an official document such as a company register. The identity verification information may also be SIM (Subscriber Identity Module) contract information under the Telecommunications Business Act. In one example, the SIM contract information of a corporation may include a telephone number, the name of the contracting corporation, and a registration ID. The memory unit 11 may also store verification information issued by the issuing unit 12, which will be described later (hereinafter referred to as "first verification information"). The memory unit 11 may be a component of the third-party device 10, or it may be located in a computer system separate from the third-party device 10.

[0026] The issuing unit 12 issues first verification information to the issuing device 3 based on the issuer's identity verification information. The first verification information is confirmed by the identity verification information to verify the existence of the issuer. The first verification information may also be an Issuer verification ID, which is an identifier that uniquely identifies the issuer. The first verification information may include some or all of the identity verification information. The issuing unit 12 may store the first verification information in the storage unit 11.

[0027] The matching unit 13 obtains information related to verification (hereinafter referred to as "second verification information") from the verifier device 5 and verifies the existence of the issuer by comparing the first verification information and the second verification information. The first verification information is the standard data (first data) issued by the issuer unit 12. The second verification information is the comparison data (second data) presented by the verifier device 5. If the matching results match, the matching unit 13 determines that the issuer exists. If the matching results do not match, the matching unit 13 determines that the issuer does not exist. The verification result may also be information indicating whether the matching matches or does not match.

[0028] Figure 2 shows an example of first information relating to identity verification and verification. For example, the storage unit 11 may store corporate SIM contract information as the issuer's identity verification information. The SIM contract information may include the issuer's telephone number, the name of the contracting corporation, and the registration ID. The storage unit 11 may store first information relating to verification in association with the identity verification information. The first information relating to verification may be an Issuer Verification ID. In one example, the storage unit 11 may store an Issuer Verification ID "V1" in association with the registration ID "0001".

[0029] An example of the operation method (verification method) of the verification system 1 will be explained with reference to Figure 3. Figure 3 is a sequence diagram showing an example of the operation of the verification system 1 as flow M1.

[0030] In step S1, the issuer device 3 requests the third-party device 10 to issue an Issuer Verification ID. For example, the issuer device 3 presents identity verification information (such as the registration ID of the corporation's SIM contract information) to the third-party device 10 and requests the issuance of an Issuer Verification ID.

[0031] In step S2, the issuing unit 12 of the third-party device 10 issues an Issuer Verification ID to the issuing device 3. The Issuer Verification ID issued by the issuing unit 12 is an example of first information related to verification. The issuing unit 12 may compare the identity verification information stored in the storage unit 11 with the identity verification information presented by the issuing device 3. If the results of the identity verification information comparison match, the issuing unit 12 may issue an Issuer Verification ID. If the results of the identity verification information comparison do not match, the issuing unit 12 does not have to issue an Issuer Verification ID. The Issuer Verification ID may include some or all of the identity verification information. The issuing unit 12 may store the issued Issuer Verification ID in the storage unit 11 as reference data (first data) for comparison.

[0032] In step S3, the issuing unit 12 transmits the Issuer Verification ID to the issuing device 3. The issuing device 3 receives the Issuer Verification ID from the third-party device 10. The processes in steps S1 to S3 may be executed in advance as preprocessing for flow M1.

[0033] In step S4, the holder device 4 requests the issuer device 3 to issue a VC.

[0034] The holder device 4 may transmit the holder's DID and the holder's digital signature to the issuer device 3. The issuer device 3 verifies the holder. For example, the issuer device 3 uses the holder's DID to obtain the holder's public key registered in VDR2. The issuer device 3 uses the holder's public key to verify the holder's digital signature.

[0035] In step S5, issuer device 3 issues a VC to holder device 4. The VC includes the issuer's DID, the issuer's digital signature, and the Issuer Verification ID. Holder device 4 retrieves the VC from issuer device 3.

[0036] In step S6, the holder device 4 presents (transmits) the VC to the verifier device 5. The verifier device 5 verifies the VC. For example, the verifier device 5 extracts the issuer's DID and the issuer's public key from the VC. The verifier device 5 uses the issuer's DID to obtain the issuer's public key registered in VDR2. The verifier device 5 uses the issuer's public key to verify the issuer's digital signature.

[0037] The holder device 4 may transmit the holder's DID and the holder's digital signature to the verifier device 5. The verifier device 5 may verify the holder. For example, the verifier device 5 uses the holder's DID to obtain the holder's public key registered in VDR2. The issuer device 3 uses the holder's public key to verify the holder's digital signature.

[0038] In step S7, the verifier device 5 extracts the Issuer verification ID from the VC. The extracted Issuer verification ID is an example of the second piece of information related to verification.

[0039] In step S8, the verifier device 5 transmits the Issuer verification ID to the third-party device 10. The matching unit 13 of the third-party device 10 receives the Issuer verification ID from the verifier device 5.

[0040] In step S9, the matching unit 13 verifies the existence of the issuer by comparing the first information related to verification with the second information related to verification. For example, the matching unit 13 compares the Issuer Verification ID (first data) issued by the Issuer Unit 12 with the Issuer Verification ID (second data) obtained from the Verifier Device 5. If the matching results match, the matching unit 13 determines that the issuer exists. If the matching results do not match, the matching unit 13 determines that the issuer does not exist.

[0041] In step S10, the matching unit 13 transmits the verification result to the verifier device 5. The verification result may be information indicating the existence or non-existence of the issuer. The verification result may also be information indicating a match or mismatch in the matching.

[0042] In the flow M1, the issuing unit 12 may use the private key of a third party to attach an electronic signature to the first information related to verification. For example, in step S2, the issuing unit 12 may use the private key of a third party to attach an electronic signature to the Issuer verification ID. In step S5, the issuer device 3 may issue a VC including the Issuer verification ID to which the electronic signature is attached. In step S7, the verifier device 5 may extract the Issuer verification ID from the VC. The verifier device 5 may use the public key of the third party to verify the electronic signature attached to the Issuer verification ID.

[0043] In the flow M1, the issuing unit 12 may use the private key of a third party to attach an electronic signature to the first information related to verification and the public key of the issuer. For example, in step S1, the issuer device 3 presents identity verification information and the public key of the issuer to the third party device 10, and requests issuance of an Issuer verification ID. In step S2, the issuing unit 12 may use the private key of the third party to attach an electronic signature to the Issuer verification ID and the public key of the issuer. In step S5, the issuer device 3 may issue a VC including the Issuer verification ID to which the electronic signature is attached and the public key of the issuer. In step S7, the verifier device 5 may extract the Issuer verification ID and the public key of the issuer from the VC. The verifier device 5 may use the public key of the third party to verify the electronic signature attached to the Issuer verification ID and the public key of the issuer.

[0044] In the flow M1, the issuing unit 12 may use the public key of the issuer to encrypt the first information related to verification. For example, in step S1, the issuer device 3 presents identity verification information and the public key of the issuer to the third party device 10, and requests issuance of an Issuer verification ID. In step S2, the issuing unit 12 may use the public key of the issuer to encrypt the Issuer verification ID. The issuer device 3 may use the private key of the issuer to decrypt the Issuer verification ID.

[0045] In flow M1, the second information related to verification may be encrypted using the public key of a third party. For example, in step S3, the issuer device 3 may encrypt the Issuer verification ID using the public key of the third party. In step S5, the issuer device 3 may issue a VC including the encrypted Issuer verification ID. In step S7, the verifier device 5 may extract the encrypted Issuer verification ID from the VC. In step S8, the verifier device 5 may transmit the encrypted Issuer verification ID (the second information related to verification) to the third party device 10. In step S9, the verification unit 13 may decrypt the second information related to verification using the private key of the third party.

[0046] Another example of the operation method (verification method) by the verification system 1 will be described with reference to FIG. 4. FIG. 4 is a sequence diagram showing another example of the operation of the verification system 1 as flow M2.

[0047] The processing of steps S11 to S14 is the same as the processing of steps S1 to S4 in flow M1, so description thereof will be omitted.

[0048] In step S15, the issuer device 3 issues an option code. The option code may be a random character string encrypted by any algorithm determined by the holder. The option code may include a VC issuance ID, which is an identifier associated with the holder.

[0049] In step S16, the issuer device 3 issues a VC to the holder device 4. The VC includes the issuer's DID, the issuer's electronic signature, an Issuer verification ID, and an option code. The holder device 4 acquires the VC from the issuer device 3.

[0050] The processing of step S17 is the same as the processing of step S6 in flow M1, so description thereof will be omitted.

[0051] In step S18, the verifier device 5 extracts the Issuer verification ID and the option code from the VC. The extracted Issuer verification ID is an example of the second information related to verification.

[0052] In step S19, the verifier device 5 transmits the Issuer verification ID and option code to the third-party device 10. The verification unit 13 of the third-party device 10 receives the Issuer verification ID and option code from the verifier device 5.

[0053] The process in step S20 is the same as the process in step S9 in flow M1, so its explanation is omitted.

[0054] In step S21, the matching unit 13 uses the option code to inquire with the issuer device 3 whether it can respond to the verifier device 5. The matching unit 13 may determine the destination of the option code inquiry by performing a reverse lookup of identity verification information (such as the registration ID of the corporate SIM contract information) from the Issuer verification ID stored in the storage unit 11. The issuer device 3 obtains the option code from the third-party device 10.

[0055] In step S22, the issuing device 3 compares the option code it issued with the option code obtained from the third-party device 10. If the option code comparison results match, the issuing device 3 may decide to allow the response. If the option code comparison results do not match, the issuing device 3 may decide to reject the response.

[0056] In step S23, the issuer device 3 transmits the result of the response approval / rejection determination to the third-party device. The third-party device 10 receives the response approval / rejection determination result from the issuer device 3.

[0057] In step S24, the matching unit 13 transmits the verification result to the verifier device 5. The verification result may be information indicating the existence or non-existence of the issuer. The verification result may be information indicating a match or mismatch in the matching. The verification result may be information indicating permission or denial of the response.

[0058] The second verification information and option code may be encrypted using a third party's public key. The matching unit 13 may decrypt the second verification information and option code using a third party's private key.

[0059] As described above, the third-party device 10 (device) relating to one aspect of this disclosure comprises an issuing unit 12 that issues first verification information to the issuer's device based on the issuer's identity verification information in DID / VC, and a matching unit 13 that obtains second verification information from the verifier's device in DID / VC and compares the first verification information with the second verification information.

[0060] A method relating to one aspect of this disclosure comprises the steps of issuing first verification information to the issuer's device based on the issuer's identity verification information in DID / VC, and obtaining second verification information from the verifier's device in DID / VC and comparing the first verification information with the second verification information.

[0061] In the apparatus and method relating to one aspect of this disclosure, first information regarding verification, backed by the issuer's identity verification information, is issued to the issuer's apparatus (issuer apparatus 3). In DID / VC, information is transferred from the issuer's apparatus to the verifier's apparatus (verifier apparatus 5) via VC. The issued first information regarding verification and the second information regarding verification obtained from the verifier's apparatus are then compared. This comparison confirms that the issuer exists and is trustworthy. As a result, the reliability of the issuer in the VC can be verified.

[0062] The issuing unit 12 uses the private key of a third party managing the device to electronically sign the first verification information. Each entity in DID / VC can verify the third party's electronic signature with the third party's public key, thus confirming that the first verification information has not been tampered with. This allows the issuer and the third party to presume that the first verification information was legitimately issued. As a result, the issuer's trustworthiness is improved.

[0063] The issuing unit 12 uses the private key of a third party managing the device to digitally sign the first verification information and the issuer's public key. Each entity in DID / VC can verify the third party's digital signature with the third party's public key, thus confirming that the first verification information and the issuer's public key have not been tampered with. This allows the issuer and the third party to presume that the first verification information was legitimately issued. As a result, the issuer's trustworthiness is improved.

[0064] The issuing unit 12 encrypts the first verification information using the issuer's public key. The issuer's device can decrypt the encrypted first verification information using the issuer's private key. This prevents eavesdropping on the first verification information between the issuer and third parties.

[0065] The second verification information is encrypted using the public key of a third party managing the device. The matching unit 13 decrypts the second verification information using the third party's private key. In DID / VC, the second verification information can be extracted from VC. Therefore, eavesdropping on the second verification information can be prevented in processing after the issuer's device.

[0066] The verification unit 13 obtains the option code issued by the issuer's device from the verifier's device and uses the option code to query the issuer's device for confirmation of whether it can respond to the verifier's device. Since the option code is information managed only by the issuer's device, it is possible to prevent impersonation of the issuer's device. As a result, the reliability of the issuer is improved.

[0067] The second verification information and option code are encrypted using the public key of a third party managing the device. The matching unit 13 decrypts the second verification information and option code using the third party's private key. In DID / VC, the second verification information and option code can be extracted from VC. Therefore, eavesdropping on the second verification information and option code can be prevented in processing after the issuer's device.

[0068] The apparatus and method of this disclosure may have the following configurations: [1] An apparatus comprising: an issuing unit that issues first verification information to the issuer's device based on the issuer's identity verification information in DID / VC (Decentralized Identifier / Verifiable Credentials); and a matching unit that obtains second verification information from the verifier's device in DID / VC and compares the first verification information with the second verification information. [2] The apparatus according to [1], wherein the issuing unit affixes an electronic signature to the first verification information using the private key of a third party managing the device. [3] The apparatus according to [1], wherein the issuing unit affixes an electronic signature to the first verification information and the issuer's public key using the private key of a third party managing the device. [4] The apparatus according to any one of [1] to [3], wherein the issuing unit encrypts the first verification information using the issuer's public key. [5] The apparatus according to any one of [1] to [4], wherein the second information relating to the verification is encrypted using the public key of a third party managing the device, and the matching unit decrypts the second information relating to the verification using the private key of the third party. [6] The apparatus according to any one of [1] to [5], wherein the matching unit obtains an option code issued by the issuer's device from the verifier's device, and uses the option code to query the issuer's device whether it can respond to the verifier's device. [7] The apparatus according to [6], wherein the second information relating to the verification and the option code are encrypted using the public key of a third party managing the device, and the matching unit decrypts the second information relating to the verification and the option code using the private key of the third party. [8] A method comprising the steps of: issuing first verification information to the issuer's device based on the issuer's identity verification information in DID / VC (Decentralized Identifier / Verifiable Credentials); and obtaining second verification information from the verifier's device in DID / VC and comparing the first verification information with the second verification information.

[0069] The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining software with the one or more of the above devices.

[0070] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0071] For example, the verification system 1 in one embodiment of the present disclosure may function as a computer that performs information processing according to the present disclosure. Figure 5 is a diagram showing an example of the hardware configuration of the verification system 1 according to one embodiment of the present disclosure. The issuer device 3, holder device 4, verifier device 5, and third-party device 10 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0072] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of verification system 1 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0073] Each function in the verification system 1 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which causes the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0074] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, each function in the verification system 1 described above may be implemented by the processor 1001.

[0075] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, each function in the verification system 1 may be implemented by a control program stored in the memory 1002 and running on the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0076] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a method according to one embodiment of the present disclosure.

[0077] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The storage 1003 may also be called an auxiliary storage device. The storage medium provided by the verification system 1 may be, for example, a database, server, or other suitable medium including at least one of the memory 1002 and the storage 1003.

[0078] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0079] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0080] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0081] Furthermore, the verification system 1 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0082] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0083] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0084] The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0085] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0086] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0087] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0088] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0089] The terms “system” and “network” as used in this disclosure are interchangeable.

[0090] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0091] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0092] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0093] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0094] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0095] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0096] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0097] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0098] 1...Verification system, 2...VDR, 3...Issuer device, 4...Owner device, 5...Verifier device, 10...Third-party device, 11...Storage unit, 12...Issuing unit, 13...Verification unit.

Claims

1. An apparatus comprising: an issuing unit that issues first verification information to the issuer's device based on the issuer's identity verification information in DID / VC (Decentralized Identifier / Verifiable Credentials); and a matching unit that obtains second verification information from the verifier's device in DID / VC and compares the first verification information with the second verification information.

2. The apparatus according to claim 1, wherein the issuing unit affixes an electronic signature to the first information relating to the verification using the private key of a third party managing the apparatus.

3. The apparatus according to claim 1, wherein the issuing unit uses the private key of a third party managing the apparatus to affix an electronic signature to the first information relating to the verification and the public key of the issuer.

4. The apparatus according to claim 1, wherein the issuing unit encrypts the first information relating to the verification using the issuer's public key.

5. The apparatus according to claim 1, wherein the second information relating to the verification is encrypted using the public key of a third party managing the apparatus, and the matching unit decrypts the second information relating to the verification using the private key of the third party.

6. The apparatus according to claim 1, wherein the matching unit obtains an option code issued by the issuer's device from the verifier's device, and uses the option code to query the issuer's device whether or not it can respond to the verifier's device.

7. The apparatus according to claim 6, wherein the second information relating to the verification and the option code are encrypted using the public key of a third party managing the apparatus, and the matching unit decrypts the second information relating to the verification and the option code using the private key of the third party.

8. A method comprising the steps of: issuing first verification information to the issuer's device based on the issuer's identity verification information in DID / VC (Decentralized Identifier / Verifiable Credentials); and obtaining second verification information from the verifier's device in DID / VC and comparing the first verification information with the second verification information.