System and method for dispatching elevators

Abstract

To provide an elevator control system capable of assigning an elevator car based on a relative number of passengers.SOLUTION: A method for dispatching a plurality of elevator cars includes receiving a call request for at least one of a plurality of elevator cars, the call request being a call request from a first location of a plurality of locations, determining a number of passengers in the plurality of elevator cars, determining a number of call requests assigned to the plurality of elevator cars and located between a current location of the plurality of elevator cars and the first location to determine an available number of passengers for each of the plurality of elevator cars, and assigning the call request from the first location to a first elevator car of the plurality of elevator cars having a greater number of available passengers than a number of available passengers for remaining elevator cars.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] Aspects of the present disclosure relate generally to systems and methods for controlling elevator traffic, and more particularly to an example elevator control system that dispatches elevator cars based on the relative occupancy of a group of elevator cars. [Background technology]

[0002] Elevator systems may commonly employ a dispatch method based on the travel time required to service a call request. In such systems, the location and 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 with the shortest travel time to the call location will be dispatched to the call request's location. However, assigning elevator cars based on location or travel time may result in dispatching a nearly full or full elevator car, preventing passengers from boarding the elevator car. As a result, passengers may be required to issue another call request for a different elevator car, which may result in reduced traffic and longer wait times for passengers. By providing a system that can assign elevator cars based on relative passenger numbers, the instances of dispatching nearly full or full elevator cars can be minimized, thereby increasing traffic and reducing passenger wait times. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] U.S. Patent No. 3,851,733 [Patent Document 2] US Patent Application Publication No. 2017 / 121147 Summary of the Invention

[0004] According to one example, a method for dispatching a plurality of elevator cars includes receiving a call for at least one of the plurality of elevator cars, the call being from a first location among a plurality of locations. The method includes determining an occupancy level for each of the plurality of elevator cars by determining a number of occupants in the plurality of elevator cars, and determining a number of calls assigned to the plurality of elevator cars and located between a current location of the plurality of elevator cars and the first location. The method further includes assigning the call from the first location to a first elevator car having a greater available occupancy level than the occupancy level of the plurality of elevator cars.

[0005] According to another example, a system for dispatching multiple elevator cars includes at least one call device disposed at multiple locations. The at least one call device is configured to transmit a call to at least one of the multiple elevator cars from a first location of the multiple locations. The system includes at least one counting device disposed at the multiple elevator cars. The at least one counting device is configured to count the number of occupants in the multiple elevator cars. The system includes a dispatch controller operably connected to the at least one call device at the multiple locations and the at least one counting device at the multiple elevator cars, whereby the dispatch controller receives data indicative of the calls and the number of occupants in the multiple elevator cars. The dispatch controller is configured to determine the number of occupants in each of the multiple elevator cars from the number of occupants in the multiple elevator cars and the number of calls assigned to the multiple elevator cars and located between the current positions of the multiple elevator cars and the first location. The dispatch controller is configured to assign the call from the first location to a first elevator car with an available occupancy greater than the occupancy of the multiple elevator cars.

[0006] According to a further example, a system for controlling traffic for a plurality of elevator cars includes a processor and a memory, the memory storing instructions that, when executed by the processor, cause the processor to perform operations including receiving a call for at least one of the plurality of elevator cars, the call from a first location among a plurality of locations. The operations include determining an occupancy level for each of the plurality of elevator cars by determining a number of occupants in the plurality of elevator cars, and determining a number of calls assigned to the plurality of elevator cars and located between a current location of the plurality of elevator cars and the first location. The operations include assigning the call from the first location to the first elevator car having an available occupancy level greater than the occupancy level of the plurality of elevator cars. [Brief explanation of the drawings]

[0007] [Figure 1] 1 illustrates a dispatch system including one or more devices communicating over a network. [Figure 2] 2 is a schematic diagram of a work environment including multiple elevator cars interacting with the dispatch system shown in FIG. 1; [Figure 3] FIG. 3 is a top view of the elevator car interior from the working environment shown in FIG. 2. [Figure 4] 2 is a schematic diagram of the hardware components of a computer device from the dispatch system shown in FIG. 1 . [Figure 5] 2 is a flow diagram of an exemplary method for dispatching elevator cars using the dispatch system shown in FIG. 1 . DETAILED DESCRIPTION OF THE INVENTION

[0008] 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 present disclosure may be implemented in conjunction with the embodiments illustrated in the accompanying drawings. These drawings illustrate different aspects of the present disclosure, and where appropriate, reference numerals indicating similar structures, components, materials, and / or elements in different figures are similarly numbered. It is understood that various combinations of 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 skilled in the art will readily recognize that features of a particular aspect or embodiment may be used in combination with any or all features of the other aspects or embodiments described in this disclosure.

[0009] The dispatch system of the present disclosure may be in the form of a variety of embodiments, some of which are illustrated in the figures and further described below. Both the foregoing general description and the following detailed description are exemplary and explanatory and are not limiting of the features as claimed. As used herein, the terms "comprises," "includes," and other variations thereof are not intended to be exclusive, such that a process, method, article, or apparatus including a list of elements is inclusive of only those elements, but may include other elements not expressly listed or inherent in such process, method, article, or apparatus. Additionally, the term "exemplary" is used herein to mean "example" rather than "ideal." Note that all numerical values ​​disclosed or claimed herein (including all disclosed values, limits, and ranges) may have a + / -10% variation from the disclosed numerical value (unless a different variation is specified). Furthermore, in the claims, values, limits, and / or ranges mean + / -10% of the value, limit, and / or range.

[0010] FIG. 1 illustrates an exemplary dispatch system 100, which may include an operation controller 105, a paging device 110, an input device 120, a counting device 125, and a dispatch controller 130. One or more devices of dispatch system 100 may communicate with each other in any configuration via network 115. For example, devices of dispatch system 100 may be communicatively connected to each other via wired or wireless connections, etc. In some embodiments, network 115 may be a wide area network (“WAN”), a local area network (“LAN”), a personal area network (“PAN”), etc. Network 115 may also include the Internet, and information and / or data provided between devices of dispatch system 100 may occur online (e.g., from a location remote from other devices or networks connected to the Internet). In other embodiments, network 115 may utilize Bluetooth technology and / or radio frequencies.

[0011] The traffic controller 105 may be operably connected to the transport unit and may be configured to detect and transmit operational data of the transport unit to one or more devices of the dispatch system 100, such as the dispatch controller 130. For example, the traffic controller 105 may measure and record one or more parameters (e.g., operational data) of the transport unit, including, but not limited to, current location, direction of travel, speed of travel, door position, status, etc. The traffic controller 105 may include a computing device having one or more hardware components (e.g., a processor, memory, sensors, communication modules, etc.) for generating, storing, and transmitting the operational data. As described in further detail herein, the traffic controller 105 may be operably connected to elevator cars located within a building, and the dispatch system 100 may include at least one traffic controller 105 for each elevator car.

[0012] Continuing with reference to FIG. 1 , the call device 110 may be located outside the transportation unit and may be configured to receive user input from one or more riders seeking access to the transportation unit. For example, the user input may indicate a call requesting transportation from the transportation unit. The call device 110 may be configured to transmit the call request to one or more devices of the dispatch system 100, such as, for example, the dispatch controller 130. The call device 110 may include a keypad, a touchscreen display, a microphone, buttons, switches, etc. The call device 110 may further be configured to receive user input from multiple locations indicating a current location (e.g., a first location) and / or a destination location (e.g., a second location) of the call request.

[0013] As described in further detail herein, call devices 110 may be located within a building, and dispatch system 100 may have at least one call device 100 for each floor of the building. Call devices 100 may be configured to transmit a message from one or more devices (e.g., dispatch controller 130) of dispatch system 100 identifying an elevator car assigned to arrive at a floor of the building to respond to a call request. The message may be communicated by call device 100 via a variety of suitable manners, including, for example, text, voice, graphics, etc.

[0014] Input device 120 may be located inside a transport unit and configured to receive user input from one or more occupants of the transport unit. For example, the user input may indicate a command requesting redirection of the transport unit. Input device 120 may be configured to transmit commands to one or more devices of dispatch system 100, such as dispatch controller 130. Input device 120 may include a keypad, a touchscreen display, a microphone, buttons, switches, etc. As described in more detail herein, input device 120 may be located in an elevator car, and dispatch system 100 may include at least one input device 100 for each elevator car in a building. In other embodiments, input device 120 may be omitted entirely from dispatch system 100.

[0015] 1 , counting device 125 may be located inside a transport unit and may be configured to detect and transmit occupant data of the transport unit to one or more devices of dispatch system 100, such as dispatch controller 130. For example, counting device 125 may measure and record the number of objects located inside the transport unit, including, but not limited to, occupants, their belongings, luggage, baggage, etc. Counting device 125 may include an optical system facing the interior of the transport unit, such as, for example, a sensor, a camera, a light beam, an infrared detector, etc. As described in further detail herein, counting device 125 may be connected to elevator cars located within a building, and dispatch system 100 may include at least one counting device 125 for each elevator car in the building.

[0016] The dispatch controller 130 may be located outside the transport unit and may be configured to receive data (e.g., operational data, call requests, redirect commands, passenger data, etc.) from one or more devices of the dispatch system 100. The dispatch controller 130 may further be configured to determine whether to dispatch at least one of the plurality of transport units to a location of a call request received from a ride seeker requesting a ride. The dispatch controller 130 may include a computing device (see FIG. 4) operable to execute one or more processes (see FIG. 5) for dispatching at least one transport unit with the maximum available capacity to the ride seeker's location. As described in further detail herein, the dispatch controller 130 may be operably connected to multiple elevator cars located within a building, and the dispatch system 100 may include at least one dispatch controller 130 for each building.

[0017] Referring now to FIG. 2 , dispatch system 100 may be utilized in a work environment 200, such as a building (e.g., a facility, a factory, a store, a school, a home, an office, and various other structures). In this example, the transport unit may include one or more elevator cars within the building. It should be understood that work environment 200 is merely exemplary, and dispatch system 100 may be utilized in a variety of other suitable environments other than those shown and described herein without departing from the scope of this disclosure. In this example, work environment 200 may include multiple floors, e.g., first floor 204A, second floor 204B, third floor 204C, and fourth floor 204D, defining multiple locations within a building. It should be understood that in other embodiments, the construction of work environment 200 may include additional and / or fewer floors.

[0018] Work environment 200 may further include one or more elevator shafts with at least one elevator car disposed within each elevator shaft. In this example, work environment 200 includes a first elevator shaft 212 with a first elevator car 210 and a second elevator shaft 212 with a second elevator car 220. Although not shown, work environment 200 may include additional (e.g., multiple) elevator shafts and / or elevator cars. Each elevator car 210, 220 may be connected to a pulley system 208 configured to move elevator cars 210, 220 within elevator shafts 202, 212 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 within elevator shafts 202, 212, including, but not limited to, motors, cables, counterweights, pulleys, etc.

[0019] 2, each elevator car 210, 220 may include at least one operation controller 105 operably connected to sheave system 208, for example, via a wireless and / or wired connection 209. The operation controller 105 is configured to measure operation data from elevator car 210, 220 by detecting relative motion of sheave system 208. Each elevator car 210, 220 may further include at least one input device 120 disposed within the cabin of elevator car 210, 220 for receiving user input from one or more occupants 10 located within the cabin.

[0020] Each floor 204A-204D may include one or more call devices 110 and access doors 206 that provide access to the elevator cars 210, 220 when the elevator doors 207 of the elevator cars 210, 220 are located at the respective floors 204A-204D. The call devices 110 may be configured to receive user input from one or more ride seekers 20 located at one of the floors 204A-204D. For example, the call devices 110 may be configured to receive user input indicating a call requesting transportation via at least one of the elevator cars 210, 220. The call devices 110 may be configured to transmit a call request to the dispatch controller 130, and the call request may include data (e.g., the second floor 204B) indicating a current location (i.e., a first location) within the work environment 200 from which the call request originates. The call request may further include data indicating a destination location (ie, a second location) within work environment 200 to which the ride seeker is seeking transportation (eg, first floor 204A).

[0021] 2, each elevator car 210, 220 may further include at least one counting device 125 disposed within the cabin. The counting device 125 may be disposed along an interior wall (e.g., the ceiling) of each elevator car 210, 220 and may be configured to detect multiple occupants 10 within the cabin. In some embodiments, the counting device 125 may be operable to distinguish between one or more objects detected within the elevator car 210, 220.

[0022] 3 , counting device 125 may be configured to detect items present in the cabin that occupy the volume of elevator car 210, 220 (e.g., occupants 10, incidental objects 12, etc.) and items in the cabin that do not appear to occupy the volume of elevator car 210, 220 (e.g., rails 14, etc.). Counting device 125 may measure the number of items detected in elevator car 210, 220 and record such measurements as occupant data. As described further herein, counting device 125 may be configured to transmit occupant data for each elevator car 210, 220 (e.g., dynamic occupant data 142, static occupant data 144, etc.) to dispatch controller 130 via network 115.

[0023] Referring now to FIG. 4 , dispatch controller 130 may include a computing device incorporating multiple hardware components that enable dispatch controller 130 to receive data (e.g., operational data, call requests, commands, passenger data, etc.), process information (e.g., passenger count), and / or perform one or more processes (see FIG. 5 ). An exemplary hardware configuration of dispatch controller 130 may include at least one processor 132, at least one communication module 134, and at least one memory 136. In some embodiments, dispatch controller 130 may include a computer, a mobile user device, a remote station, a server, cloud storage, etc. Although in the illustrated embodiment, dispatch controller 130 is shown and described herein as a device separate from other devices of dispatch system 100, in other embodiments, one or more aspects of dispatch controller 130 may be integrated with one or more other devices of dispatch system 100. In other words, the exemplary hardware configuration of the dispatch controller 130 shown and described herein may be integrated with one or more of the operation controller 105, the calling device 110, the input device 120, and / or the counting device 125.

[0024] 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 memory 136. By way of example, processor 132 may include a controller, an integrated circuit, a microchip, a computer, and / or any other computing unit operable to perform the computational and logical operations necessary to execute a program. As described in detail herein, processor 132 is configured to perform one or more operations according to instructions stored in memory 136, such as, for example, dispatch logic 138.

[0025] 4 , memory 136 may include various programmed algorithms and data that support the operation of dispatch system 100. Memory 136 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), flash memory, a hard drive, and / or any device capable of storing machine-readable instructions. Memory 136 may include one or more data sets, such as, but not limited to, operational data 140 received from operation controller 105, dynamic occupant data 142 and / or static occupant data 144 obtained from counting device 125, etc.

[0026] As described further herein, dynamic occupant data 142 may include a real-time number of occupants 10 detected within the cabin of each elevator car 210, 220 by counting device 125. Static occupant data 144 may include a number of occupants 10 previously detected within at least one elevator car 210, 220 by counting device 125 and transported to at least one of a plurality of locations within work environment 200. In other words, static occupant data 144 may correspond to a number of occupants 10 transported to at least one of a plurality of floors 204A-204D by at least one of the plurality of elevator cars 210, 220. Dispatch controller 130 may be configured to store static occupant data 144 in memory 136 and associate the numbers of occupants 10 with their corresponding destinations (e.g., floors 204A-204D) within work environment 200. For example, dispatch controller 130 may receive and correlate operational data 140 received from operations controller 105 with static crew data 144 to determine the destination location of crew member 10 .

[0027] Additionally, memory 136 may include non-transitory computer-readable media storing machine-readable instructions, such as dispatch logic 140. In one example, dispatch logic 140 may include executable instructions that enable dispatch system 100 to determine which elevator car of multiple elevator cars 210, 220 to dispatch in response to receiving a call request at a first location for transportation to a second location. Dispatch logic 140 may further facilitate determining the passenger load for each elevator car 210, 220 based on the number of passengers physically present within each elevator car 210, 220 and the number of passengers located outside each elevator car designated for collection by each elevator car. As described in further detail herein, dispatch system 100 may be configured to determine the occupancy number of each elevator car 210, 220 based on one or more of operation data 140 from operation controller 105 and counting device 125, dynamic occupancy data 142, and / or static occupancy data 144 received by dispatch controller 130.

[0028] 5, an exemplary method 300 is shown for determining the occupancy of multiple elevator cars and dispatching the elevator car with the greater occupancy using dispatch system 100. It should be understood that the steps shown and described herein, and the order in which they are presented, are merely exemplary, and that additional steps and / or fewer steps may be added and included in various configurations without departing from the scope of the present disclosure.

[0029] In step 302, dispatch system 100 may receive a call request at a first location within work environment 200. The call request may be initiated in response to ride seeker 20 activating call device 110 at the first location, such as second floor 204B. Call device 100 may transmit the call request to dispatch controller 130 over network 115, and the call request may include data indicating the first location (e.g., second floor 204B) from which the call request originated. The call request may also include data indicating a second location (e.g., first floor 204A) within work environment 200 to which ride seeker 20 is traveling (i.e., the destination location of ride seeker 20).

[0030] In step 304, dispatch controller 130 may retrieve operational data 140 for each elevator car 210, 220 from a corresponding operations controller 105. Dispatch controller 130 may be configured to determine various movement parameters for each elevator car 210, 220 from operational data 140, such as, for example, the current position of first elevator car 210 relative to first elevator shaft 202 (e.g., traveling between fourth floor 204D and third floor 204C), the current direction of movement of first elevator car 210 (e.g., toward first floor 204A), and the current speed of movement of first elevator car 210. The dispatch controller 130 may further determine the current position of the second elevator car 220 relative to the second elevator shaft 212 (e.g., stationary at the fourth floor 204D), the current direction of movement of the second elevator car 220 (e.g., toward the first floor 204A), the current speed of movement of the second elevator car 220, etc.

[0031] In step 306, dispatch controller 130 may be configured to analyze operation data 140 for each elevator car 210, 220 to determine whether the current direction of movement of elevator car 210, 220 is toward a second location (e.g., first floor 204A). If it is determined that elevator car 210, 220 is not moving toward the second location, dispatch controller 130 may be configured to remove the particular elevator car 210, 220 from further consideration in step 308. In other words, dispatch controller 130 may determine that any elevator car of multiple elevator cars 210, 220 moving in a direction other than toward the second location (relative to the current location of elevator car 210, 220) is not the best elevator car to respond to the call request. In this example, the first elevator car 210 and the second elevator car 220 may include multiple passengers 10 traveling from the fourth floor 204D to the first floor 204A, which may cause the dispatch controller 130 to determine that each elevator car 210, 220 is traveling toward the second location.

[0032] 5, in step 310, dispatch controller 130 may be configured to determine whether the current location of each elevator car 210, 220 is before the first location (e.g., second floor 204B) or whether elevator car 210, 220 has moved beyond the first location. In other words, dispatch controller 130 may determine that none of elevator cars 210, 220 currently located beyond the first location is the best elevator car to respond to the call request. If dispatch controller 130 determines that one or more of elevator cars 210, 220 is not located before the first location, dispatch controller 130 may be configured to remove the particular elevator car 210, 220 from further consideration in step 308.

[0033] In this example, because first elevator car 210 is located between fourth floor 204D and third floor 204C and second elevator car 220 is located on fourth floor 204D, dispatch controller 130 may determine that each elevator car 210, 220 is currently located before the first position. In steps 312 through 320, dispatch controller 130 may be configured to determine the number of occupants in each elevator car 210, 220 in response to determining that elevator car 210, 220 is located before the first position (e.g., second floor 204B) within elevator shaft 202, 220.

[0034] For example, in step 312, the dispatch controller 130 may be configured to determine the number of occupants 10 in each elevator car 210, 220 by retrieving dynamic occupant data 142 from a respective counting device 125 located in each elevator car 210, 220. In some embodiments, the counting devices 125 may be configured to detect the total number of occupants 10 and / or objects 12 located in each elevator car 210, 220 (see FIG. 3 ). Accordingly, the dispatch controller 130 may be configured to take into account one or more objects 12 detected by the counting devices 125 when determining the number of occupants 10 in step 312. Each counting device 125 may transmit a signal indicative of the dynamic occupant data 142 for its respective elevator car 210, 220 to the dispatch controller 130 via the network 115. In this example, dispatch controller 130 may determine that first elevator car 210 contains one occupant 10 and second elevator car 220 contains two occupants 10 .

[0035] 5, in step 314, dispatch controller 130 may be configured to determine the number of calls already assigned (e.g., by dispatch controller 130) to each elevator car 210, 220, where the (pickup) locations are between the current location of each elevator car 210, 220 and the first location. In other words, dispatch controller 130 may determine how many stops, if any, each elevator car 210, 220 is expected to make between its current location and the first location (e.g., second floor 204B). It should be understood that the number of calls already assigned to elevator cars 210, 220 is relative to when the call request in step 302 is received by dispatch controller 130. It should also be understood that calls already assigned to elevator cars 210, 220 that do not include locations between the current location of elevator car 210, 220 and the first location of the call request will not result in any stops. Therefore, dispatch controller 130 may be configured to not consider calls already assigned to elevator cars 210, 220 having (pickup) positions after the first position when determining the number of calls in step 314.

[0036] In this example, the first elevator car 210 may include an assigned call at the third floor 204C, such that the dispatch controller 130 may determine that the first elevator car 210 includes one assigned call located between the current location of the first elevator car 210 (e.g., between the fourth floor 204D and the third floor 204C) and the first location (e.g., the second floor 204B). Additionally, the second elevator car 220 may not include any assigned calls, such that the dispatch controller 130 may determine that the second elevator car 220 has zero assigned calls located between the current location of the second elevator car 220 (e.g., the fourth floor 204D) and the first location (e.g., the second floor 204B).

[0037] In step 316, dispatch controller 130 may be configured to determine the number of ride seekers 20 at each call location already assigned to elevator car 210 (step 314). In some embodiments, dispatch controller 130 may determine that each call location already assigned to elevator car 210 may contain at least one ride seeker 20. In this case, in step 318, dispatch controller 130 may determine the total number of occupants in each elevator car 210, 220 by calculating the sum of the number of occupants 10 physically present in elevator car 210, 220 (step 312) and the number of ride seekers 20 located at each assigned call (step 314). In this case, dispatch controller 130 may determine that the first elevator car 210 contains a total of two occupants (e.g., one occupant 10 in the first elevator car 210 plus at least one ride seeker 20 located on the third floor 204C). Dispatch controller 130 may further determine that second elevator car 220 contains a total of two occupants (eg, two occupants 10 and no ride seekers 20 in second elevator car 220).

[0038] In another embodiment, dispatch controller 130 may determine that each call location already assigned to an elevator car 210 may contain a maximum number of ride seekers 20 in step 316. In this case, dispatch controller 130 may determine that the maximum number of ride seekers 20 at each call location already assigned to an elevator car 210 corresponds to static occupant data 144 stored in memory 136 for that particular location (e.g., the third floor 204C). In this example, static occupant data 144 may indicate a total of two occupants 20 already traveled to the third floor 204C by at least one of the elevator cars 210, 220 prior to receiving the call request in step 302. Thus, dispatch controller 130 may determine that a call assigned to the first elevator car 210 from the third floor 204C may contain two ride seekers 20.

[0039] In step 318, the dispatch controller 130 may determine that the first elevator car 210 contains a total of three occupants (e.g., one occupant 10 in the first elevator car 210 and up to two ride seekers 20 on the third floor 204C). The static occupant data 144 stored in the memory 136 may be periodically updated by the dispatch system 100 during ongoing use of the multiple elevator cars 210, 220 in the work environment 200. Thus, the static occupant data 144 for each floor 204A-204B may be dynamic and continuously changed to track the number of current occupants 20 located on each floor 204A-204D. It should be understood that the number of current occupants 20 may increase and / or decrease based on the number of occupants 10 entering and exiting each floor 204A-204D via the multiple elevator cars 210, 220 as detected by the counting device 125.

[0040] 5 , in step 320, the dispatch controller 130 may be configured to determine the occupancy capacity of each of the plurality of elevator cars 210, 220 based on at least the total occupancy capacity (step 318) and the maximum occupancy capacity of each of the elevator cars 210, 220. In some embodiments, the maximum occupancy capacity of each elevator car 210, 220 may be communicated to the dispatch controller 130 from the counting device 125 via the network 115. In other embodiments, the dispatch controller 130 may store the maximum occupancy capacity for each of the plurality of elevator cars 210, 220 in the memory 136. It should be understood that the size and / or shape of the cabin of each of the plurality of elevator cars 210, 220 may be a determining factor in the maximum occupancy capacity. In this example, the plurality of elevator cars 210, 220 may be of substantially similar size and / or shape, such that the maximum occupancy capacity of the first elevator car 210 and the second elevator car 220 is relatively similar. In other examples, the elevator cars 210, 220 may be of different sizes and / or shapes such that the maximum passenger capacity of the first elevator car 210 and the second elevator car 220 differ from one another.

[0041] In this example, if the first elevator car 210 has a total occupancy of two and a maximum occupancy of six, the dispatch controller 130 may be configured to determine that the occupancy ratio for the first elevator car 210 is approximately 2:6 (e.g., approximately 33.33%). Alternatively, if the first elevator car 210 has a total occupancy of three and a maximum occupancy of six, the dispatch controller 130 may be configured to determine that the occupancy ratio for the first elevator car 210 is approximately 3:6 (e.g., approximately 50%). Furthermore, if the second elevator car 220 has a total occupancy of two and a maximum occupancy of six, the dispatch controller 130 may be further configured to determine that the occupancy ratio for the second elevator car 220 is approximately 2:6 (e.g., 33.33%).

[0042] 5 , in step 322, dispatch controller 130 may be configured to determine at least one of the plurality of elevator cars 210, 220 having a maximum passenger capacity available to assign the call request. Dispatch controller 130 may compare the occupancy rates of each of the plurality of elevator cars 210, 220 to determine at least one of the elevator cars 210, 220 having a maximum passenger capacity available. In this example, if the occupancy rates of the first elevator car 210 and the second elevator car 220 are each approximately 50%, dispatch controller 130 may be configured to compare operational data 140 to determine one or more operational parameters (e.g., current location, travel speed, status, etc.) of the plurality of elevator cars 210, 220.

[0043] Dispatch controller 130 may compare operational data 140 to determine which of multiple elevator cars 210, 220 to assign the call request to if the elevator cars 210, 220 have similar maximum passenger capacities. For example, dispatch controller 130 may assign the call request to a first elevator car 210 based on the distance between the first elevator car 210 and a first location (e.g., the second floor 204C) being shorter than the distance between the second elevator car 220 and the first location. As a further example, if the first elevator car 210 already has a call assigned to it and the second elevator car 220 does not have any calls assigned to it, dispatch controller 130 may determine to assign the call request to the second elevator car 220 based on the second elevator car 220 traveling faster than the first elevator car 210.

[0044] In an example where the occupancy rate of the first elevator car 210 is approximately 33.33% and the occupancy rate of the second elevator car 220 is approximately 50%, the dispatch controller 130 may be configured to assign the call request to the first elevator car 210 with the greater maximum available passenger capacity. In this case, the first elevator car 210 may be assigned the call request in step 324. In some embodiments, if the occupancies of the multiple elevator cars 210, 220 are different from one another, the dispatch controller 130 may compare the operational data 140 of the multiple elevator cars 210, 220. In this case, the dispatch controller 130 may be configured to assign the call request to at least one elevator car 210, 220, even if another of the multiple elevator cars 210, 220 has a greater available passenger capacity.

[0045] In some embodiments, dispatch controller 130 may be configured to communicate with call device 110 to transmit a message to ride seeker 20 at a first location (e.g., second floor 204B). For example, dispatch controller 130 may communicate the identity of at least one of multiple elevator cars 210, 220 assigned to respond to the call request. In other embodiments, dispatch controller 130 may identify at least one of multiple elevator shafts 202, 212 from which elevator car 210, 220 may arrive. The message may be transmitted via call device 110 in a variety of suitable formats, including, for example, via a display (e.g., text format, image format, etc.), a speaker (e.g., audio format), etc.

[0046] All technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains, unless otherwise specified. As used herein, the singular includes the plural unless the context clearly dictates otherwise.

[0047] The above description is illustrative and not intended to be limiting. Those skilled in the art may make various modifications and / or variations without departing from the general scope of the present disclosure. For example, as noted above, the above-described embodiments (and / or aspects thereof) may be used in combination with each other. In addition, portions of the above-described embodiments may be omitted without departing from the scope of the present disclosure. Furthermore, 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 be apparent to those skilled in the art upon reviewing the above description.

Claims

[Claim 1] The method described in the specification.

Images