Control system of elevator

Abstract

To enable many cars exceeding the number of cars that can be controlled by one group management control device to constitute a bank.SOLUTION: A plurality of group management control devices installed to correspond to each of a plurality of groups in a bank are connected so that the devices can communicate with one another. In each group management control device, a first extraction processing unit uses its own operation data and operation data delivered by other group management control devices to extract an allocation candidate from among all cars belonging to a bank, when receiving an allocation request from a user. If the allocation candidate is a car belonging to another group, a transfer processing unit transfers the allocation request to a group management control device of a group to which the allocation candidate belongs. A second extraction processing unit extracts an allocation candidate from among cars belonging to its own group, when an allocation request is transferred from another group management control device. An allocation processing unit performs allocation of a landing call to the allocation candidate extracted by the second extraction processing unit.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a control technique for an elevator having a bank. [Background technology]

[0002] In elevators with banks, one group management control device is generally installed for each bank, and each group management control device performs group management for all cars belonging to its own bank. A known control technology for such elevators is one in which the group management control device accumulates operation data (including call and allocation data, operation data showing the movement of cars, etc.) generated within its own bank as learning data, and uses the learning data to learn in order to achieve more optimal group management (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] In recent years, as buildings have become larger, the number of cars that make up one bank has tended to increase. On the other hand, when trying to manage a large number of cars in one bank with a single group management control device, highly accurate group management using learning data requires the group management control device to have significantly high processing power. For example, the required processing power increases exponentially with each additional car to be managed. Therefore, when attempting to perform highly accurate group management using learning data, the number of cars that can be managed by one group management control device is limited to a number corresponding to the processing power of the group management control device. In other words, it becomes difficult to configure one bank with a large number of cars exceeding that number.

[0005] Therefore, an object of the present invention is to make it possible to configure one bank with a large number of cars that exceeds the number of cars that can be managed by one group management control device. [Means for solving the problem]

[0006] The control system according to the present invention is applicable to an elevator having a bank, and includes a plurality of group management control devices, each of which is installed so that a plurality of cars belonging to the bank are divided into a plurality of groups, and each of which corresponds to one of the groups, and further includes the following configuration (Aspect 1). The plurality of group management control devices are connected to enable mutual communication. Each group management control device includes a distribution processing unit, a first extraction processing unit, a transfer processing unit, a second extraction processing unit, and an allocation processing unit. The distribution processing unit distributes operation data within its own group to other group management control devices. When a hall call allocation request is received from a user, the first extraction processing unit extracts allocation candidates from all of the cars belonging to the bank using operation data within its own group and operation data within other groups distributed by the other group management control devices. If the allocation candidate extracted by the first extraction processing unit is a car belonging to another group, the transfer processing unit transfers the allocation request to the group management control device of the group to which the allocation candidate belongs. The second extraction processing unit extracts an allocation candidate from among the cars belonging to its own group when the allocation candidate extracted by the first extraction processing unit is a car belonging to its own group, or when an allocation request is transferred from another group management control device. The allocation processing unit executes allocation of hall calls to the allocation candidate extracted by the second extraction processing unit.

[0007] According to the above-mentioned aspect 1, it is possible to have multiple group management control devices within one bank cooperate with each other by distributing operation data and transferring allocation requests. Furthermore, in the above-mentioned aspect 1, the group management control device of each group can be made to perform highly accurate processing using learning data to extract allocation candidates in the second extraction processing unit, which targets only the cars belonging to that group, while performing relatively simple processing to extract allocation candidates in the first extraction processing unit, which targets all the cars belonging to the bank. This makes it possible for the group management control device of each group to achieve the following processing while cooperating with other group management control devices within a realistic range according to its processing capacity.

[0008] First, when the group management control device of each group receives a request from a user to allocate a hall call, it extracts allocation candidates using a relatively simple process in the first extraction processing unit, making it possible to relatively easily predict from all cars which car is suitable for allocating the requested hall call. Then, the group management control device of the group to which the predicted car (allocation candidate extracted by the first extraction processing unit) belongs narrows it down to cars belonging to its own group and extracts allocation candidates using highly accurate processing in the second extraction processing unit, making it possible to determine with high accuracy which car is suitable for allocation.

[0009] By linking multiple group management control devices together within a single bank in this way, it becomes possible to control all of the cars that make up that bank as if they were being managed by a single group management control device.

[0010] In the control system according to the above-described aspect 1, each group management control device may have the following configuration (aspect 2). The second extraction processing unit may accumulate operation data within its own group as learning data, and use the learning data to perform learning to optimize allocation candidates within the group, and extract allocation candidates in a learned state. Furthermore, the first extraction processing unit may extract allocation candidates using a predetermined setting value, without performing learning to optimize allocation candidates across the entire bank.

[0011] According to the above-mentioned second aspect, it is possible to perform the extraction of allocation candidates in the second extraction processing section with high accuracy, while performing the extraction of allocation candidates in the first extraction processing section with a relatively simple process.

[0012] The control system according to the above-described aspect 1 or 2 may further include a plurality of destination floor registration devices belonging to a bank, and may have the following configuration (aspect 3). Each of the plurality of destination floor registration devices may be assigned to one of a plurality of groups and connected to the group management control device to which it is assigned. In such a configuration, when a user registers a destination floor using a destination floor registration device connected to the group management control device and the group management control device receives an allocation request from the destination floor registration device, the group management control device may extract allocation candidates using a first extraction processing unit. Furthermore, when an allocation request is transferred from another group management control device and the group management control device extracts allocation candidates using a second extraction processing unit, the group management control device may, after performing the allocation using the allocation processing unit, return information about the allocation to the group management control device that transferred the allocation request. Then, when the group management control device receives allocation information from the group management control device after transferring the request to the other group management control device using a transfer processing unit, the group management control device may inform the user of the allocation information through the destination floor registration device that originally made the allocation request.

[0013] According to the above-mentioned aspect 3, it is possible to distribute and associate the destination floor registration devices installed in one bank with multiple group management control devices, thereby enabling the extraction of allocation candidates from all the cars belonging to that one bank (first extraction process) to be executed in a distributed manner by multiple group management control devices. Therefore, even if one of the group management control devices breaks down and the destination floor registration device associated with that group management control device becomes unavailable, it is possible to register destination floors using another destination floor registration device, and as a result, it is possible to continue operation of the bank without interruption. In other words, it is possible to build a highly robust bank, including the destination floor registration devices.

[0014] Furthermore, by configuring a group, which is the smallest structural unit, to include a destination floor registration device, it is possible to build a single, highly robust bank, including the destination floor registration device, simply by combining multiple such groups.

[0015] The control system according to the above-described first or second aspect may further include a plurality of destination floor registration devices belonging to a bank, and may have the following configuration (aspect 4). The plurality of destination floor registration devices may be assigned to one of a plurality of groups, and each destination floor registration device may be configured to be able to communicate not only with the group management control device of its own group but also with other group management control devices without going through the group management control device. Each destination floor registration device may distribute an allocation request to all of the plurality of group management control devices when a user registers a destination floor therein. In such a configuration, when each group management control device receives an allocation request and the allocation request is distributed from the destination floor registration device associated with that group management control device, it may execute extraction of allocation candidates in a first extraction processing unit. Furthermore, when each group management control device receives an allocation request and the allocation request is transferred from another group management control device, it may execute extraction of allocation candidates in a second extraction processing unit and allocation in an allocation processing unit, and then notify the user of the allocation information through the destination floor registration device that originally sent the allocation request, without going through the other group management control devices.

[0016] According to the above-mentioned aspect 4, when an allocation request is transferred, the information on the allocation executed by the group management control device of the transfer destination can be provided to the user directly from the transfer destination (in other words, without going through the group management control device from which the allocation request was originally made) through the destination floor registration device that made the initial allocation request. [Effects of the Invention]

[0017] According to the present invention, one bank can be configured with a large number of cars that exceeds the number of cars that can be managed by one group management control device. [Brief explanation of the drawings]

[0018] [Figure 1] 1 is a conceptual diagram showing the overall configuration of an elevator to which a control system according to an embodiment is applied. [Figure 2] 2 is a conceptual diagram showing the configuration of each group management control device included in the control system according to the embodiment. FIG. [Figure 3] 3A and 3B are conceptual diagrams illustrating examples of first correspondence management data and second correspondence management data used in the embodiment. [Figure 4] 10 is a flowchart showing a call registration process performed by each group management control device in the embodiment. [Figure 5] FIG. 1 is a conceptual diagram showing the overall configuration of an elevator to which a control system according to a first modified example is applied. [Figure 6] 10 is a flowchart showing a call registration process performed by each group management control device in the first modified example. DETAILED DESCRIPTION OF THE INVENTION

[0019] [1] Implementation [1-1] Overall structure of the elevator Fig. 1 is a conceptual diagram showing the overall configuration of an elevator to which a control system according to an embodiment is applied. Fig. 1 shows an elevator having one bank made up of a plurality of cars G, to which the control system according to this embodiment is applied. Note that an elevator may have a plurality of banks. In this case, the control system according to this embodiment may be applied to any one of the banks, or one control system according to this embodiment may be applied to some or all of the banks.

[0020] As shown in Fig. 1, in one bank to which the control system of this embodiment is applied (hereinafter, this bank will be referred to as the "target bank"), a plurality of cars G constituting the target bank are divided into a plurality of groups (in Fig. 1, these groups are distinguished by the letters "A", "B", ...). Then, a group management control device 1 is installed corresponding to each of these groups, and these group management control devices 1 are connected so as to be able to communicate with each other.

[0021] Furthermore, in the target bank, multiple destination floor registration devices 2 are installed on each floor where passengers can board and disembark at the target bank. Here, the destination floor registration devices 2 are devices that allow users to register their destination floor Fd at the target bank. Furthermore, each of the destination floor registration devices 2 on each floor is assigned to one of the multiple groups and is connected to the group management control device 1 of the group to which it is assigned (see Figure 1).

[0022] When a user registers a destination floor Fd using each destination floor registration device 2, the destination floor Fd is transmitted to the group management control device 1 of the group to which the destination floor registration device 2 belongs (the group management control device 1 to which the destination floor registration device 2 is connected). As a result, a request for hall call allocation (a request for call registration) from the user is made to the group management control device 1. At this time, each destination floor registration device 2 transmits its own device information PdX along with the destination floor Fd to the group management control device 1 so that the group management control device 1 recognizes which destination floor registration device 2 is the source of the destination floor Fd.

[0023] [1-2] Configuration of group management control device Each group management control device 1 is a device that performs group management for the cars G that belong to its own group, and centrally manages these cars G through an elevator control device provided for each car G (see Figure 1). Within the target bank, each group management control device 1 executes call registration processing (control processing for allocating hall calls to cars G) in response to allocation requests from users in cooperation with other group management control devices 1. Details of the call registration processing will be described later.

[0024] In this embodiment, to enable cooperation with such other group management control devices 1, each group management control device 1 distributes operation data generated by group management within its own group (operation data within its own group) to the group management control devices 1 of other groups (distribution process). Here, the operation data includes various data related to operation within the group, such as data related to allocation and operation data showing the movement of the elevator car G (movement of the elevator car G, opening and closing of the doors, etc.). This allows each group management control device 1 to grasp not only the operation status within its own group, but also the operation status within other groups.

[0025] In addition, each group management control device 1 sequentially accumulates operation data within its own group as learning data Dp, and uses the learning data Dp to learn to achieve more optimal group management within the group (learning to optimize allocation candidates within the group). Here, the learning data Dp is obtained by statistically analyzing the operation data at any time, and includes analytical data on the operating status of the elevator car G (average door-open time, average door-close time, average running time between floors, average stop time at each floor, etc.) and analytical data on the usage status of the elevator (average number of hall calls generated in the past five minutes, average congestion level in the elevator car G in the past five minutes, etc.). Note that the analysis of the operation data is not limited to statistical analysis, and AI (neural network, etc.) may also be used.

[0026] 2 is a conceptual diagram showing the configuration of each group management control device 1. As shown in this diagram, each group management control device 1 includes a storage unit 11 and a control unit 12.

[0027] The storage unit 11 is a part configured with storage devices such as ROM and RAM, and stores information necessary for the control processing performed by the group management control device 1. In this embodiment, the above-mentioned learning data Dp is stored in the storage unit 11 as such information, and further, first correspondence management data Dq1 and second correspondence management data Dq2 are stored in the storage unit 11. Here, the first correspondence management data Dq1 is a database for managing, for each destination floor registration device 2, multiple pieces of information related to the destination floor registration device 2 by linking them together. The second correspondence management data Dq2 is a database for managing, for each group, multiple pieces of information related to the group management control devices 1 and the cars G in the group by linking them together.

[0028] 3(A) is a conceptual diagram illustrating the first correspondence management data Dq1 used in this embodiment. In the first correspondence management data Dq1 illustrated in this figure, for each destination floor registration device 2, device information PdX for distinguishing the destination floor registration device 2 from other devices, the installation floor Fs of the destination floor registration device 2, and the group to which the destination floor registration device 2 belongs are recorded in a mutually associated state.

[0029] As a result, when each group management control device 1 receives device information PdX together with the destination floor Fd from each destination floor registration device 2 (each destination floor registration device 2 connected to itself) belonging to its own group (when receiving a request to assign a hall call), it can identify the installation floor Fs of the destination floor registration device 2 (the destination floor registration device 2 in which the destination floor Fd has been registered) from the device information PdX by referring to the first correspondence management data Dq1. In this embodiment, the installation floor Fs of the destination floor registration device 2 is used as the departure floor Fc (boarding floor) of the user who has registered the destination floor Fd with the destination floor registration device 2.

[0030] 3(B) is a conceptual diagram illustrating the second correspondence management data Dq2 used in this embodiment. In the second correspondence management data Dq2 illustrated in this figure, for each group, device information PdY for distinguishing the group management control device 1 of that group from other devices and car information PdZ for distinguishing each car G belonging to that group from other cars G are recorded in a mutually associated state.

[0031] The control unit 12 is a part responsible for executing the control processing performed by the group management control device 1, and is composed of processing devices such as a CPU and an MPU. Specifically, the control unit 12 is responsible for executing the distribution processing described above and the call registration processing (including a first extraction processing, a transfer processing, a second extraction processing, and an allocation processing) described in detail below. The parts (processing units) responsible for these processes are constructed as software within the control unit 12 by a group management program installed in the group management control device 1. In FIG. 2, a distribution processing unit 12A and a call registration processing unit 12B (including a first extraction processing unit 121, a transfer processing unit 122, a second extraction processing unit 123, and an allocation processing unit 124) are constructed as such processing units.

[0032] The group management program described above may be stored in a readable state on a portable storage medium (for example, a flash memory) before being installed in the group management control device 1, or may be stored in a downloadable state on another server, etc. Furthermore, the control processing performed by the group management control device 1 is not limited to being realized by software through the execution of a program, but may also be realized by hardware using a processing circuit (control unit 12) built into the group management control device 1.

[0033] [1-3] Call registration process performed by the group management control device 4 is a flowchart showing the call registration process performed in this embodiment by each group management control device 1. This call registration process is started when each group management control device 1 receives a request to allocate a hall call.

[0034] In this embodiment, there are two possible cases in which each group management control device 1 receives a hall call allocation request. The first case is when a user registers a destination floor Fd using a destination floor registration device 2 belonging to the group of the group management control device 1 (in this embodiment, the destination floor registration device 2 connected to the group management control device 1), and the group management control device 1 receives the allocation request from that destination floor registration device 2. In this case, each group management control device 1 receives, as the allocation request, the destination floor Fd registered by the user and the device information PdX of the destination floor registration device 2 used to register the destination floor Fd. The second case is when each group management control device 1 receives an allocation request transferred from another group management control device 1. In this case, each group management control device 1 receives, as the allocation request, not only the destination floor Fd and the device information PdX, but also the device information PdY of the group management control device 1 that transferred the request. In both cases, the information received by each group management control device 1 as an allocation request will be collectively referred to as "received information Pr."

[0035] When the call registration process begins, the group management control device 1 determines whether the received allocation request is from a destination floor registration device 2 belonging to its own group or whether it has been transferred from another group management control device 1, by determining whether the device information PdY is included in the received information Pr (step S100).

[0036] If the group management control device 1 determines "not included (No)" in step S100, it can determine that it has received an allocation request from a destination floor registration device 2 belonging to its own group. In this case, the group management control device 1 uses the first correspondence management data Dq1 to extract the installation floor Fs associated with the device information PdX in the received information Pr, sets this as the user's departure floor Fc, and then sets this departure floor Fc and the destination floor Fd in the received information Pr as one hall call. Hereinafter, this hall call will be referred to as the "focused hall call Ck."

[0037] Then, the group management control device 1 extracts allocation candidates Gc1 for the target hall call Ck from all cars G belonging to the target bank using operation data within its own group and operation data within other groups distributed by other group management control devices 1 (step S110, first extraction process). Specifically, the group management control device 1 targets all cars G identified by the car information PdZ recorded in the second correspondence management data Dq2 and extracts allocation candidates Gc1 from these cars G.

[0038] On the other hand, in step S110 (first extraction process), the group management control device 1 does not perform learning to optimize the allocation candidate Gc1 throughout the entire target bank, but instead extracts the allocation candidate Gc1 using a predetermined setting value. In this way, in the first extraction process, the extraction of the allocation candidate Gc1 is performed using a relatively simple process.

[0039] Next, the group management control device 1 determines whether the allocation candidate Gc1 extracted in step S110 (first extraction process) is a car G belonging to its own group (step S111). Specifically, the group management control device 1 determines whether the group associated with the car information PdZ of the allocation candidate Gc1 matches the group associated with its own device information PdY by referring to the second correspondence management data Dq2. If the group management control device 1 determines that they "match," it determines that "the car G belongs to its own group (Yes)," and if it determines that they "do not match," it determines that "the car G is not a car G belonging to its own group (No)."

[0040] If the group management control device 1 determines in step S111 that "the car G belongs to its own group (Yes)", it again extracts allocation candidates Gc2 for the target hall call Ck from among the cars G that belong to its own group (step S112, second extraction process). Specifically, the group management control device 1 targets cars G identified by car information PdZ associated with the same group as itself in the second correspondence management data Dq2 (in other words, car information PdZ associated with its own device information PdY), and extracts allocation candidates Gc2 from among those cars G.

[0041] Furthermore, in step S112 (second extraction processing), the group management control device 1 uses the learning data Dp to perform learning to optimize the allocation candidate Gc2 within its own group, and extracts the allocation candidate Gc2 in the learned state. In this way, in the second extraction processing, the allocation candidate Gc2 is extracted with high accuracy.

[0042] Thereafter, the group management control device 1 executes allocation of the target hall call Ck to the allocation candidate Gc2 extracted in step S112 (second extraction process) (step S113: allocation process). Then, the group management control device 1 notifies the user of the information of the allocation executed in step S113 (such as the car information PdZ of the car G (allocation candidate Gc2) to which the target hall call Ck has been allocated) through the destination floor registration device 2 (the destination floor registration device 2 that has made the allocation request) identified by the device information PdX in the received information Pr in the first correspondence management data Dq1 (step S114: guidance process). After step S114, the group management control device 1 ends the call registration process.

[0043] On the other hand, if the group management control device 1 determines in step S111 that the car G does not belong to its own group (No), it transfers the allocation request to the group management control device 1 of the group to which the allocation candidate Gc1 belongs so that the group management control device 1 can perform the allocation (step S120. Transfer processing).

[0044] Specifically, the group management control device 1 transfers the allocation request to another group management control device 1 identified by the device information PdY associated with the same group as the car information PdZ of the allocation candidate Gc1 in the second correspondence management data Dq2 (in other words, the device information PdY associated with the car information PdZ of the allocation candidate Gc1). At this time, the group management control device 1 transmits the destination floor Fd and device information PdX in the received information Pr to the group management control device 1 of the transfer destination, and also transmits its own device information PdY to the group management control device 1 of the transfer destination so that the transfer destination knows which group management control device 1 the allocation request was transferred from.

[0045] Then, when the transfer destination group management control device 1 receives the allocation request transferred from the transfer source group management control device 1, it determines in step S100 that the device information PdY is "included (Yes)." In this case, the transfer destination group management control device 1 uses the first correspondence management data Dq1 to extract the installation floor Fs associated with the device information PdX in the received information Pr, sets this as the user's departure floor Fc, and then sets this departure floor Fc and the destination floor Fd in the received information Pr as one hall call. Hereinafter, this hall call will be referred to as the "focused hall call Cw."

[0046] Then, the group management control device 1 of the transfer destination extracts allocation candidates GcW for the target hall call Cw from among the cars G belonging to its own group (step S130, second extraction process). Specifically, the group management control device 1 targets cars G identified by car information PdZ associated with the same group as its own device information PdY in the second correspondence management data Dq2 (in other words, car information PdZ associated with its own device information PdY), and extracts allocation candidates GcW from among those cars G.

[0047] Also, in step S130 (second extraction process), the group management control device 1 uses the learning data Dp to perform learning to optimize the allocation candidate GcW within its own group, and extracts the allocation candidate GcW in the learned state. In this way, the allocation candidate GcW is extracted with high accuracy in the second extraction process of the transfer destination as well.

[0048] Thereafter, the transfer destination group management control device 1 executes allocation of the target hall call Cw to the allocation candidate GcW extracted in step S130 (second extraction process) (step S131, allocation process).

[0049] In this case, the group management control device 1 of the transfer destination returns the allocation information executed in step S131 (such as car information PdZ of the car G (allocation candidate GcW) to which the target hall call Cw is assigned) to the group management control device 1 that transferred the allocation request (the group management control device 1 from which the request was transferred) (step S132, return process). Specifically, the group management control device 1 returns the above allocation information to the group management control device 1 identified by device information PdY in the received information Pr in the first corresponding management data Dq1. After step S132, the group management control device 1 of the transfer destination ends the call registration process.

[0050] As a result, the group management control device 1 of the transfer source transfers the allocation request in step S120 of its own call registration processing, and then receives the allocation information from the group management control device 1 of the transfer destination. Therefore, after step S120, the group management control device 1 of the transfer source determines whether or not allocation information has been returned from the group management control device 1 of the transfer destination (step S121). At this time, the group management control device 1 repeats step S121 until it determines in step S121 that "a reply has been received (Yes)."

[0051] Then, if the transfer source group management control device 1 determines in step S121 that "a reply has been received (Yes)", it notifies the user of the returned allocation information through the destination floor registration device 2 (the destination floor registration device 2 that has made the allocation request) identified by the device information PdX in the received information Pr in the first correspondence management data Dq1 (step S122, guidance process). After step S122, the transfer source group management control device 1 also ends the call registration process.

[0052] According to this embodiment, it is possible for multiple group management control devices 1 within a target bank to cooperate with each other by distributing operation data and transferring allocation requests. Furthermore, in this embodiment, the group management control device 1 of each group is caused to perform highly accurate processing using the learning data Dp to extract the allocation candidate Gc2 or GcW in the second extraction process, which targets only the cars G belonging to that group, while performing relatively simple processing to extract the allocation candidate Gc1 in the first extraction process, which targets all the cars G belonging to the target bank. This allows the group management control device 1 of each group to cooperate with other group management control devices 1 to perform the following processing within a realistic range based on its processing capacity.

[0053] First, when the group management control device 1 of each group receives a request for allocation of a hall call from the destination floor registration device 2 (i.e., a user), it extracts allocation candidates Gc1 using a relatively simple process (first extraction process), thereby relatively easily predicting a car G suitable for allocation of the requested hall call from among all cars G. Then, the group management control device 1 of the group to which the predicted car G (allocation candidate Gc1 extracted in the first extraction process) belongs narrows down to the cars G belonging to its own group and extracts allocation candidates Gc2 or GcW using a highly accurate process (second extraction process), thereby determining with high accuracy the car G suitable for allocation.

[0054] By linking multiple group management control devices 1 together within a target bank in this way, it becomes possible to control all of the cars G that make up the bank as if they were being managed by a single group management control device 1. Therefore, it becomes possible to configure one bank with a large number of cars G that exceeds the number of cars G that can be managed by a single group management control device 1.

[0055] Furthermore, in this embodiment, each destination floor registration device 2 installed in the target bank is assigned to one of the multiple groups and connected to the group management control device 1 of the group to which it is assigned. This configuration allows the destination floor registration devices 2 installed in the target bank to be distributed and associated with multiple group management control devices 1, thereby allowing the extraction of allocation candidates Gc1 from all cars G belonging to the target bank (first extraction process) to be distributed and executed by multiple group management control devices 1. Therefore, even if one group management control device 1 breaks down and the destination floor registration device 2 associated with that group management control device 1 becomes unavailable, the destination floor Fd can be registered using another destination floor registration device 2, and as a result, operation of the target bank can continue without interruption. In other words, a highly robust bank can be constructed, including the destination floor registration device 2.

[0056] Furthermore, by configuring a group, which is the smallest structural unit, to include the destination floor registration device 2, it becomes possible to construct a single, highly robust bank, including the destination floor registration device 2, simply by combining multiple such groups.

[0057] [2] Variation [2-1] First modified example The first modification is a modification of the above-described embodiment.

[0058] FIG. 5 is a conceptual diagram showing the overall configuration of an elevator to which a control system according to the first modification is applied. As shown in this diagram, in this modification, the destination floor registration devices 2 installed in the target bank are each assigned to one of the multiple groups. Each destination floor registration device 2 is connected so that it can communicate not only with the group management control device 1 of its own group, but also with other group management control devices 1 without going through the group management control device 1. In other words, when a user registers a destination floor Fd at each destination floor registration device 2, the destination floor Fd and its own device information PdX can be broadcast to all group management control devices 1 in the target bank. Therefore, when a user registers a destination floor Fd at each destination floor registration device 2, an allocation request is sent to all group management control devices 1.

[0059] 6 is a flowchart showing the call registration process performed by each group management control device 1 in the first modified example. In this modified example, this call registration process is also started when the group management control device 1 of each group receives an allocation request distributed from a destination floor registration device 2 in another group. Therefore, if the group management control device 1 determines in step S100 that the device information PdY is "not included (No)" in the received information Pr, it can determine based on this determination that the allocation request has been received from a destination floor registration device 2 belonging to one of the groups in the target bank, rather than being transferred from another group management control device 1.

[0060] Therefore, if the group management control device 1 determines "not included (No)" in step S100, it determines whether the received allocation request was distributed from a destination floor registration device 2 belonging to its own group (step S201) in order to determine whether it should perform the processing from step S110 (first extraction processing). Specifically, the group management control device 1 uses the first correspondence management data Dq1 to extract a group associated with the device information PdX in the received information Pr, and then determines whether that group matches the group associated with its own device information PdY in the second correspondence management data Dq2. If the group management control device 1 determines that they "match," it determines that "the information was distributed from a destination floor registration device 2 belonging to its own group (Yes)." If the group management control device 1 determines that they "do not match," it determines that "the information was not distributed from a destination floor registration device 2 belonging to its own group (No)."

[0061] If the group management control device 1 determines in step S201 that "the information was distributed from a destination floor registration device 2 belonging to its own group (Yes)", it determines that it should perform the processing from step S110 onwards, and starts processing from step S110.

[0062] On the other hand, if the group management control device 1 determines in step S201 that "the request was not distributed from a destination floor registration device 2 belonging to its own group (No)," it can determine based on that determination that the group management control device 1 of another group to which the destination floor registration device 2 that distributed the allocation request belongs will perform processing from step S110, and therefore it terminates the call registration processing without doing anything.

[0063] In addition, in this modified example, if the group management control device 1 determines in step S111 that the allocation candidate Gc1 is "not a car G belonging to its own group (No)" and transfers the allocation request to the group management control device 1 of the group to which the allocation candidate Gc1 belongs (step S120. Transfer processing), the group management control device 1 to which the request is transferred can perform the following processing.

[0064] After executing step S130 (second extraction process) and step S131 (allocation process), the transfer destination group management control device 1 can inform the user of the allocation information executed in step S131 through the destination floor registration device 2 that originally made the allocation request (step S140), without going through the transfer source group management control device 1 (in other words, without returning to the transfer source group management control device 1). Specifically, the transfer destination group management control device 1 can inform the user of the allocation information by directly communicating with the destination floor registration device 2 identified by device information PdX in the received information Pr in the first correspondence management data Dq1.

[0065] Therefore, after the transfer source group management control device 1 transfers the allocation request in step S120 of the call registration process that it performs, it can end the call registration process without performing the guidance process (step S122 in FIG. 4).

[0066] According to this first variant, when an allocation request is transferred, the information on the allocation performed by the group management control device 1 to which the request is transferred can be provided to the user directly from the transfer destination (in other words, without going through the group management control device 1 from which the request is transferred) through the destination floor registration device 2 that originally made the allocation request.

[0067] [2-2] Second variant The second modification is a modification of the above-described embodiment.

[0068] In the target bank, instead of the destination floor registration device 2, multiple destination direction buttons may be provided for each floor, and a destination floor button may also be installed in each car G. Here, the destination direction buttons include an up button for specifying an up direction as the destination direction, and a down button for specifying a down direction as the destination direction. In addition, the destination floor button is a button for users to register a destination floor Fd in the car G, and is provided for each stopping floor at which the user can disembark in the target bank.

[0069] In this modified example, the destination direction buttons on each floor are assigned to one of a plurality of groups, and are connected to the group management control device 1 of the group to which they are assigned.

[0070] Furthermore, when a user presses a destination direction button to specify a destination direction, that destination direction is sent to the group management control device 1 of the group to which that destination direction button belongs (the group management control device 1 to which that destination direction button is connected). As a result, an allocation request (call registration request) from the user is made to the group management control device 1. At this time, the destination direction button sends device information PdX to identify itself from other buttons, devices, etc., along with the destination direction to the group management control device 1, so that the group management control device 1 can recognize which destination direction button is the source of the destination direction.

[0071] In this configuration, as in the above-described embodiment, by linking multiple group management control devices 1 together within the target bank, it becomes possible to control all of the cars G that make up the bank as if they were being managed by a single group management control device 1. Therefore, it becomes possible to configure one bank with a large number of cars G that exceeds the number of cars G that can be managed by a single group management control device 1.

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

[0073] Furthermore, from the above-described embodiments and modifications, the subject matter of the invention is not limited to the elevator control system, but may also include devices constituting the control system, control processes and programs executed by the control system, etc., or some of these may be extracted partially. Furthermore, some or all of the configuration of an elevator to which the control system is applied may also be extracted as the subject matter of the invention. [Explanation of symbols]

[0074] 1 Group management control device 2. Destination floor registration device G car 11 Storage section 12 Control Unit 12A Distribution Processing Unit 12B Call registration processing unit Ck, Cw Call at the target platform Dp training data Fc Departure Floor Fd Destination floor Fs Installation floor Pr Reception Information 121 First extraction processing unit 122 Transfer Processing Unit 123 Second extraction processing section 124 Allocation processing unit Dq1 First response management data Dq2 2nd response management data Gc1, Gc2, GcW allocation candidates PdX, PdY equipment information PdZ basket information

Claims

1. A control system applicable to an elevator with a bank, a plurality of group management control devices, each of which is installed in correspondence with a respective one of the groups, and which are connected to each other so as to be able to communicate with each other; Equipped with Each group management control device a distribution processing unit that distributes operation data within its own group to other group management control devices; a first extraction processing unit that, when receiving a hall call allocation request from a user, extracts allocation candidates from all elevator cars belonging to the bank using operation data within its own group and operation data within other groups distributed by other group management control devices; a transfer processing unit that transfers the allocation request to a group management control device of a group to which the allocation candidate belongs when the allocation candidate extracted by the first extraction processing unit is a car belonging to another group; a second extraction processing unit that extracts an allocation candidate from among cars belonging to its own group when the allocation candidate extracted by the first extraction processing unit is a car belonging to its own group, or when an allocation request is transferred from another group management control device; an allocation processing unit that executes allocation of the hall calls to the allocation candidates extracted by the second extraction processing unit; An elevator control system comprising:

2. In each group management control device, the second extraction processing unit accumulates operation data within its own group as learning data, performs learning using the learning data to optimize allocation candidates within the group, and extracts the allocation candidates in a learned state; 2. The elevator control system according to claim 1, wherein the first extraction processing unit does not perform learning to optimize the allocation candidates across the entire bank, but extracts the allocation candidates using a predetermined setting value.

3. a plurality of destination floor registration devices belonging to the bank; Further provided with The plurality of destination floor registration devices are each assigned to one of the plurality of groups and connected to the group management control device to which they are assigned, Each group management control device When the user registers a destination floor in a destination floor registration device connected to the device, and the allocation request is received from the destination floor registration device, extraction of the allocation candidates is performed in the first extraction processing unit, When the allocation request is transferred from another group management control device and the second extraction processing unit extracts the allocation candidates, after the allocation processing unit executes the allocation, information on the allocation is returned to the group management control device that transferred the allocation request; 3. The elevator control system according to claim 1, wherein, after the transfer to another group management control device is executed by the transfer processing unit, when the allocation information is returned from the group management control device, the allocation information is notified to the user via the destination floor registration device that made the allocation request.

4. a plurality of destination floor registration devices belonging to the bank; Further provided with The plurality of destination floor registration devices are each assigned to one of the plurality of groups, while each destination floor registration device can communicate not only with the group management control device of its own group, but also with other group management control devices without going through it, and when a destination floor is registered by a user, the allocation request is distributed to all of the plurality of group management control devices, Each group management control device When the allocation request is received, if the allocation request is distributed from a destination floor registration device associated with the device itself, extraction of the allocation candidate is performed in the first extraction processing unit, 3. The elevator control system according to claim 1, wherein, when the allocation request is received and the allocation request has been transferred from another group management control device, after the second extraction processing unit extracts the allocation candidates and the allocation processing unit executes the allocation, the information on the allocation is not provided to the user via the destination floor registration device that first made the allocation request, but rather via the other group management control device.

Images