JP7380934B2 - Elevator system, mobile terminal, program, and control method for mobile terminal - Google Patents

Description

The present invention relates to an elevator system, a mobile terminal, a program, and a method of controlling a mobile terminal.

Patent Document 1 discloses an elevator in which a card reader at a security gate acquires user information from an IC card, automatically registers the user's destination floor recorded in advance on the IC card in an elevator control device, and assigns a car number. The system is disclosed.

Japanese Patent Application Publication No. 2016-056017

Various devices using face recognition are beginning to become popular.

An object of the present invention is to improve user convenience in relation to an elevator system using face authentication.

The elevator system of the first aspect of the present invention includes:
An elevator system that sets a destination floor of a user before the user gets on the elevator,
an imaging unit provided to be able to image a user attempting to pass through a gate disposed on a travel route to an elevator landing;
a face authentication unit that performs face authentication of the user based on a captured image captured by the imaging unit;
an information acquisition unit that acquires destination floor change information regarding the user's changed destination floor;
a destination floor setting unit for setting the destination floor of the user;
The destination floor setting section is
If the face authentication unit successfully authenticates the user's face, but the information acquisition unit does not acquire the destination floor change information, the default destination floor specified based on the face authentication is transferred to the user. set as the destination floor of
When the face authentication of the user is successful in the face authentication unit and the information acquisition unit acquires the destination floor change information, the changed destination floor specified based on the destination floor change information is Set as the user's destination floor,
The information acquisition unit includes a first information acquisition unit that acquires the destination floor change information in a first format corresponding to the building, or a second information acquisition unit that acquires the destination floor change information in a second format that corresponds to the building. It has at least one of the following parts.

The elevator system of the second aspect of the present invention includes:
An elevator system that sets a destination floor of a user before the user gets on the elevator,
an imaging unit provided to be able to image a user attempting to use a destination floor registration device disposed in an elevator landing;
a face authentication unit that performs face authentication of the user based on a captured image captured by the imaging unit;
an information acquisition unit that acquires destination floor change information regarding the user's changed destination floor;
a destination floor setting unit for setting the destination floor of the user;
The destination floor setting section is
If the face authentication unit successfully authenticates the user's face, but the information acquisition unit does not acquire the destination floor change information, the default destination floor specified based on the face authentication is transferred to the user. set as the destination floor of
When the face authentication of the user is successful in the face authentication unit and the information acquisition unit acquires the destination floor change information, the changed destination floor specified based on the destination floor change information is Set as the user's destination floor,
The information acquisition unit includes a first information acquisition unit that acquires the destination floor change information in a first format corresponding to the building, or a second information acquisition unit that acquires the destination floor change information in a second format that corresponds to the building. It has at least one of the following parts.

The mobile terminal of the present invention includes:
a display section that displays an image;
an imaging unit;
comprising a control unit;
The control unit includes:
(i) causing the imaging unit to image the user's face;
(ii) obtaining information on available buildings, permitted floors, and destination floor change formats based on the face data captured by the imaging unit;
(iii) When the user attempts to use a changed destination floor different from the default destination floor when passing through the facial recognition system of the building, the destination floor includes information on the changed destination floor on the display section. The change code is displayed in the destination floor change format corresponding to the building.

The program of the present invention causes a computer to function as a control unit of the mobile terminal of the present invention.

The mobile terminal control method of the present invention includes:
A method for controlling a mobile terminal including a display unit that displays an image and an imaging unit, the method comprising:
(i) causing the imaging unit to image the user's face;
(ii) obtaining information on available buildings, permitted floors, and destination floor change formats based on the face data captured by the imaging unit;
(iii) When the user attempts to use a changed destination floor different from the default destination floor when passing through the facial recognition system of the building, the destination floor includes information on the changed destination floor on the display section. The change code is displayed in the destination floor change format corresponding to the building.

According to the present invention, in an elevator system using facial recognition, not only a default destination floor but also a changed destination floor can be set as the user's destination floor, and it can be used in multiple buildings, increasing the convenience of the user. can be improved.

Block diagram showing the configuration of an elevator system in Embodiment 1 A schematic plan view showing the equipment arrangement on a specific floor of a building to which the building elevator system in Embodiment 1 is applied. Block diagram showing the configuration of a building elevator system Block diagram showing the electrical configuration of the destination floor registration device Front view schematically showing the appearance of the destination floor registration device Diagram showing an example of display on the display unit of the destination floor registration device Block diagram showing the electrical configuration of the elevator control device Perspective view showing the appearance of the security gate Block diagram showing the electrical configuration of the security server Diagram showing the configuration of the registered device database stored in the storage unit of the security server Diagram showing the structure of the building user database (Building A) stored in the storage unit of the security server Diagram showing the configuration of the user database (Building B) stored in the storage unit of the security server Block diagram showing the electrical configuration of a mobile terminal Diagram showing an example of display on the display of a mobile terminal Diagram showing the configuration of the app user database stored in the storage unit of the app server Diagram showing upload from building user database to app user database Flowchart explaining the process of the destination floor setting application when registering the destination floor setting application for the first time Diagram showing an example of the display on the display of a mobile terminal when registering the destination floor setting application for the first time Flowchart explaining the processing of the application server when registering the destination floor setting application for the first time Diagram showing the addition of an app user ID in the app user database Flowchart explaining the security server processing when registering the destination floor setting app for the first time Diagram showing addition of application user ID in building user database Flowchart explaining the process of the destination floor setting application when using the building Diagram showing an example of the display of the destination floor setting application when using a building Diagram showing an example of the display of the destination floor setting application when using a building Flowchart illustrating call information signal generation processing by the security server of Building A Flowchart illustrating call information signal generation processing by the security server of Building B Flowchart explaining assignment processing by the group management control device Diagram showing an example of display on the gate display of a security gate Block diagram showing the configuration of an elevator system in a first modification of the first embodiment Block diagram showing the configuration of the elevator system (building A) in a second modification of the first embodiment Block diagram showing the configuration of the elevator system (building B) in the second modification of the first embodiment

Embodiments of the present invention will be described with reference to the drawings.

(Embodiment 1)
1. Configuration 1-1. Elevator System FIG. 1A is a block diagram showing the configuration of an elevator system in the first embodiment.

As shown in FIG. 1A, the elevator system of Embodiment 1 includes a plurality of building elevator systems and an application server 500.

A building elevator system is a system constructed to control elevators in each building. In the example shown in FIG. 1A, three buildings A, B, and C are illustrated, and a building elevator system is constructed in each of buildings A to C. Each of the building elevator systems includes a group management control device 10 and a security server 100. Each of the building elevator systems is communicably connected to a user's mobile terminal 200 and an application server 500.

A face recognition system is installed in each of Buildings A to C, and the user is authenticated based on the captured image of the user's face. If the authentication is successful, the group management control device 10 recognizes the user's face. Assign destination floor. In principle, a default destination floor is assigned as the user's destination floor, but by using a destination floor setting application installed on the mobile terminal 200, a destination floor different from the default destination floor (changed destination floor) can be used. . Information regarding the destination floor setting application is managed by the application server 500.

An exemplary configuration of a building elevator system installed in each building will be described below.

1-2. Arrangement of Elevators, etc. FIG. 1B is a schematic plan view showing an example of equipment arrangement on a specific floor of a building (building) to which the building elevator system according to the first embodiment is applied. The specific floor is, for example, a lobby floor connected to the outside of the building, and users of the building move to other floors via the specific floor.

FIG. 1B shows an example in which the building elevator system includes six elevators 60A to 60F (an example of a plurality of elevators), No. 1 to No. 6. Elevator users board the elevators 60A to 60F from the elevator hall. In the following, the elevators 60A to 60F may be referred to as "elevators 60" without distinction.

A destination floor registration device 30 is arranged at or near the elevator landing of each floor including a specific floor.

On a specific floor, a plurality of security gates 20 are arranged on the user's movement route from the entrance to the elevator hall. A user passes through one of the security gates 20 from the entrance side and enters the elevator hall. The elevator hall is provided in a specific area. The specific area is an area within the building that cannot be entered without passing through the security gate 20 from the entrance side. The specific area includes an elevator landing, a space inside each elevator 60, and a space on each floor that can be moved using the elevator 60.

On the floor on the entrance side of the security gate 20, there is a display indicating a face authentication area Ad.

1-3. System configuration 1-3-1. Overview FIG. 2 is a block diagram showing an example of the system configuration of a building elevator system.

The building elevator system includes a plurality of elevators 60A to 60F, a group management control device 10 that integrally controls the operation of these elevators 60A to 60F, and elevator control devices 40A to 40F provided corresponding to each elevator. and a destination floor registration device 30 arranged on each floor. A security server 100 that manages the security of the building and controls the security gate 20 is connected to the group management control device 10 .

Building elevator systems employ a destination floor registration method in which users are required to register their destination floor in advance before boarding the car. The destination floor is registered by, for example, facial recognition at the security gate 20, use of a destination floor change code such as a Chameleon code (registered trademark) or QR code (registered trademark), manual registration at the destination floor registration device 30, etc. be able to. The group management control device 10 assigns a call related to the destination floor registered before boarding (destination floor call) to one of the plurality of elevators 60, and uses information indicating the assigned elevator to be used. This information is displayed on the gate display 70 of the security gate 20 and the destination floor registration device 30, thereby allowing the user to board the assigned car.

Note that the destination floor registration device 30 for a specific floor is used when a user who has passed through the security gate 20 and entered a specific area misses the elevator 60 displayed on the gate display 70, or when a user who has entered a specific area after passing through the security gate 20 misses the elevator 60 displayed on the gate display 70, The elevator 60 is provided to allow use of the elevator 60 when moving to the floor.

Each elevator 60 (60A to 60F) has a car, a hoist (motor), a counterweight, and the like.

1-3-2. Group Management Control Device The group management control device 10 integrally controls the operation of the elevators 60A to 60F. In addition, the group management control device 10 controls the allocation of new calls to each car while communicating with the security server 100 and the destination floor registration device 30. Each device is connected via a network capable of transmitting information. The network is constituted by, for example, a LAN (Local Area Network) such as Ethernet (registered trademark), and various information is exchanged between devices according to various protocols such as TCP/IP. Each of the above-mentioned devices connected to the network is capable of signal transmission (information transmission) through communication according to various protocols such as TCP/IP. Note that the devices constituting the elevator system may be connected via a network of other signal formats or a dedicated signal network.

The group management control device 10 is configured using a computer, and includes a control section 11, a storage section 12, and an input/output interface 13.

The storage unit 12 is configured using, for example, RAM, ROM, HDD, SSD, etc., and stores programs and various data. The program includes programs for realizing various functions of the group management control device 10 of this embodiment.

The control unit 11 is configured using, for example, a CPU, an MPU, or the like. The control unit 11 implements various functions of the group management control device 10, which will be described later, by performing arithmetic processing using various data based on the program read from the storage unit 12.

The input/output interface 13 is configured using, for example, a LAN adapter. The input/output interface 13 is an interface for the group management control device 10 to transmit and receive various signals between the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40. be. The input/output interface 13 converts the signal output from the control unit 11 into a signal in a predetermined format and outputs the signal to the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40. . In addition, the input/output interface 13 converts signals input from the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control devices 40A to 40F into signals in a predetermined format, and sends the signals to the control unit. Output to 11.

1-3-3. Elevator Control Device Elevator control devices 40A to 40F are provided corresponding to elevators 60A to 60F. The elevator control devices 40A to 40F control the operation of the hoisting machines (motors), etc. of the corresponding elevators 60A to 60F according to control signals from the group management control device 10, thereby raising the cars of the elevators 60A to 60F. , lowering, stopping, etc. In addition, the elevator control devices 40A to 40F detect the car status of the corresponding elevator 60A to 60F, such as the position, running direction, door opening/closing, load, etc., and perform group management control on information indicating the detected car status. Output to the device 10. Note that hereinafter, the elevator control devices 40A to 40F may be referred to as "elevator control device 40" without distinction.

Like the group management control device 10 and the like, the elevator control device 40 is configured using a computer equipped with a control section, a storage section, an input/output interface, and the like.

1-3-4. Destination Floor Registration Device FIG. 3 is a block diagram showing the electrical configuration of the destination floor registration device 30.

The destination floor registration device 30 is a device that accepts registration (designation) of a destination floor by a user. The destination floor registration device 30 includes a control section 31, a storage section 32, an input/output interface 33, a display section 34, and an operation section 35.

The storage unit 32 is configured using, for example, RAM, ROM, HDD, SSD, etc., and stores programs and various data. The program includes programs for realizing various functions of the destination floor registration device 30 of this embodiment.

The control unit 31 is configured using, for example, a CPU, an MPU, or the like. The control unit 31 implements various functions of the destination floor registration device 30, which will be described later, by performing arithmetic processing using various data based on the program read from the storage unit 32.

The input/output interface 33 is configured using, for example, a LAN adapter. The input/output interface 33 is an interface through which the destination floor registration device 30 transmits and receives various signals to and from the group management control device 10. The input/output interface 33 converts the signal output from the control unit 31 into a signal in a predetermined format and outputs the signal to the group management control device 10. Further, the input/output interface 33 converts a signal input from the group management control device 10 into a signal in a predetermined format and outputs the signal to the control unit 31.

The display unit 34 displays images and the like based on display signals output from the control unit 31.

The operation unit 35 is an interface that accepts user operations on the destination floor registration device 30. The operation section 35 outputs a signal according to the operation content to the control section 31.

The display unit 34 and the operation unit 35 are integrally configured by a touch panel display device using, for example, a liquid crystal display panel or an organic EL display panel. Note that the display section 34 and the operation section 35 may be configured separately using different parts, as long as it is possible to specify the same as an object such as a button displayed on the display section 34. .

FIG. 4 is a front view schematically showing the appearance of the destination floor registration device 30. FIG. 5 is a diagram showing a display example on the display unit 34 of the destination floor registration device 30.

A face authentication camera 36 is disposed above the destination floor registration device 30, and is configured to allow the user to perform facial authentication when registering the destination floor.

The face authentication camera 36 images a subject in a predetermined field of view in front of it at a predetermined frame rate and a predetermined resolution, generates image data of the captured image (captured image), and sends the generated image data to the security server. Output to 100. The face authentication camera 36 is an example of an imaging unit. The predetermined viewing angle area is set to an angle of view that allows the user's face to be imaged when the user is in front of the destination floor registration device 30. The predetermined resolution may be any resolution as long as it can appropriately perform face detection and face matching during face authentication, and may be, for example, HD, FHD, 4K, or the like. The frame rate may be any rate, and may be, for example, 15 fps or 30 fps.

FIG. 4 shows an example in which a guidance screen as a default screen is displayed on the display unit 34 of the destination floor registration device 30. On this guidance screen, for example, a message is displayed saying, "Use is possible with face recognition. Please perform face recognition with the camera above." When the user comes in front of the face authentication camera 36 while the guide screen of FIG. Authentication processing is performed. If face authentication is successful, an operation screen as shown in FIG. 5(a) is displayed on the display unit 34, for example. On the operation screen shown in Figure 5(a), the message "Please register the destination floor" is displayed, along with the destination floor button of the permitted floor associated with the user database (described later) for the user whose face authentication was successful. Here is an example where is displayed. On the operation screen in Figure 5(a), destination floor buttons for the 9th, 10th, and 11th floors, which are permitted floors linked to the user ID "10004" registered in the user database, are displayed. Here is an example. Note that the permitted floor is a floor that the user is permitted to use, and the floor differs depending on the user whose face authentication was successful. When a user presses (touches) one of the destination floor buttons on the operation screen in FIG. 5(a), elevator assignment is performed, and an assigned car number notification as shown in FIG. 5(b) is made. The screen will be displayed. The assigned car number notification screen in FIG. 5(b) shows an example in which a message "10F No. 1 car" is displayed.

In the example shown in FIG. 4, the destination floor registration device 30 is provided with a QR code reader 129. The QR code reader 129 may be installed in a building (for example, building B) that supports the format of destination floor change using a QR code, and is indicated by a dotted line in the drawing.

1-3-5. Security Gate The security gate 20 is a device that controls entry of users into a specific area inside the building. Specifically, the security gate 20 is a device that allows authorized users to enter a specific area inside the building, while restricting entry of unauthorized users. A regular user is a user who is registered in a user database (hereinafter referred to as "user DB"), and an unauthorized user is a user who is not registered in the user DB.

FIG. 6 is a block diagram showing the electrical configuration of the security gate 20 in the first embodiment. FIG. 7 is a perspective view showing the appearance of the security gate 20. Note that FIG. 7 is a perspective view of the leftmost security gate 20 among the three security gates 20 in FIG.

As shown in FIG. 7, the gate main body 20a, which is the housing of the security gate 20, includes a QR code reader 29, a first sensor 26, a second sensor 27, a gate flapper 28, and a gate display 70. It is equipped. Further, a face authentication camera 25 is provided on the exit 20e side of the gate main body 20a. The face authentication camera 25 may be attached to the gate main body 20a, or may be provided independently.

The face authentication camera 25 images a subject in a predetermined field of view in front of it at a predetermined frame rate and a predetermined resolution, generates image data of the captured image (captured image), and outputs it to the security server 100. The face authentication camera 25 is an example of an imaging unit. The predetermined viewing angle area is not only the user's face but also the side of the user's face and body raised toward the face authentication camera 25 when the user is in the face authentication area Ad (see Figure 1). The angle of view is set to be such that the screen of the display unit 210 of the mobile terminal 200 can be imaged. The predetermined resolution may be any resolution as long as it can appropriately perform face detection and face matching during face authentication, and can also detect and analyze chameleon codes. For example, it may be HD, FHD, etc. , 4K, and other resolutions. The frame rate may be any rate, and may be, for example, 15 fps or 30 fps.

The face authentication camera 25 can be used, for example, to go to a destination floor (changed destination floor) different from the default destination floor in a building that supports the destination floor change format using a chameleon code (for example, building A). The user uses the destination floor change application on the mobile terminal 200 to display a chameleon code (destination floor change code) related to the changed destination floor on the display section and have the facial recognition camera 25 read it, thereby allowing the group management control device to 10 assigns the change destination floor. The face authentication camera 25 is an example of an information acquisition unit that acquires a destination floor change code (destination floor change information) regarding a changed destination floor.

The QR code reader 29 is arranged on the upper surface of the gate body 20a on the entrance 20i side. The QR code reader 29 includes an optical reader (scanner or camera) and a data output section. The optical reader optically reads a QR code held up by a user at a position closer than a predetermined distance. The data output unit sends a signal including the image data of the QR code read by the optical reader (hereinafter referred to as "QR code data") and the registered device ID (registered device identification information) of the QR code reader 29 to the security server. Send to 100. Note that the read QR code is displayed on the display section of the mobile terminal 200.

The QR code reader 29 can be used to go to a changed destination floor different from the default destination floor in a building (for example, building B) that supports the destination floor change format using a QR code. The user uses the destination floor change app on the mobile terminal 200 to display a QR code (destination floor change code) related to the changed destination floor on the display section, and causes the QR code reader 29 to read it. assigns a modified destination floor. The QR code reader 29 is an example of an information acquisition unit that acquires a destination floor change code (destination floor change information) regarding a changed destination floor.

The QR code reader 29 is installed in a building (for example, Building B) that supports the format of destination floor change using a QR code. The QR code reader 29 may not be installed in a building (for example, building A) that supports a destination floor changing method in a format different from the QR code (for example, chameleon code). Therefore, the QR code reader 29 is shown by a dotted line in each drawing.

The first sensor 26 is configured, for example, by a photoelectric sensor, and detects a user passing through the entrance 20i side of the passage PA of the security gate 20. When the first sensor 26 detects a user, it outputs a detection signal to the security server 100 via the control unit 21.

The second sensor 27 is configured by, for example, a photoelectric sensor, and detects a user passing through the exit 20e side of the passage PA of the security gate 20. When the second sensor 27 detects a user, it outputs a detection signal to the security server 100 via the control unit 21.

The gate flapper 28 is a door that can be opened and closed.

The gate display 70 displays screens according to various display signals output from the group management control device 10. For example, when the gate display 70 receives the assignment result signal output from the group management control device 10, it displays an assigned car notification screen for notifying the name of the assigned elevator (assigned car).

Furthermore, as shown in FIG. 6, a control section 21, a storage section 22, an input/output interface 23, and the like are housed inside the gate main body 20a.

The storage unit 22 is configured using, for example, RAM, ROM, HDD, SSD, etc., and stores programs and various data. The program includes programs for realizing various functions of the security gate 20 in this embodiment.

The input/output interface 23 is configured using, for example, a LAN adapter. The input/output interface 23 is an interface through which the security gate 20 transmits and receives various signals to and from the security server 100. The input/output interface 23 converts the signal output from the control unit 21 into a signal in a predetermined format and outputs the signal to the security server 100. Further, the input/output interface 23 converts a signal input from the security server 100 into a signal in a predetermined format and outputs the signal to the control unit 21 .

The control unit 21 is configured using, for example, a CPU, an MPU, or the like. The control unit 21 implements various functions of the security gate 20, which will be described later, by performing arithmetic processing using various data based on a program stored in the storage unit 22.

The control unit 21 opens and closes the gate flapper 28 based on detection signals from the first sensor 26 and the second sensor 27 and an open signal and a close signal from the security server 100. Further, when the control unit 21 receives a detection signal from the first sensor 26 and then receives a detection signal from the second sensor 27, it transmits a user passage signal to the security server 100.

1-3-6. Security Server The security server 100 performs face authentication processing for users in order to ensure security within the building, based on captured images represented by image data output from the face authentication camera 25 and the face authentication camera 36. For example, the security server 100 performs face detection processing on the captured image, and if a face is detected, further performs facial feature point detection processing. When facial feature points are detected from the captured image, the data of the detected facial feature points (face data) is sequentially compared with the facial feature point data (face data) of each user registered in the user DB ( ) to find the match rate. Then, it is determined whether face data (facial feature point data) having a matching rate equal to or higher than a predetermined matching rate with respect to the facial data (facial feature point data) of the detected face is registered in the user DB. That is, it is determined whether face data having a match rate equal to or higher than a predetermined match rate with respect to the face data of the detected face is registered in the user DB. If face data with a match rate higher than a predetermined match rate is registered in the user DB, the user (user whose face has been detected) who is about to pass through the security gate 20 will be able to use the registered face data. It identifies the user as the corresponding user and determines that facial recognition was successful. Note that it is preferable that the predetermined matching rate be set to a high matching rate that would not be reached in the case of another person. Thereby, face authentication can be performed appropriately. Note that the face detection process, facial feature point detection process, and verification process (authentication process) can be performed using various known methods.

Furthermore, the security server 100 controls opening and closing of the security gate 20 according to the face authentication result. Furthermore, the security server 100 generates a call information signal including information such as the user's destination floor, and outputs it to the group management control device 10. The user ID is an example of user identification information.

FIG. 8 is a block diagram showing the electrical configuration of the security server 100. The security server 100 is configured using a computer, and includes a control section 101, a storage section 102, and an input/output interface 103.

The storage unit 102 is configured using, for example, RAM, ROM, HDD, SSD, etc., and stores programs and various data. The programs include programs for realizing various functions of the security server 100 of this embodiment, which will be described later. The storage unit 102 stores a user DB as data. The configuration of the user DB will be described later.

The storage unit 102 also stores a registered device database (hereinafter referred to as “registered device DB”) as data. The configuration of the registered device DB will be described later.

The control unit 101 is configured using, for example, a CPU, an MPU, or the like. The control unit 101 implements various functions of the security server 100, which will be described later, by performing arithmetic processing using various data based on a program read from the storage unit 102.

The input/output interface 103 is configured using, for example, a LAN adapter. The input/output interface 103 is an interface through which the security server 100 transmits and receives various signals to and from the face authentication camera 25, the QR code reader 29, the group management control device 10, and the security gate 20. The input/output interface 103 converts the signal output from the control unit 101 into a signal in a predetermined format and connects the face authentication camera 25, QR code reader 29, face authentication camera 36, group management control device 10, and security gate. Output to 20. The input/output interface 103 also converts signals input from the face authentication camera 25, QR code reader 29, face authentication camera 36, group management control device 10, and security gate 20 into signals in a predetermined format. It is output to the control section 101.

FIG. 9 is a diagram showing the configuration of the registered device DB stored in the storage unit 102 of the security server 100. The registered device DB stores information on the installation floor of the registered device and the location where the registered device is installed in association with the registered device ID. The registration device here is a general term for the destination floor registration device 30 and the security gate 20 that are used to register the user's destination floor.

“Installation floor” is information indicating the floor where the registration device corresponding to the registration device ID is installed. The installation floor is used as the departure floor for users using the registration device. In the "call information signal" described later, the "installation floor" will be referred to as the "departure floor."

“Location” is information indicating the position where the registered device corresponding to the registered device ID is installed within the installation floor. The location is indicated by a serial number such as "1", "2", "3", etc., for each installation floor.

In the example shown in FIG. 9, "1" and "1" are registered as the installation floor and location in association with the registered device ID "0001". “1” and “2” are registered as the installation floor and location in association with the registered device ID “0002”. Similarly, for the remaining registered device IDs, information on the installation floor and location is registered in association with the registered device ID.

FIGS. 10A and 10B are diagrams each showing the configuration of a user DB (building user DB) stored in the storage unit 102 of the security server 100. 10A shows the building user DB stored in the storage unit 102 of the security server 100 of building A, and FIG. 10B shows the building user DB stored in the storage unit 102 of the security server 100 of building B. show. The building user DB records face data, default destination floors, permitted floors, and application user IDs in association with building user IDs. Note that a password may be further recorded in association with the building user ID. For example, facial data, default destination floors, and permitted floors are registered in the user DB by the building manager of each building, and application user IDs are automatically registered in the information sent from the application server 500. be exposed.

“Building user ID” is identification information (an example of user identification information) set to uniquely identify a building user. The "building user ID" is information that is uniquely set for each building, and different values are registered for the building user ID shown in FIG. 10A and the building user ID shown in FIG. 10B.

"Face data" is facial feature point data indicating the facial features of the user identified by the "building user ID." The facial feature point data is, for example, data indicating the position and shape characteristics of eyes, nose, mouth, and the like. The facial feature point data is generated based on the user's facial image provided or captured when the user is registered in the user DB.

The "default destination floor" is information indicating the default destination floor of the user identified by the "building user ID." As the default destination floor, for example, the numerical value of the floor where the user is occupying is set. Note that the "default destination floor" may not be set according to the user's wishes. In this case, the symbol "-" is set as the default destination floor. The symbol "-" is an example of destination floor unset information.

The "permitted floor" is information indicating a floor that the user specified by the "building user ID" is permitted to use. For example, a common floor within a building is set as the permitted floor.

The “application user ID” is identification information (an example of user identification information) set to uniquely identify a user of the destination floor setting application in the mobile terminal 200. The application user ID is transmitted from the application server 500 to the security server 100 when a predetermined registration operation in the destination floor setting application is completed. The app user ID is set for each destination floor setting app used by the user, and as shown in FIGS. 10A and 10B, a common app user ID is registered in multiple buildings A and B (for example, "80001"). ). For users whose application user IDs have not been sent and registered from the application server 500 (unregistered users), a symbol "-" is set as the application user ID.

In the example shown in FIG. 10A, regarding the user of building A, "face data 1" and "10" are linked to the building user ID "10001", and the face data, default destination floor, permitted floor, and application user ID are set as "face data 1" and "10". , "9, 10, 11", and "80001" are registered. “Face data 2”, “8”, “7,8”, and “80002” are registered as face data, default destination floor, permitted floor, and application user ID in association with building user ID “10002”. There is. “Face data 3”, “13”, “12,13”, and “-” are registered as face data, default destination floor, permitted floor, and application user ID in association with building user ID “10003”. There is. The symbol "-" in the application user ID is application user ID unset information indicating that the application user ID is not set. “Face data 4”, “-”, “9, 10, 11”, and “80004” are registered as face data, default destination floor, and permitted floor in association with building user ID “10004”. . The symbol "-" in the default destination floor is destination floor unset information indicating that the default destination floor has not been set. Similarly, for the remaining user IDs, face data, default destination floor, permitted floor, and application user ID information are registered in association with the user ID.

In the example shown in FIG. 10B, for the user of building B, "face data 1" and "20" are linked to the building user ID "101", and the face data, default destination floor, permitted floor, and application user ID are set as "face data 1" and "20". , "10, 20", and "80001" are registered. “Face data 10”, “17”, “10,17”, and “80010” are registered as face data, default destination floor, permitted floor, and application user ID in association with building user ID “102”. There is.

In the example shown in FIGS. 10A and 10B, a user is assigned a building user ID "10001" in the user DB of building A, and a user is assigned a building user ID "101" in the user DB of building B. The users who are the same are the same people (displayed in shading). Regarding the user, the face data is "face data 1" in common, the application user ID is "80001" in common, but the building user IDs are "10001" and "101", which are different. Even if the person is the same person, if different images are registered when building A is registered and when building B is registered, different face data may be registered to the extent that the person is recognized as the same person.

1-3-7. Mobile Terminal The mobile terminal 200 includes a computer including a control section, a storage section, a communication interface, a display section, an operation section, and the like. The mobile terminal 200 is, for example, a smartphone or a tablet computer. A destination floor setting application is installed in the storage section of the mobile terminal 200. The destination floor setting app allows users to change the destination floor using chameleon codes, QR codes, one-dimensional barcodes, etc. when registering a destination floor other than the default destination floor (changed destination floor) in the elevator system when using an elevator. Used to generate code (destination floor change information).

FIG. 10C is a block diagram showing the electrical configuration of the mobile terminal 200.

The mobile terminal 200 includes a control section 201, a storage section 202, a camera 203, a display section 210, an operation section 205, and a wireless communication section 206.

The control unit 201 is configured using, for example, a CPU, an MPU, or the like. The control unit 201 reads programs and various data from the storage unit 202 and performs various calculation processes based on the read programs and the like, thereby realizing various functions of the mobile terminal 200, which will be described later.

The storage unit 202 is configured using, for example, RAM, ROM, HDD, SSD, or the like. The storage unit 202 stores programs and various data. The program includes an OS and an application program for call registration (hereinafter referred to as a "call registration application" as appropriate).

When the camera 203 receives the imaging instruction signal from the control unit 201 , the camera 203 images the subject, generates imaging data, and outputs the generated imaging data to the control unit 201 . Camera 203 is an example of an imaging unit.

The display unit 210 performs display based on the display signal output from the control unit 201. Display section 210 is an example of a notification section.

The operation unit 205 is an interface for a user to operate the mobile terminal 200. The operation unit 205 outputs a signal corresponding to the operation content of the operation unit 205 to the control unit 201.

The display unit 210 and the operation unit 205 are integrally configured by a touch panel display device in which a touch sensor is arranged on a liquid crystal display panel or an organic EL display panel, for example.

The wireless communication unit 206 performs wireless communication based on various standards for wireless communication. For example, wireless communication based on various standards of wireless LAN communication such as Wi-Fi (registered trademark) and portable wireless communication such as 4G (Fourth Generation) and 5G (Fifth Generation) is performed.

The control unit 201 can acquire various information such as elevator management information stored in the two-dimensional code by performing predetermined processing on the image data output from the camera 203.

FIG. 11 is a diagram showing a display example on the display unit 210 of the mobile terminal 200.

When the user starts the destination floor setting application on the mobile terminal 200, the destination floor setting screen shown in FIG. 11(a) is displayed on the display unit 210 of the mobile terminal 200. A plurality of building selection buttons 212 are displayed on the destination floor setting screen shown in FIG. 11(a). The building selection button 212 allows the user of the mobile terminal 200 to select an available building. In FIG. 11A, a building selection button 212 for selecting building A and a building selection button 212 for selecting building B are displayed. When any building selection button 212 is pressed, a destination floor setting screen shown in FIG. 11(b) is displayed. A plurality of floor number selection buttons 214 are displayed on the destination floor setting screen shown in FIG. 11(b). The floor selection button 214 allows the user of the mobile terminal 200 to select a permitted floor available in the building selected using the building selection button 212. In FIG. 11(b), a floor selection button 214 for selecting the 9th floor, a floor selection button 214 for selecting the 10th floor, and a floor selection button 214 for selecting the 11th floor are displayed. When any of the floor number selection buttons 214 is pressed, the destination floor setting screen shown in FIG. 11(c), the destination floor setting screen shown in FIG. 11(d), etc. are displayed depending on the destination floor change format of each building. Is displayed.

A chameleon code display screen displaying a chameleon code Cd is displayed on the destination floor setting screen shown in FIG. 11(c). A QR code display screen displaying a QR code Qd is displayed on the destination floor setting screen shown in FIG. 11(d). Each of the chameleon code Cd and the QR code Qd includes information indicating the building selected with the building selection button 212, information indicating the destination floor selected with the floor selection button 214, and a user ID stored in the storage unit. (for example, an application user ID) is stored. Chameleon codes and QR codes are examples of destination floor change codes. If the building corresponding to the chameleon code (e.g. Building A) is selected, the destination floor setting screen shown in Figure 11(c) will be displayed, and if the building corresponding to the QR code (e.g. Building B) is selected, the destination floor setting screen will be displayed. , the destination floor setting screen shown in FIG. 11(d) is displayed. Not limited to the display screens shown in FIGS. 11(c) and 11(d), if a building corresponding to a destination floor change code (for example, a one-dimensional barcode) different from a chameleon code or QR code is selected, the corresponding The destination floor change code will be displayed.

If the user wishes to register a destination floor other than the default destination floor (changed destination floor) in the building elevator system in building A, the user displays the chameleon code display screen on the display unit 210 of the mobile terminal 200, and displays the displayed chameleon code. Pass through the security gate 20 with the screen facing the face authentication camera 25. In addition, if you want to register a destination floor other than the default destination floor (changed destination floor) in the building elevator system in building B, display a QR code display screen on the display unit 210 of the mobile terminal 200, and display the displayed QR code display screen. The user passes through the security gate 20 by having the QR code Qd read by the code reader 29.

On the other hand, if the user wishes to register the default destination floor in the elevator system, the user passes through the security gate 20 as usual without using the mobile terminal 200. Note that in order to pass through the security gate 20, facial authentication must be successful.

1-3-8. Application Server The application server 500 shown in FIG. 1A is a server that manages information regarding the destination floor setting application used in the mobile terminal 200. The application server 500 includes an input/output interface 502, a control section 504, and a storage section 506. The input/output interface 502 is an interface for transmitting and receiving various signals. The control unit 504 processes various data such as data stored in the storage unit 506 and data received via the input/output interface 502. The storage unit 506 stores programs and various data. The storage unit 506 stores a database regarding users of the destination floor setting application (hereinafter referred to as "app user DB") as data.

FIG. 12 is a diagram showing the configuration of a user DB (application user DB) stored in the storage unit 506 of the application server 500. The application user DB records the building ID, building name, default destination floor, permitted floor, destination floor change format, and application user ID in association with the face data.

In the app user DB, "face data", "default destination floor", "permitted floor", and "app user ID" are as shown in FIGS. 10A and 10B. ” and “app user ID”. “Building ID” is identification information set to uniquely identify the building in which face data is registered. "Building name" is data indicating the name of the building in which face data is registered, and corresponds to "building ID." “Destination floor change format” is information indicating a change format for changing the destination floor from the default destination floor, which is adopted in the building where the face data is registered.

In the example shown in FIGS. 10A and 10B, a user (the same person) to whom face data "face data 1" and application user ID "80001" are assigned has a default destination in two buildings, building A and building B. Information is registered so that a change destination floor different from the floor can be used. This is because multiple buildings were registered in the destination floor setting app. Even if they are the same person, the face data may be different to the extent that they are recognized as the same person, and the application user IDs may also be different values.

2. Operation 2-1-1. Data Upload from Security Server to Application Server The data of the application user DB shown in FIG. 12 is constructed by uploading the data of the building user DB shown in FIGS. 10A and 10B. Specifically, each time the information in the building user DB is updated by the operation of the building administrator, the security server 100 communicates with the application server 500 and sends the updated information in the building user DB to the application server 500. Send. The application server 500 uploads the information received from the security server 100 to the application user DB.

FIG. 13 is a schematic diagram showing an example of data upload from the security server 100 to the application server 500.

In the example shown in FIG. 13, in the building user DB of building A, “face data 1” and related data (building user ID “10001”, default destination floor “10”, permitted floors “9, 10, 11 ”) is newly registered, and “face data 2” and data related thereto (building user ID “10002”, default destination floor “8”, permitted floor “7, 8”) are newly registered.

In the building user DB of building B, "face data 1" and related data (building user ID "101", default destination floor "20", permitted floor "10, 20") are newly registered, “Face data 3” and data related thereto (building user ID “102”, default destination floor “17”, permitted floor “10,17”) are newly registered.

The application user ID is information sent later from the application server 500, and is initially registered as "-".

In the example shown in FIG. 13, "face data 1" in the building user DB of building A and "face data 1" in the building user DB of building B are the same person (displayed by shading).

The security server 100 in building A transmits new registration data in the building user DB to the application server 500, and the security server 100 in building B transmits new registration data in the building user DB to the application server 500. The application server 500 stores the data received from each security server 100 in the application user DB.

As shown in FIG. 13, information regarding face data, building ID, building name, default destination floor, permitted floor, and destination floor change format is registered in the application user DB of the application server 500. The face data, default destination floor, and permitted floor are information registered in the building user DB of the security server 100, whereas the building ID, building name, and destination floor change format are information unique to each building. The information is sent to the application server 400 together with the registration information in the building user DB.

The application user ID is information sent from the destination floor setting application in response to a registration operation on the destination floor setting application, and is initially registered as "-".

2-1-2. Registration Operation in Destination Floor Setting Application In order to use a destination floor (changed destination floor) different from the default destination floor, the user installs the destination floor setting application on the mobile terminal 200 and first performs a registration operation.

FIG. 14 is a flowchart regarding the user's registration operation in the destination floor setting application.

The destination floor setting application determines whether or not this is the first time the application is being used (S501). Specifically, when a user launches the destination floor setting app, it is determined whether the user is using the app for the first time or for the second time or later by referring to the past history.

If it is determined that this is the first time use (S501: YES), the destination floor setting application prompts the user to take a picture of the user's face, and saves the taken face image data (S502). Specifically, as shown in FIG. 15A, a message "Please take a picture of your face with a camera" is displayed to prompt the user to take a picture of his/her face. When the user photographs a face, the destination floor setting application saves the photographed facial image data and displays the message ``Save facial image data'' indicating that the facial image data has been saved, as shown in Figure 15(b). "Completed" message and the saved face image Im are displayed.

When step S502 is completed, or if it is determined in step S501 that the application is not used for the first time (NO in S501), the destination floor setting application transmits the face image data and the application user ID to the application server 500 (S503). Specifically, the face image data saved in step S502 and the application user ID are transmitted to the application server 500. The application user ID is identification information that is uniquely generated in association with the saved face image data, and is automatically generated by the destination floor setting application. Unique identification information is assigned to each destination floor setting application so that the application user ID does not overlap with other users.

The destination floor setting application receives available building names, permitted floors, and destination floor change format from the application server 500 (S504). Specifically, based on the face image data sent to the application server 500, face data that is recognized as the same person is identified from the application user DB shown in FIG. 12, and the building name and permission associated with the face data are identified. The floor and destination floor change format are sent from the application server 500 to the destination floor setting application.

The destination floor setting application displays available building names and allows the user to select one (S505). Specifically, as shown in FIG. 15(c), a plurality of building selection buttons 216 are displayed along with a message "Please select a building." In FIG. 15(c), a building selection button 216 for selecting building A, a building selection button 216 for selecting building B, and a building selection button 216 for selecting building C are displayed. By touching the building selection button 216, the user can select each building. FIG. 15(c) exemplifies a state in which building A and building B are selected (displayed by shading), and building C is not selected. Thereafter, as shown in FIG. 15(d), the selected building name is displayed along with the message "The following building has been registered."

The destination floor setting application transmits the selected building name to the application server 500 (S506). Specifically, information including the building name selected in step S505 is transmitted to the application server 500. For example, information such as "Building A" and "Building B" is transmitted to the application server 500 as the selected building names. The application server 500 that has received the information can specify the building name selected by the destination floor setting application.

The destination floor setting application saves the selected building name, permitted floor, and destination floor change type (S507). Specifically, the building name selected in step S505 and the permitted floor and destination floor change format linked to the selected building name from among the data group received in step S504 are saved.

By executing steps S501 to S507, the initial registration operation in the destination floor setting application is completed. This allows the user to change the destination floor using the destination floor setting application.

2-1-3. Application Server Processing Associated with Registration Operation in Destination Floor Setting Application FIG. 16 is a flowchart regarding processing of the application server 500 accompanying registration operation in the destination floor setting application.

The application server 500 determines whether facial image data and application user ID have been received (S511). Unless face image data and application user ID are sent from security server 100, application server 500 determines that it has not received face image data and application user ID (NO in S511), and repeatedly executes the determination process in step S511. do.

In response to the facial image data and application user ID being sent from the security server 100 (step S503 in FIG. 14), the application server 500 determines that the facial image data and application user ID have been received (YES in S511). , searches the application user DB for face image data that matches the received face image data, and obtains information regarding the matched face image data (S512). Specifically, the application user DB shown in FIG. 13 is searched for face data that matches the face image data received in step S511, and the matching face data and information associated with it (building ID, building name, Get the default destination floor, permitted floor, destination floor change format). If there is no matching face image data, the destination floor setting application may be notified of this and the process shown in FIG. 16 may be terminated.

The application server 500 transmits the building name, permitted floor, and destination floor change format to the destination floor setting application (S513). Specifically, among the data acquired in step S512, information regarding the building name, permitted floor, and destination floor change format is transmitted to the destination floor setting application. The destination floor setting application that has received the information can display available building names for the user to select (steps S504 and S505 in FIG. 14).

The application server 500 determines whether the building name has been received (S514). The building name is the building name selected by the user in the destination floor setting application (step S505 in FIG. 14), and unless the building name is sent from the destination floor setting application (step S506 in FIG. 14), the building name is not received. It is determined that this has not been done (NO in S514), and the determination process of step S514 is repeatedly executed.

In response to the building name being sent from the destination floor setting application (S506 in FIG. 14), the application server 500 determines that the building name has been received (YES in S514), and stores the application user ID in the application user DB. Register (S515). Specifically, the application user ID received in step S511 is registered in the application user DB in association with the building name received in step S514.

FIG. 17 is a diagram showing addition and registration of an application user ID in the application user DB. In the example shown in FIG. 17, an application user ID "80001" is newly registered in association with "face data 1" and "building A", and an application user ID "80001" is newly registered in association with "face data 1" and "building B". User ID "80001" is newly registered.

The application server 500 transmits the face image data and the application user ID to the security server 100 of the received building name (S516). Specifically, the face image data (“face data 1”) received in step S511 and the application user ID (“80001”) are combined with the building names (“Building A”, “Building B”) received in step S514. security server 100 respectively.

2-1-4. Security Server Processing Associated with Registration Operation in Destination Floor Setting Application FIG. 18 is a flowchart regarding processing of the security server 100 accompanying registration operation in the destination floor setting application.

The security server 100 of each building determines whether or not the facial image data and application user ID have been received (S521). Unless the facial image data and app user ID are sent from the app server 500, the security server 100 determines that the facial image data and app user ID have not been received (NO in S521), and repeatedly executes the determination process in step S521. do.

In response to the facial image data and app user ID being sent from the app server 500 (S516 in FIG. 16), the security server 100 determines that the facial image data and app user ID have been received (YES in S521), and The building user DB is searched for face image data that matches the received face image data, and the application user ID is added in association with the matching face image data (S522).

FIG. 19 is a diagram showing addition and registration of an application user ID in the building user DB. In the example shown in FIG. 19, the application user ID "80001" is added (displayed in shading) to the "face data 1" in the building user DB (building A) related to building A, and the building usage related to building B is linked to "face data 1". In the user DB (Building B), the application user ID "80001" is added (displayed with shading) in association with "Face Data 1".

According to the above operation, for a user who has completed the registration operation in the destination floor setting application, the application user ID is registered in the building user DB shown in FIGS. 10A and 10B, and the application user ID is registered in the application user DB shown in FIG. 12. A user ID is registered. The application user ID registered in each user DB shown in FIGS. 10A, 10B, and 12 is registered in the destination floor setting application when the user attempts to use a changed destination floor different from the default destination floor. This is used to check whether the user has completed the operation, that is, whether the user is authorized to use the changed destination floor.

2-2-1. Flowchart of the destination floor change application when the user uses the changed destination floor FIG. 20 is a flowchart regarding the process of the destination floor change application when the user uses the changed destination floor. Each process shown in FIG. 20 is executed by the control unit 201 of the mobile terminal 200 operating the destination floor setting application.

The destination floor setting application receives an application activation command from the OS (S531). Specifically, when the user operates the mobile terminal 200 to activate the destination floor setting application, an application activation command is received from the OS of the mobile terminal 200. This launches the destination floor setting app.

The destination floor setting application prompts the user to take a picture of the user's face with the camera 203 (S532). Specifically, as shown in FIG. 21A(a), a message "Please take a picture of your face with the camera" is displayed on the display unit 210 of the mobile terminal 200, prompting the user to take a picture of his face with the camera 203. , let users take pictures of their faces.

The destination floor setting application determines whether the face image taken by the camera 203 and the stored face image are the same person (S533). Specifically, the face image taken in step S532 and the face image taken and saved during the initial registration of the destination floor setting application (step S502 in FIG. 14) are compared through image processing to determine whether they are the same person. to judge.

If it is determined that they are not the same person (NO in S533), the destination floor setting application displays an error message indicating that authentication is not possible (S534), and ends the flowchart shown in FIG. 20. Specifically, as shown in FIG. 21A(b), a message "Authentication not possible" indicating that authentication is not possible is displayed on the display unit 210.

If it is determined that they are the same person (YES in S533), the destination floor setting application displays available building name buttons (S535). Specifically, as shown in FIG. 21A(c), the building name (S507) saved at the time of initial registration of the destination floor setting application shown in the flowchart of FIG. 14 is read out, and an available building name is determined. The destination floor setting application displays a plurality of building selection buttons 218 on the display unit 210 along with the words "Building Selection". In the example shown in FIG. 21A(c), a building selection button 218 for selecting building A and a building selection button 218 for selecting building B are displayed. Also, a state in which building A is selected is illustrated (displayed by shading).

The destination floor setting application determines whether any building name button 218 has been selected (S536). Unless the building name button 218 is selected (NO in S536), the determination process in step S536 is repeatedly executed.

When the user touches one of the building name buttons 218, it is determined that the building name button 218 has been selected (YES in S536), and the destination floor setting application determines the destination floor change format according to the building name (S537). . Specifically, the building name (e.g. Building A) and destination floor change type (e.g. Chameleon code) saved at the time of initial registration of the destination floor setting application shown in the flowchart of FIG. 14 are read out, and the destination floor corresponding to the building name is read out. Determine the modification format.

The destination floor setting application displays a permission floor button (S538). Specifically, the permitted floors saved at the time of initial registration of the destination floor setting application shown in the flowchart of FIG. 14 are read out, and as shown in FIG. A button 220 is displayed on the display section 210. In the example shown in FIG. 21A(d), a permitted floor button 220 for selecting the 9th floor, a permitted floor button 220 for selecting the 10th floor, and a permitted floor button 220 for selecting the 11th floor are displayed. Ru. Also, a state in which the 9th floor is selected is illustrated (displayed by shading).

The destination floor setting application determines whether any permitted floor button 220 has been selected (S539). Unless the permitted floor button 220 is selected (NO in S539), the determination process in step S539 is repeatedly executed.

When the user touches one of the permitted floor buttons 220, it is determined that the permitted floor button 220 has been selected (YES in S539), and the destination floor setting application generates a destination floor change code that includes the application user ID and information on the changed destination floor. is displayed on the screen for a certain period of time (S540). Specifically, a destination floor change code is created that includes the application user ID (for example, "80001") stored in the destination floor setting application and the permission floor selected in step S539 as the change destination floor, and the display unit 210 to be displayed.

An example of displaying the destination floor change code in step S540 is shown in FIG. 21B. In FIG. 21B(a), a chameleon code Cd including the application user ID and information on the destination floor is displayed along with the message "Please pass with the screen facing the camera." In FIG. 21B(b), a QR code Qd including the application user ID and information on the destination floor is displayed along with the message "Please hold the QR code over the reader." In FIG. 21B(c), a one-dimensional barcode Bc including the application user ID and information on the destination floor is displayed together with the message "Please hold the barcode over the reader."

When the destination floor change format determined in step S537 is "chameleon code", a screen including the chameleon code Cd in FIG. 21B(a) is displayed. If the destination floor change format determined in step S537 is a "QR code", a screen including the QR code Qd in FIG. 21B(b) is displayed. If the destination floor change format determined in step S537 is a "one-dimensional barcode", a screen including the one-dimensional barcode Bc in FIG. 21B(c) is displayed.

Note that in step S535, the available building names are displayed as buttons, but if there is only one available building, the processes in step S535 and step S536 may be omitted. In this case, if it is determined in step S533 that they are the same person (YES in S533), there is no selection of the building name, the destination floor change format is determined according to the building name (S537), and the permission floor button is displayed. (S538).

Furthermore, if there are multiple buildings available, it is also possible to obtain GPS information of the user's mobile terminal in step S535, identify the building from the user's current location, and omit the processes of step S535 and step S536. It is. In this case, the building location information is registered in the application user DB, and in step S504 of FIG. 14, the building location information is received together with available building names, permitted floors, and destination floor change format. Further, in step S507, the building location information is saved together with the selected building name, permitted floor, and destination floor change type.

2-2-2. Facial Authentication Processing and Opening/Closing Control of Security Gate Gate Flapper The security server 100 performs facial authentication on the user to ensure security within the building, based on the captured image shown by the image data output from the facial authentication camera 25. Perform processing. Specifically, when a user attempts to pass through the security gate 20 in order to move from the entrance to an elevator hall in a specific area, the user's face is detected in the face recognition area Ad (see FIG. 1) on the entrance side of the security gate 20. , further performs facial feature point detection processing.

When the security server 100 detects facial feature points from the captured image, it sequentially compares (verifies) the data of the detected facial feature points with each face data (facial feature point data) registered in the user DB. Find the match rate. Then, it is determined whether face data (facial feature point data) having a matching rate equal to or higher than a predetermined matching rate with respect to the facial data (facial feature point data) of the detected face is registered in the user DB. Then, when face data having a match rate equal to or higher than a predetermined match rate is registered in the user DB, the security server 100 registers the user who is about to pass through the security gate 20 (the user whose face has been detected). The user is identified as corresponding to the facial data provided, and the facial recognition is determined to have been successful. In this case, the security server 100 transmits an open signal to the security gate 20. This allows users registered in the user DB to pass through the security gate 20.

On the other hand, if face data (facial feature point data) having a match rate equal to or higher than a predetermined match rate does not exist in the user DB, the security server 100 will detect that the user who is about to pass through the security gate 20 is not registered in the user DB. It is determined that the user is not registered in . In this case, the security server 100 transmits a closing signal to the security gate 20. The control unit 21 of the security gate 20 closes the gate flapper 28. As a result, users who are not registered in the user DB cannot pass through the security gate 20. In other words, users who are not registered in the user DB can be prevented from passing through the security gate 20.

Note that the control unit 21 of the security gate 20 detects whether the user is detected by the first sensor 26 in a situation where neither an open signal nor a close signal is received from the security server 100, that is, in a situation where the face authentication process is not completed. If detected, the gate flapper 28 is closed. Thereby, users who have not completed the face authentication process can be prevented from passing through the security gate 20.

In this way, users who are registered in the user DB can enter the specific area, but other users cannot enter the specific area. Therefore, security within the building is ensured.

2-2-3. Machine number assignment processing 2-2-3-1. Destination floor setting process and machine number assignment process when using the security gate (in building A that supports the chameleon code destination floor change format)
In the face authentication process for a user who is about to pass through the security gate 20, if the security server 100 determines that the user is a user registered in the user DB, the security server 100 receives an output from the face authentication camera 25. Chameleon code detection processing is performed on the captured image indicated by the image data, and when a chameleon code is detected, analysis processing (decoding) of the detected chameleon code is performed. If the security server 100 determines that the chameleon code is included in the captured image within a predetermined time T (seconds) after face authentication, the security server 100 sets the default destination floor or the changed destination floor as the user's destination floor. The predetermined time T (seconds) allows the user to appropriately register the changed destination floor using the chameleon code even if there is variation in the presentation timing of the chameleon code by the user who performs face authentication and registration of the changed destination floor. For example, it is 2 (seconds). In this case, it is preferable to inform users in advance of the method for registering the changed destination floor. Note that, as described in other embodiments, a message such as "Please point this screen toward the camera during face authentication" may be displayed on the display unit 210 of the mobile terminal 200. In this case, it is expected that the user will point the chameleon code display screen toward the face authentication camera 25 at approximately the same timing during face authentication. Therefore, the predetermined time T (seconds) may be set to a short time less than 1 (second), for example. The security server 100 generates a call information signal including information such as the departure floor, location, destination floor, etc., and transmits the call information signal to the group management control device 10. Note that the "departure floor" in the call information signal is equal to the "installation floor" of the registration device, as described above.

(In building B that supports the QR code destination floor change format)
In the face authentication process for a user who is about to pass through the security gate 20, if the security server 100 determines that the user is a user registered in the user DB, the security server 100 waits for a predetermined time T (seconds) after face authentication. ) The default destination floor or the changed destination floor is set as the user's destination floor according to the judgment result of whether or not QR code data has been received from the QR code reader 29 within , and transmits the call information signal to the group management control device 10 . Note that the "departure floor" in the call information signal is equal to the "installation floor" of the registration device, as described above.

When the group management control device 10 receives the call information signal from the security server 100, it determines an assigned car to which the user's destination floor will be assigned based on the received call information signal, and sends an assignment result signal indicating the determined assigned car. , to the gate display 70 located at the departure floor and location indicated by the call information signal.

Upon receiving the assignment result signal from the group management control device 10, the gate display 70 displays an assigned car notification screen.

More detailed destination floor setting processing and car number assignment processing will be described later.

2-2-3-2. Destination floor setting processing and car number assignment processing when using the destination floor registration device The security server 100 performs face authentication processing for a user who intends to use the destination floor registration device 30 when the user is registered in the user DB. If it is determined that the user is the user, information on the default destination floor and permitted floor linked to the user is read from the user DB, and the face authentication camera 36 attached to the destination floor registration device 30 is registered. Information on the installation floor and location is read from the registered device DB based on the device ID. Then, the security server 100 generates a call information signal including information on the default destination floor and permitted floor read from the user DB, and information on the installation floor (departure floor) and location read from the registered device DB, and A call information signal is transmitted to the group management control device 10.

When the group management control device 10 receives the call information signal from the security server 100, it generates an acceptance permission signal including at least information on the permitted floor based on the received call information signal, and converts the generated reception permission signal into the call information signal. The information is sent to the destination floor registration device 30 located at the departure floor and location indicated by .

When receiving the reception permission signal, the destination floor registration device 30 displays the destination floor button of the permitted floor indicated by the permitted floor information on the display unit 34, and accepts the user's operation to specify the destination floor. When a destination floor is designated, the destination floor registration device 30 transmits an assignment request signal to the group management control device 10 requesting that any car be assigned to the designated destination floor.

Upon receiving the assignment request signal, the group management control device 10 determines an assigned aircraft to which the user's destination floor is to be assigned, and sends an assignment result signal indicating the determined assigned aircraft to the departure floor and location indicated by the call information signal. The information is sent to the destination floor registration device 30.

When the destination floor registration device 30 receives the assignment result signal from the group management control device 10, it displays on the display unit 34 an assigned car notification screen displaying the assigned car.

2-2-4. Specific Operation of Elevator System The destination floor setting process and car number assignment process when a user uses the security gate 20 will be described in more detail with reference to a flowchart.

FIGS. 22A and 22B are flowcharts illustrating call information signal generation processing by the security server 100, respectively. FIG. 22A is a flowchart regarding the security server 100 of building A that corresponds to the destination floor changing format of the chameleon code, and FIG. 22B is a flowchart regarding the security server 100 of building B that corresponds to the destination floor changing format of the QR code. The processing in this flowchart is executed for each security gate 20. Further, processing for each security gate 20 is executed in parallel.

First, a flowchart regarding the security server 100 of building A shown in FIG. 22A will be described.

As shown in FIG. 22A, the control unit 101 of the security server 100 determines whether a face is included in the captured image indicated by the image data output from the face authentication camera 25 (S11). The processing in this step may be performed for each captured image output at a predetermined frame rate, or may be performed intermittently, for example, only once every several frames.

If the captured image does not include a face (NO in S11), that is, if no face is detected, the control unit 101 of the security server 100 executes the determination in step S11 again.

When a face is included in the captured image (YES in S11), that is, when a face is detected, the control unit 101 of the security server 100 performs the above-mentioned face authentication process to obtain facial data ( It is determined whether facial data (facial feature point data) having a matching rate equal to or higher than a predetermined matching rate with respect to facial feature point data) is registered in the user DB (S12).

If face data having a match rate equal to or higher than a predetermined match rate with respect to the face data of the detected face is not registered in the user DB (NO in S12), the control unit 101 of the security server 100 closes the security gate 20. A signal is transmitted (S26). Accordingly, the control unit 21 of the security gate 20 controls the gate flapper 28 to maintain it in the closed state.

If face data having a match rate equal to or higher than a predetermined match rate with respect to the face data of the detected face is registered in the user DB (YES in S12), the control unit 101 of the security server 100 opens the security gate 20. A signal is transmitted (S13). Accordingly, the control unit 21 of the security gate 20 controls the gate flapper 28 to open.

The control unit 101 of the security server 100 sets the current time as the face authentication time tc (S14).

The control unit 101 of the security server 100 acquires the user ID associated with the face data having a predetermined matching rate or higher from the user DB (S15).

The control unit 101 of the security server 100 determines whether a chameleon code is included in the captured image indicated by the image data output from the face authentication camera 25 (S16). The processing in this step may be performed for each captured image output at a predetermined frame rate, or may be performed intermittently, for example, only once every several frames.

When a chameleon code is included in the captured image (YES in S16), that is, when a chameleon code is detected, the control unit 101 of the security server 100 analyzes (decodes) the chameleon code and converts it into a chameleon code. The application user ID and information on the destination floor to be changed are acquired from (S17).

The control unit 101 of the security server 100 determines whether the app user ID acquired from the chameleon code matches the app user ID associated with face data having a match rate equal to or higher than a predetermined match rate (S18). . Specifically, the application user ID obtained from the chameleon code by searching the building user DB of building A shown in FIG. Determine whether it matches or not.

If the app user ID obtained from the chameleon code matches the app user ID associated with face data having a match rate equal to or higher than a predetermined match rate (YES in S18), the control unit 101 of the security server 100 controls the destination floor. The change flag is set to ON (S19).

The control unit 101 of the security server 100 identifies the installation floor and location of the security gate 20 that the user intends to pass through based on the registered device ID of the security gate 20 (S21). This also involves identifying the user's departure floor and location.

The control unit 101 of the security server 100 sets the changed destination floor acquired in step S17 as the user's destination floor (S22).

The control unit 101 of the security server 100 generates a call information signal including information on the departure floor, changed destination floor, location, and destination floor change flag ON, and transmits it to the group management control device 10 (S23).

The control unit 101 of the security server 100 determines whether a user passing signal has been received from the security gate 20 (S24).

If the user passing signal has not been received from the security gate 20 (NO in S24), the control unit 101 of the security server 100 executes the determination in step S24 again.

When the user passage signal is received from the security gate 20 (YES in S24), the control unit 101 of the security server 100 transmits a closing signal to the security gate 20 (S25).

In step S16 described above, if the captured image does not include the chameleon code (NO in S16), that is, if the chameleon code is not detected, the control unit 101 of the security server 100 waits for a predetermined period of time T (seconds) from the face authentication time tc. ) has passed (S27). The predetermined time T (seconds) is as described above.

If the predetermined time T (seconds) has not elapsed since the face authentication time tc (NO in S27), the control unit 101 of the security server 100 returns to the process of step S16.

If the predetermined time T (seconds) has passed since the face authentication time tc (YES in S27), the control unit 101 of the security server 100 sets the destination floor change flag to OFF (S28).

The control unit 101 of the security server 100 acquires the default destination floor linked to the face data having a match rate equal to or higher than a predetermined match rate from the user DB (S29).

The control unit 101 of the security server 100 identifies the installation floor and location of the security gate 20 that the user intends to pass through based on the registered device ID of the security gate 20 (S30). This also involves identifying the user's departure floor and location.

The control unit 101 of the security server 100 sets the default destination floor acquired in step S29 as the user's destination floor (S31).

The control unit 101 of the security server 100 generates a call information signal including information on the departure floor, default destination floor, location, and destination floor change flag OFF, and transmits it to the group management control device 10 (S32).

In step S18 described above, if the app user ID acquired from the chameleon code does not match the app user ID associated with face data having a match rate equal to or higher than a predetermined match rate (NO in S18), the control of the security server 100 The unit 101 executes the processes after step S28 described above. If the app user IDs do not match, the user whose face authentication was successful in step S12 is not allowed to change the destination floor using the chameleon code, that is, the registration operation on the destination floor setting app has not been completed successfully. means. Therefore, the process from step S28 onward is executed when the destination floor is not changed.

In addition, when it is determined NO in step S18, the control unit 101 of the security server 100, in parallel with the processing from step S28 onward, displays a message such as "Destination floor change is not permitted. Destination floor setting application registration". Please perform the following steps.'' may be announced by voice or screen display.

Next, a flowchart regarding the security server 100 of building B shown in FIG. 22B will be described.

The flowchart shown in FIG. 22B differs from the flowchart shown in FIG. 22A in that step S16 and step S17 are changed to steps S16A and S17A.

Specifically, the control unit 101 of the security server 100 determines whether QR code data has been received from the QR code reader 29 (S16A).

When receiving QR code data from the QR code reader 29 (YES in S16A), the control unit 101 of the security server 100 analyzes (decodes) the QR code data and extracts the application user ID and the QR code data from the QR code data. Information on the changed destination floor is acquired (S17A).

FIG. 23 is a flowchart illustrating assignment processing by the group management control device 10. The processing in this flowchart is executed when the group management control device 10 receives a call information signal of a new call from the security server 100. It is also executed in parallel each time a call information signal for a new call is received.

The flowchart shown in FIG. 23 has contents common to the case of receiving a call information signal from the security server 100 of Building A shown in FIG. 22A and the case of receiving a call information signal from the security server 100 of Building B shown in FIG. 22B. Yes, I will explain them all.

When the group management control device 10 receives the call information signal from the security server 100, it starts the process shown in the flowchart of FIG. 23 and acquires various information included in the call information signal (S51).

The group management control device 10 determines whether the destination floor change flag indicated by the call information signal is ON (S52).

If the destination floor change flag is ON (YES in S52), the group management control device 10 allocates the departure floor and change destination floor indicated by the call information signal to one of the elevators (S55).

The group management control device 10 transmits a signal indicating the assignment result (assignment result signal) to the gate display 70 of the departure floor and location indicated by the call information signal (S56). At this time, an assigned car notification screen is displayed on the gate display 70.

FIG. 24 is a diagram showing a display example on the gate display 70 of the security gate 20. FIG. 24(a) is a diagram showing an example of an allocated machine notification screen. In the example of FIG. 24(a), "7F, No. 3" indicating that No. 3 has been assigned to the 7F of the changed destination floor, and "Destination floor 7F has been read." are displayed. Note that a message indicating that the destination floor has been changed from the default destination floor may be displayed (for example, "Change from 10F to 7F has been accepted.").

In step S52 above, if the destination floor change flag is not ON (NO in S52), that is, if the destination floor change flag is OFF, the group management control device 10 registers the value of the default destination floor in the call information signal. It is determined whether or not (S57).

If the value of the default destination floor is registered (YES in S57), the group management control device 10 assigns the departure floor and default destination floor indicated by the call information signal to one of the elevators (S58).

The group management control device 10 transmits a signal indicating the allocation result to the gate display 70 of the departure floor and location indicated by the call information signal (S59). At this time, an assigned car notification screen is displayed on the gate display 70. The displayed content is either FIG. 24(b) or FIG. 24(c). In the example of FIG. 24(b), "10F Car No. 1" is displayed, indicating that car No. 1 is assigned to the default destination floor 10F. In the example of FIG. 24(c), "10F Car 1" indicates that car No. 1 has been assigned to the default destination floor 10F, and the change destination floor 12F is not permitted and must be registered in the destination floor setting application. A message prompting, ``The destination floor 12th floor has been read, but the 12th floor is not permitted. Please register using the destination floor setting app.'' is displayed.

The display screen in FIG. 24(b) shows that in step S27 shown in FIGS. 22A and 22B, it is determined that T seconds have passed since the face authentication time tc (YES in S27), and the destination floor change flag is set to OFF. (S28). The display screen of FIG. 24(c) shows the app user ID whose app user ID acquired from the chameleon code or QR code data is linked to face data with a predetermined matching rate or higher in step S18 shown in FIGS. 22A and 22B. This is displayed when it is determined that the destination floor change flag does not match (S27: YES) and the destination floor change flag is set to OFF (S28).

If the value of the default destination floor is not registered (NO in S57), that is, if the symbol "-" (destination floor unset information) is registered as the default destination floor in the user DB, the group management control device 10 , a signal for displaying a display prompting the destination floor registration device 30 to register the destination floor is transmitted to the gate display 70 of the departure floor and location indicated by the call information (S60). At this time, a screen prompting the user to register the destination floor is displayed on the gate display 70. FIG. 24(d) is a diagram showing an example of a screen prompting registration of a destination floor. In the example of FIG. 24(d), the message ``Please register the destination floor with the destination floor registration device in the elevator hall.'' is displayed. Note that the destination floor is registered in the destination floor registration device 30, for example, when a user who frequently goes to multiple permitted floors does not intentionally set a default destination floor, or when a user who frequently visits multiple permitted floors does not intentionally set a default destination floor. This occurs when you forget that you have the mobile terminal 200.

3. Effects of this Embodiment In the elevator system of this embodiment, face authentication of a user attempting to pass through the security gate 20 is performed based on a captured image captured by the face authentication camera 25. In addition, when the chameleon code is not detected from the captured image within a predetermined time T (seconds) after facial recognition is successful (Building A), or when the QR code is not read by the QR code reader 29 ( In building B), the default destination floor linked to the user in advance is set as the user's destination floor. On the other hand, when the chameleon code is detected from the captured image within a predetermined time T (seconds) after face recognition is successful (Building A), or when the QR code is read by the QR code reader 29 (Building B ), the changed destination floor indicated by the chameleon code or QR code is set as the user's destination floor. Therefore, when a user passes through a gate that uses facial recognition, it is possible to register not only the default destination floor but also a changed destination floor.

In addition, even if the format of destination floor change information is different in multiple buildings, by having a function to obtain destination floor change information in a format suitable for each building, it is possible to correspond to multiple buildings, and the user Convenience can be improved. By using the destination floor application connected to the application server 500, even the same user can use a changed destination floor different from the default destination floor in multiple buildings.

In the first embodiment, an example was described in which the security server 100 detects and analyzes a destination floor change code such as a chameleon code or a QR code (obtains an application user ID and a changed destination floor). but not limited to. In the present invention, the group management control device 10 or another analysis device may detect and analyze the destination floor change code (obtain the application user ID and the changed destination floor). Below, a first modification and a second modification of the first embodiment will be described.

(First modification of Embodiment 1)
In the first modification of the first embodiment, the group management control device 10 in building A detects and analyzes the chameleon code instead of the security server 100, and the group management control device 10 in building B detects and analyzes the QR code. Read and parse to obtain app user ID and change destination floor.

FIG. 25 is a block diagram showing the system configuration of the elevator system in the first modification of the first embodiment.

In the first modification of the first embodiment, each face authentication camera 25 is connected not only to the security server 100 but also to the group management control device 10; The image data of the captured image is also output for the captured image. In building B, each QR code reader 29 is connected to the group management control device 10 and outputs QR code data to the group management control device 10. Then, the group management control device 10 of Building A performs chameleon code detection processing on the captured image, analyzes the detected chameleon code, and obtains the application user ID and the changed destination floor. Furthermore, the group management control device 10 of Building B analyzes the QR code data output from the QR code reader 29 and obtains the application user ID and the changed destination floor.

According to this modification, effects similar to those of Embodiment 1 can be obtained. In addition, since the process of setting the default destination floor or the changed destination floor as the destination floor is performed by the group management control device 10, there is no need to perform this process in the security server 100, and changes in the specifications of the security server 100 can be suppressed as much as possible. .

(Second modification of Embodiment 1)
In the second modification of the first embodiment, an analysis device provided separately from the security server 100 and the group management control device 10 detects and analyzes the destination floor change code (obtains the application user ID and the changed destination floor). An example of how to do this will be explained below.

26A and 26B are block diagrams showing the system configuration of a building elevator system in a second modification of the first embodiment. 26A shows a building elevator system for building A, and FIG. 26B shows a building elevator system for building B.

In a second modification of the first embodiment, a chameleon code analysis device 300 is provided in the building elevator system of building A shown in FIG. 26A. Each face authentication camera 25 is connected not only to the security server 100 but also to the chameleon code analysis device 300, and outputs image data of captured images not only to the security server 100 but also to the chameleon code analysis device 300. Further, a QR code analysis device 400 is provided in the building elevator system of building B shown in FIG. 26B. Each QR code reader 29 is connected not only to the security server 100 but also to the QR code analysis device 400, and outputs QR code data not only to the security server 100 but also to the QR code analysis device 400.

The chameleon code analysis device 300 is configured by a computer having a control section, a storage section, an input/output interface, etc., like the group management control device 10 and the like. The chameleon code analysis device 300 performs chameleon code detection processing on the captured images output from each face authentication camera 25, and when a chameleon code is detected, analyzes (decodes) the chameleon code. , obtains the app user ID and the changed destination floor from the chameleon code, and uses the acquired app user ID and changed destination floor, and information specifying the face authentication camera 25 that outputs the captured image in which the chameleon code is detected, as a group. The information is sent to the management control device 10. As the information for specifying the face authentication camera 25, for example, information about the installation floor and location of the security gate 20 where the face authentication camera 25 is arranged is used. Note that the information for identifying the face authentication camera 25 may be a serial number of the face authentication camera 25 or the like.

The QR code analysis device 400 is configured by a computer having a control section, a storage section, an input/output interface, etc., like the group management control device 10 and the like. The QR code reader 29 outputs the read QR code data to the QR code analysis device 400. The QR code analysis device 400 analyzes (decodes) the QR code data output from the QR code reader 29, acquires the app user ID and the changed destination floor from the QR code data, and stores the acquired app user ID and destination floor. The change destination floor and information specifying the QR code reader 29 from which the QR code data is output are transmitted to the group management control device 10. As the information for specifying the QR code reader 29, for example, information about the installation floor and location of the security gate 20 where the QR code reader 29 is arranged is used. Note that the information identifying the QR code reader 29 may be the serial number of the QR code reader 29 or the like.

According to this modification, effects similar to those of Embodiment 1 can be obtained. In addition, since the process of setting the default destination floor or the changed destination floor as the destination floor is performed by the group management control device 10, there is no need to perform this process in the security server 100, and changes in the specifications of the security server 100 can be suppressed as much as possible. . Further, there is no need to perform analysis processing of the destination floor change code in the group management control device 10.

(Other embodiments)
In the first embodiment, in steps S16 and S27 of FIG. 22A, it is determined that the chameleon code is not detected from the captured image (NO in S16) and a predetermined time T (seconds) has elapsed from the face authentication time tc (S27 ). If it is determined that the predetermined time T (seconds) has elapsed since the face authentication time tc (YES in S27), the processes after step S28 are executed. That is, the destination floor change flag is set to OFF (S28), and a call information signal including information on the default destination floor is generated and transmitted to the group management control device 10 (S32). However, instead of the determination in step S27, it may be determined whether the first sensor 26 of the security gate 20 detects the user. In other words, it may be determined whether the user is on the way through the security gate 20 or not. According to this process, even if a chameleon code is not detected from the captured image (NO in S16), when a user is detected by the first sensor 26 of the security gate 20, the processes from step S28 onwards are executed immediately. That is, a call information signal is immediately generated and transmitted to the group management control device 10, and the allocation process is executed. Therefore, even users who use the default destination floor can receive elevator assignment without waiting for the predetermined time T (seconds) to elapse. Note that if the first sensor 26 of the security gate 20 does not detect the user, the process returns to step S16. This modification can be similarly applied to the flowchart of FIG. 22B.

In the embodiment and each modification, the security server 100 performs face detection processing and facial feature point detection processing on the captured image indicated by the image data output from the face authentication camera 25, and performs the face authentication processing. Although an example of performing the above has been described, the present invention is not limited thereto. For example, the controller of the face authentication camera 25 may perform face detection processing and facial feature point detection processing on the captured image, and the security server 100 may perform only the face authentication processing. In other words, the face authentication camera 25 and the security server 100 may share the process of "performing face authentication of the user based on the captured image captured by the image capturing unit". In this case, the face authentication camera 25 outputs facial feature point data (face data) to the security server 100 instead of the image data of the captured image. The security server 100 also performs face authentication processing based on the received face data (facial feature point data).

In the embodiment and each modification, the security server 100, the group management control device 10, or the chameleon code analysis device 300 performs chameleon code detection processing on the captured image indicated by the image data output from the face authentication camera 25. Although an example has been described in which analysis processing (decoding) of the detected chameleon code is performed at the same time, the present invention is not limited to this. For example, the controller of the face authentication camera 25 may perform chameleon code detection processing and chameleon code analysis processing on the captured image. In this case, the face authentication camera 25 outputs the user ID (app user ID) and information on the destination floor to the security server 100 or the group management control device 10 instead of the image data of the captured image. In this case, the security server 100 may use the received user ID (app user ID) and changed destination floor as they are. This content can be similarly applied to other analysis devices such as the QR code analysis device 400.

In the embodiment and each modification example, the security gate 20 including the gate flapper 28 has been illustrated as the gate in the present invention, but the gate is not limited to this. In the present invention, the gate does not need to include a gate flapper. In this case, the control related to opening and closing of the gate flapper described in the above embodiment may be omitted.

In the embodiment and each modification example, the mobile terminal 200 capable of generating and displaying a destination floor change code based on the user's operation is exemplified as the predetermined device of the present invention, but the predetermined device is not limited to this. . The predetermined device may be any device as long as it can generate a destination floor change code based on the user's operation.

In the embodiment and each modification example, the chameleon code is utilized by performing chameleon code detection and analysis processing only on the captured image output from the face authentication camera 25 disposed at the security gate 20. The case where it is possible to register a changed destination floor has been explained. However, chameleon code detection and analysis processing is also performed on the captured image output from the face authentication camera 36 attached to each destination floor registration device 30 on each floor, and the destination floor is changed using the chameleon code. registration may be made possible. In this case, when the user is in front of the destination floor registration device 30, the predetermined viewing angle area of the face authentication camera 36 includes not only the user's face but also the side of the user's face and body for facial authentication. The screen of the display unit 210 of the mobile terminal 200 held up toward the camera 36 may be set to an angle of view that allows imaging. The predetermined resolution may be any resolution as long as it allows for appropriate face detection and face matching during face authentication, as well as chameleon code detection and analysis. In the following, (1) a case where chameleon code detection processing and analysis processing are further performed in the face authentication camera 36 attached to the destination floor registration device 30 of the first embodiment will be exemplified. (2) When chameleon code detection processing and analysis processing are further performed in the face authentication camera 36 attached to the destination floor registration device 30 of the first modification of the first embodiment, (3) the first embodiment The same applies to the case where the face authentication camera 36 attached to the destination floor registration device 30 of the second modification further performs chameleon code detection processing and analysis processing.

(1) If the face authentication camera 36 attached to the destination floor registration device 30 of the first embodiment further performs chameleon code detection and analysis processing, the system configuration shown in FIG. 2 described above can be used as is. Bye.
The security server 100 may perform similar control according to the flowcharts in FIGS. 22A and 22B, respectively, on the captured images output from the face authentication cameras 36 attached to the destination floor registration device 30 on each floor. Note that "security gate" in the flowcharts of FIGS. 22A and 22B may be replaced with "destination floor registration device." Furthermore, since the destination floor registration device 30 is not equipped with a gate flapper, control related to opening and closing of the gate flapper of the security gate 20 (steps S13, S14, S24, S25) in the flowcharts of FIGS. 22A and 22B is omitted. do it.
The group management control device 10 may perform processing according to the flowchart in FIG. 23. Note that the "gate display" in the flowchart of FIG. 23 may be replaced with "destination floor registration device."
When the destination floor registration device 30 receives the signal based on the process of step S56 in FIG. 23, it causes the display unit 34 to display an assigned car notification screen similar to that shown in FIG. 24(a) described above. Further, upon receiving the signal based on the process of step S59 in FIG. 23, the destination floor registration device 30 displays on the display unit 34 an assigned car notification screen similar to that shown in FIG. 24(b) or FIG. 24(c) described above. let Further, upon receiving the signal based on the process of step S60 in FIG. 23, the destination floor registration device 30 displays a message "Please register the destination floor" on the display unit 34, and then displays the message shown in FIG. 5(a). An operation screen similar to that may be displayed.

In the embodiment and each modification example, the chameleon code, QR code, and one-dimensional barcode are used as examples of the destination floor change code (destination floor change information), but the information is not limited to this, and the information on the application user ID and the changed destination floor It may be any type of code as long as it includes.

In the embodiment and each modification, the control unit of each device is configured using a CPU, MPU, etc., and performs arithmetic processing using various data based on a program read from a storage unit. This enables various functions to be realized. In other words, each control section is realized by cooperation between hardware and software. However, each control unit may be configured using only hardware (electronic circuit), FPGA, ASIC, etc., for example.

In the embodiment and each modification example, the network is Ethernet, and the input/output interface of each device is configured using a LAN adapter or the like. However, this is just an example, and the network may be configured, for example, by a wireless LAN compliant with the IEEE standard, and the input/output interface may be configured by a wireless LAN adapter or the like.

The security server 100, group management control device 10, elevator control device 40, chameleon code analysis device 300, and QR code analysis device 400 in the embodiment and each modification are not installed in the building where the elevator 60 is located. Not required. For example, the functions of any of these devices may be executed by a cloud server. In this case, various signals and information are exchanged between the cloud server and devices such as the security gate 20, destination floor registration device 30, and gate display 70 installed in the building where the elevator 60 is located, using appropriate communications. This can be done by communication using a method.

A plurality of aspects of the present invention have been described in the embodiment and each modification. However, the specific aspects of the present invention are not limited to the above-described embodiments and modifications, and may be a combination of these.

(Summary and effects of embodiments, etc.)
(1) The elevator system of the embodiment is
An elevator system in which a user sets the user's destination floor before boarding the elevator in a building (for example, Building A or Building B),
an imaging unit (e.g., face authentication camera 25) provided to be able to image a user who is passing through a gate (e.g., security gate 20) disposed on the travel route to the elevator hall;
a face authentication unit (for example, the security server 100) that performs facial authentication of a user based on a captured image captured by the image capturing unit;
an information acquisition unit (for example, face authentication camera 25, QR code reader 29, chameleon code analysis device 300, QR code analysis device 400) that obtains destination floor change information regarding the user's change destination floor;
A destination floor setting unit (for example, a security server 100 or a group management control device 10) for setting a user's destination floor,
The destination floor setting section is
If the user's face recognition is successful in the face recognition unit, but the information acquisition unit does not acquire the destination floor change information, the default destination floor specified based on the face recognition is set as the user's destination floor. death,
When the user's face authentication is successful in the face authentication unit, and the information acquisition unit acquires the destination floor change information, the changed destination floor specified based on the destination floor change information is set as the user's destination floor. Set,
The information acquisition unit includes a first information acquisition unit (for example, face authentication camera 25 of building A) that acquires destination floor change information in a first format (for example, chameleon code) corresponding to a building (for example, building A), or The second information acquisition unit (for example, the QR code reader 29 of building B) acquires the destination floor change information in a second format (for example, QR code) corresponding to building B).

With this configuration, the user's destination floor is set based on the captured image captured by the facial authentication imaging unit (eg, face authentication camera 25) when the user passes through the gate (eg, security gate 20). can. Therefore, the user's destination floor can be set without separately providing a reader for acquiring information from an IC card or the like. In particular, according to the present embodiment, not only the default destination floor but also the changed destination floor can be set as the user's destination floor based on the destination floor change information acquired by the information acquisition unit.

In addition, even if the format of destination floor change information is different in multiple buildings, by having a function to obtain destination floor change information in a format suitable for each building, it is possible to correspond to multiple buildings, and the user Convenience can be improved.

(2) The elevator system of the embodiment is
An elevator system in which a user sets the user's destination floor before boarding the elevator in a building (for example, Building A or Building B),
an imaging unit (for example, face authentication camera 25) provided to be able to image a user attempting to use a destination floor registration device (destination floor registration device 30) disposed in an elevator hall;
a face authentication unit (for example, the security server 100) that performs facial authentication of a user based on a captured image captured by the image capturing unit;
an information acquisition unit (for example, face authentication camera 36, QR code reader 129, chameleon code analysis device 300, QR code analysis device 400) that obtains destination floor change information regarding the user's change destination floor;
A destination floor setting unit (for example, a security server 100 or a group management control device 10) for setting a user's destination floor,
The destination floor setting section is
If the user's face recognition is successful in the face recognition unit, but the information acquisition unit does not acquire the destination floor change information, the default destination floor specified based on the face recognition is set as the user's destination floor. death,
When the user's face authentication is successful in the face authentication section and the destination floor change information is acquired by the destination floor change information acquisition section, the user will be notified of the changed destination floor specified based on the destination floor change information. set as the destination floor of
The information acquisition unit includes a first information acquisition unit (for example, face authentication camera 36 of building A) that acquires destination floor change information in a first format (for example, chameleon code) corresponding to a building (for example, building A), or The second information acquisition unit (for example, the QR code reader 129 of building B) acquires destination floor change information in a second format (for example, QR code) corresponding to building B).

With this configuration, when the user uses the destination floor registration device (destination floor registration device 30), the user's You can set the destination floor. Therefore, the user's destination floor can be set without separately providing a reader for acquiring information from an IC card or the like. In particular, according to the present invention, not only the default destination floor but also the changed destination floor can be set as the user's destination floor based on the captured image captured by the image capturing unit for face authentication.

In addition, even if the format of destination floor change information is different in multiple buildings, by having a function to obtain destination floor change information in a format suitable for each building, it is possible to correspond to multiple buildings, and the user Convenience can be improved.

(3) In the elevator system of the embodiment,
The user generates first type destination floor change information (for example, chameleon code) and second type destination floor change information (for example, QR code) by operating a predetermined device (for example, mobile terminal 200).

With this configuration, destination floor change information in different formats can be easily generated and used in multiple buildings.

(4) The elevator system of the embodiment is
The predetermined device is the user's mobile terminal 200,
The operations on the predetermined device include operations on the destination floor setting application within the mobile terminal 200.

With this configuration, destination floor change information in different formats can be easily generated using the destination floor setting application of the mobile terminal 200.

(5) In the elevator system of the embodiment,
The first type of destination floor change information (for example, chameleon code) and the second type of destination floor change information (for example, QR code) each store common user identification information (for example, application user ID).

With this configuration, by storing common user identification information, it is possible to accurately and easily identify the same user.

(6) In the elevator system of the embodiment,
User identification information (for example, application user ID) is generated for each destination floor setting application in the user's mobile terminal 200.

With this configuration, identification of the same user can be performed accurately and easily.

(7) In the elevator system of the embodiment,
The first information acquisition unit (for example, the face authentication camera 25 in building A) acquires the destination floor change information from the captured image taken by the imaging unit, and the second information acquisition unit (for example, the QR code reader 29 in building B) acquires the destination floor change information from the captured image taken by the imaging unit. is placed at a gate (e.g. security gate 20) or destination floor registration device 30 (an example of a destination floor registration device) or in the vicinity of each, and receives destination floor change information from an information recording medium (e.g. mobile terminal 200) owned by the user. get.

With this configuration, the first information acquisition section and the second information acquisition section can handle different formats of destination floor change information.

(8) The mobile terminal 200 of the embodiment includes:
A display unit 210 (an example of a display unit) that displays an image;
An imaging unit (for example, camera 203),
A control unit 201 (an example of a control unit),
The control unit 201
(i) causing the imaging unit to image the user's face;
(ii) Based on the face data captured by the imaging unit, obtain information on available buildings, permitted floors, and destination floor change format;
(iii) When the user attempts to use a changed destination floor different from the default destination floor when passing through the building's facial recognition system, a destination floor change code ( For example, a chameleon code, QR code, one-dimensional barcode) is displayed in a destination floor changing format corresponding to the building.

(9) In the mobile terminal 200 of the embodiment,
The control unit 201 causes the display unit 210 to display a destination floor change code (eg, chameleon code, QR code, one-dimensional barcode) in response to the user's operation on the destination floor setting application.

(10) In the mobile terminal 200 of the embodiment,
The available buildings include multiple buildings (for example, Building A and Building B),
The control unit 201 has a function of displaying, on the display unit 210, a first type destination floor change code (for example, a chameleon code) corresponding to each of a plurality of buildings (for example, Building A), or a function of displaying a first type destination floor change code (for example, a chameleon code) corresponding to each of a plurality of buildings (for example, Building B). It has a function of displaying a second type of destination floor change code (for example, QR code) corresponding to the destination floor change code.

(11) In the mobile terminal 200 of the embodiment,
The first type of destination floor change code (eg, chameleon code) and the second type of destination floor change code (eg, QR code) each store common user identification information (eg, app user ID).

(12) In the mobile terminal 200 of the embodiment,
User identification information (for example, application user ID) is generated for each destination floor setting application.

(13) The program of the embodiment is
The computer is made to function as the control unit 201 of the mobile terminal 200.

(14) The method for controlling the mobile terminal 200 according to the embodiment is as follows:
A method for controlling a mobile terminal 200 including a display unit 210 (an example of a display unit) that displays an image, and an imaging unit (for example, a camera 203),
(i) causing the imaging unit to image the user's face;
(ii) Based on the face data captured by the imaging unit, obtain information on available buildings, permitted floors, and destination floor change format;
(iii) When the user attempts to use a changed destination floor different from the default destination floor when passing through the building's facial recognition system, a destination floor change code ( For example, a chameleon code, QR code, one-dimensional barcode) is displayed in a destination floor changing format corresponding to the building.

10 Group management control device 11 Control section 12 Storage section 13 Input/output interface 20 Security gate 20a Gate main body 20i Entrance 20e Exit 25 Face authentication camera 26 First sensor 27 Second sensor 28 Gate flapper 30 Destination floor registration device 31 Control section 32 Storage unit 33 Input/output interface 34 Display unit 35 Operation unit 36 Face authentication camera 40, 40A to 40F Elevator control device 60, 60A to 60F Elevator 70 Gate display 100 Security server 101 Control unit 102 Storage unit 103 Input/output interface 200 Mobile Terminal 201 Control unit 203 Camera 210 Display unit 300 Chameleon code analysis device 400 QR code analysis device 500 Application server T Predetermined time

Claims (7)

a display section that displays an image;
an imaging unit;
comprising a control unit;
The control unit includes:
(i) causing the imaging unit to image the user's face;
(ii) obtaining information on available buildings, permitted floors, and destination floor change formats based on the face data captured by the imaging unit;
(iii) When the user attempts to use a changed destination floor different from the default destination floor when passing through the facial recognition system of the building, the destination floor includes information on the changed destination floor on the display section. displaying the change code in the destination floor change format corresponding to the building;
Mobile device. The control unit causes the display unit to display the destination floor change code in response to a user's operation on the destination floor setting application.
The mobile terminal according to claim 1 . The available buildings include a plurality of buildings,
The control unit has a function of displaying, on the display unit, the destination floor change code in a first format corresponding to each of the plurality of buildings, or the destination floor change code in a second format corresponding to each of the plurality of buildings. It has the function of displaying
The mobile terminal according to claim 1 or 2 . 4. The mobile terminal according to claim 3 , wherein the destination floor change code in the first format and the destination floor change code in the second format each store common user identification information. The mobile terminal according to claim 4 , wherein the user identification information is generated for each destination floor setting application. A program that causes a computer to function as a control unit of a mobile terminal according to any one of claims 1 to 5 . A method for controlling a mobile terminal including a display unit that displays an image and an imaging unit, the method comprising:
(i) causing the imaging unit to image the user's face;
(ii) obtaining information on available buildings, permitted floors, and destination floor change formats based on the face data captured by the imaging unit;
(iii) When the user attempts to use a changed destination floor different from the default destination floor when passing through the facial recognition system of the building, the destination floor includes information on the changed destination floor on the display section. displaying the change code in the destination floor change format corresponding to the building;
How to control your mobile device.

Images