Operation management device, operation management method, and operation management system

The traffic management device and system facilitate efficient transfer of small aircraft passengers and cargo by integrating aircraft and ground vehicle data to manage flight and transfer paths, addressing the challenge of coordinating with non-aircraft capable vehicles for safe transportation.

JP2024161733APending Publication Date: 2024-11-20HITACHI LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023076711
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-08
Publication Date
2024-11-20

AI Technical Summary

Technical Problem

Existing technologies fail to effectively coordinate the movement of small aircraft from alternative landing sites to their destinations using various means of transportation, including vehicles operated by other companies or public transportation without takeoff and landing sections, making it difficult to safely and efficiently transport people and cargo.

Method used

A traffic management device and system that integrates information on aircraft location, surrounding environment, alternative landing sites, and ground vehicles to determine optimal transfer routes and vehicles for transporting cargo and passengers from alternative landing sites to destinations, utilizing flight plan information and ground vehicle data to calculate and manage flight and transfer paths.

Benefits of technology

Enables safe and efficient transportation and logistics by linking small aircraft with ground vehicles, ensuring seamless transfer of passengers and cargo even if the aircraft cannot reach its original destination, leveraging public transportation and other company vehicles.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161733000001_ABST
    Figure 2024161733000001_ABST
Patent Text Reader

Abstract

To provide an operation management device capable of realizing safe and efficient traffic and commodity distribution by linkage between a flying body and an other-company management vehicle or a ground vehicle of a public transportation or the like.SOLUTION: An operation management device 1 determines an alternative landing point 601 and a ground vehicle 606 for transporting a load of a flying body 104 from the alternative landing point 601 to a destination 607 based on self-position information of the flying body 104, peripheral environment information of the flying body 104, point information being the information on candidates of the alternative landing point 601 on which the flying body 104 lands, information on a navigation plan to the destination 607 of the flying body 104, and ground vehicle information being the information on candidates of a ground vehicle 606 at a transfer destination.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a traffic management device, a traffic management method, and a traffic management system for managing the operations of an aircraft and another moving body. [Background technology]

[0002] As small aircraft are implemented in society as part of transportation and logistics infrastructure, it is expected that travel will become more efficient by realizing next-generation transportation services that are linked with existing ground vehicles.

[0003] Patent Document 1 describes a technology for managing a vehicle having a takeoff and landing section on which an aircraft can take off and land so that the vehicle moves to an alternative takeoff and landing site.

[0004] According to Patent Document 1, if it is determined that an aircraft cannot land at an airfield at the scheduled landing time, an alternative airfield where the aircraft can land is determined, and a vehicle having a takeoff and landing section where the aircraft can take off and land is moved to the alternative takeoff and landing site. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 7068386 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the technology described in Patent Document 1 is a technology in which the aircraft itself, such as a drone, is moved by a vehicle with a takeoff and landing section, and it does not describe technology for landing the aircraft at an alternative location and moving people and cargo on board the aircraft from the alternative location to the destination using various means of transportation.

[0007] For this reason, it is not possible to use vehicles managed by other companies or public transportation that do not have takeoff and landing areas, making it difficult to properly transport people and cargo aboard the aircraft from the alternative location to the destination.

[0008] The object of the present invention is to provide an operation management device, an operation management method, and an operation management system that can achieve safe and efficient transportation and logistics by coordinating small aerial vehicles with vehicles managed by other companies and ground vehicles such as public transportation. [Means for solving the problem]

[0009] In order to achieve the above object, the present invention is configured as follows.

[0010] The operation management device is equipped with a transfer determination unit that determines the alternative landing site and the ground vehicle for transporting the aircraft's cargo from the alternative landing site to the destination based on the aircraft's self-location information, information about the aircraft's surrounding environment, location information which is information about candidate alternative landing sites where the aircraft will land, operation plan information to the aircraft's destination, and ground vehicle information which is information about candidate ground vehicles for transfer.

[0011] In addition, in an operation management method in which an operation management device manages the operation of an aircraft, the alternative landing site and the ground vehicle for transporting the aircraft's cargo from the alternative landing site to the destination are determined based on the aircraft's own position information, information on the aircraft's surrounding environment, location information which is information on candidate alternative landing sites where the aircraft will land, operation plan information to the destination of the aircraft, and ground vehicle information which is information on candidate ground vehicles for transfer.

[0012] The operation management system also includes an operation management device having a transfer determination unit that determines the alternative landing point and the ground vehicle for transporting the aircraft's goods from the alternative landing point to the destination based on the aircraft's own position information, information about the aircraft's surrounding environment, location information which is information about candidate alternative landing points where the aircraft will land, operation plan information to the destination of the aircraft, and ground vehicle information which is information about candidate ground vehicles for transfer, a flight path calculation unit that calculates a flight path for the aircraft to land at the alternative landing point, and a route information transmission unit that transmits the flight path to the aircraft, an environmental information transmission unit that transmits the surrounding environment information to the operation management device, a route information receiving unit that receives flight path information from the operation management device, and an aircraft having a flight control unit that controls flight based on the route information received by the route information receiving unit. Effect of the Invention

[0013] According to the present invention, it is possible to provide an operation management device, an operation management method, and an operation management system that can realize safe and efficient transportation and logistics by coordinating small aircraft with vehicles managed by other companies and ground vehicles such as public transportation. In particular, it is possible to provide an operation management device, an operation management method, and an operation management system that can appropriately move people and cargo from an alternative location to the destination by coordinating with ground vehicles when it becomes difficult for the small aircraft to arrive at the destination due to some cause during flight. [Brief description of the drawings]

[0014] [Figure 1] 1 is a conceptual diagram of a situation in which a traffic management device according to a first embodiment is applied; [Diagram 2] 1 is a schematic configuration diagram of a traffic management device according to a first embodiment. [Diagram 3] FIG. 1 is a schematic configuration diagram of a miniature aircraft according to a first embodiment. [Figure 4] FIG. 2 is a schematic configuration diagram of a traffic management device side system and a small aircraft side system in the first embodiment. [Figure 5A] FIG. 13 is a diagram showing an example of data registered in a location table. [Figure 5B] FIG. 13 is a diagram showing an example of data registered in an operation plan table. [Figure 5C] FIG. 13 is a diagram illustrating an example of data registered in a supplier table. [Figure 6] FIG. 1 is a conceptual diagram of a transfer when passengers and cargo are moved to their destination by transferring from an alternative landing point to a ground vehicle. [Figure 7] FIG. 1 is a conceptual diagram of a transfer where passengers are transferred from an alternative landing point to a rail vehicle to move to their destination. [Figure 8A] A diagram showing a fault code table stored in the memory device of the flight control device and the memory device of the miniature aircraft. [Figure 8B] FIG. 13 is a diagram showing a processing ID table stored in the storage device of the flight control device and the storage device of the miniature aircraft. [Figure 9] 13 is an operation flowchart of a transfer determination unit. [Figure 10] 10 is a flowchart showing details of step S904 in FIG. 9. [Figure 11] 11 is a flowchart showing details of step S1004 in FIG. 10. [Figure 12] 11 is a flowchart showing details of step S1005 in FIG. 10. [Figure 13] 11 is a flowchart showing details of step S1006 in FIG. 10. [Figure 14] 13 is a flowchart showing the operation of the small aircraft system. [Figure 15A] FIG. 11 is an explanatory diagram of the overall data format transmitted from the small aircraft to the traffic management device. [Figure 15B] FIG. 11 is an explanatory diagram of the data format of visibility level transmitted from a small aircraft to a traffic management device. [Figure 16] 4 is an operation flowchart of an environment prediction unit of the traffic management device. [Figure 17] 13 is an operational flowchart of a landing point candidate search in a transfer determination unit of the traffic management device. [Figure 18]FIG. 4 is a diagram illustrating a display example of a display screen of an input device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the various components of the present invention do not necessarily have to exist independently of one another, and it is acceptable for one component to be made up of multiple members, for multiple components to be made up of one member, for one component to be a part of another component, or for part of one component to overlap with part of another component. EXAMPLES

[0016] In the first embodiment, an embodiment will be described in which an operation management device determines an alternative landing site for an aircraft and a ground vehicle for transporting an item carried by the aircraft. FIG. 1 is a conceptual diagram of a situation in which an operation management device 1 (shown in FIG. 2) according to an embodiment of the present invention is applied. In FIG. 1, a small aircraft 104 takes off and lands at a takeoff and landing port 101. A camera 102 and a radar 103 detect the environment around the small aircraft 104 and the takeoff and landing port 101, and transmit the environment to an operation control device 1 in a control center 111. A wind condition sensor 105 installed in a building 110 detects wind conditions 106 in the vicinity of the takeoff and landing port 101, and transmits the environment to the operation control device 1. A Doppler lidar can be applied to the wind condition sensor 105.

[0017] Weather information from a weather company 107 can be obtained by the traffic management device 1. The small aircraft 104 determines its flight route based on information from sensors mounted on the small aircraft 104, maps, the traffic control device 1, and the like.

[0018] FIG. 2 is a schematic configuration diagram of the traffic management device 1. As shown in FIG.

[0019] 2, the traffic management device 1 includes a control unit (CPU) 201, a memory 202, a communication unit 203, a display device 204, and an input device 205. The control unit 201 is connected to the memory 202, the communication unit 203, the display device 204, and the input device 205.

[0020] The control unit 201 is also connected to the camera 102, the radar 103, and the wind condition sensor 105. The control unit 201 communicates information with the small aircraft 104 via the communication device 203. The control unit 201 also receives information from a weather company 107 via the communication device 203.

[0021] FIG. 3 is a schematic diagram of the miniature aircraft 104.

[0022] 3, the miniature aircraft 104 includes a control unit (CPU) 305, a memory 306, a communication device 307, and a storage device 304. The control unit 305 is connected to the memory 306, the communication device 307, and the storage device 304.

[0023] The control unit 305 is also connected to the camera 103, the radar 102, and the GNSS (Global Navigation Satellite System) 303. The control unit 305 communicates information with the traffic control device 1 via the communication device 307. The control unit 305 also receives information from the weather company 107 via the communication device 307. The communication device 307 has a function of notifying information such as the occurrence of a malfunction in the aircraft, passengers, cargo, etc. of the small aircraft 104. A malfunction is, for example, an incident, accident, bad weather, equipment trouble, or other event that adversely affects the operation, takeoff and landing, and transportation of goods of the small aircraft 104.

[0024] FIG. 4 is an explanatory diagram of the functions of the small aircraft side system 401 and the operation management device side system 419.

[0025] In Figure 4, the small aircraft side system 400 includes an environment recognition unit 401 that recognizes the surrounding environment of the small aircraft 104 based on information from the radar 301 and the camera 302, a self-position estimation unit 402 that estimates the self-position of the small aircraft 104 based on information from the GNSS 303, and an environment information transmission unit 403 that transmits information from the environment recognition unit 401 and the self-position estimation unit 402 to the operation management device side system 419.

[0026] In addition, the small aircraft side system 400 is equipped with a route information receiving unit 404 that receives route information transmitted from the operation management device side system 419, and a flight control unit 405 that controls flight based on the route information transmitted from the route information receiving unit 404.

[0027] The environment recognition unit 401 , self-position estimation unit 402 , environment information transmission unit 403 , route information reception unit 404 , and flight control unit 405 correspond to functions within the control unit 305 of the miniature aircraft 104 .

[0028] The traffic management device side system 419 includes an input unit 417 that inputs commands from an operator 418, and an environmental information receiving unit 406. The environmental information receiving unit 406 receives information from the input unit 417, weather information from the weather company 107, and information from the above-mentioned environmental information transmitting unit 403. The input unit 417 is included in the input device 205 of the traffic management device 1 shown in FIG. 2. The environmental information receiving unit 406 is included in the communication device 203.

[0029] When there is a problem such as an incident or accident that cannot be obtained by the weather company 107 or the wind condition sensor 105, the operator 418 inputs the information to the environmental information receiving unit 406 via the input unit 417. Furthermore, information on the problem may be automatically obtained from a network or the like and accepted by the input unit 417 without the input by the operator 418.

[0030] In addition, the traffic management device side system 419 includes an environment prediction unit 407 that predicts the environment based on information from the wind condition sensor 105, the radar 103, and the camera 102, and a transfer determination unit 408 that is supplied with information from the environment prediction unit 407 and information from the environment information receiving unit 406.

[0031] The transfer determination unit 408 includes a landing point determination unit 409 that determines an alternative landing point based on information in the location table 414, the flight plan table 415, and the client table 416, a vehicle determination unit 410 that determines a transfer vehicle, and a transfer point determination unit 411 that determines a transfer point.

[0032] Furthermore, the operation management device side system 419 includes a flight path calculation unit 412 that calculates the flight path of the small aircraft 104 based on information from the transfer determination unit 408, and a route information transmission unit 413 that transmits the flight path information calculated by the flight path calculation unit 412 to the route information receiving unit 404.

[0033] The location table 414 , the flight plan table 415 and the customer table 416 are stored in the storage device 206 of the flight management device 1 .

[0034] The environment prediction unit 407, the environment information receiving unit 406, and the flight route calculation unit 412 are included in the control unit 201 of the traffic management device 1. The route information transmitting unit 413 is included in the communication device 203 of the traffic management device 1.

[0035] 5A is a diagram showing an example of data registered in the location table 414. In the location table 414, for each location name 501A that is a candidate for an alternative landing location and a transfer location, latitude 502, longitude 503, attributes 504 of the alternative landing location and the transfer location, and information 505 on whether parking of ground vehicles is possible or not are registered.

[0036] 5B is a diagram showing an example of data registered in the flight plan table 415. In the flight plan table 415, for each flight plan of the small aircraft 104, a destination name 501B, a destination latitude 506, a destination longitude 507, a cargo 508 indicating attributes of the transported item, a size 509 of the transported item, and a quantity 510 are registered.

[0037] 5C is a diagram showing an example of data registered in customer table 416. In customer table 416, latitude 511, longitude 512, type of ground vehicle 513 of the transfer destination, and fare 514 are registered for each potential transfer destination location name 501C.

[0038] Vehicle type 513 specifies vehicle types suitable for transporting goods, passengers, and other cargo.

[0039] Figure 6 is a conceptual diagram of a transfer when passengers and cargo are moved to their destination by transferring from an alternate landing point to a ground vehicle.

[0040] 6, when some kind of trouble occurs with respect to the operation of the small aircraft 104, the small aircraft 104 lands at a landing point 601 (alternate landing point) determined by the transit decision unit 408 of the traffic management device side system 419, and the passengers 604 and the cargo 605 and other conveyances move from the landing point 601 to a rendezvous point (transfer point) 602 determined by the transit decision unit 408 of the traffic management device side system 419. The passengers are notified in advance by a display device or a broadcast device of the small aircraft 104 that a trouble has occurred and that they need to move from the landing point 601 to the rendezvous point 602.

[0041] The vehicle management company 603 moves the vehicle 606 determined by the transfer determination unit 408 of the navigation management device side system 419 to the rendezvous point 602. If the vehicle 606 can be parked at the landing point 601, the landing point 601 may be set as the rendezvous point 602.

[0042] Vehicle 606 loads passengers 604 and cargo 605 at meeting point 602 and transports them to destination 607 .

[0043] FIG. 7 is a conceptual diagram of a transfer in which passengers are transferred from an alternative landing point to a rail car to move to their destination.

[0044] 7, when some kind of trouble occurs with respect to the operation of the small aircraft 104, the small aircraft 104 lands at a landing point 601 determined by the transfer determination unit 408 of the traffic management device side system 419, and the passenger 604 moves to a railway station 701 (transfer point) determined by the transfer determination unit 408 of the traffic management device side system 419. The passenger 604 moves from the station 701 to a destination 607 by a railroad car. Here, the transfer destination is not limited to a railroad, and may be other public transportation such as a bus.

[0045] 8A is a diagram showing a fault code table stored in the memory device 206 of the traffic control device 1 and the memory device 304 of the small aircraft 104. The operation of the small aircraft 104 is determined according to the contents registered in the fault code table 8A.

[0046] In Fig. 8A, for each obstacle 801 indicating the type of incident, accident, etc., the location where the obstacle occurred 802, the payload 803 of the small air vehicle 104, the process ID 804, and the command landing point 805 are set. In Fig. 8A, "Any" means that the target is not limited, and "NA" means that the designated landing point is not limited. Note that the types of obstacles in Fig. 8A are only examples, and are not limited to these as long as they are events that impede the operation, takeoff and landing, and transportation of goods of the small air vehicle 104.

[0047] When an obstacle occurs, the process varies depending on the type of obstacle, the location of the obstacle, and the type of payload of the small flying object 104. In Figures 8A and 8B, process IDs 804 and 806 indicate the urgency of the obstacle. The higher the urgency, the more quickly the small flying object 104 needs to land.

[0048] Among the types of faults, information on incidents, fires, and accidents is not necessarily automatically input to the traffic management device 1, so the operator 418 of the traffic management device 1 may manually input the information from the input device 205. If the fault is meteorological information, information from the wind condition sensor 105, the camera 103, and the weather company 107 can be used.

[0049] 8B is a diagram showing a processing ID table stored in the storage device 206 of the traffic control device 1 and the storage device 304 of the miniature aircraft 104. In the processing ID table, a processing type 807, processing details 808, and landing conditions 809 for a fault are set for each processing ID 806 indicating the level of urgency of the fault.

[0050] If the obstacle is an eruption, since it is unknown where and what type of disaster will occur, the processing ID is 5, operations will be suspended, and the processing details are "land at the nearest location where the obstacle can be avoided."

[0051] If the disruption is an incident or fire that occurs near the destination, the aircraft cannot approach the destination, so the process ID is 5 and operations are suspended. However, if there is a fire on the route and passengers are on board, the process ID is 3 and the aircraft will land near a public transportation facility (station) to evacuate passengers to a safe place.

[0052] If the obstacle is a traffic accident, occurs near the destination, and there is a possibility that a restriction line has been set up, the process ID is 5 and operations are suspended, and if it occurs along the route, the process ID is 3 and if a no-fly zone is set, the flight will continue on an avoidance route. If the aircraft SoC (aircraft charging capacity) decreases after the avoidance, the process will follow the process for an aircraft SoC decrease.

[0053] If the obstacle is fog, the process ID is 1 and the flight continues on the evasive route. If the aircraft SoC drops after the flight is evasive, the process is the same as for a drop in aircraft SoC.

[0054] If the obstacle is heavy rain, there is a risk of the aircraft falling, so the process ID is 4 and the aircraft lands at the nearest landing point. However, to protect cargo and passengers, the aircraft will land near a delivery company in the case of cargo, and near a public transportation facility (station) in the case of passengers.

[0055] If the problem is an aircraft malfunction, it is dangerous to fly any further, so the process ID is 4 and the aircraft immediately lands at the nearest possible landing site.

[0056] If the fault is due to aircraft SoC degradation, the process ID is 2 and the aircraft lands based on the optimal route to the destination.

[0057] If the problem is a control failure, continuing operations would be dangerous, so the process ID is 5 and operations are stopped.

[0058] If the obstacle is strong winds, it is dangerous to continue flying, so the process ID is 4 and the aircraft lands at the nearest location.

[0059] FIG. 9 is a flowchart showing the operation of the connection determination unit 408.

[0060] 9, the transfer decision unit 408 receives information from the environment information receiving unit 406 or the environment predicting unit 407, determines whether or not there is a fault, and ends the process if there is no fault. If there is a fault, the process proceeds to step S902.

[0061] In step S902, the transfer determination unit 408 acquires the type of obstacle, the obstacle occurrence location, and cargo information.

[0062] Next, in step S903, the connection determination unit 408 searches the problem code table 8A stored in the storage device 206 for the process ID and the designated landing point corresponding to the acquired problem information.

[0063] Then, in step S904, the transfer determination unit 408 assigns processes to each process ID.

[0064] FIG. 10 is a flowchart showing the details of step S904 in FIG.

[0065] 10, the transfer determination unit 408 searches the landing conditions from the processing ID table 8B stored in the storage device 206 using the processing ID as a key. Then, the process proceeds to step S1002, where the landing site of the landing conditions searched for in step S1001 is obtained from the fault code table 8A stored in the storage device 206.

[0066] Next, in step S1003, the transfer determination unit 408 branches the process based on the acquired designated landing point and landing conditions. In step S1003, if there is a designated landing point and the landing conditions are the nearest designated landing point, the process proceeds to step S1004, where the nearest designated landing point is searched for in the point table 414. In step S1003, if there is no designated landing point and the landing conditions are the nearest possible landing point, the process proceeds to step S1005, where the nearest possible landing point is searched for in the point table 414. In step S1003, if the processing type is other (avoidance flight or continuing flight), the process proceeds to step S1006, where the possible landing point is searched for in the point table 414.

[0067] After the process of step S1004, S1005, or S1006, the process proceeds to step S1007, where the connection determination unit 408 determines a landing point and a meeting point.

[0068] FIG. 11 is a flowchart showing the details of step S1004 in FIG.

[0069] If there is a designated landing point and the landing conditions are the nearest designated landing point, in step S1101 of Figure 11, the transfer determination unit 408 determines whether the attribute 504 of the nearest designated landing point searched from the point table 414 in step S1004 is a public institution, and if it is a public institution, terminates the processing, and if it is not a public institution and has other attributes, proceeds to step S1102.

[0070] In step S1102, the transfer determination unit 408 determines whether the nearest designated landing point retrieved from the point table 414 in step S1004 is available for parking of ground vehicles, and if it is available, the process proceeds to step S1105, where the landing point is selected as the rendezvous point. After the process in step S1105, the process proceeds to step S1106.

[0071] In step S1102, if the nearest designated landing point searched from the point table 414 in step S1004 is not available for parking, the transfer determination unit 408 proceeds to step S1103, where it searches the point table 414 for a potential meeting point that is near the designated landing point and is available for parking of ground vehicles. Then, it proceeds to step S1104.

[0072] In step S1104, the transfer determination unit 408 selects, as the rendezvous point, a candidate that can be reached in the shortest time from the designated landing point from the candidates searched for in step S1103, and then proceeds to step S1106.

[0073] In step S1106, the transfer determination unit 408 refers to the candidates selected in step 1104 and the flight plan table 415 of the small aircraft 104, searches the customer table 416 for ground vehicles that are near the meeting point and suitable for transporting the cargo of the small aircraft 104, and in step S1107 selects as the ground vehicle the one that has the shortest travel time to the meeting point and is capable of transporting the cargo.

[0074] FIG. 12 is a flowchart showing the details of step S1005 in FIG. 10 when there is no designated landing site and the landing condition is the nearest possible landing site.

[0075] 12, the transfer determination unit 408 determines whether the nearest possible landing point retrieved from the point table 414 in step S1005 allows parking of a ground vehicle, and if parking is possible, proceeds to step S1204 and selects the landing point as a meeting point. After the process of step S1204, the process proceeds to step S1205.

[0076] In step S1201, if the nearest possible landing point searched from the point table 414 in step S1005 is not available for parking, the transfer determination unit 408 proceeds to step S1202, where it searches the point table 414 for a potential meeting point that is near the possible landing point and is available for parking of ground vehicles. Then, it proceeds to step S1203.

[0077] In step S1203, the transfer determination unit 408 selects, from the candidates searched for in step S1202, a candidate that can be reached in the shortest time from the possible landing point as the meeting point, and then proceeds to step S1205.

[0078] In step S1205, the transfer determination unit 408 refers to the candidate selected in step S1203 and the flight plan table 415 of the small aircraft 104, searches the customer table 416 for ground vehicles that are near the meeting point and suitable for transporting the cargo of the small aircraft 104, and in step S1206 selects as the ground vehicle the one that has the shortest travel time to the meeting point and is capable of transporting the cargo.

[0079] FIG. 13 is a flowchart showing details of step S1006 in FIG.

[0080] If there is no need to land at the nearest point, the connection determination unit 408 sets an initial value for the minimum estimated time in step S1301 of Fig. 13. In the illustrated example, it is set to 9999 minutes, but the minimum estimated time can be set to any value within the range of the maximum possible time or more.

[0081] Next, in step S1302, the transfer determination unit 408 calculates the flight time to the landing point based on information from the environmental information receiving unit 406, the environmental prediction unit 407, and the flight plan table 415 of the small aircraft 104, and in step S1303, the transfer determination unit 408 searches for a candidate meeting point near the candidate landing point from the point table 414. Then, in step S1304, the transfer determination unit 408 refers to the point table 414 to determine the travel time from the candidate landing point to the candidate meeting point, and in step S1305, the transfer determination unit 408 refers to the point table 414 to determine whether the designated landing point is a public institution or another landing point.

[0082] In step S1305, if the designated landing point is a public institution, the process proceeds to step S1306, and if the designated landing point is another landing point, the process proceeds to step S1310.

[0083] In step S1306, the connection determination unit 408 calculates the travel time from the meeting point candidate to the destination based on the information in the point table 414 and the flight plan table 415.

[0084] Next, in step S1307, the transfer determination unit 408 calculates an estimated travel time to the destination based on information from the environmental information receiving unit 406, the environmental prediction unit 407, the location table 414, and the flight plan table 415. The estimated travel time to the destination is the sum of the travel time from the position of the small aircraft 104 to the landing point, the travel time from the landing point to the meeting point, and the travel time from the meeting point to the destination.

[0085] Then, in step S1308, the transfer determination unit 408 determines whether the estimated travel time is less than the minimum estimated time. If the estimated travel time is less than the minimum estimated time, the process proceeds to step S1309, where the minimum estimated time is set as the estimated travel time, the process exits the processing loop for the number of vehicles, and steps S1304 to S1315 are repeated as many times as the number of candidate meeting points.

[0086] In step S1308, if the estimated travel time is equal to or greater than the minimum estimated time, the process exits from the vehicle number processing loop and repeats steps S1304 to S1315 the number of times corresponding to the number of meeting point candidates.

[0087] In step S1305, if the designated landing point is not a public facility, the process proceeds to step S1310, where the transfer determination unit 408 searches the supplier table 416 for a vehicle that can come to the meeting point.

[0088] Then, in step S1311, the transfer determination unit 408 calculates the travel time from the vehicle management company 603 to the candidate meeting point based on the information in the location table 414 and the customer table 416. Next, in step S1312, the transfer determination unit 408 calculates the travel time from the candidate meeting point to the destination based on the information in the location table 414.

[0089] In step S1313, the transfer determination unit 408 calculates an estimated travel time to the destination based on information from the environmental information receiving unit 406, the environmental prediction unit 407, the location table 414, the flight plan table 415, and the client table 416. The estimated travel time to the destination is max (the time from the aircraft position to the landing point + the time from the landing point to the meeting point, the time from the vehicle management company 603 to the meeting point + the time from the meeting point to the destination). Note that max means the maximum value.

[0090] Next, in step S1314, the transfer determination unit 408 judges whether the estimated travel time is shorter than the minimum estimated time. If the estimated travel time is shorter than the minimum estimated time, the process proceeds to step S1315, where the minimum estimated time is set as the estimated travel time, and if not, the minimum estimated time is left as is. Then, steps S1311 to S1315 are repeated until the number of vehicles reaches a predetermined number.

[0091] When the processing loop for the predetermined number of vehicles is completed, steps S1302 to S1315 are repeated until the number of landing site candidates is reached.

[0092] Then, when the process exits from the landing point candidate number processing loop, the process proceeds to step S1316, where the connection determination unit 408 selects the landing point and meeting point that realize the shortest estimated time, and the process ends. EXAMPLES

[0093] In the second embodiment, an embodiment in which a small flying object searches for new landing site candidates will be described.

[0094] FIG. 14 is a flowchart showing the operation of the small aircraft side system 400.

[0095] In step S1401 of FIG. 14, the miniature aircraft 104 measures its own position using the GNSS 303, and in step S1402, the radar 301 is directed toward the ground.

[0096] In step S1403, the control unit 305 of the miniature aircraft 104 groups points on the ground measured in step S1402 that have height coordinates within a certain range, and regards these points as flat ground.

[0097] Then, in step S1404, the control unit 305 determines whether or not the flat land area of ​​the flat land obtained in step S1403 is greater than a predetermined threshold value, and if it is greater than the threshold value, adds it to the landing site candidates in step S1405.

[0098] In step S1404, if the flat land area of ​​the flat land obtained in step S1403 is equal to or smaller than a predetermined threshold value, the control unit 305 judges the next flat land. Steps S1404 and S1405 are repeated until a predetermined number of flat land is found.

[0099] In step S1406, the miniature aircraft 104 measures visibility using the camera 302 near flat ground for a predetermined number of landing site candidates.

[0100] FIG. 15A is an explanatory diagram of the overall data format regarding the landing site candidates transmitted from the small aircraft 104 to the traffic management device 1, and FIG. 15B is an explanatory diagram of the data format regarding the visibility level.

[0101] In FIG. 15A , the entire data format consists of an aircraft ID 1501 , a transmission time 1502 , a self-position 1503 , a flight speed 1507 , a designated estimation result 1512 , and a flat ground detection result 1518 .

[0102] The self-position 1503 includes an X coordinate 1504, a Y coordinate 1505, and a Z coordinate 1506. The flight speed 1507 includes direction information 1508 and a speed 1511, and the direction information 1508 includes a vertical angle 1509 and a horizontal angle 1510.

[0103] The visibility estimation result 1512 includes a direction number 1513 and direction information 1514 , and the direction information 1514 includes a visibility level 1515 , a vertical angle 1516 , and a horizontal angle 1517 .

[0104] The flat ground detection result 1518 includes a detection number 1519 and orientation information 1320 , and the orientation information 1320 includes a distance 1521 , a vertical angle 1522 , and a horizontal angle 1523 .

[0105] In FIG. 15B, there are four visibility levels: 1, 2, 3, and 4. Level 1 has a status of "poor visibility due to clouds or fog" and a value of -1. Level 2 has a status of "obstructions present" and a value of 0. Level 3 has a status of "good visibility" and a value of 1. Level 4 has a status of "no flight" and a value of -10.

[0106] FIG. 16 is a flowchart showing the operation of the environment prediction unit 407 of the traffic management device 1.

[0107] In step S1601 of FIG. 16, the environment prediction unit 407 extracts self-position information from the data received from the environment information transmission unit 403 of the small aircraft 104 (FIG. 15A), and in step S1602, extracts the visibility estimation result from the received data (FIG. 15A).

[0108] Next, in step S1603, the environment prediction unit 407 calculates voxel coordinates to which visibility is assigned using the Bresenham algorithm based on the self-position information. Next, in step S1604, the environment prediction unit 407 adds a value corresponding to the visibility level to the value of the voxel to which the visibility was assigned in step S1603 based on the visibility estimation result. The operation of step S1604 is repeated the number of times corresponding to the number of assigned voxels. Then, the operations of steps S1603 and S1604 are repeated the number of times corresponding to the number of azimuths.

[0109] Next, in step S1605, the environment prediction unit 407 obtains the wind condition prediction result at the voxel coordinates to which the visibility level value was added in step S1604 from the wind condition sensor 105 or the environment information receiving unit 406, and in step S1606, moves the voxel value based on the wind direction and wind speed. The operations of steps S1605 and S1606 are repeated for the number of voxels. Furthermore, the operations of steps S1605 and S1606 are repeated for the number of prediction times. Then, the processing ends.

[0110] FIG. 17 is a flowchart showing the operation of the transfer determination unit 408 of the traffic management device 1 to search for landing point candidates.

[0111] In step S1701 of Fig. 17, the transfer determination unit 408 issues SQL (database language) to the location table 414 to search for locations around the position of the miniature aircraft 104. Next, in step S1701, the transfer determination unit 408 determines whether the landing location candidate calculated by the environment prediction unit 407 is within the "good visibility" range, and if it is within the "good visibility" range, proceeds to step S1703 and adds it to the landing location candidate list. Then, steps S1702 and S1703 are repeated for the number of hits. Even if it is not within the "good visibility" range in step S1702, steps S1702 and S1703 are repeated until the number of hits is reached. EXAMPLES

[0112] In the third embodiment, an embodiment relating to the input device 205 of the traffic management system 1 will be described.

[0113] FIG. 18 is a diagram showing a display example of an input screen 1801 of the input device 205. As shown in FIG.

[0114] 18 is an example of a screen on which the operator 418 inputs a fault, and the range of the fault, the details of the fault, and the level of the fault are displayed. The range 1804 in which the fault occurred (in the illustrated example, a fire in a factory 1802) can be specified and input using a mouse pointer 1803.

[0115] (Other Examples) In the above-described embodiment, it is possible that the vehicle that will take over the movement of the passengers 604 or cargo 605 to the destination cannot be detected, or it takes time to detect the vehicle, resulting in a delay in detection. In this case, the vehicle may be configured to select whether to hover above the transfer point and wait, or to land at another alternative point and wait, and communicate this to the small air vehicle 104.

[0116] In the above example, the present invention is not limited to the miniature aircraft 104, but can also be applied to aircraft other than small ones.

[0117] In addition, transported goods is a general term for passengers and cargo. [Explanation of symbols]

[0118] 1... Traffic control device, 101... Takeoff and landing port, 102... Camera, 103... Radar, 104... Small flying object, 105... Wind sensor, 106... Wind conditions, 107... Weather company, 108... House, 109... No-fly area, 110... Building, 111... Control center, 201... Control unit (CPU), 202... Memory, 203... Communication device, 204...display device, 205...input device, 303...GNSS (Global Navigation Satellite System), 304...storage device, 305...control unit (CPU), 306...memory, 400...small aircraft side system, 401...environment recognition unit, 402...self-position estimation unit, 403...environment information transmission unit, 404...route information reception unit, 405... Flight control unit, 406, environmental information receiving unit, 407, environmental prediction unit, 408, transfer determination unit, 409, landing point determination unit, 410, vehicle determination unit, 411, transfer point determination unit, 412, flight route calculation unit, 413, route information transmission unit, 414, location table, 415, flight plan table, 416, business partner table, 417, Input section, 418... operator, 419... traffic management device side system, 601... landing point, 602... meeting point, 603, vehicle management company, 604... passenger, 605... cargo, 606... vehicle, 607... destination, 701... station, 1801... display screen, 1802... factory, 1803... mouse pointer, 1804... specified range

Claims

1. Based on self-location information of the aircraft, surrounding environment information of the aircraft, location information which is information of candidates for alternative landing sites where the aircraft will land, flight plan information to the destination of the aircraft, and ground vehicle information which is information of candidates for ground vehicles to which the aircraft will be transferred, a transfer determination unit that determines the alternative landing site and the ground vehicle for transporting the cargo of the aircraft from the alternative landing site to the destination; An operation management device characterized by:

2. In the operation management device according to claim 1, The location information includes information on a candidate transfer point for transferring from the alternative landing point to the ground vehicle; The transfer determination unit determines the alternative landing site, the transfer site, and the ground vehicle for transporting the transported goods of the air vehicle from the transfer site to the destination. An operation management device characterized by:

3. 3. The traffic management device according to claim 2, An environmental information receiving unit that receives disruption information including information regarding a type and a location of an event that disrupts the operation of the aircraft or the transportation of the transported goods; The transfer determination unit determines the urgency of the failure and the conditions of the alternative landing site based on the failure information, determining the alternate landing site, the transfer site, and the ground vehicle for transporting the air vehicle's payload from the transfer site to the destination; An operation management device characterized by:

4. In the operation management device according to claim 3, The location information includes information regarding whether the transfer point candidate is related to public transportation, When the designated landing point is a public transportation facility, the transfer determination unit determines the public transportation facility for transporting the transported goods of the aircraft to the alternative landing point and the destination based on the location information. An operation management device characterized by:

5. In the operation management device according to any one of claims 2 to 4, the location information includes information regarding whether the ground vehicle can park at the alternative landing site candidates and the transfer site candidates; When the ground vehicle can be parked at the alternative landing site candidate, the transfer determination unit determines the alternative landing site and the ground vehicle for transporting the transported goods of the aircraft from the alternative landing site to the destination; When the ground vehicle cannot be parked at the alternative landing site candidate, the transfer determination unit determines the alternative landing site, the transfer site where the ground vehicle can be parked, and the ground vehicle for transporting the transported goods of the aircraft from the transfer site to the destination. An operation management device characterized by:

6. In the operation management device according to claim 1, a flight path calculation unit that calculates a flight path for the flying object to land at the alternative landing site; A route information transmission unit that transmits the flight route to the flying object. An operation management device characterized by:

7. In the operation management device according to claim 1, The surrounding environment information includes flat land information that measures the flat land area around the aircraft, and visibility level information that indicates the degree of visibility. The transfer determination unit searches for candidates for the alternative landing site based on the self-location information and the surrounding environment information. An operation management device characterized by:

8. In a traffic management method in which a traffic management device manages the traffic of an aircraft, Based on the self-location information of the aircraft, the surrounding environment information of the aircraft, the location information which is information of candidates for alternative landing sites where the aircraft will land, the flight plan information to the destination of the aircraft, and the ground vehicle information which is information of candidates for ground vehicles to which the aircraft will be transferred, The operation control device determines the alternative landing site and the ground vehicle for transporting the air vehicle's payload from the alternative landing site to the destination. A traffic management method comprising:

9. In the operation management method according to claim 8, The location information includes information on a candidate transfer point for transferring from the alternative landing point to the ground vehicle; The operation control device determines the transfer point, the alternative landing point, and the ground vehicle for transporting the air vehicle's payload from the transfer point to the destination. A traffic management method comprising:

10. 10. The traffic management method according to claim 9, The operation management device receives fault information including information regarding the type and location of an event that impedes the operation of the aircraft or the transportation of the transported item, Based on the obstacle information, determine the urgency of the obstacle and the conditions of the alternative landing site; determining the alternate landing site, the transfer site, and the ground vehicle for transporting the air vehicle's payload from the transfer site to the destination; A traffic management method comprising:

11. In the operation management method according to claim 10, The location information includes information regarding whether the transfer point candidate is related to public transportation, When the designated landing site is a public transportation facility, the operation management device determines the public transportation facility for transporting the cargo of the aircraft to the alternative landing site and the destination based on the site information. A traffic management method comprising:

12. In the operation management method according to any one of claims 8 to 11, the location information includes information regarding whether the ground vehicle can park at the alternative landing site candidates and the transfer site candidates; When the operation management device determines that parking of the ground vehicle is possible at the alternative landing site candidate, the transfer determination unit determines the alternative landing site and the ground vehicle for transporting the transported goods of the aircraft from the alternative landing site to the destination, When the ground vehicle cannot be parked at the alternative landing site candidate, the transfer determination unit determines the alternative landing site, the transfer site where the ground vehicle can be parked, and the ground vehicle for transporting the transported goods of the aircraft from the transfer site to the destination. A traffic management method comprising:

13. In the operation management method according to claim 8, The operation management device calculates a flight path for the aircraft to land at the alternative landing site, Transmitting the flight path to the air vehicle A traffic management method comprising:

14. In the operation management method according to claim 8, The surrounding environment information includes flat land information that measures the flat land area around the aircraft, and visibility level information that indicates the degree of visibility. The operation management device searches for candidates for the alternative landing site based on the self-location information and the surrounding environment information. A traffic management method comprising:

15. an operation management device having: a transfer determination unit that determines an alternative landing site and a ground vehicle for transporting the aircraft's goods from the alternative landing site to the destination based on self-location information of the aircraft, surrounding environment information of the aircraft, location information which is information on candidate alternative landing sites where the aircraft will land, flight plan information to the destination of the aircraft, and ground vehicle information which is information on candidate ground vehicles for transfer; a flight path calculation unit that calculates a flight path for the aircraft to land at the alternative landing site; and a route information transmission unit that transmits the flight path to the aircraft; and an aircraft having an environmental information transmission unit that transmits the surrounding environment information to the traffic management device, a route information receiving unit that receives flight route information from the traffic management device, and a flight control unit that controls flight based on the route information received by the route information receiving unit. A traffic management system characterized by the above.

Citation Information

Patent Citations

  • Control system

    JP2022041835A

  • Server, method, and program

    JP2023059674A

  • Unmanned aerial vehicle systems

    US20220223056A1

  • Route retrieval device, route retrieval method, route retrieval program and recording medium

    WO2009096021A1

  • Management device, program, system, and method

    JP7068386B2