Patent Application
20220098003
Aspects of the present disclosure relate generally to systems and methods for controlling elevator traffic flow, and specifically to examples of elevator control systems that dispatch elevator cars based on a travel duration relative to a group of elevator cars.
Elevator systems may generally employ a dispatch methodology based on a necessary travel time to answer a call request. In such systems, an estimated travel time of each elevator car may be determined when a call request is received. An elevator car located near the call location, and having the smallest travel time to the call location, may be dispatched to a location of the call request. In some instances, an elevator car located at another location may have the smallest travel time, such that said elevator car may be dispatched to the call request. The prospective passenger initiating the call request may be instructed to travel to the other location for pick up.
However, assigning elevator cars that are located at distant locations (relative to where the call request originated from) may result in prospective passengers missing the elevator car upon their arrival to the location. This may be due to a duration required for the prospective passenger to travel to the location of the elevator car. As a result, prospective passengers may be required to attempt another call request for a separate elevator car, thereby resulting in decreased traffic flow and greater wait times. Providing a system capable of determining a travel duration between locations when assigning elevator cars may minimize instances of dispatching elevator cars that prospective passengers may not be capable of reaching, thereby increasing traffic flow and decreasing wait times for prospective passengers.
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various exemplary embodiments and together with the description, serve to explain the principles of the disclosure.
Aspects of the disclosure may be implemented in connection with embodiments illustrated in the attached drawings. These drawings show different aspects of the present disclosure and, where appropriate, reference numerals illustrating like structures, components, materials and/or elements in different figures are labeled similarly. It is understood that various combinations of the structures, components, and/or elements, other than those specifically shown, are contemplated and are within the scope of the present disclosure. There are many aspects and embodiments described herein. Those of ordinary skill in the art will readily recognize that the features of a particular aspect or embodiment may be used in conjunction with the features of any or all of the other aspects or embodiments described in this disclosure.
According to an example, a method for dispatching an elevator car includes determining a first duration for each of a plurality of first elevator cars to travel from a current location to a first location; dispatching at least one of the plurality of first elevator cars to the first location when the first duration of the at least one first elevator car is less than a threshold duration and the first duration of the remaining plurality of first elevator cars; determining a second duration for (i) an occupant to travel from the first location to a second location, and (ii) each of a plurality of second elevator cars to travel from the current location to the second location, when the first duration for each of the plurality of first elevator cars exceeds the threshold duration; and dispatching at least one of the plurality of second elevator cars to the second location when the second duration of the at least one second elevator car is less than the threshold duration and the second duration of the remaining plurality of second elevator cars.
According to another example, a system for dispatching an elevator car includes at least one motion controller operably coupled to a plurality of elevator cars, the at least one motion controller is configured to determine a current location of the plurality of elevator cars, wherein the plurality of elevator cars includes a first subset and a second subset; and a dispatch controller operably coupled to the at least one motion controller of the plurality of elevator cars, such that the dispatch controller receives data indicative of the current location of the plurality of elevator cars. The dispatch controller is configured to: determine a first duration for each of the first subset of elevator cars to travel from the current location to a first location; dispatch, in response to the first duration of at least one of the first subset of elevator cars not exceeding a threshold duration, the at least one elevator car of the first subset to the first location; determine, in response to the first duration for each of the first subset of elevator cars exceeding the threshold duration, a second duration for (i) an occupant to travel from the first location to a second location, and (ii) each of the second subset of elevator cars to travel from the current location to the second location; and dispatch, in response to the second duration of at least one of the second subset of elevator cars not exceeding the threshold duration, the at least one elevator car of the second subset to the second location.
According to a further example, a system for controlling traffic flow of a plurality of elevator cars, comprising a processor and a memory storing instructions that, when executed by the processor, causes the processor to perform operations including: determining a first duration for each of a plurality of first elevator cars to travel from a current location to a first location; dispatching at least one of the plurality of first elevator cars to the first location when the first duration of the at least one first elevator car is less than a threshold duration; determining a second duration for (i) an occupant to travel from the first location to a second location, and (ii) each of a plurality of second elevator cars to travel from the current location to the second location, when the first duration for each of the plurality of first elevator cars exceeds the threshold duration; and dispatching at least one of the plurality of second elevator cars to the second location when the second duration of the at least one second elevator car is less than the threshold duration.
The dispatch system of the present disclosure may be in the form of varying embodiments, some of which are depicted by the figures and further described below.
Both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the features, as claimed. As used herein, the terms “comprises,” “comprising,” or other variations thereof, are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such a process, method, article, or apparatus. Additionally, the term “exemplary” is used herein in the sense of “example,” rather than “ideal.” It should be noted that all numeric values disclosed or claimed herein (including all disclosed values, limits, and ranges) may have a variation of +/−10% (unless a different variation is specified) from the disclosed numeric value. Moreover, in the claims, values, limits, and/or ranges mean the value, limit, and/or range+/−10%.
Motion controller 105 may be operably coupled to a transportation unit and configured to detect and transmit motion data of the transportation unit to one or more devices of dispatch system 100, such as, for example, dispatch controller 130. For example, motion controller 105 may measure and record one or more parameters (e.g., motion data) of the transportation unit, including, but not limited to, a current location, a travel direction, a travel speed, a door location, a status, and more. Motion controller 105 may include a computing device having one or more hardware components (e.g., a processor, a memory, a sensor, a communications module, etc.) for generating, storing, and transmitting the motion data. As described in further detail herein, motion controller 105 may be operably coupled to an elevator car located within a building and dispatch system 100 may include at least one motion controller 105 for each elevator car.
Still referring to
As described in further detail herein, call device 110 may be located within a building, and dispatch system 100 may include at least one call device 110 for each floor of the building. Call device 110 may be configured to transmit a message from one or more devices of dispatch system 100 (e.g., dispatch controller 130) identifying an elevator car assigned to arrive at the floor of the building to answer the call request. The message may be communicated by call device 110 via various suitable formats, including, for example, in a written form, an audible form, a graphic form, and more.
Input device 120 may be positioned inside the transportation unit and configured to receive a user input from one or more occupants of the transportation unit. For example, the user input may be indicative of a command requesting redirection of the transportation unit. Input device 120 may be configured to transmit the command to one or more devices of dispatch system 100, such as, for example, dispatch controller 130. Input device 120 may include a keypad, a touchscreen display, a microphone, a button, a switch, etc. As described in detail herein, input device 120 may be located within an elevator car, and dispatch system 100 may include at least one input device 120 for each elevator car in a building. In other embodiments, input device 120 may be omitted entirely from dispatch system 100.
Still referring to
Dispatch controller 130 may be positioned outside the transportation unit and configured to receive data (e.g., motion data, a call request, a redirection command, occupant data, etc.) from one or more devices of dispatch system 100. Dispatch controller 130 may be further configured to determine at least one transportation unit of a plurality of transportation units to dispatch in response to a call request received from a prospective passenger seeking transportation. Dispatch controller 130 may include a computing device (see
Referring now to
Working environment 200 may further include one or more elevator shafts with at least one elevator car positioned within each elevator shaft. In the example, working environment 200 includes a first elevator shaft 202 with at least one first elevator car 210, a second elevator shaft 212 with at least one second elevator car 220, and a third elevator shaft 222 with at least one third elevator car 230. Each elevator shaft 202, 212, 222 may be located at a different location on each of the plurality of floors 204A-204D. Stated differently, first elevator shaft 202 may be located at a first location “A,” second elevator shaft 212 may be located at second location “B” that is different than the first location “A,” and third elevator shaft 222 may be located at a third location “C” that is different than the first location “A” and second location “B,” on each of the plurality of floors 204A-204D. Although not shown, it should be appreciated that working environment 200 may include additional (e.g., a plurality) elevator shafts, elevator cars, and locations at which said elevator shafts and elevator cars are located. Accordingly, it should be appreciated that working environment 200 may include a plurality of first elevator shafts 202 including a plurality of first elevator cars 210; a plurality of second elevator shafts 212 including a plurality of second elevator cars 220; a plurality of third elevator shafts 222 including a plurality of third elevator cars 230; and more.
Each elevator car 210, 220, 230 may be coupled to a pulley system 208 configured to move elevator cars 210, 220, 230 within elevator shafts 202, 212, 222 and relative to floors 204A-204D. It should be understood that pulley system 208 may include various mechanical and/or electrical mechanisms for moving elevator cars 210, 220, 230 within elevator shafts 202, 212, 222, including but not limited to, a motor, a cable, a counterweight, a sheave, etc.
Still referring to
Each floor 204A-204D may include one or more call devices 110 and access doors 206 at a location of each elevator shaft 202, 212, 222 on said floor 204A-204D. Access doors 206 may provide accessibility to elevator cars 210, 220, 230 when an elevator door 207 of elevator car 210, 220, 230 is aligned with the respective floor 204A-204D. Call device 110 may be configured to receive a user input from one or more prospective occupants 20 located at one of the plurality of locations on one of floors 204A-204D. For example, call device 110 may be configured to receive a user input indicative of a call requesting transportation via at least one of elevator cars 210, 220, 230. Call device 110 may be configured to transmit the call request to dispatch controller 130, which may include data indicative of a current location within working environment 200 from which the call request originated from (e.g., the first location “A” on first floor 204A). The call request may further include data indicative of a destination location within working environment 200 to which the prospective passenger is seeking transportation to (e.g., fourth floor 204D).
Still referring to
For example, as seen in
Referring now to
Processor 132 may include any computing device capable of executing machine-readable instructions, which may be stored on a non-transitory computer-readable medium, such as, for example, memory 138. By way of example, processor 132 may include a controller, an integrated circuit, a microchip, a computer, and/or any other computer processing unit operable to perform calculations and logic operations required to execute a program. As described in detail herein, processor 132 is configured to perform one or more operations in accordance with the instructions stored on memory 138, such as, for example, dispatch logic 140.
Communications module 134 may facilitate communication between dispatch controller 130 and the one or more other devices of dispatch system 100, such as, for example, via network 115. User interface 136 may include one or more input and output devices, including one or more input ports and one or more output ports. User interface 136 may include, for example, a keyboard, a mouse, a touchscreen, etc., as input ports. User interface 136 may further include, for example, a monitor, a display, a printer, etc. as output ports. User interface 136 may be configured to receive a user input indicative of various commands, including, but not limited to, a command defining and/or adjusting the threshold duration 148 stored in memory 138, and more.
Still referring to
As described further herein, occupant data 144 may include a real-time number of occupants 10 detected within a cabin of each elevator car 210, 220, 230 by counter device 125. Call assignment data 146 may include a call request received from a prospective occupant 20 at one of the plurality of floors 204A-204D, for transportation by at least of the plurality of elevator cars 210, 220, 230. Dispatch controller 130 may be configured to store the occupant data 144 in memory 138 and associate the number of occupants 10 with a corresponding elevator car 210, 220, 230. Dispatch controller 130 may be further configured to store the call assignment data 146 in memory 138 to determine a current number of stops assigned to each elevator car 210, 220, 230. As described further herein, dispatch controller 130 may be configured to determine a minimum travel duration for each of the plurality of elevator cars 210, 220, 230 based on at least one or more of the motion data 142, the occupant data 144, and the call assignment data 146.
Further, memory 138 may include a non-transitory computer readable medium that stores machine-readable instructions thereon, such as, dispatch logic 140. In one example, dispatch logic 140 may include executable instructions that allow dispatch system 100 to determine which elevator car from the plurality of elevator cars 210, 220, 230 to dispatch in response to receiving a call request at the first location “A” for transportation to a destination location. Dispatch logic 140 may facilitate determining an occupant capacity of each elevator car 210, 220, 230 based on a number of occupants physically present within each elevator car 210, 220, 230. Dispatch logic 140 may further facilitate the determination of a minimum duration (e.g., duration data 150) for each of the plurality of elevator cars 210, 220, 230 to travel to a location based on one or more of the motion data 142, occupant data 144, and/or call assignment data 146. As described in further detail herein, dispatch system 100 may be configured to determine at least one elevator car 210, 220, 230 having the least duration (e.g., duration data 150) to travel to a first location in response to a call request from a prospective occupant 20.
Referring now to
At step 302, dispatch system 100 may receive a call request at the first location “A” of a plurality of locations within working environment 200. The call request may be initiated in response to a prospective occupant 20 actuating call device 110 at the first location “A,” such as, for example, on first floor 204A and adjacent to a plurality of first elevator shafts 202. Call device 110 may transmit the call request to dispatch controller 130 via network 115, and the call request may include data indicative of the first location “A” from which the call request originated. The call request may further include data indicative of a destination location (e.g., fourth floor 204D) within working environment 200 to which the prospective occupant 20 seeks to travel.
At step 304, with the call request originating from first floor 204A and adjacent to the plurality of first elevator shafts 202, dispatch controller 130 may retrieve motion data 142 from a corresponding motion controller 105 of a plurality of first elevator cars 210 located within the plurality of first elevator shafts 202. Dispatch controller 130 may be configured to determine various movement parameters of the plurality of first elevator cars 210 from the motion data 142, such as, for example, a current location of each first elevator car 210 relative to a respective first elevator shaft 202, a current travel direction of each first elevator car 210, and a current travel speed of each first elevator car 210.
It should be understood that, in response to determining one or more first elevator cars 210 are not traveling toward the first location “A,” dispatch controller 130 may be configured to disregard the particular first elevator car 210 from further consideration. Stated differently, dispatch controller 130 may determine that any elevator car traveling in a different direction than toward the first location “A” (relative to the current location of the elevator car) may not be an optimal elevator car to answer the call request. In the example, working environment 200 includes first elevator car 210 positioned between fourth floor 204D and third floor 204C, and moving toward first floor 204A.
In some embodiments, dispatch controller 130 may be further configured to determine whether a current location of the plurality of first elevator cars 210 is located prior to the first location “A,” or whether first elevator cars 210 have moved beyond the first location “A.” Stated differently, dispatch controller 130 may determine that any elevator car that is currently positioned beyond the first location “A” may not be an optimal elevator car to answer the call request. In response to determining one or more of the plurality of first elevator cars 210 are not located before the first location “A,” dispatch controller 130 may be configured to disregard said first elevator cars 210 from further consideration. In the example, as seen in
Still referring to
It should further be appreciated that any calls previously assigned to first elevator cars 210, and which do not include a location positioned between the current location and the first location “A,” do not form an intermediate stop. Accordingly, dispatch controller 130 may be configured to disregard any prior calls assigned to first elevator cars 210, and which have a (pick up) location after the first location “A,” when determining the number of calls at step 306. In the example, as seen in
Still referring to
By further example, dispatch controller 130 may determine that the minimum duration required for each first elevator car 210 to travel to the first location “A” increases based on the number of existing calls assigned to the first elevator car 210. Stated differently, dispatch controller 130 may assess the number of stops assigned to each first elevator car 210, and positioned between a current location and the first location “A,” when determining the minimum duration for each first elevator car 210. For example, dispatch controller 130 may compute a predefined increment (e.g., duration data 150) to the minimum duration for each stop assigned to a particular first elevator car 210. The predefined increment may be programmed in memory 138, and may include various suitable values ranging from about 1 second to about 120 seconds, and particularly about 60 seconds. In some embodiments, a value of the predefined increment may be selectively modified by a user of dispatch system 100, such as via user interface 136.
At step 310, dispatch controller 130 may be configured to compare the minimum duration of the plurality of first elevator cars 210 to the threshold duration 148. As described in detail above, the threshold duration 148 may define a maximum allotted duration for an elevator car to travel from a respective current location to the first location “A.” In other words, elevator cars determined to have a minimum duration that exceeds the threshold duration 148 may not be an optimal elevator car to answer the call request. In response to determining two or more of the plurality of first elevator cars 210 have a minimum duration that is less than the threshold duration 148 at step 310, dispatch controller 130 may be configured to determine a number of occupants 10 located within each of the two or more first elevator cars 210 at step 312.
For example, dispatch controller 130 may be configured to determine the number of occupants 10 within each first elevator car 210 (having a minimum duration less than the threshold duration 148) by retrieving occupant data 144 from a respective counter device 125 of each first elevator car 210. In some embodiments, counter device 125 may be configured to detect a total number of occupants 10 and/or objects 12 located within first elevator cars 210 (see
Still referring to
In the example, the plurality of first elevator cars 210 may include a substantially similar size and/or shape such that the maximum occupant capacities of each are relatively similar. In other examples, the plurality of first elevator cars 210 may include varying sizes and/or shapes, such that the maximum occupant capacity of each may differ relative to one another. In the example, first elevator car 210 may include a total occupancy of one occupant and a maximum occupant capacity of six occupants. Dispatch controller 130 may be configured to determine first elevator car 210 includes an occupancy ratio of approximately 1:6 (e.g., approximately 16.67%).
Still referring to
In instances where two or more first elevator cars 210 include a similar occupancy ratio relative to one another, dispatch controller 130 may be configured to compare the minimum duration of each to one another to determine an optimal first elevator car 210 to dispatch. For example, dispatch controller 130 may assign the call request to the first elevator car 210 having the smallest minimum duration to travel to the first location “A.” In other embodiments, dispatch controller 130 may compare the minimum durations of the plurality of first elevator cars 210 to one another even when the occupancy ratios of first elevator cars 210 vary relative to one another. In this instance, dispatch controller 130 may be configured to dispatch at least one first elevator car 210 having the shortest minimum duration despite another one of the plurality of first elevator cars 210 having a greater maximum available occupant capacity.
It should be appreciated that, in instances where dispatch controller 130 determines only one first elevator car 210 has a minimum duration that is less than the threshold duration 148 (at step 310), dispatch controller 130 may forgo performance of steps 312 to 316. In this instance, the first elevator car 210 identified at step 310 may be dispatched to the first location “A” at step 318. In other embodiments, method 300 may omit steps 312 to 316 entirely such that dispatch controller 130 may be configured to dispatch the at least one first elevator car 210 having the shortest minimum duration, at step 318.
Dispatch controller 130 may be configured to communicate with call device 110 to transmit a message to the prospective occupant 20 at the first location “A” (e.g., first floor 204A). For example, dispatch controller 130 may communicate an identification of the first elevator car 210 dispatched to the first location “A.” In other embodiments, dispatch controller 130 may identify the first elevator shaft 202 of the plurality of first elevator shafts 202 from which the first elevator car 210 may arrive from. The message may be transmitted via call device 110 in various suitable formats, including, for example, via a display (e.g., a written form, a graphic form, etc.), a speaker (e.g., an audible form), and more.
Returning to step 310, in response to determining each of the plurality of first elevator cars 210 has a travel duration that exceeds the threshold duration 148, dispatch controller 130 may be configured to disregard the plurality of first elevator cars 210 from further consideration. At step 320, dispatch controller 130 may retrieve motion data 142 from a corresponding motion controller 105 of the plurality of elevator cars 220, 230 located at various locations in working environment 200 other than the first location “A.” That is, dispatch controller 130 may consider the plurality of second elevator cars 220 (e.g., located adjacent to the second location “B”) and third elevator cars 230 (e.g., located adjacent to the third location “C”) upon determining that none of the plurality of first elevator cars 210 includes a travel duration that is less than the threshold duration 148.
Dispatch controller 130 may consider the plurality of elevator cars 220, 230 despite second elevator cars 220 and third elevator cars 230 being located further from the first location “A” (e.g., a location within working environment 200 proximate to where the call request originated from) than first elevator cars 210. Dispatch controller 130 may be configured to determine various movement parameters of the plurality of second elevator cars 220 from the motion data 142, such as, for example, a current location of each second elevator car 220 relative to a respective second elevator shaft 212, a current travel direction of each second elevator car 220, a current travel speed of each second elevator car 220, and more. Dispatch controller 130 may further determine similar movement parameters of the plurality of third elevator cars 230.
In response to determining one or more second or third elevator cars 220, 230 are not traveling toward the first floor 204A, dispatch controller 130 may be configured to disregard the particular elevator cars 220, 230 from further consideration. Dispatch controller 130 may be further configured to determine whether a current location of the plurality of second and third elevator cars 220, 230 are located prior to first floor 204A. In the example, working environment 200 includes second elevator car 220 stationary at fourth floor 204D, and third elevator car 230 stationary at second floor 204B, such that dispatch controller 130 may determine that second elevator car 220 and third elevator car 230 are located before first floor 204A.
Still referring to
At step 324, dispatch controller 130 may be configured to analyze the motion data 142 (step 322) and the call assignment data 146 (step 324) of the plurality of elevator cars 220, 230 to determine a minimum duration for each elevator car 220, 230 to travel from a respective current location to the second and/or third location “B, C.” For example, dispatch controller 130 may analyze a travel distance between a respective current location of each elevator car 220, 230 and the corresponding second and/or third location “B, C” when determining the minimum duration. Dispatch controller 130 may further analyze a travel speed of each elevator car 220, 230 when determining the minimum duration. By further example, dispatch controller 130 may determine an additional duration required to travel to the respective location “B, C,” when elevator car 220, 230 includes a preexisting call assignment. Dispatch controller 130 may assess the number of stops assigned to each elevator car 220, 230 when determining the minimum duration for each elevator car 220, 230.
Still referring to
Dispatch controller 130 may further include data indicative of the time required for prospective passengers 20 to travel between the first location “A” and the third location “C,” at which third elevator cars 230 are positioned, based on the distance between the first location “A” and the third location “C.” Dispatch controller 130 may be configured to consider the distance required for the prospective occupant 20 to travel between locations “A, C” when determining the minimum duration (e.g., a third duration) for each of the plurality of third elevator cars 230.
Accordingly, dispatch controller 130 may be configured to modify (e.g., increase) the minimum duration of the plurality of elevator cars 220, 230 based on the distance between first location “A” and the respective second location “B” or third location “C” when determining the minimum duration for elevator cars 220, 230. In other embodiments, dispatch controller 130 may be configured to compute the distance between the first location “A” and at least one of the second location “B” or the third location “C”.
At step 328, dispatch controller 130 may be configured to compare the minimum duration of the plurality of elevator cars 220, 230 to the threshold duration 148. In response to determining two or more of the plurality of elevator cars 220, 230 have a minimum duration that is less than the threshold duration 148 at step 328, dispatch controller 130 may be configured to determine the number of occupants 10 within each of the two or more elevator cars 220, 230 at step 330. For example, dispatch controller 130 may be configured to determine the number of occupants 10 within each elevator car 220, 230 (having a minimum duration less than the threshold duration 148) by retrieving occupant data 144 from the respective counter device 125 of each elevator car 220, 230.
Still referring to
At step 334, dispatch controller 130 may be configured to determine at least one of the plurality of elevator cars 220, 230 having a maximum occupant capacity that is greater than the remaining elevator cars 220, 230. Dispatch controller 130 may compare the occupancy ratios of each of the plurality of elevator cars 220, 230 to determine at least one second elevator car 220 or third elevator car 230 having the maximum available occupant capacity. Dispatch controller 130 may assign the call request received at step 302 to the elevator car 220, 230 (having a travel duration that is less than the threshold duration 148) that includes the maximum available occupant capacity. At step 336, dispatch controller 130 may dispatch the elevator car 220, 230 having the maximum available occupant capacity to the corresponding location “B, C” on first floor 204A.
In instances where two or more second elevator cars 220 and/or third elevator cars 230 include a similar occupancy ratio relative to one another, dispatch controller 130 may compare the minimum duration of each to determine an optimal elevator car 220, 230 to dispatch. For example, dispatch controller 130 may dispatch the second elevator car 220 having the smallest minimum duration for traveling to the second location “B,” or the third elevator car 230 having the smallest minimum duration for traveling to the third location “C.” In other embodiments, dispatch controller 130 may compare the minimum durations of the plurality of elevator cars 220, 230 to one another even when the occupancy ratios of elevator cars 220, 230 vary relative to one another. In this instance, dispatch controller 130 may be configured to dispatch at least one elevator car 220, 230 having the shortest minimum duration despite another one of the plurality of elevator cars 220, 230 having a greater maximum available occupant capacity.
It should be appreciated that, in instances where dispatch controller 130 determines only one second elevator car 220 or third elevator car 230 has a minimum duration that is less than the threshold duration 148 (at step 328), dispatch controller 130 may forgo performance of steps 330 to 334. In this instance, the elevator car 220, 230 identified at step 328 may be dispatched at step 336. In other embodiments, method 300 may omit steps 330 to 334 entirely such that dispatch controller 130 may be configured to dispatch the at least second elevator car 220 or third elevator car 230 having the shortest minimum duration, at step 336.
Returning to step 328, in response to determining each of the plurality of second elevator cars 220 and third elevator cars 230 have a travel duration that exceeds the threshold duration 148, dispatch controller 130 may be configured to disregard the plurality of second elevator cars 220 and third elevator cards 230 from further consideration. In this instance, dispatch controller 130 may assign the call request received at step 302 to one of the plurality of first elevator cars 210, despite each of the first elevator cars 210 having a minimum duration that exceeds the threshold duration 148. In this instance, dispatch controller 130 may determine the number of occupants present (step 312), the occupancy ratio (step 314), and the maximum available occupancy ratio (step 316) of each of the plurality of first elevator cars 210. At step 318, dispatch controller 130 may dispatch the first elevator car 210 of the plurality of first elevator cars 210 having the maximum available occupancy. Alternatively, dispatch controller 130 may omit steps 312 to 316, and dispatch the at least one first elevator car 210 having the shortest minimum duration, at step 318.
All technical and scientific terms used herein have the same meaning as commonly understood to one of ordinary skill in the art to which this disclosure belongs unless clearly indicated otherwise. As used herein, the singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.
The above description is illustrative and is not intended to be restrictive. One of ordinary skill in the art may make numerous modifications and/or changes without departing from the general scope of the disclosure. For example, and as has been described, the above-described embodiments (and/or aspects thereof) may be used in combination with each other. Additionally, portions of the above-described embodiments may be removed without departing from the scope of the disclosure. In addition, modifications may be made to adapt a particular situation or material to the teachings of the various embodiments without departing from their scope. Many other embodiments will also be apparent to those of skill in the art upon reviewing the above description.
This application claims the benefit of priority from U.S. Provisional Application No. 63/084,452, filed on Sep. 28, 2020, which is incorporated by reference herein in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63084452 | Sep 2020 | US |
