Elevator system and method for assigning a car of an elevator

Abstract

An elevator system is configured to be able to accept an internal call made by operating a panel of an elevator by a user and an external call made by a device outside the elevator using a communication network. The elevator system has a processor that allocates a car as a candidate for a call assignment from one or more cars for the internal call or the external call. The processor is configured to, in a case where the external call is accepted, execute: a working state determination process in which it is determined whether the one or more cars are in a working state or a non-working state; and an external call allocation process in which a car in the non-working state is preferentially allocated as a candidate for the call assignment compared to a car in the working state.

Description

Technical Field

[0001] This disclosure relates to elevator systems and elevator car allocation methods. Background Technology

[0002] Patent Document 1 discloses an elevator control technology that allows autonomous mobile robots to ride alongside users. In this technology, when an autonomous mobile robot has registered a wireless call signal and wants to board the elevator, and there are calls from users in the same direction as the robot's target floor, these calls are responded to first. Then, after no further calls are received, the system switches to dedicated operation for the autonomous mobile robot to the target floor. Once it is confirmed that the autonomous mobile robot has disembarked at the target floor, normal operation resumes.

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2020-114763 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] In the technology of Patent Document 1, elevator dispatch is performed on the call of an autonomous mobile robot, which is an external device, regardless of the working state of the elevator car. Therefore, the space inside the working elevator car may be occupied by the autonomous mobile robot that has already boarded the elevator, which may reduce the user's elevator usage efficiency.

[0008] This disclosure was made to solve the aforementioned problems, and its purpose is to provide a technique for dispatching elevator cars from external devices without compromising user convenience.

[0009] Methods for solving problems

[0010] The elevator system disclosed herein is configured to accept both internal and external calls. Internal calls are made by the user operating the elevator control panel, while external calls are made from external devices via a communication network. The elevator system includes: a car allocation unit configured to allocate cars as dispatch candidates from one or more cars for internal or external calls; and a car operation status determination unit that, upon receiving an external call, performs operation status determination processing, in which it determines whether one or more cars are in an operating or non-operating state. The car allocation unit receives the determination result from the operation status determination processing and performs external call allocation processing, in which non-operating cars are prioritized as dispatch candidates compared to cars in an operating state.

[0011] Furthermore, this disclosure is applied to a car allocation method in an elevator system configured to accept both internal and external calls, whereby the method allocates a car as a dispatch candidate from one or more cars for external calls. Internal calls are made by the user operating the elevator control panel, while external calls are made from external devices via a communication network. The car allocation method comprises: accepting external calls; determining whether one or more cars are in an operating or non-operating state; and performing external call allocation processing, in which non-operating cars are given priority for allocation as dispatch candidates compared to cars in an operating state.

[0012] Invention Effects

[0013] According to the elevator system and car allocation method disclosed herein, one or more cars are determined to be in a working or non-working state. Compared with cars in a working state, cars in a non-working state are given priority for allocation as dispatch candidates. Therefore, non-working cars are given priority for external calls, thus enabling car dispatch for calls from external devices without compromising the convenience of users making internal calls. Attached Figure Description

[0014] Figure 1 This is a structural diagram of the elevator system 100 according to embodiment 1.

[0015] Figure 2 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 1.

[0016] Figure 3 This is a structural diagram of the elevator management device in the elevator system of Implementation Method 1.

[0017] Figure 4 This is a flowchart illustrating the routine of the processing performed in the elevator management device 5 of Embodiment 1.

[0018] Figure 5 This is a diagram showing a variation of the hardware resources of the elevator management device 5.

[0019] Figure 6 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 2.

[0020] Figure 7 This is a flowchart illustrating the routine of the processing performed in the elevator management device 5 of Embodiment 2.

[0021] Figure 8 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 3.

[0022] Figure 9 This is a diagram illustrating an example of the relationship between dispatch limits, the number of cars in operation, and whether a dispatch is possible.

[0023] Figure 10 This is a flowchart illustrating the routine of the processing performed in the elevator management device 5 of Embodiment 3.

[0024] Figure 11 This is a block diagram showing the internal structure of the elevator system 100 according to embodiment 4.

[0025] Figure 12 This is a flowchart illustrating the routine of the dispatch limit calculation process performed in the elevator management device 5 of Embodiment 4.

[0026] Figure 13 This is a diagram illustrating an example of petabyte boundary information.

[0027] Figure 14 This is a diagram showing an example of the pirate limits calculated for each time period.

[0028] Figure 15 This is a block diagram showing the internal structure of the elevator system 100 according to embodiment 5.

[0029] Figure 16 This is a flowchart illustrating the routine of external elevator call cancellation processing performed in the elevator management device 5 of Embodiment 5. Detailed Implementation

[0030] The embodiments will now be described with reference to the accompanying drawings. Furthermore, common elements in all figures will be labeled with the same reference numerals, and repeated descriptions will be omitted.

[0031] 1. Implementation Method 1.

[0032] 1-1. Structure of the elevator system

[0033] Figure 1 This is a structural diagram of the elevator system 100 according to embodiment 1.

[0034] Elevator system 100 includes elevator 10 and external call registration device 8. Elevator 10 is configured to accept calls not only from users 6 but also from external devices 7. "External devices 7" broadly include mobile bodies such as robots capable of autonomous or remote movement, building equipment such as gates or smart locks, surveillance cameras, human sensors, positioning devices, and other equipment that uses communication networks to call for elevators.

[0035] Elevator 10 is installed in, for example, a building with multiple floors. Within the building, a shaft (not shown) is provided for elevator 10. The shaft is a relatively long space spanning multiple floors in the vertical direction. At each floor, a landing 12 is provided adjacent to the shaft.

[0036] Elevator 10 includes one or more cars 1, car control panels 2 installed in each car 1, floor control panels 3 installed in each floor 12, elevator control device 4, and elevator management device 5. One or more cars 1 are a device that transports users 6 and external equipment 7 of elevator 10 between multiple floors by traveling vertically in a shaft. For example, elevator 10 in Embodiment 1 includes three cars 1, numbered 1 to 3.

[0037] Each car 1 is equipped with a car control panel 2. The car control panel 2 is equipped with various buttons for opening and closing the car doors and specifying the destination floor. The landing control panel 3 is a device for receiving landing calls from users 6. Multiple landing control panels 3 are respectively installed on the walls of multiple landings 12.

[0038] The elevator control device 4 is a device that controls the operation of the elevator 10 based on the calls received by the car operation panel 2 or the landing operation panel 3. Hereinafter, the calls received by the car operation panel 2 or the landing operation panel 3 are referred to as "internal calls." When an internal call is received by the car operation panel 2 or the landing operation panel 3, the elevator control device 4 considers both the working car 1 and the non-working car 1 as dispatch candidates, and assigns any one car from these candidates. Here, "working state" of the car refers to the state in which the car is responding to the assigned call, such as the state when the doors are open for boarding or alighting, or the state when the car is traveling. On the other hand, "non-working state" of the car refers to the state in which no call has been assigned to the car, such as the state when the car is closed and waiting. Furthermore, the action of assigning a car to an internal call can be based on known dispatch actions; therefore, a detailed description is omitted here. The elevator control device 4 is located, for example, at the top or bottom of the hoistway. For example, if the machine room of the elevator 10 is located above the shaft, the elevator control device 4 may be located in the machine room.

[0039] The elevator management device 5 is a device that controls the operation of the elevator 10 based on calls registered from the external device 7 to the external call registration device 8. Hereinafter, calls registered from the external device 7 to the external call registration device 8 are referred to as "external calls". The elevator management device 5 is located, for example, at the top or bottom of the shaft. For example, if the machine room of the elevator 10 is located at the top of the shaft, the elevator control device 4 may also be located in the machine room. The function of the elevator management device 5 will be described in detail later.

[0040] The external call registration device 8 is a device that registers external calls received from external devices 7 via a communication network and sends the registration information to the elevator management device 5. The communication network between the external call registration device 8 and the elevator management device 5 is not limited. For example, if the external call registration device 8 is located in a remote server, it can use a common communication method such as the Internet or short-range wireless communication. Alternatively, if the external call registration device 8 is located in the machine room of the elevator 10, it can be connected to the elevator management device 5 via wired communication.

[0041] 1-2. Functions of the elevator system in Implementation Method 1

[0042] Figure 2 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 1. As an internal functional block of the elevator management device 5, it includes a car operating status determination unit 20, a car number allocation unit 22, and an external call communication unit 24. The car operating status determination unit 20 is a functional block for performing operating status determination processing, in which it determines whether one or more cars 1 are in an operating state or a non-operating state based on information received from the elevator control device 4. The car operating status determination unit 20 can be a structure that always determines the operating status of the car 1 through operating status determination processing, or it can be a structure where the external call communication unit 24, described later, performs operating status determination processing upon receiving an external call. The car operating status determination unit 20 sends the determination result information to the car number allocation unit 22.

[0043] The elevator allocation unit 22 is a functional block used to process the allocation of cars 1 for external elevator calls. Hereinafter, this process is referred to as "external elevator call allocation processing." In external elevator call allocation processing, the elevator allocation unit 22, based on the determination result information received from the car operating status determination unit 20, prioritizes one or more non-operating cars as dispatch candidates compared to cars in the operating state. More specifically, the elevator allocation unit 22 excludes the operating cars from the dispatch candidates among one or more cars 1, and only allocates non-operating cars as dispatch candidates. Then, the elevator allocation unit 22 allocates the cars responding to external elevator calls from the dispatch candidates consisting only of non-operating cars.

[0044] The external elevator call communication unit 24 is a functional block used to send and receive information related to external elevator calls between itself and the external elevator call registration device 8. For example, the external elevator call communication unit 24 receives external elevator call registration information containing registered external elevator calls from the external elevator call registration device 8. Furthermore, the external elevator call communication unit 24 sends dispatch information for the car 1 of the external elevator to the external elevator call registration device 8.

[0045] Figure 3 This is a structural diagram of the elevator management device of the elevator system according to Embodiment 1. The elevator management device 5 includes a processor 52 and a storage device 54.

[0046] Processor 52 performs various processes. Processor 52 is, for example, a microcomputer. Various information is stored in storage device 54. Examples of storage device 54 include volatile memory and non-volatile memory. External elevator call registration program is stored in storage device 54. Processor 52 executes external elevator call registration program, thereby realizing the working status determination process and external elevator call allocation process in elevator management device 5. In addition, determination result information, external elevator call registration information, and elevator dispatch information are stored in storage device 54 as various data.

[0047] 1-3. Specific processes performed in the elevator management device 5 of Embodiment 1

[0048] Figure 4 This is a flowchart illustrating the routine of the processing performed in the elevator management device 5 of Embodiment 1. Figure 4 The illustrated routine is executed by the processor 52 of the elevator management device 5 when an external call registration procedure has been performed. This flowchart also illustrates a portion of the car allocation method according to embodiments of this disclosure.

[0049] exist Figure 4In step S2 of the illustrated routine, it is determined whether an external elevator call from external device 7 has been registered. Here, the external elevator call communication unit 24 determines whether external elevator call registration information has been received from the external elevator call registration device 8. As a result, if the determination is not confirmed to be true, step S2 is repeatedly executed. On the other hand, if the determination in step S2 is confirmed to be true, the process proceeds to step S4.

[0050] In step S4, the working status determination process performed in the car working status determination unit 20 determines whether one or more cars are in a working state. As a result, if all cars are in a working state, the process proceeds to step S6; if at least one car is not in a working state, the process proceeds to step S8.

[0051] In step S6, since there are no non-working cars that should be set as dispatch candidates, the number allocation unit 22 temporarily suspends car allocation for external calls. Furthermore, the number allocation unit 22 sends a message indicating the suspension of external call allocation to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 to standby at floor 12. After step S6 is completed, the process returns to step S4.

[0052] On the other hand, in step S8, the car number allocation unit 22 allocates a car to respond to an external call from the non-working cars that are set as dispatch candidates. Furthermore, the car number allocation unit 22 sends the allocation information of the assigned car to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 of the allocated car number. This routine ends when step S8 is completed.

[0053] According to the process described above, when an external call from external device 7 is registered, cars in operation are excluded from the dispatch candidates, and only cars not in operation are selected. Therefore, if no car is not in operation, no car is assigned to handle an external call. Thus, internal calls are assigned before external calls, thereby preventing situations that would impair the convenience of ordinary users making internal calls.

[0054] Furthermore, even when there is a car that is not in operation, a car is also assigned to external calls, so that external calls from external equipment 7 can be handled without compromising the convenience of ordinary users.

[0055] 1-4. Variations of Implementation Method 1

[0056] The elevator system 100 of Embodiment 1 can also be modified as described below. Furthermore, the following modifications can also be applied to elevator systems of other embodiments described later.

[0057] Alternatively, the elevator allocation unit 22 may have a spooling function for external calls. In this case, once the car operation status determination unit 20 determines that there is a car in a non-operational state, the elevator allocation unit 22 may allocate the external call that has been spooled to the non-operational car.

[0058] Alternatively, the structure could be as follows: if the external device 7 does not have a display function, the notification from the external call communication unit 24 to the external device 7 will be displayed on an indicator installed at the landing station 12.

[0059] Figure 5 This diagram illustrates a variation of the hardware resources of the elevator management device 5. Figure 5 In the example shown, the elevator management device 5 includes, for example, a processing circuit 58, which includes a processor 52, a storage device 54, and dedicated hardware 56. Figure 5 This illustration shows an example of implementing a portion of the functions of the elevator management device 5 using dedicated hardware 56. Alternatively, all the functions of the elevator management device 5 can be implemented using dedicated hardware 56. The dedicated hardware 56 can be a single circuit, a composite circuit, a programming processor, a parallel programming processor, an ASIC (Application Specific Integrated Circuit), a FPGA (Field Programmable Gate Array), or a combination thereof.

[0060] Implementation method 2.

[0061] 2-1. Characteristic functions of the elevator system in Implementation Method 2

[0062] Figure 6 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 2. In addition to the structure of the elevator management device 5 of Embodiment 1, the elevator management device 5 of Embodiment 2 also includes an attribute determination unit 26.

[0063] The attribute determination unit 26 is a function block used to determine whether the attribute of an external elevator call is a priority object. Even external elevator calls can have the same level of urgency as internal elevator calls for ordinary users. Such priority external elevator calls are, for example, external elevator calls to users registered by user-attached guide robots, delivery robots providing indoor services, personal mobile devices, smartphones, smart devices, etc.

[0064] The external call communication unit 24 sends the external call registration information received from the external call registration device 8 to the attribute determination unit 26. The external call registration information contains attribute information indicating whether the external call is a priority object. The attribute determination unit 26 determines whether the external call is a priority object based on the received external call registration information. Hereinafter, this process is referred to as the "attribute determination process".

[0065] For external elevator calls, which are considered priority, they are allowed to be used by regular users to ensure they are given the same level of urgency as internal elevator calls. Specifically, when an external elevator call is determined to be a priority call during the attribute determination process, the dispatching unit 22 sets both the working car and the non-working car as dispatch candidates. Then, the dispatching unit 22 allocates a car to handle the external elevator call from these dispatch candidates.

[0066] On the other hand, when the attribute determination process determines that the external call is not a priority object, the number allocation unit 22 excludes one or more working cars from the dispatch candidates and sets only the non-working cars as dispatch candidates. Then, the number allocation unit 22 allocates the cars that should respond to the external call from the dispatch candidates consisting only of non-working cars.

[0067] According to the operation of the elevator system 100 of Embodiment 2 as described above, for external calls of priority objects, even a working car is set as a dispatch candidate. Therefore, appropriate dispatching corresponding to the various uses of the external equipment 7 can be performed.

[0068] 2-2. Specific processing performed in the elevator management device 5 of embodiment 2

[0069] Figure 7 This is a flowchart illustrating the routine of the processing performed in the elevator management device 5 of Embodiment 2. Figure 7 The illustrated routine is executed by the processor 52 of the elevator management device 5 when an external call registration procedure has been performed. This flowchart also illustrates a portion of the car allocation method according to embodiments of this disclosure.

[0070] exist Figure 7 In step S10 of the routine shown, it is determined whether an external call for the external device 7 has been registered. Here, the execution is performed in conjunction with... Figure 4 The process for step S2 in the example shown is the same. As a result, if the determination is not confirmed to be true, the determination in step S10 is repeatedly executed. On the other hand, if the determination in step S10 is confirmed to be true, the process proceeds to step S12.

[0071] In step S12, the attribute determination process performed in the attribute determination unit 26 determines whether the attribute of the external elevator call registered in step S10 is a priority object. Here, the attribute determination unit 26 determines whether the attribute information contained in the external elevator call registration information is a priority object. As a result, if the determination is confirmed to be true, the process proceeds to step S14; if the determination is not confirmed to be true, the process proceeds to step S16.

[0072] In step S14, the dispatching unit 22 sets both the working car and the non-working car as dispatch candidates. Then, the dispatching unit 22 allocates a car to respond to an external call from among the working and non-working cars that have been set as dispatch candidates. When the processing of step S14 is completed, this routine ends.

[0073] In step S16, the working status determination process performed in the car working status determination unit 20 determines whether one or more cars are in a working state. As a result, if all cars are in a working state, the process proceeds to step S18; if at least one car is not in a working state, the process proceeds to step S20.

[0074] In step S18, since there are no non-working cars that should be set as dispatch candidates, the number allocation unit 22 temporarily suspends the allocation of cars to external call elevators. Furthermore, the number allocation unit 22 sends a message indicating the suspension of external call allocation to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 to standby at floor 12. After processing in step S18, the process returns to the processing in step S16.

[0075] On the other hand, in step S20, the car number allocation unit 22 sets non-operating cars as dispatch candidates and allocates cars to respond to external calls from the dispatch candidates. Furthermore, the car number allocation unit 22 sends the allocation number information to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 of the allocation number. This routine ends when step S20 is completed.

[0076] According to the process described above, when an external call from external device 7 has been registered, external calls, which are priority targets, are assigned with the same priority as internal calls. Therefore, appropriate dispatching corresponding to the various uses of external device 7 can be performed.

[0077] 2-3. Variations of Implementation Method 2

[0078] The elevator system 100 of Embodiment 2 can also be modified as described below. Furthermore, the following modifications can also be applied to elevator systems of other embodiments.

[0079] Alternatively, the structure could be as follows: the attribute determination process not only determines whether the attribute of the external elevator call is a priority object, but also further determines the priority order among priority objects. For example, if the external device 7 is a personal mobile device, wearable smart device, wheelchair, or other device held or used by the user, the attribute is the highest priority object among priority objects. Furthermore, if the external device 7 is a robot, the priority of the attribute is set to "high" for the user's guide robot and food delivery robot, the priority of the goods delivery robot is set to "medium", and the priority of the cleaning robot is set to "low". Furthermore, if the external device 7 is a security robot, the priority is set to "low" in normal security situations and "high" in emergency situations. Then, when allocating elevator cars to respond to external elevator calls, the dispatching order is divided into front and back, and the cars are allocated in descending order of priority. According to this processing, flexible allocation corresponding to the priority of external elevator calls can be performed.

[0080] Implementation method 3.

[0081] 3-1. Characteristic functions of the elevator system in Implementation Method 3

[0082] Figure 8 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 3. In addition to the structure of the elevator management device 5 of Embodiment 2, the elevator management device 5 of Embodiment 3 also includes a dispatch limit setting unit 28.

[0083] The dispatch limit setting unit 28 is a function block used to perform dispatch limit setting processing, in which the number of cars that can work simultaneously among one or more cars 1 of the elevator 10 is set. Figure 9 This diagram illustrates an example of the relationship between dispatch limits, the number of working cars, and whether a dispatch is possible. As shown in the diagram, when the dispatch limit is set to one in an elevator with three cars, dispatching can be performed when there are zero working cars, but not when there are one or more working cars. Similarly, when the dispatch limit is set to two, dispatching can be performed when there are one or fewer working cars, but not when there are two or more working cars. The dispatch limit setting unit 28, in its dispatch limit setting process, sets the dispatch limit to a predetermined number of cars, for example. Alternatively, the dispatch limit setting unit 28 sets the dispatch limit to a number of cars corresponding to a predetermined ratio relative to the total number of cars. The elevator allocation unit 22 allocates cars responding to external calls within the dispatch limit range.

[0084] According to the operation of the elevator system 100 of Embodiment 3 as described above, the allocation of car to external elevator calls is limited to the dispatch limit range, thus preventing any compromise to the convenience of ordinary users.

[0085] 3-2. Specific processing performed in the elevator management device 5 of embodiment 3

[0086] Figure 10 This is a flowchart illustrating the routine of the processing performed in the elevator management device 5 of Embodiment 3. Figure 10 The illustrated routine is executed by the processor 52 of the elevator management device 5 when an external call registration procedure has been performed. This flowchart also illustrates a portion of the car allocation method according to embodiments of this disclosure.

[0087] exist Figure 10 In step S30 of the routine shown, the chute limit is set. Here, in the chute limit setting process performed in the chute limit setting unit 28, the chute limit is set to a predetermined number of units.

[0088] When step S30 is executed, the process proceeds to step S32. In steps S32, S34, and S36, the processes related to… Figure 7 The steps S10, S12, and S14 of the example shown are processed in the same way. If the determination is not confirmed in the process of step S34, the process proceeds to step S38.

[0089] In step S38, the elevator dispatching unit 22 determines whether the set dispatch limit is greater than the number of working elevators in the car. If the determination is not confirmed, it is determined that an external elevator call cannot be dispatched, and the process proceeds to step S40. Conversely, if the determination is confirmed, it is determined that an external elevator call can be dispatched, and the process proceeds to step S42.

[0090] In step S40, the elevator number allocation unit 22 temporarily suspends the allocation of cars to external elevator calls. Furthermore, the elevator number allocation unit 22 sends a message indicating the temporary suspension of external elevator call allocation to the external elevator communication unit 24. The external elevator communication unit 24 then notifies the external device 7 to remain on standby at floor 12.

[0091] Furthermore, if the set dispatch threshold is zero, external call assignment will remain suspended even if the car's operating state transitions to a non-operating state. In this case, the caller number assignment unit 22 sends a message indicating that the dispatch threshold is zero to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 that it has not transitioned to a state where dispatching can be performed. When step S40 is completed, the process returns to step S38.

[0092] On the other hand, in step S42, the car number allocation unit 22 sets non-operating cars as dispatch candidates and allocates cars to respond to external calls from the dispatch candidates. Furthermore, the car number allocation unit 22 sends the assigned car number information to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 to allocate a car number. This routine ends when step S42 is completed.

[0093] Based on the processing described above, the dispatch limits can be adjusted according to user activity or time periods. For example, during periods anticipated to be congested, the dispatch limits can be relaxed. This allows for appropriate dispatching based on user activity.

[0094] Implementation method 4.

[0095] 4-1. Characteristic functions of the elevator system in Implementation Method 4

[0096] Figure 11 This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 4. In addition to the structure of the elevator management device 5 of Embodiment 3, the elevator management device 5 of Embodiment 4 also includes a work history storage unit 30 and a dispatch limit calculation unit 32.

[0097] The work history storage unit 30 is a functional block used to store work history information that associates the work history of one or more elevator cars 1 with time. The work history storage unit 30 may be configured, for example, in the storage device 54 of the elevator management device 5. Alternatively, the work history storage unit 30 may be configured in a remote server.

[0098] The pedigree limit calculation unit 32 is a function block that reads working history information from the storage device 54 and calculates the pedigree limits. The pedigree limit calculation unit 32, for example, uses... Figure 10 In step S30 of the flowchart shown, the following paisley limit calculation is performed to set the paisley limit.

[0099] 4-2. Specific processing performed in the elevator management device 5 of embodiment 4

[0100] Figure 12 This is a flowchart illustrating the routine of the dispatch limit calculation process performed in the elevator management device 5 of Embodiment 4. Figure 12 The routine shown is executed by the processor 52 of the elevator management device 5.

[0101] exist Figure 12 In step S50 of the example shown, the padding limit calculation unit 32 sets the time interval for setting the padding limit. Here, the time interval is set, for example, between 5 minutes and 60 minutes.

[0102] Next, in step S52, the dispatch limit calculation unit 32 sets a predetermined past reference period. The reference period is, for example, a period between one week and one year. In step S54, the dispatch limit calculation unit 32 reads the work history information for the set reference period and obtains the work time for each time period using the set time interval.

[0103] In step S56, the fare limit calculation unit 32 calculates the fare limit A for each time period of each day in the reference period. Here, the fare limit calculation unit 32 calculates the fare limit A using, for example, the following formula (1).

[0104] Elevator dispatch limit A = Total number of cars - (Total working time of cars / Time interval)...(1)

[0105] For example, if the total number of elevator cars is three, the time interval is one hour, and the working time of the elevator cars from 10:00 to 11:00 on July 1st is 10 minutes, 15 minutes, and 30 minutes respectively, the dispatch limit A calculated using formula (1) is as follows.

[0106] The limit for the ladder is A = 3 - ((10 + 15 + 30) / 60) = 2.08 units.

[0107] The calculated information of the petabyte limit A is stored in the storage device 54 as petabyte limit information. Figure 13 This is a diagram illustrating an example of graticule limit information. In the example shown, the calculated graticule limits A are stored in association with dates and time periods.

[0108] In step S58, the paisley limit calculation unit 32 uses the paisley limit information to calculate the average value of the paisley limit A for each time period in the reference period as the final paisley limit. Figure 14 This diagram illustrates an example of the paisley threshold calculated for each time period. The paisley threshold calculation unit 32 sets different paisley thresholds for each time period.

[0109] According to the operation of the elevator system 100 of Embodiment 4 described above, the usage status of users in each time period can be reflected in the dispatch limits. As a result, the dispatch limits are relaxed during peak hours, and thus, appropriate dispatching corresponding to the usage status can be carried out without compromising the convenience of users.

[0110] Implementation method 5.

[0111] 5-1. Characteristic functions of the elevator system in Implementation Method 5

[0112] Figure 15This is a block diagram showing the internal structure of the elevator system 100 according to Embodiment 5. In addition to the structure of the elevator management device 5 of Embodiment 4, the elevator management device 5 of Embodiment 5 also includes a service history storage unit 34 and an external call cancellation unit 36.

[0113] The call history storage unit 34 is a functional block used to store historical information of external elevator calls received by the external elevator call communication unit 24. The call history storage unit 34 may be configured, for example, in the storage device 54 of the elevator management device 5. Alternatively, the call history storage unit 34 may be configured in a remote server.

[0114] The external call cancellation unit 36 ​​is a function block used to cancel duplicate external call requests using historical information stored in the service history storage unit 34. This process is referred to hereafter as the "external call cancellation process." The specific procedures of the external call cancellation process will be described below.

[0115] 5-2. Specific processing performed in the elevator management device 5 of embodiment 5

[0116] Figure 16 This is a flowchart illustrating the routine of external elevator call cancellation processing performed in the elevator management device 5 of Embodiment 5. Figure 16 The routine shown is executed by the processor 52 of the elevator management device 5. This flowchart also illustrates a portion of the car allocation method according to embodiments of this disclosure.

[0117] exist Figure 16 In step S60 of the illustrated routine, it is determined whether an external elevator call from external device 7 has been registered. Here, the external elevator call communication unit 24 determines whether external elevator call registration information has been received from the external elevator call registration device 8. As a result, if the determination is not confirmed to be true, the determination in step S50 is repeatedly executed. On the other hand, if the determination in step S60 is confirmed to be true, the process proceeds to step S62.

[0118] In step S62, it is determined whether the external elevator call from the same external device is repeated. Here, the external elevator call cancellation unit 36 ​​determines whether a predetermined number of external elevator calls have been continuously registered from the same external device more than a predetermined number based on historical information stored in the call history storage unit 34. The predetermined number of calls is a threshold used to determine if a device malfunction has occurred. As a result, if the determination is not confirmed, the process proceeds to step S64. On the other hand, if the determination is confirmed, it is determined that some devices have malfunctioned, and the process proceeds to step S66.

[0119] In step S64, the car number allocation unit 22 allocates a car to respond to an external call from the non-operating cars that are set as dispatch candidates. Furthermore, the car number allocation unit 22 sends the allocation information of the assigned car to the external call communication unit 24. The external call communication unit 24 notifies the external device 7 of the allocated car number. This routine ends when step S64 is completed.

[0120] In step S66, the external call cancellation unit 36 ​​cancels the external call and notifies the elevator system 100 administrator. This routine ends when step S66 is completed.

[0121] By following the procedures described above, adverse effects on external elevator calls due to equipment malfunctions can be prevented.

[0122] 5-3. Variations of Implementation Method 5

[0123] The elevator system 100 of embodiment 5 can also be modified as described below.

[0124] Alternatively, in addition to having the structure of the elevator management device 5 of Embodiment 1, Embodiment 2 or Embodiment 3, the elevator management device 5 of Embodiment 5 also has a service history storage unit 34 and an external call cancellation unit 36.

[0125] Label Explanation

[0126] 1: Car; 2: Car control panel; 3: Floor control panel; 4: Elevator control device; 5: Elevator management device; 6: User; 7: External equipment; 8: External call registration device; 10: Elevator; 12: Floor; 20: Car working status determination unit; 22: Number allocation unit; 24: External call communication unit; 26: Attribute determination unit; 28: Dispatch limit setting unit; 30: Working history storage unit; 32: Dispatch limit calculation unit; 34: Acceptance history storage unit; 36: External call cancellation unit; 52: Processor; 54: Storage device; 56: Dedicated hardware; 58: Processing circuit; 100: Elevator system.

Claims

1. An elevator system configured to receive internal and external calls, wherein the internal calls are made by a user operating the elevator control panel, and the external calls are made via a communication network from an external device separate from the elevator control panel. The elevator system has the following features: The elevator allocation unit is configured to allocate cars as dispatch candidates from one or more cars for the internal call or the external call. When the external elevator call is received, the car working status determination unit performs working status determination processing, in which it determines whether one or more cars are in a working state or a non-working state. as well as The attribute determination unit is configured to perform attribute determination processing when the external elevator call is received, wherein the attribute determination processing determines the attribute associated with the priority of the external device. The elevator number allocation unit is configured to receive the determination result of the working status determination process and perform external elevator call allocation process. In this external elevator call allocation process, compared with the elevator in the working status, the elevator in the non-working status is given priority as the elevator dispatch candidate for allocation. Furthermore, in the external elevator call allocation process, it is determined whether to allocate the elevator in the working status as the elevator dispatch candidate based on the attributes. The elevator system also includes a dispatch limit setting unit, which is configured to perform dispatch limit setting processing when the external call is received, wherein the dispatch limit setting process sets a dispatch limit for one or more cars. The caller allocation unit is configured such that, during the external call allocation process, if the dispatch limit is greater than the number of cars in the working state, the non-working cars are allocated as dispatch candidates.

2. The elevator system according to claim 1, wherein, The caller allocation unit is configured to exclude the car in the working state from the dispatch candidates during the external call allocation process.

3. The elevator system according to claim 1, wherein, The dispatch limit setting unit is configured to, in the dispatch limit setting process, obtain work history information that associates the work history of one or more cars with time, and set the dispatch limit according to the work history information for each time period.

4. The elevator system according to claim 2, wherein, The dispatch limit setting unit is configured to, in the dispatch limit setting process, obtain work history information that associates the work history of one or more cars with time, and set the dispatch limit according to the work history information for each time period.

5. The elevator system according to any one of claims 1 to 4, wherein, The elevator system also includes an external call cancellation unit, which is configured to perform external call cancellation processing when the external call is received from the same external device a predetermined number of times or more.

6. A method for allocating elevator cars, wherein in an elevator system configured to accept both internal and external calls, the method allocates a car as a dispatch candidate from one or more cars for the external call, wherein the internal call is made by a user operating the elevator control panel, and the external call is made from an external device separate from the elevator control panel via a communication network, wherein... The car allocation method is configured as follows: Accept the aforementioned external elevator calls; Determine whether one or more car cars are in a working state or a non-working state; Determine the attributes associated with the priority of the external device; An external elevator call allocation process is performed, in which non-working cars are given priority as dispatch candidates compared to cars in the working state. In the external elevator call allocation process, the attribute is used to determine whether to allocate the car in the working state as a dispatch candidate. The car allocation method is configured as follows: Set dispatch limits for the one or more elevator cars. In the external call dispatch process, if the dispatch limit is greater than the number of cars in the working state, the cars in the non-working state are dispatched as candidates.

7. The elevator car allocation method according to claim 6, wherein, The car allocation method is configured such that, in the external call allocation process, the car in the working state is excluded from the dispatch candidates.

8. The elevator car allocation method according to claim 6, wherein, The car allocation method is configured as follows: When setting the dispatch limits, the system obtains work history information that links the work history of one or more cars to time. Based on the work history information, the dispatch limits are set for each time period.

9. The elevator car allocation method according to claim 7, wherein, The car allocation method is configured as follows: When setting the dispatch limits, the system obtains work history information that links the work history of one or more cars to time. Based on the work history information, the dispatch limits are set for each time period.

10. The elevator car allocation method according to any one of claims 6 to 9, The car allocation method is configured such that if the external elevator call is received more than a predetermined number of times consecutively from the same external device, the acceptance of the external elevator call is cancelled.

Images