ROBOT MANAGEMENT DEVICE, ROBOT, AND PROGRAM

The robot management device optimizes elevator calls to minimize user wait times by ensuring robots board and disembark at intermediate floors, addressing the issue of prolonged user travel due to shared elevator rides.

JP7582538B1Active Publication Date: 2024-11-13FUJITEC CO LTD
View PDF 6 Cites -1 Cited by

Patent Information

Application Number
JP2024037866
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-03-12
Publication Date
2024-11-13
Estimated Expiration
2044-03-12

AI Technical Summary

Technical Problem

Robots require more time to get on and off elevators than users, leading to prolonged riding times for users when they share an elevator car with a robot, as the robot may board or disembark at intermediate floors, forcing users to wait.

Method used

A robot management device that controls elevator calls to ensure the robot boards and disembarks at specific floors, allowing users to disembark before the robot, by setting multiple elevator calls to bypass the robot's destination floor.

Benefits of technology

This solution reduces user riding time by enabling the robot to board and disembark at intermediate floors while the user reaches their destination first, eliminating unnecessary stops and reducing overall travel time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582538000001_ABST
    Figure 0007582538000001_ABST
Patent Text Reader

Abstract

To alleviate the prolongation of a user's riding time, which may occur when the user and a robot ride in a car together. [Solution] The robot management device judges whether the following conditions are respectively satisfied with respect to the robot's current floor and destination floor and the user's departure floor and destination direction: (1) the forward direction for the robot is the same as the user's destination direction, (2) the car arrives at the robot's current floor before arriving at the user's departure floor, (3) the user's departure floor is between the robot's current floor and the robot's destination floor, and (4) the robot's destination floor is a floor different from an end floor located in the forward direction from the current floor. If the robot management device judges that all of the above conditions are satisfied, it requests the allocation of a first hall call with the robot's current floor as the departure floor and an end floor located in the forward direction from the current floor as the destination floor.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a control technique for a robot that uses an elevator. [Background technology]

[0002] In recent years, robots have come to be used more and more for various tasks (cleaning, monitoring, transportation, etc.) within buildings (see, for example, Patent Document 1). Accordingly, elevators are increasingly being used to move robots between floors within buildings, and there are an increasing number of cases in which both users and robots use elevators. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7380793 Summary of the Invention [Problem to be solved by the invention]

[0004] On the other hand, a robot takes longer to board and disembark than a user. Therefore, in an environment where a robot uses an elevator together with a user, if the robot boards at an intermediate floor during the transportation of the user, or if the robot disembarks at an intermediate floor during the transportation of the user, the user will be forced to wait in the elevator until the robot has boarded and disembarked. In this way, when a user and a robot ride together in an elevator, the user may be forced to spend a longer time riding until the user reaches his or her destination floor.

[0005] Therefore, an object of the present invention is to alleviate the lengthening of a user's riding time that can occur when a user and a robot ride in the same car. [Means for solving the problem]

[0006] The robot management device according to the present invention is a device for managing robots used in buildings in which elevators are installed, and performs the following control process (mode 1). When a robot uses an elevator car to move from a current floor to a destination floor, and when a hall call for a user is assigned by the elevator control device, the robot management device judges whether or not the following conditions are satisfied with respect to the robot's current floor and destination floor, and the departure floor and destination direction indicated by the hall call for the user: (1) the forward direction from the robot's current floor to the robot's destination floor is the same as the destination direction of the user, (2) the car arrives at the robot's current floor before arriving at the departure floor of the user, (3) the departure floor of the user is between the robot's current floor and the robot's destination floor, and (4) the destination floor of the robot is a floor different from an end floor located in the forward direction with respect to the robot's current floor. When the robot management device determines that all of conditions (1) to (4) are satisfied, it requests the elevator control device to assign a first hall call for the robot, with the robot's current floor as the departure floor and an end floor located in the forward direction from the current floor as the destination floor.

[0007] In a normal allocation request for a hall call for a robot, the current floor and the destination floor of the robot are the departure floor and the destination floor, respectively, if conditions (1) to (4) are satisfied, a situation may arise in which, after getting on the car, the user must experience the robot getting off at a floor on the way to the car depending on the positional relationship between the floor where the user gets off and the floor where the robot gets off (= the destination floor). In a case where such a situation may arise, according to the above-mentioned aspect 1, by moving the car to an end floor on the premise that condition (4) is satisfied, it becomes possible to pass the car through the destination floor of the robot with the robot still on board. Therefore, it becomes possible to have the user get off before the robot before the end floor. This allows the user to avoid experiencing the robot getting off while moving in the car. As a result, it becomes possible to alleviate the lengthening of the user's ride time.

[0008] In addition, according to the above-mentioned aspect 1, by setting the first hall call as the destination floor, which is an end floor where the direction of movement of the elevator car will necessarily be reversed, it becomes possible to avoid unnecessary control such as stopping the elevator car at an intermediate floor where no one is getting on or off just to allow the elevator car to pass through the destination floor of the robot.

[0009] When the robot management device according to the above aspect 1 determines that all of the above conditions (1) to (4) are satisfied, it may further request the elevator control device to assign a second hall call for the robot, with the end floor as the departure floor and the robot's target floor as the destination floor (aspect 2).

[0010] According to the above aspect 2, by making a request to allocate a second hall call for such a robot, even after the car has passed the destination floor of the robot, when the car moves in the reverse direction (opposite the forward direction) from an end floor, the car can be stopped in the reverse direction at the destination floor of the robot, thereby making it possible to allow the robot to disembark at the destination floor.

[0011] The robot management device according to the above-mentioned aspect 2 may simultaneously request the elevator control device to allocate both the first hall call and the second hall call to the robot (aspect 3).

[0012] According to the above aspect 3, the first and second platform calls for the robot are easily assigned to the car so that the robot can respond to those platform calls in order while the car makes one revolution around the operating section (in other words, so that the robot can respond to the second platform call immediately after responding to the first platform call). On the other hand, if the request for the assignment of the second platform call is made with a delay from the timing of the request for the assignment of the first platform call, depending on the assignment status of other platform calls to the car at that time, it is easy for a situation to occur in which the assignment cannot be performed so that the robot can respond to the first and second platform calls in order while the car makes one revolution.

[0013] The robot management device according to the above-mentioned aspect 2 or 3 may have the following configuration (aspect 4). First, in relation to the robot management device, when the elevator control device receives a request from the robot management device and assigns both the first hall call and the second hall call to the car, and when the car arrives at a destination floor indicated by one of the hall calls, the elevator control device may transmit a dismount start signal to the robot management device to dismount the robot from the car. When the robot management device receives a dismount start signal from the elevator control device as a result, the robot management device may determine whether the stopping floor of the car at that time coincides with the destination floor of the robot. Then, when the robot management device determines that the stopping floor "matches" the destination floor of the robot, the robot management device may command the robot to dismount from the car, and then, when the dismount of the robot is completed, return a dismount completion signal to the elevator control device. On the other hand, if the robot management device determines that the destination floor of the robot does not match, it may return a disembarkation completion signal to the elevator control device as a dummy signal without instructing the robot to disembark from the elevator car.

[0014] In the above-mentioned embodiment 4, since the car responds to two hall calls (the first hall call and the second hall call) for the robot, a disembarking start signal is transmitted to the robot management device every time the car arrives at the destination floor indicated by the hall calls. On the other hand, when the car arrives at the destination floor indicated by the first hall call, the destination floor is a floor on the way to the target floor for the robot, and the robot does not need to disembark from the car. Therefore, in the above-mentioned embodiment 4, a disembarking completion signal is returned as a dummy signal in response to the disembarking start signal transmitted when responding to the first hall call. This makes it possible to keep the robot aboard the car without stalling the elevator control.

[0015] The robot management device according to any one of the above aspects 2 to 4 may have the following configuration (aspect 5). First, in relation to the robot management device, when the elevator control device receives a request from the robot management device and assigns both the first hall call and the second hall call to the car, and when the car arrives at the departure floor indicated by one of the hall calls, the elevator control device may transmit a boarding start signal to the robot management device to cause the robot to board the car. When the robot management device receives the boarding start signal from the elevator control device as a result, the robot management device may determine whether the robot has already boarded the car. Then, when the robot management device determines that the robot has not "boarded" the car, the robot management device may instruct the robot to board the car, and then, when the robot has completed boarding, may return a boarding completion signal to the elevator control device. On the other hand, when the robot management device determines that the robot has "boarded" the car, the robot management device may return a boarding completion signal as a dummy signal to the elevator control device without instructing the robot to board the car.

[0016] In the above-mentioned embodiment 5, since the car responds to two hall calls (the first hall call and the second hall call) for the robot, a boarding start signal is transmitted to the robot management device each time the car arrives at the departure floor indicated by the hall calls. On the other hand, since the car arrives at the departure floor indicated by the second hall call with the robot already aboard, there is no need to board the robot again in the car. Therefore, in the above-mentioned embodiment 5, a boarding completion signal is returned as a dummy signal in response to the boarding start signal transmitted in response to the second hall call. This makes it possible to keep the robot aboard the car without stalling the elevator control.

[0017] The robot according to the present invention is a robot used in a building in which an elevator is installed, and performs the following control process (mode 6). When the robot itself travels from a current floor to a destination floor using an elevator car, and when a hall call for a user is assigned by the elevator control device, the robot judges whether or not the following conditions are satisfied with respect to its current floor and destination floor, and the departure floor and destination direction indicated by the hall call for the user: (1) the forward direction from its current floor to the destination floor is the same as the destination direction of the user, (2) the car arrives at its current floor before arriving at the departure floor of the user, (3) the departure floor of the user is between its departure floor and the destination floor, and (4) the destination floor of its destination is a floor different from the end floor located in the forward direction with respect to the current floor. Then, when the robot determines that all of the conditions (1) to (4) are satisfied, it requests the elevator control device to assign a hall call to itself as its first hall call, with its current floor as the departure floor and an end floor located in the forward direction from the current floor as the destination floor.

[0018] The program according to the present invention is a program that causes a robot used in a building in which an elevator is installed, or a robot management device that manages the robot, to execute a judgment step and a request step (Mode 7). In the judgment step, when the robot uses an elevator car to move from a current floor to a destination floor, and when a hall call for a user is assigned by the elevator control device, the program causes the robot or the robot management device to judge whether or not the following conditions are satisfied with respect to the current floor and destination floor of the robot and the departure floor and destination direction indicated by the hall call for the user: (1) the forward direction from the current floor of the robot to the destination floor of the robot is the same direction as the destination direction of the user, (2) the car arrives at the current floor of the robot before arriving at the departure floor of the user, (3) the departure floor of the user is between the current floor of the robot and the destination floor of the robot, and (4) the destination floor of the robot is a floor different from an end floor located in the forward direction with respect to the current floor of the robot. In the request step, if the program determines in the judgment step that all of the conditions (1) to (4) are satisfied, it causes the robot or the robot management device to request the elevator control device to assign a first hall call for the robot, with the robot's current floor as the departure floor and an end floor located in the forward direction from the current floor as the destination floor. Effect of the Invention

[0019] According to the present invention, it is possible to alleviate the lengthening of a user's riding time that may occur when a user and a robot ride in the same car. [Brief description of the drawings]

[0020] [Figure 1] 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. [Diagram 2]FIG. 2 is a conceptual diagram illustrating (A) device management data, (B) hall call management data and car call management data for users, and (C) hall call management data and car call management data for robots, which are used in the embodiment. [Diagram 3] FIG. 2 is a conceptual diagram illustrating robot management data used in the embodiment. [Figure 4] 11 is a flowchart showing an allocation request process executed in the embodiment. [Diagram 5] 11 is a flowchart showing an allocation process executed in the embodiment. [Figure 6] 11 is a flowchart showing a response process executed in the embodiment. [Figure 7] 11 is a flowchart showing a first response process executed in the embodiment. [Figure 8] 11 is a flowchart showing a second response process executed in the embodiment. [Figure 9] 11 is a flowchart showing a third response process executed in the embodiment. [Figure 10] 13 is a flowchart showing a part of a third response process. [Figure 11] 4 is a flowchart showing a boarding command process executed in the embodiment. [Figure 12] 4 is a flowchart showing a disembarking command process executed in the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] [1] Implementation Example [1-1] Overall structure of elevator FIG. 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. In this embodiment, the elevator includes one car G, which is used not only by users but also by a robot H that performs various tasks (cleaning, monitoring, transport, etc.) in a building in which the elevator is installed. In addition, in this elevator, a destination direction button 1 is provided at the landing of each floor for users to specify a destination direction Kc, and a destination floor button 2 is provided in the car G for users to specify a destination floor Fd. In addition to these components, the elevator of this embodiment further includes an elevator control device 3 and a robot management device 4. The configuration of each part will be specifically described below.

[0022] <Destination button> On floors other than the terminal floor Fy, which is the top floor or the bottom floor, the destination direction button 1 includes an up button for specifying an up direction as the destination direction Kc and a down button for specifying a down direction as the destination direction Kc. On the other hand, on the top floor, the destination direction button 1 includes only the down button, and on the bottom floor, the destination direction button 1 includes only the up button.

[0023] When a user presses a destination direction button 1 at a landing to specify a destination direction Kc, the destination direction Kc is transmitted to the elevator control device 3. As a result, an assignment of a landing call Rg for the user (assignment of the landing call Rg to the car G) is requested of the elevator control device 3 (assignment request from the user). At this time, the destination direction button 1 transmits device information Pd for identifying itself from other buttons, devices, etc., together with the destination direction Kc to the elevator control device 3 so that the elevator control device 3 can recognize which destination direction button 1 is the source of the transmission of the destination direction Kc.

[0024] <Destination Floor Button> The destination floor button 2 is provided for each stop floor that can be guided by the car G, and is a button for registering the stop floor as a destination floor Fd.

[0025] When a user presses the destination floor button 2 in the car G to register a destination floor Fd, the destination floor Fd is transmitted to the elevator control device 3. As a result, the elevator control device 3 is requested to register a car call Vg for the user (registering a car call Vg in the car G).

[0026] <Elevator control device> The elevator control device 3 is a device that controls the operation of the car G. Specifically, the elevator control device 3 assigns a hall call Rg to the car G in response to an assignment request from a user at a hall (an assignment request from the destination direction button 1 in which the user specifies the destination direction Kc) (assignment process, see FIG. 5), and causes the car G to execute an operation to respond to the hall call Rg (response process, see FIGS. 6 to 10). In this embodiment, the elevator control device 3 not only executes assignment to the car G in response to an assignment request from a user at a hall, but also assigns a hall call Rh to the car G in response to an assignment request from a robot management device 4 described later (assignment process, see FIG. 5), and causes the car G to execute an operation to respond to the hall call Rh (response process, see FIGS. 6 to 10). Details of these processes will be described later.

[0027] Specifically, the elevator control device 3 includes a storage unit 31 and a control unit 32 (see FIG. 1).

[0028] The storage unit 31 is a part configured with storage devices such as ROM and RAM, and stores information necessary for the control processing performed by the elevator control device 3. In this embodiment, as such information, the storage unit 31 stores device management data Dp, hall call management data Dq1G and car call management data Dq2G for users, and hall call management data Dq1H and car call management data Dq2H for the robot H.

[0029] Here, the device management data Dp is a database for managing, for each destination direction button 1, multiple pieces of information related to that destination direction button 1 in association with each other. The hall call management data Dq1G and the car call management data Dq2G are data for managing information on hall calls Rg and car calls Vg for users, respectively. The hall call management data Dq1H and the car call management data Dq2H are data for managing information on hall calls Rh and car calls Vh for robot H, respectively. Specifically, they are as follows.

[0030] 2A is a conceptual diagram illustrating the device management data Dp used in this embodiment. In the device management data Dp illustrated in this figure, the device information Pd and the installation floor Fs are recorded for each destination direction button 1 in a mutually associated state.

[0031] As a result, when the elevator control device 3 receives device information Pd together with the destination direction Kc from each destination direction button 1, it becomes possible to identify the installation floor Fs of the destination direction button 1 (the destination direction button 1 for which the destination direction Kc has been specified by the user) from the device information Pd. In this embodiment, the installation floor Fs of the destination direction button 1 is used as the departure floor Fc (boarding floor) of the user who specified the destination direction Kc with the destination direction button 1.

[0032] FIG. 2(B) is a conceptual diagram illustrating the hall call management data Dq1G and the car call management data Dq2G for users used in this embodiment.

[0033] In the hall call management data Dq1G, for each stop floor that can be guided by the car G, and further for each direction that can be traveled from that stop floor, an allocation status is associated that indicates whether or not a hall call Rg for a user with that stop floor as the departure floor Fc and that direction as the destination direction Kc has been allocated to the car G (in other words, whether or not a button (up button or down button) for designating that direction as the destination direction Kc on the destination direction button 1 provided at that stop floor has been pressed). In the example of FIG. 2(B), a case is shown in which the allocation status for each direction from each stop floor is updated to "ON" when a hall call Rg with that stop floor as the departure floor Fc and that direction as the destination direction Kc has been allocated, and is updated to "OFF" when that hall call Rg is deleted.

[0034] In the car call management data Dq2G, each stop floor that can be guided by car G is associated with a registration status indicating whether or not a car call Vg for a user whose stop floor is a destination floor Fd is registered in car G (in other words, whether or not the destination floor button 2 for registering the stop floor as a destination floor Fd is pressed). The example in FIG. 2(B) shows a case in which the registration status for each stop floor is updated to "ON" when a car call Vg whose stop floor is a destination floor Fd is registered, and is updated to "OFF" when the car call Vg is deleted.

[0035] FIG. 2(C) is a conceptual diagram illustrating examples of the hall call management data Dq1H and the car call management data Dq2H for the robot H used in this embodiment.

[0036] In the hall call management data Dq1H, each time a hall call Rh for each robot H is assigned to a car G, the robot information Ph of the robot H and the departure floor Fc and destination floor Fd indicated by the hall call Rg are recorded in a mutually associated state. When the hall call Rh is deleted, the information is deleted from the hall call management data Dq1H.

[0037] In addition, in the car call management data Dq2H, each time a car call Vh for each robot H is registered in a car G, the robot information Ph of the robot H and the destination floor Fd indicated by the car call Vh are recorded in a mutually associated state. Then, when the car call Vh is deleted, the information is deleted from the car call management data Dq2H.

[0038] The control unit 32 is a part that is responsible for executing the control processing (including the allocation processing and the response processing) performed by the elevator control device 3. Specifically, the control unit 32 is composed of a processing device such as a CPU or an MPU, and executes a control program installed in the elevator control device 3 to realize the execution of the control processing that it is responsible for by software. Note that, before being installed in the elevator control device 3, this control program may be stored in a portable storage medium (e.g., a flash memory or the like) in a readable state, or may be stored in a state that can be downloaded to another server or the like. In addition, the control processing performed by the elevator control device 3 is not limited to being realized by software by executing a program, but may also be realized by hardware by a processing circuit (the control unit 32) constructed in the elevator control device 3.

[0039] <Robot management device> The robot management device 4 is a device that centrally manages the robots H used in the building in which the elevator of this embodiment is installed.

[0040] In this embodiment, when an inter-floor movement is required, each robot H transmits a destination floor Fx to the robot management device 4. At this time, the robot H transmits robot information Ph for identifying itself from other robots H together with the destination floor Fx to the robot management device 4 so that the robot management device 4 recognizes which robot H has transmitted the destination floor Fx.

[0041] When the robot management device 4 receives the destination floor Fx and the robot information Ph from each robot H, the robot management device 4 executes a control process for moving the robot H between floors, in order to alleviate the lengthening of the user's riding time that may occur when the user and the robot H ride together in the elevator G. Specifically, the robot management device 4 executes an allocation request process (see FIG. 4), a boarding command process (see FIG. 11), and an alighting command process (see FIG. 12). The details of these processes will be described later.

[0042] Specifically, the robot management device 4 includes a storage unit 41 and a control unit 42 (see FIG. 1).

[0043] The storage unit 41 is a part configured with storage devices such as ROM and RAM, and stores information necessary for the control processing performed by the robot management device 4. In this embodiment, robot management data Dr is stored in the storage unit 41 as such information. Here, the robot management data Dr is a database for managing, for each robot H, multiple pieces of information related to that robot H in association with each other. Specifically, it is as follows.

[0044] FIG. 3 is a conceptual diagram illustrating the robot management data Dr used in this embodiment. In the robot management data Dr illustrated in this figure, for each robot H, the robot information Ph and the current floor Ft, the destination of the robot H when it moves between floors, and the usage status of the car G are recorded in a mutually associated state. Here, the current floor Ft associated with each robot H is the floor where the robot H is located, and is updated every time the robot H moves between floors. In addition, the destination associated with each robot H records the destination floor Fx transmitted by the robot H for moving between floors, and the destination floor Fx is erased when the robot H has completed disembarking from the floor. Furthermore, the example of FIG. 3 shows a case in which the usage status associated with each robot H is updated to "riding" when the robot H has completed boarding the car G, and updated to "not in use" when the robot H has completed disembarking from the car G.

[0045] As a result, when the robot management device 4 receives robot information Ph together with the destination floor Fx from each robot H, it becomes possible to identify the current floor Ft of the robot H from the robot information Ph. In this embodiment, the current floor Ft of the robot H is used as the departure floor Fc (boarding floor) when the robot H moves between floors using an elevator car G. In addition, the robot management device 4 can determine whether the robot H is "boarding" the car G by referring to the usage status associated with the robot information Ph of each robot H.

[0046] The control unit 42 is a part that is responsible for executing the control processes (including allocation request processing, boarding command processing, and disembarking command processing) performed by the robot management device 4. Specifically, the control unit 42 is composed of a processing device such as a CPU or MPU, and executes a control program installed in the robot management device 4 to realize the execution of the control processes it is responsible for by software. Note that, before being installed in the robot management device 4, this control program may be stored in a portable storage medium (e.g., a flash memory, etc.) in a readable state, or may be stored in a state that can be downloaded to another server, etc. In addition, the control processes performed by the robot management device 4 are not limited to being realized by software by executing a program, but may also be realized by hardware by a processing circuit (control unit 42) constructed in the robot management device 4.

[0047] [1-2] Control process executed in elevators [1-2-1] Allocation request processing performed by the robot management device 4 is a flowchart showing the allocation request process executed in this embodiment. This allocation request process is started every time the robot management device 4 receives a destination floor Fx and robot information Ph from any robot H. In the allocation request process, the robot H that has transmitted the information is referred to as the "target robot Hk." Furthermore, the information received by the robot management device 4 at that time (including the destination floor Fx and robot information Ph) is collectively referred to as the "received information Pr1."

[0048] When the allocation request process is started, the robot management device 4 records the destination floor Fx in the received information Pr1 as the destination associated with the robot information Ph in the received information Pr1 in the robot management data Dr (step S100). This enables the robot management device 4 to grasp the destination of the target robot Hk even in the disembarking command process described later.

[0049] In this allocation request process, the robot management device 4 uses the current elevator information Pe (including information indicating the operating status of the car G and the user's usage status, etc.) to determine whether the target robot Hk and the user will ride in the car G together, and whether the extension of the user's ride time that may occur if they do can be mitigated, and requests the elevator control device 3 to allocate a hall call Rh (allocation of a hall call Rh for the target robot Hk) based on the result of the determination.

[0050] Therefore, the robot management device 4 first obtains the elevator information Pe at the current time from the elevator control device 3 (step S101). Specifically, the robot management device 4 requests the elevator control device 3 to return the elevator information Pe at that time. The robot management device 4 then receives the elevator information Pe returned from the elevator control device 3 in response to its request, thereby obtaining the necessary information. At this time, the robot management device 4 obtains information on the current position Qt and moving direction of the car G as information indicating the operating status of the car G, and obtains information on the hall call Rg for the user assigned to the car G as information indicating the usage status of the user.

[0051] Next, the robot management device 4 makes the following judgment using the elevator information Pe acquired in step S101.

[0052] The robot management device 4 first judges whether or not information on the hall call Rg for the user is included in the elevator information Pe (step S102). If the robot management device 4 judges "included (Yes)" in step S102, it can determine that there is a user who will board the car G, and further determine that there is a risk that the user will be riding with the target robot Hk if the target robot Hk is allowed to board the car G at that time.

[0053] In this case, the robot management device 4 uses the robot management data Dr to extract the current floor Ft associated with the robot information Ph in the received information Pr1. Then, the robot management device 4 judges whether or not all of the following conditions (1) to (4) are satisfied for the current floor Ft and the destination floor Fx in the received information Pr1 (the current floor Ft and destination floor Fx of the target robot Hk), and the information of the hall call Rg for a user who may ride with the target robot Hk (the departure floor Fc and destination direction Kc of the user indicated by the hall call Rg) (step S103).

[0054] Condition (1): The forward direction Ks from the current floor Ft of the target robot Hk to the destination floor Fx of the target robot Hk is the same as the destination direction Kc of the user. Condition (2): The elevator G arrives at the current floor Ft of the target robot Hk before arriving at the departure floor Fc of the user. Condition (3): The user's departure floor Fc is between the current floor Ft of the target robot Hk and the destination floor Fx of the target robot Hk. Condition (4): The destination floor Fx of the target robot Hk is a floor different from the end floor Fy located in the forward direction Ks with respect to the current floor Ft of the target robot Hk.

[0055] If conditions (1) to (4) are satisfied, and a normal hall call (a hall call with the current floor Ft of the target robot Hk as the departure floor Fc and the destination floor Fx of the target robot Hk as the destination floor Fd) is assigned as the hall call Rh for the target robot Hk, then after getting on the car G, depending on the positional relationship between the floor where the user disembarks and the floor where the target robot Hk disembarks (=the destination floor Fx), a situation may arise in which the user must experience the target robot Hk disembarking at an intermediate floor before disembarking. If such a situation occurs, the user will be forced to wait in the car G until the target robot Hk has disembarked at an intermediate floor. In this way, when the user and the target robot Hk ride in the car G together, the user may be forced to spend a longer ride time before disembarking due to the target robot Hk disembarking at an intermediate floor.

[0056] Therefore, when the robot management device 4 determines in step S103 that all of the conditions (1) to (4) are "satisfied (Yes)," it makes two allocation requests that differ from the usual ones (steps S110A and 110B) in order to mitigate the lengthening of the user's riding time that may occur when the user and the target robot Hk ride in the elevator G together.

[0057] In the first allocation request, the robot management device 4 requests the elevator control device 3 to allocate a first hall call Rh (first hall call) for the target robot Hk, with the current floor Ft of the target robot Hk as the departure floor Fc and an end floor Fy (an end floor on the same side as the destination floor Fx of the target robot Hk) located in the forward direction Ks from the current floor Ft as the destination floor Fd (step S110A). Specifically, the robot management device 4 sets the current floor Ft of the target robot Hk as the departure floor Fc and the end floor Fy as the destination floor Fd, and transmits these pieces of information together with the robot information Ph of the target robot Hk to the elevator control device 3.

[0058] By making such a first allocation request (first hall call allocation request), it is possible to move the car G to the terminal floor Fy on the premise that the condition (4) is satisfied, and therefore it is possible to pass the target floor Fx of the target robot Hk while the target robot Hk is still aboard the car G. Therefore, it is possible to have the user disembark before the target robot Hk before the target floor Fy. In addition, by setting the first hall call as the destination floor Fd to the terminal floor Fy where the direction of movement of the car G is always reversed, it is possible to avoid unnecessary control such as stopping the car G at an intermediate floor where no one gets on or off just to pass the target floor Fx of the target robot Hk.

[0059] In the second allocation request, the robot management device 4 requests the elevator control device 3 to allocate a second hall call Rh (second hall call) for the target robot Hk with the end floor Fy as the departure floor Fc and the target floor Fx of the target robot Hk as the destination floor Fd (step S110B). Specifically, the robot management device 4 sets the end floor Fy as the departure floor Fc and the target floor Fx of the target robot Hk as the destination floor Fd, and transmits these pieces of information together with the robot information Ph of the target robot Hk to the elevator control device 3. After step S110B, the robot management device 4 ends the allocation request process.

[0060] By making such a second allocation request (allocation request for a second hall call), even after the car G has passed the destination floor Fx of the target robot Hk, when the car G moves in the reverse direction Kt (the opposite direction to the forward direction Ks) from the end floor Fy, the car G can be stopped in the reverse direction Kt at the destination floor Fx of the target robot Hk, and as a result, it becomes possible to allow the target robot Hk to disembark at the destination floor Fx.

[0061] In this embodiment, the robot management device 4 performs steps S110A and S110B simultaneously (including the case where step S110B is performed immediately at almost the same timing after step S110A). In other words, the robot management device 4 simultaneously requests the elevator control device 3 to assign both the first hall call and the second hall call to the target robot Hk.

[0062] In this way, by performing steps S110A and S110B simultaneously, in the allocation process performed by the elevator control device 3 described later, the first and second hall calls for the target robot Hk are more likely to be allocated to the car G so that the car G can respond to those hall calls in order while making one revolution in the operating area (in other words, so that the car G can respond to the second hall call immediately after responding to the first hall call). Note that if such allocation can be performed reliably, step S110B may be executed with a delay from step S110A.

[0063] Regarding the above-mentioned conditions (1) to (4), if at least one of the conditions (1) to (3) is not satisfied, even if a normal hall call is assigned as the hall call Rh for the target robot Hk, a situation may occur in which the user does not experience any riding with the target robot at all from the time when the user boards the elevator G at the departure floor Fc until the time when the user moves in the destination direction Kc and disembarks.

[0064] Moreover, when the condition (4) is not satisfied, it is when the destination floor Fx of the target robot Hk is an end floor Fy. In this case, the user of the car G moving in the forward direction Ks gets off before the car G arrives at the destination floor Fx (=end floor Fy) of the target robot Hk, or gets off together with the target robot Hk at the destination floor Fx. In other words, when the condition (4) is not satisfied, the user does not experience the target robot Hk getting off at an intermediate floor. Therefore, in such a case, it is sufficient to assign a normal hall call as the hall call Rh for the target robot Hk.

[0065] Also, if the elevator information Pe does not include information on the hall call Rg for a user, it means that there is no user who may be riding with the target robot Hk at that time. In this case, a normal hall call can be assigned as the hall call Rh for the target robot Hk without affecting the user in any way.

[0066] Therefore, when the robot management device 4 judges that at least one of the conditions is "not satisfied (No)" in step S103, or judges that the condition is "not included (No)" in step S102, it makes a normal allocation request to the elevator control device 3 (step S120). Specifically, the robot management device 4 requests the elevator control device 3 to allocate a normal hall call as a hall call Rh for the target robot Hk, with the current floor Ft of the target robot Hk as the departure floor Fc and the target floor Fx of the target robot Hk as the destination floor Fd. More specifically, the robot management device 4 transmits the current floor Ft and the destination floor Fx of the target robot Hk as the departure floor Fc and destination floor Fd of the target robot Hk, respectively, to the elevator control device 3 together with the robot information Ph of the target robot Hk. After step S120, the robot management device 4 ends the allocation request process.

[0067] [1-2-2] Allocation process performed by elevator control device Fig. 5 is a flow chart showing the allocation process executed in this embodiment. This allocation process is started when a hall call allocation request is made to the elevator control device 3 from the destination direction button 1 or the robot management device 4. In this embodiment, even if the first hall call and the second hall call allocation requests for the robot H (steps S110A and S110B in Fig. 4) are made simultaneously, the allocation process in Fig. 5 is executed for each of them.

[0068] Hereinafter, the information received by the elevator control device 3 for each assignment request will be collectively referred to as "received information Pr2." Specifically, this received information Pr2 is a set of information including the destination direction Kc and device information Pd when the assignment request is a request from the destination direction button 1 (assignment request of hall call Rg for a user), and is a set of information including the departure floor Fc, destination floor Fd, and robot information Ph when the assignment request is a request from the robot management device 4 (assignment request of hall call Rh for robot H).

[0069] When the allocation process begins, the elevator control device 3 determines whether the received allocation request is from the destination direction button 1 or the robot management device 4, and determines whether the received information Pr2 contains the device information Pd or the robot information Ph (step S200).

[0070] If the elevator control device 3 determines in step S200 that the "device information Pd" is included, it can determine that the received allocation request is a request from the destination direction button 1. In this case, the elevator control device 3 uses the device management data Dp to extract the installation floor Fs associated with the device information Pd in ​​the received information Pr2, and sets it as the departure floor Fc of the user. Then, the elevator control device 3 performs allocation to the car G by treating the departure floor Fc and the destination direction Kc in the received information Pr2 (the destination direction Kc of the user) as one hall call Rg (allocation for the user; step S201). After that, the elevator control device 3 ends the allocation process.

[0071] On the other hand, if the elevator control device 3 determines in step S200 that "robot information Ph" is included, it can determine that the received allocation request is a request from the robot management device 4. In this case, the elevator control device 3 executes allocation to the car G by treating the departure floor Fc and destination floor Fd in the received information Pr2 as one hall call Rh (allocation for the robot H; step S202). After that, the elevator control device 3 ends the allocation process.

[0072] [1-2-3] Response processing by elevator control device Fig. 6 is a flow chart showing the response process executed in this embodiment. This response process is a normal response process executed by the elevator control device 3, and the hall calls and car calls to be responded to are not limited to hall calls and car calls for the user and robot H who are the judgment targets when it is judged that all of the conditions (1) to (4) are "satisfied (Yes)" in step S103 of the above-mentioned allocation request process (see Fig. 4), but also include hall calls and car calls for other users and robots H. This response process is started when the next stop floor of the car G is determined.

[0073] When the response process is started, the elevator control device 3 judges what kind of calls are included in the response targets to be responded to in the response process (step S30X). Specifically, the elevator control device 3 judges whether the response targets include only hall calls (either or both of a hall call Rg of a user and a hall call Rh of the robot H), only car calls (either or both of a car call Vg of a user and a car call Vh of the robot H), or both hall calls and car calls.

[0074] Then, the elevator control device 3 executes a first response process if it determines in step S30X that the call is "only a hall call", executes a second response process if it determines in step S30X that the call is "only a car call", and executes a third response process if it determines in step S30X that the call is "both a hall call and a car call". These processes will be specifically described below.

[0075] <First response process> 7 is a flowchart showing the first response process executed in this embodiment. In this first response process, the elevator control device 3 first determines whether or not the response target includes the hall call Rh of the robot H (step S300).

[0076] When the elevator control device 3 judges "not included (No)" in step S300, it can determine that the response target includes only the hall call Rg of the user. In this case, the elevator control device 3 transmits a command to the car G to stop the car G at the departure floor Fc indicated by the hall call Rg (the departure floor Fc of the user) in the same direction as the destination direction Kc indicated by the hall call Rg (step S301).

[0077] After step S301, the elevator control device 3 judges whether the car G has arrived at the departure floor Fc indicated by the hall call Rg (step S302). Furthermore, the elevator control device 3 repeatedly executes step S302 until it can judge "arrived (Yes)" in step S302.

[0078] Then, when the elevator control device 3 determines that the elevator has arrived (Yes) in step S302, it deletes the hall call Rg that has completed its function with the arrival (step S303).

[0079] After that, the user gets into the car G that has arrived, and then registers his / her destination floor Fd by pressing the destination floor button 2 in the car G. At this time, if the destination floor button 2 corresponding to his / her destination floor Fd has already been registered by pressing it by another user, the user only gets into the car G.

[0080] Therefore, after step S303, the elevator control device 3 judges whether or not an unregistered destination floor Fd has been pressed on the destination floor button 2 in the car G (step S304).

[0081] Then, when the elevator control device 3 determines that the button is "pressed (Yes)" in step S304, it registers the pressed destination floor Fd in the car G as a car call Vg for the user (step S305). This makes it possible to stop the car G at the destination floor Fd registered by the user in the car G. After that, the elevator control device 3 ends the first response process.

[0082] On the other hand, if the elevator control device 3 determines in step S304 that the button was not pressed (No), the elevator control device 3 ends the first response process without performing step S305.

[0083] When the elevator control device 3 determines in step S300 that the hall call Rh of the robot H is included in the response targets (Yes), it responds to the hall call Rh, and when the response targets further include the hall call Rg of a user, it also processes the hall call Rg of the user. Specifically, it is as follows.

[0084] The elevator control device 3 sends a command to the car G to stop the car G at the departure floor Fc indicated by the hall call Rh (the departure floor Fc of the robot H) in the direction toward the destination floor Fd indicated by the hall call Rh (step S401).

[0085] After step S401, the elevator control device 3 judges whether the car G has arrived at the departure floor Fc indicated by the hall call Rh (step S402). Furthermore, the elevator control device 3 repeatedly executes step S402 until it can judge "arrived (Yes)" in step S402.

[0086] If the elevator control device 3 determines "arrived (Yes)" in step S402, it transmits a boarding start signal Sx1 to the robot management device 4 to start the robot H boarding the car G (step S403). At this time, the elevator control device 3 extracts the robot information Ph corresponding to the currently responded hall call Rh from the hall call management data Dq1H to make the robot management device 4 recognize which robot H should be boarded, and transmits the robot information Ph to the robot management device 4 together with the boarding start signal Sx1.

[0087] Here, if the hall call Rh to be responded to is one (first hall call) that has been assigned to the car G in response to the first assignment request (step S110A in FIG. 4) from the robot management device 4, or one that has been assigned to the car G in response to a normal assignment request (step S120 in FIG. 4), at the time of execution of step S403, the robot H has not yet boarded the car G and is waiting at the current floor Ft for a command to board the car G. Therefore, in this case, in step S403, a boarding start signal Sx1 is transmitted to the robot management device 4 when the robot H should board.

[0088] On the other hand, if the hall call Rh to be responded to is the one (second hall call) that has been assigned to the car G in response to the second assignment request from the robot management device 4 (step S110B in FIG. 4), the elevator control device 3 is in a state of executing a response process for the second hall call after finishing the response process for the first hall call (in other words, after the robot H gets on the car G). In this case, at the time of executing step S403, the robot H has already gotten on the car G. Therefore, in this case, in step S403, the boarding start signal Sx1 is transmitted to the robot management device 4 even though the robot H does not need to board.

[0089] Therefore, when the robot management device 4 receives the boarding start signal Sx1 from the elevator control device 3, it executes the boarding command process shown in Fig. 11 for the robot H identified by the robot information Ph received together with the boarding start signal Sx1. The details of the boarding command process will be described later.

[0090] After step S403, the elevator control device 3 judges whether or not the boarding completion signal Sx2 has been received from the robot management device 4 (step S404). Furthermore, the elevator control device 3 repeatedly executes step S404 until it can be judged that the signal has been received (Yes) in step S404.

[0091] When the robot H gets on the car G, some trouble (such as a power system failure or insufficient battery power) may occur, and the robot H may not be able to complete the boarding into the car G. Therefore, if the elevator control device 3 is unable to receive the boarding completion signal Sx2 (is unable to determine "received (Yes)" in step S404) after a predetermined time has elapsed, the elevator control device 3 may delete the hall call Rh and proceed to step S406.

[0092] If the elevator control device 3 determines "received (Yes)" in step S404, it registers the destination floor Fd indicated by the hall call Rh (the destination floor Fd of the robot H) in the car G as a car call Vh for the robot H (step S405). This makes it possible to stop the car G at the destination floor Fd indicated by the hall call Rh. Meanwhile, the registration of the car call Vh in such a car G means that the hall call Rh has completed its role. Therefore, the elevator control device 3 deletes the hall call Rh that has completed its role.

[0093] After that, the elevator control device 3 judges whether the hall call Rg of the user is further included in the response targets in this first response process (step S406). If the elevator control device 3 judges "included (Yes)" in step S406, it executes the processes of steps S303 to S305 (deleting the hall call Rg to registering the car call Vg) as the process for the hall call Rg. Then, the elevator control device 3 ends the first response process. On the other hand, if the elevator control device 3 judges "not included (No)" in step S406, it ends the first response process without executing the processes of steps S303 to S305.

[0094] <Second response process> 8 is a flowchart showing the second response process executed in this embodiment. In this second response process, the elevator control device 3 first determines whether or not the response target includes a car call Vh of the robot H (step S310).

[0095] If the elevator control device 3 determines "not included (No)" in step S310, it can determine that only the car call Vg of the user is included in the response target. In this case, the elevator control device 3 transmits a command to the car G to stop the car G at the destination floor Fd (destination floor Fd of the user) indicated by the car call Vg (step S311).

[0096] After step S311, the elevator control device 3 judges whether the car G has arrived at the destination floor Fd indicated by the car call Vg (step S312). Furthermore, the elevator control device 3 repeatedly executes step S312 until it can judge "arrived (Yes)" in step S312.

[0097] Then, when the elevator control device 3 determines that the car has arrived (Yes) in step S312, it deletes the car call Vg that has completed its role upon arrival (step S313). After that, the elevator control device 3 ends the second response process.

[0098] When the elevator control device 3 determines in step S310 that the car call Vh of the robot H is included in the response targets (Yes), it responds to the car call Vh, and when the response targets further include a car call Vg of a user, it also processes the car call Vg of the user. Specifically, it is as follows.

[0099] The elevator control device 3 transmits a command to the car G to stop the car G at the destination floor Fd indicated by the car call Vh (the destination floor Fd of the robot H) (step S411).

[0100] After step S411, the elevator control device 3 judges whether the car G has arrived at the destination floor Fd indicated by the car call Vh (step S412). Furthermore, the elevator control device 3 repeatedly executes step S412 until it can judge "arrived (Yes)" in step S412.

[0101] If the elevator control device 3 determines "arrived (Yes)" in step S412, it deletes the car call Vh that has completed its role with the arrival (step S413). The elevator control device 3 also transmits a disembarking start signal Sy1 to the robot management device 4 to make the robot H start disembarking from the car G (step S414). At this time, the elevator control device 3 extracts the robot information Ph corresponding to the car call Vh being responded to from the car call management data Dq2H, and transmits the robot information Ph to the robot management device 4 together with the disembarking start signal Sy1, so that the robot management device 4 recognizes which robot H is to be disembarked.

[0102] Here, if the car call Vh to be responded to is registered in the car G through a hall call Rh (second hall call) corresponding to the second allocation request (step S110B in FIG. 4) from the robot management device 4, or is registered in the car G through a hall call Rh corresponding to a normal allocation request (step S120 in FIG. 4), the destination floor Fd indicated by the car call Vh is the target floor Fx of the robot H, and at the time of execution of step S414, the car G has arrived at the target floor Fx of the robot H (in other words, the floor where the robot H should dismount). Therefore, in this case, in step S414, when the robot H should dismount, a dismount start signal Sy1 is transmitted to the robot management device 4.

[0103] On the other hand, if the car call Vh to be responded to has been registered to the car G through the hall call Rh (first hall call) corresponding to the first allocation request from the robot management device 4 (step S110A in FIG. 4), the destination floor Fd indicated by the car call Vh is a floor (here, the end floor Fy) on the way to the destination floor Fx of the robot H that the car G moves around, and at the time of executing step S414, the car G has merely arrived at a floor on the way (in other words, a floor where the robot H does not need to disembark). Therefore, in this case, in step S414, the disembarkation start signal Sy1 is transmitted to the robot management device 4 even though the robot H does not need to disembark.

[0104] Therefore, when the robot management device 4 receives the dismount start signal Sy1 from the elevator control device 3, it executes the dismount command process shown in Fig. 12 for the robot H identified by the robot information Ph received together with the dismount start signal Sy1. The details of the dismount command process will be described later.

[0105] After step S414, the elevator control device 3 judges whether or not the elevator control device 3 has received the disembarkation completion signal Sy2 from the robot management device 4 (step S415). Furthermore, the elevator control device 3 repeatedly executes step S415 until it can judge "received (Yes)" in step S415.

[0106] If the elevator control device 3 determines in step S415 that the car call Vg has been received (Yes), it determines whether the user's car call Vg is further included in the response targets in this second response process (step S416). If the elevator control device 3 determines in step S416 that the car call Vg is included (Yes), it executes the process of step S313 (delete the car call Vg) as the process for that car call Vg. Then, the elevator control device 3 ends the second response process. On the other hand, if the elevator control device 3 determines in step S416 that the car call Vg is not included (No), it ends the second response process without executing the process of step S313.

[0107] <Third response process> 9 and 10 are flowcharts showing the third response process executed in this embodiment. In this third response process, the elevator control device 3 first determines whether or not the response targets include the hall call Rh of the robot H (step S320).

[0108] If the elevator control device 3 determines "not included (No)" in step S320, it can determine that the response target includes the hall call Rg of the user. In this case, the elevator control device 3 executes the same processes as steps S301 to S305 described in the first response process (steps S321 to S325).

[0109] On the other hand, if the elevator control device 3 determines in step S320 that the response is "included (Yes)", it executes the same processes as steps S401 and S402 described in the first response process (steps S421 and S422; see FIG. 10).

[0110] Here, if another robot H is riding in the car G and the stop floor where the car G arrives is the destination floor Fx of the other robot H, it is necessary to have the robot H disembark from the car G. Also, in order to smoothly board the robot H from the platform and disembark the other robot H from the car G, it is necessary to first have the robot H in the car G disembark, and then have the robot H at the platform board.

[0111] Therefore, the elevator control device 3 first determines whether or not the response targets in this third response process further include a car call Vh of another robot H (step S423).

[0112] Then, when the elevator control device 3 determines in step S423 that it is "included (Yes)", it can determine that it is necessary to cause another robot H in the car G to disembark at the stopping floor at which the car G has arrived. In this case, the elevator control device 3 executes the same processes as steps S413 to S415 (deletion of car call Vh to determination of whether or not disembarkation completion signal Sy2 has been received) described in the second response process as a process for causing the other robot H to disembark (steps S431 to S433).

[0113] If the elevator control device 3 determines in step S433 that the signal has been received (Yes), or if it determines in step S423 that the signal is not included (No), it executes the same processing as steps S403 to S405 (from sending the boarding start signal Sx1 to registering the car call Vh) described in the first response processing as processing for allowing the robot H at the landing to board the car G (steps S441 to S443).

[0114] After that, the elevator control device 3 judges whether the hall call Rg of the user is further included in the response targets in this third response process (step S451, see FIG. 9). If the elevator control device 3 judges "included (Yes)" in step S451, it executes steps S323 to S325 (deleting the hall call Rg to registering the car call Vg) as the process for the hall call Rg. Then, the elevator control device 3 proceeds to step S452. On the other hand, if the elevator control device 3 judges "not included (No)" in step S451, it proceeds to step S452 without executing the processes of steps S323 to S325.

[0115] In step S452, the elevator control device 3 judges whether or not the user's car call Vg is further included in the response targets in this third response process. If the user's car call Vg is included in the response targets, the car call Vg will also finish its role when the elevator car G arrives. Therefore, if the elevator control device 3 judges "included (Yes)" in step S452, it also deletes the car call Vg that has finished its role (step S453). Thereafter, the elevator control device 3 ends the third response process. On the other hand, if the elevator control device 3 judges "not included (No)" in step S452, it ends the third response process without performing the process of step S453.

[0116] [1-2-4] Boarding command processing by the robot management device 11 is a flowchart showing the boarding command process executed in this embodiment. This boarding command process is started every time the robot management device 4 receives the boarding start signal Sx1 and the robot information Ph from the elevator control device 3. Hereinafter, the information received by the robot management device 4 at that time (including the boarding start signal Sx1 and the robot information Ph) will be collectively referred to as "received information Pr3."

[0117] When the boarding command process is started, the robot management device 4 judges whether or not the robot H specified by the robot information Ph in the received information Pr3 (in the boarding command process, this robot H will be referred to as the "target robot Hk") has already boarded the car G (step S500). Specifically, the robot management device 4 refers to the usage status associated with the robot information Ph in the received information Pr4 in the robot management data Dr, judges whether or not the usage status is "boarding", and judges whether or not the robot has already boarded based on the result.

[0118] When the robot management device 4 determines in step S500 that the target robot Hk has not yet boarded (No), it transmits a command to the target robot Hk (step S501) to have the target robot Hk board the car G. As a result, the target robot Hk starts boarding the car G in response to the command from the robot management device 4, and when boarding is completed, notifies the robot management device 4 of the completion of boarding.

[0119] Therefore, after step S501, the robot management device 4 determines whether or not the target robot Hk has completed boarding the car G by determining whether or not a notification of boarding completion has been received from the target robot Hk (step S502). Furthermore, the robot management device 4 repeatedly executes step S502 until it can determine "completed (Yes)" in step S502.

[0120] If the robot management device 4 determines in step S502 that the boarding is completed (Yes), it returns a boarding completion signal Sx2 to the elevator control device 3 along with the robot information Ph of the target robot Hk to notify the elevator control device 3 that the boarding of the target robot Hk has been completed (step S510).

[0121] Then, the robot management device 4 updates the usage status of the target robot Hk recorded in the robot management data Dr from "not in use" to "riding" (step S511). After that, the robot management device 4 ends the riding command process.

[0122] On the other hand, when the robot management device 4 determines in step S500 that the target robot Hk has already boarded (Yes), it does not command the target robot Hk to board the car G, but returns the boarding completion signal Sx2 as a dummy signal together with the robot information Ph of the target robot Hk to the elevator control device 3 (step S520). After that, the robot management device 4 ends the boarding command process.

[0123] In this embodiment, when all of the above conditions (1) to (4) are satisfied, it is necessary to make the car G respond to the two hall calls Rh (the first hall call and the second hall call) assigned to the target robot Hk, and therefore, every time the car G arrives at the departure floor Fc indicated by those hall calls Rh, the boarding start signal Sx1 is transmitted to the robot management device 4. On the other hand, since the car G arrives at the departure floor Fc indicated by the second hall call with the target robot Hk already aboard, it is not necessary to board the target robot Hk in the car G again. Therefore, in the above boarding command process, the boarding completion signal Sx2 is returned as a dummy signal in response to the boarding start signal Sx1 transmitted when responding to the second hall call. This makes it possible to keep the target robot Hk aboard the car G without stalling the execution of the response process (see Figs. 6 to 10) in the elevator control device 3 described above.

[0124] [1-2-5] Disembarkation command processing by the robot management device 12 is a flowchart showing the disembarking command process executed in this embodiment. This disembarking command process is started every time the robot management device 4 receives a disembarking start signal Sy1 and robot information Ph from the elevator control device 3. Hereinafter, the information received by the robot management device 4 at that time (including the disembarking start signal Sy1 and the robot information Ph) will be collectively referred to as "received information Pr4."

[0125] When the disembarking command process is started, the robot management device 4 first acquires the current position Qt of the car G from the elevator control device 3 (step S600A). Specifically, the robot management device 4 requests the elevator control device 3 to return the current position Qt of the car G. Then, the robot management device 4 receives the current position Qt of the car G returned from the elevator control device 3 in response to its request, thereby acquiring the necessary information.

[0126] Next, the robot management device 4 uses the current position Qt of the elevator G obtained in step S600A and the destination (the destination floor Fx of the robot H identified by the robot information Ph) associated with the robot information Ph in the received information Pr4 in the robot management data Dr to determine whether the stopping floor of the elevator G at that time matches the destination floor Fx of the robot H (in the disembarking command processing, this robot H will be referred to as the "target robot Hk") identified by the robot information Ph in the received information Pr4 (step S600B).

[0127] When the robot management device 4 determines that the two match (Yes) in step S600B, it transmits a command to the target robot Hk to have the target robot Hk dismount from the car G (step S601). As a result, the target robot Hk starts dismounting from the car G in response to the command from the robot management device 4, and when dismounting is completed, it notifies the robot management device 4 of the completion of dismounting.

[0128] Therefore, after step S601, the robot management device 4 determines whether or not a notification of disembarking completion has been received from the target robot Hk, thereby determining whether or not disembarking of the target robot Hk from the car G has been completed (step S602). Furthermore, the robot management device 4 repeatedly executes step S602 until it can determine "completed (Yes)" in step S602.

[0129] If the robot management device 4 determines in step S602 that the process is “completed (Yes)”, it returns a disembarkation completion signal Sy2 to the elevator control device 3 along with the robot information Ph of the target robot Hk to notify the elevator control device 3 that the target robot Hk has disembarked (step S610).

[0130] Then, the robot management device 4 updates the current floor Ft recorded in the robot management data Dr for the target robot Hk to the stop floor of the car G used in the judgment in step S600B (the floor where the target robot Hk disembarks) (step S611). The robot management device 4 also updates the usage status recorded in the robot management data Dr for the target robot Hk from "on board" to "not in use". Furthermore, the robot management device 4 erases the destination floor Fx recorded as the movement destination of the target robot Hk in the robot management data Dr. After that, the robot management device 4 ends the disembarking command process.

[0131] On the other hand, if the robot management device 4 determines in step S600B that there is no match (No), it does not command the target robot Hk to dismount from the car G, but returns the dismount completion signal Sy2 as a dummy signal together with the robot information Ph of the target robot Hk to the elevator control device 3 (step S620). After that, the robot management device 4 ends the dismount command process.

[0132] In this embodiment, when all the above conditions (1) to (4) are satisfied, it is necessary to make the car G respond to the two hall calls Rh (the first hall call and the second hall call) assigned to the target robot Hk, and therefore, every time the car G arrives at the destination floor Fd indicated by those hall calls Rh (specifically, the destination floor Fd indicated by the corresponding car call Vh), the disembarkation start signal Sy1 is transmitted to the robot management device 4. On the other hand, when the car G arrives at the destination floor Fd indicated by the first hall call, the destination floor Fd is a floor on the way to the destination floor Fx for the target robot Hk, and it is not necessary for the target robot Hk to disembark from that car G. Therefore, in the above disembarkation command process, the disembarkation completion signal Sy2 is returned as a dummy signal in response to the disembarkation start signal Sy1 transmitted when responding to the first hall call. This makes it possible to keep the target robot Hk aboard the car G without stalling the execution of the response process (see Figs. 6 to 10) in the elevator control device 3 described above.

[0133] According to this control process, if a normal allocation request is made for the target robot Hk, in a situation where a user must experience the target robot Hk getting off before getting off (when the user's ride time is extended due to the target robot Hk getting off), the car G is moved to the terminal floor Fy on the premise that the condition (4) is satisfied, and the car G can pass through the destination floor Fx of the target robot Hk while the target robot Hk is still on the car G. Therefore, it is possible to have the user get off before the target robot Hk on the way to the terminal floor Fy. This means that the user does not have to experience the target robot Hk getting off while moving in the car G. As a result, it is possible to alleviate the lengthening of the user's ride time.

[0134] In addition, according to the above control process, by setting the first hall call to the end floor Fy, where the direction of movement of the elevator car G will necessarily be reversed, as the destination floor Fd, it is possible to avoid unnecessary control such as stopping the elevator car G at an intermediate floor where no one is getting on or off just to allow the target robot Hk to pass through the destination floor Fx.

[0135] [2] Variations [2-1] First modified example In the above-described embodiment, the request for allocation of a hall call Rg for a user may be appropriately changed to one requested from a destination floor registration device installed on each floor by the user registering a destination floor Fd in the destination floor registration device. In this case, the destination floor registration device transmits the destination floor Fd registered by the user and its own device information Pd to the elevator control device 3 as a request for allocation of a hall call Rg for the user.

[0136] Then, when the elevator control device 3 receives an allocation request from a destination floor registration device, it determines that it is "device information Pd" in step S200 of Figure 5, and then in the subsequent step S201, it sets the floor where the destination floor registration device (the destination floor registration device identified by the received device information Pd; see Figure 2 (A)) is installed as the departure floor Fc, and then assigns the departure floor Fc and the received destination floor Fd (the destination floor Fd registered by the user in the destination floor registration device) to a single hall call Rg, and executes allocation to the car G.

[0137] In such a configuration, the condition (1) determined in step S103 is changed to a condition that the forward direction Ks from the current floor Ft of the target robot Hk to the destination floor Fx of the target robot Hk is the same direction as the direction from the departure floor Fc of the user to the destination floor Fd of the user. Also, the condition (3) determined in step S103 is changed to a condition that the departure floor Fc of the user and the destination floor Fx of the target robot Hk are located in this order between the current floor Ft of the target robot Hk and the destination floor Fd of the user.

[0138] Also, when responding to a hall call Rg for a user in the first response process of Fig. 7, the elevator control device 3 registers the destination floor Fd indicated by the hall call Rg (destination floor Fd of the user) in the car G as a car call Vg for the user in step S303, instead of executing steps S304 and S305. Then, the elevator control device 3 deletes the hall call Rg that has completed its function, and then ends the first response process. Furthermore, when responding to a hall call Rg for a user in the third response process of Fig. 9, the elevator control device 3 performs a similar process, instead of executing steps S324 and S325.

[0139] [2-2] Second variant In any of the above-described embodiments and modified examples, each robot H may be appropriately modified to execute the control processes (including allocation request process, boarding command process, and disembarking command process) performed by the robot management device 4 on behalf of the robot management device 4. In this case, each robot H communicates with the elevator control device 3 without going through the robot management device 4. This allows each robot H to use the elevator car G autonomously.

[0140] The above-mentioned embodiments and the description of the modifications should be considered as illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims, not by the above-mentioned embodiments and modifications. Furthermore, the scope of the present invention is intended to include all modifications within the meaning and scope of the claims.

[0141] Furthermore, from the above-described embodiments and modifications, the subject of the invention is not limited to the robot management device 4 or the robot H, but the control processes and programs executed by the robot management device 4 or the robot H may be extracted individually, or a part of them may be extracted partially. Also, a part or the whole of an elevator equipped with the robot management device 4 or the robot H may be extracted as the subject of the invention. [Explanation of symbols]

[0142] 1 Destination button 2 Destination Floor Button 3 Elevator control device 4. Robot Management Device G Car H Robot 31, 41 Storage section 32, 42 Control section Dp Equipment Management Data Dr Robot Management Data Fc Departure floor Fd Destination floor Fs Installation floor Ft current floor Fx destination floor Fy end floor Hk Target Robot Kc destination direction Ks Forward Kt reverse direction Pd device information Pe Elevator Information Ph Robot Information Qt current position Rg, Rh Hall call Vg, Vh cage call Dq1G, Dq1H Hall call management data Dq2G, Dq2H cage call management data Pr1, Pr2, Pr3, Pr4 Received information Sx1 Boarding start signal Sx2 ride completion signal Sy1 Disembarkation start signal Sy2 exit completion signal

Claims

1. A device that manages robots used in buildings where elevators are installed, When the robot moves from a current floor to a destination floor using the elevator car, and when a hall call for a user is assigned by the elevator control device, the current floor and destination floor of the robot and the departure floor and destination direction indicated by the hall call for the user are determined as follows: (1) A condition that the forward direction from the current floor of the robot to the destination floor of the robot is the same as the destination direction of the user; (2) a condition that the elevator arrives at the robot's current floor before the elevator arrives at the user's departure floor; and (3) A condition that the departure floor of the user is between the current floor of the robot and the destination floor of the robot; and (4) A condition that the destination floor of the robot is a floor different from an end floor located in the forward direction with respect to the current floor of the robot; and Determine whether each of the following is satisfied, when it is determined that all of the conditions (1) to (4) are satisfied, the robot management device requests the elevator control device to assign, as a first hall call for the robot, a hall call with the robot's current floor as a departure floor and the end floor located in the forward direction from the current floor as a destination floor.

2. 2. The robot management device according to claim 1, further comprising, when it is determined that all of the conditions (1) to (4) are satisfied, a request is made to the elevator control device to assign a second hall call for the robot, with the end floor as a departure floor and the target floor of the robot as a destination floor.

3. The robot management device according to claim 2 , further comprising: a request for assignment of both the first hall call and the second hall call to the robot is made to the elevator control device simultaneously.

4. when the elevator control device, in response to a request from the robot management device, has assigned both the first hall call and the second hall call for the robot to the car, and when the car arrives at a destination floor indicated by either of the hall calls, transmits a disembarkation start signal to the robot management device to cause the robot to disembark from the car; As a result, when the disembarking start signal is received from the elevator control device, it is determined whether or not the stopping floor of the elevator car at that time coincides with the destination floor of the robot; When it is determined that the destination floor of the robot coincides with the destination floor of the robot, it instructs the robot to disembark from the elevator car, and then, when the robot has disembarked, it returns a disembarkation completion signal to the elevator control device; The robot management device according to claim 2, wherein if it is determined that the destination floor of the robot does not match, the disembarkation completion signal is returned to the elevator control device as a dummy signal without instructing the robot to disembark from the elevator car.

5. the elevator control device, upon receiving a request from the robot management device, assigns both the first hall call and the second hall call for the robot to the car, and when the car arrives at a departure floor indicated by either of the hall calls, transmits a boarding start signal to the robot management device for boarding the robot into the car; As a result, when the boarding start signal is received from the elevator control device, it is determined whether or not the robot has already boarded the elevator car; When it is determined that the user has not yet boarded the elevator car, the robot is instructed to board the elevator car, and then, when the user has completed boarding the elevator car, a boarding completion signal is returned to the elevator control device; A robot management device as described in any one of claims 2 to 4, wherein when it is determined that the robot has already boarded the elevator car, the boarding completion signal is returned to the elevator control device as a dummy signal without instructing the robot to board the elevator car.

6. A robot used in buildings equipped with elevators. When the user moves from the current floor to the destination floor using the elevator car, and the elevator control device has assigned a hall call to the user, the current floor and destination floor of the user, and the departure floor and destination direction indicated by the hall call for the user are (1) A condition that the forward direction from the current floor to the destination floor is the same as the destination direction of the user; (2) a condition that the elevator arrives at the current floor before the elevator arrives at the departure floor of the user; and (3) A condition that the departure floor of the user is between the departure floor of the user and the destination floor; and (4) A condition that the destination floor is a floor different from an end floor located in the forward direction relative to the current floor; Determine whether each of the following is satisfied, When it is determined that all of the conditions (1) to (4) are satisfied, the robot requests the elevator control device to assign, as a first hall call for itself, a hall call with the current floor of the robot as a departure floor and the end floor located in the forward direction from the current floor as a destination floor.

7. A program for causing a robot used in a building in which an elevator is installed, or a robot management device that manages the robot, to execute a determination step and a request step, In the determining step, When the robot moves from a current floor to a destination floor using the elevator car, and when a hall call for a user is assigned by the elevator control device, the current floor and the destination floor of the robot, and the departure floor and destination direction indicated by the hall call for the user are determined as follows: (1) A condition that the forward direction from the current floor of the robot to the destination floor of the robot is the same as the destination direction of the user; (2) a condition that the elevator arrives at the robot's current floor before the elevator arrives at the user's departure floor; and (3) A condition that the departure floor of the user is between the current floor of the robot and the destination floor of the robot; and (4) A condition that the destination floor of the robot is a floor different from an end floor located in the forward direction with respect to the current floor of the robot; and Determine whether each of the following is satisfied, In the request step, a program that, when it is determined in the judgment step that all of the conditions (1) to (4) are satisfied, requests the elevator control device to assign, as a first hall call for the robot, a hall call having the current floor of the robot as a departure floor and the end floor located in the forward direction from the current floor as a destination floor.

Citation Information

Patent Citations

  • Robot interlocking elevator control system

    CN117657904A

  • Group management control device and allocation method of vehicle to autonomous mobile body

    JP2020111464A

  • Elevator system, elevator group management control device and elevator number allocation method

    JP2020128279A

  • Elevator management device, method for controlling the same, and elevator management system

    JP2023092274A

  • elevator control system

    JP7380793B1