Elevator control device and control method

The elevator control device extends door opening times for suitable cars and reallocates users to minimize waiting times caused by destination floor registration delays, ensuring efficient boarding.

JP7810232B1Active Publication Date: 2026-02-03FUJITEC CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024182096
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-10-17
Publication Date
2026-02-03
Estimated Expiration
2044-10-17

AI Technical Summary

Technical Problem

Elevator users may experience long waiting times due to the time required for destination floor registration, which can cause cars to depart before they can board, especially when security authentication is involved.

Method used

An elevator control device that extends the door opening time for cars that are suitable for boarding during registration, and reallocates users to other cars if necessary to minimize waiting time.

Benefits of technology

Ensures users can board the elevator efficiently by extending door opening times for suitable cars and reallocating them to cars departing in their direction, reducing waiting times.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007810232000001_ABST
    Figure 0007810232000001_ABST
Patent Text Reader

Abstract

To allow a user to board a car as efficiently as possible even when the user needs time for a registration operation in a destination floor registration device. [Solution] When a user starts to register their destination floor using a destination floor registration device at any floor in the elevator, the control device determines (A) whether or not there is a first target car among the multiple cars equipped in the elevator, with that floor and that user as the target floor and target user, respectively, that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts to register the destination floor (registration operation), and the condition (2) that the car is scheduled to depart within the operation time required by the target user to perform the registration operation on the destination floor registration device.If the control device determines in determination (A) that a first target car "exists," it issues a command to all first target cars to perform a first door-open extension for a time equal to or longer than the operation time.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a control technique for an elevator in which a destination floor registration device is installed. [Background technology]

[0002] Some elevators have a destination floor registration device installed on each floor, and each time a user registers their destination floor using the destination floor registration device, that user is assigned to a car (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-55976 Summary of the Invention [Problem to be solved by the invention]

[0004] On the other hand, depending on the destination floor registration device, it may take a user some time to complete the registration operation. For example, if the destination floor registration device requires the user to input the destination floor using a numeric keypad, the user will need to press the numeric keypad multiple times when registering a high-rise floor (for example, pressing the numeric keypad twice when registering a two-digit floor). Furthermore, if the destination floor registration device is linked to a security system, user authentication is required when registering a destination floor, so the user will need to hold their security card (such as an IC card) over a card reader in addition to inputting the destination floor. For this reason, if such a destination floor registration device is installed, it may take approximately 3 to 5 seconds to register a destination floor.

[0005] Therefore, even if a user starts to register a destination floor (registration operation) at a floor where a car is stopped and the user is hoping to board the car, depending on the status of the car at that time (scheduled departure time, etc.), the car may depart while the user is taking time to complete the registration operation. For this reason, depending on the elevator operation status, users may be forced to wait a long time at the landing until the next car arrives.

[0006] Therefore, an object of the present invention is to allow users to board cars as efficiently as possible even when it takes time for the users to perform the registration operation on the destination floor registration device. [Means for solving the problem]

[0007] The control device according to the present invention is an elevator control device having the following configuration (Aspect 1). When a user starts to register their destination floor using a destination floor registration device at any floor of the elevator, the control device determines, with that floor and that user as the target floor and target user, respectively, whether or not there is a first target car among the elevator's multiple cars that satisfies both the following conditions: (1) that the car is stopped at the target floor when the target user starts to register the destination floor (registration operation), and (2) that the car is scheduled to depart within the operation time required by the target user to perform the registration operation on the destination floor registration device. If the control device determines in determination (A) that a first target car "exists," it issues a command to all first target cars to perform a first door-open extension for a time equal to or longer than the operation time.

[0008] In the above-mentioned aspect 1, the first target car that satisfies both the above-mentioned conditions (A) and (B) will usually depart from the target floor while the target user is performing the registration operation at the target floor. In this case, when the target user starts to register his / her destination floor (registration operation), the car is stopped at the target floor where the target user is boarding, and even if the target user is hoping to board the car, the car will depart while the target user is performing the registration operation. Therefore, depending on the elevator operation status, the target user may be forced to wait a long time (to wait for a long time) at the landing of the target floor until the next car arrives.

[0009] According to the above-mentioned aspect 1, when a first target car exists, it becomes possible to assign a hall call for the target user to the first target car (in other words, to prevent the first target car from departing during the registration operation), and it becomes possible to continue stopping (keeping the doors open) at the target floor for all of the first target cars by issuing a first door opening extension command.

[0010] The control device according to the above-mentioned aspect 1 may have the following configuration (aspect 2). When the target user completes the registration operation, the control device may make a determination (B) of whether or not there is a car among the first target cars that is scheduled to depart in the same direction as the destination direction of the target user. Furthermore, when the control device determines in determination (B) that there is a car that is scheduled to depart in the same direction as the destination direction, the control device may make a determination (C) of whether or not the shortest estimated time required for cars other than the first target car to arrive at the target floor is equal to or longer than a predetermined time. Then, when the control device determines in determination (C) that the shortest estimated time is equal to or longer than the predetermined time, the control device may select an allocation destination of the hall call for the target user from among the first target cars that is scheduled to depart in the same direction as the destination direction, designate it as a second target car, and then allocate the hall call to the second target car. Furthermore, if the scheduled departure time of the second target car from the target floor is earlier than the scheduled boarding time of the target user into the second target car, the control device may instruct the second target car to extend the second door opening period to wait for the target user to board.

[0011] In the above-mentioned aspect 2, according to judgment (B), when the first target car is made to continue stopping (keeping the door open) at the target floor due to the command to extend the first door opening, it becomes possible to determine whether there is a car among the first target cars that can efficiently board the target user.

[0012] Furthermore, by making a judgment (C) when such a car exists among the first target cars, it becomes possible to determine whether the target user will be forced to wait a long time at the boarding area of ​​the target floor if the target user is unable to board the car.

[0013] If the target user will be forced to wait a long time at the landing of the target floor, the target user can be prevented from experiencing a long wait by having the target user board a first target car that is scheduled to depart in the same direction as the target user's destination. Therefore, in the above-mentioned aspect 2, if it is determined by judgment (C) that the target user will be forced to wait a long time, the target user is assigned to a second target car selected from the first target cars that are scheduled to depart in the same direction as the target user's destination (cars that can efficiently board the target user) (an assignment different from the usual assignment), and further, by issuing a command to extend the second door opening as necessary, the target user can be reliably allowed to board the second target car, and as a result, a situation can be created in which the target user does not have to wait a long time.

[0014] The control device according to the above-mentioned aspect 1 may have the following configuration (aspect 3). When the target user completes the registration operation, the control device may perform a determination (B) of whether or not there is a car among the first target cars that is scheduled to depart in the same direction as the destination direction of the target user. Then, when the control device determines in determination (B) that there is a car that is scheduled to depart in the same direction as the destination direction, the control device may select from that car an allocation destination of the hall call for the target user, designate it as a second target car, and then allocate the hall call to the second target car. Furthermore, when the scheduled departure time of the second target car from the target floor is earlier than the scheduled boarding time of the target user to the second target car, the control device may command the second target car to perform a second door opening extension to wait for the target user to board.

[0015] According to the above-mentioned aspect 3, when the first target car is made to continue stopping (keeping the doors open) at the target floor by the first door opening extension command, if there is a car among the first target cars that can efficiently board the target user, it is possible to ensure that the target user can board one of the cars (second target cars), regardless of whether the target user will be forced to wait a long time if they are unable to board that car.

[0016] The control device according to any one of the above aspects 1 to 3 may have the following configuration (Aspect 4): In the above judgment (A), the control device may determine whether or not there exists a first target car that satisfies, in addition to conditions (1) and (2), condition (3) that the total value of the extended time at the target floor is equal to or less than a predetermined value.

[0017] According to any of the above aspects 1 to 3, if multiple users at a target floor successively register their destination floors in the destination floor registration device, a first door open extension can be repeatedly instructed to be performed on the car stopped at that target floor (first target car), thereby preventing the car from departing from the target floor with a small number of passengers. On the other hand, repeated first door open extensions may significantly lengthen the stop time of the first target car at the target floor. According to the above aspect 4, the upper limit of the total extension time at the target floor can be limited to a predetermined value, and as a result, an upper limit can also be set on the stop time of the first target car at the target floor.

[0018] The control device according to the above-mentioned aspect 1 may have the following configuration (aspect 5): The control device may set the extension time when issuing a command to extend the first door opening to a time obtained by adding the travel time of the target user from the destination floor registration device to the first target car to the operation time, or a time longer than that.

[0019] According to the above-mentioned aspect 5, by issuing a command to extend the first door opening to the first target car, the first target car can be made to continue stopping (keeping the door open) at the target floor until the target user has completed boarding.

[0020] The control device according to the above-mentioned aspect 5 may have the following configuration (aspect 6): When a target user completes the registration operation, the control device may select an allocation destination of a hall call for the target user from the first target car, designate it as a second target car, and then allocate the hall call to the second target car, and may instruct cars other than the second target car among the first target cars to cancel the first door opening extension.

[0021] According to the above-mentioned aspect 6, for the cars other than the second target car among the first target cars, it is possible to cancel the first door open extension (useless door open extension until the target user has boarded) that has become unnecessary due to the selection of the second target car. This makes it possible to prevent cars other than the second target car from stopping for an unnecessarily long time at the target floor.

[0022] The control method according to the present invention is a control method for an elevator, and has the following configuration (Aspect 7). When a user starts to register their destination floor using a destination floor registration device at any floor of the elevator, this control device determines, with that floor and that user as the target floor and target user, respectively, whether or not there is a first target car among the multiple cars provided in the elevator that satisfies both the condition (1) that it is stopped at the target floor when the target user starts to register the destination floor (registration operation) and the condition (2) that it is scheduled to depart within the operation time required for the target user to perform the registration operation on the destination floor registration device. If it is determined in the determination (A) that the first target car "exists," it issues a command to all first target cars to perform a first door-open extension for a time equal to or longer than the operation time. [Effects of the Invention]

[0023] According to the present invention, even if a user needs time to perform the registration operation on the destination floor registration device, it is possible to get the user into the car as efficiently as possible. [Brief explanation of the drawings]

[0024] [Figure 1] 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. [Figure 2] FIG. 2 is a conceptual diagram illustrating an example of an installation position of a destination floor registration device in the embodiment. [Figure 3] FIG. 2 is a conceptual diagram illustrating device management data used in the embodiment. [Figure 4] 10 is a flowchart showing a part of an allocation process executed in the embodiment. [Figure 5] 5 is a flowchart showing a continuation of FIG. 4 in the allocation process. [Figure 6] 10 is a flowchart showing a part (continuation of FIG. 4) of the allocation process executed in the first modified example. [Figure 7] 10 is a flowchart showing a part of an allocation process executed in a second modified example. [Figure 8] 10 is a flowchart showing a part (continuation of FIG. 4) of the allocation process executed in the third modified example. DETAILED DESCRIPTION OF THE INVENTION

[0025] [1] Implementation [1-1] Overall structure of the elevator FIG. 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. In this embodiment, a destination floor registration device 1 is installed on each floor of the elevator, and when a user wishes to board a car G, the user is required to register their destination floor Fd in advance with the destination floor registration device 1 installed on the boarding floor. This elevator is equipped with a plurality of cars G, and further includes a group management control device 2 that manages them in a unified manner. The configuration of each part will be specifically described below.

[0026] <Destination floor registration device> The destination floor registration device 1 is provided with a device, such as a touch panel, that functions as both an input unit and a display unit, and the device is used by the user to register the destination floor Fd and to notify the user of various information. The destination floor registration device 1 may be provided with an input unit and a display unit separately. For example, the input unit is a mechanical button (such as a numeric keypad), and the display unit is a monitor dedicated to display.

[0027] 2(A) and 2(B) are conceptual diagrams illustrating an example of an installation position Qs of a destination floor registration device 1 in an embodiment. Typically, the destination floor registration device 1 is installed at the landing of each floor, as shown in FIG. 2(A). On the other hand, at a specific floor Fz, the destination floor registration device 1 may be installed at a predetermined position away from the landing, as shown in FIG. 2(B). As an example, the specific floor Fz is a floor where a building entrance is located, and the predetermined position is a position at or near the entrance of the building. The example of FIG. 2(B) shows a case where the destination floor registration device 1 is installed at the landing of the specific floor Fz and at a predetermined position away from the landing, which are distinguished by the reference symbols 1A and 1B. Furthermore, the examples of FIG. 2(A) and FIG. 2(B) show an elevator equipped with three cars G, which are distinguished by the reference symbols G1 to G3 on the specific floor Fz (see FIG. 2(B)) in order of furthest from the predetermined position.

[0028] In this embodiment, when a user starts registering their own destination floor Fd (registration operation) using a destination floor registration device 1 at any floor, an operation start signal Sx is transmitted from that destination floor registration device 1 to the group management control device 2. Then, when the user completes registering the destination floor Fd, that destination floor Fd is transmitted to the group management control device 2. As a result, a request for allocation of a hall call X for that user is made to the group management control device 2. Furthermore, at both the time of transmitting the operation start signal Sx and the time of transmitting the destination floor Fd, device information Pd for distinguishing that destination floor registration device 1 from other registration devices is also transmitted to the group management control device 2 so that the group management control device 2 can recognize which registration device is the operated destination floor registration device 1.

[0029] Here, in the destination floor registration device 1, it may take a user time to perform the registration operation. For example, if the destination floor registration device 1 requires the user to input the destination floor Fd using a numeric keypad (a numeric keypad displayed on a touch panel or a mechanical numeric keypad), the user will need to press the numeric keypad multiple times when registering a high-rise floor (for example, pressing the numeric keypad twice when registering a two-digit floor). Furthermore, to improve security, the destination floor registration device 1 may be linked to a security system. In this case, user authentication is required when registering the destination floor Fd, so the destination floor registration device 1 is provided with a card reader, and the user is required to hold their security card (such as an IC card) over the card reader in addition to inputting the destination floor Fd. Therefore, when such a destination floor registration device 1 is installed, it may take approximately 3 to 5 seconds to register the destination floor Fd.

[0030] Therefore, even if a user starts to register a destination floor Fd (registration operation) at a certain floor and expects to be able to board the car G when the car G is stopped at that floor, the car G may depart while the user is taking time to complete the registration operation, depending on the status of the car G at that time (such as the scheduled departure time Wg). For this reason, depending on the elevator operation status, the user may be forced to wait a long time at the landing until the next car G arrives.

[0031] Therefore, in this embodiment, even if the user takes time to complete the registration operation on the destination floor registration device 1, the group management control device 2 executes a control process to enable the user to board the car G as efficiently as possible. Specifically, the allocation process described below is executed with the reception of an operation start signal Sx as a trigger. Note that, when the destination floor Fd is entered using the numeric keypad on the destination floor registration device 1, the operation start signal Sx is transmitted to the group management control device 2 when the numeric keypad is pressed for the first time (for example, when the first digit is entered when a two-digit floor is to be registered), and, when a card reader is installed on the destination floor registration device 1 for the authentication required when registering the destination floor Fd, the operation start signal Sx is transmitted to the group management control device 2 when a security card is held over (touched) the card reader.

[0032] <Group management control device> The group management control device 2 centrally controls a plurality of cars G equipped in the elevator of this embodiment through an elevator control device provided for each car G (see FIG. 1).

[0033] Specifically, the group management control device 2 starts the allocation process (see FIG. 4 ) each time it receives an operation start signal Sx from any of the destination floor registration devices 1. If an allocation request is received from the destination floor registration device 1 during the execution of the allocation process, the group management control device 2 selects an allocation destination of the hall call X from among multiple cars G, using the departure floor Fc and destination floor Fd of the user registered with the destination floor registration device 1 as one hall call X. At this time, the group management control device 2 of this embodiment selects an allocation destination from among multiple cars G without considering the travel time Tk of the user from the destination floor registration device 1. Then, the group management control device 2 allocates the hall call X to the selected allocation destination. Furthermore, the group management control device 2 instructs the allocation destination to extend door opening as necessary to wait for the user to board. Then, the group management control device 2 causes the car G to execute a response operation to the hall call X (response process). Details of the allocation process will be described later.

[0034] Furthermore, when responding to a hall call X, the group management control device 2 registers the destination floor Fd indicated by the hall call X as a car call Y for the user for the car G at an appropriate timing after the car G arrives at the departure floor Fc indicated by the hall call X (for example, when the passengers have finished boarding and disembarking and the doors have closed) (registration processing). Then, the group management control device 2 causes the car G to execute a response operation to the car call Y (response processing).

[0035] Specifically, the group management control device 2 includes a storage unit 21 and a control unit 22 (see FIG. 1).

[0036] The memory unit 21 is a part configured with storage devices such as ROM and RAM, and stores information necessary for the control processing performed by the group management control device 2. In this embodiment, the memory unit 21 stores device management data Dr, hall call management data Dx, and car call management data Dy as such information.

[0037] Here, the device management data Dr is a database for managing, for each destination floor registration device 1, a plurality of pieces of information related to that registration device in association with each other (see FIG. 3). The hall call management data Dx and the car call management data Dy are data for managing, for each car G, information on hall calls X and car calls Y for users, respectively (not shown).

[0038] 3 is a conceptual diagram illustrating the device management data Dr used in this embodiment. In the device management data Dr, for each destination floor registration device 1, the device information Pd of the registration device, the installation floor Fs, and the installation location Qs, the operation time Tj required for the registration device, and the travel time Tk from the registration device to each car G are recorded in a mutually associated state. Here, the operation time Tj associated with each device information Pd is the time (such as the average time or longest time of actual measurements) required by the user to perform the registration operation at the destination floor registration device 1 identified by the device information Pd. Furthermore, the travel time Tk is the time (such as the average time or longest time of actual measurements) required by the user to travel from a predetermined position to the entrance / exit of each car G (G1 to G3).

[0039] As a result, when the group management control device 2 receives device information Pd together with the operation start signal Sx and the destination floor Fd from any of the destination floor registration devices 1, it becomes possible to identify the floor Fs on which the destination floor registration device 1 (the registration device on which the destination floor Fd has been registered) is installed from the device information Pd. In this embodiment, the floor Fs on which the destination floor registration device 1 is installed is used as the departure floor Fc (boarding floor) of the user who operated the registration device to register the destination floor Fd.

[0040] In addition, by referring to the installation location Qs associated with each device information Pd, the group management control device 2 can determine whether the destination floor registration device 1 identified by that device information Pd is installed at a landing or a specified location.

[0041] Furthermore, when the group management control device 2 starts the allocation process triggered by the reception of an operation start signal Sx from the destination floor registration device 1 specified by the device information Pd, the operation time Tj associated with each device information Pd is used as the extension time Tm1 when issuing a command to extend the door opening to a car G stopped at the floor Fs where the destination floor registration device 1 is installed. Also, when allocation to any car G is executed in response to an allocation request from a destination floor registration device 1 installed at a predetermined position on a specific floor Fz, the travel time Tk is used to calculate the extension time (extension times Tm2 and Tm3 described below) when it is necessary to issue a command to extend the door opening to that car G.

[0042] Furthermore, even if the destination floor registration device 1 is actually installed at the boarding area, if the boarding area is large and it takes time for users to move from the installation location of the destination floor registration device 1 to the boarding and alighting entrance of each car G (G1 to G3), the destination floor registration device 1 may be considered to be installed at a predetermined location, and in the device management data Dr, the installation location Qs may be associated with the device information Pd of the destination floor registration device 1 as a "predetermined location," and the specific time required for users to move to the boarding and alighting entrance of each car G (G1 to G3) may be associated as the travel time Tk.

[0043] The control unit 22 is a part that is responsible for executing the control processes (including allocation processes, registration processes, and response processes) performed by the group management control device 2. Specifically, the control unit 22 is made up of processing devices such as a CPU or MPU, and executes a control program installed in the group management control device 2 to realize the execution of its own control processes in software. Note that, before being installed in the group management control device 2, this control program may be stored in a readable state on a portable storage medium (for example, a flash memory, etc.), or may be stored in a downloadable state on a server, etc. Furthermore, the control processes performed by the group management control device 2 are not limited to being realized in software by executing a program, but may also be realized in hardware by a processing circuit built into the group management control device 2.

[0044] [1-2] Allocation process performed by the group management control device 4 and 5 are flowcharts showing the allocation process executed in this embodiment. This allocation process is started each time the group management control device 2 receives an operation start signal Sx from any of the destination floor registration devices 1. Hereinafter, a user who starts registering a destination floor Fd (registration operation) with that destination floor registration device 1 will be referred to as a "target user." Furthermore, the information (device information Pd) that the group management control device 2 receives from the destination floor registration device 1 together with the operation start signal Sx will be referred to as "received information Pr1."

[0045] When the allocation process starts, the group management control device 2 first uses the device management data Dr (see FIG. 3) to find device information Pd recorded therein that matches the device information Pd in ​​the received information Pr1, and then extracts the installation floor Fs associated with it (step S101). The group management control device 2 then sets the installation floor Fs as the departure floor Fc of the target user (Fc=Fs). Hereinafter, this departure floor Fc (=Fs) of the target user will be referred to as the "target floor."

[0046] After step S101, the group management control device 2 determines whether or not there is a first target car Gw1 that satisfies both of the following conditions (1) and (2) among the cars G (G1 to G3) equipped in the elevator.

[0047] Condition (1): The vehicle is stopped at the target floor when the target user starts registering the destination floor Fd (registration operation). Condition (2): The departure is scheduled to occur before the operation time Tj required for the target user to perform the registration operation on the destination floor registration device 1 has elapsed.

[0048] Specifically, the group management control device 2 first extracts all the cars G (G1 to G3) that satisfy both of the conditions (1) and (2) as the first target car Gw1 (step S102).The group management control device 2 then determines whether or not the first target car Gw1 has been extracted in step S102 (step S103).

[0049] Here, the first target car Gw1 that satisfies both the above conditions (1) and (2) will normally depart from the target floor while the target user is performing the registration operation at the target floor. In this case, when the target user starts to register his / her destination floor Fd (registration operation), the car G is stopped at the target floor where the target user is boarding, and even if the target user is hoping to board the car G, the car G will depart during the registration operation. Therefore, depending on the elevator operation status, the target user may be forced to wait a long time (to wait for a long time) at the landing of the target floor until the next car G arrives.

[0050] Therefore, when the group management control device 2 determines in step S103 that "extraction was successful (Yes)" (i.e., when it determines that the first target car Gw1 "exists"), it issues a first door open extension command to all of the first target cars Gw1, with the extension time Tm1 being the same as or longer than the operation time Tj, so that the hall call X for the target user can be assigned to the first target car Gw1 (in other words, so that the first target car Gw1 does not depart during the registration operation) (step S104). As a result, it becomes possible to continue stopping (keeping the doors open) at the target floor for all of the first target cars Gw1 by issuing the first door open extension command. In other words, even before the allocation destination of the hall call X for the target user has been determined, it becomes possible to issue a door open extension command to the car G (first target car Gw1) stopped at the target floor, so that the car G can continue to be stopped.

[0051] Thereafter, when the target user completes the registration operation at the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr1, a request for allocation of a hall call X for the target user is made to the group management control device 2. After step S104, the group management control device 2 determines whether or not an allocation request has been received from the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr1 (step S110). Furthermore, the group management control device 2 repeatedly performs step S110 until it can determine "received (Yes)" in step S110.

[0052] Specifically, each time the group management control device 2 receives a destination floor Fd from any of the destination floor registration devices 1, it determines whether the device information Pd received together with the destination floor Fd matches the device information Pd in ​​the received information Pr1 at the start of the allocation process. If the group management control device 2 determines that they "match," it determines that it has "received" an allocation request from the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr1. Here, the information that the group management control device 2 receives in the allocation request (destination floor Fd and device information Pd) is collectively referred to as "received information Pr2."

[0053] If the group management control device 2 determines in step S110 that the allocation request has been "received (Yes)," it sets the direction in which the target user travels from the departure floor Fc (the departure floor Fc=Fs set in step S101) to the destination floor Fd (the destination floor Fd in the received information Pr2) as the destination direction Kc of the target user. Then, the group management control device 2 sets the departure floor Fc and destination floor Fd of the target user as one hall call X, and selects the optimal car G as the allocation destination of that hall call X.

[0054] Specifically, the group management control device 2 determines whether or not there is a car G among the first target cars Gw1 that is scheduled to depart in the same direction as the destination direction Kc of the target user set in step S111 (step S201; see FIG. 5). This makes it possible to determine whether or not there is a car G among the first target cars Gw1 that can efficiently board the target user, when the first target car Gw1 is being made to continue stopping at the target floor (keeping the doors open) due to the first door open extension command in step S104.

[0055] Furthermore, if the group management control device 2 determines "exists (Yes)" in step S201, it determines whether the shortest of the estimated times Tg required for cars G other than the first target car Gw1 to arrive at the target floor is equal to or longer than a predetermined time Tg0 (step S202). By making the determination in step S202 in this way when there is a car G scheduled to depart in the same direction as the destination direction Kc of the target user, it becomes possible to determine whether the target user will be forced to wait a long time at the boarding area of ​​the target floor if the target user is unable to board that car G.

[0056] If the group management control device 2 determines in step S202 that "the time is equal to or longer than the predetermined time Tg0 (Yes)," it can determine that the target user will be forced to wait a long time at the platform of the target floor. In this case, if the target user can be allowed to board one of the first target cars Gw1 that is scheduled to depart in the same direction as the target user's destination direction Kc, the target user will not have to experience a long wait.

[0057] Therefore, in this embodiment, when the group management control device 2 determines in step S202 that "the time is longer than the predetermined time Tg0 (Yes)", it selects an elevator car G among the first target elevator cars Gw1 that is scheduled to depart in the same direction as the destination direction Kc of the target user, to which the hall call X for the target user will be assigned, and sets it as the second target elevator car Gw2 (step S211).

[0058] After step S211, the group management control device 2 assigns the hall call X for the target user to the second target car Gw2 (step S212). Then, the group management control device 2 records the information of the hall call X (departure floor Fc and destination floor Fd) in the part of the hall call management data Dx that corresponds to the second target car Gw2.

[0059] Here, if the target user is a user who has registered the destination floor Fd in the destination floor registration device 1 installed at a designated location on the specific floor Fz, the target user may take time to travel to the boarding / alighting entrance of the second target car Gw2 assigned to them after registering the destination floor Fd, and may miss the second target car Gw2.

[0060] Therefore, after step S212, the group management control device 2 determines whether the target user will miss the second target car Gw2 (step S213).

[0061] Specifically, the group management control device 2 uses the device management data Dr (see FIG. 3) to extract the installation location Qs associated with the same device information Pd (matching the device information Pd in ​​the received information Pr1) as the device information Pd found in step S101, and then determines whether the installation location Qs is a "departure point" or a "predetermined position." If the group management control device 2 determines that the installation location Qs is not a "departure point," it then determines that the target user will "not miss the train (No)."

[0062] On the other hand, if the group management control device 2 determines that the target user is not at the "predetermined position," it further extracts the travel time Tk to each car G (G1-G3) associated with the device information Pd in ​​the device management data Dr (see FIG. 3), and estimates the scheduled boarding time Wk of the target user into each car G (G1-G3) at the specific floor Fz based on the travel time Tk. The group management control device 2 then determines whether the scheduled departure time Wg from the target floor for the second target car Gw2 is earlier than the scheduled boarding time Wk of the target user into the second target car Gw2. If the group management control device 2 determines that the target user will "miss the train (Yes)," then it determines that the target user will "not miss the train (No)." On the other hand, if the group management control device 2 determines that the target user will "not miss the train," then it determines that the target user will "not miss the train (No)."

[0063] If the group management control device 2 determines in step S213 that the target user will miss the train (Yes), it commands the second target car Gw2 to perform a second door-open extension to wait for the target user to board (step S214). Specifically, the group management control device 2 commands the second door-open extension to set the door-open extension to an extension time Tm2 that is equal to or longer than the scheduled boarding time Wk of the target user to the second target car Gw2 at the specific floor Fz.

[0064] After step S214, the group management control device 2 notifies the target user of the allocation information (allocation information; in this case, car information of the second target car Gw2) made for the hall call X of the target user through the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr2 (by screen display or voice output) (step S215). Thereafter, the group management control device 2 ends the allocation process.

[0065] On the other hand, if the group management control device 2 determines in step S213 that "the passenger will not miss the train (No)", it performs step S215 without performing step S214 (second door opening extension).

[0066] In this way, an allocation is made to the second target car Gw2 selected from the first target car Gw1 that is scheduled to depart in the same direction as the target user's destination direction Kc (an allocation different from the usual one), and further, by issuing a command to extend the second door opening as necessary, it is possible to ensure that the target user can board the second target car Gw2, and as a result, it is possible to create a situation in which the target user does not have to experience a long wait.

[0067] The group management control device 2 performs normal allocation for the target user in both cases where it determines in step S201 that the target user does not exist (No) and where it determines in step S202 that the target user has not passed the predetermined time Tg0 (No). Specifically, this is as follows.

[0068] The group management control device 2 selects an allocation destination for the hall call X of the target user from among all the cars G, and sets it as the third target car Gw3 (step S221). As an example, the group management control device 2 selects the car G that can arrive at the departure floor Fc earliest among all the cars G as the third target car Gw3.

[0069] Thereafter, the group management control device 2 assigns the hall call X for the target user to the third target car Gw3 (step S222). Then, the group management control device 2 records the information of the hall call X (departure floor Fc and destination floor Fd) in the part of the hall call management data Dx that corresponds to the third target car Gw3.

[0070] Here too, if the target user is a user who has registered the destination floor Fd in the destination floor registration device 1 installed at a designated location on the specific floor Fz, the target user may take time to travel to the boarding / alighting entrance of the third target car Gw3 assigned to them after registering the destination floor Fd, and may miss the third target car Gw3.

[0071] Therefore, after step S222, the group management control device 2 determines whether or not the target user will miss the third target car Gw3 in the same manner as in step S213 described above (step S223).

[0072] If the group management control device 2 determines in step S223 that the target user will miss the train (Yes), it commands the third target car Gw3 to extend the door opening time to wait for the target user to board (step S224). Specifically, the group management control device 2 commands the door opening extension at this time to set the extension time Tm3 to the time obtained by subtracting the scheduled departure time Wg of the third target car Gw3 from the specific floor Fz from the scheduled boarding time Wk of the target user to the third target car Gw3 at the specific floor Fz, or a time longer than that.

[0073] After step S224, the group management control device 2 notifies the target user of the allocation information (allocation information; in this case, car information of the third target car Gw3) made for the hall call X of the target user through the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr2 (by screen display or voice output) (step S225). Thereafter, the group management control device 2 ends the allocation process.

[0074] On the other hand, if the group management control device 2 determines in step S223 that "the train will not be missed (No)", it performs step S225 without performing step S224 (extending the door opening time).

[0075] If the group management control device 2 determines in step S103 that "extraction was not possible (No)" (i.e., determines that the first target car Gw1 "does not exist"), when it receives an allocation request from the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr1, it performs a normal allocation as an allocation to the car G in response to the request. Specifically, it is as follows.

[0076] If the group management control device 2 determines in step S103 that it "could not be extracted (No)", it determines whether or not it has received an allocation request from the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr1 (step S120). Furthermore, the group management control device 2 repeats step S120 until it determines in step S120 that it has "received (Yes)".

[0077] Specifically, each time the group management control device 2 receives a destination floor Fd from any of the destination floor registration devices 1, it determines whether the device information Pd received together with the destination floor Fd matches the device information Pd in ​​the received information Pr1 at the start of the allocation process. If the group management control device 2 determines that they "match," it determines that it has "received" an allocation request from the destination floor registration device 1 identified by the device information Pd in ​​the received information Pr1. Here, the information that the group management control device 2 receives in the allocation request (destination floor Fd and device information Pd) is collectively referred to as "received information Pr2."

[0078] If the group management control device 2 determines in step S120 that the allocation request has been "received (Yes)," it treats the departure floor Fc and destination floor Fd of the target user (the departure floor Fc set in step S101 and the destination floor Fd in the received information Pr2) as one hall call X, and then executes the processing of steps S221 to S225 described above.

[0079] [2] Variation [2-1] First modified example Fig. 6 is a flowchart showing part of the allocation process (a continuation of Fig. 4) executed in the first modified example. When the group management control device 2 determines "exists (Yes)" in step S201, it may execute the process from step S211 without determining whether the target user will be forced to wait a long time at the landing of the target floor (step S202).

[0080] According to the first variant example, when the first target car Gw1 is caused to continue stopping (keeping the doors open) at the target floor by a first door opening extension command, if there is a car G among the first target cars Gw1 that can efficiently board the target user, it is possible to ensure that the target user can board one of the cars G (second target car Gw2), regardless of whether the target user will be forced to wait a long time if they are unable to board the car G.

[0081] [2-2] Second variant According to the above-described embodiment and the first modified example, in either case, when multiple passengers at a target floor successively register the destination floor Fd in the destination floor registration device 1, a first door open extension can be repeatedly instructed to the car G (first target car Gw1) stopped at that target floor, and as a result, it is possible to prevent the car G from departing from the target floor with a small number of passengers. On the other hand, repeated first door open extensions may significantly extend the stop time of the first target car Gw1 at the target floor. Therefore, the group management control device 2 may execute the following processing.

[0082] 7 is a flowchart showing a part of the allocation process executed in the second modified example. When extracting the first target car Gw1 in step S102, the group management control device 2 may extract as the first target car Gw1 a car G that satisfies, in addition to conditions (1) and (2), condition (3) that the total value Tz of the extension times Tm1 at the target floor is equal to or less than a predetermined value Tz0. Here, this total value Tz may be the sum of the extension times Tm1 already instructed for each car G stopped at the target floor, or may be the sum plus one more extension time Tm1 (in other words, the sum plus the extension time Tm1 when the next first door-open extension is instructed).

[0083] According to the second variant, the upper limit of the total value Tz of the extension time Tm1 at the target floor can be limited to a predetermined value Tz0, and as a result, an upper limit can also be set on the stopping time of the first target car Gw1 at the target floor.

[0084] [2-3] Third variant In the above-described embodiment and first variant example, when the group management control device 2 commands the first target car Gw1 to extend the first door opening in step S104 (see Figure 4), the extension time Tm1 for each first target car Gw1 at that time may be set to a time obtained by adding the travel time Tk of the target user from the destination floor registration device 1 to the first target car Gw1 to the operation time Tj, or a longer time.

[0085] Specifically, the group management control device 2 uses the device management data Dr (see FIG. 3) to extract the installation position Qs associated with the same device information Pd (matching the device information Pd in ​​the received information Pr1) as the device information Pd found in step S101, and then determines whether the installation position Qs is a "hall" or a "predetermined position." If the group management control device 2 determines that the installation position Qs is a "predetermined position," it extracts the travel time Tk to each car G (G1 to G3) associated with the device information Pd in ​​the device management data Dr (see FIG. 3) that corresponds to the first target car Gw1, and adds this to the operation time Tj to set the extension time Tm1. On the other hand, if the group management control device 2 determines that the installation position Qs is a "hall," it sets the extension time Tm1 without adding the travel time Tk.

[0086] This allows the first target car Gw1 to be instructed to extend the first door opening period, so that the first target car Gw1 can continue to stop (keep the door open) at the target floor until the target user has completed boarding.

[0087] On the other hand, when allocation to the second target car Gw2 is completed in step S212 (see FIGS. 5 and 6), further continuation of the door-open extension (first door-open extension) becomes pointless for cars G other than the second target car Gw2 among the first target cars Gw1. Also, when the processing from step S221 is executed via step S201 or S202, if the third target car Gw3 selected in step S221 is a car G other than the first target car Gw1, further continuation of the door-open extension (first door-open extension) becomes pointless for all of the first target cars Gw1. Therefore, the group management control device 2 may execute the following processing.

[0088] Fig. 8 is a flowchart showing part of the allocation process (a continuation of Fig. 4) executed in the third modified example. Fig. 8 shows the case where the process of this modified example, which will be described below, is applied to the embodiment (Fig. 5). Note that the process described below can also be applied to the first modified example (Fig. 6) and the second modified example.

[0089] In this modified example, when the group management control device 2 assigns to the second target car Gw2 in step S212, it instructs the cars G other than the second target car Gw2 among the first target cars Gw1 to cancel the first door opening extension (step S230).

[0090] According to this processing, for the cars G other than the second target car Gw2 among the first target cars Gw1, the first door open extension that has become unnecessary due to the selection of the second target car Gw2 (useless door open extension until the target user has completed boarding) can be canceled. This makes it possible to prevent the stop time at the target floor from becoming unnecessarily long for cars G other than the second target car Gw2.

[0091] Furthermore, when the group management control device 2 has assigned the third target car Gw3 in step S222, it determines whether the third target car Gw3 corresponds to any of the first target cars Gw1 (step S231). If the group management control device 2 determines "corresponds (Yes)" in step S231, it commands all of the first target cars G other than the third target car Gw3 to cancel the first door open extension (step S232A). On the other hand, if the group management control device 2 determines "does not correspond (No)" to any of the first target cars Gw1 in step S231, it commands all of the first target cars Gw1 to cancel the first door open extension (step S232B).

[0092] According to this processing, for the cars G other than the third target car Gw3 among the first target cars Gw1, the first door open extension (useless door open extension until the target user has boarded) that has become unnecessary due to the selection of the third target car Gw3 can be canceled. As a result, it is possible to prevent the stop time at the target floor from becoming unnecessarily long for cars G other than the third target car Gw3.

[0093] The above-described embodiments and modifications should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined not by the above-described embodiments and modifications, but by the claims. Furthermore, the scope of the present invention is intended to include all modifications that are equivalent to the scope of the claims and fall within the scope thereof.

[0094] From the above-described embodiments and modifications, the subject of the invention is not limited to the group management control device 2, but may be extracted individually from part or all of the control processes (including the control methods corresponding to the control processes) and programs executed by the group management control device 2. Also, part or all of the above-described elevators may be extracted as the subject of the invention. [Explanation of symbols]

[0095] 1. Destination floor registration device 2 Group management control device G car X Platform call Y Cage call 21 Memory section 22 Control Unit Dr. Device management data Dx Hall call management data Dy Cage call management data Fc Departure Floor Fd Destination floor Fs Installation floor Fz specific floor Kc destination direction Pd device information Qs installation position Sx operation start signal Tg estimated time Tj operation time Tk travel time Tz total value Wg Scheduled Departure Time Wk scheduled boarding time Gw1 1st Target Basket Gw2 2nd target basket Gw3 3rd target basket Pr1, Pr2 received information Tg0 Predetermined time Tm1, Tm2, ​​Tm3 extension time Tz0 Predetermined value

Claims

1. When a user starts to register his / her destination floor using a destination floor registration device at any floor of an elevator, that floor and that user are designated as the target floor and target user, respectively, and a determination (A) is made as to whether or not there exists a first target car among the multiple cars equipped in the elevator that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts the registration, and the condition (2) that the car is scheduled to depart within the time required for the target user to perform the registration operation on the destination floor registration device, When it is determined in the determination (A) that the first target car is present, a first door-opening extension is instructed to all of the first target cars, with the extension time being the same as or longer than the operation time, When the target user has completed the registration operation, a determination is made (B) as to whether or not there is a car among the first target cars that is scheduled to depart in the same direction as the destination direction of the target user; If it is determined in the determination (B) that there is a car scheduled to depart in the same direction as the destination direction, a further determination (C) is made as to whether or not the shortest estimated time required for cars other than the first target car to arrive at the target floor is equal to or longer than a predetermined time, If it is determined in the judgment (C) that the time is equal to or longer than the predetermined time, the elevator control device selects an elevator car among the first target cars that is scheduled to depart in the same direction as the destination direction as the destination car to be assigned a hall call for the target user, and then assigns the hall call to the second target car, and further, if the scheduled departure time of the second target car from the target floor is earlier than the scheduled boarding time of the target user into the second target car, commands the second target car to perform a second door opening extension to wait for the target user to board.

2. When a user starts to register his / her destination floor using a destination floor registration device at any floor of an elevator, that floor and that user are designated as the target floor and target user, respectively, and a determination (A) is made as to whether or not there exists a first target car among the multiple cars equipped in the elevator that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts the registration, and the condition (2) that the car is scheduled to depart within the time required for the target user to perform the registration operation on the destination floor registration device, When it is determined in the determination (A) that the first target car is present, a first door-opening extension is instructed to all of the first target cars, with the extension time being the same as or longer than the operation time, When the target user has completed the registration operation, a determination is made (B) as to whether or not there is a car among the first target cars that is scheduled to depart in the same direction as the destination direction of the target user; If it is determined in the judgment (B) that there is a car scheduled to depart in the same direction as the destination direction, the elevator control device selects from that car an allocation destination for the hall call for the target user and makes it a second target car, then allocates the hall call to the second target car, and further, if the scheduled departure time of the second target car from the target floor is earlier than the scheduled boarding time of the target user into the second target car, commands the second target car to perform a second door opening extension to wait for the target user to board.

3. 3. An elevator control device as described in claim 1 or 2, wherein in the judgment (A), it is determined whether or not there exists a car as the first target car that satisfies not only the conditions (1) and (2) but also the condition (3) that the total value of the extension time at the target floor is less than or equal to a predetermined value.

4. When a user starts to register his / her destination floor using a destination floor registration device at any floor of an elevator, that floor and that user are respectively designated as a target floor and a target user, and a determination (A) is made as to whether or not there exists a first target car among the multiple cars equipped in the elevator that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts the registration, and the condition (2) that the car is scheduled to depart within the time required for the target user to perform the registration operation on the destination floor registration device, When it is determined in the determination (A) that the first target car exists, a first door opening extension command is issued to all of the first target cars, the extension time being a time obtained by adding the movement time of the target user from the destination floor registration device to the first target car to the operation time or a time longer than that, When the target user completes the registration operation, the elevator control device selects the destination of the hall call for the target user from the first target car and makes it a second target car, and then allocates the hall call to the second target car, while instructing cars other than the second target car among the first target cars to cancel the first door opening extension.

5. When a user starts to register his / her destination floor using a destination floor registration device at any floor of the elevator, that floor and that user are designated as a target floor and a target user, respectively. A determination (A) is made as to whether or not there is a first target car among the multiple cars provided in the elevator that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts the registration, and the condition (2) that the car is scheduled to depart within the operation time required by the target user to perform the registration operation on the destination floor registration device, When it is determined in the determination (A) that the first target car is present, a first door-opening extension is instructed to all of the first target cars, with the extension time being the same as or longer than the operation time, When the target user has completed the registration operation, a determination is made (B) as to whether or not there is a car among the first target cars that is scheduled to depart in the same direction as the destination direction of the target user; If it is determined in the determination (B) that there is a car scheduled to depart in the same direction as the destination direction, a further determination (C) is made as to whether or not the shortest estimated time required for cars other than the first target car to arrive at the target floor is equal to or longer than a predetermined time, When it is determined in the judgment (C) that the predetermined time is exceeded, an elevator control method selects a car among the first target cars scheduled to depart in the same direction as the destination direction as a destination to which a hall call for the target user is to be allocated, designates it as a second target car, and then allocates the hall call to the second target car; further, if the scheduled departure time of the second target car from the target floor is earlier than the scheduled boarding time of the target user into the second target car, commands the second target car to perform a second door opening extension to wait for the target user to board.

6. When a user starts to register his / her destination floor using a destination floor registration device at any floor of the elevator, that floor and that user are designated as a target floor and a target user, respectively. A determination (A) is made as to whether or not there is a first target car among the multiple cars provided in the elevator that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts the registration, and the condition (2) that the car is scheduled to depart within the operation time required by the target user to perform the registration operation on the destination floor registration device, When it is determined in the determination (A) that the first target car is present, a first door-opening extension is instructed to all of the first target cars, with the extension time being the same as or longer than the operation time, When the target user has completed the registration operation, a determination is made (B) as to whether or not there is a car among the first target cars that is scheduled to depart in the same direction as the destination direction of the target user; An elevator control method comprising the steps of: when it is determined in the judgment (B) that there is a car scheduled to depart in the same direction as the destination direction, selecting from that car an allocation destination for a hall call for the target user and making it a second target car; then allocating the hall call to the second target car; and further, when the scheduled departure time of the second target car from the target floor is before the scheduled boarding time of the target user in the second target car, issuing a command to the second target car to perform a second door opening extension to wait for the target user to board.

7. When a user starts to register his / her destination floor using a destination floor registration device at any floor of the elevator, that floor and that user are designated as a target floor and a target user, respectively. A determination (A) is made as to whether or not there is a first target car among the multiple cars provided in the elevator that satisfies both the condition (1) that the car is stopped at the target floor when the target user starts the registration, and the condition (2) that the car is scheduled to depart within the operation time required by the target user to perform the registration operation on the destination floor registration device, When it is determined in the determination (A) that the first target car exists, a first door opening extension command is issued to all of the first target cars, the extension time being a time obtained by adding the movement time of the target user from the destination floor registration device to the first target car to the operation time or a time longer than that, When the target user completes the registration operation, an elevator control method is provided in which a hall call for the target user is allocated to a second target car selected from the first target car, and the second target car is then allocated to the second target car, while commands are given to cancel the first door opening extension for cars other than the second target car among the first target cars.

Citation Information

Patent Citations

  • Group control system of elevator

    JP2016055976A

  • Elevator control device

    JP2024007698A