Patent Description:
In present high rise buildings, conventional elevator systems require passengers to take multi-segment trips (e.g., ride multiple elevators) to get to their destination. In turn, the conventional elevator systems of the high rise buildings require the passengers to learn a layout of the high rise buildings (e.g., which elevators serve which floors) to initiate and accomplish these multi-segment trips. Multi-segment trips are challenging and add a level of complication to elevator travel, especially to visitors who are new to a particular high rise building.

<CIT> describes an elevator operation device disclosing the features of the preambles of the independent claims, enabling a reduction in wasted calls based on a signal transmitted from the elevator operation device possessed by a passenger, where a length of time between calls from the device is used to filter unwanted calls.

<CIT> describes operation management of various traffic machines, including elevators, where a communication with a mobile device helps to manage movement of the traffic machines.

<CIT> describes an elevator call registering system where a passenger has a 'tag' which communicates with the elevator system to aid in the calling of elevator cars.

According to one aspect of the invention, there is provided a computer-implemented method for preventing an unintended call for a conveyance apparatus of a conveyance system according to claim <NUM>.

Further embodiments may include that the travel direction of the mobile device is determined in response to the first interaction and a location of the first location device.

Further embodiments may include that the travel direction of the mobile device is determined in response to a period of time between the first interaction and a previous interaction between the mobile device and a location device, the previous interaction being detected immediately prior to the first interaction.

Further embodiments may include that the travel direction of the mobile device is determined in response to the first interaction and an acceleration of the mobile device.

Further embodiments may include that the travel direction of the mobile device is determined in response to the first interaction and an intermediate interaction between the mobile device and a location device, the intermediate interaction being detected between the first interaction and the second interaction.

Further embodiments may include that the automatically filtering includes blocking the second interaction and any subsequent interaction between the mobile device and a location device for until at least one of a selected period of time has expired, the mobile device has reached a selected geographical location, and a selected interaction is detected between the mobile device and a selected location device.

Further embodiments may include that the automatically filtering includes blocking the second interaction and any subsequent interaction between the mobile device and a location device until an input selection is received from a user of the mobile device through an application installed on the mobile device.

Further embodiments may include that the first location device of the second location device is located in at least one of a first elevator lobby providing access to the elevator car, the elevator car, and an elevator fixture.

According to another aspect of the invention, there is provided a mobile device according to claim <NUM>.

Further embodiments may include that the travel direction of the mobile device is determined in response to the first interaction and an intermediate interaction between the mobile device and a location device, the intermediate interaction being detected between the first triggering signal and the second interaction.

The technical effects and benefits of the hands-free mechanism described herein include automatic calls of any elevator system, along with a hands-free user interface, for navigation in a high rise building with respect to any elevator trip, including multi-segment trips. The technical effects and benefits of the hands-free mechanism described herein also include preventing unnecessary and unintended automatic calls of any elevator system.

The subject matter which is regarded as the disclosure is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the disclosure are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
The following descriptions should not be considered limiting in any way.

In accordance with one or more embodiments, a hands-free mechanism provides passengers an ability to get from any source floor to any destination floor based on sequential interactions between two or more location devices and a mobile device. For instance, the hands-free mechanism operates to determine and execute an elevator call based on an initial interaction of the mobile device with a first of the two or more location devices and a subsequent interaction of the mobile device with a second of the two or more location devices. The hands-free mechanism also filters out/blocks unintended elevators calls to prevent confusion in the elevator system <NUM>.

<FIG> depicts an environment for a sequence triggering of a call for an elevator car of an elevator system <NUM> according to one or more embodiments. The environment of <FIG> may also be used to prevent unintentional sequence triggering of a call for an elevator car of the elevator system 100The environment can include a facility <NUM> (e.g., a high rise building) comprising at least one elevator shaft supporting at least one elevator car. As shown in <FIG>, 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. In one embodiment, elevator cars <NUM> and <NUM> may be able to serve and stop at any desired floors.

The environment of <FIG> 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 <NUM> that operates the elevator cars <NUM> and <NUM>. The elevator system <NUM> 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 R1, R2, R3, R4, R5 of each location zone <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can be predetermined and configured within the elevator system <NUM>, such as at a distance of a width of a lobby or an elevator car. The elevator system <NUM> 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 the environment of <FIG> and 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 and/or size.

The environment of <FIG> and 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 environment of <FIG>, these representations are not intended to be limiting and thus, any item may represent a plurality of items. Embodiments of the environment of <FIG> and the elevator system <NUM> can include configurations for a mobile device centric system (e.g., when one or more location devices is advertising a trigger signal and the mobile device <NUM> detects trigger signals from the one or more location devices), a location device centric system (e.g., when the mobile device <NUM> is advertising a trigger signal and the one or more location devices detects trigger signals from the mobile device <NUM>), or a combination thereof. Further, embodiments of the environment of <FIG> and the elevator system <NUM> can include configurations for a lobby focused system, an elevator focused system, or a combination thereof.

The environment of <FIG> and 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 environment of <FIG> and the elevator system <NUM> can detect a sequence of these multiple event triggers to automatically place a single-segment trip. Further, the environment of <FIG> and 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. Additionally, the environment of <FIG> and the elevator system <NUM> can detect a sequence of these multiple event triggers to automatically ignore the placement of a single-segment trip or multi-segment trip.

The computer <NUM> can include any processing hardware, software, or combination of hardware and software utilized by the elevator system <NUM> 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 environment of <FIG> and 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 <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>, 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 <NUM>, 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 mobile device <NUM> can also include a Microelectromechanical system (MEMS) sensor configured to detected accelerations of the mobile device <NUM>. The MEMS sensor may be a sensor such as, for example, an accelerometer, a gyroscope, or a similar sensor known to one of skill in the art.

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 and/or prevents execution of 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> or locally through location devices using short range wireless communication, such as, for example, Bluetooth). 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 <NUM>. 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 environment of <FIG> and 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 environment of <FIG> and 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 <NUM> 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 <NUM> 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 environment of <FIG> and the elevator system <NUM> herein can be applied to non-smartphone type systems where a passenger's identity is automatically detected via biometric scans, facial recognition, computer chip embedded within an ID (e.g. RFID Chip) or other means (the same resulting multi-segment trip call could be executed). Advantageously, using a non-smartphone type system would allow a person to be tracked and elevator calls processed and/or canceled, whether or not they are in possession of their smartphone. 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>.

Turning now to <FIG>, a process flow <NUM> of the elevator system <NUM> is depicted according to one or more embodiments. The process flow <NUM> is an example operation to determine and execute an elevator call based on an initial interaction of the mobile device <NUM> with a first of the two or more location devices and a subsequent interaction of the mobile device <NUM> with a second of the two or more location devices (e.g., an event trigger sequence). Note that any combination of at least two location devices of the elevator system <NUM> can be utilized to construct an event trigger sequence to implement the process flow <NUM>.

For instance, the process flow <NUM> can utilize the following location device combinations in a lobby focused system to the construct the event trigger sequences of (<NUM>) a location device <NUM> interaction followed by a location device <NUM> interaction and (<NUM>) a location device <NUM> interaction followed by a location device <NUM> interaction.

Further, the process flow <NUM> can utilize the following location device combinations in an elevator focused system to the construct the event trigger sequences of (1E) a location device <NUM> interaction followed by a location device <NUM> interaction and (2E) a location device <NUM> interaction followed by a location device <NUM> interaction.

Furthermore, the process flow <NUM> can utilize the following location device combinations in a joint lobby-elevator system to the construct the event trigger sequences of (1C) a location device <NUM> interaction followed by a location device <NUM> interaction, (2C) a location device <NUM> interaction followed by a location device <NUM> interaction, (3C) a location device <NUM> interaction followed by a location device <NUM> interaction, and (4C) a location device <NUM> interaction followed by a location device <NUM> interaction, along with utilizing the combinations (<NUM>), (<NUM>), (1E), and (2E) described herein. Note that any three or more interaction combination are also configurable.

For ease of explanation, the process flow <NUM> is now described with respect to a lobby focused system where the first and second location devices respectively align with the event trigger sequences of (<NUM>) the location device <NUM> interaction followed by the location device <NUM> interaction.

The process flow <NUM> begins at block <NUM>, with a detection of an initial interaction between a first location device at a first location and a mobile device. In accordance with one or more embodiments, the first location device can be the location device <NUM>, and the first location can be the lower lobby <NUM>. In a mobile device centric system, the initial interaction can include the mobile device <NUM> detecting a one-way triggering signal by the location device <NUM>, which the mobile device <NUM> determines as a first event in the event trigger sequence. In a location device centric system, the initial interaction can alternatively be the location device <NUM> detecting the mobile device <NUM>, which is determined by the location device <NUM> or the computer <NUM> as the first element in an event trigger sequence.

At block <NUM>, a detection of a subsequent interaction between a second location device at a second location and a mobile device occurs. In accordance with one or more embodiments, the second location device can be the location device <NUM>, and the second location can be the shared lobby <NUM>. In the mobile device centric system, the subsequent interaction can include the mobile device <NUM> detecting a one-way triggering signal by the location device <NUM>, which the mobile device <NUM> determines as a second event in the event trigger sequence. In the location device centric system, the subsequent interaction can alternatively be the location device <NUM> detecting the mobile device <NUM>, which is determined by the location device <NUM> or the computer <NUM> as the second element in an event trigger sequence.

At block <NUM>, the elevator system <NUM> automatically executes a call for an elevator car in response to detecting the subsequent interaction after the initial interaction. For example, in the mobile device centric system, the mobile device <NUM> can communicate to the computer <NUM> to execute a call for the elevator <NUM> to retrieve a passenger operating the mobile device <NUM> in the shared lobby <NUM>. In the location device centric system, after the computer <NUM> receives triggering events from the location device <NUM> and the location device <NUM> in order, the computer <NUM> can execute a call for the elevator <NUM> to retrieve a passenger operating the mobile device <NUM> in the shared lobby <NUM>.

Turning now to <FIG> with continued reference to <FIG>, a process flow <NUM> of the elevator system <NUM> is depicted according to one or more embodiments. The process flow <NUM> is an example operation to determine and prevent an unintended elevator call based on an initial interaction of the mobile device <NUM> with a first location device and a determination of a travel direction of the mobile device <NUM>.

The process flow <NUM> begins at block <NUM>, with a detection of an initial interaction between a first location device at a first location and a mobile device <NUM>. In accordance with one or more embodiments, the first location device can be the location device <NUM>, and the first location can be the upper lobby <NUM>. In a mobile device centric system, the initial interaction can include the mobile device <NUM> detecting a one-way triggering signal by the location device <NUM>, which the mobile device <NUM> determines as a first event in the event trigger sequence. In a location device centric system, the initial interaction can alternatively be the location device <NUM> detecting the mobile device <NUM>, which is determined by the location device <NUM> or the computer <NUM> as the first element in an event trigger sequence.

At block <NUM>, a travel direction of the mobile device <NUM> is determined. The determination of a travel direction of the mobile device <NUM> may be determined using multiple methods, as described below.

The determination of a travel direction of the mobile device <NUM> may be determined in response to the initial interaction of the mobile device <NUM> with the first location device and a location of the first location device. For instance, if the mobile device <NUM> interacts with the location device <NUM> on the upper lobby <NUM> it may indicate that the mobile device is approaching the elevator shaft <NUM> with the intention of traveling downward, thus the travel direction of the mobile device <NUM> would be downward.

The determination of a travel direction of the mobile device <NUM> may be determined in response to a period of time between the initial interaction of the mobile device <NUM> with the first location device and the previous interaction that the mobile device <NUM> had with any location device immediately prior to the initial interaction. If the initial interaction of the mobile device <NUM> with the first location device occurs more than a selected time period after the mobile device <NUM> has interacted with any other location device, it may indicate that the mobile device <NUM> intends to travel in a specific direction. For instance, if the mobile device <NUM> interacts with the location device <NUM> on the upper lobby <NUM> more than eight hours after interacting with any other location device then it may indicate that the mobile device <NUM> is approaching the elevator shaft <NUM> with the intention of traveling downward, thus the travel direction of the mobile device <NUM> would be downward.

The determination of a travel direction of the mobile device <NUM> may be determined in response to the initial interaction of the mobile device <NUM> with the first location device and a subsequent acceleration detected by the mobile device <NUM> within a selected time period of the initial interaction. For example, if the mobile device <NUM> interacts with the location device <NUM> on the upper lobby <NUM> proximate the elevator shaft <NUM> for an initial interaction and a downward acceleration is detected within a selected time period of the initial interaction then it may indicate that the mobile device <NUM> is traveling downward in elevator car <NUM>, thus the travel direction of the mobile device <NUM> would be downward. As described above, the mobile device <NUM> may detect acceleration using a MEMS sensor.

The determination of a travel direction of the mobile device <NUM> may also be determined by a subsequent interaction of the mobile device <NUM> with an intermediate location device of the two or more location devices (e.g., an event trigger sequence). Note that any combination of at least two location devices of the elevator system <NUM> can be utilized to construct an event trigger sequence to implement the process flow <NUM>. Also note that the intermediate location device may produce an intermediate triggering signal received between the first triggering signal in block <NUM> below and the second triggering signal in block <NUM>.

For instance, the process flow <NUM> can utilize the following location device combinations in a lobby focused system to the construct the event trigger sequences of (<NUM>) a location device <NUM> interaction followed by a location device <NUM> interaction (i.e. going down) and (<NUM>) a location device <NUM> interaction followed by a location device <NUM> interaction (i.e. going up).

Further, the process flow <NUM> can utilize the following location device combinations in an elevator focused system to the construct the event trigger sequences of (1E) a location device <NUM> interaction followed by a location device <NUM> interaction (i.e. going down) and (2E) a location device <NUM> interaction followed by a location device <NUM> interaction (i.e. going up).

Furthermore, the process flow <NUM> can utilize the following location device combinations in a joint lobby-elevator system to the construct the event trigger sequences of (1C) a location device <NUM> interaction followed by a location device <NUM> interaction, (2C) a location device <NUM> interaction followed by a location device <NUM> interaction, (3C) a location device <NUM> interaction followed by a location device <NUM> interaction, and (4C) a location device <NUM> interaction followed by a location device <NUM> interaction, along with utilizing the combinations (<NUM>), (<NUM>), (1E), and (2E) described herein. Note that any three or more interaction combinations are also configurable.

At block <NUM>, the elevator system <NUM> automatically filters a second interaction between the mobile device <NUM> and a second location device to prevent an unintended call to an elevator car in response to determination of a travel direction of the mobile device <NUM>. The elevator system <NUM> may proceed to filter subsequent interactions between the mobile device <NUM> and subsequent location devices following the second interaction. Filtering may include blocking any subsequent interaction between the mobile device <NUM> and a location device for a selected period of time.

Filtering may include blocking the second interaction and any subsequent interaction between the mobile device <NUM> and a location device until the mobile device has reached a selected geographical location, such as, for example, outside of the a selected range of the facility <NUM>. Filtering includes selectively blocking the second interaction and any subsequent interaction between the mobile device <NUM> and a location device that may execute a call for the elevator car <NUM> to retrieve a passenger and carry the passenger in a direction opposite the determined travel direction of the mobile device <NUM>. Filtering may include blocking the second interaction and any subsequent interaction between the mobile device <NUM> and a location device until a selected triggering signal is received from a selected location device. The selected location device may have a specific location relative to the facility <NUM>, such as, for example, an exit of the facility <NUM>, a security checkpoint, an entrance to an office, etc. Filtering may include blocking the second interaction and any subsequent interaction between the mobile device <NUM> and a location device until an input selection is received from a user of the mobile device <NUM>. The input selection may be made by the user of the mobile device <NUM>, through an application installed on the mobile device <NUM>, to turn off the filtering. For instance, a user of the mobile device <NUM> may make this selection of the elevator system <NUM> is no longer calling elevator cars when it should as described in method <NUM>.

In the mobile device centric system, the mobile device <NUM> can filter subsequent interactions between the mobile device and location devices (i.e. triggering signals from the location devices) to prevent an unintended call to an elevator car in response to determination of a travel direction of the mobile device <NUM>. In the location device centric system, after the computer <NUM> receives triggering events from the location device <NUM> and the travel direction of the mobile device <NUM> is determined, the computer <NUM> can filter subsequent interactions between the mobile device and location devices to prevent an unintended call to an elevator car in response to determination of a travel direction of the mobile device <NUM>.

Claim 1:
A computer-implemented method for preventing an unintended call for a conveyance apparatus of a conveyance system, the conveyance system comprising a first location device (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) and a second location device (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>), wherein the conveyance system is an elevator system (<NUM>) and the conveyance apparatus is an elevator car (<NUM>, <NUM>), the computer-implemented method comprising:
detecting a first interaction between a mobile device (<NUM>) and the first location device (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>);
determining a travel direction of the mobile device (<NUM>); and
automatically filtering a second interaction between the mobile device (<NUM>) and the second location device (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) to prevent an unintended call to a conveyance apparatus in response to the travel direction of the mobile device (<NUM>); and
characterized in that:
the automatically filtering includes blocking the second interaction and any subsequent interaction between the mobile device (<NUM>) and a location device (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) that may execute a call for the conveyance apparatus to retrieve a passenger and carry the passenger in a direction opposite the determined travel direction of the mobile device (<NUM>).