Patent Description:
Modern development in high-rise building and skyscraper architecture has led to the design and construction of skyscrapers classified as "supertall" buildings that exceed about <NUM> feet (about <NUM> meters) or even "megatall" buildings, which can exceed <NUM>,<NUM> feet (about <NUM> meters). However, implementing conventional elevator systems in supertall or megatall buildings can present issues. For example, travelers aiming to reach a specific higher floor may in a supertall building conceivably must stop at a very large number of other floors to let other passengers off and on before reaching their destination. This increases travel time for travelers aiming to reaching the highest floors, and indirectly requires many more elevator shafts to still allow acceptable travel times, thereby reducing effective floor space on each floor for all levels.

One solution to reduce elevator traveling time in supertall or megatall buildings has been the design and implementation of "sky lobbies", which are sometimes referred to as "shared lobbies. " A sky lobby is an intermediate interchange floor in the building where people can transfer from a shuttle elevator (sometimes referred to as an shuttle lift or express elevator) to one or more conventional elevators that serve a particular segment of the building. Unlike conventional elevators, a shuttle elevator travels directly between the sky lobby and another floor (e.g., from the sky lobby to the ground floor or from the sky lobby to the roof). Once at the sky lobby, travelers can transfer to the conventional elevator system which stops at every floor included in the segmented portion of the building.

<CIT> describes an elevator system operating a plurality of elevators each having a door that faces a landing, an information output device for notifying information of the next arriving elevator car before it arrives, and an elevator group management and user guidance device for managing operations of the plurality of elevators and outputting information to the information output device. The information output device notifies users standing on an landing entrance of the elevator number of an elevator corresponding to the next elevator car arriving at a floor with the information output device provided, a position of the landing of the elevator, and the number of passengers in the elevator.

<CIT> describes an elevator system with a group management control system that manages the operation of a plurality of elevator cars, and is provided with: a destination floor user number totaling processing unit that totals the number of passengers boarding from each floor from the number of times that a destination floor call is registered and totals the number of passengers disembarking at each floor from the passenger number for each destination floor call; and a processing unit for predicting the number of people within an elevator car that calculates the number of passengers in an elevator car as a prediction value from the determined number of passengers boarding from each floor, the number of passengers disembarking at each floor, and the number of people who are currently in the elevator car. The name of an elevator car and/or the floor(s) at which said elevator car will stop are announced for an elevator car that it is determined to be an elevator car that will not reach full capacity on the basis of the prediction value. As a result, elevator transport capacity is improved during periods of congestion even when the boarding area is in a saturated state due to the number of people who are present in said boarding area.

The present invention is defined by the scope of the appended claims <NUM>-<NUM>. According to a first aspect, a shuttle elevator loading system is provided in accordance with claim <NUM>.

In some embodiments, the elevator system controller dynamically controls the at least one display unit based on the assignment information.

In some embodiments, the elevator controller controls the elevator shuttle loading system to reduce passenger crowding based on the number of allocated passengers corresponding to at least one of the shuttle elevators.

In some embodiments, the elevator system controller controls the arrival display unit to display assignment information that directs a non-allocated passenger to an available shuttle elevator.

In some embodiments, the display assignment information is dynamically changed as an availability of the shuttle elevators changes.

In some embodiments, the elevator system controller is configured to control boarding of the at least one passenger based on a number of allocated passenger corresponding to a given shuttle elevator.

In some embodiments, the at least one sensor comprises a sensor configured to monitor each individual elevator queue and to detect one or more persons in the vicinity of one or more of the elevator queues.

In some embodiments, the at least one sensor includes an elevator queue sensor installed at an individual elevator queue.

In some embodiments, the elevator queue sensor is configured to monitor the individual elevator queue and to detect one or more persons in the vicinity of the individual elevator queue.

According to second aspect, a method of controlling a shuttle elevator loading system is provided in accordance with claim <NUM>.

Further embodiments may include dynamically controlling the at least one display unit based on the assignment information.

Further embodiments may include controlling the elevator shuttle loading system to reduce passenger crowding based on the number of allocated passengers corresponding to at least one of the shuttle elevators.

Further embodiments may include controlling the arrival display unit to display the assignment information that directs a non-allocated passenger to an available shuttle elevator.

Further embodiments may include dynamically changing the assignment information as an availability of the shuttle elevators changes.

Further embodiments may include controlling boarding of the at least one passenger based on a number of allocated passenger corresponding to a given shuttle elevator.

Technical effects of embodiments of the present disclosure include the ability to process a service request related to a conveyance system and determine whether to initiate a service call based on one or both of system status and one or more inputs.

As described above, shuttle elevators system are different from conventional elevator systems in that the destination of a given shuttle elevator is already known rather requiring a passenger to input a destination floor. However, shuttle elevator systems typically include a group of several individual shuttle elevators capable of servicing one or more passengers. Known boarding methods allow passengers to simply choose any shuttle elevator within the group without any guidance or direction. Further, the shuttle elevator door remains opens or is closed based on a fixed timer regardless as to the number of passengers boarded in a given car or attempting to board the car. This method reduces travel efficiently because it allows for one or more given shuttle cars to be overloaded and/or slows departure times, while one or more other shuttle cars remain available to provide a quicker and more convenient travel experience. Hence the challenge is to efficiently direct passengers to fill one so that it can leave immediately before directing passengers to the next.

At least one non-limiting embodiment of the invention provides a shuttle elevator system including an improved passenger boarding system. The shuttle elevator boarding system includes one or more passenger sensors that operate in conjunction with an arrival display zone. The sensor(s) detect a current number of passengers allocated to a given in real-time. Based on the allocated passengers, the arrival display zone directs one or more passengers to a particular shuttle car that will provide the most efficient travel experience (e.g., the quickest departure without being overcrowded with an excessive number of passengers).

With reference now to <FIG>, a perspective view of a conveyance system in the form of an elevator system <NUM> is illustrated according to a non-limiting embodiment. The elevator system includes an elevator car <NUM>, a counterweight <NUM>, a tension member <NUM>, a guide rail <NUM>, a machine <NUM>, a position reference system <NUM>, and an elevator controller <NUM>. Although the elevator car <NUM> is illustrated as a single-deck car, other types of elevator cars such as a double-deck car, for example, can be implemented without departing from the scope of the invention.

The counterweight <NUM> is configured to balance a load of the elevator car <NUM> and is configured to facilitate movement of the elevator car <NUM> concurrently and in an opposite direction with respect to the counterweight <NUM> within an elevator hoistway <NUM> and along the guide rail <NUM>.

The elevator controller <NUM> is located, as shown, in a controller room <NUM> of the elevator hoistway <NUM> and is configured to control the operation of the elevator system <NUM>, and particularly the elevator car <NUM>. For example, the elevator controller <NUM> may provide drive signals to the machine <NUM> to control the acceleration, deceleration, leveling, stopping, etc. of the elevator car <NUM>. The elevator controller <NUM> may also be configured to receive position signals from the position reference system <NUM> or any other desired position reference device. When moving up or down within the elevator hoistway <NUM> along guide rail <NUM>, the elevator car <NUM> may stop at one or more landings <NUM> as controlled by the elevator controller <NUM>. Although shown in a controller room <NUM>, those of skill in the art will appreciate that the elevator controller <NUM> can be located and/or configured in other locations or positions within the elevator system <NUM>. In one embodiment, the elevator controller <NUM> may be located remotely or in the cloud.

In one example, embodiments disclosed herein may be applicable conveyance systems such as an elevator system <NUM> and a conveyance system component such as an elevator car <NUM> of the elevator system <NUM>. In another example, embodiments disclosed herein may be applicable conveyance systems such as an escalator system and a conveyance system component such as a moving stair of the escalator system.

Turning to <FIG>, a building facility <NUM> including a shuttle elevator system <NUM> is illustrated according to a non-limiting embodiment. The environment can include a facility <NUM> (e.g., a high rise building) comprising at least one elevator shaft supporting at least one elevator car. The facility <NUM> includes an elevator shaft <NUM> supporting an elevator car <NUM> and an elevator shaft <NUM> supporting an elevator car <NUM>. Note that the elevator car <NUM> can be accessed at least at a lower lobby <NUM> (e.g., a ground floor of the facility <NUM>) and a shared lobby <NUM> (e.g., a middle floor of the facility <NUM>). Further, note that the elevator car <NUM> can be accessed at least at the shared lobby <NUM> and an upper lobby <NUM> (e.g., a top floor of the facility <NUM>). In this regard, the shaft <NUM> only permits the elevator car <NUM> to travel between a lower floor and a middle floor (which can be considered an initial segment), and the shaft <NUM> only permits the elevator car <NUM> to travel between the middle floor and a top floor (which can be considered a subsequent segment). The arrangement of elevator shafts <NUM> and <NUM> is for exemplary purposes only and any desired arrangement and number of elevator shafts and elevator cars may be used.

The shuttle elevator system <NUM> comprises a computer <NUM>. The computer <NUM> comprises a processor <NUM> and a memory <NUM>. The memory <NUM> stores program instructions that are executable by the processor <NUM> to cause the operation described herein. The computer <NUM> can support and/or be a part of an elevator system that operates the elevator cars <NUM> and <NUM>. The elevator system comprises one or more location devices.

In accordance with one or more embodiments, the one or more location devices can comprise at least a location device <NUM> with a location zone <NUM> (extending a radius R1), a location device <NUM> with a location zone <NUM> (extending a radius R2), a location device <NUM> with a location zone <NUM> (extending a radius R3), a location device <NUM> with a location zone <NUM> (extending a radius R4), and a location device <NUM> with a location zone <NUM> (extending a radius R5). The location device <NUM> can be located within and correspond thereto the lower lobby <NUM>. The location device <NUM> can be located within and correspond thereto the shared lobby <NUM>. The location device <NUM> can be located within and correspond thereto the upper lobby <NUM>. The location device <NUM> can be located within and correspond thereto the elevator car <NUM>. The location device <NUM> can be located within and correspond thereto the elevator car <NUM>. Note that each radius of the location zone <NUM> can be predetermined and configured within the elevator system, such as at a distance of a width of the a lobby or an elevator car. The elevator system interacts with a mobile device (e.g., the mobile device <NUM>) to provide a hands-free user interface for generating elevator calls.

Moreover, any location zone and location device may be placed as desired within shuttle the elevator system <NUM>, such as in an elevator fixture. In one embodiment, the location zone may be rectangular, planar, <NUM>-dimensional, or any other desired shape.

The elevator system <NUM> described herein is an example and is not intended to suggest any limitation as to the scope of use or operability of embodiments described herein (indeed additional or alternative components and/or implementations may be used). Further, while single items are illustrated for items of the elevator system <NUM>, these representations are not intended to be limiting and thus, any item may represent a plurality of items. Embodiments of t the elevator system <NUM> can include configurations for a mobile device centric system (e.g., when the mobile device <NUM> detects trigger signals from the one or more location devices), a location device centric system (e.g., when the one or more location devices detects trigger signals from the mobile device <NUM>), or a combination thereof. Further, embodiments of the elevator system <NUM> and the elevator system can include configurations for a lobby focused system, an elevator focused system, or a combination thereof.

The elevator system <NUM> can satisfy single-segment elevator trips and multi-segment elevator trips. In accordance with one or more embodiments, if multiple event triggers are placed on a same floor, the elevator system <NUM> can detect a sequence of these multiple event triggers to automatically place a single-segment trip. Further, the elevator system <NUM> can determine how many elevator trip segments are required for the multi-segment trip and what guidance should be provided to a user during the multi-segment trip.

The computer <NUM> can include any processing hardware, software, or combination of hardware and software utilized by the elevator system to carry out computer readable program instructions by performing arithmetical, logical, and/or input/output operations. The computer <NUM> can be implemented local to the facility <NUM>, remote to the facility <NUM>, or as a cloud service. The computer <NUM> can be representative of a plurality of computers dispersed throughout the elevator system <NUM>. The processor <NUM> can comprise one or more central processing units (CPU(s)), also referred to as processing circuits, coupled via a system bus to the memory <NUM> and various other internal or external components (e.g., the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>). The memory <NUM> can include a read only memory (ROM) and a random access memory (RAM). The computer <NUM>, by utilizing the processor <NUM> and the memory <NUM>, operates to provide/support automatic calls of the elevator system for navigation in the facility <NUM> with respect to any elevator trip. The computer <NUM>, by utilizing the processor <NUM> and the memory <NUM>, operates to support the hands-free user interface of the mobile device <NUM> for navigation in the facility <NUM> with respect to any elevator trip. The computer <NUM>, by utilizing the processor <NUM> and the memory <NUM>, can operate to communicate with the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. The computer <NUM> can also determine a status of each elevator car <NUM> and <NUM>, such as which floor an elevator car is located, which direction an elevator car is traveling, a number of stops designated for an elevator trip, an elevator door position, an elevator door operation (opening vs. closing), etc. The computer <NUM> can operate one or more timers (e.g., movement timers and disconnect timers) with respect to the operations described herein.

The location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be an electromechanical component that generates the corresponding location zones <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. Examples of the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> include radio devices, such as Wi-Fi devices, Bluetooth devices, wireless beacon devices, etc. The location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can utilize software and/or firmware to carry out operations particular thereto. In this regard, the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be configured to provide triggering signals (e.g., one-way communication devices advertising a location; a radio signal being broadcast to the mobile device <NUM>). For example, the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> themselves can provide a triggering signal to the mobile device that causes the mobile device <NUM> to place an elevator call, e.g., if the mobile device receives a correct event trigger sequence, with is a set of ordered interactions between the mobile device <NUM> and the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>.

The location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can include transceivers (e.g., communications and/or interface adapter) that can communicate with the computer <NUM> and/or the mobile device <NUM>. The location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may communicate with the computer <NUM> with wires or wirelessly. In this regard, the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be configured to detect the mobile device <NUM> (e.g., continuously sensing the mobile device <NUM>; the mobile device <NUM> altering a field of the corresponding location zone) and/or communicate with the mobile device <NUM> with respect to the corresponding location zones <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. For example, the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> themselves can automatically cause the execution of an elevator call based on one or more event trigger sequences respective to interactions with the mobile device <NUM>. Further, the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can generate one or more electrical signals to the computer <NUM> as a function of the mobile device detection (e.g., generates an electrical signal in response to detecting a presence of the mobile device <NUM>) and/or the mobile device communication.

The mobile device <NUM> can include any processing hardware, software, or combination of hardware and software utilized to carry out computer readable program instructions by performing arithmetical, logical, and/or input/output operations. The mobile device <NUM> can include any wireless device operated by a passenger, such as a laptop, a table computer, a mobile phone, a smartphone, a wireless beacon on the user (e.g., an electronic bracelet), radio frequency identification card, smartwatches, implants, smart glasses, wearable components, and the like. The mobile device <NUM> can interact/detect/communicate with the one or more location devices of the elevator system, can support/provide/execute an application and a hands-free user interface, and can connect to the computer <NUM> or a cloud server <NUM> (wirelessly through an internet, cellular, or cloud connection).

The cloud server <NUM>, comprising a processor <NUM> and a memory <NUM> as described herein, can include any processing hardware, software, or combination of hardware and software in communication with the mobile device <NUM> to carry out computer readable program instructions by performing arithmetical, logical, and/or input/output operations. The cloud server <NUM> can be implemented local to the facility <NUM>, remote to the facility <NUM>, or as a cloud service to the mobile device <NUM>. The cloud server <NUM>, by utilizing the processor <NUM> and the memory <NUM>, operates to support automatic calls executed by the mobile device <NUM>.

In accordance with one or more embodiments, the mobile device <NUM> executes elevator calls in response to one or more event trigger sequences based on a logic in the application (to interpret a correct sequence). The application allows the mobile device <NUM> to send messages via cellular towers or other communication means (provide information over the internet to cloud-based internet servers, such as the cloud server <NUM>). The cloud server <NUM> can in turn send elevator requests to the elevator controllers (e.g., the computer <NUM>) in a specific building (e.g., the facility <NUM>). Thus, the mobile device <NUM> detecting a trigger at one of the lobbies <NUM>, <NUM>, and <NUM> or within the elevator car <NUM> or <NUM> is able to send a message through a cellular network that eventually is received by the elevator system. Further, the logic in the application can store default, preset, and/or manual entries of floor destinations with respect to a user profile within the application and can cause the execution of elevator calls based on these entries as the mobile device <NUM> interacts with the elevator system <NUM>. In accordance with one or more embodiments, the mobile device <NUM> outputs a unique signal identifying the mobile device <NUM> to the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> to provide one or more event trigger sequences to the elevator system <NUM>. An event trigger sequence is a set of ordered interactions between the mobile device and the location devices <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. The elevator system can also operate automatic calls based on sequential detections of the mobile device <NUM> (e.g., an event trigger sequence). In this regard, the elevator system can execute each segment request internally, while a user is continuously notified of each elevator assignment without user confirmation (e.g., hands-free operation).

In accordance with one or more embodiments, the elevator system <NUM> herein can be applied to non-smartphone type systems where a passenger's identity is automatically detected via biometric scans or other means (the same resulting multi-segment trip call could be executed). For example, if a video analytics system is in-place at each floor, a process flow can be executed where if a user is detected on the lower lobby <NUM> and then the user is detected in elevator <NUM>, then an elevator call for the elevator <NUM> is automatically placed for the user at shared lobby <NUM>.

Referring now to <FIG>, a shuttle elevator loading system <NUM> is illustrated according to a non-limiting embodiment. The shuttle elevator loading system <NUM> includes a plurality of shuttle elevators 302a, 302b, 302c configured to service a building lobby <NUM>. The shuttle elevator system <NUM> operates differently from conventional elevator systems in that it is capable of servicing passengers without requiring call buttons or floor destination selection buttons. That is, when a shuttle elevator 302a, 302b, 302c is assigned a call, the doors of the called shuttle elevator are opened for a set time period and departs when the time period expires.

The shuttle elevator loading system <NUM> further includes one or more sensors 306a, 306b, 306c, 306z configured to detect one or more one passengers 308a, 308b, 308c, 308z, one or more display units 310a, <NUM>10b, 310c, 310z located at a display zone 312a, 312b, 312c, 312z of the lobby <NUM>, and an elevator system controller <NUM>. Accordingly, the shuttle elevator loading system <NUM> can execute a closed-loop passenger allocation process (rather than open-loop timer parameters), which actively directs and loads passengers to fill a targeted shuttle elevator before directing passengers to one or more remaining shuttle elevators that are partially filled or currently unavailable for boarding.

The sensors 306a, 306b, 306c, 306z include a lobby sensor 306z and elevator sensors 306a, 306b, 306c. The lobby sensor 306z can monitor the entire lobby <NUM> simultaneously and is configured to detect one or both of an allocated passenger 308a, 308b, 308c that is allocated to a shuttle elevator 302a, 302b, 302c, respectively, and a non-allocated passenger 308z that is not allocated to a shuttle elevator 302a, 302b, 302c. The elevator sensors 306a, 306b, 306c are installed at a respective shuttle elevator 302a, 302b, 302c (e.g., at the outside and/or inside of the elevator car) and/or at a respective elevator display zone 312a, 312b, 312c. Accordingly, the elevator sensors 306a, 306b, 306c can detect one or more allocated passengers 308a, 308b, 308c that are allocated to the shuttle elevator 302a, 302b, 302c servicing a respective elevator display zone 312a, 312b, 312c.

The lobby sensor 306z and/or the elevator sensors 306a, 306b, 306c can be constructed as various types of sensors or sensor systems including, but not limited to, a person recognition sensor and sensor system, or a motion detection sensor. The person recognition sensor system includes, for example, a camera and controller capable of detecting and tracking human movement and location.

The motion sensor is configured to detect motion of a passenger 308a, 308b, 308c, 308z. In one or more embodiments, the motion sensors can include an arrival motion sensor 306z and elevator motion sensor 306a, 306b, 306c. The arrival motion sensor 306z is configured to detect motion of a passenger 308z located at the arrival display zone 312z. The elevator motion sensors 306a, 306b, 306c are configured to detect motion of one or more passengers 308a, 308b, 308c located at a respective elevator display zone 312a, 312b, 312c.

The elevator system controller <NUM> is in signal communication with the sensors 306a, 306b, 306c, 306z, the display units 310a, 310b, 310c, 310z and the shuttle elevators 302a, 302b, 302c, while also monitoring passenger count and location in the lobby <NUM> and/or a given shuttle elevator 302a, 302b, 302c. The elevator controller <NUM> can be constructed as an electronic hardware controller that includes memory and a processor configured to execute algorithms and computer-readable program instructions stored in the memory. Accordingly, the elevator controller <NUM> can determine a number of allocated passengers 308a, 308b, 308c, 308z corresponding to each shuttle elevator 302a, 302b, 302c, and can generate assignment information that directs a non-allocated passenger 308z to an available shuttle elevator 302c.

The display units include an arrival display unit <NUM>10z and a plurality of elevator display units 310a, 310b, 310c. The arrival display unit <NUM> is located in an arrival display zone 312z that precedes the plurality of shuttle elevator 302a, 302b, 302c in order to reduce the possibility that a non-allocated passenger 308z will randomly choose to move toward a crowded shuttle elevator or a shuttle elevator that is not currently boarding passengers. Accordingly, once the elevator controller <NUM> determines which shuttle elevator is to be allocated to a given passenger, the elevator controller <NUM> can control the arrival display unit 310z to display assignment information instructing the allocated passenger to move to the corresponding shuttle elevator.

The elevator display units 310a, 310b, 310c are located at a respective elevator display zone 312a, 312b, 312c, which are located beyond the arrival display zone <NUM>. Accordingly, the elevator display units 310a, 310b, 310c identify a respective shuttle elevator 302a, 302b, 302c such that passengers 308a, 308b, 308c can confirm that they are waiting at the correct zone 312a, 312b, 312c instructed by the arrival display unit 310z.

Examples of the elevator display units 310a, 310b, 310c, 310z are illustrated in <FIG>. The arrival display unit <NUM> is configured to display assignment information that directs a non-allocated passenger 308z to an available shuttle elevator, e.g., shuttle elevator 302c. The display assignment information is dynamically changed as the availability and/or load of the shuttle elevators 302a, 302b, 302c change. The elevator display units 310a, 310b, 310c are configured to display boarding information of the shuttle elevators 302a, 302b, 302c corresponding to their respective display zones 312a, 312b, 312c. The boarding information includes, but is not limited to, an on-going boarding event, and an estimated time at which a boarding event will occur.

The elevator controller <NUM> directs passengers 308a, 308b, 308c, 308z to queue at the first available car until the sensors 306a, 306b, 306c, 306z indicate a given shuttle elevator 302a, 302b, 302c is fully allocated (e.g., currently on-board or waiting to board). The elevator controller <NUM> then directs passengers to the next available second shuttle elevator. Therefore, the elevator controller <NUM> can execute a closed-loop passenger allocation process (rather than open-loop timer parameters), which actively directs and loads passengers to fill a targeted shuttle elevator before directing passengers to one or more remaining shuttle elevators that are partially filled or currently unavailable for boarding.

The elevator controller <NUM> dynamically allocates passengers to a given shuttle elevator 302a, 302b, 302c based on the detection and monitoring performed by the sensors 306a, 306b, 306c, 306z, along with a preset passenger threshold assigned to the shuttle elevators 302a, 302b, 302c. For example, the elevator controller <NUM> can constantly track passenger allocations corresponding to each shuttle elevator 302a, 302b, 302c. Passenger allocations include the initial allocations determined by the elevator controller <NUM> at the initial time at which a passenger enters the arrival display zone 312z. And passenger allocations can include the actual location of a passenger determined by the sensors 306a, 306b, 306c, 306z. Accordingly, the elevator controller <NUM> can compare the number of passengers allocated to a given shuttle elevator 302a, 302b, 302c to the passenger threshold. When the number of allocated passengers exceeds the passenger threshold, the elevator controller <NUM> can determine the corresponding shuttle elevator is full. Accordingly, the elevator controller stops allocating passengers to the full shuttle elevator and then begins allocating passengers to another available shuttle elevator that has not reached its passenger threshold.

In one or more embodiments, the elevator controller <NUM> can actively modify a passenger allocation of a corresponding shuttle elevator 302a, 302b, 302c. When implementing the lobby sensor 306z as a person recognition sensor system, for example, the elevator controller <NUM> can track a location of one or more allocated passengers within the lobby <NUM>. When an allocated passenger correctly moves to their directed shuttle elevator 302a, 302b, 302c, the elevator controller <NUM> can maintain their original allocation until the allocated passenger boards the corresponding shuttle elevator 302a, 302b, 302c and departs the lobby <NUM>. When, however, an allocated passenger moves to a shuttle elevator 302a, 302b, 302c that is different from the originally allocated shuttle elevator 302a, 302b, 302c, the elevator controller <NUM> can remove the passenger allocation from the original originally allocated shuttle elevator 302a, 302b, 302c, and add a new passenger allocation to the shuttle elevator 302a, 302b, 302c chosen by the passenger.

Similarly, the elevator controller <NUM> can actively modify a passenger allocation of a corresponding shuttle elevator 302a, 302b, 302c when implementing motion detector sensors as the lobby sensor 306z and elevator sensors 306a, 306b, 306c. For example, the lobby sensor 306z can detect motion of a non-allocated passenger 308z located in the arrival display zone 312z, which in turn initiates the allocation process for allocating the passenger 308z to a shuttle elevator 302a, 302b, 302c. Once determining a targeted shuttle elevator (e.g., a non-crowded shuttle elevator 302c), the elevator controller <NUM> outputs assignment information, which is displayed on the arrival zone display unit 310z and instructs the passenger 308z to targeted shuttle elevator 302c. Accordingly, the previously non-allocated passenger (e.g., passenger 308z) is now deemed to be allocated to the targeted shuttle elevator (e.g., shuttle elevator 302c).

In one or more embodiments, once the passenger 308c is allocated, the elevator controller initiates a timer and initiates the time value to a time threshold. In the meanwhile, the elevator sensor 306c corresponding to the targeted shuttle elevator 302c continuously detects passengers entering and/or exiting the corresponding elevator display zone 312c, and outputs the detection to the elevator controller <NUM>. When the elevator controller <NUM> determines that the elevator sensor 306c detects a passenger entering the corresponding elevator display zone 312c within the time threshold, the elevator controller determines that the most recent allocated passenger 308c has successfully reached the instructed target shuttle elevator 302c and maintains the allocation.

When, however, the elevator controller <NUM> determines that the elevator sensor 306c has not detected a passenger entering the corresponding elevator display zone 312c within the time threshold (i.e., the timer value exceeds the time threshold), the elevator controller determines that the most recent allocated passenger 308c has not moved to the instructed target shuttle elevator 302c and removes this most recent allocation corresponding to the target elevator 302z. This scenario may occur when, for example, the allocated passenger 308z disregards the assignment information displayed on the arrival zone display unit <NUM>10z and instead moves to a different shuttle elevator or abandons the elevator trip all together (e.g., leaves the building). Accordingly, the allocation and load of the shuttle elevators can be dynamically adjusted based on the actions of the passengers.

The elevator controller <NUM> can also revise allocations shuttle elevators 302a, 302b, 302c that may result from passengers deciding to move to shuttle elevators to which they were initially assigned. For instance, the elevator controller <NUM> may receive an output from elevator sensor 306b indicating a passenger 308b has unexpectedly entered its elevator display zone 312b. This scenario may occur, for example, when a passenger was previously assigned to a targeted shuttle elevator (e.g., shuttle elevator 302c) decides to either move directly to shuttle elevator 302b or leave the assigned elevator display zone 312c and enter elevator display zone 312b. In either case, the elevator controller <NUM> can dynamically add a new allocation to elevator display zone 312b.

In one or more non-limiting embodiments, the elevator controller <NUM> can also control operation of the shuttle elevators 302a, 302b, 302c to discourage or reduce elevator overcrowding or inefficient ride operation. For example, a turnstile (not shown) may be installed ahead of the shuttle elevator doors, and can be in signal communication with the elevator controller <NUM>. The turnstile outputs a count value as passengers pass through the turnstile gate. The elevator controller <NUM> compares the turnstile count to a passenger allocation threshold assigned to the shuttle elevators 302a, 302b, 302c. When the turnstile count equals the passenger allocation threshold, the elevator controller <NUM> can output a turnstile control signal that locks the turnstile gate. Accordingly, passengers that were not allocated to the shuttle elevator may be prevented from overcrowding the elevator. Once the shuttle elevator departs, the elevator controller <NUM> can output control signal that unlocks the turnstile gate and allows a new group of allocated passengers to board the shuttle elevator once it becomes available.

In another example, the elevator controller <NUM> is pre-programmed with times at which the shuttle elevators 302a, 302b, 302c should depart the lobby <NUM>. The times can be dynamically adjusted based on the passenger traffic within the lobby <NUM> or predicted traffic within the lobby <NUM> based on traffic history. For example, the elevator controller <NUM> is capable of executing a passenger traffic learning algorithm to control passenger boarding of a one or more shuttle elevators 302a, 302b, 302c and/or to shut down shuttle elevators that are not needed during times of light traffic.

As described herein, various non-limiting embodiments provide a shuttle elevator system including an improved passenger boarding system. The shuttle elevator boarding system includes one or more passenger sensors that operate in conjunction with an arrival display zone. The sensor(s) detect a current number of passengers allocated to a given in real-time. Based on the allocated passengers, the arrival display zone directs one or more passengers to a particular shuttle car that will provide the most efficient travel experience (e.g., the quickest departure without being overcrowded with an excessive number of passengers).

As described above, embodiments can be in the form of processor-implemented processes and devices for practicing those processes. Embodiments can also be in the form of computer program code transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes a device for practicing the embodiments.

Those of skill in the art will appreciate that various example embodiments are shown and described herein, each having certain features in the particular embodiments, but the present disclosure is not thus limited, but are only limited by the appended claims.

Claim 1:
A shuttle elevator loading system (<NUM>) comprising:
a plurality of shuttle elevators (302a, 302b, 302c) configured to service a building lobby (<NUM>);
at least one sensor (306a, 306b, 306c, 306z) configured to detect at least one passenger (308a, 308b, 308c, 308z);
at least one display unit (310a, 310b, 310c, 310z) located at a display zone (312a, 312b, 312c, 312z) of the lobby (<NUM>); and
an elevator system controller (<NUM>) in signal communication with the at least one sensor (306a, 306b, 306c, 306z) and the at least one display unit (310a, 310b, 310c, 310z), the elevator system controller (<NUM>) configured to determine a number of allocated passengers (310a, 310b, 310c) corresponding to each shuttle elevator (302a, 302b, 302c), and to generate assignment information that directs a non-allocated passenger (308z) to an available shuttle elevator (302a, 302b, 302c);
wherein the at least one display unit includes an arrival display unit (310z) located in an arrival display zone (312z) that precedes the plurality of shuttle elevators (302a, 302b, 302c); and
characterized in that:
the at least one sensor comprises a lobby sensor (306z) and elevator sensors (306a, 306b, 306c); wherein the lobby sensor (306z) is configured to detect a passenger (308a, 308b, 308c, 308z) located at the arrival display zone (312z);
wherein the lobby sensor (306z) is configured to detect one or both of an allocated passenger (310a, 310b, 310c) that is allocated to a shuttle elevator (302a, 302b, 302c) respectively, and a non-allocated passenger (308z) that is not allocated to a shuttle elevator (302a, 302b, 302c);
wherein the elevator sensors (306a, 306b, 306c) are installed at a respective shuttle elevator (302a, 302b, 302c) and/or at a respective elevator display zone (312a, 312b, 312c);
wherein the elevator system controller (<NUM>) dynamically adjusts the number of allocated passengers (310a, 310b, 310c) corresponding to at least one shuttle elevator (302a, 302b, 303c) based at least in part on an output of the at least one sensor (306a, 306b, 306c, 306z) following an initial allocation assigned to the at least one passenger (310a, 310b, 310c); and
wherein the initial allocation is determined by the elevator controller (<NUM>) at an initial time at which a passenger enters the arrival display zone (312z).