Elevator control device, elevator control system, and elevator control method

Abstract

To efficiently move an autonomous mobile body and to improve the work efficiency of the autonomous mobile body by demonstrating the functions of the autonomous mobile body without reducing the work efficiency of a person. [Solution] An embodiment of an elevator control device is an elevator control device that has a car installed within a building and controls the raising and lowering of the car of an elevator that can carry people and autonomous mobile bodies that can move autonomously in the car and perform specified tasks, and is equipped with an acquisition unit that acquires the congestion level of the elevator, a judgment unit that determines whether the autonomous mobile body can be dispatched to the elevator based on the acquired congestion level of the elevator, and an instruction unit that, when it is determined that the autonomous mobile body can be dispatched to the elevator, instructs the autonomous mobile body that has been determined to be capable of being dispatched to move to the elevator.

Description

[Technical Field]

[0001] FIELD Embodiments of the present invention relate to an elevator control device, an elevator control system, and an elevator control method. [Background technology]

[0002] Recent elevator control systems operate in conjunction with autonomous mobile objects, such as robots that perform various tasks such as delivery services, cleaning, security, and inspection, by having them board the elevator car and move to their destination floor (target floor). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-25401 A [Patent Document 2] Patent No. 6414026 [Patent Document 3] Patent No. 6791399 [Patent Document 4] Patent No. 7106717 [Patent Document 5] Patent No. 7180810 [Patent Document 6] Patent No. 7323087 [Patent Document 7] Patent No. 6874111 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, the movement of an autonomous mobile body is controlled using an elevator regardless of the type of autonomous mobile body, and the operation specifications of the elevator linked to the autonomous mobile body are uniform. As a result, in the conventional technology, there are cases where the autonomous mobile body cannot perform work and cannot demonstrate its function, or the autonomous mobile body's movement time is extended, resulting in a decrease in the work efficiency of the autonomous mobile body. [Means for solving the problem]

[0005] An elevator control device according to an embodiment is an elevator control device that has a car installed in a building, and controls the raising and lowering of the car of an elevator that can carry an autonomous moving body capable of autonomously moving in the car to perform a predetermined task, and that can carry a person, and includes an acquisition unit that acquires a congestion level of the elevator, a determination unit that determines whether or not the autonomous moving body can be dispatched to the elevator based on the acquired congestion level of the elevator, and an instruction unit that, when it is determined that the autonomous moving body can be dispatched to the elevator, issues an instruction to move to the elevator to the autonomous moving body that has been determined to be dispatched. The autonomous mobile body includes a security autonomous mobile body for guarding the interior of a building, the acquisition unit acquires the number of users per unit time as the congestion level from one or more imaging devices set in the building and connected to the elevator control device via a network, the determination unit decides to dispatch the security autonomous mobile body when the total number of users acquired is equal to or less than a first threshold, the autonomous mobile body further includes a cleaning autonomous mobile body for cleaning the interior of the building, and the determination unit further decides to dispatch the cleaning autonomous mobile body when the total number of users acquired is equal to or greater than a second threshold that is greater than the first threshold. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of the overall configuration of an elevator control system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the functional configuration of the camera unit according to the first embodiment. [Figure 3] FIG. 3 is a block diagram illustrating an example of a functional configuration of a control panel according to the first embodiment. [Figure 4] FIG. 4 is a block diagram illustrating an example of a functional configuration of a server in the elevator cloud according to the first embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of congestion degree history data according to the first embodiment. [Figure 6] FIG. 6 is a block diagram illustrating an example of a functional configuration of a server in the robot cloud according to the first embodiment. [Figure 7] FIG. 7 is a block diagram illustrating an example of a functional configuration of the robot according to the first embodiment. [Figure 8] FIG. 8 is a sequence diagram illustrating an example of the overall flow of the elevator control process according to the first embodiment. [Figure 9] FIG. 9 is a flowchart illustrating an example of a procedure for the robot determination process according to the first embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of congestion degree history data according to the second embodiment. [Figure 11] FIG. 11 is a sequence diagram illustrating an example of the overall flow of the elevator control process according to the second embodiment. [Figure 12] FIG. 12 is a flowchart illustrating an example of a procedure for a robot determination process according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, embodiments will be described with reference to the drawings.

[0008] (First embodiment) Fig. 1 is a diagram showing an example of the overall configuration of an elevator control system 1 according to a first embodiment. As shown in Fig. 1, the elevator control system 1 of this embodiment mainly includes control panels 100A and 100B provided for each of a plurality of elevators 2A and 2B, controllers 150A and 150B provided for each of the plurality of elevators 2A and 2B, a camera unit 9, a control room 160, a server 210 in an elevator cloud 200, a server 310 in a robot cloud 300, a monitoring center 400, and robots 500A and 500B.

[0009] In this embodiment, a plurality of elevators 2A and 2B are installed in a building 3 (an example of a building) such as an office building, an apartment building, etc. In the example of Fig. 1, only two elevators 2A and 2B are shown, but in reality, three or more elevators are present.

[0010] Elevators 2A, 2B each have a car 50A, 50B in their respective hoistways 20A, 20B. Additionally, each hoistway 20A, 20B also has a hoisting machine and a counterweight (not shown). The cars 50A, 50B and the counterweight are supported so as to be able to rise and fall freely on a pair of guide rails (not shown) erected in each of the hoistways 20A, 20B, and move up and down via ropes.

[0011] In addition to the user 5A, robots 500A and 500B as autonomous moving bodies can also ride in the cars 50A and 50B.

[0012] The cars 50A and 50B are provided with operation panels 4A and 4B, cameras 7A and 7B, and load sensors 8A and 8B. The operation panels 4A, 4B receive various operations from users and issue various notifications to the elevator car 50. The operation panels 4A, 4B are provided with push buttons, non-contact sensors, speakers, LCD displays, etc. (none of which are shown) for specifying destination floors and opening and closing the doors of the elevator cars 50A, 50B. The operation panels 4A, 4B are also connected to the control panels 100A, 100B by wire or wirelessly. When users 5A, 5B press the destination floor push button or when a non-contact sensor detects the push button, a destination floor call is sent to the control panels 100A, 100B.

[0013] Here, the destination floor call is operation data that is performed by a user in the elevator car 50 to move the elevator car 50 to a desired destination floor. The destination floor call specifies a destination floor.

[0014] Furthermore, in this embodiment, a destination floor call for the robot is transmitted from the server 210 of the elevator cloud 200 to the control panel 100 via the controller 150. The destination floor call for the robot is operation data in which the robot ID of the robot 500 that wishes to use the elevator 2, the departure floor, and the destination floor (also referred to as the target floor) are specified, and the car 50 is moved to the specified departure floor and directed from the departure floor to the specified destination floor.

[0015] A platform call is operation data that a platform user performs to make a car 50 heading in either the up or down direction arrive at the platform. The platform call specifies the destination direction and the floor where the platform call is made (i.e., the departure floor).

[0016] Cameras 7A and 7B photograph the interiors of cars 50A and 50B and send the captured images to control panels 100A and 100B. When the doors of cars 50A and 50B are open at the platform, cameras 7A and 7B are capable of capturing images of the platform and send the captured images to control panels 100A and 100B.

[0017] The load sensors 8A and 8B are provided on the bottom of the cars 50A and 50B and detect the weight of the car 50. When a user 5A or a robot 500A or 500B is inside the car 50A or 50B, the load sensors 8A and 8B detect the weight of the car 50 itself, as well as the weight of the user 5A and the robot 500A or 500B. The load sensors 8A and 8B send the detected weights as detection signals to the control panels 100A and 100B.

[0018] A landing is provided on each floor. The landing is a place where users and the robot 500 wait for the arrival of the elevator cars 50A and 50B of the elevators 2A and 2B.

[0019] Camera units 9 are provided on the walls of the landings on each floor. The camera units 9 capture images of the landings. Camera units 10 are also provided in locations other than the landings within building 3 where users of elevator 2 can move. Here, camera units 9 and 10 are examples of imaging devices.

[0020] The images captured by the camera units 9 and 10 are stored in the camera units 9 and 10 and subjected to image analysis, and the number of users of the elevators 2A and 2B as a result of the image analysis is transmitted at regular intervals to the server 210 in the elevator cloud 200. Details of the camera units 9 and 10 will be described later.

[0021] Control panels 100A and 100B and controllers 150A and 150B are provided inside the elevator shafts 20A and 20B, respectively. The control panels 100A and 100B are connected wirelessly or by wire to operation panels 4A and 4B provided on the cars 50A and 50B.

[0022] The control panels 100A and 100B control the operation of the cars 50A and 50B in the elevators 2A and 2B, respectively. The control panels 100A and 100B are connected to the controllers 150A and 150B, respectively, by wire or wirelessly. The control panels 100A and 100B will be described in detail later.

[0023] Each of the controllers 150A, 150B is connected to a server 210 in the elevator cloud 200 via a network. The controllers 150A, 150B are intermediary devices that control communication between the control panels 100A, 100B and the server 210 and have an interface function and a hub function for intermediating various signals exchanged between the control panels 100A, 100B and the server 210. Each of the controllers 150A, 150B is configured as a computer that includes a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc.

[0024] The manager of building 3 is present in control room 160 and issues various instructions to control panels 100A and 100B. The manager of control room 160 also receives various instructions from control panels 100A and 100B by email or the like via a PC or terminal device.

[0025] The server 210 in the elevator cloud 200 instructs the control panels 100A and 100B via the controllers 150A and 150B to perform various controls on the cars 50A and 50B of the elevators 2A and 2B, or receives various requests and data from the control panels 100A and 100B via the controllers 150A and 150B. The server 210 in the elevator cloud 200 receives the number of users and the number of people staying there from the camera units 9 and 10. Furthermore, the server 210 in the elevator cloud 200 is connected to a monitoring center 400 (an in-house server) and a server 310 in the robot cloud 300 via a network.

[0026] An in-house server (not shown) is installed in the monitoring center 400. The in-house server is a server installed in an affiliated company of the elevator 11, and collects information necessary for maintenance management and remote monitoring of the elevator 2 from the elevators 2A and 2B. This allows maintenance personnel to deal with the malfunction by referring to the information necessary for maintenance management collected in the in-house server of the monitoring center 400. Furthermore, when functions or services are executed through the elevator cloud 200, the in-house server of the monitoring center 400 can be accessed as needed to refer to building and elevator information, or the maintenance personnel can obtain information necessary for elevator management.

[0027] The server 310 of the robot cloud 300 receives various requests and various data from the server 210 of the elevator cloud 200. The server 310 of the robot cloud 300 is connected to multiple robots 500A, 500B, and 500C in the building 3 via a network, and transmits various instructions to each of the multiple robots 500A, 500B, and 500C. The server 210 of the elevator cloud 200 and the server 310 of the robot cloud 300 will be described in detail later.

[0028] The number of elevators is not limited, and three or more elevators are installed in building 3. Alternatively, the number of elevators may be one. Therefore, the number of elevator shafts 20A, 20B, cars 50A, 50B, control panels 100A, 100B, and controllers 150A, 150B also varies depending on the number of elevators 2A, 2B. When the multiple elevators 2A, 2B, the multiple elevator shafts 20A, 20B, the multiple cars 50A, 50B, the multiple control panels 100A, 100B, and the multiple controllers 150A, 150B are not distinguished from one another, they are referred to as elevator 2, hoistway 20, car 50, control panel 100, and controller 150. When the operation panels 4A, 4B, cameras 7A, 7B, and load sensors 8A, 8B are not distinguished from one another, they are referred to as operation panel 4, camera 7, and load sensor 8.

[0029] The robots 500A and 500B are autonomous mobile bodies that can travel autonomously and board the elevator 2. When there is no need to distinguish between the robots 500A and 500B, they will be referred to as robot 500. The robots 500 perform various tasks such as delivery services, cleaning, security, and inspection. The robots 500 according to this embodiment include at least a security robot 500A that performs security work within the building 3, and a cleaning robot 500B that performs cleaning work within the building 3, including the elevator 2. Details of the robot 500 will be described later.

[0030] Next, we will explain the details of the camera units 9 and 10. The camera units 9 and 10 have the same configuration. 2 is a diagram showing an example of the functional configuration of the camera units 9 and 10 according to the first embodiment. The camera units 9 and 10 are examples of imaging devices.

[0031] As shown in FIG. 2, the camera units 9 and 10 mainly include a camera 901, an image processing unit 902, a communication unit 903, and a storage unit 910.

[0032] The storage unit 910 is a storage medium such as a hard disk drive (HDD) or a solid state drive (SSD). The camera 901 captures images of the surroundings, that is, the landing area and the inside of the building 3, and stores the captured images in the storage unit 910.

[0033] The image processing unit 902 analyzes the images captured by the camera 901 and stored in the storage unit 910, and counts the number of users per unit time of the elevator 2. Specifically, the image processing unit 902 of the camera unit 9 installed at the landing analyzes the captured images and counts the number of people (hereinafter referred to as "retainers") staying at the landing and waiting for the arrival of the elevator 2 per unit time.

[0034] The image processing unit 902 of the camera unit 10 installed outside the landing of the building 3 counts the number of people per unit time who move outside the landing in the building 3, pass the camera unit 10, and head towards the elevator 2 (hereinafter referred to as "passing people"). Here, passing people and staying people correspond to users of the elevator 2.

[0035] At regular intervals, a camera 901 captures images of the surroundings, and an image processing unit 902 starts analyzing the number of users. The start date and time of each regular interval is referred to as the acquisition time.

[0036] The communication unit 903 transmits the number of passersby and stayers per unit time (i.e., the number of users) counted by the image processing unit 902 to the server 210 in the elevator cloud 200. The unit time is, for example, 30 minutes, 1 hour, etc., but is not limited to these. Specifically, the image processing unit 902 counts the number of users for a predetermined unit time from the acquisition time, and when the unit time has elapsed, the communication unit 903 transmits the number of users counted during the unit time to the server 210 in the elevator cloud 200.

[0037] Next, the control panel 100 will be described. 3 is a block diagram showing an example of a functional configuration of the control panel 100 according to the embodiment. The control panel 100 is an example of an elevator control device. The control panel 100 has a typical computer configuration, and as shown in FIG. 3, mainly includes an image processing unit 124, a control unit 120, a communication unit 102, and a storage unit 110.

[0038] 2, the control panel 100 is connected by wire or wirelessly to the load sensor 8 and the camera 7 inside the car 50. The load sensor 8 (8A, 8B) is provided in the car 50 as described above. The camera 7 is provided near the ceiling of the car 50 so as to be able to capture images of the inside of the car 50 and, when the door of the car 50 is open, the landing.

[0039] The storage unit 110 is a storage medium (that is, a memory device) such as a ROM or RAM, etc. The storage unit 110 stores a management database 111 (hereinafter referred to as "management DB 111").

[0040] The management DB 111 is a database in which various data for using the elevator 2 is registered. For example, the management DB 111 registers the robot IDs of the robots 500 that can ride the elevator 2 controlled by the control panel 100. Here, the robot ID is information for identifying the robot 500.

[0041] The image processing unit 124 analyzes the image captured by the camera 7 . The communication unit 102 is made up of a communication device having a predetermined communication protocol, and performs communication processing between the control panel 100 and the controller 150. That is, the communication unit 102 transmits and receives various data to and from other control panels 100 and the server 210 of the elevator cloud 200 via the controller 150. The communication unit 102 also transmits and receives various instructions and notifications to and from the mobile terminal, PC, etc. of the manager of the control room 160.

[0042] The control unit 120 is made up of a hardware processor (CPU) and mainly includes a normal operation control unit 121, a robot-linked operation control unit 122, and an allocation unit 125, as shown in FIG.

[0043] When the communication unit 102 receives a destination floor call for the robot from the server 210 of the elevator cloud 200, the allocation unit 125 allocates the elevator car 50 to the destination floor call by group management control in cooperation with the control panels 100 of other elevators 2.

[0044] Here, group management control refers to control for allocating the car 5 closest to a departure floor, such as a floor where a call for the car 50 is made. In this embodiment, the allocation unit 125 performs group management control in cooperation with the other control panels 100 by, for example, inquiring of the control panels 100 of other elevators 2 about the departure floor and the current position and elevation status of the car 5 and receiving the response.

[0045] The normal operation control unit 121 controls the normal operation. Normal operation is operation in which only people are on board the elevator 5, without any robots on board.

[0046] The robot interlocking operation control unit 122 controls the robot interlocking operation. Robot-linked driving is driving in which the robot 500 rides in the car 5. Robot-linked driving includes robot-only driving in which no person rides in the car 5, and non-robot-only driving in which a person can ride in the car 5. Robot-linked driving is sometimes referred to as robot driving.

[0047] Next, the server 210 in the elevator cloud 200 will be described. 4 is a block diagram showing an example of the functional configuration of the server 210 in the elevator cloud 200 according to the embodiment. As shown in FIG. 4, the server 210 mainly includes a control unit 211, a determination unit 213, a communication unit 212, and a storage unit 220 as a general computer configuration.

[0048] The communication unit 212 is composed of a communication device having a predetermined communication protocol, and performs communication processing between the server 210 and the controller 150 of the control panel 100, and communication processing between the server 210 and the server 310 in the robot cloud 300.

[0049] In this embodiment, the communication unit 212 receives the number of passing and remaining people (that is, the number of users) per unit time in the elevator 2 from each of the camera units 9 and 10 at regular time intervals.

[0050] Furthermore, when the determination unit 213, which will be described later, determines that the robot 500 can be dispatched to the elevator 2, the communication unit 212 instructs the robot 500 determined to be able to be dispatched (i.e., the security robot 500A or the cleaning robot 500B) to move to the elevator 2. Specifically, the communication unit 212 instructs the robot 500 to move by transmitting a movement instruction specifying the robot ID of the robot 500 determined to be able to be dispatched (i.e., the security robot 500A or the cleaning robot 500B) to the server 310 in the robot cloud 300. The communication unit 212 is an example of an acquisition unit and an instruction unit.

[0051] The communication unit 212 also receives information including the robot ID, departure floor, and destination floor specified by the robot 500 from the server 310 of the robot cloud 300. The communication unit 212 also transmits the destination floor call generated by the control unit 211 to the control panel 100.

[0052] The control unit 211 is composed of a hardware processor (CPU). When the communication unit 212 receives information including the robot ID, departure floor, and destination floor specified by the robot 500 from the server 310 of the robot cloud 300, the control unit 211 generates a destination floor call including the robot ID, departure floor, and destination floor.

[0053] The determination unit 213 determines whether to dispatch the robot 500 to the elevator 2 based on the number of users per unit time as the congestion level acquired by the communication unit 212. Specifically, the determination unit 213 determines to dispatch the security robot 500A when the total number of users per unit time received by the communication unit 212 from each of the camera units 9 and 10 is equal to or less than a first threshold. Furthermore, the determination unit 213 determines to dispatch the cleaning robot 500B when the total number of users per unit time received by the communication unit 212 from each of the camera units 9 and 10 is equal to or greater than a second threshold that is greater than the first threshold. The number of users per unit time and the total number of users per unit time are examples of the congestion level.

[0054] The determination unit 213 determines whether or not to deploy the robot 500 based on the total number of users per unit time at regular intervals, and continues the determination result for the regular interval. Then, the determination unit 213 records the result of the determination on whether or not to deploy the robot 500 as congestion level history data 221 in the storage unit 220.

[0055] The storage unit 220 is a storage medium (memory device) such as an HDD, SSD, ROM, RAM, etc. The storage unit 220 stores various programs. The storage unit 220 according to this embodiment also stores the congestion level history data 221. The congestion level history data 221 is data that indicates the history of the congestion level of the elevator 2 over time.

[0056] FIG. 5 is a diagram showing an example of the congestion level history data 221 according to the first embodiment. As shown in FIG. 5, the congestion level history data 221 according to this embodiment corresponds to the acquisition time, the total number of users (i.e., the number of passers-by and passers-by) as the congestion level, the congestion level classification, whether a security robot can be deployed, and whether a cleaning robot can be deployed.

[0057] As described above, the acquisition time is the date and time when the camera units 9 and 10 start capturing images of the surrounding area and analyzing the number of users. In the congestion level history data 221 according to this embodiment, the number of users in the elevator 2 on the first floor is received at a fixed acquisition time every three hours.

[0058] The total number of users (i.e., the number of passersby and visitors) is the total number of users per unit time received by the communication unit 212. Here, the determination unit 213 acquires and sums up the number of users in the first unit time of the acquisition time every three hours.

[0059] Congestion levels are classified according to the total number of users per unit time. In the example of FIG. 5, if the total number of users per unit time is between 0 and 99, the congestion level is classified as "small." If the total number of users per unit time is between 1000 and 150, the congestion level is classified as "medium." If the total number of users per unit time is between 151 and 200, the congestion level is classified as "large." If the total number of users per unit time is 201 or more, the congestion level is classified as "extra large."

[0060] The decision as to whether or not to deploy a security robot is a decision made by the decision unit 213 based on a first threshold value. In the example of Fig. 5, the first threshold value is 50 people. Therefore, the decision unit 213 decides to deploy the security robot 500A when the total number of users per unit time is 50 people or less, and decides not to deploy the security robot 500A when the total number of users per unit time is more than 50 people, and records each decision result in the congestion level history data 221.

[0061] The decision as to whether or not to dispatch the cleaning robot is a decision made by the decision unit 213 based on a second threshold value. In the example of Fig. 5, the second threshold value is 150 people. Therefore, the decision unit 213 decides to dispatch the cleaning robot 500B when the total number of users per unit time is 150 or more, and decides not to dispatch the cleaning robot 500B when the total number of users per unit time is less than 150 people, and records each decision result in the congestion level history data 221. It should be noted that the first threshold value and the second threshold value are not limited to these examples.

[0062] Next, the server 310 in the robot cloud 300 will be described. FIG. 6 is a block diagram illustrating an example of a functional configuration of the server 310 in the robot cloud 300 according to the embodiment. As shown in FIG. 6, the server 310 mainly includes a control unit 311, a communication unit 312, and a storage unit 320, as a general computer configuration.

[0063] The storage unit 320 is a storage medium (memory device) such as a ROM, a RAM, etc. The storage unit 320 stores various programs.

[0064] The communication unit 312 is made up of a communication device having a predetermined communication protocol, and performs communication processing between the server 310 and the server 210 in the elevator cloud 200 , and communication processing between the server 310 and the robot 500 .

[0065] In this embodiment, the communication unit 312 receives information from the robot 500, including the robot ID, departure floor, and destination floor specified by the robot 500, and transmits the information to the server 210 of the elevator cloud 200.

[0066] The control unit 311 is made up of a hardware processor (CPU) and controls various processes relating to the elevator of the robot 500.

[0067] Next, the robot 500 will be described. 7 is a block diagram showing an example of the functional configuration of a robot 500 according to an embodiment. As shown in FIG. 7, the robot 500 mainly includes a camera 506, various sensors 505, a control unit 501, a communication unit 502, a drive unit 503, and a storage unit 510. The security robot 500A and the cleaning robot 500B both have the same functional configuration shown in FIG.

[0068] The camera 506 captures images of the surroundings of the robot 500 and transmits the captured images to the server 310 of the robot cloud 300. The robot 500 may be configured to further transmit the captured images to the control panel 100.

[0069] The various sensors 505 include, but are not limited to, a human sensor, an acceleration sensor, a load sensor, and the like.

[0070] The storage unit 510 is a storage medium (memory device) such as a ROM, a RAM, etc. The storage unit 510 stores various programs.

[0071] The communication unit 502 is made up of a communication device having a predetermined communication protocol, and performs communication processing between the robot 500 and the server 310 in the robot cloud 300 . In this embodiment, the communication unit 502 transmits information including the robot ID, the departure floor, and the destination floor to the server 310 in the robot cloud 300. The communication unit 502 also receives instructions to wait at a platform or to stop operation from the server 310 in the robot cloud 300.

[0072] The driving unit 503 drives the robot 500 to move. The control unit 501 is made up of a hardware processor (CPU). During normal operation of the elevator 2, the control unit 501 reads and executes various programs from the storage unit 510, thereby performing various operations in the elevator 2.

[0073] In this embodiment, when the robot gets into the car 5 of the elevator 2, the control unit 501 generates information including the robot ID, the departure floor, and the destination floor. In addition, the control unit 501 controls the driving of the driving unit 503 in response to an instruction from the server 310 in the robot cloud 300 to perform travel control.

[0074] The above configuration of the robot 500 is an example, and the robot 500 may further include an audio output unit such as a speaker and an input unit such as a touch panel.

[0075] Next, an elevator control process performed by the elevator control system 1 of this embodiment configured as above will be described. 8 is a sequence diagram showing an example of the overall flow of the elevator control process according to the first embodiment. In FIG. 8, n is the number of camera units 9 and 10.

[0076] In each of the n camera units 9, 10, the camera 901 captures an image, and the image processing unit 902 analyzes the captured image to determine the number of users per unit time (S100). Then, the communication unit 903 transmits the number of users per unit time to the server 210 of the elevator cloud 200 (S101).

[0077] In the server 210 of the elevator cloud 200, the communication unit 212 receives the number of users per unit time from each of the n camera units 9, 10. Then, the determination unit 213 executes a determination process for the robot 500 (S102).

[0078] Here, the details of the determination process of the robot 500 in S102 will be described. FIG. 9 is a flowchart illustrating an example of a procedure for the robot determination process according to the first embodiment.

[0079] First, in the server 210 of the elevator cloud 200, the determination unit 213 calculates the total number of users per unit time received by the communication unit 212, and determines whether the total is equal to or less than a first threshold (S201). If the total number of users is equal to or less than the first threshold (S201: Yes), the determination unit 213 decides to deploy the security robot 500A and not to deploy the cleaning robot 500B (S202). Then, the process returns to the caller.

[0080] On the other hand, if the total number of users is greater than the first threshold in S201 (S201: No), the determination unit 213 determines not to deploy the security robot 500A (S203). Next, the determination unit 213 determines whether the total number of users is greater than or equal to the second threshold (S204). If the total number of users is greater than or equal to the second threshold (S204: Yes), the determination unit 213 determines to deploy the cleaning robot 500B (S205).

[0081] On the other hand, if the total number of users is less than the second threshold value in S204 (S204: No), the determination unit 213 determines not to deploy the cleaning robot 500B (S206). Then, the process returns to the caller.

[0082] When the robot 500 determination process in S102 is completed and there is a robot 500 available for deployment, the communication unit 212 specifies the robot ID of the robot 500 available for deployment (i.e., a security robot 500A or / and a cleaning robot 500B) and sends a movement instruction for the robot 500 to the server 310 of the robot cloud 300 (S103).

[0083] In the server 310 of the robot cloud 300, the communication unit 312 receives a movement instruction for the robot 500 that can be deployed from the server 210 of the elevator cloud 200, and transmits the received movement instruction to the robot 500 with the specified robot ID (S104).

[0084] In the robot 500, when the communication unit 502 receives the movement instruction from the server 310 of the robot cloud 300, the control unit 501 controls the driving unit 503 to move the robot 500 from the waiting place to the boarding area in accordance with the movement instruction (S105). Then, the robot 500 waits at the boarding area.

[0085] Here, if the floor to be worked on is the same floor as the floor where the robot 500 is waiting, the process proceeds to S121, and the robot 500 performs the work (S121). That is, the security robot 500A performs security work, and the cleaning robot 500B performs cleaning work. Then, when the work is completed, the process ends.

[0086] On the other hand, if the floor to be worked on is different from the floor where the robot 500 is waiting, the following process is executed: That is, in the robot 500, the communication unit 502 transmits its own robot ID, the departure floor, and the destination floor to the server of the robot cloud 300 (S106).

[0087] In the server 310 of the robot cloud 300, the communication unit 312 receives the robot ID, departure floor, and destination floor from the robot 500, and transmits the received robot ID, departure floor, and destination floor to the server 210 of the elevator cloud 200 (S107).

[0088] In the server 210 of the elevator cloud 200, when the communication unit 212 receives the robot ID, the departure floor, and the destination floor from the server 310 of the robot cloud 300, the control unit 211 generates a destination floor call from the robot ID, the departure floor, and the destination floor (S108). Then, the communication unit 212 transmits the generated destination floor call to the control panel 100 (S109).

[0089] In the control panel 100, when the communication unit 102 receives a destination floor call from the server 210 of the elevator cloud 200 via the controller 150, the allocation unit 125 allocates a car 50 based on the received destination floor call (S110). Here, the allocation of the car 50 is performed by group management control in cooperation with the control panel 100 that controls the other elevators 2.

[0090] Next, the robot interlocking operation control unit 122 of the control panel 100 moves the allocated car 50 to the departure floor specified by the destination floor call (S111).

[0091] When the elevator car 50 arrives at the departure floor and the door opens, the robot 500, which recognizes the door opening with a camera or the like, gets on the elevator car 50 (S112). Then, the communication unit 502 of the robot 500 transmits a boarding completion notification to the server 310 of the robot cloud 300 (S113).

[0092] This boarding completion notification is transferred from the server 310 of the robot cloud 300 to the server 210 of the elevator cloud 200 (S114), and further transferred from the server 210 of the elevator cloud 200 to the control panel 100 (S115).

[0093] In the control panel 100, when the communication unit 102 receives a boarding completion notification from the server 210 of the elevator cloud 200 via the controller 150, the robot linked operation control unit 122 moves the elevator car 50 with the robot 500 in it to the destination floor (S116).

[0094] When the elevator car 50 arrives at the destination floor, the communication unit 102 in the control panel 100 transmits an arrival notification to the server 210 of the elevator cloud 200 via the controller 150 (S117). This arrival notification is transferred from the server 210 of the elevator cloud 200 to the server 310 of the robot cloud 300 (S118), and further transferred from the server 310 of the robot cloud 300 to the robot 500 (S119).

[0095] In the robot 500, when the communication unit 502 receives an arrival notification from the server 310 of the robot cloud 300, the control unit 501 controls the driving unit 503 to cause the robot 500 to dismount from the car 50 (S120). Then, the robot 500 performs work at the floor where it dismounted (S121). That is, the security robot 500A performs security work, and the cleaning robot 500B performs cleaning work. Then, when the work is completed, the process ends.

[0096] In this manner, in the elevator control system 1 according to this embodiment, the server 210 of the elevator cloud 200 acquires the congestion level of the elevator 2, and determines whether or not the robot 500 can be dispatched to the elevator 2 based on the acquired congestion level of the elevator. If it is determined that the robot 500 can be dispatched to the elevator 2, the server 210 instructs the robot 500 that has been determined to be capable of dispatching to move to the elevator 2.

[0097] Therefore, according to this embodiment, the elevator operation specifications are variable depending on the type of robot 500, so that the robot 500 can move efficiently and the functions of the robot 500 can be exerted, thereby improving the work efficiency of the robot 500 without reducing the work efficiency of people.

[0098] Furthermore, in the elevator control system 1 according to this embodiment, the server 210 of the elevator cloud 200 acquires the number of users per unit time as the degree of congestion from one or more camera units 9, 10, and decides to dispatch the security robot 500A when the total acquired number of users is equal to or less than a first threshold value.

[0099] For this reason, in this embodiment, when the number of users of the elevator 2 is low and the degree of congestion is low, the security robot 500A can be dispatched to the elevator 2 to perform security. Therefore, according to this embodiment, the security robot 500A can be moved efficiently and the functions of the security robot 500A can be exerted, thereby improving the work efficiency of the security robot 500A without reducing the work efficiency of people.

[0100] Furthermore, in the elevator control system 1 according to this embodiment, the server 210 of the elevator cloud 200 decides to dispatch the cleaning robot 500B when the total number of acquired users is equal to or greater than a second threshold value that is greater than the first threshold value.

[0101] For this reason, in this embodiment, when the number of users of the elevator 2 is large and the degree of congestion is high, there is little need to dispatch the security robot 500A to the elevator 2, and rather, since there is a concern about the generation of dirt, the cleaning robot 500B can be dispatched to perform cleaning. Therefore, according to this embodiment, the cleaning robot 500B can be moved efficiently and the functions of the cleaning robot 500B can be exerted, thereby improving the work efficiency of the cleaning robot 500B without reducing the work efficiency of humans.

[0102] Furthermore, in the elevator control system 1 according to this embodiment, the server 210 of the elevator cloud 200 issues a movement instruction to the robot 500 to the elevator 2 via the server 310 of the robot cloud 300. Therefore, according to this embodiment, the movement instruction is sent via the server 310 of the robot cloud 300 that manages the robot 500, thereby further improving the work efficiency of the robot 500.

[0103] (Second embodiment) In the first embodiment, whether or not to dispatch the robot 500 was determined based on the number of users of the elevator 2 as the degree of congestion of the elevator 2, but in this second embodiment, whether or not to dispatch the robot is determined based on the number of floors in the elevator car 50 as the degree of congestion of the elevator 2.

[0104] The configuration of the elevator control system 1, the configuration of the camera units 9 and 10, the configuration of the control panel 100, the configuration of the server 210 of the elevator cloud 200, the configuration of the server 310 of the robot cloud 300, and the configuration of the robot 500 in the second embodiment are all the same as those in the first embodiment.

[0105] The normal operation control unit 121 and the robot-linked operation control unit 122 of the control panel 100 according to this embodiment start counting the number of floors reached every time the elevator car 50 managed by them stops at each floor at regular intervals, and store the counted number of floors reached in the memory unit 110. The date and time at which the counting for each regular interval starts is referred to as the acquisition time. Here, the number of floors reached is counted as one for a stop at the departure floor, one for a stop at an intermediate floor, and one for a stop at the destination floor.

[0106] The communication unit 102 transmits the number of beds reached per unit time counted by the normal operation control unit 121 and the robot-linked operation control unit 122 to the server 210 in the elevator cloud 200 via the controller 150. The unit time is, for example, one hour, but is not limited to this. Specifically, the normal operation control unit 121 and the robot-linked operation control unit 122 count the number of beds reached for the unit time from the acquisition time, and after the unit time has elapsed, the communication unit 102 transmits the number of beds reached during the unit time to the server 210 in the elevator cloud 200.

[0107] The communication unit 212 of the server 210 of the elevator cloud 200 receives the number of elevator cars 50 that arrive at each floor per unit time from one or more control panels 100.

[0108] The determination unit 213 of the server 210 of the elevator cloud 200 decides to dispatch the security robot 500A when the total number of beds received by the communication unit 212 is equal to or less than a third threshold. In addition, the determination unit 213 decides to dispatch the cleaning robot 500B when the total number of beds received by the communication unit 212 is equal to or less than a fourth threshold that is greater than the third threshold.

[0109] The determination unit 213 determines whether or not to dispatch the robot 500 based on the total number of landings per unit time at regular intervals, and continues the determination result for the regular interval. Then, the determination unit 213 records the result of the determination on whether or not to dispatch the robot 500 as congestion level history data 221 in the storage unit 220.

[0110] FIG. 10 is a diagram showing an example of congestion level history data 221 according to the second embodiment. As shown in FIG. 10, the congestion level history data 221 according to this embodiment corresponds to the acquisition time, the total number of beds as the congestion level, the congestion level classification, whether a security robot can be deployed, and whether a cleaning robot can be deployed.

[0111] As described above, the acquisition time is the date and time when counting of the number of floor arrivals is started by the control panel 100. In the congestion degree history data 221 according to this embodiment, the number of floor arrivals for the elevator 2 on the first floor is received at a fixed acquisition time every three hours.

[0112] The total number of bed arrivals is the total number of bed arrivals per unit time received by the communication unit 212. Here, the determination unit 213 acquires and sums up the number of bed arrivals in the first unit time of every three-hour acquisition time.

[0113] The congestion level is classified according to the total number of bed arrivals per unit time. In the example of FIG. 10, if the total number of bed arrivals per unit time is between 0 and 30, the congestion level is classified as "small." If the total number of bed arrivals per unit time is between 31 and 50, the congestion level is classified as "medium." If the total number of bed arrivals per unit time is between 51 and 100, the congestion level is classified as "large." If the total number of bed arrivals per unit time is 101 or more, the congestion level is classified as "extra large."

[0114] The decision as to whether or not to deploy a security robot is a decision made by the decision unit 213 based on a third threshold value. In the example of Fig. 10, the third threshold value is 50. Therefore, the decision unit 213 decides to deploy the security robot 500A when the total number of beds reached per unit time is 50 or less, and decides not to deploy the security robot 500A when the total number of beds reached per unit time is greater than 50, and records each decision result in the congestion level history data 221.

[0115] The dispatchability of the cleaning robot is a result of the determination made by the determination unit 213 based on a fourth threshold value. In the example of Fig. 10, the fourth threshold value is 130. Therefore, the determination unit 213 determines to dispatch the cleaning robot 500B when the total number of beds landed per unit time is 130 or less, and determines not to dispatch the cleaning robot 500B when the total number of beds landed per unit time is more than 130, and records each determination result in the congestion level history data 221. It should be noted that the examples of the third threshold and the fourth threshold are not limited to these.

[0116] Next, an elevator control process performed by the elevator control system 1 of this embodiment configured as above will be described. 11 is a sequence diagram showing an example of the overall flow of elevator control processing according to the second embodiment, in which n is the number of control panels 100.

[0117] First, in each of the n control panels 100, the normal operation control unit 121 and the robot-linked operation control unit 122 count the number of floors reached by the elevator 50 (S301). Then, the communication unit 102 transmits the number of floors reached per unit time to the server 210 of the elevator cloud 200 via the controller 150 (S302).

[0118] In the server 210 of the elevator cloud 200, the communication unit 212 receives the number of floors reached per unit time from each of the n control panels 100. Then, the determination unit 213 executes a determination process for the robot 500 (S303).

[0119] Here, the details of the determination process of the robot 500 in S303 will be explained. FIG. 12 is a flowchart illustrating an example of a procedure for a robot determination process according to the second embodiment.

[0120] First, in the server 210 of the elevator cloud 200, the determination unit 213 calculates the total number of beds landed per unit time received by the communication unit 212, and determines whether the total is equal to or less than a third threshold (S401). If the total number of beds landed is equal to or less than the third threshold (S401: Yes), the determination unit 213 decides to dispatch the security robot 500A and the cleaning robot 500B (S402). Then, the process returns to the caller.

[0121] On the other hand, if the total number of landings is greater than the third threshold in S401 (S401: No), the determination unit 213 determines not to deploy the security robot 500A (S403). Next, the determination unit 213 determines whether the total number of landings is equal to or less than the fourth threshold (S404). If the total number of landings is equal to or less than the fourth threshold (S404: Yes), the determination unit 213 determines to deploy the cleaning robot 500B (S405).

[0122] On the other hand, if the total number of landings is greater than the fourth threshold value in S404 (S404: No), the determination unit 213 determines not to deploy the cleaning robot 500B (S406). Then, the process returns to the caller.

[0123] When the process of determining the robot 500 in S303 is completed and there is a robot 500 that can be deployed, the communication unit 212 specifies the robot ID of the robot 500 that can be deployed (i.e., the security robot 500A and / or the cleaning robot 500B) and transmits a movement instruction for the robot 500 to the server 310 of the robot cloud 300 (S103). The subsequent processes are performed in the same manner as in the first embodiment.

[0124] In this manner, in the elevator control system 1 according to this embodiment, the server 210 of the elevator cloud 200 acquires the number of floors reached by the elevator car 50 per unit time at each floor from one or more control panels 100, and decides to dispatch an autonomous mobile security vehicle when the total of the acquired number of floors reached is equal to or less than the third threshold value.

[0125] For this reason, in this embodiment, when the number of floors in the car 50 is small and the degree of congestion is low, the security robot 500A can be dispatched to the elevator 2 to perform security. Therefore, according to this embodiment, the security robot 500A can be moved efficiently, and the functions of the security robot 500A can be exerted, thereby improving the work efficiency of the security robot 500A without reducing the work efficiency of people.

[0126] In addition, in the elevator control system 1 according to this embodiment, the server 210 of the elevator cloud 200 decides to dispatch a cleaning autonomous moving body when the total number of acquired floor landings is equal to or less than a fourth threshold value that is greater than the third threshold value.

[0127] For this reason, in this embodiment, when the number of floors in the cars 50 is relatively high and the degree of congestion is relatively high, there is little need to dispatch the security robot 500A to the elevator 2, and rather, since there is a concern about the occurrence of dirt, the cleaning robot 500B can be dispatched to perform cleaning. Therefore, according to this embodiment, the cleaning robot 500B can be moved efficiently and the functions of the cleaning robot 500B can be exerted, thereby improving the work efficiency of the cleaning robot 500B without reducing the work efficiency of people.

[0128] (Variation) Various modifications of the above embodiment are possible. In the above embodiment, an example has been described in which one security robot 500A and one cleaning robot 500B are provided as the robot 500, but the present invention is not limited to this.

[0129] For example, a plurality of security robots 500A and cleaning robots 500B may be provided. In this case, the robots 500 can perform their original tasks more efficiently. The robots 500 may be used for security, cleaning, or other purposes.

[0130] When a security robot 500A and a cleaning robot 500B move to the same floor, the server 210 of the elevator cloud 200 may be configured to give priority to the movement of the security robot 500. Also, when the robots 500 are waiting on the same floor, the server 210 of the elevator cloud 200 may be configured to have the robots 500 ride together in the same car 50.

[0131] The security robot 500 may be configured to contact the control room 160 or the monitoring center 400 via the server 310 of the robot cloud 300 when it detects a human behaving suspiciously using the camera 506. In this case, the robot 500 may also send image and audio data collected by the camera 506.

[0132] In addition, in the above embodiment, the congestion level is compared with a threshold value to determine whether to deploy the robot 500, but the judgment unit 213 of the server 210 of the elevator cloud 200 may be configured to determine whether to deploy the robot 500 according to the classification of the congestion level.

[0133] In this case, if the congestion level is classified as "extra large," the manager of the robot 500 may manually instruct the robot 500 to perform the work.

[0134] When the congestion level is classified as "small" or "medium," the control panel 100 may be controlled so that the robot 500 is not riding together with a human in the car 50. Note that when the congestion level is classified as "large" or "extra large," the control panel 100 can be configured to not ride together with a human in the car 50.

[0135] The robot 500 may be configured so that even if the degree of congestion increases over the course of a certain period of time (e.g., three hours), the robot 500 does not stop moving the elevator car 50 of the elevator 2 or stopping work on each floor.

[0136] The robot 500 may be configured to transmit notifications from the robot 500 regarding the start, progress, and completion of work, as well as image data and voice data, to the server 310 of the robot cloud 300 in real time.

[0137] After the congestion level history data 221 is generated, the determination unit 213 of the server 210 of the elevator cloud 200 can be configured to determine whether to deploy the robot 500 based on the congestion level history data 221. For example, on a day different from the day of the acquisition time recorded in the congestion level history data 221, in a time period that is the same as the time period of the acquisition time recorded in the congestion level history data 221, the determination unit 213 can be configured to determine whether to deploy the robot 500 in accordance with the availability of deployment recorded in the congestion level history data 221. In this case, the determination process can be simplified, and work efficiency can be further improved.

[0138] Even in this case, the determination unit 213 of the server 210 of the elevator cloud 200 may be configured to acquire a congestion degree, and if the congestion degree differs from the congestion degree recorded in the congestion degree history data 221, determine whether to deploy the robot 500 based on the newly acquired congestion degree. In this case, it becomes possible to more accurately determine whether to deploy the robot 500 in accordance with changes in the congestion degree of the elevator 2, thereby enabling the robot 500 to move efficiently and, by utilizing the functions of the robot 500, to further improve the work efficiency of the robot 500A without reducing the work efficiency of people.

[0139] The elevator control program executed by the server 210 of the elevator cloud 200 according to the above-described embodiment and modifications is provided in a state that it is pre-installed in a ROM or the like.

[0140] The elevator control program executed by the server 210 of the elevator cloud 200 according to the above embodiments and modifications may be configured to be provided by being recorded in an installable or executable format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk).

[0141] Furthermore, the elevator control program executed by the server 210 of the elevator cloud 200 according to the above-described embodiments and modifications may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network.

[0142] Furthermore, the elevator control program executed by the server 210 of the elevator cloud 200 according to the above embodiment and modifications may be configured to be provided or distributed via a network such as the Internet.

[0143] The elevator control program executed on the server 210 of the elevator cloud 200 in the above-described embodiment and modified example has a modular structure including each of the functional units described above, and in actual hardware, the CPU reads and executes the elevator control program from the ROM, thereby loading each of the above units onto the main memory device and generating each of the functional units onto the main memory device.

[0144] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0145] 1...Elevator control system, 2, 2A, 2B...Elevator, 3...Building, 4, 4A, 4B...Operation panel, 5A...User, 7, 7A, 7B, 901...Camera, 9, 10...Camera unit, 8, 8A, 8B...Load sensor, 20, 20A, 20B...Hoistway, 50, 50A, 50B...Car, 100, 100A, 100B...Control panel, 120, 211, 311, 501...Control unit, 102, 212, 312, 502, 903...Communication unit, 110, 220, 320, 51 0,910...memory unit, 111...management DB, 121...normal operation control unit, 122...robot linked operation control unit, 124,902...image processing unit, 125...allocation unit, 150, 150A, 150B...controller, 160...control room, 200...elevator cloud, 210...server (elevator control device), 213...judgment unit, 221...crowding level history data, 300...robot cloud, 310...server, 500, 500A, 500B, 500C...robot, 503...drive unit.

Claims

1. An elevator control device that controls the elevation of an elevator car installed in a building, in which an autonomous moving body that can autonomously move in the car and perform a predetermined task and a person can ride, an acquisition unit that acquires the congestion degree of the elevator; a determination unit that determines whether or not the autonomous moving body can be dispatched to the elevator based on the acquired congestion degree of the elevator; an instruction unit that, when it is determined that the autonomous moving body can be dispatched to the elevator, issues an instruction to move to the elevator to the autonomous moving body that has been determined to be capable of being dispatched; the autonomous moving body includes a security autonomous moving body for guarding a building, the acquisition unit acquires the number of users per unit time as the congestion degree from one or more image capture devices that are set in the building and connected to the elevator control device via a network, the determination unit determines to deploy the security autonomous moving body when the acquired total number of users is equal to or less than a first threshold; The autonomous moving body further includes a cleaning autonomous moving body for cleaning the inside of a building, The determination unit further determines to dispatch the cleaning autonomous moving body when the acquired total number of users is equal to or greater than a second threshold value that is greater than the first threshold value. Elevator control device.

2. An elevator control device that controls the raising and lowering of a car of an elevator that has a car installed in a building and can carry an autonomous mobile body that can move autonomously in the car and perform a predetermined task, and a person, an acquisition unit that acquires the congestion degree of the elevator; a determination unit that determines whether or not the autonomous moving body can be dispatched to the elevator based on the acquired congestion degree of the elevator; an instruction unit that, when it is determined that the autonomous moving body can be dispatched to the elevator, issues an instruction to move to the elevator to the autonomous moving body that has been determined to be capable of being dispatched; the autonomous moving body includes a security autonomous moving body for guarding a building, the acquisition unit is installed in the building corresponding to the elevator car, is connected to the elevator control device via a network, and acquires the number of floors reached by the elevator car per unit time from one or more control panels that control the elevator; the determination unit determines to deploy the security autonomous moving body when the acquired total number of landing locations is equal to or less than a third threshold; The autonomous moving body further includes a cleaning autonomous moving body for cleaning the inside of a building, The determination unit further determines to dispatch the cleaning autonomous moving body when the acquired total number of landing locations is equal to or smaller than a fourth threshold value that is greater than the third threshold value. Elevator control device.

3. the elevator control device is connected via a network to an autonomous mobile body server that is connected via a network to the autonomous mobile body and controls the autonomous mobile body; the instruction unit transmits a movement instruction to the elevator to the autonomous moving body via the autonomous moving body server; The elevator control device according to claim 1 .

4. An elevator control system comprising: an autonomous mobile body capable of moving autonomously; an elevator control device that controls the elevation and descent of a car of an elevator installed in a building, the car of which can carry the autonomous mobile body and a person; and an autonomous mobile body server that is connected to the elevator control device via a network and controls the autonomous mobile body, The elevator control device includes: an acquisition unit that acquires the congestion degree of the elevator; a determination unit that determines whether or not the autonomous moving body can be dispatched to the elevator based on the acquired congestion degree of the elevator; an instruction unit that, when it is determined that the autonomous moving body can be dispatched to the elevator, transmits to the autonomous moving body server an instruction to move the autonomous moving body that has been determined to be dispatchable to the elevator; The autonomous mobile object server When a movement instruction to the elevator is received from the elevator control device, the received movement instruction to the elevator is transmitted to an autonomous moving body that is determined to be able to be dispatched; The autonomous moving body is When receiving a command to move to the elevator, start moving to the elevator; the autonomous moving body includes a security autonomous moving body for guarding a building, the acquisition unit acquires the number of users per unit time as the congestion degree from one or more image capture devices that are set in the building and connected to the elevator control device via a network, the determination unit determines to deploy the security autonomous moving body when the acquired total number of users is equal to or less than a first threshold; The autonomous moving body further includes a cleaning autonomous moving body for cleaning the inside of a building, The determination unit further determines to dispatch the cleaning autonomous moving body when the acquired total number of users is equal to or greater than a second threshold value that is greater than the first threshold value. Elevator control system.

5. An elevator control system comprising: an autonomous mobile body capable of moving autonomously; an elevator control device that controls the raising and lowering of a car of an elevator installed in a building, the car of which can carry the autonomous mobile body and people; and an autonomous mobile body server that is connected to the elevator control device via a network and controls the autonomous mobile body, The elevator control device includes: an acquisition unit that acquires the congestion degree of the elevator; a determination unit that determines whether or not the autonomous moving body can be dispatched to the elevator based on the acquired congestion degree of the elevator; an instruction unit that, when it is determined that the autonomous moving body can be dispatched to the elevator, transmits to the autonomous moving body server an instruction to move the autonomous moving body that has been determined to be dispatchable to the elevator; The autonomous mobile object server When a movement instruction to the elevator is received from the elevator control device, the received movement instruction to the elevator is transmitted to an autonomous moving body that is determined to be able to be dispatched; The autonomous moving body is When receiving a command to move to the elevator, start moving to the elevator; the autonomous moving body includes a security autonomous moving body for guarding a building, the acquisition unit is installed in the building corresponding to the elevator car, is connected to the elevator control device via a network, and acquires the number of floors reached by the elevator car per unit time from one or more control panels that control the elevator; the determination unit determines to deploy the security autonomous moving body when the acquired total number of landing locations is equal to or less than a third threshold; The autonomous moving body further includes a cleaning autonomous moving body for cleaning the inside of a building, The determination unit further determines to dispatch the cleaning autonomous moving body when the acquired total number of landing locations is equal to or smaller than a fourth threshold value that is greater than the third threshold value. Elevator control system.

6. An elevator control method executed in an elevator control system including: an autonomous mobile body capable of moving autonomously; an elevator control device that controls the elevation and descent of a car of an elevator installed in a building, in which the autonomous mobile body and a person can ride; and an autonomous mobile body server that is connected to the elevator control device via a network and controls the autonomous mobile body, the autonomous moving bodies include a security autonomous moving body for guarding the inside of a building and a cleaning autonomous moving body for cleaning the inside of the building; The elevator control device acquires a congestion degree of the elevator; a step in which the elevator control device determines whether or not to dispatch the autonomous moving body to the elevator based on the acquired congestion degree of the elevator; When it is determined that the autonomous moving body can be dispatched to the elevator, the elevator control device transmits, to the autonomous moving body server, an instruction for the autonomous moving body that has been determined to be dispatched to move to the elevator; a step in which, when the autonomous mobile body server receives a movement instruction to the elevator from the elevator control device, the autonomous mobile body server transmits the received movement instruction to the elevator to an autonomous mobile body that is determined to be able to be dispatched; a step of starting movement of the autonomous moving body to the elevator when the autonomous moving body receives a movement instruction to the elevator; a step in which the elevator control device acquires, as the congestion degree, the number of users per unit time from one or more image capture devices that are set in the building and connected to the elevator control device via a network; a step of determining, by the elevator control device, to dispatch the security autonomous moving body when the acquired total number of users is equal to or less than a first threshold; a step in which the elevator control device determines to dispatch the autonomous moving body for cleaning when the acquired total number of users is equal to or greater than a second threshold value that is greater than the first threshold value; An elevator control method comprising:

7. An elevator control method executed in an elevator control system comprising: an autonomous mobile body capable of moving autonomously; an elevator control device that controls the raising and lowering of a car of an elevator installed in a building, the car of which can carry the autonomous mobile body and a person; and an autonomous mobile body server that is connected to the elevator control device via a network and controls the autonomous mobile body, the autonomous moving bodies include a security autonomous moving body for guarding the inside of a building and a cleaning autonomous moving body for cleaning the inside of the building; The elevator control device acquires a congestion degree of the elevator; a step in which the elevator control device determines whether or not to dispatch the autonomous moving body to the elevator based on the acquired congestion degree of the elevator; When it is determined that the autonomous moving body can be dispatched to the elevator, the elevator control device transmits, to the autonomous moving body server, an instruction for the autonomous moving body that has been determined to be dispatched to move to the elevator; a step in which, when the autonomous mobile body server receives a movement instruction to the elevator from the elevator control device, the autonomous mobile body server transmits the received movement instruction to the elevator to an autonomous mobile body that is determined to be able to be dispatched; a step of starting movement of the autonomous moving body to the elevator when the autonomous moving body receives a movement instruction to the elevator; The elevator control device is installed in the building corresponding to the elevator car, is connected to the elevator control device via a network, and acquires the number of floors that the elevator car reaches per unit time from one or more control panels that control the elevator; a step of determining, by the elevator control device, to dispatch the security autonomous moving body when the acquired total number of landing floors is equal to or less than a third threshold; a step in which the elevator control device determines to dispatch the autonomous moving body for cleaning when the acquired total number of landing floors is equal to or less than a fourth threshold value that is greater than the third threshold value; An elevator control method comprising:

Images