JP2023072502A - Elevator group management device, control method of the same, terminal device, and terminal control program - Google Patents

Abstract

To provide an elevator group management device which allocates a car in response to a user's request according to a congestion situation of each car.SOLUTION: An elevator group management device (10) selects a car of an elevator to be allocated based on a riding request and includes: an information acquisition unit (111) which acquires allocation request information; a situation acquisition unit (112) which acquires a congestion level of each car; an allocation unit (113) which allocates a car to which a specified attribute is provided when a car whose congestion level is lower than a specified congestion level does not exist and allocates the car whose congestion level is lower than the specified congestion level when such a car exists; and a notification unit (114) which notifies allocation result information.SELECTED DRAWING: Figure 1

Description

The present invention relates to an elevator group management device, a control method for an elevator group management device, a terminal device that communicates with the elevator group management device, and a terminal control program therefor.

For example, Patent Literature 1 discloses an elevator system that has a control device that operates an elevator and performs destination floor registration before a user gets into the elevator. In this system, a user uses a "call registration application" for performing car call registration that operates on an information terminal device. By means of this "call registration application", the user designates "performance to be emphasized" such as the degree of congestion or exclusive use for women, and a car assigned with an attribute corresponding to the designated performance is assigned.

JP 2014-031263

Whether or not the user wishes to be assigned a dedicated car with specific attributes (for example, only for luggage, only for robots, only for women/men, and only for VIPs) can be determined at the time of requesting boarding. It is conceivable that it differs depending on the degree of congestion of the car. For example, if there is a general-purpose car that is not a dedicated car but has a low degree of congestion, the arrival time to the destination floor when using the general-purpose car is the purpose of using the dedicated car with the desired attribute. If it is earlier than the arrival time to the floor, the user may wish to use the general-purpose car.

An object of one aspect of the present invention is to provide an elevator group management apparatus that allocates a car according to a user's request according to the congestion situation of the cars.

In order to solve the above problems, an elevator group management apparatus according to one aspect of the present invention is an elevator group management apparatus that selects an elevator car to be assigned to a user based on a boarding request from the user. an information acquisition unit for acquiring allocation request information corresponding to the user, including attribute designation information specifying attributes of the car and congestion level setting information; and congestion of each of the plurality of cars. a situation acquisition unit that acquires the level, and when there is no car with a congestion level equal to or lower than the congestion level specified by the congestion level setting information when boarding is scheduled according to the allocation request information, the level specified by the attribute specifying information is determined. While allocating the car to which the attribute of being in a state of being crowded is assigned to the user, if there is a car with a congestion level equal to or lower than the congestion level specified by the congestion level setting information, the car is assigned to the user and a notification unit for notifying the user of allocation result information specifying the car allocated by the allocation unit.

According to the above configuration, when there is a car with a congestion level equal to or lower than the set congestion level, the user selects the car to which other attributes are assigned instead of the car to which the requested attribute is assigned. can be used. Therefore, it is possible to allocate a car according to the user's request according to the congestion situation of the car. In addition, since it is possible to alleviate the concentration of use of a specific car, it is possible to improve the operation efficiency of the elevator group.

In the elevator group management apparatus according to another aspect of the present invention, the information acquiring unit acquires boarding floor information included in the allocation request information, and the allocating unit enables boarding at the boarding floor indicated by the boarding floor information. With respect to the above-mentioned car, if there is no car with a congestion level equal to or lower than that specified by the congestion level setting information, the car to which the attribute specified by the attribute specifying information is assigned is used. On the other hand, if there is a car whose congestion level is equal to or lower than that specified by the congestion level setting information, the car may be allocated to the user.

According to the above configuration, since the car is selected according to the congestion level at the boarding floor, it is possible to allocate the car desired by the user according to the congestion level at the time of boarding.

In the elevator group management apparatus according to another aspect of the present invention, the information acquisition unit acquires the destination floor information included in the allocation request information, and the allocation unit determines the congestion level designated by the congestion level setting information. When the following car is assigned to the user, the congestion level of the car is equal to the congestion level during the period until the car moves from the boarding floor to the destination floor indicated by the destination floor information. Users other than the above users may be assigned to the car so that the congestion level is equal to or less than the congestion level specified by the setting information.

According to the above configuration, when a user is assigned a car with a congestion level equal to or lower than that designated by the congestion level setting information, the car allocation is performed so that the congestion level is equal to or lower than the designated congestion level until arrival at the destination floor. will be done. Therefore, the congestion level desired by the user can be maintained in the period from the time of boarding until arrival at the destination floor.

In the elevator group management apparatus according to another aspect of the present invention, the allocation unit determines the predicted boarding time of the user to the car to be allocated and the destination floor of the user to which the car to be allocated is located. The notification unit notifies the user of prediction information corresponding to at least one of the predicted boarding time and the predicted arrival time, and The allocating unit may determine the allocation of the car when acquiring allocation approval information from the user to whom the prediction information has been notified via the information acquiring unit.

According to the above configuration, the user can determine the allocation of the car after confirming the forecast information, so the user can set the congestion level according to the waiting time.

In the elevator group management apparatus according to another aspect of the present invention, the allocation unit may perform the allocation process during a predetermined time period set in advance.

According to the above configuration, it is possible to perform the allocation process during, for example, a time zone when congestion is expected. Here, in other time periods when congestion is not expected, all cars are expected to be less crowded, and there is little merit for the user to use the car provided with the attribute requested by the user. is expected. In other words, in other time periods when congestion is not expected, the operation efficiency of the elevator group can be improved by allocating cars without considering the designation of attributes desired by users for allocation.

In the elevator group management apparatus according to another aspect of the present invention, the allocating unit determines the number of users including at least one of the number of passengers in the plurality of cars and the number of people waiting in line, or the number of users per unit time. The allocation process may be performed when the number exceeds a predetermined number.

According to the above configuration, it is possible to perform the above allocation process in an actually congested situation. Here, in a situation where it is not actually crowded, it is expected that the degree of congestion in any car is low, and there is little merit for the user to use the car to which the attribute requested by the user is assigned. is expected. In other words, when there is no actual congestion, the elevator group can be operated more efficiently by allocating cars without considering the desired allocation attributes specified by the users.

In the elevator group management apparatus according to another aspect of the present invention, the allocating unit determines the number of users including at least one of the number of passengers in the plurality of cars and the number of people waiting in line, or the number of users per unit time. When the number exceeds a predetermined number of people, the car to which the attribute specified by the attribute specifying information is assigned may be assigned to the user.

According to the above configuration, in a situation where the car is actually congested, the car assigned the attribute specified by the attribute specifying information is assigned without considering the congestion level setting information.

In the elevator group management apparatus according to another aspect of the present invention, the information acquisition unit acquires the allocation request information from the terminal device operated by the user, and the notification unit sends the allocation request information to the terminal device. Result information may be sent.

According to the above configuration, the user can transmit the allocation request information and confirm the allocation result information using the terminal device.

In the elevator group management apparatus according to another aspect of the present invention, the information acquisition unit acquires the allocation request information from a reading device that reads the allocation request information recorded on the recording medium owned by the user. good.

According to the above configuration, the user records the allocation request information in advance on the recording medium and causes the recording medium to be read by the reading device, thereby transmitting the allocation request information to the elevator group management device. can be done.

In the elevator group management device according to another aspect of the present invention, the information acquisition unit receives ID information specifying the user from an authentication device that performs personal authentication of the user, and associates the ID information with the ID information. The allocation request information may be obtained from a recording unit that records the allocation request information.

According to the above configuration, the user can cause the elevator group management apparatus to recognize the allocation request information by recording the allocation request information in advance in the recording unit and performing personal authentication with the authentication device. .

In order to solve the above-described problems, a control method for an elevator group management apparatus according to one aspect of the present invention provides an elevator group control system that selects an elevator car to be assigned to a user based on a boarding request from the user. A control method for a management device, comprising: an information acquisition step of acquiring allocation request information corresponding to the user, including attribute designation information designating attributes of the car and congestion level setting information; a status acquisition step of acquiring the congestion level of each car; While allocating the car to which the attribute specified by the specified information is assigned to the user, when there is a car with a congestion level equal to or lower than the congestion level specified by the congestion level setting information, An allocation step of performing allocation processing for allocating a car to the user, and a notification step of notifying the user of allocation result information specifying the car allocated in the allocation step.

According to the above method, it is possible to allocate a car according to the user's request according to the congestion situation of the car.

In order to solve the above-described problems, a terminal device according to an aspect of the present invention is a terminal device that communicates with the elevator group management device, and includes transmission control for transmitting the allocation request information to the elevator group management device. and a display control unit for controlling display of the allocation result information received from the elevator group management device.

According to the above configuration, the user can input the allocation request information and check the allocation result information using the terminal device.

The elevator group management device and the terminal device according to each aspect of the present invention may be realized by a computer. In this case, the computer is operated as each part (software element) included in the elevator group management device and the terminal device. A control program for the elevator group management device and the terminal device, which enables the computer to implement the elevator group management device and the terminal device, and a computer-readable recording medium recording the program, are also included in the scope of the present invention.

According to one aspect of the present invention, it is possible to provide an elevator group management apparatus that allocates a car according to a user's request according to the congestion situation of the cars.

1 is a functional block diagram of an elevator management system according to Embodiment 1 of the present invention; FIG. It is a top view which shows typically an example of arrangement|positioning of a part of said elevator management system. It is a figure which shows an example of the operation screen of the terminal device of the said elevator management system. FIG. 4 is a flow chart showing the operation of the elevator group management device of the elevator management system; 4 is a sequence diagram showing an example of the flow of processing of the elevator management system; FIG. FIG. 7 is a flowchart showing the operation of the elevator group management device of the elevator management system according to Embodiment 2 of the present invention; It is a figure which shows an example of the operation screen of the terminal device of the said elevator management system. FIG. 10 is a functional block diagram of an elevator management system according to Embodiment 3 of the present invention;

[Embodiment 1]
<Overview of Elevator Management System>
An embodiment of the present invention will be described in detail below. FIG. 1 is a functional block diagram of an elevator management system 1 according to Embodiment 1 of the present invention. The elevator management system 1 is a system that allocates cars of the elevator group 50 to users U of the elevator group 50 . As shown in FIG. 1 , the elevator management system 1 includes an elevator group 50 , an elevator group management device 10 and a plurality of terminal devices 30 .

<Elevator group>
The elevator group 50 includes elevators 51A to 51C and elevator control devices 52A to 52C, as shown in FIG. In this embodiment, the elevator group 50 is described as having three elevators, but the number of elevators is not limited to the number described above and can be arranged as appropriate. Further, in the present embodiment, the elevators 51A to 51C are described as having the same boarding and alighting floors. FIG. 2 is a plan view schematically showing an example of the layout of part of the elevator management system 1. As shown in FIG. As shown in FIG. 2, elevators 51A-51C have cars AC, respectively.

Elevator controllers 52A-52C control corresponding elevators among elevators 51A-51C. Hereinafter, the elevator control device 52A will be described as a representative, but the elevator control devices 52B and 52C have the same configuration. The elevator control device 52A includes a control section 52A1. The control unit 52A1 comprehensively controls each unit of the elevator control device 52A. The functions of the controller 52A1 may be implemented by a CPU (Central Processing Unit) executing a program stored in a memory (not shown). The control unit 52A1 includes a congestion level calculation unit 522A, a communication control unit 523A, and an operation control unit 524A.

The congestion level calculator 522A calculates the congestion level of the car A of the corresponding elevator 51A. The congestion level is calculated by, for example, the ratio of the area occupied by passengers to the floor area of the car. Specifically, the congestion level calculation unit 522A may calculate the congestion level based on an image captured by a camera provided in the car A, or based on a value indicated by a load sensor of the car. The congestion level may be calculated by estimating the number of passengers in the car. In addition, a photoelectric sensor installed at the entrance/exit of the car detects the passage of the user, and based on the increase or decrease of the load sensor of the car, it is determined whether the user is boarding or getting off. The congestion level may be calculated by predicting the number of passengers.

The calculation of the congestion level may be performed by the elevator group management device 10 . In that case, the congestion level calculation unit 522A transmits information necessary for calculating the congestion level to the elevator group control device 10. FIG.

The communication control unit 523A controls communication with the elevator group management device 10. FIG. Specifically, the communication control unit 523A transmits congestion level information indicating the congestion level of the corresponding elevator 51A to the status acquisition unit 112 of the elevator group management device 10. FIG. Also, the communication control unit 523A receives allocation control information transmitted from the elevator group management device 10 . Details of the allocation control information will be described later. The operation control unit 524A operates the car A from the boarding floor of the user U to the destination floor when the car A is assigned to the user U in the allocation control information.

<Terminal device>
The terminal device 30 communicates with the elevator group management device 10, and the user U uses the terminal device 30 to transmit allocation request information and confirm allocation result information. The terminal device 30 is a mobile terminal device possessed by a user U who uses the elevator group 50, and is an information processing terminal such as a smart phone, for example. Communication between the terminal device 30 and the elevator group management device 10 is performed by, for example, a mobile phone communication line, wireless LAN, Bluetooth (registered trademark), or the like. As shown in FIG. 1, the terminal device 30 includes a terminal device control section 31, a touch panel 32, a display section 33, and a memory .

The terminal device control unit 31 comprehensively controls each unit of the terminal device 30 . The functions of the terminal device control section 31 may be implemented by the CPU executing a program stored in the memory 34 . Details of the terminal device control unit 31 will be described later.

The touch panel 32 detects touch operations and slide operations by the user's U finger, for example. The touch panel 32 is superimposed on the display section 33 . The touch panel 32 supplies the detection result to the touch panel control section 311 .

The display unit 33 displays various information. The display unit 33 displays an image instructed by the display control unit 313 . The memory 34 stores various programs executed by the terminal device control unit 31 and data used by the programs.

(Configuration of terminal device control section)
The terminal device control section 31 includes a touch panel control section 311 , a transmission control section 312 , a display control section 313 and a notification acquisition section 314 .

Touch panel control unit 311 receives information input from touch panel 32 . The touch panel control unit 311 receives allocation request information input from the touch panel 32, for example. Here, the allocation request information is information including the conditions for the car requested by the user U. Specifically, the allocation request information includes scheduled boarding time information, boarding floor information, destination floor information, congestion level setting information, and attribute designation information.

The scheduled boarding time information is information on the scheduled boarding time, which is the time when the user U is scheduled to board the car. If it is assumed that the user U makes an allocation request immediately before boarding the car, the time when the user U is scheduled to board the car may be the time when the user U makes the allocation request. Further, when the user U makes an allocation request well before the scheduled boarding time, the time when the user U is expected to pass through a predetermined place, for example, the entrance E shown in FIG. 2 may be set as the scheduled boarding time. The user U may directly input to the touch panel 32 at the scheduled boarding time, or the terminal device 30 or the elevator group control device 10 may calculate based on the position information of the terminal device 30 .

The boarding floor information is information about the number of floors that the user U plans to get on, and the destination floor information is information about the number of floors that the user U plans to get off. The user U uses the touch panel 32 to input the number of floors the user U plans to get on and the number of floors the user U plans to get off.

FIG. 3 is a diagram showing an example of an operation screen of the terminal device 30 of the elevator management system 1. As shown in FIG. An operation screen 1001 and an operation screen 1002 are operation screens for inputting allocation request information, and an operation screen 1003 is an operation screen for displaying allocation result information. In the operation screen 1001 of FIG. 3, the boarding floor is input as the "1" floor, and the destination floor is input as the "4" floor.

The attribute designation information is information on the attributes of the car requested by the user U. The user U inputs the attribute of the car requested by the user U through the touch panel 32 . On the operation screen 1002, "only for luggage" is entered as the type of dedicated car (attribute of the car).

The congestion level setting information is information on the congestion level of the car requested by the user U. The user U inputs the congestion level of the car requested by the user U through the touch panel 32 . As shown in the operation screen 1002 of FIG. 3, the congestion level can be input by a UI (user interface) for selecting an icon indicating the congestion level, or by moving the meter left and right. may be Since "20%" is entered as the congestion level on the operation screen 1002, the user U who is operating the operation screen 1002 requests to board a car with a congestion level of 20% or less. .

The transmission control unit 312 transmits allocation request information received from the user U to the information acquisition unit 111 of the elevator group management device 10 . The notification acquisition unit 314 acquires the allocation result information transmitted from the notification unit 114 of the elevator group management device 10 and outputs it to the display control unit 313 .

The display control unit 313 controls display on the display unit 33 . The display control unit 313 displays, on the display unit 33, operation screens for inputting allocation request information, such as the operation screens 1001 and 1002 shown in FIG. Further, the display control unit 313 displays the allocation result information transmitted from the elevator group control device 10 on the display unit 33 as shown in the operation screen 1003 of FIG. As a result, the user U can input the allocation request information and confirm the allocation result information by using the terminal device 30 owned by the user U. As the allocation result information, the display control unit 313 displays the assigned car and how the car was assigned (whether it was assigned based on the congestion level or based on the attribute (dedicated car)). may be displayed.

In addition, in this embodiment, although the smart phone which the user U possesses is described as the terminal device 30, it is not limited to the above. The terminal device 30 may be, for example, a shared terminal device installed in an arbitrary place such as an elevator hall or near a security gate.

When an autonomous mobile robot such as a security robot or a cleaning robot uses the elevator group 50, the robot may have the functions of the terminal device 30. In this case, the allocation request information is set in the robot in advance. good too. The robot may be programmed to send allocation request information to the elevator group manager 10 and board the assigned car based on the allocation result information sent from the elevator group manager 10 .

<Elevator group control device>
The elevator group management device 10 selects an elevator car to be assigned to the user U based on the boarding request from the user U. The elevator group management device 10 communicates with the elevator group 50 and the terminal device 30 . The elevator group management device 10 includes a management device control section 11 and a memory 12 .

The management device control section 11 comprehensively controls each section of the elevator group management device 10 . The functions of the management device control unit 11 may be implemented by the CPU executing a program stored in the memory 12 . Details of the management device control unit 11 will be described later. The memory 12 stores various programs executed by the management device control unit 11 and data used by the programs.

(Configuration of management device control unit)
The management device control unit 11 includes an attribute assignment unit 110 , an information acquisition unit 111 , a status acquisition unit 112 , an allocation unit 113 and a notification unit 114 .

The attribute assigning unit 110 assigns attributes to the cars A to C of the elevators 51A to 51C. Attributes include, for example, gender-only (male-only, female-only), luggage-only, autonomous mobile robot-only, VIP-only, and mobile bed-only. Note that the attributes may be changeable depending on the situation, or may be preset and fixed.

The information acquisition unit 111 acquires from the transmission control unit 312 allocation request information corresponding to the user U, including attribute designation information designating attributes of a car, congestion level setting information, boarding floor information, and destination floor information. The information acquisition unit 111 also acquires the scheduled boarding time from the transmission control unit 312 .

The status acquisition unit 112 acquires the respective congestion levels of the cars A to C from the communication control units 523A to 523C of the elevator control devices 52A to 52C. Also, the situation acquisition unit 112 acquires attributes of each car from the attribute assignment unit 110 .

In addition, when there is a user T (not shown) who has already been assigned to the cars A to C by the assignment process described later, the status acquisition unit 112 considers the user T and determines the congestion level acquired from the elevator group 50. may be corrected. As a result, it is possible to allocate a car according to the request of the user U based on the congestion level considering the users T getting on and off from the boarding floor to the destination floor.

(Allocation part)
The allocation unit 113 performs the following allocation process. That is, the allocating unit 113 assigns the attribute designated by the attribute designation information when there is no car with a congestion level equal to or lower than that designated by the congestion level setting information when boarding is scheduled according to the allocation request information. Assign a car to the user U. On the other hand, the allocating unit 113 allocates the car to the user U when there is a car whose congestion level is equal to or lower than that specified by the congestion level setting information.

Further, the allocating unit 113, regarding the cars that can be boarded on the boarding floor indicated by the boarding floor information, if there is no car with a congestion level equal to or lower than that specified by the congestion level setting information, the allocating unit 113 selects a car specified by the attribute specifying information. The user U is assigned a car to which the attribute of being assigned is given. On the other hand, the allocating unit 113 assigns the car to the user when there is a car whose congestion level is equal to or less than that specified by the congestion level setting information with respect to cars that can be boarded on the boarding floor indicated by the boarding floor information. Allocate to U.

As a result, when there is a car with a congestion level equal to or lower than the set congestion level, the user U uses the car with the other attribute instead of the car with the requested attribute. becomes possible. Therefore, it is possible to allocate a car according to the request of the user U according to the congestion situation of the car. In addition, since it is possible to alleviate the concentration of use of a specific car, it is possible to improve the operation efficiency of the elevator group. Furthermore, since the car is selected according to the congestion level at the boarding floor, the car desired by the user U can be allocated according to the congestion level at the time of boarding.

Regarding the car allocation performed by the allocation unit 113, a case where the user U inputs the allocation request information with the content shown in FIG. 3 will be described. As a premise, it is assumed that the car A has an attribute dedicated to luggage, the car B has an attribute dedicated to women, and the car C has an attribute dedicated to men.

First, the allocation unit 113 determines whether or not there is a car with a specified congestion level of 20% or less on the first floor, which is the boarding floor when the user U is scheduled to board. If there is no car with the specified congestion level of 20% or less on the first floor, the allocating unit 113 assigns the car A to the user U, which is given the attribute dedicated to luggage specified by the attribute specifying information. (operation screen 1003 in FIG. 3). Further, the allocation unit 113 allocates the car to the user U when there is a car with the designated congestion level of 20% or less on the first floor.

Specifically, on the first floor, if the congestion level of car A is 40%, the congestion level of car B is 50%, and the congestion level of car C is 60%, the car with the congestion level of 20% or less does not exist. In this case, the allocation unit 113 allocates to the user U the car A to which the baggage-only attribute designated by the attribute designation information is given.

On the first floor, if the congestion level of car A is 40%, the congestion level of car B is 50%, and the congestion level of car C is 15%, the specified congestion level of car C is 20%. It exists as a car for: In that case, the allocation unit 113 prioritizes the congestion level and allocates the car C to the user U regardless of the attribute.

Note that if there are a plurality of cars with a specified congestion level of 20% or less on the first floor, the allocation unit 113 may preferentially allocate the car with the lowest congestion level to the user U. . Furthermore, if there is a car with the attribute specified by the attribute specifying information among the plurality of cars with the congestion level of 20% or less on the first floor, the car is preferentially given to the user U. may be assigned to As a result, the user U can board a car more suitable for his own allocation request information.

Further, when the allocation unit 113 allocates a car with a congestion level equal to or lower than that specified by the congestion level setting information to the user T, the allocation unit 113 waits until the car moves from the boarding floor to the destination floor indicated by the destination floor information. Allocating users U other than user T to the car so that the congestion level of the car is equal to or lower than the congestion level specified by the congestion level setting information requested by user T during the period of I do.

Specifically, for example, at the boarding floor when boarding is scheduled, the congestion levels of the cars A to C are 40%, 50%, and 15%, respectively, and the congestion level of the user U who will use the elevator group 50 from now on is set. A case where the information is 20% will be described. The congestion level of the car C is lower than the congestion level setting information of the user U, but the congestion level setting information of the user T who has already boarded the car C is 15%, and the congestion level of the user T is When the car C is assigned to the user T based on the setting information, the allocation unit 113 does not judge the car C as a car in which the user U can ride. The allocation unit 113 assigns the attribute specified by the attribute specifying information of the user U, assuming that there is no car in which the user U can ride at a congestion level equal to or lower than the congestion level specified by the congestion level setting information requested by the user U. assigns a car A to a user U. When car C is assigned to user T based on user T's attribute specification information, the congestion level specified by the congestion level setting information requested by user T is not considered. is done.

As a result, when a car with a congestion level lower than that specified by the congestion level setting information is assigned to user T, the car is kept at a congestion level lower than that specified by user T until user T arrives at the destination floor. Cars are assigned such that Therefore, the congestion level desired by the user T can be maintained during the period from the time of boarding until arrival at the destination floor.

The notification unit 114 notifies the user U of allocation result information specifying the car allocated by the allocation unit 113 . Specifically, the notification unit 114 transmits the allocation result information to the notification acquisition unit 314 of the terminal device 30 . In addition, the notification unit 114 transmits allocation control information including allocation result information, boarding floor information and destination floor information of the user U to the elevator control devices 52A to 52C.

<Example of process flow in elevator group control device>
FIG. 4 is a flowchart showing the operation of the elevator group management device 10 of the elevator management system 1. As shown in FIG. FIG. 5 is a sequence diagram showing an example of the processing flow of the elevator management system 1. As shown in FIG. An example of the flow of processing in the elevator group management device 10 will be described with reference to FIGS. 4 and 5. FIG.

As shown in FIGS. 4 and 5, first, the user U inputs allocation request information in the terminal device 30 (S101 in FIG. 5). Then, the allocation request information is transmitted from the terminal device 30 to the elevator group management device 10, and the information acquisition unit 111 of the elevator group management device 10 acquires the allocation request information input from the terminal device 30 (FIGS. 4 and 4). 5 S11: information acquisition step).

Also, in the elevator group 50, the congestion level of each car is calculated (S201 in FIG. 5). Then, the congestion level information of the calculated congestion level is transmitted to the elevator group management device 10, and the status acquisition unit 112 of the elevator group management device 10 acquires the information (S12 in FIGS. 4 and 5: status acquisition step). . Also, the situation acquisition unit 112 acquires attributes of each car from the attribute assignment unit 110 .

After that, the allocation unit 113 performs allocation processing (S13 to S15 in FIG. 4). That is, the allocation unit 113 of the elevator group management device 10 determines whether or not there is a car with a congestion level equal to or lower than the specified congestion level at the boarding floor when the user U is scheduled to board (S13 in FIG. 4: Allocation step). If there is a car with a congestion level equal to or lower than the designated congestion level at the boarding floor when the user U is scheduled to board (YES in S13 of FIG. 4), the allocation unit 113 allocates the car with a congestion level equal to or lower than the user U. (S14 in FIG. 4). On the other hand, if there is no car with a congestion level equal to or lower than the specified congestion level at the boarding floor when the user U is scheduled to board (NO in S13 of FIG. 4), the allocation unit 113 uses the car with the specified attribute. person U (S15 in FIG. 4: allocation step).

Thereafter, the notification unit 114 transmits the allocation result information to the terminal device 30 and notifies the user U of the allocation result information (S16 in FIGS. 4 and 5: notification step). Also, the notification unit 114 transmits allocation control information to the elevator group 50 (S17 in FIGS. 4 and 5).

The terminal device 30 displays the allocation result information on the display unit 33 (S102 in FIG. 5). Based on the assignment control information, the elevator group 50 operates the car assigned to the user U from the boarding floor of the user U to the destination floor (S202 in FIG. 5).

Note that the allocation unit 113 may perform the allocation process in a predetermined time period set in advance. As a result, it is possible to perform the above-described allocation process, for example, during a time zone when congestion is expected. Here, in other time periods when congestion is not expected, it is expected that all the cars will be less crowded, and there is an advantage for the user U to use the car provided with the attributes requested by the user U. expected to be low. In other words, in other time periods when congestion is not expected, the elevator group can be operated efficiently by allocating cars without considering the user U's specification of attributes desired for allocation.

In addition, the allocation unit 113 performs allocation processing when the number of users including at least one of the number of passengers in a plurality of cars and the number of people waiting in a car, or when the number of users per unit time exceeds a predetermined number of people may be performed. As a result, it is possible to perform the above-described allocation process in a situation of actual congestion. Here, in a situation where it is not actually crowded, it is expected that any car will be less crowded, and there is little merit for the user U to use the car provided with the attribute requested by the user U. It is expected that. In other words, when there is no actual congestion, the car allocation is performed without considering the user U's designation of desired attributes for allocation, thereby improving the operation efficiency of the elevator group.

Further, the allocating unit 113 assigns the attribute A car provided with the attribute specified by the specified information may be assigned to the user U. As a result, when the car is actually congested, the car assigned the attribute specified by the attribute specifying information is assigned without considering the congestion level setting information.

(Modification)
In the first embodiment, attributes are set in advance for each car, but attributes are not normally assigned to the car, and attributes are appropriately set to the car according to car allocation. good too. In this case, the assignment unit 113 may set attributes to the cars in accordance with the assignment of the cars, and the attribute assignment unit 110 may assign the attributes set by the assignment unit 113 to the corresponding cars.

For example, the assigning unit 113 may set the attribute of “women only” to the car A or to the car B according to the car allocation. The attribute of the car is given by the attribute giving unit 110 when the user U who has been assigned based on the car attribute gets on the car, and the attribute is maintained while the user U gets on the car. When all the users who requested the car to which the attribute is given get off from the car, the setting of the car attribute is canceled by the allocation unit 113, and the attribute is canceled by the attribute giving unit 110.例文帳に追加It should be noted that there may be a mixture of cars for which attributes are set in advance and cars for which attributes are set according to allocation.

Alternatively, the allocation request information may include user attribute information, and the allocation unit 113 may set attributes for the car in consideration of the user attribute information and allocate the car to the user.

User attribute information is information indicating attributes of a user. User attributes include, for example, gender (female, male, etc.), luggage, autonomous mobile robot, VIP, and the like. The user attribute information may be directly input by the user U through the terminal device 30, or may be registered in the terminal device 30 or the like in advance. In addition, one or more attributes may be set for one user in the user attribute information. For example, if the user is a man carrying luggage, the user attribute information is set as "luggage" and "male".

For example, the allocating unit 113 allocates a car set with an attribute of "women only" only to allocation request information including user attribute information of "female". Further, for example, the allocation unit 113 assigns only the allocation request information including the user attribute information of the "autonomous mobile robot" to the car to which the attribute of "autonomous mobile robot" is set. assignment.

As a result, the user U can use not only the car with the requested attribute but also other cars when there is a car with a congestion level equal to or lower than the set congestion level. . Therefore, it is possible to allocate a car according to the request of the user U according to the congestion situation of the car. In addition, since it is possible to prevent the car from being operated as a dedicated car by giving an attribute to the car, it is possible to allocate an optimum car from among many cars when allocating a car to a user. Therefore, the operation efficiency of the elevator group can be improved.

It should be noted that, even in the first embodiment described above assuming that attributes are set in advance for each car, the allocation request information includes user attribute information, and the allocation unit 113 considers the user attribute information, You may assign a car to the
(Allocation example 1)
An example of car allocation performed by the allocation unit 113 will be described below. As a premise, the user attribute information of user U is “luggage” and “male”, car A is given a baggage-only attribute, car B is given a female-only attribute, and car C is given an attribute of women only. It is assumed that an attribute dedicated to men is given. Also, it is assumed that the allocation request information has been input as shown in FIG.

First, the allocating unit 113 determines that there is a car with a designated congestion level of 20% or less among the cars that the user U can board on the first floor, which is the boarding floor when the user U is scheduled to board. Determine whether or not Here, the car in which the user U can ride indicates a car whose attribute matches at least part of the user attribute information, or a car to which no attribute is assigned. In other words, it indicates a car in which the user attribute information and the car attribute do not have an exclusive relationship. Since the attribute of the car A is only for luggage and the attribute of the car C is "men only", the attributes of each of the cars A and C and part of the user attribute information of the user U are match. Therefore, the car A and the car C are cars in which the user U can get on. On the other hand, the attribute of car B is "women only", and the attribute of car B does not match the user attribute information of user U. does not become

On the first floor, if there is no car with a specified congestion level of 20% or less among the cars in which the user U can ride, the allocating unit 113 assigns the baggage-only attribute specified by the attribute specifying information. is assigned to the user U (operation screen 1003 in FIG. 3). Further, if there is a car with a designated congestion level of 20% or less among the cars that the user U can board on the first floor, the allocating unit 113 assigns the car to the user U. assign.

Specifically, on the first floor, when the congestion level of car A is 40%, the congestion level of car B is 10%, and the congestion level of car C is 60%, the number of rides that user U can take is There is no car with a congestion level of 20% or less among the cars. This is because the attribute of the car B is "women only" and the user attribute information is "male", so the car B cannot be a car in which the user U can ride. In this case, the allocating unit 113 allocates to the user U, among the cars in which the user U can ride, the car A to which the attribute for luggage specified by the attribute specifying information is assigned.

On the first floor, if the congestion level of car A is 40%, the congestion level of car B is 10%, and the congestion level of car C is 15%, then , car C exists as a car with a specified congestion level of 20% or less. In this case, the allocating unit 113 gives priority to the congestion level among the cars in which the user U can ride, and allocates the car C to the user U regardless of the attributes.

(Assignment example 2)
Another example of car allocation performed by the allocation unit 113 will be described below. As a premise, the user attribute information of user U is "luggage" and "male", attributes are not assigned to car A and car B, and car C has an attribute of "VIP only". , the car A has a relatively large floor area. Also, it is assumed that the allocation request information has been input as shown in FIG.

First, the allocating unit 113 determines that there is a car with a designated congestion level of 20% or less among the cars that the user U can board on the first floor, which is the boarding floor when the user U is scheduled to board. Determine whether or not Here, since attributes are not assigned to the car A and the car B, the car A and the car B are cars in which the user U can ride. On the other hand, the attribute of the car C is "VIP only", and the attribute of the car C and the user attribute information of the user U do not match. does not become

On the first floor, if there is no car with a specified congestion level of 20% or less among the cars in which the user U can ride, and there is no car with the specified attribute, the allocation unit 113 performs the following: process. In other words, according to the situation such as the user attribute information of the user riding in the car, the floor area of the car, etc., any of the cars that the user U can ride in that does not have an attribute The attribute specified by the user U is set in the car of U, and the car is assigned to the user U. Specifically, for example, the allocation unit 113 determines that the car A, which has a relatively large floor area, is suitable for the attribute designation information of the allocation request information, ie, "only for luggage". Set the attribute "Luggage Only".

The allocation unit 113 allocates to the user U the car A in which the attribute dedicated to the cargo specified by the attribute specifying information is set (operation screen 1003 in FIG. 3). Further, if there is a car with a designated congestion level of 20% or less among the cars that the user U can board on the first floor, the allocating unit 113 assigns the car to the user U. assign. When the allocation unit 113 assigns an attribute to the car and allocates the car with the attribute specified by the attribute designation information to the user U, during the period until the car moves from the boarding floor to the destination floor, Maintain the setting of the attributes of the car, and then cancel the setting of the attributes of the car.

[Embodiment 2]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the second embodiment, unlike the first embodiment, the elevator group management device 10a calculates at least one of the predicted waiting time and the predicted time until arrival, and notifies the user U as the predicted information. It is the same as the first embodiment. Specifically, as shown in FIG. 1, an elevator management system 1A according to the second embodiment includes an elevator group management device 10a instead of the elevator group management device 10. FIG. Elevator group management apparatus 10a includes allocation section 113a and notification section 114a instead of allocation section 113 and notification section 114, as compared with elevator group management apparatus 10a.

In addition to the function of the allocation unit 113, the allocation unit 113a performs at least the predicted boarding time of the user U to the car to be allocated and the predicted arrival time when the car to be allocated arrives at the destination floor of the user U. Calculate either one. The predicted boarding time is the time when the car to be allocated will arrive at the user U's boarding floor. The predicted arrival time is the time when the user U gets on the car from the boarding floor and then arrives at the destination floor. The allocation unit 113a calculates at least one of the predicted boarding time and the predicted arrival time based on the current position of the car to be allocated and the floor to be stopped. This makes it possible to calculate the estimated boarding time and estimated arrival time by taking into account the additional time required for deceleration, door opening/closing, boarding/alighting, and acceleration when the car stops at any floor, thus making it more accurate. Predicted boarding time and predicted arrival time can be calculated.

Alternatively, the allocation unit 113a may calculate the predicted waiting time as the time from the scheduled boarding time to the predicted boarding time. Furthermore, the predicted time to arrival may be calculated as the time from the scheduled boarding time to the predicted arrival time.

Further, when the allocation unit 113a acquires the allocation approval information from the user U to whom the prediction information has been notified via the information acquisition unit 111, the allocation unit 113a determines the car allocation.

The notification unit 114a transmits prediction information corresponding to at least one of the predicted boarding time and the predicted arrival time to the terminal device 30 and notifies the user U of the prediction information. The prediction information also includes a prediction waiting time and a prediction time until arrival.

<Example of process flow in elevator group control device>
FIG. 6 is a flowchart showing the operation of the elevator group management device 10a of the elevator management system 1A according to the second embodiment. FIG. 7 is a diagram showing an example of an operation screen of the terminal device 30 of the elevator management system 1A. An operation screen 2001 and an operation screen 2002 are operation screens for inputting allocation request information, and an operation screen 2003 is an operation screen for displaying allocation result information. An example of the flow of processing in the elevator group management device 10a will be described with reference to FIGS. 6 and 7. FIG.

First, as in the first embodiment, the user U inputs the desired boarding floor, destination floor, congestion level, and attributes into the terminal device 30 as allocation request information. On the operation screen 2001 and the operation screen 2002 of FIG. 7, "1" is entered as the boarding floor, "4" as the destination floor, "women only" as the exclusive car type, and "40%" as the congestion level. Then, the allocation request information is transmitted from the terminal device 30 to the elevator group management device 10a, and the information acquisition unit 111 of the elevator group management device 10a acquires the allocation request information input from the terminal device 30 (S21 in FIG. 6). ).

Also, in the elevator group 50, the congestion level of each car is calculated. Then, the congestion level information of the calculated congestion level is transmitted to the elevator group management device 10a, and the status acquisition unit 112 of the elevator group management device 10a acquires the information (S22 in FIG. 6). Also, the situation acquisition unit 112 acquires attributes of each car from the attribute assignment unit 110 .

After that, the allocation unit 113a of the elevator group management device 10a determines whether or not there is a car with a congestion level equal to or lower than the designated congestion level at the boarding floor when the user U is scheduled to board (S23 in FIG. 6). If there is a car with a congestion level equal to or lower than the designated congestion level at the boarding floor when the user U is scheduled to board (YES in S23 of FIG. 6), the allocating unit 113a assigns a car with a congestion level equal to or lower than the car scheduled to be allocated. , and provisionally assigned to the user U (S24 in FIG. 6). On the other hand, if there is no car with a congestion level equal to or lower than the specified congestion level at the boarding floor when the user U is scheduled to board (NO in S23 of FIG. 6), the allocation unit 113a allocates a car with the specified attribute. It is provisionally assigned to the user U as a scheduled car (S25 in FIG. 6).

Furthermore, the allocation unit 113a calculates at least one of the predicted boarding time of the user U to the car to be allocated and the predicted arrival time when the car to be allocated arrives at the destination floor of the user U ( S26 in FIG. 6). Then, the notification unit 114a transmits prediction information corresponding to at least one of the predicted boarding time and the predicted arrival time calculated by the allocation unit 113a to the terminal device 30, and notifies the user U of the prediction information. (S27 in FIG. 6). The terminal device 30 displays the prediction information notified from the notification unit 114 a on the display unit 33 . On the operation screen 2002 of FIG. 7, the predicted waiting time is displayed as "1 minute and 30 seconds" as the predicted information.

The user U decides whether or not to approve the predicted waiting time displayed on the terminal device 30 . When the user U approves the predicted waiting time, the user U touches "OK" on the operation screen 2002 in FIG. 7, and transmits the approval information from the terminal device 30 to the elevator group control device 10a.

The allocation unit 113a determines whether or not allocation approval information has been acquired from the user U who has been notified of the predicted waiting time via the information acquisition unit 111 (S28 in FIG. 6). When the information acquisition unit 111 acquires the allocation approval information (YES in S28 of FIG. 6), the allocation unit 113a confirms the temporary allocation of the car to be allocated (S30 of FIG. 6).

Thereafter, the notification unit 114a transmits the allocation result information in which the allocation is confirmed to the terminal device 30, and notifies the user U of the allocation result information (S31 in FIG. 6). In the terminal device 30, the allocation result information received from the elevator group control device 10a is displayed on the display unit 33. FIG. In the operation screen 2003 of FIG. 7, the car B is assigned to the user U based on the congestion level setting information.

In addition, the notification unit 114a transmits the allocation control information to the elevator group 50 (S32 in FIG. 6), and the elevator group 50 selects the car allocated to the user U based on the allocation control information. Operate from floor to destination floor.

Further, when the user U does not approve the predicted waiting time and the information acquisition unit 111 does not acquire the allocation approval information (NO in S28 of FIG. 6), the user selects the desired Change the dedicated car type or congestion level so that the expected waiting time is When the allocation unit 113a acquires the changed allocation request information via the information acquisition unit 111 (S29 in FIG. 6), the elevator group management device 10a returns to the process of S22.

As a result, the user U can determine the allocation of the car after confirming the prediction information, so that the user U can set the congestion level according to the waiting time.

[Embodiment 3]
Another embodiment of the invention is described below with reference to FIGS. 2 and 8. FIG. FIG. 8 is a functional block diagram of an elevator management system 1B according to Embodiment 3 of the present invention. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

In the third embodiment, the information acquisition unit 111 of the elevator group management device 10 acquires allocation request information from the security gate 60 (reading device) that reads the allocation request information recorded in the IC card 70 (recording medium) possessed by the user U. to get Embodiment 3 is different from Embodiment 1 in the configuration described above, and is the same as Embodiment 1 in other configurations and procedures. Specifically, the elevator management system 1B according to the third embodiment includes a security gate 60 and an IC card 70 instead of the terminal device 30 .

The IC card 70 is a card-type recording medium that the user U individually possesses. In the IC card 70 , allocation request information of the user U possessing the IC card 70 is stored in the memory 71 .

The security gate 60 is a gate having functions and structures that allow only the user U who is permitted to pass through. As shown in FIGS. 2 and 8, the security gate 60 is provided with gate devices 63 bordering the passage 600 on both sides of the passage 600, which is an area for entry or movement for people to enter and exit. ing. The gate device 63 includes a reading unit 611 that reads information on the user U, a door unit 64 that blocks passage, and a display unit 62 that displays information at a position visible to a passing person. In addition, the display unit 62 is not limited to the above, and may be installed in an arbitrary place such as an elevator hall or near a security gate, for example.

The security gate 60 has a gate control section 61 . The gate control section 61 controls each section of the security gate 60 in an integrated manner. The functions of the gate control unit 61 may be implemented by the CPU executing a program stored in a memory (not shown). The gate control unit 61 includes a reading unit 611 , a transmission control unit 612 , a display control unit 613 and a notification acquisition unit 614 .

In the security gate 60 , when the IC card 70 approaches the reader 611 , the reader 611 reads the allocation request information recorded on the IC card 70 . The transmission control unit 612 transmits the allocation request information read by the reading unit 611 to the information acquisition unit 111 of the elevator group management device 10 . The notification acquisition unit 614 acquires the allocation result information notified to the user U from the notification unit 114 . The display control unit 613 displays the allocation result information acquired by the notification acquisition unit 614 on the display unit 62 .

As a result, the user U records the allocation request information in the IC card 70 in advance and causes the security gate 60 to read the IC card 70, thereby transmitting the allocation request information to the elevator group control device 10. can be done.

Note that the allocation result information from the notification unit 114 is not limited to the above, and may be, for example, notified by the terminal device of the user U corresponding to the allocation request information that has been allocated. Specifically, the user U may be notified of the allocation result information by an application downloaded to the terminal device, or the user U may be notified of the allocation result information by e-mail to the terminal device. As a result, the user U can confirm the allocation result information on the terminal device owned by himself/herself.

Furthermore, when the second embodiment and the third embodiment are combined and executed, a touch panel may be superimposed on the display unit 62, and the touch panel may be used to change allocation request information and input approval information.

Also, the security gate 60 may be an authentication device that authenticates the user U as an individual. In that case, the security gate 60 reads ID information for specifying the user U from the IC card or biometric authentication, and transmits the ID information to the information acquisition unit 111 . The information acquisition unit 111 receives the ID information from the security gate 60 and acquires the allocation request information from the memory 12 (recording unit) that records the allocation request information associated with the ID information. As a result, the user U can make the elevator group management device 10 recognize the allocation request information by recording the allocation request information in the memory 12 in advance and performing personal authentication with the authentication device.

According to the configuration as described above, it is possible to provide an elevator group management apparatus that allocates a car according to a user's request according to the congestion situation of the cars. In addition, since it is possible to alleviate the concentration of use of a specific car, it is possible to improve the operation efficiency of the elevator group. Furthermore, by improving the operation efficiency of the elevator group, it is possible to save energy for the operation of the elevator group, thereby contributing to the achievement of the Sustainable Development Goals (SDGs).

[Example of realization by software]
The functions of the elevator group management device 10 and the terminal device 30 (hereinafter referred to as "apparatus") are programs for causing a computer to function as the device, and each control block of the device (especially the management device control unit 11, Each unit included in the terminal device control unit 31 can be realized by a program for causing a computer to function.

In this case, the device comprises a computer having at least one control device (eg processor) and at least one storage device (eg memory) as hardware for executing the program. Each function described in each of the above embodiments is realized by executing the program using the control device and the storage device.

The program may be recorded on one or more non-transitory computer-readable recording media. The recording medium may or may not be included in the device. In the latter case, the program may be supplied to the device via any transmission medium, wired or wireless.

Also, part or all of the functions of each control block can be realized by a logic circuit. For example, an integrated circuit in which logic circuits functioning as the respective control blocks are formed is also included in the scope of the present invention. In addition, it is also possible to implement the functions of the respective control blocks by, for example, a quantum computer.

Further, each process described in each of the above embodiments may be executed by AI (Artificial Intelligence). In this case, the AI may operate on the control device, or may operate on another device (for example, an edge computer or a cloud server).

The present invention is not limited to the above-described embodiments, but can be modified in various ways within the scope of the claims, and can be obtained by appropriately combining technical means disclosed in different embodiments. is also included in the technical scope of the present invention.

1, 1A, 1B elevator management system 10, 10a elevator group management device 30 terminal device 31 terminal device control unit 32 touch panel 60 security gate (reading device, authentication device)
70 IC card (recording medium)
111 Information Acquisition Unit 112 Status Acquisition Units 113, 113a Allocation Units 114, 114a Notification Unit 312 Transmission Control Unit 313 of Terminal Device Display Control Units A, B, C of Terminal Device Car

Claims (13)

An elevator group management device that selects an elevator car to be assigned to a user based on a boarding request from the user,
an information acquisition unit for acquiring allocation request information corresponding to the user, including attribute designation information designating attributes of the car and congestion level setting information;
a situation acquisition unit that acquires congestion levels of each of the plurality of cars;
At the time of boarding schedule according to the allocation request information, if there is no car with a congestion level equal to or lower than the congestion level setting information, the boarding to which the attribute specified by the attribute specifying information is given. Allocating a car to the user, and performing an allocation process of allocating the car to the user if the car has a congestion level equal to or lower than that specified by the congestion level setting information. Department and
and a notifying unit that notifies the user of allocation result information specifying the car allocated by the allocating unit. The information acquisition unit acquires boarding floor information included in the allocation request information,
With respect to the cars that can be boarded at the boarding floor indicated by the boarding floor information, the allocating unit, when there is no car having a congestion level equal to or lower than that specified by the congestion level setting information, assigns the attribute specifying information While allocating the car to which the attribute specified by is assigned to the user, if there is a car with a congestion level equal to or lower than the congestion level specified by the congestion level setting information, the car to the user. The information acquisition unit acquires destination floor information included in the allocation request information,
The allocating unit moves the car from the boarding floor to the destination floor indicated by the destination floor information when allocating the car with the congestion level equal to or lower than the congestion level setting information specified by the congestion level setting information to the user. Allocating users other than the above-mentioned users to the car so that the congestion level of the car is equal to or lower than the congestion level specified by the congestion level setting information during the period until the Item 3. The elevator group control device according to item 2. The allocation unit calculates at least one of a predicted boarding time of the user to the car to be allocated and a predicted arrival time when the car to be allocated arrives at the destination floor of the user. ,
The notification unit notifies the user of prediction information corresponding to at least one of the predicted boarding time and the predicted arrival time,
4. The allocation unit determines the allocation of the car when acquiring allocation approval information from the user to whom the prediction information has been sent via the information acquisition unit. Elevator group control device according to 1. The elevator group management apparatus according to any one of claims 1 to 4, wherein said allocation unit performs said allocation process in a predetermined time period set in advance. The allocation unit performs the allocation process when the number of users including at least one of the number of passengers in the plurality of cars and the number of people waiting in the car, or when the number of users per unit time exceeds a predetermined number of people The elevator group control device according to any one of claims 1 to 5, wherein The allocation unit designates the attribute when the number of users including at least one of the number of passengers in the plurality of cars and the number of people waiting in the car, or when the number of users per unit time exceeds a predetermined number of people The elevator group management apparatus according to any one of claims 1 to 5, wherein the car to which the attribute specified by the information is assigned is assigned to the user. The information acquisition unit acquires the allocation request information from the terminal device operated by the user,
The elevator group management apparatus according to any one of claims 1 to 7, wherein said notification unit transmits said allocation result information to said terminal device. The elevator group according to any one of claims 1 to 8, wherein the information acquisition unit acquires the allocation request information from a reading device that reads the allocation request information recorded on a recording medium owned by the user. management device. The information acquisition unit receives ID information specifying the user from an authentication device that performs personal authentication of the user, and receives the allocation request from the recording unit that records the allocation request information associated with the ID information. The elevator group control device according to any one of claims 1 to 9, which acquires information. A control method for an elevator group management device for selecting an elevator car to be assigned to a user based on a boarding request from the user, comprising:
an information acquisition step of acquiring allocation request information corresponding to the user, including attribute designation information designating attributes of the car and congestion level setting information;
a situation obtaining step of obtaining a congestion level of each of the plurality of cars;
At the time of boarding schedule according to the allocation request information, if there is no car with a congestion level equal to or lower than the congestion level setting information, the boarding to which the attribute specified by the attribute specifying information is given. Allocating a car to the user, and performing an allocation process of allocating the car to the user if the car has a congestion level equal to or lower than that specified by the congestion level setting information. a step;
and a notification step of notifying the user of allocation result information specifying the car allocated in the allocation step. A terminal device that communicates with the elevator group management device according to claim 8,
a transmission control unit that transmits the allocation request information to the elevator group management device;
a display control unit that controls display of the allocation result information received from the elevator group control device. 13. A terminal control program for causing a computer to function as the terminal device according to claim 12, the terminal control program for causing a computer to function as the transmission control section and the display control section.

Images