Terminal, system, method for controlling the terminal, and program

Abstract

This device provides a terminal that facilitates the system registration of information necessary for providing services using biometric authentication. [Solution] The terminal comprises an acquisition means and a transmission means. The acquisition means acquires business information necessary for the user to receive services using biometric authentication from an application installed on the device. The transmission means transmits a token registration request containing the acquired business information and the user's biometric information to the server device.

Description

Technical Field

[0001] The present invention relates to a terminal, a system, a method for controlling a terminal, and a storage medium.

Background Art

[0002] There are technologies related to biometric authentication and the provision of services using such biometric authentication.

[0003] For example, Patent Document 1 describes providing a system, a server device, an authentication method, and a storage medium that contribute to improving the accuracy of biometric authentication. The system of Patent Document 1 includes a server device and at least one authentication terminal. The server device stores by associating the ID of each of a plurality of users with biometric information. At least one authentication terminal holds an ID list that stores the IDs of at least one person staying in a predetermined area. When authentication of an authenticated person is required, at least one authentication terminal transmits an authentication request including the biometric information of the authenticated person and the ID list to the server device. The server device extracts the IDs included in the ID list from the IDs of each of the plurality of users, and performs biometric authentication using the biometric information corresponding to the extracted IDs and the biometric information included in the authentication request.

[0004] Patent Document 2 describes providing an authentication server that improves the convenience of users to whom points are given. The authentication server of Patent Document 2 includes a user registration unit, a point management unit, and a database. The user management unit acquires a first ID that uniquely determines a user and biometric information used for biometric authentication of the user. The point management unit manages a first point given to a user by a service provider who provides a service to the user using the result of biometric authentication and a second point given to the user by an online provider who provides an online service to the user. The database stores by associating the first ID, the biometric information, and the total value of the first and second points.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] Patent No. 7036300 [Patent Document 2] International Publication No. 2022 / 137954 [Overview of the project] [Problems that the invention aims to solve]

[0006] In the systems disclosed in Patent Documents 1 and 2, it is necessary to register the biometric information of users receiving services using biometric authentication, as well as information necessary for providing services using biometric information, on the server. The question then becomes how the server obtains the information necessary for providing services using biometric information.

[0007] For example, information necessary for providing biometric services includes information managed by airport operators (airport management companies) and airline systems (e.g., member IDs and boarding pass information). When a server retrieves this information from the airport operator's system, the airport operator's system must be able to handle the information provision. Here, the information necessary for providing biometric services is diverse, and changing the systems that hold each piece of information incurs significant costs. As a result, the widespread adoption of biometric authentication services is hindered.

[0008] The primary objective of this invention is to provide a terminal, a system, a terminal control method, and a storage medium that contribute to easily realizing the system registration of information necessary for providing services using biometric authentication. [Means for solving the problem]

[0009] According to a first aspect of the present invention, a terminal is provided that includes an acquisition means for acquiring business information necessary for a user to receive a service using biometric authentication from an application installed on the device, and a transmission means for transmitting a token registration request including the acquired business information and the user's biometric information to a server device.

[0010] A second aspect of the present invention provides a system comprising a server device and a terminal owned by a user, wherein the terminal obtains business information necessary for the user to receive services using biometric authentication from an application installed on the device, transmits a token registration request including the obtained business information and the user's biometric information to the server device, and the server device stores the user's biometric information and business information in association with each other in a first database upon receiving the token registration request.

[0011] A third aspect of the present invention provides a terminal control method that involves the terminal obtaining business information necessary for a user to receive a service using biometric authentication from an application installed on the terminal, and transmitting a token registration request including the obtained business information and the user's biometric information to a server device.

[0012] According to a fourth aspect of the present invention, a computer-readable storage medium is provided that stores a program for causing a computer installed in a terminal to perform the following: a process of obtaining business information necessary for a user to receive a service using biometric authentication from an application installed on the terminal; and a process of sending a token registration request including the obtained business information and the user's biometric information to a server device. [Effects of the Invention]

[0013] From each perspective of the present invention, a terminal, a system, a terminal control method, and a storage medium are provided that contribute to easily realizing the system registration of information necessary for providing services using biometric authentication. However, the effects of the present invention are not limited to those described above. The present invention may also produce other effects in lieu of or in conjunction with the effects described above. [Brief explanation of the drawing]

[0014] [Figure 1] Figure 1 is a diagram illustrating the outline of one embodiment. [Figure 2] Figure 2 is a flowchart for explaining the operation of an embodiment. [Figure 3] Figure 3 is a diagram showing an example of the schematic configuration of an information processing system according to the first embodiment. [Figure 4] Figure 4 is a diagram for explaining the operation of the information processing system according to the first embodiment. [Figure 5] Figure 5 is a diagram for explaining the applications installed on the terminal according to the first embodiment. [Figure 6] Figure 6 is a diagram showing an example of the display of the terminal according to the first embodiment. [Figure 7] Figure 7 is a diagram showing an example of the display of the terminal according to the first embodiment. [Figure 8] Figure 8 is a diagram for explaining the operation of the information processing system according to the first embodiment. [Figure 9] Figure 9 is a diagram for explaining the operation of the information processing system according to the first embodiment. [Figure 10] Figure 10 is a diagram showing an example of the processing configuration of the terminal according to the first embodiment. [Figure 11] Figure 11 is a flowchart showing an example of the operation of the token control unit according to the first embodiment. [Figure 12] Figure 12 is a diagram showing an example of the processing configuration of the airport terminal according to the first embodiment. [Figure 13] Figure 13 is a diagram showing an example of the display of the airport terminal according to the first embodiment. [Figure 14] Figure 14 is a diagram showing an example of the processing configuration of the server device according to the first embodiment. [Figure 15] Figure 15 is a diagram showing an example of the user management database according to the first embodiment. [Figure 16] Figure 16 is a flowchart showing an example of the operation of the token control unit according to the first embodiment. [Figure 17] Figure 17 is a flowchart showing an example of the operation of the authentication unit according to the first embodiment. [Figure 18] Figure 18 shows an example of table information according to the first embodiment. [Figure 19] Figure 19 shows an example of the processing configuration of an authentication terminal according to the first embodiment. [Figure 20] Figure 20 is a sequence diagram showing an example of the operation of the information processing system according to the first embodiment. [Figure 21] Figure 21 is a sequence diagram showing an example of the operation of the information processing system according to the first embodiment. [Figure 22] Figure 22 shows an example of the display of a terminal according to the second embodiment. [Figure 23] Figure 23 shows an example of an activity history management database according to the third embodiment. [Figure 24] Figure 24 shows an example of the processing configuration of a server device according to the third embodiment. [Figure 25] Figure 25 is a diagram showing an example of the hardware configuration of the terminal disclosed in this application. [Modes for carrying out the invention]

[0015] First, an overview of one embodiment will be described. The reference numerals in the drawings attached to this overview are provided for convenience as examples to aid understanding, and this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units, not hardware units. The connecting lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows schematically indicate the flow of the main signal (data) and do not exclude bidirectional flow. In this specification and in the drawings, elements that can be similarly described are given the same reference numerals to avoid redundant explanation.

[0016] A terminal 100 according to one embodiment includes an acquisition means 101 and a transmission means 102 (see Figure 1). The acquisition means 101 acquires business information necessary for a user to receive a service using biometric authentication from an application installed on the device (step S1 in Figure 2). The transmission means 102 transmits a token registration request, including the acquired business information and the user's biometric information, to the server device (step S2).

[0017] Terminal 100 obtains business information necessary to enjoy biometric authentication services from an application installed on its own device (smartphone). Terminal 100 transmits the obtained business information and the user's biometric information to the server device and requests token registration. By adopting this configuration, there is no need to transmit business information, which is centrally managed by the service provider's system, from that system to the server device. As a result, system registration of information necessary for providing biometric authentication services can be easily achieved without requiring significant changes to each service provider's system.

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

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

[0020] [System Configuration] Figure 3 is a diagram showing an example of the schematic configuration of an information processing system (authentication system) according to the first embodiment. The information processing system shown in Figure 3 includes a server device 10, a plurality of authentication terminals 20-1 to 20-4, and an airport terminal 30.

[0021] In the following explanation, unless there is a particular reason to distinguish between authentication terminals 20-1 to 20-4, they will simply be referred to as "authentication terminal 20".

[0022] Server device 10 is a device that provides services using biometric authentication to airport users. Server device 10 is operated by any organization. For example, airport companies, airlines, public institutions such as national and local governments, or private companies commissioned by airport companies or public institutions may operate server device 10.

[0023] The server device 10 may be installed within the airport or it may be installed in the cloud on the network.

[0024] The authentication terminal 20 is a terminal (touchpoint) that serves as an interface for users receiving services using biometric authentication. Service providers who offer biometric authentication services to users install authentication terminals 20 at various locations within the airport, according to the services they provide. Users receive biometric authentication services through the authentication terminal 20.

[0025] For example, authentication terminal 20-1 is a POS (Point of Sale) terminal installed in a shop or similar establishment. For example, an airport company installs authentication terminal 20-1 (POS terminal) in a shop or similar establishment. For example, the airport company provides its members (hereinafter also referred to as airport members) with a biometric authentication payment service via authentication terminal 20-1. For example, authentication terminal 20-1 performs controls related to facial recognition payments.

[0026] The authentication terminal 20-2 is, for example, a reception terminal installed in a lounge. For example, an airport company installs the authentication terminal 20-2 (reception terminal) at the entrance (reception) of a lounge. For example, the airport company grants its members (airport members) free use of the lounge. For example, the authentication terminal 20-2 notifies the staff waiting at the lounge reception whether or not the user identified by biometric authentication is eligible to use the lounge free of charge.

[0027] Authentication terminal 20-3 is, for example, a digital signage display installed in an airport lobby. For example, an airline installs authentication terminal 20-3 (digital signage) in its departure and arrival lobbies. For example, an airline provides various information to its members (hereinafter also referred to as airline members). For example, authentication terminal 20-3 guides users identified by biometric authentication to the location of their boarding gate or provides information about tourist attractions.

[0028] The authentication terminal 20-4 is, for example, a gate device installed at each boarding gate. For example, an airline installs the authentication terminal 20-4 (gate device). The authentication terminal 20-4 will refuse passage to a user if the user identified by biometric authentication is not qualified to board the aircraft.

[0029] Airport terminal 30 is a terminal installed within the airport. Users operate airport terminal 30 to perform check-in procedures, etc. Airport terminal 30 also has a function for registering user tokens. Specifically, airport terminal 30 requests user token registration (token issuance) from server device 10. Details regarding tokens will be described later.

[0030] The user possesses terminal 40. Terminal 40 has various applications installed. For example, terminal 40 has airport applications used by airport company members and airline applications used by airline members installed.

[0031] Users can enjoy various services and benefits provided by the airport company using the airport application. For example, users can use the airport application to make reservations at hotels partnered with the airport company, check flight information, etc. Alternatively, users can use the airport application to register their credit card information with the airport company's system. Users can then use their registered credit card information to make purchases (for example, online shopping).

[0032] Furthermore, users will use the airline application to purchase airline tickets, check in, and perform other procedures. For example, users will manage their boarding passes using the airline application.

[0033] Furthermore, terminal 40 is equipped with the aforementioned token registration function.

[0034] The devices included in the information processing system shown in Figure 3 (server device 10, authentication terminal 20, etc.) are configured to communicate with each other via a network. For example, the server device 10 and the authentication terminal 20 are connected by wired or wireless communication means and are configured to communicate with each other.

[0035] Figure 3 is illustrative and not intended to limit the configuration of the information provision system disclosed in this application. For example, the information processing system may include two or more server devices 10. Also, the number of authentication terminals 20 included in the information processing system is not limited to four. The information processing system only needs to include at least one authentication terminal 20.

[0036] Furthermore, the authentication terminal 20 shown in Figure 3 is an example and is not intended to limit the entity or purpose of installation of the authentication terminal 20. Airports may have authentication terminals 20 installed for purposes other than POS terminals, reception terminals, digital signage, and gate equipment. Alternatively, digital signage installed by airport companies and digital signage installed by airlines may be mixed.

[0037] [System Overview] Next, we will explain the general operation of the information processing system.

[0038] <Token Registration> As described above, airport terminals 30 and 40 are equipped with functions related to token registration.

[0039] A token is information necessary for the server device 10 to provide a service using biometric authentication to a user, and is registered in the system. Specifically, a token consists of a combination of the user's biometric information and business information, and is stored in the database of the server device 10.

[0040] Examples of biometric information include data (feature quantities) calculated from individual physical characteristics such as face, fingerprints, voiceprints, veins, retina, and iris patterns. Alternatively, biometric information may be image data such as face images or fingerprint images. Biometric information only needs to include information about the user's physical characteristics. This disclosure describes the case where biometric information related to a person's "face" (face image or feature quantities generated from a face image) is used.

[0041] Business information is the information necessary for service providers (e.g., airport companies, airlines) to provide services to users. Business information varies depending on the service provider and the type of service they provide.

[0042] For example, if a facial recognition payment service is provided to airport members, the airport company's member ID will be used as business information. In the following explanation, the airport company's member ID will be referred to as the "airport member ID." Alternatively, if a free lounge access service is provided to airport members, the airport member ID will also be used as business information.

[0043] Alternatively, if useful information is provided to airline members, the airline's member ID and boarding pass information will be considered business information. In the following explanation, the airline's member ID will be referred to as "airline member ID." Alternatively, when a user passes through authentication terminal 20-4 and boards an aircraft, the boarding pass information will be considered business information.

[0044] Before receiving biometric authentication services at the airport, users must register their tokens with the system. Specifically, users request token registration from the server device 10 using either an airport terminal 30 installed within the airport or a terminal 40 they possess.

[0045] First, we will explain the case where a user requests token registration from the server device 10 using the airport terminal 30.

[0046] When a user requests token registration (token issuance), the airport terminal 30 acquires the user's biometric information. For example, the airport terminal 30 takes a photograph of the user in front of it and acquires a facial image.

[0047] Furthermore, the airport terminal 30 acquires biometric information from the user's identification document. Specifically, the airport terminal 30 acquires facial images from identification documents equipped with IC (Integrated Circuit), such as passports, driver's licenses, and My Number cards.

[0048] Airport terminal 30 performs identity verification using biometric information obtained by photographing the user and biometric information obtained from an identification document. Airport terminal 30 performs identity verification (one-to-one authentication) using two biometric pieces of information (facial images).

[0049] If identity verification is successful, the airport terminal 30 acquires the business information necessary for providing services using biometric authentication. For example, the airport terminal 30 acquires from the user the airport company's membership information (airport member ID), the airline's membership information (e.g., airline member ID), and boarding pass information (information obtained from the boarding pass).

[0050] The airport terminal 30 sends a "token registration request" to the server device 10, which includes the user's biometric information (for example, a facial image obtained by taking a photograph or a facial image read from an identification document) and business information (see Figure 4).

[0051] Upon receiving a token registration request, the server device 10 registers (issues) a token using the biometric and business information included in the token registration request. The server device 10 registers the information (biometric and business information) obtained from the airport terminal 30 into the user management database. Details of the user management database in which the server device 10 stores tokens will be described later.

[0052] The server device 10 notifies the airport terminal 30 of the processing result for the token registration request. If token registration is successful, the server device 10 sends an affirmative response to the airport terminal 30. If token registration fails, the server device 10 sends a negative response to the airport terminal 30.

[0053] The airport terminal 30 notifies the user of the result of the token registration request.

[0054] Next, we will explain the case where a user requests token registration from the server device 10 using terminal 40.

[0055] As mentioned above, various applications are installed on the user's terminal 40. For example, the airport application and airline application mentioned above are installed on terminal 40.

[0056] Furthermore, the user installs an application on the terminal 40 to manage and control token registration. For example, the user downloads a token control application from an application store and installs it on the terminal 40.

[0057] For example, as shown in Figure 5, terminal 40 has various applications installed, such as a token control application, an airport application, and an airline application. The applications installed on terminal 40 are configured to send and receive data from each other.

[0058] Token control applications can interact with other applications. Specifically, token control applications can receive data from other applications and send data to other applications.

[0059] Here, the applications installed on terminal 40 store and manage the information necessary for their own execution. For example, an airport application manages and stores the user's airport membership ID. Alternatively, an airline application manages and stores the user's airline membership ID, boarding pass information, etc.

[0060] Airport applications, airline applications, etc., will send business information corresponding to the requested service to a token control application when a user wishes to enjoy services using biometric authentication. For example, if a user wishes to purchase goods using facial recognition at an airport shop, the airport application will send the airport member ID to the token control application.

[0061] Alternatively, if an airport application or airline application offers a biometric authentication service that can be suggested to the user, it will guide the user to that service. If the user wishes to use the suggested service, the airline application, etc., will send business information corresponding to the desired service to the token control application.

[0062] For example, an airline application might suggest using biometric authentication to pass through the gate after obtaining a boarding pass from the airline's system. The airport application would then inform the user that they can pass through the gate and board the aircraft without presenting any documents (or media), such as a boarding pass, to airline staff. In the following explanation, passing through the gate without presenting a boarding pass will be referred to as "face-based access." If the user accepts the suggestion, the airline application sends the boarding pass information to the token control application.

[0063] When the token control application retrieves business information from other applications (or receives push notifications from other applications), it obtains the user's biometric information. For example, the token control application takes a picture of the user, such as a selfie, and obtains the user's facial image.

[0064] Subsequently, the token control application obtains biometric information from the user's identification document. The token control application reads facial images from the IC chip of documents such as passports, driver's licenses, and My Number cards.

[0065] The token control application performs identity verification (one-to-one authentication) using two pieces of biometric information.

[0066] Once identity verification is successful, the token control application obtains consent to provide personal information to a third party (server device 10). For example, the token control application obtains the user's consent to provide personal information (biometric information and business information) to a third party using a GUI (Graphical User Interface) as shown in Figures 6 and 7.

[0067] Figure 6 shows an example of the GUI when the token control application obtains business information for facial recognition payment from the airport application. Figure 7 shows an example of the GUI when the token control application obtains business information for facial recognition access from the airline application.

[0068] Once the user's consent is obtained for the provision of biometric and business information to a third party, the token control application sends a "token registration request" containing the user's biometric and business information to the server device 10 (see Figure 8).

[0069] The server device 10 processes the token registration request received from terminal 40 in the same way as the token registration request received from airport terminal 30. The server device 10 notifies terminal 40 of the processing result of the token registration request (token registration successful, token registration failed). The server device 10 sends a response to the token registration request (affirmative response, negative response) to terminal 40.

[0070] Terminal 40 (token control application) notifies the user of the result of the token registration request.

[0071] In this manner, terminal 40 obtains the business information necessary for the user to receive services using biometric authentication from an application installed on its device. Terminal 40 sends a token registration request containing the obtained business information and the user's biometric information to server device 10. Upon receiving the token registration request, server device 10 stores the user's biometric information and business information in association with each other in the first database (user management database).

[0072] <Provision of Services> Users receive services using biometric authentication via the authentication terminal 20. Users who wish to enjoy services using biometric authentication move, for example, in front of the authentication terminal 20.

[0073] The authentication terminal 20 acquires the user's biometric information in response to an operation (instruction) by an employee of the service provider or the user. Alternatively, the authentication terminal 20 automatically acquires the biometric information of the user in front of it.

[0074] For example, if a user wishes to purchase goods using facial recognition payment, the authentication terminal 20-1 (POS terminal) will take a picture of the user and acquire a facial image in response to an operation by the store clerk or the user (the person purchasing the goods). Alternatively, if a user wishes to enter the lounge, the authentication terminal 20-2 (reception terminal) will take a picture of the user and acquire a facial image in response to an operation by a staff member waiting at the lounge reception.

[0075] Alternatively, when authentication terminal 20-3 (digital signage) or authentication terminal 20-4 (gate device) detects a user in front of its device, it takes a photograph of the user and acquires a facial image.

[0076] The authentication terminal 20 sends an "authentication request" containing the acquired biometric information and terminal ID to the server device 10 (see Figure 9).

[0077] The terminal ID is an ID used to identify the authentication terminal 20. The terminal ID can be the MAC (Media Access Control) address or IP (Internet Protocol) address of the authentication terminal 20.

[0078] The terminal ID is shared between the server device 10 and each authentication terminal 20 by any method. For example, the system administrator determines the terminal ID and sets the determined terminal ID on the server device 10. The system administrator also sets the determined terminal ID on each authentication terminal 20.

[0079] Upon receiving an authentication request, the server device 10 performs biometric authentication using the biometric information included in the authentication request and the biometric information registered in the user management database. The server device 10 then performs a matching process (one-to-many matching, where N is a positive integer; the same applies hereinafter) using this biometric information to identify the person to be authenticated.

[0080] Furthermore, the server device 10 identifies the authentication terminal 20 that sent the authentication request using the terminal ID included in the authentication request (identifies the type of authentication terminal 20). The server device 10 then sends business information corresponding to the identified authentication terminal 20 (business information of the authenticated person identified through the matching process) to the authentication terminal 20.

[0081] For example, when an authentication request is received from authentication terminal 20-1 (POS terminal) or authentication terminal 20-2 (reception terminal), the server device 10 notifies authentication terminal 20-1 of the airport company's airport member ID.

[0082] Alternatively, if an authentication request is received from authentication terminal 20-3 (digital signage), the server device 10 transmits the airline member ID or boarding pass information to authentication terminal 20-3. Alternatively, if an authentication request is received from authentication terminal 20-4 (gate device), the server device 10 notifies authentication terminal 20-4 of the boarding pass information, etc.

[0083] The server device 10 sends a response to the authentication request to the authentication terminal 20.

[0084] Specifically, if the matching process is successful and business information corresponding to the authentication terminal 20 is registered in the user management database, the server device 10 sends an affirmative response indicating successful authentication to the authentication terminal 20. More specifically, the server device 10 sends an affirmative response to the authentication terminal 20 that includes business information corresponding to the authentication terminal 20, which is the source of the authentication request.

[0085] If the matching process fails, or if the business information corresponding to the authentication terminal 20 is not registered in the user management database, the server device 10 sends a negative response indicating authentication failure to the authentication terminal 20.

[0086] If a negative response (authentication failure) is received, the authentication terminal 20 will notify the user or staff accordingly.

[0087] Upon receiving an affirmative response (successful authentication), the authentication terminal 20 provides services to the user using the business information obtained from the server device 10.

[0088] For example, the authentication terminal 20-1 (POS terminal) transmits the airport member ID and payment information (product name and purchase price of the product purchased by the user) obtained from the server device 10 to the airport company's system (not shown). The airport company's system (a system that provides various services to its members) identifies the product purchaser using the airport member ID and processes the payment using the identified product purchaser's credit card information and payment information.

[0089] Alternatively, the authentication terminal 20-2 (reception terminal) transmits the airport member ID obtained from the server device 10 to the airport company system. The airport company system transmits the member information (e.g., member's name, etc.) stored in association with the airport member ID to the authentication terminal 20-2. The authentication terminal 20-2 notifies the staff, etc., that the authenticated person is a member of the airport company, along with the acquired member information. The staff then authorizes the authenticated person to use the lounge free of charge.

[0090] Alternatively, the authentication terminal 20-3 (digital signage) transmits the airline member ID obtained from the server device 10 to the airline system (not shown) and obtains the corresponding member information. The authentication terminal 20-3 displays information using the obtained member information (for example, flight information regarding the aircraft the user is scheduled to board). Alternatively, the authentication terminal 20-3 provides information based on the boarding pass information obtained from the server device 10. For example, the authentication terminal 20-3 displays the location of the boarding gate for the aircraft the user is boarding.

[0091] Alternatively, the authentication terminal 20-4 (gate device) uses the boarding pass information obtained from the server device 10 to determine whether the user has the authority to board the aircraft parked beyond the authentication terminal 20-4. If the authentication terminal 20-4 obtains boarding pass information from the server device 10 for the aircraft for which it is determining whether boarding is permitted, it opens the gate and allows the user to pass. If the authentication terminal 20-4 cannot obtain boarding pass information from the server device 10 for the aircraft for which it is determining whether boarding is permitted, it closes the gate and refuses the user to pass.

[0092] In this manner, the server device 10 receives an authentication request containing the biometric information of the person to be authenticated from the authentication terminal 20. The server device 10 identifies the person to be authenticated by performing a matching process using the biometric information contained in the received authentication request and the biometric information stored in the user management database. The server device 10 transmits to the authentication terminal 20 the business information corresponding to the authentication terminal 20 from among the at least one business information of the person to be authenticated that is stored in the user management database.

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

[0094] [Terminal] Examples of terminal 40 include mobile devices such as smartphones, mobile phones, game consoles, and tablets, as well as computers (personal computers, laptops), etc.

[0095] Figure 10 shows an example of the processing configuration (processing module) of terminal 40 according to the first embodiment. Referring to Figure 10, terminal 40 comprises a communication control unit 201, a token control unit 202, and a storage unit 203.

[0096] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the server device 10. The communication control unit 201 also transmits data to the server device 10. The communication control unit 201 passes the data received from other devices to other processing modules. The communication control unit 201 transmits the data obtained from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 201. The communication control unit 201 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0097] The token control unit 202 is a means for controlling tokens on terminal 40. Specifically, the token control unit 202 requests token registration from server device 10. The token control unit 202 is a module that implements the above-mentioned token control application.

[0098] The token control unit 202 requests the server device 10 to register the token necessary for users to receive biometric authentication services both inside and outside the airport.

[0099] The token control unit 202 functions as an acquisition means, obtaining business information necessary for a user to receive services using biometric authentication from an application installed on its own device. The token control unit 202 also functions as a transmission means, sending a token registration request containing the acquired business information and the user's biometric information to the server device.

[0100] Figure 11 is a flowchart showing an example of the operation of the token control unit 202 according to the first embodiment. The operation of the token control unit 202 will be explained with reference to Figure 11.

[0101] The token control unit 202 receives business information from other applications (step S101). Specifically, the token control unit 202 obtains business information through push notifications from other applications.

[0102] For example, the token control unit 202 obtains the airport member ID from the airport application. Alternatively, the token control unit 202 obtains the airline member ID from the airline application.

[0103] The token control unit 202 may acquire business information using, for example, an inter-application communication method called Deep Link. Alternatively, the token control unit 202 may acquire business information using a predetermined API (Application Programming Interface). For example, the token control unit 202 may receive business information from other applications using an API defined by the token control application.

[0104] Upon receiving business information, the token control unit 202 acquires biometric information for identity verification (step S102). Specifically, the token control unit 202 acquires a facial image of the user by taking a photograph of the user.

[0105] Furthermore, the token control unit 202 acquires biometric information from the user's identification document. For example, the token control unit 202 acquires a facial image from the IC chip embedded in an identification document such as a passport, driver's license, or My Number card. The token control unit 202 communicates with the IC chip using NFC (Near Field Communication) and acquires the facial image stored in the IC chip.

[0106] The token control unit 202 performs identity verification (step S103). Specifically, the token control unit 202 performs identity verification using a facial image obtained by photographing the user and a facial image read from the IC chip of the identification document. The token control unit 202 determines whether the two biometric pieces of information are substantially the same and performs identity verification.

[0107] The token control unit 202 generates feature quantities from both the facial image acquired through photography and the facial image acquired from the identification document.

[0108] Regarding the feature generation process, existing technologies can be used, so a detailed explanation will be omitted. For example, the token control unit 202 extracts the eyes, nose, mouth, etc., from the face image as feature points. Then, the token control unit 202 calculates the position of each feature point and the distance between each feature point as features (generating a feature vector consisting of multiple features).

[0109] Next, the token control unit 202 performs authentication processing (one-to-one authentication) using the two generated feature quantities. Specifically, the token control unit 202 calculates the similarity between corresponding face images using the two feature quantities. Based on the result of thresholding the calculated similarity, the token control unit 202 determines whether the two images are face images of the same person. The similarity can be calculated using methods such as the chi-squared distance or the Euclidean distance. The greater the distance, the lower the similarity, and the closer the distance, the higher the similarity.

[0110] If the similarity is greater than a predetermined value (if the distance is shorter than a predetermined value), the token control unit 202 determines that identity verification is successful. If the similarity is less than or equal to the predetermined value, the token control unit 202 determines that identity verification is unsuccessful.

[0111] Furthermore, the token control unit 202 may perform "liveness authentication" to prove that the user is real. Specifically, after successfully authenticating (matching) using the facial image obtained by photography and the facial image read from the identification document, the token control unit 202 instructs the user to perform a predetermined action and determines whether the user (authenticated person) is following the instructions. For example, the token control unit 202 may give an instruction such as "Please close your right eye," and determine whether the user is real based on whether the user is following the instructions.

[0112] If identity verification fails (step S104, No branch), the token control unit 202 terminates the token registration process. In this case, the token control unit 202 may notify the user that the token cannot be registered (issued) due to the failure of identity verification.

[0113] If identity verification is successful (Step S104, Yes branch), the token control unit 202 obtains the user's consent to provide personal information to a third party (Step S105).

[0114] The token control unit 202 obtains user consent using a GUI that is appropriate to the type (content) of the acquired business information and the application that provides the business information. For example, the token control unit 202 obtains user consent regarding the provision of personal information to third parties using the GUI shown in Figures 6 and 7.

[0115] If consent for the provision of personal information (biometric information and business information) cannot be obtained (step S106, No branch), the token control unit 202 terminates the token registration process. In this case, the token control unit 202 may notify the user that the token cannot be registered unless personal information is provided to a third party.

[0116] If consent is obtained regarding the provision of personal information (step S106, Yes branch), the token control unit 202 sends a token registration request to the server device 10 (step S107). The token control unit 202 sends a "token registration request" to the server device 10 that includes the user's biometric information (for example, a facial image obtained by photography or a facial image read from an identification document) and business information.

[0117] The token control unit 202 receives a response (affirmative response, negative response) to the token registration request (step S108).

[0118] The token control unit 202 performs processing according to the result of the token registration request (step S109).

[0119] Upon receiving an affirmative response (successful token registration), the token control unit 202 notifies the user, for example, that they can receive services using biometric authentication both inside and outside the airport.

[0120] If a negative response (token registration failure) is received, the token control unit 202 will, for example, notify the user that token registration failed.

[0121] Referring to Figure 11, the token control unit 202 has described the case in which it obtains consent for the provision of personal information to a third party (step S105) after performing identity verification by biometric authentication (step S103). However, the token control unit 202 may perform identity verification by biometric authentication after obtaining consent for the provision of personal information to a third party. For example, the token control application receives boarding pass information from the airline application. Upon receiving the boarding pass information, the token control application (token control unit 202) obtains the user's consent to provide biometric information and boarding pass information to an external server, while clearly stating the purpose of use of the acquired boarding pass information. After obtaining consent, the token control application performs identity verification using the user's biometric information.

[0122] Thus, the token control unit 202 has a function as a means of obtaining consent to obtain the user's consent to provide the user's personal information (business information and biometric information) to a third party before sending a token registration request to the server device 10. Furthermore, the token control unit 202 has a function as a means of verifying identity to perform identity verification using the biometric information obtained from the user and the biometric information obtained from the identification document held by the user. After successfully verifying the identity of the user who wishes to register a token, the token control unit 202 sends a token registration request to the server device 10.

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

[0124] Detailed explanations regarding processing modules for implementing airport applications, airline applications, etc., are omitted. This is because details concerning applications other than token control applications are outside the scope of this disclosure.

[0125] [Airport Terminal] Figure 12 shows an example of the processing configuration (processing module) of the airport terminal 30 according to the first embodiment. Referring to Figure 12, the airport terminal 30 comprises a communication control unit 301, a token control unit 302, and a storage unit 303.

[0126] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the server device 10. The communication control unit 301 also transmits data to the server device 10. The communication control unit 301 passes the data received from other devices to other processing modules. The communication control unit 301 transmits the data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 301. The communication control unit 301 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0127] The token control unit 302 is a means for controlling tokens in the airport terminal 30. The token control unit 302 performs identity verification using biometric information. The identity verification operation of the token control unit 302 can be the same as the identity verification operation of the token control unit 202 of the terminal 40, so a detailed explanation is omitted.

[0128] The token control unit 302 obtains business information from the user. For example, the token control unit 302 obtains business information (e.g., airport member ID) using a GUI.

[0129] Alternatively, the token control unit 302 obtains business information from the terminal 40. For example, the token control unit 302 obtains business information using a GUI. For example, the token control unit 302 displays a list of services that can be provided using biometric authentication. The user selects the desired service from the displayed list. For example, the user selects "Purchase goods using facial recognition payment".

[0130] The token control unit 302 acquires business information corresponding to the service selected by the user. For example, the token control unit 302 acquires business information using a GUI as shown in Figure 13.

[0131] A user interacting with the GUI shown in Figure 13 operates terminal 40 to launch an application instructed by airport terminal 30. The user then performs a predetermined operation within the launched application. Terminal 40 displays a 2D barcode containing converted business information in response to the user's actions. For example, the airport application displays a 2D barcode generated based on the airport member ID.

[0132] In the GUI shown in Figure 13, when the "Confirm" button is pressed, the token control unit 302 reads the 2D barcode presented by the user and obtains business information.

[0133] The token control unit 302 sends a token registration request containing the user's biometric information and business information to the server device 10. The token control unit 302 then performs processing according to the response to the token registration request (token registration successful, token registration failed).

[0134] The memory unit 303 is a means for storing information necessary for the operation of the airport terminal 30.

[0135] [Server equipment] Figure 14 shows an example of the processing configuration (processing module) of the server device 10 according to the first embodiment. Referring to Figure 14, the server device 10 comprises a communication control unit 401, a token control unit 402, an authentication unit 403, and a storage unit 404.

[0136] The communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from the authentication terminal 20. The communication control unit 401 also transmits data to the authentication terminal 20. The communication control unit 401 passes the data received from other devices to other processing modules. The communication control unit 401 transmits the data obtained from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 401. The communication control unit 401 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0137] The token control unit 402 is a means for controlling tokens in the server device 10. The token control unit 402 processes token registration requests received from terminal 40 or airport terminal 30.

[0138] Upon receiving a token registration request, the token control unit 402 registers the biometric information and business information included in the token registration request into the user management database (see Figure 15). As shown in Figure 15, the user management database stores the user's user ID, biometric information (features), and business information in association with each other.

[0139] As shown in Figure 15, the user management database classifies and stores acquired business information into business information that is permanently stored and business information that is temporarily stored. For example, airport member IDs and airline member IDs are business information that is permanently stored, while boarding pass information is business information that is temporarily stored (for example, only for 24 hours after registration).

[0140] System administrators decide which storage method to use for each piece of business information and configure it on the server device 10. System administrators should decide on the storage method considering the content (nature) of the business information. For example, airport member IDs are business information that is used repeatedly, while boarding pass information is business information whose use ends when the user boards the aircraft. System administrators should decide on the storage method for each piece of business information considering these circumstances.

[0141] The user management database shown in Figure 15 is an example and is not intended to limit the items that can be stored. For example, "facial images" may be registered in the user management database as biometric information.

[0142] Figure 16 is a flowchart showing an example of the operation of the token control unit 402 according to the first embodiment. The operation of the token control unit 402 will be explained with reference to Figure 16.

[0143] Upon receiving a token registration request, the token control unit 402 determines the quality of the biometric information (face image) included in the token registration request (step S201).

[0144] Specifically, the token control unit 402 determines whether the received face image is of sufficient quality for authentication purposes. For example, the token control unit 402 uses a pre-prepared learning model to determine the quality of the face image. The token control unit 402 inputs the face image into the learning model and obtains the determination result.

[0145] The learning model is obtained through machine learning using a large amount of training data in which image data (face images) are labeled (quality; good, bad). Any algorithm such as support vector machines, boosting, or neural networks can be used to generate the learning model. Since the above-mentioned support vector machines and other algorithms can be publicly known, their explanation will be omitted.

[0146] If the quality of the facial image is poor (step S202, No branch), the token control unit 402 determines that token registration has failed. In this case, the token control unit 402 sends a negative response indicating token registration failure to the sender of the token registration request (step S203).

[0147] If the facial image quality is good (step S202, Yes branch), the token control unit 402 determines whether an entry for the user who wishes to register a token exists in the user management database.

[0148] Specifically, the token control unit 402 performs a matching process (one-to-many matching; N is a positive integer, the same applies hereafter) using the biometric information included in the token registration request and the biometric information stored in the user management database (step S204).

[0149] The token control unit 402 generates feature vectors from the face image included in the token registration request. The token control unit 402 sets the generated feature vectors (feature vectors) as the feature vectors on the matching side and the feature vectors registered in the user management database as the feature vectors on the registration side.

[0150] The token control unit 402 calculates the similarity between each of the feature quantities on the matching side and the multiple feature quantities on the registration side. The chi-squared distance, Euclidean distance, etc., can be used to calculate this similarity. The greater the distance, the lower the similarity; the closer the distance, the higher the similarity.

[0151] The token control unit 402 determines that the matching process was successful if, among the multiple features registered in the user management database, there is a feature whose similarity to the feature to be matched is equal to or greater than a predetermined value. If no such feature exists, the token control unit 402 determines that the matching process failed.

[0152] If the matching process fails (step S205, No branch), the token control unit 402 adds a new entry to the user management database (step S206).

[0153] Subsequently, the token control unit 402 generates a user ID to identify the user. The user ID can be any information that uniquely identifies the user. For example, the token control unit 402 may assign a unique value each time an entry is added and use that as the user ID.

[0154] The token control unit 402 stores the user ID, biometric information (features), and business information in the added entry (step S207).

[0155] If the matching process is successful (step S205, Yes branch), the token control unit 402 stores the business information in the entry identified by the matching process (the entry in which the biometric information with the highest similarity is stored) (step S208).

[0156] When a token is registered in the user management database, the token control unit 402 notifies the source of the token registration request (airport terminal 30, terminal 40) that the token registration was successful. Specifically, the token control unit 402 sends an acknowledgment indicating successful token registration to the source of the token registration request (step S209).

[0157] The token control unit 402 also has a function to delete business information registered in the user management database. The token control unit 402 accesses the user management database periodically or at predetermined intervals. The token control unit 402 deletes business information that has been temporarily stored in each entry (token) of the database for a predetermined time (for example, 24 hours) since registration.

[0158] The authentication unit 403 is a means of authenticating users (authenticated persons) who wish to receive services via the authentication terminal 20. The authentication unit 403 processes authentication requests received from each authentication terminal 20 (touch point) installed inside and outside the airport.

[0159] Figure 17 is a flowchart illustrating an example of the operation of the authentication unit 403 according to the first embodiment. The operation of the authentication unit 403 will be explained with reference to Figure 17.

[0160] The authentication request includes the user's biometric information and device ID.

[0161] The authentication unit 403 performs a matching process (one-to-many matching; N is a positive integer, the same applies hereafter) using the biometric information included in the authentication request and the biometric information stored in the user management database (step S301).

[0162] Since the verification process performed by the authentication unit 403 can be the same as the verification process performed by the token control unit 402, a detailed explanation will be omitted.

[0163] If the matching process fails (step S302, No branch), the authentication unit 403 sends a negative response to the authentication terminal 20 indicating that the authentication of the person to be authenticated failed (step S303).

[0164] If the matching process is successful (step S302, Yes branch), the authentication unit 403 uses the terminal ID included in the authentication request to identify the authentication terminal 20 (type of authentication terminal 20; for example, POS terminal, reception terminal, digital signage, gate device, etc.) that sent the authentication request.

[0165] For example, the authentication unit 403 refers to table information that stores the type of authentication terminal 20 and the business information that the authentication terminal 20 needs to provide services, and identifies the business information corresponding to the authentication terminal 20 (see Figure 18). In Figure 18, for ease of understanding, the terminal ID is shown to represent the type of authentication terminal 20 shown in Figure 3.

[0166] The authentication unit 403 attempts to read business information corresponding to the identified authentication terminal 20 from the user management database (step S304).

[0167] If business information corresponding to the authentication terminal 20 cannot be read from the user management database (step S305, No branch), the authentication unit 403 determines that the authentication of the person to be authenticated has failed. In this case, the authentication unit 403 sends a negative response to the authentication terminal 20 indicating that the authentication of the person to be authenticated has failed (step S303).

[0168] If the authentication unit 403 can retrieve business information corresponding to the authentication terminal 20 from the user management database (step S305, Yes branch), it determines that the authentication of the person to be authenticated has been successful. In this case, the authentication unit 403 sends an affirmative response to the authentication terminal 20 indicating that the authentication of the person to be authenticated has been successful (step S306). At that time, the authentication unit 403 sends an affirmative response to the authentication terminal 20 that includes the business information read from the user management database.

[0169] The memory unit 404 stores various information necessary for the operation of the server device 10. A user management database is built in the memory unit 404.

[0170] [Authentication device] Figure 19 shows an example of the processing configuration (processing module) of the authentication terminal 20 according to the first embodiment. Referring to Figure 19, the authentication terminal 20 comprises a communication control unit 501, a biometric information acquisition unit 502, an authentication request unit 503, a function implementation unit 504, and a storage unit 505.

[0171] The communication control unit 501 is a means for controlling communication with other devices. For example, the communication control unit 501 receives data (packets) from the server device 10. The communication control unit 501 also transmits data to the server device 10. The communication control unit 501 passes the data received from other devices to other processing modules. The communication control unit 501 transmits the data obtained from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 501. The communication control unit 501 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0172] The biometric information acquisition unit 502 is a means of controlling a camera (not shown) and acquiring the user's biometric information. For example, the biometric information acquisition unit 502 photographs the user in front of it in response to an operation by, for example, a store employee. Alternatively, the biometric information acquisition unit 502 photographs the area in front of the device periodically or at predetermined intervals. The biometric information acquisition unit 502 determines whether or not a human face image is included in the acquired image, and if a face image is included, it extracts the face image from the acquired image data.

[0173] Note that existing technologies can be used for the face image detection and face image extraction processes by the biometric information acquisition unit 502, so a detailed explanation will be omitted. For example, the biometric information acquisition unit 502 may extract face images (face regions) from image data using a learning model trained by a CNN (Convolutional Neural Network). Alternatively, the biometric information acquisition unit 502 may extract face images using methods such as template matching.

[0174] The biometric information acquisition unit 502 hands over the extracted facial image to the authentication request unit 503.

[0175] The authentication request unit 503 is a means of requesting authentication from the server device 10 regarding the user in front of it. The authentication request unit 503 generates an authentication request including the acquired facial image and terminal ID and transmits it to the server device 10.

[0176] The authentication request unit 503 receives a response (affirmative response, negative response) to the authentication request from the server device 10. The authentication request unit 503 then passes the received response to the function implementation unit 504.

[0177] The function implementation unit 504 is a means for implementing the functions assigned to each authentication terminal 20. A detailed explanation of the operation of the function implementation unit 504 of each authentication terminal 20 is omitted because the operation of each authentication terminal 20 is different from the intent of this disclosure.

[0178] The memory unit 505 is a means for storing information necessary for the operation of the authentication terminal 20.

[0179] [System Operation] Next, the operation of the information processing system according to the first embodiment will be described. Figure 20 is a sequence diagram showing an example of the operation of the information processing system according to the first embodiment. Referring to Figure 20, the operation of the information processing system when a token registration request is sent from terminal 40 will be described.

[0180] Terminal 40 obtains business information from an application installed on its device and sends a token registration request including the obtained business information to the server device 10 (step S01).

[0181] The server device 10 registers the token in response to the receipt of the token registration request (step S02).

[0182] The server device 10 sends the result of the token registration process (token registration successful, token registration failed) to the terminal 40 (step S03).

[0183] Terminal 40 performs processing according to the received result (token registration successful, token registration failed) (step S04).

[0184] Furthermore, users can request token registration from the server device 10 multiple times using terminal 40 or airport terminal 30. For example, a user can request registration of a token related to their airport member ID from the server device 10 using terminal 40. Subsequently, the user may request registration of a token related to their airline member ID from the server device 10 using airport terminal 30.

[0185] Figure 21 is a sequence diagram showing an example of the operation of the information processing system according to the first embodiment. The operation of the information processing system when authentication processing is performed will be explained with reference to Figure 21.

[0186] The authentication terminal 20 acquires the user's biometric information and sends an authentication request including the acquired biometric information to the server device 10 (step S11).

[0187] The server device 10 performs authentication processing using the biometric information included in the authentication request and the biometric information and business information included in the user management database (step S12).

[0188] The server device 10 sends the authentication result (authentication successful, authentication failed) to the authentication terminal 20 (step S13).

[0189] The authentication terminal 20 performs processing according to the received authentication result (authentication successful, authentication failed) (step S14).

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

[0191] <Variation> In the above embodiment, the server device 10 was described in a case where it transmits business information relating to the entity that installed the authentication terminal 20 that sends the authentication request to the authentication terminal 20. However, the business information transmitted by the server device 10 is not limited to business information relating to the entity that installed the authentication terminal 20.

[0192] For example, if the server device 10 receives an authentication request from an authentication terminal 20-1 (POS terminal) installed by an airport company, it may send the airline member ID to the authentication terminal 20-1 in place of or in addition to the airport member ID. The authentication terminal 20-1 recognizes that the authenticated person is a member of the airline by receiving the airline member ID of the authenticated person who has successfully undergone biometric authentication. In this case, the authentication terminal 20-1 can offer the airline member benefits such as discounts on merchandise.

[0193] Thus, in the information processing system according to the first embodiment, business information pre-configured in the server device 10 is transmitted to the authentication terminal 20 regardless of the entity that installed the authentication terminal 20. As a result, business partnerships between different businesses (service providers) can be easily realized.

[0194] For example, consider a case where airport company A and airline B enter into a business partnership. Airport company A can easily build a system that gives preferential treatment to airline B's users (members) among multiple airlines. For example, if airline B's members receive benefits when they purchase goods at a shop, server device 10 should send airline B's airline member ID to authentication terminal 20-1 upon successful authentication request from the authentication terminal 20-1. Alternatively, if airline B's members are also allowed to use the lounge free of charge, server device 10 should send airline B's airline member ID to authentication terminal 20-2 (reception terminal) upon processing the authentication request from the authentication terminal 20-2.

[0195] To enable the provision of biometric authentication services across multiple service providers, system administrators only need to rewrite (reconfigure) the table information shown in Figure 18.

[0196] In this manner, when the server device 10 receives a token registration request that includes the first ID of the first business operator as business information, it stores the user's biometric information and the first ID in association with each other in the user management database. Furthermore, when the server device 10 receives a token registration request that includes the second ID of the second business operator as business information, it stores the user's biometric information, the first ID, and the second ID in association with each other in the user management database.

[0197] As described above, the terminal 40 according to the first embodiment obtains business information necessary for enjoying services using biometric authentication from an application installed on its own device (for example, a smartphone). The terminal 40 transmits the obtained business information and the user's biometric information to the server device 10 and requests token registration. The information processing system according to the first embodiment registers the business information, which is distributed and stored on the terminal 40 owned by the individual, to the system (server device 10) via the token control application. Therefore, there is no need to transmit business information that is centrally managed by the service provider's system to the server device 10. As a result, system registration of information necessary for providing services using biometric authentication is easily realized.

[0198] When a service provider offers various services to users using biometric authentication, a problem arises as to how to register business information (e.g., membership information) appropriate to each service in the system. To address this problem, in the information processing system according to the first embodiment, a token control application collects business information distributed and stored on terminals 40, and registers the collected business information in the server device 10. By adopting this configuration, new services using biometric authentication can be easily started. In other words, in recent years, due to increased user awareness of personal information, there is a tendency for necessary information to be registered on smartphones and other devices. This trend is expected to continue. If business information necessary for services using biometric authentication is obtained from terminals 40 such as smartphones, it becomes possible to register the information necessary for biometric authentication in the system without implementing large-scale system integration.

[0199] Furthermore, the server device 10 according to the first embodiment stores information from each service provider (for example, information such as member IDs) in conjunction with the user's biometric information. That is, the member information (member IDs) of each service provider is in a "loosely coupled" state, being linked while being independent of each system. By storing such member information (member IDs) in a loosely coupled state, the server device 10 can easily realize cooperation between each service provider. Specifically, cooperation between each service provider can be easily realized by a system administrator or the like rewriting the table information shown in Figure 18. When the authentication process is successful, the server device 10 should send the member information of other service providers that are linked with the service provider to the authentication terminal 20 (a device installed by the service provider) according to the rewritten table information.

[0200] [Second Embodiment] Next, a second embodiment will be described in detail with reference to the drawings.

[0201] The first embodiment described a case in which an application installed on terminal 40 notifies (pushes) a token control application of business information. The second embodiment describes a case in which a token control application requests another application to provide business information.

[0202] Note that the configuration of the information processing system according to the second embodiment can be the same as that of the first embodiment, so the explanation corresponding to Figure 3 is omitted. Also, the processing configuration of the server device 10, etc., according to the second embodiment can be the same as that of the first embodiment, so its explanation is omitted.

[0203] The following will focus on explaining the differences between the first and second embodiments.

[0204] Terminal 40 displays a list of biometric authentication services available to the user and retrieves the service the user wishes to use from the displayed list. Terminal 40 retrieves the business information necessary to provide the retrieved service (the service selected by the user) from the applications installed on its device.

[0205] Specifically, when a user performs a predetermined action, the token control unit 202 of the terminal 40 displays a list of services (services using biometric information) that can be provided to the user using business information obtained from an application installed on the device.

[0206] At that time, the token control unit 202 obtains information about the applications installed on the terminal 40. For example, the token control unit 202 obtains information such as the name and version of the applications installed on the terminal 40 from the OS (Operating System).

[0207] Next, the token control unit 202 refers to table information that stores business information obtained from applications installed on the terminal 40 in association with services that can be provided to the user. The token control unit 202 refers to this table information and generates a list of services that can be provided to the user using business information obtained from other applications.

[0208] The token control unit 202 displays a GUI as shown in Figure 22 using the list of generated services. The token control unit 202 uses the GUI to obtain information about the services that the user wishes to enjoy.

[0209] The token control unit 202 requests the provision of business information from the application that stores the business information necessary for the service desired by the user. The token control unit 202 obtains the necessary business information from other applications using Deep Link, APIs, etc.

[0210] Upon acquiring business information, the token control unit 202 performs user identity verification. The token control unit 202 performs identity verification using a facial image obtained by photographing the user and a facial image obtained from an identification document.

[0211] Upon successful identity verification, the token control unit 202 obtains the user's consent to provide personal information (biometric information and business information) to a third party. The token control unit 202 obtains the user's consent using a GUI similar to those shown in Figures 6 and 7.

[0212] Once user consent is obtained, the token control unit 202 sends a token registration request, including biometric information and business information, to the server device 10.

[0213] In the second embodiment, as in the first embodiment, the token control unit 202 may perform identity verification using the user's biometric information after obtaining consent for the provision of personal information to a third party. In this case, the token control unit 202 may obtain the user's consent for the provision of personal information to a third party on a list display screen as shown in Figure 22. For example, the token control unit 202 may display together "biometric information to be provided to a third party," "business information to be provided to a third party" for each available service, and "purpose of use of personal information (biometric information, business information)."

[0214] As described above, the terminal 40 in the second embodiment presents the user with a list of services that can be provided based on business information that can be collected from applications installed on its device. The terminal 40 obtains business information corresponding to the service selected by the user from the application and registers the obtained business information in the server device 10. In the second embodiment as well, the system registration of information necessary for providing services using biometric authentication is easily realized.

[0215] [Third Embodiment] Next, a third embodiment will be described in detail with reference to the drawings.

[0216] In the third embodiment, we will describe a case in which the server device 10 provides the user's activity history to a service provider or the like.

[0217] Since the configuration of the information processing system according to the third embodiment can be the same as that of the first and second embodiments, the explanation corresponding to Figure 3 will be omitted.

[0218] The following will focus on explaining the differences between the first to third embodiments.

[0219] In the third embodiment, the authentication unit 403 stores the details of the authentication process performed in response to the receipt of an authentication request in the behavioral history management database. The authentication unit 403 generates the user's behavioral history by storing the details of the authentication process.

[0220] For example, the authentication unit 403 stores in the behavioral history management database the date and time of successful biometric authentication, information about the authentication terminal 20 used by the authenticated person (e.g., location and type) (see Figure 23). Alternatively, if the authentication unit 403 can obtain supplementary information such as payment information in addition to biometric information from the authentication terminal 20, it also stores such supplementary information in the behavioral history management database.

[0221] If the authentication unit 403 successfully authenticates the person to be authenticated, it searches the activity history management database using the user ID of the person to be authenticated as the key. If the search is successful, the authentication unit 403 stores the activity history in the entry identified by the search.

[0222] If the search fails, the authentication unit 403 adds a new entry to the activity history management database. The authentication unit 403 stores in the added entry the user's user ID and information corresponding to the ID used by the service provider to manage the user from the business information stored in the user management database. In the example of the user management database shown in Figure 15, the authentication unit 403 stores the airport company's member ID (airport member ID) and the airline's member ID (airline member ID) in the activity history management database. Furthermore, the authentication unit 403 stores the user's activity history in the added entry.

[0223] The authentication unit 403 generates an activity history as shown in the activity history management database in Figure 23. Note that the activity history management database shown in Figure 23 is an example and is not intended to limit the items to be stored.

[0224] Figure 24 shows an example of the processing configuration (processing module) of the server device 10 according to the third embodiment. Referring to Figure 24, an information provision control unit 405 is added to the configuration of the server device 10 according to the first embodiment.

[0225] The information provision control unit 405 is a means of providing information about user behavior based on requests from service providers and others participating in the system. The information provision control unit 405 generates provision information using the behavior history stored in the behavior history management database and outputs the generated provision information.

[0226] The information provision control unit 405 acquires requests for information provision from service providers. For example, the information provision control unit 405 acquires requests for information provision from service providers using a portal site or the like that can be accessed by the service provider's representatives.

[0227] The information provision control unit 405 obtains the IDs of users whose activity history it wants to know from the service provider. For example, an airport company enters the IDs (list of IDs) of its members whose activity history it wants to know into the portal site.

[0228] The information provision control unit 405 searches the behavioral history management database using the acquired ID (ID list) as a key and identifies the corresponding entry. The information provision control unit 405 provides the service provider with the behavioral history stored in the behavioral history field of the identified entry.

[0229] As described above, when the server device 10 according to the third embodiment successfully authenticates the biometric authentication of a person to be authenticated, it generates the person's behavioral history using at least information related to the authentication terminal 20. The server device 10 stores the person to be authenticated's first ID, second ID, and the generated behavioral history in association with each other in the behavioral history management database (second database). When the server device 10 obtains the first ID from the first service provider, it reads the user's behavioral history corresponding to the first ID from the behavioral history management database and provides the read behavioral history to the first service provider. As a result, behavioral histories involving multiple service providers can be easily collected. In other words, by utilizing the information provided by the server device 10 according to the third embodiment, it becomes possible to analyze data spanning multiple service providers. For example, an airport company and a railway company can perform data analysis from the perspective of MaaS (Mobility as a Service). Note that the multiple service providers may or may not cooperate with each other.

[0230] Next, we will describe the hardware of each device that makes up the information processing system. Figure 25 shows an example of the hardware configuration of terminal 40.

[0231] Terminal 40 can be configured using an information processing device (a so-called computer), and has the configuration illustrated in Figure 25. For example, terminal 40 includes a processor 311, memory 312, input / output interface 313, and communication interface 314, etc. The components of the processor 311, etc. are connected by an internal bus or the like and are configured to communicate with each other.

[0232] However, the configuration shown in Figure 25 is not intended to limit the hardware configuration of terminal 40. Terminal 40 may include hardware not shown, and may not have an input / output interface 313 if necessary. Also, the number of processors 311 etc. included in terminal 40 is not intended to be limited to the example in Figure 25; for example, terminal 40 may include multiple processors 311.

[0233] The processor 311 is a programmable device such as a CPU (Central Processing Unit), MPU (Micro Processing Unit), or DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs, including an operating system (OS).

[0234] Memory 312 includes RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc. Memory 312 stores the OS program, application programs, and various data.

[0235] The input / output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user input such as a keyboard or mouse.

[0236] The communication interface 314 is a circuit, module, etc., that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card), etc.

[0237] The functions of terminal 40 are realized by various processing modules. These processing modules are realized, for example, by the processor 311 executing a program stored in memory 312. The program can also be recorded on a computer-readable storage medium. The storage medium can be a non-transitory material such as semiconductor memory, hard disk, magnetic recording medium, or optical recording medium. In other words, the present invention can also be embodied as a computer program product. Furthermore, the program can be downloaded via a network or updated using the storage medium on which the program is stored. Moreover, the processing module may be realized by a semiconductor chip.

[0238] Furthermore, the server device 10, etc., can also be configured using an information processing device, similar to the terminal 40, and its basic hardware configuration is no different from that of the terminal 40, so the explanation will be omitted.

[0239] The terminal 40, which is an information processing device, is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the terminal 40 executes a control method for the terminal 40 through this program.

[0240] [Differentiation] The configuration and operation of the information processing system described in the above embodiment are illustrative examples and are not intended to limit the system configuration.

[0241] In the above embodiment, the operation of the information processing system disclosed in this application was explained using an authentication system at an airport as an example. However, the information processing system disclosed in this application may be applied to facilities other than airports. For example, the information processing system may be applied to an authentication system at a large station such as a terminal station. Alternatively, the information processing system may be applied to an authentication system at an event venue or the like.

[0242] In the above embodiment, the information processing system disclosed in this application was described using an airport where domestic flights take off and land as an example. However, the information processing system disclosed in this application may also be applied to airports where international flights take off and land. In this case, the user only needs to register the passport information stored in the terminal 40 as business information in the server device 10.

[0243] In the above embodiment, airport applications and airline applications were used as examples of applications other than the token control application. However, it is obvious that the application installed on terminal 40 is not limited to these applications. The token control application can obtain business information from any application installed on terminal 40. For example, the token control application may obtain business information from a train application used by a railway company's member.

[0244] The above embodiment describes a case where the system administrator sets the storage method (permanent storage, temporary storage) for each business information on the server device 10. The selection of the storage method may be made by the user themselves. For example, when the terminal 40 obtains the user's consent regarding the provision of personal information to a third party using the GUI shown in Figures 6 and 7, the user may be able to select the storage method for the business information.

[0245] In the second embodiment, it was explained that the user is provided with a list of services that can be provided using business information obtained from an application installed on the terminal 40 (see Figure 22). However, the terminal 40 may generate a list of services that can be provided to the user as a system (services using biometric authentication) and display a GUI. Also, if the user selects a service used for business information that can be obtained from an application that is not installed on the terminal 40, the terminal 40 may prompt the user to install the application that is not installed. For example, if "face recognition at the boarding gate" using boarding information obtainable from an airline application is selected, and the airline application is not installed on the terminal 40, the terminal 40 will prompt the user to install the airline application. Even when the system presents the user with a list of services that can be provided to the user, as explained in the second embodiment, the terminal 40 may perform identity verification using biometric information after obtaining the user's consent to provide personal information to a third party.

[0246] Alternatively, terminal 40 may prompt the user to update the application version if the version of the application installed on its device is outdated and it is unable to obtain appropriate business information.

[0247] In the above embodiment, the case in which the server device 10 performs quality verification of biometric information at the time of token issuance (token registration) was described. This quality verification may also be performed at airport terminal 30 or terminal 40.

[0248] The above embodiment describes a case where biometric information related to a facial image is transmitted and received between the server device 10 and the authentication terminal 20. However, feature quantities generated from the facial image may also be transmitted and received between the devices. In this case, the receiving server device 10 may use the received feature quantities and utilize them in subsequent processing. Alternatively, the biometric information stored in the user management database may be feature quantities or facial images. If a facial image is stored, feature quantities may be generated from the facial image as needed. Alternatively, both facial images and feature quantities may be stored in the user management database.

[0249] In the above embodiment, the case in which the user management database is configured inside the server device 10 was described, but the user management database may be built on an external database server or the like. In other words, some functions of the server device 10 may be implemented on another server. More specifically, it is sufficient that the "token control unit (token control means)" etc. described above is implemented in any device included in the system.

[0250] The form of data transmission and reception between each device (server device 10, terminal 40, etc.) is not particularly limited, but the data transmitted and received between these devices may be encrypted. Since biometric information and other sensitive data are transmitted and received between these devices, it is desirable that encrypted data be transmitted and received in order to appropriately protect personal information.

[0251] In the flowcharts (sequence diagrams) used in the above description, multiple processes (processes) are shown in order, but the execution order of the processes performed in the embodiment is not limited to the order in which they are shown. In the embodiment, the order of the illustrated processes can be changed to the extent that it does not impair the content, for example, by executing each process in parallel.

[0252] The embodiments described above are explained in detail to facilitate understanding of the disclosure, and it is not intended that all the configurations described above are necessary. Furthermore, when multiple embodiments are described, each embodiment may be used individually or in combination. For example, it is possible to replace parts of the configuration of one embodiment with those of another embodiment, or to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of one embodiment with those of another.

[0253] As described above, the industrial applicability of the present invention is clear, and it is particularly suitable for information processing systems that provide users with biometric authentication services.

[0254] Some or all of the above embodiments may also be described as follows, but are not limited to the following: [Note 1] A means for obtaining business information necessary for a user to receive services using biometric authentication from an application installed on the device, A transmission means that transmits a token registration request, including the acquired business information and the user's biometric information, to a server device. A terminal equipped with the following features. [Note 2] The terminal as described in Appendix 1, further comprising means for obtaining the user's consent to provide the business information and biometric information to a third party before transmitting the token registration request to the server device. [Note 3] The system further includes an identity verification method that performs identity verification using biometric information obtained from the user and biometric information obtained from the user's identification document, The transmission means is the terminal described in Appendix 2, which, after successfully verifying the identity of the user, transmits the token registration request to the server device. [Note 4] The acquisition means is, The system displays a list of biometric authentication services available to the user, and retrieves the service that the user wishes to use from the displayed list of services. A terminal as described in Appendix 3, which obtains business information necessary for providing the acquired service from among the applications installed on the aforementioned device. [Note 5] Server device, The device owned by the user, Includes, The aforementioned terminal is The system obtains the necessary business information for the user to receive services using biometric authentication from an application installed on its own device, and sends a token registration request containing the obtained business information and the user's biometric information to the server device. The server device is A system that, upon receiving the aforementioned token registration request, stores the user's biometric information and business information in association with each other in a first database. [Note 6] The server device is Upon receiving the token registration request which includes the first ID of the first business operator as business information, the biometric information of the user and the first ID are associated and stored in the first database. The system described in Appendix 5, which, upon receiving the token registration request that includes the second ID of the second business operator as business information, stores the user's biometric information, the first ID, and the second ID in association with each other in the first database. [Note 7] The server device is The authentication terminal receives an authentication request that includes the biometric information of the person to be authenticated. The system as described in Appendix 6, which identifies the person to be authenticated by matching the biometric information contained in the received authentication request with the biometric information stored in the first database, and transmits to the authentication terminal the business information corresponding to the authentication terminal from among the at least one business information of the person to be authenticated stored in the first database. [Note 8] The server device is The system as described in Appendix 7, wherein, upon successful biometric authentication of the person to be authenticated, a history of the person to be authenticated is generated using at least information related to the authentication terminal, and the first ID of the person to be authenticated, the second ID, and the generated history of the person to be authenticated are associated and stored in a second database. [Note 9] The server device is The system described in Appendix 8, which, upon obtaining the first ID from the first business operator, reads the user's activity history corresponding to the first ID from the second database and provides the read activity history to the first business operator. [Note 10] The system described in any one of the appendices 5 to 9, wherein the biometric information is a facial image or a feature quantity generated from the facial image. [Note 11] On the device, The system obtains the necessary business information for users to receive services using biometric authentication from an application installed on the device. A terminal control method that transmits a token registration request, including the acquired business information and the user's biometric information, to a server device. [Note 12] On the computer installed in the terminal, The process involves obtaining the necessary business information for a user to receive services using biometric authentication from an application installed on the device, The process involves sending a token registration request, which includes the acquired business information and the user's biometric information, to the server device. A computer-readable storage medium that stores a program to execute.

[0255] Note that the disclosures of each of the above-cited prior art documents are incorporated herein by reference. Having described the embodiments of the present invention above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications can be made without departing from the scope and spirit of the present invention. That is, the present invention naturally includes all disclosures including the claims, as well as various modifications and corrections that can be made by those skilled in the art in accordance with the technical idea.

Explanation of Reference Numerals

[0256] 10 Server device 20 Authentication terminal 20-1 Authentication terminal 20-2 Authentication terminal 20-3 Authentication terminal 20-4 Authentication terminal 30 Airport terminal 40 Terminal 100 Terminal 101 Acquisition means 102 Transmission means 201 Communication control unit 202 Token control unit 203 Storage unit 301 Communication control unit 302 Token control unit 303 Storage unit 311 Processor 312 Memory 313 Input / output interface 314 Communication interface 401 Communication control unit 402 Token control unit 403 Authentication unit 404 Storage unit 405 Information provision control unit<00009​​​​​​​​​

Claims

1. A presentation means for presenting information necessary for a user to use the service, An identity verification method that performs identity verification using facial information obtained by photographing the user and facial information linked to an identification document, A means for obtaining consent to obtain the user's consent to provide information necessary to use the service, A means for obtaining personal information necessary to use the aforementioned service, obtained from a token control application installed on the user's device for managing and controlling token registration, A transmission means for transmitting information necessary to use the acquired service to an external device, A terminal equipped with the following features.

2. The terminal according to claim 1, wherein the transmitting means transmits to the external device information necessary to use the service, including the user's biometric information.

3. The terminal according to claim 1, further comprising a service information acquisition means for acquiring information on services that the user wishes to use.

4. The presenting means presents a list of services that can be provided to the user, The terminal according to claim 3, wherein the service information acquisition means acquires information on a service selected by the user from among the listed services.

5. External device and The device owned by the user, Includes, The aforementioned terminal is A means for presenting information necessary for the user to use the service, An identity verification method that performs identity verification using facial information obtained by photographing the user and facial information linked to an identification document, A means for obtaining consent to obtain the user's consent to provide information necessary to use the service, A means for obtaining personal information necessary to use the aforementioned service, obtained from a token control application installed on the user's device for managing and controlling token registration, A transmission means for transmitting information necessary to use the acquired service to the external device, A system equipped with these features.

6. In a terminal, The system provides users with the information they need to use the service. The system performs identity verification using facial information obtained by photographing the user and facial information linked to an identification document. We obtain the user's consent to provide the information necessary to use the aforementioned service. The information necessary to use the aforementioned service is obtained from a token control application installed on the user's device for managing and controlling token registration. A terminal control method for transmitting information necessary to use the acquired service to an external device.

7. A terminal control method according to claim 6, comprising transmitting information necessary to use the service, including the user's biometric information, to the external device.

8. A terminal control method according to claim 6, which acquires information on the service that the user wishes to use.

9. A computer installed in the terminal, The process of presenting the information necessary for the user to use the service, The process involves performing identity verification using facial information obtained by photographing the user and facial information linked to an identification document. A process to obtain the user's consent to provide the information necessary to use the service, The process involves obtaining the information necessary to use the aforementioned service from a token control application installed on the user's device for managing and controlling token registration, The process involves transmitting the information necessary to use the acquired service to an external device, A program to execute.

10. The program according to claim 9, wherein the transmission process transmits to the external device information necessary to use the service, including the user's biometric information.

11. The program according to claim 9, further comprising the process of obtaining information on the service that the user wishes to use.

Images