JP6844639B2 - Elevator group management control device and group management system, and elevator system - Google Patents

Description

The present invention relates to an elevator group management control device and a group management system, and an elevator system.

Patent Document 1 discloses an elevator group management system provided with a landing destination floor registration device having a destination floor registration function. Further, in this group management system, one user in a group composed of a plurality of users inputs the number of users and the destination floor with the landing destination floor registration device, so that all the users forming the group are formed. It is configured so that the same unit can be assigned to the users of.

Japanese Patent No. 5087281

In recent years, high-rise buildings and the like are provided with security gates on lobby floors and the like connected to the outside, and there are cases where destination floors are registered using the security gates. In this case, for example, the elevator group management system assigns the user to some machine based on the user ID acquired by the information acquisition unit such as the card reader of the security gate.

In such a system, since a machine is assigned individually each time a user passes through the security gate, it is not possible to assign a plurality of users forming a group to the same machine.

The present invention is an elevator group management control device and a group capable of assigning a plurality of users to the same unit as a group even when the unit is assigned by using an information acquisition device such as a security gate card reader. It provides a management system as well as an elevator system.

The elevator group management control device according to the first aspect of the present invention is generated by the allocation request generation device based on the user information acquired by the information acquisition device arranged on or near the route to the landing. Allocate the call related to the allocation request information to one of the multiple elevators.
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the user It is configured to output the allocation request information including the group identification information indicating the group to which the group belongs to the group management control device.
The group management control device includes a control unit that assigns a call based on allocation request information to any one of a plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the same group as the group identification information included in the allocation request information received this time within the predetermined time before receiving the allocation request information. Determine whether or not the allocation request information including the identification information is acquired from the allocation request generator, and determine.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time elapses after the reception. , The second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to the same unit.

The elevator system according to the second aspect of the present invention is
A group management control device for multiple elevators and an elevator group management control device that assigns a call based on user information acquired by an information acquisition device located on or near the route to the landing to any of the multiple elevators. Have.
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the user It is configured to output the allocation request information including the group identification information indicating the group to which the group belongs to the group management control device.
The group management control device includes a control unit that assigns a call based on allocation request information to any one of a plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the same group as the group identification information included in the allocation request information received this time within the predetermined time before receiving the allocation request information. Determine whether or not the allocation request information including the identification information is acquired from the allocation request generator, and determine.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time elapses after the reception. , The second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to the same unit.

The elevator group management system according to the third aspect of the present invention is
It was generated by the information acquisition device located on or near the route to the landing, the allocation request generation device that generates allocation request information based on the user information acquired by the information acquisition device, and the allocation request generation device. It has an elevator group management control device that assigns a call related to allocation request information to any one of a plurality of elevators.
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the user It is configured to output the allocation request information including the group identification information indicating the group to which the group belongs to the group management control device.
The group management control device includes a control unit that assigns a call based on allocation request information to any one of a plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the same group as the group identification information included in the allocation request information received this time within the predetermined time before receiving the allocation request information. Determine whether or not the allocation request information including the identification information is acquired from the allocation request generator, and determine.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time elapses after the reception. , The second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to the same unit.

Further, the elevator system according to the fourth aspect of the present invention is
Multiple elevators, an information acquisition device located on or near the route to the landing, an allocation request generator that generates allocation request information based on user information acquired by the information acquisition device, and an allocation request. It has an elevator group management control device that assigns a call related to allocation request information generated by the generation device to any one of a plurality of elevators.
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the user It is configured to output the allocation request information including the group identification information indicating the group to which the group belongs to the group management control device.
The group management control device includes a control unit that assigns a call based on allocation request information to any one of a plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the same group as the group identification information included in the allocation request information received this time within the predetermined time before receiving the allocation request information. Determine whether or not the allocation request information including the identification information is acquired from the allocation request generator, and determine.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time elapses after the reception. , The second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to the same unit.

According to the present invention, it is possible to assign a plurality of users as a group to the same machine based on the user information read by the information acquisition device.

It is the schematic which shows the arrangement on the specific floor of the building to which the elevator system which concerns on Embodiment 1 is applied. It is a block diagram which shows the structure of the group management system of the elevator which concerns on Embodiment 1. It is a block diagram which shows the electrical structure of the group management control apparatus which concerns on Embodiment 1. FIG. It is a block diagram which shows the electrical structure of the destination floor registration apparatus in Embodiment 1. FIG. It is a figure which shows the display example of the display part of the destination floor registration apparatus in the group management system of the elevator which concerns on Embodiment 1. FIG. It is a block diagram which shows the electric structure of the elevator control device in Embodiment 1. FIG. It is a perspective view which shows the appearance of the security gate which concerns on Embodiment 1. FIG. It is a block diagram which shows the electrical structure of the security gate which concerns on Embodiment 1. FIG. It is a block diagram which shows the electrical structure of the gate indicator in Embodiment 1. FIG. It is a figure which shows the display example which guides the unit assigned by the group management system to the user in the gate display installed in the security gate in the group management system of the elevator which concerns on Embodiment 1. FIG. It is a block diagram which shows the electrical structure of the security server which concerns on Embodiment 1. FIG. It is a figure which shows the structure of the user DB stored in the storage part of the security server which concerns on Embodiment 1. FIG. It is a figure which shows the structure of the user DB stored in the storage part of the security server which concerns on Embodiment 1. FIG. It is a flowchart which shows the operation of the security server which concerns on Embodiment 1. It is a flowchart which shows the operation of the group management control apparatus which concerns on Embodiment 1. It is a flowchart which shows the structure of the group allocation DB of the group management control apparatus which concerns on Embodiment 1. It is a flowchart which shows the determination operation of the assigned unit in the group management control apparatus which concerns on Embodiment 1. It is a flowchart which shows the determination operation of the group assignment unit in the group management control device which concerns on Embodiment 1. FIG. It is a flowchart which shows the update operation of the group allocation DB of the group management control apparatus which concerns on Embodiment 1. It is explanatory drawing of the allocation operation with respect to the group of the group management control apparatus which concerns on Embodiment 1. FIG. It is a flowchart which shows the operation of the group management control apparatus which concerns on Embodiment 2. It is a flowchart which shows the allocation operation of the group management control apparatus which concerns on Embodiment 2.

The elevator group management system according to the embodiment of the present invention will be described with reference to the drawings.

(Embodiment 1)
1. 1. Configuration 1-1. Outline of the elevator system An outline of the elevator system according to the present embodiment will be described. FIG. 1 is a schematic view showing an arrangement of a building (building) to which the elevator system according to the first embodiment is applied on a specific floor. Here, the specific floor is, for example, a lobby floor connected to the outside of the building. Building users will move to other floors via a specific floor.

The elevator system according to the present embodiment includes a plurality of elevators (hereinafter, appropriately referred to as "units") 60A to 60F, and a group management system. The group management system of elevators comprehensively controls the running and operation of elevators (Units A to F; hereinafter appropriately referred to as "Units") 60A to 60F. In this embodiment, as an example, six elevators 60A to 60F of Units A to F are provided. Elevator 60A to 60F boarding openings are provided on the elevator hall (elevator landing) side, and users board the elevators 60A to 60F from the elevator hall. The plurality of elevators 60A to 60F have the same configuration as each other. Therefore, when it is not necessary to distinguish in the description of the configuration and the like, each elevator is appropriately referred to as "elevator 60".

In the present embodiment, it is assumed that a plurality of security gates 20A to 20C are installed between the entrance (entrance hall) and the elevator hall (elevator landing) on a specific floor such as the lobby floor of the building. The plurality of security gates 20A to 20C have the same configuration as each other. Therefore, when it is not necessary to distinguish in the description of the configuration and the like, each security gate is appropriately referred to as "security gate 20". The user enters the elevator hall from the entrance side through one of the security gates 20.

Here, in a building, the area on the elevator hall side of the security gates 20A to 20C may be appropriately referred to as a "specific area" thereafter. The specific area is an area in a building that cannot be entered unless the security gates 20A to 20C are passed from the entrance side. Therefore, the specific area may include not only the elevator hall but also the space in the car of each elevator 60, the space of each floor that can be moved by using the elevator 60, and the like.

Further, it is assumed that the destination floor registration device 30A is installed on the specific floor near the route to the elevator hall (elevator landing). Destination floor registration devices 30B to 30Z are provided on each floor other than the specific floor where the security gate 20 is not provided (see FIG. 2). A plurality of destination floor registration devices 30A to 30Z have the same configuration as each other. Therefore, when it is not necessary to distinguish in the description of the configuration and the like, each destination floor registration device is appropriately referred to as a "destination floor registration device 30".

In the elevator group management system according to the present embodiment, a destination floor registration method is adopted in which the destination floor is registered in advance using the security gate 20 and the destination floor registration device 30 before the user gets into the car of the elevator 60. ing. Then, the group management system assigns the call (destination floor call) for the destination floor registered in advance to any one of the plurality of elevators 60, and uses the information indicating the assigned machine. The user is configured to board the assigned unit. Specific control will be described later. The destination floor registration device 30A on the specific floor is arbitrary when a user who has entered the elevator hall misses the designated elevator 60 or moves to a floor that is not registered on the ID card. It is provided so that the destination floor can be registered.

1-2. Elevator group management system configuration 1-2-1. Outline The configuration of the elevator group management system according to this embodiment will be described. FIG. 2 is a block diagram showing a configuration of an elevator group management system according to the first embodiment. The elevator group management system according to the present embodiment includes a group management control device 10, a plurality of destination floor registration devices 30A to 30Z, a plurality of elevator control devices 40A to 40F, and a gate display 70. The gate indicator 70 is provided at the security gate 20.

The elevator group management system controls the allocation of new destination floor calls to each unit while communicating with the security server 100. Each device is connected via a network NW capable of transmitting information. The network NW is composed of a LAN (Local Area Network) such as Ethernet (registered trademark), and transmission / reception of various information between each device is performed according to various protocols such as TCP / IP. Each of the above-mentioned devices connected on the network NW is capable of signal transmission (information transmission) by communication according to various protocols such as TCP / IP by the input / output interface of each device. .. It should be noted that each device constituting the group management system may be connected via another signal format network or a dedicated signal network.

Each elevator (each unit) 60A to 60F has a car, a hoisting machine (motor), a balance weight, and the like.

1-2-2. Group management control device The group management control device 10 has a plurality of destination floors corresponding to the user ID (user information) read from the ID card at the security gate 20, or a plurality of destination floors input by the destination floor registration device 30. Control is performed to assign to any of the elevators 60A to 60F.

FIG. 3 is a block diagram showing an electrical configuration of the group management control device 10 according to the first embodiment.

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

The storage unit 12 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the group management control device 10 of the present embodiment. The storage unit 12 stores, for example, a group allocation DB as data. The configuration of the group allocation DB will be described later.

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

The input / output interface 13 is configured by using, for example, a LAN adapter or the like. The input / output interface 13 is between the group management control device 10, the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30 (30A to 30Z), and the elevator control device 40 (40A to 40F). It is an interface for transmitting and receiving various signals. The input / output interface 13 converts the signal output from the control unit 11 into a signal of a predetermined format and outputs it to the security server 100, the gate display 70 of the security gate 20, the destination floor registration device 30, and the elevator control device 40. To do. Further, the input / output interface 13 converts the 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 device 40 into signals of a predetermined format, and the control unit 11 Output to.

1-2-3. Destination Floor Registration Device FIG. 4 is a block diagram showing an electrical configuration of the destination floor registration device 30 according to the first embodiment. The destination floor registration device 30 is a device for the user to register the destination floor. The destination floor registration device 30 includes a control unit 31, a storage unit 32, an input / output interface 33, a display unit 34, and an operation unit 35.

The storage unit 32 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the destination floor registration device 30 of the present embodiment. The storage unit 32 stores, for example, device identification information (hereinafter, appropriately referred to as “device ID”) of the destination floor registration device 30 as data.

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

The input / output interface 33 is configured by 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 management control device 10. The input / output interface 33 converts the signal output from the control unit 31 into a signal of a predetermined format and outputs the signal to the group management control device 10. Further, the input / output interface 33 converts the signal input from the group management control device 10 into a signal of a predetermined format and outputs the signal to the control unit 31.

The operation unit 35 is an interface for the user to input the destination floor. The operation unit 35 outputs a signal corresponding to the operation content of the operation unit 35 to the control unit 31.

The display unit 34 displays based on the display signal output from the control unit 31.

The display unit 34 and the operation unit 35 are integrally configured by, for example, a touch panel type display device using a liquid crystal display panel or an organic EL display panel. The display unit 34 and the operation unit 35 may be separately configured by using different parts.

FIG. 5 is a diagram showing a display example of the display unit 34 of the destination floor registration device 30 in the elevator group management system according to the first embodiment. In this example, the numeric keypad for specifying the floor is displayed. In FIG. 5, it is shown that the 9th floor was designated and Unit A was assigned. The destination floor registration device 30 displays the input destination floor when an input operation for the destination floor is performed on the operation unit 35, and then the group management control device 10 corresponds to the destination floor registration device 30. When the assigned machine information is received, the assigned machine information is displayed in association with the displayed destination floor as shown in FIG.

1-2-4. Elevator control device The elevator control devices 40A to 40F control the operation of the hoisting machine (motor) of the corresponding elevators 60A to 60F according to the control signal from the group management control device 10, and thereby each elevator 60A to 60F. Controls the ascent, descent, stop, etc. of the car. Further, the elevator control devices 40A to 40F each detect a car state including the car position, traveling direction, door open / closed state, load, etc. of the corresponding elevators 60A to 60F, and include information indicating the detected car state. The car status signal is output to the group management control device 10. The plurality of elevator control devices 40A to 40F have the same configuration as each other. Therefore, when it is not necessary to distinguish in the description of the configuration and the like, each elevator control device is appropriately referred to as "elevator control device 40".

FIG. 6 is a block diagram showing an electrical configuration of the elevator control device according to the first embodiment. Each elevator control device 40 (elevator control devices 40A to 40F) includes a control unit 41, a storage unit 42, and an input / output interface 43.

The storage unit 42 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the elevator control device 40 of the present embodiment.

The control unit 41 is configured by using, for example, a CPU, an MPU, or the like. The control unit 41 realizes various functions described later in the elevator control device 40 by performing arithmetic processing using various data and the like based on the above program read from the storage unit 42.

The input / output interface 43 is configured by using, for example, a LAN adapter or the like. The input / output interface 43 is an interface for transmitting and receiving various signals between the elevator control device 40 and the group management control device 10. The input / output interface 43 converts the signal output from the control unit 41 into a signal of a predetermined format and outputs the signal to the group management control device 10. Further, the input / output interface 43 converts the signal input from the group management control device 10 into a signal of a predetermined format and outputs the signal to the control unit 41.

1-2-5. Security Gate The security gate 20 is a device for permitting or restricting the entry of a user into a specific area. The security gate 20 is provided as a security facility for a building. The security gate 20 allows only a user who has a legitimate ID card to enter a specific area.

FIG. 7 is a perspective view showing the appearance of the first example of the security gate 20 in the first embodiment. Note that FIG. 7 shows an example of the leftmost security gate 20A (20) in FIG. The security gate 20 includes a gate body 20a, a first sensor 26, a second sensor 27, an inlet side card reader 25, an exit side card reader 29, a gate indicator 70, and a gate flapper 28.

The first sensor 26, the second sensor 27, the entrance side card reader 25, the exit side card reader 29, and the gate display 70 are attached to the outer surface of the gate body 20a. The gate body 20a is a housing for accommodating a control unit 21 and the like, which will be described later. The gate main body 20a is arranged along the approach direction of the user. The gate main body 20a is installed in parallel with the gate main body of the adjacent security gate 20 separated by a predetermined distance (see FIG. 1). A passage PA through which the user can pass is formed on the side of the gate body 20a.

The entrance-side card reader 25 is arranged on the entrance 20i side of the upper surface of the security gate main body 20a. The entrance side of the upper surface of the security gate main body 20a is the side far from the specific area on the upper surface of the security gate main body 20a. The entrance side card reader 25 is a card reader for reading the user ID recorded on the ID card possessed by the user who enters the passage PA of the security gate 20 from the entrance side. The entrance side card reader 25 is composed of, for example, an electromagnetic induction type non-contact card reader. The entrance side card reader 25 may be composed of a contact type card reader. The entrance side card reader 25 is an example of an information reading unit.

The entrance side card reader 25 includes a control unit, a storage unit, an input / output interface, a reader main body, and the like, and the control unit performs arithmetic processing on various data and the like based on a program stored in the storage unit. , Realizes various functions in the card reader 25. As data, for example, the device ID of the card reader 25 is stored in the storage unit.

The exit-side card reader 29 is arranged on the exit 20e side of the upper surface of the security gate main body 20a. The exit side of the upper surface of the security gate main body 20a is the side close to the specific area on the upper surface of the security gate main body 20a. The exit-side card reader 29 is a card reader for reading the user ID recorded on the ID card possessed by the user who enters the passage of the security gate 20 from the exit side. As the exit-side card reader 29, one having the same configuration as the above-mentioned entrance-side card reader 25 can be used. The storage unit stores, for example, the device ID of the card reader 29 as data.

The gate display 70 displays the assigned machine information. The detailed configuration of the gate display 70 will be described later.

The first sensor 26 detects the movement of the user on the entrance 20i side of the passage PA of the security gate 20. When the first sensor 26 and the second sensor 27 detect the movement of the user, they output a detection signal.

The second sensor 27 detects the movement of the user on the exit 20e side of the passage PA of the security gate 20. When the first sensor 26 and the second sensor 27 detect the movement of the user, they output a detection signal.

The gate flapper 28 is a door that can be opened and closed. The gate flapper 28 allows the user to pass through the security gate 20 in the open state. The gate flapper 28 prevents the user from passing through the security gate 20 in the closed state.

FIG. 8 is a block diagram showing an electrical configuration of the security gate 20 according to the first embodiment. The security gate 20 further includes a control unit 21, a storage unit 22, and an input / output interface 23 in addition to the above-mentioned components.

The storage unit 22 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions of the security gate 20 in the present embodiment.

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

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, the gate OPEN signal from the security server 100, the gate CLOSE signal, and the like.

When the entrance side card reader 25 and the exit side card reader 29 read the user ID recorded on the ID card, the read user ID and the device ID of the entrance side card reader 25 or the exit side card reader 29 are obtained. It is transmitted to the security server 100.

The input / output interface 23 is configured by 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 signals output from the control unit 21, the entrance side card reader 25, and the exit side card reader 29 into signals of a predetermined format and outputs the signals to the security server 100. Further, the input / output interface 23 converts the signal input from the security server 100 into a signal of a predetermined format and outputs the signal to the control unit 21.

1-2-6. Gate indicator The gate indicator 70 is an indicator installed at the security gate 20 for guiding the user to the unit assigned by the group management control device 10. The gate indicator 70 is installed at the security gate 20, but is a part of the elevator group management system as a system. The gate display 70 is assigned to a user (user ID corresponding to the ID card presented by the user) who passes through the security gate 20 provided with the gate display 70 from the entrance 20i side to the exit 20e side. Display the assigned machine information indicating the elevator.

FIG. 9 is a block diagram showing an electrical configuration of the gate indicator 70 according to the first embodiment. The gate display 70 is configured by using a computer so that display control based on the information received from the group management control device 10 is possible. As shown in FIG. 9, the gate display 70 includes a control unit 71, a storage unit 72, an input / output interface 73, and a display unit 74.

The storage unit 72 is configured by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions described later of the gate display 70 of the present embodiment.

The control unit 71 is configured by using, for example, a CPU, an MPU, or the like. The control unit 71 realizes various functions described later in the gate display 70 by performing arithmetic processing using various data and the like based on the above program read from the storage unit 72.

The input / output interface 73 is configured by using, for example, a LAN adapter or the like. The input / output interface 73 is an interface for transmitting and receiving various signals between the gate display 70 and the group management control device 10. The input / output interface 73 converts the signal output from the control unit 71 into a signal of a predetermined format and outputs the signal to the group management control device 10. Further, the input / output interface 73 converts the signal input from the group management control device 10 into a signal of a predetermined format and outputs the signal to the control unit 71.

The display unit 74 is configured by using, for example, a liquid crystal display panel or an organic EL display panel.

FIG. 10 is a diagram showing a display example of the gate indicator 70 in the elevator group management system according to the first embodiment. In this example, the gate indicator 70 indicates that Unit A has been assigned.

1-2-7. Security server The security server 100 performs authentication based on the user ID read by the card reader 25 of the security gate 20, and transmits a gate OPEN signal or a gate CLOSE signal to the control unit 21 of the security gate 20 based on the authentication result. .. Further, the security server 100 generates allocation request information (destination floor information, departure floor information, device ID, etc.) based on the user ID and the like, and outputs the allocation request information to the group management control device 10. Further, as will be described later, when the user corresponding to the user ID belongs to the group, the security server 100 further includes the group number and the number of non-entrants in the allocation request information and outputs the group management control device 10. To do.

FIG. 11 is a block diagram showing an electrical configuration of the security server 100 according to the first embodiment. The security server 100 is configured by 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 by using, for example, a RAM, a ROM, an HDD, an SSD, or the like, and stores a program and various data. The program includes a program for realizing various functions described later of the security server 100 of the present embodiment. The storage unit 102 stores a user database (hereinafter referred to as "user DB") as data. The configuration of the user DB will be described later.

Further, the storage unit 102 stores the installation floor information indicating the installation floor of the security gate 20 as data. The installation floor information is used as departure floor information for users who have passed through the security gate 20. When the security gate 20 is installed on a plurality of floors, the storage unit 102 stores, for example, an installation floor information table in which the device ID of the card reader 25 and the installation floor information are recorded in association with each other. You may. In this case, when the device ID is received from the entrance side card reader 25 or the exit side card reader 29 of the security gate 20, the installation floor corresponding to the device ID of the entrance side card reader 25 of the security gate 20 is displayed from the installation floor information table. Information may be acquired and the acquired installation floor information may be used as departure floor information.

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

The input / output interface 103 is configured by using, for example, a LAN adapter or the like. The input / output interface 103 is for transmitting and receiving various signals between the security server 100, the group management control device 10, and the security gate 20 (entrance side card reader 25, exit side card reader 29, and control unit 21). It is an interface. The input / output interface 103 converts the signal output from the control unit 101 into a signal of a predetermined format, and the group management control device 10 and the security gate 20 (entrance side card reader 25, exit side card reader 29, and control unit). Output to 21). Further, the input / output interface 103 converts the signal input from the group management control device 10 and the security gate 20 (inlet side card reader 25, exit side card reader 29, and control unit 21) into a signal of a predetermined format. Is output to the control unit 101.

FIG. 12A is a diagram showing a configuration of a user DB stored in the storage unit 102 of the security server 100 in the first embodiment. The user DB records the user ID of the ID card, the destination floor (destination floor information), the group number, and the entry flag in association with each other.

The group number is the number of the group to which the user related to the user ID belongs. In the user DB, the fact that an integer value of "1" or more is recorded as the group number in association with the user ID means that the user related to the user ID is a user who belongs to the group of the group number. Indicates that it is registered (hereinafter referred to as "group registration" as appropriate). On the other hand, the fact that "0" is recorded as the group number in association with the user ID indicates that the user related to the user ID is not registered as a group in any of the groups.

The entry flag is a flag indicating whether or not the user related to the user ID currently exists in a specific area of the building. The fact that "ON" is recorded as the entry flag in association with the user ID indicates that the user related to the user ID currently exists in the specific area of the building. On the other hand, the fact that "OFF" is recorded as the entry flag in association with the user ID indicates that the user related to the user ID does not currently exist in the specific area of the building.

In the example shown in FIG. 12A, "10th floor" is recorded as the destination floor information in association with the user ID "00001". "8th floor" is recorded as destination floor information in association with the user ID "00002". “15th floor” is recorded as destination floor information in association with the user ID “00003”. For other user IDs, the corresponding destination floors are recorded in the same manner. Further, "1" is recorded as a group number in association with the user IDs "00003", "00004", "00006", and "00007", respectively. This indicates that the users corresponding to the user IDs "00003", "00004", "00006", and "00007" are registered as users belonging to the group with the group number "1". Further, "2" is recorded as a group number in association with the user IDs "00002" and "00005", respectively. This indicates that the user corresponding to the user IDs "00002" and "00005" is registered as a user belonging to the group with the group number "2". On the other hand, "0" is recorded as a group number in association with the user IDs "00001", "00002", "00005", and "00008", respectively. This indicates that the users corresponding to the user IDs "00001", "00002", "00005", and "00008" are not registered in any of the groups. In addition, "OFF" is recorded as an entry flag for all user IDs. This indicates that the users corresponding to all the user IDs do not currently exist in the specific area of the building.

FIG. 12B is a diagram showing a configuration of a user DB stored in the storage unit 102 of the security server 100 in the first embodiment. In FIG. 12B, "ON" is recorded as an entry flag in association with the user IDs "00005" and "00007", respectively. This indicates that the user corresponding to the user IDs “00005” and “00007” exists in the specific area of the building. That is, as compared with FIG. 12A, it can be seen that the user corresponding to the user IDs “00005” and “00007” has entered the specific area of the building.

The group registration in the user DB can be performed by accessing the security server 100 from, for example, the computer of the building administrator, the computer of the user, a smartphone, or the like via a communication line or the like. Has been done. Various known methods can be used for the configuration for registration in the database via a communication line or the like.

2. Operation 2-1. Outline With reference to FIG. 2, the opening / closing operation of the gate flapper 28 of the security gate 20 and the unit allocation control by the group management system will be described in chronological order.

2-1-1. Opening and closing the gate flapper of the security gate First, the opening and closing operation of the gate flapper 28 of the security gate 20 will be described in chronological order. When the user enters the security gate 20 (20A to 20C) while bringing the ID card into contact with or close to the entrance side card reader 25, the entrance side card reader 25 reads the user ID from the ID card and the entrance side card. ID information (user ID, device ID of the entrance side card reader 25) is transmitted from the reader 25 to the security server 100. When the user ID included in the received ID information is legitimate, the security server 100 transmits the gate OPEN signal to the control unit 21 of the security gate 20 corresponding to the entrance side card reader 25 of the device ID. .. In this case, the control unit 21 keeps the gate flapper 28 in the open state. As a result, the user can pass through the security gate 20.

On the other hand, when the ID card is non-genuine, the security server 100 transmits the gate CLOSE signal to the control unit 21 of the security gate 20 corresponding to the entrance side card reader 25 of the device ID. In this case, the control unit 21 closes the gate flapper 28. Therefore, the user who presents the non-genuine ID card cannot pass through the security gate 20.

Further, when the signal from the first sensor 26 is received without receiving the gate OPEN signal from the security server 100, the control unit 21 of the security gate 20 controls the gate flapper 28 in the closed state. This is because there is a possibility that a non-genuine user who does not have an ID card is trying to pass through the security server 100, and this is to prevent this.

In this way, a user with a legitimate ID card can enter the elevator hall, but a user without an ID card or a user with a non-legitimate ID card cannot enter the elevator hall. .. Therefore, the security in the building is ensured.

2-1-2. When the user ID included in the ID information (user ID, device ID) received from the entrance side card reader 25 of the security gate 20 is a legitimate one, the elevator unit allocation control security server 100 uses the user ID as the user ID. With reference to the corresponding group number, it is determined whether or not the user related to the user ID belongs to the group. Then, when the user related to the user ID received from the entrance side card reader 25 does not belong to the group, the security server 100 reads the destination floor information corresponding to the user ID from the user DB. Then, the destination floor information, the departure floor information, and the device ID of the security gate 20 are transmitted to the group management control device 10 as allocation request information. As the departure floor information, as described above, the installation floor information corresponding to the device ID of the entrance side card reader 25 is used.

On the other hand, when the user belongs to the group, the security server 100 reads the destination floor information corresponding to the user ID from the user DB. Further, the security server 100 refers to the user DB and refers to the entry flags of all the user IDs having the same group number as the group number corresponding to the user ID, and is not currently in the entry state. Find the number of people (number of non-entrants). Then, the destination floor information corresponding to the user ID, the departure floor information, the device ID of the security gate 20 in which the entrance side card reader 25 of the transmission source is installed, the group number, and the number of non-entrants Is transmitted to the group management control device 10 as allocation request information. As the departure floor information, as described above, the installation floor information corresponding to the device ID of the entrance side card reader 25 is used.

When the group management control device 10 receives the allocation request information (destination floor information, departure floor information, device ID, group number, number of non-entering persons) for the group, the users belonging to the group based on the received allocation request information. Determine the assigned unit so that can board the same unit. Then, the group management control device 10 transmits the assigned machine information indicating the determined assigned machine to the gate display 70 of the security gate 20 indicated by the received device ID.

Further, when the group management control device 10 receives the normal allocation request information (destination floor information, departure floor information, device ID), the group management control device 10 determines the allocation unit based on the received allocation request information. Then, the group management control device 10 transmits the assigned machine information indicating the determined assigned machine to the gate display 70 of the security gate 20 indicated by the received device ID.

When the gate display 70 receives the assigned unit information from the group management control device 10, the gate display 70 displays the assigned unit information.

2-1-3. Unit allocation control when the user inputs the destination floor on the destination floor registration device If the user misses the assigned unit, or it is necessary to go to a floor other than the destination floor registered corresponding to the ID card. In some cases, the user can specify the destination floor by the destination floor registration device 30. The unit allocation control by the group management system in this case will be described in chronological order.

When the user inputs the destination floor to the operation unit 35, the destination floor registration device 30 includes the destination floor information indicating the input destination floor, the departure floor information, and the destination floor registration device 30 of the destination floor registration device 30. The device ID and the device ID are transmitted to the group management control device 10 as allocation request information. The destination floor registration device 30 stores the installation floor information of the own device, and sets the storage floor related to the stored installation floor information of the own device as the departure floor related to the departure floor information.

When the group management control device 10 receives the allocation request information (destination floor information, departure floor information, device ID), the group management control device 10 determines the allocation unit based on the destination floor information and the departure floor information included in the received allocation request information. Then, the group management control device 10 transmits the assigned machine information indicating the determined assigned machine to the destination floor registration device 30 indicated by the received device ID.

When the destination floor registration device 30 receives the assigned machine information from the group management control device 10, the destination floor registration device 30 displays the assigned machine information.

2-2. Specific operation 2-2-1. Specific operations of the security server The specific operations of the group management system will be explained. First, the processing performed by the security server 100 when the user passes through the security gate 20 will be described. FIG. 13 is a flowchart showing the operation of the security server 100 according to the first embodiment.

When the entrance side card reader 25 and the exit side card reader 29 (hereinafter, both are appropriately collectively referred to as "card readers 25 and 29") read the user ID from the ID card, the read user ID and the card concerned. The device ID of the reader 25 or 29 is transmitted to the security server 100 as ID information.

The security server 100 (control unit 101) determines whether or not ID information (user ID, device ID) has been received from any of the plurality of card readers 25 and 29 (S11).

If the ID information (user ID, device ID) has not been received (NO in S11), the security server 100 (control unit 101) re-executes the determination in this step S11.

When ID information (user ID, device ID) is received from any of the plurality of card readers 25 and 29 (YES in S11), the security server 100 receives the ID information from the entrance side card reader 25 of the security gate. Is determined (S12). The security server 100 stores, for example, the device ID of each card reader and the card reader identification information indicating whether each card reader is the entrance side card reader 25 or the exit side card reader 29 in association with each other by a table or the like. When the ID information is received, the card reader identification information corresponding to the received device ID is acquired, and based on the acquired device ID card reader identification information, the entrance side card reader 25 or the exit side Determine if it is a card reader 29.

When the ID information is received from the entrance side card reader 25 (YES in S12), the security server 100 authenticates whether or not the user ID included in the received ID information is legitimate (S13). For example, the control unit 101 of the security server 100 refers to the user DB stored in the storage unit 102, and the user ID included in the received ID information is registered as the user ID of the user DB. Make a judgment such as whether or not.

If it is determined that the user ID is legitimate (YES in S13), that is, if the authentication is successful, the control unit 101 of the security server 100 determines whether or not the received user ID is a user ID belonging to the group. Is determined (S14). Specifically, the control unit 101 of the security server 100 determines whether or not a group number is registered in association with the received user ID in the user DB.

If the user ID does not belong to the group (NO in S14), the control unit 101 of the security server 100 refers to the user DB stored in the storage unit 102 and acquires the destination floor information corresponding to the user ID. (S15).

The control unit 101 of the security server 100 assigns the acquired destination floor information, the departure floor information, and the device ID of the security gate 20 in which the entrance side card reader 25 of the source of the received ID information is arranged. Is transmitted to the group management control device 10 (S16). As the departure floor information, as described above, the installation floor information corresponding to the device ID of the entrance side card reader 25 is used.

When the ID belongs to a group (YES in S14), the control unit 101 of the security server 100 acquires the group number corresponding to the user ID from the user DB (S17).

The control unit 101 of the security server 100 obtains the number of users who do not exist in the specific area among the users belonging to the group of the acquired group number (hereinafter, referred to as “the number of non-entrants”) (S18). .. For example, the control unit 101 of the security server 100 uses the user DB to set an entry flag other than the user ID received this time among the user IDs associated with the same group number as the acquired group number. Count the number of user IDs that are "OFF". The process of updating the entry flag will be described later.

The control unit 101 of the security server 100 refers to the user DB stored in the storage unit 102 to acquire the destination floor information corresponding to the user ID (S19).

The control unit 101 of the security server 100 includes the acquired destination floor information, the departure floor information, the device ID of the security gate 20 in which the entrance side card reader 25 of the source of the received ID information is arranged, the group number, and the group number. The number of non-entrants is transmitted to the group management control device 10 as allocation request information (S20). As the departure floor information, as described above, the installation floor information corresponding to the device ID of the entrance side card reader 25 is used.

The control unit 101 of the security server 100 transmits a gate OPEN signal to the security gate 20 (S21). Upon receiving the gate OPEN signal, the control unit 21 of the security gate 20 controls the gate flapper 28 in an open state, enabling the user to pass through the security gate 20.

The control unit 101 of the security server 100 sets the entry flag corresponding to the user ID in the user DB to "ON" indicating that the user corresponding to the user ID exists in the specific area. (S22).

On the other hand, if it is determined in step S13 that the user ID is not legitimate (NO in S13), that is, if authentication is not established, the control unit 101 of the security server 100 sends a gate CLOSE signal to the security gate 20. Transmit (S23). Upon receiving the gate CLOSE signal, the control unit 21 of the security gate 20 controls the gate flapper 28 in a closed state and restricts the user from passing through the security gate 20.

Further, in step S12, when it is determined that the ID information is not received from the entrance side card reader 25 (NO in S13), that is, when the ID information is received from the exit side card reader 29, the security server 100 The control unit 101 transmits a gate OPEN signal to the security gate 20 (S24). Upon receiving the gate OPEN signal, the control unit 21 of the security gate 20 controls the gate flapper 28 in an open state, enabling the user to pass through the security gate 20.

The control unit 101 of the security server 100 sets the entry flag corresponding to the user ID in the user DB to "OFF" indicating that the user corresponding to the user ID does not exist in the specific area. (S25).

2-2-2. Specific operation of the group management control device The process of determining the assigned unit by the group management control device 10 will be described. FIG. 14 is a flowchart showing the operation of the group management control device 10 according to the first embodiment.

The group management control device 10 determines whether or not the allocation request information has been received from the security server 100 (S31).

If not received (NO in S31), the group management control device 10 re-executes the process of step S31.

When it is received (YES in S31), the group management control device 10 determines whether or not the group number is included in the allocation request information (S32).

When the group number is not included (NO in S32), the group management control device 10 determines the allocation unit for each user instead of the group by the usual allocation method (S36).

When the group number is included (YES in S32), the group management control device 10 determines whether or not the group allocation information for the group number is registered in the group allocation DB (S33). Here, the group allocation information is deleted when a predetermined time T has elapsed since it was registered as described later. Therefore, if the predetermined time T has not elapsed since the group allocation information for the group number was registered, the determination is YES.

FIG. 15 is a diagram showing a configuration of a group allocation DB stored in the storage unit 12 of the group management control device 10 in the first embodiment. The group allocation DB stores group allocation information for each group of users including a plurality of people. The group allocation information is registered in the group allocation DB when the first user constituting the group passes through, is retained for a predetermined time C, and is deleted when the predetermined time C elapses. The group allocation DB records the group number, the group allocation unit, and the gate passage time in association with each other.

The group number is an identification number of a group composed of a plurality of users.

The group allocation machine is an allocation machine assigned for the users of the group at the time of passing by the first user among the users belonging to the group indicated by the group number. The first user is the first user to pass in the group after the user belonging to the group has not passed for a predetermined time C or more.

The gate passage time is the time when the first user belonging to the group passes through the security gate 20.

In the example shown in FIG. 15, "A" is recorded as the group allocation unit in association with the group number "1", and 15h55m15s is recorded as the gate passage time. Further, "C" is recorded as the group allocation machine in association with the group number "2", and 15h55m20s is recorded as the gate passage time.

Returning to the flowchart of FIG. 14, when the group allocation information for the group number is registered in the group allocation DB (YES in S33), the group management control device 10 records in association with the group number in the group allocation DB. The group allocation unit for the group, which has been set, is set as the allocation unit (S34).

When the group allocation information for the group number is not registered in the group allocation DB (NO in S33), the group management control device 10 determines the allocation unit for the group by the allocation method described later (S35).

When the assigned unit is determined in any of the steps S34, S35, and S36, the group management control device 10 receives the assigned unit information indicating the determined assigned unit in the security gate 20 corresponding to the received device ID. It is transmitted to the gate display 70 (S37).

2-2-2-1. Assignment machine determination operation when the allocation number is determined individually instead of the group Next, the determination operation when the allocation number is determined individually instead of the group in step S36 described above will be specifically described. FIG. 16A is a flowchart showing the determination operation of the assigned unit for the group in the group management control device 10 according to the first embodiment.

The group management control device 10 sets 1 as the car number i (S41A). Since the car and the machine have a one-to-one correspondence, the car number i is also the number of the machine. In this embodiment, six elevators 60A to 60F are provided, so i is 1 to 6.

The group management control device 10 determines whether or not unloaded and / or full passage occurs when one call from the departure floor to the destination floor indicated by the allocation request information received this time is assigned to the unit i (S42A). ). Various known methods can be used to determine whether or not unloaded and / or full passage occurs, and can be performed, for example, as follows. That is, new calls are temporarily assigned to each unit, and the number of people in the car of each unit when each unit departs or arrives on each floor is counted, and the service is completed among the calls received so far. Obtained by accumulating the number of people corresponding to calls that have not been made. Then, by determining whether or not the obtained number of people exceeds the predetermined number of people set based on the capacity of the car, etc., it is determined whether or not unloaded and / or full passage occurs. be able to.

If no unloaded and / or full passage occurs (NO in S42A), the group management control device 10 adds Unit i as an allocation candidate unit (S43A).

On the other hand, when unloaded and / or full passage occurs (YES in S42A), the group management control device 10 does not add Unit i as an allocation candidate unit (S44A).

When it is determined that the unit i is set as the allocation candidate unit (S43A) or not set (S44A), the group management control device 10 sets the current i plus 1 as the car number i (S45A). ..

The group management control device 10 determines whether or not the car number i is a value larger than the number of elevators 60 (S46A). That is, the group management control device 10 determines whether or not the processes from S42A to S44A have been completed for all the elevators 60 (units).

When the processing for all elevators 60 (units) is not completed (NO in S46A), the group management control device 10 executes the processing related to S42A to S44A for the next unit.

When the processing is completed for all the elevators 60 (units) (YES in S46A), the group management control device 10 determines whether or not the allocation candidate units exist (S47A).

If there is no allocation candidate unit (NO in S47A), the group management control device 10 selects the optimum unit from all the units according to a predetermined rule and assigns it to the call related to the allocation request information received this time (NO). Determine the assigned machine) (S52A).

When the allocation candidate unit exists (YES in S47A), the group management control device 10 selects the optimum unit from the allocation candidate units according to a predetermined rule and assigns it to the call related to the allocation request information received this time. (Determine the assigned unit) (S48A).

The selection of the assigned machine in steps S52A and S48A is performed as follows, for example. For example, the group management control device 10 first sets an evaluation value for each elevator (unit) for selecting an elevator (assignment unit) to which the destination floor related to the destination floor call is to be assigned, based on the operation information of each elevator. calculate. Here, the operation information of each elevator is, for example, the car state of each elevator (including the car position, the traveling direction, the open / closed state of the door, the load, etc.), the predicted waiting time (the assigned unit arrives at the departure floor). Time to service), expected service completion time (time until the assigned machine arrives at the destination floor), scheduled number of car outages (scheduled elevator stoppage before service completion), etc. Contains information. After calculating the evaluation value, the group management control device 10 selects, for example, the elevator having the highest evaluation value from the elevators 60A to 60F, and assigns the destination floor to the selected elevator. In addition to this method, the group management control device 10 may allocate the destination floor to any elevator by using another generally known method.

2-2-2-2. Assignment machine determination operation when determining the allocation number for the group Next, the assignment number determination operation for the group in step S35 described above will be specifically described. FIG. 16B is a flowchart showing the determination operation of the assigned unit for the group in the group management control device 10 according to the first embodiment. Since S41B to S52B perform the same processing as S41A to S52A of FIG. 16A except for S42B, the differences from FIG. 16A will be mainly described.

When the group management control device 10 sets 1 as the car number i (S41B), when the calls from the departure floor to the destination floor indicated by the allocation request information received this time are assigned to the unit i for the number of non-entrants. , Judgment whether or not unloaded and / or full passage occurs (S42B).

When the unloaded and / or full passage does not occur (NO in S42B), the group management control device 10 adds the unit i as an allocation candidate unit (S43B), while the unloaded and / or the full passage occurs (S42B). YES), the group management control device 10 sets a value obtained by adding 1 to the current i as the car number i (S45B) without adding the i unit as the allocation candidate unit (S44B).

Then, in steps S45B to S48B and S52B, the same processing as in the case of performing individual allocation instead of group allocation is performed.

When the group management control device 10 determines the optimum allocation unit from the allocation candidate units in step S48B, the group management control device 10 sets the current time as the gate passage time (S49B).

The group management control device 10 sets the assigned machine determined in step S48B as the group assigned machine to be assigned to the group to which the user who has passed the security gate 20 this time belongs (S50B).

The group management control device 10 associates the gate passage time set in step S49B and the group allocation machine name set in step S50B with the group number of the group to which the user who has passed the security gate 20 belongs this time, and associates the group allocation DB. Register in (S51B).

Here, in step S48B, when the optimum allocation unit is determined from the allocation candidate units for the group at the time of the first user entry, the group management control device 10 further calls for the number of non-entrants. Is determined at the same time, and the allocation is confirmed for the calls for the remaining number of non-entrants. In addition, in the determination of steps S42A and S42B for other new calls (new calls other than the group concerned) thereafter, it is assumed that the above-mentioned calls for the number of non-entrants have been allocated, and a judgment regarding unloaded or full passage is made. .. As a result, if the remaining users of the group pass through the group management control device 10 within a predetermined time C after the first user of the group passes, the remaining non-entrants of the group are notified. The same unit as the first user can be reliably assigned. Even if the allocation is not confirmed for the calls for the remaining number of non-entrants, it is possible to allocate the remaining non-entrants to the same unit as long as the occupancy rate of the group allocation unit is not extremely high. Highly sexual.

Even if the allocation for the number of non-entrants is confirmed as described above, the number of non-entrants may not pass within the predetermined time C. In this case, the group management control device 10 cancels the call for the number of users who did not pass, and in steps S42A and S42B, subtracts the number of users who did not pass and allocates a new call thereafter. In such a case, a judgment may be made regarding the occurrence of unloaded cargo or overcrowded passage. As a result, it is possible to assign other calls to the unit as much as the number of non-entrants who do not board.

2-2-2-3. Group allocation DB update operation The operation of updating the group allocation DB by the group management control device 10 will be described. FIG. 17 is a flowchart showing an update operation of the group allocation DB of the group management control device according to the first embodiment.

The group management control device 10 determines whether or not the group allocation information (group number, group allocation unit, gate passage time) is registered in the group allocation DB (S61).

When the group allocation information is not registered (NO in S61), the group management control device 10 counts the time T seconds (after the time T seconds have elapsed) (S66), and then executes the process of step S61 again. .. The time T is an update cycle of the group allocation DB, and is, for example, 0.5 seconds. The time T may be shorter than 0.5 seconds.

When the group allocation information is registered (YES in S61), the group management control device 10 acquires the gate passage time included in the group allocation information of one group (S62).

The group management control device 10 determines whether or not the current time is larger than the time when the predetermined time C is added to the gate passing time, that is, whether or not the time when the predetermined time C is added to the gate passing time has passed. (S63). The predetermined time C is a time slightly longer than the time during which a predetermined number of users forming the group can pass through the security gate at a general walking speed, and is set to, for example, 10 seconds. The predetermined number of people is, for example, five. The predetermined time C may be longer or shorter than 10 seconds, but if it is too short, the users forming the group may not be able to pass within the predetermined time C, and the group may not be assigned. ..

When the current time has passed the time obtained by adding the predetermined time C to the gate passing time (YES in S63), the group management control device 10 has the group allocation information (group number, group) corresponding to the gate passing time acquired this time. (Assigned machine, gate passage time) is deleted (S64).

When the current time does not pass the time obtained by adding the predetermined time C to the gate passing time (NO in S63), or when the group allocation information is deleted in step S64, the group management control device 10 registers in the group allocation DB. It is determined whether or not the determination process of step S63 is completed for all the group allocation information that has been performed (S65).

When the determination process for all the group allocation information is not completed (NO in S65), the group management control device 10 re-executes the processes of steps S62 to S64.

When the above processing for all the group allocation information is completed (YES in S65), the group management control device 10 waits for the time T seconds to elapse in the above step S66, and then executes the processing after step S61 again. To do.

2-2-2-4. Specific Example of Assignment Operation for Group of Group Management Control Device A specific example of allocation operation for a group of group management control device 10 will be described. FIG. 18 is an explanatory diagram of the allocation operation for the group of the group management control device 10 according to the first embodiment.

FIG. 18A shows an example in which eight users P1 to P8 pass through the security gate 20 while holding their respective ID cards from the entrance 20i side to the exit 20e side. Of these, four users P1, P3, P6, and P8 are all users belonging to the same group and are not within the specific area. In this case, when the first user P1 of the group passes through the security gate 20, the security server 100 calculates that the number of non-entrants is 4 based on the entry flag, and determines the number of non-entrants and the gate passage time. The allocation request information including the allocation request information is transmitted to the group management control device 10. Then, in the group management control device 10, the gate passage time is recorded in the allocation DB, and the counting of the elapsed time from the gate passage time starts. Then, when the group management control device 10 determines that there is a unit capable of assigning users P1, P3, P6, and P8 for the number of non-entrants, in this example, four users, the unit is designated as the group allocation unit. Set. Then, as shown in FIG. 18A, when all the users belonging to the same group pass through the group management control device 10 within a predetermined time C from the gate passage time, the four users P1, P3, P6, The group allocation machine is assigned to all of P8. As a result, the four users P1, P3, P6, and P8 can board the same unit.

On the other hand, as shown in FIG. 18B, of the four users P1, P3, P6, and P8 of the same group, only three users P1, P3, and P6 are within the predetermined time C from the gate passage time. When passing through the security gate 20, the group management control device 10 assigns the same group allocation unit to the three users P1, P3, and P6. As a result, the three users P1, P3, and P6 can board the same unit. The same unit will not be assigned to the user P8, but if the predetermined time C is lengthened, it becomes necessary to delay the departure time so that the user P8 does not miss the boarding, and the transportation efficiency in the elevator group decreases. May lead to. Therefore, the predetermined time C is preferably set to, for example, about 10 seconds as described above.

Further, as shown in FIG. 18C, when one user P8 among the four users P1, P3, P6, and P8 of the same group already exists in the specific area, the beginning of the group. When the user P1 passes through the security gate 20, the security server 100 calculates that the number of non-entrants is 3 based on the entry flag, and the allocation request information including the number of non-entrants and the gate passage time is group-managed. It is transmitted to the control device 10. Then, in the group management control device 10, the gate passage time is recorded in the allocation DB, and the counting of the elapsed time from the gate passage time starts. Then, when it is determined that there is a unit capable of assigning users P1, P3, and P6 for the number of non-enterers, in this example, three users, the unit is set as a group allocation unit. Then, as shown in FIG. 18C, when all the users belonging to the same group pass through the group management control device 10 within a predetermined time C from the gate passage time, the three users P1, P3, and P6 The group allocation machine is assigned to all. As a result, the three users P1, P3, and P6 can board the same unit. As described above, in the example of FIG. 18C, since the user P8 already existing in the specific area is not assigned, no extra allocation is made and another user is assigned to the machine. It becomes possible. Therefore, even though group allocation is performed, there is almost no effect on transportation efficiency.

2-3. Example of use of group allocation in the present embodiment The user may be a tenant in an office building, a worker at a company, a resident of a condominium, or a visitor to an office building or a condominium. In this case, the visitor and the guide may be temporarily registered as users of one group. For example, an ID card registered as a group may be temporarily created for the visitor, and the guide may distribute the ID card to the visitor before passing through the security gate. By doing so, the guide and the visitor can board the same machine. In this case, after the visitor returns, the ID card is collected and the group registration is deleted.

(Embodiment 2)
In the first embodiment, if there is no elevator that can allocate calls for the number of non-entrants among the users forming the group, the group is not assigned. However, even if not all calls for the number of non-entrants can be assigned, only the number of people who can be assigned may be assigned as a group. A specific example thereof will be described below.

FIG. 19 is a flowchart showing the operation of the group management control device 10 according to the second embodiment.

In steps S71 to S73 and S77, the same processing as in steps S31 to S33 and S36 of the flowchart of FIG. 14 of the first embodiment is performed.

If it is determined in step S73 that the registration is registered (YES in S73), the group management control device 10 determines the allocation unit for the group by the allocation method described later (S76).

On the other hand, when it is determined in step S73 that the group is not registered (NO in S73), the group management control device 10 is left unloaded and / when assigned to the group allocation unit registered for the group in the group allocation DB. Alternatively, it is determined whether or not a full passage occurs (S74). As will be described later, in the present embodiment, even if the calls for the number of non-entrants in one group cannot be assigned, only the number of people who can be assigned is assigned as a group. In order to achieve this, for each user ID related to the group, whether or not it can be assigned to the group allocation machine, that is, whether or not unloaded and / or full passage occurs, is determined for each passage of the users who make up the group. to decide.

When unloaded and / or full passage occurs (YES in S74), in step S76, the group allocation unit for the group is determined by the allocation method described later.

When the unloaded and / or the full passage does not occur (NO in S74), the group management control device 10 sets the group allocation unit for the group, which is recorded in association with the group number in the group allocation DB, as the allocation unit. Is set as (S75).

When the assigned unit is determined in any of the steps S75, S76, and S77, the group management control device 10 receives the assigned unit information indicating the determined assigned unit in the security gate 20 corresponding to the received device ID. It is transmitted to the gate display 70 (S78).

Next, the operation of determining the assigned unit for the group in step S76 will be specifically described. FIG. 20 is a flowchart showing an operation of determining an assigned unit for a group in the group management control device 10 according to the second embodiment. In this flowchart, a process similar to the process according to the flowchart of FIG. 15 of the first embodiment is performed. Therefore, the differences will be mainly described.

The group management control device 10 sets 0 as the unassignable number p (S81). The non-allocation number p is the number of people that cannot be allocated when allocating as a group the users corresponding to the number of non-entering persons forming the group.

The group management control device 10 sets 1 as the car number i (S82). Since the car and the machine have a one-to-one correspondence, the car number i is also the number of the machine. In this embodiment, six elevators 60A to 60F are provided, so i is 1 to 6.

When the group management control device 10 allocates the calls from the departure floor to the destination floor indicated by the allocation request information received this time to the number i, which is obtained by subtracting the unassignable number p from the number of non-entrants, the group management control device 10 is left unloaded. / Or determine whether or not a full passage occurs (S83).

When the unloaded and / or the full passage does not occur (NO in S83), the group management control device 10 adds the unit i as the allocation candidate unit (S84). On the other hand, when unloaded and / or full passage occurs (YES in S83), the group management control device 10 does not add Unit i as an allocation candidate unit (S85).

In subsequent steps S86 to S92, the same processing as in steps S45 to S51 of the first embodiment is performed.

Here, when it is determined in step S88 that the allocation candidate unit does not exist (NO in S88), in the present embodiment, the group management control device 10 adds 1 to the unassignable number p (S93), and is not. It is determined whether or not the number of people who entered the room minus the number of people who cannot be assigned p is larger than 1 (S94).

When the number of people obtained by subtracting the unassignable number p from the number of non-entrants is larger than 1 (YES in S94), the group management control device 10 returns to step S82 and executes the subsequent processing. That is, the group management control device 10 determines whether or not unloaded and / or full passage occurs for each unit based on the number of non-entering persons minus the number of unassignable persons p (S83). .. Then, according to the determination result, the group management control device 10 determines whether or not to add the unit i as the allocation candidate unit (S84 or S85). If there is an allocation candidate machine (YES in S88), the processes of steps S89 to S92 relating to group allocation are performed.

When the number of people who cannot be assigned by subtracting the unassignable number p from the number of non-entrants is not larger than 1 (NO in S94), the group management control device 10 selects the optimum unit from all the units according to a predetermined rule. Then, it is assigned to the call related to the allocation request information received this time (determine the allocation number) (S95).

According to the present embodiment having the above-described configuration, when it is not possible to allocate calls for all the non-entering persons, it is possible to allocate as a group only for the number of assignable persons.

(Summary of embodiments)
(1) The elevator group management control device 10 according to the first and second embodiments has a user ID (user information) acquired by a security gate 20 (information acquisition device) arranged on or near the route to the landing. ), The call related to the allocation request information generated by the security server 100 (allocation request generator) is assigned to any of the plurality of elevators 60.
When the user ID (user information) is acquired by the security gate 20 (information acquisition device), the security server 100 (assignment request generation device) uses the user ID (user information) based on the user ID (user information). Is configured to output allocation request information including a group number (group identification information) indicating the group to which the user belongs to the group management control device 10 when it is determined that the user belongs to a group composed of a plurality of users. Has been done.
The group management control device 10 includes a control unit 11 that assigns a call based on allocation request information to any one of a plurality of elevators 60.
The control unit 11
When the allocation request information including the group number (group identification information) is received from the security server 100 (allocation request generator), the allocation request information received this time within the predetermined time C before receiving the allocation request information is added to the allocation request information. It is determined whether or not the allocation request information including the same group number (group identification information) as the included group number (group identification information) is acquired from the security server 100 (assignment request generator).
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time C elapses after the reception. , The second call related to the allocation request information including the same group number (group identification information) as the group number (group identification information) included in the allocation request information received this time is assigned to the same unit.

As a result, a plurality of users can be assigned to the same machine as a group based on the user ID (user information) acquired by the security gate 20 (information acquisition device).

(2) In the elevator group management control device 10 according to the first and second embodiments.
When the security server 100 (assignment request generation device) acquires a user ID (user information), the security server 100 (assignment request generation device) is a group in which a user is composed of a plurality of users based on the user ID (user information). When it is determined that the group belongs to, the allocation request information including the group number (group identification information) and the information indicating the number of users constituting the group is output to the group management control device 10.
The control unit 11
When the first call is received, it is determined whether or not there is a unit that can assign calls for the number of users that make up the group.
If there is an assignable unit, one of the assignable units is set as a group allocation candidate unit for assigning calls for the number of users who make up the group.
The group allocation candidate unit is assigned as the allocation unit for the second call received before the predetermined time C elapses.

As a result, the same unit can be assigned to the users who make up the group.

(3) In the elevator group management control device 10 according to the second embodiment.
The control unit 11
If there is no unit that can assign calls for the number of users that make up the group, one unit that meets the predetermined conditions is assigned the number of users that can be assigned among the users that make up the group. Set as a group allocation candidate machine for
Of the second calls received before the lapse of the predetermined time C, the group allocation candidate units are assigned as the allocation units for the calls for the number of assignable users.

As a result, the same unit can be assigned to the number of users who can be assigned among the users who make up the group.

(4) In the elevator group management control device 10 according to the first and second embodiments.
The security gate 20 (information acquisition device) is
An entrance-side card reader 25 (first information acquisition unit) that acquires a user ID (user information) from an ID card (identification medium) possessed by a user who enters the inside of a specific area.
It has an exit-side card reader 29 (second information acquisition unit) that acquires a user ID (user information) from an ID card (identification medium) possessed by a user who exits from a specific area.
The security server 100 (assignment request generator)
When the user ID (user information) is acquired by the entrance side card reader 25 (first information acquisition unit), the user is a user group based on the allocation request information received from the security gate 20 (information acquisition device). While judging whether or not it belongs to
It is determined whether the user ID (user information) has been acquired by either the entrance side card reader 25 (first information acquisition unit) or the exit side card reader 29 (second information acquisition unit).
(A) When it is determined that the user ID (user information) has been acquired by the entrance side card reader 25 (first information acquisition unit) that belongs to the group, the user indicated by the user ID (user information) Register the information indicating that you are in the room (entrance flag ON) and
And / or (b) When it is determined that the user ID (user information) belongs to the group and the exit side card reader 29 (second information acquisition unit) has acquired the user ID (user information), the user ID (user information) indicates. Register information indicating that the user has not entered the room (entrance flag OFF).
The security server 100 (assignment request generator)
As the number of users forming the group, the number of users obtained based on the information indicating that the room is entered and / or the information indicating that the room is not entered is set.

As a result, the number of users (number of non-entrants) obtained based on the information indicating that the room is entered and / or the information indicating that the room is not entered is set as the number of users constituting the group. That is, the number of users (number of non-entrants) according to the current situation is set as the number of users forming the group. Therefore, there is no need to group-assign users who are not expected to board the unit to which the group has been assigned. Therefore, it is possible to allocate other users to the machine to which the group allocation has been performed. In other words, group allocation can be performed while considering transportation efficiency.

(5) The elevator system according to the first and second embodiments is
Security server 100 (assignment request generator) based on user IDs (user information) acquired by a plurality of elevators 60 and a security gate 20 (information acquisition device) arranged on or near the route to the landing. ), It has an elevator group management control device 10 that assigns a call related to the allocation request information to any one of a plurality of elevators 60.
When the user ID (user information) is acquired by the security gate 20 (information acquisition device), the security server 100 (assignment request generation device) uses the user ID (user information) based on the user ID (user information). Is configured to output allocation request information including a group number (group identification information) indicating the group to which the user belongs to the group management control device 10 when it is determined that the user belongs to a group composed of a plurality of users. Has been done.
The group management control device 10 includes a control unit 11 that assigns a call based on allocation request information to any one of a plurality of elevators 60.
The control unit 11
When the allocation request information including the group number (group identification information) is received from the security server 100 (allocation request generator), the allocation request information received this time within the predetermined time C before receiving the allocation request information is added to the allocation request information. It is determined whether or not the allocation request information including the same group number (group identification information) as the included group number (group identification information) is acquired from the security server 100 (assignment request generator).
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time C elapses after the reception. , The second call related to the allocation request information including the same group number (group identification information) as the group number (group identification information) included in the allocation request information received this time is assigned to the same unit.

As a result, the above effect can be obtained in an elevator system having a plurality of elevators 60 and an elevator group management control device 10.

(6) The elevator group management system according to the first and second embodiments is
Allocation request information is generated based on the security gate 20 (information acquisition device) arranged on or near the route to the landing and the user ID (user information) acquired by the security gate 20 (information acquisition device). A group management control device for an elevator that assigns a call related to the allocation request information generated by the security server 100 (allocation request generation device) and the security server 100 (allocation request generation device) to any one of a plurality of elevators 60. 10 and.
When the user ID (user information) is acquired by the security gate 20 (information acquisition device), the security server 100 (assignment request generation device) uses the user ID (user information) based on the user ID (user information). Is configured to output allocation request information including a group number (group identification information) indicating the group to which the user belongs to the group management control device 10 when it is determined that the user belongs to a group composed of a plurality of users. Has been done.
The group management control device 10 includes a control unit 11 that assigns a call based on allocation request information to any one of a plurality of elevators 60.
The control unit 11
When the allocation request information including the group number (group identification information) is received from the security server 100 (allocation request generator), the allocation request information received this time within the predetermined time C before receiving the allocation request information is added to the allocation request information. It is determined whether or not the allocation request information including the same group number (group identification information) as the included group number (group identification information) is acquired from the security server 100 (assignment request generator).
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time C elapses after the reception. , The second call related to the allocation request information including the same group number (group identification information) as the group number (group identification information) included in the allocation request information received this time is assigned to the same unit.

As a result, the above effect can be obtained in an elevator group management system having a security gate 20 (information acquisition device), a security server 100 (assignment request generation device), and an elevator group management control device 10.

(7) The elevator system according to the first and second embodiments is
To a plurality of elevators 60, a security gate 20 (information acquisition device) arranged on or near the route to the landing, and a user ID (user information) acquired by the security gate 20 (information acquisition device). A call related to the allocation request information generated by the security server 100 (allocation request generator) that generates the allocation request information based on the security server 100 (allocation request generator) is sent to any of the plurality of elevators 60. It has a group management control device 10 for elevators to be assigned.
When the user ID (user information) is acquired by the security gate 20 (information acquisition device), the security server 100 (assignment request generation device) uses the user ID (user information) based on the user ID (user information). Is configured to output allocation request information including a group number (group identification information) indicating the group to which the user belongs to the group management control device 10 when it is determined that the user belongs to a group composed of a plurality of users. Has been done.
The group management control device 10 includes a control unit 11 that assigns a call based on allocation request information to any one of a plurality of elevators 60.
The control unit 11
When the allocation request information including the group number (group identification information) is received from the security server 100 (allocation request generator), the allocation request information received this time within the predetermined time C before receiving the allocation request information is added to the allocation request information. It is determined whether or not the allocation request information including the same group number (group identification information) as the included group number (group identification information) is acquired from the security server 100 (assignment request generator).
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received before the predetermined time C elapses after the reception. , The second call related to the allocation request information including the same group number (group identification information) as the group number (group identification information) included in the allocation request information received this time is assigned to the same unit.

As a result, the above effect can be obtained in an elevator system having a plurality of elevators 60, a security gate 20 (information acquisition device), a security server 100 (assignment request generation device), and an elevator group management control device 10. ..

(Other embodiments)
In each of the above-described embodiments, when performing group allocation, the number of non-entering persons is obtained, and the calls for the number of non-entering persons are assigned to the unit. However, instead of the number of non-entrants, the number of calls for all the users registered as users belonging to the group may be assigned to the unit. In this case, even the number of occupants already in the building is allocated, but it is not necessary to count the number of non-entrants, and the configuration of the security server 100 can be simplified.

In S42A, S42B, and S83 of the flowchart of each of the above-described embodiments, the case where the destination floors of the users forming the group are the same floor has been described. However, the destination floors of the users who make up the group may be different. In this case, in S42A, S42B and S83, it is judged that each destination floor of each non-entry user has passed or left unloaded, and as a result of the judgment about each destination floor, all of these destination floors have passed and are full. Units that do not cause leftovers may be set as group allocation units.

In each of the above embodiments, the card readers 25 and 29 are exemplified as the first and second information acquisition units of the present invention. However, the first and second information acquisition units are not limited to card readers, and may be, for example, NFC (Near Field Communication) readers. Further, the medium for storing the user ID is not limited to an ID card (IC card), and may be, for example, a mobile terminal such as a smartphone that supports NFC communication.

Further, the first and second information acquisition units may be a fingerprint reading device capable of reading a fingerprint or an IC tag reader capable of communicating with an IC tag.

In each of the above-described embodiments, the control units 11, 21, 31, 41, 71, 101 are configured by using a CPU, MPU, or the like, and are used as programs read from the storage units 12, 22, 32, 42, 72, 102. Based on this, various functions are realized by performing arithmetic processing using various data and the like. That is, each of the control units 11, 21, 31, 41, 71, 101 is realized by the cooperation of hardware and software. However, each control unit 11, 21, 31, 41, 71, 101 may be configured by using, for example, only hardware (electronic circuit), FPGA, ASIC, or the like.

In each of the above embodiments, the network NW is Ethernet (registered trademark), and the input / output interfaces 13, 23, 24, 33, 43, 73, and 103 are configured by using a LAN adapter or the like. However, the network NW is, for example, a wireless LAN conforming to the IEEE standard, and the input / output interfaces 13, 23, 24, 33, 43, 73, 103 may be configured by using a wireless LAN adapter or the like.

In each of the above embodiments, the card readers 25 and 29 are connected to the input / output interface 23, as described with reference to FIG. However, the card readers 25 and 29 may be connected to the control unit 21. In this case, the user ID read by the card readers 25 and 29 may be transmitted to the security server 100 via the control unit 21 and the input / output interface 23. Further, the device IDs of the card readers 25 and 29 may also be transmitted to the security server 100 not from the card readers 25 and 29 but via the control unit 21 and the input / output interface 23.

10 Group management control device 11 Control unit 12 Storage unit 13 Input / output interface 20, 20A, 20B, 20C Security gate 20a Gate body 20i Entrance 20e Exit 21 Control unit 22 Storage unit 23 I / O interface 25 Entrance side card reader 26 1st sensor 27 Second sensor 28 Gate flapper 29 Exit side card reader 30, 30A to 30Z Destination floor registration device 31 Control unit 32 Storage unit 33 Input / output interface 34 Display unit 35 Operation unit 40, 40A to 40F Elevator control device 41 Control unit 42 Storage Unit 43 Input / output interface 60, 60A to 60F Elevator 70 Gate display 71 Control unit 72 Storage unit 73 Input / output interface 74 Display unit 100 Security server 101 Control unit 102 Storage unit 103 Input / output interface

Claims (6)

Allocation request information generated by the allocation request generator based on the user information acquired by the information acquisition device provided in the security gate when the user passes through the security gate arranged on the route to the landing. It is an elevator group management control device that assigns the call related to to one of the multiple elevators.
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the allocation request generation device is concerned. It is configured to output allocation request information including group identification information indicating the group to which the user belongs and information indicating the number of users constituting the group to the group management control device.
The group management control device includes a control unit that assigns a call based on the allocation request information to any one of the plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the allocation request is made within a predetermined time before the gate passage time when the user related to the allocation request information passes through the security gate. It is determined whether or not the allocation request information including the same group identification information as the group identification information included in the information is acquired from the allocation request generator.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received between the gate passage time and the predetermined time elapses. Therefore, the second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to any one of the same units. Configured
The control unit
When the allocation request information for the first call is received, it is assumed that calls for the number of users constituting the group indicated by the group identification information included in the allocation request information are simultaneously generated, and for the number of users. Allocate the call to the same No. 1 machine to which the call for the number of users can be assigned,
Each time the allocation request information for the second call is received between the time when the gate passes and the predetermined time elapses, the allocated first machine is set as the allocation machine for the second call.
For calls for the number of users who did not pass through the security gate between the time when the gate passed and the predetermined time elapsed, the allocation to the first machine was canceled and other users who did not belong to the group were canceled. Can assign a new call generated when passing through the security gate after the lapse of the predetermined time to the first unit.
Elevator group management control device. The information acquisition device is
The first information acquisition unit that acquires user information from the identification medium possessed by the user who enters the inside of the specific area, and
It has a second information acquisition unit that acquires user information from an identification medium possessed by a user who exits from the specific area.
The allocation request generator is
When the user information is acquired by the first information acquisition unit, it is determined whether or not the user belongs to the user group based on the allocation request information received from the information acquisition device.
It is determined whether or not the user information has been acquired by either the first information acquisition unit or the second information acquisition unit.
(A) When it is determined that the user information belongs to the group and the user information has been acquired by the first information acquisition unit, the information indicating that the user indicated by the user information is in the room is registered.
And / or (b) When it is determined that the user information belongs to the group and the second information acquisition unit has acquired the user information, the information indicating that the user indicated by the user information has not entered the room is registered.
The allocation request generator is
As the number of users constituting the group, the number of users obtained based on the information indicating that the room is entered and / or the information indicating that the room is not entered is set.
The elevator group management control device according to claim 1. It also has a user database that stores user information, destination floors, and group identification information for all users in association with each other.
The group indicated by one group identification information includes users with different destination floors.
The elevator group management control device according to claim 1 or 2. When a user passes through multiple elevators and a security gate located on the route to the landing, the allocation request generator is based on the user information acquired by the information acquisition device provided in the security gate. An elevator system having an elevator group management control device that assigns a call related to the generated allocation request information to any one of the plurality of elevators.
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the allocation request generation device is concerned. It is configured to output allocation request information including group identification information indicating the group to which the user belongs and information indicating the number of users constituting the group to the group management control device.
The group management control device includes a control unit that assigns a call based on the allocation request information to any one of the plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the allocation request is made within a predetermined time before the gate passage time when the user related to the allocation request information passes through the security gate. It is determined whether or not the allocation request information including the same group identification information as the group identification information included in the information is acquired from the allocation request generator.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received between the gate passage time and the predetermined time elapses. Therefore, the second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to any one of the same units. Configured
The control unit
When the allocation request information for the first call is received, it is assumed that calls for the number of users constituting the group indicated by the group identification information included in the allocation request information are simultaneously generated, and for the number of users. Allocate the call to the same No. 1 machine to which the call for the number of users can be assigned,
Each time the allocation request information for the second call is received between the time when the gate passes and the predetermined time elapses, the allocated first machine is set as the allocation machine for the second call.
For calls for the number of users who did not pass through the security gate between the time when the gate passed and the predetermined time elapsed, the allocation to the first machine was canceled and other users who did not belong to the group were canceled. Can assign a new call generated when passing through the security gate after the lapse of the predetermined time to the first unit.
Elevator system. Allocation request information is generated based on the information acquisition device provided in the security gate arranged on the route to the landing and the user information acquired by the information acquisition device when the user passes through the security gate. In an elevator group management system having an allocation request generator and an elevator group management control device that assigns a call related to the allocation request information generated by the allocation request generation device to any one of a plurality of elevators. There,
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the allocation request generation device is concerned. It is configured to output allocation request information including group identification information indicating the group to which the user belongs and information indicating the number of users constituting the group to the group management control device.
The group management control device includes a control unit that assigns a call based on the allocation request information to any one of the plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the allocation request is made within a predetermined time before the gate passage time when the user related to the allocation request information passes through the security gate. It is determined whether or not the allocation request information including the same group identification information as the group identification information included in the information is acquired from the allocation request generator.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received between the gate passage time and the predetermined time elapses. Therefore, the second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to any one of the same units. Configured
The control unit
When the allocation request information for the first call is received, it is assumed that calls for the number of users constituting the group indicated by the group identification information included in the allocation request information are simultaneously generated, and for the number of users. Allocate the call to the same No. 1 machine to which the call for the number of users can be assigned,
Each time the allocation request information for the second call is received between the time when the gate passes and the predetermined time elapses, the allocated first machine is set as the allocation machine for the second call.
For calls for the number of users who did not pass through the security gate between the time when the gate passed and the predetermined time elapsed, the allocation to the first machine was canceled and other users who did not belong to the group were canceled. Can assign a new call generated when passing through the security gate after the lapse of the predetermined time to the first unit.
Elevator group management system. Based on information acquisition devices provided in a plurality of elevators and security gates arranged on the route to the landing, and user information acquired by the information acquisition devices when a user passes through the security gates. It has an allocation request generation device that generates allocation request information, and an elevator group management control device that assigns a call related to the allocation request information generated by the allocation request generation device to any one of the plurality of elevators. It ’s an elevator system,
When the allocation request generation device determines that a user belongs to a group composed of a plurality of users based on the user information when the user information is acquired by the information acquisition device, the allocation request generation device is concerned. It is configured to output allocation request information including group identification information indicating the group to which the user belongs and information indicating the number of users constituting the group to the group management control device.
The group management control device includes a control unit that assigns a call based on the allocation request information to any one of the plurality of elevators.
The control unit
When the allocation request information including the group identification information is received from the allocation request generator, the allocation request is made within a predetermined time before the gate passage time when the user related to the allocation request information passes through the security gate. It is determined whether or not the allocation request information including the same group identification information as the group identification information included in the information is acquired from the allocation request generator.
If it is determined that the information has not been acquired and the predetermined allocation condition is satisfied, the first call related to the allocation request information received this time and the allocation request information received between the gate passage time and the predetermined time elapses. Therefore, the second call related to the allocation request information including the same group identification information as the group identification information included in the allocation request information received this time is assigned to any one of the same units. Configured
The control unit
When the allocation request information for the first call is received, it is assumed that calls for the number of users constituting the group indicated by the group identification information included in the allocation request information are simultaneously generated, and for the number of users. Allocate the call to the same No. 1 machine to which the call for the number of users can be assigned,
Each time the allocation request information for the second call is received between the time when the gate passes and the predetermined time elapses, the allocated first machine is set as the allocation machine for the second call.
For calls for the number of users who did not pass through the security gate between the time when the gate passed and the predetermined time elapsed, the allocation to the first machine was canceled and other users who did not belong to the group were canceled. Can assign a new call generated when passing through the security gate after the lapse of the predetermined time to the first unit.
Elevator system.

Images