Control device, mobile body, control system, and control method

Abstract

In order to improve throughput in an environment where a plurality of moving bodies are operating, the present invention comprises: group setting units (102a, 102b) that set groups of a plurality of moving bodies M on the basis of positions and destinations of the moving bodies M; and movement rule setting units (103a, 103b) that set, for the moving bodies M belonging to a group set by the group setting units (102a, 102b), a movement rule (113) shared by the moving bodies M belonging to the group. The movement rule setting units (103a, 103b) set the movement rule (113) so that the moving bodies M belonging to the group move in the shared movement pattern.

Description

Control Device, Mobile Body, Control System, and Control Method

[0001] The present invention relates to the technology of a control device, a mobile body, a control system, and a control method.

[0002] With the expansion of the EC (Electronic Commerce) market, automation technology in the logistics field has been developing remarkably. In particular, many robots have been introduced for the automation of in-warehouse operations. On the other hand, in the logistics industry, a co-logistics method in which assets related to logistics transportation are shared among multiple shippers has begun to spread against the backdrop of a severe labor shortage. Therefore, in next-generation warehouses, automation technology and robot control technology that can be flexibly applied to dynamic changes such as various shippers, commodities, and quantities are required.

[0003] The conveyance method in a warehouse is roughly classified into conveyance by fixed facilities such as conveyors or conveyance by non-fixed facilities (hereinafter referred to as a conveyance system) such as AGVs and AMRs. AGV is an abbreviation for Automatic Guided Vehicle. Also, AMR is an abbreviation for Autonomous Mobile Robot. Even for movable facilities such as a conveyance device, conventionally, only a conveyance system of a specific vendor operates for each process / area in the warehouse. However, in the future, in order to flexibly respond to the above-described dynamic changes, it is expected to mix and operate conveyance systems of various vendors. Therefore, a cooperative control technology that enables the mixed operation of a conveyance system in which a plurality of vendors and a plurality of types of conveyance devices are operating in the same space becomes important.

[0004] Such cooperative control technology has already been partly put into practical use. These achieve mixed operation by previously setting markers that can be commonly recognized by both conveyance systems and a path that can be commonly traveled. However, such operation requires a great deal of preliminary design work such as marker placement, path design, establishment of a common communication interface, and construction of a unified control server. Moreover, since the space where mixed operation is possible is also limited, there is room for improvement from the viewpoints of flexibility and productivity improvement.

[0005] Therefore, Patent Document 1 proposes a control technology that enables more efficient coordinated operation of multiple transport systems without relying on the aforementioned prior design. Patent Document 1 discloses a transport system, control method, and control device, stating that "because there is no mechanism for sharing information such as the travel plan of transport devices between multiple transport systems manufactured by different manufacturers, if a collision avoidance function is activated between a transport device belonging to the first transport system and a transport device belonging to the second transport system, the transport time will be longer than initially expected, and the transport efficiency will decrease. The transport system (1) includes a first transport device (11) used for work involving the transport of materials and a control device (12). The control device (12) includes a prediction unit (121) that predicts the travel status of a second transport device (21) used for the aforementioned work based on progress information representing the progress of the work, a determination unit (122) that determines the travel plan of the first transport device (11) according to the travel status of the second transport device (21) predicted by the prediction unit (121), and a control unit (123) that controls the first transport device (11) based on the travel plan."

[0006] International Publication No. 2021 / 229746

[0007] The integrated management system shown in Patent Document 1 is a mechanism that takes the destination and immediate planned route of a group of transport devices under the management of the second (or first) transport system as input, and sequentially replans the route of any transport device (one transport device) under the management of the first (or second) transport system based on a predicted long-term action plan.

[0008] In other words, the technology described in Patent Document 1 is set up as a problem of resolving the coordination of actions between a self-conveying device (one conveying device) and another group of conveying devices (multiple conveying devices). In this case, depending on the number and density of conveying devices, the number of mediations may increase, causing each conveying device to slow down or stop to take a detour, leading to a decrease in productivity. As an example, consider a case where two groups of conveying devices, such as a group of conveying devices from one direction and a group of conveying devices from the second conveying system from another direction, pass each other in a somewhat coordinated manner. In this case, it is conceivable that a single mediation resolution based on any conveying device may propagate to create mediation points between other conveying devices, resulting in the separation of both groups of conveying devices that were moving as a "certain group," forcing a large number of conveying devices to take a detour.

[0009] Considering these examples, the integrated management system proposed in Patent Document 1 has room for improvement from the perspective of overall optimization (efficiency). Furthermore, it is conceivable that the frequency of deadlock situations, where specific transport devices become locked together and continuous operation becomes impossible, may increase due to the increase in the number and density of the transport devices mentioned above. In addition, the increase in the number of arbitrations may increase the computational load on the integrated management system. Therefore, Patent Document 1 has room for improvement not only in terms of overall system productivity but also in terms of system availability and computational load. These issues are not limited to environments where multiple types of transport devices (mobile bodies) or transport devices from multiple vendors are mixed, but are also true in environments where multiple transport devices (mobile bodies) of a single type are in operation.

[0010] In light of this background, the present invention was made, and the objective of the present invention is to improve throughput in environments where multiple mobile objects are in operation.

[0011] To solve the aforementioned problems, the present invention comprises a group setting unit that sets up groups of moving bodies based on the positions and destinations of each of the multiple moving bodies, and a movement rule setting unit that sets common movement rules for the moving bodies belonging to the groups set up by the group setting unit, wherein the movement rule setting unit sets the movement rules so that the moving bodies belonging to the groups move in a common movement pattern. Other solutions will be described as appropriate in the embodiments.

[0012] According to the present invention, it is possible to improve throughput in environments where multiple mobile objects are in operation.

[0013] This figure shows an example of the configuration of the functional blocks of the control system according to this embodiment. This figure shows an example of the operating environment of the control system in a warehouse or factory assumed in this embodiment. This figure shows an overview of the AGV driving environment. This is a conceptual diagram of block control and mutual exclusion control performed in the AGV system. This figure shows an overview of the AGF driving environment. This is a conceptual diagram of the AGV used in this embodiment. This is a functional block diagram of the AGV. This is a conceptual diagram of the AGF used in this embodiment. This is a functional block diagram of the AGF. This figure shows an example of the configuration of the functional blocks of the AGV system. This figure shows an example of the configuration of the functional blocks of the AGF system. This is a conceptual diagram showing an example of group formation. This is a conceptual diagram showing an example of group release processing. This is a diagram (1) showing a specific example of a movement rule. This is a diagram (2) showing a specific example of a movement rule. This is a diagram (3) showing a specific example of a movement rule. This is a diagram (4) showing a specific example of a movement rule. This is a diagram (5) showing a specific example of a movement rule. This is a diagram (6) showing a specific example of a movement rule. This is a flowchart (1) showing the procedure of the control method according to this embodiment. This is a flowchart (2) showing the procedure of the control method according to this embodiment. This is a flowchart (part 3) showing the procedure of the control method according to this embodiment. This is a diagram showing an example of an AGV with a built-in control device. This is a diagram showing an example of an AGF with a built-in control device. This is a diagram showing the hardware configuration of the computer.

[0014] Next, embodiments for carrying out the present invention (hereinafter referred to as "embodiments") will be described in detail with reference to the drawings as appropriate.

[0015] The embodiments of the present invention will be described in detail below with reference to Figures 1 to 25. In this embodiment, the description will focus on inter-process transportation within a warehouse or factory as an example.

[0016] <Control System Z> Figure 1 shows an example of the configuration of the functional blocks of the control system Z according to this embodiment.

[0017] The control system Z consists of a control device 1, a mobile body control device 40a, a mobile body control device 40b, an AGV 2, and an AGF 3.

[0018] <AGV2> AGV2 comprises an on-board controller 210 and a drive unit 220. The on-board controller 210 transmits control commands to the drive unit 220 according to the route 711 (see Figure 3) received from the mobile control device 40a. As a result, AGV2 moves according to the route 711. Further details of AGV2 will be described later. Note that "AGV" is an abbreviation for Automatic Guided Vehicle.

[0019] <AGF3> The AGF3 comprises an on-board controller 310 and a drive unit 320. The on-board controller 310 transmits control commands to the drive unit 320 according to the route 712 (see Figure 5) received from the mobile control device 40b. As a result, the AGF3 moves according to the route 712. Further details of the AGF3 will be described later. Note that "AGF" is an abbreviation for Automated Guided Forklift.

[0020] <Control Device 1> The control device 1 controls multiple mobile bodies M and includes an AGV position / state aggregation unit 101a (AGF position / state aggregation unit 101b) and a group setting unit 102a (group setting unit 102b). The control device 1 also includes a movement rule setting unit 103a (movement rule setting unit 103b) and a communication unit 104. Thus, in this embodiment, prioritizing ease of explanation, the control device 1 has a configuration for AGV2 and a configuration for AGF3. In other words, the control device 1 is provided with a configuration for AGV2 consisting of the AGV position / state aggregation unit 101a to the movement rule setting unit 103a. The control device 1 is also provided with a configuration for AGF3 consisting of the AGF position / state aggregation unit 101b to the movement rule setting unit 103b. However, this embodiment is not limited to this, and the functions for AGV2 and AGF3 may be common, that is, the configurations for AGV2 and AGF3 may not be distinguished and may be provided in the control device 1. In this embodiment, AGV2 and AGF3 are collectively referred to as mobile unit M as appropriate.

[0021] The following sections will mainly describe the overview of the AGV position / state aggregation unit 101a to the movement rule setting unit 103a. Details of the processing performed by the AGV position / state aggregation unit 101a to the movement rule setting unit 103a will be described later. Furthermore, the AGF position / state aggregation unit 101b to the movement rule setting unit 103b are the same as the AGV position / state aggregation unit 101a to the movement rule setting unit 103a except for processing AGF3, so their explanation will be omitted.

[0022] (AGV position / state aggregation unit 101a) The AGV position / state aggregation unit 101a receives the current position (position and orientation) and current destination 720 (see Figure 3) of each AGV 2 from the mobile control device 40a via the communication unit 104, and updates the past information. The AGF position / state aggregation unit 101b performs the same processing for the AGF 3.

[0023] (Group setting unit 102a) The group setting unit 102a groups together multiple AGVs 2 that are located in close proximity and moving in the same direction into a single group 800 (see Figure 12) (clustering). In this way, the group setting unit 102a sets up groups 800 of multiple mobile bodies M based on the respective positions and destinations 720 of each mobile body M. Setting up groups 800 includes forming groups 800 and canceling groups 800. Details of forming groups 800 and canceling groups 800 will be described later. At this time, the group setting unit 102a sets the maximum number of mobile bodies M managed by one group 800 by the maximum number of mobile bodies 112a (maximum number of mobile bodies 112). In other words, the group setting unit 102a can also form groups 800 according to the maximum number of mobile bodies 112a. Furthermore, if multiple types of mobile bodies M are present, the group setting unit 102a assigns mobile bodies M of the same type to the same group 800.

[0024] Furthermore, if a mobile body M that satisfies a pre-set release condition 111a (release condition 111) exists in the group 800, the group setting unit 102a releases the mobile body M that satisfies the release condition 111a from the group 800. Details of the release condition 111a will be described later.

[0025] (Movement rule setting unit 103a)

[0026] The movement rule setting unit 103a sets a common movement rule 113a (movement rule 113) for each of the AGV2s that have been grouped into the same group 800 (see Figure 12) as a result of the group formation of the AGV2s. The movement rule setting unit 103a sets the movement rule 113a common to the mobile bodies M belonging to the group 800 formed by the group setting unit 102a for the mobile bodies M belonging to the group 800. At this time, the movement rule setting unit 103a sets the movement rule 113a so that the mobile bodies M belonging to the group 800 move in a common movement pattern. Details of the movement rule 113a will be described later.

[0027] <Mobile Vehicle Control Device 40a> The mobile vehicle control device 40a controls a group of multiple mobile vehicles M, which are AGVs 2, based on the movement rules 113a set by the movement rule setting unit 103a. The mobile vehicle control device 40a includes a communication unit 408a and a destination setting unit 405a. The mobile vehicle control device 40a communicates with the control device 1 and the AGVs 2 via the communication unit 408a, and the destination setting unit 405a sets the destination 720 (see Figure 3) for the AGVs 2. Then, the mobile vehicle control device 40a generates a route 711 (see Figure 3) for each AGV 2 based on the set destination 720. Details of the mobile vehicle control device 40a will be described later.

[0028] <Mobile Unit Control Device 40b> The mobile unit control device 40b controls the AGF3, which are a group of multiple mobile units M, based on the movement rule 113b set by the movement rule setting unit 103b. The mobile unit control device 40b includes a communication unit 408b and a destination setting unit 405b. The mobile unit control device 40b communicates with the control device 1 and the AGF3 via the communication unit 408b, and the destination setting unit 405b sets the destination 720 (see Figure 5) for the AGF3. Then, the mobile unit control device 40b generates a route 712 (see Figure 5) for each AGF3 based on the set destination 720. Details of the mobile unit control device 40b will be described later.

[0029] Next, before describing the distinctive features of this embodiment, we will explain the underlying technology of this embodiment with reference to Figures 2 to 11.

[0030] <Operating Environment 5> Figure 2 shows an example of the operating environment 5 of the control system Z in a warehouse or factory as assumed in this embodiment.

[0031] In this embodiment, as described in the background art, it is assumed that multiple AGV2s and AGF3s are operated together in the same space. In this embodiment, "different types" refers to AGV2s and AGF3s. In this embodiment, a differential two-wheel type AGV2 is used as one form of transport operation. However, the form of AGV2 is not limited to this, and a drive configuration such as an AGV2 equipped with Mecanum wheels that can move in all directions may be used. In addition, in this embodiment, an AGF3 is also used as a transport configuration different from that of AGV2s. Compared to AGV2s, AGF3s have a larger vehicle shape and can transport a larger amount of cargo 503 at once. AGF3s are configured to transport cargo 503 placed on a pallet 501. Thus, in this embodiment, an operating environment 5 is assumed in which two types of mobile vehicles M, AGV2s and AGF3s, are operated together.

[0032] In this embodiment, it is assumed that multiple types of mobile devices M with different applications, such as AGV2 and AGF3, are in operation together. In other words, "multiple types" refers to multiple types of applications. However, for example, in an operating environment 5 where only AGV2 is in operation, multiple types of mobile devices M may be in operation by operating AGV2 with different driving performance. Alternatively, multiple types of mobile devices M may be in operation by operating AGV2 from different vendors. That is, "multiple types" may refer to multiple types of device specifications.

[0033] In operating environment 5, the process of appropriately transporting a collection of goods 503 received from a transport truck 51 to storage shelves 521 in the warehouse is shown. At this time, the received goods 503 are placed on a pallet 501 as a collection of goods 502, such as several cardboard boxes, by worker P. In this embodiment, the collection of goods 502 refers to goods 503 stored in cardboard boxes that are then placed in a larger cardboard box. The collection of goods 502 is transported by AGF3 along with the pallet 501 to the temporary storage area 511.

[0034] Subsequently, in the temporary storage area 511, worker P performs inspection work and, if necessary, separates the combined shipment 502 on the pallet 501 into individual shipments 503 (each cardboard box, etc.). The individual shipments 503 are transported to the storage rack 521 by the AGV 2 and placed and stored in appropriate sections of the storage rack 521 by worker P positioned around the storage rack 521. If it is not necessary to separate the combined shipment 502, efficiency can be improved by having the combined shipment 502, along with the pallet 501, transported together to the area around the storage rack 521 by the AGF 3. In this embodiment, such a work configuration is envisioned, and it is assumed that the transport of (separated) shipments 503 by the AGV 2 and the transport of the combined shipment 502 by the AGF 3 will be realized in the same space.

[0035] Furthermore, the area within the operating environment 5 where the storage shelves 521 are located will be appropriately referred to as the storage area 531.

[0036] For example, as shown in Figure 2, the destinations 720 of both AGV2 and AGF3 (see Figures 3 and 5) are concentrated around the grid 601 (node ​​611) (see Figure 3) of the storage area 531 and temporary storage area 511 of the operating environment 5. Therefore, the control device 1 considers, for example, AGV2 heading to the storage area 531 as candidates for the same group. Also, the control device 1 considers, for example, AGV2 heading to the temporary storage area 511 as candidates for the same group.

[0037] <AGV Driving Environment 6> Figure 3 is a diagram showing an overview of AGV driving environment 6. AGV driving environment 6 shows information related to the operation of AGV2 from the operating environment 5 shown in Figure 2.

[0038] In the AGV driving environment 6, the entire area of ​​the driving environment is divided by a grid 601 with rectangular (square) shapes. The center of the grid 601 is called a node 611, and the information connecting each node 611 is called a link 612. Then, a graph structure 610 consisting of nodes 611 and links 612 is created. In Figure 3, nodes 611 and links 612 (i.e., the graph structure 610) are shown in part of the AGV driving environment 6, but in reality, nodes and links 612 are set up throughout the entire area of ​​the driving environment. Based on this graph structure 610, a route 711 to the final destination 721 of AGV2 (node ​​611 of the final destination 721) is generated. The route 711 is generated by selecting nodes 611 and links 612. Note that the route 711, together with the route 712 of AGF3 shown in Figure 5, will be appropriately referred to as route 710. Furthermore, the final destination 721 will be appropriately referred to as destination 720 together with the final destination 721 and sub-goal 722 of AGF3, which will be described later in Figure 5.

[0039] (Block Control / Exclusion Control) Figure 4 is a conceptual diagram of the block control and exclusion control performed in the AGV system 4a (see Figure 10).

[0040] In the AGV system 4a, in order to avoid collisions and interference between AGVs 2, a function is provided to occupy a specific section of the route 711 to the final destination 721, and to prevent other vehicles from entering the occupied section. Such control is generally called block control or exclusive control. Block control and exclusive control are safety functions that operate independently of the generation of the route 711 (route generation). Hereafter, in this embodiment, it will be consistently referred to as block control.

[0041] In the example shown in FIG. 4, there are AGVs 2a and 2b, and the route 711 to the final destination 721a of AGV 2a and the route 711 to the final destination 721b by AGV 2b partially overlap. In contrast, AGV 2a blocks four grids 601a (grids 601 shown by grid-like hatching) among the grids 601 corresponding to the route 711 of AGV 2a. In contrast, AGV 2b is in a situation where it is only permitted to travel up to three grids 601b (grids 601 shown by horizontal line hatching) ahead. Grid 601a is the blocked area 631 of AGV 2a, and grid 601b is the blocked area 631 of AGV 2b. Thus, the blocked area 631 is an area exclusively occupied by the moving body M.

[0042] Also, in the example shown in FIG. 4, the grid 601c shown by the thick frame should be a common blocked area 63 for AGV 2a and AGV 2b, but in reality, it is assigned as the blocked area 631 of AGV 2a. This is because the blocked area 631 of AGV 2a was set earlier, or because the priority of AGV 2a is higher than that of AGV 2b. The reason why up to four grids 601 are set as the blocked area 631 is that the maximum blocked area length is set to "4".

[0043] The number (length) of the grids 601 in such a blocked area 631 greatly affects the productivity of the AGV system 4a. The length of the blocked area 631 needs to be appropriately set according to the performance of the movement control device 40a and the in-vehicle controller 210 shown in FIG. 1 and the number of AGVs 2. However, since the setting of the length of the blocked area 631 is not the main focus of this embodiment, the detailed design guidelines for the blocking control will not be described.

[0044] <AGF Travel Environment 7> FIG. 5 is a diagram showing an overview of the AGF travel environment 7. The AGF travel environment 7 shows information related to the travel of the AGF 3 in the operation environment 5 shown in FIG. 2.

[0045] In this embodiment, the AGF3 does not travel in sections delimited by the grid 601 like the AGV2, but can freely travel across the entire area of a specific region. The reason for the free-traveling form of the AGF3 is that the number of AGF3s is less than the number of AGV2s. The AGF3 may move based on the grid 601 (links 612 and nodes 611) shown in FIG. 3, or the AGV2 may have a free-traveling form like the AGF3 shown in FIG. 5.

[0046] More specifically, the path generation unit 406b (see FIG. 11) calculates the path 712 (composed of a time series of target position, attitude, and speed information) of each individual AGF3 using model predictive control. The path 712 may be a path from the current location of the AGF3 to the final destination 721. Alternatively, for reducing the calculation load, the path 712 may be a path from the current location of the AGF3 to an intermediate location (hereinafter referred to as a sub-goal 722). The final destination 721 is the position where the AGF3 finally arrives.

[0047] In this embodiment, the path generation unit 406b (see FIG. 11) sequentially optimizes the path 712 of the AGF3 by model predictive control so as not to interfere with other AGF3s and obstacles (not shown). At this time, the path generation unit 406b sequentially optimizes the path 712 using the paths 712 of other AGF3s and surrounding obstacle information as input information. Therefore, compared with the AGV system 4a, the AGF3 can travel to the destination 720 (final destination 721 or sub-goal 722) while avoiding other AGF3s and obstacles on a smoother path 712. The path generation by model predictive control will be only outlined in the path generation unit 406b of the movement control device 40b described later, but since the details of the process are well-known techniques, detailed description is omitted in this embodiment.

[0048] Next, referring to FIGS. 6 to 9, the configurations of the AGV2 and the AGF3 will be described.

[0049] (AGV2) FIG. 6 is a conceptual diagram of the AGV2 handled in this embodiment.

[0050] As shown in Figure 6, the AGV2 is driven by the drive wheels 21. In this embodiment, a differential two-wheel type AGV2 is used as an example. However, as mentioned above, it is not limited to this, and various drive types of AGV2 such as omni-wheel type and Mecanum wheel type may be used. Here, in the position information (x, y, θ) of the AGV2, "x" and "y" represent the x and y coordinates of the AGV2, respectively. Also, "θ" represents the orientation (direction) of the AGV2. In the diagram shown in Figure 6, "θ" is the axial angle of the AGV2 with respect to the X axis. The self-position calculation unit 215, which will be described later in Figure 7, calculates its own position by calculating the current values ​​of (x, y, θ).

[0051] (Functional block diagram of AGV2) Figure 7 is a functional block diagram of AGV2.

[0052] Each AGV2 is equipped with an on-board controller 210 and a drive unit 220 for performing control calculations. The on-board controller 210 includes a route management unit 211, an on-board sensor 212, a driving map management unit 213, a control command generation unit 214, a self-position calculation unit 215, and a communication unit 216. Of these, the communication unit 216 communicates with the mobile control device 40a shown in Figure 10. The drive unit 220 includes a drive unit 221 and an encoder 222. The outlines of each function are described below.

[0053] The route management unit 211 receives the route 711 (see Figure 3) generated by the mobile device control device 40a via the communication unit 216. As shown above in Figure 3, the route 711 consists of a collection of nodes 611 and links 612. The route management unit 211 receives the route 711 as it is sequentially updated from the mobile device control device 40a.

[0054] The on-board sensor 212 is an external sensor mounted on the AGV2. In this embodiment, as an example of the on-board sensor 212, a LiDAR is assumed to be mounted on the on-board controller 210. LiDAR is an abbreviation for Light Detection and Ranging. LiDAR is a sensor that uses laser light to measure the distance to objects in the irradiation range. However, AR tags or RFID tags may be installed on the road surface or the like, not limited to LiDAR. The on-board controller 210 may then read these tags with a dedicated sensor (not shown) to obtain the driving position and direction of the AGV2. AR is an abbreviation for Augmented Reality, and RFID is an abbreviation for Radio Frequency Identification.

[0055] The driving map management unit 213 manages a driving map (a different image map from the AGV driving environment 6 shown in Figure 3: not shown) that shows obstacle information in the aforementioned operating environment 5 (see Figure 2). The driving map is created in advance by SLAM before the start of operation, using measurement data of the AGV 2 during driving and input information of the distance traveled by the AGV 2. The measurement data of the AGV 2 during driving is acquired from the on-board sensor 212 (LiDAR in the example shown in this embodiment). The distance traveled information is obtained from the encoder 222 provided in the drive unit 220. Incidentally, SLAM is an abbreviation for Simultaneous Localization and Mapping. The creation of the driving map by SLAM is a known technology, so an explanation is omitted.

[0056] The self-position calculation unit 215 combines measurement data obtained from the on-board sensor 212 and encoder 222 to estimate the self-position of the AGV 2 relative to an arbitrary coordinate system on the driving map. The self-position is expressed as the position coordinates (coordinate values ​​x, y) and orientation θ of the AGV 2. Specifically, the self-position calculation unit 215 estimates the self-position using map matching technology. Since the self-position estimation technology using map matching is publicly known technology, a detailed explanation is omitted.

[0057] The control command generation unit 214 is a function that performs calculations related to the driving control of the AGV2. The control command generation unit 214 takes the path 711 and its own position as input information and performs calculations to determine the control command for the vehicle to follow the path 711. "The vehicle" refers to the mobile body M (AGV2, AGF3) itself, which is controlled by the onboard controller 210 or the onboard controller 310 shown in Figure 9. For example, the control command generation unit 214 sets the nearest node 611 relative to its own position, which constitutes the path 711, as the target node, and sequentially calculates the speed "v" and angular velocity "ω" to reach this target node. Specifically, the control command generation unit 214 determines the control command using methods such as the forward-looking model (Pure Pursuit method). Since such a method for determining control commands is publicly known, a detailed explanation is omitted.

[0058] The drive unit 221 converts the command values ​​(velocity "v" and angular velocity "ω") included in the control command input from the control command generation unit 214 into predetermined current values ​​in order to transmit power to the drive wheels 21 (see Figure 6) of the AGV2. The encoder 222 acquires the amount of rotation of the drive wheels 21 and estimates the distance traveled and the current speed of the AGV2. The encoder 222 then transmits the estimated values ​​(distance traveled and current speed) as response values ​​from the drive unit 221 to the self-position calculation unit 215.

[0059] The above is an overview of the functions of AGV2. Next, we will explain the configuration of AGF3, focusing only on the differences from AGV2.

[0060] (AGF3) Figure 8 is a conceptual diagram of AGF3 used in this embodiment.

[0061] The AGF3 used in this embodiment is a forklift consisting of fixed wheels 31 on the fork side and drive wheels 32 and driven wheels (casters) 33 on the bumper side, but it can also handle various other drive configurations. Here, the state variables of the AGF3 are expressed as (x, y, θ) in the same way as in the AGV2.

[0062] (Functional block diagram of AGF3) Figure 9 is a functional block diagram of AGF3.

[0063] Similar to the AGV2, the AGF3 is equipped with a drive unit 320 and an on-board controller 310 that performs control calculations for the drive unit 320. The following description will focus on the control command generation unit 314, which is unique to the AGF3. Other configurations are the same as those of the AGV2 and will therefore not be described.

[0064] (Control Command Generation Unit 314) In the AGF system 4b shown in Figure 11, the mobile control device 40b is characterized by calculating the path 712 (see Figure 5: time-series information of state variables (x, y, θ)) for each AGF 3. Therefore, the onboard controller 310 does not need to generate target control input information. The control command generation unit 314 then transmits the control input information (information on velocity "v" and angular velocity "ω") of the first step of the path 712 to the drive unit 321. In the AGF 3, since the path 712 is transmitted sequentially from the mobile control device 40b, only the first step of the path 712 is repeatedly transmitted to the drive unit 321.

[0065] The above describes the configuration of AGV2 and AGF3. Next, with reference to Figures 10 and 11, the configuration of the control functions (AGV system 4a and AGF system 4b) that manage AGV2 and AGF3 will be described.

[0066] (AGV system 4a) Figure 10 shows an example of the configuration of the functional blocks of the AGV system 4a.

[0067] In this embodiment, the AGV system 4a consists of a mobile control device 40a and a plurality of AGVs 2. As described above, the on-board controller 210 is provided in each AGV 2. The mobile control device 40a includes a position / state / performance storage unit 401a, a graph structure storage unit 402a, a blockage state storage unit 403a, and a blockage control unit 404a. Furthermore, the mobile control device 40a includes a destination setting unit 405a, a route generation unit 406a, a route determination unit 407a, and a communication unit 408a. Also, in Figures 10 and 11, the lines with arrows represent the flow of data. Hereafter, an overview of each functional block provided by the mobile control device 40a will be described based on the configuration example in Figure 10.

[0068] (Position, State, and Performance Storage Unit 401a) The position, state, and performance storage unit 401a stores the current position, attitude, current state, and basic information of the AGV2. The current state may include the remaining battery level of the AGV2 and the loading status (loaded or empty) of the load 503 (see Figure 2). This information is updated sequentially by receiving it from the on-board controller 210 installed in the AGV2 via the communication unit 408a. Specific examples of basic information include dimensions related to the shape of the AGV2, such as its width, length, height, and wheelbase. Furthermore, specific examples of basic information may include values ​​related to the AGV2's driving capabilities, such as the maximum (minimum) speed, maximum (minimum) angular velocity, and maximum (minimum) acceleration. The position, state, and performance storage unit 401a also manages the AGV2's maximum battery capacity and the maximum weight of the load 503 that can be transported. Furthermore, the position, state, and performance storage unit 401a also manages the maximum block section length, which will be handled by the block control unit 404a described later.

[0069] (Graph structure storage unit 402a) The graph structure storage unit 402a manages the graph structure 610 composed of nodes 611 and links 612 (see Figure 3 for the graph structure 610). Weights can be assigned to the links 612 as needed when the AGV2 passes through them. For example, each link 612 is assigned a weight, and the AGV2 preferentially moves in the direction of the link 612 with the greater weight. Furthermore, in the example shown in this embodiment, the grid 601 constituting the driving environment is square as shown in Figure 3, and there is no difference in travel distance in the forward, backward, and left-right directions of the AGV2. In other words, the length of the links 612 is the same in all directions.

[0070] In this embodiment, as an example, a weight of "1.0" is set for each of the links 612. Also in this embodiment, in the layout shown in Figure 3, the grid 601 corresponding to the storage area 531 and the temporary storage area 511 is set as the final destination 721. The AGV 2 then repeatedly performs the operation of traveling back and forth between the storage area 531 and the temporary storage area 511.

[0071] (Destination setting unit 405a) The destination setting unit 405a determines the destination 720 for each AGV2 based on the task information requested for the entire AGV system 4a. There is also a method of changing the order of destinations 720 to maximize productivity within a given time, according to the content of the tasks. However, since this method is not a core part of this embodiment, in this embodiment, tasks are assigned to the AGV2s in task waiting state in order from the top of the task group list. The task group is a collection of tasks that are input to the mobile control device 40a by the user. The destination 720 may be the position coordinates of the final destination 721 corresponding to the task, or it may be a sub-goal 722 which is an intermediate point (waypoint) between the current position and the final destination 721.

[0072] (Route Generation Unit 406a) The route generation unit 406a generates a route 711 (see Figure 3) from the current position of each AGV2 to the destination 720 in a unified manner. The route generation unit 406a generates the route 711 using the graph structure 610, the current position and current state of each AGV2, and the destination 720 (grid 601) as input information. The graph structure 610 is information managed by the graph structure storage unit 402a, and the current position and current state of each AGV2 are information managed by the position / state / performance storage unit 401a. The destination 720 (grid 601) is information output from the destination setting unit 405a.

[0073] There are many existing methods for route generation, such as Dijkstra's algorithm and the A* (A-star) algorithm. While a detailed explanation is omitted, this embodiment uses an algorithm based on the A* algorithm. The generated route 711 is represented as a set of links 612 through which the AGV2 passes, as described above. The AGV2 travels along these links 612 in order, guaranteeing arrival at the destination 720. The route 711 shown in Figure 3 is an example of a generated route 711. The generated route 711 is transmitted to the block control unit 404a.

[0074] (Blocking State Storage Unit 403a and Blocking Control Unit 404a) Details of the blocking control performed by the blocking control unit 404a are as described above in the explanation of blocking control using Figure 4. Based on the maximum blocking section length managed by the position, state, and performance storage unit 401a, the blocking control unit 404a calculates how far the route 711 generated by the route generation unit 406a can occupy. The maximum blocking section length is the maximum length of grid 601 that can be secured as a blocking area 631 (see Figure 4). The range in which it can travel changes each time depending on the blocking state of other AGVs 2, but the blocking control unit 404a is designed to always block the grid 601 corresponding to the current position in order to avoid collisions with other vehicles. The grid 601 corresponding to the current position is the grid 601 where the AGV 2 is located. In this way, the blocking control unit 404a sets the blocking area 631 based on the route 711.

[0075] The blockage state storage unit 403a manages which grid 601 each AGV2 is currently blocking (occupying) (blockage information). Since the blocked area 631 of the AGV2 changes moment by moment, the blockage information managed by the blockage state storage unit 403a is updated sequentially in conjunction with the input / output information of the path generation unit 406a and the blockage control unit 404a, which will be described later.

[0076] (Route determination unit 407a) The route 711 generated by the route generation unit 406a is sent to the blockage control unit 404a, where the blockage control unit 404a sets the blockage region 631. The route determination unit 407a transmits the route 711, which has been output after processing by the blockage control unit 404a, to the on-board controller 210 of each AGV2 via the communication unit 408a. The transmitted route 711 is acquired by the route management unit 211 provided in the on-board controller 210 of the AGV2.

[0077] (AGF System 4b) Figure 11 shows an example of the configuration of the functional blocks of the AGF System 4b.

[0078] In this embodiment, the AGF system 4b is composed of a mobile device control unit 40b and AGF3. As described above, the on-board controller 310 is provided in each AGF3. The configuration of the mobile device control unit 40b is generally the same as that of the mobile device control unit 40a. Hereafter, only the route generation unit 406b, route management unit 411, and control input determination unit 412, which are the differences in configuration from the mobile device control unit 40a, will be described. The configurations other than the route generation unit 406b, route management unit 411, and control input determination unit 412 are the same as those of the mobile device control unit 40a, so their description will be omitted.

[0079] (Route Generation Unit 406b) The route generation unit 406b uses model predictive control to determine a route 712 (see Figure 5) leading to the destination 720 set by the destination setting unit 405b. The route 712 is represented by a set (time series) of target positions (xt, yt, θt) for each arbitrary time step and target control inputs (vt, ωt) to realize these states. The route generation unit 406b uses a model that mathematically expresses the operating characteristics of the AGF3 drive unit 320 to generate a route 712, which is time-series information of optimal control inputs for reaching the target state (in this case, the destination) (model predictive control). At this time, the route generation unit 406b generates a route 712 that does not interfere with other AGF3s by adding the routes 712 of other AGF3s as non-interference regions as constraints for the optimization calculation by model predictive control. The routes 712 of other AGF3s are input from the route management unit 411, which will be described later. Regarding the details of model predictive control, since it is a publicly known technology, the details of the calculations will be omitted. The generated route 712 is transmitted to the route management unit 411 and the control input determination unit 412.

[0080] (Route Management Unit 411) The route management unit 411 aggregates and manages the routes 712 for each AGF3 that are generated by the route generation unit 406b. Since the processing performed by the route generation unit 406b is a periodically executed process, the routes 712 for each AGF3 are updated each time a route 712 is generated.

[0081] (Control Input Determination Unit 412) The control input determination unit 412 transmits the control input information for the first step in the route 712 generated by the route generation unit 406b to the in-vehicle controller 310 of the AGF3 that is the target of the route 712, via the communication unit 408b. The transmitted control input information is the velocity "vt" and angular velocity "ωt" information for the first step in the route 712.

[0082] The above is an overview of the AGV system 4a and AGF system 4b. The following describes the processing performed by the control system Z, which is the main focus of this embodiment.

[0083] <Objective of this embodiment> In an environment where multiple types of mobile vehicles M (AGV2 and AGF3 in this embodiment) coexist, the following phenomena may occur. For example, if the AGV system 4a and the AGF system 4b cannot understand (share) each other's precise control methods or the tracking accuracy of the route 710, it is necessary to predict the routes 710 of both systems to some extent and mediate their actions. The tracking accuracy changes depending on the arrival time to each destination 720 and the possibility of route changes.

[0084] When behavioral mediation involving prediction is performed, each AGV2 and AGF3 will take actions to avoid collisions, such as pausing or avoiding other mobile objects M. Therefore, depending on the number and density of mobile objects M, frequent deceleration and stopping for detours may occur, potentially leading to a decrease in overall productivity. Furthermore, it is possible that the resolution of one behavioral mediation may propagate, causing further mediation to be required at other locations. In addition, the computation time required for behavioral mediation may increase with the number of mobile objects M.

[0085] <Group 800> Next, the characteristic features of this embodiment will be described with reference to Figures 12 to 22. In this embodiment, group formation processing is performed in both AGV2 and AGF3, but in Figures 12 to 19, unless otherwise noted, the explanation will primarily focus on AGF3 for the sake of clarity. The processing of group 800 in AGV2 is the same as in AGF3.

[0086] Figure 12 is a conceptual diagram illustrating an example of group formation. Refer to Figure 1 as appropriate.

[0087] In Figure 12, AGF3a and AGF3b, which are in close proximity to each other and traveling toward the storage area 531 (see Figure 2), are grouped together as the same group 801 (group 800). Also in Figure 12, AGF3c and AGF3d, which are in close proximity to each other and traveling toward the temporary storage area 511 (see Figure 2), are grouped together as the same group 802 (group 800). As AGF3c and AGF3d continue traveling, they will approach AGF3e, which is traveling in the same direction. Therefore, the group setting unit 102b updates group 800 to group 803 (group 800), which includes AGF3e, in a process several steps (several seconds) ahead. In this embodiment, once a group of mobile bodies M is formed, it will maintain the same group 800 unless it falls under the conditions for group dissociation shown below.

[0088] While various grouping logics (clustering logics) are possible, in this embodiment, grouping is performed based on the location of the AGF3 and its proximity to the destination 720. Based on proximity to the destination 720 means that AGF3s heading toward adjacent destinations 720 are added to the same group 800. Specifically, the group setting unit 102b performs the following two types of calculations and assigns the same group ID to AGF3s that are set as group candidates in both calculations.

[0089] (A1) Proximity of AGF3 locations: The group setting unit 102b takes the current location of each AGF3 as input information and designates AGF3s whose distance from each other is within a specific threshold as candidates for the same group. The specific threshold is, for example, 5m. The current location of each AGF3 is acquired by the AGF location / state aggregation unit 101b.

[0090] (A2) Proximity of destination 720: The group setting unit 102b groups the AGF3 based on the location of the destination 720 of each AGF3. In this case, the group setting unit 102a considers the AGF3 to be the same group candidate if the distance between the respective target locations is within a certain threshold or if they are located in the same area. The location of the destination 720 of the AGF3 is acquired by the AGF location / state aggregation unit 101b.

[0091] Furthermore, since there are no other AGF3s that satisfy the conditions (A1) and (A2) described above, AGF3f to 3h are individually formed into groups 804 to 806 (group 800).

[0092] The occlusion region 631 of group 800 (see Figure 4) will be described later, but the type of occlusion region 631 can be arbitrarily set in advance by the user.

[0093] Furthermore, if a large number of mobile bodies M (AGF3 in the example of Figure 12) are managed and formed as a single group 800, one group 800 (a collection of mobile bodies M) will occupy a large blockage area 631. As a result, other mobile bodies M may be forced to take excessive detours. Therefore, the maximum number of mobile bodies M managed by one group 800 may be set by the maximum number of mobile bodies 112b shown in Figure 1. By setting the maximum number of mobile bodies 112b, it is possible to prevent one group 800 from becoming excessively large, and to prevent other mobile bodies M from being forced to take excessive detours.

[0094] <Group Disconnection> The movement rule setting unit 103b assigns common or adjacent destinations 720 (see Figure 5) to all moving objects M (AGF3 in the example shown in Figure 12) belonging to the same group 800. As a result, the moving objects M belonging to the same group 800 travel in the same direction and in close proximity to each other. On the other hand, each moving object M will eventually reach a different destination 720. Therefore, at some point it is necessary to disconnect the group 800 and assign each moving object M a destination 720. In this embodiment, when the position of any one of the moving objects M belonging to the same group 800 becomes within a predetermined distance (for example, 3 m) of the destination 720, the group setting unit 102b disconnects the group 800.

[0095] Figure 13 is a conceptual diagram showing an example of a group ungrouping process.

[0096] In the example shown in Figure 13, group 800 has a common final destination 721, and AGF3A and AGF3B, which are moving in parallel toward the common final destination 721, belong to this group. After passing the sub-goal 722, when AGF3A and AGF3B approach a certain distance from their respective final destinations 721A and 721B, the group setting unit 102b releases group 800. That is, if the moving bodies M (AGF3A, 3B) are within a predetermined range from the destination 720, the group setting unit 102b determines that the release condition 111 is met and releases group 800. As a result, AGF3A and 3B move toward their respective final destinations 721A and 721B. At this time, the movement rule setting unit 103b switches the control of the moving bodies M, which have been released from group 800, from following the common movement rule 113 to controlling each individual moving body M. This allows each mobile unit M (AGF3 in the example shown in Figure 13) to reach the correct destination 720. The release condition 111b (release condition 111) shown in Figure 1 stores a predetermined distance to the destination 720 set in group 800.

[0097] In this way, the group setting unit 102b determines whether or not the pre-set release condition 111 is met based on the position of the moving object M. The group setting unit 102b then determines that the release condition 111 is met if the moving object M is within a predetermined range from the destination 720.

[0098] The above describes the group formation and degrouping performed by the group setting unit 102b. In this embodiment, the group setting unit 102a also performs the same processing for AGV2.

[0099] <Movement Rule 113> The movement rule setting unit 103b then sets a common movement rule 113 for the moving objects M that have been grouped into the same group 800 (see Figure 12) as a result of the group formation of the moving objects M. The following six specific examples of movement rules 113 are set.

[0100] (B1) Relative speed / velocity. In other words, the movement rule setting unit 103b sets a common running speed or a common relative speed as movement rule 113 (movement rule 113b) for the moving bodies M (AGF3) belonging to group 800. As a result, the moving bodies M belonging to the same group 800 move at roughly the same speed as each other, that is, at a small relative speed. This makes it possible for the moving bodies M belonging to the same group 800 to move without changing the size of group 800.

[0101] (B2) Direction. In other words, mobile objects M belonging to the same group 800 move in the same direction (clockwise, counterclockwise, etc.).

[0102] (B3) Sub-goal 722 (see Figure 5). In other words, the position coordinates of a common sub-goal 722 and the position coordinates of nearby sub-goals 722 are set for mobile bodies M belonging to the same group 800. Incidentally, it is also possible to set a sub-goal 722 for AGV2.

[0103] (B4) Final destination 721 (see Figure 5). In other words, the position coordinates of a common final destination 721, or the position coordinates of nearby final destinations 721, are set for mobile bodies M belonging to the same group 800.

[0104] (B3) and (B4) cause the movement rule setting unit 103b to set a common destination 720f (see Figure 17) or nearby destinations 720e, 720g (see Figure 17) for the moving bodies M (AGF3) belonging to group 800. That is, the movement rule setting unit 103b sets the common destination 720f, which is a common destination 720, as a common movement rule 113 (movement rule 113b). Alternatively, the movement rule setting unit 103b sets nearby destinations 720e, 720g, which are nearby destinations 720, as a common movement rule 113 for the moving bodies M belonging to group 800. As a result, each of the moving bodies M belonging to group 800 moves together in a common direction.

[0105] (B5) Blocked area 631 (see Figure 4). The movement rule setting unit 103b sets a blocked area 631 that includes a group of multiple moving bodies M. The movement rule setting unit 103b then sets the movement rule 113 (movement rule 113b) within the set blocked area 631 to the moving bodies M (AGF3) belonging to group 800. As a result, the control device 1 does not need to manage the blocked area 631 for each individual moving body M, thus reducing the computational load on the control device 1.

[0106] For AGV2, the closure area 631 is set based on the grid 601 shown in Figure 4. However, for AGF3, the closure area 631 is set without relying on the grid 601 by setting a predetermined movable area and an entry-restricted area (obstacle area).

[0107] (B6) Relative distance. In other words, the movement rule setting unit 103b sets the movement rule 113 so that the relative distance between the moving bodies M (AGF3) belonging to group 800 remains constant. As a result, the speed of each moving body M is set so that the moving bodies M belonging to the same group 800 travel as close together as possible without colliding with each other. As a result, the moving bodies M belonging to group 800 can move together without colliding with each other.

[0108] It should be noted that these movement rules 113b (movement rule 113) cannot always be set and depend on the control characteristics of the AGF system 4b (or AGV system 4a). For example, regarding (B4) the final destination 721 among the movement rules 113b described above, if it is set in advance by the mobile device control device 40b (mobile device control device 40a) and cannot be changed (updated) from the outside, it cannot be treated as movement rule 113b (movement rule 113a).

[0109] Furthermore, all of the aforementioned (B1) to (B6) may be set in group 800. Alternatively, the user may select any movement rule 113 from (B1) to (B6) according to the situation, and the selected movement rule 113 may be set in group 800. Alternatively, the movement rule setting unit 103b may set a specific movement rule 113 from (B1) to (B6) in group 800 according to the situation of the moving object M. For example, the movement rule 113 set may differ depending on the type of moving object M, such as only (B1) for AGV2 and (B3) + (B5) for AGF3. In such a case, the movement rule 113 set manually is selected. Alternatively, the movement rule 113 applied by the vendor of AGV2 or AGF3 may be selected. Alternatively, when a group is formed, only the movement rule 113 (B1) may be set for AGF3 that is close to the final destination 721, while (B1) to (B3) may be set for the others. In other cases, the movement rule 113 may be set dynamically according to the state of the moving body M.

[0110] When movement rule 113 is set, it means that movement rule 113 is set for each of the mobile units M (AGV2 and AGF3) belonging to group 800.

[0111] Figures 14 to 19 show specific examples of the movement rule 113 described above.

[0112] The conceptual diagrams shown in Figures 14 and 15 illustrate the conceptual diagrams of (B1) and (B6) of the aforementioned movement rules 113. Figure 14 shows the behavior of AGF3 immediately after grouping and before movement rules 113 are set. In the state shown in Figure 14, each AGF3 belonging to group 811 (group 800) is traveling at a different speed (velocity vectors 901, 902).

[0113] In contrast, Figure 15 shows a state in which movement rule 113b (movement rule 113) has been set for group 811 (group 800). In this case, the movement rule setting unit 103b causes the AGF3 belonging to group 811 to move as a single unit as possible. That is, the movement rule setting unit 103b unifies the speed (velocity vector 903) of each AGF3 belonging to group 811 and adjusts the speed to set the relative speed to 0. The movement rule setting unit 103b also sets movement rule 113b to maintain the relative distance 911 between moving bodies M belonging to group 800 at a constant interval.

[0114] In this way, the movement rule setting unit 103b sets a common running speed or a common relative speed as a movement rule 113 for each moving body M belonging to group 800, as shown by the velocity vector 903.

[0115] Figures 16 and 17 show conceptual diagrams of (B3) or (B4) of the aforementioned movement rule 113b. In Figures 16 and 17, groups 812 and 813 are shown to represent the differences in movement for each group 800.

[0116] Figure 16 shows the state immediately after grouping, before the movement rule 113 has been set. In addition, Figure 16 shows AGV2 in addition to AGF3 to explain how to set the destination 720.

[0117] In the state shown in Figure 16, each AGF3j,3k and AGV2j,2k moves toward a different destination 720 (destinations 720a to 720d in the example shown in Figure 16). In the example shown in Figure 16, AGV2j, belonging to group 812, is moving toward destination 720a, and AGV2k is moving toward destination 720b, which is close to destination 720a. Also, AGF3j, belonging to group 813, is moving toward destination 720c, and AGF3k is moving toward destination 720d.

[0118] However, as shown in Figure 17, after grouping, the movement rule setting unit 103a sets the destination 720 for each AGV2 so that the AGV2s belonging to the same group 800 travel as a single unit as much as possible. Similarly, the movement rule setting unit 103b sets the destination 720 for each AGF3 so that the AGF3s belonging to the same group 800 travel as a single unit as much as possible. Specifically, the movement rule setting units 103a and 103b set a common destination or a nearby destination 720 for the mobile bodies M belonging to the same group 800.

[0119] For example, as mentioned above, in group 812, AGV2j and 2k are grouped together. As shown in Figure 3, AGV2 moves based on a path 711 that is based on links 612 and nodes 611 set in grid 601. In other words, AGV2 can only move forward, backward, or left or right, and has a low degree of freedom in the direction of movement. If a common destination 720 is set for AGV2 that moves in this way, from the viewpoint of block control, it is expected that one of the AGV2s belonging to group 800 will decelerate or stop. In other words, if a common destination 720 is set for multiple AGV2s, it is expected that the AGV2s will decelerate or stop in order to avoid collisions between the AGV2s. For this reason, for AGV2, instead of a common destination 720 as shown in Figure 17, the destination 720 for each AGV2 is set in an adjacent grid 601. In the example shown in Figure 17, the movement rule setting unit 103a sets adjacent destinations 720e and 720g for each of the AGVs 2k and 2j, which are the nearby destinations 720. The adjacent destinations 720g and 720e are set in adjacent (nearby) grids 601. The control device 1 then instructs the mobile body control device 40a to update the path 712 of AGV 2j to head towards destination 720e. Similarly, the control device 1 instructs the mobile body control device 40a to update the path 712 of AGV 2k to head towards destination 720g. As a result, AGVs 2j and 2k move in a common direction (arrow A1).

[0120] On the other hand, as mentioned above, AGF3j and 3k are grouped into group 813. In this embodiment, route generation is performed for AGF3 using model predictive control. With such model predictive control, it is possible to adjust the behavior of AGF3 (speed, direction of movement, etc.) in accordance with the behavior of other AGF3. Therefore, with respect to AGF3, it is possible to set a common destination 720 for multiple AGF3, as shown in destination 720f in Figure 17. In other words, the movement rule setting unit 103b sets a common destination 720 for AGF3 belonging to the same group 800. By setting a common destination 720 for AGF3 belonging to the same group 800 in this way, AGF3 belonging to the same group 800 can travel in parallel with each other. In the example shown in Figure 17, common destination 720f is set as a common destination 720 for AGF3j and 3k belonging to the same group 800. Then, the control device 1 instructs the mobile body control device 40b to update the paths 712 of AGF3j and AGF3k so that they proceed towards the destination 720f. As a result, AGF3j and 3k move in a common direction (arrow A2).

[0121] Figures 18 and 19 show a conceptual diagram of (B5) the blocked area 631 (operable area, no-entry area (obstacle area)) of the movement rule 113.

[0122] Figure 18 shows the state immediately after grouping, before the movement rule 113 is set. Before the movement rule 113 is set, AGV2 belonging to group 814 and AGF3 belonging to group 815 are traveling with different occluded areas 631 set for each. However, after the movement rule 113 is set, AGV2 and AGF3 belonging to the same group 800 travel as a single unit as much as possible. Therefore, as shown in Figure 19, a common occluded area 631, i.e., occluded areas 631c and 631d that include the grouped multiple mobile bodies M are set for AGV2 and AGF3 belonging to group 800. As shown in Figure 19, the occluded area 631 is also an area that prevents other mobile bodies M from entering, and its shape may be rectangular as shown in occluded area 631c. Alternatively, a polygonal occluded area 631 may be set as shown in occluded area 631d. Alternatively, although not shown in Figure 19, an elliptical occluded area 631 may be set. For AGV2 and AGF3 belonging to such group 800, the blocking control unit 404a and the movement rule setting unit 103b set a common blocking region 631 for the moving body M belonging to group 800. Such setting is performed by a predetermined algorithm. For example, the blocking region 631c shown in Figure 19 is configured by combining the blocking regions 631 of the two AGV2 in Figure 18 and then matching the length in the direction of travel of the AGV2 and the length in the direction opposite to the direction of travel. Also, the blocking region 631d shown in Figure 19 is set to include a common destination 720 (destination 720f in Figure 17) for the two AGF3 and to include the paths 712 of the two AGF3.

[0123] However, a common occlusion region 631 may not be set for the mobile bodies M belonging to group 800, and the occlusion region 631 set for each individual mobile body M (AGV2, AGF3) may be used. For example, a common occlusion region 631 may not be set for AGV2, but a common occlusion region 631 may be set for AGF3. The occlusion control unit 404a and the movement rule setting unit 103b set an appropriate shape according to the region shape (rectangle or polygon) that can be set in the AGV system 4a or AGF system 4b. In this way, the occlusion control unit 404a and the movement rule setting unit 103b set occlusion regions 631c and 631d that include the grouped mobile bodies M.

[0124] In this embodiment, as shown in Figure 1, group control is performed on the AGF3 side (AGF position / state aggregation unit 101b to movement rule setting unit 103b). AGF3 (group 800) avoids AGV2 (group 800) by the obstacle detection and avoidance function of the mobile body control device 40b. In other words, AGF3 (group 800) avoids AGV2 (group 800) by considering AGV2 as an obstacle. The same applies to AGV2.

[0125] In this way, by setting the movement rules 113 (movement rules 113a, 113b), each of the moving objects M belonging to group 800 moves in a common movement pattern.

[0126] <Control Method> Figures 20 to 22 are flowcharts showing the procedure of the control method according to this embodiment.

[0127] In the control method shown in this embodiment, the movement rule 113 for group 800 is set to include common or adjacent subgoals 722 for AGV2 and AGF3 (B3). Note that the processing shown in Figures 20 to 22 is just one example, and any of the movement rules 113 (B1) to (B6) described above may be set. Furthermore, different movement rules 113 may be set for AGV2 and AGF3, respectively.

[0128] First, in step S101 of Figure 20, the AGV system 4a is started, and in step S102, the AGF system 4b is started. Furthermore, in step S103, the control device 1 is started. Note that the start-up order is not limited to steps S102 to S103; any order is acceptable.

[0129] Next, in step S111, the movement rule setting unit 103a determines which of the aforementioned movement rules 113a (B1) to (B6) to apply to the AGV2. As described above, in this embodiment, the movement rule 113a relating to subgoal 722 is applied. Similarly, in step S112, the movement rule setting unit 103b determines which of the aforementioned movement rules 113b (B1) to (B6) to apply to the AGF3. In this embodiment, the movement rule 113b relating to subgoal 722 is also set for the AGF3. Note that the order of processing in steps S111 and S112 is not limited to the order shown in Figure 20, and any order is acceptable. Also, the determination of the movement rules 113 in steps S111 and S112 may be done manually by the user. Alternatively, if a method for determining the movement rules 113 (such as (B1) to (B3) for AGV2 and (B4) to (B6) for AGF3) has been set in advance, the control device 1 may make the determination according to such a determination method.

[0130] Next, in step S121, the destination setting unit 405a of the mobile control device 40a acquires a task group for each AGV2. The task group is a collection of tasks (= destinations 720) and is set by the user via the input device (not shown) of the mobile control device 40a.

[0131] Similarly, in step S122, the destination setting unit 405b of the mobile control device 40b acquires a group of tasks for each AGF3. The processing in step S122 is the same as on the AGV2 side (step S121). Note that the processing order for steps S121 and S122 is not limited to the order shown in Figure 20, and can be any order.

[0132] The subsequent processing will be partially performed by the control device 1, but the processing will be executed for AGV2 and AGF3 respectively. The processing for AGV2 will be steps S201 to S233, and the processing for AGF3 will be steps S301 to S333. In this case, steps S301 to S333 may be executed after steps S201 to S233, or both processes may be executed in parallel at their respective cycles, like in multithreading.

[0133] Hereafter, "task standby state" and "driving state" are defined as expressions that indicate a state of the vehicle. "Task standby state" refers to the state in which the mobile vehicle M is stopped when the AGV system 4a or AGF system 4b is started or after the current task is completed (destination 720 has been reached) until the next task is received. "Driving state" refers to the state in which the mobile vehicle M is driving after receiving a task.

[0134] (Control on the AGV2 side) First, in step S201 of Figure 21, the AGV position / state aggregation unit 101a acquires the current position (initial position) of each AGV2. When the AGV system 4a starts operating, the drives 220 and the on-board controller 210 in the AGV2 also start operating. At that time, the AGV position / state aggregation unit 101a acquires the current position of each AGV2 by acquiring the calculation result of the self-position calculation unit 215 of the on-board controller 210.

[0135] Next, in step S202, the destination setting unit 405a sets a destination 720 for each AGV2. As described above, the destination 720 is stored as a task in the task group. In step S202, the destination setting unit 405a assigns tasks to the AGV2s from the task group acquired in step S121 in the order in which the tasks were registered. In this way, the destination setting unit 405a assigns the position coordinates of the destination 720 to be executed to the AGV2s. Basically, when the AGV system 4a is started, it is expected that all AGV2s are in a task waiting state. Therefore, the destination setting unit 405a first compares the current position (waiting position) of each AGV2 acquired in step S201 with the position of the destination 720. Then, the destination setting unit 405a assigns tasks to the AGV2s in order of proximity to the destination 720. In this flowchart, it is assumed that a sub-goal 722 is stored in each task, and that the sub-goal 722 is set in step S202.

[0136] Once all tasks, i.e., destinations 720 (subgoals 722), have been assigned to AGV2, the process moves to step S203. Note that once AGV2 reaches destination 720, it transitions to a waiting state to receive the next destination 720. Therefore, steps S202 to S233 are executed sequentially until all tasks in the task group are completed.

[0137] Next, in step S203, the destination setting unit 405a of the mobile device control device 40a determines whether or not all tasks in the task group have been completed.

[0138] If all tasks are completed (S203 → YES), the AGV system 4a terminates control.

[0139] If not all tasks are completed (S203 → NO), the control system Z proceeds to step S211. Not all tasks are completed if there are still executable tasks remaining, or if any of the AGV2s are in a driving state.

[0140] Then, in step S211, the control device 1 starts generating routes for each AGV2. The processes shown in steps S211 to S233 are processes that are executed at regular intervals.

[0141] Step S212 is a process performed by the AGV position / state aggregation unit 101a, and step S213 is a process performed by the mobile body control device 40a. Steps S221 and S222 are processes performed by the control device 1. Steps S231 and S232 are processes performed by the mobile body control device 40a and the on-board controller 210. Therefore, although Figure 21 is a flowchart showing the flow of processing, each process is executed by a different computer C (see Figure 25), so it is assumed that the calculation cycles will be different for each process. On the other hand, in this embodiment, for the sake of simplicity, all computers C are assumed to be executed at, for example, 10 Hz and in synchronization.

[0142] First, in step S212, the AGV position / state aggregation unit 101a acquires the current position of AGV2. The content of this process is the same as in step S201. The purpose of this process is to acquire the self-position coordinates updated by the operation of AGV2 according to the path generation described later (steps S231, S232).

[0143] Next, in step S213, the destination setting unit 405a of the mobile control device 40a determines whether or not there is an AGV2 that has reached the destination 720 (sub-goal 722 in this flowchart). The processing in step S213 is performed based on the self-position calculated by the self-position calculation unit 215. The determination result is sent to the control device 1. The destination 720 is the position coordinate determined in step S202. In this embodiment, as an example, if the distance between the position coordinate of the destination 720 and the AGV2 becomes 0.1m or less, the destination setting unit 405a determines that the vehicle has reached the destination 720.

[0144] If there is an AGV2 that has reached destination 720 (S213 → YES), the control system Z transitions the AGV2 that has reached destination 720 to a task standby state. Then, the control system Z proceeds back to step S202. The destination setting unit 405a then extracts the next task from the task group and sets the next destination 720 for the AGV2 in the task standby state. Note that an AGV2 that has transitioned to the task standby state does not need to be included in the group formation, route generation, and operation update processes from step S221 onward until it receives the next destination 720 and enters a driving state.

[0145] If no AGV2 has reached destination 720 (S213 → NO), the control system Z proceeds to step S221.

[0146] In step S221, the group setting unit 102a updates the group 800 of the AGV2s. Step S221 is the "group setting step". The group 800 is updated based on the destination 720 of each AGV2 set in step S202 and the current position of each AGV2 obtained in step S212. The group 800 update includes the formation and dissolution of groups 800. The formation or dissolution of groups 800 is as described in Figures 12 and 13. Specifically, the group 800 update includes the formation of a new group 800, as shown in group 803 in Figure 12, and the dissolution of groups of AGV2s that have reached the vicinity of the destination 720, as shown in Figure 13.

[0147] Next, in step S222, the movement rule setting unit 103a updates the movement rule 113a (movement rule 113) for the group 800 formed in step S221. Step S222 is the "movement rule setting step". Specifically, the movement rule setting unit 103a sets a common movement rule 113a for each of the AGV2s belonging to the group 800. Alternatively, the movement rule setting unit 103a removes the movement rule 113a for AGV2s that have been removed from the group 800. As mentioned above, in this flowchart, it is assumed that (B3), that is, the common subgoal 722, is set among the movement rules 113a. The setting of the movement rule 113a is as shown in Figures 16 and 17.

[0148] The configured movement rule 113a (the setting of the common sub-goal 722 in the example shown in this flowchart) is transmitted via the communication units 104 and 408a to the destination setting unit 405a of the mobile device control device 40a. Subsequently, the control system Z proceeds to step S231.

[0149] Next, in step S231, the route generation unit 406a of the mobile control device 40a generates routes for each AGV2 based on the destination 720 (sub-goal 722) set by the movement rule 113a. Prior to the processing in step S231, the destination setting unit 405a sets the destination 720 set based on the movement rule 113a as the new destination 720 for the AGV2. In this flowchart, destination 720 is the sub-goal 722. In step S231, the destination setting unit 405a generates a new route 711 based on the set destination 720. As a result, route 711 is updated to route 711 based on the movement rule 113a. Details of route generation are as described above in Figure 10.

[0150] The generated route 711 is transmitted via the communication units 408a and 216 to the route management unit 211 of the AGV2's onboard controller 210. The control system Z then proceeds to step S232.

[0151] Next, in step S232, the control command generation unit 214 of the in-vehicle controller 210 executes the movement based on the updated route 711. Details of step S232 are as shown in the control command generation unit 214 in Figure 7.

[0152] This completes the route generation for each AGV2 (S233). Thereafter, the control system Z repeatedly executes steps S211 to S233 until all AGV2s reach their respective destinations.

[0153] (Control on the AGF3 side: Steps S301 to S333 in Figure 22) The control on the AGF3 side is the same as the control process on the AGV2 side described above (S201 to S233 in Figure 21), so the explanation is omitted.

[0154] Furthermore, in step S203 in Figure 21 and step S303 in Figure 22, if all tasks of both AGV2 and AGF3 are completed, the control system Z terminates the overall processing.

[0155] The above describes the contents of the control system Z proposed in this embodiment for use in an environment where different types of mobile bodies M are operated together.

[0156] <Modified Example> Next, with reference to Figures 23 and 25, an example of a mobile body M incorporating the control device 1 is shown.

[0157] Figure 23 shows an example of an AGV2Z with a built-in control device 1.

[0158] The AGV2Z comprises a control device 1, a mobile body control device 40a, an on-board controller 210, and a drive device 220. The control device 1 has the functions of the control device 1 shown in Figure 1, and the mobile body control device 40a has the functions of the mobile body control device 40a shown in Figure 10. The control device 1 shown in Figure 23 may be one of the control devices 1 shown in Figure 1 that has the functions of the AGV position / state aggregation unit 101a to the movement rule setting unit 103a. In this way, the AGV2Z incorporates the control device 1, and the control device 1 controls the AGV2Z, which is the mobile body M, based on the set movement rule 113a.

[0159] Such an AGV2Z functions as a command center for other AGV2s.

[0160] Figure 24 shows an example of an AGF3Z with a built-in control device 1.

[0161] The AGF3Z comprises a control device 1, a mobile body control device 40b, an on-board controller 310, and a drive device 320. The control device 1 has the functions of the control device 1 shown in Figure 1, and the mobile body control device 40b has the functions of the mobile body control device 40b shown in Figure 11. The control device 1 shown in Figure 24 may have the functions of the AGF position / state aggregation unit 101b to the movement rule setting unit 103b of the control device 1 shown in Figure 1. In this way, the AGF3Z incorporates the control device 1, and the control device 1 controls the AGV3Z, which is the mobile body M, based on the set movement rule 113b.

[0162] Such an AGF3Z functions as a command center for other AGF3s.

[0163] <Hardware Configuration> Figure 25 shows the hardware configuration of computer C. Computer C consists of control unit 1, mobile device control unit 40a, mobile device control unit 40b, and in-vehicle controllers 210 and 310.

[0164] Computer C includes memory D1, arithmetic unit D2, storage device D3, communication device D4, etc. Memory D1 is composed of RAM, etc. Arithmetic unit D2 is composed of CPU, GPU, etc. Storage device D3 is composed of HDD, SSD, ROM, etc. RAM is an abbreviation for Random Access Unit, CPU is an abbreviation for Central Processing Unit, and GPU is an abbreviation for Graphic Processing Unit. Similarly, HDD is an abbreviation for Hard Disk Drive, SSD is an abbreviation for Solid State Drive, and ROM is an abbreviation for Read Only Memory.

[0165] When computer C is control unit 1, mobile device control unit 40a, and mobile device control unit 40b, the storage device D3 is often an HDD or SSD. When computer C is an in-vehicle controller 210 or 310, the storage device D3 is often a ROM.

[0166] The communication device D4 corresponds to the communication unit 104 in Figure 1, the communication unit 216 in Figure 7, the communication unit 316 in Figure 9, the communication unit 408a in Figure 10, and the communication unit 408b in Figure 11.

[0167] Then, the program stored in the storage device D3 is loaded into memory D1, and the loaded program is executed by the arithmetic unit D2. This brings into practice the AGV position / state aggregation unit 101a to the movement rule setting units 103a and 103b shown in Figure 1. Similarly, the route management unit 211, the driving map management unit 213 to the self-position calculation unit 215 shown in Figure 7, and the map information management unit 313 to the self-position calculation unit 315 shown in Figure 9 are brought into practice. Furthermore, the block control unit 404a to the route determination unit 407a shown in Figure 10, and the destination setting unit 405b to the control input determination unit 412 shown in Figure 11 are brought into practice.

[0168] <Effects> In this embodiment, in an environment where multiple types of mobile bodies M are present, the control device 1 groups the mobile bodies M that are in the vicinity of it. A common movement rule 113 is then set for each mobile body M belonging to the same group 800 (see Figure 12). As a result of setting the movement rule 113 for each of the grouped mobile bodies M, the mobile bodies M belonging to group 800 can move together to a certain extent.

[0169] This allows multiple mobile objects M moving in the same direction to move together to a certain extent. This reduces the number of mediations with other mobile objects M, improving productivity and availability in environments where multiple types of mobile objects M coexist, while enabling cooperative control that reduces the computational load associated with action mediation, thereby improving throughput.

[0170] Thus, according to this embodiment, the number of decelerations and stops associated with the aforementioned behavioral mediation can be reduced, contributing to improved throughput, productivity, and availability. Furthermore, by grouping, multiple vehicles are mediated as a single unit, thus reducing the computational load. In other words, even when many moving objects M pass each other in a group, the number of behavioral mediations can be reduced, and the frequency of deadlock situations can be decreased.

[0171] These effects can also be achieved when the technology of this embodiment is applied to operating environments 5 in which different types of mobile devices M are not mixed, such as an operating environment 5 with only AGV2 or an operating environment 5 with only AGF3.

[0172] Furthermore, while the mobile units M belong to group 800, each mobile unit M cannot reach its original destination 720. In this embodiment, by releasing the mobile units M from group 800, each mobile unit M becomes able to reach its destination 720.

[0173] In this embodiment, two types of mobile devices M, AGV2 and AGF3, are used in a mixed operation. However, this embodiment is not limited to this configuration and can also be applied to environments where three or more types of mobile devices M are used in a mixed operation.

[0174] Furthermore, while this embodiment focuses on a mobile unit M intended for inter-process transport within a warehouse or factory, it is not limited to this, and could also be a control system Z in which multiple mobile units M are in operation. For example, the mobile unit M could be a cleaning robot, an agricultural robot, or the like.

[0175] Furthermore, in this embodiment, different types of mobile vehicles M, such as AGV2 and AGF3, are in mixed operation. However, as mentioned above, by grouping by vendor, for example, this embodiment can also be applied to environments where a single mobile vehicle M is in operation. In this case, "multiple types" refers to the types of vendors.

[0176] In this embodiment, AGV2s are grouped together in a group 800, and AGF3s are grouped together in a group 800. In other words, an operating environment 5 is assumed in which multiple types of mobile bodies M are mixed together. The group setting units 102a and 102b process mobile bodies M of the same type to belong to the same group 800. However, if the conditions are met, AGV2s and AGF3s may be mixed in a single group 800. However, by forming groups 800 with the same type of mobile body M, or with mobile bodies M from the same vendor, it is possible to form groups 800 that take into account differences in the driving performance of the mobile bodies M. This makes it possible to suppress differences in driving performance among mobile bodies M with different driving performance differences within a group 800.

[0177] Furthermore, in this embodiment, the control device 1 performs group control on the AGV2 side (AGV position / state aggregation unit 101a to movement rule setting unit 103a). Similarly, on the AGF3 side, group control is performed on the AGF3 side (AGF position / state aggregation unit 101b to movement rule setting unit 103b). For example, AGV2 (group 800) avoids AGF3 (group 800) by considering AGF3 as an obstacle. Similarly, AGF3 (group 800) avoids AGV2 (group 800) by considering AGV2 as an obstacle.

[0178] However, the AGV2 may also have location information, route information, and information about the blocked area 631 of the AGF3. The group setting unit 102a and the movement rule setting unit 103a may form groups 800 or set movement rules 113a considering the route 712 and blocked area 631 of the AGF3. Similarly, the group setting unit 102b and the movement rule setting unit 103b may form groups 800 or set movement rules 113b considering the route 711 and blocked area 631 of the AGV2.

[0179] Furthermore, there are cases where the release condition 111 is not set in advance. For example, if a group of mobile units M all have the same final destination 721 and travel in a chain-like manner, the group 800 may be released after each mobile unit M reaches its destination in order to proceed to the next destination 720. In addition, the condition for releasing the group 800 may be dynamically changed depending on the distance between the final destinations 721 of each group of mobile units M. Therefore, the release condition 111 may or may not be set in advance. Furthermore, the movement rule setting units 103a and 103b may provide a common destination 720 within the blocked area 631.

[0180] The present invention is not limited to the embodiments described above, and various modifications are included. For example, the embodiments described above are described in detail to illustrate the present invention clearly, and are not necessarily limited to those having all the configurations described.

[0181] Furthermore, some or all of the above-mentioned configurations, functions, storage devices D3, etc., may be implemented in hardware, for example by designing them as integrated circuits. Similarly, some or all of the AGV position / state aggregation units 101a to movement rule setting units 103a, etc., may be implemented in hardware, for example by designing them as integrated circuits. And some or all of the AGF position / state aggregation units 101b to movement rule setting units 103b, etc., may be implemented in hardware, for example by designing them as integrated circuits. Also, some or all of the position / state / performance storage units 401a to path determination units 407a, etc., may be implemented in hardware, for example by designing them as integrated circuits. Similarly, some or all of the position / state / performance storage units 401b to control input determination units 412, etc., may be implemented in hardware, for example by designing them as integrated circuits. Furthermore, the route management unit 211 to the self-position calculation unit 215, the map information management unit 313 to the self-position calculation unit 315, etc., may be implemented in hardware, for example, by designing some or all of them using integrated circuits.

[0182] Furthermore, as shown in Figure 25, each of the above-mentioned configurations and functions may be implemented in software by a processor such as a CPU interpreting and executing programs that realize each function. Information such as programs, tables, and files that realize each function can be stored not only in the HD, but also in memory D1, a recording device such as an SSD, or a recording medium such as an IC (Integrated Circuit) card, an SD (Secure Digital) card, or a DVD (Digital Versatile Disc).

[0183] Furthermore, in each embodiment, only those control lines and information lines deemed necessary for explanation are shown, and not all control lines and information lines are necessarily shown in the actual product. In practice, it can be assumed that almost all components are interconnected.

[0184] 1 Control device 2, 2j, 2k, 2Z AGV 3, 3a to 3k, 3A, 3B, 3Z AGF 40a Mobile device control device 40b Mobile device control device 101a, 101b AGV position / state aggregation unit 102a, 102b Group setting unit 102a, 102b Group setting unit 111, 111a, 111b Release conditions 112, 112a, 112b Maximum number of mobile devices 113, 113a, 113b Movement rules 404a Blocking control unit 631 Blocking area 631c, 631d Blocking area including multiple grouped mobile devices 720a to 720d Destination 720e Nearby destination 720f Common destination 720g Nearby destination 800, 801 to 806, 811 to 815 Group 903 Velocity vector (velocity, relative velocity) 911 Relative distance S221 AGV group update (group setting step) S222 Movement group update (movement rule setting step) S321 AGF group update (group setting step) S322 Movement group update (movement rule setting step)

Claims

1. A control device comprising: a group setting unit that sets up groups of multiple moving objects based on the positions and destinations of each of the moving objects; and a movement rule setting unit that sets common movement rules for the moving objects belonging to the groups set by the group setting unit, wherein the movement rule setting unit sets the movement rules so that the moving objects belonging to the groups move in a common movement pattern.

2. The control device according to claim 1, wherein multiple types of the moving bodies are present, and the group setting unit assigns moving bodies of the same type to the same group.

3. The control device according to claim 1, characterized in that, if a moving body that satisfies the release condition is present in the group, the group setting unit releases the moving body that satisfies the release condition from the group.

4. The control device according to claim 3, characterized in that the group setting unit determines whether or not a preset release condition is met based on the position of the moving body.

5. The control device according to claim 4, characterized in that the group setting unit determines that the release condition is met when the moving body is within a predetermined range from the destination.

6. The control device according to claim 3, characterized in that the movement rule setting unit switches from controlling the moving bodies that have been released from the group according to the common movement rule to controlling each of the moving bodies.

7. The control device according to claim 1, characterized in that the group setting unit sets the maximum number of mobile bodies, which is the maximum number of mobile bodies managed by one group.

8. The control device according to claim 1, characterized in that the movement rule setting unit sets a common travel speed or a common relative speed as the movement rule for the moving bodies belonging to the group.

9. The control device according to claim 1, characterized in that the movement rule setting unit sets the movement rules such that the relative distance between the moving bodies belonging to the group is constant.

10. The control device according to claim 1, characterized in that the movement rule setting unit sets a common destination, which is a common destination, as a common movement rule for the moving bodies belonging to the group, or sets a nearby destination, which is a nearby destination, as a common movement rule for the moving bodies belonging to the group.

11. A mobile body having the control device described in claim 1 built in, wherein the control device controls the mobile body based on the set movement rules.

12. A control system comprising: a control device according to claim 1; and a mobile body control device that controls a group of mobile bodies based on the movement rules set by the movement rule setting unit of the control device.

13. The control system according to claim 12, wherein the control system sets a closed area that includes a group of the moving bodies, and the control device sets the movement rules within the set closed area for the moving bodies belonging to the group.

14. A control method comprising: a control device for controlling a plurality of moving objects, which includes a group setting step for setting up groups of the moving objects based on the positions and destinations of the plurality of moving objects; and a movement rule setting step for setting movement rules common to the moving objects belonging to the group set up in the group setting step, wherein in the movement rule setting step, the control device sets the movement rules so that the moving objects belonging to the group move in a common movement pattern.

Images