System, server device, server device control method, and storage medium

The system addresses the inefficiency of verifying multiple user certificates by integrating a user terminal, verification devices, and an information sharing device to provide pre-verified user information to third parties, thereby reducing the verification burden on businesses.

WO2026133440A1PCT designated stage Publication Date: 2026-06-25NEC CORP

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
NEC CORP
Filing Date
2024-12-18
Publication Date
2026-06-25

Smart Images

  • Figure JP2024044705_25062026_PF_FP_ABST
    Figure JP2024044705_25062026_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a system for reducing the burden on business operators and the like that require information about users who possess prescribed qualifications or the like. The system includes: a terminal held by a user to whom a plurality of certificates have been issued; a plurality of verification devices, each of which verifies the corresponding one of the certificates; and an information coordination device. Each of the plurality of verification devices notifies the information coordination device of the verification result of the certificate to be verified by the verification device. The information coordination device provides information about the user to a third party if the verification result of each of the plurality of certificates is successful.
Need to check novelty before this filing date? Find Prior Art

Description

System, Server Device, Control Method of Server Device, and Storage Medium

[0001] The present invention relates to a system, a server device, a control method of a server device, and a storage medium.

[0002] There is a technology for introducing human resources via a network.

[0003] For example, Patent Document 1 describes providing a human resource introduction method and a human resource introduction system using an electronic authentication technology that can provide a recruiter with highly reliable information about the qualifications held by a registrant when introducing human resources via a network. The user terminal of Patent Document 1 receives a qualification certificate with an electronic signature of the qualification certificate issuing authority from the qualification certificate issuing authority server. Then, the user terminal generates a user electronic signature using the user's private key for the received qualification certificate, and transmits the qualification certificate with this user electronic signature to the job hunting / transfer site server. The job hunting / transfer site server decrypts and verifies the user electronic signature using the user's public key. Then, the job hunting / transfer site server extracts the electronic signature of the qualification certificate issuing authority, decrypts and verifies this electronic signature of the qualification certificate issuing authority using the public key of the qualification certificate issuing authority. Then, the job hunting / transfer site server compares the name of the subject person included in the qualification certificate with the name included in the user's electronic certificate, and registers it as the user's qualification if they match.

[0004] Japanese Patent Application Laid-Open No. 2006-163832

[0005] As described in Patent Document 1, the qualifications and the like held by a user are proved by an electronic proof certificate. Usually, a user holds a proof certificate corresponding to their academic background, work experience, qualifications, etc. Also, companies and the like that utilize proof certificates often confirm whether a user has the qualifications required by their company based on a plurality of proof certificates. Here, for companies and the like that utilize proof certificates, verifying the above plurality of proof certificates is a significant burden.

[0006] A main object of the present invention is to provide a system, a server device, a control method of a server device, and a storage medium that contribute to reducing the burden on business operators and the like that require information about users having predetermined qualifications and the like.

[0007] According to a first aspect of the present invention, a system is provided which includes a terminal owned by a user to whom multiple certificates have been issued, multiple verification devices, each of which verifies the corresponding certificate, and an information sharing device, wherein each of the multiple verification devices notifies the information sharing device of the verification result of the certificate it is verifying, and the information sharing device provides information about the user to a third party if the verification result of each of the multiple certificates is successful.

[0008] According to a second aspect of the present invention, a server device is provided that includes an acquisition means for acquiring verification results of certificates that each verification device is subject to verification from each of a plurality of verification devices, and a provision means for providing information to a third party about the user to whom the plurality of certificates were issued if the verification results of each of the plurality of certificates are successful.

[0009] A third aspect of the present invention provides a server control method that obtains verification results for certificates targeted for verification by each of a plurality of verification devices from each of a plurality of verification devices, and if the verification results for each of the plurality of certificates are successful, provides to a third party information about the user to whom the plurality of certificates were issued.

[0010] According to a fourth aspect of the present invention, a computer-readable storage medium is provided that stores a program for causing a computer mounted on a server device to execute the following: a process of obtaining the verification results of certificates that each verification device is verifying from each of a plurality of verification devices, and a process of providing information to a third party regarding the user to whom the plurality of certificates were issued if the verification results of each of the plurality of certificates are successful.

[0011] From each perspective of the present invention, a system, a server device, a control method for a server device, and a storage medium are provided that contribute to reducing the burden on businesses and other entities that require information on users who possess certain qualifications. However, the effects of the present invention are not limited to those described above. The present invention may also produce other effects in lieu of or in conjunction with the effects described above.

[0012] 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 showing an example of the processing configuration of a terminal according to an embodiment of this disclosure. Figure 8 is a flowchart showing an example of the operation of an acquisition control unit according to an embodiment of this disclosure. Figure 9 is a flowchart showing an example of the operation of a utilization control unit according to an embodiment of this disclosure. Figure 10 is a diagram showing an example of the display of a terminal according to an embodiment of this disclosure. Figure 11 is a diagram showing an example of the processing configuration of a server device according to an embodiment of this disclosure. Figure 12 is a diagram showing an example of the processing configuration of a service server according to an embodiment of this disclosure. Figure 13 is a diagram illustrating the operation of a service provision control unit according to an embodiment of this disclosure. Figure 14 is a diagram showing an example of the processing configuration of a collaborative server according to an embodiment of this disclosure. Figure 15 is a diagram showing an example of a worker management database according to an embodiment of this disclosure. Figure 16 is a flowchart showing an example of the operation of a service provision control unit 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 an embodiment of this disclosure. Figure 18 is a sequence diagram showing an example of the operation of an information processing system according to an embodiment of this disclosure. Figure 19 is a diagram showing an example of the hardware configuration of a cooperating server according to this disclosure. Figure 20 is a diagram showing an example of the display of a terminal according to a modified example of this disclosure.

[0013] 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.

[0014] One embodiment of the system includes a terminal 101 held by a user to whom multiple certificates have been issued, multiple verification devices 102, each performing verification of a corresponding certificate, and an information sharing device 103 (see Figure 1). Each of the multiple verification devices 102 notifies the information sharing device 103 of the verification result of the certificate it is verifying (step S1 in Figure 2). If the verification result of each of the multiple certificates is successful, the information sharing device 103 provides information about the user to a third party (step S2).

[0015] The system described above involves a verification device 102 that verifies each of the multiple certificates held by the user and notifying the information sharing device 103 of the verification results. The information sharing device 103 then combines the verification results received from each verification device 102 to generate user information required by a third party. For example, the information sharing device 103 provides the third party with information (e.g., name, facial image, etc.) of a person whose qualifications and skills the third party requires the user to possess have been verified in advance. In other words, the third party does not need to verify whether the user truly possesses the necessary qualifications and skills. The third party only needs to accept information about the user that has been pre-verified by the information sharing device 103. As a result, the burden on businesses and other entities that require information about users who possess the prescribed qualifications is reduced.

[0016] Specific embodiments will be described in more detail below with reference to the drawings.

[0017] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0018] [System Configuration] As shown in Figure 3, the information processing system according to the first embodiment includes at least one certificate issuer, an information sharing business operator, and at least one service provider.

[0019] 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."

[0020] 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.

[0021] Alternatively, the certificate issuer may issue a certificate proving that the user has completed the prescribed training, a certificate proving the skills the user possesses, a certificate proving the qualifications the user holds, etc.

[0022] Furthermore, certificate issuers also act as certificate verifiers, verifying the certificates they themselves issue. For example, a training institution that organizes training programs issues certificates related to the training completed by users and also verifies those certificates.

[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] The server device 10 also functions as a verification device, which verifies certificates issued by itself. The information processing system includes multiple verification devices, each of which verifies the corresponding certificates.

[0025] An information sharing service provider is a business that manages information about users and provides that user information to service providers. More specifically, an information sharing service provider provides a service that links various types of information held by users and provides that linked information to third parties.

[0026] The information sharing service provider has a sharing server 20. The sharing server 20 is a server that performs the processing and operations necessary to carry out the information sharing service provider's business. The sharing server 20 operates as an information sharing device. The sharing server 20 may be installed in the building of the information sharing service provider or it may be installed on a network (on the cloud).

[0027] A service provider is a business that provides services to individuals, companies, etc. For example, a service provider may obtain information on personnel needed in a specific industry or sector from information sharing businesses and provide that information. Service providers are not limited to private companies; public institutions such as city halls are also included as service providers in the disclosures made in this application.

[0028] 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).

[0029] The user possesses terminal 40. For example, the user operates terminal 40 to request (demand) the issuance of a certificate from the certificate issuer. Terminal 40 is possessed by multiple users who have been issued certificates.

[0030] Each device shown in Figure 3 is connected to a network. Specifically, the server device 10, the collaboration server 20, the service server 30, and the terminal 40 are connected to the network by wired or wireless communication means.

[0031] 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 collaboration server 20 of the information sharing business 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, an information sharing business operator may include multiple collaboration servers 20, and each service provider may include multiple service servers 30.

[0032] [Outline of Operation] Next, the outline of the operation of the information processing system according to the first embodiment will be described.

[0033] In the first embodiment, we will describe a case where the service provider's business is the recruitment and dispatch of workers to work in factories, etc. Workers working in factories, etc. are required to have completed training stipulated by laws and regulations, and to possess prescribed skills and qualifications. The service provider (recruitment company) provides the factory, etc. with information on workers who meet the requirements (work qualifications) for working in the factory, etc.

[0034] <Preparing the Digital Wallet> Users (workers) will use a digital wallet. A digital wallet is an electronic information storage service that guarantees information security, including data integrity, reliability, and availability.

[0035] The user utilizes an online wallet service (web wallet). The user operates terminal 40 to access the wallet provider's server (not shown in Figure 3, etc.). The user creates an account on the wallet provider's server.

[0036] Users who have created an account on the wallet provider's server install a wallet application on terminal 40. The wallet application controls and manages the user's digital wallet.

[0037] By opening a digital wallet, users can store various digital content such as identification documents like My Number cards, completed training certificates, skill certificates, and qualification certificates in that digital wallet. The wallet application accesses the online digital wallet to store and retrieve digital content.

[0038] <Acquisition of Digital Content> Users who have opened a digital wallet will acquire the digital content to be stored in that digital wallet.

[0039] 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".

[0040] 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".

[0041] 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.

[0042] <Obtaining Credentials> First, we will explain how to obtain credentials.

[0043] Before issuing a credential certificate, the user's terminal 40 (wallet application) generates a pair of public and private keys. The terminal 40 also generates a decentralized identifier (DID). For example, the terminal 40 generates the wallet address of the digital wallet as the user's DID.

[0044] The terminal 40 registers the generated DID (user DID; holder DID) and the public key in the blockchain (step S01 in FIG. 5).

[0045] Furthermore, while presenting the user DID, the user's terminal 40 requests the issuance of a credential certificate from the credential certificate issuer (server device 10). Specifically, the terminal 40 transmits a "certificate issuance request" including information about the certificate for which issuance is requested (e.g., the type of the credential certificate), information specifying the object to be proved by the credential certificate, the user DID, etc. to the server device 10 (step S02).

[0046] The server device 10 generates, stores in advance, and stores the issuer's DID (issuer DID), private key, and public key.

[0047] Upon receiving the certificate issuance request, the certificate issuer determines whether it is possible to issue the credential certificate desired by the user.

[0048] If it is possible to issue the credential certificate desired by the user, the server device 10 generates a credential certificate including the issuer DID and the user DID.

[0049] Specifically, the server device 10 generates a credential certificate including metadata such as the type of the credential certificate, the name of the issuing organization, the issuance date and time, the expiration period, etc., the claim content (qualification information, claim), and proofs such as the issuer's public key information and digital signature. The specific information to be proved by the issuer is described in the claim content.

[0050] 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).

[0051] Specifically, the server device 10 stores the generated credential certificate in online storage. The server device 10 generates a certificate retrieval URL from the URL (Uniform Resource Locator) where the credential certificate is stored. The server device 10 sends an acknowledgment (response to the certificate issuance request) containing the generated certificate retrieval URL to the terminal 40.

[0052] Furthermore, the server device 10 registers the issuer DID and the generated public key, etc., on the blockchain (step S04). Alternatively, the server device 10 may register the status of the issued credential certificate (valid, invalid), the credential ID that uniquely identifies the credential certificate, the issuer DID, etc., in the VDR (Virtual Data Room).

[0053] Terminal 40 accesses the URL for obtaining the certificate included in the acknowledgment and obtains the credential certificate. Terminal 40 stores the obtained credential certificate in its digital wallet.

[0054] For example, a user may request the issuance of a training completion certificate (VCs) from the organization that hosts the training. Alternatively, a user may request the issuance of a skills certificate (VCs) or qualification certificate (VCs) from a certification body for skills or qualifications. Terminal 40 stores the acquired credential certificates in its digital wallet.

[0055] <Information Provision Service> Users who wish to work in factories, etc., register in advance with the service provider (recruitment agency). Users create an account with the service provider and register their name, gender, date of birth, address, telephone number, email address, etc. to that account. The service server 30 stores the user's name, gender, email address, etc.

[0056] Service providers receive requests for personnel placement from factories and other businesses. For example, factories and other businesses notify service providers of the employment period, work location, work content, number of people to be hired, and the requirements for workers (work qualifications; for example, information on training to be completed, skills possessed, qualifications possessed, etc.).

[0057] Upon receiving the notification, the service provider's employees input the information obtained from the factory (work period, work location, work content, number of people to be recruited, work qualifications, etc.) into the service server 30. The service server 30 assigns a work ID to the request from the factory. The service server 30 uses the work ID to manage the requests (worker recruitment) from the factory.

[0058] Subsequently, the service server 30 notifies pre-registered users (potential workers) of the factory's worker recruitment. Specifically, the service server 30 sends a "worker recruitment notification" to the terminal 40 held by the pre-registered user (step S11 in Figure 6). The service server 30 sends the "worker recruitment notification," which includes the work ID and all or part of the information obtained from the factory (for example, work period, work location, number of people to be recruited, work content, work qualifications, etc.), to the pre-registered user's email address.

[0059] Furthermore, the service server 30 also sends the above-mentioned worker recruitment notice to the information sharing service provider's sharing server 20.

[0060] Upon receiving a worker recruitment notice, the linked server 20 generates a worker management database for managing workers who apply for positions at the factory. The linked server 20 manages information about workers performing work at the factory (hereinafter referred to as "worker information") using the worker management database. Details of the worker management database will be described later.

[0061] Upon receiving a worker recruitment notice, terminal 40 displays the information contained in the notice (e.g., work period, work location, work content, work qualifications, etc.) and obtains whether or not the user intends to apply for the worker position.

[0062] When a user wishes to apply for a job opening, terminal 40 reads multiple credential certificates from its digital wallet.

[0063] Specifically, terminal 40 reads identity verification documents (VCs) from the digital wallet. More specifically, terminal 40 reads identity verification documents (VCs) from the digital wallet that include biometric information (e.g., facial image) in addition to information such as name, gender, date of birth, and address. For example, terminal 40 reads My Number Card VCs from the digital wallet.

[0064] Furthermore, terminal 40 retrieves credential certificates from its digital wallet that correspond to each item of work qualifications included in the worker recruitment notice (e.g., training name, skill name, qualification name). For example, terminal 40 retrieves completed training certificates (VCs), held skill certificates (VCs), and held qualification certificates (VCs) from its digital wallet.

[0065] Terminal 40 signs each of several credential certificates (e.g., identity certificate VCs, completed training certificate VCs, skills certificate VCs, qualification certificate VCs) using a private key corresponding to the user DID (e.g., wallet address).

[0066] When a user signs an identity document (VCs), the terminal 40 requests the corresponding certificate issuer to verify each credential. For example, the terminal 40 requests the issuing municipality of the My Number Card to verify the My Number Card VCs. Alternatively, the terminal 40 requests the organization that hosted the training to verify the completed training certificate VCs.

[0067] At that time, terminal 40 sends a "verification request" including the user DID, the work ID included in the worker recruitment notice, and the credential certificate to the certificate issuer's server device 10 (step S12). For example, terminal 40 sends a verification request including the user DID, the work ID, and completed training certificates VCs to the training institution's server device 10. Similarly, terminal 40 sends a verification request including the user DID, the work ID, and held skill certificates VCs to the skills certification organization's server device 10.

[0068] Furthermore, terminal 40 acquires the user's facial image. Terminal 40 acquires a selfie facial image through a so-called self-portrait. Terminal 40 sends a "biometric information notification" including the user DID, selfie facial image, work ID, and identity certificate VCs to the linked server 20 (step S13).

[0069] Each server device 10 that receives a verification request verifies the credential certificate included in the request. Subsequently, the server device 10 sends a "verification result notification" to the linked server 20, which includes the user DID, work ID, information about the credential certificate to be verified, and the verification result (verification successful, verification failed) included in the verification request (step S14). Examples of information about the credential certificate to be verified include the names of the skills or qualifications certified by the credential certificate.

[0070] For example, when the training institution's server device 10 verifies the acquired completed training certificates VCs, it sends a verification result notification to the linked server 20 that includes the user DID, work ID, the name of the completed training certified by the completed training certificates VCs, and the verification result (verification successful, verification failed).

[0071] The collaborative server 20 receives verification result notifications from the server devices 10 of each certificate issuer. The collaborative server 20 also receives biometric information notifications from the user's terminal 40.

[0072] Upon receiving these notifications, the coordinating server 20 uses the work ID included in each notification to identify the worker recruitment targeted by each notification received from the server device 10 or terminal 40. Furthermore, the coordinating server 20 uses the user DID included in each notification to match the selfie face image, identity document VCs, and pre-verification results included in each notification.

[0073] Once the data matching is complete, the linked server 20 checks the verification results from the certificate verifier (server device 10). If the linked server 20 finds that "verification failed" among the multiple verification results, it discards the information of the corresponding user. In other words, the linked server 20 determines that users who have failed to verify their identity cards (VCs) or completed training certificates (VCs) do not meet the requirements (work qualifications) set by the factory, etc., and discards the information of such users.

[0074] If the verification result received from each certificate issuer is "verification successful," the linked server 20 performs identity verification using biometric information (selfie face image) obtained from the user's terminal 40 and biometric information (face image) obtained from the identity certificate VCs.

[0075] If identity verification is successful, the linked server 20 stores the worker information in a worker management database prepared for each work ID. For example, the linked server 20 stores the fact that pre-verification was successful for each item of personal information (name, gender, etc.), biometric information (e.g., selfie facial image), and work qualifications obtained from the identity certificate VCs.

[0076] Furthermore, once the number of recruits obtained from the recruitment agency has been registered in the worker management database, the linked server 20 may discard information provided by other users regarding the same recruitment.

[0077] Furthermore, when the number of users registered in the worker management database reaches the number of people needed, the linked server 20 provides the worker information registered in the worker management database to the service provider (recruitment agency). Specifically, the linked server 20 sends a "worker roster notification" to the service server 30, which includes worker information (for example, name, gender, date of birth, address, biometric information, names of completed training, names of skills held, names of qualifications held, etc.) along with the work ID (step S15).

[0078] The service provider (recruitment agency) compiles the acquired worker information into a list or similar format in a prescribed format and submits it to the client requesting the recruitment services (a business such as a factory).

[0079] The factory will utilize the acquired list. For example, the factory will build an access control system for workers using the provided worker information. For example, the access control system will perform facial recognition when a worker attempts to enter the work area. The access control system will perform a comparison between the facial image of the worker attempting to enter the work area and the facial image acquired from the service provider. If the facial matching is successful, the access control system will determine that the worker has been successfully authenticated. The access control system will then allow the worker to enter the work area.

[0080] In this way, terminal 40 requests each server device 10 to verify the certificates among the multiple certificates issued to the user that correspond to the items requested by the third party (e.g., a recruitment agency, a factory). Each of the multiple server devices 10 notifies the linked server 20 of the verification results of the certificates it is verifying. If the verification results for each of the multiple certificates are successful, the linked server 20 provides information about the user (worker information) to the third party.

[0081] Furthermore, terminal 40 acquires the user's biometric information and transmits the acquired biometric information along with an identification document issued to the user that guarantees the reliability of the biometric information, to the linked server 20. The linked server 20 performs identity verification using the biometric information acquired by terminal 40 and the biometric information obtained from the identification document, and if identity verification is successful, provides information about the user to a third party. More specifically, the linked server 20 provides the third party with at least one piece of personal information obtained from the identification document, such as name, gender, date of birth, and address, along with the user's biometric information.

[0082] Next, we will describe the details of each device included in the information processing system according to the first embodiment.

[0083] [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.

[0084] Figure 7 shows an example of the processing configuration (processing module) of a terminal 40 according to the embodiment disclosed herein. Referring to Figure 7, the terminal 40 comprises a communication control unit 201, an acquisition control unit 202, a utilization control unit 203, and a storage unit 204.

[0085] 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.

[0086] The wallet application is implemented by the acquisition control module 202 and the utilization control module 203. A detailed explanation of the wallet application installation is omitted, as its installation is obvious to those skilled in the art.

[0087] The acquisition control unit 202 is a means for controlling the acquisition of credential certificates. The acquisition control unit 202 requests the certificate issuer to issue the certificate selected by the user and stores the certificate obtained from the certificate issuer in the digital wallet.

[0088] Figure 8 is a flowchart illustrating an example of the operation of the acquisition control unit 202. The operation of the acquisition control unit 202 according to the embodiment disclosed herein will be explained with reference to Figure 8.

[0089] When a user who has opened a digital wallet launches the wallet application and performs a predetermined action (for example, pressing the certificate issuance button), the acquisition control unit 202 performs control related to the acquisition of the credential certificate desired by the user.

[0090] First, the acquisition control unit 202 generates a public key and private key pair, and a distributed identifier, the user DID. For example, the acquisition control unit 202 generates a wallet address to be used in a digital wallet as 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 S101).

[0091] Next, the acquisition control unit 202 uses a GUI or the like to acquire the items necessary for requesting the issuance of a credential certificate (acquisition of necessary items; step S102).

[0092] Specifically, the acquisition control unit 202 acquires 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 local government, the name of the training institution, the name of the certification body for qualifications, etc.), the type of certificate desired, etc. Furthermore, the acquisition control unit 202 acquires information that the certificate issuer uses to identify the person to be certified (for example, a combination of name and date of birth, etc.).

[0093] The acquisition control unit 202 notifies the certificate issuer of the acquired necessary items and user DID. Specifically, the acquisition control unit 202 notifies the certificate issuer of the type of credential certificate, information for identifying the subject of certification (information for identifying the recipient of the certificate), and user DID.

[0094] The acquisition control unit 202 transmits a "certificate issuance request" including the type of credential certificate, information identifying the subject of certification, user DID, etc., to the server device 10 of the certificate issuer selected by the user (step S103).

[0095] The acquisition control unit 202 receives a response (affirmative response, negative response) to the certificate issuance request from the server device 10 (step S104).

[0096] If a negative response is received indicating that the issuance of the certificate failed (step S105, No branch), the acquisition control unit 202 notifies the user that the credential certificate was not issued (notification of non-issuance; step S106).

[0097] If an affirmative response indicating that the certificate has been successfully issued is received (step S105, Yes branch), the acquisition control unit 202 accesses the certificate acquisition URL included in the affirmative response and acquires the credential certificate issued by the certificate issuer (step S107).

[0098] The acquisition control unit 202 stores the acquired credential certificate in the digital wallet (step S108).

[0099] For example, users acquire identity certificates (VCs), completed training certificates (VCs), skills certificates (VCs), qualification certificates (VCs), etc. The acquisition control unit 202 stores the acquired credential certificates in a digital wallet.

[0100] The usage control unit 203 is a means for controlling the use of digital content (credential certificates) stored in the digital wallet.

[0101] Figure 9 is a flowchart showing an example of the operation of the utilization control unit 203. The operation of the utilization control unit 203 according to the embodiment disclosed herein will be explained with reference to Figure 9.

[0102] For example, the user control unit 203 (wallet application) is activated when it receives an email (worker recruitment notification) from the service server 30.

[0103] Upon receiving a worker recruitment notice, the user control unit 203 presents the information contained in the notice (e.g., employment period, work location, work content, work qualifications, etc.) and obtains whether or not the user intends to apply for the worker position (intention confirmation; step S201). For example, the user control unit 203 obtains whether or not the user intends to apply for the worker position using a GUI (Graphical User Interface) as shown in Figure 10.

[0104] If the user does not intend to apply for the worker recruitment (step S202, No branch), the user control unit 203 terminates the process.

[0105] If the user intends to apply for the worker recruitment (step S202, Yes branch), the user control unit 203 reads multiple credential certificates from the digital wallet (obtains multiple VCs; step S203).

[0106] Specifically, the user control unit 203 reads identity verification documents (VCs) from the digital wallet that guarantee the reliability of biometric information (e.g., facial image) in addition to name and date of birth. For example, the user control unit 203 reads My Number Card VCs from the digital wallet.

[0107] Furthermore, the user control unit 203 reads the credential certificates corresponding to each item of work qualifications included in the worker recruitment notice from the digital wallet. For example, the user control unit 203 obtains completed training certificates VCs corresponding to required training, possessed skill certificates VCs corresponding to required skills, and possessed qualification certificates VCs corresponding to required qualifications from the digital wallet.

[0108] Furthermore, the user may select a credential certificate corresponding to each item of the work qualification, and the user control unit 203 may read the credential certificate selected by the user from the digital wallet.

[0109] Furthermore, if the digital wallet does not contain the identity certificates (VCs) that guarantee the reliability of the above biometric information, or the credential certificates corresponding to each item of the work qualification, the user control unit 203 may inform the user that they cannot apply for the worker recruitment and terminate the process.

[0110] The user control unit 203 requests the certificate issuer (certificate verifier) ​​to verify the acquired credential certificate. The user control unit 203 requests the verifier to verify the credential certificate.

[0111] Specifically, the user control unit 203 signs each of the multiple credential certificates using a private key corresponding to the user DID (e.g., wallet address). Subsequently, the user control unit 203 sends a verification request to the server device 10 corresponding to each credential certificate (step S204).

[0112] More specifically, the user control unit 203 transmits a "verification request" that includes the user DID, work ID, and credential certificate. For example, the user control unit 203 transmits a verification request that includes completed training certificates (VCs) to the server device 10 of the training institution that hosted the completed training.

[0113] Before or after the verification request is sent, the user control unit 203 acquires the user's biometric information (step S205). For example, the user control unit 203 acquires a selfie face image through a so-called selfie.

[0114] The user control unit 203 sends a "biometric information notification" including the acquired selfie face image, user DID, work ID, and identity card VCs to the linked server 20 (step S206).

[0115] The memory unit 204 is a means for storing information necessary for the operation of the terminal 40.

[0116] [Server Device] Figure 11 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 11, the server device 10 comprises a communication control unit 301, a certificate issuance unit 302, a certificate verification unit 303, and a storage unit 304.

[0117] 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.

[0118] 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.

[0119] Upon receiving a certificate issuance request, the certificate issuance unit 302 searches a database (not shown in Figure 11, etc.) that stores user information, using information to identify the subject of the certificate issuance request (for example, a combination of name and date of birth) as a key.

[0120] 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.

[0121] 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.

[0122] For example, if a user requests the issuance of a training completion certificate (VCs), the certificate issuing unit 302 determines whether or not the user has completed the corresponding training.

[0123] 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.

[0124] 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).

[0125] If it is possible to issue a credential certificate to the user, the certificate issuing unit 302 generates a credential certificate to be issued to the user. The certificate issuing unit 302 generates a credential certificate that includes the issuer DID and the user DID (the DID of the recipient of the certificate; the user DID included in the certificate issuance request).

[0126] Specifically, the certificate issuing unit 302 generates a credential certificate that includes 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.

[0127] The certificate issuing unit 302 stores the generated credential certificate in online storage (cloud storage), etc. The certificate issuing unit 302 generates a certificate retrieval URL from the URL where the credential certificate is stored. The certificate issuing unit 302 sends an acknowledgment containing the generated certificate retrieval URL to the terminal 40. Furthermore, the certificate issuing unit 302 registers the previously generated issuer DID and public key, etc., on the blockchain.

[0128] The certificate verification unit 303 is a means for verifying the credential certificate received from the terminal 40. The certificate verification unit 303 verifies the credential certificate included in the verification request received from the terminal 40.

[0129] The certificate verification unit 303 verifies at least one of the three items related to the validity of the credential certificate.

[0130] The first item is the verification of the electronic signature attached to the credential certificate.

[0131] In this case, the certificate verification unit 303 obtains the issuer DID and user DID listed on the credential certificate. The certificate verification unit 303 obtains the public key corresponding to the obtained issuer DID from the blockchain. Similarly, the certificate verification unit 303 obtains the public key corresponding to the obtained user DID from the blockchain.

[0132] The Certificate Verification Unit 303 verifies the signature of the holder (the user who wishes to receive the service; the job seeker) and the signature of the issuer attached to the credential certificate. By verifying these signatures, the Certificate Verification Unit 303 confirms that the credential certificate obtained from the user (the holder of the credential certificate) has not been tampered with and that it is a certificate issued by a trustworthy issuer.

[0133] The Certificate Verification Unit 303 determines that the credential certificate has been verified if it successfully verifies the signatures of both the holder and the issuer of the credential certificate. The Certificate Verification Unit 303 determines that the credential certificate has been verified if it fails to verify the signature of at least one of the holder or issuer of the credential certificate.

[0134] The second item is to verify that the credential certificate has not been set to invalid.

[0135] In this case, the certificate verification unit 303 accesses the blockchain or VDR using the credential ID and issuer DID to confirm that the received credential certificate is not listed in the certificate issuer's revocation list. The certificate verification unit 303 also confirms that the credential certificate obtained from the user has not been invalidated by the issuer before its expiration date.

[0136] The certificate verification unit 303 determines that the verification of the credential certificate was successful if the credential certificate is not listed in the revocation list. The certificate verification unit 303 determines that the verification of the credential certificate failed if the credential certificate is listed in the revocation list.

[0137] The third item is verification that the validity period (expiration date) of the credential certificate has not expired.

[0138] The certificate verification unit 303 checks the validity period set on the credential certificate. If the validity period set on the credential certificate has not expired, the certificate verification unit 303 determines that the verification of the acquired credential certificate was successful. If the validity period set on the credential certificate has expired, the certificate verification unit 303 determines that the verification of the acquired credential certificate failed.

[0139] The certificate verification unit 303 determines that it has successfully verified the credential certificate obtained from the user if it determines that "verification was successful" in one of the predetermined items from the first to third items.

[0140] The certificate verification unit 303 determines that it has failed to verify the credential certificate obtained from the user if it determines that "verification failed" in one of the predetermined items from the first to third items.

[0141] Subsequently, the certificate verification unit 303 sends a "verification result notification" to the linked server 20, which includes the user DID, work ID, information about the credential certificate to be verified, and the pre-verification result (verification successful, verification failed) included in the verification request.

[0142] The memory unit 304 is a means for storing information necessary for the operation of the server device 10.

[0143] [Service Server] Figure 12 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 12, the service server 30 comprises a communication control unit 401, a service provision control unit 402, and a storage unit 403.

[0144] 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.

[0145] The service provision control unit 402 is a means for performing control related to the services provided by the service provider.

[0146] The service provision control unit 402 includes a function for generating user accounts.

[0147] The service provision control unit 402 obtains information such as name, gender, date of birth, address, telephone number, and email address from users who access a designated website (for example, a user registration site). The service provision control unit 402 stores the name, contact information, etc., in a designated database.

[0148] The service provision control unit 402 obtains information about workers required by the factory from the service provider's employees, etc. For example, the service provision control unit 402 obtains information related to worker recruitment (e.g., employment period, work location, number of people to be recruited, work content, work qualifications, etc.).

[0149] When the service provision control unit 402 obtains information regarding the recruitment of workers, it assigns a work ID to the recruitment. The service provision control unit 402 stores the work ID, factory information (for example, the name of the factory that requested the recruitment of workers), and the information regarding the recruitment of workers obtained from the factory, etc., in association with each other.

[0150] The service provision control unit 402 notifies pre-registered users of the recruitment of workers. Specifically, the service provision control unit 402 sends a "worker recruitment notification" to email addresses stored in the database, which includes the work ID and all or part of the information obtained from the factory (for example, work period, work location, number of people to be recruited, work content, work qualifications, etc.).

[0151] The service provision control unit 402 receives a worker roster notification from the cooperating server 20. Based on the work ID included in the worker roster notification, the service provision control unit 402 identifies the business operator, such as a factory, that requested the recruitment of workers.

[0152] The service provision control unit 402 outputs information to be submitted to the identified factory. Specifically, the service provision control unit 402 outputs worker information included in the received worker roster notification in a predetermined format, such as a list. For example, the service provision control unit 402 outputs a list having the contents shown in Figure 13.

[0153] In this case, the service provision control unit 402 may output the name, gender, date of birth, address, biometric information, etc., of each worker that meets the requirements of the factory, etc., in a spreadsheet file format. Alternatively, the service provision control unit 402 may output the information of each worker in a machine-processable format such as JSON (JavaScript Object Notation). In this way, the service provision control unit 402 may present the worker information to the factory (ordering party, etc.) in a predetermined format.

[0154] The service provision control unit 402 stores a file containing worker information on a USB (Universal Serial Bus) memory or the like. Alternatively, the service provision control unit 402 may print the file or send it to the email address of an employee of the service provider. Alternatively, the service provision control unit 402 may send the file to the email address of a person in charge at the factory or other facility.

[0155] Furthermore, the service provision control unit 402 may notify each user to whom a worker recruitment notice has been sent whether or not they have been hired for a position at a factory or other facility. Specifically, the service provision control unit 402 identifies workers included in the worker roster notice based on their name, etc. The service provision control unit 402 sends a message to the email address of the identified worker informing them that they have been hired as a worker. In addition, the service provision control unit 402 may send a message to workers to whom a worker recruitment notice has been sent but who are not included in the worker roster notice, informing them that they have not been hired as a worker.

[0156] The memory unit 403 is a means for storing information necessary for the operation of the service server 30.

[0157] [Cooperation Server] Figure 14 is a diagram showing an example of the processing configuration (processing module) of the cooperation server 20 according to the embodiment disclosed herein. Referring to Figure 14, the cooperation server 20 comprises a communication control unit 501, an information provision control unit 502, and a storage unit 503.

[0158] 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.

[0159] The information provision control unit 502 is a means for controlling the provision of user information.

[0160] The information provision control unit 502 processes worker recruitment notifications received from the service server 30, biometric information notifications received from the terminal 40, and verification result notifications received from the server device 10.

[0161] Upon receiving a worker recruitment notice, the information provision control unit 502 generates a worker management database for managing users who have applied for positions at the factory (see Figure 15). The information provision control unit 502 generates a worker management database for each work ID. The information provision control unit 502 manages verification results for each item of the worker, such as name, gender, date of birth, address, biometric information, and work qualifications, using the worker management database. Note that the worker management database shown in Figure 15 is an example and is not intended to limit the items to be stored.

[0162] The information provision control unit 502 receives verification result notifications from the server devices 10 of each certificate issuer. The information provision control unit 502 also receives biometric information notifications from the user's terminal 40.

[0163] Figure 16 is a flowchart showing an example of the operation of the information provision control unit 502 according to the embodiment disclosed herein. The operation of the information provision control unit 502 will be explained with reference to Figure 16.

[0164] The information provision control unit 502 periodically or at predetermined intervals performs matching of received verification result notifications and biometric information notifications (perform matching; step S301). Specifically, the information provision control unit 502 uses the user DID included in each notification to match biometric information (selfie face image), identity card VCs, and at least one verification result.

[0165] Furthermore, the information provision control unit 502 determines that the data matching is incomplete if there is any information among the biometric information (selfie facial image), identity card VCs, and verification results that has not been notified. For example, the information provision control unit 502 determines that the data matching is incomplete if the verification results corresponding to the items corresponding to work qualifications have not been notified. The information provision control unit 502 does not include information for which data matching is incomplete in subsequent processing.

[0166] Once the data matching is complete, the information provision control unit 502 verifies each of the multiple verification results (verification result verification; step S302).

[0167] If "verification failed" is among the multiple verification results (step S303, No branch), the information provision control unit 502 discards the corresponding user information (step S304).

[0168] If the verification result received from each certificate issuer is "verification successful" (step S303, Yes branch), the information provision control unit 502 performs identity verification using the selfie face image acquired from the terminal 40 and the face image obtained from the identity document VCs (step S305).

[0169] Specifically, the information provision control unit 502 performs identity verification using a selfie face image and a face image included in the identity document VCs. The information provision control unit 502 determines whether the two face images are substantially the same and performs identity verification.

[0170] The information provision control unit 502 generates feature quantities from both the selfie face image and the face image included in the identity document VCs.

[0171] Regarding the feature generation process, existing technologies can be used, so a detailed explanation will be omitted. For example, the information provision control unit 502 extracts the eyes, nose, mouth, etc., from the face image as feature points. Subsequently, the information provision control unit 502 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).

[0172] Next, the information provision control unit 502 performs a matching process (one-to-one matching) using the two generated feature quantities. Specifically, the information provision control unit 502 calculates the similarity between corresponding face images using the two feature quantities. Based on the result of thresholding the calculated similarity, the information provision control unit 502 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.

[0173] If the similarity is greater than a predetermined value (if the distance is shorter than a predetermined value), the information provision control unit 502 determines that identity verification was successful. If the similarity is less than or equal to the predetermined value, the information provision control unit 502 determines that identity verification failed.

[0174] If identity verification fails (step S306, No branch), the information provision control unit 502 discards the corresponding user's information (step S304).

[0175] If identity verification is successful (step S306, Yes branch), the information provision control unit 502 stores the worker information in the worker management database prepared for each work ID (step S307). Specifically, the information provision control unit 502 stores the fact of successful verification for each item of personal information (e.g., name, gender, date of birth, address), biometric information (e.g., selfie facial image), and work qualifications obtained from the identity certificate VCs.

[0176] Here, when the number of users registered in the worker management database reaches the number of people needed to be hired, the information provision control unit 502 provides the worker information registered in the worker management database to the service provider (recruitment agency).

[0177] Specifically, the information provision control unit 502 sends a "worker roster notification" to the service server 30 that includes the work ID and at least one piece of worker information (for example, name, gender, date of birth, address, biometric information, name of completed training, name of skills held, name of qualifications held, etc.).

[0178] The memory unit 503 is a means for storing information necessary for the operation of the cooperative server 20.

[0179] [System Operation] Next, the operation of the information processing system according to the first embodiment will be described.

[0180] 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 issuance of a credential certificate of the information processing system according to the first embodiment will be described.

[0181] Terminal 40 generates a public key, a private key, and a user DID, and registers the user DID and public key on the blockchain (step S21).

[0182] Terminal 40 sends a certificate issuance request including the above-mentioned user DID to the certificate issuer's server device 10 (step S22).

[0183] The server device 10 generates the user's (the recipient of the credential certificate) claim details (claims, qualification information) and generates a credential certificate containing the generated claim details (step S23). The server device 10 generates a credential certificate that includes the user DID and issuer DID and is electronically signed.

[0184] The server device 10 provides the generated credential certificate to the terminal 40 by storing it in online storage or the like (step S24).

[0185] Terminal 40 obtains a credential certificate according to the URL for obtaining the certificate and stores the obtained credential certificate in the digital wallet (step S25).

[0186] Figure 18 is a sequence diagram showing an example of the operation of an information processing system according to the embodiment disclosed herein. Referring to Figure 18, the operation of the information provision operation of the information processing system according to the first embodiment will be described.

[0187] Upon receiving a worker recruitment notice from the service server 30, terminal 40 sends a request for verification of the credential certificate to the certificate issuer's server device 10 (step S31).

[0188] Furthermore, terminal 40 transmits a biometric information notification, including the user's biometric information, to the cooperating server 20 (step S32).

[0189] Each server device 10 verifies the acquired credential certificate and sends a verification result notification, including the verification result, to the linked server 20 (step S33).

[0190] The collaborative server 20 consolidates the information acquired from each server device 10 and terminal 40, verifies the identity of the user, and stores the information (worker information) of users whose identity has been successfully verified (step S34).

[0191] The collaboration server 20 transmits information (worker information) of multiple users to the service server 30. Specifically, the collaboration server 20 transmits a worker roster notification to the service server 30 (step S35).

[0192] Next, a modified example of the first embodiment will be described.

[0193] <Variation 1> The cooperating server 20 may delete the information stored in the worker management database after sending it to the service provider (service server 30). Alternatively, the cooperating server 20 may continue to store the information stored in the database until the employment period (work period) for the worker recruitment has elapsed.

[0194] <Modification 2> The coordinating server 20 may instruct the service server 30 to delete the worker information provided by the coordinating server 20 after the employment period has elapsed. That is, the coordinating server 20 may instruct the service server 30 to delete the personal information when the validity period of the worker information (the validity period of the personal information that the user agreed to provide when working at the factory, etc.) has expired. The service server 30 may further instruct the factory, etc. to delete the worker information.

[0195] <Modification 3> The cooperating server 20 may store a history of worker information sent to the service server 30. The cooperating server 20 may also store a history that allows for retrospective verification of the recipients of the worker information.

[0196] <Variation 4> When the certificate issuer's server device 10 verifies a credential certificate, even if the certificate's expiration date has not expired, if the credential certificate's expiration date falls during the employment period, the server device 10 may determine that the verification of the credential certificate has failed. In other words, even if the credential certificate is valid at the time of verification, if the credential certificate becomes invalid during the employment period, the server device 10 may determine that the verification of the credential certificate has failed.

[0197] <Modification 5> In the above embodiment, the case in which the certificate issuer's server device 10 sends a verification result notification to the cooperating server 20 was described. However, the server device 10 may also send a verification result notification to the terminal 40. The terminal 40 that receives the verification result notification may also send the said verification result notification to the cooperating server 20.

[0198] <Modification 6> The user's terminal 40 may perform identity verification of the user when opening a digital wallet. For example, the terminal 40 may perform identity verification using a My Number Card or the like.

[0199] As described above, in the information processing system according to the first embodiment, each server device 10, which is a verification device, verifies each of the multiple credential certificates held by the user and notifies the linked server 20 of the verification results. The linked server 20 links the verification results received from each server device 10 and generates worker information required by a third party such as a factory. In other words, factories and the like do not need to verify that workers have the necessary qualifications, skills, etc. Factories and the like only need to accept the worker information provided by the linked server 20 without having to verify the credential certificates that prove qualifications, skills, etc. As a result, the burden on businesses and the like that need information on workers who have the required qualifications, etc. is reduced.

[0200] Thus, the collaborative server 20 functions as a hub that aggregates the verification results of the credential certificates provided by each verifier and provides the necessary information to external parties (service providers or businesses such as factories). In the information processing system disclosed in this application, multiple credential certificates are verified in parallel, the collaborative server 20 aggregates the verification results, and provides the information required by third parties to external parties. Furthermore, businesses such as factories can obtain only the information necessary for their own operations through the service provider. In addition, since the collaborative server 20 does not hold the users' credential certificates, there is no risk of information leakage from the collaborative server 20.

[0201] Furthermore, the linked server 20 can treat identity verification documents such as My Number Cards as facial verification documents, and obtain user personal information guaranteed by public institutions. As a result, the linked server 20 can provide highly reliable information free from fraud, such as impersonation.

[0202] 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 collaborative server 20.

[0203] The collaborative 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 collaborative 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.

[0204] However, the configuration shown in Figure 19 is not intended to limit the hardware configuration of the collaboration server 20. The collaboration 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 collaboration server 20 is not intended to be limited to the example in Figure 19; for example, multiple processors 311 may be included in the collaboration server 20.

[0205] 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).

[0206] 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.

[0207] 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.

[0208] 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).

[0209] The functions of the collaborative server 20 are realized by various processing modules. These processing modules are realized, for example, by the processor 311 executing a program stored in the 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.

[0210] Furthermore, the server device 10, service server 30, and terminal 40, etc., can also be configured using information processing devices, similar to the collaboration server 20. Since their basic hardware configurations are no different from those of the collaboration server 20, a detailed explanation will be omitted.

[0211] The information processing device, the interoperation server 20, is equipped with a computer, and its functions are realized by having the computer execute a program. Furthermore, the interoperation server 20 executes a control method for the interoperation server 20 using this program. Similarly, the terminal 40 is equipped with a computer, and its functions are realized by having the computer execute a program. Furthermore, the terminal 40 executes a control method for the terminal 40 using this program.

[0212] [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.

[0213] In the above embodiment, a facial image was used as an example of biometric information to explain the operation of the information processing system. Here, biometric information includes, for example, data (feature quantities) calculated from individual physical characteristics such as face, fingerprints, voiceprints, veins, retina, and iris patterns. Alternatively, biometric information may be image data such as a facial image or fingerprint image. Biometric information only needs to include information about the user's physical characteristics.

[0214] In the above embodiment, the operation of the information processing system was explained using the recruitment of workers for a factory or the like as an example. However, it goes without saying that the information processing system disclosed in this application can be applied to uses other than worker recruitment.

[0215] In the above embodiment, the operation of the information processing system was explained using the example of a service provider being a business engaged in personnel placement and temporary staffing. However, the service provider may also be a business such as a factory. In this case, the terminal 40 may use a GUI as shown in Figure 20 instead of the GUI shown in Figure 10 to obtain whether or not the user consents to the provision of information.

[0216] The above embodiment described a case in which the certificate issuer verifies the credential certificate. However, the certificate issuer and the certificate verifier may be different entities. For example, a business operator or other entity commissioned by the certificate issuer may act as the certificate verifier.

[0217] In the above embodiment, the case where the digital wallet used by the user is configured online was described. However, the digital wallet may also be configured inside the terminal 40.

[0218] 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).

[0219] Some functions of the linked server 20, etc., may be implemented in other devices or equipment. More specifically, it is sufficient if the "information provision control unit (information provision control means)" etc. described above is implemented in any of the devices included in the system.

[0220] 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.

[0221] 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.

[0222] 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.

[0223] As described above, the industrial applicability of the present invention is clear, and it is particularly suitable for information processing systems that utilize credential certificates and the like stored in digital wallets.

[0224] Some or all of the above embodiments may also be described as follows, but are not limited to the following:

[0225] [Note 1] A system comprising: a terminal held by a user to whom multiple certificates have been issued; multiple verification devices, each of which verifies the corresponding certificate; and an information sharing device, wherein each of the multiple verification devices notifies the information sharing device of the verification result of the certificate it is verifying; and the information sharing device provides information about the user to a third party if the verification result of each of the multiple certificates is successful.

[0226] [Note 2] The system as described in Note 1, wherein the terminal requests the verification device to verify the certificate corresponding to the item requested by the third party from among the plurality of certificates.

[0227] [Note 3] The system described in Note 2, wherein the terminal acquires the user's biometric information and transmits the acquired biometric information and an identification card issued to the user that guarantees the reliability of the biometric information to the information sharing device.

[0228] [Note 4] The information sharing device is the system described in Note 3, which performs identity verification using biometric information acquired by the terminal and biometric information obtained from the identification document, and provides information about the user to the third party if the identity verification is successful.

[0229] [Note 5] The information sharing device is the system described in Note 4, which provides the third party with at least one piece of personal information obtained from the identification document, name, gender, date of birth, and address, as well as the user's biometric information.

[0230] [Appendix 6] The verification device is a system described in any one of the appendices 1 to 5, which makes the certificate issued by the device itself the subject of verification.

[0231] [Note 7] The system described in any one of Notes 1 to 5, wherein each of the aforementioned multiple certificates is a credential certificate.

[0232] [Note 8] A server device comprising: an acquisition means for acquiring the verification results of certificates that each verification device is verifying from each of a plurality of verification devices; and a provision means for providing information to a third party about the users to whom the plurality of certificates were issued if the verification results of each of the plurality of certificates are successful.

[0233] [Note 9] A server control method for which a server device obtains verification results for certificates that each verification device is verifying from each of a plurality of verification devices, and if the verification results for each of the plurality of certificates are successful, provides information about the users for whom the plurality of certificates were issued to a third party.

[0234] [Note 10] A computer-readable storage medium that stores a program for causing a computer installed in a server device to execute the following: a process for obtaining the verification results of certificates that each verification device is verifying from each of the multiple verification devices; and a process for providing information to a third party about the user for whom the multiple certificates were issued, if the verification results of each of the multiple certificates are successful.

[0235] 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.

[0236] 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.

[0237] 10 Server device 20 Interoperability server 30 Service server 40 Terminal 101 Terminal 102 Verification device 103 Information interoperability device 201 Communication control unit 202 Acquisition control unit 203 Utilization control unit 204 Storage unit 301 Communication control unit 302 Certificate issuance unit 303 Certificate verification unit 304 Storage unit 311 Processor 312 Memory 313 Input / output interface 314 Communication interface 401 Communication control unit 402 Service provision control unit 403 Storage unit 501 Communication control unit 502 Information provision control unit 503 Storage unit

Claims

1. A system comprising: a terminal owned by a user to whom multiple certificates have been issued; multiple verification devices, each of which verifies the corresponding certificate; and an information sharing device, wherein each of the multiple verification devices notifies the information sharing device of the verification result of the certificate it is verifying; and the information sharing device provides information about the user to a third party if the verification result of each of the multiple certificates is successful.

2. The system according to claim 1, wherein the terminal requests the verification device to verify the certificate corresponding to the item requested by the third party from among the plurality of certificates.

3. The system according to claim 2, wherein the terminal acquires the user's biometric information and transmits the acquired biometric information and an identification document issued to the user that guarantees the reliability of the biometric information to the information sharing device.

4. The system according to claim 3, wherein the information sharing device performs identity verification using biometric information acquired by the terminal and biometric information obtained from the identification document, and if the identity verification is successful, provides the information relating to the user to the third party.

5. The system according to claim 4, wherein the information sharing device provides the third party with at least one piece of personal information obtained from the identification document, name, gender, date of birth, and address, and the user's biometric information.

6. The system according to any one of claims 1 to 5, wherein the verification device is the subject of verification of the certificate issued by the device itself.

7. The system according to any one of claims 1 to 5, wherein each of the plurality of certificates is a credential certificate.

8. A server device comprising: an acquisition means for acquiring the verification results of certificates that each verification device is subject to verification from each of a plurality of verification devices; and a provision means for providing information to a third party about the user to whom the plurality of certificates were issued if the verification results of each of the plurality of certificates are successful.

9. A server control method for which a server device obtains verification results for certificates that each verification device is verifying from each of several verification devices, and if the verification results for each of the several certificates are successful, provides information about the users for whom the several certificates were issued to a third party.

10. A computer-readable storage medium that stores a program for causing a computer installed in a server device to execute the following: a process for obtaining the verification results of certificates that each verification device is verifying from each of several verification devices; and a process for providing information to a third party about the user to whom the multiple certificates were issued, if the verification results of each of the multiple certificates are successful.