Patent Description:
Existing elevator systems allow a user to submit an elevator call (e.g., a hall call or a destination call) using their own mobile device (e.g., a smartphone).

<CIT> discloses a system comprising the features of the preamble of the independent claims, including an input/output unit for receiving a user request to call an elevator and a processor for processing the user request to assign an elevator to the user. The processor performs one of a first assignment process and a second assignment process. The first assignment process includes determining whether a delay condition exists for delaying assignment of the elevator to the user, delating assignment of the elevator to the user based on determining that the delay condition exists, and assigning the elevator to the user based on determining that the delay condition does not exist. The second assignment process includes assigning the elevator to the user and notifying the user of the assignment, determining whether an assignment change condition exists, changing the assignment to another elevator based on determining that the assignment change condition exists, and notifying the user of the assignment change.

A method of reassigning an elevator call for an elevator car is provided in accordance with claim <NUM>.

Further embodiments may include that determining that the first elevator car cannot serve the elevator call further includes: determining that the first elevator car has encountered an operational fault and the first elevator car cannot serve the elevator call due to the operational fault.

Further embodiments may include that determining that the first elevator car cannot serve the elevator call further includes: determining that the first elevator car is delayed in traffic and the first elevator car cannot serve the elevator call due to the first elevator car being delayed in traffic.

Further embodiments may include that determining that the first elevator car cannot serve the elevator call further includes: determining that the mobile device has not entered the first elevator car within a selected period of time waiting at the boarding floor and the first elevator car cannot serve the elevator call due to the mobile device having not entered the first elevator car within the selected period of time waiting at the boarding floor.

Further embodiments may include: detecting a location of the mobile device, wherein determining that the first elevator car cannot serve the elevator call further includes: determining the first elevator car will be waiting at the boarding floor greater than a selected period of time in response to the location of the mobile device and the first elevator car cannot serve the elevator call.

Further embodiments may include that the detecting further includes: connecting, using a building sensor, to the mobile device via at least one of Wi-Fi and Bluetooth; and determining a distance between the building sensor and the mobile device.

Further embodiments may include that the detecting further includes: detecting, using a building sensor, a wireless signal of the mobile device, wherein the building sensor does not connect to the wireless signal; and determining a distance between the building sensor and the mobile device.

Further embodiments may include that the detecting further includes: detecting a beacon transmitted by a building sensor using the mobile device; and determining a distance between the building sensor and the mobile device in response to a strength of the beacon.

Further embodiments may include that determining that the first elevator car cannot serve the elevator call further includes further includes: determining a passenger wait time of the first elevator car to arrive at the boarding floor; determining a passenger wait time of the second elevator car to arrive at the boarding floor; determining that the passenger wait time of the first elevator car is greater than the passenger wait time of the second elevator car and that the first elevator car cannot serve the elevator call.

Further embodiments may include that receiving a passenger wait time threshold from the mobile device, wherein determining that the first elevator car cannot serve the elevator call further includes: determining a first passenger wait time for the first elevator car to arrive at the boarding floor; determining a second passenger wait time for the second elevator car to arrive at the boarding floor; and determining that a difference between the first passenger wait time and the second passenger wait time is greater than the passenger wait time threshold and that the first elevator car cannot serve the elevator call.

Further embodiments may include that determining that the first elevator car cannot serve the elevator call further includes further includes: determining a passenger wait time of the first elevator car to arrive at the boarding floor; determining a passenger wait time of the second elevator car to arrive at the boarding floor; determining that the passenger wait time of the first elevator car is greater than the passenger wait time of the second elevator car.

Further embodiments may include that prior to assigning a second elevator car to the elevator call, the method further includes: activating an alert on the mobile device that the passenger wait time of the first elevator car is greater than the passenger wait time of the second elevator car.

Further embodiments may include: receiving a selection input from the mobile device selecting the second elevator car.

Further embodiments may include: moving the second elevator car to the destination floor.

Further embodiments may include: receiving a selection input from the mobile device; and adjusting a user setting in response to the selection input.

Further embodiments may include that a user adjusts one or more user setting of the elevator system through a selection input, wherein the user settings are elevator reassignment criteria options.

An elevator system is provided in accordance with claim <NUM>.

A computer program product tangibly embodied on a computer readable medium is provided in accordance with claim <NUM>.

Technical effects of embodiments of the present disclosure include the ability for an elevator control system to receive elevator destination calls from a mobile device, detect if an assigned elevator car cannot serve the destination call, and reassigned the elevator call to another elevator car in accordance with preferences from a passenger received from the mobile device.

The foregoing features and elements may be combined in various combinations within the scope of the appende claims.

<FIG> depicts an elevator call control system <NUM> in an example embodiment. The elevator call control system <NUM> includes one or more elevator system <NUM> installed at a building <NUM>. In some embodiments, the building <NUM> may be a building or a collection of buildings that may or may not be physically located near each other. The building <NUM> may include any number of floors. Persons entering the building <NUM> may enter at a lobby floor, or any other floor, and may go to a destination floor via one or more conveyance devices, such as the elevator system <NUM>.

The elevator system <NUM> may be operably connected to one or more computing devices, such as a system controller <NUM>. The system controller <NUM> may be configured to control dispatching operations for one or more elevator cars <NUM> associated with one or more elevator systems <NUM>. It is understood that the elevator system <NUM> may utilize more than one system controller <NUM>. Although three elevator systems <NUM> are shown in <FIG>, it is understood that any number of elevator systems <NUM> may be utilized. Additional, although each elevator system <NUM> is illustrated as having one elevator car <NUM>, it is understood that any number of elevators cars <NUM> may be used each elevator system <NUM>. The elevator cars <NUM> of <FIG> may be referred to also as a first elevator car 103a, a second elevator car 103b, and a third elevator car 103c. It is understood that other components of the elevator system <NUM> (e.g., drive, counterweight, safeties, etc.) are not depicted for ease of illustration in <FIG>.

The system controller <NUM> may include a processor <NUM>, memory <NUM> and communication module <NUM>, as shown in <FIG>. The processor <NUM> can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory <NUM> is an example of a non-transitory computer readable storage medium tangibly embodied in the system controller <NUM> including executable instructions stored therein, for instance, as firmware. The communication module <NUM> may implement one or more communication protocols as described in further detail herein.

Also shown in <FIG> is a mobile device <NUM>. The mobile device <NUM> may be a mobile computing device that is typically carried by a person, such as, for example a smart phone, PDA, smart watch, tablet, laptop, etc. The mobile device <NUM> may include a touch screen (not shown). The mobile device <NUM> may include a processor <NUM>, memory <NUM> and communication module <NUM> as shown in <FIG>. The processor <NUM> can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory <NUM> is an example of a non-transitory computer readable storage medium tangibly embodied in the mobile device <NUM> including executable instructions stored therein, for instance, as firmware. The communication module <NUM> may implement one or more communication protocols as described in further detail herein. The mobile device <NUM> belongs to a resident or employee of the building <NUM> who currently has access to the elevator system <NUM>.

Each mobile device <NUM> may transmit an elevator call <NUM> to the system controller <NUM> and the system controller <NUM> will move an elevator car <NUM> in response to the elevator call <NUM>. The elevator call <NUM> may include a "boarding floor" and a "destination floor. " The "boarding floor" is where the person with the mobile device <NUM> desires to board the elevator car <NUM> and the "destination floor" is where the person with the mobile device <NUM> intends to travel. In one embodiment, the elevator call <NUM> may only include the "destination floor" and the "boarding floor" may be automatically determined by the elevator system <NUM>. Embodiments herein generate a graphical user interface on the mobile device <NUM> through an application <NUM>. The mobile device <NUM> may transmit an elevator call <NUM> through an application <NUM>.

The mobile device <NUM> and the system controller <NUM> communicate with one another. For example, the mobile device <NUM> and the system controller <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The mobile device <NUM> and the system controller <NUM> may communicate over a wireless network, such as <NUM>. 11x (Wi-Fi), short-range radio (Bluetooth), cellular, satellite, etc. In some embodiments, the system controller <NUM> may include, or be associated with (e.g., communicatively coupled to) a networked element, such as kiosk, beacon, hall call fixture, lantern, bridge, router, network node, door lock, elevator control panel, building intercom system, etc. The networked element may communicate with the mobile device <NUM> using one or more communication protocols or standards. For example, the networked element may communicate with the mobile device <NUM> using near field communications (NFC). A connection between the mobile device <NUM> and the system controller <NUM> may be direct between mobile device <NUM> and system controller <NUM> or it may be through a web service. The connection also may include security elements such as VPN or authentication or encryption. In other embodiments, the system controller <NUM> may establish connection with a mobile device <NUM> that is inside and/or outside of the building <NUM> in order to detect a location of the mobile device <NUM>. A location of the mobile device may be determined using various technologies including GPS, triangulation, trilateration, signal strength detection, accelerometer detection, gyroscopic detection, or barometric pressure sensing by way of non-limiting example. The triangulation and trilateration may use various wireless technologies including but not limited to Wi-Fi and Bluetooth. In example embodiments, the mobile device <NUM> communicates with the system controller <NUM> over multiple independent wired and/or wireless networks. Embodiments are intended to cover a wide variety of types of communication between the mobile device <NUM> and system controller <NUM>, and embodiments are not limited to the examples provided in this disclosure. Communication between the mobile device <NUM> and the system controller <NUM> will allow the system controller <NUM> to determine the location of the mobile device <NUM> in relation to the elevator system <NUM>. The location of the mobile device <NUM> may be communicated to the system controller <NUM> through a plurality of sensors <NUM>, discussed further below.

Each elevator system <NUM> may also include a sensor <NUM> configured to detect whether a mobile device <NUM> has entered the elevator car <NUM>. In an embodiment, the sensor <NUM> may be located on the elevator car <NUM>. The system controller <NUM> is in electronic communication with each sensor <NUM> through a wired connection and/or wireless connection. In an alternative embodiment, each sensor may be in indirect communication with the system controller <NUM> through the mobile device <NUM>. In a non-limiting example, if the sensors <NUM> are a Bluetooth beacon, then the mobile device <NUM> can detect when it is in proximity of the sensor <NUM>, then the mobile device <NUM> can communicate with the system controller <NUM> that it is in the elevator car <NUM>.

Further, although only one sensor <NUM> is shown per elevator car <NUM> for ease of illustration it is understood that each elevator car <NUM> may contain one or more sensors <NUM>. Each sensor <NUM> may also be configured to detect operational data of the elevator car <NUM>, such as for example, elevator door position (e.g. open/closed), elevator car location, speed, voltage, vibration, acceleration, noise, deceleration, jerk, and any other performance parameter of any component of the elevator system <NUM> known to one of skill in the art.

The sensors <NUM> detect the presence of an individual in an elevator car <NUM> and identify the individual using various sensing technology, such as, for example Wi-Fi transceivers, Bluetooth transceivers, radio transceivers, visual recognition cameras, people counters, microphones, etc. to detect persons and/or mobile devices entering and leaving the elevator car. The type and nature of sensors <NUM> within the sensor system <NUM> is not limited to the embodiments disclosed herein. The mobile device <NUM> and the sensors <NUM> communicate with one another. For example, the mobile device <NUM> and the sensors <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The mobile device <NUM> and the sensors <NUM> may communicate over a wireless network, such as <NUM>. 11x (Wi-Fi), ZigBee, Z-Wave and short-range radio (Bluetooth).

In an embodiment, the sensors <NUM> may include a Wi-Fi transceiver to connect to a mobile device <NUM> when the mobile device <NUM> enters the elevator car <NUM> in order to identify the mobile device <NUM>. In another embodiment, the sensors <NUM> may include a Bluetooth transceiver to connect to a mobile device <NUM> when the mobile device <NUM> enters the elevator car <NUM> in order to identify the mobile device <NUM>. The sensors <NUM> are configured to detect a distance between the elevator car <NUM> and the mobile device <NUM> to determine whether the mobile device <NUM> is entering and/or leaving the elevator car <NUM>. The sensors <NUM> may be configured to detect a distance between the elevator car <NUM> and the mobile device <NUM> through wireless signal strength detection.

Communication between the mobile device <NUM> and the sensors <NUM> can be one-way or two-way communication. In one example, if Bluetooth is utilized then the mobile device <NUM> may advertise a Bluetooth signal and the sensors <NUM> may receive it. In another example, the sensors <NUM> may advertise a Bluetooth signal and the mobile device <NUM> may receive it. In another example, there may be two-way Bluetooth communication between the sensors <NUM> and the mobile device <NUM>. In another example, a Wi-Fi transceiver (i.e. sensor <NUM>) may be placed in an elevator car and the mobile device may detect the Wi-Fi beacon frame as part of the <NUM>. 11x protocol as well as the received signal strength of that beacon frame to approximate the distance between the Wi-Fi transceiver and the mobile device <NUM> but not connect to the Wi-Fi signal. In another example, the mobile device <NUM> may actively send a probe request looking for Wi-Fi transceivers, then a Wi-Fi transceiver (i.e. sensor <NUM>) located in an elevator car may extract the MAC address of the mobile device <NUM> from the probe request and approximate distance between the Wi-Fi transceiver and the mobile device <NUM> from received signal strength.

In another embodiment, the mobile device <NUM> and the sensors <NUM> may communicate over a non-radio frequency network. In an example the mobile device <NUM> and the sensors <NUM> may communicate through audio transmission, such as, for example a high frequency audio transmission. The mobile device <NUM> may emit a chirp signature between <NUM>-<NUM> that one or more microphones (i.e. sensor <NUM>) can detect and extract a signature to determine which mobile device <NUM> is present. In this example, Audio gain at speaker may be measured to a distance between the microphone and the mobile device <NUM> may be determined in response to the audio gain. Advantageously, more microphones may help better determine distance. Alternatively, the speakers (i.e. sensors <NUM>) may be located in the elevators car <NUM> and may emit the high frequency audit for the mobile device <NUM> to detect. Advantageously, one or more speakers may be help better determine distance.

The elevator call control system <NUM> may also include an indoor positioning system <NUM> comprising one or more building sensors <NUM> in electronic communication with the system controller <NUM>. The building sensors <NUM> may be located throughout the building <NUM>. Each building sensor <NUM> may be configured to emit and/or detect a wireless signal. The building sensor <NUM> may be configured to emit a wireless signal that may be detected by the mobile device <NUM>. The building sensor <NUM> may be able to detect a wireless signal emitted by mobile device <NUM>. In an embodiment, a building sensor <NUM> may be a door lock that controls access to a room within the building <NUM>. In an embodiment, a building sensor <NUM> may be a wireless access protocol device that provides Wi-Fi access to computing devices throughout the building <NUM>.

The building sensors <NUM> may detect the location of the mobile device <NUM> within a building <NUM> using various sensing technology, such as, for example Wi-Fi transceivers, Bluetooth transceivers, radio transceivers, etc. to detect the presence of mobile devices <NUM> within the building <NUM>. The type and nature of building sensors <NUM> within the sensor system <NUM> is not limited to the embodiments disclosed herein. The mobile device <NUM> and the building sensors <NUM> communicate with one another. For example, the mobile device <NUM> and the building sensors <NUM> may communicate with one another when proximate to one another (e.g., within a threshold distance). The mobile device <NUM> and the building sensors <NUM> may communicate over a wireless network, such as <NUM>. 11x (Wi-Fi), ZigBee, Z-Wave and short-range radio (Bluetooth).

In an embodiment, the building sensors <NUM> may include a Wi-Fi transceiver to connect to a mobile device <NUM> when the mobile device <NUM> is located within a threshold distance in order to determine the location of the mobile device <NUM>. In another embodiment, the building sensors <NUM> may include a Bluetooth transceiver to connect to a mobile device <NUM> when the mobile device <NUM> is located within a threshold distance in order to determine the location of the mobile device <NUM>. The building sensors <NUM> may be configured to detect a distance between each of the building sensor <NUM> and the mobile device <NUM> through wireless signal strength detection. The wireless signal strength detected between the mobile device <NUM> and a single building sensor <NUM> may be enough to approximate a location of the mobile device <NUM> or the indoor positioning system <NUM> may utilize three or more building sensors <NUM> to triangulate the position of the mobile device <NUM> utilizing the wireless signal strength detected between the mobile device <NUM> and each of the three building sensors <NUM>.

Communication between the mobile device <NUM> and the building sensors <NUM> can be one-way or two-way communication. In one example, if Bluetooth is utilized then the mobile device <NUM> may advertise a Bluetooth signal and the building sensors <NUM> may receive it. In another example, the building sensors <NUM> may advertise a Bluetooth signal and the mobile device <NUM> may receive it. In another example, there may be two-way Bluetooth communication between the building sensors <NUM> and the mobile device <NUM>. In another example, a the building sensor <NUM> may be a Wi-Fi transceiver (i.e., a wireless access protocol device) and the mobile device <NUM> may detect the Wi-Fi beacon frame as part of the <NUM>. 11x protocol as well as the received signal strength of that beacon frame to approximate the distance between the Wi-Fi transceiver and the mobile device <NUM> but not connect to the Wi-Fi signal. In another example, the mobile device <NUM> may actively send a probe request looking for Wi-Fi transceivers, then a Wi-Fi transceiver (i.e. building sensor <NUM>) may extract the MAC address of the mobile device <NUM> from the probe request and approximate distance between the Wi-Fi transceiver and the mobile device <NUM> from received signal strength.

In one embodiment, the mobile device <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM> and transmit that distance to the system controller <NUM> to determine the location of the mobile device <NUM>. In another embodiment, the indoor positioning system <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM> and transmit that distance to the system controller <NUM> to determine the location of the mobile device <NUM>. The location of the mobile device <NUM> may be determined by the mobile device <NUM> or by the indoor positioning system <NUM>. In one embodiment, the mobile device <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM>, then the mobile device <NUM> may use that distance to determine the location of the mobile device <NUM> to transmit to the system controller <NUM>. In another embodiment, the indoor positioning system <NUM> may determine a distance between the mobile device <NUM> and each of the building sensors <NUM>, then the indoor positioning system <NUM> may use that distance to determine the location of the mobile device <NUM> to transmit to the system controller <NUM>. A global positioning system (GPS) or any other known location determining method may also be utilized to determine a location of the mobile device.

Referring now to <FIG> with continued reference to <FIG>. <FIG> shows a flow chart of a method <NUM> of reassigning an elevator call <NUM> for an elevator car <NUM>. The method <NUM> may be performed by system controller <NUM>. <FIG> illustrates a mobile device <NUM> graphical user interface <NUM> for operating the application <NUM>. The mobile device <NUM> may be a laptop computer, smart phone, tablet computer, smart watch, or any other mobile computing device known to one of skill in the art. In the example shown in <FIG>, the mobile device <NUM> is a touchscreen smart phone. The mobile device <NUM> may include a display screen <NUM> and an input device <NUM>, such as, example, a mouse, a touch screen, a scroll wheel, a scroll ball, a stylus pen, a microphone, a camera, etc. In the example shown in <FIG>, since the mobile device <NUM> is a touchscreen smart phone, then the display screen <NUM> may also function as an input device <NUM>. <FIG> illustrate a graphical user interface <NUM> on the mobile device <NUM>. A user may interact with the graphical user interface <NUM> through a selection input, such as, for example, a "click", "touch", verbal command or any other input to the user interface <NUM>.

The application <NUM> may include various user settings <NUM> that may be adjusted through the graphical user interface <NUM>, as shown in <FIG> at <NUM>. It is understood that the user settings <NUM> illustrated in <FIG> are examples and the application <NUM> may include fewer user settings or additional user settings that are not illustrated in <FIG>. There may be one or more user settings <NUM> to adjust through a user input. The user settings <NUM> may be elevator reassignment criteria options for the elevator system <NUM> to determine when to notify a user of available elevator cars <NUM> and reassignments of elevator cars <NUM> and when to automatically reassign elevator cars elevator cars <NUM>. The user settings <NUM> may include when to notify a user of the mobile device <NUM> when the elevator car <NUM> assigned to their elevator call <NUM> is late, such as, for example, how late is too late. For example, the user settings <NUM> at <NUM> may be set to only notify the user of the mobile device <NUM> if the elevator car <NUM> selected to answer the elevator call <NUM> will be greater than a selected period of time late. The user settings <NUM> may also include when to notify a user of the mobile device <NUM> when another elevator car <NUM> not assigned to their elevator call <NUM> will arrive sooner than the elevator car <NUM> that has been assigned to their elevator call <NUM>, at <NUM>. For example, the user settings <NUM> at <NUM> may be set to only notify that user if a second elevator car 103b will arrive sooner than the elevator car <NUM> selected to answer the elevator call <NUM> if the second elevator car 103b will be there sooner than a selected period of time, as shown at <NUM>. The user settings <NUM> may also include whether or not to give the user of the mobile device <NUM> a notification (e.g., an alert) if another better or faster elevator car <NUM> is available to serve the elevator call <NUM> at <NUM>. The user settings <NUM> may also include whether or not to have the system controller <NUM> automatically change to another better or faster elevator car <NUM> if one is available to serve the elevator call <NUM> at <NUM>. The user settings <NUM> may also include what to have the system controller <NUM> do if the individual carrying the mobile device were to walk away without boarding an elevator car <NUM> assigned to their elevator call <NUM>, at <NUM>.

At block <NUM> of method <NUM>, an elevator call <NUM> is received from a mobile device <NUM>. The elevator call <NUM> including a destination request to travel from a boarding floor to a destination floor. At block <NUM>, a first elevator car 103a is assigned to the elevator call <NUM>. At block <NUM>, an alert is activated on the mobile device <NUM> that the first elevator car 103a has been assigned to the elevator call <NUM>, at <NUM>.

At block <NUM>, it is determined that the first elevator car 103a cannot serve the elevator call <NUM>. It may be determined that the first elevator car 103a cannot serve the elevator call <NUM> by determining that the first elevator car 103a has encountered an operational fault (e.g., broken down) and the first elevator car 103a cannot serve the elevator call <NUM> due to the operation fault. It may also be determined that the first elevator car 103a cannot serve the elevator call <NUM> by determining that the first elevator car 103a is delayed in traffic and the first elevator car 103a cannot serve the elevator call <NUM> due to being delaying in traffic. It may also be determined that the first elevator car 103a cannot serve the elevator call <NUM> by determining that the mobile device <NUM> has not entered the first elevator car 103a within a selected period of time waiting at the boarding floor and the first elevator car 103a cannot serve the elevator call <NUM> due to the mobile device <NUM> not having entered the first elevator car 103a within the selected period of time waiting at the boarding floor. Thus, the first elevator car 103a may now be free to serve additional elevator calls <NUM> after the selected period of time waiting at the boarding floor.

It may also be determined that the first elevator car 103a cannot serve the elevator call <NUM> because a user setting is violated. The application <NUM> may notify a user of the mobile device <NUM> that a user setting <NUM> is violated by the first elevator car <NUM>. The application <NUM> may automatically attempt to find a new elevator car <NUM> that does not violate a user setting <NUM> or the application <NUM> may request a user input to allow the violation of the user setting <NUM> and keep the first elevator car 103a assigned to the elevator call <NUM> or the application <NUM> may request an adjustment to a user setting <NUM>. The method <NUM> may also include: detecting a location of the mobile device <NUM>. It may also be determined that the first elevator car 103a cannot serve the elevator call <NUM> by determining the first elevator car 103a will be waiting at the boarding floor greater than a selected period of time in response to the location of the mobile device <NUM> and the first elevator car 103a cannot serve the elevator call <NUM> due to the first elevator car 103a being tied up for too long at the boarding floor waiting on the individual carrying the mobile device <NUM> to arrive and board the first elevator car 103a.

The location of the mobile device <NUM> may be detected by: connecting a building sensor <NUM> to the mobile device <NUM> via at least one of Wi-Fi and Bluetooth; and determining a distance between the building sensor <NUM> and the mobile device <NUM>, which may be done with three or more building sensors <NUM> to triangulate the position of the mobile device <NUM>.

The location of the mobile device <NUM> may be detected by: detecting, using a building sensor <NUM>, a wireless signal of the mobile device <NUM> where the building sensor <NUM> does not connect to the wireless signal; and determining a distance between the building sensor <NUM> and the mobile device <NUM>, which may be done with three or more building sensors <NUM> to triangulate the position of the mobile device <NUM>.

The location of the mobile device <NUM> may be detected by: detecting a beacon transmitted by a building sensor <NUM> using the mobile device <NUM>; and determining a distance between the building sensor <NUM> and the mobile device <NUM> in response to a strength of the beacon, which may be done with three or more building sensors <NUM> to triangulate the position of the mobile device <NUM>. A global positioning system (GPS) or any other known location determining method may also be utilized to determine a location of the mobile device.

The method <NUM> further comprises: receiving a desired passenger wait time from the mobile device <NUM>. The desired passenger wait time may depict how long an individual carrying the mobile device <NUM> is willing to wait for the first elevator car 103a to arrive at the boarding floor. The location of the mobile device <NUM> may be detected by: determining that the first elevator car 103a will not arrive at the boarding floor within the desired passenger wait time and the first elevator car 103a cannot serve the elevator call <NUM>.

It may also be determined that the first elevator car 103a cannot serve the elevator call <NUM> by: determining a passenger wait time of the first elevator car 103a to arrive at the boarding floor; determining a passenger wait time of the second elevator car 103b to arrive at the boarding floor; determining that the passenger wait time of the first elevator car 103a is greater than the passenger wait time of the second elevator car 103b and that the first elevator car 103a cannot serve the elevator call <NUM> due to the first elevator car 103a is greater than the passenger wait time of the second elevator car 103b. The system controller <NUM> may automatically switch over to the second elevator car 103b (or any other elevator car <NUM>) if the second elevator car 103b has a shorter passenger wait time than the first elevator car 103a. The system controller <NUM> may automatically switch over to the second elevator car 103b (or any other elevator car <NUM>) if the second elevator car 103b has a shorter passenger wait time than the first elevator car 103a by a passenger wait time threshold that was received from the mobile device <NUM>. The passenger wait time threshold may be saved in the user settings <NUM>. For example, the individual carrying the mobile device <NUM> (i.e., the passenger) may only wish that the system controller <NUM> transfer the elevator call <NUM> to the elevator car 103b if the second elevator car 103b can arrive <NUM> seconds earlier (e.g., passenger wait time threshold) than the first elevator car 103a.

The system controller <NUM> may request confirmation from the individual carrying the mobile device <NUM> to switch over to the second elevator car 103b (or any other elevator car <NUM>) if the second elevator car 103b has a shorter passenger wait time than the first elevator car 103a. The system controller <NUM> may alert the individual of the shorter passenger wait time by activating an alert on the mobile device <NUM> indicating that the second elevator car 103b has a shorter passenger wait time than the first elevator car 103a, as shown in <FIG> at <NUM>. The system controller <NUM> may receive a selection input <NUM> from the mobile device <NUM> selecting the second elevator car 103b (e.g., or "yes" at <NUM> in <FIG>) and then the system controller <NUM> can transfer the elevator call <NUM> to the second elevator car <NUM>.

At block <NUM>, a second elevator car 103b is assigned to the elevator call <NUM>. At block <NUM>, an alert is activated on the mobile device <NUM> indicating that the second elevator car 103b has been assigned to the elevator call <NUM>, as shown at <NUM>. The alert may be visual, audible, and/or vibratory. As shown in <FIG> at <NUM>, the alert may be displayed on the display screen <NUM> of the mobile device <NUM>. The method <NUM> may further comprise, moving the second elevator car 103b to the destination floor. The method <NUM> may further comprise: receiving a selection input from the mobile device <NUM>; and adjusting a user setting <NUM> in response to the selection input.

Claim 1:
A method (<NUM>) of reassigning an elevator call (<NUM>) for an elevator car (<NUM>), the method comprising:
receiving (<NUM>) an elevator call (<NUM>) from a mobile device (<NUM>), the elevator call (<NUM>) including a destination request to travel from a boarding floor to a destination floor;
assigning (<NUM>) a first elevator car (103a) to the elevator call (<NUM>);
activating (<NUM>) an alert on the mobile device (<NUM>) that the first elevator car (103a) has been assigned to the elevator call (<NUM>);
determining (<NUM>) that the first elevator car (103a) cannot serve the elevator call (<NUM>);
assigning (<NUM>) a second elevator car (103b) to the elevator call (<NUM>); and
activating (<NUM>) an alert on the mobile device (<NUM>) indicating that the second elevator car (103b) has been assigned to the elevator call (<NUM>);
characterized in that determining that the first elevator car (103a) cannot serve the elevator call (<NUM>) comprises:
receiving a desired passenger wait time from the mobile device (<NUM>) and determining that the first elevator car (103a) will not arrive at the boarding floor within the desired passenger wait time and the first elevator car (103a) cannot serve the elevator call (<NUM>).