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

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 and registration system, a face authentication device, and a face authentication and registration method. [Background technology]

[0002] 2. Description of the Related Art Conventionally, face recognition systems have been developed that perform face recognition processing based on image data obtained by photographing a subject.

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

[0004] Incidentally, paragraph

[0273] of Patent Document 1 states that "a user who has failed in face registration is reported to an administrator, and the administrator is prompted to re-register the user." Also, paragraph

[0288] states that "if face registration has failed, a request to delete face features is not made, and face matching is performed with the old face features unchanged." [Prior art documents] [Patent documents]

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

[0006] However, in a configuration such as the technology described in Patent Document 1, in which multiple face recognition devices and a server device having a face matching process and a face matching database are connected via a network, if a communication failure occurs, the face recognition device will not be able to obtain the user's authentication results.

[0007] To solve the above-mentioned inconveniences, a facial recognition device installed at the facility used by the user can be configured to accumulate the user's facial information (e.g., facial feature data) and then compare the user's facial image data with the facial information.

[0008] However, when storing the facial information of a subject in multiple facial recognition devices, if registration of new facial information to a specific facial recognition device fails, the following problem will occur: If the state where registration has failed only in a specific facial recognition device is left as it is, different phenomena will occur, for example, the entrance / exit equipment linked to the facial recognition device where registration was successful can be authenticated (unlocked), but the entrance / exit equipment linked to the facial recognition device where registration failed cannot be authenticated (unlocked).

[0009] In addition, Patent Document 1 describes a method of urging a user who fails to register his / her face to re-register, but there are cases where the re-registration fails even if the user tries to re-register. Also, in the technology described in Patent Document 1, when face registration fails, face matching is performed using old face features.

[0010] In light of the above situation, when a user's facial information is stored and facial recognition is performed using multiple facial recognition devices installed in a facility, it is desirable to prevent the occurrence of different phenomena, such as a user being able to be recognized using some equipment but not using other equipment. [Means for solving the problem]

[0011] In order to solve the above problems, a face authentication registration system according to one aspect of the present invention is a face authentication registration system including a face registration server that stores face information, and a plurality of face authentication devices that register the face information and use it for face authentication. When the face registration server receives a face information synchronization event, it executes a face information synchronization process for the plurality of target face authentication devices, and if synchronization fails for any one of the plurality of face authentication devices, it controls the plurality of face authentication devices to return to a state before the synchronization process. Effect of the Invention

[0012] According to at least one aspect of the present invention, when a user's facial information is stored and facially recognized using multiple facial recognition devices installed in a facility, it is possible to prevent the occurrence of different phenomena, such as authentication being possible with some equipment but not with other equipment. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an example of a scene in which a face authentication registration system according to an embodiment of the present invention is used. [Diagram 2] 1 is a diagram showing an example of the overall configuration of a face authentication registration system according to an embodiment of the present invention and an overview of face registration; [Diagram 3] FIG. 2 is a diagram illustrating an example of a functional configuration of a face authentication device according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram illustrating an example of a functional configuration of a face registration server according to an embodiment of the present invention. [Diagram 5] FIG. 2 is a block diagram showing an example of the hardware configuration of a computer provided in each device constituting the face authentication registration system according to an embodiment of the present invention. [Figure 6] 4 is a sequence chart showing an example of face registration processing (normal) by the face authentication registration system according to one embodiment of the present invention. [Figure 7] FIG. 2 is a diagram showing an example of a synchronization target list created during face registration processing (normal) in the face authentication registration system according to one embodiment of the present invention. [Figure 8] 4 is a sequence chart showing an example of face registration processing (failure) by the face authentication registration system according to one embodiment of the present invention. [Figure 9] FIG. 2 is a diagram showing an example of a synchronization target list created during face registration processing (failure) in the face authentication registration system according to one embodiment of the present invention. [Figure 10] 4 is a sequence chart showing an example of face deletion processing (normal) by the face authentication registration system according to one embodiment of the present invention. [Figure 11] FIG. 2 is a diagram showing an example of a synchronization target list created during face deletion processing (normal) in the face authentication registration system according to an embodiment of the present invention. [Figure 12] 1 is a sequence chart showing an example of face deletion processing (failure) by the face authentication registration system according to an embodiment of the present invention. [Figure 13] FIG. 11 is a diagram showing an example of a synchronization target list created when a face deletion process (fails) in the face authentication registration system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an example of a mode for carrying out the present invention (hereinafter referred to as an "embodiment") will be described with reference to the accompanying drawings. In this specification and the accompanying drawings, identical components or components having substantially the same functions are designated by the same reference numerals, and duplicated descriptions will be omitted.

[0015] <One embodiment> [Scenes in which the facial recognition registration system is used] First, a usage example of a face authentication registration system according to an embodiment of the present invention will be described with reference to FIG. Fig. 1 is a diagram showing an example of a situation in which a face authentication registration system according to an embodiment of the present invention is used. The configuration of the face authentication registration system will be described in detail from Fig. 2 onwards.

[0016] As an example of a usage form of the face recognition registration system, it is possible to provide an entrance / exit service by face recognition to residents of an apartment building (also called "condominium" in Japan). As shown in Fig. 2 described later, the face recognition registration system according to this embodiment is a system that can register faces from the cloud (face registration server 30 in Fig. 2 described later) to a face recognition device having a face recognition function by AI (Artificial Intelligence) or the like.

[0017] A resident U of an apartment building can receive various entrance and exit services by registering his / her face in a face recognition registration system using a mobile device or the like. For example, an entrance to an apartment building may be equipped with two doors. The first door 1 is an automatic door, and anyone other than the resident U can enter and exit through it. The second door 2 after passing through the first door 1 is an auto-lock type, and must be unlocked using an unlocking method (key, PIN number, facial image) or must be unlocked by the resident U.

[0018] If face registration has been completed, the resident U can unlock the second door 2 by authenticating the face image captured by the surveillance camera 4. In addition, the resident U can realize car call of the elevator 3 and automatic destination floor registration by authenticating the face image captured by the surveillance camera 5 in the elevator hall. The face of the resident U is linked to the destination floor by pre-registration. Such a face recognition registration system can also be applied to entrance and exit services for office buildings, factories, etc.

[0019] [Overall configuration of the face recognition registration system and overview of face registration] Next, the overall configuration of the face authentication registration system according to this embodiment and an overview of face registration will be described with reference to FIG. FIG. 2 is a diagram showing an example of the overall configuration of the face authentication registration system according to this embodiment and an overview of face registration.

[0020] 2, the face authentication registration system 50 includes a first face authentication device 21, a second face authentication device 22, a third face authentication device 23, and a face registration server 30. In this example, a first camera 11 and a second camera 12 are connected to the first face authentication device 21, a third camera 13 and a fourth camera 14 are connected to the second face authentication device 22, and a fifth camera 15 and a sixth camera 16 are connected to the third face authentication device 23. The number of face authentication devices is not limited to three, and may be two, four or more. Also, the number of cameras connected to one face authentication device may be three or more.

[0021] The user operates a touch sensor implemented on the display 41 of the mobile terminal 40 to select a menu for synchronizing face information from a menu screen. The user takes a picture of the face of a person (the user or a family member, etc.) to be registered with the camera of the mobile terminal 40, and transmits the face photo (face image data) to the face registration server 30 to apply for face registration.

[0022] In addition to the mobile terminal 40, various terminals can be used to apply for face registration, such as an information processing device such as a desktop PC (Personal Computer) integrated with a camera display, or a camera with a communication function. Also, face registration may be applied for using a face photo that has been taken in advance and stored in a terminal or the like. Also, subjects who can apply for face registration are those who have been given permission to enter and leave the facility in advance by the manager or person in charge of the facility.

[0023] The face registration server 30 accepts a user's application for face registration from the mobile terminal 40. The face registration server 30 extracts features of the face image received from the mobile terminal 40 at the time of the face registration application, and stores the extracted features in a database (master) as face feature data to be synchronized. The face registration server 30 then transmits the face feature 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 itself, and synchronizes the face feature data. Hereinafter, the face feature data will be abbreviated as "facial feature".

[0024] When the synchronization of the facial feature amounts is successful, the first face authentication device 21, the second face authentication device 22, and the third face authentication device 23 store the synchronized facial feature amounts in their respective databases (slave).

[0025] In the face authentication registration system 50 of this embodiment, the facial feature of the user may be synchronized with a face authentication device installed in a facility (such as an apartment building, an office building, or a factory) used by the user. For example, when the first face authentication device 21 and the second face authentication device 22 are installed in the apartment building where the user lives, the face registration server 30 synchronizes the facial feature of the first face authentication device 21 and the second face authentication device 22 based on the user information.

[0026] The flow (1) to (5) from face registration by the face recognition registration system 50 to entering and leaving a facility will be described below using entering and leaving an apartment building as an example. (1) A resident U of an apartment building takes a picture of his / her face with the camera of the mobile terminal 40 and transmits the face picture (face image) to the face registration server 30. (2) The face registration server 30 stores the facial features extracted from the face photograph in a database of the face registration server 30. (3) The facial feature amount is synchronized with a plurality of facial recognition devices (first facial recognition device 21 to third facial recognition device 23) installed in the apartment building. (4) The multiple face recognition devices perform face recognition by matching face images Im acquired from the surveillance cameras with face feature amounts synchronized by the face registration server 30. The cameras used for face recognition may be integrated with the face recognition devices. (5) Once the face recognition device recognizes the face of resident U, it controls the unlocking of the entrance door and the calling of elevator 3.

[0027] Conventionally, facial features are synchronized with multiple facial recognition devices. However, if synchronization fails with only a specific facial recognition device, a gap occurs in which some doors can be unlocked by facial recognition, but other doors cannot be unlocked because facial recognition cannot be performed. For example, assume that the first camera 11 is the surveillance camera 4 in FIG. 1, the second camera 12 is the surveillance camera 5, and the facial features of a resident U are registered in the first facial recognition device 21, but the facial features of a resident U are not registered in the second facial recognition device 22. In this case, the resident U can pass through the second door 2 at the entrance, but cannot call a car in the elevator hall where the surveillance camera 5 is installed.

[0028] Such differences are inconvenient and confusing for the resident U. For this reason, it is necessary for the facial feature amounts to be synchronized in all of the multiple facial recognition devices installed in the facility used by the resident U. Hereinafter, a method for synchronizing the facial feature amounts in all of the facial recognition devices in the facility that the user is to use in the facial recognition registration system 50 according to this embodiment will be described.

[0029] [Facial recognition device functions] 3 is a diagram showing an example of the functional configuration of the face recognition device according to this embodiment. The functional configuration of the face recognition device will be described using the first face recognition device 21 as an example, but the same applies to the second face recognition device 22 and the third face recognition device 23.

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

[0031] The camera image acquisition unit 211 acquires data in a stream from a surveillance camera installed at the entrance, elevator hall, or the like, and decodes the data from video to still images (sometimes simply called "images").

[0032] The face authentication unit 212 detects a face from the image acquired by the camera image acquisition unit 211. Then, the face authentication unit 212 extracts features from the detected face area and compares the extracted features with the face features stored in the face feature database 215. For example, when the feature matching rate is equal to or higher than a preset standard, the face authentication unit 212 determines that the matched face features are those of a person whose face is registered (authentication successful).

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

[0034] The facial feature amount synchronization client 214 periodically polls the face registration server 30 to check whether the facial feature amount database 370 has been updated. When the facial feature amount database 370 has been updated, the facial feature amount synchronization client 214 performs processing according to the contents of the update.

[0035] For example, when a facial feature is added or changed in the facial feature database 370 of the face registration server 30, the facial feature synchronization client 214 acquires the corresponding facial feature from the face registration server 30 and stores it in the facial feature database 215 of its own device. In addition, when a registration instruction is received from the face registration server 30, the facial feature synchronization client 214 acquires the corresponding facial feature from the face registration server 30 and stores it in the facial feature database 215 of its own device.

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

[0037] The facial feature amount database 215 is a database that stores facial feature amounts used for matching by the face authentication unit 212. The facial feature amount database 215 is a slave of the facial feature amount database 370 that the face registration server 30 has.

[0038] [Face registration server functions] FIG. 4 is a diagram showing 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 facial feature amount synchronization management unit 360 , and a facial feature amount database 370 .

[0039] The face registration screen processing unit 310 generates and provides a Web screen for a user to use the mobile terminal 40 to register or delete his / her face in the face registration server 30. The face registration screen processing unit 310 also refers to user information stored in the user information database 320 and controls login from the mobile terminal 40.

[0040] The user information database 320 is a database that stores information (hereinafter referred to as "user information") about users who use the entrance / exit system 60 and the elevator 3. For example, the user information managed includes login users, passwords, and information about facilities to which the users belong or which they use. Facilities to which the users belong or which they use include apartment complexes, workplaces (office buildings, factories, etc.), and facilities to which they have made reservations to visit.

[0041] The management information registration screen processing unit 330 generates and provides a screen for registering information (user information) about the user who is registering face information, and for registering information about equipment (such as a face authentication device) used for face authentication that is installed in the facility the user enters and exits. The user information is, for example, the user's name and information about the facility used. It is assumed that the information about the equipment on the facility side will be input by the administrator of the face authentication registration system 50 or the person in charge of the facility. The management information registration screen processing unit 330 stores the input information in the user information database 320 or the device information database 340 depending on the content of the information input.

[0042] The device information database 340 manages information on authentication devices installed in facilities where users enter and exit. The authentication devices are related to entrance and exit by facial recognition, and are, for example, facial recognition devices. In Fig. 4, a first facial recognition device 21, a second facial recognition device, and a third facial recognition device 23 are installed in a facial recognition registration system 50 as the above-mentioned devices.

[0043] The face registration unit 350 executes processing according to the content of an operation performed by the user on the mobile terminal 40. The content of the operation performed by the user includes a registration event and a deletion event of a face image. For example, when a face photo is registered on the management information registration screen (i.e., when a registration event occurs), the face registration unit 350 extracts facial features from the face photo and sends the information of the facial features to the facial feature synchronization management unit 360.

[0044] The facial feature amount synchronization management unit 360 creates a synchronization target list shown in Fig. 7 etc. in response to a registration event or deletion event received from the face registration unit 350 to manage the registration status of the facial feature amount. The facial feature amount synchronization management unit 360 notifies the update status of the facial feature amount in response to a synchronization acquisition request from the first face authentication device 21, the second face authentication device, and the third face authentication device 23. The facial feature amount synchronization management unit 360 also plays a role in transmitting the facial feature amount to the first face authentication device 21, the second face authentication device, and the third face authentication device 23. Furthermore, the facial feature amount synchronization management unit 360 refers to the device information database 340 and creates a synchronization target list for the face authentication devices installed in the target facility.

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

[0046] The user is only aware of the result of whether the registration of face information (hereinafter also referred to as "face registration") was successful or unsuccessful. Conversely, the user is not aware of which face recognition device the registration of face information was successful in. The same is true for the deletion of face information (hereinafter also referred to as "face deletion"). In this embodiment, "successful registration" and "unregistered" are defined as follows. "Enrollment successful" refers to face information being registered in all target face recognition devices. "Unregistered" refers to the case where facial information is not registered in any of the target facial recognition devices.

[0047] Based on the above definitions, the face authentication registration system 50 according to this embodiment has the following three main functions. (1) When registering face information, if registration of face information fails for any of the multiple target face recognition devices, the face information of the face recognition devices that have already succeeded in registration is deleted and the registration is set to a failed (unregistered) state. →Ask the user to try registering their face information again using their mobile device.

[0048] (2) When deleting face information, if the deletion of face information from any of the multiple target face recognition devices fails, the face information from the face recognition devices that have already succeeded in deleting the face information is restored and the state is changed to one of failed deletion (registered). →Ask the user to try deleting the facial information from their mobile device again.

[0049] (3) If a specific facial recognition device continues to fail to register or delete a face, it will be determined that there is a malfunction, and a notification will be sent to the user (such as "currently unavailable") to prevent them from registering or deleting their face.

[0050] [Computer hardware configuration] Here, the hardware configuration of the control system of the first face authentication device 21, the second face authentication device 22, the third face authentication device 23, and the face registration server 30, which constitute the face authentication registration system 50, will be described with reference to FIG.

[0051] Fig. 5 is a block diagram showing an example of the hardware configuration of the control system of each device constituting the face recognition registration system 50. The calculator 500 shown in Fig. 5 is an example of hardware used as a computer. In each of the first face recognition device 21, the second face recognition device 22, the third face recognition device 23, and the face registration server 30 shown in this embodiment, the calculator 500 (computer) executes a program, and the functional blocks shown in Figs. 3 and 4 cooperate to realize face registration and face authentication.

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

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

[0054] The non-volatile storage 504 is an example of a recording medium, and is capable of storing data used by a program, data obtained by executing a program, etc. An operating system (OS) and programs executed by the CPU 501 may also be recorded in the non-volatile storage 504. As the non-volatile storage 504, a hard disk drive (HDD), a solid state drive (SSD), a disk medium using light or magnetism, a semiconductor memory card, etc. may be used.

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

[0056] The communication interface 505 is implemented by a communication device such as a network interface card (NIC). The communication interface 505 is configured to be capable of transmitting and receiving various data to and from an external device via a communication network such as a LAN or the Internet to which a terminal is connected, or a dedicated line. In the face authentication device, communication with the face registration server 30 is realized by using the communication interface 505. Similarly, in the face registration server 30, communication with the face authentication device is realized by using the communication interface 505.

[0057] In the first to third face authentication devices 21 to 23, the CPU 501 executes a program to realize the functions of the blocks shown in FIG.

[0058] 4 is implemented by the CPU 501 executing a program in the face registration server 30. The user information database 320, the device information database 340, and the face feature amount database 370 are implemented by the non-volatile storage 504.

[0059] The mobile terminal 40 and the management PC 80 also include a similar computer 500. However, the mobile terminal 40 and the management PC 80 are connected to an input device and an output device (not shown). The mobile terminal 40 also includes a camera (not shown). A user takes a picture of his / her face with the camera of the mobile terminal 40 and transmits the face image to the face registration server 30 to apply for face registration.

[0060] [Face registration process (if successful)] Next, face registration processing (normal) by the face authentication registration system 50 will be described with reference to FIG. Fig. 6 is a sequence chart showing an example of face registration processing (normal) by the face authentication registration system 50. The example shown in Fig. 6 is an example in which the face registration server 30 registers (synchronizes) face information in the first face authentication device 21 and the second face authentication device 22. The number of target face authentication devices is not limited to two, and 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 a face registration screen to the mobile terminal 40 via the face registration screen processing unit 310. The user applies for registration of his / her own face information via 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 his / her own face with the camera of the mobile terminal 40, and transmits the taken face picture to the face registration server 30 as a face ID "XXX" together with user information (S1).

[0062] At the stage of applying for face information registration, the user's face information is not registered in the face registration server 30, so "Not Registered" is displayed on the face registration screen of the mobile terminal 40. Face ID (IDentification) is information that uniquely identifies face information (face image and face feature amount extracted from the face image). For example, when a face is registered on the face registration screen, a face ID is assigned by the face registration server 30.

[0063] Next, the face registration unit 350 of the face registration server 30 accepts the face registration application from the mobile terminal 40 and registers the face information. That is, the face registration unit 350 extracts features (hereinafter also referred to as "facial feature amounts") from the received face photograph and sends the information on the facial feature amounts to the facial feature amount synchronization management unit 360 (S2).

[0064] Then, the facial feature amount synchronization management unit 360 of the face registration server 30 stores the facial features in the facial feature amount database 370, creates a synchronization target list for managing synchronization targets and synchronization states, and temporarily stores the list in the RAM 503 (S3). At this stage, the registration of face information is not yet complete, so the face registration screen of the mobile terminal 40 displays "Registering".

[0065] 7 shows an example of a synchronization target list created by the face feature amount synchronization management unit 360. Here, an example of a synchronization target list 700 created during face registration processing (normal case) is shown. The synchronization target list 700 has fields for "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 feature amount extracted from the face image). In the example of Fig. 7, the "face ID" field stores the face ID "XXX" transmitted from the mobile terminal 40 in step S1.

[0067] The "device ID" field stores identification information for uniquely identifying authentication devices installed in the facility the user enters and exits. In this example, 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 as device IDs. For example, among multiple face authentication devices connected to the face registration server 30, the device ID of a face authentication device installed in a 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 from information managed in the device information database 340.

[0068] The "synchronization state" field stores information indicating the synchronization state of face information in the face authentication device. Immediately after step S3, the synchronization state for both device IDs "1" and "2" is "waiting for registration."

[0069] Returning to Fig. 6, the description will be continued. After step S3, the facial feature amount synchronization client 214 of the first face authentication device 21 executes synchronization acquisition with the face registration server 30 (S4). That is, the facial feature amount synchronization client 214 periodically polls the face registration server 30 to check whether the facial feature amount database 370 has been updated.

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

[0071] Next, the facial feature amount synchronization client 214 of the first face authentication device 21 stores the facial feature amount of the face ID "XXX" transmitted from the face registration server 30 in the facial feature amount database 215. Then, the facial feature amount synchronization client 214 returns a response to the face registration server 30 indicating that synchronization of the facial feature amount of the face ID "XXX" has been completed (S6).

[0072] Next, the facial feature amount synchronization management unit 360 of the face registration server 30 updates the synchronization target list 700 (S7). Here, the facial feature amount synchronization management unit 360 changes the synchronization status of the 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 facial feature amount synchronization management unit 360 of the face registration server 30 returns a response to the first face authentication device 21 regarding the completion of synchronization (S8).

[0074] Similarly, the facial feature amount synchronization client 214 of the second face authentication device 22 executes synchronization acquisition with the face registration server 30 (S9). Next, the facial feature amount synchronization management unit 360 of the face registration server 30 transmits the facial feature amount of the face ID "XXX" to the second face authentication device 22 in response to the synchronization acquisition command from the second face authentication device 22 (S10).

[0075] Next, the facial feature synchronization client 214 of the second face authentication device 22 stores the facial features of the face ID "XXX" transmitted from the face registration server 30 in the facial feature database 215, and sends a reply to the face registration server 30 notifying that synchronization of the facial features of the face ID "XXX" has been completed (S11).

[0076] Next, the facial feature amount synchronization management unit 360 of the face registration server 30 updates the synchronization target list 700 (S12). Here, the facial feature amount 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.”

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

[0078] Next, since synchronization of face registration for the first face authentication device 21 and the second face authentication device 22 is completed, the face feature amount 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 processor 310 of the face registration server 30 notifies the mobile terminal 40 of the result of the user's face registration application, i.e., that face registration has been completed successfully (S15). Since the registration of the user's face information has been completed successfully, the face registration screen of the mobile terminal 40 displays "Registered".

[0080] As shown in FIG. 6, when the face registration process is performed normally, the face registration server 30 creates a synchronization target list when face registration is requested, and when synchronization of the target face recognition device is completed, the target is deleted from the synchronization target list.

[0081] In addition, after the facial feature amount synchronization management unit 360 of the face registration server 30 creates the synchronization target list 700 (step S3), the facial feature amount of the face ID "XXX" may be transmitted to the first face authentication device 21, so that the synchronization acquisition process of step S4 may be omitted. Step S9 may also be omitted.

[0082] [Face registration process (if failed)] Next, the face registration process (failure) by the face authentication registration system 50 will be described with reference to FIG. Fig. 8 is a sequence chart showing an example of face registration processing (failure) by the face authentication registration system 50. The example shown in Fig. 8 is an example in which face registration is successful in the first face authentication device 21 and fails in the second face authentication device 22. In Fig. 8, steps S1 to S10 are the same as the example in Fig. 6.

[0083] After the first face authentication device 21 has successfully registered the face, the processes of steps S9 and S10 are carried out between the second face authentication device 22 and the face registration server 30.

[0084] After the process of step S10, the facial feature amount synchronization client 214 of the second face authentication device 22 executes a process of storing the facial feature amount of the face ID "XXX" transmitted from the face registration server 30 in the facial feature amount database 215. Here, if the registration of the facial feature amount of the face ID "XXX" is not completed normally in the second face authentication device 22 for some reason, the facial feature amount synchronization client 214 cannot return a synchronization completion notice to the face registration server 30 (S11a).

[0085] The facial feature amount synchronization management unit 360 of the face registration server 30 performs a timeout process when no synchronization completion is returned from the second face authentication device 22 even after a predetermined time has elapsed. Then, the facial feature amount synchronization management unit 360 updates the synchronization target list (S12a).

[0086] 9 shows an example of a synchronization target list 900 created by the facial feature amount synchronization management unit 360 during face registration processing (in the case of failure). Here, the facial feature amount 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 facial feature amount synchronization management unit 360 of the face registration server 30 requests the first face authentication device 21 to delete the facial information (facial feature amount) of the face ID "XXX" that has already been successfully registered (S21). Upon receiving the request to delete the facial information of the face ID "XXX", the facial feature amount synchronization client 214 of the first face authentication device 21 deletes the facial feature amount of the face ID "XXX" stored in the facial feature amount database 215, and returns a deletion response to the face registration server 30 (S22).

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

[0089] If face registration fails in any of the multiple target face recognition devices during face registration processing, the face feature synchronization management unit 360 deletes the face information from the face recognition devices that have already succeeded in registration, and sets the state to registration failed (unregistered).

[0090] In addition, the face registration server 30 cannot distinguish whether the face authentication device has failed to receive the synchronous acquisition response and the target facial feature has not been registered, or whether the face authentication device has successfully received the synchronous acquisition response and registered the facial feature, but has failed to transmit the synchronization completion. Therefore, the face registration server 30 also transmits a deletion request to the second face authentication device 22 that caused the registration failure.

[0091] In this way, when the synchronization event of face information is a registration process of face information, the face feature amount synchronization management unit 360 of the face registration server 30 requests the multiple face authentication devices to delete the face information when the registration of the face information fails in any one of the multiple target face authentication devices. Then, the face feature amount synchronization management unit 360 controls the multiple face authentication devices to delete the face information, so that the face information becomes unregistered in the multiple face authentication devices.

[0092] This allows the synchronization state of face information in multiple target face recognition devices to be consistent as "registration failed (not registered)."

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

[0094] Next, since synchronization (deletion) of face information for 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 target (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 face registration has failed as a result of the user's face registration application (S26). Since the user's face registration has failed, the face registration screen of the mobile terminal 40 displays "Not Registered."

[0096] Here, if registration of face information fails in any one of the multiple face recognition devices, the face registration screen processing unit 310 of the face registration server 30 may display a message encouraging 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 fault when any particular face authentication device continues to fail to register face information, and may issue 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 fault (or malfunction) when face registration fails three consecutive times. In this way, by notifying the user that face information cannot be registered, it is possible to avoid unnecessary face registration processing in the face registration server 30, and reduce the processing load on the registration server 30.

[0098] 8 and 9, when synchronization (face registration) fails in any face authentication device, a process is executed to make the synchronization state uniform in the target face authentication devices. This makes it possible to prevent different events from occurring, such as an entrance / exit facility (e.g., a door) linked to a face authentication device where face registration was successful can be unlocked, but an entrance / exit facility (e.g., a door) linked to a face authentication device where face registration was unsuccessful cannot be unlocked.

[0099] [Face removal process (normal)] Next, the face deletion process (normal) by the face authentication registration system 50 will be described with reference to FIG. 10 is a sequence chart showing an example of face deletion processing (normal) by the face authentication registration system 50. The example shown in FIG. 10 is an example in which the face registration server 30 deletes (synchronizes) face information from the first face authentication device 21 and the second face authentication 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 a face registration screen to the mobile terminal 40 via the face registration screen processing unit 310. The user applies for the deletion of his / her own face information via the face registration screen displayed on the display 41 of the mobile terminal 40 (S31). For example, if user information is entered on the face registration screen and face information is registered, face information (face image) of the registered face ID "XXX" is displayed. If there is no mistake in the face image, the user presses a confirmation button (not shown) and proceeds with the face deletion application. Usually, one user registers one piece of face information. However, multiple pieces of face information may be registered for one user.

[0101] At the stage when a request for deletion of facial information is made, the user's facial information is registered in the face registration server 30, so that the face registration screen of the mobile terminal 40 displays "Registered".

[0102] Next, the facial feature amount synchronization management unit 360 of the face registration server 30 accepts the face deletion request from the mobile terminal 40, creates a synchronization target list, and temporarily stores it in the RAM 503 (S32). At this stage, since the deletion of the face information is not yet complete, the face registration screen of the mobile terminal 40 displays "Deleting".

[0103] 11 shows an example of a synchronization target list created by the face feature amount synchronization management unit 360. Here, an example of a synchronization target list 1100 created during face deletion processing (normal case) is shown. The synchronization target list 1100 has fields for "face ID", "device ID", and "synchronization status", just like when a face is registered.

[0104] 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 authentication device 21 and the device ID "2" of the second face authentication device 22. The "synchronization status" field is "waiting for deletion" for both device IDs "1" and "2."

[0105] Returning to Fig. 11, the description will continue. After step S32, the facial feature amount synchronization client 214 of the first face authentication device 21 executes synchronization acquisition with the face registration server 30 (S33). That is, similar to the time of face registration, the facial feature amount synchronization client 214 periodically polls the face registration server 30 to check whether the facial feature amount database 370 has been updated. Note that, in a manner similar to step S4 in Fig. 6, this step S33 (and step S38 described later) may be omitted.

[0106] Next, the facial feature amount 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 facial feature amount of the face ID "XXX" has been deleted from the facial feature amount database 370, the facial feature amount synchronization management unit 360 transmits an instruction to delete the facial feature amount of the face ID "XXX" to the first face authentication device 21.

[0107] Next, the facial feature amount synchronization client 214 of the first face authentication device 21 deletes the facial feature amount of the face ID "XXX" from the facial feature amount database 215 in accordance with the deletion instruction for the facial feature amount of the face ID "XXX" transmitted from the face registration server 30. Then, the facial feature amount synchronization client 214 returns a reply to the face registration server 30 to inform that synchronization of the facial feature amount of the face ID "XXX" has been completed (S35).

[0108] Next, the facial feature amount synchronization management unit 360 of the face registration server 30 updates the synchronization target list 1100 (S36). Here, the facial feature amount 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.”

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

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

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

[0112] Next, the facial feature amount synchronization management unit 360 of the face registration server 30 updates the synchronization target list 1100 (S41). Here, the facial feature amount 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.”

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

[0114] Next, since synchronization of face deletion for the first face authentication device 21 and the second face authentication device 22 is completed, the face feature amount 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 completed successfully (S44). Since the deletion of the user's face information has been completed successfully, the face registration screen of the mobile terminal 40 displays "Not registered."

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

[0117] [Face removal process (if failed)] Next, the face deletion process (failure) by the face authentication registration system 50 will be described with reference to FIG. Fig. 12 is a sequence chart showing an example of face deletion processing (failure) by the face authentication registration system 50. The example shown in Fig. 12 is an example in which face deletion is successful in the first face authentication device 21 and face deletion is unsuccessful in the second face authentication device 22. In Fig. 12, steps S31 to S39 are the same as the example in Fig. 10.

[0118] After the first face authentication device 21 has succeeded in deleting the face, the processes of steps S38 and S39 are carried out between the second face authentication device 22 and the face registration server 30.

[0119] After the process of step S39, the facial feature amount synchronization client 214 of the second face authentication device 22 executes a process of deleting the facial feature amount of face ID "XXX" from the facial feature amount database 215 in accordance with the instruction to delete the facial feature amount of face ID "XXX" transmitted from the face registration server 30. Here, if the deletion of the facial feature amount of face ID "XXX" is not completed normally in the second face authentication device 22 for some reason, the facial feature amount synchronization client 214 cannot return a synchronization completion to the face registration server 30 (S40a).

[0120] The facial feature amount synchronization management unit 360 of the face registration server 30 performs a timeout process when no synchronization completion is returned from the second face authentication device 22 even after a predetermined time has elapsed. Then, the facial feature amount synchronization management unit 360 updates the synchronization target list (S41a).

[0121] 13 shows an example of the synchronization target list 1300 created by the facial feature amount synchronization management unit 360 during face registration processing (in the case of failure). Here, the facial feature amount 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 failed”.

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

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

[0124] If the facial deletion process fails for any one of the multiple target facial recognition devices, the facial feature synchronization management unit 360 restores the facial information of the facial recognition devices that have already succeeded in the deletion, and sets the state to a deletion failure (registered). For example, the facial information once deleted from the facial feature database 215 by the first facial recognition device 21 is temporarily stored in the RAM 503. Alternatively, the data of the facial feature database 215 may be read into the RAM 503, and the data may be written back to the facial feature database 215 after the success or failure of the synchronization (here, the deletion) is confirmed.

[0125] In addition, the face registration server 30 cannot distinguish whether the face authentication device has failed to receive the synchronous acquisition response and the target facial feature has not been deleted, or whether the face authentication device has successfully received the synchronous acquisition response and deleted the facial feature, but has failed to transmit the synchronization completion. Therefore, the face registration server 30 also transmits a registration request to the second face authentication device 22 that caused the deletion failure.

[0126] In this way, when the synchronization event of face information is a process of deleting face information, the face feature amount synchronization management unit 360 of the face registration server 30 requests the registration (restoration) of face information to the multiple face authentication devices when the deletion of face information fails in any one of the multiple target face authentication devices. Then, the face feature amount synchronization management unit 360 controls the multiple face authentication devices to register (restore) the face information, so that the face information is registered in the multiple face authentication devices.

[0127] This makes it possible to align the synchronization status of face information in multiple target face recognition devices to "deletion failed (registered)".

[0128] Next, the facial feature amount synchronization management unit 360 of the face registration server 30 receives the registration response from the first face 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 amount synchronization management unit 360 receives the registration response from the second face authentication device 22, and changes the synchronization status of the device ID "2" in the synchronization target list 1300 from "deletion failed" to "registered."

[0129] Next, since synchronization (registration) of face information for 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 target (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 has failed as a result of the user's face deletion request (S56). Since the user's face deletion has failed, "Deletion failed" is displayed on the face registration screen of the mobile terminal 40.

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

[0132] Furthermore, the face registration screen processing unit 310 of the face registration server 30 may determine that there is a fault when any particular face authentication device continues to fail to delete face information, and may issue a notification to the mobile terminal 40 to prevent the user from deleting the face information. For example, the face registration screen processing unit 310 may determine that there is a fault (or malfunction) when face deletion fails three consecutive times. In this way, by notifying the user that face information cannot be deleted, unnecessary face deletion processing in the face registration server 30 can be avoided, and the processing load of the registration server 30 can be reduced.

[0133] 12 and 13, when synchronization (face deletion) fails in any face authentication device, a process is executed to make the synchronization states of the multiple target face authentication devices consistent. This makes it possible to prevent different events from occurring, such as an entrance / exit facility (e.g., a door) linked to a face authentication device that has successfully deleted a face cannot be unlocked, but an entrance / exit facility (e.g., a door) linked to a face authentication device that has failed to delete a face can be unlocked.

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

[0135] In this embodiment configured as above, when synchronization of face information fails in any face authentication device, a process is executed to make the synchronization state uniform in the target multiple face authentication devices. This makes it possible to prevent different events from occurring, such as authentication being possible for equipment (e.g., doors, elevators) linked to a face authentication device with which synchronization of face information has been successful, but authentication being impossible for equipment (e.g., doors, elevators) linked to a face authentication device with which synchronization of face information has failed. Therefore, this embodiment makes it possible to prevent inconvenience and confusion for the user.

[0136] The present invention is not limited to the above-described embodiment, and various other applications and modifications are possible without departing from the gist of the present invention described in the claims. For example, the above-described embodiment is a detailed and specific description of the configuration in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to a configuration having all of the components described. In addition, it is also possible to add, replace, or delete other components to a part of the configuration of the above-described embodiment.

[0137] In addition, the above-mentioned configurations, functions, processing units, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. As the hardware, a broad processor device such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit) may be used. In addition, a cloud environment may be used to store facial features, user information, device information, etc.

[0138] In addition, each component (functional block) of each device constituting the face authentication registration system according to the above-mentioned embodiment may be implemented in any hardware as long as each hardware can transmit and receive information to each other via a network. In addition, the process performed by a certain processing unit may be realized by a single piece of hardware, or may be realized by distributed processing by multiple pieces of hardware.

[0139] In the above-described embodiment, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it may be considered that almost all components are connected to each other. [Explanation of symbols]

[0140] 21...first face authentication device, 22...second face authentication device, 23...third face authentication device, 30...face registration server, 40...mobile terminal, 50...face authentication registration system, 60...entrance / exit system, 70...elevator control panel, 211...camera image acquisition unit, 212...face authentication unit, 213...device linkage unit, 214...face feature amount synchronization client, 215...face feature amount 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 amount synchronization management unit, 370...face feature amount database, 700...synchronization target list, 900...synchronization target list, 1100...synchronization target list, 1300...synchronization target list

Claims

1. A face authentication registration system including a face registration server that stores face information, and a plurality of face authentication devices that register the face information and use it for face authentication, When the face registration server receives a face information synchronization event, it executes a synchronization process of the face information for the plurality of target face authentication devices, and if the synchronization of any one of the plurality of face authentication devices fails, it controls the plurality of face authentication devices to return to a state before the synchronization process. Face recognition registration system.

2. When the synchronization event of the face information is a registration process of the face information, the face registration server, when the registration of the face information fails in any one of the plurality of target face authentication devices, requests the plurality of face authentication devices to delete the face information, and controls so that the face information is unregistered in the plurality of face authentication devices. The face recognition and registration system according to claim 1 .

3. When the face registration server fails to register the face information in any one of the face authentication devices, the face registration server displays a message on the terminal used by the user to register the face information, prompting the user to re-register the face information. The face recognition and registration system according to claim 2 .

4. The face registration server notifies the terminal not to register the face information if the face authentication device continues to fail to register the face information. The face recognition and registration system according to claim 3 .

5. When the synchronization event of the face information is a process of deleting the face information, if the face registration server fails to delete the face information in any one of the plurality of target face authentication devices, the face registration server requests the plurality of face authentication devices to register the face information, and controls so that the face information is registered in the plurality of face authentication devices. The face recognition and registration system according to claim 1 .

6. When the face registration server fails to delete the face information from any of the plurality of face authentication devices, the face registration server displays a message on the terminal used by the user to delete the face information, prompting the user to delete the face information again. The face recognition and registration system according to claim 5 .

7. If the face authentication device continues to fail to delete the face information, the face registration server issues a notification to the terminal not to delete the face information. The face recognition and registration system according to claim 6.

8. A face authentication system for performing face authentication using face information stored in a face registration server, comprising: The face authentication devices synchronize the face information stored in the face registration server, and if the synchronization of the face information fails, return the face information to a state before the synchronization in accordance with a command transmitted from the face registration server. Facial recognition device.

9. A face authentication registration method using a face authentication registration system including a face registration server that stores face information and a plurality of face authentication devices that register the face information and use it for face authentication, a process of performing a synchronization process of the face information on the plurality of target face authentication devices when a synchronization event of the face information is received in the face registration server; If synchronization fails for any one of the plurality of face authentication devices, the face registration server controls the plurality of face authentication devices to return to a state before the synchronization process. How to register face recognition.

Images