Information processing device, system, control method for information processing device, and storage medium
The system addresses the challenge of proving product ownership by using electronic identification and biometric verification to issue certificates, ensuring users can validate ownership and access services like repairs, with resaleable products managed through NFTs.
Patent Information
- Application Number
- PCT/JP2025/017166
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-12
- Publication Date
- 2026-11-19
AI Technical Summary
Existing systems fail to efficiently prove product ownership, especially when paper-based warranty certificates are lost, preventing genuine product owners from receiving repair services.
An information processing device and system that acquires electronic identification documents and biometric information to issue a certificate of ownership, utilizing a terminal, collaboration server, and business server to verify identity and generate certificates, which can be in the form of credential certificates or NFTs.
Facilitates easy proof of product ownership, enabling users to receive repair services and allowing resaleable products to be transferred through NFTs, enhancing user convenience and service accessibility.
Smart Images

Figure JP2025017166_19112026_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 exists a technique for determining risks and the like that arise in transactions.
[0003] For example, Patent Document 1 describes that entities and subjects involved in transactions in a supply chain are each verified, and risk assessment is performed, so that specific risks that may arise in relation to the relevant transactions and countermeasures therefor are determined. The supply chain risk management apparatus of Patent Document 1 includes a verification unit and a risk management unit. The verification unit acquires subject credential information of a subject transacted in the supply chain, and entity credential information related to an entity that handles the subject. Further, the verification unit verifies the subject credential information and the entity credential information against a blockchain. The risk management unit generates risk management information indicating risk elements and risk countermeasures by the entity and the subject, based on entity transaction information indicating the past transaction history of the entity, the subject credential information, and the entity credential information.
[0004] Japanese Unexamined Patent Publication No. 2025-004321
[0005] When a home appliance or a game console breaks down, the product purchaser will request the manufacturer to repair it. At that time, manufacturers often require proof that the person requesting repair is the owner who purchased the genuine product. Normally, the above proof is provided by a paper-based warranty certificate or the like, but product purchasers often lose the paper-based warranty certificate. In this case, even a purchaser of a genuine product cannot receive the service (product repair).
[0006] Note that Patent Document 1 merely discloses a technique for determining risks and the like that arise in transactions. Therefore, even if the technique disclosed in Patent Document 1 is applied, the above problem cannot be solved.
[0007] The primary objective of this invention is to provide an information processing device, a system, a control method for the information processing device, and a storage medium that contribute to easily proving ownership of a product.
[0008] According to a first aspect of the present invention, an information processing device is provided, comprising: an acquisition means for acquiring an electronic identification document and biometric information of a user who has purchased a product; and an issuing means for issuing a certificate of ownership of the product, with the user who purchased the product as the recipient, upon successful verification of the acquired identification document and successful identity verification using the biometric information obtained from the acquired identification document.
[0009] According to a second aspect of the present invention, a system is provided that includes a business server operated by a business operator, a collaboration server operated by an information collaboration business operator, and a terminal held by a user who has purchased a product manufactured by the business operator, wherein the terminal transmits the user's electronic identification card and biometric information to the collaboration server, the collaboration server, upon successful verification of the received identification card and successful identity verification using the biometric information obtained from the identification card and the received biometric information, transmits information of the user who purchased the product to the business operator server, the business operator server, upon receiving information of the user who purchased the product, issues a certificate of ownership of the product with the user who purchased the product as the recipient, and the terminal stores the issued certificate of ownership.
[0010] A third aspect of the present invention provides a control method for an information processing device, which acquires the electronic identification card and biometric information of a user who purchased a product, successfully verifies the acquired identification card, and, if successful in verifying the user's identity using the biometric information obtained from the acquired identification card, issues a certificate of ownership of the product, with the user who purchased the product as the recipient.
[0011] A fourth aspect of the present invention is provided, a computer-readable storage medium that stores a program for causing a computer to execute the following: a process for acquiring an electronic identification document and biometric information of a user who purchased a product; and a process for issuing a certificate of ownership of the product, with the user who purchased the product as the recipient, if the acquired identification document is successfully verified and the biometric information obtained from the acquired identification document and the user's identity using the acquired biometric information are successful.
[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 easily proving ownership of a product. 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 showing an example of a certificate of ownership according to an embodiment of this disclosure. Figure 8 is a diagram showing an example of a certificate of ownership according to an embodiment of this disclosure. Figure 9 is a diagram showing an example of the processing configuration of a terminal according to an embodiment of this disclosure. Figure 10 is a flowchart showing an example of the operation of an acquisition control unit according to an embodiment of this disclosure. Figure 11 is a flowchart showing an example of the operation of a utilization 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 collaborative server according to an embodiment of this disclosure. Figure 14 is a flowchart showing an example of the operation of a purchaser information control unit according to an embodiment of this disclosure. Figure 15 is a diagram showing an example of the processing configuration of a business server according to an embodiment of this disclosure. Figure 16 is a diagram showing an example of a product management database 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 processing configuration of a product according to an embodiment of this disclosure. Figure 20 is a diagram for explaining the operation of an information processing system according to an embodiment of this disclosure. Figure 21 is a diagram for explaining the operation of an information processing system according to an embodiment of this disclosure. Figure 22 is a diagram showing an example of the processing configuration of a business server according to an embodiment of this disclosure. Figure 23 is a diagram for explaining the operation of an information processing system according to an embodiment of this disclosure. Figure 24 is a diagram showing an example of the hardware configuration of a business 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 an acquisition means 101 and an issuance means 102 (see Figure 1). The acquisition means 101 acquires the electronic identification card and biometric information of the user who purchased the product (step S1 in Figure 2). The issuance means 102, upon successful verification of the acquired identification card and successful identity verification using the biometric information obtained from the acquired identification card, issues a certificate of ownership of the product to the user who purchased the product (step S2).
[0016] Users who purchase a product from a business can obtain a certificate of ownership for that product from the information processing device 100. If the product malfunctions, the user can easily prove that they are the owner of the product by presenting the certificate of ownership stored on their smartphone or other device.
[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 sharing business operator, and at least one business operator.
[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] 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).
[0023] An information sharing service provider is a business whose business is to acquire information from users and provide information about those users to the service provider. An information sharing service provider is a business that facilitates information exchange between users and service providers.
[0024] The information sharing service provider has a sharing server 20. The sharing server 20 is operated by the information sharing service provider. The sharing server 20 is a server that performs the processing and operations necessary to carry out the business of the information sharing service provider. 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).
[0025] Businesses are corporations and other entities that conduct profit-making or non-profit activities.
[0026] The business operator provides a business operator server 30 for conducting business. The business operator server 30 is operated by the business operator. The business operator server 30 may be installed in the business operator's building or on a network (on the cloud).
[0027] 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.
[0028] Each device shown in Figure 3 is connected to a network. Specifically, the server device 10, the cooperating server 20, the carrier server 30, and the terminal 40 are connected to the network by wired or wireless communication means.
[0029] The configuration of the information processing system shown in Figure 3 is illustrative and not intended to limit its configuration. For example, each certificate issuer's server device 10, the information sharing service provider's sharing server 20, and the service provider's service provider server 30 may belong to different networks. 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 service provider may include multiple sharing servers 20, and each service provider may include multiple service provider servers 30.
[0030] [Outline of Operation] Next, the outline of the operation of the information processing system according to the first embodiment will be described.
[0031] In the first embodiment, a user purchases a product manufactured by a business, and the business issues a certificate of ownership to the purchaser. For example, a game console manufacturer issues a certificate of ownership to the purchaser of the game console.
[0032] <Marketplace Account Creation> Users create an account on a marketplace for buying, selling, and storing NFTs (Non-Fungible Tokens). Users operate terminal 40 to access a server (not shown in Figure 3, etc.) that implements the marketplace. Users create an account on the server that implements the marketplace.
[0033] In the following explanation, the wallet address indicating the owner of an NFT will be referred to as the "NFT wallet address."
[0034] <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.
[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 and employee IDs 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 the terminal 40 to request a certificate issuer to issue a certificate. Specifically, the wallet application sends a certificate issuance request to the certificate issuer. The certificate issuer issues VCs (Verifiable Credentials) whose content can be verified online as certificates. In the following description, VCs are referred to as "credential certificates".
[0040] In addition, a specific certificate issued as a credential certificate is represented by appending "VCs" after the name of the certificate. For example, a My Number card issued as a credential certificate is referred to as "My Number card VCs".
[0041] By acquiring credential certificates from each certificate issuer, digital content such as that shown in Figure 4 is stored in the user's digital wallet. Note that in the following description, unless otherwise specified, the content stored in the digital wallet described above is a credential certificate.
[0042] <Acquisition of Credential Certificate> First, the acquisition of a credential certificate will be described.
[0043] Prior to the credential certificate issuance request, the user's terminal 40 (wallet application) generates a public key and private key pair. 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 on the blockchain (step S01 in Figure 5).
[0045] Further, the user's terminal 40 requests the credential certificate issuer (server device 10) to issue a credential certificate while presenting the user DID. Specifically, the terminal 40 transmits a "certificate issuance request" including information related to the certificate to be issued (for example, the type of the credential certificate), information required for issuing the credential certificate, the user DID, and the like to the server device 10 (step S02).
[0046] It should be noted that the server device 10 generates and stores the issuer's DID (issuer DID), private key, and public key in advance.
[0047] Upon receiving the certificate issuance request, the certificate issuer determines whether the issuance of the credential certificate desired by the user is possible.
[0048] If the issuance of the credential certificate desired by the user is possible, 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 containing the type of the credential certificate, issuing organization name, issuance date and time, validity period, etc., assertion content (qualification information, claims), and proof such as the issuer's public key information and electronic signature. Note that specific information certified by the issuer is described in the assertion 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 acquisition URL from the URL (Uniform Resource Locator) of the storage location of the credential certificate. The server device 10 transmits an affirmative response (response to the certificate issuance request) including the generated certificate acquisition 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 (Verifiable Data Registry).
[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] <Issuance of Certificate of Ownership> When a user purchases a product, the business's employees request the purchaser to provide purchaser information. At that time, the business code and order code are communicated to the purchaser by any means (see Figure 6).
[0055] A business code is a code (ID) assigned to each business participating in the information processing system. Business codes are shared between information sharing businesses and businesses by any means. For example, the administrator of an information sharing business determines the business code and notifies the business of the determined business code. The person in charge at the information sharing business sets the determined business code and the corresponding business information (e.g., company name, contact information, business server 30 address, etc.) on the sharing server 20. The person in charge at the business also sets the notified business code on their own business server 30.
[0056] An order code is a code (ID) used to identify a sales contract concluded between a user and a business (or retailer). For example, an employee instructs the business server 30 to issue an order code via the business terminal 31. The business server 30 generates a unique order code for each order and sends it to the business terminal 31.
[0057] The business terminal 31 displays the received order code. At that time, the business terminal 31 converts the business code and the order code to generate a two-dimensional code and displays the generated two-dimensional code. The product purchaser operates terminal 40 to read the two-dimensional code displayed on the business terminal 31.
[0058] Terminal 40 decrypts the 2D code to obtain the business code and order code. Once the business code and order code are obtained, terminal 40 reads an electronic identification document from the digital wallet. Specifically, terminal 40 reads identification documents (VCs) from the digital wallet that verify biometric information (e.g., facial image) in addition to the four basic pieces of information such as name, gender, date of birth, and address. For example, terminal 40 reads My Number Card VCs from the digital wallet.
[0059] Terminal 40 signs the identity document VCs using a private key corresponding to the user DID (for example, the wallet address of a digital wallet).
[0060] Furthermore, terminal 40 acquires the user's biometric information. For example, terminal 40 acquires a facial image through a so-called selfie.
[0061] Terminal 40 sends a "purchaser information request" to the linked server 20, which includes the business code, order code, biometric information, user DID, NFT wallet address, and identity certificate VCs (step S11 in Figure 6).
[0062] Upon receiving a request for purchaser information, the linked server 20 verifies the identity document VCs included in the request. If the verification of the identity document VCs is successful, the linked server 20 performs identity verification using the biometric information (selfie face image) included in the purchaser information request and the biometric information (face image) obtained from the identity document VCs.
[0063] If the verification of the identity document VCs and identity confirmation are successful, the linked server 20 transmits all or part of the information obtained from the identity document VCs to the business server 30 of the business corresponding to the business code.
[0064] For example, the linked server 20 sends a "purchaser information notification" containing the four basic pieces of information obtained from the identity certificate VCs, the order code, the user DID, and the NFT wallet address to the business server 30 corresponding to the business code (step S12).
[0065] When the interoperation server 20 sends a buyer information notification to the business server 30, it sends an affirmative response (a response to the buyer information request) to the terminal 40 indicating that the buyer information has been successfully provided to the business. If the interoperation server 20 is unable to send the buyer information notification to the business server 30, it sends a negative response to the terminal 40 indicating that the buyer information cannot be provided to the business.
[0066] Furthermore, the business operator's employees input information that identifies the product being sold (product identification information; for example, the product's serial number) into the business operator's terminal 31. The business operator's terminal 31 then sends a "request for issuance of proof of ownership" to the business operator's server 30, which includes the input product identification information and the order code (the order code notified to the product purchaser) (step S13).
[0067] Upon receiving the buyer information notification and the ownership certificate issuance request, the business server 30 generates an ownership certificate designating the product buyer as the owner of the sold product.
[0068] Here, the business server 30 stores information about products manufactured by the company. For example, the business server 30 of a game console manufacturer stores the product name, manufacturing date, serial number, exterior photos, product specifications, etc. The business server 30 stores information such as the product name and manufacturing date using a product management database.
[0069] The business server 30 uses the order codes included in the buyer information notification and the ownership certificate issuance request to associate the information included in the buyer information notification with the information included in the ownership certificate issuance request.
[0070] Furthermore, the business server 30 searches the product management database using the product identification information (e.g., serial number) included in the ownership certificate issuance request as a key. From the entries identified by the search, the business server 30 retrieves information about the product purchased by the user (e.g., product name, manufacturing date, etc.).
[0071] The business server 30 generates a certificate of ownership using the retrieved product information and the product purchaser information (e.g., basic four pieces of information, user DID, NFT wallet address). The business server 30 generates a certificate of ownership that proves that the owner of the sold product is the product purchaser.
[0072] In this case, the business server 30 generates (issues) a certificate of ownership in either the form of a credential certificate or an NFT. If the product sold to the user is a non-resaleable product, the business server 30 generates a certificate of ownership in the form of a credential certificate. If the product sold to the user is a resaleable product, the business server 30 generates a certificate of ownership in the form of an NFT.
[0073] For example, if the product being sold is a game console or home appliance, the ownership certificate will be generated in the form of an NFT (Non-Funded Transaction). Alternatively, if the product being sold is a medical device, the ownership certificate will be generated in the form of a credential certificate.
[0074] Furthermore, the business operator's administrators, etc., register the resale settings (resal permitted, resale prohibited) in the business operator's server 30 in advance, according to the product's characteristics and the company's policies. In addition, the business operator's employees, etc., explain the resale regulations to the buyer when selling the product.
[0075] First, we will explain the case where the service provider server 30 issues a certificate of ownership in the form of a credential certificate.
[0076] In this case, the business server 30 generates ownership certificate VCs using the purchaser information (basic four pieces of information about the product purchaser, user DID) and product information obtained from the cooperating server 20. For example, the business server 30 generates ownership certificate VCs that include the information shown in Figure 7.
[0077] The business server 30 issues the generated ownership certificates (VCs) to the user (product purchaser). Specifically, the business server 30 stores the generated ownership certificates (VCs) in online storage or the like and generates a URL for obtaining the certificate. The business server 30 sends an acknowledgment (a response to the ownership certificate issuance request) containing the generated URL for obtaining the certificate to the business terminal 31 (step S14 in Figure 6).
[0078] The carrier terminal 31 converts the URL for obtaining the certificate included in the received acknowledgment into a two-dimensional code. The carrier terminal 31 then displays the two-dimensional code.
[0079] The user operates terminal 40 to read a 2D code. Terminal 40 decrypts the 2D code and obtains a URL for obtaining a certificate. Terminal 40 accesses the URL for obtaining a certificate and obtains ownership certificates (VCs). Terminal 40 stores the ownership certificates (VCs) in a digital wallet.
[0080] Next, we will explain the case where the service provider server 30 issues a certificate of ownership in NFT format. In the following explanation, the NFT issued as a certificate of ownership will be referred to as a "certificate of ownership NFT".
[0081] First, the business operator's representative generates a smart contract to issue ownership certificate NFTs, and then deploys the generated smart contract to the blockchain.
[0082] When a business server 30 needs to issue a Certificate of Ownership NFT, it calls a function in the smart contract and inputs the information necessary to issue the Certificate of Ownership NFT (the NFT wallet address of the product purchaser, information about the product being sold, the business ID, etc.).
[0083] When the smart contract is executed, a Certificate of Ownership NFT is issued. For example, the business server 30 issues a Certificate of Ownership NFT containing information as shown in Figure 8. The metadata of the Certificate of Ownership NFT includes information about the product being sold. When the smart contract is executed, the buyer's wallet (NFT wallet address) is associated with the Certificate of Ownership NFT.
[0084] Since the Certificate of Ownership NFT is made public via the blockchain, as shown in Figure 8, the Certificate of Ownership NFT (the metadata of the Certificate of Ownership NFT) does not contain personal information such as the owner's basic four pieces of information.
[0085] The operator server 30 sends an acknowledgment (response to the request for issuance of a certificate of ownership) to the operator terminal 31, which includes the token ID, contract address, transaction ID, and product name obtained from the execution of the smart contract (step S14 in Figure 6).
[0086] The carrier terminal 31 converts the token ID and other information included in the received acknowledgment into a two-dimensional code. The carrier terminal 31 then displays the two-dimensional code.
[0087] The user operates terminal 40 to read the 2D code. Terminal 40 decrypts the 2D code and obtains the token ID, etc. Terminal 40 stores the product name and ownership certificate NFT information (token ID, contract address, transaction ID, etc.) in association.
[0088] Alternatively, terminal 40 may store the ownership certificate NFT information as one of the digital contents in a digital wallet. In the following explanation, the operation of the information processing system will be described using the case where the ownership certificate NFT information is stored in a digital wallet as an example.
[0089] In this manner, the terminal 40 held by a user who has purchased a product manufactured by the business transmits the user's electronic identification document (identification document VCs) and biometric information to the linked server 20. If the linked server 20 successfully verifies the received identification document and also successfully verifies the user's identity using the biometric information obtained from the identification document and the received biometric information, it transmits the user's information (basic four pieces of information, user ID, etc.) to the business server 30. Upon receiving the user's information, the business server 30 issues a certificate of ownership of the product, with the user who purchased the product as the recipient. The terminal 40 stores the issued certificate of ownership (certificate of ownership VCs, certificate of ownership NFT).
[0090] Furthermore, if the product is set to be non-resaleable, the business server 30 issues a certificate of ownership as a credential certificate. Alternatively, if the product is set to be resalable, the business server 30 issues a certificate of ownership as an NFT (Non-Fungible Token).
[0091] <Use of Proof of Ownership Certificate> If a purchased product malfunctions, the user can visit the business's store or other location to request repairs. In this case, the user can use the Proof of Ownership Certificate of the purchased product as a product warranty.
[0092] An employee of a business that has been requested to perform repairs or other services will require the user to present proof of ownership of the purchased goods.
[0093] The user operates terminal 40 to select the ownership certificate (ownership certificate VCs, ownership certificate NFT) of the target product from among the digital content stored in the digital wallet.
[0094] Terminal 40 reads the designated ownership certificate from the digital wallet.
[0095] If the ownership certificate is issued as a credential certificate, terminal 40 signs the ownership certificate VCs read using the private key corresponding to the user DID.
[0096] Terminal 40 provides the business operator with signed ownership certificates (VCs). Specifically, terminal 40 converts the signed ownership certificates (VCs) and user DID into a two-dimensional code and displays it. Terminal 40 presents the ownership certificates (VCs) to the business operator as verifiable presentations (VPs).
[0097] Employees of the business operator operate the business operator terminal 31 to read the 2D code and obtain ownership certificates (VCs). The business operator terminal 31 verifies the obtained ownership certificates (VCs). At that time, the business operator terminal 31 obtains the public key from the blockchain.
[0098] If the verification of the acquired ownership certificate VCs is successful, the business terminal 31 outputs the information stated in the ownership certificate VCs (for example, the four basic pieces of information of the owner, product name, serial number, etc.). For example, the business terminal 31 displays or prints the four basic pieces of information, product name, serial number, etc. stated in the ownership certificate VCs on the LCD monitor.
[0099] The service provider's employees check the information output by the service provider terminal 31 (basic four pieces of information, product name, serial number, etc.) and decide whether or not to accept the user's request (repair request). For example, the employee will accept the repair if the serial number of the product brought in by the user matches the serial number obtained from the ownership certificate VCs.
[0100] If the ownership certificate is issued as an NFT, terminal 40 converts the contract address, token ID, and NFT wallet address of the ownership certificate NFT into a two-dimensional code and displays the generated two-dimensional code.
[0101] The operator terminal 31 obtains the contract address, token ID, etc. of the ownership certificate NFT via a 2D code. The operator terminal 31 accesses the blockchain and obtains the ownership certificate NFT corresponding to the contract address and token ID obtained from terminal 40.
[0102] The operator terminal 31 verifies the acquired ownership certificate NFT. Specifically, if the owner address obtained from the acquired ownership certificate NFT matches the NFT wallet address obtained from terminal 40, the operator terminal 31 determines that the user of terminal 40 is the owner of the ownership certificate NFT. In other words, the operator terminal 31 determines that it has successfully verified the ownership certificate NFT.
[0103] If the verification of the ownership certificate NFT is successful, the operator terminal 31 accesses the metadata of the acquired ownership certificate NFT and obtains the product name, serial number, etc.
[0104] The service provider terminal 31 displays the acquired product name, serial number, etc. An employee of the service provider checks the information output by the service provider terminal 31 and decides whether or not to accept the user's request (repair request).
[0105] In this manner, terminal 40 provides the business terminal 31 with the ownership certificate stored in the digital wallet in response to the user's operation. The business terminal 31, operated by an employee of the business, provides the employee with information obtained from the provided ownership certificate. Specifically, the business terminal 31 verifies the ownership certificate (ownership certificate VCs, ownership certificate NFT) provided by terminal 40, and if the verification is successful, it notifies the employee of the product information (product name, serial number, etc.) obtained from the ownership certificate.
[0106] <Transfer of Goods> As mentioned above, goods for which ownership certificates have been issued in NFT format can be transferred (resold). Users who wish to sell their possessions can list the ownership certificate NFT corresponding to the item on the marketplace.
[0107] Once a sales contract is concluded between the transferor and the transferee, settlement is carried out by the marketplace, and the ownership of the item is changed. At this time, a smart contract for reselling the item is executed, and a transaction corresponding to the change of ownership of the ownership certificate NFT is written to the blockchain.
[0108] Next, we will describe the details of each device included in the information processing system according to the first embodiment.
[0109] [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.
[0110] Figure 9 shows an example of the processing configuration (processing module) of a terminal 40 according to the embodiment disclosed herein. Referring to Figure 9, the terminal 40 comprises a communication control unit 201, an acquisition control unit 202, a utilization control unit 203, and a storage unit 204.
[0111] 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.
[0112] 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.
[0113] Figure 10 is a flowchart showing 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 10.
[0114] 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.
[0115] 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).
[0116] 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).
[0117] 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 (e.g., name of the local government, name of the training institution, name of the certification body for qualifications, etc.), the type of certificate desired, etc. Furthermore, the acquisition control unit 202 acquires information necessary for the certificate issuer to issue the credential certificate (e.g., name, etc.).
[0118] 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, the information necessary for issuing the certificate, and the user DID.
[0119] The acquisition control unit 202 transmits a "certificate issuance request" including the type of credential certificate, information necessary for issuing the certificate, user DID, etc., to the server device 10 of the certificate issuer selected by the user (step S103).
[0120] The acquisition control unit 202 receives a response (affirmative response, negative response) to the certificate issuance request from the server device 10 (step S104).
[0121] 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).
[0122] 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).
[0123] The acquisition control unit 202 stores the acquired credential certificate in the digital wallet (step S108).
[0124] For example, a user obtains identity verification documents (VCs) from the local government. The acquisition control unit 202 stores the acquired credential certificates in a digital wallet.
[0125] The usage control unit 203 is a means for controlling the use of digital content (credential certificates) stored in the digital wallet.
[0126] Figure 11 is a flowchart showing an example of the operation of the usage control unit 203. The operation of the usage control unit 203 according to the embodiment disclosed herein will be explained with reference to Figure 11. Here, the operation of the usage control unit 203 when obtaining a certificate of ownership will be explained.
[0127] The user control unit 203 reads the two-dimensional code in response to the user's operation and obtains the business operator code and order code from the read two-dimensional code (step S201).
[0128] Upon obtaining the business code and order code, terminal 40 requests the information sharing service provider to provide the purchaser information.
[0129] Specifically, the usage control unit 203 obtains identity certificates (VCs) from the digital wallet that prove the basic four pieces of information and biometric information of the recipient (step S202). For example, the usage control unit 203 reads My Number Card VCs from the digital wallet.
[0130] The user control unit 203 signs the identity certificate VCs using the private key corresponding to the user DID.
[0131] Furthermore, the user control unit 203 acquires the user's biometric information (step S203). For example, the user control unit 203 acquires the user's face image (selfie face image) through a so-called selfie.
[0132] The user control unit 203 sends a "purchaser information request" to the linked server 20, which includes the business code, order code, biometric information, user DID and NFT wallet address, and signed identity certificate VCs (step S204).
[0133] The user control unit 203 receives a response (affirmative response, negative response) from the linked server 20 to the request for purchaser information (step S205).
[0134] Upon receiving a negative response (step S206, No branch), the user control unit 203 notifies that the user's information was not provided to the service provider (notification of information provision failure; step S207).
[0135] Upon receiving an affirmative response (step S206, Yes branch), the user control unit 203 notifies that the user's information has been provided to the service provider (notification of successful information provision; step S208).
[0136] When the purchaser information is transmitted to the service provider, the user control unit 203 can obtain the ownership certificate (ownership certificate VCs, ownership certificate NFT) issued by the service provider server 30.
[0137] Specifically, the user control unit 203 reads the two-dimensional code displayed on the service provider terminal 31 in response to the user's operation. If a URL for obtaining a certificate is obtained from the two-dimensional code, the user control unit 203 accesses the URL and obtains ownership certificates (VCs). If a token ID or the like is obtained from the two-dimensional code, the user control unit 203 obtains information regarding the ownership certificate NFT issued by the service provider server 30.
[0138] The usage control unit 203 stores the acquired ownership certificate in the digital wallet.
[0139] When storing a Certificate of Ownership NFT in a digital wallet, the usage control unit 203 associates the product name with the Certificate of Ownership NFT information (token ID, contract address, transaction ID, etc.) and stores it in the digital wallet.
[0140] Next, we will explain the operation of the usage control unit 203 when using the ownership certificate stored in the digital wallet.
[0141] The user control unit 203 reads the digital content specified by the user (information regarding ownership certificates VCs and ownership certificate NFTs) from the digital wallet.
[0142] When ownership certificate VCs are read, the user control unit 203 signs the read ownership certificate VCs using the private key corresponding to the user DID. The user control unit 203 converts the signed ownership certificate VCs and the user DID into a two-dimensional code and displays it.
[0143] When a Certificate of Ownership NFT (information related to the Certificate of Ownership NFT) is read, the user control unit 203 converts the contract address, token ID, and NFT wallet address of the Certificate of Ownership NFT into a two-dimensional code and displays the generated two-dimensional code.
[0144] The memory unit 204 is a means for storing information necessary for the operation of the terminal 40.
[0145] [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 issuing unit 302, and a storage unit 303.
[0146] 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.
[0147] 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.
[0148] 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 contained in the certificate issuance request (for example, a combination of name and date of birth) as a key.
[0149] 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.
[0150] 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.
[0151] 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.
[0152] 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).
[0153] 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).
[0154] 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.
[0155] 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.
[0156] The memory unit 303 is a means for storing information necessary for the operation of the server device 10.
[0157] [Link Server] Figure 13 is a diagram showing an example of the processing configuration (processing module) of the link server 20 according to the embodiment disclosed herein. Referring to Figure 13, the link server 20 comprises a communication control unit 401, a purchaser information control unit 402, and a storage unit 403.
[0158] 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.
[0159] The buyer information control unit 402 is a means for controlling information related to product purchasers. The buyer information control unit 402 processes the buyer information provision request received from the terminal 40.
[0160] Figure 14 is a flowchart showing an example of the operation of the purchaser information control unit 402 according to the embodiment disclosed herein. Referring to Figure 14, the operation of the purchaser information control unit 402 when a purchaser information request is received will be explained.
[0161] Upon receiving a request for purchaser information, the purchaser information control unit 402 verifies the identity document VCs included in the request (step S301).
[0162] The purchaser information control unit 402 verifies at least one of the three items related to the validity of the identity document VCs (credential certificates).
[0163] The first item is the verification of the electronic signature attached to the credential certificate.
[0164] In this case, the buyer information control unit 402 obtains the issuer DID and user DID listed on the credential certificate. The buyer information control unit 402 obtains the public key corresponding to the obtained issuer DID from the blockchain. Similarly, the buyer information control unit 402 obtains the public key corresponding to the obtained user DID from the blockchain.
[0165] The buyer information control unit 402 verifies the signature of the holder and the signature of the issuer attached to the credential certificate. By verifying these signatures, the buyer information control unit 402 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.
[0166] The buyer information control unit 402 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 buyer information control unit 402 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.
[0167] The second item is to verify that the credential certificate has not been set to invalid.
[0168] In this case, the buyer information control unit 402 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 buyer information control unit 402 also confirms that the credential certificate obtained from the user has not been invalidated by the issuer before its expiration date.
[0169] The buyer information control unit 402 determines that the verification of the credential certificate was successful if the credential certificate is not listed in the revocation list. The buyer information control unit 402 determines that the verification of the credential certificate failed if the credential certificate is listed in the revocation list.
[0170] The third item is verification that the validity period (expiration date) of the credential certificate has not expired.
[0171] The buyer information control unit 402 checks the validity period set on the credential certificate. If the validity period set on the credential certificate has not expired, the buyer information control unit 402 determines that the verification of the acquired credential certificate was successful. If the validity period set on the credential certificate has expired, the buyer information control unit 402 determines that the verification of the acquired credential certificate failed.
[0172] The purchaser information control unit 402 determines that the verification of the credential certificate 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.
[0173] The purchaser information control unit 402 determines that the verification of the credential certificate obtained from the user has failed if it determines that "verification failed" in one of the predetermined items from the first to third items.
[0174] If the verification of the identity document VCs fails (step S302, No branch), the purchaser information control unit 402 sends a negative response to the terminal 40 (step S303). By sending the negative response, the purchaser information control unit 402 notifies the terminal 40 that it has failed to provide purchaser information.
[0175] If the verification of the identity document VCs included in the buyer information request is successful (step S302, Yes branch), the buyer information control unit 402 performs identity verification (step S304).
[0176] Specifically, the purchaser information control unit 402 performs identity verification using biometric information (selfie face image) included in the purchaser information request and biometric information (face image) obtained from the identity document VCs. The purchaser information control unit 402 determines whether the two face images are substantially the same and performs identity verification.
[0177] The purchaser information control unit 402 generates feature quantities from both the selfie face image and the face image included in the identity document VCs.
[0178] Regarding the feature generation process, existing technologies can be used, so a detailed explanation will be omitted. For example, the purchaser information control unit 402 extracts the eyes, nose, mouth, etc., from the face image as feature points. Then, the purchaser information control unit 402 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).
[0179] Next, the buyer information control unit 402 performs a matching process (one-to-one matching) using the two generated feature quantities. Specifically, the buyer information control unit 402 calculates the similarity between corresponding face images using the two feature quantities. Based on the result of thresholding the calculated similarity, the buyer information control unit 402 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.
[0180] If the similarity is greater than a predetermined value (if the distance is shorter than a predetermined value), the purchaser information control unit 402 determines that identity verification was successful. If the similarity is less than or equal to the predetermined value, the purchaser information control unit 402 determines that identity verification failed.
[0181] If identity verification fails (step S305, No branch), the purchaser information control unit 402 sends a negative response to the terminal 40 indicating that it failed to provide purchaser information (step S303).
[0182] If identity verification is successful (step S305, Yes branch), the purchaser information control unit 402 sends a purchaser information notification to the business server 30 (step S306). The purchaser information control unit 402 sends the purchaser information notification to the business server 30 of the business corresponding to the business code included in the purchaser information provision request.
[0183] Specifically, the purchaser information control unit 402 sends a "purchaser information notification" to the business server 30, which includes the four basic pieces of information obtained from the identity certificate VCs and the order code, user DID, and NFT wallet address obtained from the purchaser information request.
[0184] Furthermore, before or after sending the buyer information notification, the buyer information control unit 402 sends an acknowledgment to the terminal 40 (step S307). By sending the acknowledgment, the buyer information control unit 402 notifies the terminal 40 that it has successfully provided the buyer information.
[0185] The memory unit 403 is a means for storing information necessary for the operation of the cooperative server 20.
[0186] [Carrier Server] Figure 15 is a diagram showing an example of the processing configuration (processing module) of a carrier server 30 according to the embodiment disclosed herein. Referring to Figure 15, the carrier server 30 comprises a communication control unit 501, an ownership certificate control unit 502, and a storage unit 503.
[0187] 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 cooperation server 20. The communication control unit 501 also transmits data to the cooperation server 20. 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 send 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.
[0188] The ownership certificate control unit 502 is a means for controlling the ownership certificate of the product.
[0189] When the ownership certificate control unit 502 receives an instruction to issue an order code from the business terminal 31, it generates a unique order code. The ownership certificate control unit 502 then transmits the generated order code to the business terminal 31.
[0190] Upon receiving a buyer information notification from the linked server 20 and a request for issuance of a certificate of ownership from the business terminal 31, the certificate of ownership control unit 502 generates a certificate of ownership designating the product purchaser as the owner of the sold product. The certificate of ownership also certifies information about the product purchased by the user (in particular, product identification information; for example, serial number).
[0191] For example, when a request for issuance of a certificate of ownership is received, the certificate of ownership control unit 502 generates a certificate of ownership if there is a buyer information notification with the same order code among the buyer information notifications already received.
[0192] The ownership certificate control unit 502 searches the product management database using product identification information (e.g., serial number) included in the ownership certificate issuance request as a key. As shown in Figure 16, the product management database stores product name, manufacturing date, serial number, exterior photograph, product specifications, etc. Furthermore, the product management database stores resale settings (resalable, resale not permitted).
[0193] The ownership certificate control unit 502 identifies the product purchased by the user using product identification information (serial number). The ownership certificate control unit 502 reads the information of the product purchased by the user from the product management database.
[0194] Furthermore, the ownership certificate control unit 502 obtains information about the product purchaser (for example, basic four pieces of information, user DID, NFT wallet address) from the purchaser information notification.
[0195] The ownership certificate control unit 502 generates an ownership certificate using the read product information and the product purchaser information. At that time, the ownership certificate control unit 502 determines the format of the ownership certificate according to the resale setting (resal allowed, resale not allowed) of the product purchased by the user.
[0196] Specifically, if the product for sale is set to "not for resale," the ownership certificate control unit 502 generates an ownership certificate in the form of a credential certificate. Conversely, if the product for sale is set to "resale permitted," the ownership certificate control unit 502 generates an ownership certificate in the form of an NFT.
[0197] If the product being sold is not resalable, the ownership certificate control unit 502 generates (issues) ownership certificate VCs with the user corresponding to the user DID as the recipient (holder). For example, the ownership certificate control unit 502 issues ownership certificate VCs, as shown in Figure 7, which include the recipient's basic four pieces of information and product information in the claim details.
[0198] The ownership certificate control unit 502 stores the generated ownership certificate VCs in online storage and generates a URL for obtaining the certificate. The ownership certificate control unit 502 sends an acknowledgment containing the generated URL for obtaining the certificate to the business terminal 31.
[0199] If the product being sold is resalable, the ownership certificate control unit 502 issues an ownership certificate NFT to the user corresponding to the NFT wallet address, designating the user as the issuer (owner of the NFT).
[0200] The ownership certificate control unit 502 reads the function of the smart contract deployed on the blockchain and inputs the information necessary for issuing the ownership certificate NFT (NFT wallet address, information on the product being sold, business ID, etc.).
[0201] When a smart contract is executed, a Certificate of Ownership NFT is issued. For example, the Certificate of Ownership Control Unit 502 issues a Certificate of Ownership NFT containing information as shown in Figure 8. Note that, as shown in Figure 8, the Certificate of Ownership NFT (Metadata of the Certificate of Ownership NFT) does not contain personal information such as the owner's basic four pieces of information.
[0202] The ownership certificate control unit 502 sends an acknowledgment to the business terminal 31 that includes the token ID, contract address, transaction ID, and product name obtained from the execution of the smart contract.
[0203] If a certificate of ownership cannot be issued for reasons such as the product corresponding to the serial number included in the request for issuance of a certificate of ownership not being stored in the product management database, the certificate of ownership control unit 502 will send a negative response to the business terminal 31 indicating that fact.
[0204] Thus, the ownership certificate control unit 502 issues an ownership certificate as a credential certificate when the user's purchased product is set to be non-resaleable. Conversely, when the purchased product is set to be resaleable, the ownership certificate control unit 502 issues an ownership certificate as an NFT (Non-Fungible Token).
[0205] Furthermore, the ownership certificate control unit 502 issues a credential certificate as an ownership certificate, which verifies the four basic pieces of information obtained from an electronic identity card. Alternatively, the ownership certificate control unit 502 issues an NFT as an ownership certificate, which does not include the name, gender, date of birth, and address of the user who purchased the product as metadata.
[0206] The memory unit 503 is a means for storing information necessary for the operation of the business server 30.
[0207] [Carrier Terminal] Examples of carrier terminals 31 include mobile devices such as smartphones, mobile phones, game consoles, and tablets, as well as computers (personal computers, laptops), etc. Carrier terminal 31 can be any device or equipment as long as it can receive user input and communicate with the carrier server 30, etc. Furthermore, the configuration and operation of carrier terminal 31 are clear to those skilled in the art from the above description, so a detailed explanation is omitted.
[0208] [System Operation] Next, the operation of the information processing system according to the first embodiment will be described.
[0209] 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.
[0210] 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).
[0211] Terminal 40 sends a certificate issuance request including the above-mentioned user DID to the certificate issuer's server device 10 (step S22).
[0212] 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.
[0213] The server device 10 provides the generated credential certificate to the terminal 40 by storing it in online storage or the like (step S24).
[0214] 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).
[0215] Figure 18 is a sequence diagram showing an example of the operation of the information processing system according to the embodiment disclosed herein. Referring to Figure 18, the operation relating to the issuance of a certificate of ownership of the information processing system according to the first embodiment will be described.
[0216] Terminal 40 sends a request to the linked server 20 for purchaser information, including identity documents VCs (electronic identity documents issued as credential certificates), biometric information (selfie facial image), etc. (step S31).
[0217] The linked server 20 verifies the identity document VCs included in the received purchaser information request and performs identity verification. If the linked server 20 successfully verifies the identity document VCs and verifies the identity of the purchaser, it sends a purchaser information notification containing the four basic pieces of information of the product purchaser to the business server 30 (step S32).
[0218] The operator server 30 receives a request for issuance of a certificate of ownership from the operator terminal 31.
[0219] The business server 30 generates a certificate of ownership using the information of the product purchaser obtained from the purchaser information notification and the information of the product purchased by the product purchaser (step S33).
[0220] If the purchased item is not resalable, the business server 30 generates ownership certificates (VCs). If the purchased item is resalable, the business server 30 generates ownership certificates (NFTs).
[0221] The business server 30 issues the generated ownership certificate to the product purchaser (step S34). Specifically, the business server 30 provides the terminal 40 via the business terminal 31 with the URL for obtaining the ownership certificate VCs, the token ID of the ownership certificate NFT, etc.
[0222] Terminal 40 stores the ownership certificate in its digital wallet (step S35).
[0223] Next, a modified example of the first embodiment will be described.
[0224] <Modification 1> When purchasing a product, the user may use terminal 40 to verify their identity and present the result to the business operator's employees, etc. Terminal 40 may perform identity verification using the user's identification document VCs and a selfie facial image, and display the result (identity verification successful, identity verification failed). The business operator may sell the product to the customer whose identity has been successfully verified.
[0225] <Modification 2> The purchaser's terminal 40 may transmit identity certificate VCs, biometric information, user DID, NFT wallet address, etc. to the business server 30 without going through the linked server 20. The business server 30 may issue a certificate of ownership if it successfully verifies the identity certificate VCs and confirms the identity of the purchaser.
[0226] In other words, the ownership certificate control unit 502 of the business server 30 may have functions as both an acquisition means and an issuance means. The acquisition means acquires the user's electronic identification document (identity certificate VCs) and biometric information (e.g., a selfie face image) from the terminal 40. Furthermore, the acquisition means also acquires the user's DID, NFT wallet address, etc. from the user's terminal 40. The issuance means may issue an ownership certificate for the product to the user who purchased the product if it has successfully verified the acquired identification document and has also successfully verified the user's identity using the biometric information obtained from the acquired identification document.
[0227] <Modification 3> The purchaser's terminal 40 may provide the business terminal 31 with identity certificate VCs, biometric information, user DID, NFT wallet address, etc. For example, terminal 40 converts the identity certificate VCs, etc. into a two-dimensional code and displays it. Business terminal 31 reads the two-dimensional code displayed on terminal 40 and obtains the identity certificate VCs, etc.
[0228] The business terminal 31 may send a request to the business server 30 for the issuance of a certificate of ownership, which includes the acquired identity certificates (VCs), biometric information, user DID, NFT wallet address, product identification information (e.g., serial number of the product being sold), etc.
[0229] The business server 30 may issue a certificate of ownership if it has successfully verified the acquired identity documents VCs and has also successfully confirmed the identity of the product purchaser.
[0230] <Variation 4> If a purchased product malfunctions, the user may request repairs online. In this case, terminal 40 submits a certificate of ownership (certificate of ownership VCs, certificate of ownership NFT) to the carrier server 30. For example, the carrier server 30 requests the user to provide a certificate of ownership on a website for repair requests.
[0231] The user selects the certificate of ownership for the faulty product. Terminal 40 transmits the selected certificate of ownership to the service provider server 30. The service provider server 30 determines whether to accept the repair based on the product information obtained from the certificate of ownership. If the repair is accepted, the service provider server 30 presents the user with the shipping address for the faulty product.
[0232] <Modification 5> In the above embodiment, the case in which the terminal 40 and the carrier terminal 31 send and receive data using a two-dimensional code was described. However, the terminal 40 and the carrier terminal 31 may also send and receive data using short-range wireless communication means such as Bluetooth® or NFC (Near Field Communication). Alternatively, the terminal 40 and the carrier terminal 31 may send and receive data using Wi-Fi (Wireless Fidelity) or the like.
[0233] <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.
[0234] <Variation 7> If the product purchased by the user is a non-resaleable product, the business server 30 may issue ownership certificate VCs that verify the biometric information of the product purchaser (for example, a facial image obtained from an identification certificate VCs). When the user requests product repair, the business terminal 31 may display a facial image obtained from the ownership certificate VCs. The business's employees may accept the repair request if the face of the user in front of them matches the face (facial image) displayed on the business terminal 31.
[0235] As described above, in the information processing system according to the first embodiment, when the cooperating server 20 successfully verifies the identity certificate VCs obtained from the user and confirms the user's identity, it transmits the user's information (for example, basic four pieces of information) to the business server 30. When the business server 30 obtains information about the product purchased by the user (for example, the serial number) from the business terminal 31, it uses the information obtained from the cooperating server 20 and the information about the product purchased by the user to issue a certificate of ownership in the name of the user. The business server 30 does not need to verify the identity certificate VCs or perform identity confirmation, so the load on the business server 30 is reduced.
[0236] When a user receives a service from a business (for example, product repair service), they only need to present the proof of ownership stored in the digital wallet of terminal 40. In other words, users do not need to keep paper product warranties or other documents, and can receive services from businesses without any obligation to do so.
[0237] Furthermore, users who cannot present a valid proof of ownership will not be able to receive services from the business. Therefore, users who purchase stolen goods or products through channels other than authorized dealers will not be able to receive services from the business. By making this fact widely known, the buying and selling (distribution) of stolen goods and illegally obtained products will be prevented.
[0238] Furthermore, the business operator (business operator server 30) can set the product to be resalable or not resalable by changing the format of the ownership certificate. As a result, the business operator can reflect its own policies in the distribution of the product.
[0239] [Second Embodiment] Next, a second embodiment will be described in detail with reference to the drawings.
[0240] The first embodiment described a case where the certificate of ownership can be used as a product warranty. The second embodiment described a case where the certificate of ownership can be used as the "key" to the product.
[0241] 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 business operator server 30, etc., according to the second embodiment can be the same as that of the first embodiment, so its explanation is omitted.
[0242] The following will focus on explaining the differences between the first and second embodiments.
[0243] In the second embodiment, the explanation will be given using the example of a case where the user purchases an automobile as a product. The user can start the engine using the automobile's ownership certificate as the "key".
[0244] In the second embodiment, the business operator server 30 issues a certificate of ownership for the product to the product purchaser (first user), similar to the first embodiment. The user's terminal 40 stores the certificate of ownership issued to the user. The product (automobile) obtains the certificate of ownership issued to the user from the terminal 40, determines whether the user is the owner of the product (automobile) based on the obtained certificate of ownership, and if the user is the owner of the product, allows the user to use it (permits use).
[0245] More specifically, the product requests the user's terminal 40 to provide proof of ownership of the product. In response to this request, the terminal 40 provides the product with the proof of ownership stored in its digital wallet.
[0246] Figure 19 is a diagram showing an example of the processing configuration of product 32 according to the embodiment of the present disclosure. Referring to Figure 19, product 32 comprises a communication control unit 601, a control unit 602, and a storage unit 603.
[0247] The communication control unit 601 is a means for controlling communication with other devices. For example, the communication control unit 601 receives data (packets) from the terminal 40. The communication control unit 601 also transmits data to the terminal 40. The communication control unit 601 passes the data received from other devices to other processing modules. The communication control unit 601 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 601. The communication control unit 601 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.
[0248] The control unit 602 is a means for realizing the functions of product 32.
[0249] For example, when the button for starting the engine is pressed, the control unit 602 requests the user (user's terminal 40) to present proof of ownership.
[0250] Specifically, the control unit 602 sends a "request for provision of proof of ownership" to the terminal 40 (step S41 in Figure 20). For example, the communication control unit 601 sends the request for provision of proof of ownership to the terminal 40 using a short-range wireless communication means such as Bluetooth® or NFC. The request for provision of proof of ownership includes information such as the product name (vehicle model).
[0251] In response to the receipt of a request for proof of ownership, the usage control unit 203 of terminal 40 transmits the proof of ownership (proof of ownership for the vehicle type specified by the vehicle) stored in the digital wallet to the vehicle. Specifically, the usage control unit 203 transmits the specified proof of ownership (proof of ownership VCs, proof of ownership NFT information) and information identifying the owner (user DID, NFT wallet address) from the vehicle (step S42).
[0252] The vehicle's control unit 602 uses the received ownership certificate to determine whether the user is the owner of the vehicle.
[0253] When the control unit 602 receives a Certificate of Ownership VCs, it verifies the received Certificate of Ownership VCs. If the verification is successful, the control unit 602 determines whether the serial number (product ID) written on the Certificate of Ownership VCs matches the serial number set on the vehicle.
[0254] If the two serial numbers match, the control unit 602 determines that the user is the owner and starts the engine. In other words, the control unit 602 determines that the user has legitimate usage rights and starts the engine. If the two serial numbers do not match, the control unit 602 determines that the user does not have legitimate usage rights and does not start the engine.
[0255] When the control unit 602 receives a Certificate of Ownership NFT (information about the Certificate of Ownership NFT), it accesses the blockchain and obtains the Certificate of Ownership NFT corresponding to the contract address and token ID obtained from the terminal 40.
[0256] The control unit 602 determines whether the owner address obtained from the acquired ownership certificate NFT matches the NFT wallet address obtained from the terminal 40, and whether the serial number written on the ownership certificate NFT matches the serial number set on the automobile.
[0257] If both checks are successful, the control unit 602 determines that the user is the owner of the vehicle and starts the engine. That is, the control unit 602 determines that the user has the right to use the vehicle and starts the engine. If at least one of the two checks fails, the control unit 602 determines that the user does not have the right to use the vehicle and does not start the engine.
[0258] The memory unit 603 is a means for storing information necessary for the operation of the product 32.
[0259] As described above, the terminal 40 according to the second embodiment stores a certificate of ownership of a product sold by the business to a user, which is issued by the business server 30. The usage control unit 203 of the terminal 40 has a function as a means of providing the stored certificate of ownership to the product 32 in response to a request from the product 32. As a result, the owner of the product 32 can use the product 32 if they possess a terminal 40 such as a smartphone. In other words, a person who does not have legitimate authority to use the product 32 (for example, a criminal who stole the product 32) cannot use the product 32.
[0260] [Third Embodiment] Next, a third embodiment will be described in detail with reference to the drawings.
[0261] The second embodiment describes a case where a certificate of ownership can be used as the "key" to the product. The third embodiment describes a case where a certificate of use that can be used as the key to the product is issued.
[0262] Since the configuration of the information processing system according to the third embodiment can be the same as that of the first embodiment, the explanation corresponding to Figure 3 will be omitted.
[0263] The following will focus on explaining the differences between the first to third embodiments.
[0264] In the third embodiment, the configuration and operation of the information processing system will be explained using the example of a case where the right to use product 32 is granted to the user's family.
[0265] The user's family requests the owner of product 32 to grant them the right to use the product. The owner's terminal 40 obtains the family's identification documents (VCs, e.g., My Number Card VCs), biometric information (e.g., selfie facial image), user DID, NFT wallet address, etc. For example, the user control unit 203 of terminal 40 obtains the family's (the person requesting the right to use the product) identification documents (VCs, etc.) using Bluetooth® or a 2D code.
[0266] Terminal 40 transmits the acquired family identification documents (VCs, etc.) and the ownership certificate for product 32 to the business server 30. Specifically, the user control unit 203 transmits a "request for issuance of usage rights certificate" to the business server 30, which includes the acquired family identification documents (VCs, etc.), biometric information, user DID, NFT wallet address, and ownership certificate for product 32 (step S51 in Figure 21).
[0267] Figure 22 is a diagram showing an example of the processing configuration of the business operator server 30 according to the embodiment disclosed in this application. Referring to Figure 22, a license certificate control unit 504 is added to the configuration of the business operator server 30 according to the first embodiment.
[0268] Upon receiving a request for issuance of a usage rights certificate, the usage rights certificate control unit 504 verifies the ownership certificates (ownership certificates VCs, ownership certificates NFTs) included in the request. By verifying the ownership certificates, the usage rights certificate control unit 504 determines whether or not the request for issuance of a usage rights certificate is from the legitimate owner.
[0269] If the ownership certificate is successfully verified, the user right certificate control unit 504 verifies the identity document VCs of the recipient of the user right certificate (the user's family). If the identity document VCs are successfully verified, the user right certificate control unit 504 performs identity verification using the biometric information obtained from the identity document VCs and the biometric information included in the user right certificate issuance request.
[0270] If the verification of the identity documents (VCs) and identity confirmation are successful, the user rights certificate control unit 504 issues a user rights certificate.
[0271] The user rights certificate control unit 504 issues a user rights certificate in the form of a credential certificate or NFT.
[0272] First, we will explain the cases in which a certificate of right to use is issued in the form of a credential certificate.
[0273] In this case, the license certificate control unit 504 issues license certificates VCs that include the following information in the claim: basic four pieces of information of the recipient (in the above example, the user's family), product information (product name, serial number, etc.), and information regarding the certificate of ownership that serves as the basis for granting the license.
[0274] If the ownership certificate is a credential certificate, the usage rights certificate control unit 504 sets the credential ID and expiration date of the ownership certificate VCs as information regarding the ownership certificate that serves as the basis for granting usage rights. If the ownership certificate is an NFT, the usage rights certificate control unit 504 sets the token ID and owner's address (wallet address) of the ownership certificate NFT as information regarding the ownership certificate that serves as the basis for granting usage rights.
[0275] The user rights certificate control unit 504 transmits the generated user rights certificates VCs to the terminal 40 (step S52 in Figure 21). Specifically, the user rights certificate control unit 504 transmits an acknowledgment (response to the user rights certificate issuance request) to the terminal 40 that includes a URL for obtaining the user rights certificates VCs.
[0276] Terminal 40 provides a URL for obtaining a certificate to the family member's terminal 40 using Bluetooth® or a QR code (step S53). The family member's terminal 40 obtains the usage rights certificates VCs according to the URL for obtaining the certificate and stores them in a digital wallet.
[0277] Next, we will explain the case where a license certificate is issued in NFT format.
[0278] The user rights certificate control unit 504 calls a function of the smart contract and inputs the information necessary for issuing the user rights certificate NFT (the recipient's NFT wallet address, information on the product being sold, information on the ownership certificate that forms the basis for granting the user rights, the business operator's ID, etc.).
[0279] When the smart contract is executed, a Certificate of Use NFT is issued. Specifically, the Certificate of Use control unit 504 sends the generated Certificate of Use NFT to the terminal 40 (step S52 in Figure 21). More specifically, the Certificate of Use control unit 504 sends an acknowledgment to the terminal 40 that includes the token ID, contract address, transaction ID, product name, etc., obtained from the execution of the smart contract.
[0280] The user's terminal 40 provides the family member's terminal 40 with the information of the Certificate of Use NFT included in the acknowledgment (step S53). The family member's terminal 40 stores the Certificate of Use NFT (information of the Certificate of Use NFT) in its digital wallet.
[0281] If the user rights certificate cannot be issued, such as when the verification of the identity document VCs fails, the user rights certificate control unit 504 will send a negative response to the terminal 40 indicating that fact.
[0282] Next, we will explain how to use the user rights certificate.
[0283] Here, we will describe a case where a certificate of right of use is used as the key for a vehicle, similar to the second embodiment.
[0284] When the button for starting the engine is pressed, the control unit 602 of product 32 (automobile) requests the terminal 40 to present a certificate of ownership or a certificate of usage rights.
[0285] Specifically, the control unit 602 sends a "certificate provision request" specifying the ownership certificate and the usage right certificate as the required certificates (step S61 in Figure 23).
[0286] In response to the receipt of a certificate request, the usage control unit 203 of terminal 40 transmits the ownership certificate or usage right certificate stored in the digital wallet to the vehicle (step S62).
[0287] The vehicle's control unit 602 determines whether the user has the right to use the vehicle based on the received ownership certificate or usage right certificate.
[0288] If a certificate of ownership is received, the control unit 602 should perform the operation (determination) described in the second embodiment.
[0289] When a license certificate VCs is received, the control unit 602 verifies the received license certificate VCs. If the verification is successful, the control unit 602 determines whether the serial number (product ID) written on the license certificate VCs matches the serial number set on the vehicle. If the two serial numbers match, the control unit 602 determines whether the ownership certificate that served as the basis for granting the license to the user is valid.
[0290] If the ownership certificate VCs are the basis for granting the right of use, the control unit 602 determines whether the expiration date of the ownership certificate VCs listed on the right of use certificate VCs has expired. Furthermore, the control unit 602 determines whether the ownership certificate VCs corresponding to the credential ID listed on the right of use certificate VCs have been set to invalid.
[0291] If the ownership certificates (VCs) have not expired and have not been set to invalid, the control unit 602 determines that the ownership certificate that formed the basis for granting the right of use is valid. If the ownership certificates (VCs) have expired or have been set to invalid, the control unit 602 determines that the ownership certificate that formed the basis for granting the right of use is invalid.
[0292] If the ownership certificate NFT is the basis for granting the right to use, the control unit 602 determines whether the owner address of the ownership certificate NFT corresponding to the token ID obtained from the right to use NFT (the token ID of the ownership certificate NFT) matches the owner address (owner of product 32) written on the right to use NFT.
[0293] If the two addresses match, the control unit 602 determines that the certificate of ownership that formed the basis for granting the right of use is valid. If the two addresses do not match, the control unit 602 determines that the certificate of ownership that formed the basis for granting the right of use is invalid.
[0294] If the certificate of ownership that formed the basis for granting the right of use is valid, the control unit 602 starts the engine (making the product 32 available for use by the user). If the certificate of ownership that formed the basis for granting the right of use is invalid, the control unit 602 does not start the engine.
[0295] The control unit 602 may obtain a certificate of ownership and a certificate of usage rights. In this case, if the control unit 602 can confirm the user's right to use the system based on at least one of the certificates, it will start the engine.
[0296] Furthermore, if the product is resold, the owner address listed on the corresponding ownership certificate NFT will not match the owner address listed on the usage rights certificate. In that case, the control unit 602 of product 32 can determine that the ownership certificate NFT issued before the product was resold is invalid and refuse use by the user (the user who was granted usage rights before the resale).
[0297] Furthermore, if the ownership certificates (VCs) for the product (a product that cannot be resold) are invalidated for any reason, the control unit 602 of product 32 can refuse use by the user (the user who was granted the right to use the product before the ownership certificates (VCs) were invalidated).
[0298] Thus, the system includes a first terminal 40 belonging to a first user (e.g., a product purchaser) and a second terminal 40 held by a second user (e.g., a family member of the product purchaser). The first terminal 40 obtains the second user's electronic identification and biometric information and transmits the obtained electronic identification and biometric information to the business server 30, requesting the issuance of a product usage rights certificate for the second user. The business server 30 issues the usage rights certificate if it successfully verifies the obtained identification of the second user and also successfully verifies the user's identity using the biometric information obtained from the second user's identification and the obtained biometric information of the second user. The business server 30 issues a product usage rights certificate for the second user. The second terminal 40 stores the usage rights certificate issued to the second user in its digital wallet.
[0299] Product 32 also requests the second terminal 40 to provide a certificate of right to use Product 32. The second terminal 40 provides Product 32 with the certificate of right to use that is stored in its digital wallet in response to the request. Product 32 determines whether the second user has been granted the right to use Product 32 based on the provided certificate of right to use. If the second user has been granted the right to use Product 32, Product 32 enables the second user to use Product 32.
[0300] Next, a modified example according to the third embodiment will be described.
[0301] <Modification 1> The user rights certificate control unit 504 of the operator server 30 may issue user rights certificates VCs that include the biometric information of the user to whom the user rights are granted. In this case, the control unit 602 of the product 32 takes a picture of the user (the user attempting to start the engine) and acquires biometric information (for example, a facial image).
[0302] The control unit 602 may permit the user to use the system (start the engine) if it successfully performs one-to-one authentication using the acquired biometric information and the biometric information obtained from the user rights certificate VCs.
[0303] <Modification 2> The license certificate control unit 504 may issue a license certificate NFT using a dynamic NFT. In this case, the ownership certificate control unit 502 issues the ownership certificate NFT as a dynamic NFT.
[0304] When issuing a user rights certificate VCs, the user rights certificate control unit 504 adds information about the user rights certificate VCs to be issued (e.g., token ID, etc.) to the ownership certificate NFT (dynamic NFT). The user rights certificate control unit 504 also sets information about the ownership certificate NFT that serves as the basis for granting the user rights (e.g., token ID, etc.) in the user rights certificate NFT.
[0305] When verifying the user's license NFT, the control unit 602 of product 32 obtains the ownership certificate NFT (the ownership certificate NFT that forms the basis for granting the user's license) from the user's license NFT. If the token ID of the user's license NFT obtained from terminal 40 is set in the obtained ownership certificate NFT, the control unit 602 permits the user to use product 32.
[0306] <Modification 3> The operator server 30 may issue a user license certificate with access control functionality. For example, the user license certificate control unit 504 may issue a user license certificate for maintenance personnel in addition to a user license certificate for regular users.
[0307] When a user's license certificate for product 32 is presented, the control unit 602 of product 32 performs normal functions (functions described in the product 32 instruction manual). In contrast, when a user's license certificate for automobile repair personnel is presented, the control unit 602 may perform special functions in addition to normal functions (for example, adjustment of internal parameters or updating of the control program).
[0308] <Modification 4> The business server 30 may limit the number of license certificates that can be issued based on one ownership certificate. Alternatively, the business server 30 may determine the number of license certificates to be issued according to the sales price of the product 32, etc.
[0309] <Modification 5> A company (corporation) may request the business server 30 to issue a usage rights certificate. For example, a leasing company or rental car company that has purchased a car may request the business (business server 30) to issue a usage rights certificate to its customer.
[0310] As described above, the information processing system according to the third embodiment issues a certificate of right to use product 32 to a third party other than the owner of product 32. The person who receives the certificate of right to use product 32 can use product 32 in the same way as the owner. As a result, the convenience of the owner of product 32 and their related parties (e.g., family) is improved.
[0311] Next, we will describe the hardware of each device that makes up the information processing system. Figure 24 shows an example of the hardware configuration of the operator server 30.
[0312] The operator server 30 can be configured using an information processing device (a so-called computer), and has the configuration illustrated in Figure 24. For example, the operator server 30 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.
[0313] However, the configuration shown in Figure 24 is not intended to limit the hardware configuration of the carrier server 30. The carrier server 30 may include hardware not shown, and may not have an input / output interface 313 if necessary. Furthermore, the number of processors 311 etc. included in the carrier server 30 is not limited to the example in Figure 24; for example, multiple processors 311 may be included in the carrier server 30.
[0314] 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).
[0315] 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.
[0316] 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.
[0317] 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).
[0318] The functions of the operator server 30 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.
[0319] Furthermore, the server device 10, the cooperating server 20, and the terminal 40 can also be configured using information processing equipment, similar to the operator server 30. Since their basic hardware configuration is the same as that of the operator server 30, a detailed explanation will be omitted.
[0320] The information processing device, the business operator server 30, is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the business operator server 30 executes a control method for the business operator server 30 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.
[0321] [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.
[0322] 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.
[0323] If the product is not resalable, the business server 30 may issue a certificate of ownership in the form of an SBT (SoulBound Token) in place of or in addition to a certificate of credentials.
[0324] 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.
[0325] 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 issue certificates that require a Certificate Authority (certificates based on a public key infrastructure). Similarly, the business server 30 may issue ownership certificates and usage right certificates in the form of certificates based on a public key infrastructure.
[0326] The business operator (business operator server 30) may grant the user the right to purchase the product before actually selling the product. In this case, the user provides the linked server 20 with identification certificate VCs along with information identifying the product they wish to purchase (e.g., product name). The linked server 20 verifies the identification certificate VCs, and if the verification is successful, requests the business operator server 30 selling the product to issue the right to purchase, specifying the product. If the business operator server 30 has a product available for sale to the user, it generates a purchase right certificate VCs containing the product ID (e.g., serial number) and sends the generated purchase right certificate VCs to the linked server 20. The linked server 20 sends the received purchase right certificate VCs to the user's terminal 40. The terminal 40 stores the purchase right certificate VCs in its digital wallet. The user receives the product at the store. At that time, the user presents the purchase right certificate VCs and identification certificate VCs stored in the digital wallet to the store employee (business operator terminal 31). The business terminal 31 performs identity verification using a facial image obtained by photographing the user in front of it and a facial image obtained from the identity document VCs. If identity verification is successful, the business terminal 31 verifies the purchase right certificate VCs, and if the verification is successful, sells the product corresponding to the ID (serial number) written on the certificate to the user.
[0327] Some functions of the linked server 20, etc., may be implemented in other devices or equipment. More specifically, it is sufficient if the "purchaser information control unit (purchaser information control means)" etc. described above is implemented in any of the devices included in the system.
[0328] 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.
[0329] 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.
[0330] 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.
[0331] 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.
[0332] Some or all of the above embodiments may also be described as follows, but are not limited to the following:
[0333] [Note 1] An information processing device comprising: an acquisition means for acquiring the electronic identification document and biometric information of a user who purchased the product; and an issuance means for issuing a certificate of ownership of the product to the user who purchased the product, if the verification of the acquired identification document is successful and the identity verification using the biometric information obtained from the acquired identification document is successful.
[0334] [Note 2] The issuance means is the information processing device described in Note 1, which issues the ownership certificate as a credential certificate when the product is set to be non-resaleable, and issues the ownership certificate as an NFT (Non-Fungible Token) when the product is set to be resaleable.
[0335] [Note 3] The information processing device described in Note 2, wherein the issuing means issues the credential certificate, which certifies the four basic pieces of information obtained from the identity certificate, as the ownership certificate, and issues the NFT, which does not include the name, gender, date of birth, and address of the user who purchased the product, as the ownership certificate.
[0336] [Note 4] The ownership certificate is an information processing device described in any one of Notes 1 to 3, which certifies the identification information of the product.
[0337] [Note 5] The electronic identification document is a certificate issued as a credential, as described in any one of Notes 1 to 3.
[0338] [Appendix 6] A system comprising: a business server operated by a business operator; a collaboration server operated by an information collaboration business operator; and a terminal held by a user who has purchased a product manufactured by the business operator, wherein the terminal transmits the user's electronic identification and biometric information to the collaboration server; the collaboration server, upon successful verification of the received identification and successful identity verification using the biometric information obtained from the identification and the received biometric information, transmits information of the user who purchased the product to the business operator server; the business operator server, upon receiving information of the user who purchased the product, issues a certificate of ownership of the product with the user who purchased the product as the recipient; and the terminal stores the issued certificate of ownership.
[0339] [Note 7] The system according to Note 6, further comprising a business terminal operated by an employee of the business operator, wherein the terminal provides the stored ownership certificate to the business operator terminal in response to the user's operation, and the business operator terminal provides the employee with information obtained from the provided ownership certificate.
[0340] [Note 8] The system described in Note 7, wherein the business operator's server issues the ownership certificate as a credential certificate when the product is set to be non-resaleable, and issues the ownership certificate as an NFT (Non-Fungible Token) when the product is set to be resaleable.
[0341] [Note 9] A control method for an information processing device, wherein the information processing device acquires the electronic identification document and biometric information of a user who purchased the product, and when the verification of the acquired identification document is successful and the identity verification using the biometric information obtained from the acquired identification document is successful, the device issues an ownership certificate for the product to the user who purchased the product.
[0342] [Note 10] A computer-readable storage medium that stores a program for causing a computer to execute the following: a process for acquiring the electronic identification document and biometric information of a user who purchased the product; and a process for issuing a certificate of ownership of the product, with the user who purchased the product as the recipient, if the acquired identification document is successfully verified and the biometric information obtained from the acquired identification document and the identity verification using the acquired biometric information are successful.
[0343] Furthermore, some or all of the configurations described in Appendices 2 to 5, which are subordinate to Appendice 1 above, may also be subordinate to Appendices 6, 9, and 10 in the same way as those described in Appendices 2 to 5. Moreover, not limited to Appendices 1, 6, 9, and 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.
[0344] 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.
[0345] 10 Server device 20 Interoperation server 30 Business operator server 31 Business operator terminal 32 Product 40 Terminal 100 Information processing device 101 Acquisition means 102 Issuance means 201 Communication control unit 202 Acquisition control unit 203 Usage control unit 204 Storage unit 301 Communication control unit 302 Certificate issuance unit 303 Storage unit 311 Processor 312 Memory 313 Input / output interface 314 Communication interface 401 Communication control unit 402 Purchaser information control unit 403 Storage unit 501 Communication control unit 502 Ownership certificate control unit 503 Storage unit 504 Right of use certificate control unit 601 Communication control unit 602 Control unit 603 Storage unit
Claims
1. An information processing device comprising: an acquisition means for acquiring the electronic identification document and biometric information of a user who purchased a product; and an issuing means for issuing a certificate of ownership of the product to the user who purchased the product, upon successful verification of the acquired identification document and successful identity verification using the biometric information obtained from the acquired identification document.
2. The information processing apparatus according to claim 1, wherein the issuing means issues the ownership certificate as a credential certificate when the product is set to be non-resaleable, and issues the ownership certificate as an NFT (Non-Fungible Token) when the product is set to be resaleable.
3. The information processing apparatus according to claim 2, wherein the issuing means issues the credential certificate, which certifies the four basic pieces of information obtained from the identity certificate, as the ownership certificate, and issues the NFT, which does not include the name, gender, date of birth, and address of the user who purchased the product, as the ownership certificate.
4. The information processing device according to any one of claims 1 to 3, wherein the ownership certificate is subject to the identification information of the product.
5. The information processing device according to any one of claims 1 to 3, wherein the electronic identification document is a document issued as a credential document.
6. A system comprising: a business server operated by a business operator; a linkage server operated by an information linkage business operator; and a terminal held by a user who has purchased a product manufactured by the business operator, wherein the terminal transmits the user's electronic identification and biometric information to the linkage server; the linkage server, upon successful verification of the received identification and successful identity verification using the biometric information obtained from the identification and the received biometric information, transmits information of the user who purchased the product to the business operator server; the business operator server, upon receiving information of the user who purchased the product, issues a certificate of ownership of the product with the user who purchased the product as the recipient; and the terminal stores the issued certificate of ownership.
7. The system according to claim 6, further comprising a business terminal operated by an employee of the business operator, the terminal providing the stored ownership certificate to the business operator terminal in response to the user's operation, and the business operator terminal providing the employee with information obtained from the provided ownership certificate.
8. The system according to claim 7, wherein the business operator's server issues the ownership certificate as a credential certificate when the product is set to be non-resaleable, and issues the ownership certificate as an NFT (Non-Fungible Token) when the product is set to be resaleable.
9. A control method for an information processing device, which acquires the electronic identification document and biometric information of a user who purchased a product, and when it is successful to verify the acquired identification document and when it is successful to verify the identity of the user using the biometric information obtained from the acquired identification document, it issues a certificate of ownership of the product to the user who purchased the product.
10. A computer-readable storage medium that stores a program for causing a computer to execute the following: a process for acquiring the electronic identification document and biometric information of a user who purchased a product; and a process for issuing a certificate of ownership of the product, with the user who purchased the product as the recipient, upon successful verification of the acquired identification document and successful identity verification using the biometric information obtained from the acquired identification document.
