Patent Description:
Buildings that have a large number of floors and elevator banks can use destination management software, such as CompassPlus™ from Otis Elevator Company, to direct passengers to a particular elevator car(s). CompassPlus groups passengers and stops, and assigns an elevator car to a group of passengers heading for the same place or series of floors, or zones. Passengers enter their floor destinations in a keypad on a free-standing device entry terminal (DET), in a wall-mounted hallway fixture, or on a mobile device, and the destination management software suggests an elevator and provides directions to the elevator.

Signal emitting devices such as DETs and hallway fixtures may require significant installation time for each individual unit. Along with the physical installation, the installation also includes setting a user identifier (UID) of the DET, a floor location identifier (ID), a location of the DET, and an orientation in a lobby or hallway of the DET with reference to each elevator car or bank of elevators, a distance from the DET to each elevator or bank of elevators, and an estimate travel, or walking, time from the DET to each elevator or bank of elevators. This information is used by the DET to give the passenger instructions about how to get to the assigned elevator car. Similar information may also be required for mobile DET applications, which can provide a common digital user experience to direct a passenger to an elevator car or bank of elevators as that provided by a DET or hallway fixture.

<CIT> discloses a system and method for determining floor numbers of wireless terminals disposed in halls by measuring the field intensity between the hall terminals and a single wireless terminal disposed in an elevator car at several elevator car positions.

According to an embodiment, a system configured to determine a location of a signal emitting device is provided according to claim <NUM>.

Further embodiments of the system may include the system further comprising a third movable communication device that is different than the first and second movable communication devices, the third movable communication device being arranged to transmit the third data.

Further embodiments of the system may include that the operations further include based at least in part on the location of the signal emitting device, computing a distance and direction from the signal emitting device to a destination.

Further embodiments of the system may include at least one of the first, second, and third data further including orientation information, and the operations further including determining an orientation of the signal emitting device based at least in part on the received orientation information, where the computing a distance and direction are further based at least in part on the orientation of the signal emitting device.

Further embodiments of the system may include the orientation information including a magnetometer reading from the signal emitting device.

Further embodiments of the system may include the orientation information including an angle of arrival of the first signal.

Further embodiments of the system may include the signal emitting device being a destination system management unit that directs users to elevator cars and the destination is an entry location for an elevator car.

Further embodiments of the system may include the location of the signal emitting device being transmitted to the signal emitting device.

Further embodiments of the system may include computing a location based at least in part on triangulation.

Further embodiments of the system may include the signal emitting device being a destination management system unit.

According to an embodiment, a method of determining a location of a signal emitting device is provided according to claim <NUM>.

Further embodiments of the method may include the third data being received from a third movable communication device that is different than the first and second movable communication devices.

Further embodiments of the method may include, based at least in part on the location of the signal emitting device, computing a distance and direction from the signal emitting device to a destination.

Further embodiments of the method may include at least one of the first, second, and third data further including orientation information, and the operations further including determining an orientation of the signal emitting device based at least in part on the received orientation information, where the computing a distance and direction are further based at least in part on the orientation of the signal emitting device.

Further embodiments of the method may include the orientation information including at least one of a magnetometer reading from the signal emitting device and an angle of arrival of the first signal.

Further embodiments of the method may include the signal emitting device being a destination system management unit that directs users to elevator cars and the destination is an entry location for an elevator car.

Technical effects of embodiments of the present disclosure include simplified and automated installation of signal emitting devices such as destination management system units that include, but are not limited to hallway fixtures and DETs. Technical effects of embodiments of the present disclosure also include time and cost reductions for the installation of hallway fixtures and DET systems, as well as other building monitoring assets such as but not limited to heating, ventilation, and air conditioning (HVAC) systems and fire/smoke detectors. Additional technical effects of embodiments of the present disclosure include an enhanced mobile experience by automatically determining a current floor. Further technical effects of embodiments of the present disclosure include maintenance time saving.

One or more embodiments of the present disclosure provide for automatic determination of positions and orientations of signal emitting devices such as, but not limited to destination management system units for elevators. Destination management system units can include, but are not limited to wall-mounted hallway fixtures and free-standing destination entry terminals (DETs). In accordance with one or more embodiments, wireless communication devices (WCDs) are mounted on elevator cars that travel up and down through a building. The WCDs can scan all the available information from the hoistways and elevator cars, noting their positions while scanning and creating a bank of required information for setting up each individual destination management system for the elevator. One or more embodiments of the present disclosure can be extended to gather additional information in the building and commission other systems pertaining to the building itself such as, but not limited to security; safety; lighting; and heating, ventilation, and air conditioning (HVAC) systems).

The collected information can include, but is not limited to: a unique identification number for each destination management system unit; a floor number where each destination management system unit is located, obtained for example by referencing the current elevator floor information or by using Z-axis triangulation based on known elevator car positions; location of the destination management unit on the floor, which can be obtained for example by triangulation using mobile and stationary known reference points; and orientation of the destination management unit, obtained for example by destination management system units that transmit their magnetometer readings or by determining the angle of arrival of wireless signals from the destination management system units.

In accordance with one or more embodiments of the present disclosure, a DET or hallway fixture having a wireless presence and knowledge of its exact location can also be used for tracking and detecting mobile smart devices which can be programmed to provide the same service/interface as a stationary DET or a hallway fixture.

Turning now to <FIG>, a schematic illustration <NUM> of using an elevator system to provide location data for a destination management system unit is generally shown in accordance with one or more embodiments of the present disclosure. <FIG> includes elevator cars <NUM>, a destination location <NUM> labeled "A6" that corresponds to the location where doors of the elevator car <NUM> labeled "A6" will open on floor <NUM>, a wall mounted hallway fixture <NUM> having a display screen <NUM>, a free standing DET <NUM> having a display screen <NUM>, and a person holding a mobile device <NUM> that has a display screen. Though the content of the display screen of the mobile device <NUM> is not shown in <FIG>, it is similar to display screen <NUM> and display screen <NUM> in that it directs the person from their current location to the destination location <NUM> labeled "A6.

As shown in <FIG> signals <NUM> are exchanged between at least one of the elevator cars <NUM> and hallway fixture <NUM>. In an embodiment, the three elevator cars <NUM> include wireless control devices (WCDs) that are at known locations. The positions of the elevator cars <NUM> are continuously monitored by a controller, such as controller <NUM> of <FIG>. In an embodiment, the position of an elevator car <NUM> is referenced to the position of its WCD. In another embodiment, the WCD device is capable of defining its own position, independently of the elevator car <NUM>, based on sensor readings (e.g., accelerometers). The WCDs broadcast signals <NUM> that are received by the hallway fixture <NUM>, and the hallway fixture <NUM> sends return signals <NUM> back to the WCDs. Protocols used to transmit/receive the signals can include, but are not limited to: Bluetooth Low Energy (BLE), Bluetooth, zWave, Zigbee, and LoRa. In an embodiment, the signal broadcasted by the WCD uses a different protocol, or is a different type of signal, than the signal returned to the WCD. For example, the broadcast signal can be a ranging signal (e.g., RFID) and the return signal can be a data signal (e.g., Bluetooth) containing data messaging, or vice versa. In an embodiment system orientation and localization may be performed only during the configuration of static fixtures.

Mobile devices can be located when sending a request (e.g., a floor call using a mobile DET application). Which mobile devices should be part of the system localization can be defined prior to installation in the configuration or there can be a procedure of adding the devices to the system.

In an embodiment, once a device is located and oriented it can be used (e.g., along with other located and oriented devices) to localize other devices.

In an embodiment, the WCDs transmit information about the return signals to a location calculation module executed for example, by controller <NUM> of <FIG> or by a server located external to the elevator system <NUM> of <FIG>. Information about the return signal can include signal strength of the return signal, a unique ID of the hallway fixture <NUM> sending the signal, and a location of the WCD at the time that the return signal was received. The location calculation module can use this information to calculate the location of the hallway fixture <NUM> using known methods such as, but not limited to, triangulation. The location can be expressed in three-dimensional coordinates, and translated into building floors and be assigned other labels (e.g., front lobby). The location calculation module can also determine a distance and estimated passenger travel time between the hallway fixture and any elevator cars or banks in the building.

Additional information can be sent to the location calculation module to determine an orientation of the hallway fixture <NUM>. This additional information can include an angle of arrival of the return signal as measured by the WCD or a magnetometer reading received from the hallway fixture <NUM> in the return signal.

The location and orientation information is used by the destination management software to generate displays such as those shown in <FIG>. As shown in <FIG> display screen <NUM> points to the destination location <NUM> labeled "A6" relative to hallway fixture <NUM> (e.g., back left <NUM>%), and display screen <NUM> points to the destination location <NUM> labeled "A6" relative to the DET <NUM> (e.g., front right <NUM>%). Directions in this form or other forms such as a map and/or text can be communicated to a user standing at hallway fixture <NUM> who is looking for the location of elevator A6.

Turning now to <FIG>, a schematic illustration of a system <NUM> for automatic determination of position and orientation of a DET is generally shown in accordance with one or more embodiments of the present disclosure. <FIG> depicts three elevator cars <NUM> each having a WCD <NUM>, a server <NUM>, and a DET <NUM> having a WCD <NUM>. The elevator cars <NUM> can be in communication with the DET <NUM> via any short-range wireless communication interface known in the art such as, but not limited to Bluetooth, Zigbee, Wi-Fi, zWave, RFID, BLE, cellular, and infrared. The elevator cars <NUM> can be in communication with the server <NUM> via any short or long-range wireless or wired communication methods known in the art over networks such as, but not limited to the Internet, a local area network (LAN), and a wide area network (WAN), Wi-Fi, zWave, RFID, BLE, and cellular.

In one or more embodiments, the WCDs <NUM><NUM> are implemented by nodes and gateways using any protocol(s) known in the art. WCDs can be mounted on a variety of devices such as, but not limited to: elevator cars, DETs, kiosks, hall buttons, lanterns, fire sensors, thermostats, and mobile devices.

As shown in <FIG>, elevator car 103a broadcasts a signal 314a from WCD 306a which is at a known location. Signal 314a is received by DET <NUM> via WCD <NUM>, and WCD <NUM> responds to signal 314a by sending a return signal 312a, that includes a unique ID of DET <NUM>, to WCD 306a in elevator car 103a. In an embodiment, WCD 306a, or other hardware and/or software in elevator car 103a determines the signal strength of return signal 312a. In an alternate embodiment, the raw data from the return signal is passed to the server <NUM> which then determines the signal strength. WCD 306a transmits data 316a to a location calculation module <NUM> executing on a server <NUM>. In an alternate embodiment, the location calculation module <NUM> can be executed by a processor not located in the server such as, but not limited to a processor located in the cloud or in an elevator controller. In an embodiment, the data 316a includes the unique ID of the DET <NUM>, the determined signal strength, and the location of WCD 306a when it received the return signal 312a.

As shown in <FIG>, elevator car 103b broadcasts a signal 314b from WCD 306b which is at a known location. Signal 314b is received by DET <NUM> via WCD <NUM>, and WCD <NUM> responds to signal 314b by sending a return signal 312b, that includes the unique ID of DET <NUM>, to WCD 306b in elevator car 103b. In an embodiment, WCD 306b, or other hardware and/or software in elevator car 103b determines the signal strength of return signal 312b. WCD 306b transmits data 316b to a location calculation module <NUM> executing on a server <NUM>. In an embodiment, the data 316b includes the unique ID of the DET <NUM>, the determined signal strength, and the location of WCD 306b when it received the return signal 312b.

Also as shown in <FIG>, elevator car 103c broadcasts a signal 314c from WCD 306c which is at a known location. Signal 314c is received by DET <NUM> via WCD <NUM>, and WCD <NUM> responds to signal 314c by sending a return signal 312c, that includes the unique ID of DET <NUM>, to WCD 306c in elevator car 103c. In an embodiment, WCD 306c, or other hardware and/or software in elevator car 103c determines the signal strength of return signal 312c. WCD 306c transmits data 316c to a location calculation module <NUM> executing on a server <NUM>. In an embodiment, the data 316c includes the unique ID of the DET <NUM>, the determined signal strength, and the location of WCD 306c when it received the return signal 312c.

The location calculation module <NUM> determines the location and orientation parameters of the DET <NUM> based on contents of the data <NUM>. In one or embodiments, the server <NUM> (or location where the location calculation module <NUM> is executing) transmits data back to the DET <NUM> that contains the location and orientation parameters of the DET <NUM>, and optionally additional parameters detailing a distance of the DET <NUM> from specific elevator cars, an orientation of the DET <NUM> relative to specific elevator cars, and an estimated travel time to specific elevator cars. In other embodiments, the additional parameters are calculated by a processor executing at the DET <NUM>. As shown in <FIG>, the data can be transmitted back to the DET <NUM> via one or more WCDs <NUM> in the elevator cars <NUM>. In other embodiments, the data is transmitted directly between the server <NUM> and the DET <NUM>.

As shown in <FIG>, the server <NUM> includes the location calculation module <NUM> to determine locations of destination management system units. Although the server <NUM> is depicted herein as a single device, it should be appreciated that the server <NUM> may alternatively be embodied as a multiplicity of systems. It should be appreciated that, although particular elements are separately defined in the schematic block diagram of <FIG>, each or any of the elements may be otherwise combined or separated via hardware and/or software.

A minimum of three signals from known locations are required by the location calculation module <NUM> to determine a location of the DET <NUM>. The signals can be received from three (or more) different elevator cars <NUM> as shown in <FIG>. The three signals can also all be received from the same elevator car <NUM> when it is at three different positions. The three signals can be received from any number of elevator cars (one, two, three) as long as each signal is received at a different physical location. When more than three signals are received the additional signals can provide additional accuracy and/or validation. In an alternate embodiment directional receivers are utilized that can determine what vector the signal is coming from, and just a single signal is required to determine a location of the DET <NUM>.

Turning now to <FIG>, a flow diagram <NUM> illustrating a method of automatic determination of position and orientation of a destination management system unit is generally shown in accordance with one or more embodiments of the present disclosure. At block <NUM>, a destination management system unit, such as DET <NUM> of <FIG>, is physically installed at a location, such as in a building with elevators. The destination management system unit can include, but is not limited to a DET and a hallway fixture. At block <NUM>, signals, such as signals <NUM> of <FIG>, are broadcast from WCDs, such as WCDs <NUM> of <FIG>, in elevator cars. At block <NUM> a return signal, such as return signal <NUM> of <FIG>, is received from a WCD, such as WCD <NUM> of <FIG>, in the destination management system unit. The WCD, or other hardware/software device in the elevator car determines a signal strength of the return signal and sends data, such as data <NUM>, that includes the signal strength along with an identifier of the destination management system unit and the location of the WCD when it received the return signal to a server, such as server <NUM> of <FIG>.

At block <NUM> of <FIG>, the location of the destination management system unit is calculated, by for example location calculation module <NUM> of <FIG>, based on contents of the received data using triangulation and translating signal strength values into approximate distances. At block <NUM>, an orientation of the destination management system unit is calculated. In one or more embodiments, the orientation is calculated based on a reading from a sensor (e.g., a compass) in the destination management system unit that is included in the return signal to the elevator car and in the data sent to the server. In one or more other embodiments, the WCDs in the elevator cars have antennas that can measure an angle of arrival of a signal from the DET <NUM> and this information is included in the data sent to the server.

At block <NUM>, parameters for the destination management system unit are calculated. The parameters can include, but are not limited to: location, orientation, a distance from specific elevator cars, an orientation relative to specific elevator cars, and an estimated travel time to specific elevator cars.

In accordance with one or more embodiments, the process of <FIG> is performed periodically to validate that none of the destination management system units have changed locations or to adjust the parameters if the location has changed, or is a new one has been added.

In accordance with one or more embodiments, WCDs located in destination management system units are used to track other devices in a building. In an example scenario, elevator cars are used to define locations of devices such as kiosks, DETs, and hall buttons. These devices and their known locations are then used to determine locations of other devices. A group of devices with known locations can be built, taking into account that the precision of the identified locations decreases as the devices are further from the original devices. For example, a location of a second device that is estimated based on a location of a first original device is likely to have a higher accuracy than a location of a third device that is estimated based on the location of the second device.

Contemporary implementations of mobile DET applications may not know the current floor of the user and the user inputs that information into the application. This can occur as follows: user enters current floor number, presses enter, user enters "to" floor number, and presses enter. An embodiment can remove the requirement for the user to enter the current floor number and pressing enter by knowing the current floor of user. A user may have predefined floors, and proposed floors may be presented to the user based on history, current time (lunch - cafeteria floor, down-peak to lobby).

Claim 1:
A system (<NUM>) configured to determine a location of a signal emitting device (<NUM>, <NUM>, <NUM>), the system (<NUM>) comprising:
at least one elevator car (<NUM>; 103a, 103b, 103c);
a processor; and
a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations, the operations comprising:
receiving first, second, and third data from at least one movable communication device (<NUM>) attached to the at least one elevator car (<NUM>), each of the first, second, and third data comprising a unique identifier of the signal emitting device (<NUM>, <NUM>, <NUM>), a signal strength of a signal (<NUM>) received by the at least one movable communication device (<NUM>) from the signal emitting device (<NUM>, <NUM>, <NUM>), and a location of the at least one movable communication device (<NUM>) when it received the signal (<NUM>), each of the first, second, and third data comprising different locations of the at least one movable communication device (<NUM>, <NUM>, <NUM>); and
computing a location of the signal emitting device (<NUM>, <NUM>, <NUM>) based at least in part on the received first, second, and third data;
characterised in that:
the system (<NUM>) further comprises a first movable communication device (306a) attached to the at least one elevator car (103a) and arranged to transmit the first data, and a second movable communication device (306b) attached to the at least one elevator car (103b) that is different than the first movable communication device (306a), the second movable communication device (306b) being arranged to transmit the second data.