Data management system, data management method, and non-transient recording medium
The data management system uses biometric-generated keys for secure data encryption and management, addressing data loss and privacy risks in SSI technologies, enabling secure access without personal devices.
Patent Information
- Application Number
- KR1020237031695
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-05-31
- Filing Date
- 2022-05-23
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2042-05-23
AI Technical Summary
Existing self-sovereign identity (SSI) technologies using blockchain and smartphones face issues such as data loss due to device loss, privacy risks from cloud backups, and unauthorized data presentation, especially when the device is stolen or not owned by the individual.
A data management system utilizing biometric information to generate secret keys, encrypting data with public keys, and managing data indices, allowing secure data access and presentation without relying on personal devices.
Ensures secure data management and presentation even without personal devices, preventing data loss and misuse, while enabling access for individuals without smartphones.
Smart Images

Figure 112023102474186-PCT00001_ABST
Abstract
Description
Technology Field
[0001] [Citation by Reference]
[0002] The present application claims priority to Japanese Patent Application No. 2021-90942 filed on May 31, 2021, and incorporates the contents thereof by reference.
[0003] The present invention relates to a data management system, a data management method, and a non-transient recording medium. Background Technology
[0004] Self-sovereign Identity (SSI) technology using blockchain and smartphones is known. In this technology, an individual or an organization that is the issuer of a Verifiable Credential (VC) creates a pair of its own identifier (DID), a public key, and a private key, records the DID and the public key on a blockchain, and stores and manages the private key on a device such as a smartphone. The issuer of the Verifiable Credential issues a Verifiable Credential to the individual. Specifically, the individual applies for a VC from the issuer and receives the Verifiable Credential. The individual then holds the Verifiable Credential on a device owned by the individual, such as a smartphone. In this technology, the individual presents the Verifiable Credential to a verifier using the device owned by the individual. Non-patent document 1 describes a data format for a Verifiable Credential to realize the above technology. Prior art literature
[0005] Manu Sporny, Dave Longley, David Chadwick, "Verifiable Credentials Data Model 1.0," World Wide Web Consortium, November 2019, [Accessed May 20, 2021], Internet<https: / / www.w3.org / TR / vc-data-model> The problem to be solved
[0006] In the aforementioned prior art, if an individual loses a personal device such as a smartphone, data such as electronic credentials or secret keys are also lost, making it impossible to verify the said data. Meanwhile, if data such as electronic credentials or secret keys are backed up to storage such as a cloud, there is a risk of misuse by a storage administrator or infringement of privacy, as well as a risk that data such as electronic credentials or secret keys may be leaked to an attacker and impersonated.
[0007] Furthermore, a person who does not own a device such as a smartphone cannot use the aforementioned technology in the first place. In addition, if an individual's smartphone is stolen and misused, there is a risk that data such as electronic credentials will be presented arbitrarily and impersonated. Therefore, one embodiment of the present invention safely manages data even without using an individual's device. means of solving the problem
[0008] To solve the above problem, one aspect of the present invention adopts the following configuration. A data management system comprising a first calculator, a second calculator, and a third calculator, wherein the first calculator generates a secret key from biometric information of a user of the first calculator, the second calculator possesses a public key corresponding to the secret key, encrypted data which is data encrypted based on the public key, a list of indices indicating the type of the data, and an index of the encrypted data, and transmits the list to the first calculator, the first calculator designates an index of the data to be presented which is an index included in the list, and transmits the designated index to the second calculator, the second calculator transmits encrypted data corresponding to the index transmitted by the first calculator to the first calculator, and the first calculator decrypts the encrypted data corresponding to the index based on the secret key and transmits it to the third calculator. Effects of the invention
[0009] According to one aspect of the present invention, data can be safely managed even without using a personal device.
[0010] Problems, configurations, and effects other than those mentioned above will become apparent from the description of the embodiments below. Brief explanation of the drawing
[0011] FIG. 1 is a block diagram illustrating an example of the configuration of a data management system in Example 1. FIG. 2 is a sequence diagram illustrating an example of the registration process in Example 1. FIG. 3a is a sequence diagram illustrating an example of data issuance processing in Example 1. FIG. 3b is a sequence diagram illustrating an example of data issuance processing in Example 1. FIG. 4a is a sequence diagram illustrating an example of data presentation processing in Example 1. FIG. 4b is a sequence diagram illustrating an example of data presentation processing in Example 1. FIG. 5a is an explanatory diagram illustrating an example of a screen transition of an output device of a registration terminal in the registration process of Example 1. FIG. 5b is an explanatory diagram illustrating an example of a screen transition of an output device of a registration terminal in the registration process of Example 1. FIG. 6a is an explanatory diagram illustrating an example of a screen transition of an output device of a registered terminal in the data issuance process in Example 1. FIG. 6b is an explanatory diagram illustrating an example of a screen transition of an output device of a registered terminal in the data issuance process in Example 1. FIG. 7a is an explanatory diagram illustrating an example of a screen transition of an output device of a registered terminal in the data presentation processing of Example 1. FIG. 7b is an explanatory diagram illustrating an example of a screen transition of an output device of a registered terminal in the data presentation process in Example 1. Specific details for implementing the invention
[0012] Hereinafter, embodiments of the present invention will be described in detail based on the drawings. In the embodiments described herein, the same reference numerals are used in principle for identical components, and descriptions of repetition are omitted. Furthermore, it should be noted that the embodiments described herein are merely examples for realizing the present invention and do not limit the technical scope of the present invention.
[0013] Examples 1
[0014] FIG. 1 is a block diagram illustrating an example configuration of a data management system. The data management system includes, for example, a publishing terminal (100), a registration terminal (200), a verification terminal (300), and a PDS (Personal Data Store) (400) connected to a network such as the Internet. The publishing terminal (100) is configured by a calculator having, for example, a CPU (Central Processing Unit) (101), memory (102), an auxiliary storage device (103), a communication device (104), an input device (105), and an output device (106).
[0015] The CPU (101) includes a processor and executes a program stored in memory (102). Memory (102) includes a non-volatile memory element, ROM (Read Only Memory), and a volatile memory element, RAM (Random Access Memory). ROM stores an immutable program (e.g., BIOS (Basic Input / Output System)). RAM is a high-speed and volatile memory element, such as DRAM (Dynamic Random Access Memory), and temporarily stores a program executed by the CPU (101) and data used during the execution of the program.
[0016] The auxiliary storage device (103) is a large-capacity and non-volatile storage device, such as a magnetic storage device (HDD (Hard Disk Drive)) or flash memory (SSD (Solid State Drive)), and stores a program executed by the CPU (101) and data used during the execution of the program. That is, the program is read from the auxiliary storage device (103), loaded into memory (102), and executed by the CPU (101).
[0017] The input device (105) is a device that receives input from an operator, such as a keyboard or a mouse. The output device (106) is a device that outputs the execution result of a program in a format visible to the operator, such as a display device or a printer.
[0018] The communication device (104) is a network interface device that controls communication with other devices according to a predetermined protocol. Additionally, the communication device (104) includes a serial interface such as, for example, USB (Universal Serial Bus).
[0019] Part or all of the program executed by the CPU (101) may be provided to the publishing terminal (100) via a network from a removable media (CD-ROM, flash memory, etc.) which is a non-transient storage medium, or from an external calculator equipped with a non-transient storage device, and stored in a non-volatile auxiliary storage device (103) which is a non-transient storage medium. For this reason, the publishing terminal (100) may have an interface for reading data from the removable media. This is also true for the registration terminal (200), verification terminal (300), and PDS (400).
[0020] The issuing terminal (100) is a computer system configured on a single computer physically, or on multiple computers configured logically or physically, and may operate as separate threads on the same computer or on a virtual computer built on multiple physical computer resources. This is also true for the registration terminal (200), verification terminal (300), and PDS (400).
[0021] The CPU (101) includes, for example, an authentication unit (111), a certificate generation unit (112), a data issuance unit (113), and an encryption unit (114). The authentication unit (111) performs authentication with the registered terminal (200). The certificate generation unit (112) generates an electronic certificate. Here, the electronic certificate may be data to which a digital signature generated based on key data (121) is added to data to which predetermined information is added to data included in personal data (122). Additionally, the electronic certificate may be data to which a digital signature generated based on key data (121) is added to data that includes a UID (an ID identifying the user of the registered terminal (200)) received from the registered terminal (200), a first public key certificate, and, in the case where the identity of the user is verified by the issuing entity or the issuing terminal (100), a method of identity verification, i.e., a second public key certificate.
[0022] The data issuing unit (113) issues data included in the personal data (122) to the registration terminal (200) or PDS (400). The encryption unit (114) encrypts the personal data.
[0023] For example, the CPU (101) functions as an authentication unit (111) by operating according to an authentication program loaded in memory (102), and functions as a certificate generation unit (112) by operating according to a certificate generation program loaded in memory (102). The relationship between the program and the function unit is the same for other function units included in the CPU (101). In addition, the relationship between the program and the function unit is the same for the function units described later that are included in each of the CPU (201) of the registration terminal (200), the CPU (301) of the verification terminal (300), and the CPU (401) of the PDS (400).
[0024] In addition, some or all of the functions of the functional parts included in the CPU (101), the CPU (201) of the registration terminal (200), the CPU (301) of the verification terminal (300), and the CPU (401) of the PDS (400) may be realized by hardware such as, for example, an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array).
[0025] The auxiliary storage device (103) holds, for example, key data (121) and personal data (122). The key data (121) includes the key of the issuing terminal (100) or the public key of the registration terminal (200). The personal data (122) includes the personal data of the user of the registration terminal (200).
[0026] Additionally, some or all of the information stored in the auxiliary storage device (103), the auxiliary storage device (203) of the registration terminal (200), the auxiliary storage device (303) of the verification terminal (300), and the auxiliary storage device (403) of the PDS (400) may be stored in the memory (102), memory (202), memory (302), and memory (402), respectively, or may be stored in a database connected to the said device.
[0027] In addition, in the present embodiment, the information used by the data management system may be represented in any data structure without relying on the data structure. In the present embodiment, the information is represented in a table format, but, for example, a data structure appropriately selected from a list, a database, or a queue may store the information.
[0028] The registration terminal (200) is configured by a calculator having, for example, a CPU (201), memory (202), auxiliary storage device (203), communication device (204), input device (205), output device (206), and biometric information acquisition device (207).
[0029] The description of the hardware for the CPU (201), memory (202), auxiliary storage device (203), communication device (204), input device (205), and output device (206) is omitted because it is the same as the description of the hardware for the CPU (101), memory (102), auxiliary storage device (103), communication device (104), input device (105), and output device (106).
[0030] The CPU (201) includes, for example, a biometric information acquisition unit (211), a key generation unit (212), a certificate generation unit (213), an authentication unit (214), an encryption unit (215), an index acquisition unit (216), and a UID assignment unit (217). The biometric information acquisition unit (211) acquires biometric information of a user of a registered terminal (200) through a biometric information acquisition device (207). The key generation unit (212) generates a public key, a private key, and a common key.
[0031] The certificate generation unit (213) generates a public key certificate. The authentication unit (214) performs authentication with the issuing terminal (100) and authentication with the PDS (400). The encryption unit (215) encrypts data transmitted to the verification terminal (300). The index acquisition unit (216) acquires a data index that specifies the type of data. The UID designation unit (217) designates a UID, which is an ID that identifies the user of the registered terminal (200).
[0032] The auxiliary storage device (203) holds, for example, one or more wallets (221) and key data (222). Each wallet (221) is associated with the user UID of the registered terminal (200) and holds data issued by the issuing terminal (100) to the user. That is, a wallet (221) is a data storage area on the auxiliary storage device (403) that is determined for each user and managed by the user, for storing data including data issued by the issuing terminal (100) to the registered terminal (200) (for example, the user's personal data, electronic certificate, and public key certificate). The key data (222) holds the user's key or auxiliary information of the registered terminal (200).
[0033] The biometric information acquisition device (207) acquires the user's biometric information. For example, a camera that captures an image of the user's face, and a scanner that acquires the user's fingerprints or veins are examples of the biometric information acquisition device (207).
[0034] The verification terminal (300) is configured by a calculator having, for example, a CPU (301), memory (302), auxiliary storage device (303), communication device (304), input device (305), and output device (306). The description of the hardware of the CPU (301), memory (302), auxiliary storage device (303), communication device (304), input device (305), and output device (306) is omitted because it is the same as the description of the hardware of the CPU (101), memory (102), auxiliary storage device (103), communication device (104), input device (105), and output device (106). The CPU (301) includes, for example, a signature verification unit (311). The signature verification unit (311) verifies a signature assigned to data received from the registration terminal (200).
[0035] The PDS (400) is configured by a calculator having, for example, a CPU (401), memory (402), auxiliary storage device (403), communication device (404), input device (405), and output device (406). The description of the hardware of the CPU (401), memory (402), auxiliary storage device (403), communication device (404), input device (405), and output device (406) is omitted because it is the same as the description of the hardware of the CPU (101), memory (102), auxiliary storage device (103), communication device (104), input device (105), and output device (106).
[0036] The CPU (401) includes, for example, a data management unit (411), an authentication unit (412), and a search unit (413). The data management unit (411) creates a wallet (421) corresponding to a designated UID and manages data stored in the created wallet (421). The authentication unit (412) performs authentication with the registered terminal (200). The search unit (413) searches for a wallet (421) corresponding to a UID. The auxiliary storage device (403) holds a wallet (421) for each of, for example, one or more UIDs. The wallet (421) holds data issued by the issuing terminal (100) to the user associated with the UID.
[0037] Additionally, some devices included in the data management system may be integrated, for example. For example, the issuing terminal (100) and the registration terminal (200) may be integrated, and the registration terminal (200) and the PDS (400) may be integrated. Between devices integrated in this way, the authentication process described later may be omitted.
[0038] FIG. 2 is a sequence diagram illustrating an example of a registration process. The UID designation unit (217) of the registration terminal (200) designates a UID, which is an ID identifying the user of the registration terminal (200) (S201). The UID designation unit (217) may store the designated UID in an auxiliary storage device (203) and / or memory (202).
[0039] Specifically, for example, the UID designation unit (217) receives input of a UID from a user of the registered terminal (200) and designates the received UID. Additionally, for example, the UID designation unit (217) may automatically designate the UID, or the registered terminal (200) may possess a UID corresponding to the user, and the UID designation unit (217) may designate the UID by acquiring the UID.
[0040] The biometric information acquisition unit (211) acquires biometric information of a user of a registered terminal (200) (e.g., finger vein, fingerprint, facial image, or signature, etc.) through a biometric information acquisition device (207) (S202). The key generation unit (212) generates a key pair of a secret key and a public key from the biometric information, and auxiliary information as needed (S203). Specifically, for example, the key generation unit (212) generates a key pair from the biometric information according to an algorithm such as a Fuzzy Extractor or Fuzzy Signature. When an algorithm such as a Fuzzy Extractor is used, the said auxiliary information is used in the key generation process from the biometric information during data issuance or data presentation, which will be described later.
[0041] The certificate generation unit (213) generates a first public key certificate (S204). Specifically, for example, the certificate generation unit (213) may generate the first public key certificate by generating a self-certificate based on the secret key generated in step S203, or may obtain the first public key certificate from an authentication station connected to the registration terminal (200).
[0042] The certificate generation unit (213) transmits the UID, the first public key certificate, and auxiliary information, if generated, to the PDS (400) (S205). The data management unit (411) of the PDS (400) creates a wallet (421) corresponding to the UID and registers the first public key certificate and auxiliary information in the wallet (421) (S206). The data management unit (411) transmits the registration result for the wallet (421) of the UID and the first public key certificate to the registration terminal (200) (S207).
[0043] The certificate generation unit (213) stores the UID and the first public key certificate in the wallet (221) (S208). The processing of step S208 may be omitted, but if the processing of step S208 is executed so that a common registration terminal (200) is used for registration processing, data issuance processing, and data presentation processing, the processing of the registration terminal (200) requesting the public key certificate from the PDS (400) can be omitted, thereby reducing the number of communications between the registration terminal (200) and the PDS (400) and improving processing performance. The key generation unit (212) deletes the secret key (S209) and terminates the registration processing.
[0044] Additionally, the certificate generation unit (213) may acquire a second public key certificate issued by the issuing terminal (100) as an electronic certificate in addition to or instead of the first public key certificate, and transmit it to the PDS (400). In this case, the PDS (400) registers the first public key and / or the second public key certificate in the wallet (421) corresponding to the UID. The second public key certificate is a certificate in, for example, X509 format, and includes a description of the UID in the Subject or Subject Unique ID, a public key in the Subject Public Key Info, and an identifier of the data issuing entity in the Issuer. Additionally, the extensions may include a description of an identity verification method (for example, the data issuing entity verifying the insurance card by meeting the user).
[0045] In addition, while the present embodiment describes an example in which a secret key, a public key, and a common key are generated from biometric information, the secret key, public key, and common key may be generated not only from information containing personality such as biometric information, but also from information that an individual can present without effort, such as personal memory information like a password, for example.
[0046] FIGS. 3a and 3b are sequence diagrams illustrating an example of data publication processing. Additionally, although FIGS. 3a and 3b describe processing by a registration terminal (200), the processing described below may be executed by a terminal other than the registration terminal (200) used for data registration processing. That is, the registration terminal (200) used for data registration processing and data publication processing may be the same terminal or a different terminal.
[0047] The UID designation unit (217) of the registered terminal (200) obtains a UID, for example, based on input from a user of the registered terminal (200) (S301). Additionally, if the UID designated by the UID designation unit (217) in step S201 is stored in the memory (102) or auxiliary storage device (103), the processing of step S301 may be omitted.
[0048] Additionally, if auxiliary information is generated in step S203, the UID designation unit (217) transmits the UID to the PDS (400) (S302), and the search unit (413) of the PDS (400) obtains the auxiliary information stored in the wallet (421) corresponding to the UID and sends it to the registration terminal (200) (S303).
[0049] The biometric information acquisition unit (211) acquires biometric information of the user of the registered terminal (200) (e.g., biometric information of the same type as that used during registration processing, such as finger veins, fingerprints, or facial images) through the biometric information acquisition device (207) (S304). The key generation unit (212) generates a secret key from the biometric information using, for example, auxiliary information (S305).
[0050] The UID designation unit (217) transmits the UID to the PDS (400) (S307), and authentication is performed between the registered terminal (200) and the PDS (400) (S309). Specifically, the authentication unit (214) of the registered terminal (200) uses a secret key (S306), and the authentication unit (412) of the PDS (400) uses a first public key certificate or a second public key certificate (hereinafter, if either the first public key certificate or the second public key certificate can be used, it will simply be referred to as a public key certificate) (S308), and authentication is performed between the registered terminal (200) and the PDS (400).
[0051] The processing of steps S302 to S309 may be omitted, but by executing the processing of steps S302 to S309, security against impersonation or input errors of the UID for the PDS (400) from the registered terminal (200) can be ensured. In addition, instead of the processing of steps S302 to S309, authentication by other authentication means (e.g., password authentication or FIDO (First IDentity Online) authentication) may be executed.
[0052] If authentication between the registered terminal (200) and the PDS (400) is successful, the process proceeds to the following steps, but if it fails, the process is terminated. The authentication unit (214) of the registered terminal (200) transmits a request for a public key certificate to the PDS (400) that includes a UID (however, if the processing of step S305 is executed, the UID does not need to be included) (S310). The search unit (413) of the PDS (400) searches for a wallet (421) corresponding to the UID and transmits the public key certificate stored therein to the registered terminal (200) (S311).
[0053] The authentication unit (214) transmits the acquired public key certificate to the issuing terminal (100) (S313), and authentication is performed between the registration terminal (200) and the issuing terminal (100) (S315). Specifically, the authentication unit (214) of the registration terminal (200) uses a secret key (S312), and the authentication unit (111) of the issuing terminal (100) uses the received public key certificate (S314), so that authentication is performed between the registration terminal (200) and the issuing terminal (100).
[0054] If authentication between the registration terminal (200) and the issuing terminal (100) is successful, the process proceeds to the following steps, but if it fails, the process is terminated. The UID designation unit (217) of the registration terminal (200) generates a data issuance application including a data index, which is information specifying the type of data, and a UID (S316), and transmits it to the issuing terminal (100) (S317).
[0055] The user of the registration terminal (200) presents identity verification information to the user of the issuing terminal (100) (S318). The user of the issuing terminal (100) verifies the presented identity verification information (S319). Additionally, the presentation and verification of identity verification information may be performed by the user of the registration terminal (200) and the user of the issuing terminal (100) meeting face-to-face to directly present and visually verify the identity verification document, or the user of the registration terminal (200) may transmit from the registration terminal (200) to the issuing terminal (100), and the user of the issuing terminal (100) may verify the identity verification information displayed on the output device (106) of the issuing terminal (100).
[0056] For example, the user of the issuing terminal (100) can verify the identity of the user of the issuing terminal (100) by using the issuing terminal (100) or another terminal owned by the user to read the My Number card and transmitting the My Number card from the issuing terminal (100) to the registration terminal (200). Additionally, for example, the registration terminal (200) can verify the identity of the user of the issuing terminal (100) by transmitting a public key certificate obtained from the PDS (400) to the issuing terminal (100), or by transmitting personal data (for example, data regarding the attributes or history of the user of the registration terminal (200)) to the issuing terminal (100) in a manner similar to the data presentation processing described later in FIGS. 4a and 4b.
[0057] Additionally, the processing of steps S318 and S319 does not need to be executed, but by executing these processes, impersonation of the user of the registered terminal (200) can be suppressed. Furthermore, after executing these processes, by describing the information regarding the means of identity verification executed therein in the extension area of the second public key certificate described later, the degree to which the second public key certificate can be trusted by other issuing entities or verification entities can be increased.
[0058] The data issuing unit (113) searches for personal data (122) and generates data by obtaining data corresponding to the data index indicated by the received data issuance application and the personal identification information of the user included in the said public key certificate or said identity verification information (S320). This data is, for example, personal data regarding the attributes, qualification information, history, etc. of the user of the registered terminal (200). Examples of the said personal data include the PCR (Polymerase Chain Reaction) test result information (negative certification information) of the user of the registered terminal (200) for Covid-19, a degree certificate proving that the user has obtained a degree from the university when the issuing entity is a university, and the user of the registered terminal (200)'s past purchase history information on an EC (Electric Commerce) site operated by the user of the issuing terminal (100).
[0059] The certificate generation unit (112) of the issuing terminal (100) generates one or more electronic certificates using a secret key included in key data (121) (S321). Here, the electronic certificate is data including user data containing information related to the user and an electronic signature generated using the secret key included in the key data (121) for the user data. The user data may be personal data regarding the user's attributes, qualification information, history, etc., as described above, and in that case, the data format of the electronic certificate may be the VC (Verifiable Credential) format described in Non-Patent Document 1. Additionally, the user data may include a public key included in the public key certificate described above. An electronic certificate containing such a public key can be used as the second public key certificate described above. The second public key certificate may be in X509 format and may include information regarding a UID or a means of identity verification. Additionally, the certificate generation unit (112) may generate multiple electronic certificates in step S321. Also, if the data generated in the aforementioned step S320 does not include electronic certificates, the processing of step S321 does not need to be performed.
[0060] Additionally, the data issuing unit (113) may include one or more electronic certificates generated in step S321 in the data generated in step S320. Additionally, the data issuing unit (113) may generate multiple types of data in step S320.
[0061] The encryption unit (114) generates encrypted data by encrypting the data generated in step S320 (and the electronic certificate if an electronic certificate was generated in step S321) respectively (S322). Specifically, for example, the encryption unit (114) generates encrypted data by obtaining a public key from, for example, a first public key certificate and encrypting the data with the obtained public key using a public key cryptographic method. In addition, for example, the encryption unit (114) generates a common key randomly, encrypts the data with the common key using a common key cryptographic method, and encrypts the common key with the public key using a public key cryptographic method, and the data including the encrypted data and the encrypted common key is encrypted data.
[0062] Additionally, a secret key and a public key are stored in the key data (121) of the issuing terminal (100), and the encryption unit (114) may, after applying a signature to the data generated in S321 using the secret key, execute the encryption data generation process of step S322 and distribute the public key to the verification terminal (300). By doing so, the verification terminal (300) can verify the signature by the issuer applied to the data using the said public key. In particular, if the said signature is executed after the identity verification in steps S318 and S319 is executed, the issuer can guarantee that the data was generated after the issuer verified their identity, at the issuer's security level, without using an authentication station or a registration station.
[0063] The data issuing unit (113) transmits the UID, the data index, and the encrypted data to the PDS (400) (S323). The processing of steps S322 and S323 may be omitted, but by executing the processing of step S322, the processing of steps S324 to S328 described later may be omitted, thereby reducing the effort of the user of the issuing terminal (100). Alternatively, steps S322 and S323 may be omitted, in which case the processing of steps S324 to S328 is executed.
[0064] The data issuing unit (113) transmits the data obtained in step S320 to the registered terminal (200) (S324). The biometric information acquisition unit (211) of the registered terminal (200) acquires the biometric information of the user of the registered terminal (200) through the biometric information acquisition device (207) and generates a secret key using auxiliary information (S325). Additionally, if the processing of steps S302 to S305 is executed, the processing of step S323 may be omitted.
[0065] The encryption unit (215) generates a signature for the received data using the secret key (S326). The processing of step S324 may be omitted, but by executing the processing of step S326, evidence can be left that the user of the registered terminal (200) has personally verified that there are no errors in the content of the data. In the data presentation process described later using FIGS. 4a and 4b, the verification terminal (300) can verify this signature to ensure the reliability of the data.
[0066] The key generation unit (212) generates a common key using auxiliary information from biometric information, and the encryption unit (215) generates encrypted data by encrypting data using the said common key (S327). Additionally, the method of generating encrypted data in step S327 may be the same as the method of generating data described in step S322. The encryption unit (215) transmits the UID, the data index, and the encrypted data to the PDS (400) (S328).
[0067] The data management unit (411) of the PDS (400) stores encrypted data (which may include encrypted electronic certificates) and a data index in a wallet (421) corresponding to the UID (S329). The key generation unit (212) of the registered terminal (200) deletes the secret key and the common key (S330).
[0068] FIGS. 4a and 4b are sequence diagrams illustrating an example of data presentation processing. Additionally, although FIGS. 4a and 4b describe processing by a registration terminal (200), the processing described below may be executed by a terminal different from the registration terminal (200) used for data registration processing and the registration terminal (200) used for data publication processing. That is, the registration terminal (200) used for data registration processing, data publication processing, and data presentation processing may all be the same terminal, or some or all of them may be different terminals.
[0069] The UID designation unit (217) of the registered terminal (200) designates the user UID of the registered terminal (200) (S401). The UID designation unit (217) may designate the user's UID in the same manner as, for example, step S201, or, if the UID is stored in the auxiliary storage device (203) and / or memory (202), may read the UID from the auxiliary storage device (203) or memory (202).
[0070] The index acquisition unit (216) acquires one or more data indices representing the types of data to be presented, for example, according to user input (S402). Additionally, for example, when a data index is specified from a verification terminal (300) (for example, when a data index of data to be presented to a user of the verification terminal (300) is predetermined), the processing of step S402 may be omitted, or the specified data index may be notified to the registration terminal (200), and the index acquisition unit (216) may select only the data indices (partially or entirely) included in the specified index.
[0071] The index acquisition unit (216) transmits the specified UID and a request to acquire a list of data indexes to the PDS (400) (S403). The search unit (413) of the PDS (400) searches for a wallet (421) corresponding to the UID and acquires the public key certificate, the list of data indexes, and auxiliary information stored therein (S404).
[0072] The biometric information acquisition unit (211) of the registered terminal (200) acquires biometric information through the biometric information acquisition device (207) (S405). The search unit (413) of the PDS (400) returns the auxiliary information acquired in step S404 to the registered terminal (200) (S406). The key generation unit (212) generates a secret key using the biometric information acquired in step S405 and the auxiliary information acquired in step S404 (S407). Authentication is performed between the registered terminal (200) and the PDS (400) (S409). Specifically, for example, the authentication unit (214) of the registered terminal (200) performs authentication using the secret key generated in step S407 (S408), and the authentication unit (412) of the PDS (400) performs authentication using the public key certificate included in the search result (S410).
[0073] By executing the authentication of steps S407 to S410, it becomes safer against impersonation of the UID or designation errors by the registered terminal (200). Additionally, other authentication means (such as password authentication or FIDO authentication) may be used in steps S407 to S410. Furthermore, the processing of steps S407 to S410 may be omitted. However, if the encrypted data is written using a public key cryptography method, the processing of step S407 needs to be executed because a secret key is used in the data decryption process described later.
[0074] If authentication in steps S407 to S410 is successful, processing after step S411 is executed, but if authentication in steps S407 to S410 is unsuccessful, processing after step S411 is not executed and processing is terminated. The search unit (413) of the PDS (400) transmits the data index list and public key certificate obtained in step S404 to the registered terminal (200) (S411).
[0075] The index acquisition unit (216) of the registered terminal (200) selects one or more data indices from the received index list, for example, according to user input (S412). The index acquisition unit (216) transmits the selected data indices to the PDS (400) (S413). The search unit (413) of the PDS (400) searches for and obtains encrypted data corresponding to the received data indices from the wallet (421) corresponding to the UID (S414). The search unit (413) transmits the obtained encrypted data to the registered terminal (200) (S415).
[0076] The key generation unit (212) generates a common key using the biometric information obtained in step S405 (S416). However, if the data is not encrypted with the common key in step S322, the processing of step S417 may be omitted. The encryption unit (215) decrypts the encrypted data using a secret key or a common key according to the algorithm in which the encrypted data was encrypted (S417).
[0077] The encryption unit (215) applies an electronic signature to the decrypted data and the consent information for providing the data using a secret key (S418). This consent information for providing is, for example, held in advance in a verification terminal (300) and transmitted by the verification terminal (300) to a registration terminal (200). The consent information for providing includes, for example, the hash value of the data, user information, verifier information, the creation date and time of the data, and the purpose of use of the data (for example, determined by the input of a user of the issuing terminal (100)). By applying an electronic signature in step S418, the user of the verification terminal (300) can prove to a third party that the data was not obtained fraudulently or is not being used for purposes other than intended. The encryption unit (215) transmits the designated UID and data, and further, if generated, the consent information for providing, various signatures, electronic certificates, and the public key certificate obtained in step S411 to the verification terminal (300) (S419).
[0078] The signature verification unit (311) of the verification terminal (300) verifies the signature generated in step S418 using the public key included in the public key certificate received in step S419 (S420). Specifically, for example, the signature verification unit (311) verifies the electronic signature assigned to the data and the electronic signature assigned to the consent to provide information generated in step S418 using the public key included in the public key certificate received in step S419 (S420). The signature verification unit (311) displays the verification result, for example, on the output device (306) of the verification terminal (300) and / or the output device (206) of the registration terminal (200).
[0079] In summary, the data management system of the present embodiment generates a common key from biometric information as described above and stores data in a PDS (400) in a form that cannot be decrypted without the common key, thereby enabling even users who do not possess a mobile terminal (such as a smartphone or tablet terminal) for performing data or key management to perform registration processing and data presentation processing. As a result, the risk of loss or theft of the mobile terminal is eliminated, and even users who do not possess a mobile terminal can utilize the structure of a self-sovereign identity.
[0080] In addition, since the registered terminal (200) performs authentication or signing using a public key generated from the user's own biometric information, it is possible to prevent fraudulent acts such as the user colluding with another person to transfer or sell data or, if the registered terminal (200) is a mobile terminal, the mobile terminal.
[0081] FIGS. 5a and 5b are explanatory diagrams illustrating an example of a screen transition of an output device (206) of a registration terminal (200) during registration processing. In addition, in the example of a screen transition described below, the designation of the UID is performed automatically by the registration terminal (200). Furthermore, in the example of a screen transition of FIGS. 5a to 7b, the registration terminal (200) obtains a Covid-19 negative certificate from the issuing terminal (100), registers it in the PDS (400), and presents it to the verification terminal (300). Also, in FIGS. 5a to 7b, if "Back" is selected, it returns to the previous screen.
[0082] First, the home screen (501) is displayed. On the home screen (501), an icon (551) for launching a data management application is displayed. When the icon (551) is selected, the screen transitions to the menu screen (502). When "-Create New Wallet" is selected on the menu screen (502), data issuance processing begins, and the screen transitions to the wallet creation screen (503).
[0083] In the wallet creation screen (503), input of the wallet name is required. When the wallet name is entered in the wallet creation screen (503), the process transitions to the first biometric registration screen (504). In the examples of FIGS. 5a and 5b, a face image, an image of the right finger vein, and an image of the left finger vein are acquired as biometric information. In the first biometric registration screen (504), input of a face image is required via a camera, which is an example of a biometric information acquisition device (207).
[0084] In the first biometric registration screen (504), when the face image is captured by the camera, the screen transitions to the first biometric registration completion screen (505). In the first biometric registration completion screen (505), information indicating that the registration of the face image is complete is displayed. In the first biometric registration completion screen (505), when "NEXT" is selected, the screen transitions to the second biometric registration screen (506). In the second biometric registration screen (506), input of an image of the right finger vein is required by a scanner, which is an example of a biometric information acquisition device (207).
[0085] In the second biometric registration screen (506), once the image of the right finger vein is scanned once with a scanner, the screen transitions to the second biometric registration screen (507). In the example of FIG. 5a and FIG. 5b, the registration of the right finger vein and the left finger vein is completed by scanning them three times each. After the second biometric registration screen (507) is displayed, when the image of the right finger vein is scanned two more times with a scanner, the screen transitions to the third biometric registration screen (508).
[0086] In the third biometric registration screen (508), once the image of the left finger vein is scanned once with a scanner, the process transitions to the third biometric registration screen (509). After the third biometric registration screen (509) is displayed, if the image of the left finger vein is scanned two more times with a scanner, the acquisition of biometric information in step S202 is completed, the processing of steps S202 to S209 is executed, and the process transitions to the biometric registration confirmation screen (510). On the biometric registration confirmation screen (510), information indicating that biometric information has been acquired and the registration process is completed, or a wallet name, is displayed. From the biometric registration confirmation screen (510), the process returns to the home screen (501).
[0087] FIGS. 6a and 6b are explanatory diagrams illustrating an example of screen transitions of an output device (206) of a registered terminal (200) in data issuance processing. First, transitions are made from the home screen (501) to the menu screen (502). When "-Create New Wallet" is selected on the menu screen (502), transitions are made to the identity verification screen (603). On the identity verification screen (603), the processing of step S302 is executed. That is, on the identity verification screen (603), input of a face image is required through a camera, which is an example of a biometric information acquisition device (207) (i.e., information indicating the modality of the biometric information of the input target is displayed).
[0088] When the input of the face image is completed on the identity verification screen (603), the processing of steps S303 to S312 is executed, that is, authentication between the registration terminal (200) and the PDS (400), and authentication between the registration terminal (200) and the issuing terminal (100) is executed, and the process transitions to the identity verification screen (604). On the identity verification screen (604), information indicating that authentication was successful and the name of the wallet are displayed. On the identity verification screen (604), if "Yes, I'm" is selected, the process transitions to the wallet menu selection screen (605).
[0089] In the wallet menu selection screen (605), if "Enrol a New Data" is selected, the processing of step S314 is initiated, and the system transitions to the data issuance request screen (606). In the data issuance request screen (606), a method for generating a data issuance request to be transmitted to the issuance terminal (100) (here, "Two-dimensional code" or "IC chip") is displayed. Additionally, in the data issuance request screen (606), if "complete" is selected, the system transitions to the encryption and PDS registration screen (609) described later (however, if the registration terminal (200) does not possess data, the system returns to, for example, the menu screen (502)).
[0090] In the data issuance request screen (606), if "Two-dimensional code" is selected, the process transitions to the data issuance screen (607), and the data issuance screen (607) displays a request to scan the two-dimensional code. Additionally, in the data issuance request screen (606), if "IC Chip" is selected, the data issuance screen (607) displays a request to execute reading of the IC chip. When the two-dimensional code is read by a camera or the like while the data issuance screen (607) is displayed, the processing of step S314 is completed, at least the processing of steps S319 and S312 is executed, and the process transitions to the data issuance confirmation screen (608).
[0091] On the data issuance confirmation screen (608), the issued data is displayed. If "Yes, I Confirmed" is selected on the data issuance confirmation screen (608), the system returns to the data issuance request screen (606). Additionally, if "No, Retry" is selected on the data issuance confirmation screen (608), the system returns to the data issuance request screen (606), for example, after the data is destroyed.
[0092] When "complete" is selected on the data issuance request screen (606), the process transitions to the encryption and PDS registration screen (609). On the encryption and PDS registration screen (609), an indication is displayed to determine whether to encrypt the issued data and transmit it to the PDS (400). When "Yes, I Confirmed" is selected on the encryption and PDS registration screen (609), the processing of steps S325 to S328 is performed, and the process transitions to the registration completion screen (610). When "No, I don't" is selected on the encryption and PDS registration screen (609), the process returns to, for example, the menu screen (502).
[0093] FIGS. 7a and 7b are explanatory diagrams illustrating an example of screen transitions of the output device (106) of the registered terminal (200) in data presentation processing. Transitions to the home screen (501), menu screen (502), identity authentication screen (603), identity verification screen (604), and wallet menu selection screen (605) are omitted from the description as they are the same as those in FIG. 6a.
[0094] In the wallet menu selection screen (605), if "Present Your Data" is selected, at least the processing of step S412 is executed, and the process transitions to the data index selection screen (706). On the data index selection screen (706), a list of data indices is displayed, and it is possible to select which data index corresponds to the data to be acquired. Here, in the data index selection screen (706) (i.e., in step S413), "Certificate of Testing for Covid-19" is selected as the data index, the processing of steps S414 to S416 is executed, and the process transitions to the data decryption screen (707).
[0095] In the data decoding screen (707), biometric information required to generate a key for decoding data is required (i.e., information indicating the modality of the required biometric information is displayed). Here, data is decoded by a key generated from the vein of one finger. When biometric information is acquired through the biometric information acquisition device (207) while the data decoding screen (707) is displayed, the processing of step S418 is executed, and the transition to the data presentation screen (708) is performed.
[0096] In the data presentation screen (708), decrypted data and decrypted electronic certificates are presented. For example, when the data presentation screen (708) is displayed and a predetermined amount of time has elapsed, the process transitions to the consent acquisition screen (709). In the consent acquisition screen (709), information regarding the purpose of use included in the decrypted data is displayed. In the consent acquisition screen (709), if "Yes, I do" is selected, the processing of steps S418 and S419 is executed, and the process transitions to the data transmission completion screen (710).
[0097] In the screen for obtaining consent (709), if "No, I don't" is selected, the system returns to, for example, the menu screen (502). In the data transmission completion screen (710), information indicating that data has been transmitted to the verification terminal (300) is displayed. In the data transmission completion screen (710), if "END" is selected, the system returns to the home screen (501).
[0098] Furthermore, the present invention is not limited to the embodiments described above and includes various modifications. For example, the embodiments described above are detailed to facilitate understanding of the present invention and are not limited to having all the described configurations. Additionally, it is possible to substitute a part of the configuration of one embodiment with a part of another embodiment, and it is also possible to add a part of another embodiment to a part of an embodiment. Furthermore, it is possible to add, delete, or substitute other configurations for a part of the configuration of each embodiment.
[0099] Furthermore, each of the above-mentioned components, functions, processing units, processing means, etc. may be realized in hardware by, for example, designing some or all of them as integrated circuits. Additionally, each of the above-mentioned components, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files that realize each function may be stored in memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.
[0100] Furthermore, control lines and information lines are indicated only as deemed necessary for illustrative purposes, and it cannot be said that all control or information lines are necessarily shown on the product. In reality, it can be assumed that almost all components are interconnected.
Claims
Claim 1 A data management system comprising a first calculator, a second calculator, and a third calculator, wherein the first calculator generates a secret key from biometric information of a user of the first calculator, the second calculator possesses a public key corresponding to the secret key, encrypted data which is data encrypted based on the public key, a list of indices indicating the type of the data, and an index of the encrypted data, and transmits the list to the first calculator, wherein the first calculator designates an index of the data to be presented which is an index included in the list, and transmits the designated index to the second calculator, wherein the second calculator transmits encrypted data corresponding to the index transmitted by the first calculator to the first calculator, and the first calculator decrypts the encrypted data corresponding to the index based on the secret key and transmits it to the third calculator. Claim 2 A data management system according to claim 1, wherein the second calculator holds the public key, and the first calculator uses the secret key and the second calculator uses the public key to perform authentication between the first calculator and the second calculator, and when the authentication is successful, the second calculator transmits the list to the first calculator. Claim 3 A data management system according to claim 1, wherein the third calculator holds the public key, the first calculator holds the consent information for the provision of the data, assigns an electronic signature to the consent information for the provision using the secret key, transmits the consent information for the provision with the electronic signature assigned to the third calculator, and the third calculator verifies the electronic signature using the public key. Claim 4 A data management system according to claim 1, comprising a fourth calculator, wherein the first calculator generates a common key from the biometric information, the fourth calculator retains the original data prior to encryption of the encrypted data and transmits the original data to the first calculator, and the encrypted data retained by the second calculator is the data transmitted to the second calculator by the first calculator after encrypting the original data based on the common key. Claim 5 A data management system according to claim 4, wherein the first calculator has a biometric information acquisition device and is connected to a display device, the encrypted data held by the second calculator includes an encrypted electronic certificate in which an electronic certificate by the fourth calculator is encrypted based on the public key, the first calculator displays information indicating the modality of the biometric information on the display device, acquires biometric information through the biometric information acquisition device, generates the secret key from the acquired biometric information, decrypts the encrypted electronic certificate included in the encrypted data corresponding to the index based on the secret key, transmits it to the third calculator, and displays the decrypted data and the decrypted electronic certificate on the display device. Claim 6 A data management system according to claim 1, comprising a fourth calculator, wherein the fourth calculator holds the original data prior to encryption of the encrypted data and the public key, and the encrypted data held by the second calculator is data transmitted to the second calculator by the fourth calculator after encrypting the original data based on the public key. Claim 7 A data management system according to claim 6, wherein the first calculator has a biometric information acquisition device and is connected to a display device, the encrypted data held by the second calculator includes an encrypted electronic certificate in which an electronic certificate by the fourth calculator is encrypted based on the public key, the first calculator displays information indicating the modality of the biometric information on the display device, acquires biometric information through the biometric information acquisition device, generates the secret key from the acquired biometric information, decrypts the encrypted electronic certificate included in the encrypted data corresponding to the index based on the secret key, transmits it to the third calculator, and displays the decrypted data and the decrypted electronic certificate on the display device. Claim 8 A data management system according to claim 6, wherein the second calculator holds a public key certificate including the public key and transmits the public key certificate to the first calculator, and the public key held by the fourth calculator is the public key included in the public key certificate transmitted by the first calculator to the fourth calculator, and the first calculator uses the secret key and the fourth calculator uses the public key certificate to perform authentication between the first calculator and the fourth calculator. Claim 9 A data management system according to claim 8, wherein the first calculator uses the secret key and the second calculator uses the public key certificate to perform authentication between the first calculator and the second calculator, and if the authentication is successful, the second calculator transmits the public key certificate to the first calculator. Claim 10 A data management method by a data management system comprising a first calculator, a second calculator, and a third calculator, wherein the first calculator generates a secret key from biometric information of a user of the first calculator - the second calculator possesses a public key corresponding to the secret key, encrypted data which is data encrypted based on the public key, a list of indices indicating the type of the data, and an index of the encrypted data -; the first calculator transmits the list to the first calculator after generating the secret key; the first calculator designates a data index of a presenting target which is an index included in the list received from the second calculator, and transmits the designated index to the second calculator; the second calculator transmits encrypted data corresponding to the index transmitted by the first calculator to the first calculator; and the first calculator decrypts the encrypted data corresponding to the index received from the second calculator based on the secret key and transmits it to the third calculator. Claim 11 A computer-readable, non-transient recording medium having a data management program for executing data management in a data management system comprising a first calculator, a second calculator, and a third calculator, wherein the data management program executes a process to generate a secret key from biometric information of a user of the first calculator on the first calculator, the second calculator possesses a public key corresponding to the secret key, encrypted data which is data encrypted based on the public key, a list of indices indicating the type of the data, and an index of the encrypted data, and the data management program executes a process to transmit the list to the first calculator on the second calculator, a process to specify a data index of a presenting target which is an index included in the list on the first calculator, and to transmit the specified index to the second calculator, a process to transmit encrypted data corresponding to the index transmitted by the first calculator to the first calculator, and a process to decrypt the encrypted data corresponding to the index transmitted by the first calculator on the first calculator based on the secret key and transmit it to the third calculator.
Citation Information
Patent Citations
Information processing system, information processor and method, program, and recording medium
JP2007058532A
System, device, method and program for authenticating communication partner by means of electronic certificate including personal information
KR1020090075705A
Mobile system, service system and service providing method for securely transmitting private information for use in service
KR1020100067267A
Systems and methods for biometric key generation in data access control, data verification, and path selection in block chain-linked workforce data management
US10530577B1
