Patent Description:
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.

<CIT> discloses an elevator swing operation system for use in a building includes a plurality of floors with landings that are grouped into zones. The elevator cars are allocated to service the zones with a default allocation setup or configuration. The allocation of elevator cars to zones can be modified by moving an elevator car from one zone to another in response to a maximum estimated time to arrival being exceeded and a maximum number of elevator cars allowed to change zones not being exceeded. Furthermore, the default configuration or allocation can be restored when the system is in swing operation, an elevator car is parked, and a minimum time for receiving no calls has been exceeded.

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 embodiment of the invention, a method for dispatching an elevator car according to claim <NUM> is presented.

According to a non-claimed 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 non-claimed 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 +/- <NUM>% (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 +/-<NUM>%.

<FIG> shows an exemplary dispatch system <NUM> that may include motion controller <NUM>, call device <NUM>, input device <NUM>, counter device <NUM>, and dispatch controller <NUM>. The one or more devices of dispatch system <NUM> may communicate with one another across a network <NUM> and in any arrangement. For example, the devices of dispatch system <NUM> may be communicatively coupled to one another via a wired connection, a wireless connection, or the like. In some embodiments, network <NUM> may be a wide area network ("WAN"), a local area network ("LAN"), personal area network ("PAN"), etc. Network <NUM> may further include the Internet such that information and/or data provided between the devices of dispatch system <NUM> may occur online (e.g., from a location remote from other devices or networks coupled to the Internet). In other embodiments, network <NUM> may utilize Bluetooth® technology and/or radio waves frequencies.

Motion controller <NUM> 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 <NUM>, such as, for example, dispatch controller <NUM>. For example, motion controller <NUM> 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 <NUM> 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 <NUM> may be operably coupled to an elevator car located within a building and dispatch system <NUM> may include at least one motion controller <NUM> for each elevator car.

Still referring to <FIG>, call device <NUM> may be positioned outside the transportation unit and configured to receive a user input from one or more prospective occupants for accessing the transportation unit. For example, the user input may be indicative of a call requesting transportation from the transportation unit. Call device <NUM> may be configured to transmit the call request to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. Call device <NUM> may include a keypad, a touchscreen display, a microphone, a button, a switch, etc. Call device <NUM> may be further configured to receive a user input indicative of a current location of the call request (e.g., a first location) and/or a destination location from a plurality of locations.

As described in further detail herein, call device <NUM> may be located within a building, and dispatch system <NUM> may include at least one call device <NUM> for each floor of the building. Call device <NUM> may be configured to transmit a message from one or more devices of dispatch system <NUM> (e.g., dispatch controller <NUM>) 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 <NUM> via various suitable formats, including, for example, in a written form, an audible form, a graphic form, and more.

Input device <NUM> 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 <NUM> may be configured to transmit the command to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. Input device <NUM> may include a keypad, a touchscreen display, a microphone, a button, a switch, etc. As described in detail herein, input device <NUM> may be located within an elevator car, and dispatch system <NUM> may include at least one input device <NUM> for each elevator car in a building. In other embodiments, input device <NUM> may be omitted entirely from dispatch system <NUM>.

Still referring to <FIG>, counter device <NUM> may be positioned inside the transportation unit and configured to detect and transmit occupant data of the transportation unit to one or more devices of dispatch system <NUM>, such as, for example, dispatch controller <NUM>. For example, counter device <NUM> may measure and record a number of objects located within the transportation unit, including, but not limited to, an occupant, a personal belonging, a luggage, a baggage, and more. Counter device <NUM> may include an optical system facing an interior of the transportation unit, such as, for example, a sensor, a camera, a light beam, an infrared detector, etc. As described in further detail herein, counter device <NUM> may be coupled to an elevator car that is located within a building, and dispatch system <NUM> may include at least one counter device <NUM> for each elevator car of the building.

Dispatch controller <NUM> 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 <NUM>. Dispatch controller <NUM> 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 <NUM> may include a computing device (see <FIG>) operable to perform one or more processes (see <FIG>) for dispatching at least one transportation unit with the smallest duration to pick up a prospective passenger. As described in further detail herein, dispatch controller <NUM> may be operably coupled to a plurality of elevator cars located within a building, and dispatch system <NUM> may include at least one dispatch controller <NUM> for each building.

Referring now to <FIG>, dispatch system <NUM> may be utilized in a working environment <NUM>, such as a building (e.g., a facility, a factory, a store, a school, a house, an office, and various other structures). In the example, the transportation unit may include one or more elevator cars within the building. It should be appreciated that working environment <NUM> is merely illustrative such that dispatch system <NUM> may be utilized in various other suitable environments than those shown and described herein without departing from a scope of this disclosure. In the example, working environment <NUM> may include a plurality of floors defining a plurality of locations within the building, such as first floor 204A, second floor 204B, third floor 204C, and fourth floor 204D. It should be appreciated that, in other embodiments, the building of working environment <NUM> may include additional and/or fewer floors.

Working environment <NUM> may further include one or more elevator shafts with at least one elevator car positioned within each elevator shaft. In the example, working environment <NUM> includes a first elevator shaft <NUM> with at least one first elevator car <NUM>, a second elevator shaft <NUM> with at least one second elevator car <NUM>, and a third elevator shaft <NUM> with at least one third elevator car <NUM>. Each elevator shaft <NUM>, <NUM>, <NUM> may be located at a different location on each of the plurality of floors 204A-204D. Stated differently, first elevator shaft <NUM> may be located at a first location "A," second elevator shaft <NUM> may be located at second location "B" that is different than the first location "A," and third elevator shaft <NUM> 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 <NUM> 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 <NUM> may include a plurality of first elevator shafts <NUM> including a plurality of first elevator cars <NUM>; a plurality of second elevator shafts <NUM> including a plurality of second elevator cars <NUM>; a plurality of third elevator shafts <NUM> including a plurality of third elevator cars <NUM>; and more.

Each elevator car <NUM>, <NUM>, <NUM> may be coupled to a pulley system <NUM> configured to move elevator cars <NUM>, <NUM>, <NUM> within elevator shafts <NUM>, <NUM>, <NUM> and relative to floors 204A-204D. It should be understood that pulley system <NUM> may include various mechanical and/or electrical mechanisms for moving elevator cars <NUM>, <NUM>, <NUM> within elevator shafts <NUM>, <NUM>, <NUM>, including but not limited to, a motor, a cable, a counterweight, a sheave, etc..

Still referring to <FIG>, each elevator car <NUM>, <NUM> may include at least one motion controller <NUM> operably coupled to pulley system <NUM>, such as, for example, via a wireless connection and/or a wired connection <NUM>. Motion controller <NUM> may be configured to measure motion data from elevator cars <NUM>, <NUM> by detecting a relative movement of pulley system <NUM>. Each elevator car <NUM>, <NUM> may further include at least one input device <NUM> positioned within a cabin of elevator car <NUM>, <NUM> for receiving a user input from one or more occupants <NUM> located within the cabin.

Each floor 204A-204D may include one or more call devices <NUM> and access doors <NUM> at a location of each elevator shaft <NUM>, <NUM>, <NUM> on said floor 204A-204D. Access doors <NUM> may provide accessibility to elevator cars <NUM>, <NUM>, <NUM> when an elevator door <NUM> of elevator car <NUM>, <NUM>, <NUM> is aligned with the respective floor 204A-204D. Call device <NUM> may be configured to receive a user input from one or more prospective occupants <NUM> located at one of the plurality of locations on one of floors 204A-204D. For example, call device <NUM> may be configured to receive a user input indicative of a call requesting transportation via at least one of elevator cars <NUM>, <NUM>, <NUM>. Call device <NUM> may be configured to transmit the call request to dispatch controller <NUM>, which may include data indicative of a current location within working environment <NUM> 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 <NUM> to which the prospective passenger is seeking transportation to (e.g., fourth floor 204D).

Still referring to <FIG>, each elevator car <NUM>, <NUM>, <NUM> may further include at least one counter device <NUM> positioned within a cabin. Counter device <NUM> may be positioned along an inner wall (e.g., a ceiling) of each elevator car <NUM>, <NUM>, <NUM> and configured to detect a number of occupants <NUM> within the cabin. In some embodiments, counter device <NUM> may be operable to distinguish between one or more objects detected within elevator cars <NUM>, <NUM>, <NUM>.

For example, as seen in <FIG>, counter device <NUM> may be configured to detect items present within the cabin and occupying a capacity of elevator cars <NUM>, <NUM>, <NUM> (e.g., occupants <NUM>, ancillary objects <NUM>, etc.) and items within the cabin that may not occupy a capacity of elevator cars <NUM>, <NUM>, <NUM> (e.g., rails <NUM>, etc.). Counter device <NUM> may measure a number of items detected within elevator cars <NUM>, <NUM>, <NUM> and record such measurements as occupant data. As discussed further herein, counter device <NUM> may be configured to transmit occupant data (e.g., occupant data <NUM>) for each elevator car <NUM>, <NUM>, <NUM> to dispatch controller <NUM> via network <NUM>.

Referring now to <FIG>, dispatch controller <NUM> may include a computing device incorporating a plurality of hardware components that allow dispatch controller <NUM> to receive data (e.g., motion data, call requests, commands, occupant data, etc.), process information (e.g., occupant capacity), and/or execute one or more processes (see <FIG>). Illustrative hardware components of dispatch controller <NUM> may include at least one processor <NUM>, at least one communications module <NUM>, a user interface <NUM>, and at least one memory <NUM>. In some embodiments, dispatch controller <NUM> may include a computer, a mobile user device, a remote station, a server, a cloud storage, and the like. In the illustrated embodiment, dispatch controller <NUM> is shown and described herein as a separate device from the other devices of dispatch system <NUM>, while in other embodiments, one or more aspects of dispatch controller <NUM> may be integrated with one or more of the other devices of dispatch system <NUM>. Stated differently, the illustrative hardware components of dispatch controller <NUM> shown and described herein may be integral with one or more of motion controller <NUM>, call device <NUM>, input device <NUM>, and/or counter device <NUM>.

Processor <NUM> 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 <NUM>. By way of example, processor <NUM> 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 <NUM> is configured to perform one or more operations in accordance with the instructions stored on memory <NUM>, such as, for example, dispatch logic <NUM>. Communications module <NUM> may facilitate communication between dispatch controller <NUM> and the one or more other devices of dispatch system <NUM>, such as, for example, via network <NUM>. User interface <NUM> may include one or more input and output devices, including one or more input ports and one or more output ports. User interface <NUM> may include, for example, a keyboard, a mouse, a touchscreen, etc., as input ports. User interface <NUM> may further include, for example, a monitor, a display, a printer, etc. as output ports. User interface <NUM> 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 <NUM> stored in memory <NUM>, and more.

Still referring to <FIG>, memory <NUM> may include various programming algorithms and data that support an operation of dispatch system <NUM>. Memory <NUM> 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 <NUM> may include one or more data sets, including, but not limited to, motion data <NUM> received from motion controller <NUM>, occupant data <NUM> captured from counter device <NUM>, call assignment data <NUM> and duration data <NUM> for each of the plurality of elevator cars <NUM>, <NUM>, <NUM>, and the like. Memory <NUM> may further include a threshold duration <NUM> that may be preprogrammed and/or adjustable by a user of dispatch system <NUM>, such as, for example, via user interface <NUM>.

As described further herein, occupant data <NUM> may include a real-time number of occupants <NUM> detected within a cabin of each elevator car <NUM>, <NUM>, <NUM> by counter device <NUM>. Call assignment data <NUM> may include a call request received from a prospective occupant <NUM> at one of the plurality of floors 204A-204D, for transportation by at least of the plurality of elevator cars <NUM>, <NUM>, <NUM>. Dispatch controller <NUM> may be configured to store the occupant data <NUM> in memory <NUM> and associate the number of occupants <NUM> with a corresponding elevator car <NUM>, <NUM>, <NUM>. Dispatch controller <NUM> may be further configured to store the call assignment data <NUM> in memory <NUM> to determine a current number of stops assigned to each elevator car <NUM>, <NUM>, <NUM>. As described further herein, dispatch controller <NUM> may be configured to determine a minimum travel duration for each of the plurality of elevator cars <NUM>, <NUM>, <NUM> based on at least one or more of the motion data <NUM>, the occupant data <NUM>, and the call assignment data <NUM>.

Further, memory <NUM> may include a non-transitory computer readable medium that stores machine-readable instructions thereon, such as, dispatch logic <NUM>. In one example, dispatch logic <NUM> may include executable instructions that allow dispatch system <NUM> to determine which elevator car from the plurality of elevator cars <NUM>, <NUM>, <NUM> to dispatch in response to receiving a call request at the first location "A" for transportation to a destination location. Dispatch logic <NUM> may facilitate determining an occupant capacity of each elevator car <NUM>, <NUM>, <NUM> based on a number of occupants physically present within each elevator car <NUM>, <NUM>, <NUM>. Dispatch logic <NUM> may further facilitate the determination of a minimum duration (e.g., duration data <NUM>) for each of the plurality of elevator cars <NUM>, <NUM>, <NUM> to travel to a location based on one or more of the motion data <NUM>, occupant data <NUM>, and/or call assignment data <NUM>. As described in further detail herein, dispatch system <NUM> may be configured to determine at least one elevator car <NUM>, <NUM>, <NUM> having the least duration (e.g., duration data <NUM>) to travel to a first location in response to a call request from a prospective occupant <NUM>.

Referring now to <FIG>, an example method <NUM> of using dispatch system <NUM> to determine a travel duration of a plurality of elevator cars and to dispatch an elevator car having the shortest travel duration is depicted.

At step <NUM>, dispatch system <NUM> may receive a call request at the first location "A" of a plurality of locations within working environment <NUM>. The call request may be initiated in response to a prospective occupant <NUM> actuating call device <NUM> at the first location "A," such as, for example, on first floor 204A and adjacent to a plurality of first elevator shafts <NUM>. Call device <NUM> may transmit the call request to dispatch controller <NUM> via network <NUM>, 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 <NUM> to which the prospective occupant <NUM> seeks to travel.

At step <NUM>, with the call request originating from first floor 204A and adjacent to the plurality of first elevator shafts <NUM>, dispatch controller <NUM> may retrieve motion data <NUM> from a corresponding motion controller <NUM> of a plurality of first elevator cars <NUM> located within the plurality of first elevator shafts <NUM>. Dispatch controller <NUM> may be configured to determine various movement parameters of the plurality of first elevator cars <NUM> from the motion data <NUM>, such as, for example, a current location of each first elevator car <NUM> relative to a respective first elevator shaft <NUM>, a current travel direction of each first elevator car <NUM>, and a current travel speed of each first elevator car <NUM>.

It should be understood that, in response to determining one or more first elevator cars <NUM> are not traveling toward the first location "A," dispatch controller <NUM> may be configured to disregard the particular first elevator car <NUM> from further consideration. Stated differently, dispatch controller <NUM> 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 <NUM> includes first elevator car <NUM> positioned between fourth floor 204D and third floor 204C, and moving toward first floor 204A.

In some embodiments, dispatch controller <NUM> may be further configured to determine whether a current location of the plurality of first elevator cars <NUM> is located prior to the first location "A," or whether first elevator cars <NUM> have moved beyond the first location "A. " Stated differently, dispatch controller <NUM> 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 <NUM> are not located before the first location "A," dispatch controller <NUM> may be configured to disregard said first elevator cars <NUM> from further consideration. In the example, as seen in <FIG>, first elevator car <NUM> is positioned between fourth floor 204D and third floor 204C, such that dispatch controller <NUM> may determine that first elevator car <NUM> is currently located before first floor 204A (e.g., the first location "A").

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may be configured to determine a number of calls assigned to each of the plurality of first elevator cars <NUM> (e.g., by dispatch controller <NUM>) and that have a (pick up) location positioned between a current location of each first elevator car <NUM> and the first location "A. " Stated differently, dispatch controller <NUM> may determine how many, if any, intermediate stops each first elevator car <NUM> 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 <NUM> is relative to when the call request (step <NUM>) is received by dispatch controller <NUM>.

It should further be appreciated that any calls previously assigned to first elevator cars <NUM>, 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 <NUM> may be configured to disregard any prior calls assigned to first elevator cars <NUM>, and which have a (pick up) location after the first location "A," when determining the number of calls at step <NUM>. In the example, as seen in <FIG>, first elevator car <NUM> may include a previously-assigned call at third floor 204C such that dispatch controller <NUM> may determine that first elevator car <NUM> includes one stop between the current location of first elevator car <NUM> and first floor 204A (e.g., the first location "A").

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may be configured to analyze the motion data <NUM> (step <NUM>) and the call assignment data <NUM> (step <NUM>) collected for the plurality of first elevator cars <NUM> to determine a minimum duration (e.g., a first duration) for each first elevator car <NUM> to travel from a respective current location to the first location "A. " For example, dispatch controller <NUM> may analyze a travel distance between a current location of each first elevator car <NUM> and the first location "A" when determining the minimum duration. Dispatch controller <NUM> may further analyze a travel speed of each first elevator car <NUM> when determining the minimum duration.

By further example, dispatch controller <NUM> may determine that the minimum duration required for each first elevator car <NUM> to travel to the first location "A" increases based on the number of existing calls assigned to the first elevator car <NUM>. Stated differently, dispatch controller <NUM> may assess the number of stops assigned to each first elevator car <NUM>, and positioned between a current location and the first location "A," when determining the minimum duration for each first elevator car <NUM>. For example, dispatch controller <NUM> may compute a predefined increment (e.g., duration data <NUM>) to the minimum duration for each stop assigned to a particular first elevator car <NUM>. The predefined increment may be programmed in memory <NUM>, and may include various suitable values ranging from about <NUM> second to about <NUM> seconds, and particularly about <NUM> seconds. In some embodiments, a value of the predefined increment may be selectively modified by a user of dispatch system <NUM>, such as via user interface <NUM>.

At step <NUM>, dispatch controller <NUM> may be configured to compare the minimum duration of the plurality of first elevator cars <NUM> to the threshold duration <NUM>. As described in detail above, the threshold duration <NUM> 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 <NUM> 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 <NUM> have a minimum duration that is less than the threshold duration <NUM> at step <NUM>, dispatch controller <NUM> may be configured to determine a number of occupants <NUM> located within each of the two or more first elevator cars <NUM> at step <NUM>.

For example, dispatch controller <NUM> may be configured to determine the number of occupants <NUM> within each first elevator car <NUM> (having a minimum duration less than the threshold duration <NUM>) by retrieving occupant data <NUM> from a respective counter device <NUM> of each first elevator car <NUM>. In some embodiments, counter device <NUM> may be configured to detect a total number of occupants <NUM> and/or objects <NUM> located within first elevator cars <NUM> (see <FIG>). Thus, dispatch controller <NUM> may consider one or more objects <NUM> detected by counter device <NUM> when determining the number of occupants <NUM> at step <NUM>. Each counter device <NUM> may transmit a signal to dispatch controller <NUM> via network <NUM> indicative of the occupant data <NUM> for the respective first elevator car <NUM>.

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

In the example, the plurality of first elevator cars <NUM> 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 <NUM> 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 <NUM> may include a total occupancy of one occupant and a maximum occupant capacity of six occupants. Dispatch controller <NUM> may be configured to determine first elevator car <NUM> includes an occupancy ratio of approximately <NUM>:<NUM> (e.g., approximately <NUM>%).

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may be configured to determine at least one of the plurality of first elevator cars <NUM> having a maximum occupant capacity that is greater than the remaining plurality of first elevator cars <NUM>. Dispatch controller <NUM> may compare the occupancy ratios of each of the plurality of first elevator cars <NUM> to determine at least one first elevator car <NUM> having the maximum available occupant capacity. Dispatch controller <NUM> may assign the call request received at step <NUM> to the first elevator car <NUM> of the plurality of first elevator cars <NUM> (having a travel duration that is less than the threshold duration <NUM>) that includes the maximum available occupant capacity. At step <NUM>, dispatch controller may be configured to dispatch the at least one first elevator car <NUM> to the first location "A.

In instances where two or more first elevator cars <NUM> include a similar occupancy ratio relative to one another, dispatch controller <NUM> may be configured to compare the minimum duration of each to one another to determine an optimal first elevator car <NUM> to dispatch. For example, dispatch controller <NUM> may assign the call request to the first elevator car <NUM> having the smallest minimum duration to travel to the first location "A. " In other embodiments, dispatch controller <NUM> may compare the minimum durations of the plurality of first elevator cars <NUM> to one another even when the occupancy ratios of first elevator cars <NUM> vary relative to one another. In this instance, dispatch controller <NUM> may be configured to dispatch at least one first elevator car <NUM> having the shortest minimum duration despite another one of the plurality of first elevator cars <NUM> having a greater maximum available occupant capacity.

It should be appreciated that, in instances where dispatch controller <NUM> determines only one first elevator car <NUM> has a minimum duration that is less than the threshold duration <NUM> (at step <NUM>), dispatch controller <NUM> may forgo performance of steps <NUM> to <NUM>. In this instance, the first elevator car <NUM> identified at step <NUM> may be dispatched to the first location "A" at step <NUM>. In other embodiments, method <NUM> may omit steps <NUM> to <NUM> entirely such that dispatch controller <NUM> may be configured to dispatch the at least one first elevator car <NUM> having the shortest minimum duration, at step <NUM>.

Dispatch controller <NUM> may be configured to communicate with call device <NUM> to transmit a message to the prospective occupant <NUM> at the first location "A" (e.g., first floor 204A). For example, dispatch controller <NUM> may communicate an identification of the first elevator car <NUM> dispatched to the first location "A. " In other embodiments, dispatch controller <NUM> may identify the first elevator shaft <NUM> of the plurality of first elevator shafts <NUM> from which the first elevator car <NUM> may arrive from. The message may be transmitted via call device <NUM> 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 <NUM>, in response to determining each of the plurality of first elevator cars <NUM> has a travel duration that exceeds the threshold duration <NUM>, dispatch controller <NUM> may be configured to disregard the plurality of first elevator cars <NUM> from further consideration. At step <NUM>, dispatch controller <NUM> may retrieve motion data <NUM> from a corresponding motion controller <NUM> of the plurality of elevator cars <NUM>, <NUM> located at various locations in working environment <NUM> other than the first location "A. " That is, dispatch controller <NUM> may consider the plurality of second elevator cars <NUM> (e.g., located adjacent to the second location "B") and third elevator cars <NUM> (e.g., located adjacent to the third location "C") upon determining that none of the plurality of first elevator cars <NUM> includes a travel duration that is less than the threshold duration <NUM>.

Dispatch controller <NUM> may consider the plurality of elevator cars <NUM>, <NUM> despite second elevator cars <NUM> and third elevator cars <NUM> being located further from the first location "A" (e.g., a location within working environment <NUM> proximate to where the call request originated from) than first elevator cars <NUM>. Dispatch controller <NUM> may be configured to determine various movement parameters of the plurality of second elevator cars <NUM> from the motion data <NUM>, such as, for example, a current location of each second elevator car <NUM> relative to a respective second elevator shaft <NUM>, a current travel direction of each second elevator car <NUM>, a current travel speed of each second elevator car <NUM>, and more. Dispatch controller <NUM> may further determine similar movement parameters of the plurality of third elevator cars <NUM>.

In response to determining one or more second or third elevator cars <NUM>, <NUM> are not traveling toward the first floor 204A, dispatch controller <NUM> may be configured to disregard the particular elevator cars <NUM>, <NUM> from further consideration. Dispatch controller <NUM> may be further configured to determine whether a current location of the plurality of second and third elevator cars <NUM>, <NUM> are located prior to first floor 204A. In the example, working environment <NUM> includes second elevator car <NUM> stationary at fourth floor 204D, and third elevator car <NUM> stationary at second floor 204B, such that dispatch controller <NUM> may determine that second elevator car <NUM> and third elevator car <NUM> are located before first floor 204A.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may be configured to determine how many, if any, intermediate stops second elevator cars <NUM> are expected to have between a respective current location and the second location "B" (e.g., on first floor 204A). Dispatch controller <NUM> may similarly determine the number of calls assigned to third elevator cars <NUM>, and that have a (pick up) location positioned between a respective current location of each third elevator car <NUM> and the third location "C" (e.g., on first floor 204A). In the example, second elevator car <NUM> may include an assigned call at second floor 204B, and third elevator car <NUM> may not include any assigned calls. Accordingly, dispatch controller <NUM> may determine that second elevator car <NUM> includes one stop between the current location of second elevator car <NUM> and the second location "B.

At step <NUM>, dispatch controller <NUM> may be configured to analyze the motion data <NUM> (step <NUM>) and the call assignment data <NUM> (step <NUM>) of the plurality of elevator cars <NUM>, <NUM> to determine a minimum duration for each elevator car <NUM>, <NUM> to travel from a respective current location to the second and/or third location "B, C. " For example, dispatch controller <NUM> may analyze a travel distance between a respective current location of each elevator car <NUM>, <NUM> and the corresponding second and/or third location "B, C" when determining the minimum duration. Dispatch controller <NUM> may further analyze a travel speed of each elevator car <NUM>, <NUM> when determining the minimum duration. By further example, dispatch controller <NUM> may determine an additional duration required to travel to the respective location "B, C," when elevator car <NUM>, <NUM> includes a preexisting call assignment. Dispatch controller <NUM> may assess the number of stops assigned to each elevator car <NUM>, <NUM> when determining the minimum duration for each elevator car <NUM>, <NUM>.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> is further configured to modify the minimum duration computation for elevator cars <NUM>, <NUM> based on a distance the prospective occupant <NUM> may be required to travel (e.g., walk) from the first location "A" to each of the second location "B" and third location "C. " Dispatch controller <NUM> may include data (e.g., duration data <NUM>) indicative of the time required to travel from the first location "A," at which the call request originated from, to the second location "B" at which second elevator cars <NUM> are positioned, based on the distance between the first location "A" and the second location "B. " Dispatch controller <NUM> may be configured to consider the distance required for the prospective occupant <NUM> to travel between locations "A, B" when determining the minimum duration (e.g., a second duration) for each of the plurality of second elevator cars <NUM>.

Dispatch controller <NUM> may further include data indicative of the time required for prospective passengers <NUM> to travel between the first location "A" and the third location "C," at which third elevator cars <NUM> are positioned, based on the distance between the first location "A" and the third location "C. " Dispatch controller <NUM> may be configured to consider the distance required for the prospective occupant <NUM> 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 <NUM>.

Accordingly, dispatch controller <NUM> may be configured to modify (e.g., increase) the minimum duration of the plurality of elevator cars <NUM>, <NUM> 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 <NUM>, <NUM>. In other embodiments, dispatch controller <NUM> 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 <NUM>, dispatch controller <NUM> may be configured to compare the minimum duration of the plurality of elevator cars <NUM>, <NUM> to the threshold duration <NUM>. In response to determining two or more of the plurality of elevator cars <NUM>, <NUM> have a minimum duration that is less than the threshold duration <NUM> at step <NUM>, dispatch controller <NUM> may be configured to determine the number of occupants <NUM> within each of the two or more elevator cars <NUM>, <NUM> at step <NUM>. For example, dispatch controller <NUM> may be configured to determine the number of occupants <NUM> within each elevator car <NUM>, <NUM> (having a minimum duration less than the threshold duration <NUM>) by retrieving occupant data <NUM> from the respective counter device <NUM> of each elevator car <NUM>, <NUM>.

Still referring to <FIG>, at step <NUM>, dispatch controller <NUM> may be configured to determine an occupancy ratio of each of the plurality of elevator cars <NUM>, <NUM> based on at least the number of occupants <NUM> detected within the elevator car (step <NUM>) and a maximum occupant capacity of each elevator car. In the example, second elevator car <NUM> may include a total occupancy of two occupants and a maximum occupant capacity of six occupants, and third elevator car <NUM> may include a total occupancy of one occupant and a maximum occupant capacity of five occupants. Dispatch controller <NUM> may be configured to determine second elevator car <NUM> includes an occupancy ratio of <NUM>:<NUM> (e.g., approximately <NUM>%), and third elevator car <NUM> includes an occupancy ratio of <NUM>:<NUM> (e.g., approximately <NUM>%).

At step <NUM>, dispatch controller <NUM> may be configured to determine at least one of the plurality of elevator cars <NUM>, <NUM> having a maximum occupant capacity that is greater than the remaining elevator cars <NUM>, <NUM>. Dispatch controller <NUM> may compare the occupancy ratios of each of the plurality of elevator cars <NUM>, <NUM> to determine at least one second elevator car <NUM> or third elevator car <NUM> having the maximum available occupant capacity. Dispatch controller <NUM> may assign the call request received at step <NUM> to the elevator car <NUM>, <NUM> (having a travel duration that is less than the threshold duration <NUM>) that includes the maximum available occupant capacity. At step <NUM>, dispatch controller <NUM> may dispatch the elevator car <NUM>, <NUM> 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 <NUM> and/or third elevator cars <NUM> include a similar occupancy ratio relative to one another, dispatch controller <NUM> may compare the minimum duration of each to determine an optimal elevator car <NUM>, <NUM> to dispatch. For example, dispatch controller <NUM> may dispatch the second elevator car <NUM> having the smallest minimum duration for traveling to the second location "B," or the third elevator car <NUM> having the smallest minimum duration for traveling to the third location "C. " In other embodiments, dispatch controller <NUM> may compare the minimum durations of the plurality of elevator cars <NUM>, <NUM> to one another even when the occupancy ratios of elevator cars <NUM>, <NUM> vary relative to one another. In this instance, dispatch controller <NUM> may be configured to dispatch at least one elevator car <NUM>, <NUM> having the shortest minimum duration despite another one of the plurality of elevator cars <NUM>, <NUM> having a greater maximum available occupant capacity.

It should be appreciated that, in instances where dispatch controller <NUM> determines only one second elevator car <NUM> or third elevator car <NUM> has a minimum duration that is less than the threshold duration <NUM> (at step <NUM>), dispatch controller <NUM> may forgo performance of steps <NUM> to <NUM>. In this instance, the elevator car <NUM>, <NUM> identified at step <NUM> may be dispatched at step <NUM>. In other embodiments, method <NUM> may omit steps <NUM> to <NUM> entirely such that dispatch controller <NUM> may be configured to dispatch the at least second elevator car <NUM> or third elevator car <NUM> having the shortest minimum duration, at step <NUM>.

Returning to step <NUM>, in response to determining each of the plurality of second elevator cars <NUM> and third elevator cars <NUM> have a travel duration that exceeds the threshold duration <NUM>, dispatch controller <NUM> may be configured to disregard the plurality of second elevator cars <NUM> and third elevator cards <NUM> from further consideration. In this instance, dispatch controller <NUM> may assign the call request received at step <NUM> to one of the plurality of first elevator cars <NUM>, despite each of the first elevator cars <NUM> having a minimum duration that exceeds the threshold duration <NUM>. In this instance, dispatch controller <NUM> may determine the number of occupants present (step <NUM>), the occupancy ratio (step <NUM>), and the maximum available occupancy ratio (step <NUM>) of each of the plurality of first elevator cars <NUM>. At step <NUM>, dispatch controller <NUM> may dispatch the first elevator car <NUM> of the plurality of first elevator cars <NUM> having the maximum available occupancy. Alternatively, dispatch controller <NUM> may omit steps <NUM> to <NUM>, and dispatch the at least one first elevator car <NUM> having the shortest minimum duration, at step <NUM>.

Claim 1:
A method (<NUM>) for dispatching an elevator car, the method comprising:
determining a first duration for each of a plurality of first elevator cars (<NUM>) to travel from a current location to a first location;
dispatching at least one of the plurality of first elevator cars (<NUM>) to the first location when the first duration of the at least one first elevator car is less than a threshold duration (<NUM>);
when the first duration for each of the plurality of first elevator cars (<NUM>) exceeds the threshold duration (<NUM>),
determining a second duration for each of a plurality of second elevator cars (<NUM>) to travel from a respective current location to a second location that is different than the first location,
modifying the second duration based on a time required for a prospective occupant to travel from the first location to the second location based on a distance between the first location and the second location, and
dispatching at least one of the plurality of second elevator cars (<NUM>) to the second location when the second duration of the at least one second elevator car is less than the threshold duration (<NUM>).