Elevator capacity allocation system, elevator capacity allocation method and elevator

Abstract

This invention provides an elevator capacity allocation system, method, and elevator, including: a strategy parameter setter, an elevator status detector, an elevator floor controller, an elevator dispatch controller, and an external call controller. The elevator floor controller connects or disconnects the button switches and indicator lights on the elevator car floor selection buttons to the elevator button panel, and the external call controller connects or disconnects the button switches and indicator lights on the elevator external call buttons to the elevator button panel. This prevents the phenomenon of "lower-floor passengers entering the car prematurely while higher-floor passengers are unable to enter," solving the problem of long-term inaccessibility for higher-floor passengers. Furthermore, through strategy control, designated elevators in the elevator group are dedicated to serving passengers on peak downward flights. During peak downward flights, the elevator dispatch controller, based on a set strategy, ensures that the elevator car reaches the base floor as fully loaded as possible on each downward trip, minimizing intermediate stops and solving the problem of long waiting times for passengers on downward flights.

Description

Technical Field

[0001] This invention relates to the field of elevator access technology, and in particular to an elevator capacity distribution system, an elevator capacity distribution method, and an elevator. Background Technology

[0002] Vertical elevators are an indispensable transportation tool in modern buildings, enabling convenient and rapid transport of people and goods, playing a vital role in daily life. However, during peak hours, elevators often experience long travel times due to overcrowding and numerous stops, making waiting a daily problem for most people. In an attempt to shorten waiting times, some individuals engage in improper maneuvers, further causing elevators to idle and creating a vicious cycle that exacerbates the waiting time. For those on lower floors, the elevator is often already full in the upper floors, frequently stopping empty upon arrival and forcing them to press the down call button again to wait for the next elevator. Consequently, some people on lower floors press both the up and down call buttons simultaneously to ascend from their lower floors to higher floors before descending to the common areas. Because people on lower floors enter the elevator in advance, people on higher floors cannot enter the elevator. When the elevator descends from the higher floors, it stops and opens the door again at the same lower floor because of the previously pressed lower floor down call. However, no one is waiting at this time, which further lengthens the car's turnaround time and reduces the elevator's capacity. At the same time, people on lower floors entering the car in advance and taking the elevator in the opposite direction prevents people on higher floors from entering, causing people on higher floors to wait for the elevator for a long time.

[0003] Furthermore, the following factors are currently causing a decrease in elevator capacity:

[0004] 1. During peak hours, there are usually floor-to-floor stops, which can cause the elevator to stop too many times per trip. The car has to slow down before it can accelerate, resulting in the car running at low speed for a long time. This makes it difficult for the elevator to turn around quickly and reduces its carrying capacity.

[0005] 2. When the elevator is fully loaded but not overloaded, the elevator's control system still responds to passenger requests, causing the car to stop at all floors where the call button has been pressed. After stopping, people outside cannot enter because the elevator is full, which is actually an invalid intermediate stop. These intermediate stops increase the elevator's deceleration time, the car's door opening and closing time, and the car's leveling waiting time, resulting in a significant increase in elevator turnaround time and a serious reduction in elevator capacity.

[0006] 3. Elevators typically only dispatch one car to respond to a call. Other cars often remain stationary on a floor and wait for a period of time before being dispatched to respond to a call, resulting in wasted capacity.

[0007] To address these issues, some elevator companies can program elevators to adapt to peak-hour operating requirements, but this is costly, and in many cases, such adjustments cannot keep pace with constantly changing circumstances. For example, relocations of companies in office buildings and adjustments to work schedules can alter peak elevator usage times, and elevator companies cannot always respond to user needs by changing their operating strategies accordingly. Furthermore, buildings with existing elevator installations and relatively old elevator systems cannot solve capacity shortages simply by adding more elevators.

[0008] It should be noted that the information disclosed in the background section above is only for understanding the background of this application, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0009] The purpose of this invention is to solve the problem of elevators being able to quickly respond to the elevator requests of people going downhill during peak hours, thereby shortening the waiting time for elevator users.

[0010] To achieve the above objectives, the present invention adopts the following technical solution:

[0011] An elevator capacity distribution system includes:

[0012] The strategy parameter setter is used to set the strategy parameters related to the elevator operation strategy and download the strategy parameters to the elevator dispatch controller. The elevator operation strategy enables the designated elevators in the elevator group to be used exclusively to serve the downward peak floors, and to reduce intermediate stops while ensuring that the car is as fully loaded as possible to the base station floor on each downward trip, so as to make full use of the elevator's downward carrying capacity and solve the problem of long waiting time for downward elevators.

[0013] Elevator status detectors are used to detect the status of the elevator car and send the car status to the elevator floor controller in real time.

[0014] The elevator floor controller interfaces with the elevator's own control system. It can selectively connect or disconnect the button switches and indicator lights on the floor selection buttons inside the elevator car from the elevator button panel. When disconnected, the passenger's floor selection signal cannot be sent to the elevator's own control system, preventing the elevator from responding to internal call requests. The elevator floor controller can forward the car status sent by the elevator status detector to the elevator dispatch controller and receive the command signals from the elevator dispatch controller. Based on the specified floor, it simulates sending the corresponding button press-triggered signal to cause the car to proceed to the corresponding floor.

[0015] The elevator dispatch controller receives car status information from the elevator status detector forwarded by the elevator floor controller. It then performs dispatch calculations based on the strategy parameters set by the strategy parameter setter and the car status detected by the elevator status detector. This determines the planned peak-hour floors for the elevator to stop at, and dispatches each car in turn to stop at those peak-hour floors. Once a car meets specified conditions, it proceeds directly to the designated floor, reducing intermediate stops and improving the elevator's downward transport efficiency. Based on the dispatch calculation results, the elevator dispatch controller sends a command signal to the elevator floor controller to press the corresponding floor button, prompting the car to proceed to that floor, thus achieving elevator dispatch.

[0016] The external call controller interfaces with the elevator's own control system and can selectively connect or disconnect the button switches and indicator lights on the original elevator external call buttons from the elevator button panel. When disconnected, the button signals from passengers cannot be sent to the elevator's own control system, preventing the elevator from responding to external call requests.

[0017] In some embodiments, the outbound call controller can detect the up / down call signal of the outbound call button and send the signal to the elevator dispatch controller through the communication port. It can also receive the instruction signal from the elevator dispatch controller and send a button indicator light on / off signal to the corresponding outbound call button.

[0018] In some embodiments, a passenger counting system is further included, comprising: a passenger counting device inside each elevator car and a passenger counting device in the waiting hall on each floor; the passenger counting device inside each elevator car feeds back the number of passengers inside the car to the elevator floor controller, which then sends the information to the elevator dispatch controller; the passenger counting device in the waiting hall on each floor feeds back the number of passengers in the waiting hall to the elevator dispatch controller; enabling the elevator dispatch controller to perform dispatch calculations by combining the number of passengers in the elevator car and the waiting hall fed back by the passenger counting system.

[0019] In some embodiments, the external call controller uses passive dry contact technology to interface with the elevator's own control system. When powered on, it can disconnect the button switches and indicator lights on the original elevator external call buttons from the elevator button panel, so that the button signals of the passengers cannot be sent to the elevator's own control system, and the light / light-off signals sent by the elevator's own control system cannot turn on / off the button indicator lights. When the power is off, a fault is detected, or there is no need for downhill peak scheduling, it can restore the interrupted signals to the state of connection with the elevator's own control system, that is, restore the elevator to the original system mode.

[0020] In some embodiments, the elevator floor controller uses passive dry contact technology to interface with the elevator's own control system. When powered on, it can disconnect the button switches on the floor selection buttons inside the elevator car from the elevator button panel, so that the floor selection signal of the passenger cannot be sent to the elevator's own control system, but is instead detected and processed by the elevator floor controller. When the power is off, a fault is detected, or there is no need for downhill peak scheduling, it can restore the interrupted signal to the state of being connected to the elevator's own control system, that is, restore the elevator to the original system mode.

[0021] In some embodiments, the strategy includes: a downhill peak floor that has already been stopped at must wait until all other downhill peak floors that are waiting to be scheduled have been scheduled before it can stop again after a new round of scheduling, so that people on all floors have the opportunity to take the elevator.

[0022] In some embodiments, the strategy parameters include: base station floor, and which elevator cars are dedicated to downlink peak scheduling.

[0023] In some embodiments, the strategy parameters may further include: the time period during which the system enters the down-peak mode, the time period during which each floor is determined to be a down-peak floor, and the maximum number of floors that the elevator car stops at in each trip during peak hours; or may include the number of people in the waiting hall that corresponds to a floor being determined to be a down-peak floor, the number of floors in the elevator hall that reach the down-peak standard when the system automatically enters the down-peak mode, and the maximum passenger capacity of the elevator car.

[0024] In some embodiments, the elevator operation strategy conforms to the following model:

[0025]

[0026] Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip, η be the fixed time cost of one trip of the elevator, and y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i i = 1, 2, ..., I, T operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, and n is the total travel time of the elevator. r,i This represents the number of people who enter the elevator on the i-th floor during the r-th trip.

[0027] In some embodiments, the model constraints include:

[0028]

[0029] Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i Let i = 1, 2, ..., I, C be the maximum number of passengers per trip, M be a sufficiently large integer, and T be the maximum number of passengers per trip. operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, S r,i This is an integer input parameter that can take the value 0 or 1, and its meaning is as follows:

[0030]

[0031] The present invention also discloses an elevator, which includes the elevator capacity distribution system described above.

[0032] This invention also discloses an elevator capacity allocation method, comprising the following steps:

[0033] S1: Receive user input, set the strategy parameters related to elevator operation through the strategy parameter setter, and download the strategy parameters to the elevator dispatch controller;

[0034] S2: The elevator dispatch controller detects whether it has entered the downhill peak mode. If so, it allocates all designated cars for downhill peak transportation, disconnects the button switch on the outbound call button from the elevator button panel, and disconnects the button switch on the floor selection button inside the car from the elevator button panel, so that the elevator does not respond to the passenger's outbound call.

[0035] S3: The elevator dispatch controller determines which floors are currently experiencing peak downhill hours based on the elevator operation strategy corresponding to the strategy parameters.

[0036] S4: The elevator dispatch controller dispatches the elevator cars to determine the planned down-peak floors according to the elevator operation strategy, and dispatches each car used for down-peak transportation in turn to stop at the floors. After the car meets the specified conditions, it goes directly to the base station floor, reducing intermediate stops and improving the efficiency of elevator down-peak transportation.

[0037] In some embodiments, the strategy parameters related to the strategy in step S1 include: base station floor, the time period during which the system enters the downlink peak mode, the time period during which each floor is determined to be a downlink peak floor, which elevator cars are dedicated to downlink peak scheduling, and the maximum number of floors that each peak car stops at; or it may also include the number of people in the waiting hall that corresponds to the floor being determined to be a downlink peak floor, the number of floors in the elevator hall that reach the downlink peak standard when the system automatically enters the downlink peak mode, and the maximum number of passengers that the elevator car can carry.

[0038] In some embodiments, in step S2, the elevator dispatch controller determines to enter the downhill peak mode after detecting that the time has arrived, based on the elevator operation strategy corresponding to the strategy parameters set by the strategy parameter setter.

[0039] In some embodiments, in step S2, the number of people waiting for the elevator and the number of floors that have reached the peak downward movement standard are detected by the number of people counting system to determine whether to enter the peak downward movement mode.

[0040] In some embodiments, step S3 includes: determining which floors are peak downhill floors according to the strategy parameter setting information.

[0041] In some embodiments, step S3 includes: determining which floors are currently experiencing peak downhill traffic based on the number of people in the single-floor waiting area detected by the headcount system.

[0042] In some embodiments, step S4 includes: determining which floors need to be served based on which floors are currently peak downhill floors and whether the call button for the corresponding peak downhill floor has been pressed, and the elevator dispatch controller sorts these floors to be served.

[0043] In some embodiments, step S4 includes: the elevator dispatch controller dispatches the floors to be served in order, and at the same time the outbound call controller outputs a signal to the outbound call button indicator light to light up the outbound call button indicator light; or the elevator dispatch controller sends a command signal to the outbound call controller of the corresponding floor to output a signal to the downbound outbound call button indicator light to light up the downbound outbound call button indicator light.

[0044] In some embodiments, step S4 includes: the elevator dispatch controller dispatches the car according to the elevator operation strategy, determines the planned down-peak floors based on how many floors the car will be fully loaded after stopping, and dispatches each car used for down-peak transportation to take turns stopping at the floors. After the car meets the full-load condition, it goes directly to the base station floor, reducing intermediate stops and improving the down-peak transportation efficiency of the elevator.

[0045] In some embodiments, step S4 includes:

[0046] The elevator status detector checks whether each car has completed a certain task. If a car has completed the task, it is dispatched to the planned downhill peak floor to transport passengers according to the elevator operation strategy.

[0047] In some embodiments, if the elevator status detector detects that the operating status of the corresponding car changes from running to timed-out stationary, or if the elevator status detector detects that the car assigned a task has arrived at the base station floor set by the elevator operation strategy and opened the door, then it is determined that a certain task has been completed.

[0048] In some embodiments, step S4 includes: the downhill peak floor that has already stopped must wait for all other downhill peak floors that are waiting to be scheduled to be scheduled before it can stop again after a new round of scheduling, so that people on the middle, high and low floors have the opportunity to take the elevator.

[0049] In some embodiments, step S4 includes:

[0050] S41: The floor is placed in the dispatch queue according to the time sequence in which it is detected that it is a peak downhill floor and that floor is not placed in the dispatch queue, or according to the time sequence in which it is detected that it is a peak downhill floor, the outbound call controller detects that a downhill outbound call button has been pressed, and that floor is not placed in the dispatch queue. The dispatch queue refers to the queue of floors with stopping needs.

[0051] S41: If the elevator dispatch controller detects through the elevator status detector that a car has completed the previous task, it will take the first k floors that have not yet been marked as "already dispatched" from the queue to be dispatched, and mark these floors as "already dispatched".

[0052] S42: The elevator dispatch controller takes the highest dispatch floor f from these k floors and sends a registration floor f instruction signal to the elevator floor controller of the corresponding car. After receiving the instruction signal, the elevator floor controller simulates the signal triggered by the corresponding button being pressed, causing the car to go to the corresponding floor.

[0053] S43: When the elevator dispatch controller detects through the elevator status detector that the designated car has stopped after a timeout or changed direction while traveling upwards to the top floor, if the top floor reached is floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor reached is not floor f, it sends instruction signals for the k floors and the base station floor to the corresponding elevator floor controller. When the elevator dispatch controller detects through the elevator status detector that the designated car has traveled downwards to floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. After receiving the instruction signals, the elevator floor controller simulates the signal triggered by pressing the corresponding button, causing the car to travel to the corresponding floor.

[0054] S44: When the elevator dispatch controller detects that the door of a designated car is open on a floor out of the k floors through the elevator status detector, it considers that the car has stopped at that floor once. The elevator dispatch controller sends a command signal to the call controller of the corresponding floor, outputs a signal to the down call button indicator light, turns off the down call button indicator light, and removes the floor from the dispatch queue. It then continues to determine whether the floor is still a peak down call floor and whether it needs to be placed at the end of the dispatch queue to enter the next round of dispatch.

[0055] In some embodiments, in step S41, the maximum number of floors the elevator car will stop at during peak hours is set according to the elevator operation strategy or the detection results of the passenger count system.

[0056] In some embodiments, step S43 includes: during the downlink process, if the passenger counting system detects in advance that the car is full, then the downlink peak floor that is planned to stop outside the base station floor is removed, while the position of the canceled floor in the original waiting queue is retained, and the "already in scheduling" mark is removed or the mark is changed to "not in scheduling", so that other cars can stop at these floors first after completing their tasks.

[0057] In some embodiments, step S4 includes: if the outbound call controller detects a passenger request that the upbound outbound call button on a downbound peak floor is pressed or the upbound / downbound outbound call button on a non-downbound peak floor is pressed during the downbound peak period, the elevator dispatch controller dispatches a car operation designated for use outside of the downbound peak period to respond to the passenger request.

[0058] In some embodiments, the elevator operation strategy conforms to the following model:

[0059]

[0060] Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and tr Let y be the total running time of the r-th trip, η be the fixed time cost of one trip of the elevator, and y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i i = 1, 2, ..., I, T operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the travel time of the elevator from floor i to floor j.

[0061] In some embodiments, the model constraints include:

[0062]

[0063]

[0064] Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i Let i = 1, 2, ..., I, C be the maximum number of passengers per trip, and T be the maximum number of passengers per trip. operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, S r,i This is an integer input parameter that can take the value 0 or 1, and its meaning is as follows:

[0065]

[0066] The present invention also discloses an elevator, including a central controller and a memory, wherein the memory stores a computer program, and when the elevator is running, the central controller retrieves the program stored in the memory to implement the above-mentioned elevator capacity allocation method.

[0067] The present invention has the following beneficial effects:

[0068] The elevator control system of this invention selectively connects or disconnects the button switches on the floor selection buttons inside the elevator car and the elevator button panel via an elevator floor controller, and selectively connects or disconnects the button switches and indicator lights on the external call buttons to the elevator button panel via an external call controller. This ensures that the elevator can only stop at the designated floors during peak downward periods, and proceeds directly to the designated floor after being fully loaded. This prevents passengers from pressing other floor buttons, thus eliminating unnecessary frequent stops. While ensuring the elevator car is fully loaded, it shortens the elevator's downward travel time, increases elevator speed, improves downward capacity, and reduces waiting time for passengers. Since both internal and external calls are controlled, it also prevents passengers from riding the elevator in the opposite direction, thus preventing wasted capacity and exacerbating long waiting times. In this method, during peak downward periods, the elevator dispatch controller automatically dispatches designated elevator cars to prioritize passengers requesting elevators on peak downward floors according to set strategy parameters, thereby increasing downward elevator capacity and solving the problem of long waiting times for passengers going downhill.

[0069] Furthermore, since the number of floors the elevator stops at on each trip can be controlled by strategy parameters, users can set these parameters based on the actual number of floors the car needs to stop before it becomes fully loaded. This ensures that the elevator is nearly fully loaded on each downward trip, preventing any loss of passenger capacity. Simultaneously, the elevator dispatch controller will schedule the elevators to stop at each floor in sequence, ensuring that all peak downward floors (high, medium, and low) are visited in turn, resulting in a roughly equal opportunity for passengers. Even if users on lower floors do not travel in the opposite direction, they will not find themselves without an elevator due to high-rise buildings being overcrowded. Attached Figure Description

[0070] Figure 1 This is a flowchart of the elevator capacity allocation method in an embodiment of the present invention;

[0071] Figure 2 These are schematic diagrams of the elevator capacity distribution system in Embodiments 1 and 2 of the present invention;

[0072] Figure 3 This is a flowchart of the elevator capacity allocation system operation task allocation in Embodiment 1 of the present invention;

[0073] Figure 4 This is a flowchart of the elevator capacity allocation system operation task allocation in Embodiment 2 of the present invention;

[0074] Figure 5 This is a flowchart of the elevator capacity allocation system operation task allocation in Embodiment 3 of the present invention;

[0075] Figure 6 This is a schematic diagram of the elevator capacity distribution system in Embodiment 3 of the present invention;

[0076] Figure 7This is a flowchart of the elevator capacity allocation system operation task allocation in Embodiment 4 of the present invention;

[0077] Figure 8 This is a schematic diagram of the elevator capacity distribution system in Embodiment 4 of the present invention;

[0078] Figure 9 This is a flowchart of the elevator capacity allocation system operation task allocation in Embodiment 5 of the present invention;

[0079] Figure 10 This is a schematic diagram of the elevator capacity distribution system in Embodiment 5 of the present invention. Detailed Implementation

[0080] The embodiments of the present invention will be described in detail below. It should be emphasized that the following description is merely exemplary and not intended to limit the scope and application of the present invention.

[0081] It should be noted that when a component is referred to as "fixed to" or "set on" another component, it can be directly or indirectly attached to that other component. When a component is referred to as "connected to" another component, it can be directly or indirectly connected to that other component. Furthermore, a connection can be used for fixing, coupling, or communication.

[0082] It should be understood that the terms "length", "width", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", and "outer" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the present invention.

[0083] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of the present invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0084] To address the problems of uneven capacity distribution during peak hours due to the inability of elevators' built-in control systems, long waiting times for passengers, elevator idling, and increased elevator operating costs, an elevator capacity distribution system and method are proposed.

[0085] The components of the elevator capacity distribution system in this embodiment of the invention are as follows:

[0086] 1. Outbound call controller (in some embodiments, it only has control functions and no detection functions; in other embodiments, it has both control and detection functions)

[0087] Each floor of the building is equipped with an outbound call controller. Each outbound call controller can be assigned an address for communication and is used to correspond to a specific floor.

[0088] The external call controller is equipped with a communication port, which can communicate with the elevator dispatch controller;

[0089] The external call controller uses passive dry contact technology to interface with the elevator's own control system. Upon power-up, it can selectively connect or disconnect the button switches and indicator lights on the original elevator external call buttons from the elevator control panel. When disconnected, the user's button signals cannot be sent to the elevator's own control system, and the indicator lights on / off signals from the elevator's own control system also cannot be turned on / off. These interrupted signals are then detected and processed by the external call controller. When peak-hour scheduling is not required, or in the event of a power outage or a detected fault (including communication failure), the interrupted signals can be restored to the state of connection with the elevator control panel, thus restoring the elevator to its original system mode without affecting passenger access.

[0090] The external call controller can detect the pressed signals of the external call buttons, including the pressed signals of the up / down call buttons, and send the signals to the elevator dispatch controller through the communication port;

[0091] The external call controller can receive command signals from the elevator dispatch controller and send indicator light on / off signals to designated external call buttons, including sending indicator light on / off signals to the up / down call buttons;

[0092] II. Strategy Parameter Setter

[0093] The strategy parameter setter has an input interface for users to set relevant strategy parameters for elevator descent peak-hour scheduling strategies, including:

[0094] The time period during which the system enters the downward peak mode: The time periods during which the elevator capacity allocation system enters the downward peak mode can be set according to the actual peak time of elevator passenger flow in the building (hereinafter referred to as the downward peak period). During the downward peak period, the system will enter the downward peak mode, and at least during the downward peak period, the elevator scheduling will be changed from the original elevator system to the elevator scheduling controller.

[0095] Downward peak floors and time periods for each floor to be identified as downward peak floors: In the downward peak mode, the floors that are identified as downward peak floors can be determined based on the number of passengers on each floor during the peak hours of actual elevator traffic. The time period for each floor to be in the downward peak mode (referred to as the floor peak period) is also set. When the elevator dispatch controller detects that a floor has entered the floor peak period, it will be included in the dispatch queue. The dispatch queue refers to the queue of floors with stopping needs.

[0096] Maximum number of floors the elevator car stops at during peak hours: This setting is based on the estimated number of floors the car will typically stop at before reaching full capacity during its descent.

[0097] Base station floor: This refers to the destination floor during the downlink peak hours. It is the floor to which the elevator car will directly travel after being fully loaded during the downlink peak hours, usually the 1st floor, etc.

[0098] Maximum passenger capacity of the car: This is used to set the number of people in the car when it is fully loaded.

[0099] Peak Hour Number of People per Floor: This setting determines the floor that is considered a peak hour floor during the downhill peak mode, based on the number of people in the waiting area. In other words, it indicates when the system detects that a floor has reached a certain number of people in its waiting area and enters the downhill peak mode.

[0100] When the system automatically enters the downhill peak mode, the number of floors in the elevator lobby that meet the downhill peak standard is used to set the number of people the system detects. When the system detects that the number of floors in the elevator lobby has reached the downhill peak standard, the system will automatically enter the downhill peak mode. In non-downhill peak mode, the downhill peak standard is considered to have been reached when the number of people in the elevator lobby reaches the specified number.

[0101] Which cars are dedicated to peak-hour dispatch: These are the cars specifically designated to respond to requests to ride the elevator during peak-hour periods (peak-hour cars). Once set, calls from peak-hour floors or non-peak-hour floors will dispatch other designated cars to complete the ride.

[0102] The strategy parameter setter is equipped with a communication interface for downloading user-defined strategy parameters to the elevator dispatch controller, allowing the elevator dispatch controller to perform dispatch calculations according to the set strategy.

[0103] The elevator operation strategy designates elevators in the elevator group to serve downward travel, and ensures that the car is as fully loaded as possible to the base station floor on each downward trip, thereby reducing intermediate stops and making full use of the elevator's downward carrying capacity, thus solving the problem of long waiting time for downward travel.

[0104] III. Elevator Dispatch Controller

[0105] The elevator dispatch controller is equipped with a communication port, which can receive strategy parameters from the strategy parameter setter; it can also receive button signals from the external call controller through the communication port, and at the same time, it can send up / down external call button indicator light-on / off signals to the external call controller of a designated floor through the communication port; it can also send button control command signals to the elevator floor controller through the communication port, so that the elevator floor controller can simulate sending button press command signals to the elevator's own control system, causing the car to move to the corresponding floor; at the same time, it can receive car status information sent by the elevator status detector forwarded by the elevator floor controller through this communication port.

[0106] The elevator dispatch controller contains a dispatch algorithm. Based on the status of each car, it performs dispatch calculations according to a set strategy. By sending a command signal to the elevator floor controller to press the corresponding floor, it dispatches the corresponding car to the corresponding floor to pick up the passenger. After picking up the passenger, it uses the same method to send the car to the corresponding destination floor.

[0107] Specifically, the elevator dispatch controller performs dispatch calculations based on the strategy parameters set by the strategy parameter setter and the car status detected by the elevator status detector to determine the planned downhill peak floors. The downhill peak floors are the floors that have entered the downhill peak mode. The elevators are dispatched in turn to serve the downhill peak floor passenger requests in turn. After the car meets the specified conditions, it goes directly to the base floor, reducing intermediate stops and improving the downhill transport efficiency of the elevator. In this embodiment, the specified conditions refer to the set full load conditions. In some embodiments, downhill peak floors that have already been stopped are placed at the end of the dispatch queue and stopped again after dispatch.

[0108] IV. Elevator Status Detector

[0109] Elevator status detectors are installed in each car and consist of various sensors. By adding these sensors, the car's status can be detected without retrieving data from the elevator's own system. This includes information such as which floor the car is currently on, whether it is running or stopped, whether the doors are open or closed when stopped, and whether it is moving up or down.

[0110] The elevator status detector is equipped with a communication port, which can send the car status to the elevator floor controller in real time, and then the controller forwards it to the elevator dispatch controller for use in dispatch calculations.

[0111] V. Elevator Floor Controller

[0112] The elevator floor controller is equipped with a communication port, which can communicate with the elevator dispatch controller;

[0113] The elevator floor controller can forward the car status sent by the elevator status detector to the elevator dispatch controller;

[0114] The elevator floor controller uses passive dry contact technology to interface with the elevator's own control system. Upon power-up, it disconnects the button switches and indicator lights on the floor selection buttons inside the elevator car from the elevator control panel, preventing the passenger's floor selection signal from being sent to the elevator's own control system. Instead, the elevator floor controller detects and processes the signal. When peak-hour scheduling is not required, or in the event of a power outage or a detected fault (including communication failure), the interrupted signal is restored to its original connection with the elevator control panel, reverting to the original elevator system mode without affecting passenger access.

[0115] The elevator floor controller can receive instruction signals from the elevator dispatch controller and send out signals triggered by pressing the corresponding buttons according to the specified floor, so as to cause the elevator car to move to the corresponding floor.

[0116] VI. Headcount System (In some embodiments, a headcount system is included; in other embodiments, no headcount system is included)

[0117] The use of the passenger counting system is divided into two scenarios: application inside the elevator car and application in the waiting hall on each floor. This allows the elevator dispatch controller to perform dispatch calculations based on the passenger count data provided by the passenger counting system, as detailed below:

[0118] (1) Each elevator car can have a occupancy meter, which can feed back the number of people in the car in real time or not in real time to the elevator floor controller. The elevator floor controller then sends the information to the elevator dispatch controller, which determines the processing logic for issuing tasks based on the number of people.

[0119] A. If an elevator car is full, then cancel the remaining scheduled downhill peak floors for this car in this mission, excluding the base station floor. Do not remove these floors from the original waiting queue, and allow the corresponding floors to be given priority for new scheduling.

[0120] B. If the room is not full, continue to execute the tasks on the remaining floors.

[0121] (2) A quorum meter is installed in the waiting area on each floor. The number of people in the waiting area can be fed back to the elevator dispatch controller in real time or not. The elevator dispatch controller determines the logical processing of the task based on the number of people:

[0122] A. The elevator dispatch controller uses the passenger count system to determine whether the system has entered the downhill peak mode based on the strategy parameters set by the strategy parameter setter.

[0123] B. The elevator dispatch controller uses the passenger count system and the strategy parameters set by the strategy parameter setter to determine whether the corresponding floor should enter the peak downward mode.

[0124] C. When the elevator dispatch controller retrieves the first floor to be dispatched from the queue, it accumulates the number of people inside the car and the number of people on these floors one by one. When the number of people reaches the point where the car is full, it stops retrieving the next floor. That is, it determines the strategy parameter k (maximum number of stops per trip in the peak period), which is the first k floors in the queue that have not yet been marked as "already dispatched" (or marked as "not dispatched").

[0125] The elevator operation strategy in this embodiment of the invention satisfies the following model:

[0126] First, determine the decision variable of the model as x. r,i x r,i It is an integer variable that can take the value of 0 or 1, and the meaning of its value is as follows:

[0127]

[0128] Consider the following parameters as input parameters to the model: total number of floors I; total number of people N during peak downhill hours. all The number of passengers on the i-th floor is N. i , i = 1, 2, ..., I. N i Obtained from the passenger count system. The maximum number of elevator trips, R; the maximum number of passengers per trip, C; and the allowed time per trip, T. lim In addition, the following time parameter was obtained through experimental measurement: the total time T for the elevator doors to open and close. operat The average time for each passenger to enter the elevator is T. in The average time for each passenger to leave the elevator is T. out The travel time T of the elevator from floor i to floor j elva (i,j).

[0129] Since this is a peak downhill period elevator dispatch, without loss of generality, we assume that most passengers exit the elevator from the 1st floor, ignoring the number of passengers exiting from other floors. Therefore, the total travel time t for the r-th trip is... r The following formula can be used to calculate:

[0130]

[0131] Among them, the first item Running time from layer i to layer j. r,i x r,j The meaning of x is: only when both the i-th and j-th floors are docked simultaneously, i.e., x r,i x r,j When the value is 1, the elevator travel time T from the i-th floor to the j-th floor is... elva(i,j) is included in the total time, where 2 is excluded because there may be duplicate situations. For example, the downlink demand of the three layers 9 / 5 / 3 may result in a time of 5-9 / 3-5 / 9-1, which is exactly twice the original time. This represents the total time spent on all floors. This represents the total time for passengers on floors 2 and above to enter the elevator, where n r,i This represents the number of people entering the elevator on the i-th floor during the r-th trip. The calculation method and constraints are described below. This represents the time required for the total number of people entering the elevator on the rth trip to leave the elevator on the 1st floor.

[0132] Let's calculate n. r,i According to the elevator capacity constraint, the total number of people entering the elevator above the 2nd floor in the r-th trip cannot exceed C. Therefore, we have Furthermore, if the elevator does not stop at the i-th floor on the r-th trip, no one will get on that floor, therefore n r,i ≤C·x r,i Finally, at most R passes are required, and all N values ​​in each layer are obtained. i All passengers have been dropped off, therefore there are

[0133]

[0134] Finally, we also need to consider the signal input S of the elevator floor controller in the elevator dispatch controller provided by this invention. r,i , where i represents the i-th floor and r represents the r-th trip of the elevator. S r,i It is an integer input parameter that can take the value of 0 or 1, and its meaning is...

[0135]

[0136] Since the elevator can only stop on the i-th floor if the button signal from the passenger on the i-th floor is sent to the elevator's own control system, there is a constraint x. r,i ≤S r,i .

[0137] Finally, we must also consider minimizing the number of elevator trips. We introduce an auxiliary decision variable, y. r If the r-th elevator runs, then y r =1, otherwise y r =0. Therefore, y can be established. r With x r,i The relationship between them is as follows: Where M is a sufficiently large integer. It is worth noting that here y r The introduction of this feature is for the convenience of modeling and is not intended as a necessary technical feature of this model.

[0138] The goal of this model is to minimize the total running time and the total number of runs, therefore... Where η is a large constant, which can be considered as the fixed time cost of one elevator trip.

[0139] In summary, the elevator dispatching problem during peak downhill hours can be represented by the following mathematical model, where the decision variable x is... r,i It can be solved using conventional commercial solvers such as COPT, GUROBI, or CPLEX.

[0140]

[0141]

[0142] The specific implementation examples are as follows:

[0143] Suppose a 5-story building has an elevator travel time of (ji) × 3 seconds from floor i to floor j, where j > i. The total time for the elevator doors to open and close is 6 seconds, and the time T for each passenger to enter the elevator is... in and the time T when leaving the elevator out The values ​​are 1s and 0.6s respectively. The elevator capacity is limited to 5 people. Assume that the elevator signal for each passenger on each floor is delivered to the elevator system. First, assume that the number of people waiting for the elevator on floors 2 to 5 are 2 to 5 respectively, and choose a maximum elevator run count of 5. Substituting the values ​​into the model, the solution is obtained:

[0144]

[0145] as well as

[0146]

[0147] It can be seen that the elevator operation strategy in this embodiment of the invention is divided into three trips: (1) transporting 4 people to the 4th floor; (2) transporting 2+3=5 people to the 2nd and 3rd floors; (3) transporting 5 people to the 5th floor; the total time used is 52.4s. The time cost of each trip is as follows:

[0148] Time taken for the first trip:

[0149] It takes 9 minutes to go from the 1st floor to the 4th floor (one door opening and closing);

[0150] It takes 9 minutes to go from the 4th floor to the 1st floor (one door opening and closing);

[0151] In addition, the time for opening and closing the door and for passengers to enter and exit is 6*2 + 1.6*4 = 18.4;

[0152] Therefore, the total duration is 18 + 18.4 = 36.4 seconds.

[0153] Time taken for the second trip:

[0154] It takes 6 minutes to go from the 1st floor to the 3rd floor (one door opening and closing);

[0155] The time taken to go from the 3rd floor to the 2nd floor is 3 (one door opening and closing);

[0156] It takes 3 minutes to go from the 2nd floor to the 1st floor (one door opening and closing);

[0157] The round trip takes a total of 6 + 3 + 3 = 12 hours.

[0158] In addition, the time for opening and closing the door and for passengers to enter and exit is 6*3+1.6*5=26;

[0159] Therefore, the total is 12 + 26 = 38 seconds.

[0160] Time taken for the third trip:

[0161] It takes 12 minutes to go from the 1st floor to the 5th floor (one door opening and closing);

[0162] It takes 12 minutes to go from the 5th floor to the 1st floor (one door opening and closing);

[0163] In addition, the time for opening and closing the door and for passengers to enter and exit is 6*2+1.6*5=20;

[0164] Therefore, the total duration is 44 seconds.

[0165] The total time is 36.4 + 38 + 44 = 118.4 seconds.

[0166] If the method of the present invention is not adopted, and only the elevator capacity is considered, the following transportation strategies will occur: (1) transport 5 people on the 5th floor; (2) transport 4 people on the 4th floor + 1 person on the 3rd floor; (3) transport 3-1 = 2 people on the 3rd floor and 2 people on the 2nd floor.

[0167] Time taken for the first trip:

[0168] It takes 12 minutes to go from the 1st floor to the 5th floor (one door opening and closing);

[0169] It takes 12 minutes to go from the 5th floor to the 1st floor (one door opening and closing);

[0170] In addition, the time for opening and closing the door and for passengers to enter and exit is 6*2+1.6*5=20;

[0171] Therefore, the total duration is 44 seconds.

[0172] Time taken for the second trip:

[0173] It takes 9 minutes to go from the 1st floor to the 4th floor (one door opening and closing);

[0174] It takes 3 minutes to go from the 4th floor to the 3rd floor (one door opening and closing);

[0175] It takes 6 minutes to go from the 3rd floor to the 1st floor (one door opening and closing);

[0176] The round trip took a total of 18 minutes.

[0177] In addition, the time for opening and closing the door and for passengers to enter and exit is 6*3+1.6*5=26;

[0178] Therefore, the total duration is 44 seconds.

[0179] Time taken for the third trip:

[0180] It takes 6 minutes to go from the 1st floor to the 3rd floor (one door opening and closing);

[0181] The time taken to go from the 3rd floor to the 2nd floor is 3 (one door opening and closing);

[0182] It takes 3 minutes to go from the 2nd floor to the 1st floor (one door opening and closing);

[0183] The round trip took a total of 12 minutes.

[0184] In addition, the time for opening and closing the door and for passengers to enter and exit is 6*3+1.6*4=24.4;

[0185] Therefore, the total duration is 36.4 seconds;

[0186] The total time is 36.4 + 44 + 44 = 124.4 seconds.

[0187] The total running time of the scheduling method in this embodiment of the invention is less than that of the elevator operation strategy that only considers elevator capacity, because the scheduling method in this embodiment of the invention saves the elevator one unnecessary stop.

[0188] This invention addresses the characteristics of peak downhill periods, such as office building commuting hours and residential building commuting hours, where there are many people going downhill and few people visiting each other within the building or going uphill. It schedules designated elevators specifically for downhill service and minimizes intermediate stops while ensuring the elevator car reaches the base station floor as fully as possible on each downhill trip, thus maximizing the elevator's downhill capacity and solving the problem of long waiting times for downhill passengers. It also includes preventative measures against improper operations that could exacerbate elevator capacity strain during peak downhill periods.

[0189] The basic logic of the elevator operation task allocation method in this embodiment of the invention is as follows:

[0190] Multiple downhill peak periods, peak periods for each floor, the destination floor (base station floor) of the elevator during the downhill peak period can be set, and the maximum number of floors k for each trip of the peak elevator can be set according to the estimated number of floors the elevator will stop at before the car is fully loaded during the downhill peak period. In some embodiments, the maximum number of floors k for each trip of the peak elevator can be set according to the estimated number of floors the elevator will stop at before the car is fully loaded based on the detection results of the passenger count system. During peak downward travel times, the elevator dispatch controller allocates capacity, prioritizing all or most of the elevator cars to meet the demand for downward travel. Based on the passenger count system or strategy parameters set by the strategy parameter setter, the elevator dispatch controller determines whether the system has entered peak downward travel mode. If so, the external call controller disconnects the button switches on the external call buttons from the elevator control panel, and the elevator floor controller disconnects the button switches on the floor selection buttons inside the car from the elevator control panel. This prevents the elevator from responding to passenger calls, and allocates all designated cars for peak downward travel. Simultaneously, while ensuring that each downward trip reaches the base floor as fully as possible, intermediate stops are minimized to fully utilize the elevator's downward travel capacity, thereby solving the problem of long waiting times for downward travel. The specific logic is as follows:

[0191] 1. The elevator dispatch controller determines whether each floor is currently in the downhill peak mode based on the strategy parameters set by the passenger counting system and / or the strategy parameter setter. It can also determine whether a floor is in the downhill peak mode when the downhill call button is pressed. If so, the floor is placed in the dispatch queue. Before placing the floor, the controller checks whether the floor is already in the dispatch queue. If it is, no processing is required. If not, the floor is placed at the end of the dispatch queue, thus ensuring that each floor is placed in the dispatch queue in order.

[0192] 2. The elevator dispatch controller uses elevator status detectors to detect whether each peak-hour car (a car specifically used for downward peak dispatch) has completed a transport task. (If the elevator status detector detects that the running status of the corresponding car has changed from running to timeout-stationary (timeout-stationary means that the elevator has not run for more than the predetermined time), or if the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and opened the door, it is determined that a task has been completed.)

[0193] 3. After receiving the signal, the elevator dispatch controller takes the first k floors that have not yet been marked as "already dispatched" (or marked as "not dispatched") from the queue of waiting dispatch, based on the maximum number of stops k for each trip of the peak car. These k floors are assigned to the car as the task of stopping and picking up passengers for the next trip (Task 1). From these k floors, the highest dispatch floor f is taken out, and an instruction signal is sent to the corresponding elevator floor controller to register floor f. At the same time, the elevator dispatch controller marks these k floors as "already dispatched". k can be set by the strategy parameter setter or inferred from the passenger count system. The order of the first k floors taken out is consistent with their order in the queue of waiting dispatch.

[0194] 4. Upon receiving the instruction signal, the elevator floor controller simulates the signal sent by a person pressing the corresponding button and sends a signal that floor f has been pressed to the elevator control panel of the elevator system. This causes the indicator light of the internal call button (floor selection button) on floor f to light up, thereby notifying the elevator control system to control the elevator car to move to floor f.

[0195] 5. The elevator dispatch controller detects the status of the car by checking its status. If the car stops after a timeout or changes direction while traveling upwards to the top floor, and the top floor reached is floor f, then the controller sends the command signals for registering the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor reached is not floor f, then the controller sends the command signals for registering the k floors and the destination floor (base station floor) set by the previous strategy parameter setter to the elevator floor controller. When the elevator dispatch controller detects that the designated car has traveled downwards to floor f through the elevator status detector, it sends the command signals for registering the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller.

[0196] 6. Upon receiving the instruction signal, the elevator floor controller sends a signal indicating that the floor has been pressed to the elevator system's own button panel based on the received floor simulation user's button press. This illuminates the indicator light on the corresponding floor's internal call button, notifying the elevator's own control system to move the elevator car to that floor. Since the external call button signals are all blocked, the elevator will only stop at these k floors during its descent to reach full car capacity before directly reaching the base station floor. This maximizes the elevator's carrying capacity (full load for each trip) and speeds up the elevator's turnaround time (directly reaching the base station floor after full load without stopping at other floors), thus maximizing the elevator's transportation efficiency.

[0197] 7. The elevator dispatch controller continues to monitor the car status through the elevator status detector. Once the car stops and opens the door, it is considered that the floor has been stopped and the corresponding floor is removed from the dispatch queue. If a new stopping request is detected for that floor later, it will be put back into the dispatch queue (possibly at the end) for new dispatch.

[0198] 8. When the elevator dispatch controller detects that the elevator car has arrived at the base station floor and the door has opened through the elevator status detector, it means that the current trip is completed. The elevator dispatch controller can then take a new batch of the first k floors that have not yet been marked as "already in dispatch" (or marked as "not in dispatch") from the queue to perform a new round of task execution.

[0199] like Figure 1 As shown, this embodiment of the invention provides an elevator capacity allocation method, including the following steps:

[0200] S1: Receive user input and set elevator operation strategy parameters through the strategy parameter setter. The strategy parameters are then downloaded to the elevator dispatch controller.

[0201] Specifically, the elevator operation strategy parameters include: base station floor, the time period during which the system enters the down-peak mode, the time period during which each floor is determined to be a down-peak floor, the maximum number of stops per trip for each car during the down-peak period (set according to how many floors the car is expected to stop at before it is fully loaded), which cars are dedicated to down-peak scheduling, the number of people in the waiting hall that corresponds to the floor being determined to be a down-peak floor, the minimum number of floors in the waiting hall that meet the down-peak standard when the system automatically enters the down-peak mode, and the maximum passenger capacity of the car.

[0202] S2: The elevator dispatch controller detects whether it has entered the down-peak mode. If so, the external call controller disconnects the button switch on the external call button from the elevator button panel, and the elevator floor controller disconnects the button switch on the floor selection button inside the car from the elevator button panel, so that the elevator does not respond to the passenger's internal and external call calls, and the designated cars are all used for down-peak transportation.

[0203] Specifically, the elevator dispatch controller determines the time period during which the system enters the downhill peak mode by setting the time through the strategy parameter setter.

[0204] Specifically, the system uses a headcount system to detect the number of people in the elevator lobby and the number of floors that meet the peak downhill criteria to determine whether the system has entered the peak downhill mode.

[0205] S3: The elevator dispatch controller determines which floors are currently experiencing peak downhill hours based on the elevator operation strategy corresponding to the strategy parameters.

[0206] Specifically, the strategy parameters determine which floors are currently experiencing peak downhill traffic.

[0207] Specifically, the system determines which floors are currently experiencing peak downhill traffic based on the number of people in the waiting area detected by the headcount system or by setting strategy parameters.

[0208] S4: The elevator dispatch controller dispatches the elevator cars to determine the planned down-peak floors according to the elevator operation strategy corresponding to the strategy parameters. It then dispatches each car used for down-peak transportation in turn to stop at the floors. Once the car meets the specified conditions, it goes directly to the base station floor, reducing intermediate stops and improving the efficiency of the elevator's down-peak transportation. In this embodiment, the specified conditions refer to the set full-load conditions. In some embodiments, down-peak floors that have already been stopped are placed at the end of the dispatch queue and stopped again after dispatch, so that people on high, middle and low floors have the opportunity to take the elevator. Once the specified conditions are met, the car goes directly to the base station floor.

[0209] Specifically, based on which floors are currently experiencing peak downhill hours and whether the call buttons for the corresponding peak downhill floors have been pressed, the elevator dispatch controller determines which floors require stopping service and sorts these floors accordingly.

[0210] Furthermore, if the elevator dispatch controller determines that one or more floors are currently the floors requiring service, it will place these floors into the dispatch queue in order. Simultaneously, the outbound call controller will output a signal to the outbound call button indicator light, illuminating the indicator light. Alternatively, the elevator dispatch controller will send a command signal to the outbound call controller of the corresponding floor, illuminating the downbound outbound call button indicator light. The method for placing the floors into the dispatch queue in order is as follows: either based on the time sequence in which the floor is detected as a peak downbound floor and is not yet in the dispatch queue, or based on the time sequence in which the floor is detected as a peak downbound floor, the outbound call controller detects a downbound outbound call button being pressed, and the floor is not yet in the dispatch queue.

[0211] The elevator status detector detects whether the elevator car used for peak-hour downward transport has completed a certain task. If a car has completed its task, it is dispatched to the planned peak-hour downward floor to transport passengers according to the elevator operation strategy corresponding to the strategy parameters. The strategy includes: determining the planned floor to stop at by stopping at a certain number of floors before the car is fully loaded; and driving directly to the base station floor after the car meets the full-load condition. The detection of how many floors the car will stop at before it is fully loaded includes: 1. the value set by the strategy parameters; 2. calculated based on the passenger count system.

[0212] Furthermore, if the elevator status detector detects that the operating status of the corresponding car has changed from running to timed-out stationary, or if the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and the door has opened, then it is determined that a certain task has been completed.

[0213] Specifically, if the outbound call controller detects that the outbound call button for the peak downbound floor is pressed during the downbound peak period, or that the outbound / downbound call button for the off-peak floor is pressed, the elevator dispatch controller will dispatch a car designated for use outside of the downbound peak dispatch to respond to the elevator request.

[0214] Step S3 in this embodiment of the invention includes: if the current mode is a downlink peak, the downlink peak floors are placed into the scheduling queue in order.

[0215] Specifically, if the outbound call controller detects that a downbound outbound call button has been pressed, it sends the outbound call request to the elevator dispatch controller for processing. The elevator dispatch controller determines that the downbound outbound call button for a peak downbound floor has been pressed, and then places the downbound outbound calls into the dispatch queue in the order they were received. The outbound call controller itself outputs a signal to the outbound call button indicator light to illuminate the outbound call button indicator light; or the elevator dispatch controller sends a command signal to the outbound call controller on the corresponding floor to illuminate its corresponding outbound call button indicator light.

[0216] Step S4 in this embodiment of the invention includes:

[0217] S41: If the elevator dispatch controller detects through the elevator status detector that a car has completed the previous trip, it will take the first k floors that have not yet been marked as "already in dispatch" (or marked as "not in dispatch") from the queue to be dispatched, and mark these floors as "already in dispatch".

[0218] The markings here are explained as follows:

[0219] In this embodiment, the markers include "already in scheduling / not in scheduling", where "already in scheduling" indicates that there is a need to stop on the floor and a car has been assigned to perform the stopping service; "not in scheduling" indicates that there is a need to stop on the floor, but the car is still waiting to be assigned. Once a peak service car becomes available for the downhill period, the scheduler will select the first k floors from these "not in scheduling" floors for scheduling.

[0220] Specifically, k is specified according to strategy parameters, or is set based on the number of floors the elevator car will be fully loaded based on the detection results of the passenger count system.

[0221] S42: The elevator dispatch controller takes the highest dispatch floor f from these k floors and sends a registration floor f instruction signal to the elevator floor controller of the corresponding car. After receiving the instruction signal, the elevator floor controller simulates the signal triggered by the corresponding button being pressed, causing the car to go to the corresponding floor.

[0222] S43: When the elevator dispatch controller detects through the elevator status detector that the designated car has stopped after a timeout or changed direction while traveling upwards to the top floor, if the top floor reached is floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor reached is not floor f, it sends instruction signals for the k floors and the base station floor to the corresponding elevator floor controller. When the elevator dispatch controller detects through the elevator status detector that the designated car has traveled downwards to floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. After receiving the instruction signals, the elevator floor controller simulates the signal triggered by pressing the corresponding button, causing the car to travel to the corresponding floor.

[0223] Specifically, during the downhill process, if the passenger count system detects that the car is full in advance, it will remove the downhill peak floors that are scheduled to stop outside the base station floor but have not yet stopped. At the same time, the positions of the canceled floors in the original waiting queue will be retained, and the "already in scheduling" mark will be removed or the mark will be changed to "not in scheduling", so that other cars can stop at these floors first after completing their tasks.

[0224] S44: When the elevator dispatch controller detects that the door of a designated car is open on a floor out of k floors through the elevator status detector, it considers that the car has stopped at that floor once. The elevator dispatch controller sends a command signal to the call controller of the corresponding floor, outputs a signal to the down call button indicator light, and turns off the down call button indicator light. The floor is then removed from the dispatch queue. The floor is then checked to see if it is still a down peak floor. If it is still a down peak floor and the call controller detects that a down call button has been pressed, the floor is added to the dispatch queue and the next round of dispatching begins.

[0225] The elevator operation strategy in this embodiment of the invention conforms to the following model:

[0226]

[0227]

[0228] Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip, η be the fixed time cost of one trip of the elevator, and y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i i = 1, 2, ..., I, T operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator.out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the travel time of the elevator from floor i to floor j.

[0229] The model constraints in this embodiment of the invention include:

[0230]

[0231] Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i Let i = 1, 2, ..., I, C be the maximum number of passengers per trip, and T be the maximum number of passengers per trip. operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, S r,i It is an integer input parameter that can take the value of 0 or 1, and its meaning is...

[0232]

[0233] In other embodiments, the elevator status detector can also be connected to the elevator dispatch controller to directly send the car status to the elevator dispatch controller for processing.

[0234] Example 1:

[0235] The outbound call controller in Example 1 has no detection function and no caller count function.

[0236] The working principle of the elevator capacity distribution system in Embodiment 1 of the present invention is as follows:

[0237] The elevator dispatch controller determines whether it is a peak downhill period and which floors are in the peak downhill period based on the strategy parameter setter. If a floor is in the peak downhill period, it determines whether it has been added to the dispatch queue. If it is already in the dispatch queue, it will not be added again. If it is not in the dispatch queue, it will be added. Then, the elevator car is allocated according to the dispatch queue, and the task allocation is completed.

[0238] Detailed explanation is as follows:

[0239] 1. Users can configure elevator operation strategies through the strategy parameter setter, such as which time periods to enter the downhill peak mode, which floors are the downhill peak floors during which time periods, how many floors the car typically stops at before reaching full capacity during downhill peak hours, the base station floor (F), and which cars are dedicated to downhill peak scheduling. This information is routinely set through the strategy parameter setter, and this setting can be changed at any time according to human management requirements. The strategy parameters will be downloaded to the elevator dispatch controller.

[0240] 2. When the elevator dispatch controller detects that it is currently in a downhill peak period, the external call controller will cut off external calls: The external call controller uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches and indicator lights on the original external call buttons from the elevator control panel; the elevator floor controller also uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches on the original floor selection buttons inside the elevator car from the elevator control panel. This prevents button signals from being directly sent to the elevator's own control system, thus preventing the elevator from responding to passengers' internal or external calls. Simultaneously, the indicator light on / off signals sent by the elevator's own control system will also prevent the indicator lights on the buttons from lighting up / off. These cut-off signals prevent users from calling the elevator via the external call buttons.

[0241] 3. The elevator dispatch controller automatically detects and determines which floors are currently in the down-peak period based on the information set by the strategy parameter setter, and checks whether these down-peak floors have been added to the dispatch queue. If they have not been added, they are added to the end of the dispatch queue and marked as "not in dispatch".

[0242] 4. When the elevator dispatch controller detects that a car has completed a trip (the elevator status detector detects that the corresponding car's running status changes from running to timeout and stationary, or the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and opened the door, it determines that a trip has been completed), it will take out the first k floors in the dispatch queue that have not yet been marked as "already dispatched" (or marked as "not dispatched"). These k floors are the planned downhill peak floors for the current car trip. These floors will be marked as "already dispatched". Other cars will not take these floors when taking a trip. After taking out the floors, the elevator dispatch controller first takes out the highest dispatch floor f from these k floors and sends a signal to the corresponding car elevator floor controller to register the highest dispatch floor f. After receiving the signal, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by the corresponding button press according to the specified floor, prompting the car to go to the corresponding floor.

[0243] 5. When the elevator dispatch controller detects through the elevator status detector that the designated car has reached the top floor and stopped after a timeout or changed direction, if the top floor is floor f, it sends instruction signals for registering the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor is not floor f, it sends instruction signals for registering k floors and the base station floor to the corresponding elevator floor controller. When the elevator dispatch controller detects through the elevator status detector that the designated car has reached the bottom floor, it sends instruction signals for registering the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. After receiving the signals, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by pressing the corresponding button according to the designated floor, registers the corresponding floor inside the car, illuminates the floor call button indicator, and prompts the car to move to the designated floor. It also registers the base station floor; the basic public floor is defined as the base station floor, such as the 1st floor.

[0244] 6. During operation, the elevator dispatch controller detects whether the car door is open via the elevator status detector. If the car door is open, it checks whether the floor the car is on is the floor in the car's assigned task. If so, it means the car has completed its task and stopped at the corresponding floor, allowing passengers to enter. The system clears the information for that floor from the dispatch queue and controls the down call button indicator light for that floor to turn off via the outbound call controller. The elevator dispatch controller also checks whether the floor is still a peak downbound floor at the current time. If so, it checks whether these peak downbound floors have been added to the dispatch queue. If not, it adds the floor to the end of the dispatch queue and marks it as "not in dispatch".

[0245] 7. When the elevator dispatch controller detects that the car has stopped at the base station floor and the door has opened via the elevator status detector, it indicates that the current trip is complete, and the car can be reassigned to a new task according to step 4. At the same time, if the elevator dispatch controller finds that there are still floors in the task that have not been stopped, the elevator dispatch controller retains the original order of these floors in the waiting queue, but deletes their "already dispatched" mark or changes the mark to "not dispatched", so that these tasks can be preferentially assigned to the next available car for response.

[0246] The flowchart of the elevator capacity allocation system operation task allocation in Embodiment 1 of the present invention is as follows: Figure 3 As shown, the specific task allocation is as follows: The elevator dispatch controller obtains relevant setting information such as the downhill peak period from the strategy parameter setter; based on the strategy parameters, it checks whether each floor has entered the downhill peak mode; if so, it checks whether the floor exists in the dispatch queue; if not, it places the floor at the end of the dispatch queue and marks it as "not in dispatch". Specifically, this includes the following steps:

[0247] SA1: The elevator dispatch controller determines whether the system has entered the down-peak mode and which floors are the down-peak floors based on the set strategy parameters.

[0248] SA2: Check if there is a corresponding floor in the queue to be dispatched. If not, place it at the end of the queue to be dispatched, mark it as "not in dispatch", and light up the downlink outbound call button indicator.

[0249] SA3: Check if there are any peak-hour cars (cars specifically for descending peak floors) available for dispatch. If yes, proceed to step SA4; otherwise, proceed to step SA7.

[0250] SA4: Take the first k floors that have not yet been marked as "already in scheduling" (or marked as "not in scheduling") from the queue to be scheduled, mark these k floors as "already in scheduling", k is set by the strategy setter according to how many floors the car usually stops at when it is full load in actual situation, take out the highest scheduling floor f among these k floors and register it.

[0251] SA5: Detected that the designated car has stopped after timeout while traveling to the top floor or has changed direction of travel;

[0252] SA6: If the highest floor reached is floor f, then register the other k-1 floors besides floor f and the base station floor. If the highest floor reached is not floor f, then register k floors and the base station floor. If the elevator dispatch controller detects that the designated car has descended to floor f, then register the other k-1 floors besides floor f and the base station floor; prompt the car to go to the corresponding floor.

[0253] SA7: Detects if there is a peak-hour car stop or door opening. If so, it determines whether the stopping floor is one of the k floors in the car's dispatch task. If the stopping floor is one of the floors in the car's dispatch task, the corresponding floor is removed from the waiting queue, and the corresponding downlink outbound call button indicator light is turned off. If the stopping floor is not one of the floors in the task, it determines whether it is a base station floor. If it is a base station floor, the task is completed, and the car is marked as "awaiting dispatch" for the next round of dispatch. If it is not a base station floor, it continues to wait for door opening detection for re-determination. If the car has reached a base station floor but there are still floors in the dispatch task that have not been stopped, the "already dispatched" mark of these floors in the waiting queue is removed, or the mark is changed to "not dispatched". The position of these floors in the original waiting queue is not cleared, allowing the corresponding floors to receive new dispatch first.

[0254] The structural diagram of the elevator control system of Embodiment 1 of the present invention is as follows: Figure 2As shown, in this embodiment, the elevator control panel includes a floor selection control panel and an external call control panel. Elevator cars one through N, along with the floor selection control panels and buttons respectively installed therein, constitute an elevator self-controlled system. The elevator self-controlled system also includes an external call control panel and buttons. Assuming the building has M floors and N elevators, the strategy parameter setter is connected to the elevator dispatch controller. The elevator dispatch controller is connected to the first elevator floor controller through the Nth elevator floor controller. The first elevator floor controller is connected to the first elevator status detector and is also connected to the floor selection control panel and buttons in elevator car one. The Nth elevator floor controller is connected to the Nth elevator status detector and is also connected to the floor selection control panel and buttons in elevator car N. The elevator floor controller connects the floor selection buttons and the floor selection control panel, selectively connecting or disconnecting the button switches on the elevator car floor selection buttons from the floor selection control panel.

[0255] Each floor has an elevator lobby, which contains an external call controller and connected external call button panels and buttons. For example, the first-floor lobby has a first-floor external call controller, external call button panel, and external call buttons; the second-floor lobby has a second-floor external call controller, external call button panel, and external call buttons; and the M-floor lobby has an M-floor external call controller, external call button panel, and external call buttons. The first-floor external call controller is connected to the first-floor external call button panel and buttons, the second-floor external call controller is connected to the second-floor external call button panel and buttons, and the M-floor external call controller is connected to the M-floor external call button panel and buttons. The external call controller connects to both the external call buttons and the external call button panel, allowing for selective connection or disconnection of the button switches on the elevator car's external call buttons to the external call button panel.

[0256] The elevator dispatch controller is also connected to the outbound call controller on the first floor, the outbound call controller on the second floor, and the outbound call controller on the M floor. In this embodiment, the outbound call controller only outputs signals to the outbound call button and does not receive outbound call signals from the outbound call button.

[0257] In one embodiment, an elevator scheduling method for an elevator capacity allocation system that lacks detection and passenger counting functions in its outbound call controller is exemplified below:

[0258] Time 1:

[0259] During the downhill peak period (18:00-19:00), the following queue of cars is obtained based on the set strategy parameters: [37, 32, 26, 17, 10]. The queue of cars to be scheduled is shown in Table 1a below. The maximum number of stops per car during peak hours is set to 2. Cars A and B are dedicated to downhill peak scheduling. The following shows the operating status of cars A and B at different times and under different conditions:

[0260] Table 1a

[0261] order Downward Peak Floor state 1 37 Not in scheduling 2 32 Not in scheduling 3 26 Not in scheduling 4 17 Not in scheduling 5 10 Not in scheduling

[0262] Time 2:

[0263] The queue to be scheduled is shown in Table 1b below. At this time, there is one idle car, which is car A. The current status of each car is as follows: Car A is on the base station floor, and car B is executing a previous task. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 32].

[0264] It should be noted that the elevator floor controllers of cars A and B receive and register the highest dispatch floor f1 / f2 among the k1 / k2 dispatch floors issued by the elevator dispatch controller. After the elevator dispatch controller detects that the designated car has timed out or changed direction after reaching the highest floor through the elevator status detector, if the highest floor reached is f1 / f2, it will send the instruction signals for registering the other k1-1 / k2-1 floors and the base station floor to the corresponding elevator floor controller. If the highest floor reached is not f1 / f2, it will send the instruction signals for registering the k1 / k2 floors and the base station floor to the corresponding elevator floor controller. If the elevator dispatch controller detects that the designated car has reached the f1 / f2 floor after descending through the elevator status detector, it will send the instruction signals for registering the other k1-1 / k2-1 floors and the base station floor to the corresponding elevator floor controller.

[0265] Each elevator floor controller registers the k / k-1 dispatch floors issued by the elevator dispatch controller simultaneously, without any order.

[0266] Where k1 and k2 correspond to the maximum number of stops per trip for each car during peak hours in Task 1 and Task 2, respectively. In this embodiment, k1 = k2 = k, and the value of k is set by the strategy parameter setter.

[0267] Furthermore, the dispatch floors k1 and k2 are elevator floor controllers registered to car A and car B respectively, where the floors in dispatch floors k1 include [37, 32], and are registered to the elevator floor controller of car A.

[0268] The elevator floor controller of car A receives and registers the highest dispatch floor 37 in the dispatch floor [37, 32] sent by the elevator dispatch controller. If the highest floor reached is not 37, the elevator floor controller of car A receives and registers both dispatch floors [37, 32] and the base station floor sent by the elevator dispatch controller. If the highest floor reached is 37, the dispatch floor 32 and the base station floor will be registered at the same time.

[0269] Table 1b

[0270] order Downward Peak Floor state Assigning cars 1 37 Already in the process of scheduling Car A 2 32 Already in the process of scheduling Car A 3 26 Not in scheduling 4 17 Not in scheduling 5 10 Not in scheduling

[0271] Time 3:

[0272] The queue to be scheduled is shown in 1c below. At this time, there is one idle car, car B. The current status of each car is as follows: Car A has stopped at the 37th floor (the 37th floor is still the peak downhill floor at this time after stopping) and is going down to the 32nd floor. Car B is at the base station floor. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 32], Task 2: Car B is assigned task [26, 17].

[0273] Table 1c

[0274] order Downward Peak Floor state Assigning cars 2 32 Already in the process of scheduling Car A 3 26 Already in the process of scheduling Car B 4 17 Already in the process of scheduling Car B 5 10 Not in scheduling 6 37 Not in scheduling

[0275] Time 4:

[0276] The queue to be scheduled is shown in Table 1d below. There are no idle cars at this time. The current status of each car is as follows: Car A has stopped on the 32nd floor (the 32nd floor is still the peak downhill floor at this time after stopping), and is in the process of going downhill from the 32nd floor to the base station floor; Car B is in the process of preparing to go to the 26th floor; The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 32], Task 2: Car B executes task [26, 17].

[0277] Table 1d

[0278] order Downward Peak Floor state Assigning cars 3 26 Already in the process of scheduling Car B 4 17 Already in the process of scheduling Car B 5 10 Not in scheduling 6 37 Not in scheduling 7 32 Not in scheduling

[0279] Time 5:

[0280] The queue to be scheduled is shown in Table 1e below. At this time, there is one idle car, car A. The current status of each car is as follows: Car A has completed all floors in the task and is at the base station floor. Car B has stopped at the 26th floor (after car B stops, the 26th floor is still the downhill peak floor in the current time period) and is preparing to go to the 17th floor for downhill. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 10], Task 2: Car B executes task [26, 17].

[0281] Table 1e

[0282] order Downward Peak Floor state Assigning cars 4 17 Already in the process of scheduling Car B 5 10 Already in the process of scheduling Car A 6 37 Already in the process of scheduling Car A 7 32 Not in scheduling 8 26 Not in scheduling

[0283] Time 6:

[0284] The queue to be scheduled is shown in Table 1f. At this time, car B has completed its stop at the 17th floor (after car B stops, the 26th floor is still a peak downhill floor in the current time period) and has arrived at the base station and stopped. There is one idle car at this time, which is car B. The current status of each car: Car A is on its way to the 37th floor. Car B has completed its stops at all floors in the task and is at the base station floor, so the scheduler reassigns the task to B. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 10], Task 2: Car B executes task [32, 26].

[0285] Table 1f

[0286] order Downward Peak Floor state Assigning cars 5 10 Already in the process of scheduling Car A 6 37 Already in the process of scheduling Car A 7 32 Already in the process of scheduling Car B 8 26 Already in the process of scheduling Car B 9 17 Not in scheduling

[0287] The advantages of Example 1 are as follows:

[0288] 1. Because the external call button is controlled, it prevents people on lower floors from entering the elevator in the opposite direction, thus avoiding situations where people on lower floors enter the elevator car in advance, preventing them from entering the elevator on higher floors and causing them to be unable to use the elevator for extended periods. This solves the problem of difficulty in using elevators on higher floors.

[0289] 2. Automatic Operation: The elevator dispatch controller automatically dispatches all elevators to participate in the operation during the downhill peak period according to the elevator operation strategy corresponding to the strategy parameters, thereby increasing the carrying capacity. The strategy parameters include the downhill peak period and the queue to be dispatched.

[0290] 3. Because the call button is controlled, the elevator only stops at a specified number of floors per trip. Once the number is reached, it goes directly to the base station floor, reducing intermediate stops, speeding up elevator turnover, and increasing capacity.

[0291] 4. Due to the control of internal calls, during peak downward periods, elevators can only go to the base station floor to prevent passengers in the car from pressing other floor buttons, which would cause unnecessary frequent stops, shorten the elevator's downward time, and improve the elevator's transportation speed.

[0292] 5. Each car will take turns going to the corresponding floor in sequence. If the number of floors is set reasonably, there will be no problem of a certain floor not being served for a long time during the peak downward flow.

[0293] 6. Once each car completes a task, it is immediately and automatically assigned to the next task, without stopping empty, thus making full use of the elevator's capacity.

[0294] 7. Configurable Strategy Parameters: The system can freely configure the time period and floor level for entering the downlink peak mode. The system will automatically execute tasks based on the strategy parameters, achieving flexible configuration during peak periods, adaptively improving capacity, and solving the problem of difficult passage during downlink peak periods.

[0295] 8. For buildings where elevators have already been installed and for elevators with their own control systems that cannot be upgraded, retrofitting can be carried out to achieve peak capacity transformation.

[0296] 9. It can be installed in any elevator, which is more cost-effective than upgrading the elevator's own system. Since it does not involve major modifications to the elevator's own control system, it will not cause problems or hidden dangers to the elevator's own control system due to major modifications. It also saves on the approval process by eliminating the need for elevator inspection.

[0297] 10. Supports emergency disconnection. In an emergency, the entire system can be completely disconnected from the elevator's own control system by inputting a fire signal or other emergency signal, restoring the elevator's own control system to operation without causing any safety hazards.

[0298] Example 2:

[0299] The outbound call controller in Example 2 has detection function and no-caller-count function.

[0300] The working principle of the elevator capacity distribution system in Embodiment 2 of the present invention is as follows:

[0301] The elevator dispatch controller determines whether it is currently a downhill peak period and which floors are experiencing downhill peaks based on the strategy parameter setter. It then determines whether the outbound call request is for the downhill direction. If not, the elevator car is dispatched to respond to the request, excluding those designated for downhill peak scheduling, and task allocation is complete. If the call is for a downhill signal, it determines whether the floor is within the downhill peak period. If not, it dispatches an elevator car not designated for downhill peak scheduling, and task allocation is complete. If the floor is within the downhill peak period, it checks if the elevator has already been added to the dispatch queue. If already in the queue, it is not added again; if not, it is added. Finally, elevator cars are allocated according to the queue, and task allocation is complete.

[0302] Detailed explanation is as follows:

[0303] 1. Users can configure policy parameters through the policy parameter setter, such as which time periods to enter the downhill peak mode, which floors are in different downhill peak periods, how many floors the elevator car typically stops at before reaching full capacity during downhill peak periods, the base station floor (F), and which cars are dedicated to downhill peak scheduling. This information is routinely set through the policy parameter setter, and can be changed at any time according to human management requirements. The policy parameters will be downloaded to the elevator dispatch controller.

[0304] 2. When the elevator dispatch controller detects that it is currently in a downhill peak period, the outbound call controller will cut off outbound calls: The outbound call controller uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches and indicator lights on the original elevator outbound call buttons from the elevator button panel; the elevator floor controller also uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches on the original floor selection buttons inside the elevator car from the elevator button panel. This prevents button signals from being directly sent to the elevator's own control system, thus preventing the elevator from responding to passengers' outbound or inbound calls. Simultaneously, the button indicator light on / off signals sent by the elevator's own control system cannot ignite / extinguish the button indicator lights. These cut-off signals are detected, processed, and received by the outbound call controller in this embodiment, and then uniformly allocated by the dispatch controller.

[0305] 3. The elevator dispatch controller automatically detects and determines which floors are currently in the downhill peak according to the information set by the strategy parameter setter. In this embodiment, the determination of which floors are currently in the downhill peak is based on the strategy parameter set information.

[0306] 4. When a user needs to take the elevator downhill, they press the downhill call button. The call controller detects this press. Due to the controller's control mechanism, there is no signal connection between the call button and the elevator's own control system. The button press signal is only detected by the call controller and sent to the elevator dispatch controller for processing. The call controller itself outputs a signal to the call button indicator light, illuminating it. Alternatively, the elevator dispatch controller sends a command signal to the call controller on the corresponding floor to illuminate its corresponding call button indicator light. The elevator dispatch controller checks if the pressed button belongs to a downhill floor during peak hours. If not, the elevator car designated for peak downhill dispatch will serve the user. If it does, the controller checks if the floor is already in the dispatch queue. If not, the floor is moved to the end of the queue and marked "Not in Dispatch".

[0307] 5. When the elevator dispatch controller detects that a car has completed a trip (the elevator status detector detects that the corresponding car's running status changes from running to timeout and stationary, or the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and opened the door, it is determined that a trip has been completed), it will take the first k floors that are not marked as "already in dispatch" (or marked as "not in dispatch") from the queue to be dispatched. These k floors are the floors that the car is scheduled to stop at in this trip. These floors will be marked as "already in dispatch". Other cars will not take these floors when taking a trip. After taking these floor numbers, the elevator dispatch controller first takes the highest dispatch floor f from these k floors and sends a signal to the elevator floor controller to register the highest dispatch floor f. After receiving the signal, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by the corresponding button being pressed according to the specified floor, so that the car goes to the corresponding floor.

[0308] 6. When the elevator dispatch controller detects that a designated car has reached the top floor and stopped within a timeout period or changed direction, if the top floor is floor f, it sends command signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor is not floor f, it sends command signals for the k floors and the base station floor to the corresponding elevator floor controller. Similarly, if the elevator dispatch controller detects that a designated car has reached floor f, it sends command signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. Upon receiving the signals, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by pressing a button, registering the corresponding floor inside the car, illuminating the internal call button indicator, and prompting the car to proceed to the designated floor. It also registers the base station floor; basic public floors are defined as base station floors, such as the first floor.

[0309] 7. During operation, the elevator dispatch controller detects whether the car door is open through the elevator status detector. If the car door is detected to be open, it checks whether the floor where the car is located is the floor in the car's task. If so, it means that the car has completed the stop at the corresponding floor in the task and allowed the passenger to enter. The system clears the information of that floor from the dispatch queue and controls the down call button indicator light of the corresponding floor to turn off through the call controller. At this time, the floor is removed from the dispatch queue. If there is a new user call request later, it will be put back into the dispatch queue according to step 4 and wait for execution.

[0310] 8. When the elevator dispatch controller detects that the car has stopped at the base station floor and the door has opened via the elevator status detector, it indicates that the current trip is complete, and the car can be reassigned to a new task according to step 5. At the same time, if the elevator dispatch controller finds that there are still floors in the task that have not been stopped, the elevator dispatch controller retains the original order of these floors in the waiting queue, but deletes their "already dispatched" mark, or changes the mark to "not dispatched", so that these tasks can be preferentially assigned to the next available car for response.

[0311] 9. Reverse calls from peak-downward floors and calls from non-peak-downward floors will be handled by dispatching designated elevator cars outside of peak-downward scheduling to respond to elevator requests and complete the elevator ride: For some people on peak-downward floors who need to reverse their journey during peak-downward periods, or for people on non-peak-downward floors who need to go down, since they represent a very small portion of the total number of passengers during peak-downward periods, they can be flexibly configured. Designated elevators in the elevator group can be arranged to shuttle up and down to solve the problem of some people on peak-downward floors needing to go up and people on non-peak-downward floors needing to go up / down during peak-downward periods. When the call button for a peak-downward call or a non-peak-downward call is pressed, the call button's connection to the elevator's internal control system is severed by the call controller via a passive dry contact. Upon receiving the call request signal, the call controller detects and receives the signal, then sends it to the elevator dispatching system for task assignment. The dispatching system assigns the task to the elevator floor controller of a car not used for peak-downward dispatch, illuminating the corresponding upward departure floor. The elevator's internal control system then directs the car not used for peak-downward dispatch to that floor. Alternatively, the call buttons and indicator lights of cars not used for peak-downward dispatch are connected to the elevator control panel and remain connected, controlled by the elevator's internal control system, dispatching the car to the corresponding floor to provide service. The call responses of this elevator and the elevator group used for peak-downward dispatch are independent and do not affect each other.

[0312] refer to Figure 4 In this embodiment, the elevator operation includes the following steps:

[0313] SB1: The elevator dispatch controller determines whether the system has entered the downhill peak mode based on the strategy parameters and determines which floors are the downhill peak floors;

[0314] SB2: Detect whether an outbound call button has been pressed. If so, determine whether the pressed button is the outbound call button for a peak downhill floor. If the pressed button is the outbound call button for a peak downhill floor, check if there is a corresponding floor in the dispatch queue. If not, put it at the end of the dispatch queue, mark it as "not in dispatch", and light up the outbound call button indicator light. If the pressed button is not the outbound call button for a peak downhill floor, dispatch a car designated for use outside of peak downhill dispatch to provide service.

[0315] SB3: Check if there are any peak-hour car vacancies available for dispatch. If yes, proceed to step SB4; otherwise, proceed to step SB7.

[0316] SB4: Take the first k floors that have not yet been marked as "already in scheduling" (or marked as "not in scheduling") from the queue to be scheduled, and mark these k floors as "already in scheduling". k is set by the strategy setter according to how many floors the car usually stops at when it is full load. Take out the highest scheduling floor f among these k floors and register it.

[0317] SB5: Detects that the designated car has timed out and stopped at the top floor or changed direction of travel;

[0318] SB6: If the highest floor reached is floor f, then register the other k-1 floors besides floor f and the base station floor; if the highest floor reached is not floor f, then register k floors and the base station floor; if the elevator dispatch controller detects that the designated car has descended to floor f, then register the other k-1 floors besides floor f and the base station floor; prompt the car to go to the corresponding floor.

[0319] SB7: Detect whether there is a peak-hour car stop or door opening. If so, determine if the stopping floor is one of the k floors in this car's dispatch task. If the stopping floor is one of the floors in this car's dispatch task, remove the corresponding floor from the waiting queue and turn off the corresponding downlink outbound call button indicator. If the stopping floor is not one of the floors in this car's dispatch task, determine if the stopping floor is a base station floor. If it is a base station floor, the current task is completed, and the car is marked as "awaiting dispatch," available for the next round of dispatch. If it is not a base station floor, continue to wait for door opening detection for further determination. If the car has reached a base station floor but there are still floors in the dispatch task that have not been stopped, remove the "already dispatching" mark from the waiting queue for these floors, or change the mark to "not dispatching," without removing these floors from the original waiting queue, allowing the corresponding floors to receive new dispatch priority.

[0320] The schematic diagram of the elevator capacity distribution system in Embodiment 2 of the present invention is shown below. Figure 2As shown, in this embodiment, the elevator button panel includes a floor selection button panel and an external call button panel. Elevator cars one through N and the internal call button panels respectively installed therein constitute the elevator's own control system. The elevator's own control system also includes an external call button panel and external call buttons. Assuming the building has M floors and N elevators, the strategy parameter setter is connected to the elevator dispatch controller. The elevator dispatch controller is connected to the first elevator floor controller through the Nth elevator floor controller. The first elevator floor controller is connected to the first elevator status detector and is also connected to the floor selection button panel and floor selection buttons in elevator car one. The Nth elevator floor controller is connected to the Nth elevator status detector and is also connected to the floor selection button panel and floor selection buttons in elevator car N. The elevator floor controller connects the floor selection buttons and the floor selection button panel respectively, and can selectively connect or disconnect the button switch on the elevator car floor selection button from the floor selection button panel.

[0321] Each floor has an elevator lobby, which contains an external call controller and connected external call button panels and buttons. For example, the first-floor lobby has a first-floor external call controller, external call button panel, and external call buttons; the second-floor lobby has a second-floor external call controller, external call button panel, and external call buttons; and the M-floor lobby has an M-floor external call controller, external call button panel, and external call buttons. The first-floor external call controller is connected to the first-floor external call button panel and buttons, the second-floor external call controller is connected to the second-floor external call button panel and buttons, and the M-floor external call controller is connected to the M-floor external call button panel and buttons. The external call controller connects to both the external call buttons and the external call button panel, allowing for selective connection or disconnection of the button switches on the elevator car's external call buttons to the external call button panel.

[0322] The elevator dispatch controller is also connected to the outbound call controller on the first floor, the outbound call controller on the second floor, and the outbound call controller on the M floor. In this embodiment, the outbound call controller is connected to the outbound call button and receives the outbound call signal from the outbound call button. The elevator floor controller detects and processes the outbound call signal.

[0323] In this embodiment, the elevator dispatching of an elevator capacity distribution system with an outbound call controller that has detection function but no passenger count function is illustrated as follows:

[0324] Time 1:

[0325] When the downhill peak period begins (17:00-18:00), the system enters the downhill peak mode. The outbound call buttons for floors 35, 29, 37, 27, 30, 34, 31, 33, and 36 are pressed sequentially. These floors are all downhill peak floors during this period. The corresponding floors for which the outbound call buttons are pressed are recorded, thus obtaining the queue to be dispatched as shown in Table 2a below. k is set to 3, and cars A, B, and C are dedicated to downhill peak dispatch.

[0326] Table 2a

[0327] Outbound call order Outbound call floors state 1 35 Not in scheduling 2 29 Not in scheduling 3 37 Not in scheduling 4 27 Not in scheduling 5 30 Not in scheduling 6 34 Not in scheduling 7 31 Not in scheduling 8 33 Not in scheduling 9 36 Not in scheduling

[0328] Time 2:

[0329] The queue to be scheduled is shown in Table 2b below. The current status of each elevator is as follows: Car A, Car B, and Car C are at the base station floor and are all idle. The task allocation is as follows: Task 1: Car A is assigned tasks [37, 35, 29]; Task 2: Car B is assigned tasks [34, 30, 27]; Task 3: Car C is assigned tasks [36, 33, 31].

[0330] It should be noted that the elevator floor controllers of cars A / B / C receive and register the highest dispatch floor f among the k1 / k2 / k3 dispatch floors issued by the elevator dispatch controller. After the elevator dispatch controller detects that the designated car has timed out or changed direction after reaching the highest floor, if the highest floor reached is floor f, it will send the instruction signals for registering the other k1-1 / k2-1 / k3-1 floors and the base station floor to the corresponding elevator floor controller. If the highest floor reached is not floor f, it will send the instruction signals for registering the k1 / k2 / k3 floors and the base station floor to the corresponding elevator floor controller. If the elevator dispatch controller detects that the designated car has reached floor f after descending through the elevator status detector, it will send the instruction signals for registering the other k1-1 / k2-1 / k3-1 floors and the base station floor to the corresponding elevator floor controller.

[0331] Each elevator floor controller registers the k / k-1 dispatch floors issued by the elevator dispatch controller simultaneously, without any order.

[0332] Where k1, k2, and k3 correspond to the maximum number of stops per trip for each car during peak hours in Task 1, Task 2, and Task 3, respectively. In this embodiment, k1 = k2 = k, and the value of k is set by the strategy parameter setter. Furthermore, the dispatched floors k1, k2, and k3 are elevator floor controllers registered to cars A, B, and C, respectively. Specifically, the floors in dispatched floor k1 include [37, 35, 29], registered to the elevator floor controller for car A; the floors in dispatched floor k2 include [34, 30, 27], registered to the elevator floor controller for car B; and the floors in dispatched floor k3 include [36, 33, 31], registered to the elevator floor controller for car C.

[0333] The elevator floor controller of car A receives and registers the highest floor 37 from the [37, 35, 29] list sent by the elevator dispatch controller. If the highest floor reached is not 37, the elevator floor controller of car A receives and registers the three dispatch floors [37, 35, 29] plus the base station floor sent by the elevator dispatch controller. If the highest floor reached is 37, the two dispatch floors [35, 29] plus the base station floor will be registered at the same time.

[0334] The elevator floor controller of car B receives and registers the highest floor 34 in the [34, 30, 27] list sent by the elevator dispatch controller. If the highest floor reached is not 34, the elevator floor controller of car B receives and registers the three dispatch floors [34, 30, 27] plus the base station floor sent by the elevator dispatch controller. If the highest floor reached is 34, the two dispatch floors [30, 27] plus the base station floor will be registered at the same time.

[0335] The elevator floor controller of car C receives and registers the highest floor 36 in the [36, 33, 31] list sent by the elevator dispatch controller. If the highest floor reached is not 36, the elevator floor controller of car B receives and registers the three dispatch floors [36, 33, 31] plus the base station floor sent by the elevator dispatch controller. If the highest floor reached is 36, the two dispatch floors [33, 31] plus the base station floor will be registered at the same time.

[0336] Table 2b

[0337] Outbound call order Outbound call floors state Assigning cars 1 35 Already in the process of scheduling Car A 2 29 Already in the process of scheduling Car A 3 37 Already in the process of scheduling Car A 4 27 Already in the process of scheduling Car B 5 30 Already in the process of scheduling Car B 6 34 Already in the process of scheduling Car B 7 31 Already in the process of scheduling Car C 8 33 Already in the process of scheduling Car C 9 36 Already in the process of scheduling Car C

[0338] Time 3:

[0339] The peak-hour elevator queue is shown in Table 2c below. There are currently no idle elevators. The current status of each elevator is as follows: Car A has stopped at floor 37 and is proceeding to floor 35; Car B has stopped at floor 34 and is proceeding to floor 30; Car C has stopped at floor 36 and is proceeding to floor 33. The task allocation / execution status is as follows: Task 1: Car A executes task [37, 35, 29]; Task 2: Car B executes task [34, 30, 27]; Task 3: Car C executes task [36, 33, 31]. During this period, the downhill call buttons for peak floors 28, 32, and 38 are detected being pressed sequentially.

[0340] Table 2c

[0341] Outbound call order Outbound call floors state Assigning cars 1 35 Already in the process of scheduling Car A 2 29 Already in the process of scheduling Car A 4 27 Already in the process of scheduling Car B 5 30 Already in the process of scheduling Car B 7 31 Already in the process of scheduling Car C 8 33 Already in the process of scheduling Car C 10 28 Not in scheduling 11 32 Not in scheduling 12 38 Not in scheduling

[0342] Time 4:

[0343] The peak-hour queue is shown in Table 2d below. At this time, there is one idle elevator, car C. The current status of each elevator is as follows: Car A has stopped at floor 35 and is now heading to floor 29; Car B has stopped at floor 30 and is now heading to floor 27; Car C has stopped at floor 33 and is now heading to floor 31. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 35, 29]; Task 2: Car B executes task [34, 30, 27]; Task 3: Car C executes task [36, 33, 31]. During this period, the down-going call buttons for peak floors 34, 37, and 36 are detected to be pressed in sequence.

[0344] Table 2d

[0345] Outbound call order Outbound call floors state Assigning cars 2 29 Already in the process of scheduling Car A 4 27 Already in the process of scheduling Car B 7 31 Already in the process of scheduling Car C 10 28 Not in scheduling 11 32 Not in scheduling 12 38 Not in scheduling 13 34 Not in scheduling 14 37 Not in scheduling 15 36 Not in scheduling

[0346] Time 5:

[0347] The peak-hour floor scheduling queue is shown in Table 2e below. At this time, there is one idle elevator, car B. The current status of each elevator is as follows: Car A is completing its task and stopping at all floors, and is descending to the base station floor on the 29th floor; Car B is completing its task and stopping at all floors, and is currently at the base station floor; Car C is completing its task and stopping at all floors, and is descending to the base station floor on the 31st floor. The task allocation at this time is as follows: Car A is assigned the task [37, 35, 29]; Car B is assigned the task [38, 32, 28]; Car C is assigned the task [36, 33, 31].

[0348] Table 2e

[0349] Outbound call order Outbound call floors state Assigning cars 10 28 Already in the process of scheduling Car B 11 32 Already in the process of scheduling Car B 12 38 Already in the process of scheduling Car B 13 34 Not in scheduling 14 37 Not in scheduling 15 36 Not in scheduling

[0350] Time 6:

[0351] The peak-hour queue for dispatching is shown in Table 2f below. At this time, there is one idle elevator, car A. The current status of each elevator is as follows: car A is at the base station floor, car B is ascending to the 37th floor, and car C is descending from the 31st floor to the base station floor. The task allocation at this time is as follows: car A is assigned the task [37, 36, 34]; car B is executing the task [38, 32, 28]; and car C is executing the task [36, 33, 31].

[0352] Table 2f

[0353] Outbound call order Outbound call floors state Assigning cars 10 28 Already in the process of scheduling Car B 11 32 Already in the process of scheduling Car B 12 38 Already in the process of scheduling Car B 13 34 Already in the process of scheduling Car A 14 37 Already in the process of scheduling Car A 15 36 Already in the process of scheduling Car A

[0354] 1. Users can configure elevator operation strategies through the strategy parameter setter, such as base station floor (F), which cars are dedicated to downhill peak scheduling, the number of passengers corresponding to a full car load, and waiting area settings.

[0355] The advantages of Example 2 regarding the peak-hour limit for the stairwell are as follows:

[0356] Introducing outbound call detection:

[0357] 1. Only when the downlink outbound call is pressed will the call be placed in the dispatch queue for dispatch, thus avoiding the problem of invalid intermediate stops caused by the floor entering the downlink peak mode but no one actually needing to go down.

[0358] 2. Based on outbound call data, it can be decided whether to allocate peak-hour elevator cars or use elevator cars exclusively for use outside of the downhill peak dispatch, thus resolving the issue of passengers taking the elevator in the opposite direction during downhill peak hours and on non-downhill peak hours.

[0359] Example 3:

[0360] The outbound call controller in Example 3 has no detection function and a number of callers system;

[0361] The working principle is as follows:

[0362] The elevator dispatch controller determines whether it is a peak downhill period based on the passenger count system outside the elevator car, and which floors are peak downhill floors. If they are peak downhill floors, it checks whether they have been added to the dispatch queue. If they are already in the dispatch queue, they are not added again; if they are not in the dispatch queue, they are added. Then, the elevator car is allocated according to the dispatch queue, and the task allocation is completed. When the elevator car is running, it checks whether the relevant elevator car is full. If it is found that the relevant elevator car is full, the remaining peak downhill floors that are planned to stop at in this task, except for the base station floor, are canceled, allowing the elevator car to go directly to the base station floor. At the same time, the "already dispatched" mark for these floors in the dispatch queue is canceled, or the mark is changed to "not dispatched". The position of these floors in the original dispatch queue is not cleared, allowing the corresponding floors to be given priority for new dispatch.

[0363] Detailed explanation is as follows:

[0364] (In non-peak descent mode, the number of floors in the waiting area that exceed the peak descent threshold; in peak descent mode, the number of floors in the waiting area that exceed the peak descent threshold are considered peak descent floors.) Information such as the minimum number of floors in the waiting area that reach the peak descent threshold before the system enters peak descent mode is also provided. This information is routinely set via the strategy parameter setter, which can be changed at any time according to human management requirements. The strategy parameters are then downloaded to the elevator dispatch controller.

[0365] 2. In this embodiment, the system can determine which floors have reached the peak descent threshold based on the number of passengers detected in the elevator lobby by the passenger counting system. If the number of these floors exceeds a set value, the system is considered to have entered the peak descent mode. This peak descent mode must be maintained for at least a certain period (e.g., 5 minutes). After 5 minutes, the passenger counting system will re-determine whether to exit the peak descent mode. When the elevator dispatch controller detects that it is currently in the peak descent period, the external call controller will cut off external calls: The external call controller uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches and indicator lights on the original elevator external call buttons from the elevator button panel; the elevator floor controller also uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches on the original floor selection buttons inside the elevator car from the elevator button panel. This prevents button signals from being directly sent to the elevator's own control system, thus preventing the elevator from responding to passengers' external or external calls. Simultaneously, the button indicator light on / off signals sent by the elevator's own control system cannot turn on / off the button indicator lights. These cut-off signals prevent users from calling the elevator via the external call buttons. In this embodiment, the system can determine which floors have reached the peak number of people waiting in the elevator lobby based on the number of people detected by the counting system. If the number of these floors exceeds the set value, the system is considered to have entered the peak downward mode. The peak downward mode must be maintained for at least a certain period of time (e.g., 5 minutes). After 5 minutes, the system will re-determine whether to exit the peak downward mode.

[0366] 3. The elevator dispatch controller automatically detects and determines which floors are currently in the down-peak period based on the number of people detected by the people counting system and the information set by the strategy parameter setter. It also checks whether these down-peak floors have been added to the dispatch queue. If they have not been added, they are added to the end of the dispatch queue in order and marked as "not in dispatch".

[0367] 4. When the elevator dispatch controller detects that a car has completed a trip (the elevator status detector detects that the corresponding car's running status changes from running to timed-out stationary, or the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and opened the door, it determines that a trip has been completed), it will retrieve the first k floors in the dispatch queue that have not yet been marked as "already dispatched" (or marked as "not dispatched"). These k floors are the planned downhill peak floors for this car's trip, and they will be marked as "already dispatched." Other cars will not retrieve these floors when picking up their trips. When the elevator dispatch controller retrieves floors not marked as "already dispatched" (or marked as "not dispatched") from the dispatch queue, it also collects the number of people in the waiting hall of the corresponding floor through the personnel counting system, and determines k based on the number of people in the waiting hall of each floor. The method for determining the value of k is as follows: k is initially 0, and k increases by 1 for each floor selected, k = k + 1. At the same time, the number of people waiting in the elevator lobby on these floors is accumulated (obtained through the passenger count system outside the car). When the accumulated number of people is greater than or equal to the maximum passenger capacity of the car, the final value of k is determined.

[0368] 5. After retrieving k floors, the elevator dispatch controller first retrieves the highest dispatch floor f from these k floors and sends a signal to the corresponding elevator floor controller to register the highest dispatch floor f. After receiving the signal, the elevator floor controller uses passive dry contact technology to simulate sending the corresponding button-triggered signal according to the specified floor, causing the car to go to the corresponding floor.

[0369] 6. When the elevator dispatch controller detects through the elevator status detector that the designated car has reached the top floor and stopped after a timeout or changed direction, if the highest dispatch floor reached is floor f, it will send instruction signals for registering the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the highest floor reached is not floor f, it will send instruction signals for registering k floors and the base station floor to the corresponding elevator floor controller. When the elevator dispatch controller detects through the elevator status detector that the designated car has reached floor f, it will send instruction signals for registering the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. After receiving the signals, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by pressing the corresponding button according to the designated floor, registers the corresponding floor inside the car, illuminates the internal call button indicator, and prompts the car to move to the sent floor. It also registers the base station floor; the basic public floor is defined as the base station floor, such as the 1st floor.

[0370] 7. During operation, the elevator dispatch controller detects whether the car door is open via the elevator status detector. If the car door is open, it checks whether the floor the car is on is the floor in the car's assigned task. If so, it means the car has completed its task and stopped at the corresponding floor, allowing passengers to enter. The system clears the information for that floor from the dispatch queue and controls the down call button indicator light for that floor to turn off via the outbound call controller. The elevator dispatch controller also checks whether the floor is still a peak downbound floor at the current time. If so, it checks whether these peak downbound floors have been added to the dispatch queue. If not, it adds the floor to the end of the queue and marks it as "not in dispatch".

[0371] 8. During task execution, when the elevator dispatch controller detects that the number of people in the car has reached or exceeded the set full load limit through the car's passenger count system, or when the elevator car is overloaded, it will issue a command signal to the elevator floor controller to cancel previously registered floors that have not yet stopped. This allows the elevator's own control system to prevent the car from stopping at subsequent floors and proceed directly to the base floor. For these floors that did not stop due to cancellation, the elevator dispatch controller retains their original order in the dispatch queue, only deleting their "already dispatched" mark or changing the mark to "not dispatched," so that these remaining tasks can be prioritized and assigned to the next available car for response.

[0372] 9. When the elevator dispatch controller detects that the car has stopped at the base station floor and the door has opened via the elevator status detector, it indicates that the current trip is complete, and the car can be reassigned to a new task according to step 4. At the same time, if the elevator dispatch controller finds that there are still floors in the task that have not been stopped, the elevator dispatch controller retains the original order of these floors in the waiting queue, but removes their "already dispatched" mark, or changes the mark to "not dispatched", so that these tasks can be preferentially assigned to the next available car for response.

[0373] like Figure 5 As shown, the elevator operation in this embodiment includes the following steps:

[0374] SC1: Determine whether the system has entered the downhill peak mode based on the passenger count system outside the car and determine which floors are the downhill peak floors;

[0375] SC2: Check if the corresponding floor is in the queue to be dispatched. If not, put it at the end of the queue to be dispatched, mark it as "not in dispatch", and light up the downlink outbound call button indicator.

[0376] SC3: Check if there are any peak-hour cars available for dispatch. If yes, proceed to step SC4; otherwise, proceed to step SC7.

[0377] SC4: Take the first k floors from the queue that have not yet been marked as "already in scheduling" (or marked as "not in scheduling"), and mark these k floors as "already in scheduling". The method for determining the value of k is as follows: the initial value of k is 0, and k = k + 1 for each floor taken. At the same time, accumulate the number of people in the waiting hall outside the car on these floors (obtained through the outside passenger count system). When the accumulated number of people is greater than or equal to the maximum passenger capacity of the car, the final k is determined. Take the highest scheduling floor f among these k floors and register it.

[0378] SC5: Detects that the designated car has timed out and stopped at the top floor or changed direction of travel;

[0379] SC6: If the highest floor reached is floor f, then register the other k-1 floors besides floor f and the base station floor; if the highest floor reached is not floor f, then register k floors and the base station floor; if the elevator dispatch controller detects that the designated car has descended to floor f, then register the other k-1 floors besides floor f and the base station floor; prompt the car to go to the corresponding floor.

[0380] SC7: Detects if there is a peak-hour car stop or door opening. If so, it determines whether the stopping floor is one of the k floors in this car's dispatch task. If the stopping floor is one of the floors in this car's dispatch task, the corresponding floor is removed from the waiting queue, and the corresponding downlink outbound call button indicator light is turned off. If the stopping floor is not one of the floors in this car's dispatch task, it determines whether it is a base station floor. If it is a base station floor, the current task is completed, and the car is marked as "awaiting dispatch," available for the next round of dispatch. If it is not a base station floor, it continues to wait for door opening detection for re-determination. If it has reached a base station floor but there are still floors in the dispatch task that have not been stopped, it cancels the "already dispatching" mark of these floors in the waiting queue, or changes the mark to "not in dispatch," without clearing the position of these floors in the original waiting queue, allowing the corresponding floors to receive new dispatch first.

[0381] SC8: Detect whether the relevant car is full. If it is detected that it is full, cancel the remaining downlink peak floors that the car is scheduled to stop at in this mission except for the base station floor, so that the car can go directly to the base station floor. At the same time, cancel the "already in scheduling" mark of these floors in the scheduling queue, or change the mark to "not in scheduling". Do not clear the position of these floors in the original scheduling queue, so that the corresponding floors can be given priority to accept new scheduling.

[0382] A schematic diagram of the elevator capacity distribution system in this embodiment of the invention is shown below. Figure 6As shown, in this embodiment, the elevator control panel includes a floor selection control panel and an external call control panel. Elevator cars one through N, along with the floor selection control panels, floor selection buttons, and a passenger counting system (inside the car), constitute the elevator's own control system. The elevator's own control system also includes an external call control panel and external call buttons. Assuming the building has M floors and N elevators, in this embodiment, the elevator control panel includes an internal call control panel and an external call control panel. The strategy parameter setter is connected to the elevator dispatch controller. The elevator dispatch controller is connected to the first elevator floor controller through the Nth elevator floor controller. The first elevator floor controller is connected to the first elevator status detector and is also connected to the floor selection control panel and floor selection buttons in elevator car one. The Nth elevator floor controller is connected to the Nth elevator status detector and is also connected to the floor selection control panel and floor selection buttons in elevator car N. The elevator floor controller connects the floor selection buttons and the floor selection control panel, selectively connecting or disconnecting the button switches on the elevator car floor selection buttons from the floor selection control panel.

[0383] Each floor has an elevator lobby, which contains an external call controller and connected external call button panels and buttons. For example, the first-floor lobby has a first-floor external call controller, external call button panel, and external call buttons; the second-floor lobby has a second-floor external call controller, external call button panel, and external call buttons; and the M-floor lobby has an M-floor external call controller, external call button panel, and external call buttons. The first-floor external call controller is connected to the first-floor external call button panel and buttons, the second-floor external call controller is connected to the second-floor external call button panel and buttons, and the M-floor external call controller is connected to the M-floor external call button panel and buttons. The external call controller connects to both the external call buttons and the external call button panel, allowing for selective connection or disconnection of the button switches on the elevator car's external call buttons to the external call button panel.

[0384] The waiting halls are also equipped with a number counting system. For example, the first-floor waiting hall has a number counting system, the second-floor waiting hall has a number counting system, and the M-floor waiting hall has a number counting system.

[0385] The elevator dispatch controller is also connected to the outbound call controller on the first floor, the outbound call controller on the second floor, and the outbound call controller on the M floor. In this embodiment, the outbound call controller only outputs signals to the outbound call button and does not receive outbound call signals from the outbound call button.

[0386] In this embodiment, the elevator dispatching system of the elevator capacity allocation system with no outbound call controller and a passenger count system is illustrated as follows:

[0387] Time 1:

[0388] In this embodiment, the floor with more than 4 people in the waiting hall is designated as a peak-hour floor for descent. The system enters peak-hour mode when at least 3 floors have reached the peak-hour standard. The external passenger counting system detects the number of people in the waiting hall as shown in Table 3a, and the system enters peak-hour mode. The maximum number of floors each car can stop at during peak hours is set to k, where k depends on the number of people in the waiting hall and the maximum passenger capacity of the car. Floors with 5 or more people in the waiting hall detected by the passenger counting system can be designated as peak-hour floors for descent. The maximum passenger capacity of the car is 15, and cars A and B are dedicated to peak-hour scheduling. In this embodiment, after the external passenger counting system detects that the number of people in the waiting hall of a certain floor is greater than or equal to the preset number and designates it as a peak-hour floor for descent, if the number of people in the waiting hall of this floor changes to less than the preset number before the car stops, the floor is not removed from the scheduling queue or car task.

[0389] Table 3a

[0390] order Downward Peak Floor Number of people in the waiting hall 1 37 7 2 32 3 3 26 5 4 17 3 5 10 6

[0391] Time 2:

[0392] The queue for dispatch and the number of people in the waiting hall are shown in Table 3b below. Among them, the number of people in the waiting halls on the 32nd and 17th floors is less than 5, and there is one idle car, which is car A. The current status of each elevator is as follows: Car A is at the base station floor, and car B is executing the previous task. The task allocation / execution status at this time is as follows: Task 1: Car A is assigned tasks [37, 26, 10].

[0393] It should be noted that the elevator floor controllers of cars A and B receive and register the highest dispatch floor f1 / f2 among the k1 / k2 dispatch floors issued by the elevator dispatch controller. After the elevator dispatch controller detects that the designated car has timed out or changed direction after reaching the highest floor through the elevator status detector, if the highest floor reached is f1 / f2, it will send the instruction signals for registering the other k1-1 / k2-1 floors and the base station floor to the corresponding elevator floor controller. If the highest floor reached is not f1 / f2, it will send the instruction signals for registering the k1 / k2 floors and the base station floor to the corresponding elevator floor controller. If the elevator dispatch controller detects that the designated car has reached the f1 / f2 floor after descending through the elevator status detector, it will send the instruction signals for registering the other k1-1 / k2-1 floors and the base station floor to the corresponding elevator floor controller.

[0394] Where k1 and k2 correspond to the maximum number of stops per trip for each car during peak hours in Task 1 and Task 2, respectively. In this embodiment, k1 = k2 = k, and the value of k is set by the strategy parameter setter. Furthermore, the dispatched floors k1 and k2 are elevator floor controllers registered to car A and car B, respectively. The floors in the dispatched floors k1 include [37, 26, 10], and are registered to the elevator floor controller of car A.

[0395] Each elevator floor controller registers the k / k-1 dispatch floors issued by the elevator dispatch controller simultaneously, without any order.

[0396] The elevator floor controller of car A receives and registers the highest dispatch floor 37 from the [37, 26, 10] dispatch floor issued by the elevator dispatch controller. If the highest floor reached is not 37, the elevator floor controller of car A receives and registers the three dispatch floors [37, 26, 10] plus the base station floor issued by the elevator dispatch controller. If the highest floor reached is 37, the two dispatch floors [26, 10] plus the base station floor will be registered at the same time.

[0397] Table 3b

[0398] order Downward Peak Floor Number of people in the waiting hall state Assigning cars 1 37 7 Already in the process of scheduling Car A 2 26 5 Already in the process of scheduling Car A 3 10 6 Already in the process of scheduling Car A

[0399] Time 3:

[0400] The queue for dispatch and the number of people in the waiting hall are shown in Table 3c below. At this time, there is one idle elevator, which is elevator B. The current status of each elevator is as follows: elevator A is descending from the 37th floor to the 26th floor, while elevator B is at the base station floor. At this time, the number of people in the waiting halls on the 32nd floor and the 17th floor has reached 5 and 7 people respectively, which meets the demand of the descending peak floors, so they are arranged in the queue for dispatch. The task allocation / execution status at this time is as follows: Task 1: Elevator A executes task [37, 26, 10]; Task 2: Elevator B is assigned task [32, 17].

[0401] If the highest floor reached by car B is not the highest dispatch floor of k2, floor 32, then the elevator floor controller of car B receives and simultaneously registers the two dispatch floors [32, 17] plus the base station floor issued by the elevator dispatch controller; if the highest floor reached is floor 32, then one dispatch floor plus the base station floor

[17] will be registered simultaneously.

[0402] Table 3c

[0403] order Downward Peak Floor Number of people in the waiting hall state Assigning cars 2 26 5 Already in the process of scheduling Car A 3 10 6 Already in the process of scheduling Car A 4 17 7 Already in the process of scheduling Car B 5 32 5 Already in the process of scheduling Car B

[0404] Time 4:

[0405] The queue of passengers waiting to be dispatched and the number of passengers in the waiting hall are shown in Table 3d. At this time, the passenger counting system detects that the number of peak floors for the downward movement is less than 3. If the number of peak floors for the downward movement is greater than 3 within 5 minutes, the system will maintain the downward peak mode. If the number of peak floors for the downward movement is still less than 3 after 5 minutes, the system will automatically exit the downward peak mode. At this time, there are no empty elevators. The current status of each elevator is as follows: Car A is descending from the 26th floor to the 10th floor, and Car B is descending from the 32nd floor to the 17th floor. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 26, 10]; Task 2: Car B executes task [32, 17].

[0406] Table 3d

[0407] order Downward Peak Floor Number of people in the waiting hall state Assigning cars 3 10 6 Already in the process of scheduling Car A 4 17 7 Already in the process of scheduling Car B

[0408] The advantages of Example 3 are as follows:

[0409] Add a headcount system:

[0410] 1. The elevator dispatch controller can determine whether to perform peak-hour dispatching based on the real-time passenger flow, making it more accurate and intelligent;

[0411] 2. Able to reasonably arrange the number of stops on each floor based on the number of people on each floor, reducing stops and improving efficiency;

[0412] 3. The system can schedule elevators based on passenger load, ensuring they travel directly to the base station floor when fully loaded, avoiding intermediate stops and improving efficiency. Incorporating a passenger count system ensures that each elevator car is prioritized for allocation to a full floor in the dispatch queue, then proceeds directly to the base station floor, reducing stops, increasing elevator speed, and maximizing elevator utilization.

[0413] Example 4:

[0414] The external call controller in Example 4 has a detection function and a passenger counting system inside the elevator car (only including passenger counting devices inside each elevator car, excluding passenger counting devices in the waiting hall on each floor);

[0415] The working principle is as follows:

[0416] The elevator dispatch controller determines whether it is currently a downhill peak period and which floors are experiencing downhill peaks based on the strategy parameter setter. It then determines whether the outbound call request is for the downhill direction. If not, it dispatches an elevator car not designated for downhill peak scheduling, completing the task allocation. If the call is for a downhill signal, it determines whether it is for a downhill peak floor. If not, it dispatches an elevator car not designated for downhill peak scheduling, completing the task allocation. If it is for a downhill peak floor, it checks if the elevator is already in the dispatch queue. If already in the queue, it is not added again; otherwise, it is added. Finally, it allocates elevator cars according to the dispatch queue, completing the task allocation. When the elevator car is running, it checks whether the relevant elevator car is full. If it is found that the relevant elevator car is full, it cancels the remaining downlink peak floors that the elevator car is scheduled to stop at in this mission, except for the base station floor, so that the elevator car can go directly to the base station floor. At the same time, it cancels the "already scheduled" mark of these floors in the scheduling queue, or changes the mark to "not scheduled". It does not clear the position of these floors in the original scheduling queue, so that the corresponding floors can be given priority to accept new scheduling.

[0417] Detailed explanation is as follows:

[0418] 1. Users can configure policy parameters through the policy parameter setter, such as which time periods to enter the downhill peak mode, which floors are in different downhill peak periods, how many floors the elevator car typically stops at before reaching full capacity during downhill peak periods, the base station floor (F), the number of passengers corresponding to a full car, and which cars are dedicated to downhill peak scheduling. This information is routinely set through the policy parameter setter, and can be changed at any time according to human management requirements. The policy parameters will be downloaded to the elevator dispatch controller.

[0419] 2. When the elevator dispatch controller detects that it is currently in a downhill peak period, the outbound call controller will cut off outbound calls: The outbound call controller uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches and indicator lights on the original elevator outbound call buttons from the elevator button panel; the elevator floor controller also uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches on the original floor selection buttons inside the elevator car from the elevator button panel. This prevents button signals from being directly sent to the elevator's own control system, thus preventing the elevator from responding to passengers' outbound or inbound calls. Simultaneously, the button indicator light on / off signals sent by the elevator's own control system cannot ignite / extinguish the button indicator lights. These cut-off signals are detected, processed, and received by the outbound call controller in this embodiment, and then uniformly allocated by the dispatch controller.

[0420] 3. The elevator dispatch controller automatically detects and determines which floors are currently in the downhill peak according to the information set by the strategy parameter setter. In this example, the system determines which floors are currently in the downhill peak according to the strategy parameter set information.

[0421] 4. When a user needs to take the elevator downhill, they press the downhill call button. The call controller detects this press. Due to the controller's control mechanism, there is no signal connection between the call button and the elevator's own control system. The button press signal is only detected by the call controller and sent to the elevator dispatch controller for processing. The call controller itself outputs a signal to the call button indicator light, illuminating it. Alternatively, the elevator dispatch controller sends a command signal to the call controller of the corresponding floor, instructing it to illuminate its corresponding call indicator light. The elevator dispatch controller checks if the pressed button belongs to a downhill call button for a peak downhill floor. If not, the elevator will be served by an elevator car specifically designated for peak downhill dispatch. If so, it checks if the floor is already in the dispatch queue. If not, it adds the floor to the end of the queue and marks it as "not in dispatch."

[0422] 5. When the elevator dispatch controller detects that a car has completed a trip (the elevator status detector detects that the corresponding car's running status changes from running to timeout and stationary, or the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and opened the door, it is determined that a trip has been completed), it will take the first k floors that are not marked as "already in dispatch" (or marked as "not in dispatch") from the waiting queue. These k floors are the planned downhill peak floors for the current car trip. These floors will be marked as "already in dispatch". Other cars will not take these floors when taking a task. After taking these floor numbers, the elevator dispatch controller first takes the highest dispatch floor f from these k floors and sends a signal to the elevator floor controller to register the highest dispatch floor f. After receiving the signal, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by the corresponding button press according to the specified floor, prompting the car to go to the corresponding floor.

[0423] 6. When the elevator dispatch controller detects that a designated car has reached the top floor and stopped within a timeout period or changed direction, if the top floor is floor f, it sends command signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor is not floor f, it sends command signals for the k floors and the base station floor to the corresponding elevator floor controller. Similarly, if the elevator dispatch controller detects that a designated car has reached floor f, it sends command signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. Upon receiving the signals, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by pressing a button, registering the corresponding floor inside the car, illuminating the internal call button indicator, and prompting the car to proceed to the designated floor. It also registers the base station floor; basic public floors are defined as base station floors, such as the first floor.

[0424] 7. During operation, the elevator dispatch controller detects whether the car door is open through the elevator status detector. If the car door is detected to be open, it checks whether the floor where the car is located is the floor in the car's task. If so, it means that the car has completed the corresponding floor stop in the task and allowed the passenger to enter. The system clears the information of that floor from the dispatch queue and controls the down call button indicator light of the corresponding floor to turn off through the call controller. At this time, the floor is removed from the dispatch queue. If there is a new user call request later, it will be put back into the dispatch queue according to step 3 and wait for execution.

[0425] 8. During task execution, when the elevator dispatch controller detects that the number of people in the car has reached or exceeded the set full load limit through the car's passenger count system, or when the elevator car is overloaded, it will issue a command signal to the elevator floor control to cancel previously registered floors that have not yet stopped. This allows the elevator's own control system to prevent the car from stopping at subsequent floors and proceed directly to the base floor. For these floors that did not stop due to cancellation, the elevator dispatch controller retains their original order in the dispatch queue, only deleting their "already dispatched" mark or changing the mark to "not dispatched," so that these remaining tasks can be prioritized and assigned to the next available car for response.

[0426] 9. When the elevator dispatch controller detects that the car has stopped at the base station floor and the door has opened through the elevator status detector, it indicates that the current trip is complete, and the car can be reassigned to a new task according to step 4. At the same time, if the elevator dispatch controller finds that there are still floors in the task that have not been stopped, the elevator dispatch controller retains the original order of these floors in the waiting queue, but removes their "already being dispatched" mark, so that these tasks can be preferentially assigned to the next available car for response.

[0427] 10. Reverse calls from peak-downward floors and calls from non-peak-downward floors will be handled by dispatching designated elevator cars outside of peak-downward scheduling to respond to elevator requests and complete the elevator ride: For some people on peak-downward floors who need to reverse their journey during peak-downward periods, or for people on non-peak-downward floors who need to go down, since they represent a very small portion of the total peak-downward capacity, they can be flexibly configured. Designated elevators in the elevator group can be arranged to shuttle up and down to solve the problem of some people on peak-downward floors needing to go up and people on non-peak-downward floors needing to go up / down during peak-downward periods. When the call button for a peak-downward call or a non-peak-downward call is pressed, the call button's connection to the elevator's internal control system is severed by the call controller via a passive dry contact. Upon receiving the call request signal, the call controller detects and receives the signal, then sends it to the elevator dispatching system for task assignment. The dispatching system assigns the task to the elevator floor controller of a car not used for peak-downward dispatch, illuminating the corresponding upward departure floor. The elevator's internal control system then directs the car not used for peak-downward dispatch to that floor. Alternatively, the call buttons and indicator lights of cars not used for peak-downward dispatch are connected to the elevator control panel and remain connected, controlled by the elevator's internal control system, dispatching the car to the corresponding floor to provide service. The call responses of this elevator and the elevator group used for peak-downward dispatch are independent and do not affect each other.

[0428] like Figure 7 As shown, the elevator operation in this embodiment includes the following steps:

[0429] SD1: The elevator dispatch controller determines whether the system has entered the downhill peak mode based on the strategy parameters and determines which floors are the downhill peak floors;

[0430] SD2: Detects if an outbound call button has been pressed. If so, it determines whether the pressed button is for a peak downbound floor. If it is, it checks if the corresponding floor is in the dispatch queue. If not, it is placed at the end of the dispatch queue, marked "not in dispatch", and the downbound call button indicator light is illuminated. If the pressed button is not for a peak downbound floor, it dispatches a car designated for use outside of peak downbound dispatch for service.

[0431] SD3: Check if there are any peak-hour cars available for dispatch. If so, proceed to step SD4; otherwise, proceed to step SD7.

[0432] SD4: Take the first k floors from the queue that have not yet been marked "already in scheduling" (or marked "not in scheduling"), and mark these k floors as "already in scheduling". k is set by the policy setter based on how many floors the elevator car usually stops at when it is full. Take the highest scheduling floor f among these k floors and register it.

[0433] SD5: Detected that the designated car has timed out and stopped at the top floor or changed direction of travel;

[0434] SD6: If the highest floor reached is floor f, then register the other k-1 floors besides floor f and the base station floor; if the highest floor reached is not floor f, then register k floors and the base station floor; if the elevator dispatch controller detects that the designated car has descended to floor f, then register the other k-1 floors besides floor f and the base station floor; prompt the car to go to the corresponding floor.

[0435] SD7: Detects if there is a peak-hour car stop or door opening. If so, it determines if the stopping floor is one of the k floors in this car's dispatch task. If the stopping floor is one of the floors in this car's dispatch task, the corresponding floor is removed from the waiting queue, and the corresponding downlink outbound call button indicator light is turned off. If the stopping floor is not one of the floors in this car's dispatch task, it determines if it is a base station floor. If it is a base station floor, the current task is completed, and the car is marked as "awaiting dispatch," available for the next round of dispatch. If it is not a base station floor, it continues to wait for door opening detection for re-determination. If it has reached a base station floor but there are still floors in the dispatch task that have not been stopped, it cancels the "already dispatching" mark for these floors in the waiting queue, or changes the mark to "not in dispatch," without clearing the position of these floors in the original waiting queue, allowing the corresponding floors to receive new dispatch first.

[0436] SD8: Detect whether the relevant car is full. If the relevant car is full, cancel the remaining downlink peak floors planned to stop for this car in this mission, except for the base station floor, so that the car can go directly to the base station floor. At the same time, cancel the "already in scheduling" mark of these floors in the scheduling queue, or change the mark to "not in scheduling" without clearing the position of these floors in the original scheduling queue, so that the corresponding floors can be given priority to accept new scheduling.

[0437] A schematic diagram of the elevator capacity distribution system in this embodiment of the invention is shown below. Figure 8As shown, in this embodiment, the elevator control panel includes a floor selection control panel and an external call control panel. Elevator cars one through N, along with the floor selection control panels, floor selection buttons, and a passenger counting system (inside the car), constitute the elevator's own control system. The elevator's own control system also includes an external call control panel and external call buttons. Assuming the building has M floors and N elevators, in this embodiment, the elevator control panel includes an internal call control panel and an external call control panel. The strategy parameter setter is connected to the elevator dispatch controller, which is connected to the first elevator floor controller through the Nth elevator floor controller. The first elevator floor controller is connected to the first elevator status detector and is also connected to the floor selection control panel and floor selection buttons in elevator car one. The Nth elevator floor controller is connected to the Nth elevator status detector and is also connected to the floor selection control panel and floor selection buttons in elevator car N. The elevator floor controller connects the floor selection buttons and the floor selection control panel, selectively connecting or disconnecting the button switches on the elevator car floor selection buttons from the floor selection control panel.

[0438] Each floor has an elevator lobby, which contains an external call controller and connected external call buttons. For example, the first-floor lobby has a first-floor external call controller, a first-floor external call button panel, and first-floor external call buttons; the second-floor lobby has a second-floor external call controller, a second-floor external call button panel, and second-floor external call buttons; and the M-floor lobby has an M-floor external call controller, an M-floor external call button panel, and M-floor external call buttons. The first-floor external call controller is connected to the first-floor external call button panel and buttons, the second-floor external call controller is connected to the second-floor external call button panel and buttons, and the M-floor external call controller is connected to the M-floor external call button panel and buttons. The external call controller connects to both the external call buttons and the external call button panel, allowing for selective connection or disconnection of the button switches on the elevator car's external call buttons to the external call button panel.

[0439] The elevator dispatch controller is also connected to the call controller on the first floor, the call controller on the second floor, and the call controller on the M floor. In this embodiment, the call controller input terminal is connected to the call button to receive the call signal from the call button. The elevator floor controller detects and processes the call signal.

[0440] In this embodiment, an elevator dispatching system with detection function and a passenger counting system (including only passenger counting devices inside each elevator car, excluding passenger counting devices in the waiting hall on each floor) is illustrated as follows:

[0441] Time 1:

[0442] When the downhill peak period begins (17:00-18:00), the system enters the downhill peak mode. The outbound call buttons for floors 35, 32, 30, 34, 31, and 33 are pressed sequentially, and these floors are all downhill peak floors during this period. The corresponding floors for which the outbound call buttons are pressed are recorded, thus obtaining the queue to be dispatched as shown in Table 4a. k is set to 3, the car's full load capacity is set to 15 people, and cars A, B, and C are dedicated to downhill peak dispatch.

[0443] Table 4a

[0444]

[0445]

[0446] Time 2:

[0447] The queue to be dispatched is shown in Table 4b below. Currently, there are two idle elevators, car A and car B. The current status of each elevator is as follows: cars A and B are at the base station floor, and car C is executing a previously completed task. The task allocation is as follows: Task 1: Car A is assigned tasks [35, 32, 30]; Task 2: Car B is assigned tasks [34, 33, 31]; Car C is executing a previously completed task.

[0448] It should be noted that the elevator floor controllers of cars A / B / C receive and register the highest dispatch floor f among the k1 / k2 / k3 dispatch floors issued by the elevator dispatch controller. After the elevator dispatch controller detects that the designated car has timed out or changed direction after reaching the highest floor, if the highest floor reached is floor f, it will send the instruction signals for registering the other k1-1 / k2-1 / k3-1 floors and the base station floor to the corresponding elevator floor controller. If the highest floor reached is not floor f, it will send the instruction signals for registering the k1 / k2 / k3 floors and the base station floor to the corresponding elevator floor controller. If the elevator dispatch controller detects that the designated car has reached floor f after descending through the elevator status detector, it will send the instruction signals for registering the other k1-1 / k2-1 / k3-1 floors and the base station floor to the corresponding elevator floor controller.

[0449] Each elevator floor controller registers the k / k-1 dispatch floors issued by the elevator dispatch controller simultaneously, without any order.

[0450] Where k1, k2, and k3 correspond to the maximum number of stops per trip for each car during peak hours in Task 1, Task 2, and Task 3, respectively. In this embodiment, k1 = k2 = k3 = k, and the value of k is set by the strategy parameter setter. Furthermore, the dispatched floors k1, k2, and k3 are elevator floor controllers registered to cars A, B, and C, respectively. Specifically, the floors in dispatched floor k1 include [35, 32, 30], registered to the elevator floor controller for car A; the floors in dispatched floor k2 include [34, 33, 31], registered to the elevator floor controller for car B.

[0451] The elevator floor controller of car A receives and registers the highest dispatch floor 35 from the [35, 32, 30] dispatch floor issued by the elevator dispatch controller. If the highest floor reached is not 35, the elevator floor controller of car A receives and registers the three dispatch floors [35, 32, 30] plus the base station floor issued by the elevator dispatch controller. If the highest floor reached is 35, the two dispatch floors [32, 30] plus the base station floor will be registered at the same time.

[0452] The elevator floor controller of car B receives and registers the highest dispatch floor 34 in the [34, 33, 31] dispatched by the elevator dispatch controller. If the highest floor reached is not 34, the elevator floor controller of car B receives and registers the three dispatch floors [34, 33, 31] plus the base station floor issued by the elevator dispatch controller. If the highest floor reached is 34, the two dispatch floors [33, 31] plus the base station floor will be registered at the same time.

[0453] Table 4b

[0454] Outbound call order Outbound call floors state Assigning cars 1 35 Already in the process of scheduling Car A 2 32 Already in the process of scheduling Car A 3 30 Already in the process of scheduling Car A 4 34 Already in the process of scheduling Car B 5 31 Already in the process of scheduling Car B 6 33 Already in the process of scheduling Car B

[0455] Time 3:

[0456] The queue to be dispatched is shown in Table 4c1 below. At this time, there are no idle cars. The current status of each elevator is as follows: Car A has stopped at the 35th floor and is heading to the 32nd floor; Car B has stopped at the 34th floor and is heading to the 33rd floor; Car C is executing a previous task. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [35, 32, 30]; Task 2: Car B executes task [34, 33, 31].

[0457] Table 4c1

[0458] Outbound call order Outbound call floors state Assigning cars 2 32 Already in the process of scheduling Car A 3 30 Already in the process of scheduling Car A 5 31 Already in the process of scheduling Car B 6 33 Already in the process of scheduling Car B

[0459] The load conditions of each car at this time are shown in Table 4c2 below:

[0460] Table 4c2

[0461] Car Load capacity A 13 B 8

[0462] Time 4:

[0463] The queue to be dispatched is shown in Table 4d1 below. At this time, there is one idle car, C. The current status of each elevator is as follows: Car A has stopped at the 35th floor and is now heading to the 32nd floor. Car A is fully loaded with 15 people but is not overloaded, so Car A will head to the base station floor. The down call button is pressed at the 32nd floor, and the 32nd floor enters the end of the queue to be dispatched again. The 30th floor retains its original position in the queue to be dispatched first. Car B has stopped at the 33rd floor and is now heading to the 31st floor. Car C is at the base station floor. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [35, 32]; Task 2: Car B executes task [34, 33, 31]; Task 3: Car C is assigned task [36, 30, 27].

[0464] Table 4d1

[0465] Outbound call order Outbound call floors state Assigning cars 3 30 Already in the process of scheduling Car C 6 31 Already in the process of scheduling Car B 7 27 Already in the process of scheduling Car C 8 36 Already in the process of scheduling Car C 9 32 Not in scheduling

[0466] The load conditions of each car at this time are shown in Table 4d2 below:

[0467] Table 4d2

[0468] Car Load capacity A 15 B 11 C 0

[0469] Time 5:

[0470] The queue to be dispatched is shown in Table 4e1 below. At this time, there is one idle car, A. The current status of each elevator is as follows: Car A is at the base station floor; Car B has completed its task of stopping at all floors and is descending to the base station floor at floor 31. During this process, the down call button is pressed at floor 31, and floor 31 enters the end of the queue to be dispatched; Car C has completed its task of stopping at floor 36 and is descending to floor 30. The task allocation / execution status at this time is as follows: Task 1: Car A is assigned the task [37, 32, 31]; Task 2: Car B executes the task [34, 33, 31]; Task 3: Car C executes the task [36, 30, 27].

[0471] Table 4e1

[0472] Outbound call order Outbound call floors state Assigning cars 3 30 Already in the process of scheduling Car C 7 27 Already in the process of scheduling Car C 9 32 Already in the process of scheduling Car A 10 37 Already in the process of scheduling Car A 11 31 Already in the process of scheduling Car A

[0473] The load conditions of each car at this time are shown in Table 4e2 below:

[0474] Table 4e2

[0475]

[0476]

[0477] Time 6:

[0478] The queue to be scheduled is shown in Table 4f1 below. At this time, there is one idle car, B. The current status of each elevator is as follows: Car A is going up to the 37th floor, Car B has completed all the stops on all the floors in the task and is at the base station floor, and Car C has completed the stop on the 30th floor and is going down to the 27th floor. The task allocation / execution status at this time is as follows: Task 1: Car A executes task [37, 32, 31]; Task 3: Car C executes task [36, 30, 27].

[0479] Table 4f1

[0480] Outbound call order Outbound call floors state Assigning cars 7 27 Already in the process of scheduling Car C 9 32 Already in the process of scheduling Car A 10 37 Already in the process of scheduling Car A 11 31 Already in the process of scheduling Car A

[0481] The load conditions of each car at this time are shown in Table 4f2:

[0482] Table 4f2

[0483] Car Load capacity A 0 B 0 C 11

[0484] Example 5:

[0485] The outbound call controller in Example 5 has a detection function and a number of callers system;

[0486] The working principle is as follows:

[0487] The elevator dispatch controller determines whether it is a downhill peak period and which floors are downhill peak floors based on the passenger count system outside the car. It then determines whether the outgoing call request is for the downhill direction. If not, the elevator car designated for downhill peak scheduling responds to the request, and task allocation is complete. If the call is for the downhill direction, the controller determines whether it is a downhill peak floor based on the passenger count system. If not, the elevator car designated for downhill peak scheduling is dispatched, and task allocation is complete. If it is a downhill peak floor, the controller checks if the elevator is already in the dispatch queue. If already in the queue, it is not added again; if not, it is added. Finally, elevator cars are allocated according to the dispatch queue, and task allocation is complete. When the elevator car is running, it checks whether the relevant elevator car is full. If it is found that the relevant elevator car is full, it cancels the remaining downlink peak floors that the elevator car is scheduled to stop at in this mission, except for the base station floor, so that the elevator car can go directly to the base station floor. At the same time, it cancels the "already scheduled" mark of these floors in the scheduling queue, or changes the mark to "not scheduled". It does not clear the position of these floors in the original scheduling queue, so that the corresponding floors can be given priority to accept new scheduling.

[0488] Detailed explanation is as follows:

[0489] 1. Users can configure policy parameters through the policy parameter setter: base station floor (F), which elevator cars are dedicated to downhill peak scheduling, the number of passengers corresponding to a full car load, the peak passenger limit in the waiting hall (in non-downhill peak mode, the number of passengers in the waiting hall exceeding the corresponding floor to reach the downhill peak standard; in downhill peak mode, the number of passengers in the waiting hall exceeding the corresponding floor to be determined as a downhill peak floor), and the minimum number of floors where the waiting hall passenger reaches the downhill peak standard for the system to enter downhill peak mode, etc. The above information is routinely set through the policy parameter setter, and this setting can be changed at any time according to human management requirements. The policy parameters will be downloaded to the elevator dispatch controller.

[0490] 2. In this embodiment, the system can determine which floors have reached the peak descent threshold based on the number of passengers detected in the elevator lobby by the passenger counting system. If the number of passengers on these floors exceeds a set value, the system is considered to have entered the peak descent mode. This peak descent mode must be maintained for at least a certain period (e.g., 5 minutes). After 5 minutes, the passenger counting system will re-determine whether to exit the peak descent mode. When the elevator dispatch controller detects that it is currently in the peak descent period, the external call controller will cut off external calls: The external call controller uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches and indicator lights on the original elevator external call buttons from the elevator button panel; The elevator floor controller also uses passive dry contact technology to interface with the elevator's own control system, disconnecting the button switches on the original floor selection buttons inside the elevator car from the elevator button panel. This prevents the button signals from being directly sent to the elevator's own control system, thus preventing the elevator from responding to passengers' external or external calls. Simultaneously, the button indicator light on / off signals sent by the elevator's own control system cannot turn the button indicator lights on / off. These truncated signals are detected, processed, and received by the outbound call controller in this embodiment, and then uniformly allocated by the dispatch controller.

[0491] 3. In the downward peak mode, the elevator dispatch controller, based on the information set by the strategy parameter setter, automatically detects and determines which floors are currently in the downward peak mode through the passenger count system, and marks these floors. When the passenger count system detects that the number of people waiting in the elevator lobby is greater than or equal to the set "peak passenger limit in the elevator lobby," the corresponding floor is marked as a downward peak floor. In the downward peak mode, the elevator car will stop at each floor for a certain period of time (e.g., 3 minutes) before the passenger count system checks again to see if the corresponding floor has exited the downward peak mode. When a user needs to take the elevator, they press the call button. Due to the control of the call controller, there is no signal connection between the call button and the elevator's own control system. After the call controller detects that a downward call button has been pressed, this button press signal will only be detected by the call controller and sent to the elevator dispatch controller for processing. The call controller itself outputs a signal to the call button indicator light, which illuminates the call button indicator light. Alternatively, the elevator dispatch controller sends a command signal to the call controller of the corresponding floor to illuminate its corresponding call button indicator light.

[0492] 4. The elevator dispatch controller detects whether the pressed call button belongs to the down button of the down peak floor. If not, the elevator car dedicated to down peak dispatch will provide service. If so, it checks whether the floor has been put into the dispatch queue. If not, it puts it to the end of the dispatch queue and marks it as "not in dispatch".

[0493] 5. When the elevator dispatch controller detects that a car has completed a trip (the elevator status detector detects that the corresponding car's running status changes from running to timed-out stationary, or the elevator status detector detects that the car has reached the base station floor set by the strategy parameters and opened the door, it determines that a trip has been completed), it will retrieve the first k floors from the dispatch queue that are not marked as "already dispatched" (or marked as "not dispatched"). These k floors are the planned downhill peak floors for this car's trip, and they will be marked as "already dispatched." Other cars will not retrieve these floors when picking up their trips. When the elevator dispatch controller retrieves floors not marked as "already dispatched" (or marked as "not dispatched") from the dispatch queue, it also collects the number of people in the corresponding floor's waiting hall at that time through the people counting system, and determines k based on the number of people in the waiting halls of each floor. The method for determining the value of k is as follows: k is initially 0, and k increases by 1 for each floor selected, k = k + 1. At the same time, the number of people waiting in the elevator lobby on these floors is accumulated (obtained through the passenger count system outside the car). When the accumulated number of people is greater than or equal to the maximum passenger capacity of the car, the final value of k is determined.

[0494] 6. After retrieving k floors, the elevator dispatch controller first retrieves the highest dispatch floor f from these k floors and sends a signal to the elevator floor controller to register the highest dispatch floor f. After receiving the signal, the elevator floor controller uses passive dry contact technology to simulate sending the corresponding button-triggered signal according to the specified floor, causing the car to move to the corresponding floor.

[0495] 7. When the elevator dispatch controller detects that the designated car has reached the top floor and stopped after a timeout or changed direction, if the top floor is floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor is not floor f, it sends instruction signals for the k floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. When the elevator dispatch controller detects that the designated car has reached the bottom floor, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. After receiving the signal, the elevator floor controller uses passive dry contact technology to simulate the signal triggered by pressing the corresponding button according to the designated floor, registers the corresponding floor in the car, illuminates the internal call button indicator, and prompts the car to go to the sent floor.

[0496] 8. During operation, the elevator dispatch controller detects whether the car door is open through the elevator status detector. If the car door is detected to be open, it checks whether the floor where the car is located is the floor in the car's task. If so, it means that the car has completed the stop at the corresponding floor in the task and allowed the passenger to enter. The system clears the information of that floor from the dispatch queue and controls the down call button indicator light of the corresponding floor to turn off through the call controller. The above actions are repeated in sequence until all the task floors have been stopped and the elevator has reached the base station floor. Floors that have been removed from the dispatch queue and whose call button indicator lights have turned off will be put back into the dispatch queue for execution if there are new user call requests in the future, following steps 3 and 4.

[0497] 9. During task execution, when the elevator dispatch controller detects that the number of people in the car has reached or exceeded the set full load limit through the car's passenger count system, or when the elevator car is overloaded, it will issue a command signal to the elevator floor control to cancel previously registered floors that have not yet stopped. This allows the elevator's own control system to prevent the car from stopping at subsequent floors and proceed directly to the base floor. For these floors that did not stop due to cancellation, the elevator dispatch controller retains their original order in the dispatch queue, only deleting their "already dispatched" mark or changing the mark to "not dispatched," so that these remaining tasks can be prioritized and assigned to the next available car for response.

[0498] 10. When the elevator dispatch controller detects that the car has stopped at the base station floor and opened the door through the elevator status detector, it indicates that the current trip is complete, and the car can be reassigned to a new task according to step 5. At the same time, if the elevator dispatch controller finds that there are still floors in the task that have not been stopped, the elevator dispatch controller retains the original order of these floors in the waiting queue, but deletes their "already dispatched" mark, or changes the mark to "not dispatched", so that these tasks can be preferentially assigned to the next available car for response.

[0499] 11. Reverse calls from peak-downward floors and calls from non-peak-downward floors will be handled by dispatching designated elevator cars outside of peak-downward scheduling to respond to elevator requests and complete the elevator ride: For some people on peak-downward floors who need to reverse their journey during peak-downward periods, or for people on non-peak-downward floors who need to go down, since they represent a very small portion of the total peak-downward capacity, they can be flexibly configured. Designated elevators in the elevator group can be arranged to shuttle up and down to solve the problem of some people on peak-downward floors needing to go up and people on non-peak-downward floors needing to go up / down during peak-downward periods. When the corresponding call button for a peak-hour downhill floor or an off-peak floor is pressed, the call button is disconnected from the elevator's internal control system by the call controller via a passive dry contact. Upon receiving the call request signal, the call controller detects and receives the signal and sends it to the elevator dispatching system for task assignment. The dispatching system assigns the task to the elevator floor controller of the car designated for use outside of peak-hour downhill dispatch, illuminating the corresponding uphill departure floor. The elevator's internal control system then directs the car designated for use outside of peak-hour downhill dispatch to that floor. Alternatively, the call buttons and indicator lights of the car designated for use outside of peak-hour downhill dispatch are connected to the elevator button panel and remain connected. The elevator's internal control system controls its operation, dispatching it to the corresponding floor to provide elevator service. The call responses of this elevator and the elevator group designated for peak-hour downhill dispatch are independent and do not affect each other.

[0500] like Figure 9 As shown, the elevator operation in this embodiment includes the following steps:

[0501] SE1: Determine whether the system has entered the downhill peak mode based on the passenger count system outside the car and determine which floors are the downhill peak floors;

[0502] SE2: Detects if an outbound call button has been pressed. If so, it determines whether the pressed button is for a peak downbound floor. If it is, it checks if the corresponding floor is in the dispatch queue. If not, it is placed at the end of the dispatch queue, marked "not in dispatch", and the downbound call button indicator light is illuminated. If the pressed button is not for a peak downbound floor, it dispatches a car designated for use outside of peak downbound dispatch for service.

[0503] SE3: Check if there are any peak-hour cars available for dispatching. If yes, proceed to step SE4; otherwise, proceed to step SE7.

[0504] SE4: Take the first k floors from the queue that have not yet been marked as "already in scheduling" (or marked as "not in scheduling"), and mark these k floors as "already in scheduling". The method for determining the value of k is as follows: k is initially 0. For each floor taken, k = k + 1. At the same time, the number of people waiting in the elevator lobby on these floors is accumulated (obtained through the elevator car counting system). When the accumulated number of people is greater than or equal to the maximum passenger capacity of the elevator car, the final k is determined. The highest scheduling floor f among these k floors is taken and registered.

[0505] SE5: Detected that the designated car has timed out and stopped after reaching the top floor or changed direction of travel;

[0506] SE6: If the highest floor reached is floor f, then register the other k-1 floors besides floor f and the base station floor; if the highest floor reached is not floor f, then register k floors and the base station floor; if the elevator dispatch controller detects that the designated car is descending to floor f, then register the other k-1 floors besides floor f and the base station floor, prompting the car to go to the corresponding floor.

[0507] SE7: Detects if a peak-hour car stops or opens its door. If so, it determines if the stopping floor is one of the k floors in the current car dispatch task. If it is, the corresponding floor is removed from the dispatch queue, and the corresponding downlink call button indicator light is turned off. If the stopping floor is not in the current car dispatch task, it determines if it is a base station floor. If it is, the task is completed, and the car is marked as "awaiting dispatch," available for the next round of dispatch. If it is not a base station floor, it continues to wait for door opening detection for further determination. If a base station floor has been reached but there are still floors in the dispatch task that have not been stopped, the "already dispatching" mark for these floors in the dispatch queue is removed, or the mark is changed to "not dispatching." The positions of these floors in the original dispatch queue are not cleared, allowing the corresponding floors to receive new dispatch priority.

[0508] SE8: Detect whether the relevant car is full. If the relevant car is full, cancel the remaining downlink peak floors that the car is scheduled to stop at in this mission, except for the base station floor, so that the car can go directly to the base station floor. At the same time, cancel the "already scheduled" mark of these floors in the scheduling queue, or change the mark to "not scheduled". Do not clear the position of these floors in the original scheduling queue, so that the corresponding floors can be given priority to accept new scheduling.

[0509] A schematic diagram of the elevator capacity distribution system in this embodiment of the invention is shown below. Figure 10 As shown, in this embodiment, the elevator control panel includes a floor selection control panel and an external call control panel. Elevator cars one through N, along with the floor selection control panels, floor selection buttons, and a passenger counting system (inside the car), constitute the elevator's own control system. The elevator's own control system also includes an external call control panel and external call buttons. Assuming the building has M floors and N elevators, in this embodiment, the elevator control panel includes an internal call control panel and an external call control panel. The strategy parameter setter is connected to the elevator dispatch controller, which is connected to the first elevator floor controller through the Nth elevator floor controller. The first elevator floor controller is connected to the first elevator status detector and is also connected to the floor selection control panel and floor selection buttons in elevator car one. The Nth elevator floor controller is connected to the Nth elevator status detector and is also connected to the floor selection control panel and floor selection buttons in elevator car N. The elevator floor controller connects the floor selection buttons and the floor selection control panel, selectively connecting or disconnecting the button switches on the elevator car floor selection buttons from the floor selection control panel.

[0510] Each floor has an elevator lobby, which contains an external call controller and connected external call button panels and buttons. For example, the first-floor lobby has a first-floor external call controller, external call button panel, and external call buttons; the second-floor lobby has a second-floor external call controller, external call button panel, and external call buttons; and the M-floor lobby has an M-floor external call controller, external call button panel, and external call buttons. The first-floor external call controller is connected to the first-floor external call button panel and buttons; the second-floor external call controller is connected to the second-floor external call button panel and buttons; and the M-floor external call controller is connected to the M-floor external call button panel and buttons. The external call controller connects to both the external call buttons and the external call button panel, allowing for selective connection or disconnection of the button switches on the elevator car's external call buttons with the external call button panel.

[0511] The waiting halls are also equipped with a number counting system. For example, the first-floor waiting hall has a number counting system, the second-floor waiting hall has a number counting system, and the M-floor waiting hall has a number counting system.

[0512] The elevator dispatch controller is also connected to the call controller on the first floor, the call controller on the second floor, and the call controller on the M floor. In this embodiment, the call controller input terminal is connected to the call button to receive the call signal from the call button. The elevator floor controller detects and processes the call signal.

[0513] In one embodiment, an elevator dispatching system with an outbound call controller that has detection and passenger count functions is exemplified as follows:

[0514] The system can set the number of people on each floor during peak hours (how many people in the waiting hall are considered a peak downhill floor) and the maximum passenger capacity of the elevator car. In this example, the number of people on a floor during peak hours is 5. If there are 5 or more people on a floor, then that floor is a peak downhill floor, and the maximum passenger capacity of the elevator car is 15 people.

[0515] 1. Take the first k floors from the queue that have not yet been marked as "already in scheduling" or marked as "not in scheduling", and mark these k floors as "already in scheduling". The method for determining the value of k is as follows: the initial value of k is 0, and k = k + 1 for each floor taken. At the same time, accumulate the number of people in the waiting hall of these floors (obtained through the passenger count system outside the car). When the accumulated number of people is greater than the maximum passenger capacity of the car, the final k is determined. Take the highest scheduling floor f among these k floors and register it.

[0516] 2. Based on the floor corresponding to the queue to be dispatched, randomly dispatch elevators that have completed their previous task but have not received the next task, and stop at the floors from high to low.

[0517] 3. If the floor number is still in the dispatch queue, but the elevator has not stopped at that floor, pressing the call button again will not re-order the floor.

[0518] Examples of specific elevator scheduling scenarios in the elevator capacity distribution system of this invention are as follows:

[0519] The planned stops for the southbound peak hours are between floors 27 and 37, with only three car types (A / B / C). During the southbound peak hours, the specific task allocation is as follows:

[0520] Time 1:

[0521] The system obtains the number of people in the waiting hall of each floor by counting people and determines whether each floor has entered the peak downward mode. After entering the peak downward mode, the call buttons of floors 35, 29, 30, 34, 31 and 33 are pressed in sequence, and these floors are all peak downward floors during this period, thus obtaining the queue to be dispatched as shown in Table 5a below.

[0522] Table 5a

[0523] Outbound call order Outbound call floors state 1 35 Not in scheduling 2 29 Not in scheduling 3 30 Not in scheduling 4 34 Not in scheduling 5 31 Not in scheduling 6 33 Not in scheduling

[0524] Time 2:

[0525] At this time, there are two available elevator cars, car A and car B. The elevator dispatch controller will then assign tasks to cars A and B. During task assignment, the number of people in the waiting hall is obtained through the external passenger count system to determine the floor.

[0526] The number of people in the queue to be dispatched and the number of people in the waiting hall are shown in Table 5b. The task allocation is as follows: Task 1: Car A is assigned the task [35, 29]; Task 2: Car B is assigned the task [34, 31, 30]; Car C is executing the previous task.

[0527] It should be noted that the elevator floor controllers of cars A and B receive and register the highest dispatch floor f1 / f2 among the k1 / k2 dispatch floors issued by the elevator dispatch controller. After the elevator dispatch controller detects that the designated car has timed out and stopped or changed direction of travel after reaching the highest floor through the elevator status detector, if the highest floor reached is floor f, it will send the instruction signals for registering the other k1-1 / k2-1 floors and the base station floor to the corresponding elevator floor controller. If the highest floor reached is not floor f, it will send the instruction signals for registering the k1 / k2 floors and the base station floor to the corresponding elevator floor controller. If the elevator dispatch controller detects that the designated car has reached floor f after traveling downward through the elevator status detector, it will send the instruction signals for registering the other k1-1 / k2-1 floors and the base station floor to the corresponding elevator floor controller.

[0528] Where k1 and k2 correspond to the dispatch floors of Task 1 and Task 2 respectively, and the dispatch floors k1 and k2 are the elevator floor controllers registered to car A and car B respectively. The dispatch floors k1 include [35, 29], which are registered to the elevator floor controller of car A; the dispatch floors k2 include [34, 31, 30], which are registered to the elevator floor controller of car B.

[0529] If the highest floor reached by car A is not the highest dispatch floor of k1 (35th floor), then the elevator floor controller of car A will receive and simultaneously register the two dispatch floors [35, 29] plus the base station floor issued by the elevator dispatch controller; if the highest floor reached is 35th floor, then the dispatch floor 29 plus the base station floor will be registered simultaneously.

[0530] If the highest floor reached by car B is not the highest dispatch floor of k2 (34th floor), then the elevator floor controller of car B will receive and simultaneously register the three dispatch floors [34, 31, 30] plus the base station floor issued by the elevator dispatch controller; if the highest floor reached is 34th floor, then the two dispatch floors [31, 30] plus the base station floor will be registered simultaneously.

[0531] Table 5b

[0532] Outbound call order Outbound call floors Number of people in the waiting hall state Assigning cars 1 35 5 Already in the process of scheduling Car A 2 29 15 Already in the process of scheduling Car A 3 30 5 Already in the process of scheduling Car B 4 34 5 Already in the process of scheduling Car B 5 31 6 Already in the process of scheduling Car B 6 33 Not in scheduling

[0533] Time 3:

[0534] During elevator operation, the down-call buttons for floors 27 and 36, two peak-hour floors, were pressed sequentially. After stopping at floors 35 and 29 respectively, car A began its descent towards the base floor. At this point, the down-call button for floor 29 was pressed again, and floor 29 moved to the end of the dispatch queue. Car B had already stopped at floors 34 and 31 and was found to be fully loaded with 15 people. The "already dispatching" marker for the stop at floor 30 in the dispatch queue will be removed or restored to "not dispatching," while the order remains unchanged. The dispatch queue at this time is shown in Table 5c.

[0535] Table 5c

[0536] Outbound call order Outbound call floors state 3 30 Not in scheduling 6 33 Not in scheduling 7 27 Not in scheduling 8 36 Not in scheduling 9 29 Not in scheduling

[0537] Time 4:

[0538] At this time, car C is idle, and the elevator dispatch controller will assign a task to car C. When assigning a task, the number of people in the waiting hall is obtained through the external passenger count system to determine the maximum number of stops k for each trip during peak hours. Assuming that the number of people at that time is as shown in Table 5d, the task assignment is as follows: Task 3: Car C is assigned the task [33, 30, 27];

[0539] Table 5d

[0540]

[0541]

[0542] Time 5:

[0543] During elevator operation, the down-going call buttons for floors 37 and 28 during peak hours are pressed, and car C stops at floor 33. Afterwards, car A stops at the base station floor. The elevator dispatch controller will then reassign a new task to car A. During task assignment, the number of people in the waiting hall is obtained through the external passenger count system to determine the maximum number of stops (k) for each peak-hour trip. Assuming the number of people at that time is as shown in Table 5e, the task assignment is as follows: Task 4: Car A is assigned the task [36, 29];

[0544] Table 5e

[0545] Outbound call order Outbound call floors Number of people in the waiting hall state Assigning cars 3 30 Already in the process of scheduling Car C 7 27 Already in the process of scheduling Car C 8 36 5 Already in the process of scheduling Car A 9 29 10 Already in the process of scheduling Car A 10 37 Not in scheduling 11 28 Not in scheduling

[0546] Time 6:

[0547] When car B arrives at the base station floor and stops, the elevator dispatch controller will reassign a new task to car B. When assigning tasks, the number of people in the waiting hall is obtained through the external passenger count system to determine the maximum number of floors k that the car can stop at during peak hours. Assuming that the number of people at that time is as shown in Table 5f, the task assignment is as follows: Task 5: Car A is assigned the task [37, 28];

[0548] Table 5f

[0549] Outbound call order Outbound call floors Number of people in the waiting hall state Assigning cars 3 30 Already in the process of scheduling Car C 7 27 Already in the process of scheduling Car C 8 36 Already in the process of scheduling Car A 9 29 Already in the process of scheduling Car A 10 37 5 Already in the process of scheduling Car B 11 28 6 Already in the process of scheduling Car B

[0550] 1. If the call button for going up or down is pressed on a floor outside of the down-peak hours, or the call button for going up is pressed on a floor outside of the down-peak hours, a car designated for use outside of the down-peak hours dispatch will be assigned to respond. For example, if the floors outside of the down-peak hours are 32 and 28, and the call button for going down or up is pressed, a car designated for use outside of the down-peak hours dispatch will be assigned for the passenger.

[0551] 2. The floors corresponding to the queue to be dispatched are designated as task floors. Elevators that have completed their previous tasks but have not received the next task are randomly dispatched to respond to the task and stop at floors from high to low.

[0552] 3. If the floor number is still in the dispatch queue, but the elevator has not stopped at that floor, pressing the call button again will not re-order the floor.

[0553] The above description provides a further detailed explanation of the present invention in conjunction with specific / preferred embodiments, and it should not be construed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art, various substitutions or modifications can be made to these described embodiments without departing from the concept of the present invention, and all such substitutions or modifications should be considered within the scope of protection of the present invention. In the description of this specification, the reference to terms such as "an embodiment," "some embodiments," "preferred embodiment," "example," "specific example," or "some examples," etc., indicates that the specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. Without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification and the features of different embodiments or examples. Although the embodiments of the present invention and their advantages have been described in detail, it should be understood that various changes, substitutions, and modifications can be made herein without departing from the scope of protection of the patent application.

Claims

1. An elevator capacity distribution system, characterized in that, include: The strategy parameter setter is used to set the strategy parameters related to the elevator operation strategy and download the strategy parameters to the elevator dispatch controller. The elevator operation strategy enables the designated elevators in the elevator group to be used exclusively to serve the downward peak floors, and to reduce intermediate stops while ensuring that the car is as fully loaded as possible to the base station floor on each downward trip, so as to make full use of the elevator's downward carrying capacity and solve the problem of long waiting time for downward elevators. Elevator status detectors are used to detect the status of the elevator car and send the car status to the elevator floor controller in real time. The elevator floor controller interfaces with the elevator's own control system. It can selectively connect or disconnect the button switches and indicator lights on the floor selection buttons inside the elevator car from the elevator button panel. When disconnected, the passenger's floor selection signal cannot be sent to the elevator's own control system, preventing the elevator from responding to internal call requests. The elevator floor controller can forward the car status sent by the elevator status detector to the elevator dispatch controller and receive the command signals from the elevator dispatch controller. Based on the specified floor, it simulates sending the corresponding button press-triggered signal to cause the car to proceed to the corresponding floor. The elevator dispatch controller receives car status information from the elevator status detector forwarded by the elevator floor controller. It then performs dispatch calculations based on the strategy parameters set by the strategy parameter setter and the car status detected by the elevator status detector. This determines the planned peak-hour floors for the elevator to stop at, and dispatches each car in turn to stop at those peak-hour floors. Once a car meets specified conditions, it proceeds directly to the designated floor, reducing intermediate stops and improving the elevator's downward transport efficiency. Based on the dispatch calculation results, the elevator dispatch controller sends a command signal to the elevator floor controller to press the corresponding floor button, prompting the car to proceed to that floor, thus achieving elevator dispatch. The specified conditions refer to the set full-load conditions. The external call controller interfaces with the elevator's own control system and can selectively connect or disconnect the button switches and button indicator lights on the original elevator external call buttons from the elevator button panel. When disconnected, the button signals of the passenger cannot be sent to the elevator's own control system, so that the elevator cannot respond to external call requests. The strategy includes: if a passenger stops at a peak-hour floor that has already been served, the passenger can only stop at that floor again after all other peak-hour floors that are waiting to be served have been served, so that passengers on all floors, whether high, medium, or low, can take the elevator.

2. The elevator capacity distribution system as described in claim 1, characterized in that, The external call controller can detect the up / down call signal of the external call button and send the signal to the elevator dispatch controller through the communication port. It can also receive the instruction signal from the elevator dispatch controller and send the button indicator light to turn on / off to the corresponding external call button.

3. The elevator capacity distribution system as described in claim 1, characterized in that, It also includes a passenger counting system, which comprises: a passenger counting device inside each elevator car and a passenger counting device in the waiting hall on each floor; the passenger counting device inside each elevator car feeds back the number of passengers inside the car to the elevator floor controller, which then sends the information to the elevator dispatch controller; the passenger counting device in the waiting hall on each floor feeds back the number of passengers in the waiting hall to the elevator dispatch controller; enabling the elevator dispatch controller to perform dispatch calculations by combining the number of passengers in the elevator car and the waiting hall fed back by the passenger counting system.

4. The elevator capacity distribution system as described in claim 1, characterized in that, The external call controller uses passive dry contact technology to interface with the elevator's own control system. When powered on, it disconnects the button switches and indicator lights on the original elevator external call buttons from the elevator button panel, preventing the user's button signals from being sent to the elevator's own control system. At the same time, the light-on / light-off signals sent by the elevator's own control system also prevent the button indicator lights from turning on / off. When there is a power outage, a fault is detected, or there is no need for downhill peak scheduling, it can restore the interrupted signals to the state of connection with the elevator's own control system, that is, restore the elevator to its original system mode.

5. The elevator capacity distribution system as described in claim 1, characterized in that, The elevator floor controller uses passive dry contact technology to interface with the elevator's own control system. When powered on, it can disconnect the button switch on the floor selection button in the original elevator car from the elevator button panel, so that the floor selection signal of the passenger cannot be sent to the elevator's own control system, but is instead detected and processed by the elevator floor controller. In the event of a power outage, a detected fault, or when peak-hour scheduling is not required, the interrupted signal can be restored to a state connected to the elevator's own control system, that is, restored to the original system mode of the elevator.

6. The elevator capacity distribution system as described in claim 1, characterized in that, The strategy parameters include: base station floor and which elevator cars are dedicated to downlink peak scheduling.

7. The elevator capacity distribution system as described in claim 6, characterized in that, The strategy parameters also include: the time period during which the system enters the downhill peak mode, the time period during which each floor is determined to be a downhill peak floor, and the maximum number of floors that the elevator car stops at during peak hours; or they may include the number of people in the waiting hall that corresponds to a floor being determined to be a downhill peak floor, the number of floors in the elevator hall that reach the downhill peak standard when the system automatically enters the downhill peak mode, and the maximum passenger capacity of the elevator car.

8. The elevator capacity distribution system as described in claim 1, characterized in that, The elevator operation strategy conforms to the following model: Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip, η be the fixed time cost of one trip of the elevator, and y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i i = 1, 2, ..., I, T operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, and n is the total travel time of the elevator. r,i This represents the number of people who enter the elevator on the i-th floor during the r-th trip.

9. The elevator capacity distribution system as described in claim 8, characterized in that, The model constraints include: n r,i It is an integer. Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i Let i = 1, 2, ..., I, C be the maximum number of passengers per trip, M be a sufficiently large integer, and T be the maximum number of passengers per trip. operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, S r,i This is an integer input parameter that can take the value 0 or 1, and its meaning is as follows: x r,i It is an integer variable that takes the value of 0 or 1, and the meaning of its value is as follows:

10. An elevator, characterized in that, The elevator includes the elevator capacity distribution system as described in any one of claims 1-9.

11. A method for allocating elevator capacity, characterized in that, The method applicable to the elevator capacity distribution system according to any one of claims 1 to 9 includes the following steps: S1: Receive user input, set the strategy parameters related to elevator operation through the strategy parameter setter, and download the strategy parameters to the elevator dispatch controller; S2: The elevator dispatch controller detects whether it has entered the downhill peak mode. If so, it allocates all designated cars for downhill peak transportation, disconnects the button switch on the outbound call button from the elevator button panel, and disconnects the button switch on the floor selection button inside the car from the elevator button panel, so that the elevator does not respond to the passenger's outbound call. S3: The elevator dispatch controller determines which floors are currently experiencing peak downhill hours based on the elevator operation strategy corresponding to the strategy parameters. S4: The elevator dispatch controller dispatches the elevator cars to determine the planned down-peak floors according to the elevator operation strategy, and dispatches each car used for down-peak transportation in turn to stop at the floors. After the car meets the specified conditions, it goes directly to the base station floor, reducing intermediate stops and improving the efficiency of elevator down-peak transportation.

12. The method as described in claim 11, characterized in that, The strategy parameters related to the strategy mentioned in step S1 include: base station floor, time period when the system enters downlink peak mode, time period when each floor is determined to be a downlink peak floor, which elevator cars are dedicated to downlink peak scheduling, and maximum number of floors per trip for peak elevator cars; or it may also include the number of people in the waiting hall that corresponds to the floor being determined to be a downlink peak floor, the number of floors in the elevator hall that reach the downlink peak standard when the system automatically enters downlink peak mode, and the maximum passenger capacity of the elevator car.

13. The method as described in claim 11, characterized in that, In step S2, the elevator dispatch controller determines to enter the downhill peak mode after detecting that the time has arrived, based on the elevator operation strategy corresponding to the strategy parameters set by the strategy parameter setter.

14. The method as described in claim 11, characterized in that, In step S2, the number of people waiting for the elevator and the number of floors that have reached the peak descending standard are detected by the number of people counting system to determine whether to enter the peak descending mode.

15. The method as described in claim 11, characterized in that, Step S3 includes: determining which floors are the peak downhill floors according to the strategy parameter settings.

16. The method as described in claim 11, characterized in that, Step S3 includes: determining which floors are currently experiencing peak downhill traffic based on the number of people in the single-floor waiting area detected by the headcount system.

17. The method as described in claim 11, characterized in that, Step S4 includes: determining which floors need to be stopped based on which floors are currently peak downhill floors and whether the call button for the corresponding peak downhill floor has been pressed, and sorting these floors to be stopped.

18. The method as described in claim 17, characterized in that, Step S4 includes: the elevator dispatch controller dispatches the identified floors for service in sequence, and simultaneously the outbound call controller outputs a signal to the outbound call button indicator light, causing the outbound call controller to illuminate the outbound call button indicator light; or the elevator dispatch controller sends a signal to the corresponding floor. Floor outbound call control The device sends a command signal to the downlink outbound call button indicator light, illuminating the downlink outbound call button. Call button indicator light.

19. The method as described in claim 11, characterized in that, Step S4 includes: The elevator dispatch controller dispatches the car according to the elevator operation strategy, determines the planned peak downhill floors based on how many floors the car will be fully loaded after stopping, and dispatches each car used for downhill peak transportation to take turns stopping at the floors. After the car meets the full load condition, it goes directly to the base station floor, reducing intermediate stops and improving the efficiency of elevator downhill transportation.

20. The method as described in claim 19, characterized in that, Step S4 includes: The elevator status detector checks whether each car has completed a certain task. If a car has completed the task, it is dispatched to the planned downhill peak floor to transport passengers according to the elevator operation strategy.

21. The method as described in claim 20, characterized in that, If the elevator status detector detects that the operating status of the corresponding car changes from running to timeout and stops, or if the elevator status detector detects that the car with the assigned task has arrived at the base station floor set by the elevator operation strategy and opened the door, then it is determined that a certain task has been completed.

22. The method as described in claim 11, characterized in that, Step S4 includes: For downhill peak floors that have already stopped, they can only stop again after all other downhill peak floors that are waiting for dispatch have been dispatched, so that people on middle, high and low floors can have the opportunity to take the elevator.

23. The method as described in claim 11, characterized in that, Step S4 includes: S41: The floor is placed in the dispatch queue according to the time sequence in which it is detected that it is a peak downhill floor and that floor is not placed in the dispatch queue, or according to the time sequence in which it is detected that it is a peak downhill floor, the outbound call controller detects that a downhill outbound call button has been pressed, and that floor is not placed in the dispatch queue. The dispatch queue refers to the queue of floors with stopping needs. S41: If the elevator dispatch controller detects through the elevator status detector that a car has completed the previous task, it will take the first k floors that have not yet been marked as "already dispatched" from the queue to be dispatched, and mark these floors as "already dispatched". S42: The elevator dispatch controller takes the highest dispatch floor f from these k floors and sends a registration floor f instruction signal to the elevator floor controller of the corresponding car. After receiving the instruction signal, the elevator floor controller simulates the signal triggered by the corresponding button being pressed, causing the car to go to the corresponding floor. S43: When the elevator dispatch controller detects through the elevator status detector that the designated car has stopped after a timeout or changed direction while traveling upwards to the top floor, if the top floor reached is floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. If the top floor reached is not floor f, it sends instruction signals for the k floors and the base station floor to the corresponding elevator floor controller. When the elevator dispatch controller detects through the elevator status detector that the designated car has traveled downwards to floor f, it sends instruction signals for the other k-1 floors (excluding floor f) and the base station floor to the corresponding elevator floor controller. After receiving the instruction signals, the elevator floor controller simulates the signal triggered by pressing the corresponding button, causing the car to travel to the corresponding floor. S44: When the elevator dispatch controller detects that the door of a designated car is open on a floor out of the k floors through the elevator status detector, it considers that the car has stopped at that floor once. The elevator dispatch controller sends a command signal to the call controller of the corresponding floor, outputs a signal to the down call button indicator light, turns off the down call button indicator light, and removes the floor from the dispatch queue. It then continues to determine whether the floor is still a peak down call floor and whether it needs to be placed at the end of the dispatch queue to enter the next round of dispatch.

24. The method as described in claim 23, characterized in that, In step S41, the maximum number of floors the elevator car will stop at during peak hours is set according to the elevator operation strategy specified or the detection results of the passenger count system.

25. The method as described in claim 23, characterized in that, Step S43 includes: during the downlink process, if the passenger counting system detects that the car is full in advance, the downlink peak floors that are not scheduled to stop at the base station floor are removed. At the same time, the position of the canceled floors in the original waiting queue is retained, and the "already in scheduling" mark is removed or the mark is changed to "not in scheduling", so that other cars can stop at these floors first after completing their tasks.

26. The method as described in claim 11, characterized in that, Step S4 includes: if the outbound call controller detects an elevator ride request during the down-peak period that the upbound outbound call button on a down-peak floor has been pressed, or that the upbound / downbound outbound call button on a non-down-peak floor has been pressed, the elevator dispatch controller dispatches a car operation designated for use outside of the down-peak dispatch to respond to the elevator ride request.

27. The method as described in claim 11, characterized in that, The elevator operation strategy conforms to the following model: Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip, η be the fixed time cost of one trip of the elevator, and y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i i = 1, 2, ..., I, T operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, and n is the total travel time of the elevator. r,i This represents the number of people who enter the elevator on the i-th floor during the r-th trip.

28. The method as described in claim 27, characterized in that, The model constraints include: n r,i It is an integer. Where R is the upper limit of the total number of elevator runs, r is the number of elevator runs, and t r Let y be the total running time of the r-th trip. r Let I be the total number of floors, and N be the decision variables. all Let N be the total number of passengers during the downhill peak hours, where N is the number of passengers on the i-th floor. i Let i = 1, 2, ..., I, C be the maximum number of passengers per trip, M be a sufficiently large integer, and T be the maximum number of passengers per trip. operat T is the total time for the elevator doors to open and close. in T represents the average time each passenger takes to enter the elevator. out T represents the average time each passenger spends leaving the elevator. elva (i,j) represents the elevator travel time from floor i to floor j, S r,i This is an integer input parameter that can take the value 0 or 1, and its meaning is as follows: x r,i It is an integer variable that takes the value of 0 or 1, and the meaning of its value is as follows:

29. An elevator, comprising a central controller and a memory, wherein the memory stores a computer program, characterized in that, When the elevator is running, the central controller retrieves the program stored in the memory to implement the method as described in any one of claims 11-28.

Images