Elevator group management system, group management method, and recording medium

Abstract

The invention provides an elevator group management system, a group management method and a recording medium. A group management system is provided with: a first landing call reception unit that receives, from a registration device, registration of a first landing call that specifies a landing floor and a travel direction; a second landing call reception unit that, when the first landing call has been registered, receives, from the registration device, registration of a second landing call in which a landing floor and a travel direction common to the first landing call are identified; and a landing call assignment unit that assigns a response to the first landing call to a first assignment car selected from among the plurality of cars when the registration of the first landing call is accepted, and assigns a response to the second landing call to a second assignment car selected from among the plurality of cars when the registration of the second landing call is accepted. A car satisfying a specific condition in which a specific state of the car is determined is selected from among the plurality of cars other than the first allocated car to allocate a response to the second landing call.

Description

Technical Field

[0001] The present invention relates to a technology for a group management system of elevators. Background Art

[0002] Patent Document 1 discloses a technology for prohibiting the reopening of an elevator car based on service conditions. In this technology, when a landing destination button is pressed while the elevator car is responding to a destination call, the elevator car is reopened if the probability of the elevator car stopping at the currently pressed destination call floor is greater than a predetermined probability value. If the probability of the elevator car stopping at the currently pressed destination call floor is less than the predetermined probability value, the currently pressed destination call floor is reassigned to another elevator car.

[0003] Prior art literature

[0004] Patent Document 1: Japanese Patent Application Laid-Open No. 2003-12246 Summary of the Invention

[0005] When making a landing call in an elevator with multiple cars, some users may wish to be assigned a different car from the one assigned to the previous user's landing call, for purposes such as avoiding congestion. However, in the technology of Patent Document 1, in order to improve transportation efficiency, the device determines the action when a landing destination button is pressed while the elevator car is responding to a destination call. Therefore, the user cannot choose to have the currently pressed destination call floor reassigned to another elevator car.

[0006] The present invention is completed to solve the above-mentioned problems, and its purpose is to provide a group management system technology that, when making a floor call for an elevator having multiple cars, can call a car different from the car responding to the floor call of the previous user at the same floor without deteriorating the overall operating efficiency.

[0007] The elevator group management system of the present invention is a group management system for managing landing calls of elevators having multiple cars, wherein the elevator group management system comprises: a first landing call receiving unit, which receives a registration of a first landing call that determines a landing floor and a travel direction from a registration device; a second landing call receiving unit, which receives a registration of a second landing call that determines a landing floor and a travel direction that are common to the first landing call from the registration device when the first landing call has been registered; and a landing call allocating unit, which, when accepting the registration of the first landing call, allocates a response to the first landing call to a first allocated car selected from multiple cars, and, when accepting the registration of the second landing call, allocates a response to the second landing call by selecting a car that meets a specific condition from the multiple cars other than the first allocated car, wherein the specific condition determines a specific state of the car.

[0008] In addition, the group management method of the elevator of the present invention is a group management method for managing the registration of the floor call of the elevator having multiple cars by a computer, wherein the group management method of the elevator includes the following steps: accepting the registration of the first floor call that determines the floor floor and the travel direction from the registration device; when the first floor call has been registered, accepting the registration of the second floor call that determines the floor floor and the travel direction that are common with the first floor call from the registration device; and when the registration of the first floor call is accepted, allocating the response of the first floor call to the first assigned car selected from the multiple cars, and when the registration of the second floor call is accepted, selecting the car that meets specific conditions from the multiple cars other than the first assigned car to allocate the response of the second floor call, wherein the specific condition determines the specific state of the car.

[0009] In addition, the computer-readable recording medium of the present invention stores a group management program for causing a computer to execute management of floor call registrations for an elevator having multiple cars, the group management program being configured to cause a computer to execute the following processing: accepting a registration for a first floor call that determines a floor floor and a direction of travel from a registration device; when the first floor call has been registered, accepting a registration for a second floor call that determines a floor floor and a direction of travel that are common to the first floor call from the registration device; when the registration for the first floor call is accepted, assigning a response to the first floor call to a first assigned car selected from a plurality of cars; when the registration for the second floor call is accepted, assigning a response to the second floor call by selecting a car that satisfies a specific condition from a plurality of cars other than the first assigned car, wherein the specific condition determines a specific state of the car.

[0010] Effects of the Invention

[0011] According to the technology of the present invention, when a landing call is made in an elevator having multiple cars, a car different from the car responding to the landing call of the previous user can be called at the same landing without deteriorating the overall operating efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 This is a block diagram for explaining the configuration of the elevator group management system according to the first embodiment.

[0013] Figure 2 This is a diagram showing an example of a landing call registration device.

[0014] Figure 3 It is a block diagram showing the hardware structure of the group management device.

[0015] Figure 4 This is a flowchart of a process for causing a car information display section to display car information in the group management system according to the first embodiment.

[0016] Figure 5 This is a flowchart of a process for allocating cars to a first landing call in the group management system according to the first embodiment.

[0017] Figure 6 This is a flowchart of a process for allocating cars to a second landing call in the group management system according to the first embodiment.

[0018] Figure 7 It is a diagram showing a modified example of hardware resources of the group management device.

[0019] Figure 8 This is a flowchart of the advance notification process executed in the group management system according to the first embodiment.

[0020] Figure 9 It is a diagram showing a modified example of the landing call registration device.

[0021] Figure 10 It is a diagram showing a modified example of the landing call registration device.

[0022] Figure 11 This is a block diagram showing a modified example of the group management system according to the first embodiment.

[0023] Figure 12 This is a block diagram showing the functions of the group management system according to the second embodiment.

[0024] Figure 13 This is a flowchart of the cancellation process executed in the group management system according to the second embodiment.

[0025] Label Description

[0026] 10: Group management device; 11: Car information acquisition unit; 12: First-floor station call reception unit; 13: Second-floor station call reception unit; 14: Floor call distribution unit; 15: Display information generation unit; 20: Elevator; 22: Car; 24: Control panel; 30: Floor call registration device; 32: First-floor station call input unit; 34: Second-floor station call input unit; 36: Cancellation request unit; 40: Floor display device; 42: Car information display unit; 50: Processor; 52: Memory; 54: Group management program; 56: Data; 60: Dedicated hardware; 62: Processing circuit; 70: Portable terminal; 100: Group management system. DETAILED DESCRIPTION

[0027] Hereinafter, the embodiment will be described with reference to the accompanying drawings. In addition, the same reference numerals are given to the common elements in each figure, and repeated descriptions are omitted.

[0028] 1. Implementation Methods 1.

[0029] 1-1. Configuration of Elevator Group Management System According to Embodiment 1

[0030] Figure 1 This is a block diagram illustrating the configuration of an elevator group management system according to Embodiment 1. Group management system 100 according to this embodiment is applied to a building, such as a structure, having multiple floors. Group management system 100 includes a group management device 10, multiple elevators 20, a landing call registration device 30, and a landing display device 40.

[0031] Each elevator 20 is installed in a building. A shaft for each elevator 20 is provided in the building. A shaft is a space that is long in the vertical direction and spans multiple floors. A landing adjacent to the shaft is provided on each floor. Each elevator 20 includes a car 22 and a control panel 24. The car 22 is a device that travels vertically in the shaft to transport users between multiple floors. The control panel 24 of the elevator 20 is a device that controls the operation of the elevator 20. The operation control in the control panel 24 includes, for example, the operation of the car 22. The car 22 is provided with a destination button (not shown). When a user presses the destination button, the destination floor of the car 22 is registered. The call for the destination floor registered by the destination button is hereinafter referred to as a "car call". In addition, the car 22 is provided with a weighing device (not shown) for calculating the car load.

[0032] The landing call registration device 30 is a registration device that accepts input operations from users who register landing calls. "Land call" here refers to calling the car 22 at a landing. In this example, the landing call registration device 30 is located at each of the multiple floors. The landing call registration device 30 accepts registrations for landing calls that specify the direction of travel to the destination floor. Furthermore, among the landing calls registered by the landing call registration devices 30 located at each landing, the floor on which the landing call registration device 30 is located is identified as the registered landing floor where the user is boarding. That is, the landing call registration device 30 accepts registrations for landing calls that specify the registered landing floor and the direction of travel.

[0033] The landing call registration device 30 includes a first landing call input unit 32 and a second landing call input unit 34 as a portion that receives an input operation by a user who registers a landing call. Figure 2 This figure shows an example of a landing call registration device 30. The first landing call input unit 32 and the second landing call input unit 34 are, for example, landing buttons each including an up button and a down button for designating the travel direction of the car 22. The buttons of the first landing call input unit 32 and the second landing call input unit 34 each have a built-in lamp that can be illuminated independently.

[0034] The first landing call input unit 32 accepts registrations of previously unregistered landing calls. A landing call inputted via the first landing call input unit 32 is hereinafter referred to as a "first landing call." When an operation to register a first landing call is inputted via the first landing call input unit 32, the landing call registration device 30 transmits the inputted first landing call information to the group control device 10. This first landing call information includes information on the registered landing floor and travel direction.

[0035] The second landing call input unit 34 is a unit that accepts registration of a landing call that is common to a previously registered landing call, if a landing call has already been registered. A landing call inputted via the second landing call input unit 34 is hereinafter referred to as a "second landing call." When an operation to register a second landing call is inputted via the second landing call input unit 34, the landing call registration device 30 transmits the inputted second landing call information to the group control device 10. This second landing call information includes information on the registered landing floor and the travel direction.

[0036] The landing display device 40 displays information indicating the status of each elevator 20 to users. In this example, the landing display device 40 is located at each of the multiple floors. The landing display device 40 includes a car information display unit 42. The car information display unit 42 is, for example, a digital sign or a liquid crystal display. The displayed information may include, for example, the floor where each car 22 is located, the car load, and the call registration status for each floor. By referring to the displayed information, users can predict, for example, the arrival time of a car 22 at a specific floor or the number of people in the car upon arrival.

[0037] The group management device 10 performs operations management, etc., within the group management system 100. Operation management within the group management device 10 includes, for example, assigning a landing call to an arbitrary car 22. The elevator 20, including the car 22 to which the landing call is assigned, uses the control panel 24 to cause the car 22 to travel in response to the landing call. That is, after the car 22 travels to the registered landing floor identified by the landing call, it allows the user who registered the call to board the car and travel to the destination floor identified by the car call. The group management device 10 is electrically connected to the landing call registration device 30, the landing display device 40, and the control panel 24 of each elevator 20 in a manner that enables communication. The group management device 10 may also be connected to a communication network such as the Internet or a telephone line network.

[0038] Figure 3 1 is a block diagram illustrating a hardware configuration of a group management device. The group management device 10 is a microcomputer including at least one processor 50 and at least one memory 52. ​​The group management device 10 is also referred to as an information processing device.

[0039] The memory 52 stores a group management program 54 and various data 56 for executing the group management program 54. The processor 50 includes a CPU (Central Processing Unit). The processor 50 reads and executes the group management program 54, thereby implementing the various functions of the group management device 10. The group management program 54 may be recorded on a computer-readable recording medium or stored on a server such as a cloud server that can communicate with the group management device 10.

[0040] Return again Figure 1 As a function realized by reading and executing the group management program 54 by the processor 50, the group management device 10 includes a car information acquisition unit 11, a first floor call receiving unit 12, a second floor call receiving unit 13, a floor call allocating unit 14 and a display information generating unit 15.

[0041] The car information acquisition unit 11 is a functional block for executing a process for acquiring car information indicating the status of the car 22 of each elevator 20. This process is hereinafter referred to as "car information acquisition processing." The car information acquired in the car information acquisition process includes the car position, travel direction, car load, door open / close status, and car call allocation status of each car 22.

[0042] The first-floor call receiving unit 12 is a functional block for executing a process for receiving first-floor call information from the landing call registration device 30. This process is hereinafter referred to as "first-floor call reception processing." The first-floor call information received by the first-floor call receiving unit 12 specifies the registered landing floor and travel direction of the first-floor call.

[0043] The second-landing call receiving unit 13 is a functional block for executing a process for receiving second-landing call information from the landing call registration device 30. This process is hereinafter referred to as "second-landing call reception processing." The second-landing call information received by the second-landing call receiving unit 13 specifies the registered landing floor and travel direction of the second-landing call.

[0044] The landing call allocation unit 14 is a functional block for executing a process for allocating the best car 22 to a landing call. This process is hereinafter referred to as the "allocation process." In the allocation process, when the first landing call reception unit 12 receives the registration of the first landing call, the landing call allocation unit 14 refers to the information of the first landing call and allocates the best car to the first landing call. The "best car" here refers to, for example, the car that arrives at the registered landing floor for the landing call the earliest. The period from the allocation of a car 22 to a landing call until the car 22 arrives at the registered landing floor and completes door closing after opening the door is recorded as the state of the car 22 being "responding." In addition, the car 22 in the state of "responding" to the first landing call is hereinafter referred to as the "first allocated car."

[0045] Furthermore, during the allocation process, when the second landing call receiving unit 13 receives registration of a second landing call, the landing call allocation unit 14 refers to the second landing call information and allocates a car 22 that satisfies specific conditions. The car 22 in the "responding" state to the second landing call is hereinafter referred to as the "second allocated car."

[0046] As a condition for a car that can immediately respond to a second landing call, the specific condition is set as an empty car with its doors closed and the number of passengers in the car being 0. Whether the car 22 is an empty car can be determined, for example, by determining whether the car is stopped with its doors closed and the car load being 0 based on the car information.

[0047] As another example, as a condition for determining that the congestion level in the entire group management system 100 is low, a specific condition is set that the average value of the predicted waiting time of the floor call currently assigned to each elevator car 22 at floors other than the registered floor call of the second floor call is less than the judgment value.

[0048] The display information generation unit 15 is a functional block that generates display information based on the car information acquired during the car information acquisition process. This process is hereinafter referred to as the "display information generation process." The display information generated here includes, for example, car position, travel direction, number of passengers, car call allocation, and predicted waiting time at registered landings, representing the operating status of each car 22. This generated display information is transmitted to the landing display device 40.

[0049] 1-2. Specific Processing Executed by the Group Management Device of Embodiment 1

[0050] Hereinafter, various specific processes executed in the group management device 10 will be described with reference to flowcharts.

[0051] Figure 4 This is a flowchart of a process for causing a car information display section to display car information in the group management system according to the first embodiment. Figure 4 The routine shown is executed by the processor 50 of the group management device 10 executing the group management program 54 stored in the memory 52. ​​The routine also shows a part of the group management method in which the group management system 100 assigns an arbitrary car 22 in response to a landing call registration made by a user.

[0052] In step S100, the car information acquisition unit 11 acquires car information by executing a car information acquisition process. In the following step S102, the display information generation unit 15 executes a display information generation process to generate display information. In the following step S104, the display information generation unit 15 transmits the generated display information to the landing display device 40, and causes the car information display unit 42 to display the car information.

[0053] According to the above processing, the operating status of each car 22 is displayed on the car information display unit 42 of the landing display device 40 installed at the landing. As a result, users at the landing can refer to the displayed information to determine whether to make a landing call. In addition, users who have made a landing call can know the estimated waiting time until the car arrives.

[0054] Figure 5 This is a flowchart of a process for allocating cars to a first landing call in the group management system according to the first embodiment. Figure 5The routine shown is executed by the processor 50 of the group management device 10 executing the group management program 54 stored in the memory 52. ​​The routine also shows a part of the group management method in which the group management system 100 assigns an arbitrary car 22 in response to a landing call registration made by a user.

[0055] In step S110, the first landing call receiving unit 12 determines whether a first landing call registration has been received from the first landing call input unit 32 of the landing call registration device 30. If the determination is not confirmed, the processing of this routine ends. If the determination is confirmed, the processing proceeds to step S112.

[0056] In step S112, the landing call allocating unit 14 allocates the best car as the first allocated car for the received first landing call. Furthermore, in step S114, in response to the acceptance of the first landing call registration, the landing call allocating unit 14 illuminates the button of the first landing call input unit 32 corresponding to the travel direction of the first landing call in the landing call registration device 30 installed at the landing floor where the first landing call is registered.

[0057] According to the above processing, when the registration of the first landing call is accepted, the best car can be assigned as the first assigned car. In addition, since the button of the first landing call input unit 32 is lit when the registration of the first landing call is accepted, the user located on the registration landing floor can know that the landing call has been registered on the registration landing floor.

[0058] Figure 6 This is a flowchart of a process for allocating cars in response to a second landing call in the group management system according to the first embodiment. Figure 6 The routine shown is executed by the processor 50 of the group management device 10 executing the group management program 54 stored in the memory 52. ​​The routine also shows a part of the group management method in which the group management system 100 assigns an arbitrary car 22 to a landing call registration made by a user.

[0059] exist Figure 6 In step S120 of the routine shown, the second landing call receiving unit 13 determines whether a second landing call registration has been received from the landing call registration device 30. If the determination is not confirmed to be successful, the processing of this routine is terminated. If the determination is confirmed to be successful, the processing proceeds to step S122.

[0060] In step S122, the second landing call receiving unit 13 determines whether a first landing call having the same registered landing floor and travel direction as the registered second landing call has been registered and the first assigned car is responding. If the determination is not confirmed to be successful, the processing of this routine is terminated. If the determination is confirmed to be successful, the processing proceeds to step S124.

[0061] In step S124, the landing call allocation unit 14 illuminates the button of the second landing call input unit 34 corresponding to the travel direction of the second landing call in the landing call registration device 30 installed at the registration landing floor of the registered second landing call. After executing step S124, the process proceeds to step S126.

[0062] In step S126, the landing call allocation unit 14 determines, based on the acquired car information, whether there is an empty car with closed doors and no users boarding, among the multiple cars 22. If the determination is confirmed to be successful, the process proceeds to step S130; if the determination is not successful, the process proceeds to step S128.

[0063] In step S128, the landing call allocation unit 14 determines whether the average value of the predicted waiting time for landing calls assigned to each car 22 at floors other than the landing floor for which the second landing call is registered is equal to or less than a determination value. The determination value here can utilize a predetermined value as a threshold value for determining whether the congestion level of the group management system 100 is low. If the determination is confirmed to be established, the process proceeds to step S130; if the determination is not established, the process proceeds to step S132.

[0064] In step S130, the landing call allocator 14 allocates a car different from the first allocated car in the current response as the second allocated car in response to the second landing call registration. Typically, if there is a vacant car among the multiple cars 22, the landing call allocator 14 allocates the vacant car as the second allocated car. Alternatively, if there is no vacant car among the multiple cars 22, the landing call allocator 14 allocates the best car among the multiple cars 22 as the second allocated car. When the processing of step S130 is completed, this routine ends.

[0065] In step S132, the landing call allocating section 14 waits for the timing when the responding car starts closing its door at the registered landing floor, and newly allocates the best car to the second landing call registration. When the processing of step S132 is completed, this routine ends.

[0066] According to the processing of the group management system 100 of the first embodiment described above, when a second landing call is registered, the timing of assigning the second assigned car is changed according to the operating status of each car 22. This allows a car 22 to be immediately assigned to a second landing call when there are few users in the multiple elevators 20, and allows a car 22 to be assigned at a staggered timing when there are many users in the multiple elevators 20. Therefore, it is possible to meet the needs of users who wish to call a car different from the one currently using the car, without degrading overall operating efficiency.

[0067] 1-3. Modifications

[0068] The group management system 100 of the first embodiment may also be modified as described below. These modifications are also applicable to group management systems of other embodiments described below.

[0069] 1-3-1. Hardware Resources of the Group Management Device 10

[0070] Figure 7 FIG. 1 is a diagram showing a modified example of hardware resources of a group management device. Figure 7 In the illustrated example, the group management device 10 includes, for example, a processing circuit 62 including a processor 50 , a memory 52 , and dedicated hardware 60 . Figure 7 The example in which a portion of the functions of the group management device 10 are implemented by dedicated hardware 60 is shown. All functions of the group management device 10 may also be implemented by dedicated hardware 60. Dedicated hardware 60 may be a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0071] Furthermore, all or part of the functions of the group control device 10 of the group control system 100 may be mounted on the hall call registration device 30 , the hall display device 40 , or the elevator 20 .

[0072] 1-3-2. Hall call distribution unit 14

[0073] Alternatively, the landing call assignment unit 14 may allow the user to determine in advance whether the second landing call can be assigned immediately. Typically, if the second landing call can be assigned immediately, the landing call assignment unit 14 executes a process of flashing the corresponding landing button on the second landing call input unit 34 in advance. This process is hereinafter referred to as "preliminary notification processing." Figure 8This is a flowchart of the advance notification process executed in the group management system according to the first embodiment. Figure 8 The routine shown is executed by the processor 50 of the group management device 10 executing the group management program 54 stored in the memory 52. ​​The routine also shows a part of the group management method in which the group management system 100 assigns an arbitrary car 22 to a landing call registration made by a user.

[0074] exist Figure 8 In step S140 of the routine shown, the landing call allocating section 14 determines whether the first landing call has been registered. If the determination is not confirmed, the processing of this routine is terminated. If the determination is confirmed, the processing proceeds to step S142.

[0075] In step S142, the landing call allocation unit 14 determines, based on the acquired car information, whether there is an empty car with closed doors and no passengers among the multiple cars 22. If the determination is confirmed to be successful, the process proceeds to step S146; if the determination is not successful, the process proceeds to step S144.

[0076] In step S144, the landing call allocation unit 14 determines whether the average value of the predicted waiting time for landing calls assigned to each car 22 at floors other than the registered landing floor for the first registered landing call is equal to or less than a determination value. The determination value here can utilize a predetermined value as a threshold value for determining whether the congestion level of the group management system 100 is low. If the determination is confirmed to be established, the process proceeds to step S146; if the determination is not established, the process proceeds to step S148.

[0077] In step S146, the landing call allocation unit 14 flashes the button corresponding to the travel direction of the first landing call on the second landing call input unit 34 of the landing call registration device 30 located at the registration landing floor of the registered first landing call. On the other hand, in step S148, the landing call allocation unit 14 unlights the button corresponding to the travel direction of the first landing call on the second landing call input unit 34 of the landing call registration device 30 located at the registration landing floor of the registered first landing call. After executing step S146 or S148, the processing of this routine ends.

[0078] The advance notification process described above can determine in advance whether the second landing call will be assigned immediately, so the user can easily determine whether there is a high possibility that two cars will arrive successively when the button of the second landing call input unit 34 is pressed.

[0079] 1-3-3. Hall call registration device 30

[0080] The structure of the landing call registration device 30 is not limited to Figure 2 That is, the first landing call input unit 32 and the second landing call input unit 34 of the landing call registration device 30 may have Figure 2 Different button shapes.

[0081] Furthermore, the first landing call input unit 32 and the second landing call input unit 34 of the landing call registration device 30 may be of a type that accepts landing call registrations designating a destination floor. Figure 9 and Figure 10 It is a diagram showing a modified example of the landing call registration device. Figure 9 and Figure 10 The landing call registration device 30 shown is configured as a touch panel display provided at the landing. The first landing call input unit 32 is configured with buttons for selecting the displayed destination floor. The first landing call input unit 32 is unlit if a destination floor is registered, and is lit if no destination floor is registered. Figure 9 In the illustrated example, the unlit indications of the third and fourth floors for the first floor call have already been registered in the first floor call input unit 32, and the lit indication of the second floor for the first floor call can be registered.

[0082] The second landing call input unit 34 displays the state in which the first landing call is registered at the landing, that is, the state in which at least one destination floor is registered in the first landing call input unit 32. Figure 9 In the example shown, the first floor call input unit 32 can register only the second floor as the destination floor, and the second floor call input unit 34 can register the second to fourth floors as the destination floors. In such a situation, a user who wants to go to the second floor can press the first floor call input unit 32 or the second floor call input unit 34. When the user presses the second floor button of the first floor call input unit 32, the user rides the first assigned car. At this time, the second floor button of the first floor call input unit 32 is switched to an off display. On the other hand, when the user presses the second floor button of the second floor call input unit 34, a new second floor call is registered, and the display changes to Figure 10 The status of the screen shown. Figure 10 In the screen shown, a further second landing call can be made. In addition, a restriction may be imposed on the number of second assigned cars that can be registered in the second landing call input unit 34, such as a maximum of two cars.

[0083] 1-3-4. Landing display device 40

[0084] The landing display device 40 can also be used with Figure 9 and Figure 10 The landing call registration device 30 is integrally formed with the touch panel display shown. In this case, the car information display section 42 is configured as a portion that causes the touch panel display of the landing display device 40 to display car information. Figure 9 and Figure 10 In the display, the predicted time until arrival at the landing and the number of passengers are displayed as car information. According to this structure, the user who enters the destination floor on the touch panel display of the landing display device 40 can confirm the status of each car 22 on the screen and determine whether to make a second landing call.

[0085] 1-3-5. Functions of the landing call registration device 30 and the landing display device 40

[0086] The group management system 100 may be configured so that a landing call can be executed from a mobile terminal held by a user. Figure 11 This is a block diagram showing a modified example of the group management system according to the first embodiment. Figure 11 The group management system 100 of the illustrated modified example includes a portable terminal 70 held by a user. The portable terminal 70 is, for example, a portable terminal device such as a smartphone or a tablet computer equipped with a wireless communication function. The portable terminal 70 is connected to the group management device 10 via a communication network such as the Internet or a telephone line. In this example, the portable terminal 70 has a touch panel display that has a display function for displaying information on an input screen to the user and an operation function for accepting input from the user. The portable terminal 70 is installed with an elevator call registration application for registering the landing floor and destination floor of the elevator user. When the user activates the elevator call registration application on the portable terminal 70, the functions of the first landing call input unit 32, the second landing call input unit 34, and the car information display unit 42 are realized.

[0087] 2. Implementation Method 2.

[0088] In the second embodiment, the differences from the example disclosed in the first embodiment are described in particular detail. For features not described in the second embodiment, any features of the example disclosed in the first embodiment can be adopted.

[0089] 2-1. Functional Structure of Group Management System in Implementation 2

[0090] The group management system 100 according to the second embodiment is characterized in that unnecessary processing of second-floor calls is canceled. Figure 12This is a block diagram illustrating the functions of the group management system according to Embodiment 2. The landing call registration device 30 of the group management system 100 further includes a cancellation request unit 36. The cancellation request unit 36 ​​is a portion that receives a user's operation to cancel a second landing call. Typically, upon receiving an operation requesting cancellation of the second landing call through the second landing call input unit 34, the cancellation request unit 36 ​​transmits information regarding the input cancellation request to the group management device 10. The cancellation request operation may be, for example, pressing a lighted button on the second landing call input unit 34. The cancellation request information here includes information regarding the cancellation request floor and travel direction corresponding to the button. Furthermore, upon receiving an operation requesting cancellation of the second landing call, the landing call registration device 30 turns off the light of the pressed button.

[0091] If there is a registration of a second landing call corresponding to the received cancellation request, the landing call assignment unit 14 of the group control device 10 cancels the registration of the second landing call and the assignment of the second car. This processing is hereinafter referred to as "cancellation processing."

[0092] 2-2. Specific Processing Executed by the Group Management System of Implementation Method 2

[0093] Figure 13 This is a flowchart of the cancellation process executed in the group management system according to the second embodiment. Figure 13 The routine shown is executed by the processor 50 of the group management device 10 executing the group management program 54 stored in the memory 52. Figure 13 The cancellation handling routine shown is the same as Figure 5 and Figure 6 The illustrated allocation processing routines are executed independently.

[0094] exist Figure 13 In step S200 of the routine shown, the landing call allocating unit 14 determines whether cancellation request information has been received from the cancellation request unit 36 ​​of the landing call registration device 30. If the determination is confirmed to be successful, the process proceeds to step S202. If the determination is not successful, the process of this routine ends.

[0095] In step S202, the landing call allocation unit 14 determines whether a second landing call has been registered for the cancellation request floor and travel direction included in the cancellation request information. If the determination is successful, the process proceeds to step S204. If not, the process of this routine ends.

[0096] In step S204, the landing call allocating section 14 cancels the allocation to the second car when the registered second landing call is to be canceled and there is a second allocated car that is responding to the second landing call. When the processing of step S204 is completed, the processing of this routine ends.

[0097] According to the group management system 100 of the second embodiment described above, it is possible to accept a user's cancellation request and cancel the corresponding second landing call. This can suppress unnecessary calls and prevent a deterioration in overall operating efficiency.

[0098] 2-3. Modifications

[0099] The group management system 100 of the second embodiment may also be modified as described below.

[0100] The cancellation request unit 36 ​​may be provided at a location other than the landing call registration device 30. Specifically, for example, if a camera is installed at each floor landing, the camera can be used to determine whether or not there are users on each floor. Therefore, the cancellation request unit 36 ​​may be configured as a unit that transmits cancellation request information to the group control device 10 when it is determined, based on data captured by the camera, that a second landing call is unnecessary. Furthermore, a situation in which a second landing call is unnecessary may occur, for example, when all users at a landing on a floor for which a second landing call is registered have boarded the first assigned car that is currently responding to a first landing call.

[0101] Alternatively, when a cancel button is provided in the interior of the car 22, the cancel request unit 36 ​​may be configured as a portion that receives an operation of the cancel button. With such a configuration, when a user who has registered a second landing call has already boarded the first assigned car that is responding to the first landing call, the user can request cancellation of the second landing call by pressing the cancel button from inside the car 22.

[0102] 4. Others

[0103] While preferred embodiments have been described in detail above, the present invention is not limited to the above-described embodiments and the like, and various modifications and substitutions may be made to the above-described embodiments and the like without departing from the scope of the claims.

[0104] Hereinafter, various aspects of the present invention will be described in general as supplementary notes.

[0105] (Note 1)

[0106] An elevator group management system is a group management system for managing landing calls of an elevator having a plurality of cars, wherein the elevator group management system comprises:

[0107] a first-floor call receiving unit for receiving a first-floor call registration in which a landing floor and a travel direction are specified from the registration device;

[0108] a second landing call receiving unit for receiving, when the first landing call has already been registered, a registration of a second landing call specifying the same landing floor and the same travel direction as the first landing call from the registration device; and

[0109] A floor call allocation unit, which, upon accepting the registration of the first floor call, allocates the response of the first floor call to a first allocated car selected from the multiple cars, and, upon accepting the registration of the second floor call, allocates the response of the second floor call by selecting a car that meets a specific condition from the multiple cars other than the first allocated car, wherein the specific condition determines a specific state of the car.

[0110] (Note 2)

[0111] The elevator group management system according to Supplementary Note 1, wherein:

[0112] The specific conditions include: the car is stopped with its doors closed in a state where the number of users in the car is zero.

[0113] (Note 3)

[0114] The elevator group management system according to Supplementary Note 1, wherein:

[0115] The specific condition includes that, at floors other than the landing floor corresponding to the second landing call, an average value of predicted waiting times of currently assigned landing calls is smaller than a determination value.

[0116] (Note 4)

[0117] The elevator group management system according to any one of Supplementary Notes 1 to 3, wherein:

[0118] The landing call allocating section allocates the second landing call to a car selected from the plurality of cars after the first allocated car with its door open at the landing floor of the first landing call starts closing its door, if there is no car satisfying the specific condition.

[0119] (Note 5)

[0120] The elevator group management system according to any one of Supplementary Notes 1 to 4, wherein:

[0121] The elevator group management system includes a cancellation request unit that receives a cancellation request for canceling car allocation for the second landing call received by the second landing call receiving unit.

[0122] The landing call assigning section is configured to cancel the car assignment for the second landing call in response to the cancellation request.

[0123] (Note 6)

[0124] The elevator group management system according to Supplementary Note 5, wherein:

[0125] The second landing call receiving unit is a landing button provided at each of the landings on a plurality of floors.

[0126] The cancellation request unit is configured to accept the cancellation request for the second landing call in response to the landing button corresponding to the second landing call being pressed.

[0127] (Note 7)

[0128] The elevator group management system according to Supplementary Note 5, wherein:

[0129] The cancellation request section is configured to accept the cancellation request in response to a cancel button provided inside the car being pressed.

[0130] (Note 8)

[0131] The elevator group management system according to any one of Supplementary Notes 1 to 7, wherein:

[0132] The elevator group management system has:

[0133] a car information acquiring unit that acquires car information indicating states of the plurality of cars; and

[0134] A display information generating unit generates display information to be displayed on a display device based on the car information.

[0135] (Note 9)

[0136] The elevator group management system according to Supplementary Note 8, wherein:

[0137] The display information includes any one of the car position, the travel direction, the number of passengers, the allocation status of landing calls, and the predicted waiting time at each landing floor of each of the plurality of cars.

[0138] (Note 10)

[0139] The elevator group management system according to any one of Supplementary Notes 1 to 9, wherein:

[0140] The registration device is a landing call registration device installed at the landings of a plurality of floors.

[0141] The landing call registration device includes:

[0142] a first landing call input unit for inputting registration of the first landing call; and

[0143] The second landing call input unit is used to input registration of the second landing call.

[0144] (Note 11)

[0145] The elevator group management system according to Supplementary Note 10, wherein:

[0146] The second landing call input unit includes an up button and a down button for designating the travel direction.

[0147] The up button and the down button are configured to be lighted and displayed separately.

[0148] The floor call allocation unit is configured such that, when the first floor call has been registered, if there is a car that meets a specific condition among the multiple cars other than the first allocated car, in the second floor call input unit of the floor floor of the registered first floor call, the button of the up button and the down button corresponding to the travel direction of the first floor call is flashed, wherein the specific condition determines the specific state of the car.

[0149] (Note 12)

[0150] The elevator group management system according to any one of Supplementary Notes 1 to 9, wherein:

[0151] The registration device is a portable terminal held by the user,

[0152] The mobile terminal is configured to display an input screen for registering the first landing call or the second landing call,

[0153] Registration of the first landing call or the second landing call is accepted in accordance with an input operation from the input screen.

[0154] (Note 13)

[0155] An elevator group management method is provided, wherein a computer is used to manage registration of landing calls of an elevator having multiple cars, wherein the elevator group management method comprises the following steps:

[0156] The registration device receives the registration of the first landing call that specifies the landing floor and travel direction;

[0157] In a state where the first landing call has already been registered, receiving registration of a second landing call that specifies the same landing floor and the same travel direction as the first landing call from the registration device; and

[0158] When the registration of the first floor call is accepted, the response to the first floor call is assigned to the first assigned car selected from the multiple cars. When the registration of the second floor call is accepted, the response to the second floor call is assigned by selecting a car that meets a specific condition from the multiple cars other than the first assigned car, wherein the specific condition determines a specific state of the car.

[0159] (Note 14)

[0160] A group management program causes a computer to execute processing for managing registration of landing calls of an elevator having a plurality of cars, the program being configured to cause the computer to execute the following processing:

[0161] The first landing call registration that specifies the landing floor and travel direction is received from the registration device.

[0162] In a state where the first landing call has already been registered, a registration of a second landing call specifying the same landing floor and the same travel direction as the first landing call is received from the registration device;

[0163] When the registration of the first floor call is accepted, the response to the first floor call is assigned to the first assigned car selected from the multiple cars. When the registration of the second floor call is accepted, the response to the second floor call is assigned to a car that meets a specific condition from the multiple cars other than the first assigned car, wherein the specific condition determines a specific state of the car.

Claims

1. An elevator group management system for managing landing calls of an elevator having a plurality of cars, wherein: The elevator group management system has: a first-floor call receiving unit for receiving a first-floor call registration in which a landing floor and a travel direction are specified from the registration device; a second landing call receiving unit for receiving, when the first landing call has already been registered, a registration of a second landing call specifying the landing floor and the travel direction common to the first landing call from the registration device; as well as A floor call allocation unit, which, upon accepting the registration of the first floor call, allocates the response of the first floor call to a first allocated car selected from the multiple cars, and, upon accepting the registration of the second floor call, allocates the response of the second floor call by selecting a car that meets a specific condition from the multiple cars other than the first allocated car, wherein the specific condition determines a specific state of the car.

2. The elevator group management system according to claim 1, wherein: The specific conditions include: the car is stopped with its doors closed in a state where the number of users in the car is zero.

3. The elevator group management system according to claim 1, wherein: The specific condition includes that, at floors other than the landing floor corresponding to the second landing call, an average value of predicted waiting times of currently assigned landing calls is smaller than a determination value.

4. The elevator group management system according to any one of claims 1 to 3, wherein: The landing call allocating section allocates the second landing call to a car selected from the plurality of cars after the first allocated car with its door open at the landing floor of the first landing call starts closing its door, if there is no car satisfying the specific condition.

5. The elevator group management system according to any one of claims 1 to 3, wherein: The elevator group management system includes a cancellation request unit that receives a cancellation request for canceling car allocation for the second landing call received by the second landing call receiving unit. The landing call assigning section is configured to cancel the car assignment for the second landing call in response to the cancellation request.

6. The elevator group management system according to claim 5, wherein: The second landing call receiving unit is a landing button provided at each of the landings on a plurality of floors. The cancellation request unit is configured to accept the cancellation request for the second landing call in response to the landing button corresponding to the second landing call being pressed.

7. The elevator group management system according to claim 5, wherein: The cancellation request section is configured to accept the cancellation request in response to a cancel button provided inside the car being pressed.

8. The elevator group management system according to any one of claims 1 to 3, wherein: The elevator group management system has: a car information acquiring unit that acquires car information indicating states of the plurality of cars; and A display information generating unit generates display information to be displayed on a display device based on the car information.

9. The elevator group management system according to claim 8, wherein: The display information includes any one of the car position, the travel direction, the number of passengers, the allocation status of landing calls, and the predicted waiting time at each landing floor of each of the plurality of cars.

10. The elevator group management system according to any one of claims 1 to 3, wherein: The registration device is a landing call registration device installed at the landings of a plurality of floors. The landing call registration device includes: a first landing call input unit for inputting registration of the first landing call; as well as The second landing call input unit is used to input registration of the second landing call.

11. The elevator group management system according to claim 10, wherein: The second landing call input unit includes an up button and a down button for designating the travel direction. The up button and the down button are configured to be lighted and displayed separately. The floor call allocation unit is configured such that, when the first floor call has been registered, if there is a car that meets a specific condition among the multiple cars other than the first allocated car, in the second floor call input unit of the floor floor of the registered first floor call, the button of the up button and the down button corresponding to the travel direction of the first floor call is flashed, wherein the specific condition determines the specific state of the car.

12. The elevator group management system according to any one of claims 1 to 3, wherein: The registration device is a portable terminal held by the user, The mobile terminal is configured to display an input screen for registering the first landing call or the second landing call, Registration of the first landing call or the second landing call is accepted in accordance with an input operation from the input screen.

13. A method for group management of elevators, wherein a computer manages registration of landing calls of an elevator having a plurality of cars, wherein: The elevator group management method comprises the following steps: The registration device receives the registration of the first landing call that specifies the landing floor and travel direction; In a state where the first landing call has already been registered, receiving registration of a second landing call that specifies the same landing floor and the same travel direction as the first landing call from the registration device; as well as When the registration of the first floor call is accepted, the response to the first floor call is assigned to the first assigned car selected from the multiple cars. When the registration of the second floor call is accepted, the response to the second floor call is assigned by selecting a car that meets a specific condition from the multiple cars other than the first assigned car, wherein the specific condition determines a specific state of the car.

14. A computer-readable recording medium having recorded thereon a group management program for causing a computer to execute management of landing call registrations of an elevator having a plurality of cars, the group management program being configured to cause the computer to execute the following processing: The first landing call registration that specifies the landing floor and travel direction is received from the registration device. In a state where the first landing call has already been registered, a registration of a second landing call specifying the same landing floor and the same travel direction as the first landing call is received from the registration device; When the first landing call registration is accepted, the response to the first landing call is assigned to a first assigned car selected from the plurality of cars, and when the second landing call registration is accepted, the response to the second landing call is assigned to a car that satisfies a specific condition from among the plurality of cars other than the first assigned car, wherein The specific condition determines a specific state of the car.

Images