Facial recognition registration system, facial recognition device, and facial recognition registration method

Abstract

To prevent generation of a case in which the face of a user can be authenticated in one system and cannot be authenticated in another system when the face information of the user is stored by a plurality of face authentication machines set in a facility so that the face is authenticated.SOLUTION: A face authentication registration system 50 includes: a face registration server 30 for storing face information; and a plurality of authentication devices 21 to 23 for registering face information and using the face information for face authentication. The face registration server 30 receives a synchronization event of the face information and executes synchronization processing of the face information on the plurality of face authentication devices 21 to 23 as targets, and performs control so that the face authentication devices 21 to 23 are returned to the state before synchronization even if one of the face authentication devices 21 to 23 fails to be synchronized.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] The present invention relates to a face authentication registration system, a face authentication device, and a face authentication registration method.

Background Art

[0002] Conventionally, a face authentication system that executes face authentication processing based on image data of a subject has been developed.

[0003] For example, Patent Document 1 discloses a technique for significantly reducing the processing load and device cost on the face authentication machine side by dividing the processing required for face authentication in a face authentication system. The face authentication system described in Patent Document 1 has a plurality of face authentication machines and a server device connected to the face authentication machines via a network. This server device has a plurality of face matching units that perform face matching. Each face matching unit has a face matching process for executing a face matching program on the face image data of the user received from the face authentication machine, and a face matching database in which information (face feature amount data) of the user to be compared for face matching is registered.

[0004] In addition, paragraph

[0273] of Patent Document 1 describes that "users who have failed in face registration are reported to the administrator and urged to re-register." Also, paragraph

[0288] describes that "when face registration fails, a request for deleting face feature amounts is not made, and face matching is performed with the old face feature amounts."

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] By the way, in a configuration such as the one described in Patent Document 1, where multiple facial recognition devices and a server device having a facial matching process and a facial matching database are connected via a network, if a communication failure occurs, the facial recognition devices will not be able to obtain the user's authentication result.

[0007] To resolve the above inconveniences, a possible configuration is in which a facial recognition device installed at the facility used by the user stores the user's facial information (e.g., facial feature data), and the facial recognition device matches the user's facial image data with the facial information.

[0008] However, when storing a person's facial information in multiple facial recognition devices, if registration of new facial information fails with a particular facial recognition device, the following problem arises: If the registration failure with a specific facial recognition device is left unaddressed, different behaviors may occur. For example, access control equipment linked to a facial recognition device with successful registration may be able to authenticate (unlock), but access control equipment linked to a facial recognition device with failed registration may not be able to authenticate (unlock).

[0009] Furthermore, while Patent Document 1 describes prompting users who have failed to register their faces to re-register, there are cases where re-registration fails even after the user attempts to register again. Also, in the technology described in Patent Document 1, if face registration fails, face matching is performed using the old facial features.

[0010] Given the above situation, it was desirable to prevent discrepancies in the occurrence of situations where authentication could be performed by one device but not another when multiple facial recognition devices installed at the facility were used to store and perform facial recognition on the user's face. [Means for solving the problem]

[0011] To solve the above problems, one aspect of the present invention provides a face recognition registration system comprising a face registration server that stores face information and a plurality of face recognition devices that register face information and use it for face recognition. When the face registration server receives a face information synchronization event, it performs face information synchronization processing on the target plurality of face recognition devices, and if synchronization fails on any one of the plurality of face recognition devices, it controls the plurality of face recognition devices to return to the state before the synchronization processing. [Effects of the Invention]

[0012] According to at least one aspect of the present invention, when a user's facial information is stored and facial recognition is performed using multiple facial recognition devices installed on the facility side, it is possible to prevent the occurrence of discrepancies such as authentication being possible with one device but not with another. Other issues, configurations, and effects not mentioned above will be clarified by the following description of the embodiments. [Brief explanation of the drawing]

[0013] [Figure 1] This figure shows an example of a scenario in which a facial recognition registration system according to one embodiment of the present invention is used. [Figure 2] This figure shows an example of the overall configuration of a facial recognition registration system and an overview of facial registration according to one embodiment of the present invention. [Figure 3] This figure shows an example of the functional configuration of a facial recognition device according to one embodiment of the present invention. [Figure 4] This figure shows an example of the functional configuration of a face registration server according to one embodiment of the present invention. [Figure 5] This is a block diagram showing an example of the hardware configuration of a computer provided in each device constituting a facial recognition registration system according to one embodiment of the present invention. [Figure 6] This is a sequence chart showing an example of a face registration process (successful) by a face recognition registration system according to one embodiment of the present invention. [Figure 7] This figure shows an example of a synchronization target list created during face registration processing (successfully) in a face recognition registration system according to one embodiment of the present invention. [Figure 8] A sequence chart showing an example of face registration processing (failure) by a face authentication registration system according to an embodiment of the present invention. [Figure 9] A diagram showing an example of a synchronization target list created during face registration processing (failure) in a face authentication registration system according to an embodiment of the present invention. [Figure 10] A sequence chart showing an example of face deletion processing (normal) by a face authentication registration system according to an embodiment of the present invention. [Figure 11] A diagram showing an example of a synchronization target list created during face deletion processing (normal) in a face authentication registration system according to an embodiment of the present invention. [Figure 12] A sequence chart showing an example of face deletion processing (failure) by a face authentication registration system according to an embodiment of the present invention. [Figure 13] A diagram showing an example of a synchronization target list created during face deletion processing (failure) in a face authentication registration system according to an embodiment of the present invention.

Mode for Carrying Out the Invention

[0014] Hereinafter, examples of embodiments for carrying out the present invention (hereinafter referred to as "embodiments") will be described with reference to the accompanying drawings. In this specification and the accompanying drawings, the same reference numerals are assigned to the same components or components having substantially the same functions, and duplicate descriptions are omitted.

[0015] <One Embodiment> [Scene of Using the Face Authentication Registration System] First, an example of using a face authentication registration system according to an embodiment of the present invention will be described with reference to FIG. 1. FIG. 1 is a diagram showing an example of a scene of using a face authentication registration system according to an embodiment of the present invention. The configuration of the face authentication registration system will be described in detail later in FIGS. 2 and subsequent figures.

[0016] One example of how the facial recognition registration system can be used is to provide a facial recognition-based entry and exit service to residents of apartment buildings (also known as "mansions" in Japan). As shown in Figure 2, which will be described later, the facial recognition registration system according to this embodiment is a system that allows facial registration from the cloud (facial registration server 30 in Figure 2, which will be described later) to a facial recognition device that has a facial recognition function using AI (Artificial Intelligence), etc.

[0017] Residents of an apartment building (U) can access various entry and exit services by registering their faces in a facial recognition registration system using a mobile device or similar device. For example, an apartment building may have two doors at its entrance. The first door 1 is an automatic door, allowing anyone other than resident U to enter and exit. The second door 2, accessed after passing through the first door 1, is an auto-locking door, requiring either an unlocking method (key, PIN, or facial image) or unlocking by resident U.

[0018] If facial registration is complete, resident U can unlock the second door 2 by authenticating their facial image captured by surveillance camera 4. Furthermore, resident U can call elevator 3 and automatically register their destination floor by authenticating their facial image captured by surveillance camera 5 in the elevator hall. Resident U's face and destination floor are linked through prior registration. Such a facial recognition registration system can also be applied to access control services in office buildings, factories, and other similar facilities.

[0019] [Overall configuration of the facial recognition registration system and overview of facial registration] Next, the overall configuration of the facial recognition registration system according to this embodiment and an overview of facial registration will be described with reference to Figure 2. Figure 2 shows an example of the overall configuration of the facial recognition registration system according to this embodiment and an overview of facial registration.

[0020] In Figure 2, the facial recognition registration system 50 comprises a first facial recognition device 21, a second facial recognition device 22, a third facial recognition device 23, and a facial registration server 30. In this example, the first camera 11 and the second camera 12 are connected to the first facial recognition device 21, the third camera 13 and the fourth camera 14 are connected to the second facial recognition device 22, and the fifth camera 15 and the sixth camera 16 are connected to the third facial recognition device 23. Note that the number of facial recognition devices is not limited to three; it may be two, four or more. Also, three or more cameras may be connected to a single facial recognition device.

[0021] The user operates the touch sensor implemented on the display 41 of the mobile terminal 40 to select a menu for synchronizing facial information from the menu screen. The user takes a picture of the face of the person they want to register (such as themselves or a family member) with the camera on the mobile terminal 40 and sends the facial photograph (facial image data) to the facial registration server 30 to apply for facial registration.

[0022] In addition to the mobile terminal 40, various other devices can be used to apply for facial registration, including information processing devices such as desktop PCs (Personal Computers) with integrated cameras and displays, and cameras with communication capabilities. Furthermore, applicants may also apply for facial registration using facial photographs taken in advance and stored on their devices. Those eligible to apply for facial registration are individuals who have been granted prior permission to enter and exit the facility by the manager or person in charge of the facility.

[0023] The face registration server 30 accepts face registration applications from users via mobile terminals 40. The face registration server 30 extracts feature quantities from the face image received from the mobile terminal 40 at the time of the face registration application and stores them in the database (master) as face feature quantity data to be synchronized. The face registration server 30 then transmits the face feature quantity data to the first face recognition device 21, the second face recognition device 22, and the third face recognition device 23, which are connected to the server, to synchronize the face feature quantity data. Hereafter, face feature quantity data will be abbreviated as "face features".

[0024] If the synchronization of facial features is successful, the first facial recognition device 21, the second facial recognition device 22, and the third facial recognition device 23 save the synchronized facial features to their respective databases (slaves).

[0025] In the facial recognition registration system 50 of this embodiment, the user's facial features can be synchronized with the facial recognition devices installed in the facilities used by the user (such as apartment buildings, office buildings, or factories). For example, if a first facial recognition device 21 and a second facial recognition device 22 are installed in the apartment building where the user resides, the facial registration server 30 synchronizes the facial features with the first facial recognition device 21 and the second facial recognition device 22 based on the user information.

[0026] The following explains the process from facial registration using the facial recognition registration system 50 to entering and exiting a facility (1) to (5), using entry and exit to an apartment building as an example. (1) Resident U of the apartment building takes a picture of his face with the camera of his mobile terminal 40 and sends the facial photograph (facial image) to the facial registration server 30. (2) The face registration server 30 stores the facial features extracted from the facial photographs in its database. (3) The facial features are synchronized with multiple facial recognition devices (first facial recognition device 21 to third facial recognition device 23) installed in the apartment building. (4) Multiple facial recognition devices perform facial recognition by matching facial images Im acquired from surveillance cameras with facial features synchronized from the facial registration server 30. The cameras used for facial recognition may be installed integrally with the facial recognition devices. (5) The facial recognition device, once it has authenticated resident U's face, controls the system to unlock the entrance door and call elevator 3.

[0027] Traditionally, facial features are synchronized across multiple facial recognition devices. However, if synchronization fails for only a specific facial recognition device, a gap occurs where some doors can be unlocked through facial recognition, while others cannot be unlocked due to a lack of facial recognition. For example, suppose the first camera 11 is surveillance camera 4 in Figure 1, the second camera 12 is surveillance camera 5, and the facial features of resident U are registered in the first facial recognition device 21, but not in the second facial recognition device 22. In this case, resident U can pass through the second door 2 of the entrance, but cannot call the elevator car in the elevator hall where surveillance camera 5 is installed.

[0028] Such differences are inconvenient and confusing for resident U. Therefore, it is necessary that the facial features are synchronized across all facial recognition devices installed in the facilities used by resident U. Below, we will describe how to synchronize the facial features across all facial recognition devices in the facilities used by the user in the facial recognition registration system 50 according to this embodiment.

[0029] [Functions of facial recognition devices] Figure 3 shows an example of the functional configuration of the facial recognition device according to this embodiment. The functional configuration of the facial recognition device will be explained using the first facial recognition device 21 as an example, but the same applies to the second facial recognition device 22 and the third facial recognition device 23.

[0030] The first facial recognition device 21 includes a camera image acquisition unit 211, a facial recognition unit 212, a device linkage unit 213, a facial feature synchronization client 214, and a facial feature database 215.

[0031] The camera image acquisition unit 211 acquires data in a stream from surveillance cameras installed in entrances, elevator lobbies, etc., and performs decoding from video to still images (sometimes simply called "images").

[0032] The facial recognition unit 212 performs face detection from the image acquired by the camera image acquisition unit 211. The facial recognition unit 212 then extracts feature quantities from the detected face region and compares the extracted feature quantities with the facial feature quantities stored in the facial feature quantity database 215. For example, if the feature quantity matching rate is above a predetermined standard, the facial recognition unit 212 determines that the matched facial feature quantities belong to a person whose face is registered (authentication successful).

[0033] The device linkage unit 213 notifies the access control system 60 and the elevator control panel 70 of the authentication result when facial recognition is successful in the facial recognition unit 212. For example, if facial recognition is successful, the access control system 60 unlocks the access control equipment (e.g., a door), and the elevator control panel 70 automatically registers the elevator car and destination floor. Access control equipment such as doors is an example of equipment on the facility side that employs facial recognition. In this invention, it is assumed that facial recognition will enable the use of various equipment, such as elevators 3, in addition to access control equipment.

[0034] The face feature synchronization client 214 periodically polls the face registration server 30 to check for updates to the face feature database 370. If an update is found in the face feature database 370, the face feature synchronization client 214 processes the update according to its contents.

[0035] For example, if there are additions or changes to face features in the face feature database 370 of the face registration server 30, the face feature synchronization client 214 retrieves the corresponding face features from the face registration server 30 and stores them in its own device's face feature database 215. Also, if the face feature synchronization client 214 receives a registration instruction from the face registration server 30, it retrieves the corresponding face features from the face registration server 30 and stores them in its own device's face feature database 215.

[0036] Furthermore, if a face feature is deleted from the face feature database 370 of the face registration server 30, the face feature synchronization client 214 deletes the corresponding face feature from its own device's face feature database 215. Also, if a deletion instruction is received from the face registration server 30, the face feature synchronization client 214 deletes the corresponding face feature from its own device's face feature database 215.

[0037] The facial feature database 215 is a database that stores facial features used for matching by the facial recognition unit 212. The facial feature database 215 is a slave of the facial feature database 370 owned by the facial registration server 30.

[0038] [Face Registration Server Functions] Figure 4 shows an example of the functional configuration of the face registration server 30 according to this embodiment. The face registration server 30 includes a face registration screen processing unit 310, a user information database 320, a management information registration screen processing unit 330, a device information database 340, a face registration unit 350, a face feature synchronization management unit 360, and a face feature database 370.

[0039] The face registration screen processing unit 310 generates and provides a web screen for the user to register or delete their own face with the face registration server 30 using a mobile terminal 40. The face registration screen processing unit 310 also performs login control from the mobile terminal 40 by referring to user information stored in the user information database 320.

[0040] The user information database 320 is a database that stores information about users who use the access control system 60 and elevator 3 (hereinafter referred to as "user information"). For example, user information managed includes the logged-in user, password, and information about the facilities to which the user belongs or uses. Examples of facilities to which the user belongs or uses include apartment buildings, workplaces (office buildings, factories, etc.), or facilities that the user has booked a visit to.

[0041] The management information registration screen processing unit 330 generates and provides screens for registering information about users who register facial information (user information) and information about facial recognition equipment (facial recognition devices, etc.) installed in facilities where users enter and exit. User information includes, for example, the user's name and information about the facilities used. It is assumed that the facility-side equipment information will be entered by the administrator of the facial recognition registration system 50 or the facility manager. The management information registration screen processing unit 330 stores the entered information in the user information database 320 or the equipment information database 340 according to the content of the information.

[0042] The device information database 340 manages information on authentication devices installed in facilities that users enter and exit. Authentication devices are related to entry and exit using facial recognition, such as facial recognition devices. In Figure 4, the facial recognition registration system 50 is equipped with the above-mentioned devices: a first facial recognition device 21, a second facial recognition device, and a third facial recognition device 23.

[0043] The face registration unit 350 performs processing according to the user's actions on the mobile terminal 40. User actions include face image registration events and deletion events. For example, when a face photograph is registered via the management information registration screen (i.e., a registration event occurs), the face registration unit 350 extracts face features from the face photograph and sends the face feature synchronization management unit 360 with the face feature information.

[0044] The facial feature synchronization management unit 360 manages the registration status of facial features by creating a synchronization target list, as shown in Figure 7, etc., in response to registration or deletion events received from the facial registration unit 350. The facial feature synchronization management unit 360 notifies the first facial recognition device 21, the second facial recognition device, and the third facial recognition device 23 of the update status of facial features in response to synchronization acquisition requests. The facial feature synchronization management unit 360 also plays a role in transmitting facial features to the first facial recognition device 21, the second facial recognition device, and the third facial recognition device 23. Furthermore, the facial feature synchronization management unit 360 refers to the device information database 340 and creates a synchronization target list for the facial recognition devices installed at the target facility.

[0045] The facial feature database 370 is a database in the facial registration server 30 that stores information on facial features. The facial feature database 370 is the master of the facial feature databases 215 owned by the first facial recognition device 21, the second facial recognition device, and the third facial recognition device 23.

[0046] The user is only aware of whether the registration of facial information (hereinafter also referred to as "facial registration") was successful or unsuccessful. Conversely, the user is not aware of which facial recognition device was used to successfully register the facial information. The same applies to the deletion of facial information (hereinafter also referred to as "facial deletion"). In this embodiment, "successful registration" and "unregistered" are defined as follows. "Successful registration" means that the facial information has been registered with all of the target facial recognition devices. "Unregistered" refers to a situation where facial information has not been registered with any of the target facial recognition devices.

[0047] Based on the above definitions, the facial recognition registration system 50 according to this embodiment has three main functions. (1) When registering facial information, if the registration of facial information fails at one of the multiple facial recognition devices targeted, the facial information of the facial recognition device that has already successfully registered will be deleted, and the device will be set to a registration failure (unregistered) state. →The user will be asked to try registering their facial information again using their mobile device.

[0048] (2) If the deletion of facial information fails at one of the multiple facial recognition devices targeted, the facial information of the facial recognition device that has already successfully deleted the information will be restored to the state of deletion failed (registered). →The user will be asked to try deleting their facial information from their mobile device again.

[0049] (3) If a specific facial recognition device continuously fails to register or delete faces, it will be determined that there is a malfunction, and a notification will be sent to the user to prevent them from registering or deleting faces (e.g., "Currently unavailable").

[0050] [Computer hardware configuration] Here, the hardware configuration of the control system for the first facial recognition device 21, the second facial recognition device 22, the third facial recognition device 23, and the facial registration server 30, which constitute the facial recognition registration system 50, will be explained with reference to Figure 5.

[0051] Figure 5 is a block diagram showing an example of the hardware configuration of the control systems for each device constituting the facial recognition registration system 50. The computer 500 shown in Figure 5 is an example of hardware used as a computer. In this embodiment, the first facial recognition device 21, the second facial recognition device 22, the third facial recognition device 23, and the facial registration server 30 each work in conjunction with the functional blocks shown in Figures 3 and 4 to realize facial registration and facial recognition when the computer 500 (computer) executes a program.

[0052] Computer 500 includes a CPU (Central Processing Unit) 501, ROM (Read Only Memory) 502, and RAM (Random Access Memory) 503 connected to a system bus. Furthermore, computer 500 includes non-volatile storage 504 and a communication interface 505.

[0053] The CPU 501 reads the program code for the software that implements each function according to this embodiment from the ROM 502, loads it into the RAM 503, and executes it. Variables and parameters that occur during the calculation process of the CPU 501 are temporarily written to the RAM 503, and these variables and parameters are read out by the CPU 501 as appropriate. The functions of each device constituting the facial recognition registration system 50 are realized by the execution of the program code by the CPU 501. However, other processors such as an MPU (Micro Processing Unit) may be used instead of the CPU 501.

[0054] Non-volatile storage 504 is an example of a recording medium that can store data used by a program or data obtained by executing a program. The operating system (OS) or programs executed by the CPU 501 may also be stored on the non-volatile storage 504. Examples of non-volatile storage 504 include HDDs (Hard Disk Drives), SSDs (Solid State Drives), disk media that utilize light or magnetism, or semiconductor memory cards.

[0055] In this embodiment, the facial feature database 215 of the facial recognition device is configured using non-volatile storage 504. Furthermore, the user information database 320, device information database 340, and facial feature database 370 of the facial registration server 30 are also configured using non-volatile storage 504.

[0056] A communication device such as a NIC (Network Interface Card) is used for the communication interface 505. The communication interface 505 is configured to send and receive various types of data with external devices via a communication network such as a LAN or the Internet, or a dedicated line, to which its terminals are connected. In the facial recognition device, communication with the facial registration server 30 is achieved using the communication interface 505. Similarly, in the facial registration server 30, communication with the facial recognition device is achieved using the communication interface 505.

[0057] In the first to third facial recognition devices 21 to 23, the CPU 501 executes a program to realize the functions of each block shown in Figure 3. The facial feature database 215 is realized by the non-volatile storage 504.

[0058] In the face registration server 30, the CPU 501 executes programs to realize the functions of each block shown in Figure 4. Furthermore, the user information database 320, the device information database 340, and the face feature database 370 are implemented by the non-volatile storage 504.

[0059] The mobile terminal 40 and the management PC 80 are also equipped with the same computer 500. However, the mobile terminal 40 and the management PC 80 are connected to input and output devices, which are not shown. The mobile terminal 40 is also equipped with a camera, which is not shown. The user takes a picture of their face with the camera on the mobile terminal 40 and sends the face image to the face registration server 30 to apply for face registration.

[0060] [Face registration process (if successful)] Next, the facial registration process (successful) by the facial recognition registration system 50 will be explained with reference to Figure 6. Figure 6 is a sequence chart showing an example of a face registration process (normal) by the face recognition registration system 50. The example shown in Figure 6 is an example in which the face registration server 30 registers (synchronizes) face information with the first face recognition device 21 and the second face recognition device 22. The target face recognition devices are not limited to two, but may be three or more.

[0061] First, the user operates the mobile terminal 40 to access the face registration server 30, and the face registration screen processing unit 310 of the face registration server 30 sends the face registration screen to the mobile terminal 40. The user applies to register their face information using the face registration screen displayed on the display 41 of the mobile terminal 40. For example, on the face registration screen, the user takes a picture of their face with the camera of the mobile terminal 40 and sends the captured face photo to the face registration server 30 along with user information as face ID "XXX" (S1).

[0062] At the stage when a user applies to register their facial information, their facial information is not yet registered with the facial registration server 30, so the facial registration screen on the mobile device 40 displays "Not Registered." A facial ID (IDentification) is information that uniquely identifies facial information (facial image and facial features extracted from the facial image). For example, when a user registers their face using the facial registration screen, the facial registration server 30 assigns a facial ID.

[0063] Next, the face registration unit 350 of the face registration server 30 receives a face registration request from the mobile terminal 40 and registers the face information. Specifically, the face registration unit 350 extracts feature quantities (hereinafter also referred to as "face feature quantities") from the received face photograph and sends the face feature quantity synchronization management unit 360 (S2).

[0064] Then, the face feature synchronization management unit 360 of the face registration server 30 saves the face features to the face feature database 370, creates a synchronization target list that manages the synchronization targets and synchronization status, and temporarily saves it to RAM 503 (S3). At this stage, the registration of face information is not yet complete, so "Registering" is displayed on the face registration screen of the mobile terminal 40.

[0065] Figure 7 shows an example of a synchronization target list created by the face feature synchronization management unit 360. Here, an example of the synchronization target list 700 created during face registration processing (in the case of normal operation) is shown. The synchronization target list 700 has the following fields: "Face ID", "Device ID", and "Synchronization Status".

[0066] As described above, the "Face ID" field stores identification information for uniquely identifying face information (face image and face features extracted from the face image). In the example in Figure 7, the "Face ID" field stores the face ID "XXX" sent from the mobile terminal 40 in step S1.

[0067] The "Device ID" field stores identification information to uniquely identify the authentication device installed in the facility the user enters and exits. An example is shown where the device IDs stored are "1" for the first facial recognition device 21 and "2" for the second facial recognition device 22. For example, among the multiple facial recognition devices connected to the facial registration server 30, the device ID of the facial recognition device installed in the facility that the user has applied to use is registered in the synchronization target list. The facility that the user has applied to use can be confirmed using the information managed in the device information database 340.

[0068] The "Synchronization Status" field stores information indicating the synchronization status of facial information in the facial recognition device. Immediately after step S3, the synchronization status for both device IDs "1" and "2" is "Waiting for registration".

[0069] Returning to Figure 6, we continue the explanation. After step S3, the face feature synchronization client 214 of the first face recognition device 21 performs synchronization acquisition with the face registration server 30 (S4). That is, the face feature synchronization client 214 periodically polls the face registration server 30 to check whether the face feature database 370 has been updated.

[0070] Next, the face feature synchronization management unit 360 of the face registration server 30 responds to the synchronization acquisition command from the first face recognition device 21 (S5). If the face feature of face ID "XXX" has been newly registered in the face feature database 370, the face feature synchronization management unit 360 sends the face feature of face ID "XXX" and a registration instruction to the first face recognition device 21.

[0071] Next, the face feature synchronization client 214 of the first face recognition device 21 stores the face features of face ID "XXX" sent from the face registration server 30 in the face feature database 215. Then, the face feature synchronization client 214 sends a reply to the face registration server 30 indicating that the synchronization of the face features of face ID "XXX" is complete (S6).

[0072] Next, the face feature synchronization management unit 360 of the face registration server 30 updates the synchronization target list 700 (S7). Here, the face feature synchronization management unit 360 changes the synchronization status of device ID "1" in the synchronization target list 700 from "waiting for registration" to "registered".

[0073] Next, after updating the synchronization target list 700, the face feature quantity synchronization management unit 360 of the face registration server 30 returns a response to the first face recognition device 21 indicating that the synchronization is complete (S8).

[0074] Similarly, the face feature synchronization client 214 of the second face recognition device 22 performs synchronization acquisition with the face registration server 30 (S9). Then, the face feature synchronization management unit 360 of the face registration server 30 sends the face features of face ID "XXX" to the second face recognition device 22 as a response to the synchronization acquisition command from the second face recognition device 22 (S10).

[0075] Next, the face feature synchronization client 214 of the second face recognition device 22 saves the face features of face ID "XXX" sent from the face registration server 30 to the face feature database 215 and sends a reply to the face registration server 30 indicating that the synchronization of the face features of face ID "XXX" is complete (S11).

[0076] Next, the face feature synchronization management unit 360 of the face registration server 30 updates the synchronization target list 700 (S12). Here, the face feature synchronization management unit 360 changes the synchronization status of device ID "2" in the synchronization target list 700 from "waiting for registration" to "registered".

[0077] Next, after updating the synchronization target list 700, the face feature synchronization management unit 360 returns a response to the second face recognition device 22 indicating that the synchronization is complete (S13).

[0078] Next, since the synchronization of face registration to the first face recognition device 21 and the second face recognition device 22 is complete, the face feature synchronization management unit 360 deletes the information of the synchronization target (face ID, device ID) from the synchronization target list 700 (S14).

[0079] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the mobile terminal 40 of the result of the user's face registration application, that is, that face registration has been successfully completed (S15). Since the registration of the user's face information has been successfully completed, "Registered" is displayed on the face registration screen of the mobile terminal 40.

[0080] As shown in Figure 6, if the face registration process is performed successfully, the face registration server 30 creates a synchronization target list when a face registration is requested, and removes the target from the synchronization target list when the synchronization of the target face authentication device is complete.

[0081] Alternatively, the face feature synchronization management unit 360 of the face registration server 30 may create a synchronization target list 700 (step S3) and then send the face features of face ID "XXX" to the first face authentication device 21, thereby omitting the synchronization acquisition process in step S4. Step S9 may also be omitted in the same manner.

[0082] [Face registration process (if it fails)] Next, the face registration process (failure) by the face recognition registration system 50 will be explained with reference to Figure 8. Figure 8 is a sequence chart showing an example of a face registration process (failure) by the face recognition registration system 50. The example shown in Figure 8 is one in which face registration is successful with the first face recognition device 21, but fails with the second face recognition device 22. In Figure 8, steps S1 to S10 are the same as in the example in Figure 6.

[0083] After successful face registration by the first face recognition device 21, the processes in steps S9 and S10 are performed between the second face recognition device 22 and the face registration server 30.

[0084] After the processing in step S10, the face feature synchronization client 214 of the second face recognition device 22 executes the process of saving the face features of face ID "XXX" sent from the face registration server 30 to the face feature database 215. However, if the registration of the face features of face ID "XXX" is not completed successfully in the second face recognition device 22 for any reason, the face feature synchronization client 214 cannot send a synchronization completion message to the face registration server 30 (S11a).

[0085] The face feature synchronization management unit 360 of the face registration server 30 performs a timeout process if it does not receive a synchronization completion response from the second face recognition device 22 after a predetermined period of time has elapsed. Then, the face feature synchronization management unit 360 updates the synchronization target list (S12a).

[0086] Figure 9 shows an example of the synchronization target list 900 created by the face feature synchronization management unit 360 during the face registration process (in the event of failure). Here, the face feature synchronization management unit 360 changes the synchronization status of device ID "2" in the synchronization target list 900 from "waiting for registration" to "registration failed".

[0087] Next, the face feature synchronization management unit 360 of the face registration server 30 requests the first face authentication device 21 to delete the face information (face features) of face ID "XXX" that has already been successfully registered (S21). The face feature synchronization client 214 of the first face authentication device 21 receives the request to delete the face information of face ID "XXX", deletes the face features of face ID "XXX" stored in the face feature database 215, and sends a deletion response back to the face registration server 30 (S22).

[0088] Similarly, the face feature synchronization management unit 360 of the face registration server 30 requests the second face authentication device 22 to delete the face information (face features) for face ID "XXX" (S23). The face feature synchronization client 214 of the second face authentication device 22 receives the request to delete the face information for face ID "XXX", deletes the face features for face ID "XXX" stored in the face feature database 215, and sends a deletion response back to the face registration server 30 (S24). The requests from the face registration server 30 to delete face information from the first face authentication device 21 and the second face authentication device 22 may be processed in parallel or in any order.

[0089] The facial feature synchronization management unit 360, during the facial registration process, deletes the facial information of any facial recognition device that has already successfully registered a face if one of the target facial recognition devices fails to register a face, thereby setting the device to a registration failure (unregistered) state.

[0090] Furthermore, the face registration server 30 cannot distinguish whether the face recognition device failed to receive the synchronization acquisition response and therefore the target face features were not registered, or whether the synchronization acquisition response was successfully received and the face features were registered, but the transmission of the synchronization completion failed. For this reason, the face registration server 30 also sends a deletion request to the second face recognition device 22, which was the cause of the registration failure.

[0091] Thus, when a face information synchronization event is a face information registration process, the face feature synchronization management unit 360 of the face registration server 30 requests the multiple face recognition devices to delete the face information if one of the target face recognition devices fails to register the face information. The face feature synchronization management unit 360 then controls the multiple face recognition devices to delete the face information so that the face information remains unregistered in all of them.

[0092] This allows the synchronization status of facial information across multiple target facial recognition devices to be standardized to "registration failed (not registered)".

[0093] Next, the face feature synchronization management unit 360 of the face registration server 30 receives a deletion response from the first face recognition device 21 and changes the synchronization status of device ID "1" in the synchronization target list 900 from "registered" to "deleted". Similarly, the face feature synchronization management unit 360 receives a deletion response from the second face recognition device 22 and changes the synchronization status of device ID "2" in the synchronization target list 900 from "registration failed" to "deleted".

[0094] Next, since the synchronization (deletion) of face information between the first face recognition device 21 and the second face recognition device 22 is complete, the face feature synchronization management unit 360 deletes the information of the synchronization targets (face ID, device ID) from the synchronization target list 900 (S25).

[0095] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the mobile terminal 40 that the user's face registration application has failed (S26). Since the user's face registration has failed, "Not Registered" is displayed on the face registration screen of the mobile terminal 40.

[0096] Here, the face registration screen processing unit 310 of the face registration server 30 may, if the registration of face information fails at one of the multiple face recognition devices, display a message prompting the user to re-register on the mobile terminal 40 used to register the face information.

[0097] Furthermore, the face registration screen processing unit 310 of the face registration server 30 may determine that there is a problem if any particular face recognition device continuously fails to register face information, and may send a notification to the mobile terminal 40 to prevent the user from registering face information. For example, the face registration screen processing unit 310 may determine that there is a problem (or malfunction) if face registration fails three times in a row. By notifying the user that face information cannot be registered in this way, the face registration server 30 can avoid unnecessary face registration processing and reduce the processing load on the registration server 30.

[0098] In the processing examples shown in Figures 8 and 9 above, if synchronization (face registration) fails in any of the facial recognition devices, a process is executed to synchronize the synchronization status across multiple target facial recognition devices. This prevents different events from occurring in this embodiment, such as being able to unlock access control equipment (e.g., doors) associated with facial recognition devices that have successfully registered faces, but being unable to unlock access control equipment (e.g., doors) associated with facial recognition devices that have failed to register faces.

[0099] [Face removal process (normal)] Next, the face deletion process (successful) by the face recognition registration system 50 will be explained with reference to Figure 10. Figure 10 is a sequence chart showing an example of a face deletion process (normal) by the face recognition registration system 50. The example shown in Figure 10 is an example in which the face registration server 30 deletes (synchronizes) face information from the first face recognition device 21 and the second face recognition device 22.

[0100] First, the user operates the mobile terminal 40 to access the face registration server 30, and the face registration screen processing unit 310 of the face registration server 30 sends the face registration screen to the mobile terminal 40. The user requests the deletion of their face information using the face registration screen displayed on the display 41 of the mobile terminal 40 (S31). For example, if user information has been entered and face information has been registered on the face registration screen, the face information (face image) of the registered face ID "XXX" will be displayed. If the face image is correct, the user presses a confirmation button (not shown) and proceeds with the request to delete the face. Normally, one user registers only one piece of face information. However, multiple pieces of face information may be registered for one user.

[0101] At the stage when a request is made to delete facial information, the user's facial information is registered with the facial registration server 30, so the facial registration screen on the mobile device 40 displays "Registered".

[0102] Next, the face feature synchronization management unit 360 of the face registration server 30 receives a request to delete a face from the mobile terminal 40, creates a list of items to be synchronized, and temporarily saves it in RAM 503 (S32). At this stage, the deletion of face information is not yet complete, so "Deleting" is displayed on the face registration screen of the mobile terminal 40.

[0103] Figure 11 shows an example of a synchronization target list created by the face feature synchronization management unit 360. Here, an example of the synchronization target list 1100 created during face deletion processing (in the case of normal operation) is shown. The synchronization target list 1100 has the fields "Face ID", "Device ID", and "Synchronization Status", similar to the face registration process.

[0104] In Figure 11, the "Face ID" field stores the face ID "XXX" transmitted from the mobile terminal 40 in step S31. The "Device ID" field stores the device ID "1" of the first face recognition device 21 and the device ID "2" of the second face recognition device 22. The "Synchronization Status" field shows "Waiting for Deletion" for both device IDs "1" and "2".

[0105] Returning to Figure 11, we continue the explanation. After step S32, the face feature synchronization client 214 of the first face recognition device 21 performs synchronization acquisition with the face registration server 30 (S33). That is, as with face registration, the face feature synchronization client 214 periodically polls the face registration server 30 to check whether the face feature database 370 has been updated. Note that this step S33 (and step S38 described later) may be omitted in the same manner as step S4 in Figure 6.

[0106] Next, the face feature synchronization management unit 360 of the face registration server 30 responds to the synchronization acquisition command from the first face authentication device 21 (S34). If the face feature of face ID "XXX" has been deleted from the face feature database 370, the face feature synchronization management unit 360 sends an instruction to the first face authentication device 21 to delete the face feature of face ID "XXX".

[0107] Next, the face feature synchronization client 214 of the first face recognition device 21 deletes the face feature of face ID "XXX" from the face feature database 215 in accordance with the instruction to delete the face feature of face ID "XXX" sent from the face registration server 30. Then, the face feature synchronization client 214 replies to the face registration server 30 that the synchronization of the face feature of face ID "XXX" is complete (S35).

[0108] Next, the face feature synchronization management unit 360 of the face registration server 30 updates the synchronization target list 1100 (S36). Here, the face feature synchronization management unit 360 changes the synchronization status of device ID "1" in the synchronization target list 1100 from "waiting for deletion" to "deleted".

[0109] Next, after updating the synchronization target list 1100, the face feature quantity synchronization management unit 360 of the face registration server 30 returns a response to the first face recognition device 21 indicating that the synchronization is complete (S37).

[0110] Similarly, the face feature synchronization client 214 of the second face recognition device 22 performs synchronization acquisition with the face registration server 30 (S38). Then, the face feature synchronization management unit 360 of the face registration server 30 sends an instruction to delete the face feature of face ID "XXX" to the second face recognition device 22 in response to the synchronization acquisition command from the second face recognition device 22 (S39).

[0111] Next, the face feature synchronization client 214 of the second face recognition device 22 deletes the face feature of face ID "XXX" from the face feature database 215 in accordance with the instruction to delete the face feature of face ID "XXX" sent from the face registration server 30, and sends a reply to the face registration server 30 indicating that the synchronization of the face feature of face ID "XXX" is complete (S40).

[0112] Next, the face feature synchronization management unit 360 of the face registration server 30 updates the synchronization target list 1100 (S41). Here, the face feature synchronization management unit 360 changes the synchronization status of device ID "2" in the synchronization target list 1100 from "waiting for deletion" to "deleted".

[0113] Next, after updating the synchronization target list 1100, the facial feature synchronization management unit 360 returns a response to the second facial recognition device 22 indicating that the synchronization is complete (S42).

[0114] Next, since the synchronization of face deletion between the first face recognition device 21 and the second face recognition device 22 is complete, the face feature synchronization management unit 360 deletes the information of the synchronization target (face ID, device ID) from the synchronization target list 1100 (S43).

[0115] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the mobile terminal 40 of the result of the user's face deletion request, i.e., that the face deletion has been successfully completed (S44). Since the deletion of the user's face information has been successfully completed, "Not Registered" is displayed on the face registration screen of the mobile terminal 40.

[0116] As shown in Figure 10, if the face deletion process is performed successfully, the face registration server 30 creates a synchronization target list when a face deletion request is made, and removes the target from the synchronization target list when the synchronization of the target face authentication device is completed.

[0117] [Face removal process (if it fails)] Next, the face deletion process (failure) by the face recognition registration system 50 will be explained with reference to Figure 12. Figure 12 is a sequence chart showing an example of a face deletion process (failure) by the face recognition registration system 50. The example shown in Figure 12 is one in which face deletion is successful by the first face recognition device 21, but fails by the second face recognition device 22. In Figure 12, steps S31 to S39 are the same as in the example in Figure 10.

[0118] After the first facial recognition device 21 successfully deletes a face, steps S38 and S39 are performed between the second facial recognition device 22 and the face registration server 30.

[0119] After the processing in step S39, the face feature synchronization client 214 of the second face recognition device 22 executes the process of deleting the face feature of face ID "XXX" from the face feature database 215 in accordance with the instruction to delete the face feature of face ID "XXX" sent from the face registration server 30. However, if the deletion of the face feature of face ID "XXX" is not successfully completed in the second face recognition device 22 for any reason, the face feature synchronization client 214 cannot send a synchronization completion message to the face registration server 30 (S40a).

[0120] The face feature synchronization management unit 360 of the face registration server 30 performs a timeout process if it does not receive a synchronization completion response from the second face recognition device 22 after a predetermined period of time has elapsed. Then, the face feature synchronization management unit 360 updates the synchronization target list (S41a).

[0121] Figure 13 shows an example of the synchronization target list 1300 created by the face feature synchronization management unit 360 during the face registration process (in the event of failure). Here, the face feature synchronization management unit 360 changes the synchronization status of device ID "2" in the synchronization target list 1300 from "waiting for deletion" to "deletion failed".

[0122] Next, the face feature synchronization management unit 360 of the face registration server 30 requests the first face recognition device 21 to register the face information (face features) of face ID "XXX" that has already been successfully deleted (S51). The face feature synchronization client 214 of the first face recognition device 21 receives the registration request for face information of face ID "XXX", registers (restores) the face features of face ID "XXX" in the face feature database 215, and sends a registration response back to the face registration server 30 (S52).

[0123] Similarly, the face feature synchronization management unit 360 of the face registration server 30 requests the second face recognition device 22 to register face information (face features) for face ID "XXX" (S53). The face feature synchronization client 214 of the second face recognition device 22 receives the registration request for face information for face ID "XXX", registers the face features for face ID "XXX" in the face feature database 215, and sends a registration response back to the face registration server 30 (S54). The face registration server 30's requests for face information registration to the first face recognition device 21 and the second face recognition device 22 may be processed in parallel or in any order.

[0124] The facial feature synchronization management unit 360, during the face deletion process, restores the face information of a facial recognition device that has already successfully deleted a face if the deletion fails at any of the target facial recognition devices, and sets the deletion to a failed (registered) state. For example, the face information that the first facial recognition device 21 has deleted from the facial feature database 215 is temporarily stored in the RAM 503. Alternatively, the data from the facial feature database 215 may be read into the RAM 503, and after the success or failure of the synchronization (in this case, deletion) is determined, the data may be written back to the facial feature database 215.

[0125] Furthermore, the face registration server 30 cannot distinguish whether the face recognition device failed to receive the synchronization acquisition response and therefore the target face features were not deleted, or whether the synchronization acquisition response was successfully received and the face features were deleted, but the transmission of the synchronization completion failed. For this reason, the face registration server 30 also sends a registration request to the second face recognition device 22, which was the cause of the deletion failure.

[0126] Thus, when a face information synchronization event is a face information deletion process, the face feature synchronization management unit 360 of the face registration server 30 requests the multiple face recognition devices to register (restore) the face information if the deletion of face information fails at one of the multiple target face recognition devices. The face feature synchronization management unit 360 then controls the multiple face recognition devices to register (restore) the face information so that the face information is registered at all of the multiple face recognition devices.

[0127] This allows the synchronization status of facial information across multiple target facial recognition devices to be standardized to "deletion failed (registered)".

[0128] Next, the face feature synchronization management unit 360 of the face registration server 30 receives a registration response from the first face recognition device 21 and changes the synchronization status of device ID "1" in the synchronization target list 1300 from "deleted" to "registered". Similarly, the face feature synchronization management unit 360 receives a registration response from the second face recognition device 22 and changes the synchronization status of device ID "2" in the synchronization target list 1300 from "deletion failed" to "registered".

[0129] Next, since the synchronization (registration) of face information to the first face recognition device 21 and the second face recognition device 22 is complete, the face feature synchronization management unit 360 deletes the information of the synchronization targets (face ID, device ID) from the synchronization target list 1300 (S55).

[0130] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the mobile terminal 40 that the face deletion request from the user has failed (S56). Since the user's face deletion failed, "Deletion Failed" is displayed on the face registration screen of the mobile terminal 40.

[0131] Here, the face registration screen processing unit 310 of the face registration server 30 may, if one of the multiple face recognition devices fails to delete the face information, display a message prompting the user to delete the face information again on the mobile terminal 40 used to delete the face information.

[0132] Furthermore, the face registration screen processing unit 310 of the face registration server 30 may determine that there is a malfunction if any particular face recognition device continuously fails to delete face information, and may send a notification to the mobile terminal 40 to prevent the user from deleting face information. For example, the face registration screen processing unit 310 may determine that there is a malfunction (or failure) if face deletion fails three times in a row. By notifying the user that face information cannot be deleted in this way, the face registration server 30 can avoid unnecessary face deletion processing and reduce the processing load on the registration server 30.

[0133] In the processing examples shown in Figures 12 and 13 above, if synchronization (face deletion) fails in any facial recognition device, a process is executed to synchronize the synchronization status across multiple target facial recognition devices. This prevents the occurrence of different events in this embodiment, such as access control equipment (e.g., doors) associated with facial recognition devices that successfully deleted faces being unable to be unlocked, while access control equipment (e.g., doors) associated with facial recognition devices that failed to delete faces being able to be unlocked.

[0134] As described above, the face recognition registration system 50 according to this embodiment includes a face registration server that stores face information (at least face features extracted from face images) and a plurality of face recognition devices that register face information and use it for face recognition. When the face registration server receives a face information synchronization event (registration / deletion), it performs face information synchronization processing on the target plurality of face recognition devices, and if synchronization fails on any one of the plurality of face recognition devices, it controls the plurality of face recognition devices to return to the state before the synchronization processing.

[0135] In this embodiment, if facial information synchronization fails in any facial recognition device, a process is executed to synchronize the synchronization status across multiple target facial recognition devices. This prevents discrepancies from occurring, such as being able to authenticate equipment (e.g., doors, elevators) associated with a facial recognition device that successfully synchronized facial information, but not being able to authenticate equipment (e.g., doors, elevators) associated with a facial recognition device that failed to synchronize facial information. Therefore, this embodiment prevents users from experiencing inconvenience or confusion.

[0136] It should be noted that the present invention is not limited to the embodiments described above, and various other applications and modifications are possible as long as they do not depart from the gist of the invention as described in the claims. For example, the embodiments described above are described in detail and specifically in order to explain the configuration of the present invention in an easy-to-understand manner, and are not necessarily limited to those comprising all the components described. Furthermore, it is possible to add, replace, or delete other components in some of the configurations of the embodiments described above.

[0137] Furthermore, some or all of the above configurations, functions, and processing units may be implemented in hardware, for example, by designing them as integrated circuits. Broadly defined processor devices such as FPGAs (Field Programmable Gate Arrays) and ASICs (Application Specific Integrated Circuits) may be used as hardware. In addition, a cloud environment can be utilized for storing facial features, user information, device information, etc.

[0138] Furthermore, each component (functional block) of each device constituting the facial recognition registration system according to the above embodiment may be implemented on any hardware, as long as the respective hardware can send and receive information from each other via a network. Also, the processing performed by a certain processing unit may be realized by a single piece of hardware, or by distributed processing by multiple pieces of hardware.

[0139] Furthermore, in the embodiments described above, the control lines and information lines shown are those deemed necessary for explanatory purposes, and not all control lines and information lines are necessarily shown in the actual product. In practice, it can be assumed that almost all components are interconnected. [Explanation of Symbols]

[0140] 21…First facial recognition device, 22…Second facial recognition device, 23…Third facial recognition device, 30…Face registration server, 40…Mobile terminal, 50…Face recognition registration system, 60…Access control system, 70…Elevator control panel, 211…Camera image acquisition unit, 212…Face recognition unit, 213…Device linkage unit, 214…Face feature synchronization client, 215…Face feature database, 310…Face registration screen processing unit, 320…User information database, 330…Management information registration screen processing unit, 340…Device information database, 350…Face registration unit, 360…Face feature synchronization management unit, 370…Face feature database, 700…Synchronization target list, 900…Synchronization target list, 1100…Synchronization target list, 1300…Synchronization target list

Claims

1. A facial recognition registration system comprising a facial registration server for storing facial information, and a plurality of facial recognition devices for registering the facial information and using it for facial recognition, When the face registration server receives a face information registration process as a face information synchronization event, it performs the face information registration process on the target multiple face recognition devices. If the registration of the face information fails on any one of the multiple face recognition devices, it requests the multiple face recognition devices to delete the face information, thereby controlling the multiple face recognition devices so that the face information remains unregistered. Facial recognition registration system.

2. If the face registration server fails to register the face information with any of the multiple face recognition devices, it will display a message prompting the user to re-register on the terminal used to register the face information. The facial recognition registration system according to claim 1.

3. If the facial recognition device repeatedly fails to register the facial information, the facial registration server will notify the terminal to prevent further registration of the facial information. The facial recognition registration system according to claim 2.

4. If the facial information synchronization event is the facial information deletion process, the facial registration server will: If one of the target facial recognition devices fails to delete the facial information, the system will request the registration of the facial information from all of the facial recognition devices and control them so that the facial information is registered in all of them. The facial recognition registration system according to claim 1.

5. If one of the multiple facial recognition devices fails to delete the facial information, the facial registration server will display a message prompting the user to delete the facial information again on the terminal used to delete the facial information. The facial recognition registration system according to claim 4.

6. If the facial recognition device repeatedly fails to delete the facial information, the facial registration server will notify the terminal to prevent the deletion of the facial information. The facial recognition registration system according to claim 5.

7. Multiple facial recognition devices used in a facial recognition registration system that performs facial recognition using facial information stored in a facial registration server, Multiple facial recognition devices perform the registration process of the facial information stored in the facial registration server. If any one of the multiple facial recognition devices fails to register the facial information, the multiple facial recognition devices delete the facial information in accordance with a command sent from the facial registration server, and the facial information is left unregistered in all of the multiple facial recognition devices. Facial recognition device.

8. A facial recognition registration method using a facial recognition registration system comprising a facial registration server for storing facial information and a plurality of facial recognition devices for registering the facial information and using it for facial recognition, When the face registration server receives the face information registration process as a face information synchronization event, it performs the face information registration process for the target multiple face authentication devices. If one of the multiple facial recognition devices fails to register the facial information, the facial registration server requests the multiple facial recognition devices to delete the facial information, thereby controlling the multiple facial recognition devices to remain unregistered. How to register using facial recognition.

Images