JP7327556B1 - elevator system - Google Patents

Abstract

The object of the present invention is to provide an elevator system that enables registration of not only a default destination floor but also a changed destination floor when a user passes through a security gate using face authentication. An elevator system includes an imaging unit (25), a notification unit (70), an information acquisition unit (29), a face authentication unit (100), and a destination floor setting unit (100), The destination floor setting unit sets the default destination floor specified based on the face authentication as the destination floor of the user when the predetermined information is not acquired by the information acquisition unit when the face authentication is successful, and When the authentication is successful and the predetermined information is obtained by the information obtaining unit, the changed destination floor indicated by the predetermined information is set as the user's destination floor, and the information obtaining unit is located on the left side of the lane (50) at the gate. and a second information acquisition section (29B) arranged on the right side. [Selection drawing] Fig. 7B

Description

The present invention relates to elevator systems.

Patent Literature 1 discloses an elevator system that automatically registers the user's destination floor in an elevator control device and assigns a car number by acquiring user information from an IC card (ID card) with a security gate reader. ing.

JP 2016-056017 A

Security gates using face recognition are beginning to spread.

The present invention provides an elevator system that enables registration of not only a default destination floor but also a changed destination floor when a user passes through a gate using face authentication.

The elevator system of the present invention includes:
An elevator system for setting the destination floor of the user before the user gets on the elevator,
an imaging unit provided so as to be able to capture an image of a user who is about to pass through a gate arranged on a moving route to an elevator hall;
a notification unit that notifies the user;
an information acquisition unit that acquires predetermined information from an information recording medium possessed by the user before passing through the gate;
a face authentication unit that performs face authentication of the user based on the captured image captured by the imaging unit;
a destination floor setting unit for setting the destination floor of the user,
The destination floor setting unit
When the face authentication unit succeeds in the face authentication of the user and the information acquisition unit does not acquire the predetermined information, the default destination floor specified based on the face authentication is used as the destination of the user. set as floor,
In the case where the face authentication unit has successfully authenticated the face of the user and the predetermined information is acquired by the information acquisition unit, the changed destination floor indicated by the predetermined information is set as the destination floor of the user. ,
The information acquisition section includes a first information acquisition section arranged on the left side of the lane at the gate, and a second information acquisition section arranged on the right side.

According to the present invention, it is possible to register not only the default destination floor but also the changed destination floor when the user passes through the gate using face authentication.

Schematic plan view showing equipment arrangement on a specific floor of a building to which the elevator system according to Embodiment 1 is applied Block diagram showing the configuration of the 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 A 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 controller Perspective view showing the appearance of the security gate Schematic plan view showing the appearance of the security gate Block diagram showing the electrical configuration of the security server A diagram showing the configuration of the registered device database (security gate DB) stored in the storage unit of the security server. A diagram showing the configuration of the registration device database (destination floor registration device DB) stored in the storage unit of the security server Diagram showing the structure of the user database stored in the storage unit of the security server A diagram showing an example of display on the display unit of a mobile terminal Flowchart explaining call information signal generation processing by the security server Flowchart explaining call information signal generation processing by the security server Flowchart explaining assignment processing by the group supervisory control device Diagram showing an example of display on the security gate display 1 is a block diagram showing the configuration of an elevator system in a first modified example of the first embodiment; FIG. Block diagram showing the configuration of the elevator system in the second modification of the first embodiment Schematic plan view showing the appearance of a security gate according to Embodiment 2 The figure which showed the structure of the registration apparatus database (security gate DB) in Embodiment 2 Flowchart explaining QR code data reception processing by the security server in Embodiment 3 Flowchart explaining call information signal generation processing by the security server in Embodiment 3

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

(Embodiment 1)
1. Configuration 1-1. Arrangement of Elevators, etc. FIG. 1 is a schematic plan view showing the arrangement of equipment on a specific floor of a building to which an elevator system according to Embodiment 1 is applied. A 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. 1 shows an example in which the elevator system includes six elevators 60A to 60F numbered 1 to 6 (an example of a plurality of elevators). Elevator users board the elevators 60A to 60F from the elevator hall. Hereinafter, elevators 60A to 60F may be referred to as "elevator 60" without distinction.

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

On a specific floor, a plurality of security gates 20 are arranged on the movement route of users 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. Elevator landings are provided in specific areas. The specific area is an area in the building that cannot be entered without passing through the security gate 20 from the entrance side. The specific area includes an elevator hall, a space in each elevator car, and a space on each floor that can be moved using the elevator 60 .

A face authentication area Ad is displayed on the floor on the entrance side of the security gate 20 .

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

The elevator system includes a plurality of elevators 60A to 60F, a group management control device 10 for integrally controlling 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 building security and controls the security gates 20 is connected to the group supervisory control device 10 .

The elevator system employs a destination floor registration method that allows users to register destination floors in advance before boarding a car. The destination floor can be registered, for example, by face authentication at the security gate 20, use of a QR code (registered trademark), manual registration with the destination floor registration device 30, and the like. A QR code is an example of predetermined information. The group supervisory control device 10 assigns a call (destination floor call) related to a destination floor registered before boarding to one of the elevators 60, and uses information indicating the assigned elevator. The information is displayed on the gate display device 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 the specific floor is registered when the user who has passed through the security gate 20 and entered the specific area misses the elevator 60 displayed on the gate indicator 70, or when the user enters a floor other than the default destination floor. It is provided to allow the elevator 60 to be used when moving to the floor.

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

1-2-2. Group Supervisory Controller The group supervisory controller 10 comprehensively controls the operation of the elevators 60A-60F. In addition, the group supervisory control device 10 performs allocation control 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 configured by, for example, a LAN (Local Area Network) such as Ethernet (registered trademark), and transmission and reception of various information between devices are performed according to various protocols such as TCP/IP. Each of the above devices connected to the network is capable of signal transmission (information transmission) by communication according to various protocols such as TCP/IP. It should be noted that each device constituting the elevator system may be connected via a network of another signal format or a dedicated signal network.

The group supervisory 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 programs include programs for realizing various functions of the group supervisory control device 10 of this embodiment.

The control unit 11 is configured using, for example, a CPU, an MPU, and the like. Based on the program read from the storage unit 12, the control unit 11 performs arithmetic processing using various data and the like, thereby realizing various functions of the group supervisory control device 10, which will be described later.

The input/output interface 13 is configured using, for example, a LAN adapter or the like. The input/output interface 13 is an interface for the group supervisory control device 10 to transmit and receive various signals to and from the security server 100, the gate indicator 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 indicator 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40. . 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 of a predetermined format, 11.

1-2-3. Elevator Control Device Elevator control devices 40A-40F are provided corresponding to elevators 60A-60F. The elevator controllers 40A-40F control the operation of the hoisting machines (motors) of the corresponding elevators 60A-60F in accordance with the control signal from the group supervisory controller 10, thereby raising the cars of the elevators 60A-60F. , descent, stop, etc. In addition, the elevator control devices 40A to 40F detect the position of the corresponding elevators 60A to 60F, the traveling direction, the opening and closing of the doors, and the state of the car such as the load, and transmit the information indicating the detected state of the car for group management control. Output to device 10 . It should be noted that hereinafter, the elevator control devices 40A to 40F may be referred to as the "elevator control device 40" without distinguishing between them.

The elevator control device 40 is configured using a computer including a control section, a storage section, an input/output interface, etc., like the group supervisory control device 10 and the like.

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

The destination floor registration device 30 is a device that receives 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 programs include programs for realizing various functions of the destination floor registration device 30 of the present embodiment.

The control unit 31 is configured using, for example, a CPU, an MPU, and the like. Based on the program read from the storage unit 32, the control unit 31 performs arithmetic processing using various data and the like, thereby realizing various functions of the destination floor registration device 30, which will be described later.

The input/output interface 33 is configured using, for example, a LAN adapter or the like. The input/output interface 33 is an interface for transmitting and receiving various signals between the destination floor registration device 30 and the group supervisory 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 supervisory control device 10 . The input/output interface 33 also converts a signal input from the group supervisory control device 10 into a signal in a predetermined format and outputs the signal to the control unit 31 .

The display unit 34 displays an image or the like based on a display signal output from the control unit 31 .

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

The display unit 34 and the operation unit 35 are integrally configured by a touch panel type display device using, for example, a liquid crystal display panel or an organic EL display panel. Note that the display unit 34 and the operation unit 35 may be configured separately using different parts as long as they can be specified in the same way as objects such as buttons displayed on the display unit 34. .

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

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

The face authentication camera 36 captures an image of a subject in a predetermined angle of view area in front of it at a predetermined frame rate and a predetermined resolution, generates image data of the captured image (captured image), and transmits 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 angle-of-view area is set to an angle of view that allows the user's face to be imaged with a size that enables appropriate face authentication when the user is in front of the destination floor registration device 30. . The predetermined resolution may be any resolution at which a face can be detected. For example, the resolution may be HD or FHD. The frame rate may be any rate, such as 15 fps or 30 fps.

FIG. 4 shows an example in which a guide 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 that reads, "Face authentication is available. Please perform face authentication with the upper camera." When the user comes in front of the face authentication camera 36 while the guide screen of FIG. Authentication processing is performed. When face authentication is successful, an operation screen such as that shown in FIG. 5A is displayed. In the operation screen of FIG. 5(a), the message "Please register the destination floor" is displayed on the display unit 34, and the permitted floor linked to the user whose face authentication is successful is displayed in the user database (to be described later). is displayed. In FIG. 5(a), the 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 described later, are displayed. Give an example. Note that the permitted floor is a floor that the user is permitted to use, and is a different floor depending on the user for whom face authentication has succeeded. When any destination floor button is pressed (touched) by the user on the operation screen of FIG. A screen appears. In the assigned car notification screen of FIG. 5(b), a message "10F No. 1 car" is displayed on the display unit 34. FIG.

1-2-5. Security Gate The security gate 20 is a device that controls entry of users to a specific area inside the building. Specifically, the security gate 20 is a device that permits authorized users to enter a specific area inside the building, while restricting unauthorized users from entering. A regular user is a user 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 according to Embodiment 1. As shown in FIG. 7A and 7B are a perspective view and a schematic plan view showing the appearance of the security gate 20, respectively. 7A is a perspective view of the leftmost security gate 20 among the three security gates 20 in FIG.

As shown in FIG. 7A, the gate main body 20a, which is the housing of the security gate 20, has two QR code readers 29, a first sensor 26, a second sensor 27, a gate flapper 28, and a gate indicator. 70 are provided. A face authentication camera 25 is provided on the exit 20e side of the gate body 20a. The face authentication camera 25 may be attached to the gate body 20a or may be provided independently.

The face authentication camera 25 captures an image of a subject in a predetermined field angle area in front thereof at a predetermined frame rate and a predetermined resolution, generates image data of the captured image (captured image), and outputs the image data to the security server 100 . The face authentication camera 25 is an example of an imaging unit. The predetermined angle-of-view area is set to an angle of view that allows the user's face to be imaged in a size that enables appropriate face authentication when the user is in the face-authentication area Ad (see FIG. 1). ing. The predetermined resolution may be any resolution at which a face can be detected. For example, the resolution may be HD or FHD. The frame rate may be any rate, such as 15 fps or 30 fps.

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 has an optical reader (scanner or camera) and a data output section. An optical reader optically reads a QR code held by a user at a position closer than a predetermined distance. The data output unit sends a signal containing image data of the QR code read by the optical reader (hereinafter referred to as "QR code data") and identification information (QR reader ID) of the QR code reader 29 to the security server 100. Send. The QR code to be read may be displayed on the display unit of the mobile terminal 200, or may be printed on paper or the like.

In Embodiment 1, one security gate 20 is provided with two QR code readers 29 on the left and right sides. This makes it compatible with ambidextrous use.

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

The second sensor 27 is composed of, for example, a photoelectric sensor, and detects a user passing through the security gate 20 on the side of the exit 20e of the passage PA. When detecting the user, the second sensor 27 outputs a detection signal to the security server 100 via the control section 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 supervisory control device 10 . The gate indicator 70 is an example of a notification unit that notifies the user. For example, when the gate display 70 receives the assignment result signal output from the group supervisory control device 10, it displays an assigned elevator notification screen for notifying the name of the assigned elevator (assigned elevator).

As shown in FIG. 6, the gate main body 20a accommodates a control section 21, a storage section 22, an input/output interface 23, and the like.

The storage unit 22 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 gate 20 in this embodiment.

The input/output interface 23 is configured using, for example, a LAN adapter or the like. The input/output interface 23 is an interface for transmitting and receiving various signals between the security gate 20 and 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 . The input/output interface 23 also 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, and 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 the programs stored in the storage unit 22. FIG.

The control unit 21 opens and closes the gate flapper 28 based on the detection signals from the first sensor 26 and the second sensor 27 and the open and close signals 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 .

As shown in FIG. 7B, in Embodiment 1, as the three security gates 20, security gates 20A, 20B, and 20C are provided in order from the left side. The security gates 20A, 20B, 20C are respectively face authentication cameras 25A, 25B, 25C (face authentication cameras 25), lanes 50A, 50B, 50C, and gate indicators 70A, 70B, 70C (gate indicators 70). and Hereinafter, lanes 50A, 50B, and 50C may be referred to as "lane 50" without distinction.

Lanes 50A, 50B, 50C are defined as spaces for users to pass through security gates 20A, 20B, 20C, respectively. A "lane ID" is set as information for specifying the lanes 50A, 50B, and 50C. As shown in FIG. 7B, lane ID1, lane ID2, and lane ID3 are assigned to lanes 50A, 50B, and 50C, respectively.

Similarly, "display device ID" is set as information for specifying the gate displays 70A, 70B, and 70C. The gate indicators 70A, 70B, and 70C are assigned indicator ID1, indicator ID2, and indicator ID3, respectively.

Each of the gate displays 70A to 70C and the face authentication cameras 25A, 25B, and 25C are provided, while the QR code reader 29 is provided in total of four units according to the dominant hand of the user. ing. As shown in FIG. 7B, four QR code readers 29A, 29B, 29C, and 29D are arranged in order from the left.

QR code readers 29A and 29B are provided corresponding to security gate 20A. Similarly, QR code readers 29B and 29C are provided corresponding to security gate 20B, and QR code readers 29C and 29D are provided corresponding to security gate 20C.

The second QR code reader 29B from the left is shared by the two left and right security gates 20A and 20B. Similarly, the second QR code reader 29C from the right is shared by the two left and right security gates 20B and 20C.

According to the above configuration, the user can use both the left QR code reader 29 and the right QR code reader 29 when using each of the lanes 50A to 50C. Specifically, in lane 50A, the QR code reader 29A on the left and the QR code reader 29B on the right can be used. The same applies to other lanes 50B and 50C. For example, a right-handed user can use the QR code reader 29 on the right side, and a left-handed user can use the QR code reader 29 on the left side. can be done. This makes it possible to accommodate ambidexters and improve convenience for the user.

Here, when the QR code is read by the QR code reader 29, not only the QR code of the user whose face was imaged, but also the QR code of the next user who is going to pass through the same lane 50. is assumed. In addition, since the QR code readers 29B and 29C are shared by the two security gates 20 on the left and right sides, the QR code may be read by another user passing through the adjacent lane 50. FIG. In the elevator system of Embodiment 1, the QR code data read by the QR code reader 29 is used to identify whether the QR code is held up by the user who has performed face imaging/face authentication. It is determined whether or not the person ID matches the user ID associated with the user's face data imaged by the face authentication camera 25 . Detailed processing will be described later.

1-2-6. Security Server The security server 100 performs face authentication processing for users to ensure security in the building, based on captured images indicated by image data output from the face authentication cameras 25 and 36 . For example, the security server 100 performs face detection processing on the captured image, and when a face is detected, further performs facial feature point detection processing. Then, when facial feature points are detected from the captured image, the data of the detected facial feature points (face data) and the facial feature point data (face data) of each user registered in the user DB are sequentially compared ( matching) to obtain the matching 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 face data (facial feature point data) of the detected face is registered in the user DB. That is, it is determined whether or not face data having a matching rate equal to or higher than a predetermined matching rate with respect to the face data of the detected face is registered in the user DB. Then, when face data having a matching rate equal to or higher than a predetermined matching rate is registered in the user DB, the user who is going to pass through the security gate 20 (a user whose face has been detected) is Identify the corresponding user and determine that the face authentication was successful. It should be noted that it is preferable that the predetermined match rate is set to a high match rate that cannot be reached by other people. Thereby, face authentication can be performed appropriately. Note that face detection processing, face feature point detection processing, and matching processing (authentication processing) can be performed using various known methods.

In addition, 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 destination floor of the user and outputs it to the group supervisory control device 10 . A user ID is an example of user identification information.

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

The storage unit 102 is configured using, for example, a RAM, ROM, HDD, SSD, etc., and stores programs and various data. The programs include programs for implementing 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, and 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 the program read from the storage unit 102. FIG.

The input/output interface 103 is configured using, for example, a LAN adapter or the like. The input/output interface 103 is an interface for transmitting and receiving various signals between the security server 100 and the face authentication camera 25 , the QR code reader 29 , the group 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 outputs it to the face authentication camera 25, the QR code reader 29, the face authentication camera 36, the group control device 10, and the security gate. 20. The input/output interface 103 converts signals input from the face recognition camera 25, QR code reader 29, face recognition camera 36, group control device 10, and security gate 20 into signals of a predetermined format. Output to the control unit 101 .

9A and 9B are diagrams showing the configuration of the registered device DB stored in the storage unit 102 of the security server 100. FIG. FIG. 9A is a registration device DB (hereinafter also referred to as a "security gate DB") relating to the security gate 20 as a registration device, and FIG. 9B is a registration device DB (hereinafter referred to as a registration device DB) relating to the destination floor registration device 30 as a registration device. Also referred to as a “destination floor registration device DB”). The registered device DB stores the installation floor of the registered device and other information in association with the lane ID/registered device ID. The registration device here is a general term for the security gate 20 and the destination floor registration device 30 that are used to register the user's destination floor.

In the security gate DB shown in FIG. 9A, "lane ID" is information for identifying the lane 50 of each security gate 20. FIG. Lane ID "1" identifies the left lane 50A in the configuration shown in FIG. 7B, lane ID "2" identifies the center lane 50B, and lane ID "3" identifies the right lane 50C. Identify.

"Installation floor" is information indicating the floor on which the security gate 20 corresponding to the lane ID is installed. The installation floor is used as a departure floor for users using the security gate 20 . In the later-described "call information signal", the "installation floor" is referred to as the "departure floor". As in the example shown in FIG. 9A, when the security gate 20 is installed only on one floor, the installation floor information in the registration device DB may be omitted.

The “display device ID” is information for identifying the gate display device 70 corresponding to the lane ID. In the configuration shown in FIG. 7B, the indicator ID "1" identifies the left gate indicator 70A, the indicator ID "2" identifies the central gate indicator 70B, and the indicator ID "3". identifies the right gate indicator 70C.

"QR reader ID" is information for identifying the QR code reader 29 corresponding to the lane ID. QR reader ID "1" specifies the leftmost QR code reader 29A in the configuration shown in FIG. 7B, QR reader ID "2" specifies the second QR code reader 29B from the left, ID "3" identifies the second QR code reader 29C from the right, and QR reader ID "4" identifies the rightmost QR code reader 29D.

In the example shown in FIG. 9A, two QR reader IDs "1 and 2" are stored corresponding to lane ID "1". This is because, in the configuration shown in FIG. 7B, two left and right QR code readers 29A and 29B (QR reader IDs "1 and 2") are provided in the left lane 50A (lane ID "1"). means. The same applies to other lane IDs and QR reader IDs.

In the destination floor registration device DB shown in FIG. 9B , “registration device ID” is information for identifying the destination floor registration device 30 .

"Installation floor" is information indicating the floor on which the destination floor registration device 30 corresponding to the registration device ID is installed.

"Location" is information indicating the position where the destination floor registration device 30 corresponding to the registration device ID is installed within the installation floor. Locations are indicated by serial numbers such as "1", "2", "3", and so on for each installation floor.

In the example shown in FIG. 9B, "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, the installation floor and location information are registered in association with the registered device IDs.

FIG. 10 is a diagram showing the configuration of the user DB stored in the storage unit 102 of the security server 100. As shown in FIG. The user DB records face data, default destination floors, and permitted floors in association with user IDs. A password may be further recorded in association with the user ID. Registration of such information in the user DB is performed by, for example, a building manager.

“User ID” is identification information (user identification information) set to uniquely identify a user.

“Face data” is facial feature point data indicating facial features of the user identified by the “user ID”. The facial feature point data is, for example, data indicating the features of the position and shape of the eyes, nose, mouth, and the like. The facial feature point data is generated based on the facial image of the user 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 "user ID". As the default destination floor, for example, the numerical value of the floor where the user resides is set. It is also possible not to set the "default destination floor" as desired by the user. In this case, the symbol "-" is set as the default destination floor. The symbol "-" is an example of destination floor unset information.

"Permitted floor" is information indicating a floor that the user identified by the "user ID" is permitted to use. For example, a common floor in a building is set as the permitted floor.

In the example shown in FIG. 10, "face data 1", "10", and "9, 10, 11" are registered as face data, default destination floors, and permitted floors in association with user ID "10001". It is "Face data 2", "8", and "7, 8" are registered as face data, default destination floors, and permitted floors in association with user ID "10002". "Face data 3", "13", and "12, 13" are registered as face data, default destination floors, and permitted floors in association with user ID "10003". "Face data 4", "-", and "9, 10, 11" are registered as face data, default destination floors, and permitted floors in association with user ID "10004". The symbol "-" in the default destination floor is destination floor unset information indicating that the default destination floor is not set. Similarly, for the remaining user IDs, face data, default destination floors, and permitted floor information are registered in association with user IDs.

1-2-7. Portable Terminal The portable terminal 200 is configured by 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 smart phone or a tablet computer. A destination floor setting application is installed in the storage unit of the mobile terminal 200 . The destination floor setting application is used to generate a QR code when a destination floor other than the default destination floor (changed destination floor) is registered in the elevator system when the user uses the elevator.

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

When the user activates the destination floor setting application on the mobile terminal 200, the display unit 210 of the mobile terminal 200 displays the destination floor setting screen shown in FIG. 11(a). A destination floor input frame Fi, a QR code generation button Bi, and the like are displayed on the destination floor setting screen. When the user inputs the destination floor in the destination floor input frame Fi and touches the QR code generation button Bi, a QR code is generated and displayed on the display unit 210 of the mobile terminal 200, for example, as shown in FIG. A QR code display screen displaying the code Cd is displayed. The QR code Cd stores information indicating the destination floor entered in the destination floor input box Fi and information indicating the user ID stored in the storage unit.

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

When the security server 100 detects facial feature points from the captured image, the security server 100 sequentially compares (collates) the data of the detected facial feature points with each face data (facial feature point data) registered in the user DB. Find percent match. 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 face data (facial feature point data) of the detected face is registered in the user DB. Then, when face data having a matching rate equal to or higher than a predetermined matching rate is registered in the user DB, the security server 100 allows the user who is going to pass through the security gate 20 (the user whose face has been detected) to register. The user is identified as the user corresponding to the identified face data, and it is determined that the face authentication has succeeded. In this case, the security server 100 transmits an opening signal to the security gate 20 concerned. As a result, users registered in the user DB can pass through the security gate 20 .

On the other hand, if face data (facial feature point data) having a matching rate equal to or higher than a predetermined matching rate does not exist in the user DB, the security server 100 determines that the user who is about to pass through the security gate 20 It is determined that the user is not registered with In this case, the security server 100 transmits a closing signal to the security gate 20 concerned. The controller 21 of the security gate 20 closes the gate flapper 28 . This prevents users who are not registered in the user DB from passing through the security gate 20 . In other words, it is possible to prevent a user who is not registered in the user DB from passing through the security gate 20 .

Note that the control unit 21 of the security gate 20 receives neither an open signal nor a closed signal from the security server 100, that is, in a state in which face authentication processing has not been completed. When detected, the gate flapper 28 is closed. This prevents a user who has not completed the face authentication process from passing through the security gate 20 .

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

2-1-2. Machine allocation process 2-1-2-1. Destination floor setting processing and car number allocation processing when using the security gate In face authentication processing for a user who is about to pass through the security gate 20, if the user is determined to be a user registered in the user DB, the security The server 100 determines whether or not the QR code data is received from the QR code reader 29 within a predetermined time T (seconds) after face authentication, and determines the default destination floor or the changed destination floor as the user's destination floor. setting, generates a call information signal including information such as departure floor, display ID, destination floor, etc., and transmits the call information signal to the group supervisory control device 10; The "departure floor" in the call information signal is equal to the "installation floor" of the registration device as described above.

Upon receiving the call information signal from the security server 100, the group supervisory control device 10 determines the assigned car to which the destination floor of the user is assigned based on the received call information signal, and sends an assignment result signal indicating the decided assigned car. , to the gate indicator 70 located at the departure floor and indicator ID indicated by the call information signal.

When receiving the allocation result signal from the group supervisory control device 10, the gate display 70 displays the allocated car notification screen.

More detailed destination floor setting processing and elevator number allocation processing will be described later.

2-1-2-2. Destination floor setting processing and car number allocation 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, and the user is registered in the user DB. When it is determined that the user is a user, the information on the default destination floor and permitted floor associated with the user is read from the user DB, and the face authentication camera 36 installed in the destination floor registration device 30 is registered. Based on the device ID, the installation floor and location information are read from the registered device DB, the default destination floor and permitted floor information read from the user DB, and the installation floor (departure floor) and location information read from the registered device DB. etc., and transmits the call information signal to the group supervisory control device 10 .

Upon receiving the call information signal from the security server 100, the group supervisory control device 10 generates a reception permission signal including at least information on the permitted floor based on the received call information signal, and determines the departure floor and location indicated by the call information signal. is transmitted to the destination floor registration device 30 located in the .

Upon receiving the acceptance 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 receives the designation operation of the destination floor by the user. When a destination floor designation operation is performed, the destination floor registration device 30 transmits an allocation request signal to the group supervisory control device 10 requesting allocation of any car to the designated destination floor.

Upon receiving the allocation request signal, the group supervisory control device 10 determines the allocated car to which the destination floor of the user is allocated, and places the allocation result signal indicating the determined allocated car at the departure floor and location indicated by the call information signal. is transmitted to the destination floor registration device 30.

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

2-1-3. Specific Operation of Elevator System Destination floor setting processing and elevator number allocation processing when a user uses the security gate 20 will be described in more detail with reference to flowcharts.

12A and 12B are flowcharts for explaining the call information signal generation processing by the security server 100. FIG. The processing of this flowchart is executed for each security gate 20 . In addition, processing for each security gate 20 is executed in parallel.

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

If the captured image does not include a face (NO in S11), the control unit 101 of the security server 100 makes the determination in step S11 again.

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

If face data having a matching rate equal to or higher than a predetermined matching 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 controller 21 of the security gate 20 controls the gate flapper 28 to keep it closed.

When face data having a matching rate equal to or higher than a predetermined matching 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 from the user DB the user ID associated with face data with a predetermined matching rate or more (S15).

The control unit 101 of the security server 100 identifies the lane ID of the lane 50 in which the user is imaged (S16). As shown in FIG. 7B, since the face authentication cameras 25A to 25C are provided corresponding to the respective lanes 50A to 50C, any face authentication camera 25 out of the three face authentication cameras 25A to 25C Based on whether the user's face is captured, the lane ID of the lane 50 in which the user is captured can be identified.

The control unit 101 of the security server 100 acquires QR reader IDs linked to the lane IDs acquired in step S16, and sets them as qrD1 and qrD2 (S17). Specifically, with reference to the security gate DB shown in FIG. 9A, two QR reader IDs corresponding to the lane ID obtained in step S16 are obtained and designated as qrD1 and qrD2, respectively.

The control unit 101 of the security server 100 determines whether or not the QR code data has been acquired from the QR code reader 29 of qrD1 (S18). Thereby, for example, it is determined whether or not the QR code data is acquired from the QR code reader 29 installed on the left side of the lane 50 through which the user is going to pass. The QR code data includes at least information on the user ID and the changed destination floor.

If the QR code data is not acquired from the QR code reader 29 of qrD1 (NO in S18), the control unit 101 of the security server 100 determines whether or not the QR code data is acquired from the QR code reader 29 of qrD2 (S19 ). Thereby, for example, it is determined whether or not the QR code data is acquired from the QR code reader 29 installed on the right side of the lane 50 through which the user is going to pass.

If the QR code data is not acquired from the QR code reader 29 of qrD2 (NO in S19), the control unit 101 of the security server 100 determines whether a predetermined time T (seconds) has passed since the face authentication time tc (S20). . The predetermined time T (seconds) is set to a value obtained by adding a small extra time to the standard time from when the user performs face authentication to when the QR code is read. ).

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

When the QR code data is acquired from the QR code reader 29 of qrD1 (YES in S18), the control unit 101 of the security server 100 determines that the user ID included in the QR code data is the user ID linked to the face data. It is determined whether or not the ID matches (S21). Specifically, it is determined whether or not the user ID included in the QR code data acquired in step S18 matches the user ID linked to the face data acquired in step S15. As a result, it can be determined whether or not the user whose face is imaged by the face authentication camera 25 and the user who holds the QR code over the QR code reader 29 are the same person.

When the two user IDs do not match (NO in S21), that is, when the QR code read by the QR code reader 29 of qrD1 is the QR code held up by the next user in the same lane 50 or in the next lane 50, the control unit 101 of the security server 100 shifts to the process of step S19.

Similarly, when QR code data is acquired from the QR code reader 29 of qrD2 (YES in S19), the control unit 101 of the security server 100 associates the user ID included in the QR code data with the face data. It is determined whether or not it matches the user ID obtained (S22). Specifically, it is determined whether or not the user ID included in the QR code data acquired in step S19 matches the user ID linked to the face data acquired in step S15. When it is determined that the two user IDs do not match (NO in S22), that is, when the QR code read by the QR code reader 29 of qrD2 is the QR code held by the next user in the same lane 50, or If another user of the adjacent lane 50 holds the card over the card, the control unit 101 of the security server 100 proceeds to the process of step S20.

If it is determined that the user IDs match in step S21 (YES in S21), or if it is determined that the user IDs match in step S22 (YES in S22), the control unit 101 of the security server 100 A floor change flag is set to ON (S23). That is, when the user whose face is imaged by the face authentication camera 25 and the user who holds the QR code over the QR code reader 29 can be determined to be the same person based on the user ID, the user is associated with the face data. Instead of the default destination floor that has been set, the process proceeds to the processing of setting the changed destination floor included in the QR code data as the destination floor.

If the QR code data is not acquired from the QR code readers 29 of qrD1 and qrD2 (NO in S18, NO in S19), or if the two user IDs do not match even if the QR code data is acquired (NO in S21, NO in S22), the control unit 101 of the security server 100 repeatedly executes the processes of steps S18 to S20.

When T seconds have elapsed since the face authentication time tc without making a determination of YES in steps S21 and S22 (YES in S20), the control unit 101 of the security server 100 sets the destination floor change flag to OFF (S24). . As a result, the processing proceeds to set the default destination floor linked to the face data as the destination floor.

That is, if the two user IDs do not match even if the QR code data is acquired by the QR code reader 29 of either qrD1 or qrD2 (NO in S21, NO in S22), the user whose face has been authenticated is not the QR code held up by the user, and the changed destination floor included in the QR code data is not set as the destination floor of the user who has undergone face authentication, and is temporarily defaulted as the destination floor of the user. Maintain destination floor.

When the destination floor setting flag is set to ON in step S23, as shown in FIG. Acquired from DB (S31).

The control unit 101 of the security server 100 identifies the installation floor and display device ID of the security gate 20 through which the user is going to pass based on the lane ID of the security gate 20 identified in step S16 (S32). This also identifies the user's departure floor.

The control unit 101 of the security server 100 sets the changed destination floor included in the QR code data acquired in step S18 or step S19 as the user's destination floor (S33).

The control unit 101 of the security server 100 generates a call information signal including information on the departure floor, the changed destination floor, the permitted floor, the display device ID, and the destination floor change flag ON, and transmits the call information signal to the group supervisory control device 10 (S34). .

The control unit 101 of the security server 100 determines whether or not a user passage signal has been received from the security gate 20 (S35).

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

When the user passage signal is received from the security gate 20 (YES in S35), the controller 101 of the security server 100 transmits a closing signal to the security gate 20 (S36).

On the other hand, when the destination floor setting flag is set to OFF in step S24, the control unit 101 of the security server 100 acquires from the user DB the default destination floor linked to face data having a matching rate equal to or higher than a predetermined matching rate. (S37).

The control unit 101 of the security server 100 identifies the installation floor and display device ID of the security gate 20 through which the user is going to pass based on the lane ID of the security gate 20 (S38). This also identifies the user's departure floor.

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

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

It should be noted that determination of NO in steps S21 and S22 also means that subsequent face authentication of the user has not been completed. At the same time, for example, a message saying, "Since face recognition has not been completed for the customer who has just been held over the QR code, please start again from face recognition" is voiced from a speaker separately provided at the security gate 20 or the like. may be notified.

FIG. 13 is a flow chart for explaining allocation processing by the group supervisory control device 10. As shown in FIG. The processing of this flowchart is executed when the group supervisory control device 10 receives a call information signal for 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.

When the group supervisory control device 10 receives the call information signal from the security server 100, it starts the processing of the flowchart of FIG. 13 and acquires various information contained in the call information signal (S51).

The group supervisory control device 10 determines whether or not 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 supervisory control device 10 determines whether or not the destination floor to be changed actually exists (S53).

If the changed destination floor is an existing floor (YES in S53), the group supervisory control device 10 determines whether or not the changed destination floor is included in the permitted floors (S54).

If the change destination floor is included in the permitted floors (YES in S54), the group supervisory control device 10 assigns the departure floor and change destination floor indicated by the call information signal to one of the elevators (S55).

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

FIG. 14 is a diagram showing a display example on the gate indicator 70 of the security gate 20. As shown in FIG. FIG. 14(a) is a diagram showing an example of an assigned car notification screen. In the example of FIG. 14(a), "4F No. 1" is displayed to indicate that No. 1 has been assigned to the 4th floor of the destination floor. In addition, as shown in FIG. 14(e), it is also possible to more carefully display the content of "4F No. 1. Destination floor 4F has been read."

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 supervisory control device 10 registers the default destination floor value in the call information signal. (S57).

If the value of the default destination floor is registered (YES in S57), the group supervisory 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 supervisory control device 10 transmits a signal indicating the allocation result to the gate indicator 70 of the departure floor and indicator ID indicated by the call information signal (S59). At this time, the assigned car notification screen is displayed on the gate display 70 . The display contents are the same as those in FIGS. 14(a) and 14(e).

If the value of the default destination floor is not registered (NO in S57), that is, if the symbol "-" (floor unset information) is registered as the default destination floor in the user DB, the group supervisory control device 10 , to the gate indicator 70 of the departure floor and indicator ID indicated by the call information, to display a signal prompting the destination floor registration device 30 to register the destination floor (S60). At this time, a screen prompting the registration of the destination floor is displayed on the gate display 70 . FIG. 14(d) is a diagram showing an example of a screen prompting registration of a destination floor. In the example of FIG. 14(d), "Please register the destination floor with the destination floor registration device in the elevator hall." is displayed. The situation in which the destination floor is registered by the destination floor registration device 30 is, for example, when a user who frequently visits a plurality of permitted floors does not dare to set the default destination floor, or when the destination floor is changed. This occurs when the portable terminal 200 is forgotten.

In step S53, if the destination floor to be changed does not actually exist (NO in S53), the group supervisory control device 10 causes the call information signal to display a signal to notify that the destination floor to be changed does not actually exist. It is transmitted to the gate indicator 70 of the departure floor and indicator ID (S61). At this time, the gate display 70 displays a screen notifying that the changed destination floor does not actually exist. FIG. 14(b) is a diagram showing an example of a screen notifying that the changed destination floor does not actually exist. In the example of FIG. 14(b), "Destination floor 99 has been read. The 99th floor does not exist." is displayed. In addition, on the screen of FIG. 14(b), the same content as the display content of FIG. 14(d) "Please register the destination floor with the destination floor registration device in the elevator hall." may

In the above step S54, if the destination floor to be changed is not included in the permitted floors (NO in S54), the group supervisory control device 10 outputs a signal for displaying a notification that the destination floor to be changed is not a permitted floor. It is transmitted to the gate indicator 70 of the departure floor and indicator ID indicated by the signal (S62). At this time, the gate display 70 displays a screen notifying that the changed destination floor is not the permitted floor. FIG. 14(c) is a diagram showing an example of a screen notifying that the changed destination floor is not a permitted floor. In the example of FIG. 14(c), the message "Destination floor 12 has been read. The 12th floor is not permitted." In addition, on the screen of FIG. 14(b), the same content as the display content of FIG. 14(d) "Please register the destination floor with the destination floor registration device in the elevator hall." may

3. Effect of this Embodiment In the elevator system of this embodiment, the face of the user who is about to pass through the security gate 20 is authenticated based on the image captured by the face authentication camera 25 . Further, if the QR code is not read by the QR code reader 29 within a predetermined time T (seconds) after the face authentication is successful, the default destination floor associated with the user in advance is the user's destination. If the QR code is read by the QR code reader 29 within a predetermined time T (seconds) after the face authentication is successful, the changed destination floor indicated by the QR code is set as the user's destination floor. set. Therefore, when a user passes through a gate that uses face authentication, it is possible to register not only the default destination floor but also the changed destination floor.

Furthermore, in this embodiment, as shown in FIG. 7B, by installing two QR code readers 29 on the left and right in one lane 50, ambidextrousity is accommodated. In addition, when the QR code is read by the QR code reader 29, the user ID included in the QR code data acquired by the QR code reader 29 is used to identify that the QR code is from a user who has performed face authentication. Then, it is determined whether or not the user ID associated with the face data captured by the face authentication camera 25 matches. As a result, after confirming the identity of the user when the two user IDs match, the changed destination floor included in the QR code data that is judged to have been held by the user who performed face authentication is used. set as the destination floor for passengers. If the identity cannot be confirmed, control is performed so that the changed destination floor is not set as the user's destination floor. In this way, it is possible to prevent the registration of the destination floor while accommodating ambidexters.

In the first embodiment, the security server 100 analyzes the QR code data output from the QR code reader 29 and acquires the user ID and the changed destination floor, but the present invention is limited to this. not. In the present invention, the group supervisory control device 10 or another analysis device may analyze the QR code data output from the QR code reader 29 to acquire the user ID and the changed destination floor. Below, the 1st modification of Embodiment 1 and the 2nd modification are demonstrated.

(First Modification of Embodiment 1)
In the first modification of Embodiment 1, an example will be described in which the group supervisory control device 10 analyzes the QR code data output from the QR code reader 29 and acquires the user ID and the changed destination floor.

15 is a block diagram showing the system configuration of the elevator system in the first modified example of the first embodiment; FIG.

In the first modification of Embodiment 1, each QR code reader 29 is connected to the group supervisory control device 10 and outputs QR code data to the group supervisory control device 10 . Then, the group supervisory control device 10 analyzes the QR code data output from the QR code reader 29 and acquires the user ID and the changed destination floor.

According to this modification, the same effects as in the first embodiment 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 supervisory control device 10, there is no need to perform the processing in the security server 100, and specification changes to the security server 100 can be suppressed as much as possible. .

(Second Modification of Embodiment 1)
In the second modification of the first embodiment, a QR code analysis device provided separately from the security server 100 and the group supervisory control device 10 analyzes the QR code data output from the QR code reader 29 and uses it. An example of acquiring a person ID and a changed destination floor will be described.

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

The QR code analysis device 300 is composed of a computer having a control section, a storage section, an input/output interface, etc., like the group supervisory control device 10 and the like. The QR code reader 29 outputs the read QR code data to the QR code analysis device 300 . The QR code analysis device 300 analyzes (decodes) the QR code data output from the QR code reader 29, acquires the user ID and the changed destination floor from the QR code data, and converts the acquired user ID and The changed destination floor and information specifying the QR code reader 29 from which the QR code data is output are transmitted to the group supervisory control device 10 . As the information specifying the QR code reader 29, for example, the installation floor of the security gate 20 where the QR code reader 29 is located and the information of the QR reader ID/lane ID are used. The information specifying the QR code reader 29 may be the serial number of the QR code reader 29 or the like.

According to this modification, the same effects as in the first embodiment 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 supervisory control device 10, there is no need to perform the processing in the security server 100, and specification changes to the security server 100 can be suppressed as much as possible. . In addition, the group supervisory control device 100 does not need to analyze the QR code data.

(Embodiment 2)
In Embodiment 2, in addition to providing two QR code readers 29 in one lane 50, an example in which two gate indicators 70 are provided will be described.

FIG. 17 is a block diagram showing the system configuration of the elevator system according to Embodiment 2. FIG.

As shown in FIG. 17, two gate indicators 70 are provided for each lane 50A, 50B, 50C. Specifically, two left and right gate indicators 70D and 70E are provided corresponding to the left lane 50A, and two left and right gate indicators 70F and 70G are provided corresponding to the center lane 50B. Two left and right gate indicators 70H and 70I are provided corresponding to the right lane 50C.

Although the two gate indicators 70D and 70E provided corresponding to the lane 50A are physically separated, they are interlocked and controlled to display the same content. The same applies to the two gate indicators 70F and 70G provided corresponding to the lane 50B, and the two gate indicators 70H and 70I provided corresponding to the lane 50C.

As shown in FIG. 17, the gate display 70D is provided in the same housing as the QR code reader 29A, and the gate displays 70E and 70F are provided in the same housing as the QR code reader 29B. The displays 70G and 70H are provided in the same housing as the QR code reader 29C, and the gate display 70I is provided in the same housing as the QR code reader 29D.

Although the gate indicators 70E and 70F are provided adjacent to each other in the same housing, they correspond to different lanes 50, so the display contents are not interlocked. The same applies to the gate indicators 70G and 70H.

According to the above configuration, when the user passes through a certain lane 50, the left and right QR code readers 29 can be used, and the left and right gate indicators 70 can be used to confirm the allocation result of the elevator 60 and the like. be able to. As a result, the device (QR code reader 29) used for changing the destination floor and the device (gate display device 70) used for confirmation work such as allocation results can be selectively used according to the user's dominant hand and preference. The user's convenience can be further improved.

In order to distinguish between the six gate indicators 70D-70I, an indicator ID is assigned to each of the gate indicators 70D-70I. In the example shown in FIG. 17, as indicated by underlined numbers, the gate indicator 70D is assigned the indicator ID "1", the gate indicator 70E is assigned the indicator ID "2", and the gate indicator 70F is assigned. is assigned the indicator ID "3", the gate indicator 70G is assigned the indicator ID "4", the gate indicator 70H is assigned the indicator ID "5", and the gate indicator 70I is assigned the indicator ID " 6" is assigned.

FIG. 18 is a diagram showing the configuration of a security gate DB according to the second embodiment. As shown in FIG. 18, two indicator IDs are stored in association with one lane ID. In the example shown in FIG. 18, display device IDs "1, 2" are stored corresponding to lane ID "1". This means that in the configuration shown in FIG. 17, two gate indicators 70D and 70E are provided correspondingly to the left lane 50A. Similarly, display device IDs "3, 4" are stored corresponding to lane ID "2", and display device IDs "5, 6" are stored corresponding to lane ID "3".

The security server 100 and the group supervisory control device 10 of the second embodiment may use the configurations shown in FIGS. 17 and 18 and perform the same processing as in the first embodiment. Specifically, the security server 100 executes the processing of the flow shown in FIGS. 12A and 12B, and the group supervisory control device 10 executes the processing of the flow shown in FIG.

In the flow shown in FIG. 12B, the security server 100 refers to the security gate DB shown in FIG. Identify two indicator IDs corresponding to the lane ID. Further, when the security server 100 generates the call information signal and transmits it to the group supervisory control device 10 (S34, S40), the security server 100 generates the call information signal including the two indicator IDs specified in steps S32 and S38. It is transmitted to the group supervisory control device 10 .

In the flow shown in FIG. 13, the group supervisory control device 10 transmits a predetermined signal to the gate indicator 70 of the departure floor and indicator ID indicated by the call information signal (S56, S59, S60, S61, S62). , to the two gate indicators 70 corresponding to the two indicator IDs included in the call information signal. As a result, display instruction signals are transmitted to the two gate displays 70 on the left and right of the lane 50 through which the user is to pass.

The two left and right gate displays 70 that have received the predetermined signal display information such as the allocation result in conjunction. As a result, the user can check the allocation results and the like using the two gate displays 70 on the left and right, and in addition to being able to use the QR code readers 29 on the left and right, convenience can be further improved. can.

The display contents of the two gate displays 70 on the left and right may be the same, or may be different while at least part of the information overlaps, and may be interlocked by any display method.

(Embodiment 3)
In Embodiments 1 and 2, it is assumed that the QR code is obtained by the QR code reader 29 after the face is imaged by the face authentication camera 25 and face authentication is performed. A case is assumed in which the order of face imaging/face authentication and QR code acquisition does not matter.

The device configuration in Embodiment 3 is the same as the device configuration in Embodiment 1, as shown in FIGS. 1 to 11. FIG.

FIG. 19 is a flow chart for explaining QR code data reception processing by the security server 100 .

The control unit 101 of the security server 100 determines whether or not the QR code data has been received (S71). Specifically, in the configuration shown in FIG. 7B, it is determined whether or not QR code data has been received by any of the four QR code readers 29A to 29D. If the QR code data is not received (NO in S71), the control unit 101 of the security server 100 executes the process of step S71 again.

If the QR code data has been received (YES in S71), the control unit 101 of the security server 100 acquires the user ID and destination floor (changed destination floor) from the QR code data acquired in step S71, and sets the variable id, A variable d is set (S72). At this time, variable id=user ID and variable d=destination floor (changed destination floor).

The control unit 101 of the security server 100 sets the variable QRData (S73). At this time, based on the variable id (user ID) and the variable d (changed destination floor) set in step S72, the variable QRData[id]=d.

FIG. 20 is a flow chart illustrating call information signal generation processing including face image data reception processing by the security server 100 . The security server 100 executes the processing of the flow shown in FIG. 19 and the processing of the flow shown in FIG. 20 in parallel.

In the flowchart of FIG. 20, steps S81 to S83 are provided instead of steps S15, S17 to S19, S21, and S22 of the flowchart of FIG. 12A of the first embodiment.

Specifically, after executing steps S11 to S14 in the same manner as in Embodiment 1, the security server 100 acquires from the user DB the user ID associated with face data having a matching rate equal to or higher than a predetermined matching rate. (S81). At this time, the variable userID=user ID is set.

After executing step S16, the security server 100 determines whether the destination floor is set in the variable QRData[userID] (S82). If the variable QRData[id] is set in step S73 of the flowchart shown in FIG. to decide.

If the destination floor is not set in the variable QRData[userID] (NO in S82), that is, the user having the user ID based on the facial data acquired in step S81 reads the QR code (same (including the user ID) is not read, it is determined whether or not T seconds have passed since the face authentication time tc (S20), as in the first embodiment. If T seconds have not passed since the face authentication time tc (NO in S20), the control unit 101 of the security server 100 executes the process of step S82 again.

If the destination floor is set in the variable QRData[userID] (YES in S82), that is, the user having the user ID based on the facial data acquired in step S81 reads the QR code (same (including user ID)), the control unit 101 of the security server 100 clears the value of the variable QRData [userID] (S83) and sets the destination floor change flag to ON (S23).

The processing after the destination floor change flag is set to ON is as shown in FIG. 12B, as in the first embodiment. As a result, the changed destination floor included in the QR code data is set as the destination floor (S33), and a call information signal including information on the changed destination floor is generated and transmitted to the group supervisory control device 10 (S34).

If the destination floor is not set in the variable QRData[userID] (NO at S82) and T seconds have passed since the face authentication time tc (YES at S20), the control unit 101 of the security server 100 sets the destination floor change flag. It is set to OFF (S24).

The process after setting the destination floor change flag to OFF is as shown in FIG. 12B, as in the first embodiment. As a result, the default destination floor is set as the destination floor (S39), and a call information signal including information on the default destination floor is generated and transmitted to the group supervisory control device 10 (S40).

According to the above flow, by executing the processing shown in FIG. 19 and the processing shown in FIG. Destination floor change processing can be performed regardless of the order of acquisition processing. Specifically, when the QR code data including the same user ID has already been acquired at the time when the face authentication is successful (YES in S12) (YES in S82), the changed destination floor is immediately set as the destination floor. Set (S23). Even if QR code data has not been acquired at the time when face recognition is successful (NO at S82), QR code data including the same user ID is retrieved within T seconds from face recognition time tc (NO at S20). is acquired (YES in S82), the changed destination floor is set as the destination floor (S23).

(Other embodiments)
In Embodiments 1 and 3, in step S20 of FIG. 12A and FIG. 20, it is determined whether or not T seconds have passed since the face authentication time tc. may be used to determine whether the user has been detected. That is, it may be determined whether or not the user is in the process of passing through the security gate 20 . In this case, when the user is detected by the first sensor 26 of the security gate 20, the processes after step S24 are immediately executed. In other words, a call information signal is immediately generated and transmitted to the group supervisory control device 10, and allocation processing is executed. Therefore, the user can be assigned an elevator without waiting for the predetermined time T (seconds) to elapse. On the other hand, if the user is not detected by the first sensor 26 of the security gate 20, the process returns to step S18.

In each of the above-described embodiments and modifications, 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 face authentication. Although an example of processing has been described, the present invention is not limited to this. 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 face authentication processing. In other words, the face authentication camera 25 and the security server 100 may share the processing of "performing face authentication of the user based on the captured image captured by the imaging 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 each of the above-described embodiments and modifications, the QR code reader 29 transmits optically read QR code image data (QR code data) to the security server 100, the group control device 10, and the QR code analysis device 300. The QR code data is transmitted to a predetermined device, and the predetermined device acquires the user ID by analyzing the QR code data, but the present invention is not limited to this. For example, the controller of the QR code reader 29 analyzes the QR code data to acquire information on the user ID and the changed destination floor, and sends the acquired user ID and the changed destination floor to the security server 100 and the group supervisory control device 10. You may send.

In each of the above-described embodiments and modifications, the security gate 20 having the gate indicator 70 was exemplified as the notification unit in the present invention, but the notification unit is not limited to this. It is not limited to the case where information is displayed on the screen, and any notification unit may be used, such as notifying information by voice.

Although the security gate 20 having the gate flapper 28 was exemplified as the gate in the present invention in each of the above-described embodiments and modifications, the gate is not limited to this. In the present invention, the gate may not have a gate flapper. In this case, the control related to the opening and closing of the gate flapper described in the above embodiment may be omitted.

In the above-described embodiment, as shown in FIG. 7B, the case where three lanes 50 are provided for the user to pass through is illustrated, but the number of lanes 50 may be any number.

In the above-described embodiment, the case where the QR code reader 29 is installed only at the security gate 20 was illustrated, but the QR code reader may be installed together with each destination floor registration device 30 on each floor. In this case, these QR code readers may also be connected to predetermined devices among the security server 100 , the group management control device 10 and the QR code analysis device 300 . Since the destination floor registration device 30 does not have a gate flapper, control related to its opening and closing may be omitted.

Although the QR code is exemplified as the predetermined information in the present invention in each of the above-described embodiments and modifications, the predetermined information is not limited to this. The predetermined information may be a two-dimensional bar code other than the QR code, a general one-dimensional bar code, or a color bar code such as a chameleon code (registered trademark). Further, the predetermined information may be electromagnetic information readable by NFC (Near Field Communication).

In each of the above-described embodiments and modifications, the mobile terminal 200 capable of displaying a QR code was exemplified as an information recording medium in the present invention, but the information recording medium is not limited to this. Any information recording medium may be used as long as it can store or record predetermined information. For example, the information recording medium may be a printed material such as paper on which predetermined information such as a QR code is printed. Also, the information recording medium may be a mobile terminal that stores predetermined information so that it can be read by NFC (Near Field Communication).

Although the QR code reader 29 is exemplified as an information acquisition unit in the present invention in each of the above-described embodiments and modifications, the information acquisition unit is not limited to this. Any information acquisition unit may be used as long as it can acquire the predetermined information from the information recording medium used. For example, it may be a two-dimensional barcode reader that reads two-dimensional barcodes, a one-dimensional barcode reader that reads one-dimensional barcodes, a chameleon code reader (camera) that reads chameleon codes, or the like. Also, the information acquisition unit may be a reader that reads predetermined information by NFC (Near Field Communication). If an information acquisition unit other than the QR code reader 29 is arranged in the security gate 20, it may be arranged instead of the QR code reader 29. FIG. Alternatively, the information acquisition unit may be a reader capable of both reading predetermined information such as a QR code and reading predetermined information by NFC (Near Field Communication).

In each of the above-described embodiments and modifications, the mobile terminal 200 capable of generating and displaying a QR code based on a user's operation was exemplified as the predetermined device in the present invention, but the predetermined device is not limited to this. Any device can be used as the predetermined device as long as it can generate predetermined information such as a QR code based on the user's operation. For example, the predetermined device may be a desktop computer or a notebook computer that generates predetermined information such as a QR code based on a user's operation and prints it with a printer. The information recording medium in this case is a printed matter such as paper on which predetermined information such as a QR code is printed.

In each of the above-described embodiments and modifications, 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 the storage unit. By doing so, various functions are realized. That is, each control unit is realized by cooperation of hardware and software. However, each control unit may be configured using, for example, only hardware (electronic circuit), FPGA, ASIC, or the like.

In each of the above-described embodiments and modifications, the network is Ethernet, and the input/output interface of each device is configured using a LAN adapter or the like. However, this is only an example, and the network may be configured by, for example, a wireless LAN conforming to the IEEE standard, and the input/output interface may be configured by a wireless LAN adapter or the like.

Security server 100, group supervisory control device 10, elevator control device 40, and QR code analysis device 300 in each of the above-described embodiments and modifications are not necessarily installed in the building where elevator 60 is located. For example, for any of these devices, the functions of that device may be executed by the cloud server. In this case, transmission and reception of various signals and information between devices such as the security gate 20, the destination floor registration device 30, and the gate display device 70 installed in the building where the elevator 60 is arranged and the cloud server are performed by appropriate communication. communication using the method.

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

(Summary and effects of the embodiment, etc.)
(1) The elevator system of the embodiment includes:
An elevator system for setting a user's destination floor before the user gets on the elevator,
an imaging unit (e.g., face authentication camera 25) provided so as to be able to image a user who is about to pass through a gate (e.g., security gate 20) arranged on a moving route to an elevator hall;
A notification unit (for example, a gate indicator 70) that notifies the user;
An information acquisition unit (eg, QR code reader 29) that acquires predetermined information (eg, QR code) from an information recording medium (eg, mobile terminal 200) possessed by the user before passing through the gate;
a face authentication unit (for example, a security server 100) that performs face authentication of a user based on an image captured by the imaging unit;
a destination floor setting unit (for example, the security server 100 or the group management control device 10) for setting the destination floor of the user,
Destination floor setting part,
When the user's face authentication is successful in the face authentication unit and the predetermined information is not acquired by the information acquisition unit, the default destination floor specified based on the face authentication is set as the user's destination floor,
When the face authentication unit successfully authenticates the user's face and the information acquisition unit acquires the predetermined information, the changed destination floor indicated by the predetermined information is set as the user's destination floor,
The information acquisition units include a first information acquisition unit (for example, QR code reader 29A) arranged on the left side of the lane (for example, lane 50A) at the gate and a second information acquisition unit (for example, QR code reader 29B) arranged on the right side. and

With this configuration, it is possible to register not only the default destination floor but also the changed destination floor when the user passes through a gate using face authentication (for example, the security gate 20). By providing information acquisition units (eg, QR code readers 29A and 29B) on the left and right sides of the lane (eg, lane 50A), the user can selectively use either information acquisition unit according to the dominant hand. It can be used and is ambidextrous.

(2) In the elevator system of the embodiment,
The predetermined information (e.g. QR code) further stores user identification information (e.g. user ID),
The destination floor setting unit (for example, the security server 100 or the group management control device 10)
When the predetermined information is acquired by the first information acquisition unit (QR code reader 29A) or the second information acquisition unit (QR code reader 29B), the specified information is specified based on the user identification information indicated by the predetermined information and face authentication. determine whether or not the user identification information matches,
If they match, the changed destination floor indicated by the predetermined information is set as the user's destination floor (the destination floor change flag is turned ON),
If they do not match, the changed destination floor indicated by the predetermined information is not set as the user's destination floor.

With this configuration, it is possible to prevent the user's destination floor specified based on face authentication from being changed based on the changed destination floor indicated by the predetermined information of another user.

(3) In the elevator system of the embodiment,
A first information acquisition unit (for example, QR code reader 29B) of a lane (for example, lane 50B), when there is an adjacent lane (for example, lane 50A) on the left side, a second information acquisition unit (for example, QR code reader 29B) of the lane If there is an adjacent lane (eg, lane 50C) on the right side, the second information acquisition section (eg, QR code reader 29C) also serves as the first information acquisition section (eg, QR code reader 29C) for that lane.

With this configuration, by sharing the information acquisition section between two adjacent lanes, it is possible to reduce the number of parts and reduce the manufacturing cost of the gate while supporting ambidextrous.

(4) The elevator system of Embodiment 2 is
The notification unit (for example, gate indicators 70D and 70E) is a gate indicator that displays information at the gate (for example, security gate 20A), and the first gate indicator (for example, lane 50A) arranged on the left side of the lane (for example, the gate A display 70D) and a second gate display (gate display 70E) arranged on the right side, and the first gate display and the second gate display display in conjunction with each other.

With this configuration, by providing the gate indicators on the left and right sides of the lane, respectively, the user can check the contents of the two gate indicators, thereby further improving convenience.

(5) In the elevator system of the embodiment,
It further comprises a group supervisory controller (group supervisory controller 10) that assigns the set destination floor of the user to one of the plurality of elevators.

With this configuration, the above-described effects can be obtained in an elevator system in which destination floors are assigned to a plurality of elevators by a group supervisory control device.

(6) In the elevator system of the embodiment,
Predetermined information (e.g. QR code) is generated based on a user's operation on a predetermined device (e.g. mobile terminal 200),
The group supervisory control device (group supervisory control device 10) does not allocate an elevator when a changed destination floor is set as a destination floor of a user and the changed destination floor does not actually exist, and a notification unit is notified of information indicating that the changed destination floor is a non-existent floor.

With this configuration, when the user sets a non-existing floor as the changed destination floor, the user can recognize that fact.

(7) In the elevator system of the embodiment,
Predetermined information (e.g. QR code) is generated based on a user's operation on a predetermined device (e.g. mobile terminal 200),
When a changed destination floor is set as a user's destination floor, the group supervisory control device (group supervisory control device 10), when the changed destination floor is a floor that is not permitted to be used by the user, controls the elevator. No allocation is made, and the notification unit is made to notify information indicating that the changed destination floor is a floor that the user is not permitted to use.

With this configuration, when the user has set a floor that is not permitted to use, the user can recognize that fact.

(8) In the elevator system of the embodiment,
In the destination floor setting unit (for example, the security server 100 or the group management control device 10), the face authentication unit successfully authenticated the user's face, but the information acquisition unit (for example, the QR code reader 29) is not acquired and the user's default destination floor specified based on face recognition is not registered, set the destination floor unset information as the user's destination floor,
The group supervisory control device (group supervisory control device 10) does not allocate an elevator when the destination floor unset information is set as the user's destination floor, and notifies the notification unit of the destination floor registration device (destination floor The registration device 30) notifies information prompting the user to register the destination floor.

With this configuration, it is possible to prompt the user to register the destination floor with the destination floor registration device 30 when the user's default destination floor is not set. In addition, by making it possible to set the destination floor unset information, useless calls are less likely to occur, and the operating efficiency of the elevator can be improved.

(9) In the elevator system of the embodiment,
The information acquisition unit (for example, QR code reader 29) optically reads predetermined information (for example, QR code),
A server (for example, the security server 100) that controls the gate (for example, the security gate 20) analyzes the optically read predetermined information and obtains information on the changed destination floor.

With this configuration, the server (for example, the security server 100) can analyze the predetermined information and acquire the information on the changed destination floor.

(10) In the elevator system of the embodiment,
The information acquisition unit (for example, QR code reader 29) optically reads predetermined information (for example, QR code),
A group supervisory control device (group supervisory control device 10) analyzes the optically read predetermined information and acquires information about the changed destination floor.

With this configuration, the group supervisory control device (group supervisory control device 10) can analyze the predetermined information (for example, QR code) to acquire the information of the changed destination floor.

(11) In the elevator system of the embodiment,
The information acquisition unit (for example, QR code reader 29) optically reads predetermined information (for example, QR code),
Separately from the destination floor setting unit (for example, the security server 100 or the group management control device 10) and the group management control device (group management control device 10), the optically read predetermined information is analyzed and information on the changed destination floor is obtained. It further comprises an analysis device (for example, the QR code analysis device 300) that acquires.

With this configuration, it is possible to acquire information on the destination floor to be changed by analyzing the predetermined information (for example, QR code) with an analysis device (for example, QR code analysis device 300).

10 Group supervisory control device 11 Control unit 12 Storage unit 13 Input/output interface 20, 20A to 20C Security gate 20a Gate body 20i Entrance 20e Exit 25, 25A to 25C Face authentication camera 26 First sensor 27 Second sensor 28 Gate flapper 29 , 29A to 29D QR code reader 30 Destination floor registration device 31 Control unit 32 Storage unit 33 Input/output interface 34 Display unit 35 Operation unit 36 Face authentication camera 40, 40A to 40F Elevator control device 50, 50A to 50C Lanes 60, 60A ~ 60F Elevator 70, 70A ~ 70I Gate display (notification unit)
100 Security server 101 Control unit 102 Storage unit 103 Input/output interface 200 Portable terminal 210 Display unit 300 QR code analysis device T Predetermined time

Claims (11)

An elevator system for setting the destination floor of the user before the user gets on the elevator,
an imaging unit provided corresponding to the lane so as to be able to image a user who is about to pass through the lane of the gate arranged on the moving route to the elevator hall;
a notification unit that is provided corresponding to the lane and notifies the user;
A first information acquisition unit arranged on the left side of the lane and a second information acquisition unit arranged on the right side of the lane to acquire predetermined information from an information recording medium possessed by the user before passing through the gate. an information acquisition unit that is selectably provided with a unit ;
a face authentication unit that performs face authentication of the user based on the captured image captured by the imaging unit before the user passes through the lane ;
a destination floor setting unit for setting the destination floor of the user,
The destination floor setting unit
When the face authentication unit succeeds in face authentication of the user, the predetermined information corresponding to the face data included in the captured image is not acquired by the first information acquisition unit or the second information acquisition unit , and when the user's default destination floor is identified based on face authentication , setting the default destination floor as the user's destination floor,
When the face authentication unit successfully authenticates the user's face and the predetermined information corresponding to the face data is acquired by the first information acquisition unit or the second information acquisition unit , the predetermined information sets the changed destination floor indicated by as the user's destination floor,
elevator system. The predetermined information further stores user identification information,
The destination floor setting unit
When the predetermined information is obtained by the first information obtaining unit or the second information obtaining unit, the user identification information indicated by the predetermined information matches the user identification information specified based on face authentication. decide whether to
if they match, the predetermined information corresponds to the face data, and the changed destination floor indicated by the predetermined information is set as the user's destination floor;
if they do not match, the predetermined information does not correspond to the face data, and the changed destination floor indicated by the predetermined information is not set as the user's destination floor;
The elevator system according to claim 1. The first information acquisition unit of the lane also serves as the second information acquisition unit of the lane when there is an adjacent lane on the left side, and the second information acquisition unit serves as the second information acquisition unit of the lane when there is an adjacent lane on the right side. Also serving as the first information acquisition unit of the lane,
The elevator system according to claim 1 or 2. The notification unit is a gate display for displaying information at the gate, and includes a first gate display arranged on the left side of the lane and a second gate display arranged on the right side of the lane. The gate indicator and the second gate indicator display in conjunction,
Elevator system according to any one of claims 1 to 3. Further comprising a group supervisory control device that assigns the set destination floor of the user to one of a plurality of elevators,
Elevator system according to any one of claims 1 to 4. the predetermined information is generated based on an operation of the user on a predetermined device;
When a destination floor to be changed is set as the destination floor of the user and the destination floor to be changed is a non-existent floor, the group supervisory control device does not allocate an elevator, Notify information indicating that the changed destination floor is a non-existent floor,
An elevator system according to claim 5. the predetermined information is generated based on an operation of the user on a predetermined device;
When a change destination floor is set as the destination floor of the user and the change destination floor is a floor not permitted to be used by the user, the group supervisory control device allocates elevators. First, causing the reporting unit to report information indicating that the changed destination floor is a floor that is not permitted to be used by the user;
An elevator system according to claim 5. The destination floor setting unit determines whether the predetermined information is not acquired by the information acquisition unit and the default destination floor is specified based on the face authentication when the facial authentication of the user is successful in the face authentication unit. If not , set the destination floor unset information as the destination floor of the user,
When the destination floor unset information is set as the destination floor of the user, the group supervisory control device does not allocate an elevator and registers the destination floor with the destination floor registration device in the notification unit. to inform you of information that prompts you to
An elevator system according to claim 5. The information acquisition unit optically reads the predetermined information,
The server that controls the gate analyzes the optically read predetermined information and acquires information on the changed destination floor.
Elevator system according to any one of claims 5 to 8. The information acquisition unit optically reads the predetermined information,
The group supervisory control device analyzes the optically read predetermined information to acquire information on the destination floor to be changed.
Elevator system according to any one of claims 5 to 8. The information acquisition unit optically reads the predetermined information,
In addition to the destination floor setting unit and the group supervisory control device, the vehicle further comprises an analysis device that analyzes the optically read predetermined information and acquires information on the changed destination floor.
Elevator system according to any one of claims 5 to 8.

Images