130 shown and described herein may be integral with one or more of motion controller 105, call device 110, input device 120, and/or counter device 125.

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 FIG. 4, memory 138 may include various programming algorithms and data that support an operation of dispatch system 100. Memory 138 may include any type of computer readable medium suitable for storing data and algorithms, such as, for example, random access memory (RAM), read only memory (ROM), a flash memory, a hard drive, and/or any device capable of storing machine-readable instructions. Memory 138 may include one or more data sets, including, but not limited to, motion data 142 received from motion controller 105, occupant data 144 captured from counter device 125, call assignment data 146 and duration data 150 for each of the plurality of elevator cars 210, 220, 230, and the like. Memory 138 may further include a threshold duration 148 that may be preprogrammed and/or adjustable by a user of dispatch system 100, such as, for example, via user interface 136.

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 FIG. 5, an example method 300 of using dispatch system 100 to determine a travel duration of a plurality of elevator cars and to dispatch an elevator car having the shortest travel duration is depicted. It should be understood that the steps shown and described herein, and the sequence in which they are presented, are merely illustrative such that additional and/or fewer steps may be included in various arrangements without departing from a scope of this disclosure.

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 FIG. 2, first elevator car 210 is positioned between fourth floor 204D and third floor 204C, such that dispatch controller 130 may determine that first elevator car 210 is currently located before first floor 204A (e.g., the first location “A”).

Still referring to FIG. 5, at step 306, dispatch controller 130 may be configured to determine a number of calls assigned to each of the plurality of first elevator cars 210 (e.g., by dispatch controller 130) and that have a (pick up) location positioned between a current location of each first elevator car 210 and the first location “A.” Stated differently, dispatch controller 130 may determine how many, if any, intermediate stops each first elevator car 210 is expected to have between its current location and the first location “A” (e.g., first floor 204A). It should be understood that the number of calls previously assigned to each first elevator car 210 is relative to when the call request (step 302) is received by dispatch controller 130.

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 FIG. 2, first elevator car 210 may include a previously-assigned call at third floor 204C such that dispatch controller 130 may determine that first elevator car 210 includes one stop between the current location of first elevator car 210 and first floor 204A (e.g., the first location “A”).

Still referring to FIG. 5, at step 308, dispatch controller 130 may be configured to analyze the motion data 142 (step 304) and the call assignment data 146 (step 306) collected for the plurality of first elevator cars 210 to determine a minimum duration (e.g., a first duration) for each first elevator car 210 to travel from a respective current location to the first location “A.” For example, dispatch controller 130 may analyze a travel distance between a current location of each first elevator car 210 and the first location “A” when determining the minimum duration. Dispatch controller 130 may further analyze a travel speed of each first elevator car 210 when determining the minimum duration.

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 FIG. 3). Thus, dispatch controller 130 may consider one or more objects 12 detected by counter device 125 when determining the number of occupants 10 at step 312. Each counter device 125 may transmit a signal to dispatch controller 130 via network 115 indicative of the occupant data 144 for the respective first elevator car 210.

Still referring to FIG. 5, at step 314, dispatch controller 130 may be configured to determine an occupancy ratio of each of the plurality of first elevator cars 210 based on at least the number of occupants 10 within the elevator car (step 312) and a maximum occupant capacity of each elevator car. In some embodiments, a maximum occupant capacity of the plurality of first elevator cars 210 may be communicated to dispatch controller 130 from counter device 125 via network 115. In other embodiments, dispatch controller 130 may store the maximum occupant capacity in memory 138 for each of the plurality of first elevator cars 210. It should be appreciated that a size and/or shape of the cabin of each of the plurality of first elevator cars 210 may be determinative of a maximum occupant capacity.

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 FIG. 5, at step 316, dispatch controller 130 may be configured to determine at least one of the plurality of first elevator cars 210 having a maximum occupant capacity that is greater than the remaining plurality of first elevator cars 210. Dispatch controller 130 may compare the occupancy ratios of each of the plurality of first elevator cars 210 to determine at least one first elevator car 210 having the maximum available occupant capacity. Dispatch controller 130 may assign the call request received at step 302 to the first elevator car 210 of the plurality of first elevator cars 210 (having a travel duration that is less than the threshold duration 148) that includes the maximum available occupant capacity. At step 318, dispatch controller may be configured to dispatch the at least one first elevator car 210 to the first location “A.”

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 FIG. 5, at step 322, dispatch controller 130 may be configured to determine how many, if any, intermediate stops second elevator cars 220 are expected to have between a respective current location and the second location “B” (e.g., on first floor