Face authentication system, and face authentication method

Abstract

To provide a face authentication system capable of easily executing processing of reflecting update (additions, deletions, changes, etc.) of face information on a server device side to a face authentication device side, and capable of performing daily face authentication without any problems while safely managing face information which is personal information even when the face information is updated on the server device from time to time.SOLUTION: A face authentication machine is configured to make a distribution request for face information to a management server in response to a power-on of an own device. The management server delivers face information related to the face authentication machine of a request source to the face authentication machine, in response to the distribution request from the face authentication machine. Also, the face authentication machine erases the face information stored in the own device in response to a power-off of the own device. Also, the face authentication machine performs reactivation according to a preset schedule.SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present invention relates to a face authentication system and a face authentication method that perform face authentication to permit only authorized users (registered persons) to unlock a storage device. [Background technology]

[0002] In apartment complexes, delivery lockers (storage devices) are installed to receive packages from delivery companies when the delivery company cannot deliver the package directly to the resident. In order to prevent unauthorized removal of packages, the delivery lockers require personal authentication to confirm that the resident is a resident of the apartment complex. Possible methods of personal authentication include face authentication using the user's facial image, code authentication using a PIN number, and card authentication using an IC card.

[0003] Conventionally, as a personal authentication technology for unlocking such delivery lockers, a technology is known in which face authentication using a facial image of the user is performed in addition to code authentication using a PIN (see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2022-008588 Summary of the Invention [Problem to be solved by the invention]

[0005] In a cloud-based face authentication system, a server device operated in the cloud manages face information for each user, i.e., face images and face features extracted from the face images, and performs face matching to match the face information of the user to be authenticated with the registered face information. There is also an edge-based face authentication system, in which the server device manages face information for each user, but face matching is performed by a face authentication device acting as an edge device.

[0006] Meanwhile, in the server device, the facial information of each user is updated from time to time. That is, when a new user starts using the system, the facial information of the user is added, when the user ends the use, the facial information of the user is deleted, and when the update deadline arrives, the facial information of the user is changed to new facial information. For this reason, in an edge-type facial authentication system, when an update (addition, deletion, change, etc.) is made to the facial information managed by the server device, it is required that the update of the facial information is promptly reflected in the facial information held in the facial authentication device, so that all registered users can be properly subjected to facial authentication.

[0007] In particular, it is desirable to easily implement a process for reflecting updates to face information on the server device side on the face authentication device side, so that even if face information is updated from time to time on the server device, the face information, which is personal information, can be safely managed and daily face authentication can be performed without hindrance. However, conventional technologies do not take such a demand into consideration at all.

[0008] Therefore, the main object of the present invention is to provide a face recognition system and a face recognition method that can easily perform a process of reflecting updates (addition, deletion, change, etc.) of face information on the server device side to the face recognition device side, and can perform daily face recognition without hindrance while safely managing the face information, which is personal information, even when the face information is updated from time to time on the server device. [Means for solving the problem]

[0009] The facial recognition system of the present invention comprises a storage device which is locked and unlocked by an electronic lock, a facial recognition device which is installed near the storage device and which acquires facial information of a user and compares the user's facial information with pre-registered facial information in order to allow the user to unlock the storage device, and a server device which is connected to the facial recognition device via a network and which manages facial information for each user and distributes the facial information to the facial recognition device, wherein the facial recognition device makes a distribution request for facial information to the server device in response to the distribution request from the facial recognition device, and the server device distributes facial information related to the requesting facial recognition device to the facial recognition device.

[0010] In addition, the facial recognition method of the present invention is a storage system including a storage device that is locked and unlocked by an electronic lock, a facial recognition device that is installed near the storage device and acquires facial information of a user and compares the user's facial information with pre-registered facial information in order to allow the user to unlock the storage device, and a server device that is connected to the facial recognition device via a network and manages facial information for each user and distributes the facial information to the facial recognition device, wherein the facial recognition device makes a request for distribution of facial information to the server device in response to turning on the power of the facial recognition device, and the server device distributes facial information related to the requesting facial recognition device to the facial recognition device in response to the distribution request from the facial recognition device. Effect of the Invention

[0011] According to the present invention, the face authentication device can update the face information stored in the device when the device is powered on (when booting up). This makes it easy to reflect the update of the face information performed on the server device side on the face authentication device side. [Brief description of the drawings]

[0012] [Figure 1] Overall configuration of the parcel locker system (face recognition system) [Diagram 2]Front view showing the exterior of the parcel locker and face recognition unit [Diagram 3] Block diagram showing the schematic configuration of the delivery locker and face recognition unit [Figure 4] A block diagram showing the schematic configuration of a management server and a face information server. [Diagram 5] FIG. 13 is an explanatory diagram showing a registration screen displayed on a user terminal. [Figure 6] A sequence diagram showing an overview of the process for user registration that is carried out by the delivery locker, management server, face information server, user terminal, and face recognition device. [Figure 7] FIG. 13 is an explanatory diagram showing a guide screen regarding face recognition displayed on the display of the face recognition unit. [Figure 8] A sequence diagram showing an overview of the process of face recognition performed in a delivery locker and face recognition device [Figure 9] Block diagram showing an overview of the facial recognition device and the process used to unlock a parcel locker [Figure 10] A sequence diagram showing the overview of the process performed by the management server, face information server, and face recognition device when they are restarted. [Figure 11] A sequence diagram showing an overview of the process performed by the management server, face information server, and face recognition device when checking the update status [Figure 12] A sequence diagram showing an overview of the process performed by the management server, face information server, and face recognition device when a distribution request is made, including an update status inquiry. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] A first invention made to solve the above problems comprises a storage device which is locked and unlocked by an electronic lock, a facial recognition device which is installed near the storage device and acquires facial information of a user and compares the user's facial information with pre-registered facial information in order to allow the user to unlock the storage device, and a server device which is connected to the facial recognition device via a network and manages facial information for each user and distributes the facial information to the facial recognition device, wherein the facial recognition device makes a distribution request for facial information to the server device in response to turning on the power of the facial recognition device, and the server device distributes facial information related to the requesting facial recognition device to the facial recognition device in response to the distribution request from the facial recognition device.

[0014] According to this, the face authentication device can update the face information stored in the device when the power is turned on (when starting up), which makes it easy to reflect the update of the face information performed on the server device side on the face authentication device side.

[0015] In addition, in a second invention, the face recognition device is configured to periodically perform an update status inquiry to inquire of the server device as to whether or not the face information managed by the server device has been updated since the most recent update date and time of the face information held in the face recognition device.

[0016] This allows the face authentication device to check the update status of the face information managed by the server device. As a result, when the face information managed by the server device is updated, the update of the face information on the server device side can be quickly reflected on the face authentication device side.

[0017] In a third aspect of the present invention, the face authentication device is configured to erase the face information held in the device itself when the device itself is powered off.

[0018] According to this, if the face recognition device is stolen, the face information is erased when the face recognition device is turned off, so that the face information stored in the face recognition device can be managed safely.

[0019] In a fourth aspect of the present invention, the face recognition device is configured to perform rebooting according to a preset schedule.

[0020] According to this, by rebooting the face recognition device, the face information update on the server device side can be reflected on the face recognition device side. Also, the operation of the face recognition device can be stabilized by refreshing the memory accompanying the reboot.

[0021] In a fifth aspect of the present invention, the face authentication device is configured to randomly set the time when the reboot is to be performed.

[0022] According to this, when the server device distributes face information to a plurality of face recognition devices, the timing of restarting the plurality of face recognition devices is shifted, so that the timing of distribution of face information can be distributed to reduce the load on the server device. In this case, the time of restarting may be set by a random number. Also, the period during which the restart is performed may be set by a schedule, and the time of restarting may be set randomly within the period.

[0023] In addition, in a sixth aspect of the present invention, the face recognition device is configured to set a restart schedule based on the frequency of face recognition performed by the device itself.

[0024] According to this, since the frequency of facial recognition and the frequency of updating facial information are correlated with the number of users, by setting a restart schedule based on the frequency of facial recognition, it is possible to restart the facial recognition device at an appropriate time according to the frequency of updating facial information.

[0025] In addition, a seventh invention is a storage system comprising a storage device which is locked and unlocked by an electronic lock, a facial recognition device which is installed near the storage device and which acquires facial information of a user and compares the user's facial information with pre-registered facial information in order to allow the user to unlock the storage device, and a server device which is connected to the facial recognition device via a network and manages facial information for each user and distributes the facial information to the facial recognition device, wherein the facial recognition device makes a request for distribution of facial information to the server device in response to turning on the power of the facial recognition device, and the server device distributes facial information related to the requesting facial recognition device to the facial recognition device in response to the distribution request from the facial recognition device.

[0026] According to this, like the first aspect of the invention, it is possible to easily execute the process of reflecting the update of the face information performed on the server device side on the face authentication device side.

[0027] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0028] FIG. 1 is a diagram showing the overall configuration of a delivery locker system (face authentication system, storage system) according to this embodiment.

[0029] This system includes a delivery locker 1 (storage device), a face recognition unit 2, a management server 3 (server device), a face information server 4 (server device), and a user terminal 5 (registration device).

[0030] The delivery locker 1 and the face recognition unit 2 are installed in a facility such as an apartment building. The management server 3 and the face information server 4 are operated in the cloud. The delivery locker 1 and the face recognition unit 2 are connected to the management server 3 via the Internet. The delivery locker 1 and the face recognition unit 2 are connected to each other. The management server 3 and the face information server 4 are connected to each other.

[0031] The parcel locker 1 is equipped with multiple storage boxes 11. When a delivery company is unable to deliver a parcel to a resident directly, the delivery company places the parcel in the storage box 11. When the user is determined to be a legitimate user (registered person) through facial recognition, the storage box 11 is unlocked and the user can receive the parcel.

[0032] The face recognition unit 2 includes a face recognition machine 7 (face recognition device), a camera 8, and a display 9. The face recognition unit 2 is installed near the delivery locker 1. This system is an edge-type face recognition system, and face recognition is performed by the face recognition machine 7 as an edge device.

[0033] Camera 8 captures an image of a user who wishes to receive a parcel, that is, who wishes to unlock storage box 11 of parcel locker 1.

[0034] The display 9 displays a guidance screen regarding face authentication. The user can view the guidance screen.

[0035] The face authentication machine 7 performs face authentication to allow a legitimate user (registered person) to unlock the delivery locker 1. Specifically, the face information (facial feature amount) of the user obtained from an image captured by a camera 8 that captures the user who wishes to receive the package is compared with the registered face information to identify the user who wishes to receive the package. The face authentication machine 7 obtains the face information (facial feature amount) of the user in advance from the face information server 4 via the management server 3 and stores it in its own device.

[0036] The management server 3 acquires setting information of users through registration operations on the user terminal 5, and manages the setting information for each user in a database. The setting information is information related to attribute information (name, category, ID number, etc.), conditions of use (validity period, etc.), dwelling unit information (dwelling unit number, dwelling unit name, etc.), authentication method (face authentication, code authentication, card authentication, etc.), and box allocation (storage box 11 to be allocated to a user), etc.

[0037] The face information server 4 acquires a face image of a user through a registration operation on the user terminal 5, and manages the face image for each user in a database. In addition, the face information server 4 extracts face features from the face image of the user, and manages the face features for each user in a database.

[0038] The user terminal 5 is a PC, a tablet terminal, a smartphone, etc. Based on screen information distributed from the management server 3, the user terminal 5 displays a registration screen 101 (see FIG. 5) for registering the setting information and face image of the user.

[0039] In this embodiment, a delivery locker 1 in which a delivery company places packages is described as the storage device; however, the storage device may also be a mailbox for placing deliveries other than packages, such as mail pieces such as envelopes, or a key box for storing keys to rooms in a building or vehicles at a business office.

[0040] Next, a description will be given of delivery locker 1 and face recognition unit 2. Fig. 2 is a front view showing the external appearance of delivery locker 1 and face recognition unit 2.

[0041] The delivery locker 1 is equipped with a plurality of storage boxes 11 for storing packages. Each storage box 11 is provided with an electronic lock 12. The electronic lock 12 locks and unlocks the door of the storage box 11. The delivery locker 1 includes storage boxes 11 shared by all the dwelling units of the apartment building (shared boxes) and storage boxes 11 assigned one to each dwelling unit (dwelling unit-specific boxes).

[0042] The face recognition unit 2 is installed adjacent to the delivery locker 1. The face recognition unit 2 is provided with a camera 8 and a display 9. The camera 8 captures a picture of the user's face. The display 9 displays a guide screen regarding face recognition. The display 9 may be configured as a touch panel so that the user can operate the screen.

[0043] Next, there will be described a schematic configuration of the delivery locker 1 and the face recognition unit 2. Fig. 3 is a block diagram showing a schematic configuration of the delivery locker 1 and the face recognition unit 2.

[0044] In addition to the electronic lock 12, the delivery locker 1 is equipped with a communication unit 13, a memory unit 14, and a processor 15.

[0045] The communication unit 13 communicates with the management server 3. The communication unit 13 also communicates with the face authentication device 7.

[0046] The storage unit 14 stores programs and the like executed by the processor 15. The storage unit 14 also stores registration information of a user database.

[0047] The processor 15 performs various processes by executing the programs stored in the storage unit 14. In this embodiment, the processor 15 performs an unlocking determination process, a door opening / closing control process, and the like.

[0048] In the unlocking determination process, the processor 15 determines whether or not the storage box 11 can be unlocked, i.e., whether or not to permit unlocking of the storage box 11, based on the face matching result obtained from the face authentication device 7 and the user's setting information registered in the user database.

[0049] In the door opening / closing control process, the processor 15 controls the opening / closing of the door of the storage box 11 based on the unlocking determination result. Specifically, if the determination result indicates that unlocking is permitted, the electronic lock 12 is controlled to unlock the storage box 11, and if the determination result indicates that unlocking is not permitted, the storage box 11 is kept locked.

[0050] The face recognition unit 2 includes a camera 8, a display 9, and a face recognition device 7.

[0051] The face authentication device 7 includes a communication unit 71, a memory unit 72, and a processor 73.

[0052] The communication unit 71 communicates with the delivery locker 1. The communication unit 71 also communicates with the management server 3.

[0053] The storage unit 72 stores programs executed by the processor 73, etc. The storage unit 72 also stores registration information of a facial feature amount database. The registration information of the facial feature amount database is erased when the power supply of the facial authentication device 7 is turned off. Here, if the registration information of the facial feature amount database is stored in a volatile memory, it is erased when the power supply is turned off, but an active erasure operation may be performed when the power supply is turned off. In this way, since the facial authentication device 7 is tamper-resistant, it is possible to safely handle facial feature amount data required for facial authentication even in the unlikely event that the facial authentication device 7 is stolen.

[0054] The processor 73 performs various processes by executing the programs stored in the storage unit 72. In this embodiment, the processor 73 performs face image acquisition process, face feature extraction process, face matching process, distribution request process, update status inquiry process, restart control process, schedule management process, GUI control process, and the like.

[0055] In the face image acquisition process, the processor 73 detects a person's face from an image captured by the camera 8, cuts out a face area from the captured image, and acquires a face image of the user.

[0056] In the facial feature extraction process, the processor 73 extracts facial features from the facial image of the user acquired in the facial image acquisition process.

[0057] In the face matching process, the processor 73 matches the facial features of the user acquired in the facial feature extraction process with the facial features of the user registered in the facial feature database of the own device.

[0058] In the distribution request process, the processor 73 makes a distribution request of face information (facial feature amount) to the management server 3. That is, the processor 73 requests the management server 3 to distribute the facial feature amount registered in the facial feature amount database of the facial information server 4 to the own device. In this embodiment, the distribution request of the facial information is made in response to the power-on (start-up) of the own device.

[0059] In the update status inquiry process, the processor 73 inquires of the management server 3 about the update status (presence or absence of an update) of the face information managed by the face information server 4, i.e., whether or not the face information managed by the face information server 4 has been updated since the most recent update date and time of the face information held in the device.

[0060] In the restart control process, the processor 73 restarts the device according to a preset schedule. That is, when the processor 73 determines that it is time to restart the device based on the preset restart schedule, the processor 73 restarts the device.

[0061] In the schedule management process, the processor 73 manages the restart schedule. Specifically, the processor 73 randomly sets the time to perform the restart based on a random number or the like. In this case, the implementation period of the restart may be set by a schedule, and the implementation time of the restart may be set randomly within the implementation period. The processor 73 also sets the restart schedule based on various statistical processes. In particular, the restart schedule is set based on the frequency of face authentication performed by the device itself, that is, the number of face authentications performed in a predetermined period.

[0062] In the schedule management process, the processor 73 manages the schedule for the update status inquiry. The processor 73 also manages the schedule for the distribution request that is made regardless of the restart. The restart schedule, the update status inquiry schedule, and the distribution request schedule can be designated by the administrator.

[0063] In the GUI control process, the processor 73 displays a guide screen relating to face authentication on the display 9. The processor 73 also acquires input information corresponding to a user's operation on the screen displayed on the display 9.

[0064] Next, a description will be given of the schematic configuration of the management server 3 and the face information server 4. Fig. 4 is a block diagram showing the schematic configuration of the management server 3 and the face information server 4.

[0065] The management server 3 includes a communication unit 31, a storage unit 32, and a processor 33.

[0066] The communication unit 31 communicates with the delivery locker 1, the face authentication machine 7, and the user terminal 5. The communication unit 31 also communicates with the face information server 4.

[0067] The storage unit 32 stores programs and the like executed by the processor 33. The storage unit 32 also stores registration information of a user database.

[0068] The processor 33 performs various processes by executing the programs stored in the storage unit 32. In this embodiment, the processor 33 performs a user registration process, an information management process, a delivery control process, an update confirmation process, and the like.

[0069] In the user registration process, the processor 33 displays a registration screen 101 (see FIG. 5) on the user terminal 5, and acquires setting information and a face image of the user based on an operational input on the registration screen 101 by the user.

[0070] In the information management process, the processor 33 manages the user setting information registered in the user database. Specifically, the processor 33 registers the user setting information acquired by the user registration process in the user database. The processor 33 also distributes the user setting information registered in the user database to the delivery locker 1.

[0071] In the distribution control process, the processor 33 distributes face information (facial features) registered in the face information database (facial feature database) of the face information server 4 to the face authentication device 7 in response to a distribution request from the face authentication device 7. Here, in the case of a distribution request when inquiring about an update status, differential data of face information, i.e., face information related to the update, is distributed among the face information of the user related to the face authentication device 7 of the distribution destination. On the other hand, in the case of a distribution request after a reboot, all data of face information, i.e., all face information of the user related to the face authentication device 7 of the distribution destination is distributed.

[0072] In the update confirmation process, the processor 33 determines whether there is an update to the face information managed by the face information server 4 in response to an update status inquiry from the face authentication device 7, that is, whether the face information managed by the face information server 4 has been updated since the most recent update date and time of the face information held in the inquiring face authentication device 7. Note that information regarding the update date and time of the face authentication device 7 may be obtained by a message from the face authentication device 7, or the management server 3 may manage information regarding the update date and time for each face authentication device 7.

[0073] The face information server 4 includes a communication unit 41, a storage unit 42, and a processor 43.

[0074] The communication unit 41 communicates with the management server 3 .

[0075] The storage unit 42 stores programs and the like executed by the processor 43. The storage unit 42 also stores registration information of a face image database and registration information of a face feature amount database.

[0076] The processor 43 performs various processes by executing the programs stored in the storage unit 42. In this embodiment, the processor 43 performs information management processing, facial feature extraction processing, and the like.

[0077] In the information management process, the processor 43 manages the face images registered in the face image database and the face features registered in the face feature database. Specifically, the processor 43 registers the face images acquired from the user terminal 5 via the management server 3 in the face image database. The processor 43 also registers the face features acquired in the face feature extraction process in the face feature database. The processor 43 also delivers the face features registered in the face feature database to the face authentication device 7 via the management server 3.

[0078] In the facial feature extraction process, the processor 43 extracts facial features from the facial image of the user registered in the facial image database.

[0079] Next, the registration screen 101 displayed on the user terminal 5 during user registration will be described. FIG.

[0080] At the time of user registration, a registration screen 101 is displayed on the user terminal 5 based on screen information distributed from the management server 3. On the registration screen 101, the user's setting information and face image can be registered.

[0081] The registration screen 101 is provided with an attribute information input section 102. The attribute information input section 102 is provided with input fields for the authentication subject category, the authentication subject ID, phonetic reading, and name. The authentication subject category may be, for example, a resident, a caretaker, a maintenance worker, etc.

[0082] The registration screen 101 is also provided with a usage condition specification section 103. The usage condition specification section 103 is provided with input fields for the start date and start time related to the usage start date and time. The usage condition specification section 103 is also provided with input fields for the valid date and time related to the valid period (usage end date and time). The usage condition specification section 103 is also provided with an input field for specifying whether the usage authority of the target user is to be valid or invalid. Here, the usage authority of the user can be invalidated when the resident does not use the delivery locker 1 temporarily due to a long absence or other reason. Furthermore, when the usage period of the dwelling unit is specified in a rental contract or the like, the validity period can be set to match that usage period.

[0083] The registration screen 101 also has a dwelling unit information input section 104. The dwelling unit information input section 104 has input fields for the dwelling unit number and the dwelling unit name. The dwelling unit information input section 104 also has a "select" button 111. When the user operates the "select" button 111, a list screen (not shown) of dwelling unit numbers for the target facility (apartment building) is displayed, and the user can input the dwelling unit number and the dwelling unit name by selecting the dwelling unit number on the list screen. When registering multiple users (residents) for the same dwelling unit, the operation of the registration screen 101 is repeated for each user.

[0084] The registration screen 101 also has an authentication method designation section 105. The authentication method designation section 105 has tabs 121 of "face authentication", "numeric keypad", and "card". In this example, at least one of face authentication, code authentication, and card authentication can be selected as the personal authentication, and when face authentication is performed, the "face authentication" tab 121 is operated to input settings related to face authentication. When code authentication is performed, the "numeric keypad" tab 121 is operated to input settings related to code authentication. When card authentication is performed, the "card" tab 121 is operated to input settings related to card authentication.

[0085] When the "Facial Recognition" tab 121 is operated, a check box 122 for specifying whether or not to use facial recognition, a "Delete Image" button 123, a "Select Image" button 124, and a screen display section 125 are displayed. When the user operates the "Select Image" button 124, a list screen (not shown) of facial images saved in the user terminal 5 is displayed, and when the user selects a facial image on the list screen, the facial image is imported and displayed on the screen display section 125. When the user operates the "Delete Image" button 123, the imported facial image can be deleted. Note that multiple facial images may be registered for one user.

[0086] The registration screen 101 is also provided with a box allocation section 106. In the box allocation section 106, a storage box 11 (a dwelling unit dedicated box) can be allocated to each user (dwelling unit) in the delivery locker 1. The box allocation section 106 is provided with a "storage box allocation" button 131 and a list display section 132. When a user operates the "storage box allocation" button 131, a list screen (not shown) of storage boxes 11 (dwelling unit dedicated boxes) is displayed. When the user selects a storage box 11 on the list screen, the selected storage box 11 is allocated to the user, and the number of the allocated storage box 11 is displayed in the list display section 132. Note that if there is a storage box 11 that has already been allocated to another resident or the like, only vacant storage boxes 11 can be presented on the list screen to prompt the user to make a selection.

[0087] Furthermore, the registration screen 101 is provided with an "Update" button 107. When the user operates the "Update" button 107, information based on the input contents of each section is registered in the user database of the management server 3 and the face information database (face image database and face feature amount database) of the face information server 4. Specifically, the setting information of the user input on the registration screen 101 is registered in the user database of the management server 3. Furthermore, the face image captured on the registration screen 101 is registered in the face image database of the face information server 4, and the face feature amount extracted from the face image is registered in the face feature amount database.

[0088] In this embodiment, the user's setting information and face information (face image and face feature amount) are registered by operating the registration screen 101 displayed on the user terminal 5, and the registration screen 101 is operated at any time as necessary to update (add, delete, change, etc.) the registered information in the user database of the management server 3 and the face information database (face image database, face feature amount database) of the face information server 4. For example, when a new user starts using the service, the user's setting information and face information are added. When the user ends use, the user's setting information and face information are deleted. When the update deadline arrives, the user's setting information and face information are changed to new face information.

[0089] Next, a description will be given of the processing at the time of user registration, which is carried out by the delivery locker 1, management server 3, face information server 4, user terminal 5, and face authentication device 7. Fig. 6 is a sequence diagram showing an overview of the processing at the time of user registration.

[0090] The user terminal 5 displays the registration screen 101 (see FIG. 5 ) based on the screen information delivered from the management server 3. Next, the user terminal 5 acquires the setting information and facial image of the user in response to the user's operational input on the registration screen 101, and transmits the setting information and facial image of the user to the management server 3.

[0091] When the management server 3 receives the setting information and the facial image of the user from the user terminal 5, the management server 3 registers the setting information of the user in the user database. In addition, the management server 3 transfers the facial image of the user to the facial information server 4.

[0092] When the face information server 4 receives the face image of the user from the management server 3, it registers the face image of the user in the face image database. In addition, the face information server 4 extracts face features from the face image of the user and registers the face features of the user in the face feature database.

[0093] In addition, at the start of operation and at a specified timing after the start of operation, setting information for each user registered in the user database of the management server 3 is distributed to the delivery locker 1. In addition, facial features (facial information) for each user registered in the facial feature database of the facial information server 4 is distributed to the facial authentication device 7.

[0094] Next, a description will be given of a guide screen regarding face authentication displayed on the display 9 of the face authentication unit 2. Fig. 7 is an explanatory diagram showing the guide screen regarding face authentication.

[0095] First, an initial screen 201 (standby screen) shown in Fig. 7(A) is displayed on the display 9 of the face authentication unit 2. Next, the screen transitions to an authentication in progress screen 202 shown in Fig. 7(B). At this time, the face authentication device 7 starts face matching processing.

[0096] An image captured by the camera 8 is displayed on the authentication in progress screen 202 (see FIG. 7(B)). Furthermore, characters and figures indicating that face authentication is in progress are displayed on the authentication in progress screen 202. When the face matching process is completed (successful), the screen transitions to a face authentication completion screen 203 shown in FIG. 7(C).

[0097] Characters and figures indicating that face authentication has been completed are displayed on the face authentication completion screen 203 (see FIG. 7(C)). Next, the screen transitions to an unlock notification screen 204 shown in FIG. 7(D).

[0098] The unlock notification screen 204 (see FIG. 7(D)) displays text indicating that the storage box 11 has been unlocked and text encouraging the user to remove their luggage. When the storage box 11 is unlocked, the user can open the door of the storage box 11 and remove their luggage from the storage box 11. If an indicator such as an LED lamp is provided for each storage box 11 and the indicator is made to flash (light up) when the storage box is unlocked, the user can remove their luggage more smoothly.

[0099] In the case of a storage box 11 (shared box) shared by all the dwelling units in an apartment building, the number and position of the unlocked storage box 11 may be displayed, for example, on the unlocking notification screen 204 (see FIG. 7(D)).

[0100] Next, a description will be given of the face authentication process carried out in the delivery locker 1 and the face authentication device 7. Fig. 8 is a sequence diagram showing an overview of the face authentication process.

[0101] The face authentication device 7 acquires a face image of the user from an image captured by the camera 8 (face image acquisition process). Next, the face authentication device 7 extracts face features from the face image of the user (face feature extraction process). Next, the face authentication device 7 compares the face features of the user with face features registered in the face feature database of the device itself (face matching process). Next, the face authentication device 7 transmits the face matching result to the delivery locker 1.

[0102] Next, the delivery locker 1 determines whether or not the storage box 11 can be unlocked, that is, whether or not to permit unlocking of the storage box 11, based on the face matching result obtained from the face authentication device 7 and the user's setting information registered in the user database (unlock determination process). Next, the delivery locker 1 notifies the face authentication device 7 of the unlock determination result, and reflects it on the unlock notification screen 204 (see FIG. 7(D)) etc.

[0103] Next, the delivery locker 1 controls the opening and closing of the door of the storage box 11 based on the unlocking determination result (door opening and closing control process). Specifically, if the determination result indicates that unlocking is permitted, the electronic lock 12 is controlled to unlock the storage box 11, and if the determination result indicates that unlocking is not permitted, the storage box 11 is kept locked.

[0104] Next, a description will be given of the unlocking process carried out by the face authentication device 7 and the delivery locker 1. Fig. 9 is a block diagram showing an overview of the unlocking process.

[0105] As an unlocking determination process, the delivery locker 1 determines whether or not the storage box 11 can be unlocked, that is, whether or not to permit unlocking, based on the face matching result obtained from the face authentication device 7 and the setting information of the user registered in the user database. Specifically, it determines whether or not the permission conditions (validity period, etc.) included in the setting information of the user identified by successful face matching are satisfied. At this time, if there is no storage box 11 containing a package addressed to the user (above) identified by face authentication, it is determined that the user does not have the authority to unlock.

[0106] Next, the delivery locker 1 notifies the face authentication device 7 of the unlocking determination result. Furthermore, the delivery locker 1 controls the opening and closing of the door of the storage box 11 according to the unlocking determination result as a door opening and closing control process. That is, if the determination result is that unlocking is permitted, the electronic lock 12 is controlled to unlock the storage box 11, and if the determination result is that unlocking is not permitted, the storage box 11 is kept locked.

[0107] As a GUI control process, the face authentication machine 7 displays images 211, 212, and 213 representing the result of face authentication and the state of the electronic lock 12 on the display 9 according to the contents of the unlocking determination result received from the delivery locker 1. Specifically, if face authentication fails, an image 211 representing authentication failure and unlocking not permitted is displayed. If face authentication is successful and the user does not have the authority to unlock, an image 212 representing authentication success and unlocking not permitted is displayed. If face authentication is successful and the user has the authority to unlock, an image 213 representing authentication success and unlocking permitted is displayed. The images 211, 212, and 213 are displayed on the display 9 at the same time that the unlocking notification screen 204 shown in FIG. 7(D) is displayed, for example.

[0108] Next, a description will be given of the process at the time of rebooting, which is performed by the management server 3, the face information server 4, and the face authentication device 7. Fig. 10 is a sequence diagram showing an overview of the process at the time of rebooting.

[0109] When the face authentication device 7 determines that it is time to restart the device based on a preset restart schedule, the face authentication device 7 restarts the device itself (restart control process). That is, the face authentication device 7 is powered off and then powered on.

[0110] Next, the face authentication device 7 checks the installation environment. That is, it determines whether there is a change in the installation environment of the face authentication device 7. For example, it determines whether the network to which the face authentication device 7 is connected is the same as before the reboot. Here, if there is no change in the installation environment of the face authentication device 7, the face authentication device 7 transmits a distribution request message to the management server 3. On the other hand, if there is a change in the installation environment of the face authentication device 7, it does not transmit the distribution request message to the management server 3.

[0111] Next, when the management server 3 receives the distribution request message from the face authentication device 7, it requests the face information server 4 to transfer face information (facial feature amounts). In response to the request for transfer of face information from the management server 3, the face information server 4 transfers all data of face information related to the requesting face authentication device 7 to the management server 3. The management server 3 transmits all data of face information transferred from the face information server 4 to the face authentication device 7.

[0112] Next, when the face authentication device 7 receives all the data of the face information from the management server 3, it registers all the received data of the face information (facial feature amount) in the facial feature amount database of its own device.

[0113] In this way, in this example, by restarting the face authentication device 7, the update of the face information on the face information server 4 side can be reflected on the face authentication device 7 side. In particular, the face authentication device 7 erases all data of the face information stored in its own device in response to turning off the power of its own device, so that when the face authentication device 7 is restarted, all the face information stored in the face authentication device 7 is rewritten. In addition, the operation of the face authentication device 7 can be stabilized by refreshing the memory etc. accompanying the restart of the face authentication device 7.

[0114] Furthermore, in this embodiment, since the face authentication system is an edge type, that is, face authentication is performed by the face authentication device 7 as an edge device, even if a failure occurs in the network (such as the Internet) and communication between the face authentication device 7 and the cloud (the management server 3 and the face information server 4) is interrupted, face authentication can continue by the face authentication device 7. Meanwhile, there is a risk that the security of the face information as personal information may be reduced due to the risk of the face authentication device 7 being stolen, but if the face authentication device 7 is stolen, the power is turned off and all face information data is erased, so the security of the face information can be ensured.

[0115] Furthermore, in this example, when the facial authentication device 7 is restarted, the installation environment of the facial authentication device 7 is checked, and if there is a change in the installation environment of the facial authentication device 7, the management server 3 does not deliver facial information to the facial authentication device 7. Therefore, even if the facial authentication device 7 is stolen and started up in another location, the facial authentication device 7 cannot obtain facial information from the management server 3, and all facial information data remains erased when the power is turned off, so that the facial information of the facial authentication device 7 can be safely managed. Note that, as a detection of a change in the installation environment of the facial authentication device 7, the presence or absence of a change can be detected based on the position information at the time when the facial authentication device 7 was started up.

[0116] Here, as a restart control process, the face authentication device 7 restarts its own device when it is determined that it is time to restart the device based on a preset restart schedule. Furthermore, as a schedule management process, the face authentication device 7 manages the restart schedule. In the restart schedule, the timing of the restart may be set so that the face authentication device 7 is restarted periodically. For example, the restart may be performed once a day at a specified time. In this case, it is preferable to perform the restart during a time period when the face authentication device 7 is less used (late at night or early in the morning).

[0117] Furthermore, the face authentication machine 7 can randomly set the time to perform the reboot as a schedule management process. The time to perform the reboot may be set by a random number. Furthermore, the period during which the reboot is performed may be set by a schedule, and the time to perform the reboot may be set randomly within the period.

[0118] When the management server 3 manages face information used by multiple face authentication devices 7 and distributes the face information to the multiple face authentication devices 7, if the restart timings of the multiple face authentication devices 7 are the same, the timing of the distribution of the face information will be concentrated, resulting in a significant load on the management server 3. On the other hand, if the restart is performed at a randomly set time in each face authentication device 7, the timing of the restart will differ among the multiple face authentication devices 7, and the timing of the distribution of the face information will be distributed, thereby reducing the load on the management server 3.

[0119] Furthermore, the face authentication device 7 can set a restart schedule based on various statistical processes as a schedule management process. In particular, the restart schedule is set based on the frequency of face authentication performed by the device itself, that is, the number of face authentications performed in a predetermined period.

[0120] When the number of users is large, the frequency of face authentication performed by the face authentication device 7 increases, and the frequency of updating face information performed by the face information server 4 increases, and the frequency of face authentication and the frequency of updating face information are correlated with the number of users. Therefore, by setting a restart schedule based on the frequency of face authentication, it is possible to restart the face authentication device 7 at an appropriate timing according to the frequency of updating face information. Specifically, for example, it is preferable to set the restart schedule so that the restart interval becomes shorter as the frequency of face authentication performed by the face authentication device 7 increases.

[0121] The restart schedule may also be set based on the number of users (registered persons) managed by management server 3. The restart schedule may also be set based on the number of units and / or the number of residents in an apartment building in which delivery lockers 1 are installed.

[0122] It should be noted that there may be cases where it is necessary to urgently update the face information held in the face authentication device 7, for example, for maintenance of the face authentication device 7. In this case, the face authentication device 7 may be restarted by an operator's operation, regardless of the restart schedule.

[0123] Next, a description will be given of the process performed at the time of an update status inquiry in the management server 3, the face information server 4, and the face authentication device 7. Fig. 11 is a sequence diagram showing an overview of the process at the time of an update status inquiry.

[0124] When the face authentication device 7 determines that it is time to perform an update status inquiry based on a preset schedule for the update status inquiry, it transmits an update status inquiry message to the management server 3. Here, the schedule for the update status inquiry may be such that the update status inquiry is performed periodically. For example, the update status inquiry may be performed once every half day or once every three hours.

[0125] Next, when the management server 3 receives the update status inquiry message from the face authentication device 7, it determines whether there is an update to the face information managed by the face information server 4, that is, whether the face information managed by the face information server 4 has been updated since the most recent update date and time of the face information held in the face authentication device 7 that originated the inquiry (update confirmation process). Here, if there is no update to the face information managed by the face information server 4, it sends a message of the inquiry result to that effect to the face authentication device 7.

[0126] Next, the face authentication device 7 does not perform any particular process when it receives a message from the management server 3 indicating that there is no update. Next, when the face authentication device 7 determines that it is time to perform an update status inquiry based on a preset update status inquiry schedule, it transmits an update status inquiry message to the management server 3.

[0127] Next, when the management server 3 receives the update status inquiry message from the face authentication device 7, it determines whether there is an update to the face information managed by the face information server 4 (update confirmation process). If there is an update to the face information managed by the face information server 4, it sends a message of the inquiry result to that effect to the face authentication device 7.

[0128] Next, when the face authentication device 7 receives a message from the management server 3 indicating that there is an update, the face authentication device 7 transmits a message to the management server 3 requesting distribution.

[0129] Next, when the management server 3 receives the distribution request message from the face authentication device 7, it requests the face information server 4 to transfer the face information. In response to the request for transfer of face information from the management server 3, the face information server 4 transfers differential data of the face information related to the requesting face authentication device 7 (face information related to the update) to the management server 3. The management server 3 transmits the differential data of the face information transferred from the face information server 4 to the face authentication device 7.

[0130] Next, when the face authentication device 7 receives the difference data of the face information from the management server 3, it updates the face feature amount database of the device itself with the received difference data of the face information.

[0131] Next, a description will be given of the processing at the time of a distribution request including an update status inquiry, which is performed by the management server 3, the face information server 4, and the face authentication device 7. Fig. 12 is a sequence diagram showing an overview of the processing at the time of a distribution request including an update status inquiry.

[0132] When the face authentication device 7 determines that it is time to execute a delivery request based on a preset delivery request schedule, it transmits a delivery request message including an update status inquiry to the management server 3. Here, the delivery request schedule is the same as that of the update status inquiry (see FIG. 11).

[0133] Next, when the management server 3 receives the distribution request message from the face authentication device 7, it determines whether there is an update to the face information managed by the face information server 4 (update confirmation process). If there is no update to the face information managed by the face information server 4, it sends a message of the inquiry result to that effect to the face authentication device 7.

[0134] Next, the face authentication device 7 does not perform any particular process when it receives a message from the management server 3 indicating that there is no update. Next, when the face authentication device 7 determines that it is time to execute the delivery request based on a timing determination based on a preset delivery request schedule, it transmits a delivery request message including an update status inquiry to the management server 3.

[0135] Next, when the management server 3 receives a delivery request message including an update status inquiry from the face authentication device 7, it determines whether there is an update to the face information managed by the face information server 4 (update confirmation process). If there is an update to the face information managed by the face information server 4, it requests the face information server 4 to transfer the face information. In response to the request for transfer of face information from the management server 3, the face information server 4 transfers differential data of the face information related to the face authentication device 7 that made the request (face information related to the update) to the management server 3. The management server 3 transmits the differential data of the face information transferred from the face information server 4 to the face authentication device 7.

[0136] Next, when the face authentication device 7 receives the difference data of the face information from the management server 3, it updates the face feature amount database of the device itself with the received difference data of the face information.

[0137] 11 and 12, the management server 3 performs an update confirmation process to determine whether or not there has been an update to the face information managed by the face information server 4, that is, whether or not the face information managed by the face information server 4 has been updated since the most recent update date and time of the face information held in the query source face authentication device 7. For this reason, information regarding the most recent update date and time of the face information held in the face authentication device 7 may be added to the update status query message. In addition, the management server 3 may manage the update date and time of the face authentication device 7.

[0138] Furthermore, the update confirmation process may be performed by the face authentication device 7. In this case, information regarding the update date and time of the face information managed by the face information server 4 may be transmitted from the management server 3 to the face authentication device 7.

[0139] As described above, the embodiments have been described as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited to these, and can be applied to embodiments in which modifications, substitutions, additions, omissions, etc. are made. In addition, it is also possible to combine the components described in the above embodiments to create new embodiments. [Industrial Applicability]

[0140] The facial recognition system and facial recognition method of the present invention can easily implement a process for reflecting updates (addition, deletion, change, etc.) of facial information on the server device side on the facial recognition device side, and has the effect of enabling daily facial recognition to be performed without hindrance while safely managing the facial information, which is personal information, even if the facial information is updated from time to time on the server device, and is useful as a facial recognition system and facial recognition method that performs facial recognition to allow only legitimate users (registered persons) to unlock a storage device. [Explanation of symbols]

[0141] 1. Delivery locker (storage device) 2 Face Recognition Unit 3 Management server (server device) 4. Face information server (server device) 5 User terminal (registration device) 7. Facial recognition machine (face recognition device) 8. Camera 9. Display 11 Storage Box 12 Electronic Lock

Claims

1. a storage device that is locked and unlocked by an electronic lock; a face authentication device that is installed near the storage device and acquires face information of a user and compares the face information of the user with preregistered face information in order to permit the user to unlock the storage device; a server device connected to the face authentication device via a network, for managing face information for each user, and for distributing the face information to the face authentication device; The face recognition device includes: When the device is powered on due to a reboot, the device issues a request for delivery of face information to the server device; The server device includes: A face authentication system comprising: a face authentication device that transmits face information related to the requesting face authentication device to the face authentication device in response to the transmission request from the face authentication device.

2. The face recognition device includes: The face authentication system according to claim 1, characterized in that an update status inquiry is periodically made to the server device to inquire whether the face information managed by the server device has been updated since the most recent update date and time of the face information held by the server device.

3. The face recognition device includes:

2. The face authentication system according to claim 1, wherein the face information held in the device is deleted when the device is powered off.

4. The face recognition device includes:

2. The face authentication system according to claim 1, wherein the reboot is performed according to a preset schedule.

5. The face recognition device includes:

2. The face authentication system according to claim 1, wherein the time for performing the reboot is set randomly.

6. The face recognition device includes:

2. The face authentication system according to claim 1, wherein a reboot schedule is set based on a frequency of face authentication performed by the face authentication system itself.

7. The face recognition device comprises:

4. The face authentication system according to claim 3, further comprising: determining whether or not there has been a change in an installation environment of the face authentication system itself; and, if it is determined that there has been a change in the installation environment, not transmitting the distribution request to the server device.

8. a storage device that is locked and unlocked by an electronic lock; a face authentication device that is installed near the storage device and acquires face information of a user and compares the face information of the user with preregistered face information in order to permit the user to unlock the storage device; A storage system including a server device connected to the face authentication device via a network, for managing face information for each user, and for distributing the face information to the face authentication device, The face recognition device, When the device is powered on due to a reboot, the device issues a request for delivery of face information to the server device; The server device, A face authentication method comprising the steps of: in response to the distribution request from the face authentication device, distributing face information related to the face authentication device that is a request source to the face authentication device.

Images