HK40050249B - An interface device, an elevator system, and a method for controlling displaying of a destination call - Google Patents

Description

Interface devices, elevator systems, and methods for controlling destination calls.

Technical Field

This invention generally relates to the technical field of elevators. Specifically, this invention relates to destination calling in elevators.

Background Technology

Typically, elevator systems include interface devices, such as a destination operation panel (DOP), for providing a destination call to the desired destination floor, which can be predefined or manually selected. Each destination call usually has a passenger-specific ID associated with it. Passengers can present an access device (such as an access card, ID card, or similar device) to the interface device to provide a destination call to the desired destination floor. Alternatively, the destination call to the desired destination floor can be equipped with any other device capable of providing destination calls, such as a turnstile or mobile device.

Once a destination call is generated within a predefined time (such as 2 to 5 seconds), the elevator assigned to that destination call can be immediately displayed on the interface device's display. Alternatively, if the destination call is equipped with a rotary gate or mobile device, the elevator assigned to the destination call can be displayed on the rotary gate or mobile device's display.

Passengers may forget or otherwise miss the elevator assigned to their destination call. This is especially true when there's no screen for passengers to see the generated call, making it impossible for them to see the assigned elevator. Consequently, passengers often make a new destination call, go to any elevator that might lead to their destination floor, or go to any elevator and make a new call. Each of these reduces system optimization and creates unnecessary extra calls that disrupt the destination control system, especially during peak hours.

Therefore, further solutions need to be developed to improve the efficiency of elevator systems.

Summary of the Invention

The following is a simplified overview to provide a basic understanding of some aspects of various embodiments of the invention. This overview is not a comprehensive summary of the invention. It is neither intended to identify key or essential elements of the invention nor to depict its scope. The following overview merely presents some concepts of the invention in a simplified form as a prelude to a more detailed description of exemplary embodiments of the invention.

The purpose of this invention is to provide a method, interface device, and elevator system for controlling the display of destination call information. Another purpose of this invention is to improve the efficiency of elevator systems, at least partially, through the method, interface device, and elevator system for controlling the display of destination call information.

These objectives of the present invention are achieved by the methods, interface devices, and elevator systems defined by the respective independent claims.

According to a first aspect, an interface device for controlling a display of a destination call is provided, the device comprising: an input device configured to receive input information including a passenger ID; a controller entity configured to retrieve a destination call corresponding to the passenger ID; and at least one display configured to display the retrieved destination call.

The interface device can be the Destination Operation Panel (DOP).

The input device may include at least one of the following: a card reader, an RFID reader, a QR code reader, a facial recognition camera, a keyboard, or a touch screen.

The at least one display can be configured to display a destination call during a predetermined time period.

The displayed destination call can include the destination floor.

In addition, the displayed destination call may also include the elevator ID currently assigned to the destination call, the guidance for the elevator currently assigned to the destination call, the departure floor, and/or the status of the destination call.

In response to receiving input information via an input device, including an instruction to cancel the made destination call corresponding to a passenger ID, the controller entity can be configured to cancel the recorded destination call corresponding to the passenger ID.

Furthermore, in response to receiving input information via the input device, including instructions for making a new destination call corresponding to a passenger ID, the controller entity can be configured to record the new destination call made corresponding to the passenger ID.

Destination calls can be retrieved from the controller entity or computing entity of the interface device.

The computing entity can be an elevator controller entity, an interface device controller entity, or any dedicated locally or remotely deployed device.

The at least one display can be implemented as a dynamic header element.

According to a second aspect, an elevator system is provided, wherein the elevator system includes: at least one elevator, a computing entity, and at least one of the aforementioned interface devices.

According to a third aspect, a method for controlling the display of a destination call is provided, wherein the method includes: receiving input information including a passenger ID via an input device; retrieving a destination call corresponding to the passenger ID via a control entity; and displaying the retrieved destination call via at least one display.

The method may further include: receiving input information via an input device, the input information including an instruction to cancel the made destination call corresponding to the passenger ID; and canceling the recorded destination call corresponding to the passenger ID via a controller entity.

In addition, the method may also include: receiving input information via an input device, the input information including instructions for making a new destination call corresponding to a passenger ID; and recording the new destination call made corresponding to the passenger ID via a controller entity.

Destination calls can be displayed during the scheduled time period.

The displayed destination call can include the destination floor.

In addition, the displayed destination call may also include the elevator ID currently assigned to the destination call, the guidance for the elevator currently assigned to the destination call, the departure floor, and/or the status of the destination call.

The expression "a number of" in this article refers to any positive integer starting from the first letter, such as one, two, or three.

The term "a plurality of" in this article refers to any positive integer starting from two, such as two, three, or four.

The various exemplary and non-limiting embodiments of the invention, along with their additional objects and advantages, will be best understood when the following description of specific exemplary and non-limiting embodiments is read in conjunction with the accompanying drawings.

The verbs “comprise” and “include” are used in this document as open-ended restrictions, neither excluding nor requiring the presence of features not listed. Features described in the dependent claims may be freely combined with each other unless expressly stated otherwise. Furthermore, it should be understood that the use of “a” or “an” (i.e., the singular form) throughout the document does not exclude the plural.

Attached Figure Description

In the accompanying drawings, embodiments of the invention are shown by way of example rather than limitation.

Figure 1 schematically illustrates an example of an elevator system according to an embodiment of the present invention.

Figure 2 schematically illustrates an example of an entity of an interface device according to an embodiment of the present invention.

Figure 3 illustrates an example of a controller entity of an interface device according to an embodiment of the present invention.

Figure 4 illustrates an example of an interface device according to an embodiment of the present invention.

Figure 5 illustrates an example of a method according to an embodiment of the present invention.

Figure 6 illustrates another example of an interface device according to an embodiment of the present invention.

Figure 7 illustrates an example of an elevator controller entity according to an embodiment of the present invention.

Detailed Implementation

Figure 1 schematically illustrates an example of an elevator system 100, which includes one or more elevators 102a-102n located at a location (e.g., in a building or on a ship). (For clarity, the elevator shaft is not shown in Figure 1.) The elevator system 100 includes one or more interface devices 104, such as destination operation panels (DOPs), for providing destination calls to a desired destination floor, which may be predefined or manually selected. The one or more interface devices 104 may be located, for example, in the elevator lobby of each floor where the elevator system 100 is located. Each interface device 104 may include a user interface and a controller entity 206 for at least partially controlling the operation of the interface device 104. The user interface may include an input device 202 and at least one display 204 for interacting with at least one user (i.e., a passenger). However, the invention is not limited to destination calls made by one or more interface devices 104, but may include any other destination call device capable of making destination calls to a desired destination floor, such as a rotary gate 106 or a mobile device 108.

Elevator system 100 also includes elevator controller entity 110, which is configured to control at least elevator entities 112 of elevator system 100. For example, elevator entities may include, but are not limited to, drive circuits and devices, safety circuits and devices, sensors, elevator door circuits and devices, elevator cars, etc. Elevator entities 112 are directly or indirectly at least communicatively coupled to each other, for example, through elevator controller entity 110 operating as the main equipment of elevators 102a-102n.

The elevator controller entity 110 and the one or more interface devices 104 may be communicatively coupled to each other, for example, via a communication network 114. The communication network 114 may implement wired or wireless communication technologies. The communication network 114 may be, for example, a mobile communication network or a local communication network. The elevator controller entity 110 includes a communication interface toward the communication network 114, such as a modem implementing a communication technology in use. Similarly, the one or more interface devices 104 are accordingly configured to communicate via the communication network 114.

Figure 2 schematically illustrates an example of an entity of an interface device 104 (e.g., DOP) according to an embodiment. As described above, the interface device 104 may include an input device 202 (i.e., one or more input devices), at least one display 204, and a controller entity 206. The input device 202 may include at least one of the following: a card reader, an RFID reader, an NFC reader, a QR code reader, a facial recognition camera, a keyboard, and a touchscreen.

Input device 202 can interact with at least one user via access device 402 (e.g., access card, ID card, key card, mobile device, etc.), for example, by receiving input information including at least one of the following (for input devices of interface devices): RFID tag, NFC tag, QR code. Alternatively or additionally, interaction with at least one user can be provided such that the user presses or touches a keyboard and/or touchscreen to provide input information. Alternatively or additionally, interaction with at least one user can be provided such that the user presses or touches a keyboard and/or touchscreen to provide user input. Alternatively or additionally, interaction with at least one user can be based on facial recognition, and the facial recognition camera of interface device 104 can be configured to provide image data (e.g., still or video) from the passenger's face to provide input information for making a destination call; for example, the passenger's face can be used as a passenger ID. Controller entity 206 can be configured to perform facial recognition, i.e., process the received image data, for example, to identify the passenger by analyzing the received image data.

Input device 202 can be implemented as an internal entity of interface 104, as shown in Figures 4 and 6. Alternatively or additionally, input device 202 can be implemented as a communicationally coupled external entity of interface device 104, wherein the communication coupling can be based on one or more known wired or wireless communication technologies. For making a destination call, input device 202 of interface device 104 receives input information including a passenger ID for identifying the passenger and/or the destination floor.

The destination floor can be predefined, i.e., included in the received input information, or stored in a computing entity configured to allocate an elevator to the made destination call, or stored in the controller entity 206 of the interface device 104. If the destination floor is stored in the computing entity or the controller entity 206 of the interface device 104, the received input information includes a passenger ID to identify the passenger, and for each passenger ID, the corresponding destination floor is pre-stored in the computing entity or controller entity 206. Alternatively or additionally, the passenger can manually select the destination floor via an input device.

At least one display 204 of the interface device 104 can be implemented as a dynamic title element. However, the at least one display 204 can be located anywhere on the interface device 104, preferably on the passenger-facing side when the interface device 104 is arranged, for example, in an elevator lobby. According to one embodiment, the at least one display 204 and the input device 202 can be implemented as a common touchscreen.

Figure 3 schematically illustrates an example of a controller entity 206 of an interface device 104 according to an embodiment of the present invention. The controller entity 206 may include at least the following entities: a processing unit 310 including one or more processors, a storage unit 320 including one or more memories, and a communication unit 330 including one or more communication devices (such as a modem). In addition to the aforementioned entities, the controller entity 206 may include further devices and entities, such as a battery for storing energy used by other entities. The entities of the controller entity 206 of the interface device 104 may be communicatively coupled to each other via, for example, a communication bus. The processing unit 310 may be configured to control the operation of the interface device 104 by running portions of computer program code stored, for example, in the storage unit 320. The storage unit 320 may also be used to permanently or temporarily store retrieved and received information and any other data. Furthermore, the processing unit 310 may be configured to control communication with any external entity, such as a computing entity, an elevator controller 110, one or more rotary gates 106, one or more mobile devices 108, one or more other interface devices, or any other entity.

Furthermore, the communication unit 330 may include a communication interface through which the interface device 104 can be communicatively coupled to a computing entity (such as elevator controller entity 110), another interface device, and/or any other device. Communication between the interface device 104 and the mentioned entities may be arranged, for example, via a communication network 114. Alternatively or additionally, the interface device 104 may be configured to communicate locally with at least one of the mentioned entities, for example, via short-range wireless communication technology. For example, the interface device 104 and other entities may be coupled to a local Wi-Fi network, and communication may be arranged thereon. According to yet another embodiment, a dedicated communication channel may be arranged between the interface device 104 and other entities.

The interface device 104 can be mounted on a wall in the elevator lobby where the elevator system 100 is located. Alternatively, the interface device 104 may include a base that can be disposed on the floor of the elevator lobby. The base can be fixed to the floor, or the base can be movable.

Figure 4 illustrates an example of an interface device 104, which includes a reader 202a, such as an RFID reader, NFC reader, or QR code reader, that can interact with an access card 402 including a corresponding tag 404 (e.g., an RFID tag, NFC tag, or QR code) to receive input information for making a destination call. Alternatively or additionally, the interface device 104 may include any other type of input device 202 as described above, and correspondingly, the access device 402 may be any other type of access device 402 as described above. Passengers can make a destination call by presenting the access card 402 to the reader 202a. In the example shown in Figure 4, the interface device 104 also includes a touchscreen 202b configured to receive input information for making a destination call. For example, a passenger can touch an area on the touchscreen indicating one of the floors (such as meeting room on floor 3) to make a destination call to that floor. In response to receiving input information via input device 202, the controller entity 204 of interface device 104 is configured to record the completed destination call; that is, the completed destination call is stored in the storage unit 320 of controller entity 204. Furthermore, controller entity 206 can be configured to provide input information to a computing entity for assigning an elevator to the completed destination call. In the case of a delayed destination call system (delayed DCS), the elevator assignment for the completed destination call can be performed later or postponed, or can be re-performed, re-optimized, or updated later.

In the example shown in Figure 4, the interface device 104 also includes a display 204 for displaying the destination call that has been made. The destination call displayed on the display 204 includes at least the destination floor, i.e., the floor 12 on which the destination call was made. The example shown in Figure 4 illustrates only a non-limiting example of making a destination call.

The following describes some other non-limiting examples of making destination calls. According to one example, a user can make a destination call using a mobile device 108 (e.g., a mobile phone, tablet). The mobile device 108 may include, for example, a mobile application through which the user selects a destination floor to make a destination call to that floor. The made destination call can be displayed on the display of the mobile device 108, where the destination call may include the destination floor and/or the elevator IDs of elevators 102a-102n assigned to the destination call, which the user should take to reach the destination floor if an elevator is assigned to the made destination call. The mobile device 108 may be communicatively coupled to a computing entity, for example, via a communication network 114 to make the destination call. The communication network 114 may be, for example, a mobile communication network.

According to another example, a passenger can present an access device to a rotating gate 106, which is communicatively coupled to a computing entity via a communication network 114, to provide a destination call to the desired destination floor. The rotating gate 106 may be located in an elevator lobby or corridor near elevators 102a-102n, for example, where elevator system 100 is located (e.g., in a building or on a ship). The made destination call can be displayed on the rotating gate's display, where the displayed destination call may include the destination floor and/or the elevator ID of elevator 102a-102n assigned to the destination call, which the user should take to reach the destination floor if an elevator is assigned to the made destination call.

According to another example, when the access device 402 includes a tag 404 (such as an RFID tag) for short-range wireless communication, passengers do not need to present the access device 402 to the interface device 104 and/or the turntable 106 in order to make a destination call. Passengers can simply walk past the turntable 106 or pass through the interface device 104 at a distance within the reading range of the corresponding short-range wireless communication reader (such as an RFID reader) of the interface device 104 (i.e., the distance at which the tag can be read) to make a destination call.

A destination call originating from any of the aforementioned destination calling devices can be provided to a computing entity configured to assign an elevator to the destination call. The destination call can be provided to the computing entity, for example, by generating control signals to the computing entity to assign an elevator to the destination call. Elevator assignment can be performed immediately upon receiving user information for making the destination call, or it can be performed later or postponed. Alternatively or additionally, if another elevator is defined as more suitable (e.g., faster, larger space, fewer stops on other floors, etc.), elevator assignment can be re-executed, re-optimized, or updated later (e.g., another elevator can be assigned to the destination call) to serve the passenger upon arrival at the elevator. The computing entity can also be configured to control the assignment information for the destination call. Control over the assignment information for the destination call can include, for example, storing the assignment information for the destination call, canceling the assignment of the destination call, sending the assignment information for the destination call to any other entity, etc. The destination call provided to the computing entity can include the destination floor, the location of the destination calling device, and/or the passenger ID. In response to assigning an elevator to a destination call that has been made, the computing entity is configured to send destination call assignment information to the destination call device that made the destination call. The destination call assignment information may include the destination floor, the elevator ID of the elevator 102a-102n currently assigned to the destination call, and/or guidance to the elevator 102a-102n currently assigned to the destination call. Alternatively or additionally, the computing entity may be configured to send the destination call assignment information to another destination call device besides the device that made the destination call. For example, if the destination call is made by mobile device 108, the computing entity may be configured to send the destination call assignment information to said mobile device 108 and/or one or more interface devices 104 of the elevator system 100.

Where access control is required for a passenger to access their desired destination floor, the computing entity can be further implemented as an access control entity and configured to identify the passenger by means of a passenger ID before assigning a destination call. The access control entity can be configured to store multiple passenger IDs that allow access to one or more floors at that location. A user identifier using the passenger ID can be provided so that the access control entity is configured to check whether the received passenger ID corresponds to one of the multiple passenger IDs stored in the access control entity. In response to a positive identification result (i.e., access is approved), the computing entity is configured to assign an elevator to the destination call and may further provide a confirmation signal to the destination call device indicating that access has been approved. Alternatively, in response to a negative identification result (i.e., access is denied), the computing entity can be configured to provide a confirmation signal to the destination call device indicating that access has been denied. The destination call device can then be configured to indicate the identification result to the user by means of one or more output devices (such as one or more displays, one or more lights, speakers, etc.).

The computing entity can be, for example, elevator controller entity 110, controller entity 206 of interface device 104, or any dedicated locally or remotely located device, such as a server device, configured to perform the tasks of the computing entity. The computing entity can be implemented as a standalone entity or as a distributed computing environment among multiple standalone devices (such as multiple servers providing distributed computing resources in elevator system 100).

As described above, after a passenger has made a destination call, the destination call can be displayed on the display of the destination call device to guide the passenger to the elevator 102a-102n assigned for the destination call made by the passenger. The destination call includes the destination floor, the elevator ID of the elevator 102a-102n currently assigned to the destination call, and/or guidance to the elevator 102a-102n currently assigned to the destination call. When the destination call is made by the interface device 104 or the rotating gate 106, the made destination call can be displayed on the display 204 of the interface device 104 or the display of the rotating gate 106 for a predetermined time (such as 2 to 5 seconds).

Figure 5 schematically illustrates an example of a method for controlling the display of a destination call according to an embodiment of the present invention. This method allows a passenger to check a destination call previously made by the passenger. The destination call may have been made by any of the aforementioned destination call devices (e.g., interface device 104, rotary gate 106, mobile device 108, etc.) and recorded to the destination call device and/or stored in a computing entity. In step 510, the input device 202 of the interface device 104 is configured to receive input information including at least a passenger ID. The input information can be received in several ways as described above. According to some non-limiting examples, the passenger may present the access device 402 to the input device 202 of the interface device 104, or the passenger may use the touchscreen of the input device 202 of the interface device 104 to input information, etc.

In step 520, the controller entity 206 of the interface device 104 is configured to retrieve the destination call corresponding to the passenger ID of the received input information. The destination call can be retrieved from the computing entity that allocates and stores destination calls as described above. The stored destination call may include the destination floor, the location of the destination call device, the passenger ID, the elevator ID indicating the elevator 102a-102n currently allocated to the destination call, the route to the allocated elevator 102a-102n, the departure floor, and/or the status of the destination call. The status of the destination call can be at least one of the following: active, allocated, serviced, canceled, missed elevator, etc. An active status indicates that the destination call has been recorded but not serviced or canceled. A serviced status indicates that the elevator has transported the passenger from the departure floor to the destination floor. A canceled status indicates that the destination call has been canceled, for example, by the passenger. A missed elevator status indicates that the passenger did not take the allocated elevator for some reason. Alternatively or additionally, destination calls can be retrieved from the storage unit 320 of the controller entity 206 of the interface device 104, where the destination calls have been recorded. The recorded destination calls may include at least the destination floor.

In step 530, at least one display 204 of the interface device 104 is configured to display the retrieved destination call. The displayed destination call may include at least the destination floor. The displayed destination call may also include at least one of the following (if available): an elevator ID indicating the elevator 102a-102n assigned to the destination call, guidance to the assigned elevator 102a-102n, departure floor, and/or the status of the destination call. Guidance to the assigned elevator may be, for example, an arrow pointing to the assigned elevator 102a-102n.

According to one example, if an elevator has not yet been assigned to a destination call, the displayed destination call only includes the destination floor. According to another example, if an elevator has been assigned to a destination call, the displayed destination call may include the destination floor, the elevator ID indicating the elevator 102a-102n assigned to the destination call, the route to the assigned elevator 102a-102n, the departure floor, and/or the status of the destination call.

According to one example, in the case of a delayed DCS, the allocation of elevators to destination calls and/or the display of the allocated elevators can be delayed, and the displayed destination call only includes the destination floor. This allows the elevator to be allocated later, or the allocated elevator to be changed if some other elevators are able to serve passengers before the initially allocated elevator. For example, if the elevator allocated for a destination call malfunctions, another elevator can be allocated for that destination call.

According to one example, if the destination call status is "missed elevator," meaning the passenger did not take the assigned elevator for some reason, the displayed destination call can include the destination call status, and the interface device 104 can further prompt the passenger to make a new destination call. The destination call status can be defined as "missed elevator," for example, in response to the input device 202 receiving input information including a passenger ID corresponding to a previously made destination call that is currently in service or will be in service for a short period. Alternatively or additionally, the destination call status can be defined as "missed elevator," for example, in response to the detection that no one has entered the assigned elevator during a predetermined time period and/or before the elevator car requiring the next movement of said elevators 102a-102n. This detection can be based on information obtained from the scale of light or curtain of light of said elevators 102a-102n.

At least one display 204 can be configured to display a destination call for a predetermined period of time (e.g., between 2 and 5 seconds). Thereafter, as described above, a new destination call can be made, or another destination call can be rechecked.

According to one embodiment, the input device 202 may be further configured to receive further input information, including an instruction to cancel an existing destination call corresponding to a passenger ID (optional step 540 shown in FIG. 5). In response to receiving the cancellation instruction, the controller entity 206 is configured to cancel the recorded destination call corresponding to the passenger ID. If an elevator has been assigned to a destination call, the controller entity 206 is also configured to provide input information to a computing entity to cancel the elevator assignment to the existing destination call corresponding to the passenger ID. FIG. 6 schematically illustrates an example of an interface device 104 according to an embodiment of the present invention, wherein the at least one display 204 and the input device 202 are implemented as a common touchscreen, the common touchscreen including an area indicating a button 202c, which a user can touch to provide input information including an instruction to cancel an existing destination call. The button 202c may be arranged near the existing destination call, for example, next to the existing destination call as shown in the example of FIG. 6. However, the position of the button 202c relative to the existing destination call is not limited. In the example shown in Figure 6, the destination call displayed on display 204 includes the destination floor (i.e., floor 12), the currently assigned elevators 102a-102n (i.e., elevator C 102n) that the user should take to reach the destination floor, and guidance to elevator C 102n. This guidance may be, for example, an arrow pointing to the assigned elevators 102a-102n as shown in Figure 6.

In response to the cancellation of an already made destination call, input device 202 can be further configured to receive further input information, including an instruction to make a new destination call corresponding to the received passenger ID instead of the cancelled destination call (optional step 550 shown in FIG. 5). In response to receiving the new destination call instruction, controller entity 206 is configured to record the new destination call made. Furthermore, controller entity 206 can be configured to provide input information to a computing entity to assign an elevator to the new destination call corresponding to the passenger ID. For example, a passenger can touch an area on a touchscreen indicating one of the floors (e.g., the area indicating the restaurant on floor 10 in the example shown in FIG. 6) to make a destination call to that floor.

Figure 7 schematically illustrates an example of an elevator controller entity 110. The elevator controller may include a processing unit 710 containing one or more processors, a storage unit 720 containing one or more memories, and a communication unit 730 containing one or more communication devices (such as a modem or other devices). The elevator controller entity 110 is configured to control the operation of an elevator (e.g., elevator allocation, etc.) and communicates with at least one or more interface devices 104 and/or one or more elevator entities 112 of the elevator system 100. The storage unit 720 may store portions of computer program code and any other data, and the processing unit 710 can cause the elevator controller entity 110 to operate as described by running at least some portions of the computer program code stored in the storage unit 720.

The invention allows passengers to recheck destination calls made for them, which at least partially reduces the number of unnecessary additional destination calls made by the same passenger. Therefore, unnecessary destination calls are reduced, and passenger flow can be optimized more effectively. This invention is advantageous, especially when there is no screen from which passengers can see the destination calls made.

Throughout this application, the term "destination call" refers to a destination call to which an elevator may or may not be assigned.

The specific examples provided in the above description should not be construed as limiting the applicability and/or description of the appended claims. Unless otherwise expressly stated, the list and grouping of examples provided in the above description are not exhaustive.

Claims (14)

1. An interface device (104) for controlling a display of a destination call, the interface device comprising: - Input device (202), configured to receive input information including passenger ID, - Controller entity (206) is configured to retrieve made destination calls corresponding to the passenger ID, and - At least one display (204) is configured to display the retrieved destination calls made. Wherein, if an elevator has not yet been assigned to the destination call, the displayed destination call only includes the destination floor; if an elevator has been assigned to the destination call, the displayed destination call includes the destination floor, the elevator ID of the elevator (102a-102n) currently assigned to the destination call, the guidance to the elevator (102a-102n) currently assigned to the destination call, and the status of the destination call, wherein the status of the destination call includes one of the following: active, assigned, serviced, canceled, missed elevator. 2. The interface device (104) according to claim 1, wherein the interface device (104) is a destination operation panel (DOP). 3. The interface device (104) according to claim 1, wherein the input device (202) includes at least one of the following: a card reader, an RFID reader, a QR code reader, a facial recognition camera, a keyboard, and a touch screen. 4. The interface device (104) according to claim 1, wherein the at least one display (204) is configured to display the destination call during a predetermined time period. 5. The interface device (104) according to claim 1, wherein, in response to receiving input information via the input device (202) including an instruction for canceling the made destination call corresponding to the passenger ID, the controller entity (206) is configured to cancel the recorded destination call corresponding to the passenger ID. 6. The interface device (104) according to claim 5, wherein, in response to receiving input information via the input device (202) including an instruction for making a new destination call corresponding to the passenger ID, the controller entity (206) is configured to record the new destination call made corresponding to the passenger ID. 7. The interface device (104) according to claim 1, wherein the destination call is retrieved from the controller entity (206) or computing entity of the interface device (104). 8. The interface device (104) according to claim 7, wherein the computing entity is an elevator controller entity (110), a controller entity (206) of the interface device (104), or any dedicated locally or remotely located device. 9. The interface device (104) according to claim 1, wherein the at least one display (204) is implemented as a dynamic title element. 10. An elevator system (100), comprising: -At least one elevator (102a-102n), - Computational entities, and - At least one interface device (104) according to any one of claims 1-9. 11. A method for controlling the display of a destination call, wherein the method comprises: - Receive input information including the passenger ID via the input device (510). -Retrieve (520) the destination calls corresponding to the passenger ID via the controller entity, and - The retrieved destination calls are displayed (530) via at least one display. Wherein, if an elevator has not yet been assigned to the destination call, the displayed destination call only includes the destination floor; if an elevator has been assigned to the destination call, the displayed destination call includes the destination floor, the elevator ID of the elevator (102a-102n) currently assigned to the destination call, the guidance to the elevator (102a-102n) currently assigned to the destination call, and the status of the destination call, wherein the status of the destination call includes one of the following: active, assigned, serviced, canceled, missed elevator. 12. The method of claim 11, further comprising: - Receive input information via the input device, the input information including an instruction to cancel the existing destination call corresponding to the passenger ID, and - Cancel (540) the recorded destination call corresponding to the passenger ID via the controller entity. 13. The method of claim 12, further comprising: - Receive input information (550) through the input device, the input information including instructions for making a new destination call corresponding to the passenger ID, and - The controller entity records the new destination call that has been made, corresponding to the passenger ID. 14. The method according to any one of claims 11-13, wherein the destination call is displayed during a predetermined time period.