JP7226599B1 - ELEVATOR MANAGEMENT DEVICE, ELEVATOR MANAGEMENT SYSTEM AND CONTROL METHOD - Google Patents

Abstract

A technology is realized in which a user and a self-propelled device ride together in an elevator from the same floor while ensuring the safety of the user. A boarding status information acquisition unit (111) for acquiring boarding status information including boarding completion information indicating that a self-propelled device (6) assigned to an elevator has boarded an elevator at a departure floor. ), a driving condition information acquisition unit (112) for acquiring driving condition information including elevator departure/arrival information and traveling direction, and after boarding completion information is acquired, the elevator departs from the departure floor and its traveling direction is determined. An allocation unit ( 113) and [Selection drawing] Fig. 3

Description

The present invention relates to technology for managing elevators.

Patent Literature 1 describes a technique for notifying a device provided in a hall or a device provided in a car of information indicating boarding/alighting of a self-propelled device based on a call for an elevator by the self-propelled device. ing.

Japanese Patent Laid-Open No. 2002-200002 describes a technique for setting an elevator to a robot-only mode when no person is detected in the car and in the boarding/alighting area before the robot gets into the elevator.

WO2018/066054 JP 2009-234716 A

In the technology described in Patent Document 1, even if information indicating boarding and alighting is notified, the user does not necessarily act so as not to touch the self-propelled device, and the safety of the user is not guaranteed. be. Further, in the technique described in Patent Document 2, when the robot gets on the elevator, it is in the robot-only mode, so there is a problem that the user cannot get on the same floor as the robot.

One aspect of the present invention has been made to solve the above problems, and realizes a technology that allows a user and a self-propelled device to ride together in an elevator from the same floor while ensuring the safety of the user. With the goal.

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 operation of a plurality of elevators, and is assigned to one of the plurality of elevators. a boarding state information acquiring unit for acquiring boarding state information including boarding completion information indicating that boarding operation to the elevator on the departure floor is completed; A driving situation information acquisition unit that acquires the driving situation information; and from acquisition of the boarding completion information to acquisition of the driving situation information including information indicating that the elevator departs from the departure floor and its traveling direction. and an allocation unit that allocates the elevator to a call operation in the same direction as the traveling direction by a user who is scheduled to board from the departure floor during the first period of.

In order to solve the above problems, a control method for an elevator management device according to one aspect of the present invention is a control method for controlling an elevator management device that manages operation of a plurality of elevators, wherein any one of the plurality of elevators a boarding status information acquisition step for acquiring boarding status information including boarding completion information indicating that a self-propelled device assigned to one elevator has completed boarding operation to the elevator at the departure floor; and a step of acquiring driving condition information including departure/arrival information and traveling direction of the elevator; an allocating step of allocating the elevator to the call operation in the same direction as the traveling direction by the user who is scheduled to get on from the departure floor performed during a first period until the driving status information is acquired; include.

ADVANTAGE OF THE INVENTION According to 1 aspect of this invention, a user and a self-propelled apparatus can be made to board an elevator from the same departure floor, ensuring a user's safety.

It is a mimetic diagram explaining a technical idea of an elevator management system concerning one embodiment of the present invention. It is a block diagram showing an example of the whole elevator management system composition concerning one embodiment of the present invention. It is a block diagram showing an example of functional composition of an elevator management device concerning one embodiment of the present invention. It is a figure showing an example of composition of an elevator control device concerning one embodiment of the present invention, and an elevator. It is a figure showing an example of composition of a self-propelled device concerning one embodiment of the present invention. FIG. 4 is a flow diagram showing an example of the flow of a control method according to one embodiment of the present invention; It is a timing chart explaining an example of a flow of a control method which enables a user and a self-propelled device to ride together in one embodiment of the present invention. It is a timing chart explaining an example of a flow of a control method which makes a user and a self-propelled device impossible to ride together in one embodiment of the present invention. It is a flow figure showing an example of a flow of processing by a self-propelled device concerning one embodiment of the present invention. FIG. 4 is a flow chart showing an example of the flow of processing when boarding status information is received by the elevator management device according to one embodiment of the present invention; FIG. 4 is a flow chart showing an example of the flow of processing when allocation request data is received by the elevator management device according to one embodiment of the present invention; FIG. 4 is a flowchart showing an example of a detailed flow of allocation processing to self-propelled devices by the elevator management device according to one embodiment of the present invention; FIG. 4 is a flow diagram showing an example of a detailed flow of allocation processing to users by the elevator management device according to one embodiment of the present invention; It is a block diagram which shows an example of the whole structure of the elevator management system based on the modification of this embodiment.

Hereinafter, the elevator management system 100 according to one embodiment of the present invention will be described in detail.

[Embodiment]
<Overview of Elevator Management System 100>
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 manages one or more elevators 4 . Each elevator 4 is also called "elevator". The elevator management system 100 is a system capable of notifying the user H of the elevator 4 and the self-propelled device 6 of the optimum number by the destination floor registration function. 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, a ratio request operation described later, may be one or more. When a plurality of users H are registered at one time, it is called group registration. The number of self-propelled devices 6 registered at one time may be one, or may be plural.

Here, the "destination floor registration function" is to allocate the optimum number according to the destination floor to be used, and guide the use target to the optimum number as the number that the use target rides, so that the use target is elevator 4. It is a function that can effectively shorten the time to wait for arrival. 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 4 assigned to the allocation request operation to be used, and is either one or a plurality of elevators 4 . If there are a plurality of assignable elevators 4, the optimum number is selected from them. If there is one elevator 4 that can be assigned, the elevator 4 is the optimum number.

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 data includes information indicating the destination floor and information indicating the departure floor. The "allocation request operation" is an example of the "call operation" described in the claims. When the target of use is the user H, the allocation request operation may be, for example, an operation in which the user H inputs a desired destination floor or the like to the landing destination floor registration device 2 installed on the departure floor. The landing destination floor registration device 2 sends information including information indicating the input destination floor and information indicating the floor where the landing destination floor registration device 2 is installed (that is, the departure floor) to the elevator management device 1. may be sent to 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 hall destination floor registration device 2 . When the object of use is the self-propelled device 6, for example, the self-propelled device 6 may directly transmit the allocation request data to the elevator management device 1, or send the desired destination to the hall destination floor registration device 2. An operation of inputting a floor or the like may be performed.

The self-propelled device 6 may be an automatic transport device, a self-propelled cleaning device, other multifunctional robots, etc., which are installed in the building in advance. 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 with reference to FIG. FIG. 1 is a schematic diagram for explaining the technical concept of an elevator management system 100. As shown in FIG. As illustrated in FIG. 1, according to the present technical concept, two self-propelled devices 6 (6-1, 6-2) and one user H can travel from the same departure floor to the same number. It is possible to ride in the car 41 together. Here, in order to ensure the safety of the user H, it is desirable to reduce the chances of contact between the user H and the self-propelled devices 6-1 and 6-2 as much as possible. Although one user H is shown in FIG. 1, there may be multiple users H targeted by the present technical concept. In addition, although two self-propelled devices 6-1 and 6-2 are shown in FIG. , three or more.

Therefore, the inventors paid attention to the period from when the self-propelled device 6 completes the boarding operation of getting on the car 41 at the departure floor to before the car 41 departs from the departure floor. This period is hereinafter also referred to as a “first period”. Since the self-propelled device 6 has already stopped operating during the first period, the possibility of the user H touching the self-propelled device 6 is low. Further, in the first period, since the car 41 stays at the departure floor, the user H can board the car 41 .

Specifically, as shown in FIG. 1, in step G1, the self-propelled devices 6-1 and 6-2 start getting on the car 41 of the elevator 4 in which the user H does not get on. . Next, in step G2, the self-propelled devices 6-1 and 6-2 complete the boarding operation. After that, the user H starts getting on the car 41 until the car 41 departs. In step G3, the user H completes getting on the car 41. FIG. As a result, the elevator management system 100 can allow the user H and the self-propelled device 6 to ride together in the elevator 4 from the same departure floor while ensuring the safety of the user H. The configuration and operation of the elevator management system 100 that implements the technical idea will be described in detail below.

<Configuration of Elevator Management System 100>
Next, the overall configuration of the elevator management system 100 according to this embodiment will be described with reference to FIG. FIG. 2 is a block diagram showing the overall configuration of the elevator management system 100 according to this embodiment. Note that the elevator management system 100 shown in FIG. 2 has a configuration in which the elevator management device 1 directly controls the self-propelled device 6 . A case where the elevator management device 1 controls the self-propelled device 6 via another device will be described later as a modified example.

2, the elevator management system 100 includes an elevator management device 1, a hall destination floor registration device 2, elevator control devices 3-1, 3-2, . . . , 3-n, elevators 4-1, 4-2. , . . . , 3-n will be simply referred to as “elevator control device 3” when there is no need to distinguish between the elevator control devices 3-1, 3-2, . . . , 4-n are also simply referred to as “elevator 4” when there is no need to specifically distinguish between the elevators 4-1, 4-2, . The elevator control device 3 is provided corresponding to each elevator 4 (each car). For example, the elevator control device 3-1 is provided corresponding to the elevator 4-1, and the elevator control device 3-2 is provided corresponding to the elevator 4-2. The elevator management system 100 shown in FIG. 2 is configured to manage n elevators 4 (a plurality of elevators). A case where the elevator management system 100 manages a single car will be described later as a modified example.

The elevator management device 1 allocates one of the plurality of elevators 4 to the target of use (user H or self-propelled device 6) in response to allocation request data from the target of use. The hall destination floor registration device 2 receives an allocation request operation by a utilization target and transmits allocation request data to the elevator management device 1 . The elevator control device 3 controls operation of the elevator 4 . The self-propelled device 6 is installed in a building including the elevator 4 and transmits allocation request data to the elevator management device 1 . Details of the configuration of each device will be described.

(Configuration of elevator management device 1)
The elevator management device 1 is configured using a computer including a processor, memory and network interface. The elevator management device 1 is a device that manages the operation of multiple elevators 4 . A functional configuration of the elevator management device 1 will be described with reference to FIG. FIG. 3 is a block diagram showing the functional configuration of the elevator management device 1. As shown in FIG. As shown in FIG. 3, the elevator management device 1 includes a control section 110, a storage section 120, and a communication section .

The control unit 110 is configured by a processor. The control section 110 controls each section of the computer so as to realize each function of the elevator management device 1 . The control unit 110 receives allocation request data from the target of use, and determines whether or not to allocate each car to the target of use based on the received allocation request data and the information of the already allocated machines. The control unit 110 determines the optimum car number from among allocable car number candidates, and allocates the optimum car number to the utilization target. In addition, the control unit 110 comprehensively manages the operation of each car.

In addition, the control unit 110 controls the movement and operation of the self-propelled device 6 installed in the building. When a plurality of self-propelled devices 6 are deployed in the building, in communication between the elevator management device 1 and the self-propelled devices 6, the identification information (ID) given to each of the self-propelled devices 6 is Used. The control unit 110 may be 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. Thereby, the control unit 110 can monitor and control the position and work status of each self-propelled device 6 . The control unit 110 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 control unit 110 includes a boarding status information acquisition unit 111 , a driving status information acquisition unit 112 , an allocation unit 113 , and an open state adjustment unit 114 .

The boarding status information acquisition unit 111 acquires boarding status information of the self-propelled device 6 assigned to one of the plurality of elevators 4 . Below, elevator 4 assigned to self-propelled device 6 may be described as "the elevator 4 concerned." Here, the boarding status information includes boarding completion information indicating that the self-propelled device 6 has finished boarding the elevator 4 at the departure floor. The boarding status information may also include boarding schedule information indicating that the self-propelled device 6 is scheduled to board the elevator 4 from the departure floor. The elevator 4 may be an elevator 4 in which no user H is boarding when departing from the departure floor.

The driving condition information acquisition unit 112 acquires the driving condition information including the departure/arrival information and the traveling direction of the elevator 4 .

The allocation unit 113 performs the first period from when the boarding completion information is acquired to when the information indicating that the elevator 4 will depart from the departure floor and the driving status information including the traveling direction is acquired. The elevator 4 is assigned to the call operation in the same direction as the travel direction by the user H who is scheduled to board from the departure floor. Further, the allocation unit 113 does not allocate the elevator 4 to the aforementioned call operation by the user H during the second period from when the boarding schedule information is acquired until when the boarding completion information is acquired. It may be a configuration.

When the elevator 4 is assigned to the call operation performed by the user H during the first period, the open state adjustment unit 114 determines the period during which the doors of the elevator 4 on the departure floor are kept open. Adjust length.

It should be noted that the boarding situation information acquisition unit 111 is an example of a configuration that realizes the boarding situation information acquisition unit described in the claims. The driving situation information acquisition unit 112 is an example of a configuration that implements the driving situation information acquisition unit described in the claims. The allocation unit 113 is an example of a configuration that implements the allocation unit described in the claims. The open state adjuster 114 is an example of a configuration that implements the open state adjuster described in the claims. Details of these units will be described later in the "flow of the control method S10 of the elevator management apparatus 1".

Storage unit 120 is configured by a memory. Storage unit 120 stores various computer programs read by control unit 110, data used in various processes executed by control unit 110, and the like.

The communication unit 130 is configured by a network interface. The communication unit 130 connects to an in-facility network installed in the building. The in-facility network may be, for example, a wireless LAN (Local Area Network), a wired LAN, or a combination thereof, but is not limited to these. The control unit 110 communicates with the hall destination floor registration device 2 , the elevator control device 3 , and the self-propelled device 6 via the communication unit 130 .

(Configuration of platform destination floor registration device 2)
The hall destination floor registration device 2 is provided in the elevator hall of each floor of the building. The landing destination floor registration device 2 receives an allocation request operation by a utilization target, and transmits allocation request data such as the input destination floor to the elevator management device 1 . Identification information (ID) given to each of the hall destination floor registration devices 2 is used in communication between the elevator management device 1 and the hall destination floor registration device 2 . When the landing destination floor registration device 2 receives the information of the optimum elevator in response to the allocation request operation from the elevator management device 1, it displays the information indicating the optimum elevator on a display screen or the like.

(Configuration of Elevator Control Device 3 and Elevator 4)
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 loading the user H or the self-propelled device 6, an operation control panel 40 for controlling the elevation of the car 41, and a door 42 provided at the landing of each floor.

The elevator controller 3 is a computer communicably connected to the elevator 4 . The elevator control device 3 controls operation of the elevator 4 . The elevator control device 3 has a control section 30 . The control unit 30 is configured by a processor. In addition, the control unit 30 controls each unit of the computer so as to realize each function of the elevator control device 3 .

The control unit 30 includes an instruction acquisition unit 31 , an operating condition 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 . The instructions acquired by the instruction acquisition unit 31 include a stop floor setting instruction, a destination floor setting instruction, a stop floor change instruction, a destination floor change instruction, an open period adjustment instruction for the door 42, and the like.

The operation 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 operation status, the open/close status of the landing 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. .

(Configuration of self-propelled device 6)
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 is equipped with, for example, a computer including a processor, memory and network interface.

A configuration of the self-propelled device 6 will be described with reference to FIG. FIG. 5 is a diagram showing an example of the configuration of the self-propelled device 6. As shown in FIG. The self-propelled device 6 includes a control section 610, a storage section 620, a communication section 630, and a moving mechanism 640, for example.

Control unit 610 is configured by a processor. The control section 610 controls each section of the computer and the movement mechanism 640 so as to realize each function of the self-propelled device 6 . The control unit 610 includes, for example, a boarding schedule transmission unit 611 , a boarding completion transmission unit 612 , and a movement mechanism control unit 613 . The boarding schedule transmission unit 611 transmits boarding schedule information to the elevator management device 1 . The boarding completion transmitting unit 612 transmits boarding completion information to the elevator management device 1 . The moving mechanism control section 613 controls the operation of the moving mechanism 640 under the control of the elevator management device 1 . Details of these units will be described later in the "flow of processing executed by the self-propelled device 6".

Storage unit 620 is configured by a memory. Storage unit 620 stores various computer programs read by control unit 610, data used in various processes executed by control unit 610, and the like.

Communication unit 630 is configured by a network interface. The communication unit 630 connects to an in-facility network laid in the building. The intra-facility network is as described above. The control unit 610 communicates with the elevator management device 1 via the communication unit 630 .

The moving mechanism 640 is a mechanism for moving the main body of the self-propelled device 6 . The moving mechanism 640 may be wheels, caterpillars, legs for walking, etc., but is not limited to these.

<Flow of control method S10 for controlling elevator management device 1>
The flow of the control method S10 for controlling the elevator management device 1 configured as described above will be described with reference to FIG. FIG. 6 is a flowchart for explaining the flow of control method S10. As shown in FIG. 6, the control method S10 includes steps S1-S8.

In step S<b>1 , the boarding status information acquisition unit 111 acquires boarding status information of the self-propelled device 6 assigned to one of the elevators 4 . It has been described above that the boarding status information may include boarding completion information or boarding schedule information, and that the elevator 4 may be an elevator in which no user H is boarding when departing from the departure floor. As I said. The process of step S1 may be performed at any time, for example, in response to transmission of boarding status information from the self-propelled device 6 . In other words, the processing of step S1 may be performed in parallel with the processing after step S2, or may be performed in a different order.

In step S<b>2 , the driving situation information acquisition unit 112 may acquire driving situation information including departure/arrival information and the traveling direction of the elevator 4 . The process of step S2 is performed at any time, for example, in response to transmission of operating status information from the elevator control device 3 that controls the elevator 4. FIG. In other words, the process of step S2 may be performed in parallel with the processes after step S1 or step S3, or may be performed in a different order.

In step S3, the allocation unit 113 receives an allocation request operation (call operation) in the same direction as the above-described traveling direction by the user H who is scheduled to board from the departure floor. "Allocation request operation in the same direction as the traveling direction described above" may be, for example, "allocation request operation in the same direction as the destination floor of the self-propelled device 6". In other words, the destination floor of the self-propelled device 6 and the destination floor of the user H included in the allocation request operation are included in the same direction when viewed from the departure floor.

In step S4, the allocation unit 113 determines that the allocation request operation received in step S4 indicates that the elevator 4 will depart from the departure floor after the boarding completion information is acquired, and that the elevator 4 will depart from the departure floor. is acquired in the first period. When it is judged as Yes in this step, the processing of the next step S5 is performed.

In step S5, the allocation unit 113 may be configured to allocate the elevator 4 allocated to the self-propelled device 6 in response to the allocation request. In other words, the allocation unit 113 determines that the user H can ride with the elevator 4 to which the self-propelled device 6 is allocated from the same departure floor.

In step S6, when the open state adjustment unit 114 assigns the elevator 4 assigned to the self-propelled device 6 to the above call operation by the user H performed in the first period, You may adjust the length of the period which maintains the open state of the door of the elevator 4. FIG.

When it is determined No in step S4, in step S7, the allocation unit 113 determines whether the allocation request operation is performed during the second period from when the boarding schedule information is acquired until when the boarding completion information is acquired. to judge. When it is judged as Yes in this step, the processing of the next step S8 is performed.

In step S8, the assignment unit 113 may be configured not to assign the elevator 4 assigned to the self-propelled device 6 to the assignment request operation. In other words, the allocation unit 113 determines that the user H cannot ride with the elevator 4 to which the self-propelled device 6 is allocated from the same departure floor. "Do not assign the elevator 4 assigned to the self-propelled device 6" may mean, for example, "assign another elevator 4 other than the relevant elevator 4", or "The relevant elevator 4 cannot be boarded." It may be "notifying something." However, the process for realizing "not assigning the elevator 4 assigned to the self-propelled device 6" is not limited to these.

It should be noted that FIG. 6 does not limit that the processes of steps S1 to S8 are executed in this order. A part or all of the processing of steps S1 to S8 can be performed in different order or in parallel as required.

(Specific example of cases where it is possible to ride together)
FIG. 7 is a timing chart illustrating a specific example of a case in which the user H and the self-propelled device 6 can ride together using the control method S10. Here, the number of users H who perform the allocation request operation on the lobby floor (end floor) of the plurality of elevators 4 is one, and the number of self-propelled devices 6 transmitting allocation request data is one. A case will be described. As shown in FIG. 7, the timing chart includes steps A1 to A8.

In step A1, the allocation unit 113 of the elevator management device 1 determines the optimum number among the plurality of elevators 4 according to the allocation request data received from the self-propelled apparatus 6, and sends information indicating the optimum number to the self-propelled type. Send to device 6 . The optimum elevator number is also referred to as the elevator 4 .

In addition, the elevator management device 1 controls the elevator 4 via the elevator control device 3 so as to move the elevator 4 toward the departure floor (end floor) included in the allocation request data received from the self-propelled device 6. Control.

In step A2, when the boarding schedule transmission unit 611 of the self-propelled device 6 receives the information indicating the elevator 4 as the optimum car, it may transmit the boarding status information including the boarding schedule information to the elevator management device 1. . As a result, the boarding status information acquisition unit 111 of the elevator management device 1 acquires the boarding status information including the boarding schedule information from the self-propelled device 6 . The time when the elevator management device 1 acquires boarding schedule information is assumed to be t1. This step is a specific example of step S1 in the control method S10.

After that, the time when the elevator 4 reaches the departure floor (end floor) under the control of the elevator control device 3 is t2. Further, after time t2, the time when the door 42 of the elevator 4 is opened under the control of the elevator control device 3 is defined as t3.

In step A<b>3 , the movement mechanism control section 613 of the self-propelled device 6 controls the movement mechanism 640 to cause the self-propelled device 6 to start boarding the elevator 4 . It is assumed that the time when the self-propelled device 6 starts the boarding operation is t4.

Here, the boarding motion may be a motion in which the movable portion of the self-propelled device 6 moves along with boarding the elevator 4 . The movable portion includes a moving mechanism 640 . In other words, the riding motion includes the motion of moving mechanism 640 . Also, the self-propelled device 6 may include other movable parts (not shown) in addition to the moving mechanism 640 . For example, if the other movable part is a folding bed, the boarding action may include folding the empty bed to occupy less space within the car 41 . Further, when the other movable part is the hand of the humanoid robot, the boarding motion may include a hand raising motion to notify the surroundings of the boarding. In this way, the riding motion is not limited to the motion of moving the moving mechanism 640, and may include motions of moving various movable parts along with riding. However, the "boarding motion" is not limited to the above example.

In step A4, the boarding completion transmission unit 612 of the self-propelled device 6 may transmit boarding status information including boarding completion information to the elevator management device 1 when the boarding operation is completed. As a result, the boarding status information acquisition unit 111 of the elevator management device 1 acquires the boarding status information including the boarding completion information from the self-propelled device 6 . The time when the elevator management device 1 acquires boarding completion information is set to t5. This step is a specific example of step S1 in the control method S10.

Here, the boarding completion transmitting unit 612 confirms that (i) the self-propelled device 6 is positioned in the car 41 and (ii) the operation of the self-propelled device 6 has stopped, for example. In this case, boarding status information including boarding completion information may be transmitted to the elevator management apparatus 1 assuming that the boarding operation is completed.

(i) "The self-propelled device 6 is located in the car 41" may refer to being located in a predetermined range within the car 41 (for example, around the wall facing the door 42). In addition, the position of the self-propelled device 6 within the cage 41 can be detected by, for example, various sensors (eg, a camera, a distance measuring sensor, etc.). Some or all of such various sensors may be mounted on the self-propelled device 6 or may be installed inside the car 41 .

In addition, (ii) "the operation of the self-propelled device 6 is stopped" may refer to that the movable portion of the self-propelled device 6 is not moving. If the riding motion includes motions of a plurality of movable parts, even if "the motion of the self-propelled device 6 is stopped" means that none of the movable parts are moving. good. Further, when the self-propelled device 6 has a sleep mode in which the operation is temporarily stopped, "the operation of the self-propelled device 6 is stopped" may refer to a state in which the sleep mode has been entered. .

Here, a period (time points t5 to t9) from acquisition of boarding completion information to acquisition of driving status information including information indicating that the elevator will depart from the departure floor corresponds to a first period. Note that the allocation unit 113 performs processing assuming that it is the first period from time t5 until driving situation information indicating time t9, which will be described later, is acquired.

At step A5, the allocation unit 113 of the elevator management device 1 receives allocation request data from the user H who is scheduled to board from the departure floor in the first period. Let t6 be the time when the elevator management device 1 receives the allocation request data. Specifically, the allocation unit 113 receives such allocation request data from the hall destination floor registration device 2 provided in the hall of the departure floor. The allocation request data includes information indicating the destination floor input by the user H and information indicating the departure floor. This step is a specific example of step S3 in the control method S10 and a specific example of determining Yes in step S4.

At step A6, the allocation unit 113 allocates the elevator 4 to the allocation request operation (call operation) performed by the user H at time t6. The time when the elevator 4 is assigned is t7. In other words, the allocation unit 113 determines that the self-propelled device 6 has already completed the boarding operation and that the user H can ride with the elevator 4 before departure. This step is a specific example of step S5 in the control method S10.

More specifically, the allocation unit 113 determines the elevator 4 as an allocation candidate for the allocation request operation. Also, the allocation unit 113 determines the optimum car from among the allocation candidates, and transmits information indicating the determined optimum car to the hall destination floor registration device 2 which is the source of the allocation request data. Here, it is assumed that the elevator 4 is determined as the optimum number.

At step A7, the open state adjusting unit 114 adjusts the length of the period during which the doors 42 of the elevator 4 are kept open at the departure floor. For example, the open state adjusting unit 114 may adjust the length of the period so that the open state is maintained for a predetermined period (time points t7 to t8) after allocating the elevator 4 in response to the allocation request operation. In other words, the open state adjustment unit 114 determines the timing of the time t8 at which the door 42 is closed. Such a predetermined period may be predetermined as a length sufficient for the user H to get on the vehicle. Thereby, the user H can get on the elevator 4 . Step A7 is a specific example of step S6 in control method S10.

At step A8, the operating condition information acquisition unit 112 of the elevator management device 1 acquires operating condition information including information indicating that the elevator 4 will depart from the departure floor. The time point at which this driving status information is acquired is defined as time point t9. When the driving status information is acquired, the allocation unit 113 assumes that the first period has ended and performs subsequent processing. Step A8 is a specific example of step S2 in control method S10.

As a result, in the first period, the self-propelled device 6 has already stopped operating in the car 41 of the elevator 4, so the user H can ride with the self-propelled device 6 without touching it. can be done. Further, in the first period, the elevator 4 in which the self-propelled device 6 has boarded has not departed, so the user H can get into the elevator 4 and ride together with the self-propelled device 6 .

In FIG. 7, an example in which the allocation request operation by the user H is performed during the first period (time points t5 to t9) until the time point t8 when the door 42 is closed has been described. On the other hand, it is conceivable that the allocation request operation by the user H may be performed after the door 42 is closed during the first period (time points t5 to t9). In such a case, the open state adjusting unit 114 may adjust the door 42 to open again and then maintain the open state for a predetermined period. Alternatively, in such a case, the allocation unit 113 may not allocate the elevator 4 to the allocation request operation. Also, with reference to FIG. 7, an example has been described in which the allocation request operation by the user H is performed on the lobby floor (side floor). If the allocation request operation of the user H is performed on an intermediate floor, the allocation unit 113 of the elevator management device 1 operates as follows. In this case, in step A5, the allocation unit 113 determines that the destination floor included in the allocation request data by the user H and the destination floor of the self-propelled device 6 allocated to the elevator 4 are from the departure floor (intermediate floor). It is determined whether or not they are included in the same direction when viewed, and if they are the same, the same operation is performed thereafter.

(Concrete examples of cases where passengers cannot ride together)
FIG. 8 is a timing chart illustrating a specific example of a case in which the user H and the self-propelled device 6 cannot ride together using the control method S10. Here, in the specific example shown in FIG. 7, allocation request data from user H was acquired at time t6 included in the first period (time t5 to t9). On the other hand, in the specific example shown in FIG. 8, the allocation request data from the user H on the lobby floor (side floor) is acquired at time t21 included in the second period (time t1 to t5).

In this case, the timing chart shown in FIG. 8 includes steps A1 to A3, B21 to B22, A4 and A8. Steps A1 to A4 and A8 are as described with reference to FIG. Here, steps B21 and B22 will be described.

In step B21, the allocation unit 113 of the elevator management device 1 receives allocation request data from the user H who is scheduled to board from the departure floor in the second period. Let t21 be the time when the allocation request data is received. The details of the allocation request data are as described in the control method S10.

In step B22, the allocation unit 113 does not allocate the elevator 4 to the allocation request operation by the user H performed at time t21. In other words, the allocation unit 113 determines that the user H cannot ride together in the elevator 4 until the self-propelled device 6 completes boarding the elevator 4 at the departure floor. It decides not to assign this elevator 4 to H.

As described above, in the second period, the self-propelled device 6 has not completed the operation of getting on the elevator 4 scheduled to get on from the departure floor. , the user H may touch the self-propelled device 6 . Therefore, by not assigning the user H to the elevator 4 during the second period, the safety of the user H can be ensured.

More specifically, as shown in FIG. 8, the second period includes a 2a period, a 2b period, and a 2c period. The 2a-th period is a period (time points t4 to t5) from when the self-propelled device 6 starts to complete the boarding operation. FIG. 8 illustrates a case where the time t21 at which the user H performs the allocation request operation is included in the 2a period. In this period 2a, if the user H is assigned to the elevator 4, the user H may come into contact with the self-propelled device 6 because the self-propelled device 6 is in boarding motion.

The 2b period is a period from when the door 42 of the elevator 4 is opened at the departure floor to when the self-propelled device 6 starts boarding operation (time points t3 to t4). Here, the self-propelled device 6 does not necessarily start the boarding operation at the same time when the door 42 of the elevator 4 is opened, and the 2b period may occur. There is a possibility that the user H may perform an allocation request operation during the 2b period. In this period 2b, if the user H is assigned to the elevator 4, there is a possibility that the self-propelled device 6 will start boarding after the user H starts boarding. There is a possibility of contact with the running type device 6 .

The 2c-th period is a period (time points t1 to t3) from when the self-propelled device 6 transmits the boarding schedule information to when the door 42 of the elevator 4 is opened at the departure floor. In the 2c-th period, the door 42 of the elevator 4 has not yet opened, so the self-propelled device 6 has not yet performed the boarding operation. There is a possibility that the user H may perform an allocation request operation during the 2c period. In this period 2c, if the user H is assigned to the elevator 4, both the user H and the self-propelled device 6 will start boarding after the door 42 opens, and there is a possibility that they will come into contact with each other. There is

In this way, by not allocating the user H to the allocation request operation performed by the user H during the second period including the 2a period, the 2b period, and the 2c period, the user H safety can be ensured.

<Specific example of processing for realizing control method S10>
A specific example of processing executed by each device to realize the control method S10 of the elevator management device 1 described above will be described with reference to the drawings. In the specific example of the processing described below, the number of users H who perform allocation request operations for a plurality of elevators 4 is one, and the number of self-propelled devices 6 transmitting allocation request data is A case where there is more than one will be described.

(Processing flow of self-propelled device 6)
A specific example of the flow of processing executed by the self-propelled device 6 to implement the control method S10 will be described with reference to FIG. FIG. 9 is a flow diagram showing a specific example of the flow of processing executed by the self-propelled device 6. As shown in FIG. As shown in FIG. 9, process S100 includes steps S101 to S109.

In step S<b>101 , the control unit 610 transmits allocation request data to the elevator management device 1 . The allocation request data includes information indicating the departure floor (orgFloor), information indicating the destination floor (destFloor), and information indicating the attribute of the user (userType). userType is here "self-propelled device".

In step S102, the control unit 610 determines whether or not information indicating the elevator 4 (hereinafter also referred to as the assigned elevator) assigned according to the assignment request data has been received from the elevator management device 1. When determining No in this step, the control unit 610 repeats the processing of this step. When it is judged as Yes in this step, the processing of the next step S103 is executed.

In step S<b>103 , control unit 610 stores the received information indicating the assigned car (acar) in storage unit 620 .

In step S104, control unit 610 determines whether the destination floor (destFloor) is higher than the departure floor (orgFloor). If it is determined Yes in this step, the control unit 610 sets "UP direction (upward direction)" as information indicating the moving direction (dir) of the self-propelled device 6 in step S105.

When it is determined No in step S104, in step S106, the control unit 610 sets "DOWN direction (downward)" as information indicating the movement direction (dir) of the self-propelled device 6. FIG.

In step S<b>107 , the boarding schedule transmission unit 611 transmits boarding status information including boarding schedule information to the elevator management device 1 . The boarding schedule information includes identification information (robotID) of the self-propelled device 6, information indicating the assigned car (acar), information indicating the departure floor (orgFloor), and information indicating the movement direction (dir). This process is an example of the process of the self-propelled device 6 corresponding to step S1 in the control method S10 described with reference to FIG.

Further, in step S107, when the assigned car (acar) arrives at the departure floor (orgFloor) and the door 42 opens, the moving mechanism control unit 613 controls the moving mechanism 640 so that the car 41 is boarded. As a result, the self-propelled device 6 starts boarding on the departure floor (orgFloor).

In step S108, the control unit 610 determines whether or not the self-propelled device 6 has completed the boarding operation on the departure floor (orgFloor). A specific example of determining whether or not the boarding motion is completed is as described in step A4 shown in FIGS. When determining No in this step, the control unit 610 repeats the processing of this step. When it is judged as Yes in this step, the processing of the next step S109 is executed.

In step S<b>109 , the boarding completion transmitting unit 612 transmits boarding status information including boarding completion information to the elevator management device 1 . The process of this step is an example of the process of the self-propelled device 6 corresponding to step S1 in the control method S10 described with reference to FIG.

(Processing flow of elevator management device 1)
A specific example of the flow of processing executed by the elevator management device 1 to implement the control method S10 will be described with reference to FIGS. 10 to 13. FIG.

(Flow of processing when boarding status information is received)
FIG. 10 is a flowchart showing the flow of processing S200 of the elevator management device 1 when boarding status information is received from the self-propelled device 6. As shown in FIG. As shown in FIG. 10, the process S200 includes steps S201-S204.

In step S<b>201 , the boarding status information acquisition unit 111 of the elevator management device 1 determines whether boarding status information including boarding schedule information has been received from the self-propelled device 6 . The processing of this step is an example of processing for realizing step S1 in the control method S10 described with reference to FIG. When it is judged as Yes in this step, the processing of the next step S202 is executed.

In step S202, the boarding status information acquiring unit 111 adds the boarding schedule information (including robotID, acar, orgFloor, and dir) to the boarding list (robotBoard[acar][orgFloor][dir]). The identification information robotID of the rantotype device 6 is added.

Here, the boarding list is a three-dimensional array indexed by car number, departure floor, and travel direction. In other words, the boarding list stores a list of self-propelled devices 6 that are assigned to the same car heading for the same movement direction from the same departure floor.

If No is determined in step S201, the process of next step S203 is executed.

In step S<b>203 , the boarding status information acquisition unit 111 determines whether boarding status information including boarding completion information has been received from the self-propelled device 6 . The processing of this step is an example of processing for realizing step S1 in the control method S10 described with reference to FIG. When it is determined as Yes in this step, the processing of the next step S204 is executed.

In step S204, the boarding status information acquisition unit 111 selects the vehicle from the boarding list (robotBoard[acar][orgFloor][dir]) based on the boarding completion information (including robotID, acar, orgFloor, and dir). The identification information robotID of the rantotype device 6 is deleted.

When it is determined No in step S203, or after executing the processing of steps S202 and S204, the elevator management device 1 repeats the processing from step S201.

As a result, the boarding list includes the number of self-propelled devices 6 assigned to the same car traveling in the same direction from the same departure floor, from when the boarding schedule information is transmitted until when the boarding completion information is transmitted. It contains the identification information of the self-propelled device 6 in the two periods. In addition, the boarding list does not include the identification information of the self-propelled device 6 in the first period from when the boarding completion information is transmitted until the car departs from the departure floor. Therefore, when receiving the allocation request data from the user H, the allocation unit 113 refers to the boarding list to determine whether the self-propelled device 6 is in the first period or the second period. be able to.

(Flow of processing when receiving allocation request data)
FIG. 11 is a flowchart showing the flow of processing S300 of the elevator management device 1 when allocation request data is received from the hall destination floor registration device 2 or the self-propelled device 6. FIG. As shown in FIG. 11, process S300 includes steps S301-S310.

In step S301, control unit 110 determines whether or not allocation request data has been received. The processing of this step is an example of processing for realizing step S3 in the control method S10 described with reference to FIG. When determining No in this step, the control unit 110 repeats the processing of this step. If Yes in this step, the process of the next step S302 is executed.

In step S302, the control unit 110 refers to the allocation request data, and acquires information indicating the departure floor (orgFloor), information indicating the destination floor (destFloor), and information indicating the attribute of the user (userType). .

In step S303, the control unit 110 determines whether the destination floor (destFloor) is higher than the departure floor (orgFloor). When it is determined as Yes in this step, in step S304, the control unit 110 sets "UP direction (upward)" as information indicating the moving direction (currentDir) of the elevator 4 to be assigned.

When it is determined No in step S104, in step S305, the control unit 110 sets "DOWN direction (downward)" as information indicating the moving direction (currentDir) of the elevator 4 to be assigned.

In step S306, control unit 110 determines whether or not the information indicating the attribute (userType) to be used is "self-propelled device". When it is determined as Yes in this step, the control unit 110 executes allocation processing to the self-propelled device 6 in step S307. By the allocation process of step S307, one or a plurality of allocation candidates to be allocated to the self-propelled device 6 among the plurality of elevators 4 (a plurality of elevators) are determined. Details of step S307 will be described later with different drawings.

When it is determined No in step S306, the control unit 110 executes allocation processing to user H in step S308. By the allocation process of S308, one or a plurality of allocation candidates to be allocated to the user H are determined among the plurality of elevators 4 (a plurality of elevators). Details of step S308 will be described later with different drawings.

In step S309, the allocation unit 113 determines the optimum car from one or more allocation candidates. At this time, the allocation unit 113 selects the allocation candidate prior to departure from the departure floor (orgFloor) (that is, driving status information including information indicating that the departure floor (orgFloor) has departed from among the one or a plurality of allocation candidates). (Allocation candidates that have not yet been acquired) determine the optimum machine number. In other words, for such allocation candidates, it can be considered that user H's allocation request operation was performed in the first period. That is, the processing of this step includes an example of processing for realizing step S5 in the control method S10 described with reference to FIG.

In step S310, the allocation unit 113 transmits information indicating the determined optimum car number to the landing destination floor registration device 2 or the self-propelled device 6 as the request source.

(Flow of allocation process to self-propelled device 6)
Next, with reference to FIG. 12, the details of the allocation process to the self-propelled device 6 in step S307 will be described. FIG. 12 is a flow diagram showing a detailed flow of allocation processing to the self-propelled device 6. As shown in FIG. As shown in FIG. 12, the process of step S307 includes steps S401 to S406.

In step S401, the allocation unit 113 initializes a loop counter c to one. The loop counter c is a variable for repeatedly executing the processes of steps S402 to S405, which will be described later, for each of the elevators 4-c (c=1, 2, . . . , n).

In step S402, if the allocation unit 113 temporarily controls the elevator 4-c (hereinafter referred to as c) to depart from the departure floor (orgFloor) in the movement direction (currentDir), the elevator 4-c departs. Sometimes it is determined whether the car is empty or not. If Yes is determined in this step, the process of step S404, which will be described later, is executed.

If it is determined No in step S402, in step S403, the allocation unit 113 temporarily controls the flight of the c-car to depart from the departure floor (orgFloor) in the movement direction (currentDir). It is determined whether or not there is a user H on board. If No is determined in this step, the process of the next step S404 is executed.

In step S404, the allocation unit 113 adds the c-th car to the allocation candidate list. Here, the c car is added to the allocation candidate list when (i) the c car is empty at the time of departure from the departure floor (orgFloor) in the movement direction (currentDir), or (ii) c It may be the case that there is no user H on board when the elevator departs from the departure floor (orgFloor) in the movement direction (crrenDir). Note that the case of (ii) also includes the case where only another self-propelled device 6 is on board when car c departs from the departure floor (orgFloor) in the moving direction (crrenDir).

As a result, the allocation unit 113 can allocate to the self-propelled device 6 the number of the elevator 4 in which the user H has already boarded on the departure floor or is scheduled to board the user H on the departure floor. Therefore, the safety of user H can be ensured.

If Yes is determined in step S403, or if the c-th car is added to the allocation candidate list in step S404, the allocation unit 113 adds 1 to the loop counter c in step S405. In step S<b>406 , the allocation unit 113 determines whether or not the loop counter c exceeds the number n of elevators 4 . When determining No in step S406, the allocation unit 113 repeats the process from step S402 for the next c-th car. When determining Yes in step S406, the allocation unit 113 terminates the allocation process to the self-propelled device 6. FIG.

(Flow of Allocation Processing to User H)
Next, with reference to FIG. 13, details of allocation processing to user H in step S308 will be described. FIG. 13 is a flowchart showing a detailed flow of allocation processing to user H. As shown in FIG. As shown in FIG. 13, the process of step S308 includes steps S501 to S505.

In step S501, the allocation unit 113 initializes a loop counter c to 1. The loop counter c is a variable for repeatedly executing the processes of steps S502 to S505, which will be described later, for each elevator 4-c (the c-th car described above).

In step S502, the allocation unit 113 determines whether or not the boarding list [c][orgFloor][currentDir] is empty. The boarding list [c][orgFloor][currentDir] is assigned to car No. c departing from the departure floor (orgFloor) in the moving direction (currentDir), and the self-propelled devices that have not completed the boarding operation 6 identification information list. The fact that the boarding list is empty includes a state where all the self-propelled devices 6 assigned to the car No. c have completed boarding operations. That is, when it is determined as Yes in this step, there is a possibility that all self-propelled devices 6 assigned to the c-th machine are in the first period. In this case, the next step S503 is executed.

In step S503, the allocation unit 113 adds the c-th car to the allocation candidate list. The processing of this step includes an example of processing for realizing step S5 in the control method S10 described with reference to FIG. After that, the open state adjusting section 114 may perform processing for adjusting the length from time t8 to t9. The adjustment process is an example of a process for realizing step S6 in the control method S10 described with reference to FIG. The details of the adjustment process are as described above.

If it is determined No in step S502, the allocation unit 113 proceeds to the processing for the next c-th car without adding the c-th car to the allocation candidate list. That is, the processing of step S504, which will be described later, is executed. Note that if it is determined No in step S502, it can be considered that the allocation request operation by user H was performed during the second period. Therefore, in this case, the allocation unit 113 proceeds to the process of step S504 without adding the c-th car to the allocation candidate list, thereby realizing an example of step S8 in the control method S10 described with reference to FIG. be.

Further, when the c-th car is added to the allocation candidate list in step S503, the allocating unit 113 proceeds to the processing for the next c-th car. That is, the processing of the next step S504 is executed.

In step S504, the allocation unit 113 adds 1 to the loop counter c. In step S<b>505 , the allocation unit 113 determines whether or not the loop counter c exceeds the number n of elevators 4 . When determining No in step S505, the allocation unit 113 repeats the process from step S502 for the next c-th car. When determining Yes in step S505, the allocation unit 113 terminates the allocation process to the user H. FIG.

[Modification 1]
The elevator management system 100 according to the embodiment described above can be modified into an elevator management system 100A shown in FIG. FIG. 14 is a block diagram showing the overall configuration of an elevator management system 100A according to Modification 1 of the present embodiment.

The elevator management system 100A includes an elevator management device 1A instead of the elevator management device 1. FIG. Moreover, the elevator management system 100A further includes a self-propelled device management device 5 . Otherwise, the elevator management system 100A includes the same configuration as the elevator management system 100. FIG.

The elevator management device 1A has substantially the same configuration as the elevator management device 1 described above, but differs in that the self-propelled device 6 is controlled via the self-propelled device management device 5 . Other points are as described above.

The elevator management system 100A according to Modification 1 has the advantage of being easy to introduce, for example, when the self-propelled device management device 5 and the self-propelled device 6 are already installed in the building.

[Modification 2]
The elevator management system 100 according to the embodiment described above has explained an example of managing a plurality of elevators. Here, the elevator management system 100 may operate and manage only one of the plurality of elevators 4 for reasons such as maintenance. In this case, the elevator management system 100 described above can be modified to target a single car (single elevator 4). In this case, the elevator management device 1 notifies the platform destination floor registration device 2 that it is possible to ride in the single elevator 4 when it is determined that it is possible to ride together in step S5 shown in FIG. In addition, when the elevator management device 1 determines that the passenger cannot ride together in step S8 shown in FIG.

[Modification 3]
The elevator management system 100 according to the embodiment described above can be modified to have a hall registration function instead of having a destination floor registration function. The hall registration function allocates the most suitable machine for moving in the movement direction (upward or downward) indicated by the hall registration to the hall registration from the departure floor by the target user, and the most suitable machine for the departure floor It is a function to guide the number. In this case, the ``allocation request operation in the same direction as the traveling direction described above'' received in step S3 in FIG. ”. The elevator management device 1 may inform the boarding hall that it is possible to ride in the elevator when it is allowed to ride in the elevator in step S5 shown in FIG. 6 and the relevant elevator is selected as the optimum elevator. In addition, the elevator management device 1 may not notify the hall of the elevator car for which it is prohibited to ride together in step S8 shown in FIG. 6, but may notify the hall of another optimum elevator car. As a result, the elevator management device 1 may prevent the user H and the self-propelled device 6 from riding in an elevator that is determined to be incapable of riding together. In this case, when the elevator management system 100 manages a single elevator, if the elevator management device 1 determines that it is not possible to ride together in the elevator in step S8 shown in FIG. You may notify the boarding point.

[Example of realization by software]
The function of the elevator management device 1 (hereinafter referred to as "device") is a program for causing a computer to function as the device, and the computer is used as each control block (especially each part included in the control unit 110) of the device. It can be realized by a program for functioning.

In addition, the function of the self-propelled device 6 (hereinafter referred to as each “device”) is a program for causing a computer to function as the device, and each control block of the device (especially the control units 110 and 610). It can be realized by a program for causing a computer to function as each part that is installed).

In this case, each device includes a computer having at least one control device (eg processor) and at least one storage device (eg memory) as hardware for executing the program. Each function described in each of the above embodiments is realized by executing the above program using the control device and the storage device.

The program may be recorded on one or more computer-readable recording media, not temporary. The recording medium may or may not be included in the device. In the latter case, the program may be supplied to the device via any transmission medium, wired or wireless.

Also, part or all of the functions of the above control blocks can be realized by logic circuits. For example, integrated circuits in which logic circuits functioning as the control blocks described above are formed are also included in the scope of the present invention. In addition, it is also possible to implement the functions of the control blocks described above by, for example, a quantum computer.

〔summary〕
An elevator management device according to aspect 1 of the present invention is an elevator management device that manages operation of a plurality of elevators, wherein the self-propelled device assigned to any one of the plurality of elevators has a departure floor a boarding condition information acquiring unit for acquiring boarding condition information including boarding completion information indicating that the operation of boarding the elevator in the elevator is completed; In a first period from when the obtaining unit obtains the boarding completion information to when driving status information including information indicating that the elevator departs from the departure floor and the traveling direction of the elevator is obtained, an allocation unit that allocates the elevator to a call operation in the same direction as the traveling direction by a user who is scheduled to board from the departure floor.

According to the above configuration, if the self-propelled device has already boarded the elevator and before the elevator departs from the departure floor, the user can enter the same elevator from the same departure floor as the self-propelled device. It is possible to safely ride in This allows the user and the self-propelled device to ride together in the elevator from the same departure floor while ensuring the safety of the user.

In the elevator management apparatus according to aspect 2 of the present invention, in aspect 1, the boarding status information indicates that the self-propelled device is scheduled to board the elevator assigned to the self-propelled device from the departure floor. In response to the call operation performed by the user during a second period from when the boarding schedule information is obtained until when the boarding completion information is obtained , the elevator may not be assigned.

With the above configuration, the user does not get on the elevator that the self-propelled device is scheduled to board from the departure floor before the self-propelled device completes the boarding operation. As a result, it is possible to further improve the safety when the user and the self-propelled device ride together from the same departure floor.

An elevator management device according to aspect 3 of the present invention is an elevator management device according to aspect 1 or 2, wherein the elevator assigned to the self-propelled device is an elevator in which no user is on board when departing from the departure floor. It may be a configuration.

With the above configuration, the self-propelled device does not get on the elevator in which the user is boarding. As a result, the safety of users riding in the elevator can be ensured.

The elevator management device according to aspect 4 of the present invention is, in any one of aspects 1 to 3, in response to the call operation by the user performed in the first period, the self-propelled device The configuration may further include an open state adjusting unit that adjusts the length of a period during which the door of the elevator is kept open at the departure floor when the assigned elevator is assigned.

According to the above configuration, the user assigned to the elevator in which the self-propelled device has completed the boarding operation can secure sufficient time to board the elevator.

An elevator management system according to aspect 5 of the present invention includes the elevator management device according to any one of aspects 1 to 4, and the self-propelled device.

According to the above configuration, the same effects as those of aspect 1 are obtained.

In the elevator management system according to aspect 6 of the present invention, in aspect 5, the boarding situation information acquiring unit acquires the boarding situation information from the self-propelled device.

According to the above configuration, it is possible to obtain the same effects as those of aspect 1 by using the self-propelled device that transmits the boarding status information.

A control method for an elevator management device according to aspect 7 of the present invention is a control method for controlling an elevator management device that manages operation of a plurality of elevators, wherein the elevator is assigned to any one of the plurality of elevators. A step of acquiring boarding status information including boarding completion information indicating that the self-propelled device has boarded the elevator at the departure floor; a driving situation information acquisition step of acquiring situation information; and a period from acquisition of the boarding completion information to acquisition of the driving situation information including information indicating that the elevator departs from the departure floor and its traveling direction. and an allocating step of allocating the elevator to a call operation in the same direction as the traveling direction by a user who is scheduled to board from the departure floor performed during the first period.

According to the above configuration, the same effects as those of aspect 1 are obtained.

The elevator management apparatus according to each aspect of the present invention may be realized by a computer. In this case, the elevator apparatus can be operated by the computer by operating the computer as each part (software element) included in the elevator management apparatus. A control program for an elevator management device to be realized and a computer-readable recording medium recording it are also included in the scope of the present invention.

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.

100, 100A Elevator management system 1, 1A Elevator management device 2 Hall destination floor registration device 3 Elevator control device 4 Elevator 5 Self-propelled device management device 6 Self-propelled device 110, 610 Control unit 120, 620 Storage unit 130, 630 Communication Unit 640 Moving mechanism 111 Boarding status information acquiring unit 112 Driving status information acquiring unit 113 Allocation unit 114 Open state adjusting unit 611 Boarding schedule transmitting unit 612 Boarding completion transmitting unit 613 Moving mechanism control unit

Claims (7)

An elevator management device for managing operation of a plurality of elevators,
Boarding status information for acquiring boarding status information including boarding completion information indicating that the self-propelled device assigned to one of the elevators of the plurality of elevators has boarded the elevator at the departure floor. an acquisition unit;
a driving situation information acquisition unit that acquires driving situation information including departure/arrival information and traveling direction of the elevator;
From the departure floor during a first period from when the boarding completion information is acquired until the operation status information including information indicating that the elevator departs from the departure floor and the direction of travel of the elevator is acquired an allocation unit that allocates the elevator to a call operation in the same direction as the traveling direction by a user who is scheduled to board;
An elevator management device comprising: The boarding status information includes boarding schedule information indicating that the self-propelled device is scheduled to board the elevator assigned to the self-propelled device from the departure floor,
The allocation unit
The elevator is not assigned to the call operation performed by the user during a second period from when the boarding schedule information is obtained until when the boarding completion information is obtained;
The elevator management device according to claim 1. The elevator assigned to the self-propelled device is an elevator in which no user is on board when departing from the departure floor.
The elevator management device according to claim 1 or 2. A period for maintaining the open state of the doors of the elevator on the departure floor when the elevator assigned to the self-propelled device is assigned to the call operation by the user performed during the first period. Further comprising an open state adjustment unit that adjusts the length of
The elevator management device according to any one of claims 1 to 3. an elevator management device according to any one of claims 1 to 4;
the self-propelled device;
Elevator management system with The boarding status information acquisition unit
Acquiring the boarding status information from the self-propelled device;
The elevator management system according to claim 5. A control method for controlling an elevator management device that manages operation of a plurality of elevators, comprising:
Boarding status information for acquiring boarding status information including boarding completion information indicating that the self-propelled device assigned to one of the elevators of the plurality of elevators has boarded the elevator at the departure floor. an acquisition step;
a driving situation information acquiring step of acquiring driving situation information including departure/arrival information and traveling direction of the elevator;
From the departure floor during a first period from when the boarding completion information is acquired until the operation status information including information indicating that the elevator leaves the departure floor and the direction of travel of the elevator is acquired an assignment step of assigning the elevator to a call operation in the same direction as the traveling direction by a user who is scheduled to board;
A control method for an elevator management device, comprising:

Images