Patent Description:
Typically, an elevator system comprises an interface device, e.g. a destination operation panel (DOP) for providing a destination call to a desired destination floor, which may be predefined or manually chosen. Often each destination call may have a passenger specific ID associated to it. The passenger may show an access device, such as an access card, ID card or similar device, to the interface device in order to provide a destination call to the desired destination floor. Alternatively, the destination call to the desired destination floor may be provided with any other device capable for providing the destination call, such as turnstile or mobile device.

The elevator allocated for the destination call may be displayed on a display of the interface device immediately after generation of the destination call during a predefined time, such as <NUM> to <NUM> seconds. Alternatively, if the destination call is provided with a turnstile or a mobile device, the elevator allocated for the destination call may be displayed on a display of the turnstile or the mobile device.

The passengers may forget or otherwise miss the elevator allocated for the destination call. Especially when there are no screens from which the passengers may see the made calls, the passengers cannot see the elevator allocated for the destination call. Thus, the passengers typically make new destination calls, go to whichever elevator that might go to the destination floor or go to whichever elevator and make a new call, each of these reduces the optimization of the system and creates unnecessary additional calls jamming destination control system, especially during rush hours.

Hence, there is need to develop further solutions in order to improve the efficiency of an elevator system.

<CIT>, <CIT>, and <CIT> disclose methods and systems for making elevator service requests. The methods including populating a recents list with at least one retained floor pair, displaying the recents list on a display of a user interface, receiving a user input on the recents list indicating a new elevator service request related to one of the retained floor pairs, generating an elevator service request packet based on the new elevator service request, and transmitting the elevator service request packet to an elevator controller to make an elevator service request.

An objective of the invention is to present a method, an interface device, and an elevator system for controlling displaying of an destination call information. Another objective of the invention is that the method, the interface device, and the elevator system for controlling displaying of an destination call information improve at least partly the efficiency of an elevator system.

The objectives of the invention are reached by a method, an interface device, and an elevator system as defined by the respective independent claims.

According to a first aspect of the invention, an interface device for controlling displaying of a destination call according to claim <NUM> is provided.

The interface device may be a destination operation panel, DOP.

The input means may comprise at least one of the following: a card reader, RFID reader, QR code reader, a facial recognition camera, keypad, touch screen. The at least one display may be configured to display the destination call during a predetermined time.

The displayed destination call may comprise a destination floor.

Furthermore, the displayed destination call may further comprise an elevator ID of the elevator currently allocated to the destination call, guidance to the elevator currently allocated to the destination call, departure floor, and/or state of the destination call.

In response to receiving, by the input means, input information comprising an instruction for cancelling the made destination call corresponding to the passenger ID, the controller entity may be configured to cancel the recorded destination call corresponding to the passenger ID.

Moreover, in response to receiving, by the input means, input information comprising an instruction for making a new destination call corresponding to the passenger ID, the controller entity may be configured to record the made new destination call corresponding to the passenger ID.

The destination call may be retrieved from the controller entity of the interface device or a computing entity.

The computing entity may be an elevator controller entity, the controller entity of the interface device, or any dedicated locally or remotely arranged device. The at least one display may be implemented as a dynamic header element.

According to a second aspect of the invention, an elevator system according to claim <NUM> is provided, wherein the elevator system comprising: at least one elevator, a computing entity, and at least one interface device described above.

According to a third aspect of the invention, a method according to claim <NUM> for controlling displaying of a destination call is provided.

The method may further comprise: receiving, by the input means, input information comprising an instruction for cancelling the made destination call corresponding to the passenger ID; and cancelling, by the controller entity, the recorded destination call corresponding to the passenger ID.

Moreover, the method may further comprise: receiving, by the input means, input information comprising an instruction for making a new destination call corresponding to the passenger ID; and recording, by the controller entity, the made new destination call corresponding to the passenger ID.

The destination call may be displayed during a predetermined time.

<FIG> schematically illustrates an example of an elevator system <NUM> comprising one or more elevators 102a-102n residing in a location, e.g. in a building or in a ship (for sake of clarity the elevator shafts of the elevators are not shown in <FIG>). The elevator system <NUM> comprises one or more interface devices <NUM>, e.g. a destination operation panel (DOP), for providing a destination call to a desired destination floor, which may be predefined or manually chosen. The one or more interface devices <NUM> are located at an elevator lobby of each floor of the location in which the elevator system <NUM> is arranged. Each interface device <NUM> may comprise a user interface and a controller entity <NUM> for controlling at least partly the operation of the interface device <NUM>. The user interface may comprise input means <NUM> and at least one display <NUM> for interacting with at least one user, i.e. passenger. However, the present invention is not limited to destination calls made by the one or more interface devices <NUM>, but the destination call to the desired destination floor may be provided with any other destination call device capable for making a destination call, such as a turnstile <NUM> or a mobile device <NUM>.

The elevator system <NUM> further comprises an elevator controller entity <NUM> configured to control at least elevator entities <NUM> of the elevator system <NUM>. For example, the elevator entities may comprise, but are not limited to, drive circuit and devices, safety circuit and devices, sensors, elevator door circuits and devices, elevator cabin and similar. The elevator entities <NUM> are at least communicatively coupled to each other either directly or indirectly e.g. through the elevator controller entity <NUM>, which operates as a master device for the elevator 102a-102n.

The elevator controller entity <NUM> and the one or more interface devices <NUM> may be communicatively coupled to each other e.g. over a communication network <NUM>. The communication network <NUM> may implement a wired or a wireless communication technology. The communication network <NUM> may e.g. be a mobile communication network or a local communication network. The elevator controller entity <NUM> comprises a communication interface, such a modem implementing the communication technology in use, towards the communication network <NUM>. Similarly, the one or more interface devices <NUM> is configured accordingly to communicate through the communication network <NUM>.

<FIG> schematically illustrates an example of entities of the interface device <NUM>, e.g. a DOP, according to an embodiment. As discussed above the interface device <NUM> may comprise input means <NUM>, i.e. one or more input devices, at least one display <NUM>, and a controller entity <NUM>. The input means <NUM> may comprise at least one of the following: a card reader, RFID reader, NFC reader, QR code reader, a facial recognition camera, keypad, touch screen.

The input means <NUM> may interact with the at least one user, e.g. receive input information, through an access device <NUM>, e.g. an access card, ID card, key card, mobile device, etc., comprising at least one of the following (respective to the input means of the interface device): RFID tag, NFC tag, QR code. Alternatively or in addition, the interaction with the at least one user may be provided so that the user press or touches the keypad and/or the touch screen in order to provide the input information. Alternatively or in addition, the interaction with the at least one user may be based on facial recognition and the facial recognition camera of the interface device <NUM> may be configured to provide image data, e.g. still or video, from the face of the passenger in order to provide input information for making a destination call, e.g. the face of the passenger may be used as a passenger ID. The controller entity <NUM> may be configured to perform facial recognition, i.e. process the received image data, e.g. by analyzing the received image data to identify the passenger.

The input means <NUM> may be implemented as an internal entity of the interface <NUM> as it is illustrated in <FIG> and <FIG>. Alternatively or in addition, the input means <NUM> may be implemented as an external entity of the interface device <NUM> communicatively coupled to the interface device <NUM>, wherein the communicatively coupling may be based on one or more known communication technologies, either wired or wireless. In order to make a destination call the input means <NUM> of the interface device <NUM> receives input information comprising passenger ID for identifying the passenger, and/or destination floor.

The destination floor may be predefined, i.e. included in the received input information or stored to a computing entity that is configured to allocate an elevator to the made destination calls or stored to the controller entity <NUM> of the interface device <NUM>. In case the destination floor is stored to the computing entity or to the controller entity <NUM> of the interface device <NUM>, the received input information comprises the passenger ID to identify the passenger and for each passenger ID respective destination floor is prestored to the computing entity or to the controller entity <NUM>. Alternatively or in addition, the destination floor may be manually chosen by the passenger via input means.

The at least one display <NUM> of the interface device <NUM> may be implemented as a dynamic header element. However, the at least one display <NUM> may be located anywhere of the interface device <NUM>, preferably at the side facing to the passengers when the interface device <NUM> is arranged for example to an elevator lobby in the location. According to one embodiment the at least one display <NUM> and the input means <NUM> may be implemented as a common touch screen.

<FIG> illustrates schematically an example of the controller entity <NUM> of the interface device <NUM> according to an embodiment of the invention. The controller entity <NUM> may comprise at least the following entities: processing unit <NUM> comprising one or more processors, memory unit <NUM> comprising one or more memories, and communication unit <NUM> comprising one or more communication devices, such as modems. In addition to the mentioned entities the controller entity <NUM> may comprise further devices and entities, such as batteries for storing energy to be used by the other entities. The entities of the controller entity <NUM> of the interface device <NUM> may be communicatively coupled to each other with e.g. a communication bus. The processing unit <NUM> may be configured to control the operation of interface device <NUM> by executing portions of computer program code stored e.g. in the memory unit <NUM>. The memory unit <NUM> may also be used for storing retrieved and received information together with any other data either permanently or temporarily. Furthermore, the processing unit <NUM> may be configured to control communication with any external entity, such as with a computing entity, an elevator controller <NUM>, one or more turnstiles <NUM>, one or mobile devices <NUM>, one or more other interface devices, or any other entities.

Moreover, the communication unit <NUM> may comprise a communication interface though which the interface device <NUM> may be communicatively coupled to the computing entity, such as an elevator controller entity <NUM>, to another interface device and/or any other devices. The communication between the interface device <NUM> and the mentioned entities may e.g. be arranged through the communication network <NUM>. Alternatively or in addition, the interface device <NUM> may be configured to communicate with at least one of the mentioned entities locally e.g. over a short range wireless communication technology. For example, the interface device <NUM> and the other entities may be coupled to a local Wi-Fi network and the communication may be arranged over it. According to still further embodiment a dedicated communication channel may be arranged between the interface device <NUM> and the other entities.

The interface device <NUM> may be mounted to a wall at the elevator lobby in the location in which the elevator system <NUM> is arranged. Alternatively, the interface device <NUM> may comprise a pedestal that may be arranged on a floor of the elevator lobby. The pedestal may be fixed to the floor or it may be movable.

<FIG> illustrates an example of the interface device <NUM> that comprises a reader 202a, e.g. RFID reader, NFC reader, or QR code reader, that may interact with an access card <NUM> that comprises a corresponding tag <NUM>, e.g. RFID tag, NFC tag, or QR code, in order to receive input information for making a destination call. Alternatively or in addition, the interface device <NUM> may comprise any other type input means <NUM> as discussed above and correspondingly the access device <NUM> may be any other type of access device <NUM> as discussed above. The passenger may make a destination call by showing the access card <NUM> to the reader 202a. In the example illustrated in <FIG> the interface device <NUM> comprises further a touch screen 202b configured to receive input information for making a destination call. For example, the passenger may touch the touch screen on the area indicating one of the floors, such as floor <NUM> MEETING ROOMS, in order to make a destination call to said floor. In response to receiving the input information by the input means <NUM> the controller entity <NUM> of the interface device <NUM> is configured to record the made destination call, i.e. made destination call is stored into the memory unit <NUM> of the controller entity <NUM>. Furthermore, the controller entity <NUM> may be configured to provide the input information to the computing entity for allocating an elevator to the made destination call. In case of a delayed destination call system (delayed DCS) an allocation of an elevator to the made destination call may be performed or postponed later or may be re-performed, re-optimized or updated later.

In the example illustrated in <FIG> the interface device <NUM> comprises further a display <NUM> for displaying the made destination call. The destination call displayed on the display <NUM> comprises at least the destination floor, i.e. floor <NUM>, to which the destination call is made. The example illustrated in <FIG> illustrates only one non-limiting example of making a destination call.

Next some other non-limiting examples making destination calls are introduced. According to one example, the user may use a mobile device <NUM>, e.g. mobile phone, tablet computer, to make the destination call. The mobile device <NUM> may comprise e.g. a mobile application through which the user may select the destination floor in order to make a destination call to said floor. The made destination call may be displayed on a display of the mobile device <NUM>, wherein the destination call may comprise the destination floor and/or elevator ID of the elevator 102a-102n allocated to the destination call, which the user should take to get to the destination floor, if the elevator is allocated to the made destination call. The mobile device <NUM> may be communicatively coupled to a computing entity may e.g. over a communication network <NUM> for making the destination call. The communication network <NUM> may e.g. be a mobile communication network.

According to another example, the passenger may show an access device to the turnstile <NUM> communicatively coupled to a computing entity over a communication network <NUM> in order to provide a destination call to the desired destination floor. The turnstile <NUM> may be located for example at an elevator lobby or at a corridor in the vicinity of the elevator <NUM>02a-<NUM>02n of the location, e.g. in a building or in a ship, wherein the elevator system <NUM> locates. The made destination call may be displayed on a display of the turnstile, wherein the displayed destination call may comprise the destination floor and/or elevator ID of the elevator 102a-102n allocated to the destination call, which the user should take to get to the destination floor, if the elevator is allocated to the made destination call.

According to yet another example, in case the access device <NUM> comprises a tag <NUM> for a short-range wireless communication, such as RFID tag, the passenger does not have to show the access device <NUM> to the interface device <NUM> and/or to the turnstile <NUM> in order to make the destination call, the passenger may just walk through the turnstile <NUM> or pass by the interface device <NUM> at such a distance that is within a read range, i.e. the distance from which a tag may be read, of the corresponding short-range wireless communication reader, such as RFID reader, of the interface device <NUM> to make the destination call.

The destination call made from any of the above discussed destination call devices may be provided to the computing entity that is configured to allocate an elevator to the made destination call. The destination call may be provided to the computing entity for example by generating a control signal to the computing entity for allocating an elevator to the made destination call. The allocation of an elevator may be performed immediately after receiving user information for making the destination call or the allocation of an elevator to the made destination call may be performed or postponed later. Alternatively or in addition, the allocation of an elevator may be re-performed, re-optimized or updated later, e.g. other elevator may be allocated to the destination call, if the other elevator is defined to be more propriate, e.g. quicker, more space, less stops on other floors, etc., to serve the passenger at the time when the passenger arrives to said elevator. The computing entity may further be configured to control the allocation information of the made destination calls. The controlling of the allocation information of the made destination calls may comprise for example storing of allocation information of the made destination calls, cancelling of the allocation of the made destination calls, sending the allocation information of the made destination calls to any other entity, etc. The destination call provided to the computing entity may comprise a destination floor, location of the destination call device, and/or a passenger ID. In response to allocation of the elevator to the made destination call, the computing entity is configured to send the allocation information of the destination call to the destination call device from which the destination call is made. The allocation information of the destination call may comprise the destination floor, the elevator ID of the elevator 102a-102n currently allocated to the destination call, and/or guidance to the elevator 102a-102n currently allocated to the destination call. Alternatively or in addition, the computing entity may be configured to send the allocation information of the destination call to another destination call device than the device from which the destination call is provided. For example, if the destination call is made from a mobile device <NUM>, the computing entity may be configured to send the allocation information of the destination call to said mobile device <NUM> and/or to one or more interface devices <NUM> of the elevator system <NUM>.

In case an access control is required for the passenger to enter the desired destination floor, the computing entity may further be implemented as an access control entity and configured to identify the passenger by means of the passenger ID before allocating the destination call. The access control entity may be configured to store a plurality of passenger IDs that have access to one or more floors in the location. The identification of the user by means of the passenger ID may be provided so that the access control entity is configured to check whether the received passenger ID corresponds to one of the plurality of passenger IDs stored into the access control entity. In response to positive identification result, i.e. the access is approved, the computing entity is configured to allocate an elevator to the made destination call and possibly further provide an acknowledge signal to the destination call device indicating that the access is approved. Alternatively, in response to a negative identification result, i.e. the access is denied, the computing entity may be configured to provide an acknowledge signal to the destination call device indicating that the access is denied. The destination call device may then be configured to indicate the identification result to the user by means of one or more output means, such as one or more display, one or more light, a speaker etc..

The computing entity may be for example the elevator controller entity <NUM>, the controller entity <NUM> of the interface device <NUM> or any dedicated locally or remotely arranged device, such as a server device, configured to perform the tasks of the computing entity. The implementation of the computing entity may be done as a stand-alone entity or as a distributed computing environment between a plurality of stand-alone devices, such as a plurality of servers providing distributed computing resource in the elevator system <NUM>.

As discussed above after the passenger has made the destination call, the made destination call comprising the destination floor, the elevator ID of the elevator 102a-102n currently allocated to the destination call, and/or guidance to the elevator 102a-102n currently allocated to the destination call, may be displayed on a display of the destination call device in order to guide the passenger to the elevator 102a-102n allocated for the destination call made by said passenger. In case the destination call is made by the interface device <NUM> or by the turnstile <NUM> the made destination call may be displayed by the display <NUM> of the interface device <NUM> or the display of the turnstile <NUM> during a predetermined time, such as <NUM> to <NUM> seconds.

<FIG> schematically illustrates an example of the method for controlling displaying of a destination call according to an embodiment of the invention. The method enables that the passenger checks the destination call made by said passenger previously. The destination call may have been made from any of the above destination call devices, e.g. interface device <NUM>, turnstile, <NUM> mobile device <NUM>, etc., and recorded to the destination call device and/or stored to the computing entity. In step <NUM> the input means <NUM> of the interface device <NUM> is configured to receive input information comprising at least a passenger ID. The input information may be received by several ways as discussed above. According to some non-limiting examples, the passenger may show an access device <NUM> to the input means <NUM> of the interface device <NUM> or the passenger may use the touch screen of the input means <NUM> of the interface device <NUM> to input the input information, etc..

In step <NUM> the controller entity <NUM> of the interface device <NUM> is configured to retrieve the destination call corresponding to the passenger ID of the received input information. The destination call may be retrieved from the computing entity where the destination calls are allocated and stored as discussed above. The stored destination call may comprise the destination floor, location of the destination call device, the passenger ID, elevator ID indicating the currently allocated elevator 102a-102n to the destination call, guidance to the allocated elevator 102a-102n, departure floor, and/or state of the destination call. The state of the destination call may be for example at least one of the following: active, allocated, served, cancelled, missed elevator, etc.. Active state means that the made destination call is at least recorded, but not served or cancelled. Served state means that the elevator has conveyed the passenger from the departure floor to the destination floor. Cancelled state means that the destination call is cancelled e.g. by the passenger. The missed elevator state means that the passenger has not taken the allocated elevator for some reason. Alternatively or in addition, the destination call may be retrieved from the memory unit <NUM> of the controller entity <NUM> of the interface device <NUM> where the made destination calls are recorded. The recorded made destination call may comprise at least the destination floor.

In step <NUM> the at least one display <NUM> of the interface device <NUM> is configured to display the retrieved destination call. The displayed destination call may comprise at least the destination floor. The displayed destination call may further comprise at least one of the following if available: an elevator ID indicating the allocated elevator 102a-102n to the destination call, guidance to the allocated elevator 102a-102n, departure floor, and/or state of the destination call. The guidance to the allocated elevator may be for example an arrow pointing towards the allocated elevator 102a-102n.

According to one example, if an elevator is not yet allocated to the made destination call, the displayed destination call comprises only the destination floor. According to other example, if an elevator is allocated to the made destination call the displayed destination call may comprise the destination floor, an elevator ID indicating the allocated elevator 102a-102n to the destination call, guidance to the allocated elevator 102a-102n, departure floor, and/or state of the destination call.

According to one example, in case of the delayed DCS the allocation of the elevator to the destination call and/or displaying of the allocated elevator may be delayed and the displayed destination call comprises only the destination floor. This enables that the elevator may be allocated later, or the allocated elevator may be changed, if some other elevator turns out to be able to serve the passenger before the initially allocated elevator. For example, if there becomes a failure to the elevator allocated for the destination call, another elevator may be allocated for said destination call.

According to one example, if the state of the destination call is missed elevator, i.e. the passenger has not taken for some reason the allocated elevator, the displayed destination call may comprise the state of the destination call and the interface device <NUM> may further prompt the passenger to make a new destination call. The state of the destination call may be defined to be missed elevator for example in response to that the input means <NUM> receives input information comprising passenger ID corresponding to a made destination call that is served at that time or is going to be served within a short time. Alternatively or in addition, the state of the destination call may be defined to be missed elevator for example in response to a detection that no one entered into the allocated elevator during a predetermined time and/or before a need for the next movement of the elevator car of said elevator 102a-102n. The detection may be based on information obtained from a scale or a curtain of light of said elevator 102a-102n.

The at least one display <NUM> may be configured to display the destination call during a predetermined time, e.g. during <NUM> to <NUM> seconds. After that a new destination call may be made or another destination call may be rechecked as discussed above.

According to an embodiment, the input means <NUM> may be further configured to receive further input information comprising an instruction for cancelling the made destination call corresponding to the passenger ID (optional step <NUM> illustrated in <FIG>). In response to receiving the cancelling instruction the controller entity <NUM> is configured to cancel the recorded made destination call corresponding to the passenger ID. In case an elevator is allocated to the destination call the controller entity <NUM> is further configured to provide the input information to the computing entity for cancelling the allocation of the elevator to the made destination call corresponding to the passenger ID. <FIG> illustrates schematically an example of the interface device <NUM> according to an embodiment of the invention, wherein the at least one display <NUM> and the input means <NUM> are implemented as common touch screen comprising an area indicating a button 202c, which the user may touch in order to provide input information comprising an instruction for cancelling the made destination call. The button 202c may be arranged in the vicinity of the made destination call, e.g. next to the made destination call as in the example illustrated in <FIG>. However, the location of the button 202c in relation of the made destination call is not limited. In the example illustrate in <FIG> destination call displayed on the display <NUM> comprises the destination floor, i.e. floor <NUM>, the currently allocated elevator 102a-102n, i.e. elevator C 102n, which the user should take to get to the destination floor, and a guidance to the elevator C 102n. The guidance may be for example an arrow pointing towards the allocated elevator 102a-102n as illustrated in <FIG>.

In response to cancellation of the made destination, the input means <NUM> may be further configured to receive further input information comprising an instruction for making a new destination call corresponding to the received passenger ID instead of the cancelled destination call (optional step <NUM> illustrated in <FIG>). In response to receiving the new destination call instruction the controller entity <NUM> is configured to record the made new destination call. In addition, the controller entity <NUM> may be configured to provide the input information to the computing entity for allocating an elevator to the new made destination call corresponding to the passenger ID. For example, the passenger may touch the touch screen on the area indicating one of the floors, for example in the example illustrated in <FIG> floor <NUM> RESTAURANTS, in order to make a destination call to said floor.

<FIG> schematically illustrates an example of an elevator controller entity <NUM>. The elevator controller may comprise a processing unit <NUM> comprising one or more processors, a memory unit <NUM> comprising one or more memories, and a communication unit <NUM> comprising one or more communication devices, such as modems or other devices. The elevator controller entity <NUM> is configured to control the operation of the elevator, e.g. allocation of the elevator, etc., and to communicate at least with one or more interface devices <NUM>, and/or on or more elevator entities <NUM> of the elevator system <NUM>. The memory unit <NUM> may store portions of computer program code and any other data, and the processing unit <NUM> may cause the elevator controller entity <NUM> to operate as described by executing at least some portions of the computer program code stored in the memory unit <NUM>.

The above described invention enables that the passenger may recheck the destination call made for said passenger, which in turn at least partly decreases the number of unnecessary additional destination calls made by the same passenger. As a result, less unnecessary destination calls are made, and the flow of passengers may be optimized more efficiently. The present invention is advantageous, especially when there are no screens from which the passengers may see the made destination calls.

The term "destination call" refers throughout this application to a made destination call to which an elevator may or may not be allocated.

Claim 1:
An interface device (<NUM>) for controlling displaying of a previously made destination call, the interface device (<NUM>) is located in an elevator lobby and comprises:
- input means (<NUM>) configured to receive input information comprising a passengerID,
- a controller entity (<NUM>), configured to retrieve the previously made destination call corresponding to the passenger ID, and
- at least one display (<NUM>) configured to display the retrieved previously made destination call.