Elevator, elevator control method, and terminal device
The elevator system addresses long waiting times for dedicated calls by allowing users to switch to general calls when waiting exceeds a threshold, enhancing user convenience and managing problematic user behavior.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- HITACHI LTD
- Filing Date
- 2023-03-31
- Publication Date
- 2026-06-01
AI Technical Summary
Existing elevator systems that allow dedicated calls for exclusive use often take a long time to dispatch the elevator car to the user's landing floor, prompting users to consider switching to a general call for shared rides if it takes too long.
An elevator system with a management device that calculates waiting time for dedicated calls and prompts users to switch to a general call when the wait exceeds a threshold, accompanied by a terminal device allowing users to make this change, and includes features to manage and prohibit users who frequently make errors or cause delays.
Enables users to efficiently switch from dedicated to general calls when waiting times are prolonged, improving user convenience and reducing delays by managing user behavior and preventing frequent errors.
Smart Images
Figure 0007868009000001 
Figure 0007868009000002 
Figure 0007868009000003
Abstract
Description
Technical Field
[0001] The present invention relates to an elevator, an elevator control method, and a terminal device.
Background Art
[0002] In a building having multiple floors such as an apartment building, an elevator may be used to move between these multiple floors. In recent years, there are elevators that allow a user (elevator rider) to register a dedicated call for exclusive use of the elevator.
[0003] Patent Document 1 describes an elevator control system. This elevator control system includes a car destination floor registration means provided on the first car door side, a general landing call registration means and a dedicated landing call registration means provided on the second car door side of the landing, a lifting control means for controlling the ascent and descent of the car, a call registration invalidation means for invalidating the registration of a general call when a dedicated call is registered, and a destination floor registration presence / absence determination means for determining the presence or absence of registration of the destination floor. When a dedicated call is registered, the lifting control means lands the car at the landing where the dedicated call is registered after determining that there is no registration of the destination floor.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] However, to make a dedicated call, the car must be dispatched to the landing floor of the user who made the dedicated call, which may take a long time. In this case, the user may consider that a general call to share a ride with other users may be acceptable if it takes time. The present invention aims to provide an elevator, an elevator control method, and a terminal device that allow a user who has made a dedicated call to change to a general call when it takes a long time to dispatch the elevator car to the landing floor of the user who made the dedicated call. [Means for solving the problem]
[0006] To solve the above problems, the present invention provides an elevator having a management device for managing the operation of the elevator, the management device comprising: a calculation unit that calculates the waiting time of a user who has made a dedicated call request for exclusive use of the elevator; and a transmission unit that, when the waiting time exceeds a predetermined time, inquires with the user who made the dedicated call whether or not to change from a dedicated call to a general call that other users can share. In this case, the present invention provides an elevator that allows a user who has made a dedicated call to change to a general call when it takes a long time to dispatch the elevator car to the landing floor of the user who made the dedicated call.
[0007] Here, the transmitting unit can notify the user of the waiting time when making a dedicated call. In this case, the user can be made aware of the waiting time required for a dedicated call. Furthermore, the transmitting unit can send a waiting time extension notification if the user who made a dedicated call does not switch to a general call. In this case, the user can be made aware that the waiting time will be extended. Furthermore, it is possible to set up a list of users who are prohibited from registering dedicated calls. In this case, users who frequently cause trouble or make mistakes can be excluded. Furthermore, if a user who has made a dedicated call has entered abnormal data more than a predetermined number of times, they can be designated as a user who is prohibited from registering. In this case, users who frequently make mistakes in the boarding floor or destination floor they enter can be excluded from making dedicated calls. Furthermore, the abnormal data can be defined as an abnormality in at least one of the elevator landing floor and destination floor entered by the user. In this case, an abnormality where the elevator cannot be called can be detected. Furthermore, if a user who has made a dedicated call fails to board at the specified boarding floor or alight at the destination floor more than a predetermined second number of times, they will be banned from registration. In this case, users who do not adhere to the specified boarding floor or destination floor settings can be excluded from making dedicated calls.
[0008] Furthermore, the present invention provides an elevator control method in which, by executing a program stored in memory, when a user requests a dedicated call for exclusive use of the elevator, the waiting time of the user who made the dedicated call is calculated, and if the waiting time exceeds a predetermined time, the user who made the dedicated call is asked whether they want to change from a dedicated call to a general call that other users can share. In this case, the present invention provides an elevator control method that allows a user who made a dedicated call to change to a general call when it would take a long time to dispatch the elevator car to the landing floor of the user who made the dedicated call.
[0009] Furthermore, the present invention can provide a terminal device comprising: an input unit for a user to input a request for a dedicated call for exclusive use of the elevator; and a display unit that, when the waiting time of the user who made the dedicated call exceeds a predetermined time, displays a screen allowing the user who made the dedicated call to choose whether or not to change from a dedicated call to a general call that other users can share. In this case, the terminal device provides an option for a user who made a dedicated call to change to a general call when it takes a long time to dispatch the elevator car to the landing floor of the user who made the dedicated call.
[0010] Here, the input section can be configured to allow selection between dedicated calls and general calls. In this case, user convenience is improved. Here, the display unit can show the user the waiting time when a dedicated call is made, and if the user does not change to a general call as a result of the selection, it can also display a notification that the waiting time will be extended. In this case, the user can be made aware that the waiting time will be extended. [Effects of the Invention]
[0011] According to the present invention, when a dedicated call is made and it takes a long time to dispatch the elevator car to the landing floor of the user who made the dedicated call, it is possible to provide an elevator, an elevator control method, and a terminal device that allow the user who made the dedicated call to change to a general call. [Brief explanation of the drawing]
[0012] [Figure 1] This is a block diagram showing the overall configuration of the operating system to which this embodiment is applied. [Figure 2] This diagram shows the screen on which a user registers a request using the elevator service request device at the landing. [Figure 3] This diagram shows the confirmation screen displayed when making a dedicated call. [Figure 4] (a) is a diagram showing the screen displayed when there is a significant delay before the elevator arrives after registering a dedicated call. (b) is a diagram showing the screen displayed when the waiting time is extended. [Figure 5] This diagram shows the data structure of the building database. [Figure 6] This diagram illustrates the data structure of the ID management database. [Figure 7] This diagram illustrates the data structure of the User ID DB. [Figure 8] This is a flowchart explaining the operation of the center. [Figure 9] This flowchart provides a more detailed explanation of the processes S103 to S106 in Figure 8. [Figure 10]It is a flowchart that further details the determination process of the ele-data in S208 of FIG. 9. [Figure 11] It is a flowchart that further details the determination process of the personal terminal data in S204 of FIG. 9. [Figure 12] It is a flowchart that further details the determination process of the abnormal data in S209 of FIG. 9. [Figure 13] (a) and (b) are flowcharts that explain the processes performed by the elevator operation management system when there is a call from the user. [Figure 14] It is a flowchart that explains the processes performed by the elevator operation management system when the user cancels a call. [Figure 15] It is a flowchart that explains the processes performed by the elevator operation management system when the user extends the waiting time.
Mode for Carrying Out the Invention
[0013] Hereinafter, with reference to the accompanying drawings, embodiments of the present invention will be described in detail.
[0014] <Overall Description of Operation System 1> FIG. 1 is a block diagram showing the overall configuration of an operation system 1 to which the present embodiment is applied. As shown in FIG. 1, the operation system 1 includes an elevator operation management system 10, a No. 1 elevator control system 30-1 to an Nth elevator control system 30-N, a landing elevator service request device 40, and a center 50. These are connected to each other via a network 90. Further, the elevator operation management system 10, the No. 1 elevator control system 30-1 to the Nth elevator control system 30-N, and a car not shown in the figure constitute the elevator of the present embodiment.
[0015] The elevator operation management system 10 is an example of a management device for managing the operation of an elevator. The elevator operation management system 10 comprises a receiving unit 11, an authentication unit 12, a call reception determination unit 13, a call registration unit 14, a call cancellation reception unit 15, a call cancellation unit 16, a waiting time extension detection unit 17, a notification data creation unit 18, a transmission unit 19, and an operation control unit 20.
[0016] The receiving unit 11 receives information sent from the elevator landing service request device 40 and the center 50 via the network 90. The authentication unit 12 authenticates whether the call data, which is transferred from the center 50 and received by the receiving unit 11, is data transmitted by the elevator landing service request device 40. This authentication uses an ID, password, etc., which are determined between the center 50 and the elevator operation management system 10. The call reception determination unit 13 determines the integrity of the data when a dedicated call is received from a user. For example, the call reception determination unit 13 determines whether the boarding floor and destination floor entered by the user are floors where the bus can stop. The call registration unit 14 registers the boarding floor and destination floor. The call cancellation reception unit 15 accepts cancellations of dedicated calls after the user has made a dedicated call. The call cancellation unit 16 performs a process to cancel a dedicated call when the call cancellation reception unit 15 receives a cancellation request for the dedicated call. The waiting time extension detection unit 17 is an example of a calculation unit, and when a user requests a dedicated call to use the elevator exclusively, it calculates the waiting time of the user who made the dedicated call. The waiting time extension detection unit 17 then detects whether the waiting time has changed to a value that exceeds a predetermined threshold time after the user has made the dedicated call. The notification data creation unit 18 creates notification data to be sent to the center 50. The transmitting unit 19 transmits information to the elevator landing service request device 40 and the center 50 via the network 90. As will be described in more detail later, if the waiting time calculated by the waiting time extension detection unit 17 changes to a value that exceeds a predetermined threshold time, the transmitting unit 19 sends a signal to the user who made the dedicated call asking whether they want to change from a dedicated call to a general call that other users can share. The operation control unit 20 controls the operation of elevator control systems 30-1 to N. The operation control unit 20, for example, creates an operation schedule for elevator control systems 30-1 to N to ensure efficient transportation.
[0017] The elevator control systems 30-1 to 30-N control the operation of the elevator cars of elevators 1 to N (not shown).
[0018] The elevator landing service request device 40 is a terminal device owned by the user or a terminal device provided in the elevator hall. The elevator landing service request device 40 is a computer device such as a PC (Personal Computer), smartphone, or tablet. The elevator landing service request device 40 comprises a processor such as a CPU (Central Processing Unit) as a means of calculation, and storage such as main memory and HDD (Hard Disk Drive) as means of storage. Here, the processor executes various software such as an OS (Operating System) and application programs (Application Software). The main memory is a storage area that stores various software and data used for its execution. Furthermore, the storage is a storage area that stores input data for various software and output data from various software. Furthermore, the elevator landing service request device 40 includes a communication interface for communicating with the outside, a display unit consisting of video memory and a display, and an input unit such as a keyboard or mouse. The display unit and input unit may be touch panels that combine both functions. The following explanation will focus on the case where the display unit and input unit are touch panels.
[0019] Center 50 manages the database related to elevators and authenticates users. The center 50 in this embodiment includes a receiving unit 51, an authentication unit 52, a matching unit 53, a determination unit 54, an anomaly detection unit 55, a DB (database) registration unit 56, a transmission unit 57, a building DB 58, an ID management DB 59, and a User ID DB 60. The receiving unit 51 receives information sent from the elevator operation management system 10 and the elevator landing service request device 40. The authentication unit 52 authenticates the user when a dedicated call or general call is received from the user. User authentication is not particularly limited, but for example, it can be done using the User ID and password entered by the user using the elevator landing service request device 40. The verification unit 53 verifies the User ID and the boarding floor and destination floor entered by the user. The determination unit 54 determines whether the boarding floor and destination floor entered by the user are abnormal data. The anomaly detection unit 55 creates an anomaly log when the boarding floor or destination floor has abnormal data, and registers the user as a prohibited user when the number of anomaly detections by that user exceeds a predetermined number. From then on, this user will not be able to use the dedicated call function. This makes it possible to eliminate users who make dedicated calls maliciously or who make many mistakes. The DB registration unit 56 registers a user who is prohibited from being registered in User ID DB60 if such a user is detected. The transmitting unit 57 transmits information to the elevator operation management system 10 and the elevator landing service request device 40 via the network 90. Building DB58 is a database that manages information about buildings. As will be explained in more detail later, Building DB58 stores information such as bank ID, building name, elevator stopping floors, and available elevators. ID Management DB59 is a database for managing IDs. As will be explained in more detail later, ID Management DB59 stores information for managing IDs such as bank IDs and building IDs. User ID DB60 is a database that manages user information. As will be explained in more detail later, User ID DB60 stores information such as the building each user uses and whether or not they are a prohibited user.
[0020] <Description of the User Interface (UI) of the elevator landing service request device 40> Next, we will describe the UI (User Interface) of the elevator landing service request device 40. Figure 2 shows the screen on which a user registers a request using the elevator landing service request device 40. Figure 2 shows the case where the user sets the boarding floor (shown as "boarding" in the figure) and the destination floor (shown as "disembarking" in the figure) to the 1st floor and the 3rd floor, respectively. Additionally, by checking the "No Carpooling" checkbox as an option, you can make it a dedicated call. If you do not check the "No Carpooling" checkbox, it will be a general call. Then, when you press the registration button in the state shown in the diagram, you will be taken to the screen shown in Figure 3.
[0021] Figure 3 shows the confirmation screen displayed when a dedicated call is made. Figure 3 shows a confirmation screen displayed when a dedicated call is made, indicating that it may take some time for the elevator to arrive. Specifically, it displays a message indicating that it may take 60 seconds or more for the elevator to arrive. This is displayed when, for example, the waiting time extension detection unit 17 calculates the waiting time, and the transmission unit 19 sends a signal to the user requesting the dedicated call to notify them of the waiting time. If the user presses the "Yes" button in the illustrated state, the dedicated call can be registered. In other words, once the request for a dedicated call is sent to the center 50, and there are no problems with user authentication, landing floor, destination floor, etc., the center 50 sends a command to the elevator operation management system 10 to make the dedicated call. If the user presses the "No" button, the screen returns to the screen shown in Figure 2.
[0022] Figure 4(a) shows the screen displayed when a significant amount of time is expected to pass before the elevator arrives after a dedicated call has been registered. Specifically, a warning screen is displayed indicating that a change in operation has occurred that would cause the elevator to take more than 60 seconds to arrive. Then, as shown in the diagram, a message is displayed asking the user whether or not to continue with the no-ride-with option. If the user presses the "yes" button in response to this notification, the waiting time will be extended. Then, the screen shown in Figure 4(b) will be displayed.
[0023] Figure 4(b) shows the screen displayed when the waiting time is extended. In other words, if a user who has made a dedicated call does not switch to a general call, a waiting time extension notification is issued, informing the user that the waiting time will be extended. This is displayed, for example, when the user who has made a dedicated call does not switch to a general call, by the transmission unit 19 sending a signal to display the waiting time extension notification. On the other hand, pressing the "No" button will cancel the dedicated call and switch to a general call.
[0024] In this embodiment, the elevator landing service request device 40 can also be described as a terminal device comprising: an input unit for inputting a request for a dedicated call for exclusive use of the elevator; and a display unit that, when the waiting time of the user who made the dedicated call changes to a value exceeding a predetermined threshold time, displays a screen that allows the user who made the dedicated call to choose whether or not to change from a dedicated call to a general call that other users can share. The input unit can also select between a dedicated call and a general call. Furthermore, the display unit displays the waiting time to the user when a dedicated call is made, and if the user does not change to a general call as a result of their selection, it displays a notification that the waiting time will be extended.
[0025] <Explanation of the contents of the DB (database) managed by Center 50> Next, we will explain the contents of the database (DB) managed by Center 50. Figure 5 shows the data structure of the building DB58. The illustrated building database DB58 consists of the following columns: Bank ID, Building Name, Floor, Target Elevator Management No., and Unit Name. A bank ID is an ID assigned to each bank when elevators are divided into banks such as low-rise, mid-rise, and high-rise based on the number of floors. The building name is the name of the building. The floor number refers to the floor level available in each bank. The target elevator management number is the management number assigned to each bank of elevators. The unit number is the name assigned to the elevator.
[0026] Figure 6 shows the data structure of the ID management DB59. The ID management DB59 shown in the diagram consists of columns for bank ID, building ID for personal terminals, and floor. The bank ID is the same as in Figure 5, and is an ID assigned to each bank. The building ID for personal terminals is used by the elevator landing service request device 40 and is an ID assigned to the building. The floors are the same as in Figure 5, and represent the available floor levels in each bank.
[0027] Figure 7 shows the data structure of User ID DB60. The User ID DB60 shown in the diagram consists of columns for User ID, Building ID for personal terminals, Abnormal registration, and Registration Prohibited. A User ID is an ID assigned to each user. The building ID for personal terminals is the same as in Figure 6, and is an ID assigned to the building. Anomaly registration refers to the number of times the information entered by the user was incorrect. The "Registration Prohibited" status indicates whether or not a user is a "Registration Prohibited User." Here, a "Registration Prohibited" value of 0 indicates that the user is not a "Registration Prohibited User," while a value of 1 indicates that the user is a "Registration Prohibited User." A "Registration Prohibited User" is a user who is prohibited from registering dedicated calls. Note that, in this case, User ID DB60 is managed at Center 50, but it may also be managed separately for each building.
[0028] <Detailed explanation of the operation of the operating system 1> Figure 8 is a flowchart illustrating the operation of center 50. First, the receiving unit 51 receives data from the elevator landing service request device 40 (S101). Next, the authentication unit 52 performs user authentication (S102). Furthermore, the matching unit 53 performs a comparison with the User ID and data such as the boarding floor and destination floor entered by the user (S103). Then, if no abnormality is detected as a result of the comparison (OK in S103), the determination unit 54 makes a determination on the data (S104). On the other hand, if an abnormality is detected as a result of the verification (NG in S103), the abnormality detection unit 55 performs abnormality detection processing (S105). In this case, the abnormality detection unit 55 detects, for example, a user that is prohibited from registration. Furthermore, if a user who is prohibited from being registered is detected, the DB registration unit 56 registers this user in User ID DB60 (S106).
[0029] In the process shown in Figure 8, S101, the receiving unit 51 receives data from the elevator landing service request device 40. The receiving unit 51 then decodes the received data.
[0030] In the process of S102 in Figure 8, the authentication unit 52 performs ID authentication. As for the authentication method, in the example above, it was done using a User ID and password, but for example, a method in which each user has a unique authentication ID and transmits this authentication ID, or a method in which predetermined data is encrypted in a decryption manner may also be used.
[0031] Figure 9 is a flowchart that provides a more detailed explanation of the processes S103 to S106 in Figure 8. The verification unit 53 determines whether the input data entered by the user originates from a personal terminal (S201). Here, a personal terminal is a terminal device owned by the user. As a result, if the call is not from a personal terminal (No in S201), the matching unit 53 performs a matching process for the building ID (S202). An example of a call not being from a personal terminal is when the user makes a call request from a terminal device installed in the elevator hall. The building ID can be determined from the location where the terminal device in the elevator hall is installed. Furthermore, the matching unit 53 performs a matching process on the personal input data entered by the user on the terminal device (S203). Furthermore, the determination unit 54 performs personal terminal data determination processing (S204). As will be described in detail later, the determination unit 54 determines the personal terminals possessed by the user if the user is not a prohibited user based on the results of the comparison.
[0032] On the other hand, if the request is from a personal terminal (Yes in S201), the matching unit 53 performs a User ID matching process (S205). Furthermore, the matching unit 53 performs a matching process on the data entered for the elevator (S206). The matching unit 53 then determines whether or not the notification data from the elevator contains abnormal data (S207). If the data is not included (No in S207), the determination unit 54 performs an elevator data determination process (S208). As will be explained in more detail later, the determination unit 54 verifies the consistency of the data such as the landing floor and destination floor entered by the user. If the data is included (Yes in S207), the determination unit 54 performs abnormal data determination processing (S209). As will be explained in more detail later, the determination unit 54 determines whether or not the user actually boarded / alighted at the boarding floor / destination floor entered by the user.
[0033] Figure 10 is a flowchart that provides a more detailed explanation of the element data determination process in S208 of Figure 9. First, the determination unit 54 performs a User ID detection process (S301). Next, the determination unit 54 determines whether or not the data entered by the user contains abnormal data (S302). Abnormal data is, for example, when the boarding floor and destination floor entered by the user include floors where the train does not actually stop. In this case, it can also be said that the abnormal data is data indicating that there is a discrepancy between the boarding floor entered by the user and the floors where the train can actually board, and between the destination floor entered by the user and the floors where the train can actually alight. As a result, if no abnormal data is found (No in S302), the determination unit 54 performs the process of creating notification data for the terminal device (S303). This notification data is, for example, data for displaying the screen shown in Figure 3. Then, the transmission unit 57 performs the process of sending the notification data to the personal terminal (S304).
[0034] Conversely, if abnormal data is included (Yes in S302), the abnormality detection unit 55 performs a counting process for the number of abnormal receptions (S305). The number of abnormal receptions may be calculated cumulatively or cleared at predetermined intervals (for example, every month). The anomaly detection unit 55 then determines whether the number of anomalies from the given User ID exceeds a predetermined threshold (S306). Then, if a predetermined threshold is exceeded (Yes in S306), the user with this User ID is temporarily added to the banned list (S307). In this embodiment, it can also be said that a user is banned from registration when the number of times the data entered by a user who made a dedicated call contains abnormal data exceeds a predetermined first number. In contrast, if the predetermined threshold is not exceeded (No in S306) and after S307, the transmission unit 57 performs error information transmission processing to the user's personal terminal (S304).
[0035] Figure 11 is a flowchart that provides a more detailed explanation of the personal terminal data determination process in S204 of Figure 9. First, the determination unit 54 performs the User ID detection process (S401). Next, the determination unit 54 determines whether the user of User ID is a prohibited user (S402). Furthermore, if the user is not a prohibited user (No in S402), the determination unit 54 performs the data transmission destination selection process (S403). That is, the determination unit 54 selects the personal terminal to which the data will be transmitted. Then, the determination unit 54 performs the process of creating notification data for the personal terminal (S404). Furthermore, the transmitting unit 57 performs the elevator registration transmission process to the personal terminal (S405). That is, the transmitting unit 57 notifies the user's personal terminal that the elevator call registration has been completed.
[0036] Conversely, if the user is a prohibited user (Yes in S402), the determination unit 54 performs a process to deny registration (S406). Therefore, if the user is a prohibited user, even if they request a dedicated call using their personal terminal, registration of the dedicated call will not be permitted. Furthermore, the transmitting unit 57 notifies the user that data registration is not possible on their personal terminal (S407). That is, it notifies the user that it is not possible to register an elevator call on their personal terminal.
[0037] Figure 12 is a flowchart that provides a more detailed explanation of the abnormal data detection process in S209 of Figure 9. First, the determination unit 54 performs a detection process for the destination floor and the landing floor (S501). Next, the determination unit 54 determines whether or not there are any unregistered users (S502). For example, data of unregistered users includes cases where a call has been registered in the elevator operation management system 10 but the service has not been performed, or cases where a user boarded the elevator at a landing floor but has not yet arrived at their destination floor (S502). As a result, if no unregistered users are found (No in S502), the process is terminated. On the other hand, if there is an unregistered user registration (Yes in S502), the determination unit 54 determines whether or not this user has boarded at a boarding floor (S503). Then, if a passenger boards at the boarding level (Yes in S503), the determination unit 54 determines whether or not this user disembarks at the destination level (S504). Then, if a passenger disembarks at the destination floor (Yes in S504), the determination unit 54 performs registration update processing in the DB (database) (S505).
[0038] On the other hand, if there are no passengers boarding at the boarding floor in S503 (No in S503), the determination unit 54 outputs a boarding floor anomaly log (S506). Also, if there are no passengers disembarking at the destination floor in S504 (No in S504), the determination unit 54 outputs a destination floor anomaly log (S507). The anomaly detection unit 55 then determines whether the number of anomaly detections exceeds a predetermined threshold (threshold 2) (S508). As a result, if the predetermined threshold is exceeded (Yes in S508), the abnormality detection unit 55 registers the user with this User ID to the prohibited list (S509). In this embodiment, it can also be said that a user who has made a dedicated call is prohibited from registering if the number of times they do not board at the input boarding floor or alight at the destination floor exceeds a predetermined second number. In contrast, if the predetermined threshold is not exceeded (No in S508), and after S509, the DB registration unit 56 performs DB abnormal user update processing (S510). That is, the DB registration unit 56 updates the abnormal registration and registration prohibition data for User ID DB60 shown in Figure 7.
[0039] Figures 13(a) and (b) are flowcharts illustrating the processes performed by the elevator operation management system 10 when a user makes a call. Of these, Figure 13(a) shows the process of registering a call when a call is received from a user. First, the receiving unit 11 receives predetermined data from the center 50 (S601). Next, the authentication unit 12 performs data authentication (S602). Then, the authentication unit 12 determines whether the authentication result is OK or not (S603). As a result, if the authentication result is OK (Yes in S603), the call reception determination unit 13 detects destination floor / landing floor / type information from the acquired data (S604). In this case, the type information is information that indicates either a dedicated call or a general call. Next, the call reception determination unit 13 determines whether or not existing floor information is included as the destination floor / platform floor (S605). As a result, if existing floor information is included (Yes in S605), the call reception determination unit 13 determines whether the destination floor / boarding floor is separated or not (S606). That is, if the destination floor / boarding floor belongs to the same bank, the destination floor / boarding floor is not separated. On the other hand, if the destination floor / boarding floor belongs to different banks, the destination floor / boarding floor is separated. If the destination floor and boarding floor are not separated (Yes in S606), the call registration unit 14 registers the boarding floor call (S607). Furthermore, the call registration unit 14 registers the destination floor information (S68). Then, the notification data creation unit 18 creates notification data (S609). The notification data creation unit 18 also creates notification data if the authentication result is NG in S603 (No in S603), if the floor information does not exist in S605 (No in S605), or if the destination floor / landing floor is separated in S606 (No in S606). This notification data is the same as the notification data explained in S207 of Figure 9. Specifically, the notification data includes abnormal data that notifies registration / non-stop / consistency NG, etc. Furthermore, the transmission unit 19 transmits notification data to the center 50 (S610).
[0040] Figure 13(b) shows the process of creating notification data when a user makes a request. First, the operation control unit 20 determines whether or not there is a call from a personal terminal (S701). Next, the operation control unit 20 determines whether or not the elevator has arrived in response to the landing call (S702). Then, if the elevator has not arrived (No in S702), return to S702. Conversely, if the elevator arrives (Yes in S702), the operation control unit 20 registers the elevator's destination floor (S703). Next, the operation control unit 20 detects whether or not a user has boarded the train from the boarding floor (S704). As a result, if a user boards the elevator from the landing floor (Yes in S704), the operation control unit 20 detects whether or not the elevator has arrived at the destination floor (S705). If the elevator has not arrived at the destination floor (No in S705), the system returns to S705. Conversely, when the elevator arrives at the destination floor (Yes in S705), the operation control unit 20 detects whether or not the user has disembarked at the destination floor (S706). Then, if the user disembarks (Yes in S706), the notification data creation unit 18 creates notification data (S707). Also, if there is no call from the personal terminal in S701 (No in S701), if the user does not board from the boarding floor in S704 (No in S704), or if the user does not disembark at the destination floor in S706 (No in S706), the notification data creation unit 18 also creates notification data. This notification data is the same notification data explained in S207 of Figure 9. Specifically, the notification data is data that notifies registration / NG, etc. Furthermore, the transmission unit 19 transmits notification data to the center 50 (S708).
[0041] Figure 14 is a flowchart illustrating the process performed by the elevator operation management system 10 when a user cancels a call. First, the receiving unit 11 receives predetermined data from the center 50 (S801). Next, the authentication unit 12 performs data authentication (S802). Then, the authentication unit 12 determines whether the authentication result is OK or not (S803). As a result, if the authentication result is OK (Yes in S803), the call reception determination unit 13 detects destination floor / landing floor / type information from the acquired data (S804). In this case, the type information is information that indicates either a dedicated call or a general call. Next, the call cancellation reception unit 15 determines whether or not existing floor information is included as the destination floor / boarding floor (S805). As a result, if existing floor information is included (Yes in S805), the call cancellation unit 16 determines whether or not the call registration by the terminal device has already been registered (S806). If a call registration has already been made (Yes in S806), the call cancellation unit 16 cancels the call registration for the landing floor made by the terminal device (S807). Furthermore, the call cancellation unit 16 cancels the registration of destination floor information made by the terminal device (S808). Next, the notification data creation unit 18 creates notification data (S809). The notification data creation unit 18 also creates notification data if the authentication result is NG in S803 (No in S803), if the floor information does not exist in S805 (No in S805), or if the call registration is not registered in S806 (No in S806). This notification data is the same as the notification data explained in S207 of Figure 9. Specifically, the notification data is data that notifies registration / non-stop / consistency NG, etc. Furthermore, the transmission unit 19 transmits notification data to the center 50 (S810).
[0042] Figure 15 is a flowchart illustrating the process performed by the elevator operation management system 10 when a user requests an extension of the waiting time. First, the waiting time extension detection unit 17 determines whether or not a call registration by the terminal device has already been registered (S901). If the call registration is already registered (Yes in S901), the waiting time extension detection unit 17 determines whether the call waiting time has worsened (S902). Specifically, the waiting time extension detection unit 17 determines whether the waiting time has worsened by, for example, whether the current waiting time + predicted delay time exceeds the threshold time α. In other words, the initially expected waiting time is taken as the current waiting time. This is, for example, 60 seconds. Furthermore, the waiting time extension detection unit 17 calculates the predicted delay time as the time that is expected to be delayed beyond this waiting time. Then, the waiting time extension detection unit 17 determines whether the sum of the current waiting time and the predicted delay time has changed to a value that exceeds the threshold time α. If the call waiting time is worsening (Yes in S902), the waiting time extension detection unit 17 issues a waiting time extension notification to the terminal device (S903). Next, the waiting time extension detection unit 17 determines whether the user has canceled the no-ride-sharing operation (S904). In other words, in Figure 2, when no-ride-sharing is set as an Option, it becomes a dedicated call, but the waiting time extension detection unit 17 determines whether this setting has been canceled and it has become a general call that allows ride-sharing with other users. As a result, if the ride-sharing restriction is lifted (Yes in S904), the waiting time extension detection unit 17 changes from a dedicated call to a general call (S905). Furthermore, the notification data creation unit 18 creates notification data (S906). This notification data is the same as the notification data described in S207 in Figure 9. Specifically, the notification data is data that notifies registration / non-stop / consistency NG, etc. Furthermore, the transmission unit 19 transmits notification data to the center 50 (S907). Furthermore, if there is no call registration in S901 (No in S901), if the call waiting time has not worsened in S902 (No in S902), or if the ride-sharing restriction has not been lifted in S904 (No in S904), the process will be terminated.
[0043] According to the above configuration, when a dedicated call is made and it takes a long time to dispatch the elevator car to the landing floor of the user who made the dedicated call, it is possible to provide an elevator, an elevator control method, and a terminal device that allow the user who made the dedicated call to change to a general call.
[0044] In the configuration described above, the building ID and the terminal building ID are the same, but this is not the only option. For example, if there are multiple banks in one building, the personal terminal building ID can target multiple banks, and one personal terminal building ID can be assigned to each bank.
[0045] <Explanation of elevator control methods> The processes performed by the elevator operation management system described above are realized through the cooperation of software and hardware resources. Specifically, the processor inside the computer installed in the elevator operation management system loads the software that implements each of the above-mentioned functions into memory and executes it, thereby realizing each of these functions. Therefore, the process performed by the elevator operation management system 10 can be understood as an elevator control method in which, when a user requests a dedicated call for exclusive use of the elevator, the system calculates the waiting time for the user who made the dedicated call, and if the calculated waiting time exceeds a predetermined threshold time, it sends a signal to the user who made the dedicated call asking whether they want to change from a dedicated call to a general call that other users can share.
[0046] Although this embodiment has been described above, the technical scope of the present invention is not limited to the scope described in the above embodiment. It is clear from the claims that various modifications or improvements made to the above embodiment are also included in the technical scope of the present invention. [Explanation of Symbols]
[0047] 1...Operation System, 10...Elevator Operation Management System, 11...Receiving Unit, 12...Authentication Unit, 13...Call Acceptance Judgment Unit, 14...Call Registration Unit, 15...Call Cancellation Acceptance Unit, 16...Call Cancellation Unit, 17...Waiting Time Extension Detection Unit, 18...Notification Data Creation Unit, 19...Transmission Unit, 20...Operation Control Unit, 40...Landing Elevator Service Request Device, 50...Center, 51...Receiving Unit, 52...Authentication Unit, 53...Verification Unit, 54...Judgment Unit, 55...Anomaly Detection Unit, 56...DB Registration Unit, 57...Transmission Unit, 58...Building DB, 59...ID Management DB, 60...User ID DB
Claims
1. An elevator having a control device for managing the operation of the elevator, The aforementioned control device is A calculation unit calculates the waiting time for a user who has made a dedicated call request for exclusive use of an elevator, If the waiting time calculated by the calculation unit changes to a value that exceeds a predetermined threshold time, the transmission unit sends a signal to the user who made the dedicated call asking whether they want to change from a dedicated call to a general call that other users can share a ride with, and if the user who made the dedicated call does not change to a general call, the transmission unit sends a signal to display a waiting time extension notification, which is a notification that the waiting time will be extended. An elevator equipped with [a specific feature / equipment].
2. The elevator according to claim 1, wherein the transmitting unit transmits a signal to notify a user requesting a dedicated call of the waiting time.
3. An elevator having a control device for managing the operation of the elevator, The aforementioned control device is A calculation unit calculates the waiting time for a user who has made a dedicated call request for exclusive use of an elevator, If the waiting time calculated by the calculation unit changes to a value that exceeds a predetermined threshold time, the transmission unit sends a signal to the user who made the dedicated call asking whether they want to change from a dedicated call to a general call that other users can share. Equipped with, When the number of times a user who has made a dedicated call has entered abnormal data exceeds a predetermined number, the user is designated as a "prohibited user" who is prohibited from registering dedicated calls. The aforementioned abnormal data indicates that there is a discrepancy between at least one of the following: the boarding floor entered by the user and the actual floor on which boarding is possible, and the destination floor entered by the user and the actual floor on which alighting is possible. Elevator.
4. The elevator according to claim 3, wherein a user who has made a dedicated call is designated as a prohibited user when the number of times they do not board at the inputted landing floor or alight at the destination floor exceeds a predetermined second number.
5. The processor executes the program stored in memory, When a user requests a dedicated call for exclusive use of an elevator, the waiting time for the user who made the dedicated call is calculated. If the calculated waiting time changes to a value that exceeds a predetermined threshold time, a signal is sent to the user who made the dedicated call to inquire whether they want to change from a dedicated call to a general call where other users can share the ride. If the user who made the dedicated call does not change to a general call, a signal is sent to display a waiting time extension notification, which is a notification that the waiting time will be extended. Elevator control methods.
6. An input section where the user enters a request for a dedicated call to use the elevator exclusively, If the waiting time for a user who has made a dedicated call exceeds a predetermined threshold time, a screen is displayed to the user who made the dedicated call, allowing them to choose whether or not to change from a dedicated call to a general call where other users can share a ride. The waiting time is displayed to the user, and if the user chooses not to change to a general call, a notification is displayed indicating that the waiting time will be extended. A terminal device equipped with the following features.
7. The terminal device according to claim 6, wherein the input unit is capable of selecting between a dedicated call and a general call.