JP7623310B2 - Map utilization device and program - Google Patents

Description

The present invention relates to a map utilization device and a program that effectively utilizes map information in relation to a mobile robot and a map utilization environment.

Previously, technology has been considered that allows multiple vehicles or robots to share the same map for their movement.

In Patent Document 1, in a system consisting of a vehicle that uses sensors to monitor the surroundings while traveling on the road, and a server that manages and updates maps, if the landmark positions acquired by monitoring the surroundings of the vehicle differ from the landmark positions on the map, the server considers updating the map. In Patent Document 2, in a system consisting of a vehicle capable of both manual and automatic driving, and a server that manages maps, in order to reduce the amount of communication when uploading surrounding map information acquired by the vehicle while traveling on the road to the server, map information is not uploaded to the server all the time from the vehicle, but rather only map information for the vicinity of a takeover occurs in which the vehicle switches from automatic driving to manual driving, and map updates are considered on the server.

In Patent Document 3, in order to efficiently create a vast environmental map covering a wide area, multiple autonomous robots detect the relative positions of the robots to divide and define search areas for each robot, collect map information for the search area assigned to each robot using SLAM (Simultaneous Localization and Mapping) positioning, and then combine the map information for each search area to generate the entire environmental map. In Patent Document 4, multiple robots that perform SLAM positioning share the map information that each robot has between them via landmark information, thereby improving the positioning accuracy of each robot without each robot having to accumulate large amounts of map information individually.

JP 2020-38359 A JP 2020-71053 A JP 2013-109325 A JP 2019-57312 A

However, in the conventional technologies described above, no consideration was given to making it possible for robots acting as autonomous mobile devices to appropriately use 2D maps, which can be used with less load than 3D maps, for each of the mobile robots, which may have a wide variety of individual specifications.

Map information used for autonomous navigation can be broadly categorized into two-dimensional and three-dimensional maps. Two-dimensional maps assume a flat ground surface and are therefore suitable for use indoors, or outdoors where the surface can be considered nearly flat. On the other hand, three-dimensional maps assume a slope on the ground, so they have a wider range of applications, but they also impose a heavy computational load.

The vehicles covered in Patent Documents 1 and 2 (the computers installed in the vehicles that process map information and sensor information) have ample computing resources and are able to directly download and use 3D maps shared on a server.

On the other hand, for robots whose uses are not limited to autonomous driving on roads, a wide variety of robots may be used depending on individual uses and cost constraints, and while some robots have abundant computing resources that can handle 3D maps, many robots have only limited computing resources, and these robots need to convert the 3D maps into 2D maps before handling them.

However, even in Patent Documents 3 and 4, which are aimed at robots, converting a 3D map into a 2D map is not considered, and therefore no consideration is given to a method of converting into a 2D map suitable for each mobile robot, the individual specifications of which are expected to vary widely.

When converting a map into a 2D map suited to the specifications of a mobile robot, it is important to consider the various possibilities for each robot's field of view and the driving environment in which the map is converted into a 2D map. Figures 1 and 2 show examples of such situational changes.

Figure 1 shows, in schematic form, that even with the same mobile robot 2 and the same measurement object OB-1, the appearance by the external recognition sensor when the driving environment is on a horizontal plane as shown in example EX-11 (as captured within the field of view V-11) is different from the appearance when the driving environment is an uphill slope as shown in example EX-12 (as captured within the same field of view V-11).

In the case of a horizontal plane shown in Example EX11, only the top of the measurement object OB-1 at height h1, which is a horizontal distance D1 away, is visible within the field of view V11. However, in the case of a slope shown in Example EX12, which is inclined at angle θ, this height h1 is approximately reduced to h1*(cos θ) using the cosine function cos, so the top of the measurement object OB-1 also becomes invisible within the same field of view V11, and the measurement object OB-1 becomes invisible as it is located outside the field of view V11. Note that while Figure 1 shows an example of an uphill slope at angle θ, in the case of a downhill slope at angle θ, the height h1 is also approximately reduced to h1*(cos θ), so it is expected that the measurement object OB-1 will also become invisible outside the field of view V11 of the same mobile robot 2. (That is, in the case of an uphill slope with an angle θ as shown in Figure 1, the object OB-1 with height h1 is not vertical with respect to the ground of the uphill slope, but is tilted at an angle θ from the vertical toward the mobile robot 2. In the case of a downhill slope with an angle θ not shown in Figure 1, the object OB-1 with height h1 is not vertical with respect to the ground of the downhill slope, but is tilted at an angle θ from the vertical toward the mobile robot 2. In both the uphill and downhill cases, the height h1 of the object OB-1 is approximately reduced to h1*(cos θ).)

In the example of Figure 2, even if the same cone-shaped measurement object OB-2 is a horizontal distance D away from the apex, the two mobile robots 2-A and 2-B, which have different field of view height specifications, see the measurement object OB-2 differently. In example EX2A, the field of view V2A of mobile robot 2-A is relatively high, so the cone-shaped object OB-2 is captured in its field of view V2A at a higher position, and the measurement result shows that the object is a distance DA away. However, in example EX2B, the field of view V2B of mobile robot 2-B is relatively low, so the cone-shaped object OB-2 is captured in its field of view V2B at a lower position, and the result shows that the object is a distance DB away.

In other words, even if two mobile robots 2-A and 2-B with different visibility specifications are located at the same position and the same distance D away from the same cone-shaped object OB-2, the mobile robot 2-A with a relatively high visibility V2A measures the object OB-2 a distance DA ahead, while the mobile robot 2-B with a relatively low visibility V2B measures the object OB-2 a distance DB ahead, and the relationship between these two distances is "DA>DB", resulting in different measurement results (how the two mobile robots 2-A and 2-B see the object OB-2). The mobile robot 2-A measures the object OB-2 as being relatively far away, while the mobile robot 2-B measures the object OB-2 as being relatively close. Also, since the robot 2-A can see the top of the object OB-2, while the robot 2-B can see the bottom of the object OB-2, the part and range of the object OB-2 that each robot can see are different.

As shown in the schematic examples of Figures 1 and 2 above, when a mobile robot uses a two-dimensional map to move around, it is necessary to use an appropriate two-dimensional map that takes into account the different specifications for the field of view of each individual mobile robot and the different slopes in the driving environment of each mobile robot, but conventional technology has not been able to prepare such a two-dimensional map.

In view of the problems with the conventional technology described above, the present invention aims to provide a map usage device and program that can prepare an appropriate two-dimensional map according to an individual situation.

To achieve the above object, the present invention is a map utilization device that distributes map information along a specified route to a mobile robot to move along the route, and is characterized in that it acquires 3D map information along the route from the entire 3D map information constructed for the field in which the mobile robot can move, as information surrounding the route, converts the 3D map information along the route into 2D map information taking into account the sensing range of an external recognition sensor when the mobile robot moves autonomously and the inclination of the route, and distributes the 2D map information to the mobile robot. It is also characterized in that it is a program that causes a computer to function as the map utilization device.

According to the present invention, 3D map information is converted into 2D map information taking into account the sensing range of the external recognition sensor of the mobile robot and the inclination of the route, so that an appropriate 2D map can be prepared according to individual circumstances.

FIG. 13 is a schematic diagram showing that even when using the same mobile robot and the same measurement object, the measurement object looks different when viewed from the mobile robot depending on whether the traveling environment is a horizontal surface or an inclined surface. FIG. 13 is a schematic diagram showing that even when mobile robots are placed at the same position relative to the same measurement object, the same measurement object appears differently when the mobile robots have different field of view specifications. 1 is a diagram illustrating a configuration of a map using system according to an embodiment. 1 is a functional block diagram of a user terminal, a mobile robot, and a map using device in a map using system according to an embodiment. FIG. 2 is a functional block diagram of a two-dimensional map synthesis unit according to an embodiment. 10 is a flowchart showing information management of each mobile robot by a map using device according to an embodiment. 11 is a flowchart of arranging for product delivery and updating map information involving map conversion processing by a map using device according to an embodiment. 11 is a diagram showing a schematic example of information on visual field specifications stored in a device information storage unit; FIG. FIG. 1 is a diagram showing a schematic example of two-dimensional map creation and two-dimensional map synthesis. FIG. 1 is a diagram illustrating a hardware configuration of a typical computer.

Figure 3 is a diagram showing the configuration of a map usage system 4 according to one embodiment. In this embodiment, as an example of a use of the map usage system 4, a case where an autonomous robot moves through a field F, such as a city, to a destination specified by a delivery service user (user) and delivers goods will be described, but the map usage system 4 of this embodiment can be applied to any use that involves moving an autonomous robot along a specified route within the field F.

The map utilization system 4 comprises multiple (n) user terminals 1-1, 1-2, ..., 1-n used to determine the destination, multiple (m) mobile robots 2-1, 2-2, ..., 2-m that travel to the destination by traveling through a field F such as a city, and a map utilization device 3 that stores 3D maps for the mobile robots, prepares and transmits maps in which the 3D maps are converted to 2D in an appropriate form for each of the mobile robots 2-1 to 2-m and the traveling environment along their travel routes, and performs operational monitoring and navigation to the destination. These elements that make up the map utilization system 4 can communicate with each other via a network NW such as the Internet.

Figure 4 is a functional block diagram of a user terminal 1, a mobile robot 2, and a map utilization device 3 in a map utilization system 4 according to one embodiment. Note that the user terminal 1 and the mobile robot 2 in Figure 4 each represent the functional configuration of any one of the n user terminals 1-1 to 1-n and the m mobile robots 2-1 to 2-m in Figure 3, and represent the common functional configuration of these multiple user terminals 1-1 to 1-n and mobile robots 2-1 to 2-m.

However, although the functional configuration of the multiple user terminals 1-1 to 1-n and mobile robots 2-1 to 2-m is the same as that shown in FIG. 4, the hardware specifications (performance specifications) of the sensing mechanism for estimating the self-position and the mobile mechanism of the autonomous mobile robot may be different from each other. In particular, even if the specifications of the m mobile robots 2-1 to 2-m (each of the mobile robots 2) are variously different, the map utilization system 4 of this embodiment makes it possible to utilize appropriate map information that takes into account the resources of each mobile robot 2.

The user terminal 1 is, for example, a smartphone, into which a delivery service user inputs information about a destination when ordering a product. The user terminal 1 includes a product ordering unit 101 and a destination information input unit 102.

The mobile robot 2 is an autonomous robot that delivers packages to a destination specified by a delivery service user, for example. The mobile robot 2 includes a wireless communication unit 201, a current position acquisition unit 202, a status acquisition unit 203, an imaging unit 204, a device information storage unit 205, a route information storage unit 206, a map information storage unit 207, an operation planning unit 208, and an operation control unit 209.

The map utilization device 3 is, for example, a server device that exists on the cloud, which stores 3D maps for the mobile robot 2, converts them into 2D maps with appropriate content for each of the individual visibility specifications of the mobile robots 2-1 to 2-m and the driving environment (slope conditions) along the travel route, and transmits them, as well as performs operational monitoring and navigation to the destination. Note that a 2D map imposes a lower computational load on the self-location estimation than a 3D map, and in this embodiment, the map is converted into a 2D map to enable self-location estimation even for mobile robots 2 that do not have abundant computational resources.

The map device 3 includes an operation monitoring unit 301, an order information storage unit 302, a destination acquisition unit 303, a three-dimensional map information storage unit 304, a route search unit 305, a route distribution unit 306, a two-dimensional map synthesis unit 300, and a map distribution unit 311.

Figure 5 is a functional block diagram of the 2D map synthesis unit 300 according to one embodiment, which further includes a slope information acquisition unit 307, a visual field information acquisition unit 308, a 2D map creation unit 309, and a multiple 2D map synthesis unit 310. As will be described in detail later, the 2D map synthesis unit 300 converts the 3D map into a 2D map in an appropriate form according to the slope condition of the driving environment along the route obtained by the route search unit 305 and according to the visual field specifications of the mobile robot 2 that moves along this route, and outputs the converted 3D map to the map distribution unit 313, thereby realizing the distribution of the map to the corresponding mobile robot 2. (Similarly, the mobile robot 2 receives route information from the route distribution unit 306, and can move along the route using the distributed route information and 2D map information.)

Fig. 6 is a flowchart showing how the map using device 3 manages information about each of the mobile robots 2 according to one embodiment, and Fig. 7 is a flowchart showing how the map using device 3 arranges for product delivery and updates map information, involving map conversion processing, according to one embodiment. The flowcharts in Figs. 6 and 7 can be executed in parallel by the map using device 3. According to the flow in Fig. 6, the map using device 3 periodically grasps and manages the position information, etc., of each of the mobile robots 2, and can collect the latest three-dimensional map information measured by the mobile robots 2 in a field F, such as in a city. According to the flow in Fig. 7, the map using device 3 updates the three-dimensional map information to the latest state, and when a delivery request is received, determines a delivery route, etc., and determines which of the multiple mobile robots 2 will be in charge of the delivery task, and can instruct the mobile robots 2 to deliver the product along the delivery route by distributing appropriate two-dimensional map information and route information.

Below, we will explain the details of the processing content of each functional block of the map utilization system 4 shown in Figures 4 and 5 while explaining each step in the flow in the order of Figures 6 and 7.

When the flow in FIG. 6 is started, in step S31, the mobile robot 2 determines whether the current time corresponds to the timing for transmitting its own position information, etc., and if so, proceeds to step S32, and if not, proceeds to step S33. This transmission timing may be, for example, every time a certain period of time has elapsed, and position information, etc. can be transmitted and received in real time at certain intervals.

<Step S32...Current position acquisition unit 202, status acquisition unit 203, operation monitoring unit 301>
In step S32, the current position acquisition unit 202 (and the status acquisition unit 203) processes the mobile robot 2 to transmit its own position information at the current time, etc. to the map using device 3, and the map using device 3 receives this position information and stores and manages it through the processing of the operation monitoring unit 301, after which the process proceeds to step S33.

That is, the current position acquisition unit 202 acquires the current position of the mobile robot 2 and transmits this position information to the operation monitoring unit 301. For this purpose, the current position acquisition unit 202 acquires the current position using a positioning system based on any existing method, such as GPS (Global Positioning System) or indoor GPS. Here, for indoor facilities where GPS coordinates cannot be acquired, absolute position information acquired using indoor positioning technology such as IMES (Indoor MEssaging System) may be used as the position information. Furthermore, the current position acquisition unit 202 may not only acquire the current position using these methods such as GPS, but may also correct the current position by measuring the distance to surrounding measurement objects using the imaging unit 204, which will be described later.

The status acquisition unit 203 may also acquire the current status of the mobile robot 2 and transmit this status information to the operation monitoring unit 301. For this reason, the status acquisition unit 203 acquires status data such as remaining battery power, temperature, movement speed, etc. from various sensors equipped in the mobile robot 2.

Furthermore, the operation monitoring unit 301 monitors the operation of each mobile robot 2. The operation monitoring unit 301 can perform operation monitoring by linking the position information and status information received in real time from each mobile robot 2 with information that identifies the individual mobile robot 2. The operation monitoring unit 301 analyzes the received position information and status information, and may issue an alert to a system monitor if a malfunction occurs in a mobile robot 2.

Note that, not only in step S32 but also in each step of Figs. 6 and 7, the wireless communication unit 201 is responsible for transmitting and receiving information via wireless communication between the mobile robot 2 and the map utilization device 3. Here, the wireless communication unit 201 can perform wireless communication via a base station compatible with wireless communication methods such as 4G (fourth generation mobile communication system) and 5G (fifth generation mobile communication system) that are currently in practical use, and 6G (sixth generation mobile communication system) that is expected to be practical in the future.

Although not explicitly shown as a functional block, the map usage device 3 and the user terminal 1 also have functions similar to those of the wireless communication unit 201 in the mobile robot 2, and can transmit and receive information required in each embodiment of each step in Figures 6 and 7 between the map usage device 3 and the user terminal 1, and between the map usage device 3 and the mobile robot 2, via wireless communication.

<Steps S33, S34...Transmission of map information>
In step S33, the mobile robot 2 determines whether the current time corresponds to the timing for transmitting map information for itself, and if so, proceeds to step S34, and if not, returns to step S31. In step S34, the mobile robot 2 transmits map information to the map using device 3, and then returns to step S31. The map information may be obtained in the form of three-dimensional point cloud data or the like (a data format that can be obtained by the imaging unit 204) obtained by SLAM or the like when the mobile robot 2 performs autonomous movement, which will be described later, and can be transmitted to the map using device 3.

When the mobile robot 2 of this embodiment moves autonomously, even if three-dimensional point cloud data is used as external measurement data, it is sufficient to acquire the data only in a limited range (the limited field of view of the mobile robot 2 as exemplified in Figures 1 and 2) for comparison with a two-dimensional map, rather than acquiring the data over a wide range such as the entire sky. Therefore, for the mobile robot 2 to collect the latest map information, a mobile robot 2 with higher measurement specifications that can directly use a three-dimensional map may be used, separate from the mobile robot 2 that uses the two-dimensional map in this embodiment.

Note that any existing method for keeping 3D map information up to date may be used for acquiring this map information and updating the map in the map using device 3 in step S45 of FIG. 7 described later, and functional blocks for performing specific processes for these map updates are omitted from FIG. 4 and other figures. For example, the timing for transmitting the map information in step S33 may be when it is determined that the map information acquired by the mobile robot 2 contains information that has changed from the map information received from the map using device 3 (for example, when there is an object that is estimated to be a new object), etc.

Each step in FIG. 6 has been described above. The flow in FIG. 6 is executed by each of the multiple mobile robots 2 (each of the m mobile robots 2-1 to 2-m in FIG. 3) for the map utilization device 3. In this way, the map utilization device 3 monitors all information on the m mobile robots 2-1 to 2-m in real time in the operation monitoring unit 301, and can keep the three-dimensional map information (stored in the three-dimensional map information storage unit 304, described later) up to date using map information sent appropriately from the m mobile robots 2-1 to 2-m as the latest measurement results of the field F. In this way, the map utilization device 3 can grasp all of the multiple mobile robots 2 in real time and keep the three-dimensional map information up to date by using the flow in FIG. 6. In this way, the map utilization device 3 can generate an appropriate two-dimensional map from the three-dimensional map according to the specifications and route of each mobile robot 2 by using the flow in FIG. 7, and the map utilization device 3 can arrange for product delivery.

<Step S41...3D map information storage unit 304, device information storage unit 205>
7 is started, in step S41, as a pre-processing required to enable product delivery, the map utilization device 3 constructs map information to store 3D map information of the field F in the 3D map information storage unit 304, and the device information (information on the visual field specifications of the mobile robots 2) stored in the device information storage unit 205 of each mobile robot 2 is received and stored in the 2D map synthesis unit 300, and then the process proceeds to step S42. (Note that the 2D map synthesis unit 300 uses the visual field specification information stored in step S41 to synthesize a 2D map according to the delivery route and the visual field specifications of the mobile robots 2 in step S43, which will be described later. The visual field specification information will be described later with reference to the example of FIG. 8 regarding the device information storage unit 205.)

The three-dimensional map information storage unit 304 stores nationwide road map data and associated facility data such as various facilities and stores in three dimensions as map information of the field F in which the mobile robot 2 operates. The three-dimensional map information storage unit 304 also stores indoor three-dimensional map data related to indoor facilities and stores to which the mobile robot 2 may move. The three-dimensional map information storage unit 304 may be, for example, three-dimensional point cloud map information created by the mobile robot 2 using SLAM (Simultaneous Localization and Mapping), a technology that simultaneously performs self-location estimation and environmental map creation. (As described above, in this case, a three-dimensional point cloud created by a high-spec mobile robot 2 that can directly handle a three-dimensional map, separate from the mobile robot 2 that uses a two-dimensional map in this embodiment, may be used.) Also, the three-dimensional map information may be in a different format such as an occupancy grid or a 3D model, or may be three-dimensional map information created by another moving body such as an automobile.

The three-dimensional map information storage unit 304 further links the three-dimensional map information stored as described above to information on a graph (discrete graph) for enabling route search. As is well known, a graph for route search is defined as edges connecting nodes, and can be expressed in a data format such as an adjacency matrix. The nodes are linked to the point coordinates (three-dimensional spatial coordinates) of corresponding positions in the three-dimensional map information, and similarly, the edges can be linked to spatial coordinates in the three-dimensional map information as straight lines or curves connecting adjacent nodes. (Note that when the three-dimensional map information is given as a point cloud, for example, the spatial coordinates of the nodes in the graph to be associated may or may not match any of the point clouds. For example, the center of gravity of the point cloud in a certain local spatial range may be assigned to the spatial coordinates of one node as a representative point representing this local spatial range.)

This graph linked to the three-dimensional map information is a model of the route network (such as the road network along which the mobile robot 2 can move) in the field F represented by the three-dimensional map information.

The three-dimensional map information to which the above-mentioned graph is linked and stored in the three-dimensional map information storage unit 304 in step S41 may be obtained automatically or manually by an administrator from a server or the like that manages a map information database on the network NW. In step S45 described later, the three-dimensional map information stored in the three-dimensional map information storage unit 304 can also be updated to the latest state.

The device information storage unit 205 stores height information of the camera and LiDAR, which are external recognition sensors (used when estimating the self-position) mounted on the mobile robot 2, as information on the visual field specifications of the mobile robot 2. The height information in the device information storage unit 205 may be input in advance by a person, or the height of the camera and LiDAR may be estimated by determining the distance to a characteristic object captured by the imaging unit 204 and the size of the object.

Figure 8 shows a schematic example of the information of the visual field specification stored in the device information storage unit 205. The visual field specification does not relate to the size of the mobile robot 2 itself (such as the height Hr shown in the figure), but can be given as information on the height H from the ground of the viewpoint p (camera position p) of the camera or LiDAR to specify the field of view R (sensing range R) in relation to the ground. In more detail, the visual field specification information may include information on the upper limit H1(d) and lower limit H2(d) of the vertical visual field range at a position a distance d away from the viewpoint p in front of the horizontal line. The upper limit H1(d) and lower limit H2(d) may be given in the form of table information as a function of the distance d, or may be given as constants H1 (=H1(d)) and H2 (=H2(d)) that are independent of the distance d as a simplified model of the visual field specification.

<Step S42...Determination of whether processing is required by the product ordering unit 101 and the destination information input unit 102>
In step S42, when a product delivery request is sent from any of the user terminals 1, it is determined whether or not the map using device 3 has received this request at the current time. If the request has been received, the process proceeds to step S43; if the request has not been received, the process proceeds to step S44.

When the following processing is performed by the input operation of the user in the product ordering unit 101 and destination information input unit 102 of any of the user terminals 1 used by the user requesting product delivery, a product delivery request is sent from the user terminal 1 and received by the map utilization device 3, and a positive judgment is obtained in step S42.

The product ordering unit 101 allows a user, who is a delivery service user, to select a product using a smartphone or the like owned by the user and place a manual order. The product ordering unit 101 may also manage the remaining amount of items owned by the delivery service user in real time, and automatically order replenishment products when the remaining amount falls below a preset threshold.

The destination information input unit 102 inputs information about the destination, such as an address, when a product order is placed by the product ordering unit 101 as described above. The destination information input unit 102 may reuse previous input and omit input each time. The destination information input unit 102 may also use a GPS positioning function provided in the smartphone to set the current location acquired by the GPS as the destination. The destination information input unit 102 may also use surrounding scenic information captured by the smartphone camera as a reference for the destination.

The information on the product that is the subject of the delivery request and the information on the destination to which the product is to be delivered, obtained by the product ordering unit 101 and the destination information 102, are transmitted from the user terminal 1 to the map utilization device 3 and stored as order information in the order information storage unit 302 of the map utilization device 3.

In step S43, the map utilization device 3 arranges for product delivery in accordance with the order information for which a positive judgment was obtained in step S42, and the process proceeds to step S44. In accordance with this arrangement, the mobile robot 2 can dispatch the product. Details of the product arrangement in step S43, such as route calculation, map preparation, and selection of the mobile robot 2 to be in charge of product delivery, will be described later.

In step S44, the map using device 3 determines whether the current time corresponds to the timing for updating the map information, and if so, proceeds to step S45, and if not, returns to step S42. In step S45, the map using device 3 updates the three-dimensional map information (and the graph information linked thereto) stored in the three-dimensional map information storage unit 304, for example by reflecting the latest map information transmitted from the mobile robot 2, and then returns to step S42. As described above, any existing method may be used to update the map information to the latest state, and specific functional blocks for this update process are omitted in Figure 4 etc.

In this way, according to the flow of FIG. 7, the map utilization device 3 determines at each real-time instant whether a delivery request has been received in step S42 and whether a map update is necessary in step S44. If a delivery request has been received, delivery arrangements are made, and if a map update is necessary, the map is updated, thereby enabling delivery arrangements to be made in accordance with the latest map.

In the following, regarding step S43, which will be described in detail later, we will explain the details of the delivery arrangement involving the map conversion process by the map utilization device 3, as well as the details of the product delivery by the mobile robot 2 in accordance with this delivery arrangement.

<Delivery arrangement by map using device 3 in step S43>
Specifically, the map utilization device 3 can make delivery arrangements by processing each of the functional blocks as follows.

The order information storage unit 302 receives and stores order information for ordering products from the product ordering unit 101 and the destination information input unit 102. The order information storage unit 302 works in conjunction with a purchasing system (not shown) to perform purchasing processing and develop a product delivery plan.

For example, the product delivery plan can define, for each mobile robot 2, its current location (current point) as the start point, the location where the product to be delivered specified in the order information is automatically or manually loaded onto the mobile robot 2 as the relay location (relay point), and the destination (destination location, destination point) to which the product specified in the order information is to be delivered as the end point. If the current location of the mobile robot 2 is already in, for example, a warehouse or store where the product to be delivered is located, the start point and the relay location may be deemed to match, and the relay location may be omitted.

The destination acquisition unit 303 acquires destination information from the order information stored in the order information storage unit 302.

The route search unit 305 searches for a driving route from the starting point (current position) of the mobile robot 2 to the destination acquired from the destination acquisition unit 303 based on the map information stored in the three-dimensional map information storage unit 304. The route search unit 305 searches for a driving route from the starting point to the destination using an algorithm such as Dijkstra's algorithm, A* algorithm, or genetic algorithm. The shortest route can be searched for by providing a cost according to the length of the edge (the physical distance of the straight line or curve on the three-dimensional map information corresponding to the edge).

At this time, if the mobile robot 2 is not loaded with the product to be delivered, two route searches can be performed: "start point → relay position" and "relay position → destination." Also, for each of the three points of the start point, relay position, and destination, a corresponding node in a discrete graph linked to the three-dimensional map information can be determined, and a route search can be performed on the discrete graph. The current position of the mobile robot 2 can be obtained from information monitored and grasped in real time by the operation monitoring unit 301.

The route distribution unit 306 transmits the route guidance data searched by the route search unit 305 to the mobile robot 2. This route guidance data is configured as data that traces adjacent nodes on the graph, using each edge on the graph as a route from the starting point to the destination (via any relay points).

This route guidance data is linked to two-dimensional map information by distributing a two-dimensional map synthesized by the two-dimensional map synthesis unit 300 (described later) to the mobile robot by the map distribution unit 311. The linked two-dimensional map information is referenced for self-location estimation when the mobile robot 2 moves according to the route guidance data. (In other words, map information of the surrounding environment when moving according to the route guidance data is distributed by the map distribution unit 311.)

The target of route distribution by the route distribution unit 306 (and map distribution by the map distribution unit 311, described later) may be one of the multiple mobile robots 2-1 to 2-m that has been determined to be in charge of delivery operations. This one robot may be automatically determined by estimating the time required for delivery from the route searched by the route search unit 305 and selecting the one with the shortest delivery time, or may be manually selected by an administrator or the like from among multiple robots whose estimated delivery times are within a threshold value.

The 2D map synthesis unit 300 reads map information located around the route from the 3D map stored in the 3D map information storage unit 304 for the mobile robot 2 delivering goods and its route, and converts the locations of the route that are determined to be horizontal into a 2D map according to the height H of the field of view of the mobile robot 2. This height information can be obtained by using the height of the sensor position (height H in the example of FIG. 8) as the height of the sensing range of each mobile robot 2 received from the device information storage unit 205.

Each position on the 3D map is given in advance a distinction between a movable part such as the ground and an immovable part such as a wall, as well as information on the height of the ground (for example, in the case of a building, this is not the height of the building, but the information on the height of the first floor above ground). For each position (x, y) on the 2D map, if the visual field height H of the mobile robot 2 corresponds to a movable part such as the ground (the three-dimensional position obtained by adding the visual field height H to the ground height is space and there are no objects), then it is deemed movable, and if it corresponds to the inside of a wall or other immovable obstacle (the three-dimensional position obtained by adding the visual field height H to the ground height is inside an object), then it is deemed immovable. In this way, the conversion result to the 2D map can be obtained by distinguishing between movable and immovable for each position (x, y). (Note that instead of using the visibility height H as a single value, the height of the visibility range R as shown in FIG. 8 may be used. In other words, the range of the visibility R height [H2(d),H1(d)] from the lower limit height H2 (=H2(d)) to the upper limit height H1 (=H1(d)) may be used to determine whether movement is possible or not in the same manner for the entire range of the visibility height H, H2(d)≦H≦H1(d). In the following, the visibility height H is described as a single value, but a range may be considered in this way. The horizontal distance d may also be a fixed value or a fixed range d1≦d≦d2 as the distance when the mobile robot 2 estimates its own position.)

Note that if the map is converted to a two-dimensional map by using the visibility height H to distinguish between movable and immovable, a situation may occur in which obstacles that do not appear at this height H are not reflected in the two-dimensional map and are lost. For example, for a certain position (x, y), height H is a space where no objects exist and is movable, but a situation may occur (although this is generally not considered to occur frequently) in which an obstacle exists at a lower height H/2 in the three-dimensional map. In this way, the virtual obstacle completion technology of the present applicant in Patent Application No. 2021-214770 can be used as a technology to deal with obstacles that are lost on the two-dimensional map at the visibility height H.

The 2D map synthesis unit 300 further converts the 3D map into a 2D map for any portion of the route that is not determined to be horizontal, according to the height H of the field of view of the mobile robot 2 and its inclination angle θ (when θ is positive, it can be distinguished as an uphill slope along the route, and when θ is negative, it can be distinguished as a downhill slope along the route).

In the above, in order to explain the overall overview of the processing of the two-dimensional map synthesis unit 300, the route is divided into cases according to whether it is horizontal or has an inclination angle θ, but by setting θ = 0°, it is possible to process the horizontal case in a similar framework as a special case of an inclined case.

In other words, in general, including cases where θ=0°, when the route information to the destination searched by the route search unit 305 passes through a location range where the ground slope (slope angle θ along the route) is different, the 2D map creation unit 309 converts the 3D map into a 2D map based on the ground slope angle θ at that location and the height H of the camera or LiDAR of each mobile robot 2-1 to 2-m in each location range. By utilizing the route information to the destination in this way, it becomes possible to create an appropriate 2D map that matches the field of view of each robot, even if the slope changes in the direction of the travel route from the current location of the mobile robot 2 to the destination.

To perform this process, the two-dimensional map creation unit 309 uses information from the tilt information acquisition unit 307 and the field of view information acquisition unit 308 as input, as follows:

The inclination information acquisition unit 307 acquires ground inclination information in the direction of movement along the path of the mobile robot 2 from the three-dimensional map information stored in the three-dimensional map information storage unit 304. The inclination information acquisition unit 307 only needs to acquire ground inclination information for the entire movement path of the mobile robot 2 from the departure point to the destination stored in the route distribution unit 306. The visual field information acquisition unit 308 acquires height information of the camera and LiDAR mounted on each of the mobile robots 2-1 to 2-m (information on the height H of the viewpoint p in the example of FIG. 8) from the device information storage unit 205.

Note that if the inclination angle θ on the route cannot be considered constant over a certain range due to the ground on the route being highly uneven, and changes significantly locally, it is generally considered difficult to appropriately estimate the self-location on the two-dimensional map by referring to the two-dimensional map, and it is necessary to perform self-location estimation on the three-dimensional map using a three-dimensional map. In this embodiment, it is assumed that the inclination angle θ is constant at the edges (edges moving from a node to an adjacent node) that constitute the searched route and that the two-dimensional map can be used on the route. (Note that in order to deal with cases where the two-dimensional map cannot be used, the technology of Patent Application No. 2021-210317 by the present applicant can be used as a technology for determining whether a two-dimensional map or a three-dimensional map should be used depending on the route and delivering the determined two-dimensional map or three-dimensional map to the appropriate mobile robot 2.)

At this time, the inclination angle at a certain edge E_k is θ_k, and the inclination angle at the next edge E_k+1 on the path is θ_k+1 (≠θ_k). The inclination angle may change along the path, but it is assumed that the inclination angle change is smooth and almost instantaneous. Therefore, when the mobile robot 2 is located on the edge E_k, it refers to the local two-dimensional map M_k corresponding to the inclination angle θ_k, and when it moves to the next edge E_k+1, it immediately switches to the local two-dimensional map M_k+1 corresponding to the inclination angle θ_k+1 and refers to it, thereby switching the reference map while estimating its own position along the path. (Note that an example of this switching reference will be described later with reference to FIG. 9, but by processing by the multiple two-dimensional map synthesis unit 310 described later, from the viewpoint of the mobile robot 2, by referring to a single synthesized two-dimensional map (including information that distinguishes each area corresponding to the local two-dimensional map), it is possible to obtain a result similar to that of the switching without performing processing to switch the local two-dimensional map.)

In the above, it is assumed that each edge E_k that constitutes the route has a constant slope θ_k. A discrete graph linked to a 3D map may be defined in advance so that this assumption holds true, or the 3D map range corresponding to each edge E_k may be divided into grids or the like, with a constant slope maintained for each grid and the slope changing at the grid boundaries.

The two-dimensional map creation unit 309 may determine whether there is a correlation between the ground slopes (whether there is a change in the ground slope) between grids based on a certain standard area, and may create grids where the ground slope does not change much in the same two-dimensional map, and create grids where the ground slope changes as separate two-dimensional maps. For example, if a first road where the ground slope does not change much continues for 300 m, it is desirable to create the same first two-dimensional map, and if a second road where the ground slope becomes steeper continues for 100 m after that, it is desirable to create a separate second two-dimensional map for that 100 m. (That is, for the area around the first road, the three-dimensional map may be converted into a first two-dimensional map by taking into account the slope of the first road, and for the area around the second road, the three-dimensional map may be converted into a second two-dimensional map by taking into account the slope of the second road, thereby obtaining two-dimensional maps that are converted separately for each slope that changes along the route.) The two-dimensional map creation unit 309 may, for example, set a threshold for the amount of change in ground slope, and if the threshold is exceeded, create a separate two-dimensional map.

The multiple 2D map synthesis unit 310 synthesizes 2D maps for each location (each location on the route where the inclination angle θ is determined to be constant) converted by the 2D map creation unit 309 in the route information to the destination searched by the route search unit 305, and creates a 2D map to the destination.

In this way, it is possible to create an appropriate 2D map even for the situation changes exemplified in Figures 1 and 2. In the example of Figure 1, in the presence of a common mobile robot 2 and a common object OB-1, a 2D map can be created in which object OB-1 is visible when it is horizontal, as in example EX11, and object OB-1 is invisible when there is an inclination angle θ, as in example EX12. (On the other hand, it is desirable to navigate the mobile robot 2 so that it moves based on other visible objects, so as not to collide with the invisible object OB-1 in example EX12.)

Also, if the tilt angle θ of example EX12 exists, a two-dimensional map can be created by performing a distance expansion transformation of D11=D1/(cos θ) so that the horizontal distance D1 becomes the distance D11 that takes the tilt into account. If the range of the existing tilt angles θ is small and the 1/(cos θ) factor expansion can be relatively ignored in relation to the travel distance of the mobile robot 2 (if cos θ ≒ 1 and 1/(cos θ) ≒ 1), this distance expansion transformation can be omitted.

In the example of Figure 2, even if the mobile robots are located at the same distance D from the same cone-shaped object OB-2 on the same horizontal plane, the distance is DA for mobile robot 2-A, which has a high visibility, and DB for mobile robot 2-B, which has a low visibility (DB<DA), so a two-dimensional map can be created that is suited to the individual visibility specifications of mobile robot 2.

Figure 9 is a diagram showing a schematic example of 2D map creation and 2D map synthesis by the above process. For example, for a certain mobile robot 2-1, the 2D map creation unit 309 creates separate 2D maps 71, 72, 73, and 74 for sections 61, 62, 63, and 64 where the ground slope on the route is different. The multiple 2D map synthesis unit 310 synthesizes the 2D maps 71, 72, 73, and 74 to create one 2D map 75. In this way, when the mobile robot 2-1 is located in sections 61, 62, 63, and 64, it estimates its own position by referring to the corresponding 2D maps 71, 72, 73, and 74, respectively, and becomes able to move along the specified route.

For example, when the mobile robot 2-1 is in the second section 62 of the four sections, it estimates its own position by referring only to the corresponding second two-dimensional map 72 among the two-dimensional map 75 (entire), and the result of the self-position estimation within this second two-dimensional map 72 can be obtained as being within the two-dimensional map 75 (entire), but the maps 71, 73, 74 corresponding to the other sections 61, 63, 64 other than the second are not referenced for self-position estimation. (Note that the four two-dimensional maps 71, 72, 73, and 74 define respective coordinates (x,y) ₇₁ , (x,y) ₇₂ , (x,y) ₇₃ , and (x,y) ₇₄ , and the scales and orientations of these coordinates generally differ, and the coordinates do not necessarily match. For example, if the end point of section 61 is at coordinate (100,100) ₇₁ on two-dimensional map 71, and the start point of section 62, which is at the same position, is at coordinate (100,100) ₇₂ on two-dimensional map 72, then the relationship "(100,100) ₇₁ = (100,100) ₇₂ " holds. However, since the coordinate systems are different, the relationship "(101,101) ₇₁ = (101,101) ₇₂ " does not hold for other coordinate values, for example. " does not hold in general. In this embodiment, the two-dimensional maps 71, 72, 73, and 74 are switched for each section, so the coordinate system should be switched at that time.)

In this case, for example, mobile robot 2-1 will be able to extract detection object 51 in section 63 within detection range 2002, which will be plotted as detection object 76 on a two-dimensional map. (Note that this detection range 2002 is the same as detection range 2001 in another section 61, for example, when viewed from mobile robot 2-1 as the base, but when viewed from field F as the base, it will be a different range depending on the different slopes in sections 61, 63, etc.)

On the other hand, in contrast, if the method of this embodiment is not applied and the two-dimensional map is not divided according to the change in ground inclination, the two-dimensional map 91 is created with the sections 61, 63, etc. shown in the lower part of the two-dimensional map 91, which are sections 81, 83, etc. shown in the lower part of the two-dimensional map 91. In this case, instead of the detection range 2002 (upper part) using the original inclination information for the mobile robot 2-1 to properly detect the detection object 51 in the sections 63 and 83, the inclination information of the section 81 is uniformly reflected, and the conversion to the two-dimensional map 91 is performed under the detection range 3001 that is inappropriate for the section 83. In this case, the detection object 51 is not extracted on the two-dimensional map 91, and the measurement object existing in the area indicated by the range of the reference symbol 92 on the two-dimensional map 91 cannot be correctly recognized, and the current location may be erroneously determined in the self-location estimation.

The example of this embodiment in the upper part of Figure 9 is an example of a case where a route is given in the order of sections 61, 62, 63, 64. If the direction is reversed and the route is sections 64, 63, 62, 61, the sign of the inclination angle θ will also be reversed, resulting in a different route, and it is generally assumed that a different two-dimensional map from the two-dimensional map 75 indicated by the reference symbol 75 will be synthesized.

As described above, in this embodiment, an appropriate two-dimensional map can be synthesized and distributed according to the individual visual field specifications of the mobile robot 2 and the inclination of the specifically determined route.

<Delivery process of the mobile robot 2 that has received the delivery instruction in step S43>
The above has described in detail the processing content of each functional block in charge of arranging delivery by the map using device 3 in step S43. Below, the processing of the delivery process performed by the mobile robot 2 in charge of delivery operations, which has received route information and two-dimensional map information as delivery instructions in accordance with the delivery arrangements made by the map using device 3, will be described as detailed processing of each functional block. This delivery process can be realized by moving along a specified route while estimating its own position using an existing method, referring to the received two-dimensional map.

In this embodiment, as shown in the example of Figure 9, there may be changes in inclination on the received two-dimensional map, but from the viewpoint of the mobile robot 2, it is assumed to always be on a horizontal plane, and can perform autonomous movement along a route while estimating its own position by referring to the two-dimensional map according to existing methods.

The imaging unit 204 uses a camera mounted on the mobile robot 2 to capture images of the moving direction, etc. of the mobile robot 2 as input necessary for estimating the self-position of the mobile robot 2 when it moves. The imaging unit 204 may further use a LiDAR mounted on the mobile robot 2 to measure the moving direction, etc.

The route information storage unit 206 stores route information to the destination received from the route distribution unit 306 of the map usage determination device 3, and uses this information to determine the operation of the mobile robot 2.

The map information storage unit 207 stores map information of places where the mobile robot 2 may move (i.e., places around the route) received from the map distribution unit 311 of the map-in-use determination device 3, and uses the map information to determine the operation of the mobile robot 2. The map information stored in the map information storage unit 207 is a two-dimensional map received from the map distribution unit 311 of the map-in-use determination device 3.

The motion planning unit 208 plans the next motion of the mobile robot 2 (motion at each time when moving along a route in real time). When the motion planning unit 208 moves along a route stored in the route information storage unit 206 by referring to the map stored in the map information storage unit 207, it plans motion that matches the surrounding environment using the current position acquired by the current position acquisition unit 202, the state of the mobile robot 2 acquired by the state acquisition unit 203, and the image acquired by the image acquisition unit 204. For example, when there is an obstacle ahead, the motion planning unit 208 plans motion for each local environment in which the mobile robot 2 is located so that the robot moves along a route that avoids the obstacle at an appropriate moving speed.

The details of the current position acquisition unit 202 and the status acquisition unit 203 are as described above in the explanation of step S32, and the current position and status of the mobile robot 2 can be acquired by each sensor or the like when the mobile robot 2 moves in accordance with a delivery command.

The motion control unit 209 executes the motion determined by the motion planning unit 208. The motion control unit 209 controls the driving type, such as moving forward, backward, or turning right or left, the driving speed, and the motion type other than driving, such as changing the camera direction.

The mobile robot 2 that receives a command for delivery work can move to the destination and deliver the goods as described above. The mobile robot 2 may move alone to make the delivery, or may periodically communicate with the map using device 3 along the way and move according to navigation from the map using device 3. For example, instead of receiving delivery route information and two-dimensional or three-dimensional map information all at once for the entire delivery route, the delivery route may be divided into a number of partial routes, and each time a partial route is passed, route and map information for the next partial route may be received from the map using device 3.

Below, we explain various supplementary, additional, and alternative examples.

(1) As an application example of an embodiment of the present invention, it is possible to more smoothly perform tasks using robots in a certain environment, such as a work site, by remote control (centralized management by a remote manager using the map utilization device 3). This makes it unnecessary for a worker to actually go to the work site, and it is possible to reduce carbon dioxide emissions by saving energy resources required for human movement, which makes it possible to contribute to Goal 13 of the Sustainable Development Goals (SDGs) led by the United Nations, which is to "take urgent action to combat climate change and its impacts."

(2) The conversion of distance D1 to distance D11 = D1/(cos θ) described above with reference to Figure 1 can be achieved by treating the inclined plane along the inclination angle θ as the horizontal plane from the position of the mobile robot 2 when it moves (treating it as a deemed horizontal plane) when the object OB-1 is extending vertically and is at an inclination angle of angle θ (within the range of inclination angles of angle θ on the path of the mobile robot 2), and treating the object OB-1 as extending at an inclination angle θ from the vertical direction, rather than vertically from the deemed horizontal plane.

This assumes that the object OB-1 is modeled as a sufficiently thin rod extending vertically, and when the inclination angle θ is 0° (horizontal plane), it will have the longest length h1, and when the inclination angle θ is constant, it will exist in an inclined state with its height reduced to h1*(cos θ).

More generally, if the object OB-1 has a more complex shape or is positioned at an inclination with respect to the horizontal plane, the object OB-1 can be appropriately handled in the presence of the inclination angle θ by taking into account the assumed horizontal plane when the inclination angle θ exists. To this end, an existing 3D CG model can be used to check in 3D space whether the field of view of the mobile robot 2 overlaps with the object OB-1 taking into account the inclination angle θ.

To reduce the computational load of this overlap determination in three-dimensional space, the objects on the three-dimensional map can be simply modeled as simple geometric shapes such as sufficiently thin rods or rectangular prisms, or the three-dimensional map itself can be simply modeled as having vertical walls that separate the movable and non-movable areas.

(3) The information on the visual field of the mobile robot 2 stored in the device information storage unit 205 may be modeled and stored as a field of view based on a deemed horizontal plane that changes according to the inclination angle θ. For example, when the mobile robot 2 is located on a horizontal plane (inclination angle θ=0°), the external recognition sensor such as a camera is also arranged in the mobile robot 2 in a properly vertical position, and the visual field is also horizontal. However, when the mobile robot 2 is located on an inclined plane with an angle θ, due to the presence of bending of the mechanical mechanisms from the moving mechanism (tires, etc.) of the mobile robot 2 to the camera, etc., when this inclined plane is taken as the deemed horizontal plane, the visual field is not horizontal, and faces slightly downward (closer to the ground) or upward. In such a case, the visual field according to the angle θ may be stored by prior measurement.

For example, if it has been confirmed in advance that a mobile robot 2 will be 10 percent lower when the inclination angle θ=-10° (negative inclination angle, downhill) with respect to the upper limit H1 (=H1(d)) and lower limit H2 (=H2(d)) or height H (see FIG. 8) of the vertical field of view when θ=0°, the upper limit H1 (=H1(d)) and lower limit H2 (=H2(d)) or height H for the inclination angle θ=-10° may be stored as 0.9*H1(d) and 0.9*H2(d) or height 0.9*H for the inclination angle θ=+10° (positive inclination angle, uphill), and the upper limit H1 (=H1(d) and lower limit H2(d) or height 1.1*H for the inclination angle θ=+10° may be stored as 1.1*H1(d) and 1.1*H2(d) or height 1.1*H for the inclination angle θ=+10°.

(4) The path search unit 305 searches for and determines the path of the mobile robot 2. The mobile robot 2 may move directly along this path, or may adopt this path as the global path (higher-level path) only and determine the actual local path (lower-level path) by itself.

That is, the mobile robot 2 may obtain multiple local routes L_k (k=1, 2, ..., K) with their start points S_k and end points G_k on a two-dimensional map by dividing the route obtained by the route search unit 305 (route corresponding to the upper side). Here, the end point G_k of the kth route L_k becomes the start point S_k+1 of the next k+1th route L_k+1. The start point S_k and end point G_k may use the nodes of a discrete graph when the route search is performed by the route search unit 305, or may be determined separately by dividing the route on the mobile robot 2 side.

When the mobile robot 2 actually moves autonomously, it follows multiple local routes L_k in order, with the constraint that it must pass through the starting point S_k and the ending point G_k. The robot is responsible for determining the specific local route from the starting point S_k to the ending point G_k and for autonomous movement.

In this case, the two-dimensional map synthesis unit 300 takes into consideration the slope (slope according to the expected direction of path movement) of each specific local path candidate from the starting point S_k to the end point G_k (the candidate path may not be used as a result of the local path determination by the mobile robot 2), and synthesizes a two-dimensional map in the same manner as described above.

(5) Figure 10 is a diagram showing an example of the hardware configuration of a typical computer device 70. Each of the user terminal 1, mobile robot 2, and map usage device 3 constituting the map usage system 4 can be realized as one or more computer devices 70 having such a configuration. When a partial configuration of the map usage system 4 is realized by two or more computer devices 70, information required for processing may be sent and received via a network. The computer device 70 includes a CPU (Central Processing Unit) 71 that executes predetermined instructions, a GPU (Graphics Processing Unit) 72 as a dedicated processor that executes some or all of the instructions executed by the CPU 71 in place of or in cooperation with the CPU 71, a RAM 73 as a main memory device that provides a work area for the CPU 71 (and the GPU 72), a ROM 74 as an auxiliary memory device, a communication interface 75, a display 76, an input interface 77 that accepts user input via a mouse, keyboard, touch panel, or the like, a camera 81 and a sensor 82 used for the self-position estimation function of the mobile robot 2, an actuator 83 such as a motor and a movement mechanism 84 such as wheels (including a transmission mechanism such as axles and gears) that provide the autonomous movement function of the mobile robot 2, and a bus BS for transmitting and receiving data between these.

Each functional unit of the map utilization system 4 can be realized by a CPU 71 and/or a GPU 72 that reads from a ROM 74 a predetermined program corresponding to the function of each unit and executes it. Both the CPU 71 and the GPU 72 are a type of computing device (processor). Here, when display-related processing is performed, a display 76 configured as a monitor such as an LCD or a lighting device such as an LED also operates in conjunction with the display, and when communication-related processing related to data transmission and reception is performed, a communication interface 75 also operates in conjunction with the display.

In the mobile robot 2, the imaging unit 204 and current position acquisition unit 202 are realized using inputs from the camera 81 and sensor 82, and the actuator 83 such as a motor is driven by the control output from the operation control unit 209, and the mobile mechanism 84 such as wheels is operated, thereby enabling the mobile robot 2 to move. The wireless communication unit 201 of the mobile robot 2 and the communication functions of the user terminal 1 and map utilization device 3 can be realized by the communication interface 75.

4...map utilization system, 1...user terminal, 2...mobile robot, 3...map utilization device
101...Product ordering section, 102...Destination information input section
201: wireless communication unit, 202: current position acquisition unit, 203: status acquisition unit, 204: imaging unit, 205: device information storage unit, 206: route information storage unit, 207: map information storage unit, 208: operation planning unit, 209: operation control unit
301: operation monitoring unit, 302: order information storage unit, 303: destination acquisition unit, 304: three-dimensional map information storage unit, 305: route search unit, 306: route distribution unit, 300: two-dimensional map synthesis unit, 311: map distribution unit
307: tilt information acquisition unit, 308: visual field information acquisition unit, 309: two-dimensional map creation unit, 310: multiple two-dimensional map synthesis unit

Claims (7)

A map utilization device that distributes map information along a specified route to a mobile robot so that the mobile robot can move along the specified route,
acquiring three-dimensional map information along the route as information in the vicinity of the route from the entire three-dimensional map information constructed for a field in which the mobile robot can move;
converting the three-dimensional map information along the route into two-dimensional map information corresponding to a field of view of the external environment recognition sensor based on a sensing range of the external environment recognition sensor when the mobile robot moves autonomously and an inclination of the route, and distributing the two-dimensional map information to the mobile robot ;
A map utilization device characterized in that the map utilization device is based at least on the height of an external environment recognition sensor in the mobile robot from the ground in order to convert the sensing range of the external environment recognition sensor into two-dimensional map information when the mobile robot moves autonomously. A map utilization device that distributes map information along a specified route to a mobile robot so that the mobile robot can move along the specified route,
acquiring three-dimensional map information along the route as information in the vicinity of the route from the entire three-dimensional map information constructed for a field in which the mobile robot can move;
converting the three-dimensional map information along the route into two-dimensional map information corresponding to a field of view of the external environment recognition sensor based on a sensing range of the external environment recognition sensor when the mobile robot moves autonomously and an inclination of the route, and distributing the two-dimensional map information to the mobile robot ;
A map utilization device characterized in that , in order to convert into two-dimensional map information based on the inclination of the route, when treating the inclined portion as a deemed horizontal plane, an object that extends vertically at the inclined portion is treated as extending in a direction inclined from the vertical to the deemed horizontal plane . 3. The map utilization device according to claim 1 , wherein the conversion into two-dimensional map information based on the inclination of the route is performed for each range along the route where the inclination is determined to be constant. A map utilization device according to any one of claims 1 to 3, characterized in that the conversion into two-dimensional map information based on the inclination of the route is performed for each range along the route in which the inclination is determined to be constant, and the two-dimensional map information converted for each range is synthesized to obtain two-dimensional map information along the entire route. 5. The map utilization device according to claim 1, wherein the external environment recognition sensor is a camera or a LiDAR. A map utilization device according to any one of claims 1 to 5, characterized in that when converting into two-dimensional map information based on the sensing range of an external environment recognition sensor when the mobile robot moves autonomously and the inclination of the route, the height of the sensing range is treated as changing according to the inclination of the ground along the route. 7. A program for causing a computer to function as the map utilization device according to claim 1.

Images