elevator equipment

Abstract

To improve transportation efficiency by granting landing-hall call registration permission to other cars other than those stopped at a landing hall under specific conditions.SOLUTION: An elevator device calculates the degree of congestion at a specific car as information for easing restrictions on the timing of landing-hall calls for the next car, and allows landing-hall call registration (landing-hall call operability determination control) if necessary. In a group management control device 20, a load-passenger number conversion table is prepared in advance, assuming an average weight of an adult as one person, and the number of passengers is calculated from a load detected by a load detection sensor 36.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an elevator system that manages the up-and-down operation of a plurality of cars. [Background technology]

[0002] There is known a control technology for managing the up and down operation of a group of elevator cars. For example, Patent Document 1 describes that when determining whether to enable or disable a door reopening (the operation of reopening the doors from a state where they are about to close) based on the determination element of the result of detecting the operational status of the car congestion detection device in response to the operation of a hall button, the technology uses a first determination element based on whether the car load value obtained via the car control device is equal to or greater than a predetermined value, and a second determination element based on whether a subsequent car will arrive at the hall floor corresponding to the hall call within a predetermined time. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-88647 Summary of the Invention [Problem to be solved by the invention]

[0004] Conventional elevator management control, including that of Patent Document 1, does not allow the doors to reopen, i.e., does not allow hall call registration, when a specific elevator stops at a hall call registration floor and the car congestion detection device detects a predetermined value or higher.

[0005] However, this poses a problem: elevator users cannot register a hall call until the car doors have completely closed, so they must wait until the stopped elevator departs in order to call the next elevator.

[0006] SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide an elevator system that can achieve both convenience for users when registering car hall calls and improved efficiency in transporting users. [Means for solving the problem]

[0007] An elevator system according to the present invention comprises a group management control device that coordinates and manages, as a group, a plurality of elevators each having a car with a door that can be opened and closed; hall buttons that are installed at car landings provided for each floor of a building and that register calls for the car; and a plurality of car control devices that individually control operations of the plurality of elevators including the raising and lowering operations and the opening and closing operations of the doors; and a car congestion detection device that is installed in each of the plurality of elevators and that determines the degree of congestion of people riding in the car, wherein the group management control device is characterized in that, while the car is open at a stopping floor, registration of the hall button at that stopping floor is not permitted, and when the car door of any of the elevators at the landing on a specific floor has started to close, or when it is determined that the degree of congestion of the car stopped at the landing is equal to or greater than a predetermined threshold. [Effects of the Invention]

[0008] According to the present invention, an elevator system is provided that can achieve both convenience for users when registering car hall calls and improved efficiency in transporting users. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a hardware block diagram of an elevator apparatus according to an embodiment of the present invention. FIG. [Figure 2] FIG. 2 is a functional block diagram of a group management control device according to the first embodiment. [Figure 3] 4 is a flowchart showing the operation of the group management control device. [Figure 4]FIG. 10 is a functional block diagram of a group management control device according to another embodiment of the present invention. [Figure 5] 10 is a flowchart illustrating car allocation control. [Figure 6] 10 is a flowchart according to another embodiment of additional allocation control. DETAILED DESCRIPTION OF THE INVENTION

[0010] Figure 1 shows an elevator system 10 according to an embodiment of the present invention. Hereinafter, in Figure 1 and other figures, "A" added to a number indicates a configuration related to elevator No. 1 of three elevators, "B" indicates a configuration related to elevator No. 2, and "C" indicates a configuration related to elevator No. 3.

[0011] The elevator system 10 includes a plurality of cars 12. The elevator system 10 uses an elevator control device 14 to manage the operation of the plurality of cars 12, which moves up and down.

[0012] A count weight 16 is attached to the car 12 via a cable 18, and the cable 18 is wound around a hoist 20. The car 12A functions as the first car, the car 12B as the second car, and the car 12C as the third car.

[0013] The three cars 12 are managed as one group by a group management controller 22 of the elevator control device 14. The group management controller 22 is connected to a car controller 24 that controls the elevation and descent of the car 12 of each car.

[0014] The car control device 24 controls the driving of the hoist 18, and also controls a speaker 26 provided in the car 12, an in-car operation panel 28 shown in FIG. 2, and a door opening / closing mechanism 30.

[0015] The hoist 18 operates based on a drive signal from the car control device 24 to raise and lower the car 12 .

[0016] The car control device 24 controls the opening and closing of the doors at the floors where the car 12 stops. The opening and closing of the doors of the car 12 is linked to the respective opening and closing doors 32 at each floor.

[0017] Landing buttons 340, 342 installed on each floor are connected to the group management control device 24. The landing buttons 340, 342 correspond to calls to the car 12.

[0018] The platform button 340 is provided with a main operation unit installed at a normal height and a sub-operation unit at a height that takes into consideration operability from a wheelchair, for example. The sub-operation unit may be provided on the platform button 342, or on both the platform buttons 340 and 342.

[0019] A load detection sensor 36 serving as a car congestion detection device is attached to the bottom of the car 12. The load detection sensor 36 detects the load on the floor surface of the car 12 and sends the detection result to the group management control device 22 via the car control device 24.

[0020] A landing camera 38 is installed at the landing on each floor. The landing camera 38 is connected to the group management control unit 22 via an image analysis unit 40.

[0021] The image analysis unit 40 sends the status of people at the platform, for example, the congestion status based on a headcount, to the group management control device 22 in real time based on images taken by the platform camera 38. Since the number of users at the platform increases, decreases, and moves frequently, and there may also be luggage other than users at the platform, an image recognition camera 38 that can recognize the status of users in real time, for example, the number of people and the congestion status, is optimal. Alternatively, a detection module such as an infrared camera or a load detection sensor may be used.

[0022] When the car 12 of any car stops at a floor where a hall call is registered and the congestion level is above a predetermined level, for example, the floor is nearly full, the group management control device 22 does not allow the door in the closing operation to be changed to the opening operation, i.e., does not allow the door to be reopened, even if a hall call operation is performed.

[0023] In this case, even if a user operates the hall buttons 340, 342, a new hall call cannot be registered until the door closing operation is completed.

[0024] In other words, in order to call a car (next car) other than the specific car that is currently stopped, the user must wait until the specific car departs.

[0025] Therefore, in the first embodiment, the degree of congestion in a specific car, for example, the number of passengers exceeding a predetermined number, is calculated as information for relaxing restrictions on the timing of a hall call for the next car, and hall call operations are permitted as necessary (disease call operation feasibility determination control).

[0026] In the first embodiment, the group management control device 20 prepares a load-to-number-of-people conversion table in advance, with the average weight of an adult as one unit, and calculates the number of people from the load detected by the load detection sensor 36. Note that the car congestion detection device may be a camera that takes pictures of the inside of the car 12 instead of the load detection sensor 36, and in this case, the number of passengers can be calculated by analyzing the information captured by the camera. Furthermore, the camera is not limited to a solid-state image sensor (CCD "Charge Coupled Device" sensor or CMOS "Complementary Metal Oxide Semiconductor" sensor) that converts density into an electrical signal, and may be another sensor such as an infrared thermograph as long as it can identify passengers.

[0027] 2 is a functional block diagram showing, by function, the functions of the group management control device 20, such as the hall call operation availability determination control. Note that each block does not limit the hardware configuration of the group management control device 20.

[0028] The car control device 24 is connected to an in-car operation panel 28 installed in the car 12 of the car, a door opening / closing mechanism 30, a hoist 20, a load detection sensor 36, and a speaker 26.

[0029] The in-car operation panel 28 sends operation signals to the car control device 24 in response to operations by the passenger, such as instructions for stopping floors and instructions for opening or closing. If a monitor is provided, the car control device 24 sends information to be displayed on the monitor.

[0030] The door opening / closing mechanism unit 30 is a mechanism for opening and closing the door 32 when the car 12 stops (lands) at a stopping floor based on a drive signal from the car control device 24.

[0031] The hoist 20 winds or unwinds the cable 18 based on a drive signal from the car control device 24, and raises or lowers the car 12.

[0032] The load detection sensor 36 detects the load acting on the floor surface of the car 12 and sends the detected load information to the car control device 24 .

[0033] The speaker 26 notifies information to users riding in the car 12 based on an output signal from the car control device 24. Notification is not limited to audio, and may be visual.

[0034] 2, the group management control device 22 includes an information receiving unit 50, which is connected to the landing buttons 340, 342 on each floor. The information receiving unit 50 receives signals based on the operation of the landing buttons 340, 342.

[0035] The information receiving unit 50 is connected to an operation state determining unit 52. The operation state determining unit 52 sends a car dispatch instruction to a dispatch determining unit 54 based on the operation state of the landing buttons 340, 342.

[0036] The dispatch determination unit 54 identifies the car 12 to be dispatched and determines the floors at which the identified car 12 will stop, and sends operation instruction information to the operation control unit 56. The operation control unit 56 selects the car control device 24 corresponding to the identified car 12 and outputs operation instructions.

[0037] The car control unit 24 that has received the operation instruction controls the drive of the hoist 20 to move (raise or lower) the car 12 to the stopping floor.

[0038] After the car 12 stops (lands) at a stopping floor, when the opening / closing door 32 at the stopping floor opens in conjunction with the opening of the door, the load detection sensor 36 detects the load acting on the floor surface.

[0039] In addition, at this time, even if the landing buttons 340 and 342 of the stopping floor are operated, a disallowed state is entered in which calling of other cars is not possible. This is to prevent car concentration due to overlapping car calls.

[0040] The detected load information is sent to the operation control unit 56 of the group management control unit 22 via the unit control device 24. The operation control unit 56 is connected to a congestion degree calculation unit 58, and the load information is sent to the congestion degree calculation unit 58.

[0041] The congestion degree calculation unit 58 is connected to a load-to-passenger number conversion table memory 60. The congestion degree calculation unit 58 reads out the load-to-passenger number conversion table from the load-to-passenger number conversion table memory 60, and calculates the number of passengers based on the load information received from the operation control unit 56. The calculated number of passengers is sent to a landing button registration possibility determination unit 62.

[0042] The landing button registration possibility determining unit 62 determines whether the number of passengers in the car 12 is equal to or greater than a predetermined number (for example, if the capacity is 15 passengers, then 2 / 3 of that, or 10 passengers).

[0043] If the number of registered platform buttons is more than a predetermined number, the platform button registration decision unit 62 allows operation of the platform buttons 340, 342 even if the door of the specific platform 12 is in the closing operation, since there may be cases where the currently landed platform 12 (specific platform 12) cannot accommodate all passengers.

[0044] The group management control device is composed of hardware resources such as a computer, a microcomputer, and an LSI. The controller executes a control program recorded in memory to realize the "units" that form the various functions described above. The "units" may also be referred to as "means" or "modules." Below, car hall call registration by the group management control device 22 will be explained from the perspective of the controller's operation, following the flowchart in Figure 3. The controller starts the flowchart in Figure 3 at predetermined intervals.

[0045] In step 100, the controller determines whether the car 12 has stopped at the target floor and the doors have opened. If the result in step 100 is negative, the controller ends the flowchart because there is no need to determine whether or not the car can register a hall call.

[0046] If the controller determines in step 100 that it is YES, it proceeds to step 102. In step 102, the controller sets the registration of car hall calls by operation of the hall buttons 340, 342 at the target floor to be disallowed, and proceeds to step 104. In step 104, the controller calculates the degree of congestion of the car 12 based on the load of the car 12.

[0047] In the next step 106, if the controller determines that the degree of occupancy is not equal to or greater than the threshold value, the process proceeds to step 108, where it is determined whether the door has moved from the open state to the closed state.

[0048] If step 108 is negative, the controller returns to step 104 and repeats steps 104, 106, and 108 until step 106 or step 108 is positive.

[0049] If step 106 or step 108 is positive, the controller proceeds to step 110 to permit registration of a car hall call by operating the hall buttons 340, 342 of the target floor, and then ends the flow chart.

[0050] Specific actions of a user will be described based on the flowchart in Figure 3. When a user operates the hall buttons 340, 342 to register this, the specific car 12 moves to the corresponding floor, stops, and opens the door 32 (step 100). At this point, the group management control device 22 does not allow the registration of hall calls (step 102).

[0051] Based on the load information from the detection sensor 36 (step 104), if the congestion level of the car 12 is, for example, 40% or more (step 106: Y), the car 12 is full or nearly full, so all passengers waiting at the platform may not be able to board the car, or passengers may want to avoid boarding the car.

[0052] Therefore, to enable passengers at the floor where car 12 is stopped to quickly access the car of the next car, the passengers can register a hall call even before the stopped car departs (step 106: Y). As in the conventional technology described above, if the car is configured to not allow reopening when it stops at a floor where a hall call is registered and the car congestion level is equal to or greater than a predetermined value, a new hall call cannot be registered until the doors are completely closed, which poses a problem that passengers have to wait until the car of the car stopped at that floor departs in order to call the next car.

[0053] If the car stopped at the hall call registration floor is not crowded (step 106: N), passengers cannot immediately register a car call. If this were possible without restrictions, passengers would not be able to board the car stopped at the call registration floor, which would result in poor passenger transportation efficiency.

[0054] A user cannot register a car call before the door of the car stopped at the hall call registration floor changes from an open to a closed state (step 108: N).

[0055] However, since call registration may be permitted at least from the time when the car is about to depart, users can register a call after the car door starts moving from an open to a closed state (step 108: Y).

[0056] This makes it possible to achieve both convenience for users when registering elevator car platform calls and improved efficiency in transporting users.

[0057] Another embodiment of the present invention will be described below. In the description of the second embodiment, the same components as those in the first embodiment are denoted by the same reference numerals in the drawings, and the description thereof will be omitted.

[0058] The second embodiment is characterized in that image information captured by a platform camera 38 installed at the platform is used to control the allocation of cars 12. Fig. 4 is a functional block diagram for realizing the group management control device 20. Note that Figs. 2 and 4 are each examples of functional block diagrams of the group management control device 22, and do not limit the hardware configuration of the group management control device 20.

[0059] The image analysis unit 40 analyzes images of the platform taken by the platform camera 38 installed at the platform, and sends analysis information to the information reception unit 50 of the group management control device 20. The image analysis information is, for example, real-time information relating to the congestion status (number of users) of the platform.

[0060] The congestion status determination unit 64 receives image analysis information from the information receiving unit 50 and, based on a predetermined threshold, sends a determination result as to whether the currently stopped car 12 can sufficiently accommodate the passengers at the platform to the cancellation determination unit 66. The cancellation determination unit 66 obtains congestion level information of passengers in the car 12 from the congestion level calculation unit 58.

[0061] The group management control device 22 allocates a car to a call registered by operating the hall buttons 340, 342. This is called a normal allocation. On the other hand, if the floor for which a call has been registered is crowded with many passengers and the normal allocation of cars is insufficient, the group management control device 22 allocates an additional car. This is called an additional allocation. As will be explained in detail later, if the congestion situation at the hall falls below a threshold, the cancellation determination unit 66 cancels the additional allocation without maintaining it.

[0062] The cancellation determination unit 66 is connected to the information output unit 68. The cancellation determination unit 66 creates information related to maintaining or canceling the additional allocation and transmits it to the information output unit 68. The information output unit 68 notifies the relevant information from a speaker in the car 12 via the car control device 24.

[0063] Next, the allocation control will be explained based on the flowchart in Figure 5. When the controller of the group management control device 22 detects the operation of the hall buttons 340, 342, it starts the flowchart in Figure 5. In step 200, the controller starts the normal allocation control already described. In step 202, the controller determines the number of users at the hall based on the detection information from the hall camera 38, and determines whether the hall is crowded by determining whether the number of people is above a predetermined number.

[0064] If the controller determines that the result of step 202 is negative, it executes normal allocation control and then terminates the flowchart. If the controller determines that the result of step 202 is positive, it proceeds to step 206 and starts the additional allocation control described above.

[0065] In step 208, the controller determines whether the first car has landed at the destination floor according to normal allocation control, and if the determination is affirmative, proceeds to step 210, where the number of passengers at the destination floor is determined based on the detection information from the destination floor's landing camera 38, and proceeds to step 212.

[0066] In step 212, the controller determines whether the landing is crowded, in the same way as in step 202. If the result of step 212 is affirmative, the controller proceeds to step 214, measures the load of the car, calculates the degree of congestion of the car, and then proceeds to step 216.

[0067] In step 216, the controller determines whether the congestion level is less than the threshold value, and if the determination is affirmative, proceeds to step 218, where an announcement is made via the speaker 26 to urge passengers to get into the car. Thereafter, the controller executes normal allocation control and additional allocation control, and then ends the flowchart. If the determination is negative in step 216, the controller does not execute step 218, and ends the flowchart after executing normal allocation control and additional allocation control.

[0068] If the controller determines that step 212 is negative, it proceeds to step 220, where it determines whether the second car has landed at the destination floor as a result of the additional allocation control. If the controller determines that step 220 is negative, it proceeds to step 222, where it cancels the additional allocation control midway, and ends the flowchart after executing the normal allocation control.

[0069] If the result of step 220 is affirmative, the controller determines that the cancellation of the additional allocation control was too late, and ends the flowchart after completing the normal allocation control and the additional allocation control.

[0070] The effects of the flowchart in Figure 5 will be explained below. When a car call is registered using hall buttons 340 and 342, if the hall at the destination floor is crowded with passengers, one car using normal allocation control may not be able to transport all passengers, or there is a risk that this may happen.

[0071] Therefore, in the second embodiment, the group management control device 22 performs additional allocation control to allocate an additional car to the destination floor. Additional allocation control can contribute to alleviating congestion at the landing.

[0072] However, at times other than when the car doors are completely closed, i.e., when the doors are opening, when the doors are completely opened, or when the doors are closing, passengers get on and off the car, so the hall camera 38 cannot accurately detect the number of people waiting at the hall.

[0073] Therefore, the group management control device 22 determines whether or not to perform additional allocation control when the car doors have been completely closed, and does not perform this control at any other time.

[0074] However, if congestion at the destination floor eases after the additional allocation is decided, and a car allocation different from that under normal allocation control continues, there will be few passengers using the additional car, and the allocation of the additional car will ultimately be unnecessary.

[0075] Therefore, the group management control device 22 is configured to be able to cancel the additional allocation control after determining the additional allocation and before the additional car arrives at the destination floor. This allows the group management control device 22 to refrain from unnecessary car allocation, thereby improving the transportation efficiency of users.

[0076] If the group management control device 22 performs additional allocations and the congestion level in the elevator car is low, i.e., if the rate at which passengers board the elevator car is low, the congestion level at the elevator car may not be alleviated immediately, and further additional allocations may be necessary. Therefore, it is decided to issue a notification to encourage passengers to board the elevator car (step 218). As a result, the rate at which passengers board the elevator car increases, and as a result, passenger transportation efficiency can be improved.

[0077] Even if the platform is crowded with many people, the platform camera 38 cannot distinguish whether all the people are waiting for a car 12 or whether they just happen to be at the platform. If the group management control device 22 performs additional allocation control based on information that the platform is crowded, there is a risk that the dispatch of a second car will end up being unnecessary.

[0078] However, according to the flowchart of FIG. 5, even if an additional allocation has been decided, it can be canceled (step 222), so that the decrease in transportation efficiency due to the additional allocation of cars can be suppressed.

[0079] Next, another embodiment of additional allocation control will be described. When there is only one car 12 available for additional allocation, and an event occurs in which additional car allocation is required for multiple floors, the group management control device 22 determines which floor to prioritize for additional car allocation, not in order, but in accordance with a priority according to the situation.

[0080] For example, consider a case in which the boarding areas of multiple floors (for example, the first and fifth floors) in a seven-story building become congested at the same time, making additional allocation control necessary.

[0081] During rush hour (for example, 7:00 AM), there is high demand for cars 12 at the first floor platform, so if additional cars 12 were allocated to the fifth floor, the congestion on the first floor would worsen, disrupting the flow of people through the building. Therefore, the group management control device 22 determines the floor to which additional cars should be allocated with priority depending on the time of day, as shown in the flowchart of Figure 6. The controller of the group management control device 22 starts the flowchart at predetermined intervals.

[0082] In step 300, the controller determines whether congestion has been detected on multiple floors simultaneously. If the controller determines no in step 300, it ends the flowchart. If the controller determines yes in step 300, it sets priorities for additional allocation to each of the multiple crowded floors and allocates additional cars to each floor according to the priorities. Time is a parameter for priority. The controller proceeds to step 302 and determines whether it is the rush hour (for example, 7:00 AM to 9:00 AM).

[0083] If the controller judges in step 302 as positive, it proceeds to step 304, performs additional allocation by prioritizing floors where users are concentrated when they arrive at work (e.g., the first floor), and proceeds to step 306. If the controller judges in step 302 as negative, it skips step 304 and proceeds to step 306. In step 306, the controller determines whether it is the off-work time slot (e.g., from 4:00 PM to 6:00 PM).

[0084] If the controller judges in step 306 that it is YES, it proceeds to step 308, where it performs additional allocation by prioritizing floors where users are concentrated when leaving work (e.g., the 5th floor), and proceeds to step 310. If the controller judges in step 306 that it is NO, it skips step 308 and proceeds to step 310.

[0085] In step 310, the controller determines whether there are circumstances that require a change in priority. For example, it determines whether the first car to be additionally assigned will pass through other non-priority, but congested, floors before arriving at the floor to which it has been assigned priority. In this case, it is preferable from the perspective of passenger transportation efficiency to have the car stop at the other congested floors first.

[0086] If the controller determines yes in step 310, it proceeds to step 312, where it performs additional allocation, giving priority to other crowded floors that were not given priority in step 304 or step 308, and ends the flowchart. If the controller determines no in step 310, it skips step 312 and ends the flowchart. If the controller determines no in step 310, it may perform additional allocation of cars to each of the multiple floors equally and equally, regardless of priority.

[0087] According to the flowchart in Figure 6, priority is assigned based on the parameters of time and time zone, and additional cars are allocated to each of multiple floors that are simultaneously crowded, so it is possible to improve the efficiency of transporting passengers while smoothing the flow of people in the building. Note that the parameters are not limited to time, and there are no particular restrictions on the number of passengers per floor, etc.

[0088] For example, in a seven-story building, if congestion occurs at the first and fifth floors simultaneously during rush hour, and all cars 12 are parked above the fifth floor, the first car passing the crowded fifth floor and moving to the first floor will reduce the efficiency of passenger transportation. Therefore, even if the group management control device 22 initially decides to prioritize the first floor (step 304), it can change this to prioritize the fifth floor instead. This increases the utilization rate for additional car allocations, improving passenger transportation efficiency.

[0089] The above-described embodiment is an example of the present invention and does not limit the present invention. The technical scope of the present invention also includes modifications, deletions, or replacements of parts of the above-described embodiment, or the addition of other configurations or functions. Further explanation will be given below.

[0090] If the first car 12A of the three cars 12 is equipped with a wheelchair function, when a call for that car is registered after the aforementioned additional allocation control is determined, the wheelchair-equipped car 12A will be used as a third car to provide service to users at the destination floor in addition to the two cars used for the additional allocation control. This means that three cars 12A, 12B, and 12C will be concentrated on the same floor, causing a disruption in service to other floors.

[0091] Therefore, when a call for a car for a wheelchair is registered after the additional allocation has been determined, the group management control device 22 can change the second car for additional allocation control from car No. 3 (car 12C) to car No. 1 (car 12A) if a predetermined condition is met, for example, if the required time for the additionally allocated car to arrive at the destination floor is 20 seconds or more. This allows the elevator system to accommodate wheelchair users in the additional allocation of cars without impairing the efficiency of transporting users.

[0092] On the other hand, if multiple additional cars are allocated and the first car arrives at the destination floor and completes its service to the user, but the next car is unable to reach the destination floor even after the specified time has passed, the congestion on that floor will not be alleviated and the flow of people through the building will be disrupted.

[0093] Therefore, even after determining the additional allocation, the group management control device 22 can change the allocation of cars, including car 12 that departed as the first car of the additional allocation, depending on the status of hall calls and car calls on other floors. This allows multiple cars to be dispatched to the destination floor, making it possible to alleviate congestion at the hall calls.

[0094] Next, if hall call registration is permitted (FIG. 1: step 110), it can be said that there is demand for hall calls at that time. If congestion at the hall is not detected except when the doors are completely closed (FIG. 5: step 202), the group management control device 22 cannot set additional allocation control even if a hall call is operated.

[0095] Therefore, when a hall call is permitted to be made, the group management control device 22 can detect congestion at the hall even between the time when the doors are completely opened and the time when they are completely closed. This allows additional allocation to be started at an early stage in response to congestion at the hall, and additional cars can be dispatched to the destination floor.

[0096] This specification includes inventions having the configurations described in the following appendices. (Addendum) a group management control device that manages, in cooperation with one another, a plurality of elevators, each of which has a car with an openable / closable door; a platform button that is installed at a platform for the car provided on each floor of the building and that registers a call for the car; In an elevator system including a plurality of elevator control devices that individually control the lifting and lowering operations of the plurality of elevator cars and the opening and closing operations of the doors, a platform congestion detection device for detecting the platform congestion level, When the landing congestion detection device simultaneously detects congestion on a plurality of floors and performs additional allocation of cars to a predetermined floor and a floor other than the predetermined floor, which are mutually prioritized, The group management control device An elevator device that allocates the cars to the specified floor or the other floor with priority based on a time period, and if one of the additionally allocated cars passes through a floor that is not assigned with priority before landing at the floor that is assigned with priority, reallocates the floor that is not assigned with priority as a priority target for additional allocation control. [Explanation of symbols]

[0097] 10· ... (30A, 30B, 30C) Door opening and closing mechanism unit, 32 (32A, 32B, 32C) Opening and closing door, 34A, 34B Platform button, 36 (36A, 36B, 36C) Load detection sensor, 38 Platform camera, 40 Image analysis unit, 50 Information reception unit, 52 Operation status determination unit, 54 Vehicle dispatch confirmation unit, 56 Operation control unit, 58 Congestion level calculation unit, 60 Load-to-number of passengers conversion table memory, 62 Platform button registration availability determination unit.

Claims

1. a group management control device that manages, in cooperation with one another, a plurality of elevators, each of which has a car with an openable / closable door; a platform button that is installed at a platform for the car provided on each floor of the building and that registers a call for the car; and a plurality of elevator control devices that individually control the lifting and lowering operations of the plurality of elevator cars and the opening and closing operations of the doors, a car congestion detection device that is installed in each of the plurality of elevators and determines the congestion level of people riding in the car, The group management control device While the car is open at a stop floor, registration of the platform button at the stop floor is not permitted, When the door of the car of any of the elevators at the landing of a specific floor has started to close, or when it is determined that the congestion level of the car stopped at the landing is equal to or greater than a predetermined threshold, the registration of the landing button is permitted, Further, a platform congestion detection device for detecting the platform congestion level is provided, The group management control device when a specific car stops at a landing at a predetermined stop floor and a door starts to close, if the landing congestion detection device determines that the congestion level of the landing is equal to or higher than a predetermined threshold, execute additional allocation control to additionally allocate a car of the elevator other than the specific car to the predetermined stop floor; The elevator device executes control to cancel the additional allocation control if the hall congestion detection device determines that the congestion has been resolved after the additional allocation control is determined.

2. Further, the car has a notification unit that is installed in the car and that prompts passengers to get on the car, The group management control device 2. The elevator apparatus according to claim 1, wherein when it is determined that the congestion level of the car is less than a predetermined threshold and the congestion level of the hall is equal to or greater than a predetermined threshold, the notification unit executes notification control to encourage passengers to board the elevator.

3. 2. The elevator apparatus according to claim 1, wherein, after the additional allocation control is determined and the first car has landed at the floor, if a predetermined time has elapsed while the boarding rate is below a predetermined level and congestion at the landing is above a predetermined level, the additional allocation is canceled.

4. When the landing congestion detection device simultaneously detects congestion on a plurality of floors and performs additional allocation of cars to a predetermined floor and a floor other than the predetermined floor, which are mutually prioritized, The group management control device 2. The elevator system according to claim 1, wherein the elevator cars are preferentially assigned to the predetermined floor or the different floor based on a time period, and when one of the additionally assigned cars passes through a floor that is not preferentially assigned before landing at the floor to which it is preferentially assigned, the floor that is not preferentially assigned is reallocated as a priority target for additional assignment control.

5. Among the plurality of elevators, some are equipped with cars with wheelchair accessibility and with landing buttons for calling cars with wheelchair accessibility on each floor; 2. The elevator apparatus according to claim 1, wherein the group management control device reassigns the wheelchair-equipped car as the second car for the additional allocation control if the wheelchair hall button is pressed after determining the additional allocation control and if a predetermined condition is satisfied.

6. 2. The elevator apparatus according to claim 1, wherein, if a second elevator as the additional allocation control does not arrive at the floor within a predetermined time after the additional allocation control is determined, the group management control device reallocates the second elevator as the additional allocation control to another elevator.

7. 2. The elevator system according to claim 1, wherein the group management control device detects whether or not there is congestion of hall calls even after the doors have been opened and closed, when registration of hall calls is permitted.

Images