System for supporting field operation automation and program for supporting field operation automation

JP2023075496A5Active Publication Date: 2024-12-05BS CONSULTING CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2021188427
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2021-11-19
Publication Date
2024-12-05
Estimated Expiration
2041-11-19

AI Technical Summary

Technical Problem

Existing methods for calculating flight routes of unmanned aircraft do not efficiently utilize data on radio wave intensity and signal-to-noise ratios associated with three-dimensional position information, leading to suboptimal route planning.

Method used

A system that divides airspace into polyhedral areas, classifies them based on radio wave intensity and signal-to-noise ratios, and calculates flight routes through only flyable areas, considering departure and arrival points, time slots, and no-fly zones.

Benefits of technology

Enables more efficient and safer flight route calculation by avoiding non-flyable areas and time slots, improving usability and safety by ensuring that a predetermined number of aircraft do not overlap in the same area.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide a system or a program capable of more efficiently calculating a flight route of a flying object using data in which radio wave intensity and a signal to noise ratio are associated with three-dimensional position information.SOLUTION: A field operation automation support system 1 includes an airspace polyhedron classification processing unit 12 and a flight route calculation unit 13. Using polyhedral space information obtained by dividing an airspace by a plurality of polyhedrons and three-dimensional communication quality information in which radio wave intensity of a desired signal or a signal-to-noise ratio that is a ratio of the radio wave intensity of the desired signal and the radio wave intensity other than the desired signal are associated, and based on the three-dimensional communication quality information included in each of the polyhedrons, the airspace polyhedron classification processing unit classifies each of polyhedrons into at least two classes, a flight possible area and a flight impossible area of a flight body. The flight route calculation unit calculates a flight route passing through only the polyhedron classified as the flight possible area based on departure point information and arrival point information of the flight body.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a field work automation support system and a field work automation support program for calculating a flight route of an aircraft.

Background Art

[0002] In recent years, the use of unmanned aircraft (so-called drones) that fly by autonomous flight, remote control, or visual control has been on the rise. Currently, aerial photography applications (ranging from simple landscape photography to those for surveying, inspection, monitoring, etc.) are the most common, but efforts are also underway to utilize their transportation capabilities in various fields such as the logistics field. As such commercial use of drones progresses, it is assumed that a wireless network will be widely used for remote control of drones and transmission and reception of various data. As a practical solution, it is realistic to use a mobile phone network whose infrastructure is already comprehensively developed. Thus, although it is assumed that a mobile phone network will be used for remote control of drones and transmission and reception of various data, the current situation is that the radio wave conditions in the flight route (in the air) of drones are not well understood. Regarding such problems, a drone, a three-dimensional communication quality information generation system, and a method for acquiring three-dimensional communication quality information for three-dimensionally measuring radio wave conditions in the air are disclosed in Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to the technology described in Patent Document 1, since the signal-to-noise ratio and other data are acquired in association with three-dimensional positional information, the radio wave conditions (radio wave interference conditions) in the upper atmosphere can be obtained in three dimensions. There is a need for a more efficient method to calculate the flight routes of unmanned aerial vehicles using the data acquired in this way.

[0005] In view of the above, the present invention aims to provide a system or program that can more efficiently calculate the flight route of an aircraft using data in which radio wave intensity or signal-to-noise ratio is associated with three-dimensional position information. [Means for solving the problem]

[0006] (Composition 1) A field work automation support system for calculating the flight route of an aircraft, comprising: an airspace polyhedron airspace information which divides the airspace into areas using multiple polyhedra; a 3D communication quality information which associates the radio wave intensity of a desired signal, or the signal-to-noise ratio which is the ratio of the radio wave intensity of the desired signal to the radio wave intensity of other signals, and 3D position information, and classifies each of the polyhedra into at least two areas: an area where the aircraft can fly and an area where it cannot fly; and a flight route calculation unit which calculates a flight route that passes only through the polyhedra classified as an area where the aircraft can fly, based on the departure point information and arrival point information of the aircraft.

[0007] (Configuration 2) The field operation automation support system according to Configuration 1, characterized in that the airspace polyhedron classification processing unit classifies the polyhedrons that fall under no-fly zones as non-flyable zones based on no-fly zone information.

[0008] (Composition 3) The field work automation support system according to configuration 1 or 2, characterized in that the airspace polyhedron classification processing unit classifies the polyhedrons that fall over civilian airspace outside the flight permission area as non-flyable areas based on flight permission area information.

[0009] (Composition 4) The field operation automation support system according to any one of configurations 1 to 3, characterized in that the airspace polyhedron classification processing unit classifies the polyhedrons that fall under areas requiring permission for which permission information has not been obtained as areas where flight is not permitted, based on the area requiring permission information.

[0010] (Composition 5) A field operation automation support system according to any one of configurations 1 to 4, characterized in that the flight route calculation unit associates time information of the presence of an aircraft within each of the polyhedra corresponding to the calculated flight route with each of the polyhedra, and the airspace polyhedron classification processing unit classifies the polyhedron corresponding to the time period in which a predetermined number of aircraft are present within each of the polyhedra as an area where flight is impossible during that time period.

[0011] (Composition 6) The field work automation support system according to Configuration 1, characterized in that the flight route calculation unit sets the flight route outside the no-fly zone based on the no-fly zone information.

[0012] (Composition 7) The field work automation support system according to configuration 1 or 6, characterized in that the flight route calculation unit sets the flight route to an area outside the area corresponding to airspace over civilian areas outside the flight permit area, based on the flight permit area information.

[0013] (Composition 8) The field work automation support system according to any one of configurations 1, 6, or 7, characterized in that the flight route calculation unit sets the flight route outside of the area requiring permission information for which permission information has not been obtained, based on the area requiring permission information.

[0014] (Configuration 9) The flight route calculation unit associates time information indicating the time when the flying object exists within each of the polyhedra corresponding to the calculated flight route with each of the polyhedra. When there is a time period in which a predetermined number of flying objects exist within each of the polyhedra, the corresponding polyhedron is excluded from the setting targets of the flight route in the field work automation support system according to any one of Configurations 1, 6 to 8.

[0015] (Configuration 10) The field work automation support system according to any one of Configurations 1 to 9, wherein the polyhedron is a cube.

[0016] (Configuration 11) The field work automation support system according to Configuration 10, characterized in that it accepts designation of the size of the cube and generates the polyhedron airspace information corresponding thereto.

[0017] (Configuration 12) The field work automation support system according to any one of Configurations 1 to 11, comprising an imaging processing unit that arranges display objects corresponding to each of the polyhedra and having different display forms according to the classification on a three-dimensional map.

[0018] (Configuration 13) The field work automation support system according to Configuration 12, characterized in that the display method of the display object corresponding to each of the polyhedra on the flight route is distinguished from the display objects corresponding to the other polyhedra.

[0019] (Configuration 14) A field work automation support program is characterized in that it causes a system for calculating a flight route of an aircraft to use polyhedral airspace information obtained by dividing an airspace into a plurality of polyhedrons, three-dimensional communication quality information associated with the radio wave intensity of a desired signal or the signal-to-noise ratio which is the ratio of the radio wave intensity of the desired signal to the radio wave intensity of signals other than the desired signal, and three-dimensional position information, and based on the three-dimensional communication quality information included in each of the polyhedrons, classifies each of the polyhedrons into at least two categories: an area where the aircraft can fly and an area where the aircraft cannot fly, and calculates a flight route that passes only through the polyhedrons classified as the flyable area based on the departure point information and arrival point information of the aircraft.

Advantages of the Invention

[0020] According to the field work automation support system of the present invention, it is possible to more efficiently calculate the flight route of an aircraft by using data in which the radio wave intensity or the signal-to-noise ratio is associated with three-dimensional position information.

Brief Description of the Drawings

[0021] [Figure 1] Block diagram showing an outline of the configuration of the field work automation support system according to Embodiment 1 of the present invention [Figure 2] Flowchart showing an outline of the processing operation of the field work automation support system according to Embodiment 1 [Figure 3] Flowchart showing an outline of the processing operation of the field work automation support system according to Embodiment 1 [Figure 4] Flowchart showing an outline of the processing operation of the field work automation support system according to Embodiment 1 [Figure 5] Diagram showing an example of a display screen by the field work automation support system according to Embodiment 1 [Figure 6] Flowchart showing an outline of the processing operation of the field work automation support system according to Embodiment 2

Modes for Carrying Out the Invention

[0022] The embodiments of the present invention will be described in detail below with reference to the drawings. Note that the following embodiments are merely examples of how the present invention can be implemented, and do not limit the present invention to their scope.

[0023] <Embodiment 1> Figure 1 is a block diagram illustrating the schematic configuration of the field work automation support system according to Embodiment 1 of the present invention. The field operations automation support system 1 of this embodiment is a system for calculating the flight route of an aircraft, The calculation unit 11 controls each part and performs various calculation processes, An airspace polyhedron classification processing unit 12 uses polyhedron airspace information, which divides the airspace into areas using multiple polyhedra, 3D communication quality information which associates the radio wave intensity of a desired signal, or the signal-to-noise ratio (the ratio of the radio wave intensity of the desired signal to the radio wave intensity of other signals), and 3D position information, and classifies each polyhedron into at least two classes, an area where aircraft can fly and an area where aircraft cannot fly, or, if there is a time period in which a predetermined number of aircraft are present within each polyhedron, classifies the corresponding polyhedron as an area where aircraft cannot fly during that time period. A flight route calculation unit 13 calculates a flight route that passes only through polyhedra classified as flyable areas based on the departure and arrival point information of the aircraft, and associates the time information of the aircraft's presence within each polyhedron corresponding to the calculated flight route with each polyhedron. An imaging processing unit 14 arranges display objects corresponding to each polyhedron, with different display forms depending on the classification, on a 3D map. The input / output unit 15 is an interface that transmits and receives various types of information with other devices, A storage unit 16 that stores and retains various information, It is equipped with.

[0024] "3D communication quality information" refers to information that associates communication quality information with 3D position information. For example, information obtained by the technology disclosed in Patent Document 1 is stored in the storage unit 16. Note that the 3D communication quality information may be stored in an external storage device rather than the storage unit of this system, or it may be obtained via a network from information stored in another system (in either case, it is obtained via the input / output unit 15).

[0025] A "polyhedron" can be any solid that can fill space, and may be a single type of polyhedron such as a cube, cuboid, triangular prism, or truncated octahedron, or it may be a combination of multiple types of polyhedra, such as a combination of a regular tetrahedron and a regular octahedron. In this embodiment, a cube (not strictly a cube, but an approximation, and therefore referred to as a cube) is used as the "polyhedron," and the same code system as the regional mesh code (JIS X 0410) is used to further divide the 50m mesh code into 10 latitude and longitude units, defining a mesh (cube) in 5m units (also 5m elevation), thereby defining the "polyhedron airspace information." In other words, the "polyhedron airspace information" is defined by a code that extends the regional mesh code (JIS X 0410) (a code system similar to the regional mesh code but with an increased number of digits; hereinafter referred to as "basic mesh ID" in this specification). The "basic mesh ID" is a code that can uniquely determine the position of a 5m x 5m cube (its three-dimensional position can be identified based on the basic mesh ID).

[0026] In Figure 1, the configuration is shown separately for each function, such as the airspace polyhedron classification processing unit 12, the flight route calculation unit 13, and the image processing unit 14. However, this does not necessarily mean that the hardware is divided into these configurations. For example, the calculation unit 11 may be configured using a well-known device such as a CPU, and each configuration (each function described below) may be implemented in software. Of course, each configuration may be configured in hardware, for example, by configuring dedicated hardware such as an FPGA or ASIC that functions as all or part of the processing described below.

[0027] Figure 2 is a flowchart illustrating the processing operation of the field work automation support system 1 of this embodiment. The Field Operations Automation Support System 1 of this embodiment is a system that calculates a flight route that passes through areas with good radio wave conditions, based on input such as departure point information and arrival point information for an aircraft (including a manned aircraft) such as an unmanned aircraft (so-called drone). The Field Operations Automation Support System 1 of this embodiment is configured as a server and receives requests from user terminals (not shown in particular) via a network, etc., and calculates and presents the flight route.

[0028] In step 201, in response to a request from the user terminal, a screen prompting the user to enter necessary information is sent, and based on the user's input, departure point information, arrival point information, flight date and time information, and mesh size information are obtained. The mesh size information refers to the size of the cube as a "polyhedron" (mesh granularity) as described above. In this embodiment, the basic mesh size is 5m as the lower limit, and it can be selected from 10m, 25m, and 50m.

[0029] In the following step 202, a meshing process is performed. Figure 3 is a flowchart illustrating the general operation of the meshing process performed in step 202.

[0030] In step 301, based on the "mesh size information" obtained in step 202 in Figure 2, it is determined whether or not this is a basic mesh (5m). If the specified mesh size is not a basic mesh (i.e., it is 10m, 25m, or 50m), the process of generating a temporary mesh ID for a mesh of the specified size is performed (Step 301: No → Step 302). The "temporary mesh ID," like the basic mesh ID, is generated as an extended code of the regional mesh code (JIS X 0410) (with an increased number of digits using the same code system as the regional mesh code). This allows the system to "accept the specification of the cube size and generate polyhedron airspace information accordingly." A temporary mesh includes a base mesh; for example, a 10m temporary mesh contains 8 base meshes, and a 25m temporary mesh contains 125 base meshes. As mentioned above, it uses the same coding system as the regional mesh code, and its three-dimensional location can be identified based on the temporary mesh ID. In other words, the base meshes included in a temporary mesh can be identified from the temporary mesh ID and the base mesh ID (the temporary mesh ID and the base mesh ID are mutually correlated). If the specified mesh size is the basic mesh size (i.e., 5m), step 302 is skipped.

[0031] The loop process following step 302 (or step 301) is to perform the processes described in steps 303-305 for all temporary meshes (or basic meshes if 5m is specified) within the area. In this embodiment, the "area within the area" is defined as a rectangular area in plan view with the starting point and arrival point as the vertices of the diagonal, and the elevation is set to the highest point in the 3D communication quality information within that area, forming a rectangular parallelepiped area (see Figure 5(b)). In the loop process, steps 303 to 305 are performed sequentially on each temporary mesh (or basic mesh) within the area.

[0032] In step 303 during the loop processing, it is determined whether or not 3D communication quality information exists within the target temporary mesh (or basic mesh). As mentioned above, the 3D position can be identified based on the temporary mesh ID (or basic mesh ID), and by comparing it with the 3D communication quality information that has positional information, it is determined whether or not 3D communication quality information exists within the relevant mesh. If 3D communication quality information exists, it is classified based on a predetermined threshold (a threshold that has been set in advance), and the classification information is stored in association with a temporary mesh ID (or basic mesh ID) (the data is added to the table of the storage unit 16 (not shown, hereinafter simply referred to as "table")) (Step 303: Yes → Step 304). The classification is based on at least two criteria: whether or not the drone has the minimum radio conditions necessary to reliably send and receive control signals for remote operation (flyable area and non-flyable area). Further subdivision of the flyable area would be more useful. For example, it could define the level required to reliably send and receive audio and images, or the level required to reliably send and receive video at each image quality level (SD, HD, Full HD, 4K, 480p, 720p, 1080p), etc. If there are multiple 3D communication quality information points within the target temporary mesh (or basic mesh), the communication quality of the relevant mesh is determined and classified based on a predetermined calculation formula (for example, by taking the average of multiple data points or using the lowest value among multiple data points). If 3D communication quality information is not present in the target temporary mesh (or basic mesh), a flag indicating the absence of 3D communication quality information is stored in association with the temporary mesh ID (or basic mesh ID) (Step 303: No → Step 305). In this embodiment, meshes without 3D communication quality information are treated as no-fly areas.

[0033] After performing steps 303-305 (classification based on communication quality information) for all temporary meshes (or basic meshes) within the area, the loop process is terminated, and the meshing process is finished.

[0034] Once the meshing process (Figure 2, step 202) is complete, the flight route calculation process (step 203) is performed. Figure 4 is a flowchart illustrating the processing steps of the flight route calculation process performed in step 203.

[0035] In step 401, a meshing process (Figure 2 step 202: process in Figure 3) is performed to find the shortest flight route from the starting point to the destination point, using only temporary meshes (or basic meshes) that are classified as flyable. This process can be carried out, for example, by treating a structure consisting only of temporary meshes (or basic meshes) classified as flyable as an undirected graph and using various algorithms for the shortest path problem on that graph. Any algorithm can be used as appropriate, and its explanation is omitted here.

[0036] In step 401, the route search takes into account the relationship with the flight paths of other aircraft. Specifically, when calculating the flight route, the system calculates the time periods (time periods during which the aircraft will pass through) within each temporary mesh (or basic mesh) along the flight route, based on the initially entered flight date and time information and the calculated flight route length. It then determines whether the relevant temporary mesh (or basic mesh) during those time periods overlaps with the flight routes of other aircraft. If this condition is not met, the route is determined to be unusable, and a re-route search is performed. In this embodiment, each basic mesh ID is associated with time zone information that an aircraft will pass through, as described in steps 404 and 405 below, and stored in a table. Based on this, an entry restriction flag indicating time zones where entry is prohibited is also stored in the table. Therefore, during the time zones indicated by the entry restriction flag, the corresponding basic mesh and the temporary mesh containing this basic mesh are treated as being unflyable, thereby preventing temporary meshes (or basic meshes) in the route from overlapping with the flight routes of other aircraft.

[0037] If a flight route is obtained through the route search in step 401 (step 402: Yes), the process in steps 403-405 is moved to a loop that sequentially applies to all temporary meshes (or base meshes) along the flight route.

[0038] In step 403, the time information (including year, month, and day) through which the aircraft passes is associated with the corresponding basic mesh ID and stored in the table. "The corresponding basic mesh" refers to all basic meshes included in the corresponding temporary mesh (one of the temporary meshes that make up the flight route) when it is being processed as a temporary mesh (when the mesh size is selected to be 10m or larger), and to the corresponding basic mesh (one of the basic meshes that make up the flight route) when it is being processed as a basic mesh (when the mesh size is selected to be 5m). Even when it is being processed as a temporary mesh, if the basic mesh through which the aircraft passes can be identified in the flight route, the time information through which the aircraft passes may be associated only with that basic mesh. In addition to the time information of the aircraft's passage, aircraft information (such as the aircraft's identification ID) may also be associated with and stored in the table.

[0039] The subsequent steps 404 and 405 involve setting an entry restriction flag according to predetermined conditions. In step 404, by referring to a table, it is determined whether there are a predetermined number of aircraft or more in the corresponding time period for the basic mesh ID to which the passage time information was associated in step 403. That is, it is determined whether there are a predetermined number of aircraft or more in a 5m cube of the basic mesh at the same time. The "predetermined number" may be 1, and is determined and set in advance as appropriate. If it is determined that a predetermined number of aircraft will be present in the basic mesh at the same time, an entry restriction flag containing time zone information for the period during which entry is prohibited is stored in the table, associated with the basic mesh ID (Step 403: Yes → Step 404). Note that the "time for which entry is restricted" may be the time during which a predetermined number of aircraft are present, or it may be set to be longer than the time during which a predetermined number of aircraft are present, with a predetermined margin added.

[0040] Once the loop processing in steps 403-405 is complete, the flight route calculation process ends (step 406) with a return value indicating that the flight route has been calculated.

[0041] On the other hand, if the flight route from the departure point to the arrival point could not be calculated in step 401 (step 402: No), the process proceeds to step 407. Step 407 asks the user whether or not to reset the target area for route searching, and if so, to set the range of that area (an input screen is sent to the user's terminal). As described above, in this embodiment, the target area for route search is a rectangular area based on a diagonal line with the starting point and destination point as the two ends (see Figure 5(b)). However, if a route cannot be calculated within this area, it is possible that a route may be found by expanding the target area (a detour route may be possible). Therefore, the user is asked whether to perform a re-search with an expanded target area and to set the target area. If the area is reset, the flight route calculation process ends with the reset area range information returned as the return value (Step 407: Yes → Step 408). If the area is not reset, the flight route calculation process ends with a return value indicating that the flight route cannot be calculated (Step 407: No → Step 409). Note that instead of prompting the user to reset the target area for route search, the target area may be automatically reset based on pre-configured settings.

[0042] Once the flight route calculation process (Figure 2, step 203) is complete, the return value of the flight route calculation process is determined (step 204). If the return value is range information of the reset area, the flight route is re-searched by repeating the process from step 202 onwards described above based on that area. If the return value indicates that the flight route could not be calculated, a screen message indicating that the flight route could not be calculated is sent to the user terminal (step 206).

[0043] On the other hand, if the return value indicates that the flight route has been calculated, the system performs a process to place display objects (in this embodiment, cube displays) corresponding to the cubes of the temporary mesh (or basic mesh), which have different display forms (in this embodiment, color-coded) according to their class classification, onto the 3D map (to display the 3D map on the user terminal) (step 205). Figure 5 shows an example of the display screen that appears as a result of this process. Figure 5(a) is an example in which only the cubes corresponding to each temporary mesh (or basic mesh) along the calculated flight route are drawn from the departure point to the arrival point. Figure 5(b) shows an example where, in addition to the flight route, all cubes corresponding to each temporary mesh (or basic mesh) within the searched area are depicted. Each cube is displayed in a different color according to the mesh class, and meshes for which 3D communication quality information was not available (Figure 3: Steps 303→305) are represented as transparent. Furthermore, each cube on the flight route is displayed in a color that indicates it is a cube on the route, rather than being color-coded according to its class (the display method for the display objects corresponding to each polyhedron on the flight route is distinguished from the display objects corresponding to other polyhedra). It should be noted that the 3D map itself does not need to be owned by the Field Operations Automation Support System 1; it is sufficient to display the cubes described above on a 3D map provided by another site (of course, the Field Operations Automation Support System 1 may also have 3D map information).

[0044] As described above, the field operations automation support system 1 of this embodiment converts data, in which radio wave intensity and signal-to-noise ratio are associated with 3D position information, based on polyhedral airspace information obtained by dividing the airspace into areas using multiple polyhedra. Based on this conversion, the system calculates and displays the flight route, enabling more efficient flight route calculation and improved usability. Furthermore, in this embodiment, since the flight route is calculated so that no more than a predetermined number of aircraft enter the same mesh (polyhedron) at the same time, it is possible to calculate a safer flight route. However, in cases such as when the aircraft themselves are equipped with a function to prevent collisions with each other, it is not necessarily required to ensure that "no more than a predetermined number of aircraft enter the same mesh (polyhedron) at the same time."

[0045] <Embodiment 2> Embodiment 2 is a field operations automation support system 1 of Embodiment 1 that further calculates flight routes based on no-fly zone information, permitted flight zone information, and licensed / permitted zone information. The general configuration of the field work automation support system in this embodiment is the same as in Embodiment 1, however, the airspace polyhedron classification processing unit in this embodiment is Based on no-fly zone information, polyhedra that fall within no-fly zones are classified as areas where flight is impossible. Based on the flight permission area information, the aforementioned polyhedrons that fall over civilian airspace outside the flight permission area are classified as no-fly zones. Based on the information on areas requiring permits, the aforementioned polyhedra that fall under areas requiring permits for which permit information has not been obtained are classified as areas where flight is prohibited. Each of these will also be performed. The other components of the field work automation support system in this embodiment are the same as those in Embodiment 1, and therefore will not be described here. Furthermore, the processing operation is basically the same as in Embodiment 1, except that the meshing process in Figure 6 is executed instead of the meshing process in Figure 3. Therefore, explanations of the same processing content are omitted here.

[0046] In the meshing process of this implementation (Figure 6), steps 606 to 612 are additionally performed within a loop process that classifies each temporary mesh (or basic mesh) within the target area. Although not shown in Figure 6, steps 301 and 302 in Figure 3 are also executed before the loop processing. That is, steps 301 to 305 in Figure 3 are performed similarly in Embodiment 2, but since the content of these processes is the same as in Embodiment 1, their explanation is omitted here.

[0047] In step 606, it is determined whether the temporary mesh (or base mesh) in question falls within a no-fly zone. If it does, the process proceeds to step 607, where the no-fly flag is associated with the temporary mesh ID (or base mesh ID) and stored in the table (equivalent to classifying it as an area where flight is impossible). A no-fly zone is an area designated as a no-fly zone, such as the airspace around the National Diet Building or nuclear power plants, and the rule is to avoid setting flight routes through these areas. Information regarding no-fly zones may be maintained within the field operations automation support system, or it may be referenced from information on other sites as needed.

[0048] In step 608, it is determined whether the relevant temporary mesh (or basic mesh) falls within an area where flight permission has been obtained, such as on private land (a flight-permitted area). If it is an area where flight permission has not been obtained, the process proceeds to step 609, where the temporary mesh ID (or basic mesh ID) is associated with a flight-denial flag and stored in the table (equivalent to classifying it as an area where flight is not permitted). In the case of airspace over civilian areas, if flight permission has not been obtained for that airspace, the system will not set that area as a flight route. Information regarding flight permission areas may be held in the field operations automation support system, or it may be referenced from information on other sites as needed.

[0049] In step 610, it is determined whether the temporary mesh (or basic mesh) in question falls under an area requiring permission. If it does, the process moves to step 611 to determine whether permission information exists. If there is no permission information, the process moves to step 612, where the temporary mesh ID (or basic mesh ID) is associated with a "no flight permission" flag and stored in the table (equivalent to classifying it as an area where flight is not permitted). Areas requiring permission are areas where, for example, the airspace above densely populated areas, prior permission from the Minister of Land, Infrastructure, Transport and Tourism is required before flying an aircraft, and this prevents setting such areas as flight routes without permission. Information regarding areas requiring permission may be held in the field work automation support system, or it may be referenced from information on other sites as needed. Furthermore, the determination of whether permission is required in step 611 may be done by displaying a screen on the user terminal requesting confirmation of permission status during the processing of step 611, or by having the user input the information at the beginning (in the processing of step 201 in Figure 2), or by using a system that can search for and confirm the relevant information on another system.

[0050] Following the meshing process described above, which classifies each temporary mesh (or basic mesh) within the target area, step 401 (Figure 4) of the flight route calculation process performs a route search that passes only through temporary meshes (or basic meshes) that have been classified as flyable, as explained in Embodiment 1. Therefore, in no-fly zones, areas on private land where flight is not permitted, and areas requiring permission where permission has not been obtained, measures will be taken to prevent the establishment of flight routes.

[0051] As described above, with the field operations automation support system of this embodiment, the system processes the system so that no flight routes are set in no-fly zones, private land where flight is not permitted, and areas requiring permission where permission has not been obtained, thereby enabling the selection of more practical flight routes.

[0052] In this embodiment, the ability to select the mesh size is useful because it allows for different granularity depending on the situation (for example, when flying long distances over mountainous areas, fine precision in route selection is not required, and the mesh size can be increased). However, the present invention is not limited to this, and the mesh size may be constant. Furthermore, in this embodiment, the smallest mesh is designated as the basic mesh, while the others are designated as temporary meshes. This means that the basic mesh data is always retained (always retained in a table), while the temporary mesh data is only temporarily held during the processing. Although this processing has been described in this embodiment, the present invention is not limited to this, and for example, information may be retained as always for each mesh size (a mesh ID is defined for each mesh size, and the information is always retained by associating it with these IDs in a table or the like).

[0053] In the embodiment, the meshing process is shown as being performed as needed, but the present invention is not limited to this, and the meshing process may be performed in advance (for example, as a batch process), the results may be stored and used. Note that the processing in steps 610 to 612 concerning the licensed area in the meshing process in Figure 6 cannot be performed in advance, so if this function is used, this processing part must be performed as needed. Furthermore, as mentioned above, if data for the size of each mesh is to be continuously maintained, the meshing process may be performed in advance for each mesh, the results stored, and then used.

[0054] In this embodiment, the "3D communication quality information" is limited to that measured by a drone (acquired by the technology disclosed in Patent Document 1), so it can be said that it is guaranteed that the location where such information exists is physically accessible to a drone. In contrast, if, for example, the "3D communication quality information" includes data other than that measured by the drone, and meshing based on this data results in meshes that are physically impossible for the drone to fly, then the flight route may also be calculated using terrain information, etc. This process can be carried out using the same concept as the process for handling no-fly zones described above (simply replace the no-fly zone information with terrain information). The terrain information can be the same as the information contained in a 3D map.

[0055] In this embodiment, meshes that fall under no-fly zones, meshes that fall under private land where flight is not permitted, meshes that fall under areas requiring permission where permission has not been obtained, and meshes where a predetermined number of other drones are present are each assigned a corresponding mesh ID flag, and these meshes are excluded from route searching so that flight routes are not set in these areas. In other words, each mesh itself is given information such as whether it is a no-fly zone, but the present invention is not limited to this, and it is also possible to perform route searching to avoid no-fly zones etc. without giving each mesh itself information such as whether it is a no-fly zone. For example, instead of giving each mesh itself information such as whether it is a no-fly zone, it is also possible to perform a process to exclude no-fly zones etc. from the search area when setting the search area. [Explanation of Symbols]

[0056] 1...Field work automation support system 12...Airspace Polyhedron Classification Processing Unit 13...Flight route calculation unit 14...Image Processing Unit

Claims

1. A system for calculating a flight route of an aircraft, comprising: Polyhedral airspace information that divides airspace into multiple polyhedrons; Three-dimensional communication quality information in which the radio wave strength of a desired signal or a signal-to-noise ratio, which is the ratio of the radio wave strength of the desired signal to the radio wave strength of a signal other than the desired signal, is associated with three-dimensional position information; an airspace polyhedron classification processing unit that classifies each of the polyhedrons into at least two classes, a flyable area and an unflyable area, based on the three-dimensional communication quality information included in each of the polyhedrons using the above-mentioned method; a flight route calculation unit that calculates a flight route that passes only through polyhedrons classified as the flyable area based on departure point information and arrival point information of the aircraft; A field work automation support system comprising:

2. The field operation automation support system according to claim 1, characterized in that the airspace polyhedron classification processing unit classifies the polyhedron that corresponds to a no-fly area as an unflyable area based on no-fly area information.

3. The field operation automation support system according to claim 1 or 2, characterized in that the airspace polyhedron classification processing unit classifies the polyhedron that falls within civilian airspace outside the flight permitted area as a no-fly area based on flight permitted area information.

4. A field operation automation support system as described in any one of claims 1 to 3, characterized in that the airspace polyhedron classification processing unit classifies the polyhedron that corresponds to a permission-required area for which permission information has not been obtained as a no-fly area based on permission-required area information.

5. The flight route calculation unit associates time information of the time when the aircraft exists within each of the polyhedrons corresponding to the calculated flight route with each of the polyhedrons, A field operation automation support system as described in any one of claims 1 to 4, characterized in that, when there is a time period during which a predetermined number of flying vehicles are present within each of the polyhedrons, the airspace polyhedron classification processing unit classifies the corresponding polyhedron as an area in which flight is not possible during that time period.

6. 2. The field operation automation support system according to claim 1, wherein the flight route calculation unit sets a flight route outside the no-fly area based on no-fly area information.

7. The field operation automation support system according to claim 1 or 6, characterized in that the flight route calculation unit sets the flight route outside the area corresponding to civilian airspace outside the flight permitted area based on flight permitted area information.

8. The field operation automation support system according to any one of claims 1, 6 and 7, characterized in that the flight route calculation unit sets a flight route outside a license-required area where license information has not been obtained based on license-required area information.

9. The flight route calculation unit associates time information of the time when the aircraft exists within each of the polyhedrons corresponding to the calculated flight route with each of the polyhedrons, A field operation automation support system as described in any one of claims 1, 6 to 8, characterized in that if there is a time period during which a predetermined number of flying objects are present within each polyhedron, the corresponding polyhedron during that time period is excluded from the setting of flight routes.

10. A system for calculating the flight route of an aircraft Polyhedral airspace information that divides airspace into multiple polyhedrons; Three-dimensional communication quality information in which the radio wave strength of a desired signal or a signal-to-noise ratio, which is the ratio of the radio wave strength of the desired signal to the radio wave strength of a signal other than the desired signal, is associated with three-dimensional position information; classifying each of the polyhedrons into at least two areas, a flyable area and an unflyable area, based on the three-dimensional communication quality information included in each of the polyhedrons using the above-mentioned method; A step of calculating a flight route that passes through only the polyhedrons classified as the aviation area based on departure point information and arrival point information of the aircraft; A field work automation support program that causes the program to execute the above steps.