Information processing device, method and program

Abstract

To promote information registration for biometric authentication.SOLUTION: An information processing device comprises: registration means configured to register first biological information of a user and first deposit amount information acquired through an application installed in a user terminal in association with each other; acquisition means configured to acquire a settlement request including second biological information of the user and a settlement amount; and settlement means configured to settle the settlement amount on the basis of the first deposit amount information associated with the first biological information, by collating the first biological information with the second biological information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing device, a system, a method, and a program, and more particularly to an information processing device, a system, a method, and a program for managing authentication information. [Background technology]

[0002] In recent years, biometric authentication technology including face recognition has been developed, and various services including payment using biometric authentication technology are being introduced. Patent Document 1 discloses a technology in which customer information including authentication information and a charge amount are initially registered, and when a payment request including purchase information is acquired, authentication is performed based on the purchase information, and if the authentication is successful, provisional payment information is generated for deferred payment. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-144787 A Summary of the Invention [Problem to be solved by the invention]

[0004] In order to use a payment service that uses biometric authentication, it is necessary to register in advance personal information, including biometric information, and payment information to be used for electronic payments (bank account information, credit card information, etc.). However, some people have concerns about registering personal information and payment information. This has led to a lack of promotion of information registration for biometric authentication, which is hindering the spread of biometric authentication.

[0005] The present disclosure has been made to solve such problems, and has an object to provide an information processing device, system, method, and program for facilitating information registration for biometric authentication. [Means for solving the problem]

[0006] An information processing device according to a first aspect of the present disclosure includes: a registration means for registering a first biometric information of a user and a payment balance in association with each other; an acquisition means for acquiring a payment request including second biometric information and a payment amount; a payment means for matching the first biometric information with the second biometric information and using a payment balance associated with the first biometric information to settle the payment amount; Equipped with.

[0007] An information processing system according to a second aspect of the present disclosure includes: a registration terminal that accepts first biometric information and a predetermined amount of deposit from a user; An information processing device; a payment terminal that accepts second biometric information from a user making a payment, The registration terminal transmits the first biometric information and the deposit amount to the information processing device, The information processing device registers a settlement balance based on the deposit amount received from the registration terminal in association with the first biometric information; the payment terminal transmits a payment request including the second biometric information and a payment amount to the information processing device; The information processing device includes: In response to the payment request received from the payment terminal, the first biometric information is matched with the second biometric information, and the payment amount is settled using the payment balance associated with the first biometric information.

[0008] An information processing method according to a third aspect of the present disclosure includes: The computer registering the first biometric information of the user in association with a payment balance; obtaining a payment request including the second biometric information and a payment amount; By matching the first biometric information with the second biometric information, the payment amount is paid using a payment balance associated with the first biometric information.

[0009] An information processing program according to a fourth aspect of the present disclosure, A process of registering first biometric information of a user in association with a payment balance; obtaining a payment request including second biometric information and a payment amount; a process of matching the first biometric information with the second biometric information and paying the payment amount using a payment balance associated with the first biometric information; to be executed by the computer. Effect of the Invention

[0010] The present disclosure makes it possible to provide an information processing device, system, method, and program for facilitating information registration for biometric authentication. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing a configuration of an authentication information management device according to a first embodiment of the present invention. [Diagram 2] 4 is a flowchart showing the flow of an authentication information management method according to the first embodiment. [Diagram 3] FIG. 11 is a block diagram showing the overall configuration of an authentication information management system according to a second embodiment. [Figure 4] FIG. 11 is a block diagram showing a configuration of an authentication terminal according to the second embodiment. [Diagram 5] FIG. 11 is a block diagram showing a configuration of an authentication information management device according to a second embodiment. [Figure 6] FIG. 11 is a block diagram showing a configuration of an authentication device according to a second embodiment. [Figure 7] 11 is a flowchart showing the flow of face information registration processing by the registration terminal according to the second embodiment. [Figure 8] 13 is a flowchart showing the flow of a temporary registration process according to the second embodiment. [Figure 9] 11 is a flowchart showing the flow of a main registration process according to the second embodiment. [Figure 10] 10 is a flowchart showing the flow of face information registration processing by the authentication device according to the second embodiment. [Figure 11]11 is a flowchart showing the flow of a payment process by the authentication terminal according to the second embodiment. [Figure 12] 11 is a flowchart showing the flow of a payment process by the authentication information management device according to the second embodiment. [Figure 13] 11 is a flowchart showing the flow of face authentication processing by the authentication device according to the second embodiment. [Figure 14] 11 is a flowchart showing a flow of processing according to a provisional registration status by an authentication terminal according to the second embodiment. [Figure 15] 11 is a flowchart showing a flow of processing in response to a provisional registration status inquiry by the authentication information management device according to the second embodiment. [Figure 16] FIG. 11 is a diagram showing a display example of a provisional registration status display screen according to the second embodiment. [Figure 17] FIG. 11 is a diagram showing an example of a display of a history of a cumulative deposit amount in the provisional registration status according to the second embodiment. [Figure 18] 13 is a flowchart showing a flow of processing for a response to notification information by the authentication information management device according to the second embodiment. [Figure 19] FIG. 11 is a block diagram showing the overall configuration of an authentication information management system according to a third embodiment. [Figure 20] FIG. 11 is a block diagram showing the configuration of a user terminal according to the third embodiment. [Figure 21] FIG. 11 is a block diagram showing a configuration of an authentication information management device according to a third embodiment. [Figure 22] 13 is a flowchart showing the flow of face information registration processing by a user terminal according to the third embodiment. [Figure 23] 13 is a flowchart showing the flow of a temporary registration process according to the third embodiment. [Figure 24] FIG. 11 is a block diagram showing the configuration of a user terminal according to the fourth embodiment. [Diagram 25] FIG. 13 is a block diagram showing a configuration of an authentication information management device according to a fourth embodiment. [Figure 26]13 is a flowchart showing the flow of face information registration processing by a user terminal according to the fourth embodiment. [Figure 27] 13 is a flowchart showing the flow of a temporary registration process according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.

[0013] <Embodiment 1> FIG. 1 is a block diagram showing the configuration of an authentication information management device 1 according to the first embodiment. The authentication information management device 1 is an information processing device for managing authentication information (biometric information) to use a payment service by biometric authentication. Here, the authentication information management device 1 may be connected to a predetermined terminal through a communication network (not shown, hereinafter, the communication network may also be simply referred to as a network) or a predetermined wireless communication. The network may be wired or wireless, and may use any type of communication protocol. The terminal may input to the authentication information management device 1 and perform processing according to the output from the authentication information management device 1. The terminal may be a registration terminal, an authentication terminal, a payment terminal, or the like.

[0014] The authentication information management device 1 includes an acquisition unit 11, a registration unit 12, an authentication control unit 13, a settlement unit 14, and a usage control unit 15. The acquisition unit 11 acquires a provisional registration request including the first biometric information of the user and the deposit amount. The biometric information is data (feature amount) calculated from physical characteristics unique to an individual, such as the user's fingerprint, voiceprint, veins, retina, and iris pattern. For example, the authentication information management device 1 may acquire biometric information directly from the user and may also accept a cash deposit. The authentication information management device 1 may acquire biometric information from the user via a biometric information acquisition device such as a camera. In addition, when the user deposits cash into the authentication information management device 1, the acquisition unit 11 acquires the accepted cash deposit amount. The deposit amount is not limited to cash, and may be the remittance amount of electronic money (amount deposited into an account on the authentication information management device 1 side). In these cases, the authentication information management device 1 issues a provisional registration request including the acquired biometric information and the accepted deposit amount. The acquisition unit 11 acquires an internally issued temporary registration request. Alternatively, when the above-mentioned registration terminal acquires the biometric information of the user and accepts a cash deposit, the registration terminal may issue a temporary registration request including the biometric information and the deposit amount, and transmit the temporary registration request to the authentication information management device 1. In this case, the acquisition unit 11 acquires the temporary registration request from the registration terminal.

[0015] The registration unit 12 registers the provisional registration information in which the payment balance based on the deposit amount included in the provisional registration request is associated with the first biometric information. The registration unit 12 may calculate the payment balance as an amount available for future payment based on the deposit amount included in the provisional registration request. For example, the registration unit 12 may calculate the payment balance by adding a predetermined amount to the deposit amount. Alternatively, the registration unit 12 may set the deposit amount as the payment balance. The registration unit 12 stores the provisional registration information in which the payment balance is associated with the first biometric information in a storage device (not shown) inside or outside the authentication information management device 1. Note that the provisional registration information is not limited to the case where the payment balance is directly associated with the first biometric information, but may also indirectly be associated with the payment balance and the first biometric information. For example, the first storage device may store information in which the payment balance is associated with the user ID, and the second storage device may store information in which the user ID is associated with the first biometric information. In this case, the provisional registration information can be said to associate the payment balance with the first biometric information in a storage system that combines the first storage device and the second storage device.

[0016] The authentication control unit 13 controls the (first) biometric authentication using the first biometric information for the second biometric information in response to a payment request including the second biometric information and the payment amount. The second biometric information is biometric information acquired from a user who is about to make a payment. For example, the authentication information management device 1 may directly acquire the second biometric information from the user who is the object of payment, and issue a payment request including the payment amount of the object of payment and the second biometric information. Alternatively, the payment terminal may acquire the second biometric information from the user who is the object of payment, and transmit a payment request including the payment amount of the object of payment and the second biometric information to the authentication information management device 1. In these cases, the authentication control unit 13 controls the biometric authentication in response to a payment request issued internally or a payment request received from the payment terminal. The authentication control unit 13 controls the biometric authentication using the second biometric information included in the payment request and the first biometric information included in the above-mentioned provisional registration information. In addition, when the authentication information management device 1 has the above-mentioned storage device built-in, the authentication control unit 13 performs the biometric authentication process by matching the biometric information. Alternatively, if the biometric information is stored in an external authentication device, the authentication control unit 13 causes the authentication device to perform biometric authentication processing and obtains the authentication result.

[0017] When the (first) biometric authentication by the authentication control unit 13 is successful, the settlement unit 14 settles the payment amount included in the settlement request by using the payment balance associated with the first biometric information in the temporary registration information. For example, the settlement unit 14 updates the payment balance of the temporary registration information by subtracting the payment amount from the payment balance.

[0018] The use control unit 15 controls the use of the temporary registration information according to the determination result of whether or not the temporary registration information satisfies a first condition. The first condition is a condition for restricting the use of the temporary registration information. In particular, the use control unit 15 may restrict the use of the temporary registration information when the temporary registration information satisfies the first condition. Specifically, the use control unit 15 restricts the use of the temporary registration information that satisfies the first condition in the biometric authentication by the authentication control unit 13. In other words, when the first condition is satisfied, the authentication control unit 13 cannot control the biometric authentication using the first biometric information. Alternatively, the use control unit 15 restricts the use of the temporary registration information that satisfies the first condition in the payment by the payment unit 14. In other words, when the first condition is satisfied, the payment unit 14 cannot perform the payment using the payment balance associated with the first biometric information. Therefore, even if the user to be paid has registered the temporary registration information including the first biometric information and the deposit amount in advance in the authentication information management device 1, if the first condition is subsequently satisfied, the user to be paid is restricted from using the payment service by biometric authentication. On the other hand, when the provisional registration information does not satisfy the first condition, the usage control unit 15 enables or permits the use of the provisional registration information. Note that the case where the first condition is not satisfied can also be said to be the case where the usage condition of the provisional registration information is satisfied.

[0019] 2 is a flowchart showing the flow of the authentication information management method according to the first embodiment. First, the acquisition unit 11 acquires a temporary registration request including the user's first biometric information and the deposit amount (S11). Next, the registration unit 12 registers temporary registration information that associates the settlement balance based on the deposit amount included in the temporary registration request acquired in step S11 with the first biometric information (S12).

[0020] After that, the authentication information management device 1 accepts a payment request including the second biometric information and the payment amount. At this time, the authentication control unit 13 controls (first) biometric authentication using the first biometric information for the second biometric information in response to the payment request (S13). Then, the payment unit 14 determines whether or not the biometric authentication in step S13 is successful (S14). If the (first) biometric authentication in step S13 is successful, the payment unit 14 settles the payment amount using the payment balance associated with the first biometric information (S15).

[0021] Then, the usage control unit 15 controls the usage of the temporary registration information according to the determination result of whether or not the temporary registration information satisfies the first condition (S16). If the biometric authentication in step S13 fails, the process is terminated. Alternatively, in this case, the authentication control unit 13 may transmit to the request source a notification that the biometric authentication has failed. Also, the determination of the first condition in step S16 may be performed before the biometric authentication in step S13 or before the payment in step S15. In other words, if the temporary registration information does not satisfy the first condition, the usage of the temporary registration information in the biometric authentication in step S13 or the payment in step S15 is restricted. On the other hand, if the temporary registration information satisfies the first condition, the usage of the temporary registration information in the biometric authentication in step S13 or the payment in step S15 may be permitted.

[0022] In this manner, in this embodiment, in order for a user to try out a payment service using biometric authentication, it is not necessary to register payment information that can be used for a wide range of postpaid payments, and the amount that can be paid is prepaid, thereby reducing concerns about pre-registration. In addition, the use of provisional registration information is controlled according to the determination result of whether or not certain conditions are met. For example, the use of provisional registration information that meets certain conditions is restricted, so that unexpected use is also suppressed. In addition, the registration content of provisional registration information is more limited than that of final registration information, so the registration procedure is simplified. From the above, it is possible to promote the registration of information for biometric authentication used in payment services. By promoting the registration of information for biometric authentication, it is possible to provide various biometric authentication services, thereby improving the added value of the services.

[0023] The authentication information management device 1 includes a processor, a memory, and a storage device, which are not shown in the figure. The storage device stores a computer program that implements the processing of the authentication information management method according to this embodiment. The processor then loads the computer program from the storage device into the memory and executes the computer program. As a result, the processor realizes the functions of an acquisition unit 11, a registration unit 12, an authentication control unit 13, a settlement unit 14, and a usage control unit 15.

[0024] Alternatively, the acquisition unit 11, the registration unit 12, the authentication control unit 13, the settlement unit 14, and the usage control unit 15 may each be realized by dedicated hardware. Also, a part or all of the components of each device may be realized by a general-purpose or dedicated circuit, processor, etc., or a combination of these. These may be configured by a single chip, or may be configured by multiple chips connected via a bus. A part or all of the components of each device may be realized by a combination of the above-mentioned circuits, etc., and a program. Also, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (field-programmable gate array), a quantum processor (quantum computer control chip), etc. may be used as the processor.

[0025] Furthermore, when some or all of the components of the authentication information management device 1 are realized by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged or distributed. For example, the information processing devices, circuits, etc. may be realized as a client-server system, a cloud computing system, etc., in a form in which each is connected via a communication network. Furthermore, the functions of the authentication information management device 1 may be provided in a SaaS (Software as a Service) format.

[0026] <Embodiment 2> The second embodiment is a specific example of the first embodiment described above. FIG. 3 is a block diagram showing the overall configuration of an authentication information management system 1000 according to the second embodiment. The authentication information management system 1000 is an information system for managing authentication information (face information) for using a payment service by face recognition via a plurality of authentication terminals installed in a predetermined area. In particular, in the authentication information management system 1000, a park 100 is exemplified as the predetermined area. However, the predetermined area may be an event venue, a commercial facility, or the like. The predetermined area may also include a plurality of venues or facilities.

[0027] In the following description, the authentication for personal identification is assumed to be face authentication, which is an example of biometric authentication, and the personal identification information is assumed to be face feature information, which is an example of biometric information. However, other technologies using captured images can be applied to the biometric authentication and biometric information. For example, the biometric information may be data (feature amount) calculated from physical characteristics unique to an individual, such as a fingerprint, voiceprint, vein, retina, or iris pattern. Furthermore, the authentication for personal identification may be other than biometric authentication, and the personal identification information may also be other than biometric information. For example, the personal identification information may be, but is not limited to, a combination of an ID and a password, an electronic certificate, a two-dimensional code, and the like.

[0028] The authentication information management system 1000 includes authentication terminals 110 to 140, a locker 150, a shop 160, an authentication device 200, and an authentication information management device 300. The authentication terminals 110 to 140, the authentication device 200, and the authentication information management device 300 are connected via a network N. Here, the network N is a wired or wireless communication line, for example, the Internet. The authentication terminals 110 to 140, the locker 150, and the shop 160 are assumed to be installed in a park 100. The authentication device 200 and the authentication information management device 300 can be installed anywhere. The locker 150 and the shop 160 are examples of facilities where a payment service using face recognition is available. Other facilities where a payment service using face recognition is available include, for example, rental item payment machines, vending machines, museums, zoos, event venues, etc., but are not limited to these.

[0029] The authentication information management system 1000 is used, for example, as follows. In order to provisionally use (trial use) various payment services by face authentication in the park 100, the user U deposits a predetermined amount of cash into the authentication terminal 110 installed at the entrance of the park 100. The user U also takes a picture of his / her face using the authentication terminal 110, and provisionally registers the face image and the deposit amount in the authentication information management device 300. Since the registration is provisional, a privilege may be given to the user U. For example, the authentication information management device 300 may add a privilege amount to the deposit amount of the user U to set it as the payment available amount (payment balance). The authentication information management device 300 may hold a provisional registration history for each user, and may grant a privilege when the provisional registration is performed a certain number of times or less. After that, the user U enters the park 100, and makes a payment by face authentication when using a paid locker 150 in the park 100 or purchasing a product at the shop 160. At this time, the payment balance based on the amount deposited in advance is used for the payment. Furthermore, when the user U is successful in face authentication at the authentication terminal 140 installed at the exit of the park 100, the user U can delete the provisionally registered face image, etc. Furthermore, the user U can also perform a permanent registration including the face image, personal information, and payment information in order to permanently use various payment services using face authentication. Alternatively, the user U may continue (extend) the provisional registration and make an additional deposit, etc. Note that if the same user makes multiple provisional registrations, the above-mentioned bonus may not be given. Also, a separate bonus may be given at the time of the formal registration. Note that examples of use of the authentication information management system 1000 are not limited to these.

[0030] The authentication terminal 110 is an example of a registration terminal. The authentication terminal 110 is an information terminal installed at the entrance of the park 100. The authentication terminal 110 performs registration processing corresponding to the provisional registration (first registration type) and the main registration (second registration type) on the authentication information management device 300.

[0031] 4 is a block diagram showing the configuration of an authentication terminal 110 according to the present embodiment 2. The authentication terminal 110 includes a camera 41, a deposit acceptance unit 42, a cash storage unit 43, a storage unit 44, a memory 45, a communication unit 46, an input / output unit 47, and a control unit 48.

[0032] The camera 41 is an imaging device that takes an image of the user U under the control of the control unit 48. The deposit acceptance unit 42 accepts the deposit of cash, such as bills and coins, from the user U and stores the cash in the cash storage unit 43. The deposit acceptance unit 42 also tallies the deposited cash and notifies the control unit 48 of the total amount as the deposit amount. The cash storage unit 43 is an area for storing bills and coins. The memory unit 44 is a storage device in which a program 441 for implementing each function of the authentication terminal 110 is stored. The program 441 is a computer program in which at least a face information registration process, a provisional registration status inquiry process, and the like are implemented. The memory 45 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 48 is operating. The communication unit 46 is a communication interface with the network N. The input / output unit 47 includes a display device and an input device. The input / output unit 47 is, for example, a touch panel. The control unit 48 is a processor that controls the hardware of the authentication terminal 110. The control unit 48 loads the program 441 from the storage unit 44 into the memory 45 and executes it. In this way, the control unit 48 realizes the functions of an acquisition unit 481, a registration unit 482, a display control unit 483, an authentication control unit 484, and a payment processing unit 485.

[0033] The acquisition unit 481 accepts the selection of the registration type from the user U. The acquisition unit 481 also controls the camera 41 to capture an area including the face of the user U and acquires it as a face image. If the registration type is provisional registration, the acquisition unit 481 acquires the deposit amount notified from the deposit acceptance unit 42. If the registration type is full registration, the acquisition unit 481 requests the user U to input personal information and payment information, and acquires the input personal information and payment information. Here, the personal information is the name, address, date of birth, sex, etc. of the user U. The payment information is account information of a financial institution from which the payment amount is debited when making a payment for various payment services by face recognition, credit card information used to pay the payment amount, etc. The acquisition unit 481 may acquire the payment amount by input by a staff member of the park 100, etc.

[0034] When the registration type is temporary registration, the registration unit 482 transmits a temporary registration request including a facial image and a deposit amount to the authentication information management device 300. When the registration type is permanent registration, the registration unit 482 transmits a permanent registration request including a facial image, personal information, and payment information to the authentication information management device 300.

[0035] The display control unit 483 displays the reception screen and various notification information received from the authentication information management device 300 on the input / output unit 47. The reception screen is a screen that accepts registration for use of various payment services by face authentication (selection of registration type, input information such as personal information) and selection of provisional registration status inquiry. The provisional registration status includes the payment balance included in the provisional registration information. Therefore, the provisional registration status inquiry may be called a balance inquiry. Details of the provisional registration status will be described later. The display control unit 483 also displays on the screen request messages such as transition to full registration, additional payment, and continuation of provisional registration, confirmation messages for deleting provisional registration, and selection buttons for these. The display control unit 483 also accepts input (selection, input information, etc.) from the user U on the screen and notifies the control unit 48 of the selection and input contents.

[0036] When the temporary registration status inquiry is selected, the authentication control unit 484 transmits a temporary registration status inquiry request including a facial image to the authentication information management device 300. In addition, the authentication control unit 484 may transmit a facial authentication request including a facial image to the authentication information management device 300 or the authentication device 200. In other words, the authentication control unit 484 controls facial authentication of the user U. In addition, the authentication control unit 484 transmits various processing requests in response to notifications from the display control unit 483 to the authentication information management device 300.

[0037] The payment processing unit 485 transmits a payment request including a facial image and a payment amount to the authentication information management device 300 in order to settle a predetermined payment amount through a payment service using facial recognition. Since the authentication terminal 110 is a terminal installed at the entrance of the park 100, the payment amount may be an admission fee to the park 100.

[0038] Since the authentication terminal 110 is at least a registration terminal, it is sufficient if it is provided with at least the acquisition unit 481, the registration unit 482, and the display control unit 483 of the control unit 48. In other words, the authentication control unit 484 and the payment processing unit 485 are not essential components of the registration terminal.

[0039] The authentication terminals 120 to 140 have the same configuration as that shown in Fig. 4. The authentication terminals 120 and 130 are examples of payment terminals. Therefore, it is sufficient for the authentication terminals 120 and 130 to have at least the acquisition unit 481, the display control unit 483, the authentication control unit 484, and the payment processing unit 485 of the control unit 48. Moreover, the authentication terminal 140 is an authentication terminal installed at the exit of the park 100. Therefore, it is sufficient for the authentication terminal 140 to have at least the acquisition unit 481, the display control unit 483, and the authentication control unit 484 of the control unit 48.

[0040] Returning to FIG. 3, the description will be continued. The authentication terminal 120 is an information terminal connected so as to be linked with the opening and closing of the lockers 150 for which a fee is charged. For example, the user U puts his / her luggage in an empty space of the lockers 150, closes the door, and inputs the locker number, etc., to the authentication terminal 120. The authentication terminal 120 acquires a face image of the user U, and transmits a face authentication request including the face image to the authentication information management device 300. Then, when the user U succeeds in face authentication, the authentication terminal 120 locks the door of the locker corresponding to the locker number. Also, when the user U performs an operation to unlock the locker door, the authentication terminal 120 acquires a face image of the user U, and transmits a face authentication request including the face image (a request to pay the usage fee) to the authentication information management device 300. Then, when the user U succeeds in face authentication and the usage fee for the locker 150 is paid, the authentication terminal 120 unlocks a specific locker 150. The payment of the usage fee may be made when the locker is locked.

[0041] The authentication terminal 130 is an information terminal installed in the store 160. The authentication terminal 130 is, for example, a cash register terminal. For example, the user U scans the product code (payment amount, etc.) of the product with a scanner connected to the authentication terminal 130 to purchase the product. Alternatively, a store clerk at the store 160 may input the payment amount to the authentication terminal 130 using a scanner, input buttons, etc. The authentication terminal 130 accepts the scanned payment amount, acquires a facial image of the user U, and transmits a payment request including the facial image and the payment amount to the authentication information management device 300. Then, when the user U succeeds in the facial authentication and the payment amount is paid, the authentication terminal 130 displays the payment balance of the user U. In addition, the authentication terminal 130 displays various notification information described later.

[0042] The authentication terminal 140 is an information terminal installed at the exit of the park 100. The authentication terminal 140 may be installed anywhere in the park 100, for example, near the entrance to a toilet or near a bench. The authentication terminal 140 acquires a face image of the user U and transmits a provisional registration status inquiry request including the face image to the authentication information management device 300. Then, when the user U is successful in face authentication, the authentication terminal 140 receives the payment balance and various notification information of the user U and displays the payment balance and various notification information. The authentication terminal 140 may accept a selection operation or input information according to the notification information from the user U. In that case, the authentication terminal 140 transmits various processing requests according to the selection contents or input information to the authentication information management device 300. After that, the authentication terminal 140 receives and displays the processing results from the authentication information management device 300. The authentication terminals 110, 120, and 130 may also perform the provisional registration status inquiry request and various processing requests described above.

[0043] The authentication information management device 300 is an example of the above-mentioned authentication information management device 1. The authentication information management device 300 is an information processing device that performs temporary registration and final registration of face information, updating of temporary registration history, payment processing by face authentication, temporary registration status inquiry processing, extension and deletion of temporary registration, processing according to additional payment, etc. (processing of authentication information management method). The authentication information management device 300 may be redundantly configured with multiple servers, and each functional block may be realized by multiple computers.

[0044] Next, the authentication information management device 300 will be described in detail. Fig. 5 is a block diagram showing the configuration of the authentication information management device 300 according to the second embodiment. The authentication information management device 300 includes a storage unit 310, a memory 320, a communication unit 330, and a control unit 340. The storage unit 310 is an example of a storage device such as a hard disk or a flash memory. The storage unit 310 stores a program 311, provisional registration information 312, a provisional registration history 313, and regular registration information 314. The program 311 is a computer program in which the processing of the authentication information management method according to the second embodiment is implemented.

[0045] The provisional registration information 312 is information that associates facial feature information 3121, payment balance 3122, and expiration information 3123. The facial feature information 3121 is a collection of feature points extracted from a face image. The payment balance 3122 is an amount available for payment for a payment service using facial recognition. The expiration information 3123 is information for determining the expiration date of the provisional registration information 312. The expiration information 3123 is, for example, the registration date and time of the provisional registration information 312, the validity period, the expiration date and time (expiration date and time), etc.

[0046] The temporary registration history 313 is information for managing the registration history of the temporary registration information 312. The temporary registration history 313 is information in which facial feature information 3131, the number of temporary registrations 3132, and the benefit history 3133 are associated with each other. The facial feature information 3131 is information equivalent to the facial feature information 3121 described above. The number of temporary registrations 3132 is the number of times the temporary registration information has been registered for the user corresponding to the facial feature information 3131. The number of temporary registrations 3132 may be incremented even when the expiration date of the temporary registration information is extended. The benefit history 3133 is a history of benefit information granted to the user corresponding to the facial feature information 3131. The benefit information is an amount of money, points, etc. Points are information having a pseudo-monetary value that can be exchanged for a product or service. Alternatively, the benefit information may be an electronic coupon, electronic money, cryptocurrency, electronic ticket, etc., other than points. That is, the privilege information is electronic data indicating economic value, and includes information having a monetary value equivalent to currency and information having a pseudo-monetary value. The privilege history 3133 is a cumulative value of the privilege information granted to the same user. For example, when the privilege information is an amount of money, the privilege history 3133 is a total value of the amount of money added as a privilege granted to the user corresponding to the facial feature information 3131. Furthermore, the provisional registration history 313 may include the provisional registration date and time for each provisional registration. Alternatively, the provisional registration history 313 may be information in which the facial feature information and the provisional registration date and time for each provisional registration are associated with each other. Furthermore, the provisional registration history 313 may include a history of the amount of deposit. For example, the provisional registration history 313 may be a pair of the deposit date and the amount of deposit, or may be a cumulative amount of the amount of deposit.

[0047] The main registration information 314 is information in which a user ID 3141, personal information 3142, payment information 3143, and privilege information 3144 are associated with each other. The user ID 3141 is user identification information managed in association with facial feature information managed in the authentication device 200 described later. Therefore, the main registration information 314 can uniquely identify facial feature information via the user ID 3141, and can essentially be said to be information in which facial feature information, personal information 3142, payment information 3143, and privilege information 3144 are associated with each other. The personal information 3142 is the user's name, address, date of birth, sex, etc. The payment information 3143 is account information of a financial institution from which the payment amount is debited when making a payment for various payment services using face authentication, credit card information used to pay the payment amount, etc. The privilege information 3144 is the above-mentioned privilege information, and is privilege information granted in response to various payments made at the time of main registration or after main registration.

[0048] The memory 320 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information during operation of the control unit 340. The communication unit 330 is a communication interface with the network N.

[0049] The control unit 340 is a processor, that is, a control device, that controls each component of the authentication information management device 300. The control unit 340 loads the program 311 from the storage unit 310 into the memory 320, and executes the program 311. In this way, the control unit 340 realizes the functions of an acquisition unit 341, a registration unit 342, an authentication control unit 343, a settlement unit 344, a usage control unit 345, and an update unit 346.

[0050] The acquisition unit 341 is an example of the above-mentioned acquisition unit 11. The acquisition unit 341 receives (acquires) from the authentication terminals 110 to 140 a provisional registration request, a main registration request, a payment request, an additional deposit request, a provisional registration status inquiry request, a provisional registration continuation and deletion request, a transition request from provisional registration to main registration (main registration transition request), and a payment balance update request.

[0051] The registration unit 342 is an example of the registration unit 12 described above. The registration unit 342 generates the temporary registration information 312 and the temporary registration history 313 in response to the temporary registration request, and registers them in the storage unit 310. In particular, the registration unit 342 may register the temporary registration information 312 to which the predetermined privilege information is assigned when the information included in the temporary registration request satisfies a second condition. Here, the second condition may be, for example, that the facial feature information based on the facial image included in the temporary registration request is not registered in the temporary registration information 312. Alternatively, the second condition may be that the number of temporary registrations 3132 is equal to or less than a predetermined number, or that the privilege history 3133 is equal to or less than a predetermined value, even if the facial feature information based on the facial image included in the temporary registration request is registered in the temporary registration information 312. Alternatively, the second condition may be that the number of times the privilege information is assigned is equal to or less than an upper limit, that it is within a predetermined period from the first temporary registration date of the user, and that the total amount of privileges in the privilege history 3133 is equal to or less than a predetermined amount. In addition, when the predetermined number of times is one time, that is, when the special benefit is given only to the first temporary registration request for a specific user, temporary registration history 313 may manage only facial feature information 3131, and may not require temporary registration count 3132 and special benefit history 3133. In addition, the second condition is not limited to these.

[0052] The bonus information may be provided as follows. For example, if the bonus information is a predetermined monetary amount (bonus amount), the registration unit 342 adds the bonus amount to the deposit amount included in the provisional registration request to calculate the payment balance, thereby providing the bonus information. Alternatively, if the bonus information is points or the like other than a monetary amount, the registration unit 342 may provide a predetermined number of points as bonus information, and include the provided bonus information in the provisional registration information 312. The provided points may be used when making a payment by face authentication.

[0053] Furthermore, registration in the temporary registration history may be performed as follows. For example, in response to the registration of temporary registration information 312, registration unit 342 sets facial feature information 3121 to facial feature information 3131, adds "1" to the number of temporary registrations 3132, adds the granted privilege information to privilege history 3133, and registers the result in temporary registration history 313. Then, registration unit 342 grants privilege information when temporary registration history 313 corresponding to biometric information (facial feature information) included in a subsequent temporary registration request acquired after the registration of temporary registration information 312 satisfies a second condition.

[0054] Alternatively, the temporary registration history 313 may not require either the temporary registration count 3132 or the privilege history 3133. That is, the registration unit 342 registers the number of temporary registration requests (temporary registration count 3132) of the user U or the accumulated value of the granted privilege information (privilege history 3133) in the temporary registration history. Then, when a subsequent temporary registration request is acquired, the registration unit 342 may determine that the second condition is satisfied if the number of requests is equal to or less than a predetermined number or the accumulated value is equal to or less than a predetermined value.

[0055] Note that even if the acquisition unit 341 acquires a provisional registration request, the registration unit 342 may not perform provisional registration if the second condition is not satisfied. For example, the user U may be granted a privilege for provisional registration up to three times, but may not be able to perform provisional registration if the total amount of the privilege exceeds an upper limit of several thousand yen. Furthermore, if the second condition is not satisfied, the registration unit 342 may transmit a request for transition to permanent registration (described later) to the request source.

[0056] Furthermore, when the acquisition unit 341 acquires a formal registration request, the registration unit 342 generates the formal registration information 314 and registers it in the storage unit 310. Specifically, the registration unit 342 transmits a face information registration request including a face image included in the formal registration request to the authentication device 200. Then, the registration unit 342 acquires a user ID issued in response to the registration of face information from the authentication device 200. Then, the registration unit 342 generates the formal registration information 314 by associating the acquired user ID 3141 with the personal information 3142 and the payment information 3143 included in the formal registration request. At this time, the registration unit 342 may generate the formal registration information 314 by adding the privilege information 3144. For example, when the user U makes a formal registration request without performing provisional registration, the registration unit 342 may add the privilege information 3144. In other words, it is not essential to give a privilege at the time of formal registration. In other words, the registration unit 342 may register the formal registration information to which the predetermined privilege information is added when the user has not made a provisional registration request in the past. For example, the registration unit 342 extracts facial feature information from a face image included in the formal registration request, and compares the extracted facial feature information with facial feature information 3131 in the temporary registration history 313. If there is no facial feature information whose matching degree in the facial feature information comparison is equal to or exceeds a threshold, the registration unit 342 may determine that the user has not made a temporary registration request in the past.

[0057] Furthermore, when the acquisition unit 341 acquires a request to move to main registration, the registration unit 342 generates main registration information 314 as described above and registers it in the storage unit 310. The registration unit 342 may identify the corresponding temporary registration information 312 from the request to move to main registration, and transmit a face information registration request including facial feature information 3121 included in the temporary registration information 312. In other words, the temporarily registered biometric information may be used for main registration. Furthermore, in the case of a request to move to main registration, the registration unit 342 may generate main registration information 314 by adding bonus information 3144.

[0058] The authentication control unit 343 is an example of the above-mentioned authentication control unit 13. When the acquisition unit 341 acquires a payment request or a temporary registration status inquiry request, the authentication control unit 343 controls face authentication using the facial feature information 3121 included in the temporary registration information 312. In addition, when the acquisition unit 341 acquires various processing requests other than the temporary registration request and the regular registration request, the authentication control unit 343 may similarly control face authentication using the facial feature information 3121 included in the temporary registration information 312. Specifically, the authentication control unit 343 extracts (calculates) facial feature information from a face image included in the request, collates the extracted facial feature information with the facial feature information 3121 included in the temporary registration information 312, and calculates the degree of match. When the degree of match is equal to or greater than a threshold, the authentication control unit 343 determines that face authentication (of the temporary registration information) has been successful. On the other hand, when the degree of match is less than the threshold, the authentication control unit 343 causes the authentication device 200 to perform face authentication on the face image included in the request. For example, the authentication control unit 343 transmits a face authentication request including a face image to the authentication device 200 via the network N, and receives a face authentication result from the authentication device 200. The authentication control unit 343 may detect a face area of ​​the user from the face image and include an image of the face area in the face authentication request. Alternatively, the authentication control unit 343 may extract facial feature information from the face area and include the facial feature information in the face authentication request. The authentication control unit 343 determines whether face authentication has been successful from the received face authentication result. If the face authentication result indicates success, the authentication control unit 343 determines that face authentication (of the permanent registration information) has been successful, and identifies a user ID included in the face authentication result. Alternatively, if the request includes a session ID described later, the authentication control unit 343 may identify (identify) the provisional registration information 312 or the permanent registration information 314 that has been successful and identified by face authentication corresponding to a previously performed session ID. The authentication control unit 343 may prevent the provisional registration information 312, the use of which has been restricted by the usage control unit 345, from being used when controlling biometric authentication. In other words, authentication control unit 343 does not need to use temporary registration information 312, the use of which is restricted by usage control unit 345, as a target for biometric authentication matching.

[0059] The settlement unit 344 is an example of the settlement unit 14 described above. When the face authentication of the provisional registration information based on the settlement request is successful, the settlement unit 344 judges whether the settlement balance of the user who has succeeded in face authentication is equal to or greater than the payment amount included in the settlement request. In other words, the settlement unit 344 judges whether the settlement balance is insufficient for the payment amount. When the settlement balance is equal to or greater than the payment amount, the settlement unit 344 settles the payment amount by using the settlement balance 3122 of the provisional registration information 312. Specifically, the settlement unit 344 updates the provisional registration information 312 by subtracting the payment amount from the settlement balance. Note that, when the privilege information is points or the like, the settlement unit 344 may determine the payment amount by subtracting the monetary value indicated by the points from the payment amount. On the other hand, when the settlement balance is less than the payment amount, that is, when the settlement balance is insufficient for the payment amount, the settlement unit 344 notifies the requester of the settlement request (the settlement terminal) of the shortfall. When the settlement unit 344 receives an additional deposit amount from the requester, it settles the payment amount using the settlement balance and the additional deposit amount. Note that the settlement unit 344 may make it impossible to use the settlement balance of the provisional registration information 312, the use of which is restricted by the usage control unit 345, when making a payment.

[0060] The use control unit 345 is an example of the above-mentioned use control unit 15. The use control unit 345 judges whether the provisional registration information 312 satisfies the above-mentioned first condition (condition for restricting use of provisional registration information), and if the first condition is satisfied, restricts the use of the provisional registration information 312. Here, the first condition is, for example, that a predetermined period (several days, one week, etc.) has passed since the registration of the provisional registration information, that a predetermined timing (after the closing time of the business day, etc.) has arrived, and that the settlement balance after settlement is equal to or less than a predetermined amount. Furthermore, the first condition may be that the settlement balance is equal to or less than a predetermined amount at a predetermined timing. For example, the use control unit 345 judges, at any timing, whether the expiration information 3123 of the provisional registration information 312 has expired the expiration date of the provisional registration information. Specifically, if the expiration information 3123 is the provisional registration date and time and a predetermined period has passed since the provisional registration date and time, the use control unit 345 judges that the provisional registration information 312 satisfies the first condition. Furthermore, if the expiration information 3123 is a validity period and the validity period has passed, the usage control unit 345 determines that the provisional registration information 312 satisfies the first condition. If the expiration information 3123 is an expiration date and time and the current date and time is after the expiration date and time, the usage control unit 345 determines that the provisional registration information 312 satisfies the first condition.

[0061] Alternatively, the usage control unit 345 may determine that the first condition is satisfied when a predetermined timing arrives, such as after the closing time of the day. In this case, the usage control unit 345 may delete all of the provisional registration information 312 stored in the storage unit 310.

[0062] In addition, the usage control unit 345 may determine that the provisional registration information, for which a predetermined timing has arrived and the payment balance is equal to or less than a predetermined amount, satisfies the first condition. Alternatively, the usage control unit 345 may determine that the provisional registration information, for which the payment balance is equal to or less than a predetermined amount after the payment by the payment unit 344, satisfies the first condition.

[0063] Then, when the temporary registration information 312 satisfies the first condition, the use control unit 345 deletes the corresponding temporary registration information 312 from the storage unit 310. Therefore, it can be said that the use control unit 345 has restricted the use of the corresponding temporary registration information 312 in the face authentication of the temporary registration information by the authentication control unit 343. Alternatively, the use control unit 345 may set a flag indicating that the temporary registration information 312 is unusable in the temporary registration information 312. In this case, the authentication control unit 343 cannot use the facial feature information 3121 of the temporary registration information 312 for which the flag indicating that the temporary registration information is unusable is set in the face authentication of the temporary registration information. Alternatively, the payment unit 344 may not use the payment balance 3122 of the temporary registration information 312 for which the flag indicating that the temporary registration information is unusable is set in the payment process.

[0064] When the provisional registration information satisfies the third condition, the update unit 346 notifies the corresponding user of the fact and updates the provisional registration information based on a response from the user. Here, the third condition can be at least one of a condition for notifying the user, a condition for extending the provisional registration deadline, a condition for updating the provisional registration information, a condition for moving to a full registration, etc. For example, the third condition can be a predetermined period of time that has passed since provisional registration, a payment balance that is equal to or less than a predetermined amount, a predetermined period of time that has elapsed since the provisional registration, the number of provisional registrations that has exceeded a predetermined number of times, a privilege history that has exceeded a predetermined value, a request to inquire about the provisional registration status, etc.

[0065] Furthermore, when the acquisition unit 341 acquires a provisional registration status inquiry request, the update unit 346 notifies the authentication terminal that is the request source. Alternatively, when the acquisition unit 341 acquires a provisional registration status inquiry request, the update unit 346 may determine whether or not a third condition other than the provisional registration status inquiry request is satisfied, and may notify the authentication terminal according to the determination result. Furthermore, following the payment by the payment unit 344, the update unit 346 may determine whether or not a third condition is satisfied, and may notify the payment terminal if the third condition is satisfied. In these cases, since a user (who has succeeded in face authentication of provisional registration information) is present in front of the authentication terminal or the payment terminal, the notification by the update unit 346 to the request source can be said to be a notification to the user.

[0066] The notification information notified by the update unit 346 may include, for example, that a predetermined period has passed since the provisional registration, that the payment balance is equal to or less than a predetermined amount, that it is within a predetermined period from the expiration date of the provisional registration information, etc. The notification information may also include a message encouraging continuation of provisional registration, a message confirming the deletion of provisional registration, a message encouraging additional payment, a message encouraging transition to full registration, etc. Furthermore, the notification information may include a message informing the user that special information will be granted by continuing provisional registration, making additional payment, or transitioning to full registration. The notification information also includes a provisional registration status. The provisional registration status is information indicating a current status including the provisional registration information and provisional registration history of a user who has succeeded in face authentication of the provisional registration information. The provisional registration status may include at least the payment balance.

[0067] When the response from the user indicates a request to continue the provisional registration, the update unit 346 updates the available period (expiration information 3123) of the corresponding provisional registration information so as to extend it. Furthermore, the update unit 346 may extend the available period and add predetermined benefit information to update the provisional registration information. When the response from the user indicates a request to delete the provisional registration, the update unit 346 deletes the corresponding provisional registration information 312 in addition to the formal registration process by the registration unit 342 when the response from the user indicates a request to update the payment balance, the update unit 346 updates the payment balance 3122 of the corresponding provisional registration information by adding the additional deposit amount. Note that when the response from the user indicates a request to continue the provisional registration and the extension deadline of the provisional registration has passed or the extended cumulative period has exceeded the upper limit, the update unit 346 may return a message indicating that the extension is not possible. Furthermore, if the response from the user indicates a payment balance update request but the additional payment deadline has passed or the total amount of additional payments exceeds the upper limit, the update unit 346 may reply that additional payment is not possible. Furthermore, if the response from the user indicates a request to continue provisional registration or a payment balance update request, and in either of the above cases, the update unit 346 may reply a message encouraging transition to full registration.

[0068] Returning to FIG. 3, the explanation will be continued. The authentication device 200 is an information processing device that stores facial feature information of a user who performs main registration. In response to a facial authentication request received from the outside, the authentication device 200 compares the facial image or facial feature information included in the request with the facial feature information of each user, and returns the comparison result (authentication result) to the request source.

[0069] FIG. 6 is a block diagram showing the configuration of an authentication device 200 according to the second embodiment. The authentication device 200 includes a face information DB (DataBase) 210, a face detection unit 220, a feature point extraction unit 230, a registration unit 240, and an authentication unit 250. The face information DB 210 stores a user ID 211 and face feature information 212 of the user ID in association with each other. The face feature information 212 is a set of feature points extracted from a face image. The authentication device 200 may delete the face feature information 212 in the face feature DB 210 in response to a request from a registered user of the face feature information 212. Alternatively, the authentication device 200 may delete the face feature information 212 after a certain period of time has elapsed since the main registration.

[0070] The face detection unit 220 detects a face area included in a registration image for registering face information, and outputs the face area to the feature point extraction unit 230. The feature point extraction unit 230 extracts feature points from the face area detected by the face detection unit 220, and outputs face feature information to the registration unit 240. The feature point extraction unit 230 also extracts feature points included in a face image received from the authentication terminal 110 or the authentication information management device 300, and outputs the face feature information to the authentication unit 250.

[0071] The registration unit 240 issues a new user ID 211 when registering the facial feature information. The registration unit 240 registers the issued user ID 211 in the facial feature information DB 210 in association with the facial feature information 212 extracted from the registered image. The authentication unit 250 performs face authentication using the facial feature information 212. Specifically, the authentication unit 250 compares the facial feature information extracted from the face image with the facial feature information 212 in the facial information DB 210. If the comparison is successful, the authentication unit 250 specifies the user ID 211 associated with the compared facial feature information 212. The authentication unit 250 returns the presence or absence of a match of the facial feature information to the request source as a facial authentication result. The presence or absence of a match of the facial feature information corresponds to the success or failure of authentication. Incidentally, the facial feature information matches (matches) when the degree of match is equal to or greater than a threshold. Furthermore, if the facial authentication is successful, the facial authentication result includes the specified user ID.

[0072] FIG. 7 is a flowchart showing the flow of face information registration processing by the registration terminal (authentication terminal 110) according to the second embodiment. First, the authentication terminal 110 displays a reception screen. The reception screen displays a "provisional registration" button and a "full registration" button for selecting a registration type for registration information including a face image of a user in order to use a payment service by face recognition within the park 100. The reception screen may also display that bonus information will be granted in the case of the first "provisional registration" or "full registration." The bonus information may, for example, be that 500 yen will be added to the payment balance as a bonus amount.

[0073] Then, the acquisition unit 481 of the authentication terminal 110 accepts the selection of the registration type by the operation of the user U (S101). Next, the acquisition unit 481 judges the registration type (S102). If the registration type is provisional registration, the acquisition unit 481 acquires a face image of the user U captured by the camera 41 (S103). Then, the authentication terminal 110 prompts the user U to deposit a predetermined amount via a reception screen or voice. The predetermined amount may be, for example, 1000 yen. The deposit acceptance unit 42 accepts a deposit of cash equivalent to the predetermined amount from the user U (S104). The deposit acceptance unit 42 stores the deposited cash in the cash storage unit 43, tallies the amount of deposit, and notifies the control unit 48. As a result, the acquisition unit 481 acquires the amount of deposit. Then, the registration unit 482 transmits a temporary registration request including the face image acquired in step S103 and the deposit amount acquired in step S104 to the authentication information management device 300 via the network N (S105).

[0074] If the registration type is formal registration in step S102, the acquisition unit 481 acquires a facial image of the user U captured by the camera 41 (S106). Then, the authentication terminal 110 displays input fields for personal information and payment information on the reception screen and requests the user U to input these. The acquisition unit 481 accepts the personal information and payment information input by the user U via the reception screen (S107). Then, the registration unit 482 transmits a formal registration request including the facial image acquired in step S106 and the personal information and payment information acquired in step S107 to the authentication information management device 300 via the network N (S108). Note that steps S103 and S106 may be executed before step S101.

[0075] 8 is a flowchart showing the flow of the provisional registration process according to the second embodiment. First, the acquisition unit 341 of the authentication information management device 300 receives a provisional registration request from the authentication terminal 110 via the network N (S301). The acquisition unit 341 may receive various processing requests from the authentication terminal 110, etc., determine the type of the received request, and determine that the request is a provisional registration request. The determination of the type of the received request by the acquisition unit 341 is similar to that in other processes.

[0076] The registration unit 342 acquires a face image from the received temporary registration request, and extracts facial feature information from the face image. Then, the registration unit 342 determines whether the extracted facial feature information exists in the facial feature information 3131 of the temporary registration history 313 (S302). Specifically, the registration unit 342 compares the extracted facial feature information with each facial feature information 3131 of the temporary registration history 313, calculates the degree of agreement, and determines whether the degree of agreement is equal to or greater than a threshold. If the degree of agreement of any of the facial feature information 3131 is less than the threshold, the registration unit 342 determines that the facial feature information does not exist in the temporary registration history 313. If there is facial feature information 3131 whose degree of agreement is equal to or greater than the threshold, the registration unit 342 determines that the facial feature information exists in the temporary registration history 313. If the facial feature information does not exist in the temporary registration history 313, this indicates that the user identified by the extracted facial feature information has not performed temporary registration in the past, that is, the user is about to perform the first temporary registration. In this case, the process proceeds to step S304. On the other hand, if the facial feature information exists in the temporary registration history 313 in step S302, the registration unit 342 determines whether the number of temporary registrations is equal to or less than a predetermined number (S303). Specifically, the registration unit 342 identifies the number of temporary registrations 3132 associated with the facial feature information 3131 whose degree of matching with the extracted facial feature information is equal to or greater than a threshold (if there are multiple pieces of facial feature information, the one with the highest degree of matching). Then, the registration unit 342 determines whether the identified number of temporary registrations 3132 is equal to or less than a predetermined number. For example, the predetermined number may be three times. Note that instead of step S303, the registration unit 342 may determine whether the cumulative value of the reward amount in the reward history 3133 is equal to or less than a predetermined value. For example, in a case where the reward amount is reduced as the number of temporary registrations increases, or a bonus is awarded upon payment for a predetermined product, the registration unit 342 may make a determination based on the reward award history instead of the number of temporary registrations.

[0077] If the answer is NO in step S302 or YES in step S303, the registration unit 342 adds the bonus amount to the deposit amount included in the provisional registration request to calculate the settlement balance (S304). The bonus to be awarded may be points or the like, as described above. The registration unit 342 may also determine the bonus amount according to the number of provisional registrations 3132 or the bonus history 3133. For example, the registration unit 342 may determine to reduce the bonus amount as the number of provisional registrations increases.

[0078] If the answer is NO in step S303, the registration unit 342 sets the deposit amount included in the provisional registration request as the settlement balance (S305). If the answer is NO in step S303, for example, if the number of provisional registrations exceeds a predetermined number, or if the cumulative value of the bonus amount exceeds a predetermined value, the registration unit 342 does not need to perform provisional registration.

[0079] After step S304 or S305, the registration unit 342 generates temporary registration information 312 by associating the extracted facial feature information 3121, the payment balance 3122 of step S304 or S305, and the deadline information 3123. The registration unit 342 may determine the deadline information 3123 according to the date and time of receiving the temporary registration request. Then, the registration unit 342 registers the generated temporary registration information 312 in the storage unit 310 (S306). The registration unit 342 also generates temporary registration history 313 by associating the facial feature information 3121 included in the generated temporary registration information 312, the temporary registration count 3132, and the privilege history 3133. The registration unit 342 sets the temporary registration count 3132 and the privilege history 3133 according to step S304. For example, in the case of the first temporary registration (NO in step S302), the registration unit 342 sets "1" to the number of temporary registrations 3132 and sets the bonus amount added in step S304 to the bonus history 3133. Then, the registration unit 342 registers the temporary registration history 313 (S307). Also, if the number of times is less than the predetermined number from the second time onwards (YES in step S303), the registration unit 342 adds "1" to the number of temporary registrations 3132 of the temporary registration history 313 identified in step S302, and adds the bonus amount added in step S304 to the bonus history 3133, thereby updating the temporary registration history 313.

[0080] FIG. 9 is a flowchart showing the flow of the main registration process according to the second embodiment. First, the acquisition unit 341 of the authentication information management device 300 receives a main registration request from the authentication terminal 110 via the network N (S311). Then, the registration unit 342 transmits a face information registration request including a face image included in the main registration request to the authentication device 200 via the network N (S312). Then, the registration unit 342 acquires a user ID issued in response to the registration of face information from the authentication device 200 (S313). Then, the registration unit 342 assigns reward information 3144 (S314). For example, the registration unit 342 may assign a predetermined value of points that can be used for payment by face authentication as reward information. Also, a reward does not necessarily have to be assigned in the case of main registration. The registration unit 342 generates main registration information 314 by associating the acquired user ID 3141 with the personal information 3142 and payment information 3143 included in the main registration request and the assigned reward information 3144. Then, the registration unit 342 registers the generated main registration information 314 in the storage unit 310 (S315).

[0081] 10 is a flowchart showing the flow of face information registration processing by the authentication device 200 according to the second embodiment. Here, an information registration terminal (not shown) photographs the body including the face of a user, and transmits a face information registration request including the photographed image (registration image) to the authentication device 200 via the network N. The information registration terminal is, for example, an information processing device such as a personal computer, a smartphone, or a tablet terminal. For example, the information registration terminal may be the authentication terminal 110 or the like. Here, the information registration terminal is assumed to be the authentication information management device 300 that has accepted the face information registration request from the authentication terminal 110 or the like.

[0082] First, the authentication device 200 receives a face information registration request (S201). For example, the authentication device 200 receives the face information registration request from the authentication information management device 300 via the network N. Next, the face detection unit 220 detects a face area from a face image included in the face information registration request (S202). Then, the feature point extraction unit 230 extracts feature points (facial feature information) from the face area detected in step S202 (S203). Then, the registration unit 240 issues a user ID 211 (S204). Then, the registration unit 240 associates the extracted facial feature information 212 with the issued user ID 211 and registers them in the face information DB 210 (S205). After that, the registration unit 240 returns the issued user ID 211 to the request source (information registration terminal, for example, the authentication information management device 300) (S206).

[0083] FIG. 11 is a flowchart showing the flow of payment processing by the authentication terminal 130 according to the second embodiment. Here, it is assumed that when the user U purchases a product in the shop 160, payment is made by face authentication via the authentication terminal 130. First, the acquisition unit 481 of the authentication terminal 130 acquires the payment amount (S111). For example, the authentication terminal 130 acquires the payment amount from a product code read by a connected scanner. Next, the acquisition unit 481 acquires a face image of the user U photographed by the camera 41 (S112). Then, the payment processing unit 485 transmits a payment request including the payment amount acquired in step S111 and the face image acquired in step S112 to the authentication information management device 300 via the network N (S113).

[0084] Next, a process after the authentication information management device 300 receives a payment request will be described. Fig. 12 is a flowchart showing the flow of payment processing by the authentication information management device 300 according to the second embodiment. First, the acquisition unit 341 receives a payment request from the authentication terminal 130 via the network N (S321). At this time, the authentication information management device 300 may issue a session ID for identifying the payment processing when starting the following payment processing.

[0085] Next, the authentication control unit 343 controls face authentication using the facial feature information 3121 included in the temporary registration information 312 (S322). Specifically, as described above, the authentication control unit 343 extracts facial feature information from the face image included in the request, and performs face authentication by matching it with the facial feature information 3121 included in the temporary registration information 312. Then, the authentication control unit 343 determines whether or not the face authentication of the temporary registration information has been successful (S323).

[0086] If the facial authentication of the temporary registration information is successful, the settlement unit 344 determines whether or not the payment balance of the user whose facial authentication has been successful is equal to or greater than the payment amount included in the payment request (S324). Specifically, the settlement unit 344 identifies the payment balance 3122 associated with the facial feature information 3121 of the user whose facial authentication has been successful. Then, the settlement unit 344 determines whether or not the identified payment balance 3122 is equal to or greater than the payment amount included in the payment request.

[0087] If the payment balance is equal to or greater than the payment amount in step S324, the payment unit 344 settles the payment amount using the payment balance 3122 in the provisional registration information 312 (S328). Specifically, the payment unit 344 subtracts the payment amount from the identified payment balance 3122 and updates the provisional registration information 312. Thereafter, the payment unit 344 transmits a payment completion notice including the updated payment balance 3122 to the authentication terminal 130, which is the request source, via the network N (S329).

[0088] On the other hand, if the payment balance is less than the payment amount in step S324, the payment unit 344 calculates the shortfall by subtracting the payment balance from the payment amount. The payment unit 344 then transmits a shortfall notice including the shortfall to the authentication terminal 130, which is the request source, via the network N (S325). At this time, the payment unit 344 may include the session ID issued above in the shortfall notice.

[0089] Returning to FIG. 11, the explanation will be continued. The acquisition unit 481 of the authentication terminal 130 receives a response (notification) to the payment request of step S113 from the authentication information management device 300 via the network N (S114). The acquisition unit 481 determines the type of the received notification (S115). If the type of notification is a payment completion notification, the display control unit 483 displays the fact that the payment is completed (S119). In particular, if the payment completion notification includes the payment balance, that is, if the payment was made using the provisional registration information, the display control unit 483 displays the payment balance included in the notification together with the fact that the payment is completed.

[0090] If the type of the notification is a balance shortage notification in step S115, the display control unit 483 displays the shortage amount and an additional deposit request message included in the notification (S116). In response to this, the deposit acceptance unit 42 of the authentication terminal 130 accepts additional deposit of cash from the user U (S117). The deposit acceptance unit 42 stores the deposited cash in the cash storage unit 43, tallies the additional deposit amount, and notifies the control unit 48. As a result, the acquisition unit 481 acquires the additional deposit amount. Then, the settlement processing unit 485 transmits an additional deposit request including the additional deposit amount acquired in step S117 to the authentication information management device 300 via the network N (S118). At this time, the settlement processing unit 485 may include the face image acquired in step S112 in the additional deposit request. Alternatively, if the balance shortage notification includes a session ID, the settlement processing unit 485 may include the session ID in the additional deposit request. Then, the process returns to step S114.

[0091] Returning to Fig. 12, the explanation will be continued. The acquisition unit 341 of the authentication information management device 300 receives an additional deposit request from the authentication terminal 130 (S326). If the additional deposit request includes a facial image, the acquisition unit 341 may identify that the additional deposit request is an ongoing payment process by checking whether the facial image is the same as the facial image included in the payment request received in step S321. Alternatively, if the additional deposit request includes a session ID, the acquisition unit 341 may identify that the additional deposit request is an ongoing payment process if the session ID matches the session ID issued after step S321. Here, it is assumed that the additional deposit request is identified as an ongoing payment process.

[0092] Therefore, the settlement unit 344 calculates (updates) the settlement balance by adding the additional deposit amount included in the additional deposit request to the settlement balance 3122 identified in step S324 (S327). After that, the process returns to step S324 to continue the settlement process. For example, if the settlement balance is equal to or greater than the settlement amount (due to the additional deposit) in step S324, steps S328 and S329 are executed as described above. On the other hand, if the settlement balance is less than the settlement amount in step S324 (even after taking into account the additional deposit), steps S325 and subsequent steps are executed again. Note that if step S324 returns NO a certain number of times or more, the settlement unit 344 may transmit a notice of non-payment, including a reason of insufficient amount, to the authentication terminal 130 via the network N.

[0093] If face authentication of the temporary registration information fails in step S323, the authentication control unit 343 transmits a face authentication request including the face image included in the payment request to the authentication device 200 via the network N (S330).

[0094] FIG. 13 is a flowchart showing the flow of face authentication processing by the authentication device 200 according to the second embodiment. First, the authentication device 200 receives a face authentication request from the authentication information management device 300 via the network N (S211). The authentication device 200 may receive a face authentication request from the authentication terminal 110 or the like. Next, the authentication device 200 extracts face feature information from the face image included in the face authentication request in the same manner as in steps S202 and S203 described above. Then, the authentication unit 250 of the authentication device 200 compares the face feature information extracted from the face image included in the face authentication request with the face feature information 212 of the face information DB 210 (S212) and calculates the degree of match. Then, the authentication unit 250 determines whether the degree of match is equal to or greater than a threshold (S213). If the face feature information matches, that is, if the degree of match of the face feature information is equal to or greater than a threshold, the authentication unit 250 identifies the user ID 211 associated with the face feature information 212 (S214). Then, the authentication unit 250 returns the face authentication result including the fact that the face authentication was successful and the identified user ID 211 to the authentication information management device 300 via the network N (S215). If the degree of match is less than the threshold in step S213, the authentication unit 250 returns the face authentication result including the fact that the face authentication was unsuccessful to the authentication information management device 300 via the network N (S216).

[0095] Returning to FIG. 12, the description will be continued. The authentication control unit 343 of the authentication information management device 300 receives the face authentication result from the authentication device 200 (S331). The authentication control unit 343 judges whether or not the face authentication for the main registration is successful from the received face authentication result (S332). If the face authentication for the main registration is successful, the payment unit 344 settles the payment amount using the payment information 3143 of the main registration information 314 (S333). Specifically, first, the authentication control unit 343 identifies the user ID included in the face authentication result. Then, the payment unit 344 identifies the payment information 3143 associated with the identified user ID 3141 from the main registration information 314. Then, the payment unit 344 performs a payment process based on the identified payment information 3143. For example, the payment unit 344 transmits a payment request including the payment information 3143 and the payment amount to an external payment server (a server of a financial institution or credit card company) corresponding to the payment information 3143. Then, the settlement unit 344 receives the settlement result from the settlement server. After that, the settlement unit 344 transmits a settlement completion notification to the authentication terminal 130, which is the request source, via the network N (S334).

[0096] On the other hand, if the face authentication of the permanent registration fails in step S332, the settlement unit 344 transmits a settlement failure notification including the fact that the face authentication has failed to the authentication terminal 130, which is the request source, via the network N (S335). In this embodiment, an example is described in which the DB of the biometric information of the temporary registration (the temporary registration information 312 in the authentication information management device 300) and the DB of the biometric information of the permanent registration (the face information DB 210 in the authentication device 200) are managed in different storage devices. Therefore, in FIG. 12, a case is described in which the face authentication of the temporary registration information is performed first, and if the face authentication fails, the face authentication of the permanent registration information is performed. However, the order of the face authentication of the temporary registration information and the face authentication of the permanent registration information in FIG. 12 may be reversed. In that case, steps S330 to S334 are performed after step S321, and if NO in S332, steps S322 to S329 are performed, and if NO in S323, S335 is performed. Alternatively, face authentication of the provisional registration information and face authentication of the final registration information may be performed in parallel, and the successful face authentication may be used to make the payment. If both face authentications are successful, the payment using the final registration information may be given priority.

[0097] Returning to FIG. 11, the explanation will be continued. The acquisition unit 481 of the authentication terminal 130 receives a response (notification) to the payment request of step S113 from the authentication information management device 300 via the network N (S114). The acquisition unit 481 determines the type of the received notification (S115). Here, it is assumed that the type of notification is a payment failure notification. Therefore, the display control unit 483 displays the fact that payment is not possible and the reason included in the payment failure notification (failure to authenticate the face, insufficient amount, etc.) (S120).

[0098] Although the above describes the payment process by the authentication terminal 130 installed in the kiosk 160, the payment process by the authentication terminal 120 connected to the locker 150 is similar. However, in step S111 of Fig. 11, the authentication terminal 120 acquires a payment amount according to the type (size, etc.) of the locker to be locked or unlocked. In addition, in conjunction with step S119, the authentication terminal 120 locks or unlocks the corresponding locker. The payment process of Fig. 11 can also be applied to authentication terminals installed in vending machines, entrance gates of facilities, etc.

[0099] 14 is a flowchart showing a flow of processing according to the provisional registration status by the authentication terminal 140 according to the embodiment 2. Here, it is assumed that the user U inquires about the provisional registration status by face authentication via the authentication terminal 140 installed at the exit of the park 100. However, the processing according to the provisional registration status may be executable in the other authentication terminals 110 to 130.

[0100] First, the authentication terminal 140 displays a reception screen. The reception screen displays a “Check Provisional Registration Status” button for checking the payment balance that has been charged (prepaid) to use the facial recognition payment service in the park 100.

[0101] Then, the acquisition unit 481 of the authentication terminal 140 accepts selection of the "temporary registration status inquiry" button by the operation of the user U (S131). The acquisition unit 481 acquires a face image of the user U captured by the camera 41 (S132). Then, the authentication control unit 484 transmits a temporary registration status inquiry request including the face image acquired in step S132 to the authentication information management device 300 via the network N (S133).

[0102] Next, the processing after the authentication information management device 300 receives the provisional registration status inquiry request will be described. Fig. 15 is a flowchart showing the flow of processing in response to a provisional registration status inquiry by the authentication information management device 300 according to the second embodiment. First, the acquisition unit 341 receives the provisional registration status inquiry request from the authentication terminal 140 via the network N (S341). At this time, the authentication information management device 300 may issue a session ID for identifying the following processing when starting the processing.

[0103] Next, the authentication control unit 343 controls face authentication using the facial feature information 3121 included in the temporary registration information 312, based on the face image included in the temporary registration status inquiry request (S342). Then, the authentication control unit 343 determines whether or not face authentication of the temporary registration information is successful (S343). If face authentication of the temporary registration information fails in step S343, the authentication control unit 343 transmits a message to the authentication terminal 140, which is the request source, that the temporary registration status inquiry is not possible, via the network N (S351).

[0104] If the face authentication of the temporary registration information is successful in step S343, the authentication control unit 343 acquires the temporary registration status including the payment balance 3122 associated with the facial feature information 3121 of the user who has been successful in the face authentication (S344). Specifically, the authentication control unit 343 reads out the temporary registration information 312 and the temporary registration history 313 corresponding to the user who has been successful in the face authentication from the storage unit 310, and generates the temporary registration status. For example, the authentication control unit 343 identifies and calculates the first temporary registration date, the temporary registration period up to the current time, the number of temporary registrations, the cumulative value of the granted benefits, and the like from the expiration information 3123 and the temporary registration history 313, and includes these in the temporary registration status. In addition, the authentication control unit 343 may calculate the remaining value of each item until the use of the temporary registration information is restricted (the first condition is satisfied). That is, the authentication control unit 343 may calculate the remaining value up to the upper limit value of the use condition of the temporary registration information. For example, the authentication control unit 343 calculates the additional deposit amount that can be made before the use of the temporary registration information is restricted, the remaining period during which the temporary registration information can be used, the number of times that the expiration date can be extended or additional temporary registrations can be made, the number of benefits that can be granted, and the like. The authentication control unit 343 may then include the remaining value up to the upper limit of the usage conditions of the temporary registration information in the temporary registration status. The authentication control unit 343 then determines whether the payment balance of the user who has succeeded in face authentication is equal to or less than a predetermined amount (S345). If the payment balance is equal to or less than the predetermined amount, the authentication control unit 343 adds an additional deposit request to the notification information (S346). Note that if the conditions for granting benefits, such as the second condition, are met, the authentication control unit 343 may add a message to the notification information, together with the additional deposit request, informing the user that the benefit information will be granted.

[0105] After step S346 or if NO in S345, the authentication control unit 343 judges whether it is within a predetermined period before the expiration of the temporary registration period (S347). If it is within the predetermined period before the expiration of the temporary registration period, the authentication control unit 343 adds a request for temporary registration continuation to the notification information (S348). Note that if the privilege granting condition such as the second condition is satisfied, the authentication control unit 343 may add a message notifying the user that privilege information will be granted to the notification information together with the request for temporary registration continuation.

[0106] After step S348 or if NO in S347, the authentication control unit 343 adds a request to move to permanent registration to the notification information (S349). Note that in step S349, a request to move to permanent registration is always notified when a request to inquire about the temporary registration status is received. Instead, a request to move to permanent registration may be made when the number of temporary registrations is equal to or greater than a predetermined number. In this case, if NO in step S348 or S347, the authentication control unit 343 determines whether the number of temporary registrations exceeds a predetermined number. If the number of temporary registrations exceeds the predetermined number, the authentication control unit 343 may add a request to move to permanent registration to the notification information. Note that if a privilege granting condition such as the second condition is satisfied, the authentication control unit 343 may add a message notifying that privilege information will be granted to the notification information together with the request to move to permanent registration. Then, the authentication control unit 343 transmits the provisional registration status including the payment balance acquired (generated) in step S344 and the notification information added above to the authentication terminal 140, which is the request source, via the network N (S350). At this time, the authentication control unit 343 may include the session ID issued above in the notification information.

[0107] Returning to FIG. 14, the description will be continued. The acquisition unit 481 of the authentication terminal 140 receives the provisional registration state and the notification information from the authentication information management device 300 via the network N as a response to the provisional registration state inquiry request in step S133. Then, the display control unit 483 displays the received provisional registration state and the notification information (S134). For example, the display control unit 483 displays a message and a selection button (transition to formal registration) to prompt the user to move from provisional registration to formal registration in response to a formal registration move request included in the notification information. Also, when the notification information includes a request for additional payment, the display control unit 483 displays a message and a selection button (additional payment) to prompt the user to make an additional payment. Also, when the notification information includes a request to continue the provisional registration, the display control unit 483 displays a message and a selection button (continue provisional registration) to prompt the user to continue the provisional registration. Also, the display control unit 483 displays a message and a selection button (delete provisional registration) to confirm the deletion of the provisional registration. Furthermore, the display control unit 483 may display a message informing the user that special benefit information will be provided together with at least one of the request for transition to permanent registration, the request for additional payment, and the request for continued provisional registration.

[0108] 16 is a diagram showing a display example of the temporary registration status display screen 7 according to the present embodiment 2. The temporary registration status display screen 7 includes a face image 71, a temporary registration status 72, a remaining time until usage restrictions 73, a transition to permanent registration field 74, an additional payment field 75, a temporary registration continuation field 76, and a temporary registration deletion field 77. The face image 71 may be the face image acquired in step S132, or may be the face image included in the notification information as a result of successful face authentication in the authentication information management device 300. However, the face image 71 may be omitted from the temporary registration status display screen 7.

[0109] The provisional registration status 72 is information received in step S134, and is information indicating the current provisional registration status of the user U. The provisional registration status 72 includes a payment balance 721, a provisional registration date 722, a provisional registration period 723, a provisional registration count 724, and a history of granted benefits 725. However, the provisional registration status 72 only needs to include at least the payment balance 721. In the example of FIG. 16, the payment balance 721 is 300 yen, the provisional registration date 722 is X month X day 2021, the provisional registration period 723 is 10 days, the provisional registration count 724 is 2 times, and the history of granted benefits 725 indicates that 800 yen has been granted.

[0110] The remaining amount until the usage limit 73 is information received in step S134, and is the remaining value of each item until the usage limit of the current provisional registration of the user U is reached. The remaining amount until the usage limit 73 includes a depositable amount 731, a remaining period of the provisional registration 733, a remaining number of times for the provisional registration 734, and a bonus amount that can be given 735. However, the remaining amount until the usage limit 73 is not essential on the provisional registration status display screen 7. In the example of Fig. 16, the depositable amount 731 indicates that 1000 yen can be deposited, the remaining period of the provisional registration 733 indicates that 3 days remain, the remaining number of times for the provisional registration 734 indicates that 1 time remains, and the bonus amount that can be given 735 indicates that a bonus can be given up to 200 yen.

[0111] The permanent registration transition field 74 is displayed when a request to transition to permanent registration is included in the notification information received in step S134. The permanent registration transition field 74 includes a selection button 741, a permanent registration transition request message 742, and a bonus grant notification message 743. The selection button 741 is a button for accepting a selection operation to transition to permanent registration from user U. The permanent registration transition request message 742 is an example of a message encouraging a transition from provisional registration to permanent registration, such as "Why not transition to permanent registration?". The bonus grant notification message 743 is an example of a message informing that bonus information will be granted, such as "You will be granted a bonus of 500 points (equivalent to 500 yen) right now!"

[0112] The additional deposit field 75 is displayed when the notification information received in step S134 includes a request for additional deposit. The additional deposit field 75 includes a selection button 751, an additional deposit request message 752, a bonus notification message 753, and a depositable amount 754. The selection button 751 is a button for accepting a selection operation for additional deposit from the user U. The additional deposit request message 752 is an example of a message encouraging an additional deposit, such as "Why not make an additional deposit?" The bonus notification message 753 is an example of a message informing that bonus information will be provided, such as "You will be given a bonus of 100 yen right now!" The depositable amount 754 is the same as the depositable amount 731 described above, and is information indicating the amount that can be deposited before the usage limit is reached.

[0113] The provisional registration continuation field 76 is displayed when the notification information received in step S134 includes a provisional registration continuation request. The provisional registration continuation field 76 includes a selection button 761, a provisional registration continuation request message 762, and a privilege grant notification message 763. The selection button 761 is a button for accepting a selection operation to continue the provisional registration from the user U. The provisional registration continuation request message 762 is an example of a message encouraging the provisional registration to be continued, such as "Why don't you continue your provisional registration?". The privilege grant notification message 763 is an example of a message informing that privilege information will be granted, such as "You will be granted a privilege of 50 yen right now!".

[0114] The provisional registration deletion field 77 is always displayed. Alternatively, the provisional registration deletion field 77 may be displayed when the third condition is met, like the other fields. The provisional registration deletion field 77 includes a selection button 771 and a provisional registration deletion confirmation message 772. The selection button 771 is a button for accepting a selection operation for deleting the provisional registration from the user U. The provisional registration deletion confirmation message 772 is an example of a message for confirming the deletion of the provisional registration, such as "Do you want to delete the provisional registration?"

[0115] The privilege grant notification message 743, the privilege grant notification message 753, and the privilege grant notification message 763 are displayed when the notification information includes a message notifying that privilege information will be granted together with each request.

[0116] FIG. 17 is a diagram showing an example of display of the cumulative deposit amount history of the provisional registration status according to the second embodiment. For example, the provisional registration status display screen 7 described above may further include a cumulative deposit amount history 726. The cumulative deposit amount history 726 is an example of a graph displaying the cumulative deposit amount according to the provisional registration days. The cumulative deposit amount history 726 includes the amount deposited by the user U for provisional registration, the date of deposit, the current cumulative deposit amount, and the remaining depositable amount up to the deposit upper limit. Furthermore, the cumulative deposit amount history 726 may include the initial provisional registration date, the extension time of the provisional registration, the current provisional registration deadline, the number of days remaining until the provisional registration deadline, the final deadline for the provisional registration, the extendable period, and the possible number of provisional registrations.

[0117] Returning to FIG. 14, the explanation will be continued. After step S134, the display control unit 483 receives an input (selection operation) on the screen from the user U (S135). Then, the authentication control unit 484 determines the input content (type of the selected selection button) (S136).

[0118] If the temporary registration continuation (selection button 761) is selected in step S136, the authentication control unit 484 transmits a request to continue the temporary registration to the authentication information management device 300 via the network N (S137).

[0119] When additional deposit (selection button 751) is selected in step S136, the display control unit 483 displays an additional deposit request message. In response to this, the deposit acceptance unit 42 accepts an additional deposit of cash from the user U (S138). The deposit acceptance unit 42 stores the deposited cash in the cash storage unit 43, tallies the additional deposit amount, and notifies the control unit 48. As a result, the acquisition unit 481 acquires the additional deposit amount. Then, the authentication control unit 484 transmits a payment balance update request including the additional deposit amount acquired in step S138 to the authentication information management device 300 via the network N (S139).

[0120] When the temporary registration deletion (selection button 771) is selected in step S136, the authentication control unit 484 transmits a temporary registration deletion request to the authentication information management device 300 via the network N (S140).

[0121] When the move to main registration (selection button 741) is selected in step S136, the display control unit 483 displays input fields for personal information and payment information on the reception screen, and requests the user U to input these information. The acquisition unit 481 accepts the personal information and payment information input by the user U via the reception screen (S141). Then, the registration unit 482 transmits a main registration request including the face image acquired in step S132 and the personal information and payment information acquired in step S141 to the authentication information management device 300 via the network N (S142).

[0122] In steps S137, S139, and S140, the authentication control unit 484 may include the face image acquired in step S132 in each request. Alternatively, if the notification information includes a session ID, the authentication control unit 484 may include the session ID in each request. In addition, in step S142, the registration unit 482 may include the session ID in place of the face image in the main registration request.

[0123] Incidentally, if a message indicating that the provisional registration status cannot be referred to is received in step S134, the display control unit 483 displays a message indicating that the provisional registration status cannot be referred to, and ends the process.

[0124] FIG. 18 is a flowchart showing a process flow for a response according to the notification information by the authentication information management device 300 according to the second embodiment. First, the acquisition unit 341 receives various processing requests from the authentication terminal 140 via the network N (S361). When the various processing requests include a face image, the authentication control unit 343 may collate whether the face image is the same as the face image included in the temporary registration status inquiry request received in step S341, and may specify the temporary registration information 312 of the user whose face authentication has been successful in step S342. Alternatively, when the various processing requests include a session ID, the authentication control unit 343 may specify the temporary registration information 312 of the user whose face authentication has been successful in step S342 if the session ID matches the session ID issued after step S341. Here, it is assumed that the temporary registration information 312 of the user whose face authentication has been successful in step S342 is specified.

[0125] Next, the update unit 346 determines the type of the processing request received in step S361 (S363). If it is determined in step S363 that the provisional registration should be continued, the update unit 346 extends and updates the deadline (time limit information 3123) of the identified provisional registration information (S364). At this time, the update unit 346 may further increment the provisional registration count 3132 for updating. Furthermore, the update unit 346 may add predetermined bonus information to update the provisional registration information. Also, before step S364, the update unit 346 may determine whether it is within a predetermined period from the registration of the provisional registration information, and execute step S364 if this condition is met.

[0126] If it is determined in step S363 that the additional deposit has been made, the update unit 346 adds the additional deposit amount included in the payment balance update request to the payment balance of the identified provisional registration information (S365). Furthermore, the update unit 346 may add a bonus amount to the payment balance. Then, the update unit 346 updates the payment balance 3122 of the identified provisional registration information as the payment balance after the addition (S366). Furthermore, before step S365, the update unit 346 may determine whether the cumulative deposit amount of the provisional registration is equal to or less than a predetermined value, and execute step S365 if this condition is met.

[0127] If it is determined in step S363 that the temporary registration is to be deleted, the update unit 346 deletes the specified temporary registration information (S367).

[0128] If it is determined in step S363 that the registration should proceed to the final registration, the registration unit 342 performs the final registration process (S368) in the same manner as in steps S312 and S315 in FIG. 9. However, it is not essential to provide the bonus information in step S314. For example, if it is within a predetermined period of time since the registration of the temporary registration information, the registration unit 342 may provide the bonus information 3144. If a facial image is included in the request for transition to the final registration, the registration unit 342 may use the facial image for the final registration. Alternatively, the registration unit 342 may include the facial feature information 3121 of the identified temporary registration information in the request for the final registration. Then, step S367 is executed.

[0129] Thus, in addition to the effects of the above-mentioned embodiment 1, the second embodiment has the following effects. First, by deleting the provisional registration information when the first condition (use restriction condition) is satisfied, the payment service using the provisional registration information is restricted. Therefore, temporary use can be guaranteed. By enabling provisional registration of biometric information, it is possible to motivate people to visit facilities such as the park 100. Furthermore, by granting privilege information when the second condition (privilege granting condition) is satisfied or at the time of full registration, new provisional registration can be promoted. Furthermore, when the third condition (user notification condition) is satisfied, the continuation of provisional registration and additional payment are encouraged, so that continued use of the payment service using face recognition can be promoted. Furthermore, the convenience of the payment service using face recognition is experienced through provisional registration, and then transition to full registration is encouraged, so that the cumbersome input and the resistance to registering important personal information and payment information can be reduced, and full registration can be promoted. Furthermore, by granting privilege information at the time of continuation of provisional registration, additional payment, and transition to full registration, continued use of the payment service using face recognition can be promoted. In addition, by accepting additional deposits when the settlement balance is insufficient, the convenience of payment services using facial recognition can be improved.

[0130] The second embodiment may be used as follows. For example, one provisional registration allows the provisional registration information to be used for one week (provisional registration period is one week). In this case, one week after the initial provisional registration date (expiry of the provisional registration period), the provisional registration information (payment balance) becomes unavailable. Note that the user U can request continuation of the provisional registration within the provisional registration period. If the provisional registration is continued, the number of provisional registrations may be incremented. Alternatively, after the provisional registration information becomes unavailable due to the expiration of the provisional registration period, the user U can perform provisional registration again. In this case, the number of provisional registrations is also incremented. For example, the upper limit of the number of provisional registrations is set to three times, and the maximum provisional registration period is set to three weeks. Therefore, if the number of provisional registrations exceeds three times or the cumulative provisional registration period exceeds three weeks, the user U cannot continue to use the provisional registration information even if he or she requests continuation of the provisional registration or requests provisional registration again. Also, for example, the upper limit of the cumulative bonus amount is set to 1,200 yen, and the upper limit of the deposit amount is set to 3,000 yen.

[0131] For example, assume that user U deposits 1,000 yen during the initial provisional registration. In this case, the provisional registration period will be one week, a bonus of 500 yen will be awarded, the payment balance will be 1,500 yen, and the cumulative deposit amount will be 1,000 yen. After that, user U can use the facial recognition payment service to make payments up to 1,500 yen. At this time, the payment amount will be deducted from the payment balance.

[0132] Thereafter, before the expiration of the provisional registration period, for example, on the sixth day after the initial provisional registration, the user U makes a provisional registration status request at a specified authentication terminal, and the provisional registration status display screen 7 described above is displayed. However, the specific examples of the provisional registration status 72 and the remaining time until the usage limit 73 are different. Therefore, the user U deposits an additional 1000 yen and requests continuation of the provisional registration. As a result, the bonus amount of 300 yen, which is lower than the initial amount, is granted because it is the second deposit, and 1300 yen is added to the settlement balance. In addition, the number of provisional registrations is extended to two, and the provisional registration period is extended to two weeks (the usage expiration date of the provisional registration information is two weeks after the initial provisional registration date). In addition, the cumulative amount of deposits becomes 2000 yen.

[0133] After that, for example, on the tenth day after the initial provisional registration, when the user U makes a provisional registration status request at a predetermined authentication terminal, the provisional registration status display screen 7 described above is displayed. Then, the user U deposits an additional 1000 yen and requests the continuation of the provisional registration. As a result, the user U is given a bonus amount of 100 yen, which is lower than the second deposit, and 50 yen is given as a bonus amount for the continuation of the provisional registration, and 1150 yen is added to the settlement balance. In addition, the number of provisional registrations is extended to three, and the provisional registration period is extended to three weeks (the expiration date of the provisional registration information is three weeks after the initial provisional registration date). In addition, the cumulative deposit amount becomes 3000 yen. After this, the user U cannot make an additional deposit even during the provisional registration period, and the provisional registration continuation request is not allowed. Instead, when the authentication information management device 300 receives an additional deposit or a provisional registration continuation request from the user U, it outputs a message prompting the user to move to the main registration.

[0134] The authentication information management device 300 may have the functions of the authentication terminal 110, etc. In other words, any one of the authentication terminals 110 to 140 may have the configuration of the authentication information management device 300.

[0135] In addition, depending on whether a user of a payment service using face recognition is a provisional registrant or a permanent registrant, the user may be treated differently when the service is provided. For example, assume that age verification information such as a driver's license is registered in the personal information 3142, and the user makes a payment for a product (such as tobacco or alcohol) that requires age verification when purchasing. In this case, after successful face authentication of the permanent registration in step S332 of FIG. 12, the payment unit 344 may determine the age of the user based on the personal information 3142, and if the age satisfies the condition, execute the payment process in step S333. This makes it possible to omit the age verification of the purchaser by a store clerk or the like, and makes the payment procedure more efficient and allows for appropriate sales.

[0136] In addition, when the third condition is satisfied, the update unit 346 may notify the user terminal (not shown) owned by the user U. For example, the provisional registration information 312 may include contact information such as a terminal ID of the user terminal, a user ID of the application, and an email address of the user U. Then, the update unit 346 judges whether or not each provisional registration information 312 in the storage unit 310 satisfies the third condition at a predetermined timing. For example, it is assumed that it is judged that a predetermined period has passed since provisional registration, that the settlement balance is equal to or less than a predetermined amount, that it is within a predetermined period from the expiration date of the provisional registration information, that the number of provisional registrations has exceeded a predetermined number, that the privilege history has exceeded a predetermined value, and the like. In this case, the update unit 346 notifies the contact (user terminal) corresponding to the user who has been judged to satisfy the third condition. In addition, when the update unit 346 receives a provisional registration status inquiry request from a user terminal, it may similarly notify the user terminal that is the request source. Therefore, the user terminal, like the authentication terminal, can inquire about the provisional registration status and can request transition to permanent registration, continuation of provisional registration, deletion of provisional registration, etc. In addition, the use control unit 345 may perform processing on the temporary registration information when the temporary registration history satisfies a predetermined condition in response to a processing request from the user. In this case, first, the authentication control unit 343 controls the second biometric authentication using the first biometric information for the third biometric information in response to a processing request including the third biometric information from the user U. For example, the authentication terminal 110 or the like accepts a selection operation of various processing requests from the user U, and transmits a processing request including a face image of the user U to the authentication information management device 300. The use control unit 345 of the authentication information management device 300 controls face authentication of the temporary registration information for the face image included in the received processing request. If face authentication (second biometric authentication) of the temporary registration information is successful, the use control unit 345 judges whether the temporary registration information related to the first biometric information satisfies the first condition. Then, the use control unit 345 performs processing on the temporary registration information according to the processing request based on the judgment result of the first condition. For example, the processing request is a request to continue the temporary registration. At this time, if a predetermined period has not elapsed since the registration of the provisional registration information or if the total amount of deposits at the time of provisional registration is equal to or less than a predetermined value, the usage control unit 345 determines that the first condition is not satisfied and updates the available period of the provisional registration information to be extended. Alternatively, the processing request is a payment balance update request. At this time, if a predetermined period has not elapsed since the registration of the provisional registration information or if the total amount of deposits at the time of provisional registration is equal to or less than a predetermined value, the usage control unit 345 determines that the first condition is not satisfied and adds the additional deposit amount to the payment balance of the provisional registration information. In other words, if the available period of the provisional registration has been exceeded or the total amount of deposits at the time of provisional registration is equal to or less than a predetermined value (if the first condition is satisfied), it may be impossible to extend the expiration date of the provisional registration information or to make an additional deposit to the payment balance. Furthermore, if a request to continue the provisional registration or a request to update the payment balance is received from the user and the first condition is satisfied, the usage control unit 345 may notify the user of the transition to the main registration.

[0137] The authentication terminal 110 (registration terminal) may be configured to allow the user to select the issuance of a two-dimensional code for code payment instead of the temporary registration of face information.

[0138] <Embodiment 3> The present embodiment 3 is a modified example of the above-mentioned embodiment 2. In the present embodiment 3, a user can temporarily register biometric information using a user terminal carried by the user, and facial feature information is not stored in the temporary registration history on the authentication information management device side.

[0139] Fig. 19 is a block diagram showing the overall configuration of an authentication information management system 1000a according to the present embodiment 3. In the authentication information management system 1000a, a user terminal 500 and an electronic payment system 600 are added and the authentication information management device 300a is modified, compared to Fig. 3. The other configurations are the same as those in Fig. 3, so illustrations and detailed explanations of overlapping contents will be omitted.

[0140] The user terminal 500 is an information terminal possessed by the user U. The user terminal 500 is, for example, an information processing device such as a mobile phone terminal, a smartphone, a tablet terminal, or a notebook computer with a camera. The user terminal 500 is an example of a registration terminal. The user terminal 500 performs registration processing corresponding to provisional registration (first registration type) and full registration (second registration type) on the authentication information management device 300. However, unlike the authentication terminal 110, the user terminal 500 does not accept cash, but deposits (transfers) electronic money or the like that can be used for electronic settlement into an account on the authentication information management device 300 side.

[0141] The electronic payment system 600 is a known information system that manages a specific electronic payment. For example, the electronic payment system 600 manages payments using electronic money and code payment processing (transfers between accounts), and manages user information and account information (balance information). The electronic payment system 600 may be a server that can communicate with an electronic payment application installed in the user terminal 500.

[0142] 20 is a block diagram showing the configuration of a user terminal 500 according to the present embodiment 3. The user terminal 500 includes a camera 51, a storage unit 54, a memory 55, a communication unit 56, an input / output unit 57, and a control unit 58.

[0143] The camera 51 is an image capturing device that captures the user U under the control of the control unit 58. The storage unit 54 is a storage device in which a program 541 and a temporary registration ID 542 for implementing each function of the user terminal 500 are stored. The program 541 is a computer program in which at least a face information registration process, a remittance process of electronic money or the like, a temporary registration status inquiry process, and the like are implemented. The program 541 includes a client application for the authentication information management device 300a according to this embodiment. The temporary registration ID 542 is information for identifying the temporary registration information. The temporary registration ID 542 is, for example, a terminal ID of the user terminal 500, a mobile phone number set in the user terminal 500, a user ID of the client application, and the like. The memory 55 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 58 is operating. The communication unit 56 is a communication interface with the network N. The input / output unit 57 includes a display device and an input device. The input / output unit 57 is, for example, a touch panel. The control unit 58 is a processor that controls the hardware of the user terminal 500. The control unit 58 loads the program 541 from the storage unit 54 into the memory 55 and executes it. In this way, the control unit 58 realizes the functions of an acquisition unit 581, a registration unit 582, a display control unit 583, an authentication control unit 584, and an electronic payment unit 585.

[0144] The acquisition unit 581 receives a selection of a registration type from the user U. The acquisition unit 581 also controls the camera 51 to capture an image of an area including the face of the user U and acquires the image as a face image. If the registration type is provisional registration, the acquisition unit 581 reads out the provisional registration ID 542 from the storage unit 54. If the registration type is full registration, the acquisition unit 581 requests the user U to input personal information and payment information, and acquires the input personal information and payment information.

[0145] When the registration type is temporary registration, the registration unit 582 transmits a temporary registration request including the face image, the remittance result, and the temporary registration ID to the authentication information management device 300a. When the registration type is permanent registration, the registration unit 582 transmits a permanent registration request including the face image, the personal information, and the payment information to the authentication information management device 300a.

[0146] The display control unit 583 displays a reception screen and various notification information received from the authentication information management device 300a on the input / output unit 57. Other specific operations of the display control unit 583 are similar to those of the display control unit 483 described above.

[0147] When the temporary registration status inquiry is selected, the authentication control unit 584 transmits a temporary registration status inquiry request including a facial image to the authentication information management device 300a. In addition, the authentication control unit 584 may transmit a facial authentication request including a facial image to the authentication information management device 300a or the authentication device 200. In other words, the authentication control unit 584 controls facial authentication of the user U. In addition, the authentication control unit 584 transmits various processing requests in response to notifications from the display control unit 583 to the authentication information management device 300a.

[0148] When the registration type is provisional registration, the electronic payment unit 585 accepts a remittance instruction for electronic money or code payment from the user U, and transmits the remittance instruction to the electronic payment system 600. Then, the electronic payment unit 585 receives a remittance result from the electronic payment system 600.

[0149] Fig. 21 is a block diagram showing the configuration of an authentication information management device 300a according to the third embodiment. In the authentication information management device 300a, a temporary registration ID 3124 is added to the temporary registration information 312, and the facial feature information 3131 in the temporary registration history 313 is replaced with a temporary registration ID 3131a, as compared to Fig. 5. In addition, in the authentication information management device 300a, a program 311a, an acquisition unit 341a, and a registration unit 342a are changed as compared to Fig. 5. Since the other configurations are the same as those in Fig. 5, detailed description of the overlapping contents will be omitted.

[0150] The program 311a is a computer program in which the processing of the authentication information management method according to the third embodiment is implemented. The temporary registration information 312 is information in which a temporary registration ID 3124 is further associated with facial feature information 3121. The temporary registration ID 3124 is information similar to the temporary registration ID 542 in FIG. 20 described above. The temporary registration history 313 is information in which a temporary registration ID 3131a, a temporary registration count 3132, and a privilege history 3133 are associated with each other. The temporary registration ID 3131a is information equivalent to the temporary registration ID 3124 described above.

[0151] The acquisition unit 341a is a modified example of the above-mentioned acquisition unit 341. The acquisition unit 341a receives (acquires) a provisional registration request, a main registration request, a settlement request, an additional deposit request, a provisional registration status inquiry request, a provisional registration continuation and deletion request, a transition request from provisional registration to main registration (main registration transition request), and a settlement balance update request, etc.

[0152] Registration unit 342a is a modified example of registration unit 342 described above. In response to a temporary registration request, registration unit 342a generates temporary registration information 312 in the same manner as registration unit 342, and in addition adds temporary registration ID 3124 included in the temporary registration request to temporary registration information 312. Furthermore, in response to the registration of temporary registration information 312, registration unit 342a generates temporary registration history 313 with temporary registration ID 3124 as temporary registration ID 3131a. In addition, registration unit 342a generates temporary registration history 313 in the same manner as registration unit 342.

[0153] In particular, when the second condition is satisfied, the registration unit 342a generates temporary registration information 312 to which predetermined privilege information is added. Specifically, the registration unit 342a determines that the second condition is satisfied when the temporary registration ID included in the temporary registration request is not registered in the temporary registration history 313. Furthermore, even if the temporary registration ID included in the temporary registration request is registered in the temporary registration history 313, the registration unit 342a determines that the second condition is satisfied when the temporary registration count 3132 is equal to or less than a predetermined count or the privilege history 3133 is equal to or less than a predetermined value. Note that when the predetermined count is one time, that is, when a privilege is added only the first time a temporary registration request is made for a specific user, the temporary registration history 313 may manage only the temporary registration ID 3131a, and the temporary registration count 3132 and the privilege history 3133 may be unnecessary.

[0154] Similarly to the registration unit 342, the registration unit 342a performs processes such as providing benefits, main registration, and requests to transition to main registration.

[0155] 22 is a flowchart showing the flow of face information registration processing by the user terminal 500 according to the third embodiment. First, the user terminal 500 displays a reception screen. Then, the acquisition unit 581 of the user terminal 500 accepts the selection of a registration type by an operation of the user U (S501). Next, the acquisition unit 581 determines the registration type (S502). If the registration type is provisional registration, the acquisition unit 581 acquires a face image of the user U captured by the camera 51 (S503).

[0156] Then, the electronic payment unit 585 of the user terminal 500 prompts the user U via a reception screen or voice to remit a predetermined amount of electronic money. Here, the remittance account is an account managed by the operating company of the park 100 or the authentication information management device 300a. The electronic payment unit 585 receives a remittance instruction for electronic money or code payment from the user U (S504). For example, the electronic payment unit 585 receives an instruction from the user U to remit a predetermined amount to the remittance account via a predetermined code payment application screen.

[0157] The electronic payment unit 585 transmits a remittance instruction including user U's user ID (remittance source account information), remittance destination account information, remittance amount, etc. to the electronic payment system 600 via the network N (S505). In response, the electronic payment system 600 performs remittance processing (moving and updating amount information between accounts) according to the remittance instruction, and returns the remittance result to the user terminal 500. The remittance result is information that certifies that a specified amount has been deposited (remitted) from user U to the operating company's account by a specified electronic payment. In other words, the remittance result includes the deposited amount. The electronic payment unit 585 receives the remittance result from the electronic payment system 600 (S506).

[0158] Next, the acquisition unit 581 acquires the temporary registration ID 542 by reading it from the storage unit 54 (S507). Then, the registration unit 582 transmits a temporary registration request including the face image acquired in step S503, the remittance result received in step S506, and the temporary registration ID acquired in step S507 to the authentication information management device 300a via the network N (S508).

[0159] If the registration type is formal registration in step S502, the acquisition unit 581 acquires a facial image of the user U captured by the camera 51 (S509). Then, the user terminal 500 displays input fields for personal information and payment information on the reception screen and requests the user U to input these. The acquisition unit 581 accepts the personal information and payment information input by the user U via the reception screen (S510). Then, the registration unit 582 transmits a formal registration request including the facial image acquired in step S509 and the personal information and payment information acquired in step S510 to the authentication information management device 300a via the network N (S511). Note that steps S503 and S509 may be executed before step S501.

[0160] Fig. 23 is a flowchart showing the flow of the provisional registration process according to the third embodiment. First, the acquisition unit 341a of the authentication information management device 300a receives a provisional registration request from the user terminal 500 via the network N (S301a). The acquisition unit 341a may receive various processing requests from the user terminal 500, etc., determine the type of the received request, and determine that the request is a provisional registration request. The determination of the type of the received request by the acquisition unit 341a is similar to other processes.

[0161] The registration unit 342a acquires a temporary registration ID from the received temporary registration request. Then, the registration unit 342a judges whether or not the acquired temporary registration ID exists in the temporary registration ID 3131a of the temporary registration history 313 (S302a). If the temporary registration ID does not exist in the temporary registration history 313, the process proceeds to step S304. On the other hand, if the temporary registration ID exists in the temporary registration history 313 in step S302a, the registration unit 342a judges whether or not the number of temporary registrations is equal to or less than a predetermined number (S303). Note that instead of step S303, the registration unit 342a may judge whether or not the cumulative value of the bonus amount in the bonus history 3133 is equal to or less than a predetermined value. Thereafter, steps S304 and S305 are processed in the same manner as in FIG. 8.

[0162] After step S304 or S305, the registration unit 342a acquires a face image from the received temporary registration request and extracts face feature information from the face image. Then, the registration unit 342a generates temporary registration information 312 by associating the extracted face feature information 3121 with the payment balance 3122 of step S304 or S305, the deadline information 3123, and the temporary registration ID 3124. Then, the registration unit 342a registers the generated temporary registration information 312 in the storage unit 310 (S306a). Furthermore, the registration unit 342a generates temporary registration history 313 by associating the temporary registration ID 3124 (3131a) included in the generated temporary registration information 312 with the temporary registration count 3132 and the privilege history 3133. Then, the registration unit 342a registers the temporary registration history 313 (S307a). Furthermore, if the number of times from the second time onwards is equal to or less than the specified number (YES in step S303), the registration unit 342a adds "1" to the number of provisional registrations 3132 in the provisional registration history 313 identified in step S302, and adds the bonus amount added in step S304 to the bonus history 3133, thereby updating the provisional registration history 313.

[0163] Thus, in addition to the effects of the above-mentioned embodiments 1 and 2, the third embodiment provides the following effects. First, the user can temporarily register biometric information using the user terminal carried by the user, lowering the barrier to temporary registration and promoting information registration for payment services using temporary registration information. Also, since there is no need for the certificate information management device to store facial feature information in the temporary registration history, concerns about temporarily registering biometric information during temporary registration can be alleviated.

[0164] <Embodiment 4> The fourth embodiment is a modified example of the third embodiment described above. In the fourth embodiment, the user terminal holds the number of temporary registrations, and controls whether or not to grant a special benefit for temporary registration. As a result, the authentication information management device does not hold the temporary registration history itself. In the authentication information management system of the fourth embodiment, the user terminal 500b and the authentication information management device 300b are changed compared to FIG. 19. Note that other configurations of the authentication information management system of the fourth embodiment are the same as those of FIG. 19, and therefore illustrations and detailed explanations of overlapping contents will be omitted.

[0165] Fig. 24 is a block diagram showing the configuration of a user terminal 500b according to the fourth embodiment. The user terminal 500b is a modified example of the user terminal 500. Compared to the user terminal 500, the temporary registration ID 542 of the user terminal 500b is replaced with the temporary registration count 543, and the program 541b and the registration unit 582b are modified. Since the other configurations are the same as those of Fig. 20, detailed description of the overlapping contents will be omitted.

[0166] The program 541b includes a client application for the authentication information management device 300b according to the present embodiment. The temporary registration count 543 is the number of times temporary registration information has been registered for the user U of the user terminal 500b or the client application.

[0167] When the registration type is temporary registration, the registration unit 582b sets a privilege flag according to the temporary registration count 543. Then, the registration unit 582b transmits a temporary registration request including a facial image, a remittance result, and the temporary registration count to the authentication information management device 300b. When the registration type is permanent registration, the registration unit 582b transmits a permanent registration request including a facial image, personal information, and payment information to the authentication information management device 300b.

[0168] Fig. 25 is a block diagram showing a configuration of an authentication information management device 300b according to the fourth embodiment. Compared with Figs. 5 and 21, the authentication information management device 300b is one in which the temporary registration history 313 has been deleted. The temporary registration information 312 is the same as that in Fig. 5, and the temporary registration ID 3124 is unnecessary. Also, compared with Fig. 21, the authentication information management device 300b is one in which the program 311b, the acquisition unit 341b, and the registration unit 342b have been changed.

[0169] The program 311b is a computer program in which the processing of the authentication information management method according to the fourth embodiment is implemented.

[0170] The acquisition unit 341b is a modified example of the acquisition unit 341b described above. The acquisition unit 341b receives (acquires) a provisional registration request, a main registration request, a settlement request, an additional deposit request, a provisional registration status inquiry request, a provisional registration continuation and deletion request, a transition request from provisional registration to main registration (main registration transition request), and a settlement balance update request, etc.

[0171] The registration unit 342b is a modified example of the registration unit 342 or 342a described above. When the acquisition unit 341b acquires a temporary registration request, the registration unit 342b generates temporary registration information 312 in the same manner as the registration unit 342, and registers the temporary registration information 312 in the storage unit 310. In particular, when a privilege flag included in the temporary registration request indicates ON, the registration unit 342b determines that the second condition is satisfied. That is, when a privilege flag included in the temporary registration request indicates ON, the registration unit 342b registers temporary registration information 312 to which predetermined privilege information is added. Furthermore, the registration unit 342b performs processes in response to the addition of a privilege, main registration, and a request to transition to main registration in the same manner as the registration unit 342.

[0172] Fig. 26 is a flowchart showing the flow of face information registration processing by the user terminal 500b according to the present embodiment 4. Note that a description of the same processing as in Fig. 22 will be omitted as appropriate.

[0173] First, the user terminal 500b executes steps S501 and S502 as in FIG. 22. If the registration type is temporary registration, the user terminal 500b executes steps S503 to S506 (S503b) as in FIG. 22. Then, the registration unit 582b of the user terminal 500b determines whether the temporary registration count 543 in the storage unit 54 is equal to or less than a predetermined number (S512). If the temporary registration count 543 is equal to or less than the predetermined number, the registration unit 582b sets the privilege flag to ON (S513). If the temporary registration count 543 is greater than the predetermined number in step S512, the registration unit 582b sets the privilege flag to OFF (S514).

[0174] Then, the registration unit 582b transmits a temporary registration request including the face image acquired in step S503, the remittance result received in step S506, and the benefit flag set in step S513 or S514 to the authentication information management device 300b via the network N (S508b). After that, the registration unit 582b updates the temporary registration count 543 by adding "1" (S515). Note that if the registration type is full registration in step S502, the user terminal 500b executes steps S509 to S511 (S509b) in the same manner as in FIG. 22.

[0175] Fig. 27 is a flowchart showing the flow of the provisional registration process according to the fourth embodiment. First, the acquisition unit 341b of the authentication information management device 300b receives a provisional registration request from the user terminal 500b via the network N (S301b). The acquisition unit 341b may receive various processing requests from the user terminal 500b, etc., determine the type of the received request, and determine that the request is a provisional registration request. The determination of the type of the received request by the acquisition unit 341b is also the same for other processes.

[0176] The registration unit 342b acquires a privilege flag from the received temporary registration request. Then, the registration unit 342b determines whether the acquired privilege flag is set to ON or not (S302b). If the privilege flag is set to ON, the process proceeds to step S304. On the other hand, if the privilege flag is set to OFF, the process proceeds to step S305. Steps S304 and S305 are processed in the same manner as in FIG. 8.

[0177] After step S304 or S305, the registration unit 342b acquires a face image from the received temporary registration request and extracts facial feature information from the face image. The registration unit 342b then generates temporary registration information 312 by associating the extracted facial feature information 3121 with the payment balance 3122 from step S304 or S305 and the deadline information 3123. The registration unit 342b then registers the generated temporary registration information 312 in the storage unit 310 (S306).

[0178] Thus, in addition to the effects of the above-mentioned embodiments 1 to 3, the fourth embodiment provides the following effects. First, the user terminal holds the number of provisional registrations, so that the user terminal can control whether or not to grant a privilege for provisional registration. Therefore, the authentication information management device can determine whether or not the privilege granting condition (second condition) is satisfied for each provisional registration request by checking whether the privilege flag is ON / OFF. Therefore, the process of determining whether or not the second condition is satisfied on the authentication information management device side can be simplified. In particular, since the authentication information management device does not need to hold the provisional registration history itself, concerns about temporarily registering biometric information during provisional registration can be alleviated.

[0179] <Other embodiments> In the above-mentioned second to fourth embodiments, the authentication information management device 300 and the authentication device 200 are different information processing devices, but they may be the same. For example, the authentication information management device 300 may register facial feature information in association with the user ID 3141 of the permanent registration information 314. In this case, the control unit 340 may include the face detection unit 220, the feature point extraction unit 230, the registration unit 240, and the authentication unit 250 of FIG. 6. Furthermore, the facial feature information 3121 of the temporary registration information and the facial feature information 212 of the permanent registration information may be managed in the same DB. In this case, for example, the facial feature information may be managed by attaching a flag so that the information for temporary registration and the information for permanent registration can be distinguished. Then, during authentication, the information for temporary registration and the information for permanent registration may be distinguished and checked.

[0180] Alternatively, the temporary registration information 312 , the temporary registration history 313 and the permanent registration information 314 may be stored in an external storage device connected to the authentication device 200 or the authentication information management device 300 .

[0181] As a modification of the fourth embodiment, the authentication terminal 110 (registration terminal) may transmit a provisional registration request including a privilege flag. For example, a staff member of the park 100 requests the user U who wishes to provisionally register to present personal identification information such as an ID card at the entrance of the park 100, and separately records the personal information of the user U and the provisional registration history (number of times, etc.) in a ledger or the like. The staff member then checks the provisional registration history of the user U from the ledger or the like and determines whether the user U is eligible for a privilege. The staff member inputs whether the user U is eligible for a privilege to the authentication terminal 110, and the user U performs a provisional registration operation. In response to this, the authentication terminal 110 transmits a provisional registration request including a privilege flag to the authentication information management device 300b. Therefore, the authentication information management device 300b can process the request after determining whether the user U is eligible for a privilege without holding the provisional registration history. The privilege flag may be included in the main registration request.

[0182] In the above embodiment, the present disclosure has been described as a hardware configuration, but is not limited to this. Any process of the present disclosure can be realized by causing a CPU to execute a computer program.

[0183] In the above example, the program can be stored and provided to the computer using various types of non-transitory computer readable media. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, DVD (Digital Versatile Disc), and semiconductor memory (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). The program may also be provided to the computer by various types of transitory computer readable media. Examples of the transitory computer readable media include electric signals, optical signals, and electromagnetic waves. The transitory computer readable media can provide the program to the computer via a wired communication path such as an electric wire and an optical fiber, or via a wireless communication path.

[0184] The present disclosure is not limited to the above-described embodiment, and may be modified as appropriate without departing from the spirit and scope of the present disclosure. In addition, the present disclosure may be implemented by appropriately combining the respective embodiments.

[0185] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes. (Appendix 1) an acquisition unit that acquires a temporary registration request including the first biometric information and the deposit amount of the user; a registration unit that registers temporary registration information that associates a payment balance based on the deposit amount included in the temporary registration request with the first biometric information; an authentication control unit that controls a first biometric authentication using the first biometric information for the second biometric information in response to a payment request including the second biometric information and a payment amount; a payment unit that, when the first biometric authentication is successful, settles the payment amount by using a payment balance associated with the first biometric information; a usage control unit that controls usage of the provisional registration information according to a determination result of whether the provisional registration information satisfies a first condition; An authentication information management device comprising: (Appendix 2) The usage control unit restricts usage of the provisional registration information when the provisional registration information satisfies a first condition. 2. An authentication information management device according to claim 1. (Appendix 3) The usage control unit restricts the usage of the provisional registration information by deleting the provisional registration information. 3. An authentication information management device according to claim 2. (Appendix 4) The usage control unit determines that the first condition is satisfied when a predetermined period has elapsed since the registration of the provisional registration information, and restricts the usage of the provisional registration information. 4. An authentication information management device according to claim 2 or 3. (Appendix 5) The usage control unit determines that the first condition is satisfied when the settlement balance after the settlement is equal to or less than a predetermined amount, and restricts the use of the provisional registration information. 5. An authentication information management device according to any one of claims 2 to 4. (Appendix 6) the authentication control unit controls, in response to a processing request including third biometric information from the user, a second biometric authentication using the first biometric information for the third biometric information; When the second biometric authentication is successful, the usage control unit determines whether or not the temporary registration information related to the first biometric information satisfies the first condition, and performs processing on the temporary registration information in response to the processing request based on a result of the determination of the first condition. 6. An authentication information management device according to any one of claims 1 to 5. (Appendix 7) The processing request is a request for continuation of a provisional registration, The usage control unit determines that the first condition is not satisfied if a predetermined period has not elapsed since the registration of the temporary registration information, and updates the usage period of the temporary registration information so as to extend it. 7. An authentication information management device according to claim 6. (Appendix 8) The registration unit registers the temporary registration information to which predetermined special benefit information is added when information included in the temporary registration request satisfies a second condition. 8. An authentication information management device according to any one of claims 1 to 7. (Appendix 9) The registration unit adds a reward amount to the deposit amount to calculate the settlement balance, thereby granting the reward information. 9. An authentication information management device according to claim 8. (Appendix 10) The registration unit is registering the first biometric information in a temporary registration history in response to the registration of the temporary registration information; When the temporary registration history corresponding to the biometric information included in a subsequent temporary registration request acquired after the registration satisfies the second condition, the special information is granted. 10. An authentication information management device according to claim 8 or 9. (Appendix 11) The registration unit is registering the number of times the temporary registration request has been made by the user or a cumulative value of the granted privilege information in the temporary registration history; When the number of requests is equal to or less than a predetermined number or the cumulative value is equal to or less than a predetermined value, it is determined that the second condition is satisfied. 11. An authentication information management device according to claim 10. (Appendix 12) the acquisition unit acquires a main registration request including the first biometric information, personal information, and payment information from the user; The registration unit associates the first biometric information, the personal information, and the payment information, and registers official registration information to which predetermined special benefit information is added. 12. An authentication information management device according to any one of claims 1 to 11. (Appendix 13) The registration unit registers the official registration information to which predetermined privilege information is added when the user has not made the temporary registration request in the past. 13. An authentication information management device according to claim 12. (Appendix 14) When the settlement balance is insufficient for the settlement amount, the settlement unit notifies the requester of the settlement request of the shortfall, and when an additional deposit amount is received from the requester, the settlement unit settles the settlement amount using the settlement balance and the additional deposit amount. An authentication information management device according to any one of appendix 1 to 13. (Appendix 15) and an update unit configured to notify the user when the provisional registration information satisfies a third condition and to update the provisional registration information based on a response from the user. An authentication information management device according to any one of appendix 1 to 14. (Appendix 16) The update unit updates the provisional registration information so as to extend a period during which the provisional registration information is available if the response indicates continuation of the provisional registration. 16. An authentication information management device according to claim 15. (Appendix 17) The update unit extends the available period and adds predetermined benefit information to update the provisional registration information. 17. An authentication information management device according to claim 16. (Appendix 18) When the response indicates a request for transition to a permanent registration including the first biometric information, personal information, and payment information, the update unit deletes the provisional registration information including the first biometric information; The registration unit registers official registration information in which the first biometric information, the personal information, and the payment information are associated with each other. 18. An authentication information management device according to any one of appendix 15 to 17. (Appendix 19) The registration unit registers the main registration information to which predetermined special benefit information has been added. 19. An authentication information management device according to claim 18. (Appendix 20) a registration terminal that accepts first biometric information and a predetermined amount of deposit from a user; An authentication information management device; a payment terminal that accepts second biometric information from a user making a payment, the registration terminal transmits a temporary registration request including the first biometric information and the deposit amount to the authentication information management device; the authentication information management device registers temporary registration information in which a settlement balance based on the deposit amount included in the temporary registration request received from the registration terminal is associated with the first biometric information; the payment terminal transmits a payment request including the second biometric information and a payment amount to the authentication information management device; The authentication information management device includes: Controlling a first biometric authentication using the first biometric information for the second biometric information in response to the payment request received from the payment terminal; If the first biometric authentication is successful, the payment amount is paid using a payment balance associated with the first biometric information; Controlling use of the provisional registration information according to a determination result of whether or not the provisional registration information satisfies a first condition. Credential Management System. (Appendix 21) The authentication information management device restricts use of the temporary registration information when the temporary registration information satisfies a first condition. 21. The authentication information management system according to claim 20. (Appendix 22) The computer Acquire a provisional registration request including the first biometric information of the user and the deposit amount; registering provisional registration information in which a settlement balance based on the deposit amount included in the provisional registration request is associated with the first biometric information; controlling a first biometric authentication using the first biometric information for the second biometric information in response to a payment request including the second biometric information and a payment amount; If the first biometric authentication is successful, the payment amount is paid using a payment balance associated with the first biometric information; The use of the provisional registration information is controlled according to a result of the determination as to whether the provisional registration information satisfies a first condition. How credentials are managed. (Appendix 23) A process of acquiring a temporary registration request including the first biometric information and the deposit amount of the user; a process of registering temporary registration information in which a payment balance based on the deposit amount included in the temporary registration request is associated with the first biometric information; a process of controlling a first biometric authentication using the first biometric information for the second biometric information in response to a payment request including the second biometric information and a payment amount; If the first biometric authentication is successful, a process of paying the payment amount using a payment balance associated with the first biometric information; A process of controlling use of the provisional registration information according to a determination result of whether or not the provisional registration information satisfies a first condition; A credential management program that causes a computer to execute the following:

[0186] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-mentioned embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0187] This application claims priority to Japanese Patent Application No. 2021-025719, filed on February 19, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0188] 1. Authentication information management device 11 Acquisition Department 12 Registration Department 13 Authentication control section 14 Payment Department 15. Usage control section 1000 Credential Management System 1000a Credential Management System U User N Network 100 parks 110 Authentication terminal 120 Authentication Terminal 130 Authentication terminal 140 Authentication Terminal 150 Locker 160 Shop 200 Authentication Device 210 Face Information DB 211 User ID 212 Facial Feature Information 220 Face detection unit 230 Feature Point Extraction Unit 240 Registration Department 250 Authentication Department 300 Authentication information management device 310 Storage section 311 Program 312 Provisional Registration Information 3121 Facial Feature Information 3122 Settlement balance 3123 Expiration Information 313 Provisional Registration History 3131 Facial Feature Information 3132 Provisional registrations 3133 Benefit History 314 Registration Information 3141 User ID 3142 Personal Information 3143 Payment Information 3144 Bonus Information 320 Memory 330 Communications Department 340 Control Unit 341 Acquisition Department 342 Registration Department 343 Authentication control section 344 Payment Department 345 Usage Control Section 346 Update Department 41 Camera 42 Deposit Reception Department 43 Cash Storage 44 Storage section 441 Programs 45 Memory 46 Communications Department 47 Input / output section 48 Control Unit 481 Acquisition Department 482 Registration Department 483 Display control section 484 Authentication control section 485 Payment Processing Unit 300a Authentication information management device 311a Program 3124 Provisional Registration ID 3131a Provisional Registration ID 341a Acquisition Department 342a Registration Department 500 user terminals 51 Camera 54 Storage section 541 Programs 542 Provisional Registration ID 55 Memory 56 Communications Department 57 Input / output section 58 Control Unit 581 Acquisition Department 582 Registration Department 583 Display control unit 584 Authentication control section 585 Electronic Payments Department 600 Electronic Payment Systems 300b Authentication information management device 311b Program 341b Acquisition Department 342b Registration Department 500b User terminal 541b Program 543 Provisional Registrations 582b Registration Department 7 Provisional registration status display screen 71 Face Image 72 Provisional registration status 721 Settlement balance 722 Provisional Registration Date 723 Provisional Registration Period 724 Provisional Registrations 725 Award History 726 Accumulative Deposit History 73 remaining until usage limit 731 Available for deposit 733 Remaining period of provisional registration 734 Remaining provisional registrations 735 Bonus available amount 74 Registration Transfer Column 741 Selection button 742 Registration transfer request message 743 Bonus information message 75 Additional deposit field 751 Select button 752 Additional deposit request message 753 Bonus information message 754 Depositable Amount 76 Provisional Registration Continuation Column 761 Selection button 762 Temporary registration continuation request message 763 Bonus information message 77 Provisional Registration Deletion Column 771 Select button 772 Temporary Registration Deletion Confirmation Message

Claims

1. a registration means for registering the first biometric information of the user acquired via an application installed on the user terminal and the first deposit amount information as provisional registration information in association with each other; an acquisition means for acquiring a payment request including second biometric information of a user and a payment amount; a payment means for matching the first biometric information with the second biometric information and settling the payment amount based on the first deposit amount information associated with the first biometric information; a usage control means for controlling usage of the temporary registration information according to a result of a determination as to whether or not the temporary registration information satisfies a first condition, The usage control means determines that the first condition is satisfied when the settlement balance after the settlement is equal to or less than a predetermined amount, and restricts the use of the provisional registration information. Information processing device.

2. The settlement means displays the settlement balance after the settlement to the requester of the settlement request. The information processing device according to claim 1 .

3. The usage control means restricts the usage of the provisional registration information by deleting the provisional registration information.

3. The information processing device according to claim 1 or 2.

4. The usage control means determines that the first condition is satisfied when a predetermined period of time has elapsed since the registration of the provisional registration information, and restricts the usage of the provisional registration information. The information processing device according to claim 1 .

5. the acquiring means acquires a processing request including third biometric information from the user; When biometric authentication by matching the third biometric information with the first biometric information is successful, the usage control means determines whether or not the temporary registration information related to the first biometric information satisfies the first condition, and performs processing on the temporary registration information in accordance with the processing request based on a result of the determination of the first condition. The information processing device according to claim 1 .

6. The processing request is a request for continuation of a provisional registration, The usage control means determines that the first condition is not satisfied if a predetermined period has not elapsed since the registration of the temporary registration information, and updates the usage period of the temporary registration information so as to extend it. The information processing device according to claim 5 .

7. and a depositing means for adding the second deposit amount information to the first deposit amount information associated with the first biometric information identified by matching the first biometric information with the fourth biometric information when the fourth biometric information and the second deposit amount information of the user are acquired via the application. The information processing device according to claim 1 .

8. The acquisition means further acquires a registration type selected by the user, When the registration type is the final registration, the registration means associates the first biometric information with the payment information of the user and registers the first biometric information and the payment information of the user as the final registration information instead of the temporary registration information; The settlement means performs settlement based on the main registration information by matching the first biometric information with the second biometric information. The information processing device according to claim 1 .

9. The computer registering the first biometric information of the user acquired via an application installed on the user terminal and the first deposit amount information as provisional registration information in association with each other; acquiring a payment request including second biometric information of the user and a payment amount; By matching the first biometric information with the second biometric information, the payment amount is settled based on the first deposit amount information associated with the first biometric information; Controlling use of the provisional registration information according to a determination result of whether or not the provisional registration information satisfies a first condition; When the settlement balance after the settlement is equal to or less than a predetermined amount, it is determined that the first condition is satisfied, and the use of the provisional registration information is restricted. Information processing methods.

10. A process of registering the first biometric information of the user acquired via an application installed on the user terminal and the first deposit amount information as provisional registration information in association with each other; A process of acquiring a payment request including second biometric information of a user and a payment amount; a process of matching the first biometric information with the second biometric information and settling the payment amount based on the first deposit amount information associated with the first biometric information; A process of controlling use of the provisional registration information according to a determination result of whether or not the provisional registration information satisfies a first condition; a process of determining that the first condition is satisfied and restricting use of the provisional registration information when the settlement balance after the settlement is equal to or less than a predetermined amount; An information processing program that causes a computer to execute the above.

Images