Information processing device, system, control method for information processing device, and storage medium
Patent Information
- Application Number
- PCT/JP2025/011795
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-25
- Publication Date
- 2026-10-01
Smart Images

Figure JP2025011795_01102026_PF_FP_ABST
Abstract
Description
Information processing apparatus, system, control method for information processing apparatus, and storage medium
[0001] The present invention relates to an information processing apparatus, a system, a control method for an information processing apparatus, and a storage medium.
[0002] There exist techniques related to the reissuance of certificates.
[0003] For example, Patent Document 1 describes that it provides an information processing apparatus, an information processing system, an information processing method, and a program that can efficiently reissue a certificate. The information processing apparatus of Patent Document 1 includes a storage unit and a reissuance request unit. The storage unit stores a user ID, a first SEID of a first information device before the change corresponding to the user ID, and a second SEID of a second information device after the change corresponding to the user ID. The reissuance request unit transmits an issuance request for requesting a certificate issuer for the certificate stored in the first information device to the second information device having the second SEID stored in the storage unit.
[0004] International Publication No. 2024 / 190149
[0005] As described in Patent Document 1, there are cases where it becomes necessary to reissue a certificate held by a user. For example, when a user loses a smartphone or the like, it becomes necessary to reissue the certificate stored in the smartphone. Here, in order to receive reissuance of a certificate, the user needs to memorize the information of the certificate stored in the smartphone and apply for reissuance to the issuer of each certificate.
[0006] However, as the number of certificates stored in a smartphone increases, the burden on the user regarding the reissuance of certificates increases.
[0007] A main object of the present invention is to provide an information processing apparatus, a system, a control method for an information processing apparatus, and a storage medium that contribute to reducing the burden on a user who desires reissuance of a certificate.
[0008] According to a first aspect of the present invention, an information processing device is provided, comprising: a storage means for storing a user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates, using a database; and a control means for controlling the reissuance of each of the at least one certificates held by the user, in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, that proves that the user's identity has been verified.
[0009] A second aspect of the present invention provides a system comprising: a terminal owned by a user; a plurality of server devices managed by each of a plurality of certificate issuers; and a management server, wherein the management server includes storage means for storing the user's ID, information about the issuers of each of the at least one certificates owned by the user, and the certificate ID of each of the at least one certificates using a database; and control means for controlling the reissuance of each of the at least one certificates owned by the user in response to receiving an identity verification certificate, which includes the user's ID, from the terminal owned by the user, that proves the user's identity has been verified.
[0010] A third aspect of the present invention provides a control method for an information processing device, which stores a user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database, and when an identity verification certificate including the user's ID is received from the user's terminal, the device controls the reissuance of each of the at least one certificates held by the user, which proves that the user's identity has been verified.
[0011] A fourth aspect of the present invention is provided, a computer-readable storage medium that stores a program for causing a computer mounted on an information processing device to execute the following: a process of storing a user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database; and a process of controlling the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, that proves that the user's identity has been verified.
[0012] According to each aspect of the present invention, an information processing device, a system, a control method for the information processing device, and a storage medium are provided that contribute to reducing the burden on users who wish to have their certificates reissued. However, the effects of the present invention are not limited to those described above. The present invention may produce other effects in lieu of or in conjunction with the effects described above.
[0013] Figure 1 is a diagram illustrating the outline of one embodiment. Figure 2 is a flowchart showing the operation of one embodiment. Figure 3 is a diagram showing an example of the schematic configuration of an information processing system according to an embodiment of this disclosure. Figure 4 is a diagram showing an example of the display of a terminal according to an embodiment of this disclosure. Figure 5 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. Figure 6 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. Figure 7 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. Figure 8 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. Figure 9 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. Figure 10 is a diagram showing an example of the processing configuration of a terminal according to an embodiment of this disclosure. Figure 11 is a flowchart showing an example of the operation of an acquisition control unit according to an embodiment of this disclosure. Figure 12 is a diagram showing an example of the processing configuration of a server device according to an embodiment of this disclosure. Figure 13 is a diagram showing an example of the processing configuration of a management server according to an embodiment of this disclosure. Figure 14 is a diagram showing an example of a user management database according to an embodiment of this disclosure. Figure 15 is a diagram showing an example of the processing configuration of a service server according to an embodiment of this disclosure. Figure 16 is a sequence diagram showing an example of the operation of an information processing system according to an embodiment of this disclosure. Figure 17 is a sequence diagram showing an example of the operation of an information processing system according to the embodiment of this disclosure. Figure 18 is a sequence diagram showing an example of the operation of an information processing system according to the embodiment of this disclosure. Figure 19 is a diagram showing an example of the hardware configuration of a management server according to this disclosure.
[0014] First, an overview of one embodiment will be described. The reference numerals in the drawings attached to this overview are provided for convenience as examples to aid understanding, and this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units, not hardware units. The connecting lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows schematically indicate the flow of the main signal (data) and do not exclude bidirectional flow. In this specification and in the drawings, elements that can be similarly described are given the same reference numerals to avoid redundant explanation.
[0015] An information processing device 100 according to one embodiment comprises a storage means 101 and a control means 102 (see Figure 1). The storage means 101 stores the user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database (step S1 in Figure 2). The control means 102 receives an identity verification certificate from the user's terminal, which is a certificate that proves the user's identity has been verified and includes the user's ID (step S2). In response to receiving the identity verification certificate, the control means 102 performs control regarding the reissuance of each of the at least one certificates held by the user (step S3).
[0016] The information processing device 100 stores the user's ID and information about the certificates the user possesses. More specifically, the information processing device 100 stores the user's ID and information about the issuer of each certificate the user possesses (e.g., the issuer's name) and the certificate ID. If a user loses a device such as a smartphone on which the certificates were stored, the user operates a new smartphone or similar device to request the information processing device 100 to restore the certificates they possess (certificates stored on the lost smartphone or similar device). At that time, the user provides the information processing device 100 with an identity verification certificate that includes the user's ID. Upon obtaining the identity verification certificate, the information processing device 100 extracts the user's ID from the identity verification certificate. Based on the extracted user ID, the information processing device 100 identifies the user who is requesting the restoration of the certificates. The information processing device 100 then executes control regarding the reissuance of the certificates possessed by the identified user. For example, the information processing device 100 requests each certificate issuer to reissue the certificates possessed by the user. Alternatively, the information processing device 100 transmits information about the credential certificates held by the user (a list containing information about the credential certificates held by the user) to the terminal. The terminal uses the acquired list to request each certificate issuer to reissue the certificates held by the user. The reissued certificates are stored in a new smartphone or the like. In this way, the user can retrieve the certificates that were stored in the lost smartphone by providing the identity verification certificate to the information processing device 100 from the new smartphone. In other words, the user does not need to request (apply for) the reissue of the certificates from each certificate issuer, thus reducing the burden on users who wish to have their certificates reissued.
[0017] Specific embodiments will be described in more detail below with reference to the drawings.
[0018] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.
[0019] [System Configuration] As shown in Figure 3, the information processing system according to the first embodiment includes at least one certificate issuer, an information management business operator, and at least one service provider.
[0020] A certificate issuer is the entity that issues certificates to users. For example, a certificate issuer issues certificates that prove the user's "identity" or "attributes." For example, a certificate issuer issues an identification card that proves the user's name, gender, date of birth, address, etc. Alternatively, a certificate issuer issues certificates that prove the user's "rights" or "qualifications."
[0021] For example, public institutions that issue identification documents such as driver's licenses, passports, and My Number cards are considered certificate issuers. Alternatively, universities and companies that issue graduation certificates or employment certificates are considered certificate issuers. Or, organizations that issue certificates related to technology, language, etc. are considered certificate issuers.
[0022] Alternatively, the certificate issuer may issue certificates that prove the skills the user possesses, certificates that prove the qualifications the user possesses, etc.
[0023] Each certificate issuer is provided with a server device 10. The server device 10 is a server that performs the processing and operations necessary to carry out the certificate issuer's business. The server device 10 may be managed and operated by the certificate issuer, or its management and operation may be entrusted to another business operator, etc. The server device 10 may be installed in the certificate issuer's building, or it may be installed on a network (on the cloud).
[0024] Information management service providers are businesses that control and manage information about users. In particular, information management service providers perform management services related to certificates held by users. Specifically, information management service providers provide backup services related to certificates held by users.
[0025] The information management operator shall have a management server 20. The management server 20 is a server that performs the processing and operations necessary to carry out the information management operator's business. The management server 20 may be installed in the information management operator's building or on a network (on the cloud).
[0026] A service provider is a business that provides services to individuals, companies, etc. For example, a service provider provides job placement services. Service providers are not limited to private companies; public institutions such as city halls are also included as service providers in the disclosure of this application.
[0027] The service provider has a service server 30 for providing services. For example, the service server 30 provides services to users via a website. The service server 30 may be located within the service provider's building or on a network (on the cloud).
[0028] The user possesses terminal 40. For example, the user operates terminal 40 to request (demand) the issuance of a certificate from the certificate issuer.
[0029] Each device shown in Figure 3 is connected to a network. Specifically, the server device 10, management server 20, service server 30, and terminal 40 are connected to the network by wired or wireless communication means.
[0030] The configuration of the information processing system shown in Figure 3 is illustrative and not intended to limit its configuration. For example, the server device 10 of each certificate issuer, the management server 20 of the information management operator, and the service server 30 of the service provider may each belong to a different network. Alternatively, each certificate issuer may include multiple server devices 10. Load balancing and redundancy may be achieved by using multiple server devices 10. Similarly, the information management operator may include multiple management servers 20, and each service provider may include multiple service servers 30.
[0031] [Outline of Operation] Next, the outline of the operation of the information processing system according to the first embodiment will be described.
[0032] <Preparing for a Digital Wallet> Users will use a digital wallet. A digital wallet is an electronic information storage service that guarantees information security, including data integrity, reliability, and availability.
[0033] The user installs a wallet application on their device 40 to realize a digital wallet. By opening a digital wallet, the user can store various digital content such as identification documents like My Number cards, skill certificates, and qualification certificates in the digital wallet.
[0034] <Acquisition of Digital Content> Users who have opened a digital wallet will acquire the digital content to be stored in that digital wallet.
[0035] The user operates terminal 40 to request the issuance of a certificate from the certificate issuer. Specifically, the wallet application requests the issuance of a certificate from the certificate issuer. The certificate issuer issues VCs (Verifiable Credentials) as certificates, which can be verified online. In the following explanation, VCs will be referred to as "credential certificates".
[0036] Furthermore, specific certificates issued as credential documents will be indicated by adding "VCs" after the name of the certificate. For example, a My Number Card issued as a credential document will be written as "My Number Card VCs".
[0037] By obtaining credential certificates from each certificate issuer, the user's digital wallet will store digital content such as that shown in Figure 4. Unless otherwise specified, the content stored in the digital wallet in the following explanation will be the credential certificates.
[0038] <Obtaining Credentials> First, we will outline the process of obtaining credentials.
[0039] Prior to requesting issuance of a credential certificate, the user's terminal 40 (wallet application) generates a public-private key pair. The terminal 40 also generates a Decentralized Identifier (DID).
[0040] The terminal 40 registers the generated DID (user DID; holder DID) and public key on the blockchain (step S01 in FIG. 5).
[0041] Furthermore, the user's terminal 40 requests the certificate issuer (server device 10) to issue a credential certificate while presenting the user DID.
[0042] Specifically, the terminal 40 transmits a "certificate issuance request" including information related to the requested certificate (e.g., type of the credential certificate), information necessary for issuing the credential certificate, and the user DID to the server device 10 (step S02).
[0043] Note that the server device 10 generates and stores the issuer's DID (issuer DID), private key, and public key in advance.
[0044] Upon receiving the certificate issuance request, the certificate issuer determines whether it is possible to issue the credential certificate desired by the user.
[0045] If the credential certificate desired by the user can be issued, the server device 10 generates a credential certificate including the issuer DID and the user DID.
[0046] Specifically, the server device 10 generates a credential certificate including metadata containing the type of the credential certificate, name of the issuing organization, issuance date and time, validity period, etc., claim content (qualification information, claims), and proof including the issuer's public key information, electronic signature, and the like. Note that specific information certified by the issuer is described in the claim content.
[0047] The server device 10 provides the generated credential certificate to the terminal 40 of the user (the user who becomes the holder of the certificate; the requester of the certificate issuance) (step S03).
[0048] Specifically, the server device 10 stores the generated credential certificate in an online storage. The server device 10 generates a certificate acquisition URL from the URL (Uniform Resource Locator) of the storage location of the credential certificate. The server device 10 transmits an acknowledgment (a response to the certificate issuance request) including the generated certificate acquisition URL to the terminal 40.
[0049] Furthermore, the server device 10 registers the issuer DID, the generated public key and the like in the blockchain (step S04). Alternatively, the server device 10 may register the status (valid, invalid) of the issued credential certificate, the credential ID that uniquely identifies the credential certificate, the issuer DID, and the like in a VDR (Verifiable Data Registry).
[0050] The terminal 40 accesses the certificate acquisition URL included in the acknowledgment to acquire the credential certificate. The terminal 40 stores the acquired credential certificate in a digital wallet.
[0051] <Acquisition of Identity Verification VCs> A user who has opened a digital wallet first acquires identity verification VCs. The identity verification VCs are credential certificates that prove that the user's identity verification has been completed. For example, the identity verification VCs are credential certificates that prove that identity verification using an identification card issued by a public institution has been performed. The identity verification VCs are credential certificates issued by a public institution after the user completes identity verification using an identification card issued by the public institution. For example, the local government that issued an Individual Number Card issues an identity verification VC that proves that the recipient of the identity verification VC is a user who has successfully completed identity verification using an Individual Number Card.
[0052] The user requests the local government that issued the Individual Number Card to issue the identity verification VCs.
[0053] When a user requests the issuance of an identity verification VC, terminal 40 performs identity verification of the user. For example, terminal 40 obtains a PIN that has been pre-set on the My Number Card from the user, and uses the obtained PIN to obtain a facial image and a user authentication electronic certificate from the IC (Integrated Circuit) chip embedded in the My Number Card.
[0054] Furthermore, terminal 40 takes a picture of the user and acquires a facial image. Terminal 40 acquires a facial image of the user by taking a selfie.
[0055] Terminal 40 performs identity verification using facial images obtained from the My Number Card and facial images obtained through selfies.
[0056] If identity verification is successful, terminal 40 requests the local government (local government server device 10) to issue identity verification VCs. Specifically, terminal 40 sets "identity verification VCs" as the certificate to be issued and the user authentication electronic certificate obtained from the My Number Card as the information necessary for issuing the credential certificate, and sends the certificate issuance request to the server device 10. Terminal 40 sends the certificate issuance request to the local government server device 10 (step S11 in Figure 6).
[0057] When server device 10 receives a certificate issuance request for identity verification VCs, it requests the certification authority to verify the user authentication electronic certificate included in the certificate issuance request. Specifically, server device 10 transmits the user authentication electronic certificate to the certification authority server 50, which is operated by an organization called J-LIS (Japan Agency for Local Authority Information Systems) (step S12).
[0058] The server device 10 receives the verification result (verification successful, verification failed) from the certification authority server 50. If the certification authority server 50 successfully verifies the user authentication electronic certificate, the server device 10 receives the end-user ID from the certification authority server 50 (step S13).
[0059] The end-user ID is a unique ID determined based on the user's user authentication electronic certificate (the ID corresponding to the user authentication electronic certificate).
[0060] When the server device 10 obtains the end-user ID from the certification authority server 50, it issues identity verification certificates (VCs). Specifically, the server device 10 issues a credential certificate as an identity verification certificate, in which the end-user ID (an ID uniquely determined from the user authentication electronic certificate) is set in the asserted content (credential information, claims) (step S14).
[0061] Terminal 40 retrieves identity verification VCs from online storage. Terminal 40 stores the retrieved identity verification VCs in a digital wallet.
[0062] <Obtaining Other Credential Certificates> Users obtain other credential certificates besides their identity verification VCs. For example, users request the issuance of credential certificates related to their skills, qualifications, etc., from various certificate issuers. In doing so, the user (terminal 40) provides the certificate issuer with the end-user ID obtained from their identity verification VCs.
[0063] More specifically, terminal 40 sends a certificate issuance request to each certificate issuer's server device 10, in which the end-user ID is included in the information necessary for issuing the credential certificate.
[0064] Each certificate issuer's server device 10 issues credential certificates (e.g., skills VCs, qualifications VCs) that include an end-user ID. More specifically, the server device 10 issues credential certificates that include the end-user ID as part of the claim.
[0065] The certificate issuer's server device 10 stores the credential ID and the contents of the issued credential certificate. Alternatively, the server device 10 may store the end-user ID, credential ID, and contents of the credential certificate in association with the certificate issuance request.
[0066] For example, a user requests a certification body for skills and qualifications to issue a certificate of skills (VCs) or a certificate of qualifications (VCs). Terminal 40 stores the acquired credential certificates in its digital wallet.
[0067] <Use of Credential Certificates> Users can receive services from service providers. For example, a user can receive job placement services from a job placement service provider. In this case, the user registers to receive job placement services.
[0068] When a user who has completed user registration wishes to receive job placement support services, the service server 30 requests the terminal 40 to provide the information necessary to provide said services. For example, the service server 30 requests the submission of a certificate of skills held, such as VCs.
[0069] Specifically, the service server 30 sends a "certificate provision request" to the terminal 40 (step S21 in Figure 7). This certificate provision request contains information about at least one certificate necessary for the job placement service provider to provide its services. For example, the certificate provision request contains the type of certificate that the job placement service provider requests.
[0070] Upon receiving a request for a certificate, terminal 40 sends the credential certificate stored in the digital wallet to the service server 30. Specifically, terminal 40 selects a specified credential certificate from among several credential certificates stored in the digital wallet. Then, terminal 40 signs the selected credential certificate using the private key corresponding to the user's DID (User ID). Terminal 40 sends at least one signed credential certificate to the service server 30 (step S22).
[0071] The service server 30 obtains the issuer ID and user ID contained in the received credential certificate. Furthermore, the service server 30 obtains the public key corresponding to the obtained issuer ID and the public key corresponding to the obtained user ID from the blockchain (step S23).
[0072] Subsequently, the service server 30 verifies at least one credential certificate received from the terminal 40. Specifically, the service server 30 verifies the signature of the holder and the signature of the issuer attached to the credential certificate. By verifying these signatures, the service server 30 confirms that the credential certificate obtained from the user (the holder of the credential certificate) has not been tampered with and that it was issued by a trusted issuer.
[0073] Once the service server 30 successfully verifies the acquired credential certificate, it provides services to the user (becomes ready to provide services to the user). For example, the service server 30 of a job placement service provider provides information on companies that are suitable for the user's work history.
[0074] <Backup of Credentials> Users can request their information management provider to back up at least one credential stored in their digital wallet.
[0075] First, the user operates terminal 40 to access the management server 20 and registers as a user (creates an account). The management server 20 obtains the user's name, gender, date of birth, address, email address, telephone number, etc., as well as identity verification VCs from the user (terminal 40).
[0076] The management server 20 verifies the identity verification VCs, and if the verification is successful, it generates a user account. More specifically, the management server 20 stores the name and other information obtained above in the user management database. Furthermore, the management server 20 stores the end-user ID obtained from the identity verification VCs in the user management database. Details of the user management database will be described later.
[0077] Once an account is created with the information management provider, the user can back up the credential certificates stored in their digital wallet. For example, each time terminal 40 obtains a credential certificate from the certificate issuer, it sends the newly obtained credential certificate (e.g., held skills VCs, held qualifications VCs, etc.) to the management server 20.
[0078] More specifically, terminal 40 sends a "backup request" containing the newly acquired credential certificate to the management server 20 (see Figure 8).
[0079] When the management server 20 receives a backup request, it verifies the credential certificate included in the backup request. If the verification is successful, it performs a backup of the received credential certificate.
[0080] Specifically, the management server 20 obtains (extracts) the end-user ID from the credential certificate. The management server 20 searches the user management database using the obtained end-user ID as a key and identifies the corresponding entry.
[0081] The management server 20 stores information about the received credential certificate (the credential certificate to be backed up) in the identified entry. More specifically, the management server 20 stores the name of the certificate issuer, the credential ID, and the verification result (verification successful) of the credential certificate in the user management database.
[0082] Once the information regarding the credential certificate is stored in the user management database, the credential certificate backup process is completed. Upon successful completion of the backup process, the management server 20 sends an acknowledgment to the terminal 40.
[0083] The management server 20 will then discard the backed-up credential certificates (credential certificates obtained from users).
[0084] <Reissuance of Credential Certificates> Users may lose terminal 40. In this case, the user will open a digital wallet on a new terminal 40. Since the digital wallet on the new terminal 40 does not contain the credential certificate, the user will request the information management provider to restore the backed-up credential certificate.
[0085] In this case, the user will obtain a replacement of the identity verification certificates (VCs) from the certificate issuer among the credential certificates stored in the digital wallet of the lost terminal 40. Specifically, terminal 40 performs the identity verification described above and sends a certificate issuance request, including the user authentication electronic certificate, to the local government's server device 10.
[0086] The reissued identity verification certificates (VCs) are stored in the digital wallet of the new terminal 40. Since the end-user ID that the identity verification certificates verify is uniquely associated with the user authentication electronic certificate, the same end-user ID will be assigned to both the identity verification certificates lost along with the terminal 40 and the reissued identity verification certificates.
[0087] Next, the user requests the information management provider to restore the credential certificate. Specifically, terminal 40 sends a "certificate restoration request" including the reissued identity verification VCs to the management server 20 (step S31 in Figure 9).
[0088] Upon receiving a certificate restoration request, the management server 20 verifies the identity verification VCs included in the certificate restoration request. If the verification of the identity verification VCs is successful, the management server 20 restores other credential certificates held by the user.
[0089] Specifically, the management server 20 obtains (extracts) the end-user ID from the identity verification VCs. The management server 20 searches the user management database using the obtained end-user ID as a key and identifies the corresponding entry. The management server 20 obtains the information about the credential certificate (certificate issuer name, credential ID, etc.) stored in the identified entry.
[0090] The management server 20 requests each certificate issuer to reissue the credential certificates held by the users.
[0091] Specifically, the management server 20 sends a "certificate reissuance request" including at least a credential ID to the server device 10 of the certificate issuer that has the authority to issue the credential certificate to be reissued (step S32). The management server 20 requests the certificate issuer to reissue the credential certificate corresponding to the credential ID included in the certificate reissuance request.
[0092] Each server device 10 that receives a certificate reissuance request invalidates the credential certificate corresponding to the credential ID included in the certificate reissuance request.
[0093] Furthermore, each server device 10 generates (reissues) a credential certificate with the same content as the credential certificate corresponding to the credential ID included in the certificate reissuance request. The server device 10 assigns a new credential ID and issues a credential certificate with the same content as the credential certificate for which reissuance was requested.
[0094] Each server device 10 stores the generated credential certificate in online storage and notifies the management server 20 of the location where the credential certificate is stored. Specifically, the server device 10 sends an acknowledgment (response to a request for reissuance of the certificate) including a URL for obtaining the certificate to the management server 20 (step S33).
[0095] The management server 20 notifies the terminal 40 of the storage location of the reissued credential certificates from each server device 10. Specifically, the management server 20 sends an acknowledgment (response to the certificate restoration request) to the terminal 40, which includes the URL for obtaining the certificate notified by each server device 10 (step S34).
[0096] Terminal 40 accesses each of the at least one URL for obtaining the certificate included in the acknowledgment and obtains the reissued credential certificate. Terminal 40 stores the obtained credential certificate (reissued credential certificate) in its digital wallet.
[0097] Through the operation of this information processing system, the user's credential documents, which were in their possession before the loss of terminal 40, are restored.
[0098] Next, we will describe the details of each device included in the information processing system according to the first embodiment.
[0099] [Terminal] Examples of terminals 40 include mobile devices such as smartphones, mobile phones, game consoles, and tablets, as well as computers (personal computers, laptops), etc. Terminal 40 can be any device or equipment as long as it can receive user input and communicate with the server device 10, etc.
[0100] Figure 10 is a diagram showing an example of the processing configuration (processing module) of a terminal 40 according to the embodiment disclosed herein. Referring to Figure 10, the terminal 40 comprises a communication control unit 201, an acquisition control unit 202, a utilization control unit 203, a backup control unit 204, and a storage unit 205.
[0101] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the server device 10. The communication control unit 201 also transmits data to the server device 10. The communication control unit 201 passes the data received from other devices to other processing modules. The communication control unit 201 transmits the data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 201. The communication control unit 201 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.
[0102] The wallet application is implemented by the acquisition control module 202, the utilization control module 203, and the backup control module 204. A detailed explanation of the wallet application installation is omitted, as its installation is obvious to those skilled in the art.
[0103] The acquisition control unit 202 is a means for controlling the acquisition of credential certificates.
[0104] Figure 11 is a flowchart illustrating an example of the operation of the acquisition control unit 202. The operation of the acquisition control unit 202 when acquiring identity verification VCs will be explained with reference to Figure 11.
[0105] When a digital wallet is opened, the user launches the wallet application. If no credential documents are stored in the digital wallet at that time, the acquisition control unit 202 acquires identity verification VCs.
[0106] First, the acquisition control unit 202 verifies the user's identity (step S101). More specifically, the acquisition control unit 202 verifies the user's identity using the user's identification document. Here, we will explain the case where the acquisition control unit 202 verifies the user's identity using a My Number Card.
[0107] The acquisition control unit 202 acquires the PIN for the user authentication electronic certificate using a GUI (Graphical User Interface) or the like. The acquisition control unit 202 uses the acquired PIN (a four-digit number) as a password to read information from the IC chip of the My Number Card.
[0108] The acquisition control unit 202 reads the user authentication electronic certificate and biometric information (facial image) from the IC chip of the My Number Card. The acquisition control unit 202 stores the user authentication electronic certificate and facial image read from the My Number Card in the storage unit 205.
[0109] Furthermore, the acquisition control unit 202 acquires biometric information of the user (the user of terminal 40). For example, the acquisition control unit 202 acquires a facial image through a selfie.
[0110] The acquisition control unit 202 acquires a facial image from the My Number Card and, upon acquiring a facial image of the user through a selfie, performs a matching process using the two facial images. The acquisition control unit 202 determines whether the two facial images are substantially identical.
[0111] Specifically, the acquisition control unit 202 generates feature quantities from each of the two face images.
[0112] Regarding the feature generation process, existing technologies can be used, so a detailed explanation will be omitted. For example, the acquisition control unit 202 extracts the eyes, nose, mouth, etc., from the face image as feature points. Then, the acquisition control unit 202 calculates the position of each feature point and the distance between each feature point as feature quantities (generating a feature vector consisting of multiple feature quantities).
[0113] Next, the acquisition control unit 202 performs a matching process (authentication process) using the two generated feature quantities. Specifically, the acquisition control unit 202 calculates the similarity between corresponding face images using the two feature quantities. Based on the result of thresholding the calculated similarity, the acquisition control unit 202 determines whether the two images are face images of the same person. The similarity can be calculated using methods such as the chi-squared distance or the Euclidean distance. The greater the distance, the lower the similarity, and the closer the distance, the higher the similarity.
[0114] If the similarity is greater than a predetermined value (if the distance is shorter than a predetermined value), the acquisition control unit 202 determines that the matching process was successful. If the similarity is less than or equal to the predetermined value, the acquisition control unit 202 determines that the matching process failed.
[0115] If the matching process fails, the acquisition control unit 202 determines that identity verification has failed. In this case, the acquisition control unit 202 terminates the process related to acquiring identity verification VCs.
[0116] If the matching process is successful, the acquisition control unit 202 determines that the identity verification has been successful. In this case, the acquisition control unit 202 executes the processes from step S102 onward.
[0117] If identity verification is successful, the acquisition control unit 202 generates a public key and private key pair, and a distributed identifier, the user DID. The acquisition control unit 202 registers the generated user DID and public key on the blockchain (registering the public key, etc.; step S102).
[0118] Next, the acquisition control unit 202 uses a GUI or the like to acquire the information necessary for requesting the issuance of a credential certificate (acquisition of necessary information; step S103).
[0119] Specifically, the acquisition control unit 202 acquires information about the certificate issuer who has the authority to issue identity verification VCs (for example, the name of the local government), etc. Furthermore, the acquisition control unit 202 reads the stored user authentication electronic certificate from the storage unit 205.
[0120] The acquisition control unit 202 notifies the local government, which is the issuer of the identity verification VCs, of the acquired necessary information (e.g., user authentication electronic certificate) and user DID. Specifically, the acquisition control unit 202 sets "identity verification VCs" as the type of credential certificate, sets the user authentication electronic certificate as the information necessary for issuing identity verification VCs, and sends a certificate issuance request including the user DID to the local government's server device 10 (step S104).
[0121] The acquisition control unit 202 receives a response (affirmative response, negative response) to the certificate issuance request from the local government's server device 10 (step S105).
[0122] If a negative response is received indicating that the issuance of identity verification VCs failed (step S106, No branch), the acquisition control unit 202 notifies the user that identity verification VCs were not issued (notification of non-issuance; step S107).
[0123] If an affirmative response is received indicating that the issuance of identity verification VCs has been successful (step S106, Yes branch), the acquisition control unit 202 accesses the certificate acquisition URL included in the affirmative response and acquires the identity verification VCs issued by the local government (step S108).
[0124] The acquisition control unit 202 stores the acquired identity verification VCs in the digital wallet (step S109).
[0125] The acquisition control unit 202 also acquires credential certificates other than identity verification VCs from their respective issuers. In this process, the acquisition control unit 202 may or may not perform identity verification using the above-mentioned identity documents.
[0126] Furthermore, the acquisition control unit 202 acquires information necessary for issuing the credential certificate, such as information about the certificate issuer who has the authority to issue the credential certificate that the user wishes to have issued (for example, the name of the training institution, the name of the certification body, etc.) and the type of certificate desired. In addition, the acquisition control unit 202 acquires information that the certificate issuer can use to identify the recipient of the certificate (for example, a combination of name and date of birth).
[0127] The usage control unit 203 is a means for controlling the use of digital content (credential certificates) stored in the digital wallet. The usage control unit 203 provides the service provider with certificates stored in the digital wallet that are specified by the service provider.
[0128] Specifically, the user control unit 203 processes the certificate provision request received from the service server 30 of the service provider.
[0129] Upon receiving a request for a certificate, the user control unit 203 selects the credential certificate specified by the service provider from among the multiple credential certificates stored in the digital wallet. Subsequently, the user control unit 203 signs the selected credential certificate using the private key corresponding to the user's DID (User ID).
[0130] Furthermore, the user control unit 203 signs the credential certificate to be submitted to the service provider using the private key (the private key corresponding to the user ID) that was generated when issuing the credential certificate requested by the service provider.
[0131] If the credential certificate specified by the service provider can be provided, the user control unit 203 sends an affirmative response to the service server 30 that includes a signed credential certificate (at least one credential certificate). If the credential certificate specified by the service provider cannot be provided, the user control unit 203 sends a negative response to the service server 30 indicating that the credential certificate cannot be provided.
[0132] The backup control unit 204 is a means for controlling the backup and restoration of credential certificates.
[0133] When a user performs a predetermined action in the wallet application (for example, pressing the button to create a backup account), the backup control unit 204 accesses the management server 20.
[0134] The backup control unit 204 transmits identity verification VCs stored in the digital wallet to the management server 20 in response to instructions from the management server 20 or operations from the user. The backup control unit 204 also transmits the name, gender, etc., entered by the user to the management server 20 in accordance with the GUI provided by the management server 20.
[0135] Once a backup account is created on the management server 20, the backup control unit 204 accesses the digital wallet periodically or at predetermined intervals. If a new credential certificate is stored in the digital wallet, the backup control unit 204 sends a backup request including the new credential certificate to the management server 20.
[0136] The backup control unit 204 receives responses (affirmative responses, negative responses) to backup requests from the management server 20.
[0137] If the backup control unit 204 receives an acknowledgment indicating that the backup of the credential certificate has been completed successfully, it does not perform any special processing. Alternatively, the backup control unit 204 may notify the user that the backup of the credential certificate has been completed successfully.
[0138] If a negative response indicating that the backup of the credential certificate failed is received, the backup control unit 204 performs the process of resending the new credential certificate. Alternatively, the backup control unit 204 may notify the user that the backup of the credential certificate failed.
[0139] When a user performs a predetermined action in the wallet application (for example, pressing the certificate restoration button), the backup control unit 204 requests the management server 20 to perform the credential certificate restoration process.
[0140] Furthermore, when a user requests to restore their credential certificate (when the certificate restoration button is pressed), the backup control unit 204 determines whether or not identity verification VCs are stored in the digital wallet. If identity verification VCs are not stored in the digital wallet, the backup control unit 204 instructs the user to retrieve the identity verification VCs.
[0141] If identity verification VCs are stored in the digital wallet, the backup control unit 204 sends a "certificate restoration request" including the identity verification VCs (reissued identity verification VCs) to the management server 20.
[0142] The backup control unit 204 receives a response (affirmative response, negative response) to the certificate restoration request from the management server 20.
[0143] If the backup control unit 204 receives an acknowledgment indicating that the credential certificate has been successfully restored, it accesses at least one URL for obtaining the certificate included in the acknowledgment and obtains the reissued credential certificate. The backup control unit 204 stores the obtained credentials in the digital wallet.
[0144] If the backup control unit 204 receives a negative response indicating that the restoration of the credential certificate failed, it notifies the user accordingly.
[0145] The memory unit 205 is a means for storing information necessary for the operation of the terminal 40.
[0146] [Server Device] Figure 12 is a diagram showing an example of the processing configuration (processing module) of the server device 10 according to the embodiment disclosed herein. Referring to Figure 12, the server device 10 comprises a communication control unit 301, a certificate issuance unit 302, a certificate reissuance unit 303, and a storage unit 304.
[0147] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the terminal 40. The communication control unit 301 also transmits data to the terminal 40. The communication control unit 301 passes the data received from other devices to other processing modules. The communication control unit 301 transmits the data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 301. The communication control unit 301 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.
[0148] The certificate issuing unit 302 is a means for issuing credential certificates to users. The certificate issuing unit 302 processes the "certificate issuance request" received from the terminal 40.
[0149] Here, there are differences in the generation (issuance) methods for identity verification VCs and other credential certificates. First, let's explain the issuance of identity verification VCs.
[0150] When the certificate issuance request for identity verification VCs is received, the certificate issuance unit 302 transmits the user authentication electronic certificate included in the certificate issuance request to the certification authority server 50.
[0151] The certificate issuing unit 302 receives the verification result (verification successful, verification failed) of the user authentication electronic certificate from the certification authority server 50. If the certification authority server 50 successfully verifies the user authentication electronic certificate, the certificate issuing unit 302 receives the end-user ID from the certification authority server 50.
[0152] Upon obtaining the end-user ID from the certification authority server 50, the certificate issuing unit 302 issues identity verification VCs. The certificate issuing unit 302 generates identity verification VCs that include the issuer DID and the user DID (the DID of the recipient of the certificate; the user DID included in the certificate issuance request).
[0153] Specifically, the certificate issuing unit 302 generates identity verification VCs that include metadata such as the type of credential certificate, the name of the issuing organization, the date and time of issuance, and the validity period, as well as the claims and a proof consisting of the issuer's public key information and digital signature. The digital signature affixed to the credential certificate is performed using a private key corresponding to the issuer DID that was generated in advance. The end-user ID is also set in the claims.
[0154] The certificate issuing unit 302 stores the generated identity verification VCs in online storage (cloud storage), etc. The certificate issuing unit 302 generates a certificate acquisition URL from the URL where the identity verification VCs are stored. The certificate issuing unit 302 sends an acknowledgment containing the generated certificate acquisition URL to the terminal 40. Furthermore, the certificate issuing unit 302 registers the previously generated issuer DID and public key, etc., on the blockchain.
[0155] If the certification authority server 50 fails to verify the user authentication electronic certificate, the certificate issuance unit 302 sends a negative response to the terminal 40 indicating that the identity verification VCs cannot be issued.
[0156] Next, we will explain the issuance of credential documents other than identity verification VCs.
[0157] Upon receiving a certificate issuance request, the certificate issuance unit 302 searches a database (not shown in Figure 12, etc.) that stores user information, using the information for identifying the recipient of the certificate included in the certificate issuance request (for example, a combination of name and date of birth) as a key.
[0158] If the above search fails, the certificate issuing unit 302 sends a negative response to the terminal 40 indicating that the certificate has not been issued.
[0159] If the above search is successful, the certificate issuing unit 302 will, if necessary, determine whether or not it is possible to issue the credential certificate that the user wishes to have issued.
[0160] For example, if a user requests the issuance of a skills certificate (VCs), the certificate issuing unit 302 determines whether or not the user possesses the necessary skills.
[0161] Detailed explanations regarding the determination of whether or not to issue a credential certificate are omitted, as the requirements for issuing individual credential certificates differ from the intent of this disclosure.
[0162] If it is not possible to issue a credential certificate to the user, the certificate issuing unit 302 sends a negative response to the terminal 40 indicating that the certificate issuance failed (certificate cannot be issued).
[0163] If it is possible to issue a credential certificate to the user, the certificate issuing unit 302 generates a credential certificate in the same manner as identity verification VCs. In this case, the certificate issuing unit 302 generates a credential certificate in which the end-user ID obtained from the certificate issuance request is part of the asserted content.
[0164] The certificate issuing unit 302 stores the generated credential certificate in online storage and generates a URL for obtaining the certificate.
[0165] The certificate issuing unit 302 sends an affirmative response to the terminal 40 that includes the generated URL for obtaining the certificate. The certificate issuing unit 302 sends an affirmative response to the terminal 40 indicating that the certificate has been successfully issued (certificate issuance is possible).
[0166] Furthermore, when issuing a credential certificate (a credential certificate including identity verification VCs), the certificate issuing unit 302 stores the credential ID of the issued credential certificate in association with the contents of the credential certificate. In addition, when issuing a credential certificate other than identity verification VCs, the certificate issuing unit 302 may store the credential ID, the contents of the credential certificate, and the end-user ID (the end-user ID included in the certificate issuance request) in association with each other.
[0167] When a request for issuance of a certificate for identity verification VCs is received, the certificate issuance unit 302 may use the stored information on issued identity verification VCs to determine whether or not identity verification VCs for the same user (same end-user ID) have already been issued. If identity verification VCs have already been issued for the same user, the certificate issuance unit 302 may invalidate the already issued identity verification VCs and then issue new identity verification VCs.
[0168] The certificate reissuance unit 303 is a means for reissuing credential certificates.
[0169] The certificate reissuance unit 303 receives a certificate reissuance request from the management server 20.
[0170] The certificate reissuance unit 303 invalidates the credential certificate corresponding to the credential ID included in the certificate reissuance request.
[0171] Furthermore, the certificate reissuance unit 303 generates a credential certificate with the same content as the credential certificate corresponding to the credential ID included in the certificate reissuance request. The certificate reissuance unit 303 reissues the credential certificate using the stored credential ID and the contents of the issued credential certificate.
[0172] Regarding the reissued credential certificate, the certificate reissuance unit 303 stores the credential ID (the credential ID of the reissued credential certificate) in association with the contents of the credential certificate. Alternatively, the certificate reissuance unit 303 may store the credential ID and the contents of the credential certificate in association with the end-user ID.
[0173] The certificate reissuance unit 303 stores the reissued credential certificate in online storage and notifies the management server 20 of the location where the credential certificate is stored. Specifically, the certificate reissuance unit 303 sends an acknowledgment (response to the certificate reissuance request) including a URL for obtaining the certificate to the management server 20.
[0174] If the reissuance of the credential certificate fails, the certificate reissuance unit 303 sends a negative response (response to the certificate reissuance request) to the management server 20 indicating this failure.
[0175] The memory unit 304 is a means for storing information necessary for the operation of the server device 10.
[0176] [Management Server] Figure 13 is a diagram showing an example of the processing configuration (processing module) of the management server 20 according to the embodiment disclosed herein. Referring to Figure 13, the management server 20 comprises a communication control unit 401, an account control unit 402, a backup control unit 403, and a storage unit 404.
[0177] The communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from the terminal 40. The communication control unit 401 also transmits data to the terminal 40. The communication control unit 401 passes the data received from other devices to other processing modules. The communication control unit 401 transmits the data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data with other devices via the communication control unit 401. The communication control unit 401 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.
[0178] The account control unit 402 is a means for controlling the account of a user (a user who wishes to back up their credential certificate).
[0179] When a user operates terminal 40 to access management server 20, account control unit 402 obtains the user's name, gender, date of birth, address, email address, telephone number, etc. from a designated website or the like.
[0180] Furthermore, the account control unit 402 instructs the user (terminal 40) to provide identity verification VCs.
[0181] When identity verification VCs are obtained, the account control unit 402 verifies the obtained identity verification VCs.
[0182] The account control unit 402 verifies at least one of the three items related to the validity of identity verification VCs.
[0183] The first item is the verification of the electronic signature attached to the identity verification VCs.
[0184] In this case, the account control unit 402 obtains the issuer DID and user DID listed in the identity verification VCs. The account control unit 402 obtains the public key corresponding to the obtained issuer DID from the blockchain. Similarly, the account control unit 402 obtains the public key corresponding to the obtained user DID from the blockchain.
[0185] The account control unit 402 verifies the signature of the holder (the user who wishes to back up) and the signature of the issuer attached to the identity verification VCs. By verifying these signatures, the account control unit 402 confirms that the identity verification VCs obtained from the user have not been tampered with and that they are certificates issued by a trusted issuer.
[0186] The account control unit 402 determines that the verification of identity verification VCs has been successful if it successfully verifies the signatures of both the holder and issuer of the identity verification VCs. The account control unit 402 determines that the verification of identity verification VCs has failed if it fails to verify the signature of at least one of the holder or issuer of the identity verification VCs.
[0187] The second item is to verify that identity verification VCs are not set to disabled.
[0188] In this case, the account control unit 402 accesses the blockchain and VDR using the credential ID and issuer DID to confirm that the received identity verification VCs are not listed in the certificate issuer's revocation list. The account control unit 402 also confirms that the identity verification VCs obtained from the user have not been invalidated by the issuer before their expiration date.
[0189] The account control unit 402 determines that the verification of identity verification VCs was successful if the credential certificate is not listed in the revocation list. The account control unit 402 determines that the verification of identity verification VCs failed if the identity verification VCs are listed in the revocation list.
[0190] The third item is verification that the validity period (expiration date) of the identity verification VCs has not expired.
[0191] The account control unit 402 checks the validity period set for the identity verification VCs. If the validity period set for the identity verification VCs has not expired, the account control unit 402 determines that the verification of the acquired identity verification VCs was successful. If the validity period set for the identity verification VCs has expired, the account control unit 402 determines that the verification of the acquired identity verification VCs failed.
[0192] The account control unit 402 determines that the verification of the identity verification VCs obtained from the user has been successful if it determines that "verification was successful" in one of the predetermined items from the first to third items.
[0193] If the account control unit 402 determines that "verification failed" in one of the predetermined items from the first to third items, it determines that the verification of the identity verification VCs obtained from the user has failed.
[0194] If the verification of the identity verification VCs is successful, the account control unit 402 generates the user's account. More specifically, the account control unit 402 stores the name, gender, date of birth, etc. obtained above, as well as the end-user ID obtained from the identity verification VCs, in the user management database (see Figure 14). Note that the user management database shown in Figure 14 is an example and is not intended to limit the items to be stored.
[0195] The backup control unit 403 is a means for controlling the backup and restoration of user-held credential certificates.
[0196] The backup control unit 403 receives from the user's terminal 40 an identity verification certificate (e.g., identity verification VCs) that proves that identity verification has been performed using the user's identification document and includes the user's ID (e.g., end-user ID). Upon receiving the identity verification certificate, the backup control unit 403 sends a certificate reissuance request to each server device 10 managed by the issuer of each of the at least one certificates held by the user, including the certificate ID corresponding to the certificate issued by each issuer. The certificate ID is, for example, a credential ID.
[0197] The backup control unit 403 receives a backup request from the user's terminal 40.
[0198] Upon receiving a backup request, the backup control unit 403 verifies the credential certificate included in the backup request. For example, the backup control unit 403 verifies the received credential certificate for the three items described above.
[0199] If the verification of the credential certificate fails, the backup control unit 403 determines that the backup is not possible. In this case, the backup control unit 403 sends a negative response (response to the backup request) to the terminal 40 indicating that the backup failed.
[0200] If the verification of the credential certificate is successful, the backup control unit 403 executes the backup process for the received credential certificate.
[0201] Specifically, the backup control unit 403 obtains the end-user ID from the credential certificate to be backed up. The backup control unit 403 searches the user management database using the obtained end-user ID as a key and identifies the corresponding entry.
[0202] The backup control unit 403 stores information about the credential certificate to be backed up in the identified entry. More specifically, the backup control unit 403 stores the name of the certificate issuer, the credential ID, and the verification result (verification successful) of the credential certificate in the credential certificate information field of the user management database.
[0203] Note that CID01 and CID02 shown in Figure 14 represent credential IDs.
[0204] Once the information regarding the credential certificate is stored in the user management database, the backup control unit 403 sends an acknowledgment (response to the backup request) to the terminal 40 indicating that the backup was successful.
[0205] The backup control unit 403 then discards the credential certificate to be backed up (the credential certificate obtained from terminal 40).
[0206] In this manner, the backup control unit 403 receives a backup request from the user's terminal 40, which includes a certificate (e.g., a credential certificate) newly acquired by the user. The backup control unit 403 obtains the user's ID (e.g., an end-user ID), information about the issuer, and the certificate ID from the certificate included in the backup request. The backup control unit 403 writes the obtained user ID, information about the issuer, and certificate ID to the user management database. More specifically, the backup control unit 403 writes the user's ID, information about the issuer, and certificate ID to the user management database if it successfully verifies the certificate included in the backup request.
[0207] The backup control unit 403 receives a certificate restoration request from the terminal 40.
[0208] Upon receiving a certificate restoration request, the backup control unit 403 verifies the identity verification VCs included in the certificate restoration request.
[0209] If the verification of the identity verification VCs fails, the backup control unit 403 determines that the credential certificate cannot be restored. In this case, the backup control unit 403 sends a negative response (response to the certificate restoration request) to the terminal 40 indicating that the credential certificate cannot be restored.
[0210] If the verification of the identity verification VCs is successful, the backup control unit 403 executes the process of restoring the credential certificate held by the user.
[0211] Specifically, the backup control unit 403 searches the user management database using the end-user ID obtained from the identity verification VCs as a key and identifies the corresponding entry. The backup control unit 403 retrieves the information regarding the credential certificate (certificate issuer name, credential ID) stored in the identified entry.
[0212] The backup control unit 403 requests each certificate issuer to reissue the credential certificates held by the user.
[0213] Specifically, the backup control unit 403 sends a "certificate reissuance request" including at least the credential ID to the server device 10 of the certificate issuer that has the authority to issue the credential certificate to be reissued.
[0214] For example, if a user possesses a Skills Certificate VCs, the backup control unit 403 sends a certificate reissuance request, including the credential ID of the Skills Certificate VCs, to the server device 10 of the organization that issued the Skills Certificate VCs. Similarly, if a user possesses a Qualification Certificate VCs, the backup control unit 403 sends a certificate reissuance request, including the credential ID of the Qualification Certificate VCs, to the server device 10 of the Qualification Certification Body that issued the Qualification Certificate VCs.
[0215] The backup control unit 403 receives responses (affirmative responses, negative responses) from each server device 10 that sent a certificate reissuance request.
[0216] If the received response does not include a negative response (a response indicating failure to reissue the credential certificate), the backup control unit 403 sends the certificate acquisition URL included in the affirmative response received from each server device 10 to the terminal 40. Specifically, the backup control unit 403 sends an affirmative response (a response to the certificate restoration request) to the terminal 40 that includes at least one certificate acquisition URL.
[0217] If the received response includes a negative response, the backup control unit 403 may determine that the restoration of the credential certificate has failed. In this case, the backup control unit 403 sends a negative response to the terminal 40 indicating this.
[0218] Alternatively, the backup control unit 403 may notify the terminal 40 of the URL for obtaining the reissued credential certificate. For example, the backup control unit 403 may send an acknowledgment to the terminal 40 that includes the URL for obtaining the reissued credential certificate and the name of the credential certificate that was not reissued.
[0219] Thus, the backup control unit 403 sends a certificate reissuance request if it successfully verifies the identity verification certificate (identity verification VCs). More specifically, the identity verification certificate includes the user's ID (end-user ID), and the backup control unit 403 extracts the user's ID from the identity verification certificate. Based on the extracted user ID, the backup control unit 403 identifies the certificate ID of the certificate to be reissued (the certificate to which reissuance is requested) and the server device 10 to which the certificate reissuance request will be sent.
[0220] The storage unit 404 is a means for storing information necessary for the operation of the management server 20. For example, the storage unit 404 stores the name of the certificate issuer and the address of the server device 10 managed by that certificate issuer in association with each other.
[0221] The storage unit 404 is configured with a user management database that stores the user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of those at least one certificates. The user management database stores the user's ID (e.g., end-user ID), information about the issuer (e.g., name of the certificate issuer), and certificate ID (e.g., credential ID) in association with each other.
[0222] [Service Server] Figure 15 is a diagram showing an example of the processing configuration (processing module) of a service server 30 according to the embodiment of the present disclosure. Referring to Figure 15, the service server 30 comprises a communication control unit 501, a service provision control unit 502, and a storage unit 503.
[0223] The communication control unit 501 is a means for controlling communication with other devices. For example, the communication control unit 501 receives data (packets) from the terminal 40. The communication control unit 501 also transmits data to the terminal 40. The communication control unit 501 passes the data received from other devices to other processing modules. The communication control unit 501 transmits the data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data with other devices via the communication control unit 501. The communication control unit 501 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.
[0224] The service provision control unit 502 is a means for performing control related to the services provided to the user.
[0225] When a user accesses a designated webpage or the like and requests to receive a service, the service provision control unit 502 obtains the necessary certificate (credential certificate) for providing the service.
[0226] For example, the service provision control unit 502 of a service provider that provides job placement support services acquires certificates of skills held, certificates of qualifications held, etc.
[0227] Specifically, the service provision control unit 502 sends a "certificate provision request" to the terminal 40. The service provision control unit 502 sends a certificate provision request to the terminal 40 that includes information about at least one certificate necessary for the service provider to provide the service (for example, the type of certificate).
[0228] If the terminal 40 receives a negative response (inability to provide the certificate), the service provision control unit 502 notifies the user that it cannot provide the service because it cannot obtain the necessary information.
[0229] When the service provision control unit 502 receives an acknowledgment (a response including a credential certificate) from terminal 40, it verifies the credential certificate included in the acknowledgment.
[0230] If the verification of the credential certificate fails, the service provision control unit 502 notifies the user that it cannot provide the service because it cannot obtain the necessary information.
[0231] If the credential certificate is successfully verified, the service provision control unit 502 provides the service to the user.
[0232] Further detailed explanations regarding individual service provision are omitted. This is because detailed explanations of services specific to each service provider would be inconsistent with the purpose of this disclosure.
[0233] The memory unit 503 is a means for storing information necessary for the operation of the service server 30.
[0234] [System Operation] Next, the operation of the information processing system according to the first embodiment will be described.
[0235] Figure 16 is a sequence diagram showing an example of the operation of the information processing system according to the embodiment disclosed herein. Referring to Figure 16, the operation of the information processing system according to the first embodiment concerning the backup of credential certificates will be described.
[0236] When terminal 40 obtains a credential certificate other than identity verification VCs, it sends a backup request including the obtained credential certificate to the management server 20 (step S41).
[0237] The management server 20 extracts the end-user ID from the credential certificate and identifies the user account corresponding to the extracted end-user ID. The management server 20 stores the information of the credential certificate to be backed up in the identified user account (stores VCs information; step S42).
[0238] The management server 20 sends a response (affirmative response, negative response) to the backup request to the terminal 40 (step S43). If the backup is successful, the management server 20 sends an affirmative response to the terminal 40 indicating that it is successful. If the backup fails, the management server 20 sends a negative response to the terminal 40 indicating that it is failed.
[0239] Figure 17 is a sequence diagram showing an example of the operation of the information processing system according to the embodiment disclosed herein. Referring to Figure 17, the operation relating to the restoration of the credential certificate of the information processing system according to the first embodiment will be described.
[0240] Terminal 40 obtains identity verification VCs (step S51).
[0241] Terminal 40 sends a certificate restoration request, including identity verification VCs, to the management server 20 (step S52).
[0242] The management server 20 extracts end-user IDs from the identity verification VCs and identifies the user corresponding to the extracted end-user ID. The management server 20 sends a certificate reissuance request to the server device 10 of each certificate issuer that issued the credential certificate held by the identified user (step S53).
[0243] The management server 20 sends a certificate reissuance request, including the credential ID associated with the end-user ID, to each server device 10.
[0244] Each server device 10 invalidates the credential certificate corresponding to the acquired credential ID and reissues a credential with the same content as the credential certificate corresponding to the acquired credential ID (step S54).
[0245] Each server device 10 notifies the management server 20 of the URL for obtaining the certificate from the online storage where the reissued credential certificate is stored (notification of URL; step S55). Each server device 10 sends an acknowledgment including the URL for obtaining the certificate to the management server 20.
[0246] The management server 20 notifies the terminal 40 of the URL for obtaining the certificate (notification of URL; step S56). The management server 20 sends an acknowledgment to the terminal 40 that includes the URL for obtaining the certificate notified by each server device 10.
[0247] Terminal 40 accesses online storage according to the URL for obtaining the certificate and obtains the reissued credential certificate (step S57).
[0248] Next, a modified example of the first embodiment will be described.
[0249] <Modification 1> In the above embodiment, the case in which the local government's server device 10 issues identity verification VCs was described. However, identity verification VCs may be issued by other organizations. For example, identity verification VCs may be issued by the My Number Card certification authority (J-LIS). In this case, when the certification authority server 50 obtains the user authentication electronic certificate from the local government's server device 10, it generates identity verification VCs. The certification authority server 50 stores the generated identity verification VCs in online storage and notifies the local government's server device 10 of the corresponding certificate acquisition URL. The local government's server device 10 notifies the terminal 40 of the notified certificate acquisition URL.
[0250] <Modification 2> In the above embodiment, when requesting the issuance of a credential certificate from a certificate issuer, the terminal 40 sent a certificate issuance request including the end-user ID to the server device 10. However, the terminal 40 may also send a certificate issuance request including identity verification VCs instead of the end-user ID to the server device 10.
[0251] The server device 10 may obtain an end-user ID from the identity verification VCs and issue a credential certificate using the obtained end-user ID. Alternatively, the server device 10 may issue a credential certificate if it successfully verifies the identity verification VCs included in the certificate issuance request.
[0252] As described above, the management server 20 according to the first embodiment verifies the identity verification VCs when generating a backup account for a user. If the verification of the identity verification VCs is successful, the management server 20 generates a backup account. At that time, the management server 20 stores the end user ID obtained from the identity verification VCs in the account. When the management server 20 obtains the credential certificate to be backed up from the terminal 40, it extracts the end user ID from the credential certificate. Based on the extracted end user ID, the management server 20 identifies the holder of the credential certificate (the holder's account) and stores information about the credential certificate to be backed up in the identified account. When a user requests the restoration of the credential certificate, the management server 20 obtains the identity verification VCs that the user has re-obtained. The management server 20 verifies the obtained identity verification VCs. If the verification of the identity verification VCs is successful, the management server 20 uses the end-user ID obtained from the identity verification VCs to identify the applicant (applicant's account) requesting the reissuance of the credential certificate. The management server 20 uses the information stored in the identified account to request the certificate issuer to reissue the credential certificate held by the user. The management server 20 notifies the user's terminal 40 of the storage location of the reissued credential certificates from each certificate issuer. Through this operation of the management server 20, the user can obtain the credential certificate that was stored in the lost terminal 40 simply by obtaining identity verification VCs from a new terminal 40 and providing the obtained identity verification VCs to the management server 20. In other words, the user does not need to request (apply for) the reissuance of the credential certificate from each certificate issuer, thus reducing the burden on users who wish to have their certificates reissued.
[0253] [Second Embodiment] Next, a second embodiment will be described in detail with reference to the drawings.
[0254] In the first embodiment, the case in which the management server 20 requests each certificate issuer to reissue the credential certificate held by the user was described. In the second embodiment, the case in which the terminal 40 held by the user requests each certificate issuer to reissue the credential certificate is described.
[0255] Note that the configuration of the information processing system according to the second embodiment can be the same as that of the first embodiment, so the explanation corresponding to Figure 3 is omitted. Also, the processing configuration of the management server 20, etc., according to the second embodiment can be the same as that of the first embodiment, so its explanation is omitted.
[0256] The following will focus on explaining the differences between the first and second embodiments.
[0257] Figure 18 is a sequence diagram showing an example of the operation of the information processing system according to the embodiment disclosed herein. The operation of the information processing system according to the second embodiment will be described with reference to Figure 18.
[0258] Terminal 40 acquires identity verification VCs, similar to the first embodiment, and sends a certificate restoration request including the acquired identity verification VCs to the management server 20 (steps S61, S62).
[0259] When the management server 20 receives a certificate restoration request, it notifies the terminal 40 of information regarding the credential certificate held by the user. Specifically, the backup control unit 403 of the management server 20 verifies the identity verification VCs included in the certificate restoration request. If the verification of the identity verification VCs is successful, the backup control unit 403 obtains (extracts) the end-user ID from the identity verification VCs.
[0260] The backup control unit 403 searches the user management database using the acquired end-user ID as a key and identifies the corresponding entry. The backup control unit 403 retrieves information about the credential certificate (certificate issuer name, credential ID, etc.) stored in the identified entry. The backup control unit 403 notifies the terminal 40 of the retrieved information about the credential certificate.
[0261] Specifically, the backup control unit 403 sends a "certificate possession notification" to the terminal 40 that includes information about the acquired credential certificate (for example, a list consisting of a combination of the certificate issuer name and the credential ID) (step S63).
[0262] Upon receiving the certificate of possession notification, terminal 40 (backup control unit 204) identifies the certificate issuer authorized to issue the credential certificate held by the user, based on the information about the credential certificate included in the notification (e.g., the name of the certificate issuer). Terminal 40 then sends a "certificate reissuance request" containing the corresponding credential ID to the server device 10 of at least one of the identified certificate issuers (step S64).
[0263] Each server device 10 that receives a certificate reissuance request invalidates the credential certificate corresponding to the credential ID included in the certificate reissuance request, similar to the first embodiment. Furthermore, each server device 10 generates (reissues) a credential certificate with the same content as the credential certificate corresponding to the credential ID included in the certificate reissuance request (step S65).
[0264] Each server device 10 stores the generated credential certificate in online storage and notifies the terminal 40 of the location where the credential certificate is stored. Specifically, the server device 10 sends an acknowledgment (response to the request for reissuance of the certificate) including a URL for obtaining the certificate to the terminal 40 (notification of the URL; step S66).
[0265] Terminal 40 (backup control unit 204) accesses the URL for obtaining the certificate included in the acknowledgment and obtains the reissued credential certificate (step S67). Terminal 40 stores the obtained credential certificate in the digital wallet.
[0266] As described above, in the second embodiment, the management server 20 may, upon receiving an identity verification certificate, send a certificate possession notification to the terminal 40 containing information about the issuer of each of the at least one certificates held by the user, along with a credential ID. Using the information contained in the certificate possession notification, the user's terminal 40 may request each certificate issuer to reissue the credential certificates held by the user. The user can obtain the credential certificates stored in the lost terminal 40 simply by obtaining identity verification VCs from the new terminal 40 and providing the obtained identity verification VCs to the management server 20. As a result, the burden on users who wish to have their certificates reissued is reduced.
[0267] Next, we will describe the hardware of each device that makes up the information processing system. Figure 19 shows an example of the hardware configuration of the management server 20.
[0268] The management server 20 can be configured using an information processing device (a so-called computer), and has the configuration illustrated in Figure 19. For example, the management server 20 includes a processor 311, memory 312, input / output interface 313, and communication interface 314, etc. The components of the processor 311, etc., are connected by an internal bus or the like and are configured to communicate with each other.
[0269] However, the configuration shown in Figure 19 is not intended to limit the hardware configuration of the management server 20. The management server 20 may include hardware not shown, and it may not have to have an input / output interface 313 if necessary. Also, the number of processors 311 etc. included in the management server 20 is not intended to be limited to the example in Figure 19; for example, multiple processors 311 may be included in the management server 20.
[0270] The processor 311 is a programmable device such as a CPU (Central Processing Unit), MPU (Micro Processing Unit), or DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs, including an operating system (OS).
[0271] Memory 312 can be RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc. Memory 312 stores the OS program, application programs, and various data.
[0272] The input / output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user input such as a keyboard or mouse.
[0273] The communication interface 314 is a circuit, module, etc., that communicates with other devices. For example, the communication interface 314 may include a NIC (Network Interface Card).
[0274] The functions of the management server 20 are realized by various processing modules. These processing modules are realized, for example, by the processor 311 executing a program stored in memory 312. The program can also be recorded on a computer-readable storage medium. The storage medium can be a non-transitory material such as semiconductor memory, hard disk, magnetic recording medium, or optical recording medium. In other words, the present invention can also be embodied as a computer program product. Furthermore, the program can be downloaded via a network or updated using the storage medium on which the program is stored. Moreover, the processing module may be realized by a semiconductor chip.
[0275] Furthermore, the server device 10, service server 30, and terminal 40, etc., can also be configured using information processing devices, similar to the management server 20. Since their basic hardware configurations are no different from those of the management server 20, a detailed explanation will be omitted.
[0276] The management server 20, which is an information processing device, is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the management server 20 executes a control method for the management server 20 using this program. Similarly, the terminal 40 is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the terminal 40 executes a control method for the terminal 40 using this program.
[0277] [Modification] Note that the configuration and operation of the information processing system described in the above embodiment are illustrative examples and are not intended to limit the system configuration.
[0278] The above embodiment describes a case where terminal 40 performs identity verification using a My Number Card. However, this identity verification may also be performed by the server device 10. Specifically, terminal 40 sends a certificate issuance request to the server device 10, which includes a facial image read from the My Number Card, a facial image obtained by taking a selfie, and a user authentication electronic certificate. If the server device 10 succeeds in identity verification using the two facial images, it may send the user authentication electronic certificate to the certification authority server 50 to obtain an end-user ID.
[0279] In the above embodiment, identity verification was described as being performed using a facial image obtained from a My Number Card and a facial image obtained from a selfie. However, identity verification may be performed by other methods. For example, the terminal 40 may determine that identity verification has been successful if it is able to read information from the IC card of the My Number Card using a four-digit PIN.
[0280] The above embodiment describes a case where identity verification is performed using a My Number Card. However, identity verification may be performed using other forms of identification. For example, terminal 40 may perform identity verification using a facial image obtained from the IC chip of the passport and a facial image obtained from a selfie. In this case, terminal 40 may send a certificate issuance request including the passport number obtained from the passport to the Ministry of Foreign Affairs server device 10. The Ministry of Foreign Affairs server device 10 may issue identity verification VCs using the passport number as the end-user ID.
[0281] In the above embodiment, when a new credential certificate is stored in the digital wallet, the terminal 40 automatically sends a backup request including the new credential certificate to the management server 20. Alternatively, the terminal 40 may periodically access the digital wallet and, when a new credential certificate is stored in the digital wallet, send a backup request including the newly stored credential certificate to the management server 20. Alternatively, instead of automatically sending a backup request, the terminal 40 may send a backup request to the management server 20 only when it receives instructions from the user.
[0282] Terminal 40 may provide an interface that allows the user to select the credential certificate to be backed up from among the credential certificates stored in the digital wallet.
[0283] In the above embodiment, the case was described in which the URL for obtaining the reissued credential certificate is sent to the terminal 40 via the management server 20. However, the URL for obtaining the certificate may also be sent directly from the server device 10 to the terminal 40. In this case, the management server 20 only needs to send a certificate reissue request to each server device 10, which includes the email address to which the URL for obtaining the certificate will be sent (an email address that the terminal 40 can receive).
[0284] In the above embodiment, the case was described in which the certificate issuer's server device 10 issues a credential certificate that does not require a Certificate Authority for verification. However, the server device 10 may also issue a certificate that requires a Certificate Authority (a public key infrastructure-based certificate).
[0285] Some functions of the management server 20, etc., may be implemented in other devices or equipment. More specifically, it is sufficient if the "backup control unit (backup control means)" etc. described above is implemented in any of the devices included in the system.
[0286] The form of data transmission and reception between each device (for example, server device 10, terminal 40) is not particularly limited, but the data transmitted and received between these devices may be encrypted. Personal information of users is transmitted and received between these devices, and it is desirable that encrypted data be transmitted and received in order to appropriately protect this information.
[0287] In the flowcharts (sequence diagrams) used in the above description, multiple processes are shown in order, but the execution order of the processes performed in the embodiment is not limited to the order in which they are shown. In the embodiment, the order of the illustrated processes can be changed to the extent that it does not impede the content, for example, by executing each process in parallel.
[0288] The embodiments described above are explained in detail to facilitate understanding of the disclosure, and it is not intended that all the configurations described above are necessary. Furthermore, when multiple embodiments are described, each embodiment may be used individually or in combination. For example, it is possible to replace parts of the configuration of one embodiment with those of another embodiment, or to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of one embodiment with those of another.
[0289] As described above, the industrial applicability of the present invention is clear, and it is particularly applicable to information processing systems that back up and restore credential certificates stored in digital wallets.
[0290] Some or all of the above embodiments may also be described as follows, but are not limited to the following:
[0291] [Note 1] An information processing device comprising: a storage means that stores the user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database; and a control means that controls the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, which proves that the user's identity has been verified.
[0292] [Note 2] The information processing device according to Note 1, wherein the control means transmits a certificate possession notification to the user's terminal, which includes information about the issuer of each of the at least one certificates held by the user and the certificate ID, in response to receiving the identity verification certificate from the user's terminal.
[0293] [Note 3] The information processing device according to Note 1, wherein the control means, upon receiving the identity verification certificate from the user's terminal, transmits a certificate reissuance request, including the certificate ID corresponding to the certificate issued by each issuer, to each server managed by the issuer of each of the at least one certificates held by the user.
[0294] [Note 4] The control means is the information processing device described in Note 3, which transmits a request for reissuance of the certificate when the verification of the identity verification certificate is successful.
[0295] [Note 5] The information processing device according to Note 3 or 4, wherein the control means receives a backup request from the user's terminal, including a certificate newly acquired by the user; obtains the user's ID, information about the issuer, and a certificate ID from the certificate included in the backup request; and writes the obtained user's ID, information about the issuer, and certificate ID to the database.
[0296] [Note 6] The information processing device described in Note 5, wherein the control means writes the user's ID, information about the issuer, and the certificate ID to the database when the verification of the certificate included in the backup request is successful.
[0297] [Note 7] The information processing device described in Note 6, wherein the control means extracts the user's ID from the identity verification certificate, and based on the extracted user's ID, identifies the certificate ID of the certificate subject to reissuance and the server to which the certificate reissuance request will be sent.
[0298] [Note 8] The information processing device described in Note 7, wherein the identity verification certificate is a credential certificate issued by a public institution when the user performs identity verification using an identification document issued by the public institution.
[0299] [Note 9] The user ID is the end-user ID corresponding to the user authentication electronic certificate, as described in Note 8.
[0300] [Note 10] A system comprising: a terminal owned by a user; multiple server devices managed by each of multiple certificate issuers; and a management server, wherein the management server includes: a storage means that stores the user's ID, information about the issuers of at least one certificate owned by the user, and the certificate ID of each of the at least one certificate using a database; and a control means that controls the reissuance of at least one certificate owned by the user in response to receiving an identity verification certificate, which includes the user's ID, from the terminal owned by the user, which proves that the user's identity has been verified.
[0301] [Note 11] A control method for an information processing device, wherein the information processing device stores the user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database, and controls the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, which proves that the user's identity has been verified.
[0302] [Note 12] A computer-readable storage medium that stores a program for causing a computer mounted on an information processing device to perform the following: a process of storing a user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates, using a database; and a process of controlling the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, which proves that the user's identity has been verified.
[0303] Furthermore, some or all of the configurations described in Appendices 2 to 7, which are subordinate to Appendice 1 above, may also be subordinate to Appendices 8 to 10 in the same way as Appendices 2 to 7. Moreover, not limited to Appendice 1 and Appendices 8 to 10, some or all of the configurations described as appendices may also be subordinate to various hardware, software, various recording means for recording software, or systems, without departing from the embodiments described above.
[0304] Furthermore, each disclosure of the above-mentioned prior art documents cited herein is incorporated herein by reference. Although embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. That is, the present invention naturally includes the entire disclosure, including the claims, and various modifications and alterations that can be made by those skilled in the art in accordance with the technical idea.
[0305] 10 Server device 20 Management server 30 Service server 40 Terminal 50 Certification authority server 100 Information processing device 101 Storage means 102 Control means 201 Communication control unit 202 Acquisition control unit 203 Utilization control unit 204 Backup control unit 205 Storage unit 301 Communication control unit 302 Certificate issuance unit 303 Certificate reissuance unit 304 Storage unit 311 Processor 312 Memory 313 Input / output interface 314 Communication interface 401 Communication control unit 402 Account control unit 403 Backup control unit 404 Storage unit 501 Communication control unit 502 Service provision control unit 503 Storage unit
Claims
1. An information processing device comprising: a storage means that stores the user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database; and a control means that controls the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, which proves that the user's identity has been verified.
2. The information processing device according to claim 1, wherein the control means, upon receiving the identity verification certificate from the user's terminal, transmits a certificate possession notification to the user's terminal, which includes information about the issuer of each of the at least one certificates held by the user and the certificate ID.
3. The information processing apparatus according to claim 1, wherein the control means, upon receiving the identity verification certificate from the user's terminal, transmits a certificate reissuance request, including the certificate ID corresponding to the certificate issued by each issuer, to each server managed by the issuer of each of the at least one certificates held by the user.
4. The information processing device according to claim 3, wherein the control means transmits a request for reissuance of the identification certificate when the verification of the identification certificate is successful.
5. The information processing apparatus according to claim 3 or 4, wherein the control means receives a backup request from the user's terminal, which includes a certificate newly acquired by the user; obtains the user's ID, information about the issuer, and a certificate ID from the certificate included in the backup request; and writes the obtained user's ID, information about the issuer, and certificate ID to the database.
6. The information processing apparatus according to claim 5, wherein the control means writes the user's ID, information about the issuer, and the certificate ID to the database when it has successfully verified the certificate included in the backup request.
7. The information processing apparatus according to claim 6, wherein the control means extracts the user's ID from the identity verification certificate, and based on the extracted user's ID, identifies the certificate ID of the certificate subject to reissuance and the server to which the certificate reissuance request will be sent.
8. The information processing device according to claim 7, wherein the identity verification certificate is a credential certificate issued by a public institution when the user performs identity verification using an identification document issued by the public institution.
9. The information processing apparatus according to claim 8, wherein the user ID is an end-user ID corresponding to a user authentication electronic certificate.
10. A system comprising: a terminal owned by a user; multiple server devices managed by each of multiple certificate issuers; and a management server, wherein the management server includes: a storage means for storing the user's ID, information about the issuers of at least one certificate owned by the user, and the certificate ID of each of the at least one certificate, using a database; and a control means for controlling the reissuance of at least one certificate owned by the user in response to receiving a certificate proving that the user's identity has been verified, which includes the user's ID, from the terminal owned by the user.
11. A control method for an information processing device, which stores the user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates using a database, and which controls the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, that proves the identity of the user has been verified.
12. A computer-readable storage medium that stores a program for causing a computer mounted on an information processing device to perform the following: a process of storing a user's ID, information about the issuer of each of the at least one certificates held by the user, and the certificate ID of each of the at least one certificates, using a database; and a process of controlling the reissuance of each of the at least one certificates held by the user in response to receiving an identity verification certificate, which includes the user's ID, from the user's terminal, which proves that the user's identity has been verified.