Information processing device, information processing method, information processing system, and program

Abstract

To enable the automatic retrieval of data requiring user authentication based on the user's biometric information. [Solution] The biometric information management unit acquires the user's biometric information and transmits it to the service access management unit. Based on the user's biometric information, the service access management unit determines whether the user is unwell and displays an access consent request screen to the screen display unit, asking for consent to make a reservation to use the service provider server. If the service access management unit obtains a consent result from the screen display unit indicating consent to access to the service provider server, it sends a request to the credential management unit to acquire the authentication credentials necessary to access the service provider server specified in the automatically acquired credential table.

Description

Technical Field

[0001] The present disclosure relates to information processing technology for managing highly confidential data.

Background Art

[0002] In recent years, systems that provide software functions via the Internet, called cloud services, have been increasing. Some of them provide functions such as online storage, accounting systems, learning management systems, and online medical consultations. Cloud services provide specific functions to users by the cooperation of a server that provides the service (service-providing server) and an information terminal (e.g., desktop PC, tablet terminal, wearable device, smartphone, image forming apparatus, etc.). Furthermore, the cases where multiple cloud services cooperate to provide functions are also increasing.

[0003] Generally, in scenarios where information terminals or cloud services are used, user authentication using information including a user ID and password (generally called "credentials") is performed to prevent unauthorized use and identify users. And when the service-providing server and the information terminal cooperate or when cloud services cooperate with each other, the input of the above information for user authentication is required each time, and complicated input operations may be necessary.

[0004] By the way, in recent years, technologies have also been proposed that automatically execute predetermined processing in conjunction with sensors such as wearable devices. In Patent Document 1, a technology is disclosed in which when a wearable device detects a signal indicating a user's fall, the wearable device automatically transmits a request to notify a predetermined contact to a communication device.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

[0006] Let's consider a case where a user makes a medical appointment using a cloud service. Cloud-based medical appointment bookings require cumbersome input operations because they handle personal information protected by user authentication processes for user authentication and other purposes. Therefore, if a user's health deteriorates severely, they may not be able to perform the input operations for making a medical appointment. Thus, it is conceivable that a wearable device could use the technology described in Patent Document 1 above to make a medical appointment on behalf of the user in response to the device detecting an abnormality in the user. However, conventionally, it has not been possible to read personal information protected by user authentication processes without requiring user authentication, so information terminals have not been able to automatically make medical appointments using personal information. [Means for solving the problem]

[0007] This disclosure comprises: acquisition means for acquiring a user's biometric information; management means for managing permission to read data stored in a predetermined storage means, which the user uses when using a cloud service, through a first authentication process that authenticates the user based on user input; and reading means for reading the permitted data from the predetermined storage means, wherein the management means permits reading the data from the predetermined storage means without performing the first authentication process if the biometric information satisfies predetermined conditions. [Effects of the Invention]

[0008] According to this disclosure, it becomes possible to automatically read data that requires user authentication based on the user's biometric information. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram showing the configuration of the information processing system according to Embodiment 1. [Figure 2] This is a hardware configuration diagram of each device according to Embodiment 1. [Figure 3] This is a modular configuration diagram of each device according to Embodiment 1. [Figure 4] This is a flowchart illustrating the credential selection process according to Embodiment 1. [Figure 5] This is an example of a credential selection screen according to Embodiment 1. [Figure 6] This is a sequence diagram illustrating the emergency service access processing according to Embodiment 1. [Figure 7] This is a flowchart of the authentication credential acquisition process according to Embodiment 1. [Figure 8] This is a flowchart illustrating the user authentication process according to Embodiment 1. [Figure 9] This is a flowchart illustrating the process for obtaining authorization credentials according to Embodiment 1. [Figure 10] This is a flowchart illustrating the user authorization process according to Embodiment 1. [Figure 11] This is an example of the access consent request screen, authentication result, authorization verification result, and reservation result displayed on the screen display unit according to Embodiment 1. [Figure 12] This is an example of authentication credentials related to Embodiment 1. [Figure 13] This is an example of authorization credentials relating to Embodiment 1. [Figure 14] This is an example of an authorization result issued by the authorization server according to Embodiment 1. [Figure 15] This is a modular configuration diagram of each device according to Embodiment 2. [Figure 16] This is a flowchart illustrating the user authorization process according to Embodiment 2. [Figure 17] This is a flowchart illustrating the additional credential selection process according to Embodiment 2. [Figure 18]An example of a credential list and consent screen displayed on the screen display unit of the information processing terminal according to Embodiment 2. [Figure 19] A flowchart for explaining the additional acquisition process of authorization credentials according to Embodiment 2. [Figure 20] An example of a presentation request for public credentials issued by the authorization server according to Embodiment 2. [Figure 21] An example of a response to an additional request for credentials transmitted from the service - providing server according to Embodiment 2. [Figure 22] A module configuration diagram of each device according to Embodiment 3. [Figure 23] A flowchart for explaining the credential selection process according to Embodiment 3. [Figure 24] An example of a credential list and consent screen displayed on the screen display unit of the information processing terminal according to Embodiment 3. [Figure 25] A flowchart for explaining the authorization credential acquisition process according to Embodiment 3. [Figure 26] A configuration diagram of the information processing system in Embodiment 4. [Figure 27] A module configuration diagram of each device according to Embodiment 4. [Figure 28] A sequence diagram for explaining the emergency service access process according to Embodiment 4. [Figure 29] A flowchart for explaining the authentication credential acquisition process according to Embodiment 4. [Figure 30] A configuration diagram of the information processing system according to Embodiment 5. [Figure 31] A module configuration diagram of each device according to Embodiment 5. [Figure 32] A sequence diagram for explaining the emergency service access process according to Embodiment 5. [Figure 33] A flowchart for explaining the authentication credential acquisition process according to Embodiment 5. [Figure 34]This is a flowchart illustrating the process for obtaining authorization credentials related to Embodiment 5. [Figure 35] This is a flowchart illustrating the process for obtaining additional authorization credentials related to Embodiment 5. [Figure 36] This is a diagram showing the configuration of the information processing system according to Embodiment 6. [Figure 37] This is a modular configuration diagram of each device according to Embodiment 6. [Figure 38] This is a sequence diagram illustrating the emergency service access processing according to Embodiment 6. [Figure 39] This is a flowchart illustrating the authentication credential acquisition process according to Embodiment 6. [Modes for carrying out the invention]

[0010] The best mode for carrying out the present invention will be described below with reference to the drawings. (Embodiment 1) In this embodiment, when an information processing terminal such as a smartphone detects a user's poor health, it automatically acquires personal information managed by the information processing terminal and discloses a method for automatically requesting a service from a service provider server using an authentication and authorization flow for handling personal information.

[0011] <System Configuration> Figure 1 shows a diagram of the information processing system in an embodiment of the present invention. The information processing terminal 101 is an information processing terminal such as a smartphone and has the function of requesting the provision of services from the service provision server 102 that provides cloud services. The information processing terminal 101 also has authentication and authorization functions for authenticating users and is compatible with authentication and authorization processing to the service provision server 102. Authentication is the process of verifying the identity of the user and granting the user predetermined authority. In addition, the information processing terminal 101 has the function of managing credentials for personal information such as health insurance cards, and the function of managing the user's biometric information and detecting health problems.

[0012] The service provider server 102 is a service provider server and has the function of providing services in response to requests from the information processing terminal 101. In this embodiment, the function provided by the service provider server 102 is a medical appointment scheduling function at a clinic. The service provider server 102 also has the function of managing authentication processing with the authentication server 103 in response to authentication requests from the information processing terminal 101, and the function of managing authorization processing with the authorization server 104 in response to authorization requests from the information processing terminal 101.

[0013] When the authentication server 103 receives an authentication request from the information processing terminal 101 via the service provision server 102, it sends a challenge code (also simply called a challenge) to the information processing terminal 101 and receives a signed challenge code from the information processing terminal 101. The authentication server 103 also performs signature verification processing based on the signed challenge code received from the information processing terminal 101 via the service provision server 102 and sends the signature verification result to the information processing terminal 101. The signature verification processing is performed by sending a request to the public key management server 105 to obtain public key information, which is the public key, and is performed based on the obtained public key information. The authentication server 103 is in the same service domain as the service provision server 102 and may be configured to be managed on the same server as the service provision server 102.

[0014] When the authorization server 104 receives an authorization request from the information processing terminal 101 via the service provision server 102, it sends a request for presentation of public credentials to the information processing terminal 101 via the service provision server 102. The authorization server 104 also performs authorization verification processing based on the public credentials (VP), which are credentials intended for the disclosure of personal information to the service, received from the information processing terminal 101 via the service provision server 102. Public credentials are authorization credentials from which only the information necessary for authorization verification has been extracted. The authorization server 104 sends the authorization verification result to the information processing terminal 101 via the service provision server 102. In addition, when verifying public credentials, it sends a request to the public key management server 105 to obtain public key information and verifies the signature based on the obtained public key information. The authorization server 104 is in the same service domain as the service provision server 102 and may be managed on the same server as the service provision server 102.

[0015] The public key management server 105 manages public key information associated with the sender and issuer of credentials for information processing terminals 101, etc. Furthermore, when the public key management server 105 receives a public key information retrieval request from the authentication server 103 or authorization server 104, it retrieves the public key information corresponding to the identifier (such as the DID described later) included in the public key information retrieval request and sends it to the authentication server 103 or authorization server 104.

[0016] The information processing terminal 101 is connected to the global network 107 via the local network 106. The service provision server 102, authentication server 103, authorization server 104, and public key management server 105 are also connected via the global network 107. The local network 106 is implemented via a LAN or similar. The global network 107 is a communication network implemented via one or a combination of a WAN, telephone lines, dedicated digital lines, ATM or frame relay lines, cable television lines, wireless lines for data broadcasting, etc.

[0017] <Hardware Configuration> Figure 2(a) is a block diagram showing an example of the hardware configuration of an information processing terminal 101. Figure 2(b) is a block diagram showing an example of the hardware configuration of an information processing server consisting of a service provision server 102, an authentication server 103, an authorization server 104, and a public key management server 105.

[0018] The information processing terminal 101 is equipped with a CPU 201 that executes software stored on a hard disk drive (HDD) 203, which is a storage device. The CPU 201 comprehensively controls each piece of hardware connected to the system bus 204.

[0019] Memory 202 functions as the main memory, work area, etc., of the CPU 201. HDD 203 records data as a large-capacity storage device. UI control unit 206 controls input from input devices 207, such as a touch panel. Network control unit 208 exchanges data bidirectionally with other nodes via the network. Proximity communication IF 205 is a network interface for proximity communication such as NFC or Bluetooth, and communicates with other information processing devices and authentication terminals to exchange data. TPM 209 is a tamper-resistant storage device that prevents stored data from being read from the outside for the purpose of processing and holding confidential information, and stores biometric information used for authentication, or credentials such as secret keys corresponding to biometric information. In this embodiment, TPM 209 is a storage device built into the information processing terminal 101, but it may be replaced with cloud storage that ensures the desired tamper resistance. Biometric information sensor 210 is a sensor that observes the user's biometric information, such as the user's fingerprint, veins, voiceprint, iris, facial image, body temperature, and heart rate, and converts them into digital signals. The biometric information sensor 210 is implemented using dedicated observation devices such as fingerprint sensors, or general-purpose devices such as cameras and microphones capable of observing biometric information.

[0020] The information processing server includes a CPU 211 that executes software stored in a hard disk drive (HDD) 213, which is a storage device. The CPU 211 comprehensively controls each piece of hardware connected to the system bus 214. Memory 212 functions as the main memory, work area, etc., of the CPU 211. HDD 213 records data as a large-capacity storage device. Input control unit 215 controls input from an input device 216, such as a keyboard. Depending on the role of the information processing device, the configuration may not include the input control unit 215 and the input device 216. Display control unit 217 controls the display on a display device 218, such as a liquid crystal display. Depending on the role of the information processing device, the configuration may not include the display control unit 217 and the display device 218. Network control unit 219 exchanges data bidirectionally with other nodes via the network.

[0021] The information processing server may be implemented by an information processing device provided as a cloud computing service. Cloud computing includes serverless computing and virtual machines. In cloud computing, multiple hardware configurations as shown in Figure 2(b) are used. Alternatively, the service provision server 102, authentication server 103, authorization server 104, and public key management server 105 may each be implemented by a single information processing server.

[0022] <Functional Configuration> Figure 3 is a block diagram showing an example of the functional configuration of an information processing terminal 101, a service provision server 102, an authentication server 103, an authorization server 104, and a public key management server 105.

[0023] The information processing terminal 101 comprises a screen display unit 311, a credential management unit 312, and a health management client 313. The screen display unit 311 has the function of interpreting HTML, XML, etc., and displaying a screen. In this embodiment, the screen display unit 311 receives a screen display request from the service access management unit 315 of the health management client 313 and displays the screen. The credential management unit 312 has the function of managing credentials representing personal information held by the user. In this embodiment, authentication credentials are referred to as authentication credentials, and authorization credentials are referred to as authorization credentials. In this embodiment, the data format of authentication credentials conforms to DID (Decentralized Identifier), and the data format of authorization credentials conforms to VC (Verifiable Credentials). However, authentication credentials and authorization credentials may be credentials in a different format that handles personal information. Furthermore, the service access management unit 315 of the health management client 313 can be configured to automatically acquire credentials upon receiving a request from the user when they are unwell. The service access management unit 315 also transmits public credentials. The public credentials conform to the VP (Verifiable Presentation) specification, and only the attribute information required by the authorization server from the authorization credentials (VC) can be transmitted. However, in this embodiment, all information included in the authorization credentials (VC) is disclosed and transmitted to the authorization server.

[0024] Table 1 is an example of an authentication credential management table, which is managed by the credential management unit 312 for managing authentication credentials. The authentication credentials shown in Table 1 include at least an authentication credential identifier, a credential path, a secret key, and a client auto-acquisition flag. The authentication credential identifier is the identifier of the authentication credentials, the credential path is the path to the actual data of the authentication credentials, and the secret key is the secret key used during authentication. The client auto-acquisition flag indicates whether the service access management unit 315 of the health management client 313 can automatically acquire the credentials. If the client auto-acquisition flag is "TRUE", it indicates that the service access management unit 315 can automatically acquire the credentials, and if it is "FALSE", it indicates that the service access management unit 315 cannot automatically acquire the credentials.

[0025] [Table 1]

[0026] Figure 12 shows an example of authentication credentials (C00001) in this embodiment. In the authentication credentials, "@context" indicates the format of the authentication credentials to be used, "id" is the identifier of the authentication credentials, and "authentication" indicates the format of the public key.

[0027] Table 2 is an example of an authorization credential management table, which is managed by the credential management unit 312 and is used to manage authorization credentials. The authorization credentials shown in Table 2 include at least an authorization credential identifier, which is an identifier for the authorization credentials, a credential path, which indicates the path to the actual data of the authorization credentials, and a client automatic acquisition flag.

[0028] [Table 2]

[0029] Figure 13 shows an example of authorization credentials (V00001~V00004). In the authorization credentials, "_sd" represents serialized personal information. In this embodiment, the serialization format conforms to the SD-JWT (Selective-Disclosure Json Web Token) specification. Since SD-JWT is a publicly known technology published in draft-ietf-oauth-selective-disclosure-jwt-10, a detailed explanation is omitted. In the authorization credentials, "issuer" indicates the issuer of the authorization credentials. "validFrom" indicates the date and time of issuance of the authorization credentials, "validUntil" indicates the expiration date of the authorization credentials, and "@context" indicates the format of the authorization credentials. "credentialSubject" indicates the information of the issued authorization credentials, and "_sd_alg" indicates the encryption format of the personal information.

[0030] The health management client 313 comprises a biometric information management unit 314 and a service access management unit 315. The biometric information management unit 314 manages biometric information. The biometric information management unit 314 collects biometric information obtained from the user, and if the value of the collected biometric information exceeds a threshold, it sends alarm information, which is a message notifying the service access management unit 315 of the threshold exceedance. An example of the alarm information that the biometric information management unit 314 sends to the service access management unit 315 in this embodiment is shown below. The alarm information includes at least a category indicating the type of biometric information that has exceeded the threshold, and an observed value indicating the collected value. In this embodiment, the format of the alarm information is JSON (JavaScript Object Notation), but other data formats are also acceptable.

[0031] (Example of alarm information) {"Category":"Core Body Temperature", "Observed Value":39.5} Table 3 is an example of a threshold information table for managing biological information thresholds, which is managed by the biological information management unit 314. The threshold information includes at least a threshold value for each type of biological information to be acquired, and a category indicating the type of biological information.

[0032] [Table 3]

[0033] The service access management unit 315 cooperates with the service provision server 102. When the service access management unit 315 receives a threshold exceedance message from the biometric information management unit 314, it sends a service usage request to the service provision server 102. The service access management unit 315 can also send a request to the credential management unit 312 to obtain authentication credentials and authorization credentials, and obtain the authentication credentials and authorization credentials from the credential management unit 312. Based on the obtained authentication credentials and authorization credentials, the service access management unit 315 sends an authentication request and an authorization request to the service provision server 102. Furthermore, when the service access management unit 315 receives a threshold exceedance message from the biometric information management unit 314, it selects the authentication credentials and authorization credentials to obtain from the credential management unit 312 and executes the automatic acquisition settings. Table 4 is an example of an automatically acquired credential table, which is a table that manages the credentials to be acquired. The credentials to be acquired include, at a minimum, a credential identifier and a credential type for identifying the credentials. The service access management unit 315 also has an authentication credential acquisition flag, which indicates whether or not the acquisition of authentication credentials was successful. If the authentication credential acquisition flag is "TRUE", it indicates that the credentials were acquired successfully, and if it is "FALSE", it indicates that the acquisition of authentication credentials failed. In addition, the service access management unit 315 has an authentication success flag, which indicates that authentication was successful. If the authentication success flag is "TRUE", it indicates that authentication was successful, and if it is "FALSE", it indicates that authentication failed.

[0034] [Table 4] The service provision server 102 includes an authentication management unit 321, an authorization management unit 322, and a service provision unit 323. The authentication management unit 321 sends an authentication request to the authentication server 103 based on an authentication request from the information processing terminal 101. The authentication management unit 321 also sends the challenge code sent from the authentication server 103 to the information processing terminal 101. The authorization management unit 322 sends an authorization request to the authorization server 104 based on an authorization request from the information processing terminal 101. The authentication management unit 321 also sends a request to the information processing terminal 101 to present the public credentials sent from the authorization server 104. The service provision unit 323 performs reservation processing based on a service usage request sent from the information processing terminal 101 and sends the reservation result to the information processing terminal 101. Table 5 is an example of a reservation information table managed by the service provision unit 323 of the service provision server 102. The reservation information table includes at least a reservation availability date and time field, and a reserved flag indicating whether the time is already reserved. If the reserved flag is "TRUE", it indicates that the time is already reserved; if it is "FALSE", it indicates that the time is available for reservation.

[0035] [Table 5] The authentication server 103 includes an authentication credential verification unit 331. The authentication credential verification unit 331 creates a challenge code based on the authentication request sent from the service provider server 102 and sends it to the service provider server 102. The authentication credential verification unit 331 also performs authentication processing based on the authentication credentials and signature sent from the service provider server 102 and sends the authentication result to the service provider server 102. In addition, the authentication credential verification unit 331 sends a request to the public key management server 105 to obtain public key information based on the authentication credentials and verifies the signature based on the obtained public key information.

[0036] The authorization server 104 includes an authorization credential verification unit 341. Based on the authorization request sent from the service provider server 102, the authorization credential verification unit 341 creates a request for presentation of public credentials and sends it to the service provider server 102. The authorization credential verification unit 341 also performs authority verification processing based on the public credentials sent from the service provider server 102 and sends the verification result to the service provider server 102. In addition, based on the public credentials, the authorization credential verification unit 341 sends a request to obtain public key information corresponding to the public key management server 105 and verifies whether the public credentials are legitimate based on the obtained public key information. Furthermore, if the public credentials are legitimate, the authorization credential verification unit 341 performs authority verification processing based on the public credentials.

[0037] The public key management server 105 includes a public key management unit 351. When the public key management unit 351 receives a request to obtain public key information from the authentication server 103 or the authorization server 104, it transmits the requested public key information. Table 6 is an example of a public key management information table managed by the public key management unit 351. The public key management information includes at least a public key ID for identifying the public key and a credential path which is the path to the actual data of the public key. In this embodiment, the public key ID is the DID of the credential holder and the DID of the credential issuer.

[0038] [Table 6]

[0039] Furthermore, Figure 12 shows an example of authentication credentials associated with each public key ID managed under each credential path in this embodiment. In this embodiment, the data structure of the authentication credentials is assumed to be the same as that of the authentication credentials in the credential management unit 312 of the information processing terminal 101.

[0040] <Credential Selection Process> Figure 4 shows a flowchart illustrating the credential selection process performed in the information processing terminal 101 according to this embodiment. In order to automatically acquire the credentials associated with the user of the information processing terminal 101, it is necessary to verify whether or not the credentials can be acquired. This process executes a setting to automatically acquire the credentials of the user using the information processing terminal 101 only when an abnormality in the user is detected based on biometric information.

[0041] In S401, the service access management unit 315 obtains a list of credentials from the credential management unit 312 of the information processing terminal 101.

[0042] In S402, the service access management unit 315 sends a request to select credentials to be automatically acquired in an emergency based on user input. Based on the credential list acquired in S401, the service access management unit 315 sends a request to display the credential list to the screen display unit 311 of the information processing terminal 101. Upon receiving the request to display the credential list, the screen display unit 311 displays the credential list. Figure 5(a) is an example of the credential list displayed by the screen display unit 311 of the information processing terminal 101 in this embodiment. In this embodiment, only authorization credentials with “type” “hospital” are displayed from the authorization credentials shown in Figure 13. Based on the user's credential selection received by the screen display unit 311 of the information processing terminal 101, the service access management unit 315 determines the credentials to be acquired in an emergency.

[0043] In S403, the service access management unit 315 sends a consent request for credentials to be obtained in an emergency. From the acquired list of credentials, the service access management unit 315 identifies the authentication credentials (C00001 in this embodiment) associated with the authorization credentials based on the DID included in the “issuer” of the credentials received from the user. Subsequently, the service access management unit 315 identifies the authorization credentials whose “type” is “medical”. Based on the identified list of credentials, the service access management unit 315 sends a request to display the consent request screen to the screen display unit 311 and accepts input from the user. Figure 5(b) shows an example of the consent screen displayed on the screen display unit 311 according to this embodiment.

[0044] In S404, the Service Access Management Unit 315 configures the automatic acquisition of credentials to be obtained in emergencies. The screen display unit 311 of the information processing terminal 101 receives input from the user and sends the consent result to the Service Access Management Unit 315. Upon receiving the consent result from the screen display unit 311, the Service Access Management Unit 315 sends a request to the Credential Management Unit 312 to update the client automatic acquisition flag of the credentials for which automatic acquisition consent has been obtained to "TRUE". In addition, the Service Access Management Unit 315 registers the credentials to be automatically acquired and terminates this process. Table 7 is an example of the updated authentication credential management table managed by the Credential Management Unit 312. Table 8 is an example of the updated authorization credential management table managed by the Credential Management Unit 312. Table 9 is an example of the updated automatically acquired credentials table managed by the Service Access Management Unit 315.

[0045] [Table 7]

[0046] [Table 8]

[0047] [Table 9] <Emergency Service Access Processing> Figure 6 is a sequence chart illustrating the emergency service access process according to this embodiment. This process involves the information processing terminal 101 detecting a user's poor health based on the user's biometric information and sending a service request to the service provision server 102.

[0048] At S601, the information processing terminal 101 performs the authentication credential acquisition process. Details of the authentication credential acquisition process will be described later using Figure 7.

[0049] In S602, the information processing terminal 101, service provision server 102, authentication server 103, and public key management server 105 perform user authentication processing. Details of the user authentication processing will be described later using Figure 8.

[0050] In S603, the information processing terminal 101 performs the authorization credential acquisition process. Details of the authorization credential acquisition process will be described later using Figure 9.

[0051] In S604, the information processing terminal 101, service provision server 102, authorization server 104, and public key management server 105 perform user authorization processing. Details of the user authorization processing will be described later using Figure 10.

[0052] At S605, the service access management unit 315 of the information processing terminal 101 sends a user's service request to the service provision server 102.

[0053] In S606, the service provider server 102 performs service reservation processing based on the user authentication and authorization results associated with the service request. The service provider unit 323 of the service provider server 102 searches the reservation information table, retrieves one reservation with a reserved flag of "FALSE", and sets the reserved flag to "TRUE" as shown in Table 10.

[0054] [Table 10] In S607, the service provision unit 323 of the service provision server 102 transmits the reservation result to the information processing terminal 101. The service access management unit 315 of the information processing terminal 101 transmits a request to display the reservation result to the screen display unit 311, and the screen display unit 311 displays the reservation result and terminates this process. Figure 11(d) shows an example of the reservation result displayed on the screen display unit 311 of the information processing terminal 101 in this embodiment.

[0055] <Authentication credential acquisition process (S601)> Figure 7 shows a flowchart illustrating the authentication credential acquisition process according to this embodiment. This process acquires the biometric information of the user using the information processing terminal 101 and determines whether or not the information processing terminal 101 automatically acquires the authentication credential.

[0056] In S701, the biometric information management unit 314 acquires the user's biometric information, and in this embodiment, core body temperature, and transmits the biometric information to the service access management unit 315.

[0057] In S702, the service access management unit 315 determines whether the user is unwell based on the user's biometric information. In this embodiment, whether the user is unwell is determined by whether the observed values ​​of the biometric information, such as whether the core body temperature is above a predetermined threshold, meet predetermined conditions. If unwellness is detected, the process proceeds to S703; otherwise, it returns to S701.

[0058] In S703, the service access management unit 315 displays an access consent request screen to the screen display unit 311, requesting consent to make a reservation for use with the service provision server 102. The biometric information management unit 314 sends an alarm message indicating poor health to the service access management unit 315. Upon receiving the alarm message, the service access management unit 315 sends a request to the screen display unit 311 to display the access consent request screen for the service provision server 102, causing the screen display unit 311 to display the access consent request screen. Figure 11(a) shows an example of the access consent request displayed by the screen display unit 311 of the information processing terminal 101 in this embodiment.

[0059] In S704, the service access management unit 315 obtains the consent result from the screen display unit 311. When the screen display unit 311 receives input from the user regarding the access consent request, the screen display unit 311 sends the input result to the service access management unit 315. If the service access management unit 315 obtains the input result sent from the screen display unit 311, the process proceeds to S705. Otherwise, the service access management unit 315 repeatedly executes S704 at predetermined intervals until it obtains the input result from the screen display unit 311.

[0060] In S705, the service access management unit 315 determines whether the input result is consent to access to the service provider server 102. If it is consent to access to the service provider server 102, the process proceeds to S706; otherwise, this process ends.

[0061] In S706, the Service Access Management Unit 315 sends a request to the Credential Management Unit 312 to obtain the authentication credentials necessary to access the service provider server 102 specified in the automatically acquired credentials table (Table 9). The Credential Management Unit 312 sends the requested authentication credentials to the Service Access Management Unit 315. In addition, the Service Access Management Unit 315 sets the authentication credential acquisition flag of the requested authentication credentials to "TRUE" and terminates this process.

[0062] <User authentication process (S602)> Figure 8 shows a flowchart illustrating the user authentication process according to this embodiment. This process is a user authentication process performed by the information processing terminal 101, the service provision server 102, the authentication server 103, and the public key management server 105 based on automatically acquired authentication credentials.

[0063] Figure 8(a) shows a flowchart illustrating the user authentication process performed by the information processing terminal 101.

[0064] In S801, the service access management unit 315 sends an authentication request based on the user's DID to the service provision server 102.

[0065] In S802, the service access management unit 315 determines whether it has received a challenge code from the service provision server 102. If a challenge code is obtained, it proceeds to S804; otherwise, it repeatedly executes S802 at predetermined intervals until a challenge code is received.

[0066] In S803, the Service Access Management Unit 315 sends a signature request to the Credential Management Unit 312. The Credential Management Unit 312 signs the received challenge code with its private key and sends the signature back to the Service Access Management Unit 315.

[0067] In S804, the service access management unit 315 sends a signed challenge code to the service provision server 102.

[0068] In S805, the service access management unit 315 determines whether or not it has received an authentication result from the service provision server 102. If an authentication result is received, it proceeds to S808; otherwise, it repeats S805 at predetermined intervals until an authentication result is received.

[0069] In S806, the service access management unit 315 sends a request to the screen display unit 311 to display the authentication result screen based on the received authentication result. If the authentication process is successful, the service access management unit 315 sets the authentication success flag in the automatically acquired credentials table to "TRUE" and terminates this process. In this embodiment, if user authentication is successful, no screen display is performed, and if authentication fails, the authentication result is displayed and this process terminates. Figure 11(b) shows an example of the authentication result display screen shown on the screen display unit 311 in this embodiment.

[0070] Figure 8(b) shows a flowchart illustrating the user authentication process performed by the service provider server 102.

[0071] In S821, when the authentication management unit 321 receives an authentication request from the information processing terminal 101, it sends the authentication request to the authentication server 103.

[0072] In S822, the authentication management unit 321 determines whether or not it has received a challenge code from the authentication server 103. If a challenge code is received, the process proceeds to S823; otherwise, S822 is repeated at predetermined intervals until a challenge code is received.

[0073] In S823, the authentication management unit 321 transmits the received challenge code to the information processing terminal 101.

[0074] In S824, the authentication management unit 321 determines whether or not it has received a signed challenge code from the information processing terminal 101. If a signed challenge code is received, the process proceeds to S825; otherwise, S824 is repeated at predetermined intervals until a signed challenge code is received.

[0075] In S825, the authentication management unit 321 sends the signed challenge code to the authentication server 103.

[0076] In S826, the authentication management unit 321 determines whether or not it has received an authentication result from the authentication server 103. If an authentication result is received, the process proceeds to S827; otherwise, S826 is repeated at predetermined intervals until an authentication result is received.

[0077] In S827, the authentication management unit 321 transmits the authentication result to the information processing terminal 101 and terminates this process.

[0078] Figure 8(c) shows a flowchart illustrating the user authentication process performed by the authentication server 103.

[0079] In S841, when the authentication credential verification unit 331 receives an authentication request from the service provision server 102, it issues a challenge code.

[0080] In S842, the authentication credential verification unit 331 sends the issued challenge code to the service provision server 102.

[0081] In S843, the authentication credential verification unit 331 determines whether or not it has received a signed challenge code from the service provider server 102. If it has received one, it proceeds to S844; otherwise, it repeats S843 at predetermined intervals until it receives a signed challenge code.

[0082] In S844, the authentication credential verification unit 331 sends a request to the public key management server 105 to retrieve public key information based on the DID of the holder and issuer of the authentication credentials included in the authentication request received in S841.

[0083] In S845, the authentication credential verification unit 331 determines whether or not it has received public key information from the public key management server 105. If public key information is received, the process proceeds to S846; otherwise, S845 is repeated at predetermined intervals until public key information is received.

[0084] In S846, the authentication credential verification unit 331 verifies the signature obtained in S823 based on the public key information obtained in S845.

[0085] In S847, the authentication credential verification unit 331 performs authentication processing based on the signature verification result, sends the authentication result to the service provider server 102, and terminates this process.

[0086] Figure 8(d) shows a flowchart illustrating the user authentication process performed by the public key management server 105.

[0087] In S861, when the public key management unit 351 receives a request to acquire public key information from the authentication server 103, it sends the public key information corresponding to the DID included in the request to the authentication server 103 and terminates this process. In this embodiment, the public key management unit 351 sends public key information in the public key management information table it manages, where the public key ID is "did:example:aaaaaaaabbbbccccdddd".

[0088] <Authorization Credential Acquisition Process (S603)> Figure 9 shows a flowchart illustrating the authorization credential acquisition process according to this embodiment. This process involves acquiring the biometric information of the user using the information processing terminal 101 and determining whether or not the information processing terminal 101 acquires authorization credential.

[0089] In S901, the service access management unit 315 determines whether authentication credentials were obtained when an abnormality in biometric information was detected. The authentication credentials acquisition flag is checked, and if it is "TRUE", the process proceeds to S902; otherwise, this process terminates.

[0090] In S902, the service access management unit 315 verifies that authentication using the acquired authentication credentials was successful during the user authentication process. It checks the authentication success flag, and if it is "TRUE", proceeds to S903; otherwise, terminates this process.

[0091] In S903, the Service Access Management Unit 315 sends a request to the Credential Management Unit 312 to retrieve all authorization credentials specified in the automatically retrieved credentials table. The Credential Management Unit 312 then sends the public credentials to the Service Access Management Unit 315 in a batch. In addition, the Service Access Management Unit 315 sets the authorization credential acquisition flag, which indicates that the acquisition of authorization credentials was successful, to "TRUE" and terminates this process.

[0092] <User authorization process (S604)> Figure 10 shows a flowchart illustrating the user authorization process according to this embodiment. In this process, the information processing terminal 101, service provision server 102, authorization server 104, and public key management server 105 perform authentication based on the automatically acquired authorization credentials.

[0093] Figure 10(a) shows a flowchart illustrating the user authorization process performed by the information processing terminal 101.

[0094] In S1001, the service access management unit 315 sends an authorization request to the service provision server 102.

[0095] In S1002, the service access management unit 315 determines whether it has received a request for public credentials from the service provision server 102. If it has received a request for public credentials, it proceeds to S1003; otherwise, it repeatedly executes S1002 at predetermined intervals until it receives a request for public credentials.

[0096] In S1003, the service access management unit 315 sends public credentials to the service provision server 102.

[0097] In S1004, the service access management unit 315 determines whether or not it has received the verification result of the public credentials from the service provision server 102. If it has received the verification result, it proceeds to S1005; otherwise, it repeats S1004 at predetermined intervals until it receives the verification result.

[0098] In S1005, the service access management unit 315 sends a request to the screen display unit 311 to display the authorization verification result screen based on the verification result of the received public credentials. If the authorization verification process is successful, the service access management unit 315 sets the authorization verification success flag, which is a flag indicating successful acquisition, to "TRUE" and terminates this process. In this embodiment, if the authorization verification process is successful, no screen display is performed. If the authorization verification process fails, the authorization verification result is displayed and this process terminates. Figure 11(c) shows an example of the authorization verification result displayed on the screen display unit 311 in this embodiment.

[0099] Figure 10(b) shows a flowchart illustrating the user authorization process performed by the service provider server 102.

[0100] In S1021, when the authorization management unit 322 receives an authorization request from the information processing terminal 101, it sends the authorization request to the authorization server 104.

[0101] In S1022, the authorization management unit 322 determines whether or not it has received a request from the authorization server 104 to present public credentials. If it has received a request to present public credentials, it proceeds to S1023; otherwise, it repeats S1022 at predetermined intervals until it receives a request to present public credentials.

[0102] In S1023, the authorization management unit 322 sends a request to the information processing terminal 101 to present the public credentials.

[0103] In S1024, the authorization management unit 322 determines whether or not it has received public credentials from the information processing terminal 101. If public credentials are received, the process proceeds to S1025; otherwise, S1024 is repeated at predetermined intervals until public credentials are received.

[0104] At S1025, the authorization management unit 322 sends the signature to the authorization server 104.

[0105] In S1026, the authorization management unit 322 determines whether or not it has obtained an authentication result from the authorization server 104. If an authentication result has been obtained, the process proceeds to S1027; otherwise, S1026 is repeated at predetermined intervals until an authentication result is obtained.

[0106] At S1027, the authorization management unit 322 transmits the authorization result to the information processing terminal 101 and terminates this process.

[0107] Figure 10(c) shows a flowchart illustrating the user authorization process performed by the authorization server 104.

[0108] At S1041, when the authorization credential verification unit 341 receives an authorization request from the service provider server 102, it issues a request for presentation of public credentials. Figure 20 shows an example of a request for presentation of public credentials issued by the authorization server 104. In this example, "client_id" and "response_url" indicate the endpoint to which the presentation request is sent, i.e., the service provider server 102. "response_type" indicates the format of the presentation request to be sent to the information processing terminal 101. Also, "presentation_definition" indicates the format of the authorization credentials to be requested. In the case of the request shown in Figure 20, the authorization credentials with "type" "hospital" and "medical" from the authorization credentials shown in Figure 13 are requested.

[0109] In S1042, the authorization credential verification unit 341 sends a request to the service provision server 102 to present the issued public credentials.

[0110] In S1043, the authorization credential verification unit 341 determines whether it has received public credentials from the service provider server 102. If public credentials are received, the process proceeds to S1044; otherwise, S1043 is repeated at predetermined intervals until they are received.

[0111] In S1044, the authorization credential verification unit 341 sends a request to the public key management server 105 to retrieve public key information based on the DID of the holder and issuer of the authorization credentials included in the authorization request received in S1041.

[0112] In S1045, the authorization credential verification unit 341 determines whether or not it has received public key information from the public key management server 105. If it has received it, it proceeds to S1046; otherwise, it repeatedly executes S1045 until it receives the information.

[0113] In S1046, the authorization credential verification unit 341 verifies the signature of the public credentials based on the public key information.

[0114] In S1047, the authorization credential verification unit 341 verifies the acquired public credentials. In this embodiment, it verifies that the public credentials for “name” are “X Clinic” and the public credentials for “name” are “Health Insurance Card”. If they are included, the verification is considered successful; otherwise, the verification is considered a failure.

[0115] At S1048, the authorization credential verification unit 341 sends the verification result and terminates the process. Figure 14 shows an example of an authorization result issued by the authorization server 104. In this embodiment, if the verification is successful, only the HTTP status code is returned, but it is also acceptable to issue an authorization token for access to the service provider server 102 and add it to the response body before returning it.

[0116] Figure 10(d) shows a flowchart illustrating the user authorization process performed by the public key management server 105.

[0117] In S1061, when the public key management unit 351 receives a request to acquire public key information from the authorization server 104, it sends the public key information to the authorization server 104 and terminates this process. In this embodiment, the public key management unit 351 sends public key information in bulk for public key IDs that match the DID of the issuer of authorization credentials whose "type" is "hospital" or "medical" in the public key management information table it manages. In the public key management information table shown in Table 6 and the authorization credentials shown in Figure 13, the following three public key IDs are sent in bulk in this embodiment.

[0118] ·“did:example:1111111112222ccccdddd” ·“did:example:1111111112222aaaadddd” ·“did:example:1111111112222dddddddd” (Embodiment 2) There are cases where additional personal information is required when using a service. For example, when receiving a detailed medical examination at a hospital, you may be asked to present your medical history in addition to your health insurance card and patient registration card. In this embodiment, we disclose a method for automatically executing an additional authorization flow when additional personal information is required at the request of the service provider during the authorization process, using the method disclosed in Embodiment 1.

[0119] <System Configuration> Since it is the same as Embodiment 1, the explanation will be omitted.

[0120] <Hardware Configuration> Since it is the same as Embodiment 1, the explanation will be omitted.

[0121] <Module Configuration> Figure 15 shows the module configuration diagrams of each device according to Embodiment 2.

[0122] The screen display unit 311, the credential management unit 312, and the biometric information management unit 314 of the health management client 313 in the information processing terminal 101 are the same as in Embodiment 1, so their description is omitted. In addition to the functions of the service access management unit 315 in Embodiment 1, the service access management unit 316 has the function of transmitting additional authorization credentials in response to an additional authorization credential request from the authorization server 104. In addition, it has the function of setting to transmit additional public credentials when it receives an additional authorization credential request from the authorization server 104. Table 11 is an example of an additional credential table managed by the service access management unit 316 of the information processing terminal 101. The credentials to be added have at least a credential identifier indicating the identifier of the credentials, a type indicating the type of credentials, and a name which is the name of the credentials.

[0123] [Table 11]

[0124] The authentication management unit 321 and the service provision unit 323 in the service provision server 102 are the same as in Embodiment 1, so their description is omitted. In addition to the functions of the authorization management unit 322 in Embodiment 1, the authorization management unit 324 has the function of receiving additional requests for presentation of public credentials from the authorization server 104 and transmitting the received additional requests for presentation of public credentials to the information processing terminal 101. In addition, the authorization management unit 324 receives that additional public credentials have been transmitted from the information processing terminal 101 and transmits this to the authorization server 104.

[0125] Since the authentication server 103 has the same configuration as in Embodiment 1, its description will be omitted.

[0126] In the authorization server 104, the authorization credential verification unit 342 has the function of transmitting additional authorization credential requests, in addition to the function of the authorization credential verification unit 341 in Embodiment 1. Furthermore, when the authorization credential verification unit 342 receives additional authorization credentials from the service provision server 102, it verifies the additional authorization credentials and transmits the verification result to the service provision server 102. In addition, the authorization credential verification unit 342 has the function of determining whether a user who has accessed the service has presented the data necessary for using the service. Table 12 is an example of a required information table, which is a table managed by the authorization credential verification unit 342 that manages the information necessary to use the service. The required information includes at least a user identifier that uniquely identifies the user and the type of required information. In this embodiment, the user is uniquely identified by their name, but the service may issue an identifier that uniquely identifies the user and use that as the user identifier. Also, in this embodiment, the data necessary for using the service is the public credentials "MedicalHistory".

[0127] [Table 12] <Credential Selection Process> Since it is the same as Embodiment 1, the explanation will be omitted.

[0128] <Additional credential selection process> Figure 17 shows a flowchart illustrating the additional credential selection process according to this embodiment. This process is executed by the information processing terminal 101 when it receives a request for additional authorization credentials.

[0129] In S1701, the service access management unit 316 of the information processing terminal 101 sends a request for bulk credential acquisition to the credential management unit 312 of the information processing terminal 101.

[0130] In S1702, the service access management unit 316 of the information processing terminal 101 sends a request to select credentials to be obtained when an additional request is made from the authorization server 104. Based on the credential list obtained in S1701, the service access management unit 316 sends a request to display the credential list to the screen display unit 311 of the information processing terminal 101. Upon receiving the request to display the credential list, the screen display unit 311 displays the credential list. Figure 18(a) is an example of the credential list displayed by the screen display unit 311 of the information processing terminal 101 in this embodiment. In this embodiment, only authorization credentials are displayed where "type" is "MedicalHistory" and the "id" of the credentials is linked to the authentication credentials to be obtained in an emergency (C00001 in this embodiment). Based on the user's credential selection received by the screen display unit 311 of the information processing terminal 101, the service access management unit 316 determines the credentials to be obtained in an emergency.

[0131] In S1703, the service access management unit 316 of the information processing terminal 101 sends a consent request for the credentials to be obtained when an additional request is made. The service access management unit 316 sends a request to display the consent request screen to the screen display unit 311 and accepts input from the user. Figure 18(b) is an example of the consent screen displayed on the screen display unit 311.

[0132] In S1704, the service access management unit 316 of the information processing terminal 101 sets up automatic acquisition of credentials to be acquired additionally upon request. The screen display unit of the information processing terminal 101 receives input from the user and sends the consent result to the service access management unit 316. When the service access management unit 316 receives the consent result from the screen display unit 311, it sends a request to the credential management unit 312 to update the client automatic acquisition flag for the relevant credentials to "TRUE". In addition, the service access management unit 316 registers the credentials to be automatically acquired and terminates this process. Table 13 is an example of the updated authorization credential management table managed by the credential management unit 312 of the information processing terminal 101. Table 14 is an example of the updated additional acquisition target credential table managed by the service access management unit 316 of the information processing terminal 101.

[0133] [Table 13]

[0134] [Table 14]

[0135] <Emergency Service Access Processing> Since it is the same as Embodiment 1, the explanation will be omitted.

[0136] <Authentication Credential Acquisition Process> Since it is the same as Embodiment 1, the explanation will be omitted.

[0137] <User Authentication Process> Since it is the same as Embodiment 1, the explanation will be omitted.

[0138] <Authorization Credential Acquisition Process> Since it is the same as Embodiment 1, the explanation will be omitted.

[0139] <User authorization process> Figure 16 shows a flowchart illustrating the user authorization process according to this embodiment. This process is similar to the user authorization process in Embodiment 1, but also includes the process in which the information processing terminal 101 sends additional public credentials in response to an additional authorization credential request from the authorization server 104.

[0140] Figure 16(a) shows a flowchart illustrating the user authorization process performed by the information processing terminal 101. Steps S1601 to S1604 are the same as steps S1001 to S1004 in Embodiment 1, so their explanation is omitted.

[0141] In S1605, the service access management unit 316 determines whether the response received from the service provider server 102 is a request for additional credentials. If it is a request for additional credentials, the process proceeds to S1606; otherwise, it proceeds to S1610. Figure 21 shows an example of a request for additional credentials sent from the service provider server 102. In the example shown in Figure 21, the "reason" is "missing_credentials" and it is labeled "additional_request," indicating that it is a request for additional credentials. The format of the request for additional credentials is the same as the request for public credentials shown in Figure 20. In the example shown in Figure 21, the request is for the addition of authorization credentials whose "type" is "MedicalHistory" from the authorization credentials shown in Figure 13.

[0142] In S1606, the service access management unit 316 executes the process of obtaining additional authorization credentials. Details of the process of obtaining additional authorization credentials will be described later using Figure 19.

[0143] In S1607, the service access management unit 316 determines whether or not additional authorization credentials have been obtained. If they have been obtained, the process proceeds to S1608; otherwise, it proceeds to S1610.

[0144] In S1608, the service access management unit 316 sends the acquired additional authorization credentials to the service provider server 102. The service access management unit 316 accesses the API provided by the service provider server 102, which is specified by the URL “response_url” included in the response to the additional credential request sent from the service provider server 102. The service access management unit 316 then sends the requested additional authorization credentials to the accessed API.

[0145] In S1609, the service access management unit 316 determines whether it has received an authorization result from the service provision server 102 based on the verification results of additional public credentials. If it has received one, it proceeds to S1610; otherwise, it repeats S1609 until it receives one.

[0146] Since S1610 is the same as S1008 in Embodiment 1, its explanation is omitted.

[0147] Figure 16(b) shows a flowchart illustrating the user authorization process performed by the service provider server 102. Steps S1621 to S1627 are the same as steps S1021 to S1027 in Embodiment 1, so their explanation is omitted.

[0148] In S1628, the authorization management unit 324 determines whether or not it has received additional public credentials from the information processing terminal 101. If it has received them, it proceeds to S10629; otherwise, it terminates this process.

[0149] In S1629, the authorization management unit 324 sends the received additional public credentials to the authorization server 104.

[0150] In S1630, the authorization management unit 324 determines whether it has received an authorization result from the authorization server 104 for the authorization request based on the verification results of additional public credentials. If it has received an authorization result, it proceeds to S1631; otherwise, it repeats S1630 at predetermined intervals until it receives an authorization result.

[0151] In S1631, the authorization management unit 324 transmits the received authorization result to the information processing terminal 101 and terminates this process.

[0152] Figure 16(c) shows a flowchart illustrating the user authorization process performed by the authorization server 104. Steps S1641 to S1647 are the same as steps S1041 to S1047 in Embodiment 1, so their explanation is omitted.

[0153] In S1648, the authorization credential verification unit 342 determines whether additional public credentials are required. In this embodiment, it determines whether the public credentials include medical history. First, the authorization credential verification unit 342 obtains the “FirstName” and “LastName” included in the public credentials transmitted from the information processing terminal 101 and creates a user identifier. In this embodiment, it is “TARO_EXAMPLE”. Next, the authorization credential verification unit 342 checks whether there is a credential in the required information table that corresponds to the user identifier created and whose type (in the example shown in Figure 13, “name”) is “medical history”. If it exists, this process is terminated; otherwise, the process proceeds to S1649.

[0154] In S1649, the authorization credential verification unit 342 sends a request for additional public credentials to the service provider server 102. The request for additional public credentials sent by the authorization credential verification unit 342 is the same as shown in Figure 21.

[0155] In S1650, the authorization credential verification unit 342 determines whether it has received additional public credentials from the service provider server 102. If it has received them, it proceeds to S1651; otherwise, it repeats S1650 at predetermined intervals until it obtains them.

[0156] In S1651, the authorization credential verification unit 342 sends a request to the public key management server 105 to retrieve public key information based on the issuer's DID included in the additional public credentials.

[0157] In S1652, the authorization credential verification unit 342 determines whether or not it has obtained public key information from the public key management server 105. If it has obtained it, it proceeds to S1653; otherwise, it repeats S1652 at predetermined intervals until it has obtained the information.

[0158] In S1653, the authorization credential verification unit 342 verifies the signature of the received additional public credentials based on the public key information.

[0159] In S1654, the authorization credential verification unit 342 verifies the additional public credentials. In this embodiment, it verifies that the additional public credentials include credentials where "name" is "medical history". If they do, the verification is considered successful; otherwise, the verification is considered a failure.

[0160] At S1655, the authorization credential verification unit 342 issues an authorization result for the authorization request based on the verification results of the additional public credentials and sends it to the service provider server 102, terminating this process. The format of the authorization result issued here is the same as in Figure 14.

[0161] Figure 16(d) shows a flowchart illustrating the user authorization process performed by the public key management server 105. S1661 is the same as S1061 in Embodiment 1, so its explanation is omitted.

[0162] In S1662, the public key management unit 351 determines whether or not it has received a request for additional public key information from the authorization server 104. If it has received the information, it proceeds to S1663; otherwise, this process terminates.

[0163] In S1663, the public key management unit 351 responds to the authorization server 104's request for additional public key information and sends the public key information to the authorization server 104, terminating this process. In this embodiment, the public key management unit 351 sends all public key information in a single batch, where the public key ID in the public key management information table it manages is "did:example:1111111112222aaaaaaaa".

[0164] <Additional Authorization Credential Acquisition Process (S1606)> Figure 19 shows a flowchart illustrating the process for acquiring additional authorization credentials according to this embodiment. This process involves the information processing terminal 101 acquiring additional public credentials in response to a request for additional authorization credentials from the authorization server 104.

[0165] In S1901, the service access management unit 316 determines whether or not it has received a request for additional authorization credentials. If it has received them, it proceeds to S1902; otherwise, it terminates this process.

[0166] In S1902, the service access management unit 316 checks whether it is authorized to obtain the additional requested credentials. The service access management unit 316 refers to the additional credential table it manages and obtains the credentials associated with the name of the credentials requested by the authorization server 104 (in this embodiment, "MedicalHistory"). If the acquisition is successful, the process proceeds to S1903; otherwise, this process terminates.

[0167] In S1903, the Service Access Management Unit 316 sends a request to the Credential Management Unit 312 to obtain additional credentials corresponding to the credential identifier. In response to the request, the Credential Management Unit 312 sends the public credentials "V00004" and terminates this process. (Embodiment 3) There are cases where it is desirable to automatically change the services used depending on the user's situation. Specifically, there are cases where it is desirable to change the hospital visited depending on the symptoms of the user's illness. In this embodiment, a method for changing the authorization credentials obtained depending on the user's symptoms of illness is disclosed, using the method disclosed in Embodiment 2.

[0168] <System Configuration> Since it is the same as Embodiment 2, the explanation will be omitted.

[0169] <Hardware Configuration> Since it is the same as Embodiment 2, the explanation will be omitted.

[0170] <Module Configuration> Figure 22 shows the module configuration diagrams of each device according to Embodiment 3.

[0171] In the information processing terminal 101, the screen display unit 311, the credential management unit 312, and the biometric information management unit 314 of the health management client 313 are the same as in Embodiment 2, so their description is omitted. The service access management unit 317 has the function of changing the credentials to be acquired for each type of biometric information included in the alarm information, in addition to the function of either the service access management unit 315 or 316 of Embodiments 1 and 2. Table 15 is an example of an automatically acquired credential table managed by the service access management unit 317. The credentials to be automatically acquired include the credential identifier and the credential type of Embodiment 2, as well as the biometric information type, which is the type of biometric information included in the alarm information.

[0172] Furthermore, the service access management unit 317 has an authorization credential acquisition flag, which indicates whether or not authorization credentials were successfully acquired. If the authorization credential acquisition flag is "TRUE", it indicates that authorization credentials were successfully acquired, and if it is "FALSE", it indicates that acquisition failed. In this embodiment, the biometric information type is set only once for each biometric information type, but the system may be configured to allow multiple biometric information types to be set and the biometric information type settings to be changed. The number of times credentials for each biometric information type have been set is managed by the credential setting flag for each biometric information type, and in this embodiment, it is managed by the core body temperature setting flag. If the core body temperature setting flag is "TRUE", it indicates that it has already been set, and if it is "FALSE", it indicates that it has not been set.

[0173] [Table 15]

[0174] The functional configurations of the service provider server 102, authentication server 103, authorization server 104, and public key management server 105 are the same as in Embodiments 1 and 2, so their explanation is omitted.

[0175] <Credential Selection Process> Figure 23 shows a flowchart illustrating the credential selection process according to this embodiment. In this process, similar to embodiments 1 and 2, the system automatically acquires the user's credentials for the information processing terminal 101 only when an abnormality in the user is detected based on biometric information. In this embodiment, the credentials to be automatically acquired are changed according to the type of biometric information in which the abnormality was detected.

[0176] Since S2301 is the same as S401 in Embodiment 1, its explanation is omitted.

[0177] In S2302, the service access management unit 317 of the information processing terminal 101 sends a request to select credentials to be acquired in an emergency for each biometric alarm. Based on the credential list acquired in S2301, the service access management unit 317 sends a request to display the credential list to the screen display unit 311 of the information processing terminal 101. Upon receiving the request to display the credential list, the screen display unit 311 displays the credential list. Figure 24(a) is an example of the credential list displayed by the screen display unit 311 of the information processing terminal 101 in this embodiment. In this embodiment, as shown in the example in Figure 13, only authorization credentials with “type” as “hospital” are displayed. Based on the user's credential selection received by the screen display unit 311 of the information processing terminal 101, the service access management unit 317 determines the credentials to be acquired in an emergency (in this embodiment, “V00002”).

[0178] In S2303, the service access management unit 317 of the information processing terminal 101 sends a consent request for credentials to be acquired in an emergency for each biometric information alarm. From the acquired list of credentials, the service access management unit 317 identifies the authentication credentials (C00001) linked to the authorization credentials based on the “issuer” of the emergency credentials (V00002) received from the user. Subsequently, the service access management unit 317 identifies the authorization credentials with “type” as “medical”. Based on the identified list of credentials, the service access management unit 317 sends a request to display the consent request screen to the screen display unit 311 and accepts input from the user. Figure 24(b) is an example of the consent screen displayed on the screen display unit 311.

[0179] In S2304, the service access management unit 317 of the information processing terminal 101 sets up automatic acquisition of credentials to be obtained in emergencies. The screen display unit of the information processing terminal 101 receives input from the user and sends the consent result to the service access management unit 317. When the service access management unit 317 receives the consent result from the screen display unit 311, it sends a request to the credential management unit 312 to update the client automatic acquisition flag of the credentials for which automatic acquisition consent has been obtained to "TRUE". The service access management unit 317 also sets the core body temperature setting flag to "TRUE", registers the credentials to be automatically acquired, and terminates this process. The updated authentication credential management table and authorization credential management table managed by the credential management unit 312 of the information processing terminal 101 are the same as in Tables 7 and 8 of Embodiment 2. Table 16 is an example of the updated automatically acquired credential table managed by the service access management unit 317 of the information processing terminal 101.

[0180] [Table 16] <Additional credential selection process> Since it is the same as Embodiments 1 and 2, the explanation will be omitted.

[0181] <Emergency Service Access Processing> Since it is the same as Embodiments 1 and 2, the explanation will be omitted.

[0182] <Authentication Credential Acquisition Process> Since it is the same as Embodiments 1 and 2, the explanation will be omitted.

[0183] <User Authentication Process> Since it is the same as Embodiments 1 and 2, the explanation will be omitted.

[0184] <Authorization Credential Acquisition Process> Figure 25 shows a flowchart illustrating the authorization credential acquisition process according to Embodiment 3. In this embodiment, in addition to the functions of Embodiment 2, there is a function to acquire credentials in response to alarm information. Figure 25 is a flowchart of the information processing terminal 101 in the authorization credential acquisition process.

[0185] Since sections S2501 to S2502 are the same as sections S901 to S902 in Embodiment 2, their explanation is omitted.

[0186] In S2503, the service access management unit 317 of the information processing terminal 101 sends a request to the credential management unit 312 to acquire a batch of authorization credentials specified in the automatically acquired credential table (Table 16) in response to the alarm information. In this embodiment, the biometric information used for the alarm information is "core body temperature". The credential management unit 312 sends the public credentials associated with the alarm to the service access management unit 317 in a batch. In addition, the service access management unit 317 sets the authorization credential acquisition flag to "TRUE" and terminates this process.

[0187] <User authorization process> Since it is the same as Embodiments 1 and 2, the explanation will be omitted.

[0188] <Processing for obtaining additional authorization credentials> Since it is the same as Embodiments 1 and 2, the explanation will be omitted. (Embodiment 4) In Embodiments 1 to 3, a single information processing terminal, such as a smartphone, was used for managing credentials, detecting anomalies in biometric information, and transmitting requests for service use. In this embodiment, a method is disclosed in which anomaly detection of biometric information is performed by a wearable device or the like, which is a separate information processing terminal from the one that manages credentials.

[0189] <System Configuration> Figure 26 shows the configuration diagram of the information processing system in Embodiment 4. The service provision server 102, authentication server 103, authorization server 104, public key management server 105, local network 106, and global network 107 are the same as in Embodiments 1 to 3, so their explanation is omitted.

[0190] The first information processing terminal 111 is an information processing terminal such as a smartphone. The information processing terminal 111 has the function of requesting services provided by the service provision server 102. In addition, the information processing terminal 111 has authentication and authorization functions for authenticating users and supports authentication and authorization processing to the service provision server 102. Furthermore, the information processing terminal 111 has the function of managing credentials for personal information such as health insurance cards. Moreover, it has the function of detecting information about poor health transmitted from the second information processing terminal 112, which will be described later.

[0191] The second information processing terminal 112 is an information processing terminal such as a wearable device or a smartphone. The second information processing terminal has the function of managing the user's biometric information, detecting health problems, and transmitting them to the first information processing terminal.

[0192] <Hardware Configuration> The hardware configurations of the service provision server 102, authentication server 103, authorization server 104, and public key management server 105 are the same as in Embodiment 3, so their description is omitted. Similarly, the hardware configurations of the first information processing terminal 111 and the second information processing terminal 112 are the same as those of the information processing terminal 101 in Embodiment 3, so their description is omitted.

[0193] <Module Configuration> Figure 27 shows the module configuration diagrams of each device according to Embodiment 4.

[0194] The screen display unit 311 and the credential management unit 312 in the first information processing terminal 111 are the same as those in the information processing terminal 101 of Embodiment 3, so their description is omitted. The service access management unit 318 of the health management client 313 has one of the functions of the service access management units 315 to 317 of Embodiments 1 to 3. Furthermore, the service access management unit 318 has the function of determining whether or not to acquire each credential based on the alarm information transmitted by the second information processing terminal 112. In this embodiment, the determination of credential acquisition is made based on the alarm information transmitted by the second information processing terminal 112. On the other hand, the service access management unit 318 may also be configured to manage the threshold information table held by the biometric information management unit 314 of Embodiments 1 to 3 and to perform a threshold exceedance determination.

[0195] The second information processing terminal 112 has a biometric information collection unit 319. In addition to the functions of the biometric information management unit 314 in Embodiments 1 to 3, the biometric information collection unit 319 has a function to transmit alarm information to the first information processing terminal 111. The alarm information in this embodiment is the same as the alarm information in Embodiments 1 to 3. In this embodiment, the biometric information collection unit 319 transmits alarm information only when a threshold is exceeded, but it is also possible to transmit alarm information to the first information processing terminal 111 when biometric information is collected, and the determination of whether the threshold has been exceeded is made by the first information processing terminal 111.

[0196] The configurations of the service provider server 102, authentication server 103, authorization server 104, and public key management server 105 are the same as in Embodiments 1 to 3, so their explanation is omitted.

[0197] <Credential Selection Process> Since it is the same as Embodiments 1 to 3, the explanation will be omitted.

[0198] <Additional credential selection process> Since it is the same as Embodiments 1 to 3, the explanation will be omitted.

[0199] <Emergency Service Access Processing> Figure 28 shows a sequence diagram illustrating the emergency service access processing according to Embodiment 4. In addition to the emergency service access processing of Embodiments 1 to 3, the processing for determining emergency service access between the first information processing terminal 111 and the second information processing terminal 112 is disclosed. Figure 28 shows the sequence in the first information processing terminal 111, the second information processing terminal 112, the service provision server 102, the authentication server 103, the authorization server 104, and the public key management server 105.

[0200] When this process is initiated, the authentication credential acquisition process is executed in S2801. Details of the authentication credential acquisition process will be described later using Figure 29.

[0201] Since sections S62802 to S2807 are the same as sections S602 to S607 in embodiments 1 to 3, their explanation is omitted.

[0202] <Authentication Credential Acquisition Process> Figure 29 shows a flowchart illustrating the authentication credential acquisition process according to this embodiment. This process involves acquiring the biometric information of the user using the second information processing terminal 112, and the first information processing terminal 111 determining whether or not to acquire the authentication credential. Figure 29 is a flowchart of the first information processing terminal 111 and the second information processing terminal 112 in the authentication credential acquisition process.

[0203] Figure 29(a) shows a flowchart illustrating the authentication credential acquisition process performed by the first information processing terminal 111. When this process begins, at S2901, the service access management unit 318 of the first information processing terminal 111 receives alarm information from the second information processing terminal 112.

[0204] Since sections S2902 to S2905 are the same as sections S703 to S706 in embodiments 1 to 3, their explanation is omitted.

[0205] Figure 29(b) shows a flowchart illustrating the authentication credential acquisition process performed by the second information processing terminal 112. Steps S2921 to S2922 in this process are the same as steps S701 to S702 in Embodiment 3, so their explanation is omitted.

[0206] At S2923, the biometric information collection unit 319 of the second information processing terminal 112 transmits alarm information to the first information processing terminal 111, and terminates this process.

[0207] <User Authentication Process> Since it is the same as Embodiments 1 to 3, the explanation will be omitted.

[0208] <Authorization Credential Acquisition Process> Since it is the same as Embodiments 1 to 3, the explanation will be omitted.

[0209] <User authorization process> Since it is the same as Embodiments 1 to 3, the explanation will be omitted.

[0210] <Processing for obtaining additional authorization credentials> Since it is the same as Embodiments 1 to 3, the explanation will be omitted. (Embodiment 5) In Embodiment 4, the detection of abnormalities in biometric information was performed by an information processing terminal such as a wearable device. In this embodiment, in addition to the detection of abnormalities in biometric information, the request for use of the service is performed by an information processing terminal such as a wearable device, and the management of credentials is performed by another information processing terminal such as a smartphone.

[0211] <System Configuration> Figure 30 shows a configuration diagram of the information processing system according to Embodiment 5. The service provision server 102, authentication server 103, authorization server 104, public key management server 105, local network 106, and global network 107 are the same as in Embodiments 1 to 4, so their explanation is omitted.

[0212] The first information processing terminal 113 is an information processing terminal such as a wearable device. The information processing terminal 113 has the function of requesting services provided by the service provision server 102. The information processing terminal 111 has authentication and authorization functions for authenticating users and is responsible for authentication and authorization processing to the service provision server 102. It has the function of managing the user's biometric information, detecting health problems, and transmitting them to the second information processing terminal 114, which will be described later.

[0213] The second information processing terminal 114 is an information processing terminal such as a wearable device or a smartphone. The second information processing terminal 114 has the function of managing credentials for personal information such as insurance cards. It also has the function of transmitting credentials in response to a request from the first information processing terminal 113.

[0214] <Hardware Configuration> Since it is the same as Embodiments 1 to 4, the explanation will be omitted.

[0215] <Module Configuration> Figure 31 shows the module configuration diagrams of each device according to Embodiment 5.

[0216] The screen display unit 311, credential management unit 312, and biometric information management unit 314 of the first information processing terminal 113 are the same as those in the information processing terminal 101 of Embodiments 1 to 4, so their description is omitted. The service access management unit 3110 of the health management client 313 has one of the functions of the service access management units 315 to 318 of Embodiments 1 to 4. Furthermore, the service access management unit 3110 has the function of sending a request to the second information processing terminal 114 to acquire credentials when it receives alarm information from the biometric information management unit 314.

[0217] The second information processing terminal 114 has a credential management unit 3111. In addition to the functions of the credential management unit 312 in Embodiments 1 to 4, the credential management unit 3111 has a function of receiving a credential acquisition request transmitted from the first information processing terminal 113 and transmitting the requested credential.

[0218] Since the configurations of the service providing server 102, the authentication server 103, the authorization server 104, and the public key management server 105 are the same as those in Embodiment 3, the description thereof is omitted.

[0219] <Credential Selection Process> Since it is the same as in Embodiments 1 to 4, the description thereof is omitted.

[0220] <Additional Credential Selection Process> Since it is the same as in Embodiments 1 to 4, the description thereof is omitted.

[0221] <Emergency Service Access Process> FIG. 32 shows a sequence diagram for explaining the emergency service access process according to Embodiment 5. In addition to the emergency service access process of Embodiment 3, a process for emergency service access determination between the first information processing terminal 113 and the second information processing terminal 114 is disclosed. FIG. 32 is a sequence among the first information processing terminal 113, the second information processing terminal 114, the service providing server 102, the authentication server 103, the authorization server 104, and the public key management server 105.

[0222] When this process is started, at S3201, an authentication credential acquisition process is executed. Details of the authentication credential acquisition process will be described later using FIG. 33.

[0223] Since S3202 is the same as S2802 in Embodiment 4, the description thereof is omitted.

[0224] At S3203, an authorization credential acquisition process is executed. The authorization credential acquisition process will be described later using FIG. 34.

[0225] Since S3204 to S3207 are the same as S2804 to S2807 in Embodiment 4, the description thereof will be omitted.

[0226] <Authentication Credential Acquisition Process> FIG. 33 shows a flowchart for explaining the authentication credential acquisition process according to Embodiment 5. This process is a process of acquiring the biometric information of the user who uses the first information processing terminal 113 and determining whether the first information processing terminal 113 acquires authentication credentials. When the first information processing terminal 113 acquires authentication credentials, the first information processing terminal 113 acquires the authentication credentials from the second information processing terminal 114.

[0227] FIG. 33(a) shows a flowchart for explaining the authentication credential acquisition process performed by the first information processing terminal 113. Since S3301 to S3305 are the same as S701 to S705 in Embodiments 1 to 3, the description thereof will be omitted.

[0228] At S3306, the service access management unit 3110 of the first information processing terminal 113 transmits a request for acquiring authentication credentials to the second information processing terminal 114.

[0229] At S3307, the service access management unit 3110 of the first information processing terminal 113 verifies that it has acquired the authentication credentials from the second information processing terminal 114. If acquired, this process ends; otherwise, S3307 is repeatedly executed at a predetermined interval until acquisition.

[0230] FIG. 33(b) shows a flowchart for explaining the authentication credential acquisition process performed by the second information processing terminal 114. When this process starts, at S3321, the credential management unit 3111 of the second information processing terminal 114 transmits the authentication credentials requested by the first information processing terminal 113, and this process ends.

[0231] <User Authentication Process> Since it is the same as in Embodiments 1 to 4, the description thereof will be omitted.

[0232] <Authorization Credential Acquisition Process> Figure 34 shows a flowchart illustrating the authorization credential acquisition process according to Embodiment 5. This process involves acquiring the biometric information of the user using the first information processing terminal 113, and the first information processing terminal 113 determining whether or not to acquire authorization credentials. If acquisition is deemed necessary, the first information processing terminal 113 acquires the authorization credentials from the second information processing terminal 114.

[0233] Figure 34(a) shows a flowchart illustrating the authorization credential acquisition process performed by the first information processing terminal 113. Steps S3401 to S3402 are the same as steps S904 to S905 in Embodiment 3, so their explanation is omitted.

[0234] S3403 indicates that the service access management unit 3110 of the first information processing terminal 113 transmits a request to the second information processing terminal 114 to obtain authorization credentials based on an anomaly in biometric information.

[0235] In S3404, the service access management unit 3110 of the first information processing terminal 113 determines whether it has obtained authorization credentials from the second information processing terminal 114. If authorization credentials have been obtained, this process is terminated; otherwise, S3404 is repeated at predetermined intervals until they are obtained.

[0236] Figure 34(b) shows a flowchart illustrating the authorization credential acquisition process performed by the second information processing terminal 114. When this process begins, at S3421, the credential management unit 3111 of the second information processing terminal 114 transmits the authorization credential requested from the first information processing terminal 113, and the process ends.

[0237] <User authorization process> Since it is the same as Embodiments 1 to 4, the explanation will be omitted.

[0238] <Processing for obtaining additional authorization credentials> FIG. 35 shows a flowchart for explaining the additional authorization credential acquisition process according to the present embodiment. This process discloses a process in which the first information processing terminal 113 acquires additional public credentials in response to a request for acquisition of additional authorization credentials from the authorization server 104. When acquiring, the first information processing terminal 113 acquires authorization credentials from the second information processing terminal 114.

[0239] FIG. 35(a) shows a flowchart for explaining the additional authorization credential acquisition process performed by the first information processing terminal 113. Since S3501 is the same process as S1901 in Embodiment 4, the description thereof is omitted.

[0240] In S3502, the service access management unit 3110 transmits a request for acquisition of additional credentials corresponding to the credential identifier to the second information processing terminal 114.

[0241] In S3503, the service access management unit 3110 verifies that additional authorization credentials have been acquired from the second information processing terminal 114. If acquired, this process ends; otherwise, S3503 is repeatedly executed at a predetermined interval until acquisition.

[0242] FIG. 35(b) shows a flowchart for explaining the additional authorization credential acquisition process performed by the second information processing terminal 114. Since S3521 is the same process as S1902 in Embodiment 4, the description thereof is omitted.

[0243] In S3522, the credential management unit 3111 acquires the authorization credentials requested from the first information processing terminal 113.

[0244] In S3523, the credential management unit 3111 transmits the authorization credentials requested from the first information processing terminal 113 and ends this process. (Embodiment 6) In embodiments 4 and 5, anomaly detection of biometric information was performed using an information processing terminal such as a wearable device. This embodiment discloses a method for managing biometric information on an external server and obtaining credentials and requesting access to a service based on a notification of a biometric anomaly transmitted from the external server.

[0245] <System Configuration> Figure 36 shows a configuration diagram of an information processing system according to an embodiment of the present invention. The first information processing terminal 111, service provision server 102, authentication server 103, authorization server 104, public key management server 105, local network 106, and global network 107 are the same as in Embodiments 1 to 5, so their description is omitted.

[0246] The second information processing terminal 115 is an information processing terminal such as a wearable device or a smartphone. The second information processing terminal 115 acquires the user's biometric information and transmits the biometric information to the biometric information management server 116. In addition, the second information processing terminal 115 transmits alarm information to the first information processing terminal 111 based on the biometric abnormality notification transmitted from the biometric information management server 116.

[0247] The biometric information management server 116 manages the user's biometric information. Based on the biometric information transmitted from the second information processing terminal 115, the biometric information management server 116 determines any abnormalities in the biometric information and sends an abnormality notification to the biometric information management server 116.

[0248] <Hardware Configuration> The hardware configurations of the first information processing terminal 111, the second information processing terminal 115, the service provision server 102, the authentication server 103, the authorization server 104, and the public key management server 105 are the same as in Embodiments 1 to 5, so their description is omitted. The hardware configuration of the biometric information management server 116 is the same as in Embodiments 1 to 5, the hardware configurations of the service provision server 102, the authentication server 103, the authorization server 104, and the public key management server 105, so their description is omitted.

[0249] <Module Configuration> Figure 37 shows the module configuration diagram of each device according to Embodiment 6.

[0250] The second information processing terminal 115 includes a biometric information collection unit 3112. In addition to the functions of the biometric information collection unit 319 in Embodiment 4, the biometric information collection unit 3112 has the function of transmitting biometric information to the biometric information management server 116. An example of the biometric information that the biometric information collection unit 3112 transmits to the biometric information management server 116 in this embodiment is shown below. The biometric information includes at least a category indicating the type of biometric information that has exceeded a threshold, and an observed value indicating the collected value. In this embodiment, the format of the alarm information is JSON (JavaScript Object Notation), but other data formats are also acceptable.

[0251] (An example of biometric information) {"Category":"Core Body Temperature", "Observed Value":39.5} Furthermore, when the biological information collection unit 3112 receives biological abnormality information, which is a message indicating a biological abnormality transmitted from the biological information management server 116, it transmits alarm information to the first information processing terminal 111.

[0252] The biometric information management server 116 includes a biometric information management unit 3113. The biometric information management unit 3113 manages a threshold information table that manages thresholds for biometric information. The threshold information is the same as in Embodiments 1 to 5. In addition, the biometric information transmitted from the second information processing terminal 115 is compared with the value of the threshold information corresponding to the category of the transmitted biometric information, and if the threshold is exceeded, biometric abnormality information, which is a notification of a biometric abnormality, is transmitted to the second information processing terminal 115. An example of biometric abnormality information in this embodiment is shown below. The biometric abnormality information includes at least a category indicating the type of biometric information that has exceeded the threshold. In this embodiment, the format of the alarm information is JSON (JavaScript Object Notation), but other data formats are also acceptable.

[0253] (An example of information about biological abnormalities) {"Category":"Creative Body Temperature"} The configuration of the first information processing terminal 111, service provision server 102, authentication server 103, authorization server 104, and public key management server 105 is the same as in Embodiments 1 to 5, so a description will be omitted.

[0254] <Credential Selection Process> Since it is the same as Embodiments 1 to 5, the explanation will be omitted.

[0255] <Additional credential selection process> Since it is the same as Embodiments 1 to 5, the explanation will be omitted.

[0256] <Emergency Service Access Processing> Figure 38 shows a sequence diagram illustrating the emergency service access processing according to Embodiment 6. In addition to the emergency service access processing of Embodiment 4, it discloses the processing for determining emergency service access between the first information processing terminal 111, the second information processing terminal 115, and the biometric information management server 116. Figure 38 shows the sequence in the first information processing terminal 113, the second information processing terminal 114, the service provision server 102, the authentication server 103, the authorization server 104, the public key management server 105, and the biometric information management server 116.

[0257] In S3801, the authentication credential acquisition process is executed. The authentication credential acquisition process will be explained later.

[0258] Since sections S3802 to S3807 are the same as sections S2802 to S2807 in Embodiment 4, their explanation is omitted.

[0259] <Authentication Credential Acquisition Process> Figure 39 shows a flowchart illustrating the authentication credential acquisition process according to this embodiment. This process acquires the biometric information of the user using the first information processing terminal 111, transmits it to the biometric information management server 116, and determines whether or not to acquire authentication credentials based on the biometric abnormality information transmitted by the biometric information management server 116. Figure 39 is a flowchart of the first information processing terminal 111, the second information processing terminal 115, and the biometric information management server 116 in the authentication credential acquisition process.

[0260] Figure 39(a) shows a flowchart illustrating the authentication credential acquisition process performed by the first information processing terminal 111. Steps S3901 to S3905 are the same as steps S2901 to S2905 in Embodiment 4, so their explanation is omitted.

[0261] Figure 39(b) shows a flowchart illustrating the authentication credential acquisition process performed by the second information processing terminal 115.

[0262] In S3921, the biometric information collection unit 3112 acquires the user's biometric information.

[0263] In S3922, the biometric information collection unit 3112 transmits biometric information to the biometric information management server 116.

[0264] In S3923, the biological information collection unit 3112 verifies whether it has received biological abnormality information from the biological information management server 116. If it has received the information, it proceeds to S3924; otherwise, this process terminates.

[0265] In S3924, the biometric information collection unit 3112 transmits alarm information associated with the acquired biometric information to the first information processing terminal 111, and terminates this process. The category of the alarm information corresponds to the category of the biometric information, and the value of the alarm information corresponds to the value of the biometric information.

[0266] Figure 39(c) shows a flowchart illustrating the authentication credential acquisition process performed by the biometric information management server 116.

[0267] In S3941, the biometric information management unit 3113 acquires biometric information received from the second information processing terminal 115.

[0268] In S3942, the biological information management unit 3113 checks whether the biological information exceeds a threshold. If it does, the process proceeds to S3943; otherwise, this process terminates.

[0269] At S3943, the biological information management unit 3113 transmits the biological abnormality information to the second information processing terminal 115, and terminates this process. The category of the biological abnormality information corresponds to the category of biological information that exceeds the threshold.

[0270] <User Authentication Process> Since it is the same as Embodiments 1 to 5, the explanation will be omitted.

[0271] <Authorization Credential Acquisition Process> Since it is the same as Embodiments 1 to 5, the explanation will be omitted.

[0272] <User authorization process> Since it is the same as Embodiments 1 to 5, the explanation will be omitted.

[0273] <Processing for obtaining additional authorization credentials> Since it is the same as Embodiments 1 to 5, the explanation will be omitted.

[0274] (Other examples) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions.

[0275] This disclosure includes the following configurations and methods: [Configuration 1] A means for acquiring the user's biometric information, A management means that manages permission to read data stored in a predetermined storage means, which the user uses when using the cloud service, by a first authentication process that authenticates the user based on user input, A reading means for reading the permitted data from the predetermined storage means, Equipped with, The management means, if the biometric information satisfies predetermined conditions, permits reading data from the predetermined storage means without performing the first authentication process. An information processing device characterized by the following: [Configuration 2] The aforementioned predetermined condition is that the observed value of the biological information exceeds a predetermined threshold. The information processing device according to configuration 1, characterized by the above. [Configuration 3] The data stored in the predetermined storage means includes the user's credentials used in a second authentication process for authenticating the user in a first external device providing cloud services, or in an authorization process for granting the user predetermined privileges. An information processing apparatus according to configuration 1 or 2, characterized by the above. [Structure 4] The management means permits the reading of predetermined credentials for each type of biometric information. The information processing apparatus according to configuration 3, characterized by the features described herein. [Composition 5] When the management means receives a request to add the credentials, it permits the reading of the requested credentials. The reading means reads the additional requested credentials that have been authorized to be read by the management means. The information processing apparatus according to configuration 3 or 4, characterized by the above. [Composition 6] The second authentication process or authorization process described above is a process related to making an appointment for a medical consultation at a clinic. An information processing apparatus according to any one of configurations 3 to 5, characterized by the above. [Composition 7] The predetermined storage means is a storage device provided by the information processing device. An information processing device according to any one of configurations 1 to 6. [Structure 8] The acquisition means includes an observation means for observing the user's biometric information, and acquires the biometric information from the observation means. An information processing device according to any one of configurations 1 to 7. [Composition 9] The acquisition means acquires the user's biometric information from the observation means, An information processing device according to any one of configurations 1 to 7. [Configuration 10] The reading means is a second external device equipped with the observation means, which transmits data from the predetermined storage means read to the second external device that makes a request to use the cloud service. The information processing apparatus according to configuration 9, characterized by the features described therein. [Composition 11] The acquisition means acquires the biological information from a third external device that manages the biological information. An information processing device according to any one of configurations 1 to 7. [Composition 12] The acquisition means acquires only the biological information that satisfies the predetermined conditions from the third external device. The information processing apparatus according to configuration 11, characterized by the features described above. [Composition 13] The management means receives from the third external device that the biological information meets predetermined conditions. The information processing apparatus described in configuration 11 or 12, characterized by the above. [Composition 14] The aforementioned biometric information includes at least one of the following: fingerprints, veins, voiceprints, irises, facial images, body temperature, core body temperature, and heart rate. An information processing device according to any one of configurations 1 to 13, characterized by the above. [Composition 15] An information processing system including an information processing terminal for managing credentials used by users when using cloud services and a service provision server that provides cloud services, The aforementioned information processing terminal is A means for acquiring the user's biometric information, A management means that manages permission to read data stored in a predetermined storage means, which the user uses when using the cloud service, by a first authentication process that authenticates the user based on user input, A reading means for reading the permitted data from the predetermined storage means, Equipped with, The management means permits reading data from the predetermined storage means without performing the first authentication process if the biometric information meets predetermined conditions. The service provider server performs authentication and authorization processing based on the credentials transmitted by the information processing terminal, and if the authentication and authorization processing are successful, provides the cloud service to the information processing terminal. An information processing system characterized by the following: [Composition 16] Steps to obtain the user's biometric information, The steps include: managing permission to read data stored in a predetermined storage means, which the user uses when using the cloud service, through a first authentication process that authenticates the user based on user input; The steps include reading the permitted data from the predetermined storage means, Equipped with, The aforementioned management step allows the reading of data from the predetermined storage means without performing the first authentication process if the biometric information meets predetermined conditions. An information processing method characterized by the following: [Composition 17] A program for causing a computer to function as an information processing device as described in any one of items 1 to 14.

Claims

1. A means for acquiring the user's biometric information, A management means that manages permission to read data stored in a predetermined storage means, which the user uses when using the cloud service, by a first authentication process that authenticates the user based on user input, A reading means for reading the permitted data from the predetermined storage means, Equipped with, The management means, when the biometric information satisfies predetermined conditions, permits reading data from the predetermined storage means without performing the first authentication process. An information processing device characterized by the following:

2. The aforementioned predetermined condition is that the observed value of the biological information exceeds a predetermined threshold. The information processing apparatus according to feature 1.

3. The data stored in the predetermined storage means includes the user's credentials used in a second authentication process for authenticating the user in a first external device providing cloud services, or in an authorization process for granting the user predetermined privileges. The information processing apparatus according to feature 1.

4. The management means permits the reading of predetermined credentials for each type of biometric information. The information processing apparatus according to claim 3.

5. When the management means receives a request to add the credentials, it permits the reading of the requested credentials. The reading means reads the additional requested credentials that have been authorized to be read by the management means. The information processing apparatus according to claim 3.

6. The second authentication process or authorization process described above is a process related to making an appointment for a medical consultation at a clinic. The information processing apparatus according to claim 3.

7. The predetermined storage means is a storage device provided by the information processing device. The information processing apparatus according to feature 1.

8. The acquisition means includes an observation means for observing the user's biometric information, and acquires the biometric information from the observation means. The information processing apparatus according to feature 1.

9. The acquisition means acquires the user's biometric information from the observation means, The information processing apparatus according to feature 1.

10. The reading means is a second external device equipped with the observation means, which transmits data from the predetermined storage means read to the second external device that makes a request to use the cloud service. The information processing apparatus according to feature 9.

11. The acquisition means acquires the biological information from a third external device that manages the biological information. The information processing apparatus according to feature 1.

12. The acquisition means acquires only the biological information that satisfies the predetermined conditions from the third external device. The information processing apparatus according to feature 11.

13. The management means receives from the third external device that the biological information meets predetermined conditions. The information processing apparatus according to feature 11.

14. The aforementioned biometric information includes at least one of the following: fingerprints, veins, voiceprints, irises, facial images, body temperature, core body temperature, and heart rate. The information processing apparatus according to feature 1.

15. An information processing system including an information processing terminal for managing credentials used by users when using cloud services and a service provision server that provides cloud services, The aforementioned information processing terminal is A means for acquiring the user's biometric information, A management means that manages permission to read data stored in a predetermined storage means, which the user uses when using the cloud service, by a first authentication process that authenticates the user based on user input, A reading means for reading the permitted data from the predetermined storage means, Equipped with, The management means permits reading data from the predetermined storage means without performing the first authentication process if the biometric information meets predetermined conditions. The service provider server performs authentication and authorization processing based on the credentials transmitted by the information processing terminal, and if the authentication and authorization processing are successful, provides the cloud service to the information processing terminal. An information processing system characterized by the following:

16. Steps to obtain the user's biometric information, The steps include: managing permission to read data stored in a predetermined storage means, which the user uses when using the cloud service, through a first authentication process that authenticates the user based on user input; The steps include reading the permitted data from the predetermined storage means, Equipped with, The aforementioned management step allows reading data from the predetermined storage means without performing the first authentication process if the biometric information meets predetermined conditions. An information processing method characterized by the following:

17. A program for causing a computer to function as an information processing device according to any one of claims 1 to 14.

Images