Face authentication and registration system, face authentication device, and face authentication and registration method

Abstract

The invention relates to a face authentication registration system, a face authentication apparatus, and a face authentication registration method. When face authentication is performed by accumulating face information of a user using a plurality of face authentication devices installed on a facility side, the occurrence of a different phenomenon that authentication can be performed in a certain device but cannot be performed in another device is prevented. A face authentication registration system (50) is provided with: a face registration server (30) that stores face information; and a plurality of face authentication devices (21-23) that register face information and use the face information in face authentication. When receiving a synchronization event of face information, the face registration server (30) performs a synchronization process of the face information on a plurality of face authentication devices (21-23) as a subject, and when one of the plurality of face authentication devices (21-23) fails to synchronize, the face registration server (30) performs a synchronization process of the face information on the plurality of face authentication devices (21-23). The face registration server (30) controls the plurality of face authentication devices (21-23) to return to a state before the synchronization process.

Description

Technical Field

[0001] The 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 has been developed that performs face authentication processing based on image data obtained by capturing a subject.

[0003] For example, Patent Document 1 discloses the following technology: In a facial authentication system, the processing required for facial authentication is divided, thereby significantly reducing the processing load and device cost on the facial authentication machine side. The facial authentication system described in Patent Document 1 has a plurality of facial authentication machines and a server device connected to the facial authentication machines via a network. The server device has a plurality of facial comparison units for performing facial comparison. Each facial comparison unit has a facial comparison process for executing a facial comparison program on facial image data of a user received from the facial authentication machine, and a facial comparison database for registering user information (facial feature quantity data) as a comparison object for facial comparison.

[0004] In addition, paragraph

[0273] of Patent Document 1 states that “a user whose facial registration failed is reported to the administrator, and the user is reminded to re-register.” In addition, paragraph

[0288] states that “in the case of facial registration failure, a facial feature value deletion request is not made, and facial comparison is performed while the old facial feature value is maintained.”

[0005] Prior art literature

[0006] Patent Document 1: Japanese Patent Application Publication No. 2020-126335 Summary of the invention

[0007] Problems to be solved by the invention

[0008] However, in a configuration where a plurality of facial authentication machines and a server device having a facial matching process and a facial matching database are connected via a network as in the technology described in Patent Document 1, if a communication failure occurs, the facial authentication machine cannot obtain the authentication result of the user.

[0009] In order to solve the above-mentioned disadvantages, the following structure is conceivable: a facial authentication device installed at a facility used by a user accumulates the user's facial information (for example, facial feature data), and the facial authentication device compares the user's facial image data with the facial information.

[0010] However, when the facial information of the subject is stored in a plurality of facial authentication machines, when registering new facial information to a facial authentication machine, if the registration to a specific facial authentication machine fails, the following problem occurs. This problem is that if the registration failure to a specific facial authentication machine is ignored, for example, the following different phenomena occur: the access device associated with the facial authentication machine that has successfully registered can be authenticated (unlocked), but the access device associated with the facial authentication machine that has failed to register cannot be authenticated (unlocked).

[0011] In addition, Patent Document 1 records that a user who has failed to register his / her face is prompted to register again, but sometimes even if the user registers again, the registration fails. In addition, in the technology described in Patent Document 1, when the face registration fails, the old face feature value is used for face comparison.

[0012] In view of the above situation, it is desirable to prevent the occurrence of different phenomena in which authentication is possible in one device but not in another device when accumulating user facial information and performing facial authentication using a plurality of facial authentication devices installed at a facility.

[0013] Means for solving problems

[0014] In order to solve the above-mentioned problems, a facial authentication registration system of one embodiment of the present invention comprises: a facial registration server that stores facial information; and a plurality of facial authentication devices that register facial information and use it for facial authentication. When the facial registration server receives a facial information synchronization event, it performs facial information synchronization processing on the plurality of facial authentication devices as objects, and when the synchronization of one of the plurality of facial authentication devices fails, the facial registration server controls the plurality of facial authentication devices to return to the state before the synchronization processing.

[0015] Effects of the Invention

[0016] According to at least one aspect of the present invention, when multiple facial authentication devices installed at a facility accumulate user facial information for facial authentication, it is possible to prevent the occurrence of different phenomena in which authentication is possible in one device but not in another.

[0017] Other problems, structures, and effects than those described above will become clear from the following description of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is a diagram showing an example of a scene using the face recognition registration system according to one embodiment of the present invention.

[0019] Figure 2This is a diagram showing an overall configuration example of a face recognition and registration system and an overview of face registration according to an embodiment of the present invention.

[0020] Figure 3 This is a diagram showing an example of the functional configuration of a face authentication device according to one embodiment of the present invention.

[0021] Figure 4 This is a diagram showing an example of the functional configuration of a face registration server according to one embodiment of the present invention.

[0022] Figure 5 This is a block diagram showing a hardware configuration example of a computer included in each device constituting the facial recognition registration system according to one embodiment of the present invention.

[0023] Figure 6 This is a sequence diagram showing an example of face registration processing (normal) of the face recognition registration system according to one embodiment of the present invention.

[0024] Figure 7 This is a diagram showing an example of a synchronization target list created during face registration processing (normally) in the face recognition registration system according to one embodiment of the present invention.

[0025] Figure 8 This is a sequence diagram showing an example of face registration processing (failure) of the face recognition registration system according to one embodiment of the present invention.

[0026] Fig. 9 This is a diagram showing an example of a synchronization target list created during (failed) face registration processing in the face recognition registration system according to one embodiment of the present invention.

[0027] Fig.10 This is a sequence diagram showing an example of face deletion processing (normal) in the face recognition registration system according to one embodiment of the present invention.

[0028] Fig.11 This is a diagram showing an example of a synchronization target list created during face deletion processing (normally) in the face authentication registration system according to one embodiment of the present invention.

[0029] Fig.12 This is a sequence diagram showing an example of face deletion processing (failure) in the face recognition registration system according to one embodiment of the present invention.

[0030] Fig.13 This is a diagram showing an example of a synchronization target list created at the time of face deletion processing (failure) in the face authentication registration system according to one embodiment of the present invention. DETAILED DESCRIPTION

[0031] Hereinafter, examples of modes for implementing the present invention (hereinafter referred to as "embodiments") will be described with reference to the drawings. In this specification and the drawings, the same components or components having substantially the same functions are denoted by the same reference numerals and repeated descriptions are omitted.

[0032] <One embodiment>

[0033] [Scenario using facial recognition registration system]

[0034] First, refer to Figure 1 An example of use of the face recognition registration system according to one embodiment of the present invention will be described.

[0035] Figure 1 FIG. 1 is a diagram showing an example of a scene using a facial recognition registration system according to an embodiment of the present invention. Figure 2 The structure of the facial recognition registration system will be described in detail later.

[0036] As an example of how the facial recognition registration system is used, it is conceivable to provide residents of a multi-family housing complex (also called "apartment" in Japan) with an entry and exit service based on facial recognition. Figure 2 As shown, the facial recognition registration system of this embodiment is capable of receiving data from the cloud (described later). Figure 2 A system that registers faces of face authentication devices having face authentication functions based on AI (Artificial Intelligence) or the like.

[0037] A resident U of a residential complex registers his or her face in a facial recognition registration system using a portable terminal, etc., and receives various entry and exit services. For example, sometimes two doors are provided at the entrance of a residential complex. The first door 1 is an automatic door, and even people other than the resident U can enter and exit. The second door 2 after passing through the first door 1 is an automatic locking type, and needs to be unlocked using an unlocking unit (key, password, facial image), or must be unlocked by the resident U.

[0038] If the facial registration is completed, the resident U can unlock the second door 2 by authenticating the facial image captured by the surveillance camera 4. In addition, the resident U can realize the car call of the elevator 3 and the automatic registration of the destination floor by authenticating the facial image captured by the surveillance camera 5 of the elevator hall. By pre-registration, the face of the resident U is associated with the destination floor. Such a facial authentication registration system can also be applied to entry and exit services of office buildings, factories, etc.

[0039] [Overall structure of the facial authentication registration system and outline of facial registration]

[0040] Next, refer to Figure 2The overall configuration of the face recognition and registration system and the outline of face registration according to the present embodiment will be described.

[0041] Figure 2 It is a diagram showing an overall configuration example of the face recognition and registration system according to the present embodiment and an overview of face registration.

[0042] exist Figure 2 In the example, the facial recognition registration system 50 includes: 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. In addition, the number of facial recognition devices is not limited to 3, and may be 2 or 4 or more. In addition, the number of cameras connected to one facial recognition device may be 3 or more.

[0043] The user operates the touch sensor installed on the display 41 of the portable terminal 40 and selects a menu for synchronizing facial information from the menu screen. The user uses the camera of the portable terminal 40 to take a picture of the face of the person to be registered (the user himself or herself, a family member, etc.), and sends the facial picture (facial image data) to the facial registration server 30 to apply for facial registration.

[0044] In addition, in the application for facial registration, in addition to the portable terminal 40, various terminals such as information processing devices such as desktop PCs (Personal Computers) integrated with monitors with cameras, cameras with communication functions, etc. can also be used. In addition, facial registration can also be applied for using facial photos taken in advance and stored in terminals, etc. In addition, the subject who can apply for facial registration is a person who has been allowed to enter and exit the facility in advance by the manager or person in charge of the target facility.

[0045] The face registration server 30 receives the application for face registration from the portable terminal 40. The face registration server 30 extracts the feature quantity of the face image received from the portable terminal 40 when applying for face registration, and stores it in the database (main server) as the face feature quantity data of the synchronization object. In addition, the face registration server 30 sends the face feature quantity data to the first face authentication device 21, the second face authentication device 22, and the third face authentication device 23 connected to the server, so as to synchronize the face feature quantity data. Hereinafter, the face feature quantity data is referred to as "face feature quantity".

[0046] When the facial feature value synchronization is successful, the first facial authentication device 21, the second facial authentication device 22, and the third facial authentication device 23 store the facial feature values ​​as synchronized in their respective databases (slave).

[0047] In the facial recognition registration system 50 of this embodiment, it is sufficient to synchronize the facial feature amount of the user with the facial recognition device installed in the facility used by the user (complex housing, office building, factory, etc.). For example, when the first facial recognition device 21 and the second facial recognition device 22 are installed in the complex housing where the user lives, the facial registration server 30 synchronizes the facial feature amount of the first facial recognition device 21 and the second facial recognition device 22 based on the user information.

[0048] Hereinafter, the process (1) to (5) from facial registration to facility entry and exit using the facial recognition registration system 50 will be described by taking entry and exit of a residential complex as an example.

[0049] (1) A resident U of the apartment building takes a picture of his face using the camera of the mobile terminal 40 and transmits the picture of his face (face image) to the face registration server 30 .

[0050] (2) The face registration server 30 stores the facial feature quantity extracted from the facial photograph in the database of the face registration server 30 .

[0051] (3) The facial feature amount is synchronized with a plurality of facial authentication devices (the first facial authentication device 21 to the third facial authentication device 23) installed in the apartment building.

[0052] (4) A plurality of face authentication devices perform face authentication by matching the face image Im acquired from the monitoring camera with the face feature quantity synchronized from the face registration server 30. The camera used for face authentication may be provided integrally with the face authentication device.

[0053] (5) Face Authentication Device If the face of the resident U is authenticated, control is performed to execute unlocking of the entrance door and car calling of the elevator 3 .

[0054] In the past, facial feature quantities were synchronized with multiple facial authentication devices. However, if the synchronization of only a specific facial authentication device fails, a certain door can be unlocked by facial authentication, but a certain door cannot be unlocked by facial authentication. For example, the first camera 11 is Figure 1 The second camera 12 is the surveillance camera 4, the second camera 12 is the surveillance camera 5, the facial feature quantity of the resident U is registered in the first facial recognition device 21, but the facial feature quantity of the resident U is not registered in the second facial recognition device 22. In this case, the resident U can pass through the second door 2 of the entrance, but cannot make a car call in the elevator hall where the surveillance camera 5 is installed.

[0055] Such a difference is very inconvenient and causes confusion for the resident U. Therefore, the facial feature values ​​need to be synchronized in all the multiple facial authentication devices installed in the facilities used by the resident U. The following method is described: In the facial authentication registration system 50 of the present embodiment, the facial feature values ​​are synchronized in all the facial authentication devices in the facilities used by the user.

[0056] [Function of facial authentication device]

[0057] Figure 3 1 is a diagram showing an example of the functional configuration of the face authentication device according to the present embodiment. The functional configuration of the face authentication device is described by taking the first face authentication device 21 as an example, but the second face authentication device 22 and the third face authentication device 23 are also the same.

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

[0059] The camera image acquisition unit 211 acquires data in the form of a data stream from a surveillance camera installed at an entrance, an elevator hall, etc., and performs decoding from a dynamic image to a static image (sometimes simply referred to as an “image”).

[0060] The facial authentication unit 212 performs facial detection based on the image acquired by the camera image acquisition unit 211. Then, the facial authentication unit 212 extracts feature quantities from the detected facial region, and compares the extracted feature quantities with the facial feature quantities stored in the facial feature quantity database 215. For example, when the comparison rate of the feature quantities is higher than a preset reference, the facial authentication unit 212 determines that the facial feature quantities being compared are the facial feature quantities of the person who has performed facial registration (authentication is successful).

[0061] When the facial authentication is successful in the facial authentication unit 212, the device coordination unit 213 notifies the access system 60 and the elevator control panel 70 of the authentication result. For example, when the facial authentication is successful, the access system 60 unlocks the access device (e.g., door), or the elevator control panel 70 performs car call and automatic registration of the destination floor. The access device such as the door is an example of a facility-side device that uses facial authentication. In the present invention, it is contemplated that various devices such as the elevator 3 can be used in addition to the access device through facial authentication.

[0062] The facial feature synchronization client 214 periodically polls the face registration server 30 to check whether the facial feature database 370 has been updated. If the facial feature database 370 has been updated, the facial feature synchronization client 214 performs processing according to the updated content.

[0063] For example, when there is an addition or change of facial feature values ​​in the facial feature value database 370 of the facial registration server 30, the facial feature value synchronization client 214 obtains the corresponding facial feature values ​​from the facial registration server 30 and stores them in the facial feature value database 215 of the present device. In addition, when there is a registration instruction from the facial registration server 30, the facial feature value synchronization client 214 obtains the corresponding facial feature values ​​from the facial registration server 30 and stores them in the facial feature value database 215 of the present device.

[0064] Furthermore, when there is a deletion of facial feature quantity in the facial feature quantity database 370 of the facial registration server 30, the facial feature quantity synchronization client 214 deletes the corresponding facial feature quantity from the facial feature quantity database 215 of the own device. In addition, when there is a deletion instruction from the facial registration server 30, the facial feature quantity synchronization client 214 deletes the corresponding facial feature quantity from the facial feature quantity database 215 of the own device.

[0065] The facial feature amount database 215 is a database storing facial feature amounts used for comparison by the facial authentication unit 212. The facial feature amount database 215 is a subordinate of the facial feature amount database 370 included in the face registration server 30.

[0066] [Functions of the face registration server]

[0067] Figure 4 1 is a diagram showing an example of the functional configuration of the face registration server 30 according to the present embodiment.

[0068] 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 .

[0069] The face registration screen processing unit 310 generates and provides a web screen for the user to register or delete the user's own face to or from the face registration server 30 using the portable terminal 40. In addition, the face registration screen processing unit 310 refers to the user information stored in the user information database 320 and implements login control from the portable terminal 40.

[0070] The user information database 320 is a database that stores information related to users who use the entry and exit system 60 and the elevator 3 (hereinafter referred to as "user information"). For example, as user information, information on logged-in users, passwords, and facilities to which users belong or use is managed. Examples of facilities to which users belong or use include residential complexes, workplaces (office buildings, factories, etc.), and facilities that have been scheduled to visit.

[0071] The management information registration screen processing unit 330 generates and provides a screen for registering information (user information) related to the user who registers facial information and information of a device (facial authentication device, etc.) used for facial authentication installed in a facility where the user enters and exits, and performs the following registration. User information is, for example, the name of the user and information about the facilities used. It is contemplated that the information of the facility-side device is input by an administrator or facility manager of the facial authentication registration system 50. The management information registration screen processing unit 330 stores the information in the user information database 320 or the device information database 340 according to the content of the input information.

[0072] The device information database 340 manages information about authentication devices installed in facilities where users enter and exit. The authentication devices are related to entry and exit based on facial authentication, and are, for example, facial authentication devices. Figure 4 In the facial authentication registration system 50, as the above-mentioned devices, a first facial authentication device 21, a second facial authentication device, and a third facial authentication device 23 are provided.

[0073] The face registration unit 350 performs processing corresponding to the content of the user's operation through the portable terminal 40. As the content of the user's operation, there are a registration event and a deletion event of a facial image. For example, when a facial photo is registered through the management information registration screen (that is, when a registration event is generated), the face registration unit 350 extracts facial feature quantities from the facial photo and transmits information on the facial feature quantities to the facial feature quantity synchronization management unit 360.

[0074] The facial feature synchronization management unit 360 generates a facial feature synchronization event based on the registration event or deletion event received from the facial registration unit 350. Figure 7 The facial feature synchronization management unit 360 manages the registration status of the facial feature quantity by referring to the synchronization object list shown in the figure. The facial feature quantity synchronization management unit 360 responds to the synchronization acquisition request from the first facial authentication device 21, the second facial authentication device, and the third facial authentication device 23, and notifies the update status of the facial feature quantity. In addition, the facial feature quantity synchronization management unit 360 also plays the role of sending the facial feature quantity to the first facial authentication device 21, the second facial authentication device, and the third facial authentication device 23. In addition, the facial feature quantity synchronization management unit 360 refers to the device information database 340 and creates a synchronization object list for the facial authentication devices installed in the target facility.

[0075] The facial feature amount database 370 is a database storing information of facial feature amounts in the face registration server 30. The facial feature amount database 370 is a main database of the facial feature amount database 215 possessed by the first facial authentication device 21, the second facial authentication device, and the third facial authentication device 23.

[0076] The user is only aware of the result of whether the registration of facial information (hereinafter also recorded as "face registration") is successful or failed. Conversely, the user is not aware of which facial authentication device has successfully registered the facial information. The same is true for the deletion of facial information (hereinafter also recorded as "face deletion"). In this embodiment, "registration success" and "failed registration" are defined as follows.

[0077] "Registration success" means that the facial information is registered in all the target facial authentication devices.

[0078] “Not registered” means that the facial information is not registered in all the facial authentication devices of the target.

[0079] According to the above definition, the facial recognition registration system 50 of this embodiment roughly has the following three functions.

[0080] (1) When registering facial information, if one of the multiple facial authentication devices fails to register facial information, the facial information of the facial authentication device that has successfully registered is deleted and the registration is set to a failed (unregistered) state.

[0081] → Allow the user to try to register facial information again from the portable terminal.

[0082] (2) When deleting facial information, if one of the multiple facial authentication devices fails to delete the facial information, the facial information of the facial authentication device that has successfully deleted the facial information is restored and the deletion is set to a failed (registered) state.

[0083] → Allow the user to try to delete the facial information from the portable terminal again.

[0084] (3) When a specific facial authentication device fails to continue face registration / face deletion, it is determined that there is a problem and a notification is given to the user that face registration / face deletion will not be performed (currently unavailable, etc.).

[0085] [Computer hardware structure]

[0086] Here, refer to Figure 5 The hardware configuration of the control system of the first facial authentication device 21 , the second facial authentication device 22 , the third facial authentication device 23 , and the facial registration server 30 constituting the facial authentication registration system 50 will be described.

[0087] Figure 5 1 is a block diagram showing a hardware configuration example of a control system of each device constituting the facial recognition registration system 50 . Figure 5The computer 500 shown is an example of hardware used as a computer. The first facial authentication device 21, the second facial authentication device 22, the third facial authentication device 23, and the facial registration server 30 shown in this embodiment are respectively executed by the computer 500 (computer), thereby, Figure 3 and Figure 4 The functional blocks shown cooperate to implement face registration and face authentication.

[0088] The computer 500 includes a CPU (Central Processing Unit) 501 , a ROM (Read Only Memory) 502 , and a RAM (Random Access Memory) 503 connected to a system bus. In addition, the computer 500 includes a nonvolatile storage device 504 and a communication interface 505 .

[0089] The CPU 501 reads the software program code for realizing each function of the present embodiment from the ROM 502, loads it into the RAM 503, and executes it. Variables and parameters generated during the operation processing of the CPU 501 are temporarily written into the RAM 503, and the CPU 501 reads these variables and parameters as appropriate. The CPU 501 executes the program code to realize the functions of each device constituting the facial recognition registration system 50. However, other processors such as an MPU (Micro Processing Unit) may be used instead of the CPU 501.

[0090] The nonvolatile storage device 504 is an example of a recording medium, and can store data used by a program, data obtained by executing a program, etc. In addition, an OS (Operating System) or a program executed by the CPU 501 may be recorded in the nonvolatile storage device 504. As the nonvolatile storage device 504, a HDD (Hard Disk Drive), an SSD (Solid State Drive), a disk medium using light or magnetism, or a semiconductor memory card, etc. may be used.

[0091] In this embodiment, the facial feature amount database 215 of the facial authentication device is constructed using the nonvolatile storage device 504. In addition, the user information database 320, the device information database 340, and the facial feature amount database 370 of the face registration server 30 are constructed using the nonvolatile storage device 504.

[0092] The communication interface 505 uses, for example, a communication device such as a NIC (Network Interface Card). The communication interface 505 is configured to be able to send and receive various data to and from an external device via a communication network such as a LAN or the Internet or a dedicated line of a connection terminal. In the face authentication device, the communication interface 505 is used to realize communication with the face registration server 30. Similarly, in the face registration server 30, the communication interface 505 is used to realize communication with the face authentication device.

[0093] In the first to third facial authentication devices 21 to 23, the CPU 501 executes the program, thereby realizing Figure 3 The facial feature value database 215 is implemented by the nonvolatile storage device 504 .

[0094] In the face registration server 30, the CPU 501 executes the program, thereby realizing Figure 4 The user information database 320 , the device information database 340 , and the facial feature database 370 are implemented by the nonvolatile storage device 504 .

[0095] In addition, the portable terminal 40 and the management PC 80 also have the same computer 500. The portable terminal 40 and the management PC 80 are connected to an input device and an output device not shown. In addition, the portable terminal 40 has a camera not shown. The user takes a picture of the face using the camera of the portable terminal 40 and sends the face image to the face registration server 30 to apply for face registration.

[0096] [Face registration process (normal case)]

[0097] Next, refer to Figure 6 The face registration process (normal) of the face authentication registration system 50 will be described.

[0098] Figure 6 2 is a sequence diagram showing an example of the face registration process (normal) of the face authentication and registration system 50 . Figure 6 The example shown is an example in which the face registration server 30 registers (synchronizes) the face information with the first face authentication device 21 and the second face authentication device 22. The target face authentication devices are not limited to two, but may be three or more.

[0099] First, the user operates the portable terminal 40 to access the face registration server 30, and the face registration screen processing unit 310 of the face registration server 30 transmits the face registration screen to the portable terminal 40 through the face registration screen processing unit 310. The user applies to register his / her own face information through the face registration screen displayed on the display 41 of the portable terminal 40. For example, in the face registration screen, the user uses the camera of the portable terminal 40 to take a picture of his / her own face, and sends the taken face picture as the face ID "XXX" together with the user information to the face registration server 30 (S1).

[0100] At the stage of applying for registration of facial information, the facial information of the user is not registered in the facial registration server 30, and therefore, it is displayed as "not registered" on the facial registration screen of the portable terminal 40. Facial ID (IDentification) is information that uniquely identifies facial information (facial image and facial feature quantity extracted from the facial image). For example, when registering a face based on the facial registration screen, the facial ID is assigned by the facial registration server 30.

[0101] Next, the face registration unit 350 of the face registration server 30 receives the face registration application from the portable terminal 40 and registers the face information. That is, the face registration unit 350 extracts the feature amount (hereinafter also referred to as "face feature amount") from the received face photo, and transmits the information of the face feature amount to the face feature amount synchronization management unit 360 (S2).

[0102] Then, the facial feature synchronization management unit 360 of the facial registration server 30 saves the facial feature in the facial feature database 370, creates a synchronization object list for managing synchronization objects and synchronization states, and temporarily saves it in the RAM 503 (S3). At this stage, since the registration of facial information is not yet completed, the facial registration screen of the portable terminal 40 displays "registering".

[0103] Figure 7 The following shows an example of a synchronization target list created by the facial feature synchronization management unit 360. Here, an example of a synchronization target list 700 created during face registration processing (in a normal case) is shown. The synchronization target list 700 has fields of "face ID", "device ID" and "synchronization status".

[0104] As described above, the "Face ID" field stores identification information for uniquely identifying facial information (a facial image and facial feature quantities extracted from the facial image). Figure 7 In the example, the facial ID "XXX" sent from the portable terminal 40 in step S1 is stored in the "Facial ID" field.

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

[0106] The "synchronization status" field stores information indicating the synchronization status of the facial information in the facial authentication device. After step S3, the synchronization status of the device IDs "1" and "2" is "waiting for registration".

[0107] return Figure 6 After step S3, the facial feature synchronization client 214 of the first facial authentication device 21 performs synchronization acquisition with the facial registration server 30 (S4). That is, the facial feature synchronization client 214 periodically polls the facial registration server 30 to check whether the facial feature database 370 is updated.

[0108] Next, the facial feature synchronization management unit 360 of the facial registration server 30 responds to the synchronization acquisition command from the first facial authentication device 21 (S5). When the facial feature of the facial ID "XXX" is newly registered in the facial feature database 370, the facial feature synchronization management unit 360 sends the facial feature of the facial ID "XXX" and the registration instruction to the first facial authentication device 21.

[0109] Next, the facial feature synchronization client 214 of the first facial authentication device 21 saves the facial feature of the facial ID "XXX" sent from the facial registration server 30 into the facial feature database 215. Then, the facial feature synchronization client 214 replies to the facial registration server 30 that the synchronization of the facial feature of the facial ID "XXX" has been completed (S6).

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

[0111] Next, after updating the synchronization target list 700, the facial feature amount synchronization management section 360 of the face registration server 30 returns a response to the completion of synchronization to the first facial authentication device 21 (S8).

[0112] Similarly, the facial feature synchronization client 214 of the second facial authentication device 22 performs synchronization acquisition on the facial registration server 30 (S9). Next, the facial feature synchronization management unit 360 of the facial registration server 30 sends the facial feature of the facial ID "XXX" to the second facial authentication device 22 as a response to the synchronization acquisition command from the second facial authentication device 22 (S10).

[0113] Next, the facial feature synchronization client 214 of the second facial authentication device 22 saves the facial feature of the facial ID "XXX" sent from the facial registration server 30 to the facial feature database 215, and replies to the facial registration server 30 that the synchronization of the facial feature of the facial ID "XXX" has been completed (S11).

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

[0115] Next, after updating the synchronization target list 700, the facial feature quantity synchronization management unit 360 returns a response to the completion of synchronization to the second facial authentication device 22 (S13).

[0116] Next, since the synchronization of the face registration of the first face authentication device 21 and the second face authentication device 22 is completed, the face feature synchronization management unit 360 deletes the information of the synchronization object (face ID, device ID) from the synchronization object list 700 ( S14 ).

[0117] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the portable terminal 40 of the result of the user's face registration application, that is, the face registration has been completed normally (S15). The registration of the user's face information has been completed normally, so it is displayed as "registered" in the face registration screen of the portable terminal 40.

[0118] like Figure 6 As shown, when the face registration process is performed normally, the face registration server 30 creates a synchronization target list when applying for face registration, and deletes the target from the synchronization target list when the synchronization of the target face authentication device is completed.

[0119] Alternatively, the facial feature synchronization management unit 360 of the facial registration server 30 may generate the synchronization target list 700 (step S3) and then transmit the facial feature of the facial ID "XXX" to the first facial authentication device 21, thereby omitting the synchronization acquisition process of step S4. Step S9 may also be omitted.

[0120] [Face registration process (if failed)]

[0121] Next, refer to Figure 8 The face registration process (failure) of the face authentication registration system 50 will be described.

[0122] Figure 8 : is a sequence diagram showing an example of the face registration process (failure) of the face authentication registration system 50 . Figure 8 The example shown is an example in which face registration succeeds in the first face authentication device 21 but fails in the second face authentication device 22. Figure 8 In step S1 to step S10, Figure 6 Same as the example.

[0123] After the face registration is successful in the first face authentication device 21 , the processes of steps S9 and S10 are performed between the second face authentication device 22 and the face registration server 30 .

[0124] After the processing of step S10, the facial feature synchronization client 214 of the second facial authentication device 22 performs the processing of saving the facial feature of the facial ID "XXX" sent from the facial registration server 30 into the facial feature database 215. Here, in the second facial authentication device 22, if the registration of the facial feature of the facial ID "XXX" is not completed normally for some reason, the facial feature synchronization client 214 cannot reply the synchronization completion to the facial registration server 30 (S11a).

[0125] If there is no reply of synchronization completion from the second facial authentication device 22 even after a predetermined time has passed, the facial feature synchronization management unit 360 of the face registration server 30 performs a timeout process. Then, the facial feature synchronization management unit 360 updates the synchronization target list (S12a).

[0126] Fig. 9 The following is an example of the synchronization target list 900 created by the facial feature synchronization management unit 360 during face registration processing (if failed). Here, the facial feature synchronization management unit 360 changes the synchronization status of the device ID "2" in the synchronization target list 900 from "registration waiting" to "registration failed".

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

[0128] Similarly, the facial feature synchronization management unit 360 of the facial registration server 30 requests the second facial authentication device 22 to delete the facial information (facial feature) of the facial ID "XXX" (S23). The facial feature synchronization client 214 of the second facial authentication device 22 receives the request to delete the facial information of the facial ID "XXX", deletes the facial feature of the facial ID "XXX" stored in the facial feature database 215, and replies a deletion response to the facial registration server 30 (S24). In addition, the facial information deletion requests for the first facial authentication device 21 and the second facial authentication device 22 based on the facial registration server 30 can be processed in parallel or in different orders.

[0129] During the face registration process, if face registration of one of the multiple face authentication devices fails, the facial feature synchronization management unit 360 deletes the face information of the successfully registered face authentication device and sets the registration to a failed (unregistered) state.

[0130] In addition, the face registration server 30 cannot distinguish whether the face authentication device fails to receive the synchronization acquisition response and does not register the target facial feature quantity, or successfully receives the synchronization acquisition response and registers the facial feature quantity but fails to send the synchronization completion. Therefore, the face registration server 30 also sends a deletion request to the second face authentication device 22 that caused the registration failure.

[0131] In this way, when the synchronization event of the facial information is the registration process of the facial information, when the facial information registration of one of the multiple facial authentication devices as the target fails, the facial feature synchronization management unit 360 of the facial registration server 30 requests the multiple facial authentication devices to delete the facial information. Then, the facial feature synchronization management unit 360 controls so that the facial information is deleted from the multiple facial authentication devices, thereby making the facial information unregistered in the multiple facial authentication devices.

[0132] Thereby, the synchronization state of the facial information can be made consistent with "registration failure (not registered)" in the plurality of target facial authentication devices.

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

[0134] Next, since the synchronization (deletion) of the facial information of the first facial authentication device 21 and the second facial authentication device 22 is completed, the facial feature synchronization management unit 360 deletes the information of the synchronization target (face ID, device ID) from the synchronization target list 900 ( S25 ).

[0135] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the portable terminal 40 of the failure of face registration as the result of the user's face registration application (S26). Since the user's face registration fails, the face registration screen of the portable terminal 40 displays "Not Registered".

[0136] Here, the face registration screen processing unit 310 of the face registration server 30 may cause the portable terminal 40 for the user to register face information to display a message for prompting re-registration when face information registration of one of the plurality of face authentication devices fails.

[0137] In addition, the face registration screen processing unit 310 of the face registration server 30 can determine that there is a problem when any specific face authentication device continues to fail to register face information, and send a notification to the portable terminal 40 so that the user does not register face information. For example, the face registration screen processing unit 310 determines that there is a problem (or failure) after face registration fails three times in a row. In this way, by notifying the user that the face information cannot be registered, unnecessary face registration processing can be avoided in the face registration server 30, and the processing load of the face registration server 30 can be reduced.

[0138] In the above Figure 8 as well as Fig. 9 In the processing example shown, when synchronization (face registration) fails in any face authentication device, processing is performed to make the synchronization status consistent in the multiple face authentication devices as the target. Therefore, in this embodiment, it is possible to prevent the occurrence of different phenomena such as the access device (such as a door) associated with the face authentication device that successfully registered the face can be unlocked, but the access device (such as a door) associated with the face authentication device that failed to register the face cannot be unlocked.

[0139] [Face removal processing (normal)]

[0140] Next, refer to Fig.10 , the face deletion processing (normal) of the face authentication registration system 50 is explained.

[0141] Fig.10 1 is a sequence diagram showing an example of face deletion processing (normal) of the face authentication registration system 50 . Fig.10 The illustrated example is an example when the face registration server 30 deletes (synchronizes) the face information from the first face authentication device 21 and the second face authentication device 22 .

[0142] First, the user operates the portable terminal 40 to access the facial registration server 30, and the facial registration screen processing unit 310 of the facial registration server 30 transmits the facial registration screen to the portable terminal 40 through the facial registration screen processing unit 310. The user applies to delete his own facial information through the facial registration screen displayed on the display 41 of the portable terminal 40 (S31). For example, if the user information is entered in the facial registration screen and the facial information is registered, the facial information (facial image) of the registered facial ID "XXX" is displayed. If there is no error in the facial image, the user presses the confirmation button not shown in the figure to advance the application for facial deletion. Usually, one user registers one facial information. However, multiple facial information can also be registered for one user.

[0143] At the stage where the application for deletion of the facial information is made, the facial information of the user is registered in the facial registration server 30 , and therefore, it is displayed as “registered” on the facial registration screen of the portable terminal 40 .

[0144] Next, the facial feature synchronization management unit 360 of the facial registration server 30 receives the facial deletion request from the portable terminal 40, creates a synchronization object list, and temporarily stores it in the RAM 503 (S32). At this stage, the facial information is not deleted yet, so it is displayed as "deleting" on the facial registration screen of the portable terminal 40.

[0145] Fig.11 The following is an example of a synchronization target list created by the facial feature synchronization management unit 360. Here, an example of a synchronization target list 1100 created during face deletion processing (normal case) is shown. As in face registration, the synchronization target list 1100 has fields for "face ID", "device ID", and "synchronization status".

[0146] exist Fig.11In the "Face ID" field, the face ID "XXX" sent from the portable terminal 40 in step S31 is stored. In the "Device ID" field, the device ID "1" of the first face authentication device 21 and the device ID "2" of the second face authentication device 22 are stored. In the "Synchronization Status" field, both device IDs "1" and "2" are "Waiting for Deletion".

[0147] return Fig.11 After step S32, the facial feature synchronization client 214 of the first facial authentication device 21 performs synchronization acquisition with the facial registration server 30 (S33). That is, as in facial registration, the facial feature synchronization client 214 periodically polls the facial registration server 30 to confirm whether the facial feature database 370 is updated. Figure 6 The procedure is the same as step S4, and step S33 (and step S38 described later) can be omitted.

[0148] Next, the facial feature synchronization management unit 360 of the facial registration server 30 responds to the synchronization acquisition command from the first facial authentication device 21 (S34). When the facial feature of the facial ID "XXX" is deleted from the facial feature database 370, the facial feature synchronization management unit 360 sends a deletion instruction of the facial feature of the facial ID "XXX" to the first facial authentication device 21.

[0149] Next, the facial feature synchronization client 214 of the first facial authentication device 21 deletes the facial feature of the facial ID “XXX” from the facial feature database 215 according to the deletion instruction of the facial feature of the facial ID “XXX” sent from the facial registration server 30. Then, the facial feature synchronization client 214 replies to the facial registration server 30 that the synchronization of the facial feature of the facial ID “XXX” has been completed (S35).

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

[0151] Next, after updating the synchronization target list 1100, the facial feature amount synchronization management section 360 of the face registration server 30 returns a response to the completion of synchronization to the first facial authentication device 21 (S37).

[0152] Similarly, the facial feature synchronization client 214 of the second facial authentication device 22 performs synchronization acquisition on the facial registration server 30 (S38). Next, the facial feature synchronization management unit 360 of the facial registration server 30 sends a deletion instruction of the facial feature of the facial ID "XXX" to the second facial authentication device 22 as a response to the synchronization acquisition command from the second facial authentication device 22 (S39).

[0153] Next, the facial feature synchronization client 214 of the second facial authentication device 22 deletes the facial feature of the facial ID “XXX” from the facial feature database 215 in accordance with the deletion instruction of the facial feature of the facial ID “XXX” sent from the facial registration server 30, and replies to the facial registration server 30 that the synchronization of the facial feature of the facial ID “XXX” has been completed (S40).

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

[0155] Next, after updating the synchronization target list 1100, the facial feature quantity synchronization management unit 360 returns a response to the completion of synchronization to the second facial authentication device 22 (S42).

[0156] Next, since the synchronization of face deletion for the first facial authentication device 21 and the second facial authentication device 22 is completed, the facial feature synchronization management unit 360 deletes the information of the synchronization object (face ID, device ID) from the synchronization object list 1100 ( S43 ).

[0157] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the portable terminal 40 of the result of the user's face deletion application, that is, the face deletion has been completed normally (S44). Since the deletion of the user's facial information has been completed normally, it is displayed as "unregistered" in the face registration screen of the portable terminal 40.

[0158] like Fig.10 As shown, when the face deletion process is performed normally, the face registration server 30 creates a synchronization object list when applying for face deletion, and deletes the object from the synchronization object list when the synchronization of the object face authentication device is completed.

[0159] [Face removal processing (if failed)]

[0160] Next, refer to Fig.12 The face deletion process (failure) of the face authentication registration system 50 will be described.

[0161] Fig.12 1 is a sequence diagram showing an example of face deletion processing (failure) of the face authentication registration system 50 . Fig.12 The example shown is an example in which the face is successfully deleted in the first face authentication device 21, but failed to be deleted in the second face authentication device 22. Fig.12 In step S31 to step S39, Fig.10 Same as the example.

[0162] After the face is successfully deleted in the first face authentication device 21 , the processes of steps S38 and S39 are performed between the second face authentication device 22 and the face registration server 30 .

[0163] After the processing of step S39, the facial feature synchronization client 214 of the second facial authentication device 22 executes the process of deleting the facial feature of the facial ID "XXX" from the facial feature database 215 according to the deletion instruction of the facial feature of the facial ID "XXX" sent from the facial registration server 30. Here, in the second facial authentication device 22, if the deletion of the facial feature of the facial ID "XXX" is not completed normally for some reason, the facial feature synchronization client 214 cannot reply the synchronization completion to the facial registration server 30 (S40a).

[0164] If there is no reply of synchronization completion from the second facial authentication device 22 even after a predetermined time has passed, the facial feature synchronization management unit 360 of the face registration server 30 performs a timeout process. Then, the facial feature synchronization management unit 360 updates the synchronization target list (S41a).

[0165] Fig.13 The following is an example of the synchronization target list 1300 created by the facial feature synchronization management unit 360 during face registration processing (if failed). Here, the facial feature synchronization management unit 360 changes the synchronization status of the device ID "2" in the synchronization target list 1300 from "waiting for deletion" to "deletion failure".

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

[0167] Similarly, the facial feature synchronization management unit 360 of the facial registration server 30 requests the second facial authentication device 22 to register the facial information (facial feature) of the facial ID "XXX" (S53). The facial feature synchronization client 214 of the second facial authentication device 22 receives the registration request for the facial information of the facial ID "XXX", registers the facial feature of the facial ID "XXX" in the facial feature database 215, and returns a registration response to the facial registration server 30 (S54). In addition, the facial information registration requests for the first facial authentication device 21 and the second facial authentication device 22 based on the facial registration server 30 can be processed in parallel or in different orders.

[0168] During the face deletion process, if the face deletion of one of the multiple face authentication devices as the target fails, the face feature synchronization management unit 360 restores the face information of the face authentication device that has been successfully deleted and sets it to a state of failed deletion (registered). For example, it is conceivable that the face information temporarily deleted from the face feature database 215 by the first face authentication device 21 is temporarily stored in the RAM 503. Alternatively, the data of the face feature database 215 may be read out to the RAM 503, and after determining the success or failure of synchronization (here, deletion), the data may be written back to the face feature database 215.

[0169] In addition, the face registration server 30 cannot distinguish whether the target facial feature quantity is not deleted due to failure to receive the synchronization acquisition response in the facial authentication device, or whether the target facial feature quantity is deleted due to success in receiving the synchronization acquisition response but failure to send the synchronization completion. Therefore, the face registration server 30 also sends a registration request to the second facial authentication device 22 that is the cause of the deletion failure.

[0170] In this way, when the synchronization event of the facial information is the deletion process of the facial information, the facial feature synchronization management unit 360 of the facial registration server 30 requests the plurality of facial authentication devices to register (restore) the facial information when the deletion of the facial information of one of the plurality of facial authentication devices as the target fails. Then, the facial feature synchronization management unit 360 controls so that the facial information becomes registered in the plurality of facial authentication devices by causing the plurality of facial authentication devices to register (restore) the facial information.

[0171] Thereby, the synchronization state of the facial information can be made consistent with "deletion failure (registered)" in the plurality of target facial authentication devices.

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

[0173] Next, since the synchronization (registration) of the facial information of the first facial authentication device 21 and the second facial authentication device 22 is completed, the facial feature synchronization management unit 360 deletes the information of the synchronization target (face ID, device ID) from the synchronization target list 1300 ( S55 ).

[0174] Next, the face registration screen processing unit 310 of the face registration server 30 notifies the portable terminal 40 of the face deletion failure as the result of the user's face deletion application (S56). Since the user's face deletion fails, the face registration screen of the portable terminal 40 displays "deletion failed".

[0175] Here, when the deletion of facial information of one facial authentication device among the plurality of facial authentication devices fails, the facial registration screen processing unit 310 of the facial registration server 30 may cause the portable terminal 40 for the user to delete facial information to display a message for prompting the user to delete again.

[0176] In addition, the face registration screen processing unit 310 of the face registration server 30 can determine that there is a problem when any specific face authentication device continues to fail to delete the face information, and send a notification to the portable terminal 40 so that the user does not delete the face information. For example, after the face deletion fails three times in a row, the face registration screen processing unit 310 determines that there is a problem (or failure). In this way, by notifying the user that the face information cannot be deleted, unnecessary face deletion processing can be avoided in the face registration server 30, and the processing load of the face registration server 30 can be reduced.

[0177] In the above Fig.12 as well as Fig.13 In the processing example shown, when synchronization (face deletion) fails in any facial authentication device, processing is performed to make the synchronization status consistent in the multiple facial authentication devices as the target. Therefore, in this embodiment, it is possible to prevent the occurrence of different phenomena such as the access device (such as a door) associated with the facial authentication device that successfully deleted the face cannot be unlocked, but the access device (such as a door) associated with the facial authentication device that failed to delete the face can be unlocked.

[0178] As described above, the facial authentication registration system 50 of the present embodiment includes: a facial registration server that stores facial information (at least facial feature quantities extracted from facial images); and a plurality of facial authentication devices that register facial information and use it for facial authentication. Furthermore, when the facial registration server receives a facial information synchronization event (registration / deletion), it performs facial information synchronization processing on the plurality of facial authentication devices as the target, and when the synchronization of one of the plurality of facial authentication devices fails, the facial registration server controls the plurality of facial authentication devices to return to the state before the synchronization processing.

[0179] In the present embodiment thus constituted, when the synchronization of facial information fails in any facial authentication device, a process of making the synchronization states consistent among the multiple facial authentication devices as targets is executed. Thus, the present embodiment can prevent the occurrence of different phenomena such as the device (e.g., door, elevator) associated with the facial authentication device with which the synchronization of facial information succeeded can be authenticated, but the device (e.g., door, elevator) associated with the facial authentication device with which the synchronization of facial information failed cannot be authenticated. Therefore, the present embodiment can prevent the user from feeling inconvenienced or confusing the user.

[0180] In addition, the present invention is not limited to the above-mentioned embodiments. As long as it does not deviate from the spirit of the present invention described in the claims, various other application examples and modified examples can be adopted. For example, the above-mentioned embodiments are embodiments that describe the structure in detail and specifically in order to easily explain the present invention, and are not limited to having all the described constituent elements. In addition, for a part of the structure of the above-mentioned embodiments, other constituent elements may be added, replaced, or deleted.

[0181] In addition, the above-mentioned structures, functions, processing units, etc. can be partially or entirely implemented in hardware by, for example, designing with integrated circuits. As hardware, a broad processor device such as FPGA (Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit) can be used. In addition, the cloud environment can be flexibly used to store facial feature quantities, user information, device information, etc.

[0182] In addition, each component (functional block) of each device constituting the facial recognition registration system of the above-mentioned embodiment can be installed in any hardware as long as the respective hardware can send and receive information to each other via a network. In addition, the processing implemented by a certain processing unit can be implemented by a single hardware or by distributed processing based on multiple hardware.

[0183] In the above-described embodiments, control lines or information lines are shown as lines that are considered necessary for explanation, and not all control lines or information lines are necessarily shown in a product. In reality, it is considered that almost all components are connected to each other.

[0184] Explanation of symbols

[0185] 21…a first facial authentication device, 22…a second facial authentication device, 23…a third facial authentication device, 30…a facial registration server, 40…a portable terminal, 50…a facial authentication registration system, 60…an entry and exit system, 70…an elevator control panel, 211…a camera image acquisition unit, 212…a facial authentication unit, 213…a device collaboration unit, 214…a facial feature synchronization client, 215…a facial feature database, 310…a facial registration screen processing unit, 320…a user information database, 330…a management information registration screen processing unit, 340…a device information database, 350…a facial registration unit, 360…a facial feature synchronization management unit, 370…a facial feature database, 700…a synchronization object list, 900…a synchronization object list, 1100…a synchronization object list, 1300…a synchronization object list.

Claims

1. A facial authentication registration system, comprising: a facial registration server storing facial information; a plurality of facial authentication devices registering the facial information and using it for facial authentication, characterized in that: When the facial registration server receives a facial information synchronization event, it performs synchronization processing of the facial information on the multiple facial authentication devices as objects, and when the synchronization of one of the multiple facial authentication devices fails, the facial registration server controls the multiple facial authentication devices to return to the state before the synchronization processing.

2. The facial recognition registration system according to claim 1, characterized in that: In a case where the synchronization event of the facial information is the registration processing of the facial information, when one facial authentication device among the multiple facial authentication devices as the object fails to register the facial information, the facial registration server performs the following control: requesting the multiple facial authentication devices to delete the facial information, so that the facial information is unregistered in the multiple facial authentication devices.

3. The facial recognition registration system according to claim 2, characterized in that: When one of the plurality of facial authentication devices fails to register the facial information, the facial registration server causes a terminal for a user to register the facial information to display a message prompting the user to register again.

4. The facial recognition registration system according to claim 3, characterized in that: In the case where the facial authentication device fails to continue to register the facial information, the facial registration server issues a notification to the terminal that the facial information will not be registered.

5. The facial recognition registration system according to claim 1, characterized in that: In the case where the synchronization event of the facial information is the deletion processing of the facial information, when one facial authentication device among the multiple facial authentication devices as the object fails to delete the facial information, the facial registration server performs the following control: requesting the multiple facial authentication devices to register the facial information, so that the facial information becomes registered in the multiple facial authentication devices.

6. The facial authentication registration system according to claim 5, characterized in that: In the case that one of the plurality of facial authentication devices fails to delete the facial information, the facial registration server causes a terminal used by the user to delete the facial information to display a message prompting the user to delete the facial information again.

7. The facial authentication registration system according to claim 6, characterized in that: In the case where the facial authentication device fails to continue deleting the facial information, the facial registration server sends a notification to the terminal not to delete the facial information.

8. A plurality of facial authentication devices for a facial authentication registration system, wherein the facial authentication registration system uses facial information stored in a facial registration server to perform facial authentication, characterized in that: The plurality of facial authentication devices synchronize the facial information stored in the facial registration server, and when the synchronization of the facial information fails, return to a state before synchronization of the facial information according to an instruction sent from the facial registration server.

9. A facial authentication registration method performed by a facial authentication registration system, the facial authentication registration system comprising: a facial registration server storing facial information; a plurality of facial authentication devices registering the facial information and using it for facial authentication, characterized in that: The facial recognition registration method includes the following processing: In the face registration server, when receiving a face information synchronization event, a process of performing a face information synchronization process on the plurality of face authentication devices as targets; as well as When synchronization of one of the plurality of facial authentication devices fails, the facial registration server performs a process of controlling the plurality of facial authentication devices to return to a state before the synchronization process.

Images