FLIGHT SUPPORT DEVICE, FLIGHT SYSTEM, FLIGHT SUPPORT METHOD, AND FLIGHT SUPPORT PROGRAM
The flight support device integrates flight and observation requests to dynamically adjust aircraft routes, addressing the limitation of existing systems by enabling flight paths that meet both primary flight and secondary observation needs.
Patent Information
- Application Number
- JP2021072702
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-04-22
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-04-22
AI Technical Summary
Existing flight path determination systems for aircraft, such as drones, primarily consider the original purpose of flight and fail to select routes suitable for alternative uses, such as observation, leading to inadequate support for diverse applications.
A flight support device that integrates flight request and observation request information to determine a flight path suitable for both primary flight purposes and secondary observation tasks, using sensors mounted on the aircraft to adjust flight routes based on observation requirements.
Enables the setting of flight paths that cater to purposes beyond the primary flight objective, optimizing route selection for observation tasks while ensuring efficient data acquisition.
Smart Images

Figure 0007588548000001 
Figure 0007588548000002 
Figure 0007588548000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a flight support device, a flight system, a flight support method, and a flight support program that support determining a flight path for an aircraft. [Background technology]
[0002] In recent years, remotely controlled unmanned aerial vehicles (drones) have been used for various purposes such as aerial photography and surveying, and it is expected that drones will be used in logistics in the future. Not limited to drones, aircraft that fly in response to user requests have their flight route determined in response to the user's request.
[0003] Patent Document 1 discloses a flight support system that sets routes over rivers that are free of buildings, flat, and unlikely to have people present as candidates for aircraft flight routes, and automatically selects a route over the river as the flight route if weather conditions such as lightning, hail, and thick fog, and the water level measured in the river satisfy predetermined conditions. The flight support system described in Patent Document 1 automatically sets a flight route with few obstacles by selecting routes over rivers as flight routes as much as possible. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2020-118657 A Summary of the Invention [Problem to be solved by the invention]
[0005] On the other hand, aircraft operated for purposes such as logistics, passenger transport, and aerial photography may be used for other purposes. For example, a drone for logistics may be equipped with an observation sensor, and data observed by the sensor mounted on the drone may be used. However, the technology described in Patent Document 1 has a problem in that only the original purpose of the flight is taken into consideration when setting the flight route, and it is not possible to select a flight route suitable for other purposes.
[0006] The present disclosure has been made in consideration of the above, and aims to obtain a flight support device that can set a flight path suitable for purposes other than the flight of an aircraft. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems and achieve the objectives, the flight support device according to the present disclosure is a flight support device that determines a flight route of an aircraft, and includes a flight request acquisition unit that acquires flight request information indicating a request related to the flight of the aircraft, including a departure point and a destination of the aircraft, and an observation request acquisition unit that acquires observation request information indicating a request related to observation by a sensor mounted on the aircraft; Based on the observation data period or the observation date and time corresponding to the observation request information, it is determined whether or not it is time to determine a flight route based on the observation request, and when it is determined that it is time to determine a flight route based on the observation request, Using the flight requirement information and the observation requirement information, flight requirement information corresponding to a flight that satisfies the observation requirement indicated by the observation requirement information is selected, and a flight route of the flight corresponding to the selected flight requirement information is calculated. The flight route is determined based on the flight request information and the observation request information, and a flight route of the flight corresponding to the unselected flight request information is determined based on the flight request information. When it is determined that it is not time to determine the flight route based on the observation request, the flight route of the flight corresponding to the flight request information is determined based on the flight request information. and a route determination unit that determines Effect of the Invention
[0008] According to the present disclosure, it is possible to advantageously set a flight path suitable for purposes other than the purpose of flying the aircraft. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram showing a configuration example of a flight system including a flight support device according to a first embodiment; [Diagram 2] A flowchart showing an example of a flight support processing procedure in the flight support device of the first embodiment. [Diagram 3]FIG. 1 is a diagram showing an example of flight user request information according to the first embodiment; [Figure 4] FIG. 13 is a diagram showing another example of flight user request information according to the first embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of observation user request information according to the first embodiment. [Figure 6] FIG. 13 is a diagram showing another example of observation user request information according to the first embodiment. [Figure 7] FIG. 1 is a diagram showing an example of correspondence information indicating the correspondence between an observation target and an observation data acquisition period according to the first embodiment; [Figure 8] FIG. 1 is a diagram showing an example of correspondence information indicating the correspondence between an observation target and an observation interval according to the first embodiment; [Figure 9] FIG. 1 is a diagram showing an example of correspondence information indicating the correspondence between an observation target and a data type according to the first embodiment; [Figure 10] FIG. 13 is a diagram showing an example of a range observed by the sensor according to the first embodiment when a river is specified as an observation target. [Figure 11] FIG. 1 is a diagram showing an example of each flight path of an aircraft according to the first embodiment when an observation target is a bridge. [Figure 12] A schematic diagram showing the relationship between the sensor's field of view and altitude. [Figure 13] A flowchart showing an example of a selection process procedure for flight request information corresponding to observation request information according to the first embodiment. [Figure 14] FIG. 1 is a diagram showing an example of a trunk route according to a first embodiment; [Figure 15] FIG. 1 is a diagram showing an example of a main route and a flight route according to a first embodiment. [Figure 16] FIG. 1 is a diagram showing an example of observation history information according to the first embodiment; [Figure 17] FIG. 1 is a diagram showing an example of a flight location according to the first embodiment; [Figure 18] FIG. 1 is a diagram showing an example of the configuration of a computer system that realizes a flight support device according to a first embodiment. [Figure 19] A flowchart showing an example of a flight support processing procedure in a flight support device according to a modification of the first embodiment. [Figure 20] FIG. 1 is a diagram showing a configuration example of a flight system including a flight support device according to a second embodiment. [Figure 21] A flowchart showing an example of a flight support processing procedure in a flight support device according to a second embodiment. [Figure 22] A flowchart showing an example of a procedure for setting key observation points according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Below, a flight support device, a flight system, a flight support method, and a flight support program according to embodiments will be described in detail with reference to the drawings.
[0011] Embodiment 1 1 is a diagram showing a configuration example of a flight system including a flight support device according to embodiment 1. The flight system 1 of the present embodiment includes a flight support device 2, data use user terminals 3 and 6, an aircraft flight user terminal 4, and an aircraft 5.
[0012] The aircraft 5 is, for example, a drone, but is not limited thereto, and may be either a manned or unmanned aircraft. The aircraft 5 of this embodiment can be used for purposes other than the purpose of flying the aircraft 5. The purpose of flying the aircraft 5 is, for example, logistics, aerial photography, surveying, and passengers, but is not limited thereto. The other purpose is, for example, observation by a sensor 54 mounted on the aircraft 5. Hereinafter, a case where the other purpose is observation by a sensor 54 mounted on the aircraft 5 will be described as an example. Examples of observation by the sensor 54 include, but are not limited to, river management, river observation for disaster prevention and mitigation, observation for management of facilities such as railways, observation for grasping the situation after the occurrence of a disaster, observation for grasping the environmental state, and observation for grasping the weather state. In the observation by the sensor 54, for example, periodic acquisition of data is required to grasp changes, but the request for observation is not limited to periodic acquisition, and may include a non-periodic request, such as grasping the state of a specific place after the occurrence of a disaster. The sensor 54 includes, for example, at least one of a camera that acquires images such as visible and infrared, and a laser that can acquire three-dimensional data. The sensor 54 may include, but is not limited to, at least one of a laser capable of acquiring two-dimensional and three-dimensional data, a sensor for detecting gas concentration, a wind speed sensor, a temperature sensor, and a humidity sensor.
[0013] The aircraft flight user terminal 4 is a terminal operated by a user corresponding to the purpose of the flight of the aircraft 5, and transmits flight user request information indicating a request regarding the flight of the aircraft 5 to the flight support device 2. For example, if the purpose of the flight is logistics, the aircraft flight user terminal 4 is operated by an operator who manages logistics, and if the purpose is aerial photography, the aircraft flight user terminal 4 is operated by a user who requests aerial photography. The purpose of the flight of the aircraft 5 may be single or selectable from multiple purposes. In the following, the purpose of the flight of the aircraft 5 is described as being selectable from multiple purposes by each user, but may be single, for example, the purpose of the flight of the aircraft 5 is fixed to logistics. The aircraft flight user terminal 4 may be a personal computer, a smartphone, a tablet, or the like.
[0014] The data using user terminal 3 is a terminal operated by a user who uses observation by the aircraft 5, and transmits observation user request information indicating a request for observation by the sensor 54 of the aircraft 5 to the flight support device 2. Observation by the sensor 54 may be for any of various purposes as described above. For example, when requesting observation for river management, the data using user terminal 3 is a terminal operated by an operator in an organization that is a river manager. The data using user terminal 6 is a terminal that receives data observed by the sensor 54 mounted on the aircraft 5. The data using user terminal 6 may be a terminal that is managed by the same organization as the data using user terminal 3 and processes observed data, or may be a terminal of a general user regardless of whether it is the same organization as the data using user terminal 3. Note that FIG. 1 shows an example in which both the data using user terminal 3 and the data using user terminal 6 receive data observed by the sensor 54 mounted on the aircraft 5, but either one of them may receive data observed by the sensor 54 mounted on the aircraft 5. The data using user terminals 3 and 6 may be personal computers, smartphones, tablets, etc.
[0015] In the following, in this embodiment, it is assumed that each aircraft 5 is equipped with a sensor 54 so as to be able to acquire all data of the observation data type, which is the data type requested by the observation user request information. For example, if the data type of camera images and three-dimensional data can be specified, there are multiple sensors 54, including a camera and a laser for acquiring three-dimensional data.
[0016] The flight support device 2 determines the flight route of the aircraft 5. In detail, the flight support device 2 sets a flight route suitable for the purpose of the flight of the aircraft 5 and in response to the request for observation, using the flight user request information received from the aircraft flight user terminal 4 and the observation user request information received from the data use user terminal 3. Therefore, the flight support device 2 of this embodiment can set a flight route suitable for other uses than the purpose of the flight of the aircraft 5.
[0017] In the example shown in Fig. 1, one each of the data using user terminals 3, 6 and the aircraft flying user terminal 4 is illustrated, but there is no restriction on the number of these, and there may be a plurality of each of the data using user terminals 3, 6 and the aircraft flying user terminal 4. In addition, in Fig. 1, one aircraft 5 is illustrated, but there is no restriction on the number of aircraft 5 for which the flight support device 2 can set a flight route, and there may be a plurality of aircraft 5 for which the flight support device 2 can set a flight route. Below, an example in which the flight support device 2 sets a flight route for a plurality of aircraft 5 will be described.
[0018] As shown in Figure 1, the flight support device 2 includes a flight request acquisition unit 21, a map information memory unit 22, a main route memory unit 23, a route output unit 24, an aircraft determination unit 25, a route determination unit 26, an observation request acquisition unit 27, a sensor data acquisition unit 28, a sensor data processing unit 29 and a sensor data output unit 30.
[0019] The flight request acquisition unit 21 receives flight user request information from the aircraft flight user terminal 4, and acquires flight request information by generating flight request information that includes the departure point and destination of the aircraft 5 and indicates a request regarding the flight of the aircraft 5 using the flight user request information. The flight request acquisition unit 21 outputs the flight request information to the aircraft determination unit 25 and the route determination unit 26. As described above, the flight user request information is information that indicates a request regarding the flight of the aircraft 5, and includes at least a destination and flight request identification information. The flight request identification information is identification information for identifying a flight request, and may be assigned by the aircraft flight user terminal 4, or may be assigned after the flight request acquisition unit 21 receives the flight user request information. When the flight request acquisition unit 21 assigns the flight request identification information, the flight request acquisition unit 21 notifies the data usage user terminal 3 of the flight request identification information. The flight request information is information used to determine the aircraft 5 and the flight route corresponding to the flight user request information. Details of the flight user request information and the flight request information will be described later.
[0020] The map information storage unit 22 stores map information within a range in which the aircraft 5 is expected to fly. The main route storage unit 23 stores information indicating main routes, which are the main routes along which the aircraft 5 flies. The main routes are routes within a range stored in the map information storage unit 22 and are set in advance. The main routes are routes suitable for the flight of the aircraft 5 and are routes on which the aircraft 5 is heavily trafficked. Specifically, for example, when the aircraft 5 is a drone, the main route is at least one of an airspace above a river and an airspace above a railway line. When the aircraft 5 is a manned aircraft, the main route is, for example, a route that is determined as a major air route. In addition, for example, when the aircraft 5 is a drone, the main route may include a route above a highway that is closed to traffic during a disaster or the like, or a route above power lines.
[0021] The observation request acquisition unit 27 receives the observation user request information from the data using user terminal 3, and acquires the observation request information by generating observation request information indicating a request for observation by the sensor 54 mounted on the aircraft 5 using the observation user request information. The observation request acquisition unit 27 outputs the observation request information to the route determination unit 26. As described above, the observation user request information is information indicating a request for observation by the sensor 54 of the aircraft 5, and includes at least the observation target, i.e., information indicating the observation target, and observation request identification information. The observation request identification information is identification information for identifying the observation request, and may be assigned by the data using user terminal 3, or may be assigned by the observation request acquisition unit 27 after receiving the observation user request information. When the observation request acquisition unit 27 assigns the observation request identification information, the observation request acquisition unit 27 notifies the data using user terminal 3 of the observation request identification information. The observation request information is information used to select flight request information used to execute the corresponding observation request. Details of the observation user request information and the observation request information will be described later.
[0022] The aircraft determination unit 25 uses the flight request information received from the flight request acquisition unit 21 to determine the aircraft 5 to be assigned to the request corresponding to the flight request information, and notifies the route output unit 24 of the determination result. The route determination unit 26 uses the flight request information and the observation request information to select flight request information corresponding to a flight that satisfies the observation request indicated by the observation request information, and determines the flight route of the flight corresponding to the selected flight request information. In detail, the route determination unit 26 uses the flight request information received from the flight request acquisition unit 21 and the observation request information received from the observation request acquisition unit 27 to select flight request information to be used to execute the observation request, and determines a flight route and departure time that satisfies the request corresponding to the selected flight request information and satisfies the corresponding observation request, and notifies the route output unit 24 of the determination result together with the corresponding observation request identification information and the identification information of the aircraft 5 assigned to the observation request identification information. The route determination unit 26 includes a flight request information determination unit 261 and a flight route determination unit 262. The operations of the flight request information determination unit 261 and the flight route determination unit 262 will be described later.
[0023] The route output unit 24 transmits a flight route corresponding to the flight request information to the aircraft 5 assigned to the request corresponding to the flight request information, based on the determination result by the aircraft determination unit 25 and the determination result by the route determination unit 26. In addition, the route output unit 24 notifies the sensor data processing unit 29 of the observation request identification information, the identification information of the aircraft 5 assigned to the observation request identification information, the flight route, and the departure time. Note that identification information indicating the flight to be flown may be used instead of the departure time.
[0024] The sensor data acquisition unit 28 receives sensor data from the aircraft 5, which is data observed by the sensors 54, and outputs the received sensor data together with the identification information and information indicating the departure time of the aircraft 5 to the sensor data processing unit 29. The sensor data processing unit 29 associates the sensor data received from the sensor data acquisition unit 28 with the observation request identification information notified by the route output unit 24 based on the identification information and departure time of the aircraft 5, and outputs the sensor data associated with the observation request identification information to the sensor data output unit 30.
[0025] The sensor data output unit 30 transmits the sensor data together with the observation request identification information to the data using user terminal 3. When a plurality of data using user terminals 3 are provided, the observation request acquisition unit 27 holds the correspondence between the data using user terminal 3 that is the transmission source of the observation user request information and the observation request identification information, and the correspondence between the data using user terminal 3 and the observation request identification information is also notified to the sensor data output unit 30 from the observation request acquisition unit 27 via the route determination unit 26 and the route output unit 24. Alternatively, the correspondence between the data using user terminal 3 and the observation request identification information may be directly notified to the sensor data output unit 30 from the observation request acquisition unit 27. The sensor data output unit 30 may transmit the sensor data to the data using user terminal 6. As described above, since it is sufficient to transmit the sensor data to at least one of the data using user terminal 3 and the data using user terminal 6, the sensor data output unit 30 may transmit the sensor data to either the data using user terminal 3 or the data using user terminal 6.
[0026] As shown in Fig. 1, the aircraft 5 includes a route acquisition unit 51, a control unit 52, a sensor data output unit 53, and a sensor 54. Note that the aircraft 5 also includes components not shown, such as mechanisms necessary for flight, but Fig. 1 illustrates the components related to the determination of the flight route in this embodiment.
[0027] The route acquisition unit 51 receives a flight route from the flight support device 2 and outputs the received flight route to the control unit 52. The control unit 52 uses the flight route received from the route acquisition unit 51 to control the flight of the aircraft 5 and instructs the sensor 54 to acquire data. The sensor 54 performs observation based on the instruction from the control unit 52 and outputs sensor data obtained by the observation to the sensor data output unit 53. The sensor data output unit 53 transmits the sensor data together with identification information of the aircraft 5 to the flight support device 2.
[0028] Next, the operation of the flight support device 2 of this embodiment will be described. FIG. 2 is a flowchart showing an example of a flight support processing procedure in the flight support device 2 of this embodiment. The flight request acquisition unit 21 performs the processing shown in FIG. 2, for example, at regular intervals. The flight request acquisition unit 21 creates a flight plan for the aircraft 5 for a certain period from the start time to the certain period ahead, for example, with the time after the preparation time Δt from that point as the start time. That is, the flight request acquisition unit 21 determines the flight route of the aircraft 5 from the start time to the certain period ahead at regular intervals. The certain period is, for example, one hour or half a day, but may be appropriately determined according to the frequency of occurrence of flight user request information in the flight system 1, the request for the frequency of acquisition of observation data in the observation user request information, and the like.
[0029] As shown in FIG. 2, the flight support device 2 acquires flight request information including a departure point and a destination (step S1). In detail, the flight request acquisition unit 21 receives flight user request information from the aircraft flight user terminal 4, and acquires flight request information by generating flight request information using the flight user request information, and extracts flight request information having a departure time within a certain period from the start time from the flight request information, and outputs it to the aircraft determination unit 25 and the route determination unit 26. The flight request acquisition unit 21 holds flight request information that has not been output to the aircraft determination unit 25 and the route determination unit 26. Since flight request information such as a request for a flight several days or more in the future may receive flight request information that is quite far in the future, in this case, if the date and time of the flight request is later than the target for creating the plan, the processing of the request will be performed later. Note that the flight request acquisition unit 21 is not limited to this, and may output all flight request information acquired within a certain period to the aircraft determination unit 25 and the route determination unit 26 at regular intervals, and temporarily determine the aircraft 5 and flight route, and change them based on the observation user request information.
[0030] FIG. 3 is a diagram showing an example of flight user request information of this embodiment. In the example shown in FIG. 3, the flight user request information includes flight request identification information, departure point, destination, schedule, and purpose information. The purpose information is information indicating the type of flight purpose. FIG. 3 illustrates flight user request information transmitted from an aircraft flight user terminal 4 of a user for logistics purposes. The flight user request information is information indicating a flight request for logistics. When logistics is the purpose, the aircraft 5 needs to be located on the ground at the departure point and destination in the flight user request information, so the departure point and destination in the flight user request information affect the departure point and destination of the aircraft 5, but the degree of freedom regarding the flight route of the aircraft 5 is high.
[0031] FIG. 4 is a diagram showing another example of the flight user request information of this embodiment. In the example shown in FIG. 4, similar to the example shown in FIG. 3, the flight user request information includes flight request identification information, departure point, destination, schedule, and purpose information. FIG. 4 illustrates flight user request information transmitted from an aircraft flight user terminal 4 of a user who aims to carry out surveying. When the purpose is surveying, as shown in FIG. 4, the destination may be specified within the range to be surveyed. When the purpose is surveying, the aircraft 5 needs to fly above the location to be surveyed, so the flight support device 2 will determine a flight route to fly above the destination.
[0032] In the examples shown in FIG. 3 and FIG. 4, the flight user request information includes flight request identification information, departure point, destination, schedule, and purpose information, but the flight user request information is not limited to these, and may include at least the destination and request identification information. For example, when the departure point is not specified, or when the departure point is fixed, such as a specific parking area for the aircraft 5, the flight user request information may not include the departure point, and when the purpose information is single, the flight user request information may not include the purpose information. In addition, when a rule regarding the date and time is set, such as flying as soon as possible after receiving the flight user request information, the flight user request information may not include the schedule. In addition, instead of the schedule, a day or date and time may be included. In addition, the flight user request information may include a required value of the load weight of the aircraft 5.
[0033] The flight request information generated by the flight request acquisition unit 21 may be the same as or different from the flight user request information. For example, when the destination is not specified in the flight user request information, a departure point suitable for the destination may be selected from among the parking lots of multiple aircraft 5, and the selected departure point may be included in the flight request information. Also, when the schedule is not specified in the flight user request information, a schedule may be determined based on the date and time when the flight user request information is received, and the determined schedule may be included in the flight request information.
[0034] Returning to the explanation of Fig. 2, the flight support device 2 acquires observation request information including an observation target and an acquisition cycle, i.e., an observation data acquisition cycle (step S2). In detail, the observation request acquisition unit 27 receives the observation user request information from the data using user terminal 3, acquires the observation request information by generating observation request information using the observation user request information, and outputs the observation request information to the route determination unit 26. The observation request acquisition unit 27 outputs all the observation request information acquired after outputting the observation request information to the route determination unit 26 in the previous process to the route determination unit 26.
[0035] Fig. 5 is a diagram showing an example of observing user request information of this embodiment. In the example shown in Fig. 5, the observing user request information includes observing request identification information and an observation target. In the example shown in Fig. 5, the observation target is river A. In this manner, the observation target may include a river.
[0036] FIG. 6 is a diagram showing another example of the observation user request information of this embodiment. In the example shown in FIG. 6, the observation user request information includes observation request identification information, observation target, observation data acquisition period, and data type. In the example shown in FIG. 6, the observation target is a bridge H of a river B, and the observation data acquisition period is one week, that is, data acquisition is performed once per week. The data type indicates the type of data that is requested to be acquired among the data that can be acquired by the sensor 54 mounted on the aircraft 5. In the example shown in FIG. 6, acquisition of three-dimensional data is requested, and a request is also set for the acquisition conditions as shown in parentheses after the three-dimensional data. In the example shown in FIG. 6, it is requested that the bridge H of the river B be observed downward and upward in the wide-area mode and the high-resolution mode to acquire data, and that the bridge H be observed downward in the high-resolution mode to acquire data. The wide-area mode and the high-resolution mode can be changed by changing the altitude of the aircraft 5, as described later. If the sensor 54 itself has multiple observation modes, the data type may include a designation of the mode of the sensor 54. The upward and downward directions may be changed by changing the mounting position and orientation of the sensor 54 before the flight of the aircraft 5, or a sensor 54 may be used that allows the center direction of the field of view to be changed.
[0037] The examples shown in Fig. 5 and Fig. 6 are merely illustrative, and the observation user request information is not limited to the examples shown in Fig. 5 and Fig. 6 as long as it includes at least an observation target. The observation user request information may include a date and time and a period for requesting observation instead of the observation data acquisition cycle. The observation target in the observation user request information may be specified in units of rivers as shown in Fig. 5, or may be specified as a bank, a bridge, an island, an obstacle in a river (presence or absence), a railway track, a railway overhead line, a railway bridge, an obstacle in a railway track (presence or absence), or the like. The observation target may be specified as an observation point such as latitude and longitude, or may be specified as an observation section, or both the observation target and the observation section may be specified.
[0038] The observation request information generated by the observation request acquisition unit 27 may be the same as or different from the observation user request information. For example, when the observation user request information includes an observation target and observation request identification information as illustrated in Fig. 5, the observation request acquisition unit 27 may determine at least one of the observation data acquisition cycle, the observation interval, and the data type according to the observation target, and include the determined information in the observation request information.
[0039] When the observation request acquisition unit 27 determines the observation data acquisition period based on the observation target, the observation request acquisition unit 27 holds in advance correspondence information indicating the correspondence between the observation target and the observation data acquisition period. Fig. 7 is a diagram showing an example of correspondence information indicating the correspondence between the observation target and the observation data acquisition period in this embodiment. As shown in Fig. 7, for example, if the observation target is a levee or a river, the observation data acquisition period is set to one week, if the observation target is a change in an island, the observation data acquisition period is set to one month, and if the observation target is a railway overhead line, the observation data acquisition period is set to one day. Note that Fig. 7 is an example, and the correspondence between a specific observation target and the observation data period is not limited to the example shown in Fig. 7.
[0040] When the observation request acquisition unit 27 determines the observation interval based on the observation target, the observation request acquisition unit 27 holds in advance correspondence information indicating the correspondence between the observation target and the observation interval. FIG. 8 is a diagram showing an example of correspondence information indicating the correspondence between the observation target and the observation interval in this embodiment. As shown in FIG. 8, for example, the observation interval is determined according to the observation target, such as the bank of River A corresponding to the observation interval from point x to point y of River A. The observation interval may be specified by a feature point or structure on a map such as a bridge or a confluence, or may be specified by latitude and longitude. Note that FIG. 8 is an example, and the correspondence between the specific observation target and the observation interval is not limited to the example shown in FIG. 8.
[0041] When the observation request acquisition unit 27 determines the data type based on the observation target, the observation request acquisition unit 27 holds in advance correspondence information indicating the correspondence between the observation target and the data type. FIG. 9 is a diagram showing an example of correspondence information indicating the correspondence between the observation target and the data type in this embodiment. As shown in FIG. 9, the data type is determined according to the observation target, for example, three-dimensional data for a levee and camera images for changes in an island. Note that if no direction is specified in parentheses, it is assumed that the observation is downward. Note that FIG. 9 is an example, and the correspondence between the specific observation target and the data type is not limited to the example shown in FIG. 9.
[0042] 7, 8, and 9 may be input to the flight support device 2 by an operator using an input means (not shown) and set, or may be transmitted from another device (not shown) to the flight support device 2 and set, or may be transmitted from the data using user terminal 3 to the flight support device 2 and set. In addition, the correspondence information may be changeable by input to the flight support device 2, an instruction from the data using user terminal 3, or an instruction from another device (not shown).
[0043] Returning to the explanation of FIG. 2, the flight support device 2 judges whether it is the timing to determine a flight route based on an observation request (step S3). In detail, when the observation data acquisition period is set in the observation request information previously received from the observation request acquisition unit 27, the route determination unit 26 judges that it is the timing to determine a flight route based on an observation request when the elapsed time from tp becomes tr-Δt, where tp is the date and time when the previous data was acquired and tr is the observation data acquisition period. The observation request information previously received from the observation request acquisition unit 27 is not limited to the observation request information received in the most recent certain period, but also includes the observation request information received before that, which requested periodic acquisition of observation data. Note that, as described later, the date and time when the observation was performed is recorded. Δt is set in advance according to the time required from the determination of the flight route to the flight. In addition, when the observation date and time is specified in the observation request information, the flight support device 2 judges that it is the timing to determine a flight route based on an observation request when the time is Δt before the observation date and time.
[0044] If it is the flight route determination timing based on the observation request (step S3 Yes), the flight support device 2 selects flight request information capable of acquiring observation data satisfying the observation request information based on the observation request information and the flight request information (step S4). Specifically, the flight request information determination unit 261 of the route determination unit 26 selects flight request information capable of acquiring observation data satisfying the observation request information based on the observation request information and the flight request information. More specifically, the flight request information determination unit 261 uses the departure point and destination included in the flight request information to determine a main route section that is a section used in the flight among the main routes used in the flight corresponding to the flight request information, and selects one or more flight request information that can observe the observation target by flying the determined main route section as flight request information that satisfies the observation request indicated by the observation request information. Details of step S4 will be described later. Note that the flight request information considered in step S4 includes flight request information received within a certain period of time that the route determination unit 26 received from the flight request acquisition unit 21 in step S1, but also includes flight request information received before that and for which a flight route was once determined.
[0045] Next, the flight support device 2 determines a flight route based on the observation request information and the selected flight request information (step S5). In detail, the flight route determination unit 262 of the route determination unit 26 determines a flight route and departure time based on the flight request information selected in step S4 and the observation request information, and notifies the route output unit 24 of the determined flight route in association with the flight request identification information and the observation identification information. Details of step S5 will be described later.
[0046] Next, the flight support device 2 determines a flight route based on the flight requirement information that was not selected (step S6). In detail, the flight route determination unit 262 of the route determination unit 26 determines a flight route and a departure time based on the flight requirement information that was not selected in step S4. There is no particular restriction on the method of determining the flight route based on the flight requirement information, and the flight route is determined according to the departure point and destination in the flight requirement information.
[0047] Next, the flight support device 2 determines an aircraft 5 that executes the flight request based on the flight request information and the flight route (step S7). In detail, the aircraft determination unit 25 determines an aircraft that executes the flight request by selecting an aircraft 5 that corresponds to the flight request information using the flight request information. In more detail, the aircraft determination unit 25 holds aircraft operation information indicating specifications such as the loaded weight of each aircraft 5 and an operation plan, and determines an aircraft that executes the flight request by selecting an aircraft 5 that is suitable for the flight request information and the flight route from among the aircraft 5 that can operate at the departure time based on the aircraft operation information, the flight request information, the flight route, and the departure time, and notifies the route output unit 24 of the determined aircraft 5 in association with the flight request identification information of the flight request information. For example, the aircraft determination unit 25 selects an aircraft 5 that satisfies the loaded weight requirement included in the flight request information and can fly a distance corresponding to the flight route from among the aircraft 5 that can operate at the departure time.
[0048] Next, the flight support device 2 transmits the flight route to the determined aircraft 5 (step S8). In detail, the route output unit 24 associates the aircraft 5 determined by the aircraft determination unit 25 with the flight route determined by the route determination unit 26 using the flight request identification information, and transmits the flight route corresponding to the aircraft 5 to the aircraft 5. In addition, the route output unit 24 notifies the sensor data processing unit 29 of the identification information, departure time, and observation request identification information of the corresponding aircraft 5 for the flight request identification information associated with the observation request identification information.
[0049] Next, the flight support device 2 acquires sensor data acquired from the aircraft 5 (step S9). In detail, the sensor data acquisition unit 28 receives the sensor data acquired by the sensor 54 mounted on the aircraft 5 from the aircraft 5, and outputs the received sensor data to the sensor data processing unit 29 together with the identification information and departure time of the aircraft 5.
[0050] Next, the flight support device 2 transmits the acquired sensor data in association with the observation request information (step S10), and ends the process. In detail, the sensor data processing unit 29 uses the identification information, departure time, and observation request identification information of the aircraft 5 notified from the route output unit 24 to associate the sensor data received from the sensor data acquisition unit 28 with the observation request identification information, and transmits the sensor data together with the observation request identification information to the data utilization user terminal 3 corresponding to the observation request identification information.
[0051] If the answer is No in step S3, the flight support device 2 determines a flight route based on the flight request information (step S11) and proceeds to step S7. In detail, in step S11, the flight route determination unit 262 of the route determination unit 26 determines a flight route based on the flight request information, similar to step S6.
[0052] Note that steps S9 and S10 may be performed in parallel with the processing of steps S1 to S8 and S11. The processing of steps S1 to S8 and S11 is processing for creating a plan and notifying the aircraft 5 of the plan, and steps S9 and S10 are processing during or after the flight of the aircraft 5, so depending on the time from the notification of the plan to the flight, it is possible that the next plan creation processing will be performed before acquiring sensor data. Therefore, these two processes may be performed in parallel.
[0053] Here, the main route and acquisition of observation data in this embodiment will be described. As described above, the main route is a route with a lot of traffic of aircraft 5, and in the case where the aircraft 5 is a drone, it is, for example, above a river. For example, when the airspace above a river is used as a main route, if a drone for the purpose of logistics frequently flies above the river, observation data suitable for monitoring the river can be obtained.
[0054] FIG. 10 is a diagram showing an example of a range observed by the sensor 54 of this embodiment when a river is specified as an observation target. FIG. 10 shows an example of an observation range when the aircraft 5 is a drone and observes a river by flying over the river. In the example shown in FIG. 10, a left bank embankment 202 is provided on the left side of the river water 201 flowing in the observation target river, and a right bank embankment 203 is provided on the right side of the river water 201. In FIG. 10, the back of the paper is the river mouth direction, the embankment provided on the left side toward the river mouth direction is the left bank embankment 202, and the embankment provided on the right side toward the river mouth direction is the right bank embankment 203. By having the aircraft 5 fly over the sky near the center of this river, the observation range shown in FIG. 10 is observed sequentially as the aircraft 5 flies, and observation data can be obtained over the entire river. Therefore, in this embodiment, when a flight route corresponding to a flight request is determined using flight request information, the flight route is determined to include a main route that matches the observation request information, and data for monitoring the river can be obtained by utilizing the aircraft 5 flying based on the flight request information. For example, a drone for logistics can be used to obtain observation data that meets the needs of a user requesting observation of a river, separate from the logistics user. This can reduce operating costs and energy consumption compared to flying a drone for logistics and a drone for river monitoring separately.
[0055] In addition, there is a degree of freedom in terms of the altitude at which the aircraft flies along the main route, and in terms of the location within the width of the main route when the main route is wide, so in this embodiment, it is possible to specify the flight location on the main route.
[0056] FIG. 11 is a diagram showing an example of each flight path of the aircraft 5 in this embodiment when the observation target is a bridge. In the example shown in FIG. 11, the observation target is a bridge 204 over a wide river, and the sky above the river is set as the main route. The sensor 54 is a sensor that acquires two-dimensional images, two-dimensional data, or three-dimensional data. In the example shown in FIG. 11, a flight path 301 passing over the bridge 204 near the center of the river width, a flight path 302 passing over the bridge 204 to the left of the center of the river width, and a flight path 303 passing over the bridge 204 to the right of the center of the river width are shown. In FIG. 11, the back of the page is the river mouth direction, and the left side facing the river mouth direction is the "left". In the case of a large bridge 204, the sensor 54 may not be able to observe the entire bridge 204 in one flight. In such a case, the entire bridge 204 can be observed in three flights corresponding to the flight paths 301, 302, and 303. For example, if the observation data acquisition period for bridge 204 is one week, then the observation request will be satisfied if each of flight paths 301, 302, and 303 is flown during that week.
[0057] 11 shows not only the sky above the bridge 204, but also flight paths 304, 305 that pass under the bridge 204. If there is a request to observe the bridge 204 from below looking upward, the observation request can be met by setting flight paths 304, 305 that pass under the bridge 204 in this way.
[0058] Although altitude is not shown in Fig. 11, even if the field of view of the sensor 54 is the same, the observation range changes depending on the flying altitude of the aircraft 5. Fig. 12 is a diagram showing a schematic diagram of the relationship between the field of view of the sensor and altitude. In Fig. 11, it has been described that the flight path 301 has the same altitude as the flight paths 302 and 303, but in the example shown in Fig. 12, the flight path 301 has a higher altitude than the flight path 302.
[0059] When flying along the flight path 301, the field of view 401 of the sensor 54 mounted on the aircraft 5 includes almost the entire bridge 204, but when flying along the flight path 302, the field of view 402 of the sensor 54 mounted on the aircraft 5 includes only a portion of the bridge 204 to the left of the center. On the other hand, when flying along the flight path 302, the bridge 204 can be observed closer than when flying along the flight path 301, so the resolution is higher. Therefore, by defining a wide-area mode for observing a wide area at a high altitude and a high-resolution mode for observing at a low altitude with high resolution as observation modes, determining altitudes corresponding to each mode, and setting the altitude according to an observation request, data according to an observation request can be provided. The observation mode may be set by observation user request information, or the observation mode may be appropriately defined as a data type for each observation target as exemplified in FIG. 9, and the observation request acquisition unit 27 may determine the observation mode as a data type according to the observation target. The number of observation modes is not limited to two, and three or more observation modes with different altitudes may be defined. In this manner, the information specifying the wide area mode or the high resolution mode is information regarding the altitude of the aircraft 5.
[0060] 12, flight path 304 is a path that flies under bridge 204, and the observation direction is upward as shown by field of view 404. In this way, the mode for observing upward is also defined as an observation mode. Here, three observation modes can be set: downward wide-area mode, downward high-resolution mode, and upward high-resolution mode, but in the case of upward observation, high-resolution mode and wide-area mode can also be set separately.
[0061] In this embodiment, since the flight path is set according to the observation request as described above, it is possible to perform observations suitable for various observation requests. Although a river is used as an example in the above example, even if the main route is above a railway line, above a closed highway, above power lines, etc., it is possible to set a flight path with the altitude and width direction position specified within the main route.
[0062] Next, the selection process of the flight request information corresponding to the observation request information shown in step S4 will be described. FIG. 13 is a flowchart showing an example of the selection process procedure of the flight request information corresponding to the observation request information of this embodiment. As shown in FIG. 13, the flight request information determination unit 261 of the route determination unit 26 uses the requested flight section, map information, and the main route to determine the main route and the main route section which is the section to be flown on the main route (step S21). The requested flight section is the section from the departure point to the destination included in the flight request information. Note that, for example, when surveying or aerial photography is specified as the purpose information, multiple destinations may be specified. In this case, the flight request information determination unit 261 determines the main route and the main route section which is the section to be flown on the main route so as to pass through multiple destinations. Similarly, the destination may be specified by a section. In this case, the flight request information determination unit 261 determines the main route and the main route section which is the section to be flown on the main route so as to pass through multiple destinations.
[0063] FIG. 14 is a diagram showing an example of a trunk route in this embodiment. In the example shown in FIG. 14, five trunk routes, trunk routes 81 to 85, are included in the range corresponding to the map information. In the example shown in FIG. 14, the trunk routes 81 to 83 shown by dashed lines are routes above rivers, and the trunk routes 84 and 85 shown by dashed lines are routes above railway tracks. The flight request information determination unit 261 selects, for example, a trunk route suitable for the requested flight section from among these five trunk routes 81 to 85. For example, a trunk route with the smallest difference from a route connecting the departure point to the destination in a straight line may be selected, or a priority order may be determined in advance between the trunk routes 81 to 85, and the trunk route may be set based on a value obtained by weighting and adding the difference from a route connecting the departure point to the destination in a straight line and the priority order. In addition, the flight request information determination unit 261 may calculate the flight distance when flying a route from the departure point to the destination using each of the trunk routes 81 to 85, and select the trunk route with the shortest flight distance. The method of selecting the trunk route is not limited to the above.
[0064] When the flight request information determination unit 261 selects a trunk route, it determines a trunk route section, which is a section to be flown within the trunk route. FIG. 15 is a diagram showing an example of a trunk route and a flight route of this embodiment. The example shown in FIG. 15 shows a trunk route and a trunk route section corresponding to two flight request information, namely, flight request information requesting flight from a departure point 91 to a destination point 92, and flight request information requesting flight from a departure point 95 to a destination point 96.
[0065] 15, for a flight from a departure point 91 to a destination 92, a trunk route 81 is selected, and a trunk route section 93 is determined as the section to be flown of the selected trunk route 81. Also, for a flight from a departure point 95 to a destination 96, a trunk route 85 is selected, and a trunk route section 97 is determined as the section to be flown of the selected trunk route 85.
[0066] Returning to the description of FIG. 13, the flight request information determination unit 261 then selects flight request information suitable for the observation request information based on the observation section included in the observation request information and the main route section corresponding to the flight request information (step S22), and ends the process. In detail, the flight request information determination unit 261 selects flight request information corresponding to the main route section including at least a part of the position of the observation target in the observation section included in the observation request information. As described above, the observation section included in the observation request information may be specified by the observation user request information, or may be set by the observation request acquisition unit 27. Also, if the observation section is not specified in the observation request information and the point of the observation target is specified, in step S22, the flight request information determination unit 261 selects flight request information suitable for the observation request information based on the point of the observation target.
[0067] For example, in the example shown in FIG. 15, the observation section start point 99 to the observation section end point 100 in the river corresponding to the main route 81 is specified as the observation target. As shown in FIG. 15, the main route section 93 of the main route sections 93 and 97 includes this observation section. In this case, the flight request information determination unit 261 selects the flight request information corresponding to the main route section 93 as the flight request information corresponding to the observation request information that specifies the observation section. In the example shown in FIG. 15, the main route section 93 includes all of the observation sections specified in the observation request information, but there may be no main route section that includes all of the observation sections specified in the observation request information in the main route section. For example, when there is observation request information that specifies the entire river corresponding to the main route 81 as the observation target, a part of the observation target is observed in the main route section 93. In such a case, the flight request information determination unit 261 selects multiple flight request information so as to realize the observation of the entire observation target by combining multiple main route sections that include only a part of the observation section. That is, although not shown in Fig. 15, for example, the flight request information determination unit 261 selects flight request information corresponding to a trunk route section including a portion of the trunk route 81 other than the trunk route section 93, for example, a plurality of flight request information in which the trunk route section is a route upstream and downstream of the trunk route section 93 of the trunk route 81. Also, when a plurality of data types are specified in the observation request information, the flight request information determination unit 261 may select a plurality of flight request information as the flight request information corresponding to the observation request information.
[0068] In addition, although the above example shows geographical conditions, the flight request information determination unit 261 also considers time constraints. In detail, in step S22, flight request information is selected from flight request information in which the difference between the observation date and time requested in the observation request and the date and time in the flight request information is within a threshold value, using the date and time included in the observation request information or the observation data acquisition cycle included in the observation request and the managed observation history information. Also, depending on the observation data acquisition cycle, it is sufficient to acquire data of multiple data types at multiple plan creation timings, so a process of selecting one flight request information corresponding to the observation request information at one plan creation timing and selecting one flight request information corresponding to the observation request information at the next plan creation timing may be repeated.
[0069] FIG. 16 is a diagram showing an example of the observation history information of this embodiment. The flight request information determination unit 261 holds the observation history information exemplified in FIG. 16 for each observation request information corresponding to periodic observation, that is, for each observation request information in which an observation data acquisition cycle is set. As shown in FIG. 16, the observation history information includes observation request identification information, the observation data acquisition cycle, and the previous observation data acquisition date and time indicating the date and time when the previous observation was performed. In addition, in the example shown in FIG. 16, since multiple data types are specified in the corresponding observation request, the date and time when the previous observation was performed is stored for each data type. In this way, the flight request information determination unit 261 manages the date and time when the previous observation was performed, and selects the flight request information corresponding to the observation request information by treating the time when the elapsed time from the previous observation reaches the observation data acquisition cycle as the observation request time. As shown in FIG. 16, when multiple data types are set, the flight request information determination unit 261 selects the flight request information corresponding to the observation request information so that data is acquired at the observation data acquisition cycle for each data type.
[0070] Next, a method for determining the flight route in step S5 will be described. As illustrated in FIG. 11 and FIG. 12, there may be a degree of freedom regarding which position at which altitude to fly on the main route, and depending on the required observation mode, it may also be necessary to specify the altitude. Therefore, in step S5, a flight route is determined in which the position and altitude to fly when flying the main route section are specified as flight points based on the observation target and the required observation mode. That is, the route determination unit 26 determines the flight route such that the flight route corresponding to the flight request information that satisfies the observation request indicated by the observation request information includes the flight point that satisfies the observation request. Note that if there is no request for the position, there is no need to specify the position, and if there is no request for the altitude, there is no need to specify the altitude.
[0071] FIG. 17 is a diagram showing an example of a flight location in this embodiment. For example, as shown in FIG. 17, a flight location is determined for each observation target as shown in FIG. 17, and the flight route determination unit 262 holds correspondence information indicating the correspondence between the observation target and the flight location, and the flight route determination unit 262 determines the flight location by referring to the correspondence information according to the observation target. For example, in the example shown in FIG. 17, when the entire river A is the observation target, since the first section, which is the upstream section, has a narrow river width, the entire first section is observed by flying near the center of the main route, which is the river, at an altitude of h1 km, and since the second section downstream of the first section has a wider river width, the width of the main route, which is the river, is divided into three, the center, the left route, and the right route, and observation is performed on a flight route including three flight locations. Note that, as described above, when the observation mode is specified by the observation user request information, the flight route determination unit 262 determines the flight location according to the observation request information by determining the altitude for each observation mode.
[0072] When there are multiple flight locations corresponding to the observation target for the flight request information selected by the flight request information determination unit 261, the flight route determination unit 262 selects one of the multiple flight locations where observation has not been performed within the observation data acquisition period, and determines a flight route specified to fly over the selected flight location. Note that, when the observation mode is taken into consideration in the selection of flight request information in the flight request information determination unit 261 described above, the flight route determination unit 262 specifies an altitude according to the observation mode. Through the above processing, a flight route based on the observation request indicated by the observation request information can be set.
[0073] In the above example, the flight location is on the main route, but the flight location may be set on a location other than the main route. For example, when observing a specific location during a disaster, the flight support device 2 may set an arbitrary location designated as an observation target as a flight location, and when determining a main route section determined based on the flight request information, select a main route section close to the flight location, and determine a flight route so as to observe the flight location by flying away from the main route section temporarily. In addition, during a disaster, it may be possible to fly a route other than the main route even in flights for logistics, etc., and in such a case, the flight support device 2 may select a route other than the main route as a route corresponding to the flight request information in step S4. For example, in this case, the flight support device 2 may set an arbitrary route that departs from a departure point indicated in the flight request information, passes through a flight location corresponding to an observation target specified in the observation request information, and arrives at a destination indicated in the flight request information.
[0074] Next, the hardware configuration of the flight support device 2 of this embodiment will be described. In the flight support device 2 of this embodiment, a flight support program, which is a program in which processing in the flight support device 2 is described, is executed on a computer system, so that the computer system functions as the flight support device 2. FIG. 18 is a diagram showing an example of the configuration of a computer system that realizes the flight support device 2 of this embodiment. As shown in FIG. 18, this computer system includes a control unit 101, an input unit 102, a storage unit 103, a display unit 104, a communication unit 105, and an output unit 106, which are connected via a system bus 107.
[0075] In FIG. 18, the control unit 101 is, for example, a processor such as a CPU (Central Processing Unit), and executes a flight support program in which the processing in the flight support device 2 of this embodiment is described. The input unit 102 is, for example, composed of a keyboard, a mouse, etc., and is used by a user of the computer system to input various information. The storage unit 103 includes various memories such as a RAM (Random Access Memory), a ROM (Read Only Memory), etc., and a storage device such as a hard disk, and stores the program to be executed by the control unit 101, necessary data obtained in the process of processing, etc. The storage unit 103 is also used as a temporary storage area for the program. The display unit 104 is composed of a display, an LCD (Liquid Crystal Display Panel), etc., and displays various screens to the user of the computer system. The communication unit 105 is a receiver and a transmitter that perform communication processing. The output unit 106 is a speaker, etc. Note that FIG. 18 is an example, and the configuration of the computer system is not limited to the example of FIG. 18.
[0076] Here, an example of the operation of the computer system until the flight support program of this embodiment is in an executable state will be described. In the computer system having the above-mentioned configuration, for example, the flight support program is installed in the storage unit 103 from a CD-ROM or DVD-ROM set in a CD (Compact Disc)-ROM drive or DVD (Digital Versatile Disc)-ROM drive (not shown). Then, when the flight support program is executed, the flight support program read from the storage unit 103 is stored in the storage unit 103. In this state, the control unit 101 executes the process as the flight support device 2 of this embodiment according to the program stored in the storage unit 103.
[0077] In the above description, a program describing the processing in the flight support device 2 is provided using a CD-ROM or DVD-ROM as a recording medium. However, this is not limited to this, and depending on the configuration of the computer system and the capacity of the program to be provided, for example, a program provided via a transmission medium such as the Internet via the communication unit 105 may be used.
[0078] The aircraft determination unit 25, the route determination unit 26, and the sensor data processing unit 29 shown in Fig. 1 are realized by the control unit 101 shown in Fig. 18 executing the flight support program stored in the storage unit 103 shown in Fig. 18. The map information storage unit 22 and the main line route storage unit 23 shown in Fig. 1 are part of the storage unit 103 shown in Fig. 18. The flight request acquisition unit 21, the route output unit 24, the observation request acquisition unit 27, the sensor data acquisition unit 28, and the sensor data output unit 30 shown in Fig. 1 are realized by the communication unit 105 and the control unit 101 shown in Fig. 18. The flight support device 2 may be realized by a plurality of computer systems. The flight support device 2 may be realized by a cloud system.
[0079] For example, the flight support program of this embodiment causes a computer system that determines the flight path of the aircraft 5 to execute the following steps: acquiring flight request information including the departure and destination of the aircraft 5 and indicating requirements regarding the flight of the aircraft 5; acquiring observation request information indicating requirements regarding observation by a sensor installed on the aircraft; using the flight request information and the observation request information, selecting flight request information corresponding to a flight that satisfies the observation requirements indicated by the observation request information, and determining the flight path of the flight corresponding to the selected flight request information.
[0080] 18. Moreover, the control unit 52 in the aircraft 5 of the present embodiment is realized by a control unit similar to the control unit 101 shown in Fig. 18 executing a program stored in a storage unit similar to the storage unit 103 shown in Fig. 18. The route acquisition unit 51 and the sensor data output unit 53 are realized by a communication unit and a control unit similar to the communication unit 105 and the control unit 101 shown in Fig. 18.
[0081] As described above, the data utilization user terminals 3, 6 and the aircraft flight user terminal 4 are, for example, personal computers, tablets, smartphones, etc., and their respective hardware configurations are similar to the computer system shown in FIG.
[0082] As described above, in this embodiment, the flight support device 2 sets a flight route that is suitable for the purpose of the flight of the aircraft 5 and that meets the observation request, using the flight user request information received from the aircraft flight user terminal 4 and the observation user request information received from the data use user terminal 3. Therefore, the flight support device 2 of this embodiment can set a flight route that is suitable for uses other than the purpose of the flight of the aircraft.
[0083] <Modification> In the above explanation, an example was described in which the aircraft 5 is equipped with all sensors that acquire data specified by the data type, but in a modified example, a case will be explained in which the sensors 54 installed on the aircraft 5 are different, or there is an aircraft 5 that is not equipped with a sensor 54. In such a case, the aircraft 5 will be selected according to the data type specified in the observation request information.
[0084] FIG. 19 is a flowchart showing an example of a flight support processing procedure in the flight support device 2 according to the modified example of the present embodiment. The same steps as those in FIG. 2 are assigned the same step numbers and will not be described. As shown in FIG. 19, in the modified example, step S7a is performed instead of step S7, and in step S7a, the aircraft determination unit 25 selects an aircraft that executes the flight request based on the flight request information, the flight route, the data type included in the observation request information, and the sensor 54 mounted on the aircraft. In addition, in the modified example, the aircraft operation information held by the aircraft determination unit 25 further includes information indicating the type of sensor 54 mounted on each aircraft 5, and the aircraft determination unit 25 selects an aircraft 5 equipped with a sensor 54 capable of acquiring the data type included in the observation request information. That is, in the modified example, the observation request information includes a data type requested to be acquired, and the aircraft determination unit 25 selects an aircraft 5 corresponding to the flight request information selected as the flight request information that satisfies the observation request indicated by the observation request information from among the aircraft 5 equipped with a sensor 54 capable of acquiring data corresponding to the data type using the data type included in the observation request information. This allows the aircraft determination unit 25 to select an appropriate aircraft 5 even if the sensors 54 installed on the aircraft 5 differ, or even if an aircraft 5 is included that does not have a sensor 54 installed.
[0085] Embodiment 2 FIG. 20 is a diagram showing a configuration example of a flight system including a flight support device according to the second embodiment. The flight system 1a according to the present embodiment includes a flight support device 2a, data using user terminals 3 and 6, an aircraft flying user terminal 4, and an aircraft 5. The data using user terminals 3 and 6, the aircraft flying user terminal 4, and the aircraft 5 are the same as those in the first embodiment. Components having the same functions as those in the first embodiment are given the same reference numerals as those in the first embodiment, and duplicated explanations are omitted. Below, differences from the first embodiment will be mainly explained.
[0086] Flight support device 2a of the present embodiment is similar to flight support device 2 of embodiment 1, except that flight support device 2a includes route determination unit 26a and sensor data processing unit 29a instead of route determination unit 26 and sensor data processing unit 29.
[0087] The sensor data processing unit 29a holds sensor data, extracts change points where changes have occurred using the held sensor data and the acquired sensor data, and sets the extracted change point as a key observation point if the amount of change in the change point is equal to or greater than a threshold. The sensor data processing unit 29a includes a change extraction unit 292 that extracts locations where changes have occurred using the sensor data, and a key observation point determination unit 291 that sets a key observation point using the result extracted by the change extraction unit 292 and instructs the route determination unit 26a about the set key observation point.
[0088] When a key observation point is set, the route determination unit 26a selects flight request information corresponding to a flight that can observe the key observation point, and determines a flight route corresponding to the selected flight request information. The route determination unit 26a includes a flight request information determination unit 261a and a flight route determination unit 262a. The flight request information determination unit 261a selects flight request information that selects flight request information that can acquire observation data that satisfies the observation request information, based on the observation request information, the flight request information, and the key observation point (if set). The operation of the flight request information determination unit 261a when a key observation point is not set is similar to the flight request information determination unit 261 of the first embodiment. When a key observation point is set, the flight request information determination unit 261a selects the corresponding flight request information so as to increase the frequency of observation of the corresponding observation request information, for example. Specifically, in addition to the normal observation observed in the observation data acquisition cycle, an observation for observing the key observation point is added, and flight request information is selected for the added observation.
[0089] The flight route determination unit 262a determines the flight route based on the key observation point (if set), the observation request information, and the selected flight request information. When a key observation point is not set, the operation of the flight route determination unit 262a is similar to that of the flight route determination unit 262 in the first embodiment. When a key observation point is set, the flight route determination unit 262a determines the flight route so that the key observation point can be observed. For example, the flight route is set so that observations added to observe the key observation point are observed in high resolution mode.
[0090] FIG. 21 is a flowchart showing an example of a flight support processing procedure in the flight support device 2a of this embodiment. Steps S1 to S3 are the same as those in the first embodiment. In step S4a after step S3, the flight support device 2a selects flight request information capable of acquiring observation data that satisfies the observation request information based on the observation request information, the flight request information, and the key observation point (if set). In detail, as described above, when a key observation point is set, the flight request information decision unit 261a selects flight request information so as to increase the frequency of observation. When a key observation point is not set, the same process as step S4 is performed.
[0091] In step S5a, the flight support device 2a determines a flight route based on the key observation point (if set), the observation request information, and the selected flight request information. In detail, as described above, if a key observation point is set, the flight request information determination unit 261a determines a flight route so that the key observation point can be observed. If a key observation point is not set, the same process as step S5 is performed.
[0092] Steps S6 to S11 are the same as those in the first embodiment. After step S10, the flight support device 2a judges whether or not to set a key observation point (step S31). If a key observation point is to be set (step S31 Yes), the flight support device 2a sets the key observation point and repeats the processing from step S4a. If a key observation point is not to be set (step S31 No), the flight support device 2a ends the processing.
[0093] FIG. 22 is a flowchart showing an example of a procedure for setting key observation points in this embodiment. FIG. 22 is the process of step S31 described above. The sensor data processing unit 29a holds the acquired sensor data for a certain period of time. As shown in FIG. 22, the flight support device 2a extracts change points from the acquired sensor data (step S32). In detail, the change extraction unit 292 of the sensor data processing unit 29a compares the sensor data output from the sensor data acquisition unit 28 with past sensor data to extract change points that are locations that have changed since the past. There is no restriction on the method of extracting change points, and any method may be used. For example, in the case of a camera image, a location where the difference in luminance, hue, or the like between sensor data observing the same location is equal to or greater than a predetermined value is extracted as a change point, and in the case of three-dimensional data, a location where the difference in position of points estimated to be the same location is equal to or greater than a predetermined value is extracted as a change point. In addition, when the sensor 54 observes the concentration of a gas, a location where the difference in concentration is equal to or greater than a certain value is extracted as a change point. The past sensor data to be compared with the acquired sensor data may be the sensor data acquired last time, may be an average value of sensor data acquired over a certain period of time, or may be sensor data having the same weather conditions, season, etc. as the acquired sensor data. The sensor data processing unit 29a outputs the extracted change point and the amount of change, i.e., the difference from the past sensor data, to the key observation point determination unit 291. Note that multiple change points may be extracted.
[0094] The flight support device 2a judges whether or not there is a change point that satisfies the conditions of the key observation point (step S33). In detail, the key observation point determination unit 291 judges whether or not there is a change point that satisfies the conditions of the key observation point. For example, when the amount of change received from the change extraction unit 292 is equal to or greater than a threshold, the key observation point determination unit 291 judges that there is a change point that satisfies the conditions of the key observation point.
[0095] If there is a change point that satisfies the conditions of the key observation point (step S33 Yes), the flight support device 2a sets the change point that satisfies the conditions of the key observation point as a key observation point in association with the observation request identification information (step S34), and ends the process. In step S34, in detail, the key observation point determination unit 291 determines the change point received from the change extraction unit 292 as a key observation point, and instructs the route determination unit 26a to associate the key observation point with the observation request identification information.
[0096] If there is no change point that satisfies the conditions of the key observation point (step S33 No), the flight support device 2a ends the process without setting a key observation point. If the answer to step S33 is Yes, the answer to step S3 described above is Yes, and if the answer to step S33 is No, the answer to step S3 described above is No. In the above-described example, observation of the key observation point is added in addition to observation in the normal observation data acquisition cycle, but the observation data acquisition cycle corresponding to the observation request information in which the key observation point is set may be shortened. The operation of this embodiment other than that described above is the same as that of embodiment 1.
[0097] As described above, the flight support device 2a of this embodiment uses sensor data to set locations where changes have occurred as key observation points, and adds observations of the key observation points in addition to observations during normal observation data acquisition cycles. This makes it possible to automatically and selectively observe locations where changes have occurred.
[0098] The configurations shown in the above embodiments are merely examples, and may be combined with other known technologies, or the embodiments may be combined with each other. Also, parts of the configurations may be omitted or modified without departing from the spirit of the invention. [Explanation of symbols]
[0099] 1,1a flight system, 2,2a flight support device, 3,6 data usage user terminal, 4 aircraft flight user terminal, 5 aircraft, 21 flight request acquisition unit, 22 map information storage unit, 23 main route storage unit, 24 route output unit, 25 aircraft determination unit, 26,26a route determination unit, 27 observation request acquisition unit, 28 sensor data acquisition unit, 29,29a sensor data processing unit, 30,53 sensor data output unit, 51 route acquisition unit, 52 control unit, 54 sensor, 261,261a flight request information determination unit, 262,262a flight route determination unit, 291 key observation point determination unit, 292 change extraction unit.
Claims
1. A flight support device for determining a flight path of an aircraft, comprising: A flight requirement acquisition unit that acquires flight requirement information including a departure point and a destination point of the aircraft and indicating a requirement regarding the flight of the aircraft; an observation request acquisition unit that acquires observation request information indicating a request for observation by a sensor mounted on the aircraft; a route determination unit that determines whether it is time to determine a flight route based on an observation request based on an observation data period or an observation date and time corresponding to the observation request information, and when it is determined that it is time to determine a flight route based on an observation request, uses the flight request information and the observation request information to select the flight request information corresponding to a flight that satisfies the observation request indicated by the observation request information, determines a flight route for the flight corresponding to the selected flight request information based on the flight request information and the observation request information, and determines a flight route for the flight corresponding to the flight request information not selected based on the flight request information, and when it is determined that it is not time to determine a flight route based on an observation request, determines a flight route for the flight corresponding to the flight request information based on the flight request information; A flight support device comprising:
2. The flight support device according to claim 1 , wherein the observation request information includes information indicating an observation target.
3. a main route storage unit that stores information indicating a main route which is a main route that the aircraft flies; Equipped with The flight support device described in claim 2, characterized in that the route determination unit uses the departure point and the destination to determine a main route section that is a section of the main route used in the flight corresponding to the flight request information to be used in the flight, and selects one or more of the flight request information that can observe the observation target by flying the determined main route section as the flight request information that satisfies the observation request indicated by the observation request information.
4. The flight support device according to claim 2 or 3, characterized in that the route determination unit determines the flight route corresponding to the flight request information that satisfies the observation request indicated by the observation request information so that the flight route includes a flight location that satisfies the observation request.
5. The flight support device according to claim 3 , wherein the main route includes an area above a railway line.
6. The flight support device according to claim 3 , wherein the main route includes an area above a river.
7. The flight support device according to claim 6 , wherein the observation target includes a river.
8. 8. The flight support device according to claim 7, wherein the observation target includes at least one of a levee, a bridge, and an island.
9. 9. The flight support device according to claim 1, wherein the sensor includes at least one of a camera for acquiring an image and a laser for acquiring three-dimensional data.
10. 10. The flight support device according to claim 1, wherein the observation request information includes an acquisition cycle of sensor data obtained by observation by the sensor.
11. a sensor data processing unit that stores the sensor data, extracts a change point where a change has occurred using the stored sensor data and the acquired sensor data, and sets the extracted change point as a key observation point when an amount of change in the extracted change point is equal to or greater than a threshold; Equipped with The flight support device described in claim 10, characterized in that when the key observation point is set, the route determination unit selects the flight requirement information corresponding to a flight that can observe the key observation point, and determines a flight route corresponding to the selected flight requirement information.
12. an aircraft determination unit that uses the flight requirement information to select the aircraft corresponding to the flight requirement information; a route output unit that transmits the flight route corresponding to the aircraft selected by the aircraft determination unit; 12. The flight support device according to claim 1, further comprising:
13. the observation request information includes a data type requested to be acquired, The flight support device described in claim 12, characterized in that the aircraft determination unit selects the aircraft corresponding to the flight request information selected as the flight request information that satisfies the observation request indicated by the observation request information from among the aircraft equipped with the sensor that can acquire data corresponding to the data type using the data type included in the observation request information.
14. the observation request information includes a specified observation mode; the observation mode includes a wide-area mode and a high-resolution mode; 14. The flight support device according to claim 1, wherein the route determination unit determines the altitude of the flight route by using the observation mode included in the observation request information.
15. A flight support device as described in Claim 14, characterized in that the observation modes include a downward wide-area mode, a downward high-resolution mode and an upward high-resolution mode.
16. 16. A flight support device according to claim 1, wherein the aircraft is an unmanned aerial vehicle.
17. The flight support device according to claim 16, characterized in that the flight requirement information is information indicating a flight requirement for logistics.
18. Aircraft and A flight support device that determines a flight path of the aircraft; A first user terminal that transmits flight user request information indicating a request regarding the flight of the aircraft to the flight support device; a second user terminal that transmits to the flight support device observation user request information indicating a request regarding observation by a sensor mounted on the aircraft; Equipped with The flight support device includes: A flight request acquisition unit that uses the flight user request information to generate flight request information including a departure point and a destination of the aircraft and indicating a request regarding the flight of the aircraft; an observation request acquisition unit that generates observation request information indicating a request regarding observation by the sensor using the observation user request information; a route determination unit that determines whether it is time to determine a flight route based on an observation request based on an observation data period or an observation date and time corresponding to the observation request information, and when it is determined that it is time to determine a flight route based on an observation request, uses the flight request information and the observation request information to select the flight request information corresponding to a flight that satisfies the observation request indicated by the observation request information, determines a flight route for the flight corresponding to the selected flight request information based on the flight request information and the observation request information, and determines a flight route for the flight corresponding to the flight request information not selected based on the flight request information, and when it is determined that it is not time to determine a flight route based on an observation request, determines a flight route for the flight corresponding to the flight request information based on the flight request information; A flight system comprising:
19. A flight support method for a flight support device that determines a flight route of an aircraft, comprising: obtaining flight requirements information indicating requirements for flying the aircraft, the flight requirements including a departure point and a destination point of the aircraft; obtaining observation request information indicating a request for observation by a sensor installed on the aircraft; a step of determining whether it is time to determine a flight path based on an observation request based on an observation data period or observation date and time corresponding to the observation request information, and when it is determined that it is time to determine a flight path based on an observation request, using the flight request information and the observation request information, selecting the flight request information corresponding to a flight that satisfies the observation request indicated by the observation request information, determining a flight path for the flight corresponding to the selected flight request information based on the flight request information and the observation request information, and determining a flight path for the flight corresponding to the flight request information that was not selected based on the flight request information, and when it is determined that it is not time to determine a flight path based on an observation request, determining a flight path for the flight corresponding to the flight request information based on the flight request information; A flight support method comprising:
20. In a computer system that determines the flight path of an aircraft, obtaining flight requirements information indicating requirements for flying the aircraft, the flight requirements including a departure point and a destination point of the aircraft; obtaining observation request information indicating a request for observation by a sensor installed on the aircraft; a step of determining whether it is time to determine a flight path based on an observation request based on an observation data period or observation date and time corresponding to the observation request information, and when it is determined that it is time to determine a flight path based on an observation request, using the flight request information and the observation request information, selecting the flight request information corresponding to a flight that satisfies the observation request indicated by the observation request information, determining a flight path for the flight corresponding to the selected flight request information based on the flight request information and the observation request information, and determining a flight path for the flight corresponding to the flight request information that was not selected based on the flight request information, and when it is determined that it is not time to determine a flight path based on an observation request, determining a flight path for the flight corresponding to the flight request information based on the flight request information; A flight support program characterized by executing the above.
Citation Information
Patent Citations
System, method, and program for supporting flying of aircraft and aircraft
JP2020118657A
Information processing device and information processing method
WO2019146580A1
Information processing device
WO2020189607A1
