Elevator control system and control method

Abstract

This enables group management control for multiple elevator cars without being limited by the number of elevator cars involved. [Solution] In an elevator equipped with multiple elevator cars and multiple destination floor registration devices, two or more destination floor registration devices, which are part or all of the multiple destination floor registration devices, are assigned multiple tasks (tasks for group management control) for performing group management control targeting the multiple elevator cars.

Description

[Technical Field]

[0001] The present invention relates to a control technology for an elevator provided with a destination floor registration device. [Background Art]

[0002] There are elevators provided with a plurality of cars and a plurality of destination floor registration devices (see, for example, Patent Document 1). In such an elevator, by performing group supervisory control targeting the plurality of cars, every time a user registers their own destination floor at any one of the destination floor registration devices, a candidate car is selected from among the plurality of cars, and then a hall call for that user is assigned to the candidate car. Conventionally, such group supervisory control has been performed by a dedicated group supervisory control device. [Prior Art Document] [Patent Documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2019-172461 [Patent Document 2] Japanese National Publication of International Patent Application No. 2013-510060 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] On the other hand, Patent Document 2 discloses a technology in which every time a user registers a destination floor, group supervisory control is performed by the destination floor registration device at which the registration was performed.

[0005] In recent years, with the increasing size of buildings, the number of elevator cars in a single elevator has tended to increase. However, when attempting to manage a large number of elevator cars with a single group control system, the processing power required for the system increases as the number of cars to be managed increases. For example, the required processing power increases exponentially with each additional elevator car being managed. Therefore, the number of elevator cars that can be managed by a single group control system is limited to a number corresponding to the processing power of that system. In other words, it becomes difficult to perform group control for a number of elevator cars exceeding that limit.

[0006] Furthermore, if group control is attempted using only one destination floor registration device instead of a group control device, as in Patent Document 2, the number of elevator cars that can be targeted for group control will be limited to a number corresponding to the processing capacity of the single destination floor registration device. In this case as well, it becomes difficult to perform group control for a large number of elevator cars exceeding that number.

[0007] Therefore, the objective of the present invention is to enable group management control for multiple elevator cars without being limited by the number of elevator cars involved. [Means for solving the problem]

[0008] The control system according to the present invention is a control system in an elevator equipped with a plurality of elevator cars and a plurality of destination floor registration devices, wherein two or more destination floor registration devices, which are part or all of the plurality of destination floor registration devices, share and perform a plurality of tasks (tasks for group management control) for carrying out group management control for the plurality of elevator cars (Aspect 1).

[0009] According to the above embodiment 1, a cluster for group management control is configured with two or more destination floor registration devices, and within that cluster, multiple tasks for performing group management control (tasks for group management control) can be distributed and processed. This enables the entire cluster to achieve high processing capacity. Furthermore, even if one of the destination floor registration devices fails to operate normally (for example, if it malfunctions), the other destination floor registration devices that are operating normally can share the tasks and perform group management control.

[0010] The control system according to the above embodiment 1 may have the following configuration (embodiment 2). If the above-mentioned plurality of tasks (tasks for group management control) include a calculation task and an assignment task, one of the multiple destination floor registration devices provided by the elevator may be responsible for executing the assignment task as the first higher-level device, and one or more destination floor registration devices other than the first higher-level device among the plurality of destination floor registration devices may be responsible for executing the calculation task as the first lower-level devices. In this case, the calculation task performs the process of calculating an evaluation value for each elevator car, assuming that a landing call has been assigned to that elevator car for the user when a user registers a destination floor in any of the above-mentioned multiple destination floor registration devices. In the assignment task, when a user registers a destination floor using one of the multiple destination floor registration devices mentioned above, a candidate car is selected from among the multiple cars based on the evaluation value obtained for each car through the execution of the calculation task, and then the user's boarding call is assigned to that candidate car.

[0011] According to the above embodiment 2, a cluster is formed by the first higher-level device and the first lower-level device, and within that cluster, each device can be made to perform tasks appropriate to its own device.

[0012] The control system according to the above embodiment 2 may have the following configuration (embodiment 3). In the assignment task, the first higher-level device may, when a user registers a destination floor using one of the multiple destination floor registration devices provided by the elevator, send a request to the first lower-level device to execute a calculation task, and then use the evaluation value obtained from the execution of the calculation task to select a candidate elevator car.

[0013] According to embodiment 3 described above, a cluster can be formed with the first higher-level device as the management node and the first lower-level device as the computing node.

[0014] The control system according to the above embodiment 3 may have the following configuration (embodiment 4): Each time a user registers a destination floor using one of the multiple destination floor registration devices provided by the elevator, that destination floor registration device may perform an assignment task as the first higher-level device.

[0015] According to the above embodiment 4, it becomes possible to create a situation in which any of the multiple destination floor registration devices can be either a first higher-level device or a first lower-level device (a situation with a high degree of freedom in cluster configuration).

[0016] The control system according to the above embodiment 4 may have the following configuration (embodiment 5). When the first higher-level device transmits a request to execute a calculation task to the first lower-level device, it may transmit a request to execute a calculation task for the same single train car to two or more first lower-level devices.

[0017] According to embodiment 5 described above, even if any of the first subordinate devices fail to operate normally, the evaluation value for the elevator car that that first subordinate device was responsible for can be obtained from another first subordinate device that is responsible for the same elevator car.

[0018] The control system according to the above embodiment 5 may have the following configuration (embodiment 6). After the first higher-level device sends a request to the first lower-level device to execute a calculation task, it may adopt the evaluation value that is returned from the first lower-level device as the evaluation value for each elevator car, and perform candidate car selection when all evaluation values ​​for the elevator cars targeted in the calculation task (some or all of the multiple elevator cars) have been collected.

[0019] According to the above embodiment 6, it becomes possible to improve the processing speed until the allocation is completed.

[0020] A control system according to any of the above embodiments 4 to 6 may have the following configuration (embodiment 7). The first subordinate device may have an upper limit on the number of calculation tasks that can be processed in parallel individually. In this case, when each of the first subordinate devices receives a request to execute a calculation task, it determines whether the number of calculation tasks it is currently executing has reached the upper limit, and if it determines that it has not, it can execute the calculation task corresponding to the request.

[0021] According to embodiment 7 described above, by setting an upper limit on the number of calculation tasks that the first subordinate device handles, the load on the first subordinate device can be limited. Therefore, the first subordinate device can be made to handle a part of the tasks (calculation tasks) for performing group management control without interfering with the original mechanism of the first subordinate device (its function as a user interface that enables users to register destination floors).

[0022] The control system according to aspect 7 described above may have the following configuration (aspect 8). After the first host device transmits a calculation task execution request to the first subordinate device, if an evaluation value is returned from the first subordinate device, and if all evaluation values for the target car (some or all of the plurality of cars included in the elevator) specified in the calculation task have not been collected, the first host device may re-issue a calculation task execution request targeting cars that do not yet have an evaluation value at that time to the first subordinate device.

[0023] According to aspect 8 described above, even when an increase in the number of users causes duplicate calculation task execution requests to the same first subordinate device, leading to a situation where the number of calculation tasks being executed in each first subordinate device easily reaches the upper limit, it is possible to consistently collect all evaluation values for all cars.

[0024] The control system according to any one of aspects 4 to 8 described above may have the following configuration (aspect 9). When the first host device transmits a calculation task execution request to the first subordinate device, the first host device may take charge of executing a calculation task targeting any one of the plurality of cars included in the elevator, and issue calculation task execution requests targeting each of the remaining cars to the first subordinate device.

[0025] According to aspect 9 described above, the first host device can execute calculation tasks together with the first subordinate device. This enables efficient distribution of calculation tasks to all destination floor registration devices that constitute the cluster.

[0026] The control system according to aspect 2 or 3 described above may have the following configuration (aspect 10). The control system may comprise, as a cluster for group management control configured by two or more destination floor registration devices, a first cluster including a first host device and a first lower device, and a second cluster different from the first cluster. Here, the second cluster is a cluster including a second host device and a second lower device; the second host device is any one destination floor registration device outside the first cluster and is in charge of executing an assignment task; the second lower device is one or more destination floor registration devices outside the first cluster and other than the second host device, and is in charge of executing a calculation task. Then, when any destination floor registration device in the first cluster becomes unable to operate normally, the second host device and the second lower device in the second cluster may share a plurality of tasks for performing group management control (tasks for group management control) in place of the first cluster.

[0027] According to the above aspect 10, even when the first cluster becomes unable to operate normally, the first cluster can be replaced (backed up) by the second cluster. Therefore, all group management control including control during backup can be performed only by the destination floor registration devices.

[0028] The control system according to aspect 2 or 3 described above may have the following configuration (aspect 11). The control system comprises, as a cluster for group management control configured by two or more destination floor registration devices, only the first cluster including a first host device and a first lower device, and a destination floor registration device outside the first cluster may include: a second host device that is in charge of executing the assignment task in place of the first host device when the first host device becomes unable to operate normally; and a second lower device that is in charge of executing the calculation task in place of the first lower device when the first lower device becomes unable to operate normally.

[0029] According to the above embodiment 11, even if the first cluster fails to operate normally, only the destination floor registration device that has failed to operate normally within the first cluster can be replaced (backed up) by another destination floor registration device. Therefore, all group management control, including control during backup, can be performed by the destination floor registration device alone.

[0030] The control system according to the above embodiment 10 or 11 may have the following configuration (embodiment 12). The first higher-level device may, when it and the first lower-level devices are all operating normally, distribute an assignment signal to destination floor registration devices other than itself, indicating that it is responsible for executing the assigned task. On the other hand, if any of the first lower-level devices become unable to operate normally, it may stop distributing the assignment signal from itself. In this case, if the second higher-level device is unable to receive the assignment signal from the first higher-level device, it may start executing the assigned task on behalf of the first higher-level device and start distributing the assignment signal to destination floor registration devices other than itself.

[0031] According to the above embodiment 12, if the first cluster becomes unable to perform group management control, the distribution of the assignment responsibility signal from the first higher-level device will be interrupted, thereby ensuring that the second higher-level device recognizes that a replacement (backup) for the first cluster is needed. Upon recognizing this, the second higher-level device will start executing the assignment task on behalf of the first higher-level device and start distributing the assignment responsibility signal, thereby enabling a smooth transfer of control authority for group management from the first higher-level device to the second higher-level device. Furthermore, each destination floor registration device will be able to accurately recognize which of the first and second higher-level devices is currently responsible for the assignment task.

[0032] The control system according to the above embodiment 10 or 11 may have the following configuration (embodiment 13). Any of the multiple destination floor registration devices provided by the elevator may distribute an "alive status signal" to other destination floor registration devices when it is operating normally. In this configuration, the "alive status signal" distributed by the first and second higher-level devices may include assignment information indicating whether the higher-level device is in charge of executing the assigned task or not. Furthermore, if the first higher-level device and all first lower-level devices are operating normally, it may distribute its own "alive status signal" with the assignment information in the signal indicating it is in charge. On the other hand, if any of the first lower-level devices become unable to operate normally, it may change the assignment information in its "alive status signal" to an "out of charge" state. In this case, if the assignment information in the "alive status signal" received by the first higher-level device is in a "in charge" state, the second higher-level device can distribute its own "alive status signal" with the assignment information in the signal indicating it is out of charge. Furthermore, if the second higher-level device is unable to receive an alive status signal from the first higher-level device, or if the assignment information in the alive status signal received from the first higher-level device becomes unavailable, it can start executing the assignment task on behalf of the first higher-level device and change the assignment information in its own alive status signal to an available state.

[0033] According to the above embodiment 13, when the first cluster becomes unable to perform group management control, the assignment information in the alive status signal of the first higher-level device is changed to an unassigned state, thereby ensuring that the second higher-level device recognizes that a replacement (backup) for the first cluster is needed using the alive status signal. Upon recognizing this, the second higher-level device begins executing the assignment task on behalf of the first higher-level device and changes the assignment information in its own alive status signal to an assigned state, thereby enabling a smooth transfer of control authority for group management from the first higher-level device to the second higher-level device. Furthermore, the alive status signal allows each destination floor registration device to accurately recognize which of the first and second higher-level devices is currently in charge of the assignment task.

[0034] In a control system according to any of the above embodiments 2 to 13, when selecting a first subordinate device from among a plurality of destination floor registration devices provided by the elevator, the first subordinate device may be selected from among the plurality of destination floor registration devices in order from the one with the lowest frequency of destination floor registration (Embodiment 14).

[0035] According to the above embodiment 14, the processing capacity of the destination floor registration device can be effectively utilized for the first subordinate device without interfering with the original function of the destination floor registration device (its function as a user interface) as much as possible.

[0036] A control system according to any of the above embodiments 1 to 3 may have the following configuration (embodiment 15). The control system may include a group control device that performs a plurality of tasks for carrying out group control (tasks for group control), separate from the plurality of destination floor registration devices provided by the elevator. If the group control device fails to operate normally, two or more destination floor registration devices, which are part or all of the plurality of destination floor registration devices, may take over the group control device and perform the plurality of tasks for carrying out group control (tasks for group control).

[0037] According to the above embodiment 15, if the group control device fails to operate normally, a cluster for group control can be formed using two or more destination floor registration devices, and this cluster can take over (back up) the group control device. In other words, the processing capacity of the destination floor registration devices can be effectively utilized to continue elevator operation.

[0038] The control method according to the present invention relates to an elevator equipped with a plurality of elevator cars and a plurality of destination floor registration devices, wherein two or more destination floor registration devices, which are part or all of the plurality of destination floor registration devices, are assigned a plurality of tasks (tasks for group management control) for performing group management control for the plurality of elevator cars (Aspect 16). [Effects of the Invention]

[0039] According to the present invention, group management control for multiple elevator cars can be implemented without being limited by the number of elevator cars involved. [Brief explanation of the drawing]

[0040] [Figure 1] This is a conceptual diagram showing the overall configuration of the elevator according to the first embodiment. [Figure 2] This is a block diagram showing the configuration applied to each destination floor registration device in the first embodiment. [Figure 3] This is a conceptual diagram illustrating (A) device management data and (B) cage management data used in the first embodiment. [Figure 4] This is a flowchart showing some of the assignment tasks performed in the first embodiment. [Figure 5] This flowchart shows the continuation of Figure 4 regarding the assigned tasks. [Figure 6] This is a flowchart showing the response processing (including calculation tasks) performed in the first embodiment. [Figure 7] This flowchart shows some of the assigned tasks performed in the first modified example. [Figure 8]This flowchart shows the response processing (including calculation tasks) performed in the second modified example. [Figure 9] This is a conceptual diagram showing the overall configuration of the elevator according to the second embodiment. [Figure 10] (A) A block diagram showing the configurations applied to the first and second higher-level devices in the second embodiment, and (B) A conceptual diagram illustrating the device management data Dr used in the second embodiment. [Figure 11] This is a block diagram showing the configurations applied to the first and second subordinate devices in the second embodiment. [Figure 12] This is a flowchart illustrating the assignment tasks performed in the second embodiment. [Figure 13] This is a flowchart illustrating the backup process performed in the second embodiment. [Figure 14] This flowchart shows the backup process performed in the fifth variation. [Figure 15] This is a conceptual diagram showing the overall configuration of the elevator according to the sixth modified example. [Figure 16] This is a conceptual diagram showing the overall configuration of the elevator according to the third embodiment. [Modes for carrying out the invention]

[0041] [1] First Embodiment [1-1] Overall configuration of the elevator Figure 1 is a conceptual diagram showing the overall configuration of an elevator according to the first embodiment. In this embodiment, the elevator comprises a plurality of destination floor registration devices 1, a plurality of elevator cars G, and a plurality of elevator control devices 2 that individually control each of the plurality of elevator cars G. Here, the destination floor registration device 1 is a device that functions as a user interface to enable users to register destination floors Fd. The destination floor registration devices 1 are connected to each other via a network W, and each elevator control device 2 is connected to each destination floor registration device 1 via the network W.

[0042] Conventionally, group control (control that centrally manages multiple elevator cars G through an elevator control device 2) for multiple elevator cars G was performed by a dedicated group control device. In this embodiment, however, instead of such a group control device, two or more destination floor registration devices 1, which are part or all of the multiple destination floor registration devices 1 that the elevator is equipped with, share and perform multiple tasks (tasks for group control) for performing group control. Specifically, these multiple tasks (tasks for group control) are distributed by being assigned to two or more destination floor registration devices 1, which are part or all of the multiple destination floor registration devices 1, and each destination floor registration device 1 executes the task assigned to it, so that the two or more destination floor registration devices 1 become a single cluster Q and perform group control. A detailed explanation follows below.

[0043] <Tasks for group management and control> Tasks for group management and control include computation tasks, assignment tasks, and learning tasks.

[0044] In the calculation task, when a user registers a destination floor Fd using one of the multiple destination floor registration devices 1 provided by the elevator, the system calculates an evaluation value Vx(Pg) for each elevator car G, assuming that a landing call X for that user has been assigned to that elevator car G.

[0045] Here, the evaluation value Vx for each elevator car G is a numerical representation of how suitable that elevator car G is to be assigned to a landing call X (in other words, its suitability as an assignment destination). The evaluation value Vx uses the estimated arrival time of elevator car G to the departure floor Fc (the passenger's boarding floor) indicated by the landing call X, and the estimated waiting time required for elevator car G to arrive at that departure floor Fc. When the estimated arrival time is used as the evaluation value Vx, the earlier the time indicated by the evaluation value Vx, the higher the evaluation of elevator car G as an assignment destination (higher suitability as an assignment destination). When the estimated waiting time is used as the evaluation value Vx, the shorter the time indicated by the evaluation value Vx, the higher the evaluation of elevator car G as an assignment destination (higher suitability as an assignment destination).

[0046] In the assignment task, when a user registers a destination floor Fd using one of the multiple destination floor registration devices 1 provided by the elevator, the system selects a candidate car Gk from among the multiple cars G based on the evaluation value Vx obtained for each car G through the execution of the calculation task, and then assigns the user's landing call X to that candidate car Gk.

[0047] In the learning task, for each elevator car G, the operation data of that elevator car G transmitted sequentially from the elevator control device 2 is statistically analyzed, the resulting analysis data is stored as learning data Dp, and further, learning is performed to improve the calculation accuracy when calculating the evaluation value Vx of the elevator car G using this learning data Dp. Here, the learning data Dp includes analysis data on the operation status of the elevator car G (average door opening time, average door closing time, average travel time between floors, average stop time at each floor, etc.) and analysis data on the usage status of the elevator car G (average number of landing calls X in the past 5 minutes, average congestion level inside the elevator car G in the past 5 minutes, etc.). Note that AI (such as a neural network) may be used for the analysis of the operation data, not just statistical analysis.

[0048] <Destination Floor Registration Device> In this embodiment, each time a user registers a destination floor Fd using one of the multiple destination floor registration devices 1 provided in the elevator, that destination floor registration device 1 acts as the first higher-level device and is responsible for executing the assignment task. In addition, one or more destination floor registration devices 1 other than the first higher-level device act as the first lower-level devices and are responsible for executing the calculation task. More specifically, it is as follows.

[0049] When the first higher-level device is assigned a task, it first sends a request to the first lower-level device to execute the calculation task. At this time, the first higher-level device sends car information Pg to each first lower-level device to specify which car G the execution request is for calculating the evaluation value Vx, in order to distinguish the car G to be calculated from other cars. In addition, the first higher-level device also sends device information Pd to the first lower-level device to distinguish itself from other registration devices, so that the first lower-level device can recognize which destination floor registration device 1 sent the execution request.

[0050] In elevators where the total number of destination floor registration devices 1 is more than twice the total number of elevator cars G, when the first higher-level device sends a request to execute a calculation task to the first lower-level device, it sends a request to execute a calculation task for each elevator car G to two or more first lower-level devices. In this case, the first higher-level device can distribute the elevator cars G assigned to the first lower-level devices equally among all of them.

[0051] When the first subordinate device receives a request to execute a calculation task, it executes the calculation task corresponding to that request. Specifically, the first subordinate device calculates an evaluation value Vx(Pg) for the elevator car G specified in the calculation task execution request and sends the evaluation value Vx(Pg) back to the first superior device (response processing).

[0052] Subsequently, the first higher-level device uses the evaluation value Vx(Pg) obtained from the reply from the first lower-level device to select a candidate car Gk. Specifically, after sending a request to the first lower-level device to execute the calculation task, the first higher-level device adopts the evaluation value Vx(Pg) that is returned first from the first lower-level device as the evaluation value Vx(Pg) for each car G. Once all the evaluation values ​​Vx(Pg) for the car G targeted in the calculation task (some or all of the multiple car Gs) among the multiple car Gs that the elevator has are collected, the first higher-level device selects a candidate car Gk.

[0053] On the other hand, regarding the learning task, each of the multiple destination floor registration devices 1 provided by the elevator performs the learning task on all elevator cars G, thereby learning for all elevator cars G to improve the accuracy of calculating the evaluation value Vx(Pg). As a result, each destination floor registration device 1, when assigned a calculation task as the first subordinate device, will be able to accurately calculate the evaluation value Vx of a given elevator car G, regardless of which elevator car G the calculation task targets (i.e., regardless of which elevator car G's evaluation value Vx it is calculating).

[0054] With this control system, a cluster Q for group management control is formed by the first higher-level device and the first lower-level device, and within that cluster Q, each device can be made to perform tasks appropriate to its device. In other words, the first higher-level device can be used as the management node and the first lower-level device as the computing node to form a single cluster Q. Therefore, multiple tasks for performing group management control (tasks for group management control) can be distributed and processed within that cluster Q. As a result, the entire cluster Q can achieve high processing capacity. Thus, group management control targeting multiple elevator cars G can be realized without being limited by the number of elevator cars G to be targeted.

[0055] Furthermore, according to the control system of this embodiment, in addition to enabling high processing capacity across the entire cluster Q, it becomes possible to create a situation where any of the multiple destination floor registration devices 1 provided by the elevator can act as either a first higher-level device or a first lower-level device (a situation with a high degree of freedom in the configuration of cluster Q). Therefore, even if one of the destination floor registration devices 1 becomes unable to operate normally (for example, due to a malfunction), the other normally operating destination floor registration devices 1 can share the task and carry out group management control.

[0056] Figure 2 is a block diagram showing the configuration applied to each destination floor registration device 1 in this embodiment. As shown in this figure, each destination floor registration device 1 comprises an operation unit 10, a storage unit 11, and a control unit 12.

[0057] The operation unit 10 is composed of a device that combines the functions of an input unit and a display unit, such as a touch panel, and through the operation unit 10, users can register their destination floor Fd and receive various information notifications. The operation unit 10 may also consist of separate devices for the input unit and the display unit. For example, the input unit may consist of mechanical buttons (such as a numeric keypad), and the display unit may consist of a monitor dedicated to display.

[0058] The memory unit 11 is a part composed of memory devices such as ROM and RAM, and stores information necessary for the control processing performed by the destination floor registration device 1. In this embodiment, such information stored in the memory unit 11 includes information necessary for operation as a user interface and information necessary when taking on a part of the group management control task (the learning data Dp mentioned above, and the device management data Dr and car management data Dt described below). In this embodiment, all data of the learning data Dp, device management data Dr, and car management data Dt are stored in the memory unit 11 of each destination floor registration device 1 so that they can be executed regardless of which task each destination floor registration device 1 is assigned to.

[0059] Here, the device management data Dr is a database for managing multiple pieces of information related to each destination floor registration device 1 by linking them together (see Figure 3(A)). The car management data Dt is a database for managing multiple pieces of information related to each elevator car G by linking them together (see Figure 3(B)).

[0060] Figure 3(A) 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, device information Pd for identifying that destination floor registration device 1 from other registration devices and the installation floor Fs of the destination floor registration device 1 are recorded in a manner that is associated with each other.

[0061] As a result, each destination floor registration device 1 can identify its own installation floor Fs from its own device information Pd by referring to the device management data Dr. In this embodiment, when each destination floor registration device 1 is assigned a task as the first higher-level device, the installation floor Fs of that registration device is used as the departure floor Fc of the user who operated the registration device to register the destination floor Fd.

[0062] Figure 3(B) is a conceptual diagram illustrating the car management data Dt used in this embodiment. In the car management data Dt, for each elevator car G, the car information Pg and current status Ps of that elevator car G are recorded in a corresponding manner. Here, the current status Ps of each elevator car G contains information indicating whether that elevator car G is in operation (in the example of Figure 3(B), it is either "in operation" or "off-duty").

[0063] The control unit 12 is responsible for the control processing performed by the destination floor registration device 1 (including its operation as a user interface and the execution of its assigned tasks among the group management control tasks). Specifically, the control unit 12 is composed of processing devices such as a CPU and an MPU, and implements its assigned control processing in software by executing a control program installed in the destination floor registration device 1. This control program may be stored in a readable state on a portable storage medium (e.g., flash memory) or in a downloadable state on another server before being installed in the destination floor registration device 1. Furthermore, the control processing performed by the destination floor registration device 1 is not limited to being implemented in software by executing a program, but may also be implemented in hardware by processing circuits built into the destination floor registration device 1.

[0064] <Elevator control device> Each elevator control device 2 controls the operation of its corresponding elevator car G (such as the movement of the elevator car G and the opening and closing of its doors) in accordance with the landing call X assigned to the elevator car G by the first higher-level device, and also distributes operation data indicating the operating status of the elevator car G at that time (such as its operation status and usage status) to all of the multiple destination floor registration devices 1 installed in the elevator. As described above, this operation data is used for learning (execution of learning tasks) performed by each destination floor registration device 1.

[0065] [1-2] Control processing performed by the destination floor registration device [1-2-1] Assigned tasks performed by the first higher-level device Figures 4 and 5 are flowcharts showing the assignment task performed in this embodiment. This assignment task is started in the destination floor registration device 1 (first higher-level device) each time a user registers a destination floor Fd in one of the multiple destination floor registration devices 1 provided in the elevator.

[0066] When an assignment task is initiated, the first higher-level device first extracts all the device information Pd of destination floor registration devices 1 that are functioning normally from the device information Pd recorded in the device management data Dr, in order to grasp the device information Pd of destination floor registration devices 1 (hereinafter referred to as "cluster configuration devices") that are responsible for performing group management control as cluster Q. Then, it lists these device information Pd as target device information Pdk(I) (step S101). Here, list number I is a number starting from 1. The first higher-level device then assigns the total number of target device information Pdk(I) (here, the last value of list number I) to the variable M1.

[0067] In this embodiment, each destination floor registration device 1 periodically sends an "alive status signal Sx" indicating that it is operating normally, along with its own device information Pd, to other destination floor registration devices 1. Each destination floor registration device 1 then understands the individual operating status (whether it is operating normally or not) of the other destination floor registration devices 1 based on the distribution status of the "alive status signal Sx" from the other destination floor registration devices 1. Therefore, when the first higher-level device executes step S101, it can extract only the device information Pd of destination floor registration devices 1 that are operating normally from the device information Pd recorded in the device management data Dr.

[0068] As an example of listing in step S101, the first higher-level device can randomly arrange the device information Pd of the normally functioning destination floor registration device 1, assign numbers to them, and then list them.

[0069] Next, the first higher-level device, in order to determine which elevator car G is currently in operation, extracts all elevator car information Pg recorded in the elevator car management data Dt that have a current status Ps associated with that Pg that is "in operation," and then lists these elevator car information Pg as operating elevator car information Pgk(J) (step S102). Here, the list number J is a number starting from 1. Then, the first higher-level device assigns the total number of operating elevator car information Pgk(J) (in this case, the last value of list number J) to the variable M2.

[0070] After step S102, the first higher-level device extracts a destination floor registration device 1 other than itself from the cluster configuration devices as the first lower-level device and sends a request to execute the calculation task to that first lower-level device. Specifically, it is as follows:

[0071] The first higher-level device first sets the variable Ix, which is used to read the target device information Pdk(I) in list order, to Ix=1 (step S110).

[0072] After step S110, the first higher-level device determines whether the target device information Pdk(Ix) matches its own device information Pd (step S111).

[0073] If the first higher-level device determines in step S111 that there is a "no match," it can use that determination to conclude that the destination floor registration device 1 identified in the target device information Pdk(Ix) is a registration device other than itself, and therefore should be the first lower-level device. In this case, the first higher-level device selects the car information Pg of the car G to be assigned to the destination floor registration device 1 (first lower-level device) from the operating car information Pgk(J) in order to select the car G to be assigned to the calculation task from among the operating car Gs (step S112).

[0074] As an example of step S112, although not limited to this, the first higher-level device can determine one number Jx from the range of possible list numbers J of the train car information Pgk(J) (1≦J≦M2) using the formula Jx=Ix%M2+1 (where % is the modulo operator), and select the train car information Pgk(Jx) corresponding to that number Jx as the train car information Pg for the train car G to be handled by the first lower-level device.

[0075] This selection method makes it possible to distribute the number of elevator cars G assigned to each first subordinate device equally among all first subordinate devices. Specifically, it becomes possible to allocate the elevator cars G assigned to calculation tasks to the first subordinate devices such that the number of first subordinate devices that calculate the evaluation value Vx(Pg) for the same elevator car G is the same or within ±1 for all elevator cars G in operation.

[0076] Therefore, in elevators where the total number of destination floor registration devices 1 is more than twice the total number of elevator cars G, the first higher-level device can send a request to execute a calculation task targeting that same single elevator car G to two or more first lower-level devices for each elevator car G in operation.

[0077] This makes it possible to obtain the evaluation value Vx(Pg) for the elevator car G that was handled by that first lower-level device from another first lower-level device that is also responsible for the same elevator car G.

[0078] After step S112, the first higher-level device sends a request to execute a calculation task targeting the elevator car G selected in step S112 (the elevator car G identified by the elevator car information Pgk(J=Jx)) to the destination floor registration device 1 (first lower-level device) identified by the target device information Pdk(Ix) (step S113). At this time, the first higher-level device also sends its own device information Pd to the first lower-level device so that the first lower-level device can recognize which destination floor registration device 1 is the source of the execution request. Then, the first higher-level device proceeds to step S114.

[0079] On the other hand, if the first higher-level device determines in step S111 that it "matches (Yes)", it can use that determination to determine that the destination floor registration device 1 identified in the target device information Pdk(Ix) is itself. In this case, the first higher-level device proceeds to step S114 without performing steps S112 and S113.

[0080] In step S114, the first higher-level device increments the value of the variable Ix by one in order to advance the target device information Pdk(Ix) to be judged in step S111 to the next one in the list. Then, in order to determine whether the judgment in step S111 has been made for all of the listed target device information Pdk(I), the first higher-level device determines whether the variable Ix satisfies Ix > M1 (step S115).

[0081] If the first higher-level device determines in step S115 that the condition is "not met (No)", it repeatedly executes the processes in steps S111 to S114 until it can determine in step S115 that the condition is "met (Yes)". As a result, a request to execute the calculation task is sent to all first lower-level devices that are part of the cluster configuration.

[0082] Subsequently, if the first higher-level device determines that the condition is met ("Yes") in step S115, it executes the process from step S120 (see Figure 5). Details of the process from step S120 will be described later.

[0083] [1-2-2] Response processing performed by the first subordinate device (including calculation tasks) Figure 6 is a flowchart showing the response processing performed in this embodiment. This response processing is initiated at each destination floor registration device 1 (first subordinate device) that receives a request to execute a calculation task from the first higher-level device.

[0084] When response processing begins, the first subordinate device determines whether the number of tasks N, which is the number of calculation tasks it is currently executing, has reached the upper limit Nt1 in order to limit the load it places on itself by undertaking calculation tasks (step S200). Here, the upper limit Nt1 is set in advance to limit the number of calculation tasks that can be processed in parallel by a single first subordinate device. This upper limit Nt1 is set to a value of 1 or greater.

[0085] If the first subordinate device determines in step S200 that it has "not reached (No)", it can use that determination to determine that it has the capacity to perform the requested calculation task. In this case, the first subordinate device performs the calculation task in accordance with the received request (step S210). Specifically, the first subordinate device calculates the evaluation value Vx(Pg) for the elevator car G specified in the calculation task execution request.

[0086] By setting an upper limit Nt1 on the number of tasks N of the first subordinate device in this way, the load on the first subordinate device can be limited. Therefore, the first subordinate device can be assigned some of the tasks (calculation tasks) necessary to perform group management control without interfering with its original function (function as a user interface).

[0087] After step S210, the first subordinate device sends the evaluation value Vx(Pg) calculated in step S210 back to the first superior device that requested the calculation task (step S211). At this time, the first subordinate device also sends its own device information Pd to the first superior device so that the first superior device can recognize which destination floor registration device 1 sent the evaluation value Vx(Pg). Then, the first subordinate device terminates the response processing.

[0088] On the other hand, if the first subordinate device determines in step S200 that it has "reached (Yes)", it can determine that it does not have the capacity to perform the requested calculation task. In this case, the first subordinate device does not perform the requested calculation task, but sets the evaluation value Vx(Pg) for the elevator car G specified in the request for the calculation task to Vx(Pg) = -1 to indicate that it was unable to perform the requested calculation task (step S220).

[0089] After step S220, the first subordinate device sends the evaluation value Vx(Pg) set in step S220 back to the first superior device that requested the execution of the calculation task (step S221). At this time, the first subordinate device also sends its own device information Pd to the first superior device so that the first superior device can recognize which destination floor registration device 1 is the source of the evaluation value Vx(Pg). Then, the first subordinate device terminates the response processing.

[0090] [1-2-3] Assigned tasks performed by the first higher-level device (continued) If the first higher-level device determines that the condition is met ("Yes") in step S115 (see Figure 4), it then performs the following process (see Figure 5) to collect evaluation values ​​Vx (Pg=Pgk(J)) for all elevator cars G identified by the elevator car information Pgk(J) from the first lower-level device.

[0091] The first higher-level device first defines an evaluation variable Cv(Pg=Pgk(J)) for each elevator car G identified by the elevator car information Pgk(J), in which the evaluation value Vx(Pg=Pgk(J)) obtained by executing the calculation task is substituted (step S120).

[0092] After step S120, the first higher-level device determines whether or not a new evaluation value Vx(Pg) has been received from any of the first lower-level devices (step S121). If the first higher-level device determines in step S121 that there is "no response (No)", it repeats step S121 until it can determine in step S121 that there is "a response (Yes)".

[0093] Subsequently, if the first higher-level device determines in step S121 that "a reply has been received (Yes)", it sets the car information Pg of the car G that the first lower-level device, which was the source of the reply at that time, was in charge of as the car information Pgs (step S122).

[0094] After step S122, the first higher-level device determines whether the evaluation value Vx(Pgs) is set to Vx(Pgs)=-1 in order to exclude evaluation values ​​Vx(Pgs) that were returned as a result of being unable to perform the calculation task (step S123).

[0095] If the first higher-level device determines in step S123 that it is "not set (No)", it can determine from that determination that the evaluation value Vx(Pgs) was obtained by executing the calculation task. In this case, the first higher-level device determines whether it is necessary to substitute the evaluation value Vx(Pgs) into the evaluation variable Cv(Pg=Pgs) by determining whether another evaluation value Vx has already been substituted into the evaluation variable Cv(Pgs) (step S124).

[0096] If the first higher-level device determines in step S124 that "no value has been assigned", it assigns the evaluation value Vx(Pgs) to the evaluation variable Cv(Pgs) (step S125), and then proceeds to step S126. On the other hand, if the first higher-level device determines in step S124 that "no value has been assigned", it proceeds to step S126 without performing the assignment to the evaluation variable Cv(Pgs) in step S125.

[0097] As a result, the evaluation value Vx(Pg) for each elevator car G is selected from the first lower-level device that responds most quickly, and this value is then substituted into the evaluation variable Cv(Pg).

[0098] In step S126, the first higher-level device determines whether all evaluation values ​​Vx (Pg=Pgk(J)) for the elevator car G in operation (the elevator car G identified by the elevator car information Pgk(J)) have been collected, by determining whether or not the evaluation values ​​Vx have been substituted into all evaluation variables Cv(Pg) for the elevator car G in operation (step S126).

[0099] If the first higher-level device determines in step S126 that "assigned (Yes)", it proceeds to step S130 (selection of candidate car Gk) at that point (i.e., when all evaluation values ​​Vx(Pg) for the operating car G have been collected), even if all evaluation values ​​Vx(Pg) have not yet been received from the first lower-level devices. This type of processing makes it possible to improve the processing speed until the assignment is completed.

[0100] On the other hand, if the first higher-level device determines in step S126 that "no value has been assigned (No)", it proceeds to step S127 to determine whether or not all first lower-level devices have completed sending evaluation values ​​Vx(Pg). In this embodiment, each time the first higher-level device receives an evaluation value Vx(Pg) from a first lower-level device, it uses the device information Pd transmitted from that first lower-level device along with the evaluation value Vx(Pg) to determine which first lower-level device sent the evaluation value Vx(Pg).

[0101] Furthermore, if the first higher-level device determines in step S123 that it is "configured (Yes)", it can determine that the evaluation value Vx(Pgs) was returned as a result of being unable to perform the calculation task. In this case as well, the first higher-level device proceeds to step S127 to determine whether or not it has finished receiving evaluation values ​​Vx(Pg) from all first lower-level devices.

[0102] If the first higher-level device determines in step S127 that the process is "not completed (No)", it returns to step S121 and repeatedly executes steps S121 to S127 until it can determine in step S126 that the value has been substituted (Yes), or until it can determine in step S127 that the process is "completed (Yes)".

[0103] Furthermore, if the first higher-level device determines "Completed (Yes)" in step S127, it can be determined that, based on that determination, all evaluation values ​​Vx(Pg) from the first lower-level devices have been returned without all evaluation values ​​Vx(Pg) for the elevator car G in operation being collected, or in other words, a large number of first lower-level devices were unable to perform the calculation task.

[0104] In this case, the first higher-level device lists all the car information Pg for the cars G to which it could not assign an evaluation value Vx(Pg) to the evaluation variable Cv(Pg) as the operating car information Pgk(J) (step S128). The first higher-level device also assigns the total number of operating car information Pgk(J) (here, the last value of list number J) to the variable M2. Then, the first higher-level device executes the process from step S110 again. As a result, the first lower-level device is again requested to perform the calculation task for the cars G to which it does not yet have an evaluation value Vx(Pg), with the cars G to be assigned to them specified again.

[0105] The first higher-level device then repeatedly executes the process from step S110 via step S128 until it can determine in step S126 that "substitution has been made (Yes)" (i.e., until all evaluation values ​​Vx(Pg) for the elevator car G in operation have been obtained).

[0106] With this processing method, even if the number of users increases and requests for calculation tasks to be executed to the same first subordinate device overlap, and the number of calculation tasks currently running in each first subordinate device (number of tasks N) is likely to reach the upper limit Nt1, it will always be possible to equalize the evaluation value Vx(Pg) for all elevators G.

[0107] If the first higher-level device determines in step S126 that "substitution has been made (Yes)", it evaluates the elevator car G by comparing all values ​​of the evaluation variable Cv(Pg) (evaluation value Vx(Pg)), and selects the elevator car G with the highest evaluation as the candidate elevator car Gk (step S130). For example, if the expected arrival time is used as the evaluation value Vx, the earlier the time indicated by the evaluation value Vx, the higher the evaluation of elevator car G as an assigned destination (higher suitability as an assigned destination). Also, if the expected waiting time is used as the evaluation value Vx, the shorter the time indicated by the evaluation value Vx, the higher the evaluation of elevator car G as an assigned destination (higher suitability as an assigned destination).

[0108] After step S130, the first higher-level device assigns a landing call X to the candidate elevator car Gk selected in step S130 for the user who has registered their destination floor Fd in the first higher-level device (step S131). Then, the first higher-level device displays the assignment information performed in step S131 (such as the elevator car information Pg of the candidate elevator car Gk) on its control unit 10 to guide the user on which elevator car G to board (step S132). After that, the first higher-level device completes the assignment task.

[0109] [1-3] Variant [1-3-1] First variation In the first embodiment described above, when the first higher-level device sends a request to the first lower-level device to execute a calculation task, it may be responsible for executing the calculation task for one of the elevator cars G currently in operation, and may send requests to the first lower-level device to execute calculation tasks for each of the other elevator cars G. In this case, the first higher-level device uses the evaluation value Vx(Pg) it has calculated and the evaluation value Vx(Pg) obtained from the reply from the first lower-level device to select a candidate elevator car Gk.

[0110] Figure 7 is a flowchart showing some of the assigned tasks performed in the first modified example. In this modified example, the first higher-level device is configured to also be responsible for executing calculation tasks among the assigned tasks in Figure 7. On the other hand, in order to limit the load on itself that the first higher-level device would incur by taking on calculation tasks, after step S101, it determines whether the number of tasks N, which is the number of calculation tasks it is currently executing, has reached the upper limit Nt2 (step S300). Here, the upper limit Nt2 is set in advance to limit the number of calculation tasks that the first higher-level device will process in parallel. This upper limit Nt2 is set to a value of 1 or greater.

[0111] If the first higher-level device determines in step S300 that the condition has not been met (No), it can then determine that it has the capacity to perform the calculation task. In this case, the first higher-level device performs the calculation task targeting one of the elevator cars G currently in operation (hereinafter, the elevator car information Pg of this elevator car G will be referred to as Pg=Pgt) (step S301). Specifically, the first higher-level device selects one of the elevator car information Pg recorded in the elevator car management data Dt whose current status Ps associated with that elevator car information Pg is "in operation," and then performs the calculation task targeting the elevator car G identified by that elevator car information Pg (=Pgt).

[0112] After step S301, the first higher-level device defines an evaluation variable Cv(Pg=Pgt) to which the evaluation value Vx(Pg=Pgt) obtained by executing the calculation task in step S301 is to be substituted (step S302), and then substitutes the evaluation value Vx(Pgt) into the evaluation variable Cv(Pgt) (step S303).

[0113] After step S303, the first higher-level device, in order to identify the elevator cars G in operation other than the elevator car G (car information Pg=Pgt) that it was responsible for in step S301 (calculation task), lists the elevator car information Pg recorded in the elevator car management data Dt that has a current state Ps associated with the elevator car information Pg in question and is not Pg=Pgt, as operating elevator car information Pgk(J) (step S304). Here, the list number J starts from 1. The first higher-level device then assigns the total number of operating elevator car information Pgk(J) (here, the last value of list number J) to the variable M2. After that, the first higher-level device executes the process from step S110.

[0114] On the other hand, if the first higher-level device determines in step S300 that the target has been reached (Yes), it can determine that it does not have the capacity to perform the calculation task itself. In this case, the first higher-level device will not perform the calculation task itself, but will instead have another destination floor registration device 1 (first lower-level device) perform the calculation task, and will proceed with the processing from step S102.

[0115] According to the first modification, the first higher-level device can perform calculation tasks together with the first lower-level device. This makes it possible to efficiently distribute the calculation tasks to all destination floor registration devices 1 that constitute cluster Q.

[0116] [1-3-2] Second variation In the first embodiment described above, when the first subordinate device receives a request to execute a calculation task, if at that time the user is operating to register the destination floor Fd on the first subordinate device, it may set the evaluation value Vx(Pg) for the elevator car G specified in the request to execute the calculation task to Vx(Pg)=-1 to indicate that it was not possible to execute the requested calculation task, without executing the requested calculation task.

[0117] Figure 8 is a flowchart showing the response processing (including the calculation task) performed in the second modified example. In this modified example, when the response processing starts, the first subordinate device determines whether the user is currently in the process of registering the destination floor Fd (step S310).

[0118] If the first subordinate device determines in step S310 that it is "not in operation (No)", it executes the process from step S200 as described in the first embodiment (see Figure 6). On the other hand, if the first subordinate device determines in step S310 that it is "in operation (Yes)", it proceeds to step S220 without making the determination in step S200.

[0119] According to the second modification, the first subordinate device can be assigned to perform a portion of the tasks necessary for group management control (calculation tasks) only when it is not under load (i.e., when a user is not performing a registration operation on that device), while still prioritizing its original function as a user interface.

[0120] [1-3-3] Third variation In the first embodiment described above, the more destination floor registration devices 1 that the elevator is equipped with, the more destination floor registration devices 1 among the first subordinate devices will perform calculation tasks targeting the same single elevator car G. As a result, the number of evaluation values ​​Vx(Pg) that are calculated but not adopted and are wasted (i.e., the number of wasted calculation tasks) will also increase.

[0121] Therefore, in order to reduce such waste as much as possible, the destination floor registration devices 1 may be divided into two or more groups in advance, and within each group, the destination floor registration devices 1 that are operating normally within that group may form a single cluster Q and perform group management control.

[0122] [1-3-4] Fourth variation In the first embodiment described above, when the first higher-level device sends a request to the first lower-level device to execute a calculation task, it may select a number of destination floor registration devices 1 equal to or greater than the number of elevator cars G in operation as the first lower-level device each time, and perform group management control by forming a single cluster Q together with these destination floor registration devices 1. In this case, as a method for selecting the first lower-level devices, the first higher-level device may randomly select the first lower-level devices.

[0123] Alternatively, the first higher-level device may obtain the registration frequency (the number of times a destination floor Fd was registered) from all destination floor registration devices 1 within the most recent predetermined period (e.g., one month), and select the necessary number of destination floor registration devices 1 as first lower-level devices, starting with the one with the lowest registration frequency. This selection method allows the processing capacity of the destination floor registration devices 1 to be effectively utilized for the first lower-level devices without interfering with their original functions (as a user interface) as much as possible.

[0124] [2] Second embodiment [2-1] Overall configuration of the elevator Figure 9 is a conceptual diagram showing the overall configuration of an elevator according to the second embodiment. This elevator, like the first embodiment, is equipped with multiple destination floor registration devices 1, multiple elevator cars G, and multiple elevator control devices 2.

[0125] On the other hand, in this embodiment, one of the multiple destination floor registration devices 1 is pre-selected as the registration device responsible for the first higher-level device. In addition, one or more destination floor registration devices 1 other than the first higher-level device are pre-selected as registration devices responsible for the first lower-level devices. Specifically, the same number of destination floor registration devices 1 as the number of elevator cars G equipped in the elevator are pre-selected as the first lower-level devices. Furthermore, for each first lower-level device, the elevator cars G that it will be responsible for calculating tasks are predetermined.

[0126] As a method for selecting the first higher-level device and the first lower-level device, these devices can be selected from all destination floor registration devices 1 in order from the one with the lowest registration frequency (number of times used to register destination floor Fd) within the most recent predetermined period (e.g., one month). With this selection method, the processing capacity of the destination floor registration device 1 can be effectively utilized for the first higher-level device and the first lower-level device (i.e., for the first cluster Q1) without interfering with the original function of the destination floor registration device 1 (its function as a user interface) as much as possible.

[0127] These destination floor registration devices 1 (first upper-level device and first lower-level device) constitute a cluster Q for group management control (hereinafter, this cluster Q will be referred to as "first cluster Q1").

[0128] Furthermore, a second cluster Q2 is configured by two or more destination floor registration devices 1 (two or more destination floor registration devices 1 outside the first cluster Q1) other than the destination floor registration device 1 that constitutes the first cluster Q1. This second cluster Q2 is a backup cluster Q that performs group management control in place of the first cluster Q1 if the first cluster Q1 becomes unable to operate normally.

[0129] Specifically, one destination floor registration device 1 outside the first cluster Q1 is pre-selected as a second-higher device responsible for executing the assigned task during backup. In addition, one or more destination floor registration devices 1 outside the first cluster Q1 and other than the aforementioned second-higher device are pre-selected as second-lower devices responsible for executing the calculation task during backup. In this embodiment, the same number of destination floor registration devices 1 as the number of elevator cars G are pre-selected as second-lower devices. Furthermore, for each second-lower device, the elevator cars G that it will be responsible for calculating are predetermined.

[0130] As a method for selecting the second higher-level device and the second lower-level device, these devices can be selected from among all destination floor registration devices 1, excluding those selected as the first higher-level device or first lower-level device, in order from those with the lowest registration frequency within the most recent predetermined period (e.g., one month). With this selection method, the processing capacity of the destination floor registration device 1 can be effectively utilized for the second higher-level device and the second lower-level device (i.e., for the second cluster Q2) without interfering with the original function of the destination floor registration device 1 (its function as a user interface) as much as possible.

[0131] These destination floor registration devices 1 (second upper-level device and second lower-level device) then constitute the second cluster Q2 (backup cluster Q).

[0132] This allows two or more destination floor registration devices 1 to share and perform multiple tasks (tasks for group management control) necessary for group management control, even during backup. Specifically, even during backup, multiple tasks (tasks for group management control) necessary for group management control are distributed among two or more destination floor registration devices 1, and each destination floor registration device 1 executes the task assigned to it, so that these two or more destination floor registration devices 1 can function as a single cluster Q and perform group management control. This will be explained in detail below.

[0133] Figure 10(A) is a block diagram showing the configurations applied to the first and second higher-level devices in this embodiment. As shown in this figure, the destination floor registration device 1 selected as the first or second higher-level device is configured to be capable of executing only the assignment task among the group management control tasks. For this reason, in the destination floor registration device 1, it is sufficient that the information necessary for operation as a user interface and the information necessary for executing the assignment task (device management data Dr and cage management data Dt) are stored in the storage unit 11, and the information necessary for executing the learning task and calculation task (learning data Dp) does not need to be stored in the storage unit 11.

[0134] Figure 10(B) is a conceptual diagram illustrating the device management data Dr used in this embodiment. In this device management data Dr, for each destination floor registration device 1, in addition to the device information Pd and installation floor Fs of the destination floor registration device 1, attribute information Pt of the destination floor registration device 1 is further associated. Here, attribute information Pt indicates which destination floor registration devices 1 constitute the first cluster Q1 and the second cluster Q2, respectively. In other words, the attribute information Pt of each destination floor registration device 1 indicates which cluster Q it constitutes, if that destination floor registration device 1 is a registration device that constitutes either the first cluster Q1 or the second cluster Q2. The example in Figure 10(B) shows a case where "Q1" is recorded in the attribute information Pt of the destination floor registration device 1 (the destination floor registration device 1 selected as the first higher-level device or the first lower-level device) that constitutes the first cluster Q1, and "Q2" is recorded in the attribute information Pt of the destination floor registration device 1 (the destination floor registration device 1 selected as the second higher-level device or the second lower-level device) that constitutes the second cluster Q2.

[0135] Figure 11 is a block diagram showing the configurations applicable to the first and second subordinate devices, respectively. As shown in this figure, the destination floor registration device 1 selected as the first or second subordinate device is configured to be capable of executing only the calculation task and the learning task among the group management control tasks. For this reason, in the destination floor registration device 1, it is sufficient that the information necessary for operation as a user interface and the information necessary for executing the calculation task and the learning task (learning data Dp) are stored in the storage unit 11, while the information necessary for executing the assignment task (device management data Dr and cage management data Dt) does not need to be stored in the storage unit 11.

[0136] In this embodiment, each time a user registers a destination floor Fd using one of the multiple destination floor registration devices 1 (including registration devices in the first cluster Q1 and registration devices in the second cluster Q2) provided by the elevator, that destination floor registration device 1 transmits the registered destination floor Fd to the destination floor registration device 1 (normally the first higher-level device, or the second higher-level device in backup mode) that is currently responsible for the assignment task, unless it is currently acting as a higher-level device (normally the first higher-level device, or the second higher-level device in backup mode). This sends a request to the first or second higher-level device that is currently responsible for the assignment task for that user to assign a landing call X. At this time, in order to allow the higher-level device (here, the first or second higher-level device) to recognize which destination floor registration device 1 was operated, the device information Pd of that destination floor registration device 1 is also transmitted to the higher-level device.

[0137] When the higher-level device receives an assignment request from another destination floor registration device 1, it refers to the device management data Dr to identify the destination floor registration device 1 that sent the assignment request from the device information Pd received at that time, and also identifies the installation floor Fs of that registration device. On the other hand, when a destination floor Fd is registered by the higher-level device, the higher-level device refers to the device management data Dr to identify its own installation floor Fs from its own device information Pd. In either case, the installation floor Fs identified by the higher-level device is used as the departure floor Fc of the user who registered the destination floor Fd.

[0138] Here, the first higher-level device periodically distributes an assignment signal Sy, indicating that it is responsible for executing an assigned task, to all destination floor registration devices 1 other than itself, in addition to the alive status signal Sx, provided that it and all first lower-level devices are operating normally. Specifically, the first higher-level device distributes the assignment signal Sy to all destination floor registration devices 1 other than itself when it is operating normally and has received the alive status signal Sx from all first lower-level devices in the first cluster Q1 (i.e., when it has confirmed that all first lower-level devices are operating normally).

[0139] On the other hand, if either of the first subordinate devices fails to operate normally, the first higher-level device stops executing the assignment task and also stops distributing its own assignment signal Sy.

[0140] As a result, destination floor registration devices 1 other than the first higher-level device will be able to recognize that the destination of the platform call X assignment request is the first higher-level device, upon receiving the assignment signal Sy from the first higher-level device on a regular basis. Furthermore, if the first cluster Q1 becomes unable to perform group management control, the interruption of the distribution of the assignment signal Sy from the first higher-level device will ensure that the second higher-level device recognizes that a replacement (backup) for the first cluster Q1 is needed.

[0141] If the second higher-level device is able to receive the assignment signal Sy from the first higher-level device, it will not distribute the assignment signal Sy itself, but will instead distribute only the alive status signal Sx to other destination floor registration devices 1. If the second higher-level device is unable to receive the assignment signal Sy from the first higher-level device (i.e., the distribution of the assignment signal Sy from the first higher-level device is interrupted), it will start executing the assignment task on behalf of the first higher-level device and will also start distributing the assignment signal Sy to other destination floor registration devices 1 (backup processing).

[0142] As a result, destination floor registration devices 1 other than the second higher-level device will no longer be able to receive the assignment signal Sy from the first higher-level device, while if they begin to receive the assignment signal Sy from the second higher-level device, they will be able to recognize that the destination of the platform call X assignment request has changed from the first higher-level device to the second higher-level device.

[0143] Thus, in this embodiment, if the first cluster Q1 becomes unable to perform group management control, the control entity for group management can be smoothly transferred from the first higher-level device (first cluster Q1) to the second higher-level device (second cluster Q2). Furthermore, each destination floor registration device 1 can accurately recognize which of the first and second higher-level devices is currently in charge of the assignment task (i.e., to which device the assignment request for the landing call X should be sent).

[0144] When the first higher-level device is distributing the assignment signal Sy, and a destination floor Fd is registered at that first higher-level device, or when it receives an assignment request for a landing call X from another destination floor registration device 1, it will always execute the assignment task at that first higher-level device, even if the user is in the process of registering the destination floor Fd.

[0145] Specifically, the first higher-level device requests all first lower-level devices within the first cluster Q1 to perform their respective calculation tasks by transmitting information about the landing call X (the user's departure floor Fc and destination floor Fd), which is the target of the assigned task (the target of the assignment). (Sending a request to the first lower-level devices to perform the calculation task.)

[0146] When each first subordinate device receives a request to execute a calculation task from the first superior device, it will always execute the calculation task it is responsible for, even if a user is in the process of registering the destination floor Fd on that first subordinate device. Specifically, each first subordinate device calculates an evaluation value Vx(Pg) for the elevator car G it is responsible for and sends that evaluation value Vx(Pg) back to the first superior device.

[0147] Subsequently, the first higher-level device selects a candidate elevator car Gk using the evaluation value Vx(Pg) obtained from the first lower-level device's response, and then assigns a landing call X for the user to that candidate elevator car Gk.

[0148] On the other hand, if the first higher-level device is operating normally (and is able to distribute the "alive status signal Sx") but has stopped distributing its own assignment signal Sy because one of the first lower-level devices in the first cluster Q1 has stopped operating normally, then when a user registers their destination floor Fd, the first higher-level device will send a request to the second higher-level device to assign a landing call X for that user.

[0149] When the second higher-level device is distributing its own assignment signal Sy (i.e., during backup), if the destination floor Fd is registered by the second higher-level device, or if it receives an assignment request for a landing call X from another destination floor registration device 1, the second higher-level device will always execute the assignment task, even if the user is in the process of registering the destination floor Fd.

[0150] Specifically, the second-higher device requests all second-lower devices within the second cluster Q2 to perform their respective calculation tasks by transmitting information about the landing call X (the user's departure floor Fc and destination floor Fd), which is the target of the assigned task (the target of the assignment).

[0151] When each second-tier subordinate device receives a request to execute a calculation task from the second-tier superior device, it will always execute the calculation task it is responsible for, even if a user is in the process of registering the destination floor Fd on that second-tier subordinate device. Specifically, each second-tier subordinate device calculates an evaluation value Vx(Pg) for the elevator car G it is responsible for and sends that evaluation value Vx(Pg) back to the second-tier superior device.

[0152] Subsequently, the second higher-level device selects a candidate elevator car Gk using the evaluation value Vx(Pg) obtained from the second lower-level device's response, and then assigns a landing call X for the user to that candidate elevator car Gk.

[0153] On the other hand, if the second higher-level device is operating normally (and is able to distribute the "alive status signal Sx") but has stopped distributing its own "assignment signal Sy" because it has received the "assignment signal Sy" from the first higher-level device, then when a user registers their destination floor Fd, the second higher-level device will send a request to the first higher-level device to assign a landing call X for that user.

[0154] With this control system, even if the first cluster Q1 fails to operate normally, the second cluster Q2 can take its place (back up). Therefore, all group management control, including backup control, can be performed by the destination floor registration device 1 alone.

[0155] [2-2] Control processing performed by the destination floor registration device [2-2-1] Assigned tasks performed by the higher-level device Figure 12 is a flowchart showing the assignment task performed in this embodiment. This assignment task is initiated by the higher-level device (the first higher-level device under normal circumstances, and the second higher-level device under backup conditions) when the destination floor Fd is registered, or when the higher-level device receives an assignment request for a landing call X from another destination floor registration device 1.

[0156] When an assignment task is initiated, the higher-level device first assigns its own attribute information Pt to the variable Kx (step S401). Specifically, the higher-level device identifies its own attribute information Pt from its own device information Pd by referring to the device management data Dr (Figure 10(B)), and assigns that attribute information Pt to the variable Kx. This identifies whether the group management control including the assignment task is being performed in the first cluster Q1 or the second cluster Q2 at that time.

[0157] Next, the higher-level device identifies a lower-level device within the same cluster Q as itself (the first lower-level device under normal circumstances, and the second lower-level device during backup) (step S402). In other words, the higher-level device identifies the destination floor registration device 1, which, together with itself, forms a single cluster Q (the first cluster Q1 under normal circumstances, and the second cluster Q2 during backup) and is responsible for performing group management control. Specifically, the higher-level device extracts from the device information Pd recorded in the device management data Dr the attribute information Pt associated with the device information Pd that matches the information in the variable Kx (the attribute information Pt assigned to the variable Kx in step S401).

[0158] After step S402, the higher-level device sends information about the landing call X (the user's departure floor Fc and destination floor Fd), which is the subject of the assigned task (the subject of the assignment), to all lower-level devices identified in step S402, requesting each of them to perform the calculation task they are responsible for (sending a request to perform the calculation task to the lower-level devices).

[0159] When a subordinate device receives a request from a higher-level device to execute a calculation task, it will always execute the calculation task it is responsible for, even if a user is in the process of registering the destination floor Fd on that subordinate device. Specifically, each subordinate device calculates an evaluation value Vx(Pg) for the elevator car G it is responsible for and sends this evaluation value Vx(Pg) back to the higher-level device.

[0160] Subsequently, the higher-level device selects a candidate elevator car Gk using the evaluation value Vx(Pg) obtained from the lower-level device's response, and then assigns a landing call X for the user to that candidate elevator car Gk (steps S404-S406).

[0161] Specifically, after step S403, the higher-level device determines whether or not it has completed receiving evaluation value Vx(Pg) responses from all lower-level devices (step S404). The higher-level device then repeatedly executes step S404 until it can determine that it is "completed (Yes)" in step S404.

[0162] If the higher-level device determines that the process is "completed (Yes)" in step S404, it evaluates the elevator car G by comparing all evaluation values ​​Vx(Pg) obtained from the lower-level device, and selects the elevator car G with the highest evaluation as the candidate car Gk (step S405).

[0163] After step S405, the higher-level device assigns a landing call X for the user in question to the candidate elevator car Gk selected in step S405 (step S406). Then, the higher-level device displays the assignment information from step S406 (such as the elevator car information Pg of the candidate elevator car Gk) on the operation unit 10 of the destination floor registration device 1 where the user registered their destination floor Fd, thereby guiding the user on which elevator car G to board (step S407). After that, the higher-level device completes the assignment task.

[0164] [2-2-2] Backup processing performed by the second higher-level device Figure 13 is a flowchart showing the backup process performed in this embodiment. In this backup process, the second higher-level device first determines whether or not the distribution of the assignment signal Sy from the first higher-level device has been interrupted in order to determine whether or not a backup of the group management control (replacement for the first cluster Q1) is necessary (step S501).

[0165] If the second higher-level device determines in step S501 that the connection is "not interrupted (No)", it monitors the status of the first cluster Q1 by repeatedly executing step S501. If the second higher-level device determines in step S501 that the connection is "interrupted (Yes)", it starts executing the assignment task on behalf of the first higher-level device and starts distributing the assignment signal Sy to destination floor registration devices 1 other than itself (step S502).

[0166] As a result, destination floor registration devices 1 other than the second higher-level device will recognize that the destination for the boarding call X assignment request has been changed to the second higher-level device. Consequently, if a user registers a destination floor Fd at any destination floor registration device 1 other than the second higher-level device, that destination floor registration device 1 will transmit the registered destination floor Fd to the second higher-level device.

[0167] Subsequently, if the first cluster Q1 becomes capable of performing group management control due to maintenance or other reasons, the distribution of the assignment signal Sy from the first higher-level device resumes, and the second higher-level device becomes able to receive the assignment signal Sy from the first higher-level device again. Therefore, after step S502, the second higher-level device determines whether or not the distribution of the assignment signal Sy from the first higher-level device has resumed (step S503). If it determines in step S503 that it has resumed (Yes), it stops executing the assignment task and stops distributing its own assignment signal Sy (step S504).

[0168] As a result, destination floor registration devices 1 other than the first higher-level device will once again receive the assignment signal Sy from the first higher-level device, and upon receiving this signal, they will recognize that the destination of the assignment request for the landing call X has returned to the first higher-level device.

[0169] After step S504, the second higher-level device repeatedly performs the backup process described above, as long as it is operating normally.

[0170] [2-3] Variations [2-3-1] Fifth variation <Configuration of the higher-level equipment> In the second embodiment described above, instead of the higher-level device responsible for executing the assigned task (the first higher-level device under normal circumstances, and the second higher-level device under backup conditions) distributing the assignment responsibility signal Sy, the alive status signal Sx distributed by each of the first and second higher-level devices may include assignment responsibility information Py indicating whether the higher-level device is currently responsible for executing the assigned task or not. Specifically, this is as follows.

[0171] The first higher-level device, when it and all first lower-level devices are operating normally, distributes its own alive status signal Sx with the assignment information Py within the signal set to the "in charge" state (Py = "in charge"). More specifically, the first higher-level device sets the assignment information Py within its own alive status signal Sx to the "in charge" state (Py = "in charge") when it is operating normally and has received the alive status signal Sx from all first lower-level devices in the first cluster Q1 (i.e., when it has confirmed that all first lower-level devices are operating normally).

[0172] On the other hand, if either of the first lower-level devices fails to operate normally, the first higher-level device stops executing the assigned task and changes the assignment information Py in its own alive status signal Sx to an unassigned state (Py = "unassigned").

[0173] As a result, when a destination floor registration device 1 other than the first higher-level device periodically receives an Alive status signal Sx from the first higher-level device, if the assignment information Py in that signal is in an "assigned" state (Py = "assigned"), it will be able to recognize that the destination of the landing call X assignment request is the first higher-level device. Furthermore, if the first cluster Q1 becomes unable to perform group management control, the assignment information Py in the Alive status signal Sx of the first higher-level device will be changed to an "unassigned" state (Py = "unassigned"), thereby allowing the second higher-level device to reliably recognize, using the Alive status signal Sx, that a replacement (backup) for the first cluster Q1 is needed.

[0174] The second higher-level device, if the assignment information Py in the alive status signal Sx received from the first higher-level device is in an "assigned" state (Py = "assigned"), sends its own alive status signal Sx with the assignment information Py in that signal in an "unassigned" state (Py = "unassigned"). Then, if the second higher-level device can no longer receive the alive status signal Sx from the first higher-level device, or if the assignment information Py in the alive status signal Sx received from the first higher-level device becomes "unassigned" (Py = "unassigned"), it starts executing the assignment task on behalf of the first higher-level device and changes the assignment information Py in its own alive status signal Sx to an "assigned" state (Py = "assigned") (backup process).

[0175] As a result, destination floor registration devices 1 other than the second higher-level device will be able to recognize that the destination of the platform call X assignment request has changed from the first higher-level device to the second higher-level device when the assignment information Py in the alive status signal Sx received from the first higher-level device changes to an unassigned state (Py = "unassigned"), while the assignment information Py in the alive status signal Sx received from the second higher-level device changes to an assigned state (Py = "assigned").

[0176] Thus, in this modified version as well, if the first cluster Q1 becomes unable to perform group management control, the control entity for group management can be smoothly transferred from the first higher-level device (first cluster Q1) to the second higher-level device (second cluster Q2). Furthermore, according to this modified version, the destination floor registration device 1 can be accurately recognized by using the alive status signal Sx as to which of the first and second higher-level devices is currently in charge of the assignment task (i.e., to which device the assignment request for the landing call X should be sent).

[0177] <Backup processing performed by the second-higher device> Figure 14 is a flowchart showing the backup process performed in this modified example. In this backup process, the second higher-level device first determines whether a backup of the group management control (a replacement for the first cluster Q1) is needed by checking whether the distribution of the alive status signal Sx from the first higher-level device has been interrupted (step S511). If it is determined in step S511 that the distribution has not been interrupted (No), it further determines whether the assignment information Py in the alive status signal Sx received from the first higher-level device has been changed to an unassigned state (Py = "unassigned") (step S512).

[0178] If the second higher-level device determines in step S512 that the status is "not changed (No)", it repeatedly executes steps S511 and S512 until it determines in step S511 that the status is "disconnected (Yes)" or in step S512 that the status is "changed (Yes)". In this way, the second higher-level device monitors the status of the first cluster Q1. Then, if the second higher-level device determines in step S511 that the status is "disconnected (Yes)" or in step S512 that the status is "changed (Yes)", it starts executing the assignment task on behalf of the first higher-level device and changes the assignment responsibility information Py in its own alive status signal Sx to the "responsible" state (Py = "responsible") (step S513).

[0179] As a result, destination floor registration devices 1 other than the second higher-level device will recognize that the destination for the boarding call X assignment request has been changed to the second higher-level device. Consequently, if a user registers a destination floor Fd at any destination floor registration device 1 other than the second higher-level device, that destination floor registration device 1 will transmit the registered destination floor Fd to the second higher-level device.

[0180] Subsequently, if the first cluster Q1 becomes capable of performing group management control due to maintenance or other reasons, the first higher-level device will once again distribute its own alive status signal Sx with the assignment information Py within the signal set to the "assigned" state (Py = "assigned"), thereby enabling the second higher-level device to recognize that the first cluster Q1 is once again capable of performing group management control. Therefore, after step S513, the second higher-level device will determine whether the assignment information Py within the alive status signal Sx received from the first higher-level device has returned to the "assigned" state (Py = "assigned") (step S514). If it is determined in step S514 that it has returned (Yes), it will stop executing the assignment task and return the assignment information Py within its own alive status signal Sx to the "not assigned" state (Py = "not assigned") (step S515).

[0181] As a result, destination floor registration devices 1 other than the first higher-level device will recognize that the destination of the landing call X assignment request has been returned to the first higher-level device.

[0182] After step S515, the second higher-level device repeatedly performs the backup process described above, as long as it is operating normally.

[0183] [2-3-2] Sixth Variation Figure 15 is a conceptual diagram showing the overall configuration of the elevator according to the sixth modified example. In both the second embodiment and the fifth modified example described above, as shown in Figure 15, the second upper-level device and the second lower-level device may be selected individually as devices to replace the first upper-level device and the first lower-level device, respectively, instead of being selected as devices for constructing the second cluster Q2 (backup cluster Q).

[0184] Specifically, the second higher-level device is selected to take over the execution of assigned tasks from the first higher-level device if the first higher-level device fails to operate normally (a backup device for the first higher-level device). Similarly, the second lower-level device is selected to take over the execution of calculation tasks from the first lower-level device if the first lower-level device fails to operate normally (a backup device for the first lower-level device). More specifically, for each elevator car G, the second lower-level device is selected as a backup device for the first lower-level device that is responsible for the calculation tasks of that elevator car G.

[0185] According to this modified version, even if the first cluster Q1 fails to operate normally, only the destination floor registration device 1 that has failed to operate normally within the first cluster Q1 can be replaced (backed up) by another destination floor registration device 1. Therefore, in this modified version as well, all group management control, including control during backup, can be performed by the destination floor registration device 1 alone.

[0186] [2-3-3] Seventh variation In both the second embodiment and the fifth modification described above, the second cluster Q2 is not limited to one, but multiple clusters Q may be constructed as backup clusters Q. Such a configuration enhances the robustness of the backup function.

[0187] [2-3-3] Variation 8 In all of the second embodiment and the fifth to seventh modifications described above, a single cluster Q may consist of a higher-level device that performs assignment tasks, a lower-level device that performs only computation tasks without performing learning tasks, and a lower-level device that performs only learning tasks without performing computation tasks. In this case, the lower-level device that performs only computation tasks will obtain the necessary information from the lower-level device that performs only learning tasks and then perform the computation tasks.

[0188] [3] Third embodiment [3-1] Overall configuration of the elevator Figure 16 is a conceptual diagram showing the overall configuration of an elevator according to the third embodiment. As shown in Figure 16, the elevator of this embodiment is equipped with a group control device 3, which performs all group control tasks, separately from the destination floor registration device 1. This group control device 3 is connected to the destination floor registration device 1 and the elevator control device 2 via a network W. Furthermore, when the group control device 3 is operating normally, it periodically distributes an "alive status signal Sx" to other devices (including the destination floor registration device 1 and the elevator control device 2) to indicate that it is operating normally.

[0189] In this embodiment, if the group control device 3 becomes unable to operate normally, two or more destination floor registration devices 1, which are some or all of the multiple destination floor registration devices 1 provided by the elevator, will share the task of group control in place of the group control device 3.

[0190] Specifically, as a backup cluster Q that performs group management control in place of the group management control device 3, a cluster Q similar to the second cluster Q2 described in the second embodiment (in this embodiment, this cluster Q is called "first cluster Q1," and the higher-level and lower-level devices within that cluster Q (corresponding to the second higher-level and second lower-level devices) are called "first higher-level device" and "first lower-level device," respectively) is constructed by two or more destination floor registration devices 1 of the destination floor registration devices 1 provided in the elevator of this embodiment.

[0191] Then, when the first higher-level device in the first cluster Q1 detects that the distribution of the alive status signal Sx from the group management control device 3 has been interrupted, it starts executing the assignment task on behalf of the group management control device 3 and also starts distributing the assignment responsibility signal Sy to destination floor registration devices 1 other than itself (backup processing). At this time, the first higher-level device may change the assignment responsibility information Py in its own alive status signal Sx to the "assigned" state (Py = "assigned").

[0192] As a result, destination floor registration devices 1 other than the first higher-level device will no longer be able to receive the Alive status signal Sx from the group control device 3, but will be able to recognize that the destination of the platform call X assignment request has changed from the group control device 3 to the first higher-level device if they start receiving the assignment signal Sy from the first higher-level device, or if the assignment information Py in the Alive status signal Sx received from the first higher-level device changes to the "currently assigned" state (Py = "currently assigned").

[0193] According to this embodiment, if the group control device 3 fails to operate normally, a cluster Q for group control can be formed using two or more destination floor registration devices 1, and this cluster Q can take over (back up) the group control device 3. In other words, the processing capacity of the destination floor registration devices 1 can be effectively utilized to continue elevator operation.

[0194] [3-2] Variations [3-2-1] Variation 9 In the third embodiment described above, the first cluster Q1 may contain multiple first subordinate devices, each responsible for the calculation task for the same single elevator car G. In this case, after the first higher-level device sends a request to execute the calculation task to the first subordinate devices in the first cluster Q1, it can adopt the evaluation value Vx(Pg) for each elevator car G that is returned most quickly from the first subordinate device.

[0195] According to this modified version, even if any of the first lower-level devices fail to operate normally, the evaluation value Vx(Pg) for the elevator car G that that first lower-level device was responsible for can be obtained from another first lower-level device that is responsible for the same elevator car G.

[0196] [3-2-2] 10th Variation In the ninth modified example described above, one or more destination floor registration devices 1 (one or more destination floor registration devices 1 outside the first cluster Q1) that are separate from the destination floor registration devices 1 that constitute the first cluster Q1 may be selected as backup devices to take over the execution of assignment tasks from the first higher-level device when the first higher-level device becomes unable to operate normally. With such a configuration, the robustness of the backup function is enhanced.

[0197] The above-described embodiments and modifications should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, rather than by the above-described embodiments and modifications. Furthermore, the scope of the present invention is intended to include all modifications within the meaning and scope equivalent to the claims.

[0198] From the embodiments and modifications described above, the subject matter of the invention is not limited to a control system that constitutes cluster Q with multiple destination floor registration devices 1, but may also be extracted individually from control processes (including control methods corresponding to said control processes) or programs executed in said control system. Furthermore, the subject matter of the invention may also be extracted from part or all of the elevator described above. [Explanation of Symbols]

[0199] 1. Destination Floor Registration Device 2. Elevator control device 3. Group Control System G Car I, J List Number N Number of tasks Q cluster W Network X boarding area call 10 Control section 11 Storage section 12 Control Unit Cv evaluation variable Dp training data Dr. Device Management Data Dt Basket Management Data FC Departure Floor Fd Destination Floor Fs installation floor GK candidate basket Ix, Kx variables Jx number M1, M2 variables Pd device information Pg Shopping Cart Information Ps Current Status Pt attribute information Py Assignment Information Q1 First Cluster Q2 Second Cluster Sx Alive status signal Sy Assignment Responsibility Signal Vx evaluation value Nt1, Nt2 upper limit PDK Target Device Information PGK Bus Information Pgs Featured Cart Information

Claims

1. An elevator control system comprising multiple elevator cars and multiple destination floor registration devices, wherein two or more destination floor registration devices, which are part or all of the multiple destination floor registration devices, share and perform multiple tasks for carrying out group control management for the multiple elevator cars.

2. The aforementioned multiple tasks include: When a user registers a destination floor using any of the aforementioned destination floor registration devices, a calculation task is performed to calculate an evaluation value for each elevator car, assuming that a platform call for that user has been assigned to that elevator car. When a user registers a destination floor using any of the aforementioned multiple destination floor registration devices, an assignment task is performed to select a candidate car from among the multiple cars as the destination for the user's landing call, based on the evaluation value obtained for each car through the execution of the calculation task, and then assign the user's landing call to that candidate car. It includes, One of the destination floor registration devices described above acts as the first higher-level device and is responsible for executing the assignment task. The elevator control system according to claim 1, wherein one or more destination floor registration devices among the plurality of destination floor registration devices, other than the first higher-level device, are responsible for executing the calculation task as the first lower-level device.

3. In the assignment task, the first higher-level device sends a request to the first lower-level device to execute the calculation task when a user registers a destination floor using any of the multiple destination floor registration devices, and then uses the evaluation value obtained by executing the calculation task to select the candidate elevator car, as described in claim 2.

4. The elevator control system according to claim 3, wherein each time a user registers a destination floor using one of the destination floor registration devices mentioned above, that destination floor registration device executes the assignment task as the first higher-level device.

5. The elevator control system according to claim 4, wherein when the first higher-level device transmits a request to execute the calculation task to the first lower-level device, it transmits a request to execute the calculation task for the same single elevator car to two or more first lower-level devices for each elevator car.

6. The elevator control system according to claim 5, wherein the first higher-level device transmits a request to the first lower-level device to execute the calculation task, then adopts the evaluation value that is returned from the first lower-level device as the evaluation value for each elevator car, and when all the evaluation values ​​for the elevator cars targeted in the calculation task among the plurality of elevator cars have been collected, the selection of the candidate elevator car is performed.

7. In the first subordinate device, an upper limit is set on the number of calculation tasks that can be processed in parallel individually. The elevator control system according to any one of claims 4 to 6, wherein each of the first subordinate devices, upon receiving the execution request, determines whether the number of calculation tasks it is currently executing has reached the upper limit, and if it determines that it has not reached the upper limit, executes the calculation task corresponding to the request.

8. The elevator control system according to claim 7, wherein the first higher-level device, after sending a request to the first lower-level device to execute the calculation task, receives the evaluation values ​​back from the first lower-level device, and if not all evaluation values ​​have been obtained for all of the elevator cars targeted in the calculation task among the plurality of elevator cars, then sends another request to the first lower-level device to execute the calculation task, targeting the elevator cars for which evaluation values ​​have not yet been obtained.

9. The elevator control system according to any one of claims 4 to 6, wherein when the first higher-level device transmits a request to the first lower-level device to execute the calculation task, it is responsible for executing the calculation task for one of the plurality of elevator cars, and for the other elevator cars, it sends a request to the first lower-level device to execute the calculation task for each of the other elevator cars.

10. A cluster for group management control, consisting of two or more destination floor registration devices, comprises a first cluster including the first higher-level device and the first lower-level device, and a second cluster separate from the first cluster, The aforementioned second cluster is, Any one destination floor registration device outside the first cluster and a second higher-level device responsible for executing the assignment task, A second subordinate device which is outside the first cluster and is a destination floor registration device other than the second higher-level device and is responsible for executing the calculation task, Includes, The elevator control system according to claim 2, wherein if any destination floor registration device in the first cluster fails to operate normally, the second upper-level device and the second lower-level device in the second cluster share the task of performing the group management control in place of the first cluster.

11. A cluster for group management control consisting of two or more destination floor registration devices includes a first cluster which includes the first higher-level device and the first lower-level device. The destination floor registration device outside the first cluster includes: If the first higher-level device becomes unable to operate normally, a second higher-level device will take over the execution of the assigned task from the first higher-level device, A second subordinate device which takes over the execution of the calculation task when the first subordinate device fails to operate normally, The elevator control system according to claim 2, which includes the following:

12. The first higher-level device, when both itself and the first lower-level device are operating normally, distributes an assignment signal to destination floor registration devices other than itself, indicating that it is responsible for executing the assigned task. On the other hand, if any of the first lower-level devices become unable to operate normally, it stops distributing the assignment signal from itself. The elevator control system according to claim 10 or 11, wherein the second higher-level device, when it is unable to receive the assignment signal from the first higher-level device, starts executing the assignment task on behalf of the first higher-level device and also starts distributing the assignment signal to destination floor registration devices other than itself.

13. Each of the aforementioned destination floor registration devices, when it is operating normally, sends an "alive" status signal to the other destination floor registration devices. The alive status signals distributed by the first and second higher-level devices each include assignment information indicating whether the higher-level device is currently responsible for executing the assigned task or not. The first higher-level device, when both itself and the first lower-level device are operating normally, transmits its own alive status signal with the assigned responsibility information within the signal set to the "currently assigned" state. On the other hand, if either of the first lower-level devices becomes unable to operate normally, it changes the assigned responsibility information within its own alive status signal to the "not assigned" state. If the second higher-level device receives the alive status signal from the first higher-level device and the assigned personnel information within that signal is in an "assigned" state, it will transmit its own alive status signal with the assigned personnel information within that signal in an "unassigned" state. The elevator control system according to claim 10 or 11, wherein the second higher-level device, when it is unable to receive the alive status signal from the first higher-level device, or when the assigned task information in the alive status signal received from the first higher-level device becomes unavailable, starts executing the assigned task on behalf of the first higher-level device and changes the assigned task information in its own alive status signal to an available state.

14. An elevator control system according to any one of claims 2 to 6, 10, and 11, wherein when selecting the first subordinate device from among the plurality of destination floor registration devices, the first subordinate device is selected from among the plurality of destination floor registration devices in order from the one with the lowest frequency of destination floor registration.

15. A group management control device for performing the multiple tasks for carrying out the group management control is provided separately from the multiple destination floor registration devices, An elevator control system according to any one of claims 1 to 3, wherein if the group control device fails to operate normally, two or more destination floor registration devices, which are some or all of the multiple destination floor registration devices, share the multiple tasks for performing the group control in place of the group control device.

16. An elevator control method comprising an elevator with multiple cars and multiple destination floor registration devices, wherein two or more destination floor registration devices, which are part or all of the multiple destination floor registration devices, are assigned multiple tasks for performing group control for the multiple cars.

Images