System and method for dispatching elevators

Abstract

The present invention provides an elevator control system that dispatches elevator cars based on the relative passenger capacity of a group of elevator cars. [Solution] A method for reassigning a first elevator car among a plurality of elevator cars includes dispatching the first elevator car from its current position to the first destination position in order to pick up passengers at the first destination position. The method includes determining that the first elevator car has stopped at an intermediate position located between its current position and the first destination position. The method further includes determining, after the first elevator car has stopped at the intermediate position, that the number of passengers in the first elevator car is greater than that of at least the second elevator car among the plurality of elevator cars, and directing the first elevator car to a second destination position different from the first destination position.

Description

Technical Field

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

Background Art

[0002] Elevator systems may generally reassign elevator cars in response to the occurrence of an error. In such systems, the detection of an error, such as a mechanical or electrical failure, can be a factor in determining whether a call request assigned to an elevator car requires reassignment.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, if a call request is reassigned to a different elevator car solely based on a malfunction, it is possible that an elevator car that is nearly or completely full will be dispatched indiscriminately, preventing passengers from boarding. Furthermore, when reassigning a call to a subsequent elevator car, such a system may make such reassignments based on the travel time required to respond to the call. Thus, the elevator car that is located near the call request and has the shortest travel time to respond to the call may be dispatched to the call location. However, reassigning elevator cars based on location or travel time may result in an elevator car that is nearly or completely full being dispatched. As a result, passengers may have to attempt another call request to a different elevator car, which could reduce traffic flow and increase passenger waiting times. [Means for solving the problem]

[0005] By providing a system that can reallocate elevator cars based on their relative passenger capacity, it is possible to minimize instances of sending out full elevator cars, thereby increasing traffic flow and reducing waiting times for passengers.

[0006] For example, a method for reassigning a first elevator car among a plurality of elevator cars includes dispatching the first elevator car from its current position to the first destination position in order to pick up passengers at the first destination position. The method includes determining that the first elevator car has stopped at an intermediate position located between its current position and the first destination position, and determining, after the first elevator car has stopped at the intermediate position, that the number of passengers in the first elevator car is greater than that of at least a second elevator car among the plurality of elevator cars. The method further includes orienting the first elevator car to a second destination position different from the first destination position.

[0007] In another example, a method for operating a first elevator car among several elevator cars includes moving the first elevator car toward a first destination location in response to a call from a first destination location, and stopping the first elevator car at an intermediate position located before the first destination location. The first elevator car accepts one or more passengers from the intermediate position. The method includes determining, after the first elevator car has stopped at the intermediate position, that the number of passengers in the first elevator car is at least less than that of a second elevator car. The method includes reorienting the first elevator car to a second destination location different from the first destination location so that the first elevator car does not stop at the first destination location.

[0008] In a further example, a system for dispatching a first elevator car among a plurality of elevator cars includes a counting device located inside the first elevator car and configured to count the number of passengers in the first elevator car, and a dispatch controller operably connected to the counting device to receive data indicating the number of passengers in the first elevator car. The dispatch controller is configured to dispatch the first elevator car to pick up passengers at a first destination position, determine that the first elevator car has stopped at an intermediate position before picking up the passengers at the first destination position, determine that after stopping at the intermediate position the number of passengers in the first elevator car exceeds at least the number of passengers in the second elevator car, dispatch the first elevator car to a second destination position different from the first destination position, and dispatch the second elevator car to the first destination position to pick up the passengers. [Brief explanation of the drawing]

[0009] [Figure 1] A diagram illustrating a shipping system that includes one or more devices communicating over a network. [Figure 2] A schematic diagram of the work environment, including multiple elevator cars interacting with the shipping system shown in Figure 1. [Figure 3]Figure 2 shows a top view of the inside of the elevator car from the working environment. [Figure 4] Figure 1 shows a schematic diagram of the hardware components of the computer device from the shipping system. [Figure 5] A flowchart illustrating an exemplary method for shipping an elevator car using the shipping system shown in Figure 1. [Modes for carrying out the invention]

[0010] The accompanying drawings, incorporated into and constituting part thereof, illustrate various exemplary embodiments and, together with the specification, are useful in illustrating the principles of this disclosure. Aspects of this disclosure may be implemented in relation to embodiments shown in the accompanying drawings. These drawings illustrate different aspects of this disclosure, and where appropriate, reference numerals indicating similar structures, components, materials, and / or elements in different drawings are numbered similarly. It will be understood that various combinations of structures, components, and / or elements other than those specifically shown are contemplated and fall within the scope of this disclosure. Many aspects and embodiments are described herein. Those skilled in the art will readily recognize that features of a particular aspect or embodiment may be used in conjunction with any or all features of other aspects or embodiments described herein.

[0011] The shipping system of this disclosure may take the form of various embodiments, some of which are shown in the figures and further described below. Both the general description above and the detailed description below are illustrative and descriptive and do not limit the features to those claimed. Where used herein, “equipped with,” “included,” or other variations thereof are intended not to imply that a process, method, article, or apparatus containing a list of elements includes only those, but may include other elements not expressly described or inherent in such a process, method, article, or apparatus. In addition, the term “exemplary” is used herein in the sense of “example” and not “ideal.” Note that all numerical values ​​disclosed or claimed herein (including all disclosed values, limitations, and ranges) may vary by + / - 10% from the disclosed numerical values ​​(unless different variations are specified). Furthermore, in the claims, values, limitations, and / or ranges mean + / - 10% of the values, limitations, and / or ranges.

[0012] Figure 1 shows an exemplary dispatch system 100, which may comprise a dispatch controller 105, a call device 110, an input device 120, a counting device 125, and a dispatch controller 130. One or more devices of the dispatch system 100 may communicate with each other in any configuration via a network 115. For example, the devices of the dispatch system 100 may be connected to each other in a communicative manner via wired or wireless connections. In some embodiments, the network 115 may be a wide area network ("WAN"), a local area network ("LAN"), a personal area network ("PAN"), etc. The network 115 may further include the Internet, and information and / or data provided between devices of the dispatch system 100 may originate online (for example, from a location away from other devices or the Internet-connected network). In other embodiments, the network 115 may utilize Bluetooth® technology and / or radio frequencies.

[0013] The operation controller 105 may be operably connected to a transport unit and may be configured to detect operation data of the transport unit and transmit it to one or more devices of the dispatch system 100, such as a dispatch controller 130. For example, the operation controller 105 may measure and record one or more parameters of the transport unit (e.g., operation data), which include, but are not limited to, current position, direction of movement, speed of movement, door position, status, etc. The operation controller 105 may include a computer device, which has one or more hardware components (e.g., a processor, memory, sensors, communication modules, etc.) for generating, storing, and transmitting operation data. As will be described in more detail herein, the operation controller 105 may be operably connected to an elevator car located within a building, and the dispatch system 100 may include at least one operation controller 105 for each elevator car.

[0014] Continuing to refer to Figure 1, the call device 110 may be located outside the transport unit and may be configured to receive user input from one or more passengers requesting access to the transport unit. For example, the user input may indicate a call requesting transport from the transport unit. The call device 100 may be configured to send the call request to one or more devices of the dispatch system 100, such as 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 the current location (e.g., a first location) and / or destination location (e.g., a second location) of the call request.

[0015] As will be described in more detail herein, the call device 110 may be located within a building, and the dispatch system 100 may have at least one call device 100 for each floor of the building. The call device 100 may be configured to send a message from one or more devices of the dispatch system 100 (e.g., a dispatch controller 130) that identifies an elevator car assigned to arrive at a floor of the building in response to a call request. The message may be communicated by the call device 100 through various appropriate forms, including, for example, text, voice, graphics, etc.

[0016] The input device 120 may be located inside the transport unit and may be 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. The input device 120 may be configured to send commands to one or more devices of the dispatch system 100, such as a dispatch controller 130. The input device 120 may include a keypad, a touchscreen display, a microphone, buttons, switches, etc. As described in detail herein, the input device 120 may be located inside the elevator car, and the dispatch system 100 may include at least one input device 100 for each elevator car in a building. In other embodiments, the input device 120 may be omitted entirely from the dispatch system 100.

[0017] Continuing to refer to FIG. 1, the counting device 125 may be disposed inside the transport unit and may be configured to detect passenger data of the transport unit and transmit it to one or more devices of the shipping system 100, such as the shipping controller 130. For example, the counting device 125 may measure and record the number of objects located within the transport unit, and the measurement and recording targets include, but are not limited to, passengers, their belongings, luggage, carry-on items, etc. The counting device 125 may include, for example, an optical system facing the inside of the transport unit such as a sensor, a camera, a light beam, an infrared detector, etc. As will be described in more detail herein, the counting device 125 may be connected to an elevator car disposed within a building, and the shipping system 100 may include at least one counting device 125 for each elevator car of the building.

[0018] The shipping controller 130 may be disposed outside the transport unit and may be configured to receive data (e.g., operation data, call requests, redirect commands, passenger data, etc.) from one or more devices of the shipping system 100. The shipping controller 130 may further be configured to determine to send at least one of the plurality of transport units to the location of a call request received from a passenger wishing to board. The shipping controller 130 may further be configured to reassign a call request from the original transport unit to another transport unit based on the relative passenger capacity of the plurality of transport units. The shipping controller 130 may include a computer device (see FIG. 4) operable to execute one or more processes (see FIG. 5) for reassigning a call to at least one transport unit with the largest available capacity at the location of the passenger wishing to board. As will be described in more detail herein, the shipping controller 130 may be operably connected to a plurality of elevator cars disposed within a building, and the shipping system 100 may include at least one shipping controller 130 for each building.

[0019] Referring to FIG. 2 here, the shipping system 100 may be utilized in a work environment 200 such as a building (e.g., a facility, factory, store, school, home, office, and various other structures). In this example, the transport unit may include one or more elevator cars within the building. The work environment 200 is merely exemplary, and it should be understood that the shipping system 100 can be utilized in various other suitable environments other than those shown and described herein without departing from the scope of the present disclosure. For example, the work environment may include a mass transit system such that the transport unit includes buses, trains, subway vehicles, metro vehicles, vehicles, etc. In this example, the work environment 200 may include a plurality of floors defining multiple locations within the building, such as the first floor 204A, the second floor 204B, the third floor 204C, and the fourth floor 204D. It should be understood that in other embodiments, the construction of the work environment 200 may include additional and / or fewer floors.

[0020] The work environment 200 may further include one or more elevator shafts having at least one elevator car disposed within each elevator shaft. In this example, the work environment 200 includes a first elevator shaft 202 having a first elevator car 210 and a second elevator shaft 212 having a second elevator car 220. Although not shown, the 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 the elevator cars 210, 220 within the elevator shafts 202, 212 with respect to the floors 204A - 204D. The pulley system 208 may include various mechanical and / or electrical mechanisms for moving the elevator cars 210, 220 within the elevator shafts 202, 212, and it should be understood that such mechanisms include, but are not limited to, for example, motors, cables, counterweights, pulleys, etc.

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

[0022] Each floor 204A to 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 locations on floors 204A to 204D. The call device 110 may be configured to receive user input from one or more passengers 20 located on one of the floors 204A to 204D. For example, the call device 110 may be configured to receive user input indicating a call requesting transport through at least one of the elevator cars 210, 220. The call device 100 may be configured to send a call request to a dispatch controller 130, which may include data (e.g., second floor 204B) indicating the current location (i.e., first location) within the work environment 200 from which the call request is originated. The call request may also include data indicating the destination location (i.e., second location) within the work environment 200 where the passenger is requesting transportation (e.g., first floor 204A).

[0023] Referring further to Figure 2, each elevator car 210, 220 may also include at least one counting device 125 located inside the cabin. The counting device 125 may be located along the interior wall (e.g., ceiling) of each elevator car 210, 220 and may be configured to detect a number of occupants 10 inside the cabin. In some embodiments, the counting device 125 may be operable to distinguish one or more objects detected inside the elevator car 210, 220.

[0024] For example, as shown in Figure 3, the counting device 125 may be configured to detect items present in the cabin that occupy the capacity of the elevator cars 210, 220 (e.g., passengers 10, ancillary items 12, etc.) and items in the cabin that are not expected to occupy the capacity of the elevator cars 210, 220 (e.g., rails 14, etc.). The counting device 125 may measure the number of items detected in the elevator cars 210, 220 and record the measured items as passenger data. As further described herein, the counting device 125 may be configured to transmit passenger data for each elevator car 210, 220 (e.g., current passenger data 142) to the dispatch controller 130 via the network 115.

[0025] Referring here to Figure 4, the dispatch controller 130 may include a computer device incorporating multiple hardware configurations that enable the dispatch controller 130 to receive data (e.g., operational data, call requests, commands, crew data, etc.), process information (e.g., crew capacity), and / or perform one or more processes (see Figure 5). An exemplary hardware configuration of the 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, the dispatch controller 130 may include a computer, a mobile user device, a remote station, a server, cloud storage, etc. In the illustrated embodiment, the dispatch controller 130 is shown and described herein as a separate device from other devices of the dispatch system 100, but in other embodiments, one or more aspects of the dispatch controller 130 may be integrated with one or more other devices of the dispatch system 100. In other words, the exemplary hardware configuration of the dispatch controller 130 as shown herein may be integrated with one or more of the run controller 105, caller 110, input device 120, and / or counting device 125.

[0026] The processor 132 may include any computer device capable of executing machine-readable instructions, the instructions of which may be stored in a non-temporary computer-readable medium such as memory 136. For example, the processor 132 may include a controller, an integrated circuit, a microchip, a computer, and / or any other computer processing unit capable of operating to perform the calculations and logical operations necessary to execute the program. As described in detail herein, the processor 132 is configured to perform one or more operations in accordance with instructions stored in memory 136, such as dispatch logic 138.

[0027] Continuing to refer to Figure 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 random access memory (RAM), read-only memory (ROM), flash memory, hard drive, and / or any device capable of storing machine-readable instructions. Memory 136 may include one or more datasets, which include, but are not limited to, operation data 140 received from the operation controller 105, current crew data 142 obtained from the counting device 125, and call assignment data 144 from the call device 110.

[0028] As further described herein, the current occupancy data 142 may include the real-time number of occupants 10 detected in the cabin of each elevator car 210,220 by the counting device 125. The call assignment data 144 may include call requests received from passengers 20 on at least one of the multiple floors 204A to 204D for transport by at least one of the multiple elevator cars 210,220. The dispatch controller 130 may be configured to store the current occupancy data 142 in memory 136 and associate the number of occupants 10 with the corresponding elevator cars 210,220. The dispatch controller 130 may further be configured to store the call assignment data 144 in memory 136 and correlate it with the operation data 140 and the current occupancy data 142 to determine whether to reassign the call requests.

[0029] Furthermore, memory 136 may include a non-temporary computer-readable medium for storing machine-readable instructions such as dispatch logic 140. For example, dispatch logic 140 may include executable instructions that enable dispatch system 100 to determine which of the multiple elevator cars 210, 220 to dispatch in response to receiving a call request at a first position for transport to a second position. Dispatch logic 140 may further facilitate determining the passenger capacity of each elevator car 210, 220 based on the number of passengers physically present in each elevator car 210, 220 in order to determine whether to reassign the call request to another elevator car 210, 220. As will be described in more detail herein, the dispatch system 100 may be configured to determine the passenger capacity of each elevator car 210, 220 and the reassignment of call requests based on one or more of the following received by the dispatch controller 130: operation data 140 from the operation controller 105, call device 101, and counting device 125, current passenger data 142, and / or call assignment data 144.

[0030] Referring to Figure 5, an exemplary method 300 is shown in which the dispatch system 100 is used to determine the passenger capacity of multiple elevator cars and reassigns a call to the elevator car with the greater passenger capacity. The steps shown and described herein, and the order in which they are presented, are exemplary only and should be understood to be included in various configurations, with additional and / or fewer steps, without departing from the scope of this disclosure.

[0031] In step 302, the dispatch system 100 may receive a call request at a first location among several locations within the work environment 200. The call request may be initiated in response to a passenger requesting a ride 20 activating the call device 110 at the first location, for example, the second floor 204B. The call device 100 may transmit the call request to the dispatch controller 130 via the network 115, and the call request may include data indicating the first location from which the call was made (e.g., the second floor 204B). The call request may further include data indicating the destination within the work environment 200 to which the passenger requesting a ride 20 intends to go (e.g., the first floor 204A).

[0032] In step 304, the dispatch controller 130 may retrieve operation data 140 for each elevator car 210, 220 from the corresponding operation controller 105. The dispatch controller 130 may be configured to determine various movement parameters for each elevator car 210, 220 from the operation data 140, such as the current position of the first elevator car 210 relative to the first elevator shaft 202 (for example, moving between the fourth floor 204D and the third floor 204C), the current direction of movement of the first elevator car 210 (for example, towards the first floor 204A), and the current speed of movement of the first elevator car 210. The dispatch controller 130 may also determine the current position of the second elevator car 220 relative to the second elevator shaft 212 (for example, stationary on the fourth floor 204D), the current direction of movement of the second elevator car 220 (for example, towards the first floor 204A), the current speed of movement of the second elevator car 220, and so on.

[0033] In step 306, the dispatch controller 130 may be configured to analyze the operation data 140 of each elevator car 210,220 to determine whether the current direction of movement of the elevator cars 210,220 is toward a first position (e.g., the second floor 204B). In response to determining that one or more elevator cars 210,220 are not moving toward the first position, the dispatch controller 130 may be configured in step 308 to exclude a particular elevator car 210,220 from further consideration. In other words, the dispatch controller 130 may determine that any of the elevator cars 210,220 that are moving in a direction different from the direction toward the first position (relative to the current position of the elevator cars 210,220) are not the best elevator cars to respond to a call request. In this example, the first elevator car 210 and the second elevator car 220 may include multiple passengers 10 moving from the fourth floor 204D to the first floor 204A, and the dispatch controller 130 may determine that each elevator car 210,220 is moving toward the first position.

[0034] Continuing to refer to Figure 5, in step 310, the dispatch controller 130 may be configured to determine whether the current position of each elevator car 210,220 is before the first position (e.g., the second floor 204B), or whether the elevator cars 210,220 have moved beyond the first position. That is, the dispatch controller 130 may determine that any of the elevator cars 210,220 that are currently beyond the first position are not the best elevator cars to respond to a call request. If it is determined that one or more of the elevator cars 210,220 are not before the first position, the dispatch controller 130 may be configured in step 308 to exclude a particular elevator car 210,220 from further consideration.

[0035] In this example, the first elevator car 210 is located between the fourth floor 204D and the third floor 204C, and the second elevator car 220 is located on the fourth floor 204D, so the dispatch controller 130 may determine that each elevator car 210, 220 is currently located just before the first position. In steps 312 to 318, the dispatch controller 130 may be configured to determine the passenger capacity of each elevator car 210, 220 in response to the determination that the elevator cars 210, 220 are located just before the first position (e.g., the second floor 204B) in the elevator shafts 202, 220.

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

[0037] Continuing to refer to Figure 5, in step 314, the dispatch controller 130 may be configured to determine the occupancy rate of each of the multiple elevator cars 210,220 based on at least the current occupant data 142 (i.e., the number of occupants 10 in each elevator car 210,220) and the maximum occupancy capacity 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 multiple elevator cars 210,220 in memory 136. It should be understood that the size and / or shape of each cabin of the multiple elevator cars 210,220 may be a determining factor in the maximum occupancy capacity. In this example, the elevator cars 210, 220 may be substantially similar in size and / or shape, resulting in relatively similar maximum passenger capacities for the first elevator car 210 and the second elevator car 220. In other examples, the elevator cars 210, 220 may be of various sizes and / or shapes, resulting in different maximum passenger capacities for the first elevator car 210 and the second elevator car 220.

[0038] In this example, if the first elevator car 210 has one passenger 10 and a maximum passenger capacity of six, the dispatch controller 130 may be configured to determine that the occupancy rate of the first elevator car 210 is approximately 1:6 (for example, approximately 16.67%). Furthermore, if the second elevator car 220 has two passengers 10 and a maximum passenger capacity of six, the dispatch controller 130 may be configured to determine that the occupancy rate of the first elevator car 210 is approximately 3:6 (for example, approximately 50%). Furthermore, if the total number of passengers in the second elevator car 220 is two and the maximum passenger capacity is six, the dispatch controller 130 may also be configured to determine that the occupancy rate of the second elevator car 220 is approximately 2:6 (for example, 33.33%).

[0039] Continuing to refer to Figure 5, in step 316, the dispatch controller 130 may be configured to determine at least one of the multiple elevator cars 210,220 that has the maximum available passenger capacity. The dispatch controller 130 may determine at least one of the multiple elevator cars 210,220 that has the maximum available passenger capacity by comparing the occupancy rates of each of the multiple elevator cars 210,220. In this example, the dispatch controller 130 may be configured to determine that the first elevator car 210 has the maximum available passenger capacity to respond to a call on the second floor 204B because the first elevator car 210 has a lower occupancy rate than the second elevator car 220. It should be understood that the dispatch controller 130 may further compare the operation data 140 of each elevator car 210,220 to determine which of the multiple elevator cars 210,220 to assign the call request to.

[0040] For example, the dispatch controller 130 may compare the operation data 140 to determine one or more operation parameters (e.g., speed of movement, operating status, current position, etc.) of multiple elevator cars 210, 220. The dispatch controller 130 may also analyze the operation data 140 if the elevator cars 210, 220 have similar and / or different maximum empty passenger capacities. Therefore, it should be understood that the dispatch controller 130 may be configured to assign a call request to at least one of the multiple elevator cars 210, 220 even if the empty passenger capacity of one of the elevator cars 210, 220 is greater than the empty passenger capacity of another elevator car. For example, the dispatch controller 130 may assign a call request to the first elevator car 210 based on the fact that the distance between the first elevator car 210 and the first position (e.g., the second floor 204B) is shorter than the distance between the second elevator car 220 and the first position. In an example where the first elevator car 210 has one or more additional call assignments to the second elevator car 220, the dispatch controller 130 may decide to assign the call request to the second elevator car 220 based on the fact that the second elevator car 220 is traveling at a greater speed than the first elevator car 210.

[0041] In this example, if there is a first elevator car 210 with the largest available passenger capacity among a plurality of elevator cars 210,220, the dispatch controller may assign the call to the first elevator car 210 in step 318. In some embodiments, the dispatch controller 130 may be configured to communicate with the call device 100 to send a message to a passenger 20 at a first location (e.g., the second floor 204B). For example, the dispatch controller 130 may communicate identification information of at least one of the plurality of elevator cars 210,220 (e.g., the first elevator car 210) that has been assigned to respond to the call request. In other embodiments, the dispatch controller 130 may identify at least one of a plurality of elevator shafts 202,212 (e.g., the first elevator car 210) from which the elevator cars 210,220 may arrive. Messages may be transmitted via the calling device 110 in various appropriate formats, including, for example, via a display (e.g., text format, image format, etc.) or a speaker (e.g., audio format).

[0042] Continuing to refer to Figure 5, in step 320, the dispatch controller 130 may be configured to determine whether the first elevator car 210 will stop at an intermediate position before arriving at the first position to respond to the call request received in step 302. In some embodiments, the dispatch controller 130 may detect that the first elevator car 210 has stopped at an intermediate position (e.g., the third floor 204C) located just before the first position (e.g., the second floor 204B), in response to receiving operation data 140 from the operation controller 105 indicating such movement. For example, the operation data 140 may indicate that the current position of the first elevator car 210 is at an intermediate position when the speed of movement of the first elevator car 210 has decreased to zero. In some embodiments, the dispatch controller 130 may determine that the first elevator car 210 will stop at an intermediate position in response to receiving user input from an input device 120 inside the first elevator car 210. In other embodiments, the dispatch controller 130 may be configured to detect when the elevator door 206 of the first elevator car 210 opens to an intermediate position, and / or when the access door 207 of the second floor 204B opens for the first elevator shaft 202.

[0043] In a further embodiment, the dispatch controller 130 may detect that a subsequent call request (e.g., call assignment data 144) assigned to the first elevator car 210 is from an intermediate position. In this example, the subsequent call request may be received by the dispatch controller 130 and assigned to the first elevator car 210 at a time after the call request from step 302 has been assigned to the first elevator car 210 in step 318. In another example, the subsequent call request may be received by the dispatch controller 130 and assigned to the first elevator car 210 at a time before the call request from step 302 has been assigned to the first elevator car 210 in step 318. It should be understood that the dispatch controller 130 may determine whether the first elevator car 210 will stop at an intermediate position by various other suitable methods using the operation data 140, the current occupant data 142, and / or the call assignment data 144, without departing from the scope of this disclosure.

[0044] Continuing to refer to Figure 5, in response to determining in step 320 that the first elevator car 210 is not stopped (or assigned) at an intermediate position before the first position, the dispatch controller 130 is configured to maintain the dispatch of the first elevator car 210 to the first position (e.g., the second floor 204B) and respond to the call in step 322. Alternatively, in response to determining in step 320 that the first elevator car 210 has stopped (or been assigned) at an intermediate position before reaching the first position, the dispatch controller 130 is configured to perform a reassignment evaluation of the call request received in step 302. The first elevator car 210 may accept one or more passengers 20 from an intermediate position (e.g., the third floor 204C) before arriving at the first position (e.g., the second floor 204B), and as a result, the dispatch controller 130 may determine whether the first elevator car 210 is still the best elevator car among the multiple elevator cars 210, 220 in order to respond to the call request.

[0045] In steps 312 to 316, the dispatch controller 130 may re-evaluate the passenger capacity of each of the multiple elevator cars 210, 220. In step 312, the dispatch controller 130 may retrieve updated passenger data 142 from the multiple elevator cars 210, 220 via each counting device 125 located inside each elevator car 210, 220. The updated passenger data 142 may reflect any passengers 20 who have entered the first elevator car 210 from an intermediate position, or any passengers 10 who have left the first elevator car 210 at an intermediate position. The updated passenger data 142 may further include an updated numerical value for the number of passengers 10 in each of the multiple elevator cars 210, 220. In step 314, the dispatch controller 130 may calculate the updated occupancy rate of each of the multiple elevator cars 210, 220 based on the updated passenger data 142. In step 316, the dispatch controller 130 may determine whether the first elevator car 210 maintains the maximum available passenger capacity relative to the other elevator cars 210, 220, or whether at least one of the other elevator cars 210, 220 (for example, the second elevator car 220) has a larger available passenger capacity than the first elevator car 210.

[0046] In response to determining that the first elevator car 210 has the maximum available passenger capacity for the remaining elevator cars within the working environment 200, the dispatch controller 130 may be configured to reconfirm the assignment of the call request to the first elevator car 210 in step 318. Alternatively, in response to determining that the first elevator car 210 does not have the maximum available passenger capacity for at least one of the remaining elevator cars (e.g., the second elevator car 220), the dispatch controller 130 may be configured to reassign the call received in step 302 to the elevator car that has the maximum available passenger capacity. In this example, the first elevator car 210 may accept two passengers 20 from the third floor 204C (e.g., the intermediate position) before arriving at the second floor 204B (e.g., the first position). Therefore, the number of passengers 10 in the first elevator car 210 may be equal to 3 passengers 10, and the number of passengers 10 in the second elevator car 220 may be equal to 2 passengers 10. In this case, the dispatch controller 130 may determine that the second elevator car 220 has a smaller occupancy rate (and a larger maximum empty passenger capacity) than the first elevator car 210.

[0047] Continuing to refer to Figure 5, in step 318, the dispatch controller 130 may reassign the call from the first elevator car 210 to the second elevator car 220. It should be understood that the dispatch controller 130 may further compare the operational data 140 of each elevator car 210,220 when re-evaluating the original assignment to determine which of the multiple elevator cars 210,220 to reassign the call request. Thus, the dispatch controller 130 may obtain and compare the updated operational data 140 of each of the multiple elevator cars 210,220, in addition to the updated occupant data 142, to determine whether to reassign the call request from the first elevator car 210 to at least one of the other multiple elevator cars in the work environment 200.

[0048] In response to determining that the first elevator car 210 has a higher occupancy rate (and a lower maximum empty passenger capacity) than the second elevator car 220, the dispatch controller 130 may be configured to orient the first elevator car 210 to a second position (e.g., the first floor 204A) different from a first position (e.g., the second floor 204B). In other words, the dispatch controller 130 may reorient the first elevator car 210 to a second destination position so that the first elevator car 210 does not stop at the first position (e.g., the second floor 204B) in order to respond to the call initially assigned to the first elevator car 210 in step 318. Thus, the call request received in step 302 may not be assigned to the first elevator car 210 so that the first elevator car 210 does not stop at the first destination position on the second floor 204B.

[0049] Continuing to refer to Figure 5, if the call is reassigned to the second elevator car 220 in step 318, the dispatch controller 130 may determine in step 320 whether the second elevator car 220 will stop (or is scheduled to stop) at an intermediate position. If the dispatch controller 220 determines that the second elevator car 220 will not stop at an intermediate position before arriving at the first position (e.g., the second floor 204B), it may maintain the call assignment from the second floor 204B to the second elevator car 210. Alternatively, if the dispatch controller 130 determines that the second elevator car 220 has stopped at an intermediate position, it may repeat steps 312-318.

[0050] All technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art of the subject, unless otherwise specified. Where a singular noun is used herein, it includes the plural noun unless the context clearly indicates otherwise.

[0051] The above description is illustrative and not intended to be restrictive. Those skilled in the art can make various modifications and / or changes without departing from the general scope of this disclosure. For example, as already described, the above embodiments (and / or aspects thereof) may be used in combination with each other. Furthermore, some of the above embodiments may be omitted without departing from the scope of this disclosure. Additionally, specific situations or materials may be modified to suit the teachings of various embodiments without departing from their scope. Many other embodiments will also be apparent to those skilled in the art upon consideration of the above description.

Claims

[Claim 1] The method described in the specification.

Images