JP7205610B1 - ELEVATOR MANAGEMENT DEVICE, CONTROL METHOD OF ELEVATOR MANAGEMENT DEVICE, AND ELEVATOR MANAGEMENT SYSTEM - Google Patents

Abstract

An elevator management device capable of allocating users and self-propelled devices in a state in which the possibility of the self-propelled devices coming into contact with users is reduced. An elevator management device (1) includes a first specifying unit (111) for specifying a departure floor and a destination floor of a self-propelled device based on a destination floor call signal from the self-propelled device; a second identification unit (112) for identifying the departure floor and destination floor of the user based on the destination floor call signal received prior to the floor call signal and issued by the user's operation; When the direction from the floor to the destination floor is the same as the direction from the departure floor to the destination floor of the self-propelled device, and when the boarding section of the user is included in the boarding section of the self-propelled device, and a first allocation unit (114) for allocating the self-propelled device to the elevator. [Selection drawing] Fig. 2

Description

The present invention relates to an elevator management device that manages elevators having a destination floor registration function, a control method for the elevator management device, and an elevator management system.

Patent Literature 1 discloses an autonomous mobile body control device that notifies a device provided on the autonomous mobile body of information indicating whether a user or an autonomous mobile body is getting into or out of an elevator car.

Patent Literature 2 discloses an elevator system that includes a detector that detects the presence of people in an elevator car and a boarding/alighting area instruction input section that detects the presence of people in an elevator boarding/alighting area. The elevator system can be set to a robot-only mode in which the robot has exclusive use of the elevator car.

WO2018/066054 JP 2009-234716 A

In the case of the autonomous mobile body control device disclosed in Patent Document 1, even if the user is alerted to contact with the self-propelled device, there is a possibility that the user will be contacted by the movement of the self-propelled device. There is In the case of the elevator system of Patent Document 2, there is a problem that the self-propelled device is not assigned to the same car as the user, and the elevator cannot be used efficiently.

One aspect of the present invention is to reduce the possibility of contact between the self-propelled device and the user when the robot is allowed to ride in the same elevator as the user. to an elevator, a control method for the elevator management device, and an elevator management system.

In order to solve the above problems, an elevator management device according to one aspect of the present invention is an elevator management device that manages the operation of an elevator, and is based on a destination floor call signal from a self-propelled device. a device-using floor identifying unit that identifies the departure floor and destination floor of the traveling device; a user floor identification unit that identifies the departure floor and destination floor of the user, the direction from the departure floor of the user to the destination floor of the user as the end point, and the departure floor of the self-propelled device as the starting point When the direction of the self-propelled device with the destination floor as the end point is the same direction, and the section from the user's departure floor to the user's destination floor as the end point is the self-propelled device and an assigning unit that assigns the self-propelled device to the elevator when it is included in a section starting from the departure floor of and ending at the destination floor of the self-propelled device.

An elevator management apparatus according to an aspect of the present invention includes a user floor identification unit that identifies a departure floor and a destination floor of the user based on a destination floor call signal generated by an operation of the user; a device utilization floor identification unit that identifies a departure floor and a destination floor of the self-propelled device based on a destination floor call signal from the self-propelled device received prior to the floor call signal; and a departure of the user. When the direction starting from the floor and ending at the destination floor of the user and the direction starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device are the same direction, A section starting from the departure floor of the user and ending at the destination floor of the user is included in a section starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device. an assigning unit that assigns the user to the elevator, if the case.

A control method for an elevator management device according to one aspect of the present invention is a control method for an elevator management device that manages the operation of an elevator, wherein, based on a destination floor call signal from the self-propelled device, and a destination floor call signal received prior to the destination floor call signal and issued by the user's operation, the departure floor of the user and a user floor specifying step of specifying a destination floor, a direction starting from the departure floor of the user and ending at the destination floor of the user, and the self-propelled device starting from the departure floor of the self-propelled device When the direction with the destination floor of the device as the end point is the same direction, and the section starting from the user's departure floor and ending at the user's destination floor is the departure floor of the self-propelled device. and an assigning step of assigning the self-propelled device to the elevator when included in a section starting from and ending at the destination floor of the self-propelled device.

A control method for an elevator management apparatus according to an aspect of the present invention includes a user floor specifying step of specifying a departure floor and a destination floor of the user based on a destination floor call signal issued by an operation of the user. a device utilization floor specifying step of specifying a departure floor and a destination floor of the self-propelled device based on a destination floor call signal from the self-propelled device received prior to the destination floor call signal; The direction from the departure floor of the user to the destination floor of the user and the direction from the departure floor of the self-propelled device to the destination floor of the self-propelled device are the same direction. and a section starting from the departure floor of the user and ending at the destination floor of the user is a section starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device. and an assigning step of assigning the user to the elevator.

An elevator management system according to an aspect of the present invention includes the elevator management device described above and the self-propelled device.

According to one aspect of the present invention, when the robot is allowed to ride in the same elevator as the user, the self-propelled device or Users can be assigned to elevators.

It is a figure showing an example of composition of an elevator management system concerning an embodiment of the present invention. It is a figure which shows an example of a structure of an elevator management apparatus. It is a figure which shows an example of a structure of a self-propelled apparatus. It is a figure which shows an example of a structure of an elevator control apparatus and an elevator. 4 is a flow chart showing an example of the flow of processing performed by the elevator management device; 10 is a flowchart showing an example of the flow of processing of subroutine A; 10 is a flowchart showing an example of the flow of processing of subroutine B; 1 is a diagram for explaining an outline of an elevator management system; FIG. 1 is a diagram for explaining an outline of an elevator management system; FIG. 1 is a diagram for explaining an outline of an elevator management system; FIG.

An embodiment of the present invention will be described in detail below.

(Overview of Elevator Management System 100)
FIG. 1 is a diagram showing an example of the configuration of an elevator management system 100 according to this embodiment. The elevator management system 100 is a system that manages an elevator 4 provided in a building having multiple floors. The elevator management system 100 is a system capable of notifying the user H of the elevator 4 having a destination floor registration function and the self-propelled device 6 such as a robot of the optimum number. Hereinafter, the user H and the self-propelled device 6 will be collectively referred to as use targets. Note that the number of users H registered by one destination floor registration operation, ie, allocation request operation described later, may be one or may be plural. The number of self-propelled devices 6 registered at one time may be one, or may be plural. A case will be described below in which the number of users H to be registered at one time is one and the number of self-propelled devices 6 to be registered at one time is one.

Here, the "destination floor registration function" is to allocate the optimum elevator according to the destination floor of the use target, and guide the use target to the optimum elevator as the elevator that the use target will board. It is a function that can effectively shorten the time to wait for Also, the destination floor registration function can shorten the time required for the object to be used to arrive at the destination floor. The "optimum number" is the elevator number of the elevator 4 assigned to each allocation request operation by the elevator management device 1 of the elevator management system 100 having a destination floor registration function in response to the allocation request operation of the utilization target. . The "elevator number to be assigned to the allocation request operation" is intended to be the elevator number of the elevator 4 determined by the elevator management device 1 as the optimum number to be used by the utilization target who performed the allocation request operation. A case where the elevator 4 has a plurality of elevators will be described below as an example, but the present invention is not limited to an elevator having a plurality of elevators. FIG. 1 illustrates an elevator 4 having multiple cars. In the following, a case where the elevators 4a to 4c are No. 1 to No. 3 respectively will be described as an example.

Further, the "allocation request operation" is an operation for registering in the elevator management device 1 allocation request data in which the destination floor is included in the utilization target in advance. The "allocation request operation" is also called "destination floor call registration operation". When the target of use is user H, the assignment request operation is, for example, an operation in which user H inputs a desired destination floor or the like to the destination floor call registration device 2 installed at the departure floor. good too. The destination floor call registration device 2 may transmit to the elevator management device 1 information including information indicating the input destination floor and information on the floor where the destination floor call registration device 2 is installed. The user H may directly transmit the allocation request data to the elevator management device 1 using a mobile terminal such as a smart phone without going through the destination floor call registration device 2 . When the object of use is the self-propelled device 6, the assignment request operation may be performed by the self-propelled device 6 directly transmitting the assignment request data to the elevator management device 1 to request the assignment.

The self-propelled device 6 in the elevator management system 100 may be an automatic transport device, a self-propelled cleaning device, other multifunctional robots, etc., which are pre-installed in the building. Alternatively, the self-propelled device 6 may be a dedicated device deployed in the building in accordance with the introduction of the elevator management system 100 . In addition to the self-propelled function, the self-propelled device 6 may have a function of notifying the user H of a message (for example, a voice output function, a screen display function, etc.).

(Technical Concept of Elevator Management System 100)
First, the technical concept of the elevator management system 100 will be explained using FIGS. 8 to 10. FIG. 8 to 10 are diagrams for explaining an outline of the elevator management system 100. FIG. In FIGS. 8 to 10, the direction from the departure floor of the self-propelled device 6 to the destination floor is the same as the direction from the departure floor of the user H to the destination floor. exemplified.

In the example of FIG. 8, the self-propelled device 6 gets on on the 2nd floor and gets off on the 5th floor. User H gets on the car on the 3rd floor and gets off on the 4th floor. Assume that the self-propelled device 6 and the user H are assigned the first machine as a result of performing the allocation request operation, respectively. In this case, when the user H gets on from the 3rd floor, the self-propelled device 6 has already got on from the 2nd floor, so the self-propelled device 6 does not move. Since the self-propelled device 6 gets off on the 5th floor, the self-propelled device 6 does not move when the user H gets off on the 4th floor. In this way, in a situation where the user H and the self-propelled device 6 ride on the same elevator 4, if the elevator 4 is allocated so that the self-propelled device 6 does not move when the user H gets on and off, The possibility of the self-propelled device 6 contacting the user H can be reduced.

On the other hand, in the example of FIG. 9, the self-propelled device 6 gets on on the 2nd floor and gets off on the 5th floor. User H gets on at 1F and gets off at 4F. Assume that the self-propelled device 6 and the user H are assigned the first machine as a result of performing the allocation request operation, respectively. In this case, since the user H has already boarded from the 1st floor, the self-propelled device 6 may come in contact with the user H when the self-propelled device 6 gets on from the 2nd floor. Incidentally, when the self-propelled device 6 gets off on the 5th floor, the user H has already got off on the 4th floor, so the self-propelled device 6 does not contact the user H.

Also, in the example of FIG. 10, the self-propelled device 6 gets on at 2F and gets off at 5F. User H gets on on the 4th floor and gets off on the 6th floor. Assume that the self-propelled device 6 and the user H are assigned the first machine as a result of performing the allocation request operation, respectively. In this case, when the self-propelled device 6 gets on from the 2nd floor, the user H does not get on the first car, so the self-propelled device 6 does not come into contact with the user H. However, since the user H gets off the vehicle on the 6th floor, the user H is on board when the self-propelled device 6 gets off on the 5th floor, and there is a possibility that the user H will come into contact with the self-propelled device.

As shown in FIGS. 9 and 10, when the self-propelled device 6 gets on or off the vehicle while the user H is on board, the self-propelled device 6 moves to the position where the user H is riding. may come into contact with Therefore, contact between the self-propelled device 6 and the user H may injure the user H or damage the self-propelled device 6 . Therefore, it is required to assign the self-propelled device 6 and the user H to the elevator 4 so that such a situation does not occur.

When the self-propelled device 6 and the user H are allowed to ride together in the same car, the inventors have found that the boarding section of the user H is the boarding section of the self-propelled device 6, as shown in FIG. We have found that it is necessary to assign the self-propelled device 6 and the user H to the machine so that it is included. When this assignment is made, the self-propelled device 6 does not get on or off the vehicle while the user H is on board, and the self-propelled device 6 can be used when getting on and off the vehicle. Person H is not contacted. That is, in a situation where the self-propelled device 6 and the user H can board the same car, the possibility of the self-propelled device 6 contacting the user H while the user H is boarding can be reduced. The elevator management device 1 can allocate the self-propelled device 6 to the elevator to which the user H is assigned while the contact between the self-propelled device 6 and the user H is suppressed and the user H is safe. can. Then, the user H can be assigned to the car to which the self-propelled device 6 is assigned. In addition, since the self-propelled device 6 and the user H can ride in the same car in a safe state, the elevator 4 can be used efficiently.

In order to realize the allocation described above, the elevator management device 1 of the present disclosure may include a device utilization floor identification unit, a user utilization floor identification unit, and an allocation unit shown below. The device use floor specifying unit specifies the departure floor and the destination floor of the self-propelled device 6 based on the destination floor call signal from the self-propelled device 6, that is, the allocation request data. The user floor identification unit identifies the departure floor and destination floor of the user H based on the destination floor call signal from the user H received prior to the destination floor call signal from the self-propelled device 6. . The allocation unit determines that the direction from the departure floor of the user H to the destination floor is the same as the direction from the departure floor to the destination floor of the self-propelled device 6, and that the boarding section of the user H is the self-propelled type. If it is included in the boarding section of the device 6, the self-propelled device 6 is assigned to the car of the user H.

Further, in order to realize the allocation described above, the elevator management device 1 of the present disclosure may include a device utilization floor identification unit, a user utilization floor identification unit, and an allocation unit, which will be described below. The user floor specifying unit specifies the departure floor and the destination floor of the user H based on the destination floor call signal issued by the user H's operation, that is, the allocation request data. The device use floor identification unit identifies the departure floor and the destination floor of the self-propelled device 6 based on the destination floor call signal from the self-propelled device 6 received prior to the destination floor call signal from the user H. do. The allocation unit determines that the direction from the departure floor of the user H to the destination floor is the same as the direction from the departure floor to the destination floor of the self-propelled device 6, and that the boarding section of the user H is the self-propelled type. When included in the boarding section of the device 6 , the user H is assigned to the car number of the self-propelled device 6 .

The above-mentioned "boarding section of user H" is a section that starts from the departure floor of user H and ends at the destination floor of user H. Further, the above-mentioned "boarding section of the self-propelled device 6" is a section that starts from the departure floor of the self-propelled device 6 and ends at the destination floor of the self-propelled device 6.

Here, when the above two directions are different from each other, the already assigned number of the user H is assigned to the self-propelled device 6, or the already assigned number of the self-propelled device 6 is assigned to the user H. never Therefore, there is no possibility that the self-propelled device 6 will come into contact with the user H when the self-propelled device 6 gets on or off the vehicle.

Even if the above two directions are the same, there is no possibility that the self-propelled device 6 will come into contact with the user H when the self-propelled device 6 gets on or off the vehicle in the following cases. That is, when the self-propelled device 6 and the user H are assigned to the elevator 4 so that the self-propelled device 6 and the user H do not ride on the same elevator, the self-propelled device 6 is used. There is no possibility of contact with person H.

Therefore, in the present embodiment, the explanation of the control when there is no possibility that the self-propelled device 6 will come into contact with the user H will be omitted. Below, the control when the self-propelled device 6 and the user H can ride in the same car will be described. In the following description, it is assumed that the direction from the departure floor of the user H to the destination floor and the direction from the departure floor to the destination floor of the self-propelled device 6 are the same.

(Configuration of Elevator Management System 100)
A configuration of the elevator management system 100 will be described with reference to FIG. FIG. 1 is a diagram showing an example of the configuration of an elevator management system 100 according to this embodiment. In addition, the elevator management system 100 shown in FIG. The elevator management device 1 may control the self-propelled device 6 without going through the self-propelled device management device 5 .

The elevator management system 100 includes an elevator management device 1 , a destination floor call registration device 2 , an elevator control device 3 , an elevator 4 , a self-propelled device management device 5 and a self-propelled device 6 .

The elevator management device 1 manages the operation of a plurality of elevators 4 installed in a building. Details of the elevator management device 1 will be described later.

The destination floor call registration device 2 is provided at the elevator platform on each floor of the building. The destination floor call registration device 2 accepts the allocation request operation by the user H and transmits the input allocation request data such as the destination floor to the elevator management device 1 . Identification information (ID) assigned to each destination floor call registration device 2 is used in communication between the elevator management device 1 and the destination floor call registration device 2 . For example, the ID of the destination floor call registration device 2 located on the 1st floor is "DESTREG-001", and the ID of the destination floor call registration device 2 located on the 2nd floor is "DESTREG-002". Elevator management device 1 transmits information on the optimum elevator assigned according to each allocation request operation to destination floor call registration device 2, and user H confirms the optimum elevator on the display screen of destination floor call registration device 2, etc. do. When the user H directly transmits the allocation request data to the elevator management device 1 from the mobile terminal without going through the destination floor call registration device 2, an ID is given to each user H, and the communication between the mobile terminal and the elevator 4 is performed. The ID is used for communication. A case where the user H performs an allocation request operation via the destination floor call registration device 2 will be described below.

The self-propelled device 6 transmits allocation request data to the elevator management device 1 . The elevator management device 1 transmits to the self-propelled device 6 information on the optimum elevator car allocated according to the allocation request data.

The elevator control device 3 controls operation of the elevator 4 . The elevator control device 3 is provided corresponding to each car of the elevator 4 . For example, the elevator controller 3a controls the operation of the elevator 4a, and the elevator controller 3b controls the operation of the elevator 4b. In addition, in the elevator management system 100, the number of elevator control devices 3 and elevators 4 is plural.

The self-propelled device management device 5 controls the movement, operation, etc. of the self-propelled device 6 deployed in the building. When a plurality of self-propelled devices 6 are deployed in a building, in communication between the self-propelled device management device 5 and the self-propelled devices 6, identification information given to each self-propelled device 6 ( ID) is used. The self-propelled device management device 5 is configured to appropriately receive from the self-propelled device 6 information indicating the current position of the self-propelled device 6 and work status information including information on the work currently being performed. may As a result, the self-propelled device management device 5 can monitor and control the position and work status of each self-propelled device 6 . The self-propelled device management device 5 may, for example, determine the departure floor and destination floor of the self-propelled device 6 and transmit information on the departure floor and destination floor to the self-propelled device 6 . The self-propelled device management device 5 may transmit work status information and the like to the elevator management device 1 .

(Configuration of elevator management device 1)
A configuration of the elevator management device 1 will be described with reference to FIG. FIG. 2 is a diagram showing an example of the configuration of the elevator management device 1. As shown in FIG.

The elevator management device 1 is a computer communicably connected to the destination floor call registration device 2, the elevator control device 3, and the like.

The control unit 11 is a CPU (Central Processing Unit), and the control unit 11 controls to execute processing of each function provided in the elevator management device 1 . The control unit 11 receives the allocation request data from the utilization target, and determines whether or not to allocate the utilization target elevator to the elevator car based on the received allocation request data and the already allocated elevator car information. The control unit 11 determines the optimum car from among allocatable car candidates, and allocates the use target to the optimum car. In addition, the control unit 11 comprehensively manages the operation of each car.

The control unit 11 includes, for example, a first identification unit 111, a second identification unit 112, a third identification unit 113, a first allocation unit 114, a second allocation unit 115, a determination unit 116, and a communication control unit 117.

The first identification unit 111 functions as an example of a device use floor identification unit that identifies the departure floor and destination floor of the self-propelled device 6 based on the allocation request data from the self-propelled device 6 . Also, the first specifying unit 111 functions as an example of a user floor specifying unit that specifies the departure floor and destination floor of the user H based on the allocation request data issued by the user H's operation.

Specifically, first identifying unit 111 determines whether or not allocation request data has been received from a utilization target via communication control unit 117 . The allocation request data includes information on, for example, the registration source ID of the use object, the use object attribute Rz, the departure floor Rs, and the destination floor Ri. When allocation request data is received from a utilization target, the first identifying unit 111 identifies the registration source ID of the utilization target, the utilization target attribute Rz, the departure floor Rs, and the destination floor Ri included in the allocation request data, and also identifies the registration information. Store in table 121 .

The second identifying unit 112 identifies the departure floor and destination floor of the user H based on the allocation request data from the user H received prior to the allocation request data from the self-propelled device 6. It functions as an example of a floor identification unit.

Specifically, when the allocation request data is received from the self-propelled device 6, the second specifying unit 112 has already assigned to the car, Departure floors and destination floors of all users H who are boarding or are scheduled to board are specified for each car. The second identifying unit 112 stores the identified departure floors and destination floors of all users H in the first list 122 as first departure floors Fs and first destination floors Fi. The second specifying unit 112 stores the first departure floor Fs and the first destination floor Fi of all the users H for each car. For example, when the self-propelled device 6 moves from the current floor to the upper floor, the second specifying unit 112 determines that the lower floor than the departure floor Rs of the self-propelled device 6 is registered as the departure floor. The departure floor and destination floor are read from the registration information table 121 . Then, the second specifying unit 112 stores the read departure floor and destination floor of the user H in the first list 122 as the first departure floor Fs and the first destination floor Fi.

In addition, the second specifying unit 112 determines the departure floor and destination floor of all the users H who have already been assigned to the car and who are planning to board the car after departing from the departure floor Rs of the self-propelled device 6. Identify each. The second identifying unit 112 stores the identified departure floors and destination floors of all users H in the second list 123 as second departure floors Ss and second destination floors Si. The second identifying unit 112 stores the second departure floors Ss and second destination floors Si of all the users H for each car. For example, when the self-propelled device 6 moves from the current floor to a higher floor, the second specifying unit 112 determines whether the departure floor of the user H whose departure floor is registered as a higher floor than the departure floor Rs of the self-propelled device 6 is registered as the departure floor. The floor and destination floor are read from the registration information table 121 . Then, the second specifying unit 112 registers the read departure floor and destination floor of the user in the second list 123 as the second departure floor Ss and the second destination floor Si.

A third specifying unit 113 is a device that specifies the departure floor and the destination floor of the self-propelled device 6 based on the assignment request data from the self-propelled device 6 received prior to the assignment request data from the user H. It functions as an example of a usage floor identification unit.

Specifically, when the third identifying unit 113 receives the allocation request data from the user H, the number has already been allocated, and the user H is boarding the car before arriving at the departure floor Rs. The destination floors of all self-propelled devices 6 to be boarded are specified for each car. The third identifying unit 113 stores the destination floors of all the identified self-propelled devices 6 in the third list 124 as third destination floors Mi. For example, when the user H moves from the current floor to an upper floor, the third specifying unit 113 selects the destination floor of the self-propelled device 6 whose departure floor is registered as a lower floor than the departure floor Rs of the user H. , from the registration information table 121 . Then, the third specifying unit 113 stores the read destination floor of the self-propelled device 6 in the third list 124 as the third destination floor Mi.

Further, the third specifying unit 113 specifies, for each car, the departure floors of all the self-propelled devices 6 that have already been assigned to the car and are scheduled to be boarded after leaving the departure floor Rs of the user. The third identifying unit 113 stores the departure floors of all the identified self-propelled devices 6 in the fourth list 125 as the fourth departure floor Ns. For example, when the user H moves from the current floor to an upper floor, the third specifying unit 113 selects the departure floor of the self-propelled device 6 whose departure floor is registered as a higher floor than the departure floor Rs of the user H. , from the registration information table 121 . Then, the third identifying unit 113 stores the read departure floor of the self-propelled device 6 in the fourth list 125 as the fourth departure floor Ns.

When the first allocation unit 114 receives the allocation request data from the self-propelled device 6, if the boarding section of the user H already assigned to the car number is included in the boarding section of the self-propelled device 6, It functions as an example of an allocation unit that allocates the self-propelled device 6 to the user H's car. The first allocation unit 114 stores the car identified as the allocation target in the allocation candidate list 126 .

Specifically, the first allocation unit 114, if the departure floor of the self-propelled device 6 that has transmitted the allocation request data is the same floor as the departure floor or destination floor of the user H that has already been allocated to the machine, The car number of the user H is not assigned to the self-propelled device 6 . Further, when the departure floor of the self-propelled device 6 exists between the departure floor and the destination floor of the user H, the first allocation unit 114 assigns the self-propelled device 6 to the user H's Do not assign a number. Furthermore, when the destination floor of the self-propelled device 6 is the same floor as the departure floor or the destination floor of the user H already assigned to the car, the first allocation unit 114 assigns the self-propelled device 6 to the use Person H's machine is not assigned. Further, when the destination floor of the self-propelled device 6 is between the departure floor and the destination floor of the user H, the first assigning unit 114 assigns the self-propelled device 6 to the destination floor of the user H. Do not assign a number.

When the second allocation unit 115 receives the allocation request data from the user H via the destination floor call registration device 2, the boarding section of the user H is changed to the boarding section of the self-propelled device 6 already allocated to the car number. When included, it functions as an example of an allocation unit that allocates the user H to the machine number of the self-propelled device 6 . The second allocation unit 115 stores the car identified as the allocation target in the allocation candidate list 126 .

Specifically, the second allocation unit 115, if the destination floor of the self-propelled device 6 already allocated to the car number is the same floor as the departure floor or the destination floor of the user H who transmitted the allocation request data, The number of the self-propelled device 6 is not assigned to the user H. Further, when the destination floor of the self-propelled device 6 is between the departure floor and the destination floor of the user H, the second allocation unit 115 assigns the user H the car number of the self-propelled device 6. do not assign Furthermore, the second allocation unit 115, if the departure floor of the self-propelled device 6 already allocated to the machine is the same floor as the departure floor or the destination floor of the user H who transmitted the allocation request data, the user The machine number of the self-propelled device 6 is not assigned to H. In addition, when the departure floor of the self-propelled device 6 exists between the departure floor and the destination floor of the user H, the second allocation unit 115 gives the user H the self-propelled device 6 Do not assign a number.

The determination unit 116 determines the optimum car number from among the car numbers stored in the allocation candidate list 126 and stores it in the registration information table 121 . The decision unit 116 decides, for example, the car with the shortest waiting time for the passenger on the departure floor as the optimum car.

The communication control unit 117 controls the communication unit 13 to communicate with the destination floor call registration device 2 , the elevator control device 3 , the self-propelled device management device 5 and the self-propelled device 6 . Specifically, the communication control unit 117 receives allocation request data from the destination floor call registration device 2 or the self-propelled device 6, and transmits information on the optimum number to the destination floor call registration device 2 or the self-propelled device 6. to control. When the object of use is the self-propelled device 6 , the communication control unit 117 transmits information on the optimum machine number to the self-propelled device 6 . The communication control unit 117 transmits the information of the optimum car to the destination floor call registration device 2 when the object of use is the user H.

The storage unit 12 is a storage device in which various computer programs read by the control unit 11 and data used in various processes executed by the control unit 11 are stored. The storage unit 12 stores, for example, a registration information table 121 . The storage unit 12 also stores, for example, a first list 122, a second list 123, a third list 124, a fourth list 125, and an allocation candidate list 126. FIG. The first list 122, second list 123, third list 124 and fourth list 125 will be described later. In the allocation candidate list 126, the numbers of allocable machines are displayed. is stored.

Table 1 shows an example of the registration information table 121 .

The registration information table 121 has items of, for example, reception date and time, registration source ID, use target attribute, departure floor, destination floor, and optimum car number. Information included in the allocation request data may be registered in the registration information table 121 in the order in which the elevator management apparatus 1 receives the allocation request data, for example. The date and time when the elevator management device 1 received the allocation request data from the self-propelled device 6 or the user H is stored in the column of "receipt date and time". For example, year, month, day, hour, minute and second are stored in the "receiving date and time column". The column of "registration source ID" stores information for identifying the target of use. In the column of "registration source ID", when the usage target attribute of the usage target is the user H, the ID of the destination floor call registration device 2 is stored, and the usage target attribute of the usage target is the self-propelled device 6. In this case, the ID of the self-propelled device 6 is stored. In the column of "use object attribute", information indicating "user" or "self-propelled device" is stored according to the use object. In the column of "departure floor", the floor where the user gets on the elevator 4 is stored. The column of “destination floor” stores the floor where the user gets off the elevator 4 . The column of “optimal car number” stores the optimum car number determined by the determining unit 116 .

The registration information table 121 stores the registration information of all usage targets. The registration information is updated each time allocation request data is received from a user and each time an optimum machine number is determined. In Table 1, each user H who has sent allocation request data from each destination floor call registration device 2 whose ID is "DESTREG-001", "DESTREG-003", and "DESTREG-004" has already registered the first car. assigned. Then, the allocation request data is received from the self-propelled device 6 whose ID is "ROBOT-001", and the first identification unit 111 stores the registration source ID, the attribute to be used, the departure floor, and the destination floor. showing.

The communication unit 13 is an interface for performing communication via a communication network such as a wireless LAN (Local Area Network). The communication unit 13 receives allocation request data from the destination floor call registration device 2 or the self-propelled device 6 and transmits information on the optimum car to the destination floor call registration device 2 or the self-propelled device 6 .

(Configuration of self-propelled device 6)
Next, the configuration of the self-propelled device 6 will be described with reference to FIG. FIG. 3 is a diagram showing an example of the configuration of the self-propelled device 6. As shown in FIG.

The self-propelled device 6 is a multifunctional device having a self-propelled function that is communicably connected to the elevator management device 1 . The self-propelled device 6 may be a robot capable of autonomous running or independent walking.

The self-propelled device 6 includes a control unit 60, a moving mechanism 63, a communication unit 64, and a storage unit 65, for example. The control unit 60 is a CPU, and the control unit 60 controls to execute processing of each function provided in the self-propelled device 6 .

The control unit 60 includes a management unit 61 and a communication control unit 62, for example. The management unit 61 comprehensively manages the operation of the self-propelled device 6 .

The communication control unit 62 controls the communication unit 64 to communicate with the elevator management device 1 and the self-propelled device management device 5 . Specifically, the communication control unit 62 receives instructions such as transportation of luggage from the self-propelled device management device 5, transmits allocation request data to the elevator management device 1, or It controls communication such as receiving information from

The moving mechanism 63 is a driving mechanism for moving the self-propelled device 6 . The movement mechanism 63 may be any drive mechanism such as wheels, caterpillars, and walking legs.

The communication unit 64 is an interface for performing communication via a communication network such as a wireless LAN. The communication unit 64 performs communications such as receiving instructions for transporting luggage from the self-propelled device management device 5, transmitting allocation request data to the elevator management device 1, and receiving information on the optimum elevator car from the elevator management device 1. I do.

The storage unit 65 is a storage device in which various computer programs read by the control unit 60 and data used in various processes executed by the control unit 60 are stored.

(Configuration of Elevator Control Device 3 and Elevator 4)
Next, configurations of the elevator control device 3 and the elevator 4 will be described with reference to FIG. FIG. 4 is a diagram showing an example of the configuration of the elevator control device 3 and the elevator 4. As shown in FIG.

The elevator 4 includes a car 41 for boarding the user H, etc., an operation control panel 40 for controlling the elevation of the car 41, and a door 42 provided at the landing of each floor for each car.

The elevator control device 3 is, for example, a computer provided for each car of the elevator 4 and connected to the elevator 4 so as to be communicable. For example, the elevator controller 3 controls operation of the elevator 4 .

The elevator control device 3 has a control section 30 . The control unit 30 is a CPU, and the control unit 30 controls to execute processing of each function provided in the elevator control device 3 .

The control unit 30 includes, for example, an instruction acquisition unit 31, a driving situation management unit 32, and a door opening/closing control unit 33.

The instruction acquisition unit 31 acquires various instructions from the elevator management device 1 associated with the result of allocation of the optimum elevator car. Instructions acquired by the instruction acquisition unit 31 include a stop floor setting instruction, a destination floor setting instruction, and the like.

The operating status management unit 32 acquires from the operation control panel 40 each information indicating the position of the car 41 of the elevator 4, the operating status, the opening/closing status of the door 42 of each floor, and the like.

The door opening/closing control unit 33 controls the opening/closing of the door 42 of the landing of the designated floor according to the instruction from the elevator management device 1 . For example, the door opening/closing control unit 33 can cause the elevator 4 to hold the door 42 of the elevator 4 at the landing of the designated floor in an open state, or cancel the holding of the open state. .

(Processing performed by elevator management device 1)
Next, an example of processing performed by the elevator management device 1 will be described with reference to FIG. FIG. 5 is a flowchart showing an example of processing by the control unit 11 of the elevator management device 1. As shown in FIG. As described above, it is assumed that the direction from the departure floor of the user H to the destination floor and the direction from the departure floor to the destination floor of the self-propelled device 6 are the same.

First, the first specifying unit 111 determines whether the allocation request data transmitted by the destination floor call registration device 2 or the self-propelled device 6 is received via the communication control unit 117 (step S1). When determining that the allocation request data has not been received (step S1: NO), the first identifying unit 111 repeats the process of step S1.

When determining that the allocation request data has been received (step S1: YES), the first identifying unit 111 identifies the registration source ID, the utilization target attribute Rz, the departure floor Rs, and the destination floor Ri included in the allocation request data. Together, it is stored in the registration information table 121 (step S2). In the example shown in Table 1, the usage target attribute Rz, the departure floor Rs, and the destination floor Ri included in the allocation request data received from the self-propelled device 6 are No. 4 is stored.

The first identifying unit 111 determines whether or not the utilization target attribute Rz is the self-propelled device 6 (step S3). When the allocation request data is received from the self-propelled device 6 , the allocation request data includes a utilization target attribute indicating the self-propelled device 6 . Therefore, the first identifying unit 111 determines that the utilization target attribute Rz is the self-propelled device 6 . When receiving the allocation request data from the destination floor call registration device 2, the first identification unit 111 includes a utilization target attribute indicating the user H in the allocation request data. Therefore, the first identifying unit 111 determines that the user H is the attribute Rz to be used.

When the first identifying unit 111 determines that the utilization target attribute Rz is the self-propelled device 6 (step S3: YES), the second identifying unit 112 and the first assigning unit 114 perform the processing of subroutine A ( step S4). On the other hand, when the first identifying unit 111 determines that the target of use is not the self-propelled device 6, that is, the user H (step S3: NO), the third identifying unit 113 and the second assigning unit 115 execute the subroutine Process B is performed (step S5). The processing of subroutine A and the processing of subroutine B will be described later.

In subroutine A or B, a car to be an allocation candidate is selected from among the plurality of cars and stored in allocation candidate list 126 . The determination unit 116 selects the optimum car from the allocation candidate list 126 and determines the selected car as the optimum car (step S6). As described above, the determining unit 116 determines, as the optimum elevator, the elevator with the shortest waiting time for the passenger on the departure floor Rs, for example.

The communication control unit 117 transmits the information of the optimum machine number to the utilization target that received the allocation request data (step S7), and ends the process. When the target of use is the self-propelled device 6 , the communication control unit 117 transmits the information of the optimum number to the self-propelled device 6 . When the target of use is user H, the communication control unit 117 transmits the information of the optimum elevator car to the destination floor call registration device 2 to which the user H has performed the allocation request operation.

(Processing of subroutine A)
The processing of subroutine A will be described below. FIG. 6 is a flowchart showing an example of the processing flow of subroutine A. As shown in FIG. The second identification unit 112 identifies the number of the machine. is set to 1 (step S11). That is, the second specifying unit 112 first determines whether or not the self-propelled device 6 can be assigned to the first elevator 4a.

The second identification unit 112 reads out the registration information table 121 and identifies the departure floors and destination floors of all the users H who are boarding or planning to board the No. 1 car until the No. 1 car arrives at the departure floor Rs. . The second specifying unit 112 stores the specified departure floor and destination floor in the first list 122 as the first departure floor Fs and the first destination floor Fi (step S12). In the example shown in Table 1, the second specifying unit 112 selects No. The first departure floor Fs and the first destination floor Fi ((Fs, Fi)=(1, 4)) of one user H are stored in the first list 122 .

Next, the second identifying unit 112 identifies the departure floors and destination floors of all users H who are boarding or planning to board the first car after the first car departs from the departure floor Rs. The second identifying unit 112 stores the identified departure floor and destination floor in the second list 123 as the second departure floor Ss and the second destination floor Si (step S13). In the example shown in Table 1, the second specifying unit 112 selects No. The second departure floor Ss and the second destination floor Si ((Ss, Si)=(3, 4)) of the second user H are stored in the second list 123 . Further, the second identification unit 112 selects No. The second departure floor Ss and the second destination floor Si ((Ss, Si)=(4, 6)) of the user H of No. 3 are stored in the second list 123 .

In addition, the process of step S12 should just be performed before the process of step S14. Moreover, the process of step S13 should just be performed before the process of step S20.

Next, the first assigning unit 114 determines whether or not the first list 122 is empty (step S14). When the first allocation unit 114 determines that the first list 122 is empty (step S14: YES), the process proceeds to step S20. When the first list 122 is empty, there is no user H who has boarded the first car before the self-propelled device 6 arrives. There is no possibility of contacting user H at this time. Therefore, the first allocation unit 114 advances the process to step S20, refers to the second list 123, and determines whether or not the self-propelled device 6 can be allocated to the first machine.

When the first allocation unit 114 determines that the first list 122 is not empty (step S14: NO), the first departure floor Fs and the first departure floor Fs of the specific user H in the first list 122, that is, the user Hi The first destination floor Fi is specified as the first departure floor Fsi and the first destination floor Fii (step S15). In the example shown in Table 1, the first assigning unit 114 assigns No. For one user Hi, the first departure floor Fsi=1 and the first destination floor Fii=4 are specified.

Next, the first allocation unit 114 determines whether or not the departure floor Rs of the self-propelled device 6 is smaller than the destination floor Ri (step S16). When the departure floor Rs of the self-propelled device 6 is smaller than the destination floor Ri, the self-propelled device 6 moves upward.

When the first allocation unit 114 determines that the number of the departure floor Rs of the self-propelled device 6 is smaller than the number of the destination floor Ri (step S16: YES), the first departure floor Fsi ≤ departure of the self-propelled device 6 It is determined whether or not floor Rs≦first destination floor Fii (step S17).

When the first allocation unit 114 determines that the first departure floor Fsi≦the departure floor Rs of the self-propelled device 6≦the first destination floor Fii (step S17: YES), the process proceeds to step S27. In this case, since the self-propelled device 6 will get on the first car at the departure floor Rs while the user Hi is on the first car, the self-propelled device 6 may contact the user Hi. have a nature. Therefore, the first assigning unit 114 does not assign the self-propelled device 6 to No. 1, and in step S27, assigns No. 1 to No. 1. , increment c.

When it is determined that the first departure floor Fsi≦the departure floor Rs of the self-propelled device 6≦the first destination floor Fii (step S17: NO), the first allocation unit 114 advances the process to step S19. When the first destination floor Fii<departure floor Rs of the self-propelled device 6, when the self-propelled device 6 gets on the departure floor Rs, the user Hi has already got off, and the user Since Hi does not exist, there is no possibility that the self-propelled device 6 will contact the user Hi. Therefore, in the case of NO in step S17, the first assigning unit 114 advances the process to step S19 in order to determine whether or not the self-propelled device 6 can be assigned to the first car.

In step S16, when the first allocation unit 114 determines that the number of departure floors Rs of the self-propelled device 6 is greater than the number of destination floors Ri (step S16: NO), the first destination floor Fii ≤ self-propelled type It is determined whether or not the departure floor Rs of the device 6≦the first departure floor Fsi (step S18). When the floor number of the departure floor Rs is greater than the floor number of the destination floor Ri, the self-propelled device 6 moves downward.

When the first allocation unit 114 determines that the first destination floor Fii ≤ the departure floor Rs of the self-propelled device 6 ≤ the first departure floor Fsi (step S18: YES), the process proceeds to step S27. In this case, the self-propelled device 6 will get on the first car at the departure floor Rs while the user Hi is on the first car, so the self-propelled device 6 can contact the user Hi. have a nature. Therefore, the first assigning unit 114 does not assign the self-propelled device 6 to No. 1, and assigns No. 1 to No. 1 in step S27. , increment c.

When it is determined that the first destination floor Fii≦the departure floor Rs of the self-propelled device 6≦the first departure floor Fsi (step S18: NO), the first allocation unit 114 advances the process to step S19. When the departure floor Rs of the self-propelled device 6<the first destination floor Fii, the user Hi has alighted when the self-propelled device 6 gets on the departure floor Rs, and the user Hi is in the first car. Since the user is not on board, there is no possibility that the self-propelled device 6 will come into contact with the user Hi. Therefore, in the case of NO in step S18, the first assigning unit 114 advances the process to step S19 in order to determine whether or not the self-propelled device 6 can be assigned to the first car.

In step S19, the first allocation unit 114 determines whether or not the processes of steps S15 to S18 have been completed for all the elements of the first list 122. FIG. In other words, the first assigning unit 114 determines whether or not the processes of steps S15 to S18 have been completed for all users H assigned to the first machine.

When the first assigning unit 114 determines that the processes of steps S15 to S18 have not been completed for all elements of the first list 122 (step S19: NO), the process returns to step S15. In step S15, the first allocation unit 114 identifies the first departure floor Fs and the first destination floor Fi of the other user Hi in the first list 122 as the first departure floor Fsi and the first destination floor Fii, respectively. Then, the processing after step S16 is performed.

In the case of the example shown in Table 1, when the self-propelled device 6 gets on at 2F, No. 1 user Hi is boarding the first car. That is, first departure floor Fsi<departure floor Rs of self-propelled device 6<first destination floor Fii. Therefore, it becomes YES in step S17, and the 1st allocation part 114 will not allocate the self-propelled apparatus 6 to the 1st machine.

When it is determined that the processes of steps S15 to S18 have been completed for all elements of the first list 122 (step S19: YES), the first allocation unit 114 determines whether the second list 123 is empty. (step S20). When the first allocation unit 114 determines that the second list 123 is empty (step S20: YES), the process proceeds to step S26. In this case, when the self-propelled device 6 boarded at the departure floor Rs, not all the users H boarded the first car. In addition, after the first car departs from the departure floor Rs, there is no user Hi who is scheduled to board the first car. Person H does not exist. Therefore, there is no possibility that the self-propelled device 6 will contact the user Hi, and the first allocation unit 114 adds the first vehicle to the allocation candidate list 126 in step S26.

When the first allocation unit 114 determines that the second list 123 is not empty (step S20: NO), the second departure floor Ss and the second departure floor Ss of the specific user H in the second list 123, that is, the user Hj. The second destination floor Si is specified as the second departure floor Ssj and the second destination floor Sij (step S21). In the example shown in Table 1, the first assigning unit 114 assigns No. For 2 users Hj, the second departure floor Ssj=3 and the second destination floor Sij=4 are specified. Also, the first assigning unit 114 assigns No. For 3 users Hj, the second departure floor Ssj=4 and the second destination floor Sij=6 are specified.

The first allocation unit 114 determines whether or not the number of the departure floor Rs of the self-propelled device 6 is smaller than the number of the destination floor Ri (step S22). When the first assigning unit 114 determines that the number of the departure floor Rs of the self-propelled device 6 is smaller than the number of the destination floor Ri (step S22: YES), the second departure floor Ssj≦the destination of the self-propelled device 6 It is determined whether or not floor Ri≦second destination floor Sij (step S23).

When the first allocation unit 114 determines that the second departure floor Ssj≦the destination floor Ri of the self-propelled device 6≦the second destination floor Sij (step S23: YES), the process proceeds to step S27. In this case, since the self-propelled device 6 gets off from the first car at the destination floor Ri while the user Hj is on the first car, the self-propelled device 6 may contact the user Hj. have a nature. Therefore, the first assigning unit 114 does not assign the self-propelled device 6 to No. 1, and in step S27, assigns No. 1 to No. 1. , increment c.

When it is determined that second departure floor Ssj≦destination floor Ri of self-propelled device 6≦second destination floor Sij (step S23: NO), the first allocation unit 114 advances the process to step S25. If NO in step S23, the destination floor Ri of the self-propelled device 6<the second departure floor Ssj. Alternatively, the departure floor Rs of the self-propelled device 6 < the second departure floor Ssj and the second destination floor Sij < the destination floor Ri of the self-propelled device 6, and the boarding section of the user Hj is the section of the self-propelled device 6 included in the boarding section. In these cases, when the self-propelled device 6 gets off at the destination floor Ri, the user Hj does not get on the car No. 1, and the self-propelled device 6 can contact the user Hj when getting off. no sex. In the latter case, there is a section in which the self-propelled device 6 and the user Hj ride together, but the self-propelled device 6 does not move and the possibility of the self-propelled device 6 contacting the user Hj is reduced. ing. Therefore, the first assigning unit 114 advances the process to step S25 in order to determine whether or not the self-propelled device 6 can be assigned to the first car.

When the first allocation unit 114 determines that the number of departure floors Rs of the self-propelled device 6 is greater than the number of destination floors Ri (step S22: NO), the second destination floor Sij ≤ the destination of the self-propelled device 6 It is determined whether or not floor Ri≦second departure floor Ssj (step S24).

When the first allocation unit 114 determines that the second destination floor Sij≦the destination floor Ri of the self-propelled device 6≦the second departure floor Ssj (step S24: YES), the process proceeds to step S27. In this case, since the self-propelled device 6 gets off from the first car at the destination floor Ri while the user Hj is on the first car, the self-propelled device 6 may contact the user Hj. have a nature. Therefore, the first assigning unit 114 does not assign the self-propelled device 6 to No. 1, and in step S27, assigns No. 1 to No. 1. , increment c.

When the first allocation unit 114 determines that second destination floor Sij≦destination floor Ri of self-propelled device 6≦second departure floor Ssj (step S24: NO), the process proceeds to step S25. If NO in step S24, second departure floor Ssj<destination floor Ri of self-propelled device 6 is established. Alternatively, the destination floor Ri of the self-propelled device 6 < the second destination floor Sij and the second departure floor Ssj < the departure floor Rs of the self-propelled device 6, and the user Hj boarding section of the self-propelled device 6 included in the boarding section. In these cases, when the self-propelled device 6 gets off at the destination floor Ri, the user Hj does not get on the car No. 1, and the self-propelled device 6 can contact the user Hj when getting off. no sex. In the latter case, there is a section where the self-propelled device 6 and the user Hj are riding together, but the self-propelled device 6 does not move and the possibility of the self-propelled device 6 contacting the user Hj is reduced. there is Therefore, the first assigning unit 114 advances the process to step S25 in order to determine whether or not the self-propelled device 6 can be assigned to the first car.

In step S25, the first assigning unit 114 determines whether the processes of steps S21 to S24 have been completed for all the elements of the second list. That is, the first assigning unit 114 determines whether or not all the users H assigned to the first machine have completed the processes of steps S21 to S24.

When the first assigning unit 114 determines that all the elements of the second list have not been processed (step S25: NO), the process returns to step S21. In step S21, the first allocation unit 114 identifies the second departure floor Ss and the second destination floor Si of the other user Hj in the second list 123 as the second departure floor Ssj and the second destination floor Sij. , the processing after step S22 is performed.

When the first assigning unit 114 determines that the processes of steps S21 to S24 have been completed for all the elements of the second list 123 (step S25: YES), the first assigning unit 114 assigns No. c. is added to the allocation candidate list 126 (step S26). Here, if the car c is the car No. 1, when the self-propelled device 6 gets on at the departure floor Rs, not all the users H on the first list 122 are boarding the car No. 1, and the destination floor When getting off at Ri, not all the users H on the second list 123 board the No. 1 car. Therefore, the first allocation unit 114 stores the first machine in the allocation candidate list 126 in step S26.

If YES in step S17, step S18, step S23, and step S24, and after the process of step 26, the first assigning unit 114 adds 1 to the value of c and increments it (step S27). For example, when the first allocation unit 114 stores the value of "1" indicating the elevator 4a in the allocation candidate list 126 in step S26, it sets c=2 in step S27, and assigns the second elevator 4b to the first elevator. The allocation unit 114 determines this.

Next, the first allocation unit 114 determines whether or not c is greater than the total number of cars m (step S28). When the first allocation unit 114 determines that c is equal to or less than the total number of cars m (step S28: NO), the process returns to step S12. As described above, the second specifying unit 112 performs the specifying process and the first assigning unit 114 performs the assigning process for all car Nos.

When the first allocation unit 114 determines that c is greater than the total number of cars m (step S28: YES), the second identification unit 112 executes the identification process for all the cars, and the first allocation Since the unit 114 has executed the allocation process, the process proceeds to step S6 in FIG. The processing of steps S14 to S19 and the processing of steps S20 to S25 may be executed in parallel, or the processing order may be reversed.

(Processing of subroutine B)
The processing of subroutine B will be described below. FIG. 7 is a flow chart showing an example of the processing flow of subroutine B. FIG.

The third identification unit 113 identifies the number of the machine. is set to 1 (step S31). That is, the third specifying unit 113 first determines whether or not the user H can be assigned to the first elevator 4a.

The third identifying unit 113 reads out the registration information table 121 and determines the destination floors of all the self-propelled devices 6 that are boarding or are scheduled to board the first car until the first car arrives at the departure floor Rs of the user H. identify. The third identifying unit 113 stores the identified destination floor in the third list 124 as the third destination floor Mi (step S32).

Next, the third identifying unit 113 reads out the registration information table 121, and identifies the departure floors of all the self-propelled devices 6 that are on board or are scheduled to board the first car after the first car departs from the departure floor Rs. do. The third identifying unit 113 stores the identified departure floor as the fourth departure floor Ns in the fourth list 125 (step S33).

Note that the process of step S32 may be executed before the process of step S34. Moreover, the process of step S33 should just be performed before the process of step S40.

Next, the second allocation unit 115 determines whether or not the third list 124 is empty (step S34). When the second allocation unit 115 determines that the third list 124 is empty (step S34: YES), the process proceeds to step S40. When the third list 124 is empty, when the user H gets on the first car at the departure floor Rs, the self-propelled device 6 is not on the first car. That is, there is no self-propelled device 6 that gets off from the first car while the user H is on board. Therefore, there is no possibility that the self-propelled device 6 will contact the user H. Accordingly, the second allocation unit 115 advances the process to step S40, refers to the fourth list 125, and determines whether or not the user H can be allocated to the first machine.

When the second allocation unit 115 determines that the third list 124 is not empty (step S34: NO), the third destination of the specific self-propelled device 6 in the third list 124, that is, the self-propelled device 6i. The floor Mi is identified as the third destination floor Mii (step S35).

The second allocation unit 115 determines whether or not the departure floor Rs of the user H is smaller than the destination floor Ri (step S36). If the departure floor Rs is smaller than the destination floor Ri, the user H moves upward.

When the second allocation unit 115 determines that the number of departure floors Rs of user H is smaller than the number of destination floors Ri (step S36: YES), the second allocation unit 115 determines that the departure floor Rs of user H ≤ third destination floor Mii ≤ used It is determined whether or not it is the destination floor Ri of the person H (step S37).

When the second allocation unit 115 determines that the departure floor Rs of the user H ≤ the third destination floor Mii ≤ the destination floor Ri of the user H (step S37: YES), the process proceeds to step S47. In this case, while the user H is on the first car, the self-propelled device 6i gets off the first car at the third destination floor Mii. Therefore, the second assigning unit 115 does not assign the self-propelled device 6i to No. 1, and assigns No. 1 to No. 1 in step S47. , increment c.

When the second allocation unit 115 determines that the departure floor Rs of the user H ≤ the third destination floor Mii ≤ the destination floor Ri of the user H (step S37: NO), the process proceeds to step S39. If NO in step S37, third destination floor Mii<user H's departure floor Rs. Alternatively, since the destination floor Ri of the user H < the third destination floor Mii, and naturally the third departure floor Msi of the self-propelled device 6i < the departure floor Rs of the user H, the boarding section of the user H is It is included in the boarding section of the self-propelled device 6 . In these cases, when the self-propelled device 6i gets off at the third destination floor Mii, the user Hi is not on board the first car, and the self-propelled device 6 contacts the user H when getting off. there is no possibility to In the latter case, there is a section where the self-propelled device 6i and the user H are riding together, but the self-propelled device 6i does not move and the possibility of the self-propelled device 6i contacting the user H is reduced. there is Therefore, the second allocation unit 115 advances the process to step S39 in order to determine whether or not it is possible to allocate the user H to the first machine.

In step S36, when the second allocation unit 115 determines that the number of departure floors Rs of user H is greater than the number of destination floors Ri (step S36: NO), destination floor Ri of user H ≤ third destination It is determined whether or not floor Mii≦departure floor Rs of user H (step S38). If the departure floor Rs is larger than the destination floor Ri, the user H moves downward.

When the second allocation unit 115 determines that the destination floor Ri of the user H ≤ the third destination floor Mii ≤ the departure floor Rs of the user H (step S38: YES), the process proceeds to step S47. In this case, the self-propelled device 6i gets off from the first car at the third destination floor Mii while the user Hi is on the first car. No. 1 machine is not assigned, and in step S47, No. 1 machine is assigned. , increment c.

When the second allocation unit 115 determines that the destination floor Ri of the user H ≤ the third destination floor Mii ≤ the departure floor Rs of the user H (step S38: NO), the process proceeds to step S39. If NO in step S38, the departure floor Rs of the user H<the third destination floor Mii. Alternatively, since the third destination floor Mii<the destination floor Ri of the user H, and naturally the third departure floor Msi of the self-propelled device 6i>the departure floor Rs of the user H, the boarding section of the user H is It is included in the boarding section of the self-propelled device 6i. In these cases, when the self-propelled device 6i gets off at the third destination floor Mii, the user H is not on board the first car, and the self-propelled device 6i contacts the user H when getting off. there is no possibility to In the latter case, there is a section where the self-propelled device 6i and the user H are riding together, but the self-propelled device 6i does not move and the possibility of the self-propelled device 6i contacting the user H is reduced. there is Therefore, the second allocation unit 115 advances the process to step S39 in order to determine whether or not it is possible to allocate the user H to the first machine.

In step S39, the second allocation unit 115 determines whether the processes of steps S35 to S38 have been completed for all the elements of the third list 124. FIG. That is, the second assigning unit 115 determines whether or not the processes of steps S35 to S38 have been completed for all the self-propelled devices 6 assigned to the first device.

When the second allocation unit 115 determines that the processes of steps S35 to S38 have not been completed for all the elements of the third list 124 (step S39: NO), the process returns to step S35. In step S35, the second assigning unit 115 identifies the third destination floor Mi of the other self-propelled device 6i in the third list 124 as the third destination floor Mii, and performs the processing after step S36.

When the second allocation unit 115 determines that the processes of steps S35 to S38 have been completed for all the elements of the third list 124 (step S39: YES), it determines whether the fourth list 125 is empty. (step S40). When the second allocation unit 115 determines that the fourth list 125 is empty (step S40: YES), the process proceeds to step S46. In this case, after the first car departs from the departure floor Rs, there is no self-propelled device 6 scheduled to board the first car. to add.

When the second assigning unit 115 determines that the fourth list 125 is not empty (step S40: NO), the fourth departure of the specific self-propelled device 6 in the fourth list 125, that is, the self-propelled device 6j. The floor Ns is identified as the fourth departure floor Nsj (step S41).

The second allocation unit 115 determines whether or not the departure floor Rs of the user H is smaller than the destination floor Ri (step S42). When the second allocation unit 115 determines that the number of departure floors Rs of user H is smaller than the number of destination floors Ri (step S42: YES), the second allocation unit 115 determines that the number of departure floors Rs of user H ≤ fourth departure floor Nsj ≤ used It is determined whether or not it is the destination floor Ri of the person H (step S43).

When the second allocation unit 115 determines that the departure floor Rs of the user H ≤ the fourth departure floor Nsj ≤ the destination floor Ri of the user H (step S43: YES), the process proceeds to step S47. In this case, the self-propelled device 6j gets on the first car at the fourth departure floor Nsj while the user H is on the first car, so the self-propelled device 6j contacts the user H. there's a possibility that. Therefore, the second assigning unit 115 does not assign the self-propelled device 6j to No. 1, and assigns No. 1 to No. 1 in step S47. , increment c.

When the second allocation unit 115 determines that the departure floor Rs of the user H ≤ the fourth departure floor Nsj ≤ the destination floor Ri of the user H (step S43: NO), the process proceeds to step S45. If NO in step S43, the destination floor Ri of user H<fourth departure floor Nsj. In this case, when the self-propelled device 6j gets on at the fourth departure floor Nsj, the user H does not board the first car, and the self-propelled device 6j contacts the user H when boarding. Not possible. Therefore, in the case of NO in step S43, the second assigning unit 115 advances the process to step S45 to determine whether or not it is possible to assign the user H to the first car.

When the second allocation unit 115 determines that the number of departure floors Rs of user H is greater than the number of destination floors Ri (step S42: NO), the destination floor Ri of user H ≤ fourth departure floor Nsj ≤ use It is determined whether or not it is the departure floor Rs of the person H (step S44).

When the second allocation unit 115 determines that the destination floor Ri ≤ fourth departure floor Nsj ≤ departure floor Rs (step S44: YES), the process proceeds to step S47. In this case, the self-propelled device 6j gets on the first car at the fourth departure floor Nsj while the user H is on the first car, so the second assigning unit 115 assigns the user H to the first car. First, in step S47, the No. of the car is checked. is incremented.

If the second allocation unit 115 determines that the destination floor Ri of user H ≤ fourth departure floor Nsj ≤ departure floor Rs of user H (step S44: NO), the process proceeds to step S45. If NO in step S44, fourth departure floor Nsj<user H's destination floor Ri. In this case, when the self-propelled device 6j gets on at the fourth departure floor Nsj, the user H does not board the first car, and the self-propelled device 6j contacts the user H when boarding. Not possible. Therefore, in the case of NO in step S44, the second assigning unit 115 advances the process to step S45 in order to determine whether or not it is possible to assign the user H to the first car.

In step S45, the second allocation unit 115 determines whether or not the processes of steps S41 to S44 have been completed for all the elements of the fourth list 125. FIG. That is, the second assigning unit 115 determines whether or not the processes of steps S41 to S44 have been completed for all the self-propelled devices 6 assigned to the first device.
When the second assigning unit 115 determines that the processes of steps S41 to S44 have not been completed for all the elements of the fourth list 125 (step S45: NO), the process returns to step S41. In step S41, the second allocation unit 115 identifies the fourth departure floor Ns of the other self-propelled device 6j in the fourth list 125 as the fourth departure floor Nsj, and performs the processing after step S42.

When the second allocation unit 115 determines that the processes of steps S41 to S44 have been completed for all the elements of the fourth list 125 (step S45: YES), it adds the first machine to the allocation candidate list (step S46). . In this case, when the user H is on the first car, none of the self-propelled devices 6 on the third list 124 get off at the third destination floor Mii, and all the self-propelled devices 6 on the fourth list 125 do not get off at the third destination floor Mii. The running device 6 does not board at the fourth departure floor Nsj. Therefore, the second allocation unit 115 stores the first machine in the allocation candidate list 126 in step S46.

If YES in steps S37, S38, S43, and S44, and after the process of step 46, the second assigning unit 115 adds 1 to the value of c and increments it (step S47). For example, when the second allocation unit 115 stores the value of “1” indicating the elevator 4a in the allocation candidate list 126 in step S46, it sets c=2 in step S47, and assigns the elevator 4b, which is the second car, to the second elevator. The allocation unit 115 makes a determination target.

Next, the second allocation unit 115 determines whether or not c is greater than the total number of cars m (step S48). When the first allocation unit 114 determines that c is not equal to or less than the total number of cars m (step S48: NO), the process returns to step S32. As a result, the third identifying unit 113 executes the identifying process and the second allocating unit 115 executes the allocating process for all cars.

When the first allocation unit 114 determines that c is greater than the total number of cars (step S48: YES), the third identification unit 113 executes the identification process for all the cars, and the second allocation unit 115 has executed the allocation process, the process proceeds to step S6 in FIG. The processing of steps S34 to S39 and the processing of steps S40 to S45 may be executed in parallel, or the processing order may be reversed.

(Control Method of Elevator Management Device 1)
The control method of the elevator management device 1 includes a device utilization floor identification step, a user utilization floor identification step, and an allocation step, which will be described below. The device use floor identification step identifies the departure floor Rs and the destination floor Ri of the self-propelled device 6 based on the destination floor call signal from the self-propelled device 6 . The steps S1 and S2 described above correspond to the step of identifying a floor to be used by the device. In the step of specifying the floor used by the user, the departure floor and Identify the destination floor. The steps S12 and S13 described above correspond to the user floor identification step. In the allocation step, the direction from the departure floor of the user H to the destination floor is the same as the direction from the departure floor to the destination floor of the self-propelled device 6, and the boarding section of the user H is self-propelled. If it is included in the boarding section of the running type device 6 , the self-propelled device 6 is assigned to the car of the elevator 4 . The steps S14 to S28 described above correspond to the allocation steps.

Further, the control method of the elevator management device 1 includes a user floor specification step, a device usage floor specification step, and an allocation step, which will be described below. The user floor identification step identifies the departure floor and destination floor of the user based on the destination floor call signal issued by the user H's operation. The steps S1 and S2 described above correspond to the user floor identification step. The device use floor identifying step determines the departure floor of the self-propelled device 6 based on the destination floor call signal from the self-propelled device 6 received prior to the destination floor call signal issued by the operation of the user H. and specify the destination floor. The above-described steps S32 and S33 correspond to the device utilization floor identification step. In the allocation step, the direction from the departure floor of the user H to the destination floor is the same as the direction from the departure floor to the destination floor of the self-propelled device 6, and the boarding section of the user H is self-propelled. If the user H is included in the boarding section of the running device 6, the user H is assigned to the elevator car. The steps S34 to S48 described above correspond to the allocation steps.

According to the elevator management device 1 and the control method thereof described above, the self-propelled device 6 can be operated by the user H in a state in which the possibility of contact between the self-propelled device 6 and the user H is reduced, that is, in a safe state. can be assigned to the assigned machine. Therefore, it is possible to allow the self-propelled device 6 and the user H to ride in the same car in a safe state. In addition, by allowing such sharing, it becomes possible to use the elevator 4 efficiently.

[Example of realization by software]
Control blocks (particularly control units 11 and 60) of elevator management device 1, self-propelled device management device 5, self-propelled device 6, and elevator control device 3 are logic circuits ( hardware) or software.

In the latter case, the elevator management device 1, the self-propelled device management device 5, the self-propelled device 6, and the elevator control device 3 are provided with computers that execute program instructions, which are software for realizing each function. This computer includes, for example, one or more processors, and a computer-readable recording medium storing the program. In the computer, the processor reads the program from the recording medium and executes it, thereby achieving the object of the present invention. For example, a CPU can be used as the processor. As the recording medium, a "non-temporary tangible medium" such as a ROM (Read Only Memory), a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. In addition, a RAM (Random Access Memory) or the like for developing the above program may be further provided. Also, the program may be supplied to the computer via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. Note that one aspect of the present invention can also be implemented in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

〔summary〕
As described above, the elevator management device according to aspect 1 of the present invention is an elevator management device that manages the operation of an elevator, and based on a destination floor call signal from the self-propelled device, a device use floor specifying unit for specifying a departure floor and a destination floor; a user floor specifying unit for specifying a destination floor, a direction starting from the departure floor of the user and ending at the destination floor of the user, and the self-propelled device starting from the departure floor of the self-propelled device. and the direction with the destination floor as the end point is the same direction, and the section starting at the user's departure floor and ending at the user's destination floor is the departure floor of the self-propelled device an allocation unit that allocates the self-propelled device to the elevator when included in a section whose starting point is the destination floor of the self-propelled device.

According to the above configuration, the elevator management device assigns the self-propelled device to the elevator in the above case. Therefore, only self-propelled devices that do not get on and off in the section where the user is on the elevator can be assigned to the elevator. As a result, it is possible to prevent the self-propelled device from contacting the user when the self-propelled device moves to get on and off. Therefore, the elevator management device can allocate the self-propelled device to the elevator while ensuring safety, since the possibility of the self-propelled device coming into contact with the user is reduced.

In the elevator management apparatus according to aspect 2 of the present invention, in aspect 1, the allocation unit determines whether the departure floor of the self-propelled device is the same as the departure floor or destination floor of the user, or The self-propelled device may not be assigned to the elevator when it exists between the departure floor and the destination floor of the person.

According to the above configuration, the elevator management device can allocate the self-propelled device to the elevator so as to avoid the situation where the self-propelled device gets on in the presence of the user.

In the elevator management device according to aspect 3 of the present invention, in aspect 1 or 2, the allocation unit determines whether the destination floor of the self-propelled device is the same floor as the user's departure floor or destination floor, or The self-propelled device may not be assigned to the elevator when it exists between the departure floor and the destination floor of the user.

According to the above configuration, the elevator management device can allocate the self-propelled device to the elevator so as to avoid the situation where the self-propelled device gets off under the presence of the user.

An elevator management device according to aspect 4 of the present invention is an elevator management device for managing the operation of an elevator, wherein the departure floor and the destination floor of the user are determined based on a destination floor call signal issued by the operation of the user. and a destination floor call signal from the self-propelled device received prior to the destination floor call signal. a device usage floor identifying unit that starts at the departure floor of the user and ends at the destination floor of the user; and the direction is the same direction, and the section starting from the departure floor of the user and ending at the destination floor of the user is the self-propelled device starting from the departure floor of the self-propelled device an assigning unit that assigns the user to the elevator when the user is included in a section whose end point is the destination floor of the mold device.

According to the above configuration, the elevator management device allocates users to elevators in the case described above. Therefore, the user can be assigned to the elevator only when the self-propelled device does not get on and off in the section where the user gets on the elevator. As a result, it is possible to prevent the self-propelled device from contacting the user when the self-propelled device moves to get on and off. Therefore, the elevator management device can assign users to elevators while ensuring safety because the possibility of the self-propelled device coming into contact with users is reduced.

In the elevator management apparatus according to aspect 5 of the present invention, in aspect 4, the allocation unit determines whether the destination floor of the self-propelled device is the same as the departure floor or the destination floor of the user, or The user may not be assigned to the elevator if the user exists between the departure floor and the destination floor of the user.

According to the above configuration, the elevator management device can assign users to elevators so as to avoid situations in which the self-propelled device gets off in the presence of users.

In the elevator management device according to aspect 6 of the present invention, in aspect 4 or 5, the assignment unit determines whether the departure floor of the self-propelled device is the same as the departure floor or destination floor of the user, or The elevator may not be assigned to the user if it exists between the departure floor and the destination floor of the user.

According to the above configuration, the elevator management device can assign users to elevators so as to avoid situations in which the self-propelled device gets on in the presence of users.

A control method for an elevator management device according to aspect 7 of the present invention is a control method for an elevator management device that manages the operation of an elevator, wherein, based on a destination floor call signal from the self-propelled device, and a destination floor call signal received prior to the destination floor call signal and issued by the user's operation, the departure floor of the user and a user floor specifying step of specifying a destination floor, a direction starting from the departure floor of the user and ending at the destination floor of the user, and the self-propelled device starting from the departure floor of the self-propelled device When the direction with the destination floor of the device as the end point is the same direction, and the section starting from the user's departure floor and ending at the user's destination floor is the departure floor of the self-propelled device. and an assigning step of assigning the self-propelled device to the elevator when included in a section starting from and ending at the destination floor of the self-propelled device.

According to the above method, the self-propelled device can be assigned to the elevator in a state where safety is ensured, as in mode 1 above.

A control method for an elevator management device according to an eighth aspect of the present invention is a control method for an elevator management device that manages operation of an elevator, wherein, based on a destination floor call signal issued by a user's operation, the user and a destination floor call signal from the self-propelled device received prior to the destination floor call signal. a device use floor identifying step of identifying a floor and a destination floor; a direction starting from the departure floor of the user and ending at the destination floor of the user; When the direction with the destination floor of the device as the end point is the same direction, and the section starting from the user's departure floor and ending at the user's destination floor is the departure floor of the self-propelled device. and an assigning step of assigning the user to the elevator when included in a section starting from and ending at the destination floor of the self-propelled device.

According to the above method, users can be assigned to elevators while ensuring safety, as in mode 4 above.

An elevator management system according to aspect 9 of the present invention includes the elevator management device according to any one of aspects 1 to 6 and a self-propelled device.

According to the above configuration, the self-propelled device can be assigned to the elevator while ensuring safety, as in the above aspect 1 or the above aspect 4.

The present invention is not limited to the above-described embodiments, but can be modified in various ways within the scope of the claims, and can be obtained by appropriately combining technical means disclosed in different embodiments. is also included in the technical scope of the present invention.

1 Elevator management device 2 Destination floor call registration device 3 Elevator control device 4 Elevator 6 Self-propelled device 11 Control unit 111 First identification unit (equipment use floor identification unit, user use floor identification unit)
112 second identification unit (user floor identification unit)
113 third identification unit (equipment usage floor identification unit)
114 First assigning unit (assigning unit)
115 second allocation unit (allocation unit)
116 determination unit 117 communication control unit 12 storage unit 121 registration information table 122 first list 123 second list 124 third list 125 fourth list 126 allocation candidate list 100 elevator management system S1 and S2 device use floor identification step, user use Floor identification steps S12 and S13 User floor identification steps S14 to S28 Allocation steps S32 and S33 Device use floor identification steps S34 to S48 Allocation step

Claims (9)

An elevator management device for managing the operation of an elevator,
a device utilization floor identifying unit that identifies a departure floor and a destination floor of the self-propelled device based on a destination floor call signal from the self-propelled device;
a user floor identifying unit that identifies the departure floor and destination floor of the user based on the destination floor call signal received prior to the destination floor call signal and issued by the user's operation;
A direction starting from the departure floor of the user and ending at the destination floor of the user and a direction starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device are the same direction. and a section starting from the departure floor of the user and ending at the destination floor of the user is the departure floor of the self-propelled device and ends at the destination floor of the self-propelled device. an allocation unit that allocates the self-propelled device to the elevator if it is included in the section to
An elevator management device comprising: If the departure floor of the self-propelled device is the same as the user's departure floor or destination floor, or is between the user's departure floor and destination floor, the allocation unit not assigning a running type device to the elevator;
The elevator management device according to claim 1. If the destination floor of the self-propelled device is the same as the user's departure floor or destination floor, or is between the user's departure floor and destination floor, the allocation unit 3. Elevator management device according to claim 1 or 2, wherein no running device is assigned to the elevator. An elevator management device for managing the operation of an elevator,
a user floor identification unit that identifies the departure floor and destination floor of the user based on a destination floor call signal issued by the user's operation;
a device use floor identification unit that identifies the departure floor and the destination floor of the self-propelled device based on the destination floor call signal from the self-propelled device received prior to the destination floor call signal;
A direction starting from the departure floor of the user and ending at the destination floor of the user and a direction starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device are the same direction. and a section starting from the departure floor of the user and ending at the destination floor of the user is the departure floor of the self-propelled device and ends at the destination floor of the self-propelled device. an allocation unit that allocates the user to the elevator if the user is included in the section that
An elevator management device comprising: If the destination floor of the self-propelled device is the same as the user's departure floor or destination floor, or is between the user's departure floor and destination floor, not assigning a person to said elevator;
The elevator management device according to claim 4. If the departure floor of the self-propelled device is the same as the user's departure floor or destination floor, or is between the user's departure floor and destination floor, the allocation unit determines whether the use not assigning said elevator to a person
The elevator management device according to claim 4 or 5. A control method for an elevator management device that manages operation of an elevator, comprising:
a device utilization floor identifying step of identifying a departure floor and a destination floor of the self-propelled device based on a destination floor call signal from the self-propelled device;
a user floor identification step of identifying the departure floor and destination floor of the user based on the destination floor call signal received prior to the destination floor call signal and issued by the user's operation;
A direction starting from the departure floor of the user and ending at the destination floor of the user and a direction starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device are the same direction. and a section starting from the departure floor of the user and ending at the destination floor of the user is the departure floor of the self-propelled device and ends at the destination floor of the self-propelled device. an assignment step of assigning the self-propelled device to the elevator if it is included in the section to
A control method for an elevator management device comprising: A control method for an elevator management device that manages operation of an elevator, comprising:
a user floor identification step of identifying the departure floor and destination floor of the user based on a destination floor call signal issued by the user's operation;
a device utilization floor specifying step of specifying a departure floor and a destination floor of the self-propelled device based on a destination floor call signal from the self-propelled device received prior to the destination floor call signal;
A direction starting from the departure floor of the user and ending at the destination floor of the user and a direction starting from the departure floor of the self-propelled device and ending at the destination floor of the self-propelled device are the same direction. and a section starting from the departure floor of the user and ending at the destination floor of the user is the departure floor of the self-propelled device and ends at the destination floor of the self-propelled device. an assigning step of assigning the user to the elevator if the user is included in the section to
A control method for an elevator management device comprising: an elevator management device according to any one of claims 1 to 6;
the self-propelled device;
Elevator management system including.

Images